v.04.15.24

REQUEST FOR PROPOSALS

RFP #354-UT27-17

Project Title: Swift Creek Pump Station PLC Improvements

Issue Date: October 14, 2026

Due Date: November 5, 2026 ET ET

Issuing Department: Utilities Department

Direct all inquiries concerning this RFP to:

Yang Song

Senior Project Manager, Utilities Engineering

Email: Yang.Song@carync.gov mailto:Yang.Song@carync.gov

Table of Contents

1 REQUEST FOR PROPOSALS

1.1 Introduction

1.2 Purpose and Background

1.3 Notice to Vendors Regarding RFP Terms and Conditions

1.4 RFP Response Timeline

1.5 Pre-Proposal Conference/Site Visit

1.6 Proposal Questions

1.7 Proposal Submission Requirements and Contact Information

1.8 Rights to Submitted Material

2 PROPOSALS

2.1 Request for Proposal Document

2.2 Evaluation Criteria

2.3 Proposal Evaluation Process

2.4 Final Selection

2.5 Contract Term

2.6 Invoices

2.7 Notice to Proposers Regarding RFP Terms and Conditions

3 SCOPE OF SERVICES

4 COST PROPOSAL/EXECUTION OF PROPOSAL

5 REFERENCES

INSTRUCTIONS TO VENDORS

TOWN OF CARY PRINCIPAL CONTRACT

1 REQUEST FOR PROPOSALS

1.1 Introduction

Cary is seeking proposals from qualified control system integrators to design, furnish, program, install, test, and commission improvements to the supervisory and control system at the Swift Creek Pump Station.

1.2 Purpose and Background

The Swift Creek Pump Station consists of two pump stations located at a single facility. The original pumping system, commissioned over 35 years ago, operates on 575-volt power and is now in process to convert to 480-volt power. Associated with this electrical improvement, the old pump station control and monitoring system will also need to be replaced and reprogrammed to accommodate the voltage change. The objective of this project will be to upgrade the control system and provide a solution for integrating existing pump station equipment with increased operation redundancy.

1.3 Notice to Vendors Regarding RFP Terms and Conditions

It shall be the Vendor’s responsibility to read the Instructions, the Town’s terms and conditions contained within the Town’s Principal Contract, all relevant exhibits and attachments, and any other components made a part of this RFP and comply with all requirements and specifications herein. Vendors also are responsible for obtaining and complying with all Addenda and other changes that may be issued in connection with this RFP.

If Vendors have questions, issues, or exceptions regarding any term, condition, or other component within this RFP, those must be submitted as questions in accordance with the instructions in Section 1.6 Proposal Questions. If the Town determines that any changes will be made as a result of the questions asked, then such decisions will be communicated in the form of an RFP addendum. The Town may also elect to leave open the possibility for later negotiation and amendment of specific provisions of the Principal Contract that have been addressed during the question submission period. Other than through this process, the Town rejects and will not be required to evaluate or consider any additional or modified terms and conditions submitted with Vendor’s proposal. This applies to any language appearing in or attached to the document as part of the Vendor’s proposal that purports to vary any terms and conditions or Vendors’ instructions herein or to render the proposal non-binding or subject to further negotiation. Vendor’s proposal shall constitute a firm offer. By execution and delivery of this RFP Response, the Vendor agrees that Vendor is prepared to enter into a contract in the form of the Principal Contract should Town selects Vendor’s proposal and that any additional or modified terms and conditions, whether submitted purposely or inadvertently, shall have no force or effect, and will be disregarded. Noncompliance with, or any attempt to alter or delete, this paragraph shall constitute sufficient grounds to reject Vendor’s proposal as nonresponsive.

If a Vendor desires modification of the terms and conditions of this solicitation, including any term or condition contained in the Principal Contract, it is urged and cautioned to inquire during the question period, in accordance with the instructions in this RFP, about whether specific language proposed as a modification is acceptable to or will be considered by the Town. Identification of objections or exceptions to the Town’s terms and conditions in the proposal itself shall not be allowed and shall be disregarded or the proposal rejected.

1.4 RFP Response Timeline

The RFP process shall adhere to the following schedule:

Note: All times shown as Eastern Time (ET).

1.5 Pre-Proposal Conference/Site Visit

NOTE: All Proposers are encouraged to attend a PREPROPOSAL CONFERENCE/SITE VISIT At the Swift Creek Pump Station located at 7802 Holly Springs Rd, Cary NC 27518. A summary of all questions and answers will be posted on the internet as an addendum, located under the RFP # 354-UT27-17.

It is the Proposer's responsibility to assure that all addenda have been reviewed and, if need be, signed and returned.

1.6 Proposal Questions

Upon review of the RFP documents, Vendors may have questions to clarify or interpret the RFP in order to submit the best proposal possible. To accommodate the Proposal Questions process, Vendors shall submit any such questions by the above due date. The Town will not entertain any further questions after the due date. Written questions shall be emailed to Yang.Song@carync.gov by the date and time specified above. Vendors should enter “RFP #354- UT27-17: Questions” as the subject for the email. Questions submittals should include a reference to the applicable RFP section and be submitted in a format shown below:

Reference Vendor Question

RFP Section, Page Number Vendor question …?

