CEN/TC 247/WG 4 - Open System Data Transmission

This document specifies control applications and function blocks focusing on but not limited to lighting, solar protection and HVAC applications.
It describes how energy performance, comfort, and operational requirements of buildings are translated into functional specifications for integrated plant and room control.

This document provides mechanisms through which various vendors of building automation, control, and building management systems may exchange information in a standardized way.
This document provides specifications for the Application Elements of Control Network Protocol packets as follows:
-   definitions of standardized packet (network-variable) data types;
-   definitions of device-interface files;
-   definitions of standardized configuration-property types;
-   definitions of standardized enumeration types;
-   definitions of standardized functional profiles;
-   definition of the standardized method of file transfer between devices.
The purpose of this document is to ensure interoperability between various CNP implementations. This document contains all the information necessary to read and interpret the format of data and control information that is used by EN 14908 5. It also defines the device interface for a device as specified, which is necessary to exchange data between various devices from different manufacturers.

The purpose of this document is to define data communication services and protocols for computer equipment used for monitoring and control of HVAC&R and other building systems and to define, in addition, an abstract, object-oriented representation of information communicated between such equipment, thereby facilitating the application and use of digital control technology in buildings.

This document specifies a communication protocol for networked control systems. The protocol provides peer-to-peer communication for networked control using web-services. This document describes services in layer 1 and layer 2.
The layer 1 (physical layer) specification describes the MAC sub-layer interface to the physical layer. The layer 2 (data link layer), as described in EN 14908 1, is integrated in UDP/IP communication using IPv4 and IPv6 protocols.

This document specifies an adaptation layer for the control network protocol (CNP), as described in EN 14908 1 to utilize wireless communication network. This document defines the services of the wireless communication provided to CNP layer for delivering data and commands towards and from sensors, actuators, etc. which are wirelessly connected as part of the EN 14908 1 network.
In addition, this document defines the requirements for the radio communication applicable for CNP layer operation.
For the radio communication different frequency bands can be utilized. Annex A defines requirement for operation in different frequency bands.

This document specifies, as for Home or Building Electronic Systems (HBES) for the domain of Building Automation and Control System Application and Building Management (BACS), common rules for a class of multi-application bus systems where the functions are decentralised and linked through a common communication process. This document specifies the basic requirements for products and systems. The requirements can also apply to the distributed functions of any equipment connected in a home or building control system if no specific standard exists for this equipment or system.
Due to its reference to the EN 50090 series, this document establishes requirements for the BACS area in relation to Architecture and Hardware and Application and Communication of systems based on HBES amongst other areas, and specifies the basic requirements for interoperability (between products and systems).

This standard provides a comprehensive set of procedures for verifying the correct implementation of each capability claimed on a BACnet PICS including:
(a)    support of each claimed BACnet service, either as an initiator, executor, or both,
(b)    support of each claimed BACnet object-type, including both required properties and each claimed optional property,
(c)    support of the BACnet network layer protocol,
(d)    support of each claimed data link option, and
(e)    support of all claimed special functionality.

This document defines the integration of KNX protocol implementations on top of Internet protocol (IP) networks, called KNXnet/IP. It describes a standard protocol for KNX devices connected to an IP network, called KNXnet/IP devices. The IP network acts as a fast (compared to KNX twisted pair transmission speed) backbone in KNX installations.

This document specifies a communication protocol for networked control systems. The protocol provides peer-to-peer communication for networked control using web-services. The document describes services in layer 2 and layer 3.
The layer 2 (data link layer) specification also describes the MAC sub-layer interface to the physical layer. The physical layer provides a choice of transmission media. The layer 3 (network layer), as described in EN 14908 1, is integrated in UDP/IP communication using IPv4 and IPv6 protocols.

