Unitary IP Control Unit (UICU) Technical Requirements for IAS

This article is about general and technical requirements for Unitary IP Control Unit (UICU) used in Integrated Automation System or Building Automation System.

Unitary IP Control Unit (UICU) Technical Requirements for IAS

    1. HVAC UICU controllers shall be fully programmable to meet the unique requirements of the HVAC equipment 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”.
    2. All UICUs shall be application programmable and shall always maintain their certification. All control sequences within or programmed into the UICU 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 UICU’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.
    4. The communication protocols utilized for peer-to-peer communications between UICU’s will be Niagara 4 FoxS or BACnet TCP/IP. Use of a proprietary communication protocol for peer-to-peer communications between UICU’s is not allowed.
    5. The UICU shall be licensed and enabled to support three (3) devices and shall be licensed with the following Open protocol drivers by default:
      • BACnet IP and BACnet MSTP
      • Modbus TCP and Modbus RTU
      • SNMP
    6. The UICU shall be provided with Lifetime Software Maintenance license. Labor to implement not included.
    7. The UICU 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 UICU’s.
      • Network management functions for all daisy-chain UICU’s.
    8. Programming software shall be embedded into the UICU. The UICU 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 UICU 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 UICU’s.
      • Network management functions for all daisy-chain UICU’s.
    10. The minimum controller Environmental ratings.
      • Operating Temperature Ambient Rating: -4 degrees to 140 degrees F (-20 degrees to 60 degrees C).
      • Storage Temperature Ambient Rating: -40 degrees to 185 degrees F (-40 degrees to 85 degrees C).
      • Relative Humidity: 5% to 95% non-condensing
    11. The controller shall have the additional approval requirements, listings, and approvals:
      • Meets FCC Part 15, Class B (radiated emissions) requirements.
      • C-UL
      • CE
      • UL916, Open Energy Management Class 2
      • RoHS2
      • REACH
      • WEEE
      • CAN/CSA-C22.2 No. 205-12
      • The controller housing shall be UL plenum rated mounting to either a panel or DIN rail (2.40” x 7.04” x 4.53”; 61mm x 179mm x 115mm).
    12. The UICU shall provide the following hardware features as a minimum:
      • The UICU shall provide LED indication of Power, Fault, Ethernet TX/RX/Traffic/Speed without cover removal.
      • ARM Cortex-A9/M4 9, 800 MHz
      • 512 MB DDR SDRAM
      • 2 GB Flash Memory
      • Powered from 24VAC/DC source
      • Two 10/100 MB Ethernet ports capable of daisy chaining
      • 1 RS-485 Serial Port
      • Real Time Clock
      • Secure Boot
      • Ten [10] onboard IO points
      • Supports up to 3 devices or 50 Points
    13. The UICU shall support standard Web browser access via the Intranet/Internet.
    14. The UICU 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 UICU for each alarm (at a minimum):
        • Time and date.
        • Equipment (air handler #, access way, etc.).
        • Acknowledge time, date, and user who issued acknowledgement.
    15. UICU 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).
    16. The following five [5] Universal Inputs shall be supported per each UICU:
      • Type 3 10K Thermistor
      • 0-100K ohm
      • 0-10 VDC
      • 0-20mA with external resistor
      • Dry Contact
    17. The following two [2] Analog Outputs shall be supported per each UICU:
        • 0-10VDC, 4mA max output current
    18. The following three [3] Digital Outputs shall be supported per each UICU:
      • Triac, 24VAC @ 0.5 amp
    19. The UICU shall employ a 50 Point Base License that supports one [1] IO-R-34 expansion module over a shielded RS-485 bus or three [3] devices via the embedded protocols.
    20. Each UICU shall have expansion ability to support additional I/O requirements through the use of a remote input/output module connected to an RS-485 local communication bus. Each UICU shall be able to support a maximum of one [1] 34 Point Expansion I/O Modules for a maximum of 44 physical I/O points.
        1. 34 Point Mixed Expansion I/O Module shall communicate with UICU via a 2-wire RS-485m bus.
        2. Sixteen [16] Universal Inputs shall be supported via 34 Point Expansion I/O Module:
          • Type 3 10K Thermistor
          • 0-100K ohm
          • 0-10 VDC
          • 0-20mA with external resistor
        3. Eight [8] Analog Outputs shall be supported via 34 Point Expansion I/O Module:
          • 0-10.0 Vdc
        4. Ten [10] Digital Outputs (Relay) shall be supported via 34 Point Expansion I/O Module:
          • Form A Contacts, 24 VAC at 0.5 A rated
    21. The UICU shall not include an integrated Local Operator Interface.

Discover more from PAKTECHPOINT

Subscribe to get the latest posts to your email.

Leave a Comment

error: Content is Protected.