EXHIBIT A

SCOPE OF WORK AND SCHEDULE

2026 SCADA Migration and Modernization (26-1720)

NTEA-1

Request for Proposals (RFP)

2026 SCADA MIGRATION AND MODERNIZATION (26-1720)

TABLE OF CONTENTS

1. INTRODUCTION

1.1. Operational Constraints and Performance Requirements

1.2. System Performance Requirements

1.3. Project Objectives and Success Criteria

2. BACKGROUND

2.1. Current SCADA and PLC/RTU System

2.2. Graphic SCADA Screens and Tag Counts

3. SCOPE OF WORK

3.1. Discovery and Assessment

3.2. SCADA Platform Selection

3.2.1. Deliverable Requirements

3.3. Control Strategy and Functional Requirements

3.4. Detailed Design

3.5. Historian and Data Migration

3.6. Migration Strategy

3.7. Pilot Implementation

3.8. Full Scale Implementation (Migration)

3.9. Full Scale Testing and Commissioning

3.10. Risk Management

3.11. Training and Documentation

3.12. Support

3.13. Software Ownership and Licensing

3.14. Cybersecurity Requirements

3.15. PLC/RTU Strategy and Migration Requirements

3.16. Industrial Network and Infrastructure Requirements

3.17. Server and Virtualization Requirements

3.18. Alarm Rationalization Requirements

(Continued)

2026 SCADA Migration and Modernization (26-1720)

NTEA-2

3.19. Source Code / Intellectual Property Protection

3.20. Constraints and Expectations

3.21. FAT/SAT Documentation Expectations

3.21.1. Functional Verification and Point-to-Point Validation Requirements

3.22. Configuration and Change Management

3.23. Spare Parts and Lifecycle Requirements

3.24. Warranty and Stabilization Period

3.25. Clarify Proposal Expectations for Staffing

4. REQUIRED PROPOSAL FORMAT

4.1. Executive Summary

4.2. Relevant SCADA Migration Experience

4.3. Migration Strategy and Operational Continuity

4.4. Technical Architecture

4.5. Team Qualifications

4.6. Cybersecurity Approach

4.7. Maintainability

4.8. Schedule and Risk

4.9. Cost Proposal

4.9.1. Software Development Services

4.9.2. SCADA Software/Platform & Licensing

4.9.2.1. Recommended Hardware (To be procured by District)

4.9.3. Implementation Costs

4.9.4. Projection of Ongoing Costs

4.9.5. Unit Pricing

4.9.6. Total Cost Summary

4.10. References

5. EVALUATION CRITERIA

5.1. Written Proposal

5.2. Interview

6. RFP SUBMITTAL REQUIREMENTS AND PRE-SUBMITTAL MEETING

7. APPENDICES

8. SCHEDULE

2026 SCADA Migration and Modernization (26-1720)

NTEA-3

1. INTRODUCTION AND PURPOSE

Lakehaven Water and Sewer District (“District”) is seeking qualified implementation partners/system integrators to plan, design, and implement a comprehensive migration and modernization of its Supervisory Control and Data Acquisition (SCADA) systems across two (2) wastewater treatment plants and multiple remote water and sewer facilities.

The primary objective of this project is to achieve a zero-loss-of-control migration with no unplanned service interruptions to treatment or collection systems.

The selected implementation partner/system integrator shall deliver a turnkey solution, including all labor, software, configuration, testing, and commissioning required to provide a fully functional, modern SCADA system.

The system shall be standardized, secure, maintainable, and fully owned by the District, supporting long-term operational reliability, cybersecurity resilience, and usability by District staff.

All recommended hardware, including servers, industrial network and infrastructure equipment, workstations, laptops, UPS, fiber infrastructure, and redundancy hardware systems, shall be evaluated, approved, and procured by the District. Implementation partner/system integrator shall be responsible for setup and configuration per requirements herein.

1.1. Operational Constraints and Performance Requirements

The following requirements are mandatory:

• No unplanned interruption to process control during migration.

• All cutovers must be planned, scheduled, and approved by the District.

• Maximum allowable downtime per process system shall be defined and approved by the District prior to implementation.

• Parallel operation (existing and new SCADA) shall be maintained during transition.

• A tested rollback procedure must be available for all cutovers and shall be reviewed and approved by the District prior to rollback test.

• No loss of critical data, alarms, or operator visibility during migration.

1.2. System Performance Requirements