This European Standard specifies the transporting of the Control Network Protocol (CNP) packets for commercial Building Automation, Controls and Building Management over Internet Protocol (IP) networks using a tunnelling mechanism wherein the CNP packets are encapsulated within IP packets. It applies to both CNP nodes and CNP routers.
The purpose of this European Standard is to ensure interoperability between various CNP devices that wish to use IP networks to communicate using the CNP protocol.
The main body of this European Standard is independent of the CNP protocol being transported over the IP network. The reader is directed to Annex A and Annex B for the normative and informative, respectively, aspects of this specification that are specific to EN 14908-1.
Figure 1 shows a possible configuration of such CNP devices and networks connected to an IP network.
Figure 1 depicts two types of CNP devices: CNP nodes and CNP routers. It should be noted that the routers shown can route packets between typical CNP channels (such as twisted pair or power line) and an IP channel or it can route CNP packets between two IP channels. In this European Standard the IP channel will be defined in such a way to allow it to be used like any other CNP channel.
In the above diagram, the IP network can be considered to be one or more IP channels. This European Standard covers only how CNP packets are transported over IP channels. It does not cover how CNP packets are routed between standard CNP channels and IP channels. This specification is not intended to cover the lower layers (physical, MAC and link layers) of either standard CNP or IP channels.

This European Standard applies to a communication protocol for networked control systems in commercial Building Automation, Controls and Building Management. The protocol provides peer-to-peer communication for networked control and is suitable for implementing both peer-to-peer and master-slave control strategies. This specification describes services in layers 2 to 7. In the layer 2 (data link layer) specification, it also describes the MAC sub-layer interface to the physical layer. The physical layer provides a choice of transmission media. The interface described in this specification supports multiple transmission media at the physical layer. In the layer 7 specification, it includes a description of the types of messages used by applications to exchange application and network management data.

This European Standard specifies the control network protocol (CNP) free-topology twisted-pair channel for networked control systems in commercial Building Automation, Controls and Building Management and is used in conjunction with EN 14908-1:2014. The channel supports communication at 78,125 kbit/s between multiple nodes, each of which consists of a transceiver, a protocol processor, an application processor, a power supply, and application electronics.
This European Standard covers the complete physical layer (OSI Layer 1), including the interface to the Media Access Control (MAC) sub-layer and the interface to the medium. Parameters that are controlled by other layers but control the operation of the physical layer are also specified.

This European Standard specifies all the information necessary to facilitate the exchange of data and control information over the power line medium for networked control systems in commercial Building Automation, Controls and Building Management.
This European Standard establishes a minimal set of rules for compliance. It does not rule out extended services to be provided, given that the rules are adhered to within the system. It is the intention of the standard to permit extended services (defined by users) to coexist.
Certain aspects of this standard are defined in other documents. These documents are referenced where relevant. In the case where a referenced standard conflicts with this European Standard, this part of EN 14908 will prevail.

ISO 16484-3:2005 specifies the requirements for the overall functionality and engineering services to achieve building automation and control systems. It defines terms, which shall be used for specifications and it gives guidelines for the functional documentation of project/application specific systems. It provides a sample template for documentation of plant/application specific functions, called BACS points list.
The informative function block examples explain a method to display the referenced functions in system documentation; they do not standardize the method for programming functions and applications.
ISO 16484-3:2005 covers requirements and definitions regarding BACS and application software, generic functions for plant/project specific applications and engineering functions for building controls and operations. It provides communication functions for the integration of other dedicated special system processes.
ISO 16484-3:2005 defines a method for specifying the procurement specifications containing all essential elements required for the operational functioning of a BACS. The successful installation and operation of a BACS requires that its procurement be based on a complete and accurate functional specification.

ISO 16484-2:2004 specifies the requirements for the hardware to perform the tasks within a building automation and control system (BACS). It provides the terms, definitions and abbreviations for the understanding of ISO 16484-2 and ISO 16484-3. ISO 16484-2:2004 relates only to physical items/devices, i.e. devices for management functions, operator stations and other human system interface devices; controllers, automation stations and application specific controllers; field devices and their interfaces; cabling and interconnection of devices; engineering and commissioning tools.
ISO 16484-2:2004 shows a generic system model to which all different types of BACS and their interconnections (BACS network) can fit. A graphical concept of the BACS network in terms of LAN topology will be provided in ISO 16484-5.

