210 Goddard Irvine CA 92618 USA Tel 949-769-6000 Fax 949-769-6005 www.eaintegrator.com Page Number: 0 of 22

Scope of Work

MAPS Rehabilitation v.3.0.0

PROJECT NUMBER: EA26CSM111

Prepared for: On:

City of Santa Monica July 2nd, 2026

Prepared by:

Stefan Prajogo

Reviewed by:

Zack Gentry Luke Stephenson

Address: 9050 Irvine Center Drive, Irvine, CA 92618 USA

Phone: (949) 769-6000

Web: www.eaintegrator.com http://www.eaintegrator.com/

MAPS Rehabilitation Scope of Work EA Project Number: EA26CSM111, v3.0.0

9050 Irvine Center Drive, Irvine, CA 92618 USA www.eaintegrator.com

Scope of Work MAPS Rehabilitation

Page Number: 1 of 21

History Revision Date Description of Change Author Reviewed

1.0.0 03/11/2026 Original SP ZG

2.0.0 03/24/2026 Added 10 client meetings during construction phase

SP ZG

3.0.0 07/02/2026 Included Ignition Edge Gateway setup and configuration

SP ZG

Table of Contents History Table of Contents Acronyms and Terms

1 Proposal Background 2 Project Goals 3 Assumptions 4 Supporting Documentation 5 Cost Estimate

5.1 Materials

5.2 Travel

6 Scope of Work

6.1 Project Management

6.2 Project Initiation

Project Initiation Deliverables

6.3 Meetings

Meetings Deliverables

6.4 Design

Design Deliverables

6.5 Panel Design

Panel Design Deliverables

6.6 Testing and Development Setup

Testing and Development Setup Deliverables

6.7 PLC Configuration

PLC Configuration Deliverables

6.8 SCADA Configuration

SCADA Configuration Deliverables

6.9 Testing

Testing Deliverables

6.10 Panel Testing

Panel Testing Deliverables

6.11 Commissioning

Commissioning Deliverables

6.12 Closeout

Closeout Deliverables 7 Assumptions & Clarifications

7.1 I/O Count

8 Schedule www.eaintegrator.com

Scope of Work MAPS Rehabilitation

Page Number: 2 of 21

9 Conclusion 10 Terms & Conditions Appendix A: Deliverables List

Client Deliverables Internal Deliverables

Acronyms and Terms For the remainder of the document the following acronyms will be used.

Term Description CR SCADA Change Request EA Enterprise Automation (Integrator) FAT Factory Acceptance Test HMI Human Machine Interface O&M Operation and maintenance manuals OIT Operator Interface Terminal, stand-alone graphical interface typically found on standalone equipment or remote sites PLC Programmable Logic Controller PM Project Manager SAT Site Acceptance Test SCADA Supervisory Control and Data Acquisition (refers to the entire automation system) CSM, the City City of Santa Monica www.eaintegrator.com

Scope of Work MAPS Rehabilitation

Page Number: 3 of 21

1 Proposal Background Enterprise Automation (EA) has been providing on-call control system integration services for the City of Santa Monica’s Water Resources Division (the City) since 2024.

Moss Avenue Pump Station (MAPS) is Santa Monica’s single sewage lift station and therefore the most critical site for controlling wastewater flows through the city. Because of its importance, MAPS was identified as a high-priority candidate for upgrades to improve system resiliency and reduce the risk of failures and downtime.

This rehabilitation project will replace the existing CP-1 control panel and relocate it to a new enclosure equipped with modern ControlLogix system and networking hardware. The upgrade includes an upgrade to a hot‑standby ControlLogix processor architecture to provide improved failover and redundancy. The scope also covers backpanel replacement of the SMURRF LCP-100 to bring that equipment onto the latest ControlLogix processors as well, without the hot-standby feature as CP-1.

As part of the modernization, EA will migrate the facility’s legacy ControlNet hardware to Ethernet, standardizing communications across the site and improving maintainability and future expandability. EA assumes the City’s contractor will be responsible for any physical installations and replacements. New SCADA screens for MAPS will be developed, and tag/driver and communication updates will be implemented to reflect the SMURRF PLC upgrades.

EA assumes the City’s consultant will have already installed and configured the Ignition SCADA platform prior to project kickoff; this proposal does not include initial Ignition platform setup from the legacy InTouch system.