The implementation partner/system integrator shall define and meet measurable system performance criteria, including:

• Alarm delivery latency.

• HMI screen load time.

2026 SCADA Migration and Modernization (26-1720)

NTEA-4

• Failover/redundancy switchover time.

• System availability.

• Data integrity and historian accuracy validation.

All performance metrics must be validated during testing phases.

1.3. Project Objectives and Success Criteria

The District’s objectives for this project include:

• Modernize and standardize the SCADA environment across all treatment plants and remote facilities.

• Reduce operational and cybersecurity risk associated with aging infrastructure.

• Improve system maintainability and usability for District operations and engineering staff.

• Eliminate undocumented dependencies and unsupported components.

• Improve alarm management and operational visibility.

• Establish a scalable architecture for future facilities and system expansion.

• Minimize lifecycle costs over a 15- to 20-year planning horizon.

• Maintain continuous treatment and collection system operations throughout migration activities.

Project success shall be measured by:

• Zero unplanned process outages attributable to migration activities.

• Successful completion of all acceptance testing.

• Demonstrated failover and disaster recovery capability.

• Delivery of complete editable source files and documentation.

• Successful knowledge transfer to District staff.

• Stable operation for a minimum 30-day post-cutover stabilization period per site.

2. BACKGROUND

Lakehaven has a service area population of over 135,000 people living across a 35 square mile area in south King County, making it the second largest special purpose water and sewer district in the state. The water system includes 450 miles of water mains, 25 active wells, and 12 storage tanks, which allows it to produce and treat high quality drinking water to meet a current annual average water demand of 10 million gallons per day (MGD) from the community. Lakehaven also has two (2) wastewater treatment plants (Redondo and Lakota), 34 sewer lift stations, and 350 miles of sewer mains capable of collecting and

2026 SCADA Migration and Modernization (26-1720)

NTEA-5

treating up to 15.6 MGD, adhering to EPA standards, which safeguards the local ecological system of Puget Sound.

2.1. Current SCADA and PLC/RTU Systems:

• SCADA Platform – Wonderware (now AVEVA) InTouch versions 2014 R2 and 2017.

o Alarm Notification – WIN-911 2021 R6.

o Historian – Wonderware Historian 2017.

o Data Backup and Restore – Veeam Backup and Replication version 12.3.

o Network Monitor – Observium CE version 22.12.12447.

• PLC Programming Software:

o Rockwell Automation Studio 5000 version 33 with Logix Designer version 36.

o Rockwell Automation RSLogix 5000 version 20.05.

o Rockwell Automation RSLogix 500 version 12.0.

o Rockwell Automation FactoryTalk View Studio version 12.0.

o Automation Direct DS Launch version 6.3.03.

o Automation Direct CLICK version 3.41.

o Siemens 505 WorkShop version 5.20.

2.2. Graphic SCADA Screens and Tag Counts:

FACILITIES

APPROX. NO. OF

HMI/GRAPHIC

SCREENS NO. OF TAGS

Lakota Wastewater Treatment Plant 191 >13,000 Redondo Wastewater Treatment Plant 63 >4,500 Sewer Lift Stations 44 >3,500 Water System (25 Wells and 12 Tanks) 156 >6,000

3. SCOPE OF WORK

The implementation partner/system integrator shall provide full lifecycle services including assessment, design, implementation, testing, commissioning, and support.

The implementation partner/system integrator shall provide all labor, development, software configuration, testing, documentation, coordination, commissioning, pilot implementation, and temporary systems required to deliver a fully operational system.

Unless specifically excluded in writing, all items necessary for complete and functional implementation shall be included.

2026 SCADA Migration and Modernization (26-1720)

NTEA-6

The implementation partner/system integrator shall act as the prime responsible party for:

• system integration.

• software configuration.

• migration execution.

• subcontractor coordination.

• testing.

• commissioning.

• startup support.

• training.

3.1. Discovery and Assessment:

The implementation partner/system integrator shall:

• Identify undocumented logic, hard-coded values, and operator workarounds.

• Identify single points of failure across SCADA, PLCs/RTUs, and networks.

• Identify obsolete or unsupported components.

• Evaluate alarm system performance (flooding, nuisance alarms, stale alarms).

• Perform complete system assessment (SCADA, PLCs, historian, network).

• Validate tag inventory.

• Review PLC programs and SCADA graphics.

• Redundancy, failover, and disaster recovery validation.

