The ultimate aim of EEBUS is to develop a standard that is universally applicable. For that reason, the data model is designed to be compatible with a broad range of protocols and transmission channels.
A standard based on diversity
Whenever people talk about the new language for energy, EEBUS is often mentioned. However, the underlying specification is known as SPINE (Smart Premises Interoperable Neutral-message Exchange). The name makes it clear that EEBUS is not a bus system or anything similar.
SPINE describes scenarios (use cases) in the form of data sets that are compatible with a wide range of technological platforms, communication and transmission channels – from WLAN or Thread to KNX, which is widely used in building technology.
Usable in a
SPINE can be precisely classified by means of the Smart Grid Architecture Model (SGAM) by the Smart Grid Coordination Group as well as through the Home & Building Architecture Model HBAM (DKE) derived from it.
Two-part set-up for resources and protocols
SPINE information comprises resource and protocol data, which are described in two separate specifications. As a whole, SPINE has a highly modular design and includes metadata (e.g. depending on the type of device and the variety of functions).
The resources only relate to the actual functions of the devices. They are designed for easy integration in other eco-systems such as OCF (Open Connectivity Foundation). At resource level, the transitions to other applications, such as entertainment or an existing building management system, are therefore also easy to implement. The EEBus initiative is working continually on integrating and interlinking with other organisations.
The working groups identify cross-product application scenarios and define the applications of the SPINE resources for interoperable processes.
The protocol level, which is independent of the resources, describes how a network of SPINE-capable devices can be set up, separate from the transmission channel. The modular set-up also allows the use of other protocols such as CoAP, therefore enabling broader interoperability.