2 Project Goals The goals of this project are:

1. Reduce obsolescence and improve resiliency

a. Install a modernized high-availability redundant CP-1 control panel with ControlLogix hardware.

b. Perform a backpanel replacement for LCP-100 to upgrade the existing obsolete hardware to the latest ControlLogix processor.

c. Configure PLC and RIO network interfaces from ControlNet to Ethernet for modernized data exchange.

d. Update the CP-1 and LCP-100 program to align with the new panel hardware configuration.

e. Develop up-to-date documentation for CP-1 and the LCP-100 panel

2. Reduce risk and minimize the total effort required during a tight cutover window through testing and planning appropriately.

www.eaintegrator.com

Scope of Work MAPS Rehabilitation

Page Number: 4 of 21

3 Assumptions Please see Section 6.10 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.

4 Supporting Documentation This scope was developed with support from the following documents:

1. MAPS Rehabilitation Project 100% Design Submittals

i. FINAL RFC MAPS Rehabilitation Project Drawings 2026.05.15 (1)

2. MAPS 100% Specifications

i. FINAL RFC MAPS Rehabilitation Specifications 2026.05.15 (1)

ii. 408100 SystemIntegratorQuals-SummaryOfWork

9050 Irvine Center Drive, Irvine, CA 92618 USA Tel 949-769-6000 Fax 949-769-6005 www.eaintegrator.com

Scope of Work MAPS Rehabilitation

Page Number: 5 of 21

5 Cost Estimate Payment Cost

Initiation $4,599 Meetings $28,118 Design $70,768 Panel Design and Fab $51,462 Test and Dev Platform $15,178 PLC Configuration $40,728 SCADA Configuration $53,022 Testing $53,306 Panel Testing $21,698 Commissioning $106,671 Training $11,034 Closeout $12,898 Project Management $88,796 Materials (including tax) $290,964 Travel $6,927 Total $856,169

Work under this proposal is on a fixed fee basis, and pricing included in this proposal is a firm quote. The project will be billed and invoiced to the City monthly based on project percentage complete. Any additions to the scope of work will be submitted to the City as a change order request. Approval of any change order by the City will be required prior to Enterprise Automation commencing or continuing the work task in question.

5.1 Materials

Budget has been included for EA to procure the following items:

1. CP-1 (MAPS) Panel

a. Include all control hardware components, panel enclosure and fabrication

2. LCP-100 (SMURFF)

a. Include a back panel replacement with all control hardware components and fabrication

3. New MAPS Control Room

a. Only include 1 Cisco C1300 8 Ports Ethernet Switch, with 1 additional spare (Please note that C350 series is discontinued, C1300 is the direct replacement)

4. Spare control panel hardware

a. Include 1 spare of ControlLogix PLC and each respective I/O and communication modules, panel mounted PC, and networking switches

5. Ignition Edge IIOT redundant software license with 5 years of BasicCare support www.eaintegrator.com

Scope of Work MAPS Rehabilitation

Page Number: 6 of 21

5.2 Travel

Hotel stays, flights, and car rentals are billed at cost. Per diem is billed at the U.S. General Services Administration (GSA) rate, and mileage is billed at the IRS standard mileage rate as of July 2nd, 2026.

6 Scope of Work This section details the scope of work for tasks included in the cost estimate table in Section 5, 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 client

• Internal deliverables: items EA will produce for internal use (available by request)

6.1 Project Management

EA 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 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 submit an agenda for review and meeting minutes with action items and dates assigned.

Key Project Management Roles and Activities:

1. Primary point of contact, communications coordination

2. Project scheduling

3. Internal project team meeting coordination

4. Project status tracking (daily/weekly)

5. Project status communication with the City

6. Project invoices and tracking report (monthly)

7. Project coordination

8. Procurement oversight

6.1.1 PM Communications Plan

6.1.1.1 Project Status Updates

The 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.

www.eaintegrator.com

Scope of Work MAPS Rehabilitation

Page Number: 7 of 21

6.2 Project Initiation

The “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.

6.2.1 Execution Planning

Following receipt of a Notice to Proceed or Purchase Order, execution planning will be the first technical task of this contract. This crucial engineering activity involves documenting the systematic process and milestones required to produce each deliverable.