• Assess treatment plant control strategies (P&IDs, process descriptions).

• Conduct operator and control staff interviews.

3.2. SCADA Platform Selection:

The implementation partner/system integrator shall evaluate and recommend a Supervisory Control and Data Acquisition (SCADA) platform from at least two (2) industry-recognized solutions (e.g., AVEVA System Platform and Ignition). The evaluation shall, at a minimum, address the following criteria:

• Lifecycle cost (15–20 years).

• Cybersecurity capabilities.

• Scalability.

• Maintainability by District staff.

• Licensing transparency.

• Performance and reliability.

2026 SCADA Migration and Modernization (26-1720)

NTEA-7

• Compatible with third party applications such as Hach WIM, Trimble Unity (CityWorks).

• The proposed platform shall avoid vendor lock-in and allow District staff to independently maintain and modify the system.

• The implementation partner/system integrator shall disclose any proprietary limitations or dependencies.

3.2.1. Deliverable Requirement:

The Implementation partner/system integrator shall provide a justification matrix comparing the selected SCADA platforms. The matrix shall clearly identify and disclose any proprietary components, software dependencies, licensing restrictions, and other limitations that may impact long-term maintenance, system modification, integration flexibility, or future migration to alternative platforms.

3.3. Control Strategy and Functional Requirements:

• Existing control logic shall remain functionally equivalent unless explicitly approved by the District.

• Any proposed modification must be documented, justified, and approved through formal change management.

• The consultant shall not independently alter process control philosophy.

• All changes shall follow a formal documented change management process with District approval.

3.4. Detailed Design:

The implementation partner/system integrator shall develop:

• SCADA programming standards.

• Tag naming conventions.

• HMI design standards (ISA-101).

• Alarm management strategy (ISA-18.2).

• UDT/template structures.

• Network architecture and cybersecurity design.

• PLC/SCADA interface mapping.

• Historian architecture and reporting.

• Redundancy and failover strategy.

• Identification of all system dependencies.

2026 SCADA Migration and Modernization (26-1720)

NTEA-8

3.5. Historian and Data Migration:

• Minimum historical data retention: District to define (e.g., 5 years).

• Data resolution and compression must be documented.

• Data migration must be validated for accuracy

• Regulatory reporting capability must be maintained

3.6. Migration Strategy:

The consultant shall provide a detailed, step-by-step migration plan, including:

• Parallel (shadow mode) operation methodology.

• Incremental process cutover approach.

• Detailed cutover sequence (hour-by-hour for a sample system).

• Rollback procedures (step-by-step).

• Identification of required outages.

Note: Big-bang cutovers are not permitted.

3.7. Pilot Implementation:

• Implement a pilot subsystem.

• Include alarms, historian, and failover testing.

• Demonstrate:

o Operator usability.

o System performance under load.

3.8. Full Scale Implementation:

• System procurement and configuration.

• SCADA development and graphics.

• Tag migration.

• Security configuration.

• Incremental process migration.

3.9. Full Scale Testing and Commissioning:

Successful completion of Factory Acceptance Testing using simulated PLCs, emulators, or virtual controllers shall not constitute acceptance of PLC communications or process functionality. Functional operation with the District's production PLCs/RTUs shall be demonstrated during Parallel (Shadow Mode) Validation and Site Acceptance Testing prior to final acceptance.

2026 SCADA Migration and Modernization (26-1720)

NTEA-9

Required Testing and Purpose:

• Factory Acceptance Testing (FAT) - Verify the SCADA software is built correctly.

• Parallel (Shadow Mode) Validation – Verify new SCADA accurately reflects the live process while the existing SCADA remains in control.

• Site Acceptance Testing (SAT) – Verify control functions, command handshakes, and operational performance in the production environment.

• Stabilization Verification – Demonstrate reliable operation over a defined period following cutover.

Must Include:

• Failover validation.

• Alarm and historian verification.

• Cybersecurity validation.

• Defined pass/fail criteria.

The implementation partner/system integrator shall define quantitative acceptance criteria, including:

• System performance benchmarks.

• Alarm response validation.

• Data accuracy thresholds.

• Failover performance validation.

• All acceptance criteria must be approved by the District prior to testing.

Required Testing:

• Factory Acceptance Testing (FAT).

• Site Acceptance Testing (SAT).

Must Include:

• Failover validation.

• Alarm and historian verification.

• Cybersecurity validation.