This document specifies control applications and function blocks focusing on but not limited to lighting, solar protection, and HVAC applications.
It describes how energy performance, comfort, and operational requirements of buildings are translated into functional specifications for integrated plant and room control.

This document specifies an open and extensible standard for residential, commercial, and industrial control and automation applications using the EN 14908-1 control network protocol and related protocols (EN 14908-2 to EN 14908-9) to provision and manage IoT devices, to access and update data from the devices, and to aggregate data from diverse devices and protocols for delivery to external applications and services.
The  web services as specified in this document are implemented on a central gateway or edge server that communicates with multiple sensor, actuator, and controller edge devices using one or more edge protocols such as EN 14908-1, and also interfaces with one or more enterprise and cloud services or applications.

ISO 16484-1:2010 specifies guiding principles for project design and implementation and for the integration of other systems into the building automation and control systems (BACS).
ISO 16484-1:2010 specifies the phases required for the BACS project, including:
design (determination of project requirements and production of design documents including technical specifications),
engineering (detailed function and hardware design),
installation (installing and commissioning of the BACS), and
completion (handover, acceptance and project finalization).
ISO 16484-1:2010 also specifies the requirements for as-built documentation and training.
ISO 16484-1:2010 is not applicable to operation and maintenance, nor is it applicable to retro or continuous commissioning, including a commissioning authority.

This European Standard provides mechanisms through which various vendors of building automation, control, and building management systems may exchange information in a standardized way.
This document provides specifications for the Application Elements of Control Network Protocol packets as follows:
-   definitions of standardized packet (network-variable) data types;
-   definitions of device-interface files;
-   definitions of standardized configuration-property types;
-   definitions of standardized enumeration types;
-   definitions of standardized functional profiles;
-   definition of the standardized method of file transfer between devices.
The purpose of this specification is to ensure interoperability between various CNP implementations. This document contains all the information necessary to read and interpret the format of data and control information that is used by EN 14908-5. It also defines the device interface for a device as specified, which is necessary to exchange data between various devices from different manufacturers.

The LONWORKS communication system is widely used in building automation systems for field-level and application-level functions for residential and non-residential controls in lighting, sun protection, HVAC, energy management and security applications. The BACnet communication system as well is also used in building automation systems for management-level and application-level functions. This technical specification defines the methods for combining BACnet networks with LONWORKS networks, and standardizes the interface between BACnet and LONWORKS systems.

The purpose of ISO 16484-5:2017 is to define data communication services and protocols for computer equipment used for monitoring and control of HVAC&R and other building systems and to define, in addition, an abstract, object-oriented representation of information communicated between such equipment, thereby facilitating the application and use of digital control technology in buildings.

This European Standard specifies, as for Home or Building Electronic Systems (HBES) for the domain of Building Automation and Control System Application and Building Management (BACS), common rules for a class of multi-application bus systems where the functions are decentralised and linked through a common communication process. This European Standard sets the basic requirements for products and systems. The requirements may also apply to the distributed functions of any equipment connected in a home or building control system if no specific standard exists for this equipment or system.
Due to its reference to the EN 50090 series, this European Standard sets requirements for the BACS area in relation to Architecture and Hardware and Application and Communication of systems based on HBES amongst other areas, and specifies the basic requirements for interoperability (between products and systems).
Aspects such as environmental conditions/external influences, electrical safety, EMC, etc. also used to be covered by EN 50090-2-2, which will be superseded by the now available EN 50491 series. The latter European Standards series was jointly developed by CENELEC/TC 205 and CEN/TC 247 and will in the future also include aspects like functional safety in normal use (now contained in the EN 50090-2-3). The EN 50491 series applies, together with the relevant product standard for devices, if applicable.