Questions received prior to the submission deadline date, the Town’s response, and any additional terms deemed necessary by the Town will be posted in the form of an addendum to the North Carolina Electronic Vendor Portal (eVP), https://evp.nc.gov/solicitations, and shall become an Addendum to this RFP. No information, instruction or advice provided orally or informally by any Town personnel, whether made in response to a question or otherwise in connection with this RFP, shall be considered authoritative or binding. Vendors shall rely only on written material contained in an Addendum to this RFP.

1.7 Proposal Submission Requirements and Contact Information

Submittal Requirements and Contact Information Electronic responses ONLY will be accepted through the eVP website. Interested parties must be logged in to submit proposals electronically. Registration information is available at NC Electronic

RFP Process Date and time

RFP posted October 15, 2026 R

Pre-Proposal Conference October 22, 2026 2:00 p.m.

Proposers Written Questions Due October 26, 2026 5:00 p.m.

Town Responses to Proposers questions October 28, 2026

Proposal Submission Deadline November 5, 2026 10:00 a.m.

Contract Award November, 2026

Contract Effective Date November/ December 2026 mailto:Yang.Song@carync.gov https://evp.nc.gov/solicitations/

Vendor Portal evp.nc.gov (eVP). Proposals must be clearly marked with name of the submitting company, the RFP number and RFP title. Proposers must submit one (1) electronic version, submitted as a viewable and printable Adobe Portable Document File (PDF), on or before the submittal due date and time provided in Section 1.3. Submissions that do not comply with the stated submission method will be deemed non-responsive. The Town reserves the right to reject any or all proposals for any reason and to waive any informality it deems in its best interest. Any requirements in the RFP that cannot be met must be indicated in the proposal. Proposers must respond to the entire Request for Proposals (RFP). An incomplete proposal may be eliminated from consideration at the discretion of Cary.

Proposals must follow the format as defined in Section 2 PROPOSALS.

1.8 Rights to Submitted Material

All proposals, responses, inquiries, or correspondence relating to or in reference to this RFP, and all reports, charts, and other documentation submitted by Proposers (other than materials submitted as and qualifying as trade secrets under North Carolina law) shall become the property of the Town when received and the entire proposal shall be subject to the public records laws of the State of North Carolina except where a proper trade secrets exception has been made by the Proposer in accordance with the procedures allowed by North Carolina law.

The Town reserves the right to retain all proposals submitted and to use any ideas in a proposal regardless of whether that proposal is selected. Submission of a proposal indicates acceptance by the Proposer of the conditions contained in this Request for Proposal.

2 PROPOSALS

Responses must follow the format outlined herein. The Town may reject as non-responsive at its sole discretion any proposal or any part thereof that is incomplete, inadequate in its response, or departs in any substantive way from the required format. Proposal responses shall be organized in the following manner:

1. Cover Letter/Letter of Intent Introduction letter with intent as it may pertain to the Request for Proposal.

2. Corporate Background and Experience

This section shall include background information on the organization and should give details of experience with similar projects. A list of five (5) references (including contact persons and telephone numbers) for which similar work has been performed shall be included, and the list shall include all similar contracts performed by the Proposer in the past five years. The evaluators will randomly select at least three of these references, but the evaluators reserve the right to contact all the references listed, if information from the three references contacted warrant further inquiry. The failure to list all similar contracts in the specified period may result in the rejection of the Proposer’s proposal. The evaluators may check all public sources to determine whether Proposer has listed all contracts for similar work within the designated period. If the evaluators determine that references for other public contracts for similar contracts were not listed, the evaluators may contact the public entities to make inquiry into Proposer’s performance of those contracts and the information obtained may be considered in evaluating Proposer’s proposal.

3. Project Understanding, Approach and Schedule https://evp.nc.gov/

This section shall include, in narrative, outline, and/or graph form the Proposer's approach to accomplishing the tasks outlined in the Scope of Work section of this RFP. A description of each task and deliverable and the schedule for accomplishing each shall be included.

4. Team Organization, Experience and Certifications/Qualifications This section must include the proposed staffing, deployment and organization of personnel to be assigned to this project. The Proposer shall provide information as to the qualifications and experience of all executive, managerial, legal, and professional personnel to be assigned to this project, including resumes citing experience with similar projects and the responsibilities to be assigned to each person.

5. Cost Proposal (Page with Pricing) The Cost Proposal shall be submitted and contain:

• Materials costs (refer to the recommended Bill of Material)

• Personnel costs (including hourly rates and total hours)

• Travel and Subsistence Expenses

• Subcontractor Costs (if any)

• Other Costs (e.g., office expenses)

• TOTAL COST: A total not to exceed cost representing the maximum amount for all work to be performed must be clearly indicated under this heading.

2.1 Request for Proposal Document

The RFP is comprised of the base RFP document, any attachments, and any addenda released before Contract award. All attachments and addenda released for this RFP in advance of any Contract award are incorporated herein by reference.

2.2 Evaluation Criteria

This is not a bid. There will not be a public bid opening. Proposals will be evaluated based on the following criteria:

Criteria (a) Weight

(b) Score (0-3)

(a) x (b) Weighted Score

Corporate Background and Experience 15

Project understanding and approach 35

Team Organization, References (Past Experience)

Cost Proposal 30

Final Score

Score Points

0- Missing or Does Not Meet Expectation 2- Meets Expectation

1- Partially Meets Expectation 3- Exceeds Expectation

2.3 Proposal Evaluation Process

The Town shall review all Vendor responses to this RFP to confirm that they meet the specifications and requirements of the RFP.