• Defined pass/fail criteria.

The implementation partner/system integrator shall define quantitative acceptance criteria, including:

• System performance benchmarks.

• Alarm response validation.

• Data accuracy thresholds.

2026 SCADA Migration and Modernization (26-1720)

NTEA-10

• Failover performance validation.

All acceptance criteria must be approved by the District prior to testing.

3.10. Risk Management:

• Maintain a risk register.

• Weekly risk reviews.

• Mitigation strategies required.

• Identify high-risk cutovers.

• Risk scoring methodology (likelihood vs. impact) required.

• Migration-specific risk plans required for each cutover.

3.11. Training and Documentation

• Role-based training (operators, maintenance, control, engineers, IT).

o Minimum training hours per role shall be defined.

o Training shall include hands-on system operation.

o Training sessions shall be recorded and provided to the District.

• Complete as-built documentation:

o Network diagrams.

o SCADA standards.

o Alarm configuration.

o Backup procedures.

All source files, configurations, and code shall be delivered in editable format.

3.12. Support

• Critical issue response time ≤1 hour.

• On-site support during major cutovers.

• 2-year post-implementation support.

• Knowledge transfer to District staff.

3.13. Software Ownership and Licensing:

• All software licenses shall be:

o Owned by the District.

o Registered to the District.

• The implementation partner/system integrator shall provide:

o Complete licensing details (type, quantity, limitations).

2026 SCADA Migration and Modernization (26-1720)

NTEA-11

o Identification of perpetual vs. subscription licenses.

o Annual maintenance and renewal costs.

• The system shall not include hidden or undisclosed licensing dependencies.

o The District shall retain full rights to operate, maintain, modify, and expand the system without requiring the services of the original integrator.

3.14. Cybersecurity Requirements:

The system shall be designed in accordance with industry standards, including:

• National Institute of Standards and Technology (NIST SP 800-82).

• Cybersecurity and Infrastructure Security Agency guidance.

• ISA/IEC 62443.

Requirements include:

• Network segmentation using zone/conduit model.

• Secure remote access with multi-factor authentication (MFA).

• Role-based access control (RBAC).

• Patch and vulnerability management plan.

• Logging and monitoring strategy.

• Incident response integration with District IT.

The implementation partner/system integrator shall provide:

• domain group policy modification as needed.

• system hardening checklists.

• account management procedures.

• password policy recommendations.

• logging retention recommendations.

• antivirus/endpoint protection compatibility.

• backup validation procedures.

• vulnerability remediation procedures.

Default vendor passwords shall not be permitted.

All remote access shall be encrypted, logged, role-based, and approved by the District.

3.15. PLC/RTU Strategy and Migration Requirements:

The implementation partner/system integrator shall evaluate and clearly define:

• Existing PLC/RTU hardware suitability with selected SCADA platform.

2026 SCADA Migration and Modernization (26-1720)

NTEA-12

• Firmware lifecycle and supportability.

• Communication protocol compatibility.

• Processor utilization and spare capacity.

• Redundancy capabilities.

• Cybersecurity limitations of existing controllers.

The proposal shall clearly identify:

• PLCs/RTUs to remain in service.

• PLCs/RTUs recommended for replacement.

• Required firmware upgrades.

• Required communication module upgrades.

• Any recommended standardization strategy.

Any proposed PLC replacement shall include:

• Technical justification.

• Lifecycle implications.

• Operational benefits.

• Cost impact.

• Migration risks.

All PLC logic modifications shall be:

• version controlled.

• fully documented.

• approved by the District prior to deployment.

3.16. Industrial Network and Infrastructure Requirements:

The implementation partner/system integrator shall assess and provide recommendations for:

• Industrial Ethernet network architecture.

• Fiber infrastructure.

• Managed switch configuration.

• VLAN strategy.

• Layer 2/Layer 3 segmentation.

• Firewall architecture.

• Remote site communications.

2026 SCADA Migration and Modernization (26-1720)

NTEA-13

• Cellular/radio telemetry systems.

• Time synchronization/NTP architecture.

• Redundant network paths.

• UPS/power protection requirements.

The design shall clearly define:

• OT/IT demarcation.

• DMZ architecture.

• Historian/data replication paths.

• Remote access architecture.

• Vendor access controls.

All network equipment configurations shall be delivered to the District in editable format.

3.17. Server and Virtualization Requirements:

The implementation partner/system integrator shall provide recommendations for:

