My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Item 17 - SCADA Functional Specifications and Programming Services
Clerk
>
Agenda Packets / Staff Reports
>
City Council (2004 - Present)
>
2023
>
09/19/2023 Regular
>
Item 17 - SCADA Functional Specifications and Programming Services
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
10/24/2023 11:55:32 AM
Creation date
10/24/2023 11:34:08 AM
Metadata
Fields
Template:
City Clerk
Doc Type
Agenda Packet
Agency
Public Works
Item #
17
Date
9/19/2023
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
254
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
Cambridge Pump Station Func. Spec Dev & Programming Scope of Work ENTERPRISE <br />EA Project Number: EA23CSA090, 0.0.0 AUTOMATION <br />A TETRA TECH CO-HY <br />5.2 Project initiation <br />The "Initiation" sheet in the estimate includes activities associated with starting the project. This <br />includes setting up the project in our accounting, project tracking, and resource planning systems. <br />5.2.1 Execution planning <br />Execution planning is a standard engineering activity where the engineers document the <br />systematic process required to generate each deliverable. These plans are continually updated as <br />engineering work is completed such that the team can accurately predict their future budget <br />performance. This is an elementary activity of EA's preparation and quality control process. <br />EA engineers (typically the Lead Engineer) will set up the execution plan templates prior to the <br />kickoff meeting. Their templates are based on this scope and estimate. <br />Once the kickoff meetings are complete and mutual understanding of the scope is confirmed, EA <br />will update and add more detail to the execution plans developed previously. <br />5.2.2 Internal kickoff <br />Once a PM is assigned and an engineering team has been established, they will perform an <br />internal team kickoff to review the following: <br />1. Customer history <br />2. Relevant parties involved <br />3. Relevant documentation (specs, designs, etc...) <br />4. Project scope, budget, schedule, and risk areas <br />The risk register is an especially valuable tool that is developed during or shortly after the internal <br />kickoff. Engineers use it to track any and all risks (commercial, technical, coordination, etc.) and <br />develop mitigation strategies. The risk register is updated on a regular basis throughout the life of <br />a project and is available for client review at any time. <br />5.2.3 Project kickoff meeting <br />Following the internal kickoff meeting EA will prepare for a formal kickoff meeting. We will an <br />agenda at least one week prior to the meeting. EA's project team, including project engineers and <br />the project manager, will attend the formal kickoff meeting. <br />Meeting minutes will be published containing action items with assigned responsibilities and due <br />dates. <br />5.2.4 Team check -in meetings <br />Internal project team meetings between the EA PM and EA engineering staff are conducted <br />regularly during all projects. These meetings are used to discuss overall project status, budget, <br />schedule, scope, and risk scenarios. The risk register is updated as known risks are averted or <br />mitigated and new risk scenarios are identified. <br />We consider these formal meetings a critical component to our success as they facilitate team <br />coordination and collaboration in an organized and controlled manner. <br />
The URL can be used to link to this page
Your browser does not support the video tag.