The Town will conduct a One-Step evaluation of Proposals:

Proposals will be received from each responsive Vendor in a sealed envelope or package.

All proposals must be received by the issuing agency not later than the date and time specified on the cover sheet of this RFP.

At that date and time, the package containing the proposals from each responding firm will remain sealed and opened at time of review. Interested parties are cautioned that these costs and their components are subject to further evaluation for completeness and correctness and therefore may not be an exact indicator of a Vendor’s pricing position.

At their option, the evaluators may request oral presentations or discussion with any or all Vendors for the purpose of clarification or to amplify the materials presented in any part of the proposal.

Vendors are cautioned, however, that the evaluators are not required to request presentations or other clarification—and often do not. Therefore, all proposals should be complete and reflect the most favorable terms available from the Vendor.

Proposals will generally be evaluated according to completeness, content, and experience with similar projects, ability of the Vendor and its staff, and cost. Specific evaluation criteria are listed in 2.2 EVALUATION CRITERIA, above.

Vendors are cautioned that this is a request for offers, not an offer or request to contract, and the Town reserves the unqualified right to reject any and all offers at any time if such rejection is deemed to be in the best interest of the Town.

2.4 Final Selection

Proposals will be reviewed after opening and will be ranked in order of choice. A recommendation will then be presented to the Town Manager or their designee for approval to negotiate a contract with the #1 choice and, if unsuccessful, to then pursue negotiations with the #2 choice. All Proposers will be notified of their standing immediately following Town’s decision. Price quoted must be held firm for 90 days after the RFP is due. The Town reserves the right to make an award without further discussion of the proposal submitted. The Town shall not be bound or in any way obligated until both parties have executed a contract. The Town also reserves the right to delay the award of a contract or to not award a contract. The RFP may be awarded by individual task or total proposal, whichever is most advantageous to the Town of Cary.

The general conditions and specifications of the RFP and the selected proposal, as amended by agreement between the Town and the selected Proposer including e-mail or written correspondence relative to the RFP, may become part of the contract documents. Failure of the awarded Contractor to perform as represented may result in elimination of the Contractor from competition or in contract cancellation or termination.

2.5 Contract Term

The Contract shall have an initial term of one year, beginning on the date of contract award (the “Effective Date”).

The Town shall have the option, in its sole discretion, to renew the Contract on the same terms and conditions for up to a total of two additional one-year terms. The Town will give the Vendor written notice of its intent whether to exercise each option by a duly authorized amendment.

2.6 Invoices

a) Invoices must be submitted to the Town of Cary Accounts Payable in email on the Contractor’s official letterhead stationery and must be identified by a unique invoice number.

All invoice backup reports and spreadsheets must be provided in electronic format.

b) Invoices must bear the purchase order number to ensure prompt payment. The Vendor’s failure to include the correct purchase order number may cause delay in payment.

c) Invoices must include an accurate description of the work for which the invoice is being submitted, the invoice date, the period of time covered, the amount of fees due to the Vendor.

2.7 Notice to Proposers Regarding RFP Terms and Conditions

It shall be the Proposer’s responsibility to read the Instructions, the Town’s terms and conditions, all relevant exhibits and attachments, and any other components made a part of this RFP, and comply with all requirements and specifications herein. Proposers also are responsible for obtaining and complying with all addenda and other changes that may be issued in connection with this RFP.

3 SCOPE OF SERVICES

It is the intent of these requirements to furnish the Cary Swift Creek Pump Station control system with all material, equipment, labor, engineering, programming, integration, testing, and other related work necessary to complete the Cary Swift Creek Pump Station control system improvement outlined in the Scope of Services. CONTRACTOR shall review the existing systems and deliver a complete, functioning installation while maintaining the required pump station operating capability throughout the work. CONTRACTOR shall utilize the most feasible, timely and cost-effective method(s) for completing the work.

1. Scope of Work Summary

a. The scope of work includes, but is not limited to, the items below. See Section 2 through 9 for detailed technical requirements. Provide existing system verification, detailed design, panel fabrication, programming, staged migration, integration, testing, startup, training, and documentation.

b. Inclusions:

i. PLC hardware and programming;

ii. HMI configuration;

iii. Control panel fabrication (UL 508A);

iv. VFD integration as specified;

v. Field instrumentation as specified;

vi. Site Acceptance Test (SAT);

vii. Startup and commissioning;

viii. Training;

ix. As-built documentation;

x. Software source files delivered to Owner

c. Exclusions:

i. Electrical power feed to panel;

ii. PLC panel termination work,

iii. Civil/site work;

iv. Network/telecom infrastructure;

v. Instrument process taps

d. Site Location and Access

i. Site Address: 7802 Holly Springs Rd, Cary NC 27518

ii. Working hours permitted: M-F 7:00 – 17:00; no work weekends/holidays unless approved.

e. Applicable Codes and Standards.

The work shall comply with the latest published edition of the following codes and standards, plus all applicable state and local amendments:

i. NFPA 70 — National Electrical Code (NEC)

ii. NFPA 820 — Standard for Fire Protection in Wastewater Treatment and

Collection Facilities

iii. NFPA 70E — Standard for Electrical Safety in the Workplace (arc flash)

iv. IEEE 1584 — Guide for performing arc-flash hazard calculations

v. UL 508A / UL 698A — Industrial control panels

vi. IEC 61131-3 — Programmable controllers programming languages