• Physical vs virtual server architecture.

• VMware/Hyper-V compatibility.

• Redundant host strategy.

• Storage requirements.

• Backup and restore architecture.

• Patch management strategy.

• Disaster recovery architecture.

The District prefers virtualized infrastructure where practical.

The implementation partner/system integrator shall define:

• server sizing assumptions.

• storage growth assumptions.

• historian storage requirements.

• bandwidth utilization assumptions.

3.18. Alarm Rationalization Requirements:

The implementation partner/system integrator shall facilitate an alarm rationalization process including:

• identification of nuisance alarms.

• stale alarms.

2026 SCADA Migration and Modernization (26-1720)

NTEA-14

• chattering alarms.

• duplicate alarms.

• alarm priority inconsistencies.

Alarm philosophy documentation shall include:

• alarm priority definitions.

• shelving rules.

• suppression rules.

• deadbands.

• delay timers.

• operator response expectations.

The District expects reduction of alarm flooding conditions.

3.19. Source Code / Intellectual Property Protection:

All of the following shall become property of the District upon payment:

• source code.

• scripts.

• configuration files.

• templates.

• databases.

• graphics.

• PLC programs.

• historian configurations.

• reports.

• custom software.

The implementation partner/system integrator shall not utilize encrypted, locked, password-protected, or proprietary mechanisms that prevent District modification or maintenance.

All administrative credentials shall be provided to the District prior to project closeout.

3.20. Constraints and Expectations:

The implementation partner/system integrator shall assume:

• Facilities operate continuously.

2026 SCADA Migration and Modernization (26-1720)

NTEA-15

• Treatment processes are critical infrastructure and cannot tolerate uncontrolled shutdowns.

• Migration activities may require night, weekend, or low-flow implementation windows.

• Existing documentation may be incomplete or inaccurate.

• Existing PLC logic may contain undocumented operational workarounds.

• Operations staff availability for testing and cutovers may be limited.

• Some legacy hardware and software may be unsupported or difficult to virtualize.

• Coordination with District Controls and IT teams is mandatory.

The implementation partner/system integrator shall identify all assumptions made within the proposal.

3.21. FAT/SAT Documentation Expectations:

The implementation partner/system integrator shall develop and submit formal written Factory Acceptance Testing (FAT), Parallel (Shadow Mode) Validation, Site Acceptance Testing (SAT), and Stabilization Verification procedures for District review and approval.

Testing procedures shall include, at a minimum:

• Test prerequisites.

• Test objectives.

• Expected results.

• Pass/fail criteria.

• Test data sheets.

• Issue tracking and corrective actions.

• Retest procedures.

The District reserves the right to witness any testing activities.

No production deployment or operational cutover shall occur prior to successful completion of all required testing milestones unless otherwise approved in writing by the District.

3.21.1. Functional Verification and Point-to-Point Validation Requirements:

The implementation partner/system integrator shall develop and execute a comprehensive Functional Verification and Point-to-Point Validation Program demonstrating that the migrated SCADA system is functionally equivalent to the existing production system prior to operational cutover.

2026 SCADA Migration and Modernization (26-1720)

NTEA-16

The verification program shall provide 100 percent verification of all migrated system components. Verification may be accomplished using an appropriate combination of:

• Automated database comparison and validation.

• Automated configuration verification.

• Point-to-point functional testing.

• Integrated process testing.

• Parallel (Shadow Mode) Validation.

• Site Acceptance Testing.

• Other District-approved verification methods.

The implementation partner/system integrator shall identify the verification method used for each system component.

A. Control and Safety-Critical Functions:

The following functions shall receive 100 percent functional verification using live PLC/RTU communications during Parallel Validation and/or Site Acceptance Testing:

• All operator control commands.

• Command confirmation and feedback handshakes.

• Analog outputs.

• Digital outputs.

• Interlocks.

• Permissives.

• Sequences.

• PID control functions.

• Setpoint changes.

• Equipment start/stop functions.

• Safety-related functions.

• Redundancy and failover functions.

Simulation or emulation alone shall not constitute final acceptance of these functions.

B. Monitoring and Indication Functions:

Monitoring-only functions, including digital inputs, analog inputs, calculated values, status indications, diagnostic points, and

2026 SCADA Migration and Modernization (26-1720)

NTEA-17

communication status points, shall be verified using an appropriate combination of automated validation, live communications verification, representative functional testing, and Parallel Validation sufficient to demonstrate correct operation.