Draft execution plans are created at the Initiation Stage and are frequently updated. This ongoing process helps the team accurately track progress and predict future performance.

Additionally, execution planning is an essential part of EA’s schedules and quality management program. They ensure that resource needs and technical risks are identified as early as possible.

6.2.2 Internal Kickoff

Once the project has been set up in our accounting system and an engineering team has been established, they will perform an internal team kickoff to review this proposal and discuss:

1. Client background, project background, and project goals

2. Project scope, budget, and milestones/schedule

3. All available relevant documentation (specs, designs, etc…)

During or shortly after the internal kickoff, EA will develop a formal risk register to track known or potential project risks (commercial, technical, coordination, etc.) and mitigation strategies. The risk register will be updated on a regular basis throughout the life of a project and is available for client review at any time.

6.2.3 Project Kickoff Meeting

Following the internal kickoff meeting, EA will prepare for a formal kickoff meeting with the City.

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.

Project Initiation Deliverables Client Deliverables

1. Kickoff meeting minutes

2. Project Schedule in Gantt format

Internal Deliverables

1. Execution plans

2. Initial risk register www.eaintegrator.com

Scope of Work MAPS Rehabilitation

Page Number: 8 of 21

6.3 Meetings

6.3.1 Contractor/Client Coordination Meetings

EA has reserved time for as needed coordination with the City and/or contractors. These meetings may take place over the phone, virtually, or in-person. The intent is to establish consistent communication between all parties and provide an opportunity to discuss any part of the project that requires the City’s involvement. The budgeted time has included up to 2 meetings for reporting design, up to 2 additional meetings to discuss and finalize PLC/HMI designs, and up to 1 meeting to review contractor submittals for instrumentation and VFDs.

6.3.2 Internal Team Check-in Meetings

Brief check-in meetings between the EA PM and engineering project team will be conducted regularly throughout the project. These meetings are used to align all members of our team on overall project status, budget, schedule, and scope. The risk register is also updated as known risks are averted or mitigated and new risk scenarios are identified.

These formal meetings are a critical component to the success of a project as they facilitate and ensure team coordination and collaboration on a regular basis.

Meetings Deliverables Client Deliverables

1. Reporting kickoff meeting agenda and minutes

2. Reporting design concept meeting agenda and minutes

3. Reporting design review meeting agenda and minutes

4. PLC/HMI design guide design concept meeting agenda and minutes

5. PLC/HMI design review design concept meeting agenda and minutes

1. None

6.4 Design

6.4.1 Document Review

The EA team will review the design engineer’s documentation prior to starting work on the detailed designs. This includes any P&IDs, electrical schematics, instrument list, equipment list, and specification sections.

6.4.2 Site Investigations

EA expects to travel onsite and spend up to 1 day investigating the existing panels, including travel. The primary intent of the site investigations is to ensure all the requirements have been captured for the back panel replacement. Since this is an existing panel, layout will be restricted www.eaintegrator.com

Scope of Work MAPS Rehabilitation

Page Number: 9 of 21 based on the existing panel configuration and how much slack is available on the current field wiring. EA will not be tracing wiring or performing IO verification during this visit, but instead will just be confirming things like available space and power requirements.

6.4.3 Document Maintenance

Throughout the project, we expect to make updates and modifications to the network drawings to reflect the new hardware and CP-1 panel location. EA will finalize the network design and then update the network drawings to reflect the changes and make them available to the City.

6.4.4 IO List

To begin the design phase, EA will review the investigation notes and electrical drawings for CP-1 and LCP-100 panels. EA will work with the City’s existing I/O list and the latest PLC program backups to generate a detailed I/O list, identifying which I/O points are active and which are spare. This effort is intended to document all of the I/O currently being used by the CP-1 and LCP-

100. Once all of the necessary information is collected, EA will format the information in the standard I/O list format and submit to the City for review and feedback.

6.4.5 MAPS Functional Specifications

EA will develop a functional specification that details its program functionalities. In doing so, EA will ensure that the PLC design meets the requirements of the City’s desired control strategy. The functional specification will include defined setpoints, tagging conventions, a detailed account of the process control, and scaling and device feature requirements. By documenting the full programming design up front, both EA and the City will agree on the detailed operation of the system prior to the start of programming. The document will be submitted to the City for review and feedback. The functional specifications will be used as the guide for the PLC configuration phase and is the basis for functional testing as well as during site startup.