vii. ISA / IEC 62443 — Industrial automation cybersecurity (OT)

2. Control System Architecture and Hardware

a. PLC Platform

i. Required platform: Allen-Bradley ControlLogix, CompactLogix, or GuardLogix controllers

ii. Redundancy:

• The new replacement PLC cabinet in the old control room will function as a master control system to run all six pumps across the new and old side wet wells

• The existing PLC in the new control room will function as a CPU Level hot-standby control system to take over the control of six pumps when the master PLC is in fault mode

• The Master PLC shall execute the control program and control the shared I/O. The Backup PLC shall continuously execute or monitor the same application and remain synchronized with the Master. The Backup PLC shall not control physical outputs while in standby.

• The Backup PLC shall be continuously synchronized with the Master using the PLC manufacturer’s standard redundancy functions.

Synchronization shall include all data required to continue process control without restarting the process sequence.

• The redundant PLC system shall complete an automatic processor switchover, including transfer of control authority to the shared I/O system, within the maximum time stated by the manufacturer and approved by the Owner. The Supplier shall state the guaranteed maximum time separately for processor detection, controller role transfer, shared-I/O ownership transfer, and restoration of normal process control.

• Only one PLC shall have control authority over the shared physical outputs at any time. The redundancy system shall provide a manufacturer-supported method to arbitrate output ownership and prevent simultaneous control by both PLCs.

• Because the I/O and communications equipment are shared, the Supplier shall define the response to failure of each common component. A shared-I/O failure shall generate a separate diagnostic alarm and shall not automatically be treated as a Master PLC failure.

• The redundant PLC system shall prevent both PLCs from becoming active simultaneously. Provide an authorized manual switchover function from the HMI, engineering workstation, or local control panel.

iii. Product lifecycle: Proposed PLC/HMI must be on active (not mature/obsolete) manufacturer lifecycle status; disclose support availability window.

b. I/O Requirements

i. Recommended I/O list as shown in the table below

Device/System I/O Type Signal Description

Wet Well AI Wet Well Level Transmitter

DI High Wet Well Float

DI Lead Float

DI Lag Float

DI Low Float

Pump #1 AI Pump #1 VFD Speed Feedback

AO Pump #1 VFD Speed Command

DI Pump #1 HOA Status

DI Pump #1 Run Status

DI Pump #1 Fault Status

DI Pump #1 VFD Fault

DO Pump #1/VFD Start Command

Pump #2 AI Pump #2 VFD Speed Feedback

AO Pump #2 VFD Speed Command

DI Pump #2 HOA Status

DI Pump #2 Run Status

DI Pump #2 Fault Status

DI Pump #2 VFD Fault

DO Pump #2/VFD Start Command

Pump #3 AI Pump #3 VFD Speed Feedback

AO Pump #3 VFD Speed Command

DI Pump #3 HOA Status

DI Pump #3 Run Status

DI Pump #3 Fault Status

DI Pump #3 VFD Fault

DO Pump #3/VFD Start Command

Bar Screen DI BS 1 Running

DI BS 1 Fault

DI BS 2 Running

DI BS 2 Fault

AI Differential Level

Generator/Power DI ATS Status

DI Generator Running

DI Utility Power Fail

Alarm /Safety DI Intrusion Alarm

DI Smoke Alarm

DI Combustible Gas Alarm

DO Common Alarm Horn

DO Alarm Silence Relay

ii. Provide a minimum of 15% spare I/O per type and unused rack slot space.

iii. Analog signal isolation as required for each loop

c. HMI/Local Operator Interface

i. Local HMI: Allen-Bradely Optix Panel-mounted, minimum 24-in rugged industrial rating (NEMA 4X / IP65 minimum at panel face)

ii. Screens: Overview, per-pump detail, alarm summary, setpoint/trend, maintenance. All graphics shall follow the Town of Cary’s HMI standards and High-Performance representation requirements. Represent the station and all equipment within this scope, including pumps, valves, wet wells, bar screens, switchgear, motor equipment, generator/ATS interfaces, and backup systems.

Navigation per Owner standard (see attachment 1 – HMI Software Development Standards Sections 3-7)

d. SCADA Integration

i. Protocol: Ethernet/IP, Modbus TCP, and Modbus RTU as required by the approved equipment interfaces. Include required protocol gateways.

ii. Integrator shall deliver a complete, documented SCADA tag/point database mapped to PLC tags, and configure the PLC-to-SCADA link unless otherwise noted.

iii. Central SCADA host / point of contact: Aveva System Platform

iv. Upgrade the existing AVEVA System Platform application to incorporate the consolidated controls, power monitoring, hardwired float backup status, and PLC primary/backup status. Migrate and verify all existing station functions, alarms, trends, scripts, graphics, and communications references affected by the work.

v. Duplicate the complete existing station application, including all updates under this scope, in the Town’s Tier 2 AVEVA Read-Only Solution. Include all station screens, equipment displays, tags, alarms, trends, and supporting application configuration required for equivalent monitoring.

vi. Configure Tier 2 as read-only. Disable control commands, setpoint changes, operating-mode changes, and other functions that could modify station operation. Verify that Tier 2 users cannot issue control writes.

vii. Document and test the Tier 1-to-Tier 2 data interface. Verify tag mapping, scaling, units, timestamps, data quality, update rates, and alarm/trend presentation. Changes made under this scope shall be reflected in both applications.