The District reserves the right to require additional functional testing for selected monitoring points.

C. Functional Verification:

At a minimum, the verification program shall include:

• Verification of PLC/RTU communications.

• Verification of SCADA tag configuration.

• Verification of alarm configuration, priorities, acknowledge-ments, suppression, shelving, and notifications.

• Verification of historian data collection, timestamp integrity, and reporting.

• Verification of HMI graphics, navigation, animations, faceplates, and trends.

• Verification of scripts, calculations, templates, user-defined types (UDTs), and automated processes.

• Verification of user authentication, security roles, permissions, and audit logging.

• Verification of backup, recovery, redundancy, and failover.

• Verification of all third-party system interfaces.

D. HMI Verification:

All HMI displays shall be reviewed for completeness, navigation, graphical integrity, and proper data presentation.

All operator interface screens containing control functions shall receive full functional testing.

Display-only screens with common layouts or standardized templates may be verified using representative sampling where approved by the District, provided the underlying templates and associated tag mappings have been successfully validated.

E. Test Documentation:

The implementation partner/system integrator shall maintain formal test records documenting verification activities. At a minimum, each record shall include:

• Test identifier.

2026 SCADA Migration and Modernization (26-1720)

NTEA-18

• Equipment or tag identification.

• Verification method.

• Test procedure.

• Expected result.

• Actual result.

• Pass/fail status.

• Date and time.

• Tester.

• District witness (where applicable).

• Corrective action.

• Retest results.

F. Parallel (Shadow Mode) Validation:

Prior to enabling operator control from the new SCADA system, the implementation partner/system integrator shall operate the new SCADA system in parallel with the existing production SCADA system for a District-approved validation period.

During this period:

• The new SCADA system shall receive live data from the production PLCs/RTUs.

• Operator control from the new SCADA system shall remain disabled unless specifically authorized by the District.

• The implementation partner/system integrator shall verify that displayed process values, alarms, historian records, calculations, and communications accurately reflect the production system.

• Any discrepancies shall be documented, corrected, and successfully retested prior to operational cutover.

G. Verification Traceability Matrix:

The implementation partner/system integrator shall provide a Verification Traceability Matrix demonstrating that all migrated system components have been successfully verified.

At a minimum, the matrix shall identify:

• SCADA tag.

• PLC/RTU address.

• Equipment identification.

2026 SCADA Migration and Modernization (26-1720)

NTEA-19

• Functional description.

• Read/write designation.

• Verification method.

• FAT result.

• Parallel Validation result (where applicable).

• SAT result (where applicable).

• Final acceptance status.

H. Acceptance Requirements:

Production cutover shall not occur until:

• All safety-critical and control functions have successfully passed functional verification.

• All critical deficiencies have been corrected and successfully retested.

• Required verification documentation has been submitted to and accepted by the District.

• The District has provided written authorization to proceed with production cutover.

The implementation partner/system integrator shall develop formal written FAT and SAT procedures for District review and approval.

Testing procedures shall include:

• test prerequisites.

• expected results.

• pass/fail criteria.

• test data sheets.

• issue tracking.

• retest procedures.

The District reserves the right to witness all testing activities.

No production deployment shall occur prior to successful completion of required testing milestones unless otherwise approved by the District.

3.22. Configuration and Change Management:

The implementation partner/system integrator shall implement formal configuration management procedures for:

• SCADA applications.

2026 SCADA Migration and Modernization (26-1720)

NTEA-20

• PLC programs.

• historian configurations.

• alarm databases.

• network configurations.

• supporting scripts.

Version control records shall be maintained throughout the project and delivered to the District at project closeout.

3.23. Spare Parts and Lifecycle Requirements:

The implementation partner/system integrator shall identify:

• recommended spare parts.

• recommended software support agreements.

• lifecycle status of proposed hardware/software.

• expected manufacturer support duration.

Preference shall be given to platforms with demonstrated long-term vendor support and upgrade paths.

3.24. Warranty and Stabilization Period:

Following each major cutover, the implementation partner/system integrator shall provide a stabilization support period of not less than thirty (30) calendar days.

The stabilization period shall include:

• priority issue response.

• alarm tuning.

• bug fixes.

• performance optimization.

• operator support.

The implementation partner/system integrator shall provide a minimum one-year warranty on all configuration and integration services following final acceptance.