6.4.6 SCADA Design Guide

SCADA Design Guide will be developed to guide the new Ignition SCADA screens development for the upgraded MAPS station. The Design Guide will include a screen list, tag naming scheme definitions, alarm list and trending requirements.

Screens will be designed to use the City’s standards that EA has developed. EA will likely use an automated tool to update tags during configuration and will define the tool’s configuration parameters in the design guide.

The design documentation will be submitted to the City for review and feedback.

6.4.7 Reporting Specification

EA will host reporting design workshops with the City and the contractor to discuss specific implementation details. EA plans to host 2 reporting workshops: kickoff, design concept, and design review.

If possible, the EA team will come with draft specifications (described below) to guide the discussion. For example, considerations like how the City might like to see the data displayed will be accounted for, e.g. in a similar document, a graph, bar chart, table, pie chart, etc. This information will allow EA to help the City select a reporting design that the City and the contractor www.eaintegrator.com

Scope of Work MAPS Rehabilitation

Page Number: 10 of 21 will agree on. It will also provide information that will allow EA to generate a thorough reporting specification that will act as the basis for configuration and testing. This type of discussion may not be required for all reports since it may be very obvious how to recreate some of them. The current expectation is that there are likely 2-3 simple reports that would cover something similar to the following:

1. Monthly operational report: shows daily flow totals, peak wet well level

2. Monthly power report: shows daily active power consumption

EA will use the decisions made during the workshops to inform the development of the Reporting design and specification. EA will also document the decisions in the meeting minutes and submit them to the City for their records.

EA will create a reporting specification for the reports that can be automated. The reporting specification will include an example of the report layout, the data needed for each report and its source, as well as details for each calculated data point on the report. EA will submit the reporting specification to the City for review.

Design Deliverables Client Deliverables

1. Updated network drawings

2. IO list

3. MAPS functional specifications

4. SCADA design guide

5. Reporting design

1. Investigation notes

6.5 Panel Design

EA will develop panel design documentation to detail specifics about the new CP-1 panel design and LCP-100 backpanel modifications required prior to startup. EA will develop necessary panel drawings relevant to CP-1 and LCP-100 to show the changes in hardware and connections. The new CP-1 panel will include modernized redundant ControlLogix platform, while the LCP-100 is expected to have upgraded hardware without redundancy capability. EA's panel drawings will include a parts list/bill of materials for the required components and stamped seismic calculation for the CP-1 panel. EA will submit the panel drawings to the City for review and feedback.

EA plans to upgrade the RIO networking from the legacy ControlNet hardware to Ethernet-based hardware and will reuse existing Ethernet-based hardware where possible to minimize costs. If the EA team determines that additional hardware replacements may be required, the team will discuss with CSM about expanding the scope. Following internal reviews, EA will submit each panel design to the City for feedback.

www.eaintegrator.com

Scope of Work MAPS Rehabilitation

Page Number: 11 of 21

6.5.1 Work Orders

EA will also develop work orders to detail the requirements for the LCP-100 back panel installation for a successful deployment. EA expects that a lot of the work orders will be completed by the electrical contractor prior to EA’s arrival onsite for deployment activities, although coordination will be required. EA will submit these work orders to the City for review and feedback.

6.5.2 Panel Construction Support

EA has allocated time to manage the panel fabricator during panel construction process and testing. EA will also coordinate delivery schedule with the panel fabricator and the City.

Panel Design Deliverables Client Deliverables

1. CP-1 panel drawings

2. LCP-100 panel drawings

3. Work orders

6.6 Testing and Development Setup

EA will build a dedicated development/test environment that mirrors production for safe development and validation. EA will provision the production hardware (PLC racks, RIO racks, ControlLogix modules), apply necessary firmware updates, and validate compatibility before having them installed in the panel at the factory.

EA will also configure local Ignition workstations and their hardware interfaces, set up and configure Windows-based PCs with the necessary OS settings and drivers, and install and configure Ignition. Required networking equipment, including Cisco managed switches, will be configured and tested as needed.

Testing and Development Setup Deliverables Client Deliverables www.eaintegrator.com

