1 259600v1
FIRST AMENDMENT TOAGREEMENTTHIS FIRST AMENDMENT TO AGREEMENT (Amendment) made and entered into as of this ____ day of _______________, 2024, (Effective Date) amends the Agreement entered into between the CITY OF FRESNO, a California municipal corporation ( City), and Partners in Control Inc., dba Enterprise Automation, a California corporation (Consultant). RECITALS WHEREAS, the City and Consultant entered into an agreement on March 25, 2024, (Agreement) to provide Consulting services for on-call Supervisory Control and Data Acquisition support services (Project) for a total fee not to exceed Four-Hundred Fifty Thousand Dollars ($450,000); and WHEREAS, the City desires to expand the scope of work to include the Northeast Fresno Surface Water Treatment Facility M580 Programmable Logic Controller Conversion; and WHEREAS, the City and the Consultant desire to expand the scope of services as described in Exhibit A, including all work incidental to, or necessary to perform, such services even though not specifically described in Exhibit A; and WHEREAS, the City and the Consultant desire to increase compensation by $200,000, for satisfactory performance of all services required or rendered pursuant to this Agreement which shall be a total fee not to exceed Six-Hundred Fifty Thousand Dollars ($650,000), paid on a time and materials basis in accordance with the schedule of fees contained in Exhibit A, WHEREAS, with entry into this Agreement, the Consultant agrees it has no claim, demand, or dispute against the City. AGREEMENT NOW, THEREFORE, the Parties agree that the aforesaid Agreement be amended as follows: 1. The recitals to this Amendment are incorporated and made a part of theAgreement. 2. The Agreement is amended to expand the scope of services indicated inExhibit A, attached hereto and incorporated herein by reference. 3. Section 3(a) of the Agreement is amended in its entirety to read as follows:“(a) The Consultant’s sole compensation for satisfactory performance of allservices required or rendered pursuant to this Agreement shall be a total fee not to exceed Six-Hundred Fifty Thousand Dollars ($650,000), paid on a time and materials basis in accordance with the schedule of fees contained in Exhibit A, pursuant to Subsection (c) below and authorized in writing by the Director.4. Except as otherwise provided herein, the Agreement entered into by theCity and the Consultant on March 25, 2024, remains in full force and effect. 2 259600v1
IN WITNESS WHEREOF, the parties have executed this Amendment at Fresno, California, the day and year first above written.CITY OF FRESNO, A California municipal corporation By:Brock D. Buche, PE, PLS Director Public Utilities APPROVED AS TO FORM: ANDREW JANZ City Attorney By:Christine C. Charitar DateDeputy City AttorneyATTEST:TODD STERMER, CMC CITY Clerk By:Date PARTNERS IN CONTROL INC., dba ENTERPRISE AUTOMATION, a California CorporationBy:Name: Title: (If corporation or LLC., Board Chair, Pres. or Vice Pres.) By: Name: Title: (If corporation or LLC., CFO, Treasurer, Secretary or Assistant Secretary) Addresses: CITY:City of FresnoAttention: Joseph De George Project Manager 1626 E Street Fresno, CA 93706 Phone: (559) 621-1619 E-mail: [email protected]: Enterprise Automation Attention: Josh Riley President 9050 Irvine Center Dr. Irvine, CA 92618Phone: (949) 769-6000E-mail: [email protected]: Exhibit A
210 Goddard Irvine CA 92618 USATel 949-769-6000 Fax 949-769-6005www.eaintegrator.comPage Number: 0 of 18 Scope of WorkNE SWTF M580 Conversionv.1.0.0PROJECT NUMBER:EA24COF171Prepared for: On: City of Fresno May 24, 2024 Prepared by:McKenna AndersonReviewed by:Zack GentryAddress:Phone:9050 Irvine Center Dr. (949) 769-6000 Irvine, CA 92618 Web:www.eaintegrator.com
NE SWTF M580 Conversion Scope of WorkEA Project Number:EA24COF171, v1.0.0 9050 Irvine Center Dr Irvine CA 92618 USATel 949-769-6000 Fax 949-769-6005www.eaintegrator.comScope of WorkNE SWTF M580 ConversionPage Number: 1 of 15 HistoryRevisionDateDescriptionofChangeAuthorReviewed1.0.005/24/2024OriginalMBAZGTable of ContentsHistory ............................................................................................................................................................. 1Table of Contents .......................................................................................................................................... 1Acronyms and Terms ................................................................................................................................... 21 Proposal Background ............................................................................................................................... 32 Project Goals .............................................................................................................................................. 43 Project Approach ...................................................................................................................................... 44 Assumptions .............................................................................................................................................. 45 Scope of Work ........................................................................................................................................... 55.1 Project Management ....................................................................................................................... 55.2 Project Initiation ................................................................................................................................ 6Project Initiation Deliverables ................................................................................................................. 75.3 Conversion & Design Review .......................................................................................................... 7Conversion & Design Review Deliverables ........................................................................................... 95.4 Configuration ..................................................................................................................................... 9Configuration Deliverables ................................................................................................................... 105.5 Testing ............................................................................................................................................. 11Testing Deliverables .............................................................................................................................. 115.6 Commissioning .............................................................................................................................. 11Commissioning Deliverables ............................................................................................................... 125.7 Closeout .......................................................................................................................................... 12Closeout Deliverables ............................................................................................................................ 126 Assumptions & Clarifications .............................................................................................................. 136.1 I/O Count ......................................................................................................................................... 137 Schedule .................................................................................................................................................. 148 Cost Estimate ......................................................................................................................................... 148.1 Travel ............................................................................................................................................... 149 Conclusion ............................................................................................................................................... 1410 Terms & Conditions ........................................................................................................................... 1511 Appendix A: Deliverables List ........................................................................................................... 16Client Deliverables ...................................................................................................................................... 16Internal Deliverables .................................................................................................................................. 1612 Appendix B: Cost Estimate Details ................................................................................................. 1713 Appendix C: Rates .............................................................................................................................. 18 NE SWTF M580 Conversion Scope of WorkEA Project Number:EA24COF171, v1.0.0 9050 Irvine Center Dr Irvine CA 92618 USATel 949-769-6000 Fax 949-769-6005www.eaintegrator.comScope of WorkNE SWTF M580 ConversionPage Number: 2 of 15 Acronyms and TermsFor the remainder of the document the following acronyms will be used.TermDescriptionCOF, the CityCity of FresnoDTM Device Type ManagerEAEnterprise Automation (Integrator)EU Engineering UnitNOCNetwork Operations CenterPLC Programmable Logic ControllerPMProject ManagerSCADASupervisory Control and Data Acquisition (refers to the entire automation system)UMACUnity M580 Application Converter NE SWTF M580 Conversion Scope of WorkEA Project Number:EA24COF171, v1.0.0 9050 Irvine Center Dr Irvine CA 92618 USATel 949-769-6000 Fax 949-769-6005www.eaintegrator.comScope of WorkNE SWTF M580 ConversionPage Number: 3 of 15 1 Proposal BackgroundEnterprise Automation (EA) upgraded the City of Fresno’s (the City) NE SWTF almost a decade ago. Since then, the PLCs and SCADA system have worked reliably with little issue. However, after almost 10 years, the Schneider Electric Quantum PLCs have reached their end-of-life period and will soon be discontinued. Because of their obsolescence, the Quantum PLCs need to be replaced. The City has proactively planned to replace the Quantum PLCs with new Modicon M580 PLCs. EA has worked with the Modicon series for almost a decade and is certified in Quantum Modernization from Schneider Electric. Few other integrators have this level of experience, let alone approval from the manufacturer. Due to EA’s experience with the software and with the City’s facilities, we are best equipped to complete the City’s conversion. Additionally, because the City decided to use the M580 PLCs, they will be able to reduce the amount of facility downtime needed by using wiring adapters that will connect the old wiring harnesses to the new I/O modules. The addition of a new PLC and Ethernet I/O racks in the panels may require panel modifications due to space, power, wire length, networking, etc. The City has already generated a Bill of Materials (BOM), which EA will review and confirm that all required items and quantities were purchased. If EA notices any discrepancies, EA will alert the City. EA will develop and submit work orders to the City for the necessary panel adjustments.The goal of this project is to convert the Plant Quantum PLCs while maintaining existing functionality and avoiding extensive changes. The hardware modifications will mostly be performed by the City staff while EA will support and help mitigate risk. EA will perform the software updates by converting the PLC programs using the Schneider ElectricUMAC converter tool. This tool automates some of manual tasks required for converting from Quantum to M580, but there are still many manual changes that will need to be performed to ensure the system functions as it did before.While the PLCs will be upgraded as a part of this project, EA anticipates that there will not be any changes to Citect SCADA system.
NE SWTF M580 Conversion Scope of WorkEA Project Number:EA24COF171, v1.0.0 9050 Irvine Center Dr Irvine CA 92618 USATel 949-769-6000 Fax 949-769-6005www.eaintegrator.comScope of WorkNE SWTF M580 ConversionPage Number: 4 of 15 2 Project GoalsThe goals of this project are:1. Modernize the 2 Quantum PLCs to M580 PLCs to reduce obsolescence (Main PLC and Actiflo PLC)2. Ensure all of the City’s documentation is kept up to date to support future expansions3. Minimize downtime during the cutover3 Project Approach1. Reduce risk by validating BOM and develop procedures for wiring cutover in each panel.2. Document conversion process and leverage tools or procedures to mitigate reprogramming required.3. Develop detailed testing procedures on EA test platform to validate the conversion and ensure no SCADA changes are required.4 AssumptionsPlease see Section 6 for Assumptions and Clarifications. Note: many assumptions and clarifications listed must be considered in the context of the content in this scope, otherwise they may seem unclear or inconsistent.
NE SWTF M580 Conversion Scope of WorkEA Project Number:EA24COF171, v1.0.0 9050 Irvine Center Dr Irvine CA 92618 USATel 949-769-6000 Fax 949-769-6005www.eaintegrator.comScope of WorkNE SWTF M580 ConversionPage Number: 5 of 15 5 Scope of WorkThis section details the scope of work for tasks included in the estimate in Appendix B, which are arranged to represent the expected order of execution.At the bottom of each section will be a summary of the deliverables to be produced.Client deliverables: items EA will produce and submit to the clientInternal deliverables: items EA will produce for internal use (available by request) 5.1 Project ManagementEA will provide a dedicated project manager to be the main point of contact and steward all communication through EA. The PM has primary responsibility for this project’s scope, budget, and schedule. The PM will prepare a project schedule, publish it, and periodically update it as the project unfolds. At the commencement of the project, the PM will submit the schedule to the City in electronic format.Throughout the life of the project, the PM will perform all commercial, budget, and project tracking related updates. The labor estimate for project management is comprised of the “Initiation” sheetin the cost estimate in Appendix B, plus a fixed percentage of all other engineering hours (as shown in the estimate). For each workshop or meeting involving key project decisions, EA’s PM will draft and release meeting minutes with action items and dates assigned within one week.Key Project Management Roles and Activities:1. Primary point of contact, communications coordination2. Project scheduling3. Internal project team meeting coordination4. Project status tracking (daily/weekly)5. Project status communication with the City6. Project invoices and tracking report (monthly)7. Project coordination8. Procurement oversight5.1.1 PM communications plan5.1.1.1 Project status updatesThe PM will contact the City’s project manager a minimum of once every two weeks, via email, to provide status updates for all ongoing tasks. This standard practice helps to maintain an open line of communication when current project activities do not require direct contact between EA and the City.
NE SWTF M580 Conversion Scope of WorkEA Project Number:EA24COF171, v1.0.0 9050 Irvine Center Dr Irvine CA 92618 USATel 949-769-6000 Fax 949-769-6005www.eaintegrator.comScope of WorkNE SWTF M580 ConversionPage Number: 6 of 15
5.2 Project InitiationThe “Initiation” sheet in the estimate includes activities associated with starting the project. This includes setting up the project in our accounting, project tracking, and resource planning systems.5.2.1 Internal kickoffOnce a PM is assigned and an engineering team has been established, they will perform an internal team kickoff to review the following:1. Customer history2. Relevant parties involved3. Relevant documentation (specs, designs, etc…)4. Project scope, budget, schedule, and risk areasThe risk register is an especially valuable tool that is developed during or shortly after the internal kickoff. Engineers use it to track any and all risks (commercial, technical, coordination, etc.) and develop mitigation strategies. The risk register is updated on a regular basis throughout the life of a project and is available for client review at any time.5.2.2 Project kickoff meetingFollowing the internal kickoff meeting EA will prepare for a formal kickoff meeting. We will release an agenda at least one week prior to the meeting. EA’s project team, including project engineers and the project manager, will attend the formal kickoff meeting.5.2.3 Overheads5.2.3.1 Execution planningExecution planning is a standard engineering activity where the engineers document the systematic process required to generate each deliverable. These plans are continually updated as engineering work is completed such that the team can accurately predict their future budget performance. This is an elementary activity of EA’s preparation and quality control process.EA engineers (typically the Lead Engineer) will set up the execution plan templates prior to the kickoff meeting. Their templates are based on this scope and estimate.Once the kickoff meetings are complete and mutual understanding of the scope is confirmed, EA will update and add more detail to the execution plans developed previously. 5.2.3.2 Team check-in meetingsInternal project team meetings between the EA PM and EA engineering staff are conducted regularly during all projects. These meetings are used to discuss overall project status, budget, schedule, scope, and risk scenarios. The risk register is updated as known risks are averted or mitigated and new risk scenarios are identified.We consider these formal meetings a critical component to our success as they facilitate team coordination and collaboration in an organized and controlled manner.
NE SWTF M580 Conversion Scope of WorkEA Project Number:EA24COF171, v1.0.0 9050 Irvine Center Dr Irvine CA 92618 USATel 949-769-6000 Fax 949-769-6005www.eaintegrator.comScope of WorkNE SWTF M580 ConversionPage Number: 7 of 15 Project Initiation DeliverablesClientDeliverables1. Kickoff meeting minutes2. Project Schedule in Gantt formatInternalDeliverables1. Execution plans2. Initial risk register5.3 Conversion & Design Review5.3.1 Conversion Initial StepsTo begin the software conversion from the Quantum PLC to the Schneider Electric M580 PLC, EA will start by setting up virtual machine with the latest version of Schneider Electric’s conversion software. EA will verify we have the latest Quantum project files from the City for the Main PLC and the Actiflo PLC which are the two Quantum PLCs that are going to be converted as a part of this project. EA will need the latest project files in order to run it through Unity M580 Application Converter (UMAC). The UMAC will convert the old Quantum application into the new M580 application so that the M580 can be used without needing major rework of the code base. This conversion software will not provide the City with a ready-to-use program. EA has already run through a trial conversion and identified a number of errors or program sections that will no longer function after the conversion. These will need to be reviewed and corrected manually.After the conversion, EA will confirm with the City what version of Control Expert that they want to use. We currently believe it will be version 14.1 since this is currently used in the Groundwater SCADA system for new sites. The team will need to verify this version supports the M580 hardware that was selected. Following this decision, EA will update the test platform VM with the correct version and then update the program rack layouts in Control Expert based on the BOM developed by the City. EA will confirm that the BOM has the correct parts for this conversion. The Quantum I/O racks could support up to 16 modules while the new X80 I/O racks can only support up to 12. There will need to some key architectural changes made to the software to support this, but the hardware changes will also need to be evaluated as part of the next task.
NE SWTF M580 Conversion Scope of WorkEA Project Number:EA24COF171, v1.0.0 9050 Irvine Center Dr Irvine CA 92618 USATel 949-769-6000 Fax 949-769-6005www.eaintegrator.comScope of WorkNE SWTF M580 ConversionPage Number: 8 of 15 The following panels have been identified as part of the M580 hardware conversion: 1. PCM1 (Hot Standby Main PLCs + 1 RIO rack)2. PCM2 (2 RIO racks)3. PCM3 (RIO rack)4. PCM4 (RIO rack)5. PCM5 (RIO rack)6. PCM6 (RIO rack)7. 3-LCP-1 (Actiflo)RIO-3 is already on the X80 I/O platform since this was added as part of the CO2 System Upgrade project.The team will also need to update the other plant PLC programs to align with the new Main and Actiflo PLC software version. This includes the Ozone PLC programs, as well as the RWP PLC. The software upgrade process for these programs is expected to be simple and EA is assuming there are no major conflicts with versions that would cause modifications to the programs other than re-building the project in the new version. 5.3.2 Review Documentation and HardwareEA will review the existing modules against the proposed BOM to make sure the correct modules and quantities are available for this conversion. While the number of I/O will remain the same, the number of modules may change. Because the M580 PLC supports fewer modules than the Quantum PLC, it’s expected to require backplanes via rack expanders. Swingarm I/O adapters will connect the original I/O to the additional modules.EA will need to review photos of the District’s panels to ensure that the panels are deep enough for this conversion project. Depending on concerns raised by the EA project team, this may require the City to take new photos or provide dimensions of the current panels. EA has performed a preliminary review of the hardware list, and it is unlikely that the list will need to change from what was originally quoted. If the team identifies something missing from the design, EA will create a BOM if needed, which could include items such as fiber media converters, additional I/O modules, backplanes, fiber, or Ethernet cables, etc. EA is anticipating this will be a small list of items, if any.5.3.3 Update I/O ListThough the number and type of I/O will remain the same, the I/O list will still need to be updated to accommodate the conversion changes. The updated list will need to reflect each I/O point’sexisting rack slot channel and clearly show how each I/O point will be mapped to the new rack slot channel. The team will first validate the current as-built I/O list(s) match the existing programs to ensure that we capture any changes that have occurred in the last few years. The rack, slot, channel – as well as engineering units and electrical characteristics will need to be reviewed (e.g. 0-10V vs. 4-20mA).
NE SWTF M580 Conversion Scope of WorkEA Project Number:EA24COF171, v1.0.0 9050 Irvine Center Dr Irvine CA 92618 USATel 949-769-6000 Fax 949-769-6005www.eaintegrator.comScope of WorkNE SWTF M580 ConversionPage Number: 9 of 15
5.3.4 Work OrdersEA will develop work orders for the 7 panels (10 existing backplanes) that are going to be modified during this conversion. Depending on the extent of changes needed, EA will either need to coordinate remotely with the City for new dimensions or go on-site to verify panel size and record the new dimensions required for the conversion. When rack extenders are used, using the I/O adapters may become a concern since the wiring to the old module may not reach the new rack location. The team will identify these locations and have the City staff investigate the panel wiring as needed. The cutover plan may require re-wiring modules in these cases.The work orders will also need to identify how to deal with the existing fiber connections to ensure that the redundant ring for the plant can be transferred onto the new hardware and it’s clear where cables need to be connected.5.3.5 Network Drawing UpdatesEA will need to update the network design in order to reflect the installation of the new M580 PLCs in the system. Additionally, EA will ensure the new fiber connections needed for the new racks and media converters are documented. Conversion & Design Review DeliverablesClientDeliverables1. Work orders2. Updated network drawingInternalDeliverables1. Acquire VMs and project files from the City2. Compile notes from the documentation and hardware review5.4 Configuration5.4.1 Conversion I/O UpdatesEA will review the new I/O list and update module configurations since the old module configuration settings do not transfer to the new modules. EA will also determine the range (+/-10V or 4-20mA) as well as the scaling needed for the analog I/O section re-writes. Each module will need to be updated manually to match the old configuration.After the I/O modules have been validated, EA will validate the digital I/O assignment by spot checking and comparing addressing across all digital and analog I/O in the new mapping sections, which is an auto-generated structured text. This validation is necessary to the success of the overall conversion because it ensures that the I/O line up on the cards correctly. EA expects that there may need to be some manual changes to the auto-generated structured text code since rack extenders are going to be used which will require manual changes to the position of some of the modules.
NE SWTF M580 Conversion Scope of WorkEA Project Number:EA24COF171, v1.0.0 9050 Irvine Center Dr Irvine CA 92618 USATel 949-769-6000 Fax 949-769-6005www.eaintegrator.comScope of WorkNE SWTF M580 ConversionPage Number: 10 of 15 EA will also need to reconfigure the analog I/O assignment. While the conversion process will auto-generate structured text sections to remap tags to the new channels, this will not work based on how the PLCs were programmed. The original programmer used a legacy method which will not convert over to the new M580 scheme.EA will accomplish this by re-mapping all analog inputs by creating an automated tool to reduce risk and reduce testing time. As part of the re-mapping, EA will configure all the scaling to get values to the correct engineering units. This must be done very carefully to maintain the exact same scaling as previously configured. EA engineers will develop a procedure to record and validate the channel locations and scaling in the old program and the new program match exactly. 5.4.2 Communications UpdatesAs a final part of the M580 PLC conversion, EA will need to update all communications logic and configuration with the new M580 program. There are files (DTMs) that need to be imported into the PLC program which contain the data map to communicate to some of the field devices. These do not carry over during the conversion and will need to be added to facilitate communication between the new PLC and the field devices as it was setup in the previous program. EA will also validate the communication card setup and its addressing and security. During this process, EA will verify the custom hot standby failover logic for field device NOC. Additionally, the NOC communications will need to be redone for all devices since this configuration must also be manually transferred and is not covered by the conversion process. This can be recreated by documenting the old configuration and reconfiguring it to match in the new system.EA has also identified that the communication function block programming is another area that will need to be modified because the communication function references the hardware location of the communication module. This will change slightly on the new system since the rack size is changing and will need to be updated to match the new layout to ensure its working.The newer models of Schneider Electric Modicon PLCs do not allow certain configurations within the Modbus addressing of the PLC. It will not allow engineers to assign a 2-register data type to an odd register number. All of the REAL or other double type tag addresses have to be shifted from starting with an odd number to starting with an even number because even numbered addresses are the standard for the M580. This happens automatically in the program conversion, but this may have an impact on the SCADA communications or communications to other PLCs which will need to be investigated by the team. Based on our current understanding, EA is assuming this will require minimum changes to the program but will inform the City if additional effort is required to update the program.Configuration DeliverablesClientDeliverables1. NoneInternalDeliverables1. None NE SWTF M580 Conversion Scope of WorkEA Project Number:EA24COF171, v1.0.0 9050 Irvine Center Dr Irvine CA 92618 USATel 949-769-6000 Fax 949-769-6005www.eaintegrator.comScope of WorkNE SWTF M580 ConversionPage Number: 11 of 15
5.5 Testing5.5.1 Test DocumentationEA will develop test documentation to guide the testing process. This series of checklists and procedures ensures that all test areas are covered and that no elements are forgotten during testing. EA will develop documentation for testing the rack, I/O points, communications, and confirming that SCADA is receiving proper data. All manual modifications to the program will need to be validated. EA engineers will not be able to test communications to field devices while in the office since we do not have the hardware available to connect. Two engineers will be present for testing as a form of quality control.5.5.2 Internal TestingEA will conduct internal testing point to point against the test documentation. EA will ensure that the rack, I/O points, and communications are working properly and confirm that SCADA is receiving proper data. If EA encounters any nonconformances, EA will address them, retest the system, and internally approve it before deploying it onsite.Testing DeliverablesClientDeliverables1. NoneInternalDeliverables1. Test documentation5.6 Commissioning 5.6.1 PreparationIn preparation for deployment, EA will develop a series of checklists and procedures that the EA team will follow while deploying onsite. EA will use this documentation as a guide for general deployment steps as well as more specific actions such as an I/O checkout and supporting the City staff during the hardware cutover. EA will submit the deployment documentation to the City for approval before it is used onsite.5.6.2 Deployment Planning WorkshopEA will attend a deployment planning workshop with the City to review the details of the deployment. EA and the City may discuss items such as scheduling and coordination, downtime, startup, and installation. This workshop ensures that the City and EA agree on the deployment execution plan and are working cohesively to get the new M580 PLCs deployed.
NE SWTF M580 Conversion Scope of WorkEA Project Number:EA24COF171, v1.0.0 9050 Irvine Center Dr Irvine CA 92618 USATel 949-769-6000 Fax 949-769-6005www.eaintegrator.comScope of WorkNE SWTF M580 ConversionPage Number: 12 of 15
5.6.3 DeployDuring deploy, the EA team will assist the City and review hardware install that the City staff will be performing. The team will need to install the latest Control Expert programming software on the production Programmer virtual machine. The team may need to update the firmware of the new PLCs at this time. EA staff will deploy the new program to the new M580s, or other PLCs that require updates for the new software version. Next the team will validate communications to SCADA, the field devices, and other PLCs. The team will then spend time conducting I/O checkouts with City staff. Because there are hundreds of I/O points scattered across 10 different I/O racks, EA will not be checking every individual I/O point but will be examining a variety of I/O points, specifically one of each type of I/O from each panel. This will ensure that the conversion wiring adapter were properly aligned with each the of modules that we were expecting to use.The team may identify that the I/O wiring adapters will not work in some cases and cannot be used. In these cases, the modules will need to be re-wired for each channel. In these cases, the team will need to verify all I/O points on the module to ensure that they are all functioning. Depending on how many modules need to be fully rewired, additional time may be required by the team to validate all I/O points. After the deployment of the new M580 PLCs is complete, EA will be available to provide as needed support for the City during the plant startup. It is currently unclear if the plant startup will occur directly after the hardware conversion and I/O validation is complete. If it needs to happen at a later date, then EA will assist with troubleshooting to the best of our ability from the office, or a separate support visit will need to be scheduled outside the scope of this project.Commissioning DeliverablesClientDeliverables1. NoneInternalDeliverables1. Deployment documentation5.7 CloseoutAt the end of the project, EA will provide the city with as-built documentation. The as-builts included are the updated I/O list and network drawings to capture any changes made during the commissioning phase.Closeout DeliverablesClientDeliverables1. I/O list2. Network designInternalDeliverables1. None NE SWTF M580 Conversion Scope of WorkEA Project Number:EA24COF171, v1.0.0 9050 Irvine Center Dr Irvine CA 92618 USATel 949-769-6000 Fax 949-769-6005www.eaintegrator.comScope of WorkNE SWTF M580 ConversionPage Number: 13 of 15 6 Assumptions & ClarificationsThe following assumptions and clarifications were used in preparing this proposal:1. EA will be onsite either during or directly after the City performs the hardware conversion. EA will not be performing any physical modifications to the panel hardware. 2. EA is not procuring any hardware.3. EA has not identified the need to make SCADA changes as part of this conversion. The project currently does not include time to make changes or deploy a new configuration to the CitectSCADA system.4. EA will be supporting programming and troubleshooting. A total of 40 hours have been allocated for this support and project contingency. 5. EA is not affiliated with any hardware or software manufacturer. EA is not responsible for implementing new firmware updates or patches outside the scope of this project. We will provide advice to our clients, who can choose to pursue in the event that such an update is required.6. Unless specifically indicated in this scope of work, design documentation developed through this project will not be stamped by a professional engineer.7. All submittals will be transmitted in electronic format (no hard copies will be provided) 8. Written approval (email or letter) from the City is required for all submittals within 10 business days of release by EA.9. Delays due to mechanical, electrical, or IT related issues, production scheduling constraints, or lack of system availability out of EA’s control, which result in additional site time, will be charged at EA’s standard hourly rates.6.1 I/O Count The cost estimate and scope of this proposal was developed based on the following I/O information.9EIORacks550 I/O combined1RackwithCPU&I/OforActifloPLC143 I/OEA expects that this count will change during the project and has budgeted for some minorvariability. If the I/O count changes significantly following the City’s acceptance of this proposal and release of work against it, additional budget may be required. EA will work with the City to mitigate this risk.
NE SWTF M580 Conversion Scope of WorkEA Project Number:EA24COF171, v1.0.0 9050 Irvine Center Dr Irvine CA 92618 USATel 949-769-6000 Fax 949-769-6005www.eaintegrator.comScope of WorkNE SWTF M580 ConversionPage Number: 14 of 15 7 ScheduleThe PM will release an initial schedule upon project initiation. 8 Cost EstimateThe tasks to be performed along with the estimated time to complete the tasks are detailed in the attached cost estimate (Appendix B). Work under this proposal is on a time and expenses basis, and the pricing in Appendix B is an estimate only made in good faith without consideration for delays and unknowns.Enterprise Automation will continually track task progress against this estimate and will inform the City of any anticipated projected overruns. Any additional hours required to perform the specified tasks will be submitted to the City as a change order request. The decision to continue the work or consider alternative options will therefore remain with the City.Approval of any change order by the City will be required prior to Enterprise Automation commencing or continuing the work task in question.Billings will occur every month and will include man-hour break downs indicating hours expended, resources utilized, on a per task basis. Enterprise Automation will maintain an open line of communication with the City to discuss status of the work in progress, potential problems with scheduled work, changes in the estimated hours, and to coordinate up and coming tasks. 8.1 TravelAll travel is billed at cost according to the U.S. General Services Administration (GSA) for hotel and per diem rates and the IRS standard mileage rate as of May 24, 2024.9 ConclusionI welcome any further discussion that may facilitate the refinement of this scope of work. Please contact me at (949) 769-6000 x 122 or alternatively on my cell phone at (949) 584-3051 with any questions.Submitted byZack GentryAutomation Architect NE SWTF M580 Conversion Scope of WorkEA Project Number:EA24COF171, v1.0.0 9050 Irvine Center Dr Irvine CA 92618 USATel 949-769-6000 Fax 949-769-6005www.eaintegrator.comScope of WorkNE SWTF M580 ConversionPage Number: 15 of 15 10 T erms & ConditionsValidityThis proposal is valid for 60 days starting May 24, 2024. Please note that due to current supply chain and economic factors, hardware pricing and availability may change without notice.InvoicesBillings will occur every month and will include man-hour break downs indicating hours expended, resources utilized, on a per task basis. Enterprise Automation will maintain an open line of communication with the City to discuss status of the work in progress, potential problems with scheduled work, changes in the estimated hours, and to coordinate up and coming tasks.Any additions to the scope of work will be submitted to City of Fresno as a change order request. Approval of any change order by City of Fresno will be required prior to Enterprise Automation commencing or continuing the work task in question.PaymentPayment terms are 30 days net. If applicable, Paid when Consultant Paidterms will not be accepted.WarrantyA warranty is not provided by Enterprise Automation for any deliverables or work performed as part of this project. City of Fresno remains solely responsible for any warrantees for the facility and equipment.ResolutionofdisputesIf a dispute arises out of or relates to this scope of work and if the dispute cannot be settled through negotiation, the dispute shall be decided by arbitration administered by the American Arbitration Association under its Construction Industry Arbitration Rules, and judgment on the award rendered by the arbitrator(s) may be entered in any court having jurisdiction. The law governing this Contract shall be the place of the projects as shall the place of the arbitration. The prevailing party in the arbitration shall be entitled to recover its attorneys' fees, interest, and arbitration expenses as elements of any award.IntellectualpropertyAll designs, specifications, documentation, and software to be developed and provided by Enterprise Automation shall remain the sole intellectual property of Enterprise Automation. Following acceptance and final payment to Enterprise Automation, Enterprise Automation will grant to City of Fresno a perpetual, nontransferable, non-exclusive license to use the materials for their internal purposes only, including implementation at other City of Fresno-owned facilities.LimitofliabilityThe total liability of EA and City of Fresno to each other for any loss, indemnity, damage or delay of any kind except payment of the price will not under any circumstances exceed the lesser of twenty-five (25%) of the contract sum or the applicable insurance amounts covering the liability. Under no circumstances will Enterprise Automation or City of Fresno be liable to the other for any loss, indemnity, damage or delay arising out of its failure to perform due to causes beyond its reasonable control, including, without limitation, acts of God, interference by others, delays in receiving approvals or necessary information from each other, fires, strikes, floods, war, terrorism, riots, delays in transportation and adverse weather. Under no circumstances will either Enterprise Automation or City of Fresno be liable to each other for any special, incidental or consequential damages.Enterprise Automation is not liable for any loss, damage, expense, cost, injury, or loss of life occurring as a result of or arising from the use of any programmed, integrated, or commissioned product/s and/or Equipment by City of Fresno’s employees, customers, invitees, or any other person. Provided that, any liability of Enterprise Automation shall be reduced to the extent that such loss, damage, or injury was caused by or contributed to by the negligence of Enterprise Automation.NosolicitationofemployeesCommencing immediately, and continuing until a date one year after the date of final completion of the scope of work, EA and City of Fresno agree not to directly or indirectly employ, solicit for employment, or advise or recommend to any other person that such other person employ or solicit for employment, any person employed by or under contract to the other.EntireagreementThe scope defined in this document describes the complete project scope and sets forth the entire understanding and agreementbetween EA and City of Fresno. It supersedes all prior discussions and understandings in respect to the scope of this project, whether written or oral.
NE SWTF M580 Conversion Scope of WorkEA Project Number:EA24COF171, v1.0.0 9050 Irvine Center Dr Irvine CA 92618 USATel 949-769-6000 Fax 949-769-6005www.eaintegrator.comScope of WorkAppendix A: Deliverables List 11 Appendix A: Deliverables ListClient Deliverables1.Kickoff meeting minutes2.Project Schedule in Gantt format3.Work orders4.Updated network drawing5.I/O list6.Network designInternal Deliverables1.Execution plans2.Initial risk register3.Acquire VMs and project files from the City4.Compile notes from the documentation and hardware review5.Test documentation6.Deployment documentation FY24 Engineering Rates
9050 Irvine Center Dr, Irvine CA 92618 USATel 949-769-6000 Fax 949-769-6005www.eaintegrator.comV 1.0.0 Rate Classification1Standard RateAdmin$ 105.00 / hr.Engineering Intern$ 105.00 / hr.I&C Technician 1*$ 140.00 / hr.I&C Technician 2*$ 180.00 / hr.Electrical Engineer 2*$ 180.00 / hr.Electrical Engineer 3*$ 215.00 / hr.CAD*$ 155.00 / hr.Automation Project Engineer 1$ 212.00 / hr.Automation Project Engineer 2$ 258.00 / hr.Project Technical Lead$ 270.00 / hr.Project Manager 1$ 220.00 / hr.Project Manager 2$ 265.00 / hr.Automation Architect$ 280.00 / hr.Principal$ 335.00 / hr. *Through Tetra Tech1Rate classifications charged are based on a project role/responsibility basis, not titleduration if meaningful staff changes occur with prior notification.Service calls covered by an Enterprise Automation service contract are prioritized while all other service requests are dependent on existing schedules and the availability of engineering staff.ItemDescriptionTime and a halfOutside of normal business hours (8am-5pm), or time in excess of 10 hours per day (unless otherwise arranged)Double timeSaturday, Sunday, and holidays (unless otherwise arranged)ItemDescriptionTravel timeCharged at engineering ratesVehicle mileageAs per the published IRS mileage rate (if applicable)Travel expensesAt cost (if applicable)Meals and incidentalsGSA established per diem rate (if applicable)Payment terms Net 30 daysRateseffective11/1/2023through9/30/2024