ISO 16484-6:2014 defines a standard method for verifying that an implementation of the BACnet protocol provides each capability claimed in its Protocol Implementation Conformance Statement (PICS) in conformance with the BACnet standard.
ISO 16484-6:2014 provides a comprehensive set of procedures for verifying the correct implementation of each capability claimed on a BACnet PICS, including support of each claimed BACnet service, either as an initiator, executor, or both, support of each claimed BACnet object-type, including both required properties and each claimed optional property,support of the BACnet network layer protocol,support of each claimed data link option, andsupport of all claimed special functionality.

This European Standard defines the integration of KNX protocol implementations on top of Internet Protocol (IP) networks, called KNXnet/IP. It describes a standard protocol for KNX devices connected to an IP network, called KNXnet/IP devices. The IP network acts as a fast (compared to KNX transmission speed) backbone in KNX installations.
Widespread deployment of data networks using the Internet Protocol (IP) presents an opportunity to expand building control communication beyond the local KNX control bus, providing:
-   remote configuration;
-   remote operation (including control and annunciation);
-   fast interface from LAN to KNX and vice versa;
-   WAN connection between KNX systems (where an installed KNX system is at least one line).
A KNXnet/IP system contains at least these elements:
-   one EIB line with up to 64 (255) EIB devices;
OR
one KNX segment (KNX-TP1, KNX-TP0, KNX-RF, KNX-PL110, KNX-PL132);
-   a KNX-to-IP network connection device (called KNXnet/IP server);
and typically additional
-   software for remote functions residing on e.g. a workstation (may be data base application, BACnet Building Management System, browser, etc.).
Figure 1 shows a typical scenario where a KNXnet/IP client (e.g. running ETS) accesses multiple KNX installed systems or KNX subnetworks via an IP network. The KNXnet/IP client may access one or more KNXnet/IP servers at a time. For subnetwork, routing server-to-server communication is possible.

This European Standard provides mechanisms through which various vendors of building automation, control, and building management systems may exchange information in a standardised way.
This document provides specifications for the Application Elements of Control Network Protocol packets as follows:
-   definitions of standardized packet (network-variable) data types;
-   definitions of device-interface files;
-   definitions of standardized configuration-property types;
-   definitions of standardized enumeration types;
-   definitions of standardized functional profiles;
-   definition of the standardized method of file transfer between devices.
The purpose of this specification is to insure interoperability between various CNP implementations. This document contains all the information necessary to read and interpret the format of data and control information that is used by EN 14908-5. It also defines the device interface for a device as specified, which is necessary to exchange data between various devices from different manufacturers.

This European Standard specifies the transporting of Control Network Protocol (CNP) packets over Internet Protocol (IP) networks using a tunnelling mechanism wherein the CNP packets are encapsulated within the IP packets. It applies to both CNP nodes and CNP routers.
The purpose of this European Standard is to insure interoperability between various CNP devices that wish to use IP networks to communicate using the CNP protocol.
The main body of this European Standard is independent of the CNP protocol being transported over the IP network. The reader is directed to Annex A and Annex B for the normative and informative, respectively, aspects of this specification that are specific to EN 14908-1.
Figure 1 shows a possible configuration of such CNP devices and networks connected to an IP network.
Figure 1  Typical CNP/IP application
Figure 1 depicts two types of CNP devices: CNP nodes and CNP routers. It should be noted that the routers shown can route packets between typical CNP channels (such as twisted pair or power line) and an IP channel or it can route CNP packets between two IP channels. In this European Standard the IP channel will be defined in such a way to allow it to be used like any other CNP channel.
In the above diagram the IP network can be considered to be one or more IP channels. This European Standard covers only how CNP packets are transported over IP channels. It does not cover how CNP packets are routed between standard CNP channels and IP channels. This specification is not intended to cover the lower layers (physical, MAC and link layers) of either standard CNP or IP channels.