viii. Loss of SCADA or Tier 2 communications shall not prevent local station control, PLC failover, or hardwired float backup operation.

e. Control Philosophy and Operating Modes

i. Each pump shall have a Hand / Off / Auto (HOA) selector. Required operating modes.

ii. Local Automatic — level-based lead/lag alternation with configurable alternation strategy (equal runtime, fixed, etc.).

• Lead alternate across all six pumps to equalize the use of the pumps.

• Lag alternate shall avoid running all three submersible pumps in same wet well before the other wet well pumps start working. This is to fully use the hydrological capacity for the pump station.

iii. Remote Monitoring — SCADA allows remote monitoring but no operation remotely.

iv. Manual / Maintenance — local hand operation with safety interlocks retained.

v. Failure / fault handling: fail-safe shutdown on low-low level, high-high level, motor fault, over-temp, VFD fault, loss of communication. Alarms latched and require manual reset where indicated.

vi. Soft start/stop sequencing and alternation logic shall be per Owner-approved sequence of operations (see Section 6.a).

vii. Submit a cause-and-effect matrix covering normal operation, equipment faults, PLC failover, hardwired float backup, communications failures, and recovery.

Define control authority and transfer conditions for each operating mode.

3. Instrumentation and Field Devices

a. Level Measurement (Existing)

i. Primary level: ultrasonic transmitter, range 0-15 ft, output 4-20 mA.

ii. Redundant high-level float and low-level float: independent, hardwired to safety shutdown logic.

iii. Lead/lag, high-high alarm, low-low shutdown shall be hardwired where feasible, not solely software-implemented.

b. Flow Metering (Existing)

i. Application: Influent (X1) and discharge (X2). Both old and new wet well control

PLCs shall be able to read the influent flow and discharge flows from both discharge force mains.

ii. Meter type: Magnetic flowmeter (conductive)

iii. Output: 4-20 mA

c. Pressure, Temperature and Vibration

i. Thermal contacts for stator winding temperature monitoring

ii. Leakage sensor in the stator housing or inspection chamber

iii. Leakage sensor in the junction box

iv. Pt100 sensor to measure the stator winding temperature

v. Pt100 sensor to measure the main bearing temperature

vi. Current transformer for pump current and speed measurement

vii. Vibration sensor for 3-axis vibration measurement, integrated into the pump electronic module

viii. Discharge pressure: gauge + transmitter (shared by three pumps), 4–20 mA to

PLC.

4. Electrical and Power System Integration

a. Electrical Power Monitoring

i. Integrate the new electrical switchgear, VFDs, soft starters and pump monitoring cabinet with the PLC and SCADA systems through ethernet/IP, Modbus RTU and/or Modbus TCP, as supported by the equipment.

ii. Obtain and verify communications settings, register maps, data formats, and supported measurements with the equipment suppliers.

iii. Acquire available and specified phase voltages and currents, real/reactive/apparent power, power factor, frequency, energy, demand, operating status, and fault information. Include available VFD speed/load information and soft starter diagnostics.

iv. Submit a register/tag schedule identifying source equipment, addresses, data types, scaling, units, polling rates, and destination tags. Identify required measurements unavailable from the supplied equipment and resolve additional metering requirements before final design approval.

v. Provide communications-loss alarms and data-quality indications. Verify electrical readings against equipment displays and confirm consistent presentation in Tier 1 and Tier 2.

vi. Preserve required generator/ATS signaling, load sequencing, and motor protection interfaces when modifying the controls.

b. Standby Power Interface

i. Generator interface: ATS signaling, exercise mode, fail-to-start alarms, and load management / step sequencing to avoid overloading the genset.

ii. Genset details: [Caterpillar/C32GC /1000kW]

c. Motor Protection

i. Solid-state overload relays with phase-loss / phase-reversal detection.

ii. Motor temp inputs and coordination with motor starter / VFD supplier as applicable.

d. Arc Flash and Safety

i. Provide dead-front construction and NFPA 70E-compliant PPE category labels on all panels. Should 3rd party testing agency needed to certify the arc flash and safety for the panel, Contractor shall notify Cary and collaborate on the certification.

5. Communications and Cybersecurity

a. Network Architecture

i. Ethernet/IP backbone with managed industrial switches and redundant ring topology if determined to be necessary.

ii. Provide a coordinated communications design for both CompactLogix PLCs, field equipment, local HMI, Tier 1 System Platform application, and Tier 2 AVEVA Read-Only Solution.

iii. Coordinate addressing, routing, firewall requirements, accounts, and application interfaces with the Town’s IT/OT staff. Identify infrastructure and installation responsibilities before implementation.

b. Protocols

i. Match central SCADA protocol: [Ethernet/IP]

ii. Require conformance test certificates for any protocol gateway. Document and test the specified interfaces, including gateway configuration, register addressing, byte/word order, polling performance, and communications recovery.

c. Cybersecurity

i. Comply with a recognized framework: NIST CSF / ISA-IEC 62443 / AWWA water-sector cybersecurity guidance.

ii. Role-based access control, password policy, audit/transaction logging, firmware patching responsibility defined.

iii. IT/OT segmentation required between corporate IT and the OT control network.

iv. Enforce Tier 2 read-only access through the application and communications configuration. Test the restrictions and confirm that loss of Tier 2 connectivity does not affect station operation.

6. Software, Programming and Documentation

a. Programming Standards

