Attch_2_-BAS_Controls_Specifications_-_Manchester_BAS_27_Jul_26.pdf

NWFSC BAS Controls Specifications

07/27/2026 Page 1 of 3

PART 1 GENERAL

1.1 INTENT & OPEN ARCHITECTURE MANDATE

A. Core Principle: Furnish and install a fully operational Building Automation System (BAS) using direct digital control (DDC) built entirely on open, non-proprietary communication protocols and commercially supported hardware/software.

B. Vendor Independence: The BAS shall execute without reliance on single-source suppliers, proprietary software tools, exclusive territorial service agreements, or vendor lock-in. Any qualified system integrator must be able to commission, service, modify, or expand the system.

C. Hierarchical Architecture: The system connectivity and software architecture shall adhere to a 6-layer open framework:

1. Presentation Layer: HTML5 Web Interface, GUI, Dashboards.

2. Application Layer: Integration, Analytics, Supervisory Control.

3. Data Layer: Relational Databases, Warehousing, Historical Logs.

4. Communications Layer: BACnet, Modbus, MQTT, Open APIs.

5. Network Layer: Ethernet Routing, Switching, Cybersecurity.

6. Process Layer: Field Devices, Sensors, Actuators, Edge/Unitary Controllers.

D. Order of Precedence: This specification defines the technical baseline for Building Automation System (BAS) performance, open architecture, and IT security. If any technical requirement in this specification conflicts with a project-specific requirement in the Statement of Work (SOW)—such as equipment point counts, data retention durations, or spare hardware capacity—the Statement of Work (SOW) shall govern.

1.2 OWNERSHIP & LICENSING RIGHTS

A. Data Ownership: NWFSC retains absolute ownership of all real-time and historical data, whether stored on local controllers, local servers, or cloud repositories.

B. Code & Software Ownership: NWFSC shall be the named license holder for all system software.

NWFSC shall receive full ownership of all job-specific configuration files, source code, graphical files, database backups, and custom applications developed for the project.

C. No Recurring Fees: Core system software, programming environments, and graphics shall require no mandatory ongoing or recurring licensing or subscription fees.

1.3 SUBMITTALS & QUALITY ASSURANCE

A. Submittals: Provide complete architecture diagrams, controller schedules, input/output point schedules, sequence of operations, BACnet PICS statements, and cybersecurity plans prior to installation.

B. Qualifications: Integrators must be factory-authorized and demonstrated experts in open-protocol BAS deployment.

1.4 SYSTEM DESCRIPTION & LEGACY INTEGRATION

A. Native Communication: The BAS shall consist of interoperable, stand-alone digital controllers communicating through open protocols to supervisory controllers and operator interfaces.

B. Legacy System Integration: Where existing government-owned legacy hardware is retained on site (such as existing EasyIO controllers or seawater monitoring gateways), the Contractor shall integrate these assets into the unified BAS using BACnet communications, as per the SOW.

PART 2 PRODUCTS & MATERIALS

2.1 NATIVE OPEN COMMUNICATION PROTOCOLS. All controllers and supervisory devices must communicate natively using standard open protocols without requiring proprietary translation gateways:

A. Network/Field Level: BACnet/IP, BACnet MS/TP, Modbus TCP/IP, Modbus RTU.

B. Enterprise & Transport Level: MQTT, RESTful APIs, HTTPS, IP/UDP/TCP.

07/27/2026 Page 2 of 3

2.2 CONTROLLER HARDWARE & I/O SPECIFICATIONS

A. Supervisory & Field Controllers: Microprocessor-based, stand-alone digital controllers capable of executing local PID control loops, schedules, and safety logic independently of upstream network connectivity.

B. Input/Output (I/O) Capability:

1. Universal Inputs (UI): 12-bit Analog-to-Digital (A2D) resolution with Programmable Gain

Amplifiers. Must support resistance (0–500k Ohm, 10k Type II/III, 1k Platinum/Balco thermistors), 0–10 VDC, 0–20 mA, dry contact, and pulse inputs (up to 20 Hz).

2. Digital Outputs (DO): Form-A/C dry contact relays rated for minimum 1A @ 24 VAC/VDC with LED status indication.

3. Universal Outputs (UO): Software-configurable for 0–10 VDC, 0–20 mA, or 4–20 mA (driving load impedance up to 800 ohms).

C. Spare Capacity: Controllers and control panels must maintain a minimum of twenty percent (20%) spare physical I/O capacity (AI, AO, BI, BO) and logical processing capacity, as per the SOW, unless noted otherwise in the SOW.

2.3 USER INTERFACE & PROGRAMMING ENVIRONMENT

