THIRD PARTY INTERFACES FOR INTEGRATED AUTOMATION SYSTEM

This article is about general and technical requirements for Third Party Interfaces used in Integrated Automation System or Building Automation System.

THIRD PARTY INTERFACES FOR INTEGRATED AUTOMATION SYSTEM

<THE BASE SYSTEM WILL BE A NIAGARA N4 FRAMEWORK WITH NIAGARA N4 IP FIELD CONTROLLERS AND/OR LONWORKS, BACNET OR PROPRIETARY FIELD LEVEL DEVICES. IT IS IMPORTANT TO SELECT THE PRIMARY FIELD LEVEL PROTOCOL BASED ON CLIENT REQUIREMENTS AND EXPECTATIONS. DO NOT LEAVE SELECTION OF THE PRIMARY FIELD LEVEL PROTOCOL OPEN TO SELECTION BY THE CONTRACTOR. EACH PROTOCOL PROVIDES A SET OF FEATURES AND BENEFITS THAT MUST BE UNDERSTOOD AND CONSIDERED PRIOR TO SYSTEM DESIGN. CONTACT HONEYWELL WEBS FOR MORE INFORMATION ON PROTOCOL SELECTION.>

<PROTOCOLS OTHER THAN THE BASE PROTOCOL ARE CONSIDERED “THIRD PARTY” PROTOCOLS. THIS SECTION DEFINES THE REQUIREMENTS FOR INTEGRATING THIRD PARTY DEVICES. THE DETAILS PROVIDED MUST BE VERIFIED AND/OR MODIFIED AS REQUIRED TO MEET THE REQUIREMENTS OF THE PROJECT. CLOSELY COORDINATE THIS SECTION WITH THE DESIGN DRAWINGS TO IDENTIFY THE LOCATION OF THIRD PARTY INTERFACES/EQUIPMENT. DO NOT USE ANY OF THE INFORMATION WITHIN THIS SECTION WITHOUT VERIFYING ITS RELEVANCE TO THE PROJECT DESIGN>

• GENERAL

  • RELATED DOCUMENTS

    1. Drawings and general provisions of the Contract, including General and Supplementary Conditions and Division 01 Specification Sections, apply to this Section.
    2. Specifications throughout all Divisions of the Project Manual are directly applicable to this Section, and this Section is directly applicable to them.
    3. Integrated Automation System (IAS) General for definitions and abbreviations. Integrated Automation System Definitions and Abbreviations.

  • SUMMARY <MODIFY AS REQUIRED>

    1. Contractor shall provide interface equipment as needed to intelligently obtain required data points in the specified read-write manner for each piece of equipment or system as specified in the contract documents.
    2. Sections include:
       1. Interfacing with Manufacture Supplied communication cards or devices
       2. Protocols and Integration Methods

• REFERENCE STANDARDS

  1. The latest published edition of a reference shall be applicable to this Project unless identified by a specific edition date.
  2. All reference amendments adopted prior to the effective date of this Contract shall be applicable to this Project.
  3. All materials, installation and workmanship shall comply with the applicable requirements and standards addressed within all references.
• PRODUCTS

  • GENERAL

    1. All materials shall meet or exceed all applicable referenced standards, federal, state and local requirements, and conform to codes and ordinances of authorities having jurisdiction.

  • Equipment Manufacturer provided interfaces <MODIFY AS REQUIRED>

    1. The equipment manufacturer communication interface provided with the equipment shall enable access to data via an approved open standard.
    2. <Projects are typically bid on and awarded prior to selecting equipment manufacturers for all components. Therefore, details regarding the communication protocol supported by some equipment are not available until after the equipment manufacturer has been selected. Coordinate communication requirements with other specification sections and design including Mechanical and Electrical>. The contractor shall provide Niagara N4 interfaces to this equipment using the following protocols in the order of preference for which they are listed. <Modify order of protocols listed below based on preference>
       1. <LonTalk
       2. BACnet
       3. MODBUS
       4. TCP/IP
       5. Other approved open standard, OBIX, XML, OPC, etc.>
    3. The use of manufacturer interfaces shall be limited to equipment as identified on the drawings. <Coordinate with Design Drawings>
    4. The manufacturer interface shall be compatible with the Niagara framework open protocol drivers.
    5. Manufacturer Interfaces shall be read-write.
    6. Points exposed via the manufacturer interface shall match those available in the equipment’s native communication language. The contractor shall provide interfaces that meet the point lists included on the drawings. <Coordinate with Design Drawings>
    7. It shall be the Manufacturers responsibility to meet the sequence of operation as defined in Section 25 90 00

  • Third party interfaces

    1. Manufacturer third party interfaces shall be limited to equipment which the IAS contractor cannot or has not been contracted to control directly via DDC controllers. This equipment shall include the following examples. <Modify list to address project specific equipment that will be provided with third party interfaces>
       1. <CRAC units
       2. ATS
       3. Energy meters
       4. Lighting systems>