Scope of Work MAPS Rehabilitation

Page Number: 12 of 21

6.7 PLC Configuration

Using the functional specification, EA will develop the CP-1 program to align with the new redundant system and remap the RIO to transition from ControlNet to Ethernet. The majority of the logic programmed in the existing LCP-100 PLC will be re-used without significant modification, EA plans to upgrade the firmware to match the modernized hardware and make any applicable updates from RS500 to Studion5000 without adding a redundancy feature.

Configuration tasks for PLC programming include but are not limited to:

• Upgrade PLC software (version TBD)

• Upgrade PLC firmware (version TBD)

• Converted LCP-100 PLC program

• Fully programmed hot standby CP-1 PLC program

Within the LCP-100 program, the hardware configuration must be mostly re-done since the processor and Ethernet remote I/O network will need to be created from scratch. There is a manufacturer recommended process to migrate the ControlNet modules to the new Ethernet network, but the process requires a lot of manual steps. This is the majority of the effort which will need to be fully validated against the old program.

PLC Configuration Deliverables

6.8 SCADA Configuration

EA will install, deploy, and configure the Ignition Edge Gateway. EA will also perform the necessary backend configuration updates to the City’s central Ignition application to enable communication with the Edge Gateway, if it is available. EA will create up to 5 new screens for the MAPS lift station using the City’s existing SCADA standards. The visual look, functionality, navigation, and alarms relating to the updates that reflect the newly upgraded MAPS system will be uniform with the existing SCADA system and the graphics, navigation, and alarms already in place. EA will also make any driver or tags updates applicable to the LCP-100 hardware modernizations.

The anticipated screens would include the following:

1. MAPS process overview screen

2. Level transmitter selection configuration popup

3. Operational setpoints/commands popup

4. Maintenance screen with power information

5. Standard faceplates for motor control, and lead/lag selection www.eaintegrator.com

Scope of Work MAPS Rehabilitation

Page Number: 13 of 21

SCADA Configuration Deliverables

6.9 Testing

6.9.1 Test documentation

EA will prepare test procedures and documentation to define the quality control process for testing the integrated automation system. The test documentation will be based on, and incorporate, the design specifications developed by EA and approved by the City. The test procedures will encompass:

1. SCADA configuration

2. Reporting configuration

3. PLC programming

4. Networking configuration

The test documentation package will be submitted to the City for approval one week in advance of the commencement of unwitnessed testing. Approval is required so that the same documentation can be used for the witnessed FAT.

6.9.2 Internal Integrated Testing

Internal SCADA testing will include a project engineer and the project’s lead engineer. The SCADA test platform will provide a highly effective environment for testing since it replicates the computing and networking conditions expected on site.

As the test procedures are executed, the engineers will log all non-conformances in EA standard format and make corrections. Once the non-conformances are corrected and the architect, project manager, lead engineer, and testing engineers review and approve the completed test documentation, the system will be released for witnessed FAT.

6.9.3 SCADA witnessed FAT

EA will host a witnessed SCADA FAT for City representatives at EA’s Irvine facility. The FAT will cover the new SCADA screens for the MAPS. This process will provide the City the opportunity to view, inspect, and operate the final control system before it is installed onsite. EA has allocated up to one day for City representatives to complete the FAT.

The City will be asked to select a subset of the SCADA test procedures to complete as executing the entire suite of SCADA test procedures would take well more than allotted time. The system will also be available for City representatives to perform ad-hoc unscripted testing during the witnessed FAT.

While the FAT is not a substitute for the SCADA system training, this provides an additional opportunity for the operations team to get familiar with the new software prior to deployment.

www.eaintegrator.com

Scope of Work MAPS Rehabilitation

Page Number: 14 of 21

The FAT will conclude with formal sign-off by the City which signifies that the software is approved for installation on site. The completed and signed-off FAT documentation will be scanned and submitted to the City in electronic format.

Testing Deliverables

1. Executed FAT test documentation

1. Internal test documentation

6.10 Panel Testing

6.10.1 Panel Test Documentation

Testing documentation will be developed for the new panel and backpanel and will help guide the verification process. This documentation helps ensure sure the major elements of the panels are tested at the fabricator’s facility prior to delivery.