3.25. Clarify Proposal Expectations for Staffing:

The proposal shall identify:

• key personnel assigned to the project.

• their role.

• years of experience.

• relevant certifications.

• percentage of project involvement.

The District reserves the right to approve substitution of key personnel.

2026 SCADA Migration and Modernization (26-1720)

NTEA-21

4. REQUIRED PROPOSAL FORMAT (40 Letter Size Pages)

Proposals must follow this format:

4.1. Executive Summary.

Include acknowledgement of receipt and review of the most recent revision (R1) of the Scope and Schedule.

4.2. Relevant SCADA Migration Experience.

Provide 3–5 projects including:

• Platforms migrated (from/to):

• System size and complexity:

• Actual downtime experienced:

• Key challenges and lessons learned.

4.3. Migration Strategy and Operational Continuity.

• Step-by-step migration approach.

• Sample cutover plan (required).

• Rollback procedure.

4.4. Technical Architecture:

• System architecture diagram (required).

• Network and cybersecurity design.

• Redundancy strategy.

• Data flow description.

4.5. Team Qualifications:

• Roles and experience.

• On-site staffing during cutover.

• Years of certification.

4.6. Cybersecurity Approach:

• Network segmentation.

• Remote access method.

• Authentication strategy.

• National Institute of Standards and Technology (NIST SP 800-82).

• Cybersecurity and Infrastructure Security Agency guidance.

• ISA/IEC 62443.

2026 SCADA Migration and Modernization (26-1720)

NTEA-22

4.7. Maintainability:

• Tag standards.

• HMI approach.

• How District staff will maintain system.

4.8. Schedule and Risk:

• Detailed schedule.

• Risk register.

4.9. Cost Proposal:

Implementation partner/system integrator must submit a detailed, itemized cost proposal using the following structure:

4.9.1. Software Development Services:

• Assessment Phase.

• Design.

• Development.

• Testing (FAT, SAT).

• Commissioning.

• Training.

• Project Management.

4.9.2. SCADA Platform (Software) and Licensing:

• SCADA platform.

• Historian.

• Alarm/notification software.

• Development tools.

• Third-party software.

MUST INCLUDE:

• License type (perpetual/subscription).

• Quantity and unit cost.

• Annual maintenance cost.

4.9.2.1. Recommended Hardware (to be procured by District):

• Servers.

• Network equipment.

• Workstations.

• Redundancy systems.

2026 SCADA Migration and Modernization (26-1720)

NTEA-23

4.9.3. Implementation Costs:

• Installation.

• Site work.

• Travel.

• On-site support.

4.9.4. Projection of Ongoing Costs:

Provide 5-year and 10-year projection of costs for:

• Software maintenance.

• Licensing renewals.

• Support agreements.

4.9.5. Unit Pricing:

Provide unit cost for:

• Additional PLC/RTU integration.

• Additional HMI screens.

• Additional tags.

• Hourly rates (by role).

4.9.6. Total Cost Summary:

• Total Project Cost.

• Total 5-Year Projection Cost.

• Total 10-year Projection Cost.

Important: Failure to follow this cost format may result in reduced scoring.

4.10. References:

Three (3) references for your firm’s most recent three (3) different clients, listed in order from most current to eldest, that also meet the following criteria:

• At least one (1) of the clients on the reference list shall have their services and/or work product completed.

• The names, phone numbers, and email addresses of at least two (2) contacts associated with each of the referenced clients shall be provided.

• Services/projects listed for references need not have been completed within a certain period of time.

• Clients referenced shall not include Lakehaven Water and Sewer District.

2026 SCADA Migration and Modernization (26-1720)

NTEA-24

5. EVALUATION CRITERIA

5.1. Written Proposal:

Category Points A) SCADA Migration

B) Technical Architecture 15 C) Migration Strategy 25 D) Team Qualifications 15 E) Cybersecurity 10 F) Maintainability 5 G) Schedule and Risk 5 H) Cost 5

5.2. Interview:

Shortlisted firms will be interviewed and scored based on:

Category Points I) Migration Understanding 20 J) Risk Awareness 15 K) Technical Clarity 10 L) Team Competence 10 M) Communication and Trust 5

6. RFP SUBMITTAL REQUIREMENTS AND PRE-SUBMITTAL MEETING

6.1. RFP Submittal Requirements:

• Submittal method: Proposal documents shall be submitted in PDF format by direct email to:

