P2030 Smart Grid Standard Text Submittal Form
This text is intended as proposed text for consideration of the P2030 Writing Group to the P2030 Draft Guide for Smart Grid Interoperability of Energy Technology and Information Technology Operation with the Electric Power System (EPS), and End-Use Applications and Loads.
SUBMITTAL INFORMATION
date SUBMITTED: 2/23/2010
SUBMITTED BY: Michael Loiacono, Hans-Joachim Langels, and Justinian Rosca
Affiliation: Siemens
Email:
TEXT PLACEMENT INFORMATION
In the P2030 Outline Draft (Mentor DOC#27-2010):
There are several clauses that could accommodate the proposed text:
Clause #: 7
Clause Heading: Interoperability characteristics, design criteria, operations, and end-use applications
Clause #: 8
Clause Heading: Interoperability configurations and topologies
Clause #: 11.6.5.1/2
Clause Heading: Communication Systems Interoperability/Load Management /HAN/BAN
Clause #: 13
Clause Heading: Smart grid interoperability and legacy technologies coordination
PROPOSED TEXT
The last-mile ecosystem of the smart grid is rich with potential applications for home/building automation and control. Whether in a single-family house or in an office complex, the demand for comfort and versatility in the management of air-conditioning, lighting and access control systems is growing. At the same time, the efficient use of energy is becoming increasingly important. More convenience and safety coupled with lower energy consumption can however only be achieved by intelligent control and monitoring of all products involved. This however implies more wiring/infrastructure connecting the sensors and actuators to the control and monitoring centers, and overall, a high degree of complexity. Such a mass of wiring and complexity in turn means higher design and installation effort, increased fire risk and soaring costs.
In order to ensure interoperability and reduce the complexity of such building management components, it is beneficial to employ a system that does away with isolated devices and ensures that all components communicate via one common language.
KNX is a distributed controls system specifically designed for Home and Building Controls applications like lighting, heating-ventilation-air-conditioning (HVAC), security, and energy management. Designed for simple installation and configuration by electrical installers, KNX features Twisted Pair, Powerline, and RF media, as well as any additional medium that is capable of carrying UDP/IP. Its OSI-based protocol provides powerful management and configuration mechanisms. KNX is approved internationally as ISO/IEC 14543-3; in Europe as CENELEC EN50090 and CEN EN 13321-1,2; in China as GB/Z 20965; and in the USA as ANSI/ASHRAE 135, ISO 16484-5 (mapping to BACnet). Also, KNX interfaces with ISO/IEC 29341 (“UPnP”), which is the basis for DLNA.
KNX is an open system, supported by a common, vendor-independent software tool called Engineering Tool Software (ETS). ETS is used for PC-based project design, configuration, diagnostics and maintenance. ETS accepts any KNX manufacturer’s product libraries. Based on a flexible topology with low-cost routers, a single KNX system may contain many thousands of nodes. The KNX communication architecture is depicted in Figure 1.
Figure 1. KNX Communication Architecture.
Distributed applications on KNX deal with energy, light, load, temperature and climate, access control and security, control of audio and video services, etc.; they are modeled via datapoints (up to 32,000 per installation) grouped in functional blocks, also called object interworking standards, and take advantage of KNX’s simple and bandwidth-efficient multicast “group addressing”. The system supports this by specifying datapoint types including Boolean, (Un)Signed Integer, Float, Relative Control (%), String etc., to transfer physical and control values (temperature, position, brightness, etc.) between sensors, actuators and controllers on the KNX home or field bus network. The KNX standard is continually updated to accommodate changing market needs.
A Certification program, run by the neutral KNX Association, ensures full compliance in terms of protocol and run-time interworking and compatibility of all products bearing the KNX trademark logo.
KNX is being used as a field level bus providing basic building controls functions in building automation systems. Gateways and interfaces exist for industry leading building management systems. The role of KNX in different building management applications is depicted in Figure 2.
Figure 2. Role of KNX in Home and Building Controls Systems.
In homes, KNX provides a complete set of components for home control systems. In small and medium sized buildings, KNX takes on basic building automation functions, whereas in large buildings KNX is applied as a field bus serving the building automation control systems.
BACnet plays a leading role in open Building Automation Control Systems. KNX as an open standard for field level controls is designed to closely interact with BACnet systems. Mapping KNX object interworking standards to BACnet objects is part of the BACnet standard (ISO 16484-5, Annex H.5) as approved by ANSI/ASHRAE 135 and the international standards committee ISO TC205. This approach combines the strengths of both protocols in an ideal fashion.
3