Laserfiche WebLink
Well 40 Programming and Consulting Services Scope of Work <br />EA Project Number: EA25CSAI 60, 0.0.0 <br />4.13Value Added Services <br />ENTERPRISE <br />AUTOMATION <br />AT -TECH -NY <br />There are several tasks that are necessary for the completion and success of each site capital <br />project but were not included in the City's RFP (ex. Project initiation, key design document <br />development, commissioning practices, etc.). These tasks have proven critical in maintaining <br />project budgets, schedules, and deliverable quality. Though they are labeled as'Value Added <br />Services', we consider them non -optional scope. <br />4.13.1 Project Initiation and Meetings <br />4.13.1.1 Execution Planning <br />Following receipt of a Notice to Proceed or Purchase Order, execution planning will be the first <br />technical task of this contract. This crucial engineering activity involves documenting the <br />systematic process and milestones required to produce each deliverable. <br />Draft execution plans are created at the Initiation Stage and are frequently updated. This ongoing <br />process helps the team accurately track progress and predict future performance. <br />Additionally, execution planning is an essential part of EA's schedules and quality management <br />program. They ensure that resource needs and technical risks are identified as early as possible. <br />4.13.1.2 Internal Kickoff <br />Once the project has been set up in our accounting system and an engineering team has been <br />established, they will perform an internal team kickoff to review this proposal and discuss: <br />1. Client background, project background, and project goals <br />2. Project scope, budget, and milestones/schedule <br />3. All available relevant documentation (specs, designs, etc...) <br />During or shortly after the internal kickoff, EA will develop a formal risk register to track known or <br />potential project risks (commercial, technical, coordination, etc.) and mitigation strategies. The <br />risk register will be updated on a regular basis throughout the life of a project and is available for <br />client review at any time. <br />4.13.1.3 Project Kickoff Meeting <br />Following the internal kickoff meeting, EA will prepare for a formal kickoff meeting with the City. <br />We will release an agenda at least one week prior to the meeting. EA's project team, including <br />project engineers and the project manager, will attend the formal kickoff meeting. <br />4.13.1.4 Internal Team Check -in Meetings <br />Brief check -in meetings between the EA PM and engineering project team will be conducted <br />regularly throughout the project. These meetings are used to align all members of our team on <br />overall project status, budget, schedule, and scope. The risk register is also updated as known <br />risks are averted or mitigated and new risk scenarios are identified. <br />These formal meetings are a critical component to the success of a project as they facilitate and <br />ensure team coordination and collaboration on a regular basis. <br />4.13.2 Specifications <br />In addition to the Functional Specification, EA will need to develop: <br />