• EXECUTION

  • PREPARATION

    1. Examine areas and conditions under which equipment is to be installed. Do not proceed with Work until unsatisfactory conditions have been corrected in manner acceptable to the Owner.

  • INSTALLATION

    1. Installation shall meet or exceed all applicable Federal, state and local requirements, referenced standards and conform to codes and ordinances of authorities having jurisdiction.
    2. All installation shall be in accordance with manufacturer’s published recommendations.
    3. Provide all interface devices and software to provide an integrated system.
    4. Closely coordinate with the Owner, or designated representative, to establish IP addresses and communications necessary to assure proper operation of the IAS within the Owner’s WAN.
    5. Contractor shall be responsible for providing necessary networks, control wiring, and interface devices to communicate with third party equipment or systems.
    6. It shall be the Manufacturers responsibility to meet the sequence of operation as defined in Section 25 90 00.

  • Protocol integration <Modify as required, add additional protocols as required>

    1. MODBUS SYSTEM INTEGRATION <Verify use of MODBUS Protocol; coordinate the requirements with the IAS design drawings including selection of wiring type and transmission mode. Coordinate with other specification sections including Mechanical and Electrical.> <Refer to honeywell.com or MODBUS.org for more design information>

       • <The Network Area Controller shall support the integration of device data from MODBUS <RTU, ASCII, or TCP> control system devices. The connection to the MODBUS system shall be via an <RS-232, RS485, or Ethernet IP> as required by the device.
       • All scheduling, alarming, logging and global supervisory control functions, of the MODBUS system devices, shall be performed by the Network Area Controller.
       • The IAS contractor shall provide a MODBUS system communications driver. The equipment system vendor that provided the equipment utilizing MODBUS shall provide documentation of the system’s MODBUS interface and shall provide factory support at no charge during system commissioning>

    2. BACnet INTEGRATION <Modify as Required, delete if BACnet is the Base protocol> <Refer to buildingcontrols.honeywell.com or ASHRAE.org for more design information>

       1. <The Network Area Controller shall support the integration of device data from BACnet systems. The connection to the BACnet system shall be through a  NIAGARA N4 BACnet driver, as required by the system.
       2. The BACnet installation shall utilize MS/TP <IP> protocol, and MAC addresses, device instance numbers, and network numbers.
       3. All scheduling, alarming, logging and global supervisory control functions, of the BACnet system devices, shall be performed by the Network Area Controller.
       4. The IAS contractor shall provide a NIAGARA N4 BACnet communications driver.
       5. All devices shall be BACnet BTL certified.>

    3. LonWorks INTEGRATION <Modify as Required, delete if LonWorks is the Base protocol> <Refer to buildingcontrols.honeywell.com or LonMark.org for more design information>

       1. <The Network Area Controller shall support the integration of device data from LonWorks systems. The connection to the LonWorks system shall be through an associated driver, as required by the system.
       2. The LonWorks installation shall utilize LonTalk <LonTalk IP> protocol, and Neuron ID and Logical addresses. No more than 60 devices shall be installed on any subnet.
       3. Provide the required network variables in the library, included with the Graphical User Interface programming software, to support the integration of the existing system data into the CCS. Objects provided shall include at a minimum:
          • Read/Write Standard Network Variable Input – NVI
          • Read/Write Standard Network Variable Output – NVO
          • Write Standard Network Configuration Input – NCI
       4. All scheduling, alarming, logging and global supervisory control functions, of the LonWorks system devices, shall be performed by the Network Area Controller.
       5. The IAS contractor shall provide a NIAGARA N4 LonWorks communications driver.
       6. All devices shall be LonMark Certified.>
    4. <EXISTING> SYSTEM INTEGRATION <Modify as Required>
       1. The Network Area Controller shall support the integration of device data from the <existing> control system. The connection to the existing system shall be via the <existing> Network Area Controller network and the existing control system.
       2. The Owner, and/or the existing control system representative shall ensure that the <existing> system’s database is setup to make all data to be integrated into the IAS available. Any modifications to the existing system database must be coordinated with the Owner.
       3. All scheduling, alarming, logging and global supervisory control functions (demand limiting, etc.), of the <existing> system devices, shall be coordinated with the new system and performed by the Network Area Controller.