Devices communicate over dedicated sensorial networks • These networks connect devices (sensors and actuators) enabling control over building equipment • Control logic of those devices is embedded into their firmware and distributed into a system that is typically decentralized Daylight Side Actuation (KNX) Sensors (Modbus) Actuation (BACnet) Actuation (EG2)
(Modbus) Actuation (BACnet) Actuation (EG2) Auto open blinds during day time (one time setup by technician) K N X E G 2 Auto Dimming Luminaries Energy-‐Efficiency Technique 1 Energy-‐Efficiency Technique 2
(Modbus) Actuation (BACnet) Actuation (EG2) Auto open blinds during day time (one time setup by technician) K N X E G 2 Auto Dimming Luminaries Energy-‐Efficiency Technique 1 Energy-‐Efficiency Technique 2 EE Techniques is commissioned into distributed and embedded hardware controllers, over a dedicated network
(Modbus) Actuation (BACnet) Actuation (EG2) Auto open blinds during day time (one time setup by technician) K N X E G 2 Auto Dimming Luminaries 1. Most automaAon protocols are open, but their commissioning instrucAons are closed to their vendors
(Modbus) Actuation (BACnet) Actuation (EG2) Auto open blinds during day time (one time setup by technician) K N X E G 2 Auto Dimming Luminaries 1. Most automaAon protocols are open, but their commissioning instrucAons are closed to their vendors 2. EE techniques are installed on hardware controllers (like a BIOS), therefore hard to update and require also vendor intervenAon
protocols are open, but their commissioning instrucAons are closed to their vendors 2. EE techniques are installed on hardware controllers (like a BIOS), therefore hard to update and require also vendor intervenAon 3. In presence of mulAple BASs, given their heterogeneity the same techniques must be programmed repeatedly Actuation (KNX) Sensors (Modbus) Actuation (BACnet) Actuation (EG2) Auto open blinds during day time (one time setup by technician) K N X E G 2 Auto Dimming Luminaries
(Modbus) Actuation (BACnet) Actuation (EG2) Auto open blinds during day time (one time setup by technician) K N X E G 2 Auto Dimming Luminaries Energy Efficiency techniques should be done on socware, but there is no infrastructure to support it!
system can not be based on limited hardware controllers • There is no framework for the development of energy efficiency applicaAons, or any kind, but specially these one’s • The implementaAon of this energy efficiency techniques requires real Ame data processing capabiliAes • CollecAng such data requires a session management component, because BASs aeach and detach their IP gateways in an intermieent way
would be accessible for applicaAons • RegistraAon of new data points based on the exisAng (virtual data points) ones • A real-‐Ame noAficaAons and alarms could be triggered based on sets of condiAons • UAlity consumpAon allocaAon to people, spaces and Ame periods would be reachable for applicaAons of mulAple buildings
framework enabling development of applicaAon for buildings? • Can such framework enable the deployment of energy efficiency applicaAons for mulAple buildings? • Such framework would allow provider independence, thus abolishing vendor lock-‐in pracAces 29 Statement
Survey of exisAng BEMS soluAons and features • Development of a small set of applicaAon to validate the proposed framework • Improve the core framework iteraAvely based on the obtained results and/or problems encountered • ValidaAon in a real-‐world sejng, featuring some heterogeneity to achieve a beeer demo (IST Taguspark campus) 31 Overview
known, therefore the variability of applicaAon needs are low! • Middleware for BASs exists, but do not solve the heterogeneity problem completely • There is no plalorm for the development of energy efficiency applicaAons for buildings
applicaAons to perform queries over real-‐Ame data from BAS, would unleash endless possibiliAes • Such queries are hard to perform, because they involve real-‐ Ame, and some are not known at start (ad-‐hoc) • Moreover, such framework must be able to deal with streams of data coming from intermieent data sources
Layer Data Access Layer Space Planning Billing Models Data Source Management Data Point Management Device Management User Management Notification Services Data Acquisition Data Querying Data History Application Layer Central Administration BEMS: An Architecture Blueprint Data Integration Layer Building Management API Building Data Endpoints Data Source Connectors Field Level / Technology Dependent Layer Energy Dashboard Other Energy Applications n 1 Building Management API Building Data Endpoint (Client - Uses SDK) Driver KNX Driver ModBus Other Driver Data Source Connector Data Source Connector Data Source Connector
Layer Data Access Layer Space Planning Billing Models Data Source Management Data Point Management Device Management User Management Notification Services Data Acquisition Data Querying Data History Application Layer Central Administration BEMS: An Architecture Blueprint Data Integration Layer Building Management API Building Data Endpoints Data Source Connectors Field Level / Technology Dependent Layer Energy Dashboard Other Energy Applications n 1 Building Management API Building Data Endpoint (Client - Uses SDK) Driver KNX Driver ModBus Other Driver Data Source Connector Data Source Connector Data Source Connector
Layer Data Access Layer Space Planning Billing Models Data Source Management Data Point Management Device Management User Management Notification Services Data Acquisition Data Querying Data History Application Layer Central Administration BEMS: An Architecture Blueprint Data Integration Layer Building Management API Building Data Endpoints Data Source Connectors Field Level / Technology Dependent Layer Energy Dashboard Other Energy Applications n 1 Building Management API Building Data Endpoint (Client - Uses SDK) Driver KNX Driver ModBus Other Driver Data Source Connector Data Source Connector Data Source Connector
Layer Data Access Layer Space Planning Billing Models Data Source Management Data Point Management Device Management User Management Notification Services Data Acquisition Data Querying Data History Application Layer Central Administration BEMS: An Architecture Blueprint Data Integration Layer Building Management API Building Data Endpoints Data Source Connectors Field Level / Technology Dependent Layer Energy Dashboard Other Energy Applications n 1 Building Management API Building Data Endpoint (Client - Uses SDK) Driver KNX Driver ModBus Other Driver Data Source Connector Data Source Connector Data Source Connector
Layer Data Access Layer Space Planning Billing Models Data Source Management Data Point Management Device Management User Management Notification Services Data Acquisition Data Querying Data History Application Layer Central Administration BEMS: An Architecture Blueprint Data Integration Layer Building Management API Building Data Endpoints Data Source Connectors Field Level / Technology Dependent Layer Energy Dashboard Other Energy Applications n 1 Building Management API Building Data Endpoint (Client - Uses SDK) Driver KNX Driver ModBus Other Driver Data Source Connector Data Source Connector Data Source Connector
Layer Data Access Layer Space Planning Billing Models Data Source Management Data Point Management Device Management User Management Notification Services Data Acquisition Data Querying Data History Application Layer Central Administration BEMS: An Architecture Blueprint Data Integration Layer Building Management API Building Data Endpoints Data Source Connectors Field Level / Technology Dependent Layer Energy Dashboard Other Energy Applications n 1 Building Management API Building Data Endpoint (Client - Uses SDK) Driver KNX Driver ModBus Other Driver Data Source Connector Data Source Connector Data Source Connector
Layer Data Access Layer Space Planning Billing Models Data Source Management Data Point Management Device Management User Management Notification Services Data Acquisition Data Querying Data History Application Layer Central Administration BEMS: An Architecture Blueprint Data Integration Layer Building Management API Building Data Endpoints Data Source Connectors Field Level / Technology Dependent Layer Energy Dashboard Other Energy Applications Buildin Driver KNX Data Source Connector
framework iteraAvely based on the obtained results and/or problems encountered • ValidaAon in a real-‐world sejng, featuring some heterogeneity to achieve a beeer demo (IST Taguspark campus) 58 Overview
Layer Data Access Layer Data Source Management Data Point Management Device Management Authentication Only Notification Services Data Acquisition Data History Application Layer Central Administration Data Integration Layer Auto Dimming Lumaries App Auto Blind Shutoff App Building Management API Building Data Endpoints Data Source Connectors
enable the development of energy efficiency applicaAons • As we have seen these techniques must be performed via socware • There is no framework for achieve this purpose • Base on our related work, we propose the implementaAon of a prototype of this framework that will be validated in a real world sejng. Overview