This European Standard specifies all the information necessary to facilitate the exchange of data and control information over the power line medium.
This European Standard establishes a minimal set of rules for compliance. It does not rule out extended services to be provided, given that the rules are adhered to within the system. It is the intention of the standard to permit extended services (defined by users) to coexist.
Certain aspects of the standard are defined in other documents. These documents are referenced where relevant. In the case where a referenced standard conflicts with this European Standard, this European Standard will prevail.

This specification applies to a communication protocol for networked control systems. The protocol provides peer-to-peer communication for networked control and is suitable for implementing both peer-to-peer and master-slave control strategies. This specification describes services in layers 2 - 7. In the layer 2 (data link layer) specification, it also describes the MAC sub-layer interface to the physical layer. The physical layer provides a choice of transmission media. The interface described in this specification supports multiple transmission media at the physical layer. In the layer 7 specification, it includes a description of the types of messages used by applications to exchange application and network management data.

This European Standard specifies the control network protocol (CNP) free-topology twisted-pair channel and serves as a companion European Standard to prEN14908-1. The channel supports communication at 78.125 kbps between multiple nodes, each of which consists of a transceiver, a protocol processor, an application processor, a power supply, and application electronics.
This European Standard covers the complete physical layer (OSI Layer 1), including the interface to the Media Access Control (MAC) sub-layer and the interface to the medium. Parameters that are controlled by other layers but control the operation of the physical layer are also specified.

This specification defines the integration of KNX protocol implementations on top of Internet Protocol (IP) networks, called KNXnet/IP. It describes a standard protocol for KNX devices connected to an IP network, called KNXnet/IP devices. The IP network acts as a fast (compared to KNX transmission speed) backbone in KNX installations.
   Widespread deployment of data networks using the Internet Protocol (IP) presents an opportunity to expand building control communication beyond the local KNX control bus providing:
   Remote configuration
   Remote operation (including control and annunciation)
   Fast interface from LAN to KNX and vice versa
   WAN connection between KNX systems (where an installed KNX system is at least one line)
   A KNXnet/IP system contains at least these elements:
   one EIB line with up to 64 (255) EIB devices
OR
one KNX segment (KNX-TP1, KNX-TP0, KNX-RF, KNX-PL110, KNX-PL132),
   a KNX-to-IP network connection device
(called KNXnet/IP server),
and typically additional
   software for remote functions residing on e.g. a workstation
(may be iETS, data base application, BACnet Building Management System, browser, ...).
Figure 1 shows a typical scenario where a KNXnet/IP client (e.g. running ETS) accesses multiple KNX installed systems or KNX subnetworks via an IP network. The KNXnet/IP client may access one or more KNXnet/IP servers at a time. For subnetwork routing server-to-server communication is possible.

This standard shall be applied to conformance testing of protocol implementations, in particular for the testing of conformance of the implementations to the protocol standards or prestandards for system neutral data communication in HVAC systems. This standard may be applied by any test realizer whether the test results will be used in a certification system (which is not within the scope of this standard).

This protocol provides a comprehensive set of messages for conveying encoded binary, analog, and alphanumeric data between devices including, but notlimited to: (a) hardware binary input and output values, (b) hardware analog input and output values, (c) sofware binary and analog values, (d) text string values, (e) schedule information, (f) alarm and event information, (g) files, and (h) control logic.

This prestandard defines FLN-objects and FLN-services to be used on a field level for system neutral exchange of data for HVAC applications. This prestandard defines the semantics of the objects and the abstract services applicable to them and it defines an optional syntax to be used to exchange data with communication front-end unit. The syntax of the object data on the underlying communication (bus) protocol is not within the scope of this prestandard.

This European Prestandard defines a system neutral data communication method for use at the automation level in heating, ventilating and air conditioning and related building management applications.

This European Prestandard defines a system neutral data communication mechanism for use at the automation level in heating, ventilating, air conditioning and related building management applications.

This European Prestandard defines a system neutral data communication mechanism for use at the field level in heating, ventilating, air-conditioning and relate  building management applications.