PROGRAMMABLE IP CONTROL UNIT TECHNICAL REQUIREMENTS

This article is about general and technical requirements for PROGRAMMABLE IP CONTROL UNIT (PICU) used in Integrated Automation System or Building Automation System.

PROGRAMMABLE IP CONTROL UNIT TECHNICAL REQUIREMENTS

    1. HVAC PICU controllers shall be fully programmable to meet the unique requirements of the facility it shall control. The controller platform shall provide options and advanced system functions, programmable and configurable using Niagara 4 Framework, that allow standard and customizable control solutions required in executing the “Sequence of Operation”. PICU shall be BACnet BTL; AWS/C, WSP listed. PICU shall meet the BACnet Building Controller (B-BC) Profile.
    2. All PICUs shall be application programmable and shall always maintain their certification. All control sequences within or programmed into the PICU shall be stored in non-volatile memory, which is not dependent upon the presence of a battery to be retained.
    3. The controllers shall be capable of daisy-chain IP communications with other PICU’s and peer-to-peer communications with SNC’s and with any OWS connected to the BAS, whether the OWS is directly connected, connected via cellular modem or connected via the Internet.
      1. Daisy Chain IP connectivity Integrated Fail-safe utilizing Spanning Tree Protocol 802.1w.
    4. The communication protocols utilized for peer-to-peer communications between PICU’s will be Niagara 4 FoxS or BACnet TCP/IP. Use of a proprietary communication protocol for peer-to-peer communications between PICU’s is not allowed.
    5. The PICU shall be licensed and enabled to support four (4) devices and shall be licensed with the following Open protocol drivers by default:
      1. BACnet IP
    6. The PICU shall be provided with Lifetime Software Maintenance license. Labor to implement not included.
    7. The PICU shall be capable of executing application control programs to provide:
      • Calendar functions.
      • Scheduling
      • Trending
      • Alarm monitoring and routing.
      • Time synchronization.
      • Integration of all daisy-chain PICU’s.
      • Network management functions for all daisy-chain PICU’s.
    8. Programming software shall be embedded into the PICU. The PICU shall not require any external configuration tool or programming tool. All configuration and programming tasks shall be accomplished and accessible from within the embedded Niagara 4 environment.
    9. The PICU shall support the following security functions.
      • Module code signing to verify the author of programming tool and confirm that the code has not been altered or corrupted.
      • Role-Based Access Control (RBAC) for managing user roles and permissions.
      • Require users to use strong credentials.
      • Data in Motion and Sensitive Data at Rest be encrypted.
      • Encrypted (PKI) Secure IP Stack Communication Security.
      • FIPS 140-2 Level 1 Cryptographic Module Compliant.
    10. The minimum controller Environmental ratings.
      • Operating Temperature Ambient Rating: -4 degrees to 131 degrees F (-20 degrees to 55 degrees C).
      • Storage Temperature Ambient Rating: -4 degrees to 150 degrees F (-20 degrees to 65 degrees C).
      • Relative Humidity: 5% to 95% non-condensing.
    11. The controller shall have the additional approval requirements, listings, and approvals:
      • UL 60730-1.
      • Meets FCC Part 15, Subpart B, Class B (radiated emissions) requirements.
      • Conforms requirements European Consortium standard EN 61000-6-1; 2001 (EU Immunity).
      • Conforms requirements European Consortium standard EN 61000-6-3; 2001 (EU Emission).
      • The controller housing shall be UL plenum rated mounting to either a panel or DIN rail (2.3” x 5.3” x 4.3”; 57.4mm x 135mm x 110mm).
    12. The PICU shall provide the following hardware features as a minimum:
      • The PICU shall provide LED indication of Power, Fault, Ethernet TX/RX/Traffic/Speed without cover removal.
      • Four 10/100/1000 Mbps Ethernet unmanaged switch, RJ-45 ports.
      • ARM 9 32-bit processor, 800 MHz
      • 1 GB RAM
      • 512 KB MRAM
      • 2 GB Flash Memory
      • One USB 2.0 port.
      • 0 A fast-acting Overcurrent Protection.
      • Integrated 20-30 VAC Global Power Supply
      • Real Time Clock, 24 hour, 365 day, multi-year calendar +/- 1 minute per month at 77F (25C).
      • RTC Power Failure Backup, 24 hours at 32 degrees to 100 degrees F (0 degrees to 38 degrees C)
      • Power Output: 20 VDC +/- 10% at 7 mA maximum.
      • AC power consumption at 9VA, max 100VA.
      • Removable Terminal Blocks.
      • Sensor, Actuator, and I/O Module Expandability via a 2-wire, polarity insensitive local PICU communication bus.
      • 150 Point Base License (Expandable).
      • LED for each hardware I/O point.
      • Output H-O-A Switches.
      • VAV PICU shall include an internal differential pressure sensor.
        • Operating Range: 0 to 2 inch WC (0 to 374 Pa).
        • Accuracy: +/- 2% of full scale at 32 degrees to 122 degrees F (0 degrees to 50 degrees C).
      • The PICU shall support standard Web browser access via the Intranet/Internet.
      • The PICU shall be able to route any alarm condition to any defined user location whether connected to a local network or wide-area network.
        1. Alarm generation shall be selectable for annunciation type and acknowledgement requirements including but not limited to:
          • Alarm
          • Return to normal.
          • To default.
        2. Alarms shall be annunciated in any of the following manners as defined by the user:
          • Screen message text.
          • Email of complete alarm message to multiple recipients.
          • Pagers via paging services that initiate a page on receipt of email message.
          • Graphics with flashing alarm object(s).
        3. The following shall be recorded by the PICU for each alarm (at a minimum):
          • Time and date.
          • Equipment (air handler #, access way, etc.).
          • Acknowledge time, date, and user who issued acknowledgement.
    13. PICU Controllers shall support at minimum the following control techniques:
      • General-purpose control loops that can incorporate Demand Limit Control strategies, Set point reset, adaptive intelligent recovery, and time of day bypass.
      • General-purpose, non-linear control loops.
      • Start/stop Loops.
      • If/Then/Else logic loops.
      • Math Function loops (MIN, MAX, AVG, SUM, SUB, SQRT, MUL, DIV, ENTHALPY).
      • Analytic calculations.
    14. The following six [6] integral Universal Inputs/Outputs shall be supported per each PICU:
      • UI/O as Analog Inputs; 16 Bit resolution (Thermistor or RTD configurable from 100 to 100K Ohm, 0-10 VDC, 4-20 mA).
      • UI/O as Digital Inputs; Dry Contact / Totalizer.
        1. Dry Contact to detect Open / Closed Circuit (Voltage Rating; 0-30 VDC Open Circuit: Resistance Rating; Open Circuit >3,000 Ohms, Closed Circuit <500 Ohms).
        2. Totalizer – Dry Contact (100 Hz, 360,000 pulses per hour maximum frequency: Minimum Duty Cycle 5 ms ON / 5 ms OFF).
      • UI/O as Analog Outputs ([3] UI/O can be configured as AO)
        1. 0-10.0 Vdc, 10.0mA maximum.
        2. 0-20.0 mA, 550 Ohms maximum.
      • LED for each hardware I/O point.
    15. The following six [6] integral Digital Outputs (Triac) shall be supported per each PICU:
      1. Solid State Relay normally open contacts, 20-30 VAC @ 50/60 Hz, at 1.0 A Continuous, 3.5 A Inrush.
      2. LED for each hardware I/O point.
      3. Output H-O-A Switches.
    16. The PICU shall employ a 150 Point Base License (expandable) device count capacity license model that supports I/O expansion capabilities.
    17. Each PICU shall have expansion ability to support additional I/O requirements through the use of remote input/output modules and a local communication bus. Each PICU shall be able to support a maximum of 15 Expansion I/O Modules for a maximum of 312 physical I/O points.
      1. Mixed Expansion I/O Modules (UI/O & DO) shall communicate with PICU via a 2-wire bus and include removable terminals for field device wires.
      2. Mixed Expansion I/O Modules shall be available in the following configurations:
        1. 3 UI/O, 2 AO, and 2 DO (7 Points).
        2. 14 UI/O (5 can be configured as AO) and 6 DO (20 Points).
      3. Universal Inputs/Outputs shall be supported per each Expansion I/O Module:
        1. UI/O as Analog Inputs; 16 Bit resolution (Thermistor or RTD configurable from 100 to 100K Ohm, 0-10 VDC, 4-20 mA).
        2. UI/O as Digital Inputs; Dry Contact / Totalizer.
          • Dry Contact to detect Open / Closed Circuit (Voltage Rating; 0-30 VDC Open Circuit: Resistance Rating; Open Circuit >3,000 Ohms, Closed Circuit <500 Ohms).
          • Totalizer – Dry Contact (100 Hz, 360,000 pulses per hour maximum frequency: Minimum Duty Cycle 5 ms ON / 5 ms OFF).
        3. UI/O as Analog Outputs (UI/O can be configured as AO)
          • 0-10.0 Vdc, 10.0mA maximum.
          • 0-20.0 mA, 550 Ohms maximum.
        4. LED for each hardware I/O point.
      4. Digital Outputs (Triac) shall be supported per each Expansion I/O Module:
        1. Solid State Relay normally open contacts, 20-30 VAC @ 50/60 Hz, at 1.0 A Continuous, 3.5 A Inrush.
        2. LED for each hardware I/O point.
        3. Output H-O-A Switches.
    18. The PICU shall not include an integrated Local Operator Interface but shall be capable of utilizing a standard browser-based device such as a Tablet, Touch Screen Device, etc.

Discover more from PAKTECHPOINT

Subscribe to get the latest posts to your email.

Leave a Comment

error: Content is Protected.