Network Controller Technical Requirement and Concept for IAS

This article is about general and technical requirements for Network Controller used in Integrated Automation System or Building Automation System.

Network Controller Technical Requirement and Concept for IAS

  1. General Requirements: The Network Controllers shall be Niagara N4 JACE-8000 controllers. The contractor shall <develop or expand> the <new or existing> system to accomplish the following as part of this project.
    1. These controllers are designed to manage communications between the Programmable IP Control Unit (PICU), Programmable Plant Control Unit (PPCU), Unitary IP Control Unit (UICU), Advanced Unitary Controllers (AUC), and BACnet Touchscreen Communicating Thermostat (BCT) which are connected to its communications trunks or directly on the IP network, manage communications between itself, other system network controllers (NC), PICUs, PPCUs, UICUs, and with any Graphical User Interface (GUI) that are part of the IAS, and perform control and operating strategies for the system based on information from any controller connected to the IAS.
    2. The controllers shall be fully programmable or configurable to meet the unique requirements of the facility it shall control.
    3. The controllers shall be capable of peer-to-peer communications with other NC’s, PICUs, PPCUs, UICUs, and with any OWS connected to the IAS, 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 NC’s will be Niagara 4 FoxS, BACnet TCP/IP and SNMP. Use of a proprietary communication protocol for peer-to-peer communications between NC’s is not allowed.
    5. All NC hardware licenses and certificates shall be stored on local MicroSD memory card employing encrypted “safe boot” technology.
    6. The NC shall employ a device count capacity license model that supports expansion capabilities.
    7. The NC shall utilize I/O Expansion Modules (IO-R-16 and/or IO-R-34) for direct control of equipment.
    8. The NC shall be enabled to support and shall be licensed with the following Open protocol drivers (client and server) by default:
      • BACnet
      • Lon
      • MODBUS
      • SNMP
      • KNX
    9. The NC shall be capable of executing application control programs to provide:
      • Calendar functions.
      • Scheduling
      • Trending
      • Alarm monitoring and routing.
      • Time synchronization.
      • Integration of LonWorks, BACnet, and MODBUS controller data.
      • Network management functions for all NC, PPCU, AUC, and protocol connected devices.
    10. The NC shall support standard Web browser access via the Intranet/Internet. It shall support a minimum of 16 simultaneous users.
    11. The NC shall provide alarm recognition, storage, routing, management and analysis to supplement distributed capabilities of equipment or Advanced Unitary Controllers.
    12. The NC shall be able to route any alarm condition to any defined user location whether connected to a local network or remote via cellular modem, 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 SNC for each alarm (at a minimum):
        • Time and date.
        • Equipment (air handler #, access way, etc.).
        • Acknowledge time, date, and user who issued acknowledgement.
    13. Programming software and all controller “Setup Wizards” shall be embedded into the SNC.
    14. The NC 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.
      • LDAP and Kerberos integration of access management.
    15. The NC shall support the following data modeling structures to utilize Search; Hierarchy; Template; and Permission functionality:
      • Metadata: Descriptive tags to define the structure of properties.
      • Tagging: Process to apply metadata to components
      • Tag Dictionary
    16. The NC shall employ template functionality. Templates are a containerized set of configured data tags, graphics, histories, alarms… that are set to be deployed as a unit based upon manufacturer’s controller and relationships. All lower level communicating controllers (PICU, PPCU, UICU, AUC, VFD…) shall have an associated template file for reuse on future project additions.
      The NC shall be provided with a <1 or 3 or 5> Year Software Maintenance license. Labor to implement not included.
    17. Niagara N4 Data Collection and Storage:
      1. The network controller shall collect data for any property of any object and store this data for future use.
        • The data collection shall be performed by log objects, resident in the network controller that shall have, at a minimum, the following configurable properties: Designating the log as interval or deviation.
        • For interval logs, the object shall be configured for time of day, day of week and the sample collection interval.
        • For deviation logs, the object shall be configured for the deviation of a variable to a fixed value. This value, when reached, will initiate logging of the object.
        • For all logs, provide the ability to set the maximum number of data stores for the log and to set whether the log will stop collecting when full, or rollover the data on a first-in, first-out basis.
        • Each log shall have the ability to have its data cleared on a time-based event or by a user-defined event or action.
      2. All log data shall be stored in a relational database in the network controller and the data shall be accessed from a server (if the system is so configured) or a standard Web Browser.
      3. All log data, when accessed from a server, shall be capable of being manipulated using standard SQL statements.
      4. All log data shall be available to the user in the following data formats:
        • HTML
        • XML
        • Plain text
        • Comma or tab separated values
      5. Systems that do not provide log data in HTML and XML formats at a minimum shall not be acceptable.
      6. The network controller shall have the ability to archive its log data either locally (to itself), or remotely to a server or other network controller on the network. Provide the ability to configure the following archiving properties, at a minimum:
        • Archive on time of day
        • Archive on user-defined number of data stores in the log (buffer size)
        • Archive when log has reached its user-defined capacity of data stores
        • Provide ability to clear logs once archived

    18. Audit Log

      1. Provide and maintain an Audit Log that tracks all activities performed on the network controller. Provide the ability to specify a buffer size for the log and the ability to archive log based on time or when the log has reached its user-defined buffer size.  Provide the ability to archive the log locally (to the network controller), to another network controller on the network, or to a server.  For each log entry, provide the following data:
        • Time and date
        • User ID
        • Change or activity (change set point, add or delete objects, commands, etc.)

    19. Database Backup and Storage

      • The network controller shall have the ability to automatically back up its database. The database shall be backed up based on a user-defined time interval.
      • Copies of the current database and, at the most recently saved database shall be stored in the network controller. The age of the most recently saved database is dependent on the user-defined database save interval.
      • The network controller’s database shall be stored, at a minimum, in XML format to allow for user viewing and editing, if desired. Other formats are acceptable as well, as long as XML format is supported.
      • Provisioning – Automatic downloading of software updates, backups to the entire system database etc. based on user defined parameters.

    20. Graphical User Interface Software – Niagara N4 Supervisor®

      1. The IAS Contractor shall provide system software based on server/thin-client architecture, designed around the open standards of web technology. The IAS server shall communicate using Ethernet and TCP. Server shall be accessed using a web browser over Owner intranet and remotely over the Internet.
      2. The intent of the thin-client architecture is to provide the operator(s) complete access to the IAS system via a web browser. The thin-client web browser Graphical User Interface (GUI) shall be browser and operating system agnostic, meaning it will support HTML5 enabled browsers without requiring proprietary operator interface and configuration programs or browser plug-ins. Microsoft, Firefox, and Chrome browsers (current released versions), and Windows as well as non-Window operating systems.
      3. The IAS server software shall support at least the following server platforms (Windows 7, 8.1, 10, Server 12). The IAS server software shall be developed and tested by the manufacturer of the system stand-alone controllers and network controllers/routers.
      4. The web browser GUI shall provide a completely interactive user interface and shall provide a HTML5 experience that supports the following features as a minimum:
        1. Trending
        2. Schedulling
        3. Electrical demand limiting.
        4. Duty Cycling.
        5. Downloading Memory to field devices.
        6. Real time ‘live’ Graphic Programs.
        7. Tree Navigation.
        8. Parameter change of properties.
        9. Set point adjustments.
        10. Alarm / event information.
        11. Configuration of operators.
        12. Execution of global commands.
        13. Add, delete, and modify graphics and displayed data.
      5. Software Components: All software shall be the most current version. All software components of the IAS system software shall be provided and installed as part of this project. IAS software components shall include:
        • Server Software, Database and Web Browser Graphical User Interface.
        • 3 or 5 Year Software Maintenance license. Labor to implement not included.
        • Embedded System Configuration Utilities for future modifications to the system and controllers.
        • Embedded Graphical Programming Tools.
        • Embedded Direct Digital Control software.
        • Embedded Application Software.
      6. IAS Server Database: The IAS server software shall utilize a Java Database Connectivity (JDBC) compatible database such as: MS SQL 8.0, Oracle 8i or IBM DB2. IAS systems written to Non -Standard and/or Proprietary databases are NOT acceptable.
      7. Thin Client – Web Browser Based: The GUI shall be thin client or browser based and shall meet the following criteria:
        • Web Browser’s for PC’s: Only the current released browser (Explorer/Firefox/Chrome) will be required as the GUI and a valid connection to the server network. No installation of any custom software shall be required on the operator’s GUI workstation/client. Connection shall be over an intranet or the Internet.
        • Secure Socket Layers: Communication between the Web Browser GUI and IAS server shall offer encryption using 128-bit encryption technology within Secure Socket Layers (SSL). Communication protocol shall be Hyper-Text Transfer Protocol Secure (HTTPS).
      8. The following supervisory control applications shall be addressed as a minimum:
        • Fire Alarm System response. (Secondary notification)
        • Smoke Control system response. (Secondary notification)
        • HVAC Global Sequence of Operation.
        • Electrical Demand Limiting.
        • Security System Message Priority Management.

    21. Network Controller and Server Licensing Requirements

      1. All New and Existing Network Controllers and Server equipment and software furnished by or integrated with this project shall be fully licensed to the Owner. The licensing rights shall include the rights for the Owner to authorize any Contractor of their choosing to perform work on the IAS system. The installing contractor shall hold no exclusive rights to the system as it pertains to software, hardware, system updates, system access, modifications, developed databases, etc.
      2. Provide the Owner all required user names and passwords for system access yielding full administration and configuration rights. These shall apply to work stations, servers, network controllers, configurable network electronics, controllers, system software / database and the like.
      3. The Contractor shall not limit in any fashion the ability for other contractors, vendors or operators the ability to manage, configure, or modify the parameters of each Network Controller, server or system software / database.
      4. The Contractor shall coordinate and hold no exclusive rights pertaining to inter-station links between Network Controllers.
      5. The owner shall have rights to update and modify site specific graphics, application programs and database files associated with the sequence of operation.
      6. The owner shall reserve the right and possess the ability to hire a contractor to service, maintain and modify the system. The ability to program, configure, and perform database modifications associated with of all the DDC controllers shall likewise be the property of the Owner. The Contractor shall hold no exclusive rights, or access levels to the system. Third party Contractors shall have full rights and access to the system at any point for system expansion or existing system modifications. All configurations shall be performed via Niagara N4 Supervisor®.
      7. Upon substantial completion the Contractor shall deliver as part of the O&M manuals to the owner electronic copies containing the current databases, Systems Usernames, Passwords and Access Levels for the following components:
        • Network Controllers
        • Server Machine
        • DDC Controllers

Leave a Comment

error: Content is Protected.