1、*USACE / NAVFAC / AFCESA / NASA UFGS-25 10 10 (November 2012)-Preparing Activity: USACE SupersedingUFGS-25 10 10 (May 2010)UNIFIED FACILITIES GUIDE SPECIFICATIONSReferences are in agreement with UMRL dated October 2012*SECTION TABLE OF CONTENTSDIVISION 25 - INTEGRATED AUTOMATIONSECTION 25 10 10UTILI
2、TY MONITORING AND CONTROL SYSTEM (UMCS) FRONT END AND INTEGRATION11/12PART 1 GENERAL1.1 SUMMARY1.1.1 System Requirements1.1.1.1 General System Requirements1.1.1.2 LonWorks Requirements1.1.1.3 BACnet Requirements1.1.1.4 Modbus Requirements1.1.1.5 OPC Requirements1.1.1.6 Niagara Framework Requirements
3、1.1.2 General Information Assurance Requirements1.1.3 Symbols, Definition and Abbreviations1.1.4 System Units and Accuracy1.1.5 Data Packages/Submitals Requirements1.2 REFERENCES1.3 DEFINITIONS1.3.1 Alarm Generation1.3.2 Alarm Handling1.3.3 Alarm Routing1.3.4 Application Generic Controller (AGC)(Lon
4、Works)1.3.5 Application Specific Controller (ASC)(LonWorks)1.3.6 BACnet (BACnet)1.3.7 BACnet Advanced Application Controller (B-AAC)(BACnet)1.3.8 BACnet Advanced Operator Workstation (B-AWS)(BACnet)1.3.9 BACnet Application Specific Controller (B-ASC)(BACnet)1.3.10 BACnet Building Controller (B-BC)(B
5、ACnet)1.3.11 BACnet Internetwork (BACnet)1.3.12 BACnet Interoperability Building Blocks (BIBBs) (BACnet)1.3.13 BACnet Operator Display (B-OD)(BACnet)1.3.14 BACnet Operator Workstation (B-OWS)(BACnet)1.3.15 BACnet Smart Actuator (B-SA)(BACnet)1.3.16 BACnet Smart Sensor (B-SS)(BACnet)1.3.17 BACnet Tes
6、ting Laboratories (BTL)(BACnet)1.3.18 BACnet Testing Laboratories (BTL) Listed (BACnet)1.3.19 Binary1.3.20 Binding (LonWorks)SECTION 25 10 10 Page 1Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-1.3.21 Broadcast1.3.22 Building Control Network (BCN)1
7、.3.23 Building Control System (BCS)1.3.24 Building Point of Connection (BPOC)1.3.25 Channel (LonWorks)1.3.26 Commandable (BACnet)1.3.27 Configuration Property (LonWorks)1.3.28 Control Logic Diagram1.3.29 Device Object (BACnet)1.3.30 Explicit Messaging (LonWorks)1.3.31 External Interface File (XIF) (
8、LonWorks)1.3.32 Facility Point Of Connection (FPOC)1.3.33 Field Control Network1.3.34 Field Control System (FCS)1.3.35 Fox Protocol (Niagara Framework)1.3.36 Functional Profile (LonWorks)1.3.37 Gateway1.3.38 General Purpose Programmable Controller (GPPC) (LonWorks)1.3.39 Internetwork (BACnet)1.3.40
9、JACE (Niagara Framework)1.3.41 LonMark Object (LonWorks)1.3.42 LNS Plug-in (LonWorks)1.3.43 LonMark (LonWorks)1.3.44 LonMark International (LonWorks)1.3.45 LonWorks (LonWorks)1.3.46 LonWorks Network Services (LNS) (LonWorks)1.3.47 LonWorks Network Services (LNS) Database (LonWorks)1.3.48 Modbus1.3.4
10、9 Master-Slave/Token Passing (MS/TP)(BACnet)1.3.50 Monitoring and Control (M R 2004) Office Machines and Supplies - Alphanumeric Machines - Keyboard ArrangementAMERICAN SOCIETY OF HEATING, REFRIGERATING AND AIR-CONDITIONING ENGINEERS (ASHRAE)ASHRAE 135 (2010; INT 1-3 2011; Addenda AD Errata 2012; IN
11、T 5 2012) BACnetA Data Communication Protocol for Building Automation and Control NetworksASHRAE FUN IP (2009; Errata 2010) Fundamentals Handbook, I-P EditionASHRAE FUN SI (2009; Errata 2010) Fundamentals Handbook, SI EditionCONSUMER ELECTRONICS ASSOCIATION (CEA)CEA-709.1-C (2010) Control Network Pr
12、otocol SpecificationCEA-709.3 (1999; R 2004) Free-Topology Twisted-Pair Channel SpecificationCEA-852-B (2010) Tunneling Component Network Protocols Over Internet Protocol ChannelsINSTITUTE OF ELECTRICAL AND ELECTRONICS ENGINEERS (IEEE)IEEE 1815 (2012) Electric Power Systems Communications-Distribute
13、d Network Protocol (DNP3)IEEE 754 (2008) Floating-Point Arithmetic - IEEE Computer SocietyIEEE 802.11 (2012; AA 2012; AE 2012) Information technology-Telecommunications and Information Exchange Between Systems Local and Metropolitan Area Networks-Specific Requirements Part 11: Wireless LAN Medium Ac
14、cess Control (MAC) and Physical Layer (PHY) SpecificationsSECTION 25 10 10 Page 14Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-IEEE C62.41 (1991; R 1995) Recommended Practice on Surge Voltages in Low-Voltage AC Power CircuitsIEEE Stds Dictionary (
15、2009) IEEE Standards Dictionary: Glossary of Terms Version 3.4LonMark SNVT List (2003) LonMark SNVT Master List; Version 113LonMark XIF Guide (2001) LonMark External Interface File Reference Guide; Revision 4.402MODBUS ORGANIZATION, INC (MODBUS)Modbus (2006) Modbus Application Protocol Specification
16、; Version 1.1b and Modbus Messaging on TCP/IP Implementation Guide; Version V1.0bNATIONAL ELECTRICAL MANUFACTURERS ASSOCIATION (NEMA)NEMA 250 (2008) Enclosures for Electrical Equipment (1000 Volts Maximum)NATIONAL FIRE PROTECTION ASSOCIATION (NFPA)NFPA 262 (2011) Standard method of Test for Flame Tr
17、avel and Smoke of Wires and Cables for Use in Air-Handling SpacesNFPA 70 (2011; Errata 2 2012) National Electrical CodeOPC FOUNDATION (OPC)OPC DA (2002) OPC Data Access (DA) Specification; Version 2.05aTELECOMMUNICATIONS INDUSTRY ASSOCIATION (TIA)TIA J-STD-607 (2002a) Commercial Building Grounding (
18、Earthing) and Bonding Requirements for SECTION 25 10 10 Page 15Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TelecommunicationsTIA-568-C.1 (2009; Add 2 2011; Add 1 2012) Commercial Building Telecommunications Cabling StandardTIA/EIA-606 (2002a; Err
19、ata 2007; R 2007; Adm 1 2008) Administration Standard for the Telecommunications InfrastructureTHE INTERNET ENGINEERING TASK FORCE (IETF)IETF RFC 4361 (2006) Node-specific Client Identifiers for Dynamic Host Configuration Protocol Version Four (DHCPv4)IETF RFC 5246 (2008) The Transport Layer Securit
20、y (TLS) Protocol Version 1.2IETF RFC 5545 (2009) Internet Calendaring and Scheduling Core Object Specification (iCalendar)RFC 821 (2001) Simple Mail Transfer Protocol (SMTP)TRIDIUM, INC (TRIDIUM)Niagara Framework (2012) NiagaraAX Users GuideTridium Open NiCS (2005) Understanding the NiagaraAX Compat
21、ibility Statement (NiCS)U.S. AIR FORCE (USAF)AF ETL 11-1 (2011) Civil Engineer Industrial Control System Information Assurance ComplianceU.S. ARMY (DA)DA AR 25-2 (2007; RAR 2009) Information AssuranceU.S. FEDERAL COMMUNICATIONS COMMISSION (FCC)FCC EMC (2002) FCC Electromagnetic Compliance Requiremen
22、tsFCC Part 15 Radio Frequency Devices (47 CFR 15)UNDERWRITERS LABORATORIES (UL)UL 1778 (2005; Reprint Oct 2011) Uninterruptible Power SystemsUL 60950 (2000; Reprint Oct 2007) Safety of Information Technology Equipment1.3 DEFINITIONSThe following list of definitions may contain terms not found elsewh
23、ere in this Section but are included here for completeness. Some terms are SECTION 25 10 10 Page 16Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-followed with a protocol reference in parenthesis (for example: (BACnet) indicating to which protocol t
24、he term and definition applies.1.3.1 Alarm GenerationThe process of comparing a point value (thepoint being alarmed) with a pre-defined alarm condition (e.g. a High Limit) and performing some action based on the result ofthe comparison.1.3.2 Alarm Handlingsee Alarm Routing1.3.3 Alarm RoutingAlarm ro
25、uting is M hand-held terminals or other very simple user interfaces.1.3.14 BACnet Operator Workstation (B-OWS)(BACnet)Monitoring and Control (M it is intended for specific applications.SECTION 25 10 10 Page 18Provided by IHSNot for ResaleNo reproduction or networking permitted without license from I
26、HS-,-,-1.3.16 BACnet Smart Sensor (B-SS)(BACnet)A hardware device BTL Listed as a B-SS. A simple sensing device with very limited resources.1.3.17 BACnet Testing Laboratories (BTL)(BACnet)Established by BACnet International to support compliance testing and interoperability testing activities and co
27、nsists of BTL Manager and the BTL Working Group (BTL-WG). BTL also publishes Implementation Guidelines.1.3.18 BACnet Testing Laboratories (BTL) Listed (BACnet)A device that has been certified by BACnet Testing Laboratory. Devices may be certified to a specific device profile, in which case the certi
28、fication indicates that the device supports the required capabilities for that profile, or may be certified as “other“.1.3.19 BinaryA two-state system or signal; for example one where an “ON“ condition is represented by a high signal level and an “OFF“ condition is represented by a low signal level.
29、 Digital is sometimes used interchangeably with binary.1.3.20 Binding (LonWorks)The act of establishing communications between CEA-709.1-C devices by associating the output of a device to the input of another so that information is automatically (and regularly) sent without being requested by the re
30、cipient.1.3.21 BroadcastUnlike most messages, which are intended for a specific recipient device, a broadcast message is intended for all devices on the network.1.3.22 Building Control Network (BCN)The network used by the Building Control System. Typically the BCN is a BACnet ASHRAE 135 or LonWorks
31、CEA-709.1-C network installed by the building control system contractor.1.3.23 Building Control System (BCS)One type of Field Control System. A control system for building electrical and mechanical systems, typically HVAC (including central plants) and lighting. A BCS generally uses Direct Digital C
32、ontrol (DDC) Hardware and generally does NOT include its own local front end.1.3.24 Building Point of Connection (BPOC)A FPOC for a Building Control System. (This term is being phased out of use in preference for FPOC but is still used in some specifications and criteria.)1.3.25 Channel (LonWorks)A
33、portion of the control network consisting of one or more segments SECTION 25 10 10 Page 19Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-connected by repeaters. Channels are separated by routers. The device quantity limitation is dependent on the to
34、pology/media and device type. For example, a TP/FT-10 network with locally powered devices is limited to 128 devices per channel.1.3.26 Commandable (BACnet)A point (Object) is commandable if its Present_Value Property is writable and it supports the optional Priority_Array Property. This functionali
35、ty is useful for Overrides.1.3.27 Configuration Property (LonWorks)Controller parameter used by the application which is usually set during installation/testing and seldom changed. For example, the P and I settings of a P-I control loop. Also see Standard Configuration Property Type (SCPT)1.3.28 Con
36、trol Logic DiagramA graphical representation of control logic for multiple processes that make up a system.1.3.29 Device Object (BACnet)Every BACnet device requires one Device Object, whose properties represent the network visible properties of that device. Every Device Object requires a unique Obje
37、ct_Identifier number on the BACnet internetwork. This number is often referred to as the device instance or device ID.1.3.30 Explicit Messaging (LonWorks)A non-standard and often vendor (application) specific method of communication between devices.1.3.31 External Interface File (XIF) (LonWorks)A fi
38、le which documents a devices external interface, specifically the number and types of LonMark objects, the number, types, directions, and connection attributes of network variables, and the number of message tags.1.3.32 Facility Point Of Connection (FPOC)The FPOC is the point of connection between t
39、he UMCS IP Network and the field control network (either an IP network, a non-IP network, or both). The hardware at this location which provides the connection is generally one of a control protocol router, a control protocol gateway, or an IT device such as a switch, IP router, or firewall.In gener
40、al, the term “FPOC Location“ means the place where this connection occurs, and “FPOC Hardware“ means the device that provides the connection. Sometimes the term “FPOC“ is used to mean either and its actual meaning (i.e. location or hardware) is determined by the context in which it is used.1.3.33 Fi
41、eld Control NetworkThe network used by a field control system.SECTION 25 10 10 Page 20Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-1.3.34 Field Control System (FCS)A building control system or utility control system.1.3.35 Fox Protocol (Niagara Fr
42、amework)The protocol used for communication between components in the Niagara Framework. By default, Fox uses TCP port 19111.3.36 Functional Profile (LonWorks)A standard description, defined by LonMark International, of a LonMark Object used to classify and certify devices.1.3.37 GatewayA device tha
43、t translates from one protocol to another. Devices that change only the transport mechanism of the protocol - “translating“ from LonWorks over TP/FT-10 to LonWorks over IP for example - are not gateways as the underlying protocol (data format) does not change. Gateways are also called Communications
44、 Bridges or Protocol Translators.1.3.38 General Purpose Programmable Controller (GPPC) (LonWorks)Unlike an ASC or AGC, a GPPC is not furnished with a fixed application program and does not have a fixed ProgramID or XIF file. A GPPC can be (re-)programmed, usually using vendor-supplied software. When
45、 a change to the program affects the external interface (and the XIF file) the ProgramID will change.1.3.39 Internetwork (BACnet)See BACnet Internetwork.1.3.40 JACE (Niagara Framework)Java Application Control Engine. See Niagara Framework Supervisory Gateway1.3.41 LonMark Object (LonWorks)A collecti
46、on of network variables, configuration properties, and associated behavior defined by LonMark International and described by a Functional Profile. It defines how information is exchanged between devices on a network (inputs from and outputs to the network).1.3.42 LNS Plug-in (LonWorks)Software which
47、 runs in an LNS compatible software tool, typically a network configuration tool. Device configuration plug-ins provide a user friendly method to edit a devices configuration properties.1.3.43 LonMark (LonWorks)See LonMark International. Also, a certification issued by LonMark International to CEA-7
48、09.1-C devices.1.3.44 LonMark International (LonWorks)Standards committee consisting of independent product developers, system SECTION 25 10 10 Page 21Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-integrators and end users dedicated to determining and maintaining the interoperability guidelines for LonWorks. Maintain