i. IEC 61131-3 structured, well-commented code; function blocks preferred for reuse.

ii. Tag naming: per Owner-approved convention. Should follow Cary’s standard (See Attachment 2 - PLC Controller Development Standards and Tag names Conventions)

• PLC and SCADA tag names shall be consistent and shall match exactly for all points exchanged between the PLC and SCADA system.

• Each SCADA tag shall include a clear, descriptive point description that identifies the associated equipment and the function, status, alarm, command, setpoint, or measured value represented by the tag. For example, a tag associated with a pump run command shall be described as “Pump [Identifier] Run Command.”

iii. Sequence of Operations narrative required as part of the proposal (not just a BOM) to demonstrate understanding of the process.

iv. Inventory existing station PLC and SCADA functions. Document their migration into the updated Tier 1 application and duplication in Tier 2. Retire existing functions only with Town approval.

b. Intellectual Property / Code Ownership

i. Full code ownership: all application code, HMI screens, and configuration files delivered to Owner with full rights — no vendor lock-in.

ii. Native (uncompiled) source files required at closeout.

c. Documentation Deliverables

i. As-built panel drawings (DWG and PDF); PLC source code with comments;

HMI runtime and source; Tier 1 and Tier 2 application files and backups; I/O list; SCADA tag database; network architecture; sequence of operations;

failover and float backup description; alarm setpoint schedule; O&M manual.

d. Site Acceptance Test

i. SAT / commissioning plan: formal plan with loop checks, sequence-of-operation verification, and a punch list with sign-off.

ii. Include all test hardware, instruments, simulators, leads, software tools, and other equipment needed to execute the approved tests.

iii. Test primary-controller faults, controller power loss, and specified communications failures. Verify backup takeover, required I/O availability, prevention of conflicting commands, and controlled recovery.

iv. Demonstrate independent hardwired float backup for each wet well with PLC control unavailable. Verify start/stop sequencing, required motor and valve protection, operating-mode transfer, and restoration of normal control.

v. Verify every physical and communications point through the PLC, local HMI, Tier 1 application, and Tier 2 read-only application. Confirm all station screens and equipment representations are complete and consistent.

vi. Verify Tier 2 read-only restrictions and stale-data indications. Record results, correct deficiencies, and retest affected functions before acceptance.

vii. Acceptance criteria: sequence-of-operation verification, Pump alternation verification, Failure/fault handling verification.

7. Calibration, Startup, and Training

a. Instrument Calibration

i. All field instruments calibrated before startup; calibration certificates and baseline setpoint record submitted.

b. Startup Services

i. Integrator engineer on-site to verify sequence of operation, alternation logic, alarm thresholds, and SCADA tag mapping.

ii. Punch-list closeout milestone defined; minimum 2 days on-site support post-

SAT.

c. Training

i. On-site training: [1–2] sessions for operations and maintenance staff.

ii. User-level and admin-level HMI/PLC training plus delivery of training materials.

8. Warranty, Spare Parts, and Long-Term Support

a. Warranty

i. Minimum [12] months (parts and labor) covering hardware and programming defects.

ii. Critical-failure callout response: [4-hour remote / 24-hour on-site]

b. Spare Parts

