Sources Sought for Allen-Bradley ControlLogix 5580 PLC

Solicitation Number: N62478CON31FY2610

Notice Type: Sources Sought

Code 7G21 – IT AND TELECOM – NETWORK: DIGITAL NETWORK PRODUCTS (HARDWARE AND PERPETUAL LICENSE SOFTWARE)

NAICS:

334513 – Instruments and Related Products Manufacturing for Measuring, Displaying and Controlling Industrial Process Variables

Synopsis:

The Government intends to procure, under only one responsible source, where no other suppliers or service will satisfy the agency requirements.  The Naval Facilities Engineering Systems Command, Hawaii (NAVFAC Hawaii) is conducting market research to determine if other potential products/services can provide for a Programmable Logic Controller (PLC) and Input/Output (I/O) Module that has the equal performance and listing/approval requirements as the Allen-Bradley ControlLogix 5580 (1756-L83E) PLC and Allen-Bradley Flex 5000 IO module (5094-) as well as the Rockwell Automation programming software Studio 5000, all manufactured by Rockwell Automation Inc., 1201 South 2nd Street, Milwaukee, WI, 53204-2496.  The alternate product/service must meet the following requirements/specifications:

1.   The existing Allen-Bradley MicroLogix 1400 PLCs installed throughout portions of the Fort Kamehameha WWTP SCADA system are reaching mature lifecycle status. As part of the long term SCADA modernization effort, selection of a compatible new PLC platform is required. The proposed products shall be compatible with the cybersecurity and standardization requirements for the existing SCADA system. The cybersecurity Approval To Operate (ATO) is granted based on the existing SCADA system. Therefore, the proposed products shall be able to integrate and communicate with existing Allen-Bradley PLCs and I/O modules on the existing Fort Kamehameha WWTP SCADA system without additional hardware or software added to the existing PLCs and I/O modules. The system shall also provide a fully redundant supervisory control system to maintain continuous WWTP operation during a controller failure. The system must maintain coordinated controller logic, process data, and distributed I/O status during failover. The existing legacy panels shall also be integrated directly into the new supervisory architecture over the existing EtherNet/IP network via existing fiber optic connections.

2.   Hardware: All process related functions, calculations, timers, and numeric manipulations must be accomplished in the PLC hardware and not in the HMI.

3.   The PLC system must be microprocessor-based, capable of receiving binary and analog inputs and, through programming via the manufacturer’s standard development software, must be able to control binary and analog output functions, perform data handling operations, and communicate with external devices. The platforms must meet the requirements of Class A computing devices, comply with 47 CFR 15, and withstand conducted susceptibility tests as outlined in NEMA ICS 1, NEMA ICS 2, NEMA ICS 3, and IEEE C37.90.1. The PLC hardware must function properly at operating temperatures between 32 and 122 degrees F at 5 to 95 percent relative humidity non-condensing. The hardware must tolerate storage temperatures between minus 40 and plus 140 degrees F at 5 to 95 percent relative humidity non-condensing.

4.   Modular PLC: The PLC must be based on a modular, field-expandable design allowing the system to be tailored to the process control application. The system must be expandable through the use of additional hardware and user software. As a minimum, the main PLC chassis must include a mounting backplane, a power supply module, a central processing unit (CPU) module, and Ethernet communications. Distributed/remote I/O must utilize industrial Ethernet adapters and modular I/O terminal bases. The modules must be grouped together in mounting racks or cabinets. The backplanes and terminal bases must provide the communications mechanism to fully integrate the individual modules. Modules other than remote I/O must plug directly into the backplane. Wire connectors between modules are strictly prohibited except for standard Ethernet expansion between backplanes. The system configuration must support Removal and Insertion Under Power (RIUP), allowing for the removal and/or installation of modules while the system is energized.

5.   Central Processing Unit (CPU) Module: The CPU module must be a self-contained, microprocessor-based unit providing network time synchronization, scanning, application program execution, storage of application programs, storage of numerical values related to the application process and logic, I/O bus traffic control, peripheral and external device communications, and embedded self-diagnostics. The scan time must be 100 milliseconds or better (capable of sub-millisecond ranges depending on logic size), ensuring abundant processing capacity including spare I/O channels.

7.   Communications Module: The communications architecture must allow peer-to-peer communication with other PLCs and central/remote workstations using embedded Gigabit industrial Ethernet ports on the CPU and the remote I/O adapters. The communication network must utilize the manufacturer's standard industrial protocol over standard Ethernet architecture. The network must allow programming of the PLC to be done locally through a laptop computer or remotely from the central station or workstation via the standard programming software.

8.   Power Supply Module: One or more power supply modules must be provided as necessary to power other modules installed in the same cabinet. Main chassis power supplies must plug directly into the backplane. Auxiliary power supplies may be used to supply power to remote I/O cabinets or distributed modules.

1. Power supply modules must use AC power with a nominal voltage of 120 VAC plus or minus 5 percent. Modules must monitor incoming line voltage, provide over-current/over-voltage protection, and ensure a safe, orderly shutdown if voltage falls out of range.
2. Modules must withstand a power loss for a minimum of 20 milliseconds while remaining in operation and providing adequate power to all connected modules.
3. Each power supply module must be provided with an on-off switch integral to the module. If the manufacturer's standard power supply module is not provided with an integral switch, a miniature toggle-type switch must be installed near the PLC and clearly labeled.
4. Power supply modules must feature indicating LED lights that remain lit to confirm proper operating status.