A. Web-Based Interface: HTML5-compliant native web server supporting standard modern browsers (Edge, Chrome, Firefox, Safari). Strictly no proprietary browser plug-ins, Flash, or Java required.

B. Programming Tools: One unified, non-proprietary engineering software tool for system programming, live logic viewing, and real-time commissioning. System must support live online tuning and real-time parameter changes without offline compilation shutdowns.

PART 3 EXECUTION & CONTROL STRATEGIES

3.1 OBJECT LIBRARIES & LOGIC STANDARDS. The system shall utilize standard object-oriented programming libraries complying with BACnet Standard 135:

A. Standard BACnet Objects: Analog Input/Output/Value, Binary Input/Output/Value, Multi-State

Input/Output/Value, Schedule, Calendar, and Device Objects.

B. Command Prioritization: Binary/Analog outputs must incorporate 16-level BACnet command priority arrays for override management.

C. Control Strategies: Standard objects shall support PID Control Loops, Start-Stop Time Optimization, Interlocks, and Temperature Overrides.

3.2 RELATIONAL DATABASE & TRENDING

A. Relational Database (RDMS): Store trend logs, alarm histories, and system configuration in standard

SQL/RDMS database structures.

B. Data Export: Support automated export of trend logs in CSV, XML, JSON, or HTML formats.

C. Automated Backups: Historical trend data, alarm logs, graphics, and controller logic databases must be included within scheduled, automated system backup procedures.

D. Data Retention: Historical operational data, trend logs, and calculated values shall be maintained within the system for a minimum of twenty-four (24) months without degradation of system performance, as per the SOW, unless noted otherwise in the SOW.

3.3 SYSTEM INTEGRATION

A. Third-Party Integration: The BAS shall support integration with third-party and existing facility systems using open, non-proprietary communication methods. Where existing government-owned legacy hardware is retained on site (such as existing EasyIO controllers or seawater monitoring gateways), the Contractor shall integrate these assets into the unified BAS using BACnet communications, as per the

SOW.

07/27/2026 Page 3 of 3

3.4 CYBERSECURITY

A. Standard Compliance: All network-connected devices must support modern encryption protocols (TLS

1.2 or higher, HTTPS, SSH, 802.1x authentication for network access).

B. Credential Management: Default factory passwords must be changed prior to commissioning. Unused physical or logical ports must be disabled. Direct Internet exposure is prohibited; remote access must route through Owner-approved VPN/VLAN pathways.

PART 4 ENCLOSURES, CABLING, & INSTALLATION

4.1 ENCLOSURE CONSTRUCTION & RATINGS

A. Panel Fabrication: Controllers shall be housed in lockable, vandal-proof enclosures fabricated from minimum 14 SWG CRCA sheet steel with seam-welded joints, hinged/latched doors, and internal wire management.

B. Environmental Protection:

1. Indoor / Clean Areas: NEMA 1 / IP30 minimum.

2. Mechanical Rooms / Dust-Prone Areas: NEMA 12 / IP54 minimum.

3. Outdoor / Wet Locations: NEMA 3R / IP66 minimum, UL-listed for outdoor applications.

4.2 WIRING & CONDUITS

A. Conduit & Separation: Run separate conduits for power wiring and low-voltage communication cabling.

Maintain separation from sources of strong electromagnetic noise.

B. Termination & Bushings: All panel conduit entries shall utilize smooth-bore brass bushes or approved fittings to prevent cable sheath damage. All field wiring must terminate on internal panel terminal blocks.

C. Labeling: Permanently label all controllers, expansion modules, sensors, actuators, network nodes, and cable ends with markers matching as-built shop drawings.

4.3 FIELD DEVICES

A. Sensors & Actuators: Commercial-grade sensors (temperature, pressure, humidity, flow) selected for accuracy and response characteristics. Actuators shall be electronic modulating with true position feedback and fail-safe return where specified.

PART 5 TESTING, COMMISSIONING, & CLOSEOUT

5.1 VERIFICATION & THIRD-PARTY COMMISSIONING

A. 100% Point Verification: Point-to-point end-to-end verification of every physical and software point prior to functional testing.

B. Third-Party Commissioning: System commissioning shall be conducted by an independent third-party agent against the contract specification and approved point schedules.

5.2 DELIVERABLES & TRAINING

A. Closeout Package: Deliver searchable PDF O&M manuals, as-built network/wiring schematics, verified system backup image files, and editable native source code.

B. Training Requirement: Provide a minimum of 16 hours of instructor-led operational, administrative, and troubleshooting training for NWFSC staff.

C. Warranty: Provide a 1-year comprehensive hardware, firmware, and software warranty following final system acceptance.