i. Recommended spare parts list with pricing; starter kit (one of each critical module, fuse, relay, PLC card type.

9. Professional Services Expected to Provide

a. Upon receipt of a written Notice to Proceed from Cary, the Contractor shall plan and execute a kick-off meeting with Cary. The kick-off meeting shall occur within 30 days of the Contractor receiving written Notice to Proceed. Subcontractors should be included at the discretion of the Contractor. At the kick-off meeting, the Contractor shall be prepared to review the scope of the Project, provide an initial project schedule, and confirm deliverables. Agendas, presentations, and handouts shall be prepared by the Contractor and distributed to all attendees ahead of the meeting as required. Meeting minutes shall be prepared and distributed within three business days of meeting completion.

b. Prior to beginning work, the Contractor shall develop an installation, startup, and commissioning plan. The plan shall be submitted to Cary for review and approval prior to any modifications at the plant. The plan shall include the following:

i. A detailed timeline for demolition of old equipment and commissioning of new equipment.

ii. The duration of removal, installation, testing, programming, and commissioning activities.

iii. Develop an implementation plan for the new hardware and application upgrades to be reviewed and approved by Cary.

iv. Develop a commissioning, acceptance testing, and start-up plan for review by Cary.

v. The need for additional operational support.

vi. Test forms for each component, each I/O point on the final system, and each loop.

vii. Any other information the Contractor deems necessary.

c. Produce new drawings for each control panel for hardware and wiring changed by this scope of work.

d. Provide all necessary submittals for review and approval by Cary.

e. Completely remove wiring that will no longer be used. All removed equipment shall be turned over to Cary.

f. Procure, furnish, and install all equipment as specified in the design and required hardware/platform.

i. Parts were selected based on compatibility with existing wiring schemes and not to intentionally eliminate any one bidder.

ii. Provide any additional equipment, mounting hardware, or other items required to provide a complete and functioning system.

h. Remove or reconnect I/O points from the existing PLC racks to the new PLC racks in accordance with the existing and new I/O lists and associated instructions in a manner th at minimizes disruption to the pump station operation.

i. Provide wire labels for all wires missing labeling.

j. Testing of each I/O point from the source equipment all the way to the PLC and

HMI/OIT. Signoff forms shall include the polarity of each digital signal and the raw and engineering range of each analog signal.

k. Upgrade the existing PLC and I/O hardware to Allen-Bradley controllers and I/O hardware.

l. Update the existing PLC program to a modern logic such as Studio 5000 program version

34 or newer to run with the new Allen-Bradley controllers. All messaging between PLCs needs to remain.

q. Re-address the tags in the existing Aveva System Platform application for the new PLC tags.

r. Duplicate the complete station application in the Cary’s Tier 2 AVEVA Read-Only Solution.

s. Provide one 4-hour training session on the maintenance of physical assets such as PLC systems Wonderware and power supplies provided for the project.

The new hardware and software shall be compatible with the current SCADA system: Aveva System Platform.

10. Schedule Limitations

a. The pump station new wet well side shall not be taken out of service during the work.

b. The old wet well submersible pumps can only be taken out of service for a maximum of

30 consecutive days with the possibility of running the pumps manually.

11. Documentation for Review The following drawings and information are available for review:

• HMI Software Development Standards (Attachment 1)

• PLC Controller Development Standards and Tag names Conventions (Attachment 2)

• Swift Creek Pump Station Electrical Improvement Drawings (Attachment 3)

• Existing Old Wet Well Pump Control PLC Cabinet Drawings (Attachment 4)

• Existing Old Wet Well Pump Valve Control Details and Assembly (Attachment 5)

The existing PLC programs and SCADA programs will be made available to the awarded Contractor.

The Contractor is to review the information provided and provide a solution that is fully functional.

12. Contract Deliverables

Contractor responsibilities include, but are not limited to:

a. Control Panel Submittal including:

i. Table of Contents

ii. Bill of Materials

iii. Datasheets for each major component with part number clearly indicated.

iv. Panel design drawings

• Drawings shall include layout, power distribution, and PLC I/O.

• Provide native drawing files for all new drawings.

b. Project Implementation Plan including the following minimum content:

ii. Project timeline, including submittal period, implementation schedule, and testing schedule.

iii. PLC replacement plan

c. Project Closeout Documentation including:

i. Revised I/O list

ii. Contractor warranty statement on workmanship and materials of 1-year.

iii. All completed testing forms.

iv. Final As-Built drawings

v. Digital copies of all PLC programs and HMI applications

vi. Project training materials

d. Contractor shall submit all deliverables electronically (in PDF unless otherwise specified) to Cary

e. Access to any sites will be granted as agreed to with Cary

Requests for additional work or change orders must be submitted in writing and approved by Cary in advance of commencing work.

4 COST PROPOSAL/EXECUTION OF PROPOSAL

By submitting this proposal, the potential contractor certifies the following:

• This proposal is signed by an authorized representative of the firm.

• The cost and availability of all equipment, materials, and supplies associated with performing the services described herein have been determined and included in the proposed cost.

• All labor costs, direct and indirect, have been determined and included in the proposed cost.

• The potential contractor has read and understands the conditions set forth in this RFP to include TOC general conditions/service terms, any addenda, and all attached exhibits and agrees to them with no exceptions.

By:

(Signature)

Name:

(Printed)

Title:

Date

5 REFERENCES

Offeror must supply (3) three Governmental Agency or Private Company references for PLCs replacement services have been performed during the past (5) five years. Offerors are cautioned to provide accurate reference information. References will be checked during evaluation period.

OFFEROR: _________________________________________________________________

CITY, STATE, ZIP: __________________________________________________________

Reference # 1

Agency or Firm Name: ________________________________________________________

Business Address

City: ______________________________ State: ________ Zip Code: _____________

Phone Number: (____) ______________________ Fax Number: (____) ________________

Email Address: ______________________________________________________________

Reference # 2

Agency or Firm Name: ________________________________________________________

Business Address

City: ______________________________ State: ________ Zip Code: _____________

Reference # 3

Agency or Firm Name: ________________________________________________________

Business Address ____________________________________________________________

City: ______________________________ State: ________ Zip Code: _____________

INSTRUCTIONS TO VENDORS

1. READ, REVIEW AND COMPLY: It shall be the Vendor’s responsibility to read this entire document, review all enclosures and attachments, and any addenda thereto, and comply with all requirements specified herein, regardless of whether appearing in these Instructions to Vendors or elsewhere in this RFP document.

2. ACCEPTANCE AND REJECTION: The Town reserves the right to reject any and all proposals, to waive any informality in proposals and, unless otherwise specified by the Vendor, to accept any item in the proposal. If either a unit price or an extended price is obviously in error and the other is obviously correct, the incorrect price will be disregarded.

3. BASIS FOR REJECTION: The Town reserves the right to reject any and all offers, in whole or in part, by deeming the offer unsatisfactory as to quality or quantity, delivery, price or service offered, non-compliance with the requirements or intent of this solicitation, lack of competitiveness, error(s) in specifications or indications that revision would be advantageous to the Town, cancellation or other changes in the intended project or any other determination that the proposed requirement is no longer needed, limitation or lack of available funds, circumstances that prevent determination of the best offer, or any other determination that rejection would be in the best interest of the Town.

4. EXECUTION: Failure to sign EXECUTION PAGE in the indicated space will render proposal non-responsive, and it shall be rejected.

5. ORDER OF PRECEDENCE: In cases of conflict between specific provisions in this solicitation or those in any resulting contract, the order of precedence shall be (high to low): (1) The Principal Contract Terms, (2) RFP Terms, (3) Instructions in INSTRUCTIONS TO VENDORS, and (4) Vendor’s Proposal.

6. INFORMATION AND DESCRIPTIVE LITERATURE: Vendor shall furnish all information requested and, in the spaces, provided in this document. Further, if required elsewhere in this proposal, each Vendor must submit with their proposal sketches, descriptive literature and/or complete specifications covering the products offered. Reference to literature submitted with a previous proposal or available elsewhere will not satisfy this provision. Proposals that do not comply with these requirements shall be subject to rejection without further consideration.

7. CONFIDENTIAL INFORMATION: To the extent permitted by applicable statutes and rules, the Town will maintain confidential trade secrets that the Vendor does not wish disclosed. As a condition to confidential treatment, each page containing trade secret information shall be identified in boldface at the top and bottom as “CONFIDENTIAL” by the Vendor, with specific trade secret information enclosed in boxes or similar indication. Cost information shall not be deemed confidential under any circumstances. Regardless of what a Vendor may label as a trade secret, the determination whether it is or is not entitled to protection will be determined in accordance with G.S. 132-1.2. Any material labeled as confidential constitutes a representation by the Vendor that it has made a reasonable effort in good faith to determine that such material is, in fact, a trade secret under G.S. 132-1.2. Vendors are urged and cautioned to limit the marking of information as a trade secret or as confidential so far as is possible.

8. COMMUNICATIONS BY VENDORS: In submitting its proposal, the Vendor agrees not to discuss or otherwise reveal the contents of its proposal to any source, government or private, outside of the using or issuing agency until after the award of the Contract or cancellation of this RFP. All Vendors are forbidden from having any communications with the using or issuing agency, or any other representative therein, concerning the solicitation, during the evaluation of the proposals (i.e., after the public opening of the proposals and before the award of the Contract), unless the Town directly contacts the Vendor(s) for purposes of seeking clarification or another reason permitted by the solicitation. A Vendor shall not: (a) transmit to the issuing and/or using agency any information commenting on the ability or qualifications of any other Vendor to provide the advertised good, equipment, commodity; (b) identify defects, errors and/or omissions in any other Vendor’s proposal and/or prices at any time during the procurement process; and/or (c) engage in or attempt any other communication or conduct that could influence the evaluation and/or award of the Contract that is the subject of this RFP.

Vendors not in compliance with this provision may be disqualified, at the option of the Town, from the Contract award. Only those communications with the using agency or issuing agency authorized by this RFP are permitted.

9. WITHDRAWAL OF PROPOSAL: A Proposal may be withdrawn only in writing and actually received by the office issuing the RFP prior to the time for the opening of Proposals identified on the cover page of this RFP (or such later date included in an Addendum to the RFP). A withdrawal request must be on Vendor’s letterhead and signed by an official of the Vendor authorized to make such request. Any withdrawal request made after the opening of Proposals shall be allowed only for good cause shown and in the sole discretion of the Town.

10. INFORMAL COMMENTS: The Town shall not be bound by informal explanations, instructions or information given at any time by anyone on behalf of the Town during the competitive process or after award. The Town is bound only by information provided in this RFP and in formal Addenda issued through the eVP website.

11. COST FOR PROPOSAL PREPARATION: Any costs incurred by Vendor in preparing or submitting offers are the Vendor’s sole responsibility; the Town will not reimburse any Vendor for any costs incurred prior to award.

12. VENDOR’S REPRESENTATIVE: Each Vendor shall submit with its proposal the name, address, and telephone number of the person(s) with authority to bind the firm and answer questions or provide clarification concerning the firm's proposal.

13. SUBCONTRACTING: Unless expressly prohibited, a Vendor may propose to subcontract portions of the work to identified subcontractor(s), provided that its proposal clearly describe what work it plans to subcontract and that Vendor includes in its proposal all information regarding employees, business experience, and other information for each proposed subcontractor that is required to be provided for Vendor itself.

14. INSPECTION AT VENDOR’S SITE: The Town reserves the right to inspect, at a reasonable time, the equipment/item, plant, or other facilities of a prospective Vendor prior to Contract award, and during the Contract term as necessary, for the Town determination that such equipment/item, plant or other facilities conform with the specifications/requirements and are adequate and suitable for the proper and effective performance of the Contract.

TOWN OF CARY PRINCIPAL CONTRACT

Any Vendor whose proposal is selected by Town shall be expected to enter into the following Principal Contract with Town. As stated in section 1.3 of this RFP, any Vendor who submits a response to this RFP certifies by making said submittal that it has reviewed this Principal Contract and are, at the time of submittal, are prepared to enter into this Principal Contract should its proposal be selected. Also as stated in section 1.3, Vendor should use the question procedure described in section 1.6 to address any questions Vendor has about the Principal Contract prior to making its submittal. Notwithstanding anything to the contrary contained in Contractor’s Proposal, the terms and conditions of the Principal Contract and the RFP, if any, apply and take precedence and control over inconsistent, ambiguous or contrary terms and conditions in Proposal. However, if Proposal imposes a more stringent standard or obligation on Contractor then the more stringent standard or obligation shall apply.

A copy of the Town’s Principal agreement can be found at the following location:

https://carync.box.com/s/qbtn33vd135i3uzwji7eorn7s3gpwgee https://carync.box.com/s/qbtn33vd135i3uzwji7eorn7s3gpwgee