9.   Input/Output (I/O) Modules: The distributed I/O modules must be self-contained, microprocessor-based units that provide an interface to field devices. Each module must contain visual LED indicators to display the on-off and fault status of individual inputs or outputs. Each I/O channel must be protected against reversal of signal polarity. Analog inputs and analog outputs must feature configurable per-channel 'open circuit, short circuit, and out of range' detection.

10. Program Storage/Memory Requirements: The CPU must utilize the manufacturer's standard non-volatile memory for the operating system. The controller must feature electronically readable and writeable non-volatile memory (such as a Secure Digital card or Flash PROM) for the permanent storage of user programs. User programs must be loaded via the programming software from a central station or laptop. The memory capacity must be properly evaluated against the system's control requirements such that, when the system is completely programmed and functional, no more than 50 percent of the allocated memory is utilized.

11. Input/Output Characteristics: Each PLC system must allow for analog input, analog output, binary input, and binary output. The number and type of I/O points must comply with the sequence of control drawings, explicitly including a minimum of 20 percent spare I/O points (and no less than two spare points) for each installed point type. During normal operation, a malfunction in any isolated I/O channel must affect the operation of that specific channel only, without impacting the CPU or other active channels. All input and output circuits must utilize optical isolation (minimum of 1500 VRMS) and must be filtered to guard against high voltage transients from externally connected devices.

12. Analog Inputs: Analog input circuits must be available in 4-20 mA.

13. Binary Inputs: Binary input circuits must be available in 10-30 VDC or 79-132 VAC.

14. Analog Outputs: Analog output circuits must be available in 4-20 mA.

15. Binary Outputs: Binary output circuits must be available in 10-30 VDC or 79-132 VAC.

16. Wiring Connections: Wiring connections must utilize heavy-duty, self-lifting Removable Terminal Blocks (RTBs) in pressure-type screw or spring-terminal configurations, ensuring easy wire insertion and secure connections. Terminals must be capable of accepting up to two #14 AWG wires. The terminal base must include a protective hinged cover over the wiring connections, featuring a write-on area for the identification of external circuits.

17. On-Off Switch: Each controller chassis must be provided with an integral on-off power switch. If the controller/distributed node is not provided with a manufacturer's standard on-off switch, a miniature toggle-type switch must be installed in the control panel near the hardware and clearly labeled as to its function.

18. Diagnostics: The system must implement advanced diagnostic routines in firmware. The CPU must continuously perform self-diagnostic routines during normal system operation to evaluate the configuration and status of the CPU, memory, communications, and I/O traffic. A portion of the scan time must be dedicated to performing these housekeeping functions. A more extensive diagnostic routine must execute automatically at power-up and during controlled system shutdowns. The CPU must log system and I/O module faults in internal tables accessible for display. When a fault occurs on an I/O or communications module, the system must shut down only the affected hardware and continue operating utilizing healthy system components. All faults must be annunciated at the PLC and the central station. Diagnostic software must be useable in conjunction with the portable tester.  The following diagnostics must be performed:

1. Analog Inputs: Sensor out of range detection, open loop detection, shorted loop detection, and analog-to-digital converter operational check;

1. Analog Outputs: Open or shorted loop;

1. Configuration: Validation of electronic keying, module compatibility, and active availability of selected I/O over the network;

1. Hardware and software: Internal logic validation, major/minor fault handling, and firmware integrity checks;

1. Memory: Checksum validation, parity checks, and end-to-end CPU memory verification.

19. Accuracy: Analog input and output modules must perform analog-to-digital and digital-to-analog conversions with a high degree of precision. The analog I/O modules must have an overall accuracy of plus or minus 0.1 or 0.25 percent of full-scale span across the standard normal operating temperature range.

20. The Original Equipment Manufacturer (OEM)-native engineering and configuration software environment for the programming and configuration of the proposed Programmable Logic Controller (PLC) and distributed Input/Output (I/O) platforms shall be provided. This software must serve as the singular, integrated engineering tool designed specifically for the proposed control architecture. To maintain hardware compatibility, ensure secure network integration, and provide reliable long-term lifecycle support for the supervisory control system, third-party bridging tools are prohibited. A single software package must natively handle controller logic, network configuration, and distributed I/O hardware setup. Furthermore, the software suite must natively configure, manage, and monitor standard industrial Ethernet communication protocols and high-availability controller redundancy schemes. Finally, the environment must provide centralized tools for auditing and updating the firmware of the CPU, communication modules, and distributed I/O nodes.

This notification is for market research purposes only and should not be construed as a commitment of any kind by the U.S. Government to issue a solicitation, request for proposals, quotes, or invitation of bids or award a contract.

Interested parties with a comparable product meeting the requirements described in this announcement are invited to submit complete technical data, information and specifications in order for the Government to conduct an evaluation of your product to ensure compatibility with the existing system.  Technical response shall be typed, at least 11 point Times New Roman or larger, single-sided 8.5 by 11 inch pages and submitted in Adobe PDF format.  Also, provide company information and point of contract (name, title, email, phone, mailing address).

The Government will not reimburse any responder for any costs associated with information submitted in response to this sources sought announcement.

Any information provided to the Government in response to this request for information (RFI) will become U.S. Government property and will not be returned.  All proprietary or classified information will be treated appropriately.  The Government reserves the right to disregard any submittal that is incomplete or vague. Please do not submit your company brochure.

Interested parties shall submit information and specifications to Dallas Wong and Justin Pang, Contracting Specialists via email at dallas.j.wong.civ@us.navy.mil and  justin.r.pang.civ@us.navy.mil. Interested parties responding to this announcement by Wednesday, 24 June 2026 at 2:00 p.m. Hawaii Standard Time will be considered.