6.10.2 Panel Testing (unwitnessed)

The unwitnessed panel tests will be hosted at the fabricator’s facility. During the panel tests, EA will check elements such as wiring, labels, power supplies and redundancy, UPS functionality, I/O modules, and PLC modules to make sure that everything is in working order and meets the City’s standards.

6.10.3 Panel FAT (witnessed)

The City’s staff and contractor will be invited to the facility for an abbreviated panel testing procedure following the completion of unwitnessed testing. This witnessed FAT ensures that the City is satisfied with the panels prior to site delivery.

Following the FAT, EA will coordinate shipment of the panels from the fabricator’s facility to the project site. It’s assumed that the prime contractor will be responsible for receiving the control panels and their proper storage on-site prior to the electrical contractor’s installation. The panel should not be powered until EA has inspected the installation and performed a site acceptance test checklist to ensure it is safe to do so.

EA will coordinate the spare hardware delivery with the City and contractor. EA assumes the contractor will be responsible for onsite handling and proper storage of the spare hardware.

www.eaintegrator.com

Scope of Work MAPS Rehabilitation

Page Number: 15 of 21

Panel Testing Deliverables Client Deliverables

1. Executed panel FAT test documentation

2. Shipment of CP-1 panel

3. Shipment of LCP-100 backpanel

6.11 Commissioning

6.11.1 Preparation

To prepare for deployment, EA will create deployment documentation to guide the process and ensure all steps are taken and that important details are not overlooked. This documentation will consist of a variety of checklists and procedures that outline the steps of conducting a network checkout, I/O checkout, completing startup, system tuning, etc.

Following deployment documentation while onsite is one of the many ways EA mitigates risk during commissioning, as it reduces the chance of crucial deployment steps being overlooked.

The team will create the deployment plan with the intent to minimize plant downtime during this critical cutover. EA will submit the deployment documentation to the City for approval before using the documentation onsite.

6.11.2 Deployment Planning Workshop

EA will host a deployment planning workshop with the City prior to onsite deployment. The intent of this workshop is to review the deployment documentation and discuss the overall approach to commissioning to ensure that EA, the contractors, and the City are in alignment with the execution plan. Topics such as scheduling and coordination, downtime, rollback options, and startup may be discussed. EA will maintain an overall control system commissioning plan that will align with the overall plan discussed in the deployment planning workshops.

6.11.3 Deployment

EA will arrive onsite to commission the new CP-1 panel and LCP-100 backpanel, perform a hardware checkout, I/O and equipment checkout, networking checkout, and startup procedures.

EA expects to provide testing support for the Ethernet equipment such as VFDs and MCCs. EA has budgeted for up to two working weeks in order to complete the cutover in the shortest possible timeline. Daily work reports will be generated via email and sent to the commissioning team which will cover work completed and delays or concerns related to the work.

It’s currently assumed that EA will participate in the final phases of the cutover and commissioning as outlined in the project specifications (Phase 5 – Installation of New Equipment and Phase 6 – Final Cutover and Commissioning). It’s expected that Phase 6 - Final Cutover and Commissioning will take less than 10 full working days on-site for EA to complete commissioning activities (IO checkout, device testing and startup). Note that EA also intends to support the contractor’s cutover plan (Phase 1 – Pre-Demolition and Planning and Coordination) and provide www.eaintegrator.com

Scope of Work MAPS Rehabilitation

Page Number: 16 of 21 feedback related to the automation. Any additional time required for EA during the other phases is not included in our scope of work or budget.

EA has included budget for 10 virtual check-in meetings with clients and contractor during the construction phase.

Commissioning Deliverables

1. Executed FAT test documentation

6.12 Closeout

6.12.1 As-built documentation

At the end of the project, EA will provide as-built documentation for the CP-1 and LCP-100 panels, updated specifications, and the updated network drawings. These documents will be filed in the City’s system to be used for future reference. EA does not anticipate providing redlined instrumentation drawing sheets from the engineering drawing package since a separate network drawing and control panel schematics will be developed as submittals for this project.

6.12.2 Operator SCADA Training

The Operator training will have a screen training session over the course of a single day. The City is welcome to record these trainings for future use. EA plans to make 2 separate trips to host training for the City’s staff, one will be before startup and another trip after the system has been fully commissioned, totaling to 8 hours of total training sessions. This can be hosted virtually or in person at the City’s facility.