o Mary Young, Purchasing Manager: myoung@lakehavenwsd.gov.

Alternatively, paper proposals may be submitted either directly to the District’s business office at 31627A 1st Avenue South, Federal Way, Washington, or by mail to:

Lakehaven Water and Sewer District Attn: Purchasing Manager 31627A 1st Avenue South Federal Way, WA 98003

Proposals shall be submitted no later than the date and time specified in the published advertisement and/or as posted on the BeaconBid portal.

6.2. Pre-Submittal Meeting:

Pre-Submittal Meeting (via Teams) with District’s Project Manager for up to one (1) hour is available for the following dates and times:

• Contact District’s Project Manager, Jennifer To, to schedule the virtual meeting.

mailto:myoung@lakehavenwsd.gov

2026 SCADA Migration and Modernization (26-1720)

NTEA-25

• Available dates and times:

o Monday – Thursday, July 20, 2026, through July 23, 2026.

o Time: 8:00 a.m. to 11:00 am and 2:00 p.m. to 4:00 p.m.

7. APPENDICES

Appendix A: Assessment Report – November 2025 by Parametrix

8. SCHEDULE

8.1. RFP Schedule:

Milestone Target Date RFP Issued July 15, 2026 Pre RFP Meeting (Teams) July 20 to July 23, 2026 Proposal Submittal Due September 1, 2026 Proposal Selection September 30, 2026 Notice to Proceed October 29, 2026

8.2. Pre-Migration/Implementation Schedule:

Milestone Target Date Discovery and Assessment Completion

February 28, 2027

SCADA Platform Selection Completion

February 28, 2027

8.3. Migration Schedule:

The milestone dates identified in this section represent the Owner's anticipated implementation schedule. Proposers shall develop and submit a detailed project schedule that meets the overall project completion requirements while incorporating the following sequencing constraints:

• Treatment Plant Implementation Sequence. The SCADA migration and implementation activities for the Redondo and Lakota Wastewater Treatment Plants shall be performed sequentially. The successful proposer shall complete the implementation, testing, commissioning, and operational stabilization of the first treatment plant before beginning implementation activities at the second treatment plant. Concurrent implementation of both wastewater treatment plants is not permitted without prior written approval from the Owner.

• Standardization Objective. This sequencing requirement is intended to allow the successful proposer to develop, validate, and refine standardized SCADA architecture, programming standards, HMI templates, alarm philosophy, 2026 SCADA Migration and Modernization (26-1720)

NTEA-26

documentation, and implementation practices at the first treatment plant.

Lessons learned and improvements identified during the first implementation shall be incorporated into the second treatment plant implementation to improve consistency, quality, maintainability, and long-term support.

• Concurrent Remote Site Work. While treatment plant implementations shall be sequential, the Owner encourages concurrent design, programming, testing, and implementation activities for the water and wastewater remote facilities (pump stations and other remote sites), provided such activities do not adversely affect the treatment plant implementation schedule or available project resources.

• Resource Planning. Proposers shall demonstrate in their project schedule and staffing plan that sufficient resources are allocated to satisfy the above sequencing requirements while achieving the required project milestones and overall completion dates.

The Owner reserves the right to review and approve the proposer's detailed project schedule and may require modifications to ensure compliance with these sequencing requirements.

8.3.1. Redondo Wastewater Treatment Plant:

Milestone Target Date Design Completion July 31, 2027 Pilot Completion August 31, 2027 Full Implementation FAT Completion

November 30, 2027

Full Implementation SAT Completion

February 28, 2028 December 31, 2028

8.3.2. Lakota Wastewater Treatment Plant:

Milestone Target Date Design Completion March 31, 2028 Pilot Completion May 31, 2028 Full Implementation FAT Completion

October 31, 2028

Full Implementation SAT Completion

December 31, 2028

2026 SCADA Migration and Modernization (26-1720)

NTEA-27

8.3.3. Sewer Remote Sites:

Milestone Target Date Design Completion September 30, 2028 Full Implementation FAT Completion

November 30, 2028

Full Implementation SAT Completion

December 31, 2028

8.3.4. Water Remote Sites:

Milestone Target Date Design Completion September 30, 2028 Full Implementation FAT Completion

November 30, 2028

Full Implementation SAT Completion

December 31, 2028

8.3.5. 2-Year Post Implementation Completion:

Milestone Target Date 2-Year Post Implementation Completion

December 31, 2030