6.12.3 Project Closeout Meeting

EA plans to have a project closeout meeting with the City to debrief the project. The as-built documents will be delivered to the City at the meeting.

Closeout Deliverables Client Deliverables

1. As-built documents

2. Operator training manual

1. Project closeout meeting notes www.eaintegrator.com

Scope of Work MAPS Rehabilitation

Page Number: 17 of 21

7 Assumptions & Clarifications The following assumptions and clarifications were used in preparing this proposal:

1. EA will not be responsible for configuring the MCCs/VFDs/motor starters but will assist during testing during the commissioning process.

2. EA has included budget for spare control panel hardware. However, EA did not include budget to test each spare part prior to shipment.

3. EA will not be responsible for any instrumentation scope. EA assumes the contractor will procure, deliver, configure and commission the instrumentation. EA will assist with troubleshooting the signal within the PLC control cabinet.

4. EA assumes there will be approximately up to 35 networked I/O from ethernet devices (VFD, MCC, etc.) that will need to be configured into Ignition. EA expects that this count will change during the project and has budgeted for some minor variability. 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.

5. EA assumes the City will only require up to 3 basic reports to be developed and configured for the scope of this proposal. Additional number of reports and complexity may require additional budget.

6. EA will not be responsible for procuring or configuring the DeskJet SCADA report printer, or any associated software or hardware.

7. EA assumes the control panel design will align with the EA standard design that was developed for PLC-1 and may have a slightly different layout or part selection from what is included in the plans.

8. EA assumes that the SCADA platform for MAPS/SMURRF has been replaced and is running on their new Ignition system which will be ready for new development.

9. EA assumes that the MAPS PLC will be reprogrammed since the vast majority of the I/O is new and will need to be fully commissioned. The programming for the MAPS facility will use the new Ignition and AB standards that EA has developed for the City.

10. EA assumes that the SMURRF PLC will be converted from RSLogix 500 to the latest version being used by CSM (versus a full reprogram) since this only the PLC is being upgraded and none of the IO is changing.

11. The engineering workstation in the control room will have already been replaced with a new workstation that is running Ignition. Within the new MAPS control room, EA will only be responsible for procuring and configuring the Cisco C1300 series ethernet switch.

12. 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.

However, we may provide advice to our clients, who can choose to pursue our advice in the event that such an update is required.

www.eaintegrator.com

Scope of Work MAPS Rehabilitation

Page Number: 18 of 21

13. EA will be utilizing software provided by a third-party vendor as part of their scope of work.

EA provides no warranty that the software is free from vendor caused defect or bugs. If during development, testing, or deployment a software issue is discovered that can be attributed to a vendor caused defect or bug, EA will attempt a reasonable amount of troubleshooting with the vendor to try and fix the issue. If the time spent goes beyond what EA deems is reasonable, EA will discuss possible solutions with the City, such as having the City’s staff continue with the vendor, or having EA continue on a T&M basis.

14. Unless specifically indicated in the scope of work:

a. Design documentation developed through this project will not be stamped by a professional engineer.

b. No hardware installation or instrumentation calibration services are included

15. All submittals will be transmitted in electronic format (no hard copies will be provided).

16. In order to maintain project flow and schedule:

a. Written approval (email or letter) is required for all submittals within 10 business days of release.

b. Response to meeting requests is required within 5 business days.

17. Delays due to mechanical, electrical, or IT related issues, production scheduling constraints, or lack of system availability out of EA’s control that result in additional site time will be charged at EA’s standard hourly rates.

18. Lead-Time & Supply Chain Impacts: All quoted hardware lead times are current estimates and may change without notice due to external supply‑chain issues and global conditions.

19. Unless otherwise indicated by the Scope of Work above, the following is not included within this quotation:

a. All Equipment and Services Identified to be by a “Vendor”.

b. Conduit, field wire, tubing, or basic trade installation materials (brackets, screws, bolts, j-box, stanchions, pull-box, etc.).

c. Instrumentation mounting components, brackets, stanchions, sunshields, etc.

d. Local control stations and/or field mounted disconnects.

e. Instrumentation, devices, components, or equipment not specifically identified in the above quotation.

f. Fiber optic patch panels, cable, splicing or terminations.

g. Networking infrastructure or architecture modifications to existing facilities.

h. Any 3rd party testing, harmonic testing/analysis, protective device coordination study, short-circuit analysis, or Arc-Flash Risk Assessment (AFRA) services.

i. Electrical interconnection diagrams for equipment not furnished by EA.

j. ISA process control loop diagrams.

k. Signal loop diagrams for equipment not furnished by EA.

20. EA shall provide cybersecurity services to the City in accordance with industry best practices and applicable laws and regulations.

www.eaintegrator.com

Scope of Work MAPS Rehabilitation

Page Number: 19 of 21

21. the City acknowledges that no cybersecurity system is completely secure, and EA makes no guarantees regarding the prevention or detection of all cybersecurity threats.

22. EA shall not be liable for any losses or damages arising from a cybersecurity attack that occurs despite the provision of cybersecurity services.

23. the City shall be responsible for maintaining adequate backups and disaster recovery plans in case of a cybersecurity attack.

24. the City shall notify EA promptly in the event of a cybersecurity attack. If the City requests EA’s support, the City shall provide all necessary cooperation and information to assist in remediation.

25. the City shall indemnify and hold harmless EA from any claims, damages, or expenses arising from a cybersecurity attack that is caused by the City's negligence or misconduct.

7.1 I/O Count

The cost estimate and scope of this proposal was developed based on the following I/O information.

Panel Name:

CP-1

Digital Inputs Digital Outputs Analog Inputs Analog Outputs 59 10 10 4

Networked I/O:

Panel Name:

LCP-100

Digital Inputs Digital Outputs Analog Inputs Analog Outputs 54 12 16 7

Networked I/O:

N/A

EA expects that this count will change during the project and has budgeted for some minor variability. 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.

www.eaintegrator.com

Scope of Work MAPS Rehabilitation

Page Number: 20 of 21

8 Schedule This proposal was developed assuming that all work will be completed by 03/31/2028, assuming project kickoff by 09/31/2026. If the project extends past this date, supplementary budget may be required to cover additional overheads and project management.

The PM will release an initial schedule upon project initiation.

9 Conclusion I 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) 548-3051 with any questions.

Submitted by

Zack Gentry

Automation Architect www.eaintegrator.com

Scope of Work MAPS Rehabilitation

Page Number: 21 of 21

10 Terms & Conditions Validity This proposal is valid for 60 days starting July 2nd, 2026. Please note that due to current supply chain and economic factors, hardware pricing and availability may change without notice.

Invoices Billings will occur every month and will be based on progress percentage complete on a per task basis.

Any additions to the scope of work will be submitted to City of Santa Monica as a change order request.

Approval of any change order by City of Santa Monica will be required prior to Enterprise Automation commencing or continuing the work task in question.

Payment Payment terms are 30 days net. If applicable, Paid when Consultant Paid terms will not be accepted.

Warranty A warranty is not provided by Enterprise Automation for any deliverables or work performed as part of this project. City of Santa Monica remains solely responsible for any warrantees for the facility and equipment.

Resolution of disputes If 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.

Intellectual property All 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 Santa Monica a perpetual, nontransferable, non-exclusive license to use the materials for their internal purposes only, including implementation at other City of Santa Monica-owned facilities.

Limit of liability The total liability of EA and City of Santa Monica 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 Santa Monica 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 Santa Monica 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 Santa Monica’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.

No solicitation of employees Commencing immediately, and continuing until a date one year after the date of final completion of the scope of work, EA and City of Santa Monica 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.

Entire agreement The scope defined in this document describes the complete project scope and sets forth the entire understanding and agreement between EA and City of Santa Monica. It supersedes all prior discussions and understandings in respect to the scope of this project, whether written or oral.

www.eaintegrator.com

Scope of Work Appendix A: Deliverables List

Appendix A: Deliverables List

1. Kickoff meeting minutes

2. Project Schedule in Gantt format

3. Updated network drawings

4. IO list

5. MAPS functional specifications

6. SCADA design guide

7. Reporting design

8. CP-1 panel drawings

9. LCP-100 panel drawings

10. Work orders

11. As-built documents

Internal Deliverables

1. Execution plans

2. Initial risk register

3. Investigation notes