BOSS: Building Operating System Services Stephen Dawson-Haggerty https://picasaweb.google.com/lh/photo/u8KnCljx6QipMRCjl8IkuA http://creativecommons.org/licenses/by-nd/3.0/ BOSS: Building Operating System Services Stephen Dawson-Haggerty

motivation Electricity grids are becoming more and more dynamic as a result of more renewable energy on the grid. Fossil-fuel-based firming is expensive, so it would be nice to modulate the loads in response to grid conditions and renewable availability. http://www.clker.com/clipart-85295.html http://cliparts101.com/free_clipart/31033/FACTORY.aspx http://www.clker.com/clipart-15789.html 1/11/13 SDB Pretreat

motivation Advanced control strategies for operating buildings are being developed in the lab, but pickup is hampered by the difficulty of getting your code into the building. Analyze the fault dependencies for me  1/11/13 SDB Pretreat

motivation Occupant-driven control strategies have seen savings as high as 50%, but require direct access to the building systems. 1/11/13 SDB Pretreat

Architecture components outline Problem overview Use networked resources Enable multiple control applications Maintain system properties (robustness, discoverability…) Architecture components Hardware abstraction Directory Historian Transaction manager Control processes 1/11/13 SDB Pretreat

Does not address reliability when controlling across a networked SCADA architecture Does not address reliability when controlling across a networked head-end supervisory panel direct device 1/11/13 SDB Pretreat

existing solutions work around this issue Standardized communications protocols Completely partitioned implementation “It’s a box” OpenADR WattStopper head-end BACNet Implications for the types of solutions people try to deploy. panel device 1/11/13 SDB Pretreat

Security and authorization Hardware abstraction design goals Fault tolerance Between domains Isolation Between processes, systems Scheduling Of users, changes Security and authorization Manage the principals Hardware abstraction Capture component relationships Provide a namespace Historical data Process, query, reduce multiprogramming Go through MPC application and these requirements. Challenges brought on by interconnection 1/11/13 SDB Pretreat

boss: a proposed architecture Control processes Fault tolerance Isolation + Scheduling “Kernel” interface Security Directory History Trans. mgr. History Functional components, interfaces, concerns. Also the decomposition onto hardware is important – the transaction manager needs to be in the building, for instance. Hardware Abstraction Layer Abstraction HPL HPL HPL HPL 1/11/13 SDB Pretreat

hardware presentation lots of underlying diversity & heterogeneity sMAP Electrical Geographical Occupancy Water Physical Information Weather Environmental Actuator Structural 1/11/13 SDB Pretreat

considerations and related work Pub/Sub JMS, TIBCO, AMQP, CORBA TinyDB Management SNMP Syndication RSS/Atom, PubSubHubbub XMPP, SenseAndrew, SenseWeb Embeddability CoAP/CORE, TinyWebServices Industrial protocols BACnet, OPC, DeviceNet Protocol Year Network Example Applications Modbus 1979 RS-485, TCP/IP Panel monitoring, alarms Fieldbus/HART 1988 various Industrial Control BACnet 1995 ARCNET, Ethernet, IP, RS-232, etc. HVAC, Lighting, Fire… WirelessHART 2007 802.15.4e Industrial control, wire replacement Zigbee SEP 2.0 2012? 802.15.4 Plug-load monitoring 1/11/13 SDB Pretreat

HPL: Represent sensors and actuators Objects are time-series and collections Represent the underlying sense and actuation points Expose over HTTP Time-series are durably identified A collection of structured key-value pairs, data Data is (time, value[, seqno]) vector { "/" : { "Contents" : ["sensor0"], “Metadata” : { “SourceName” : “Example sMAP Source” }, }, "/sensor0" : { "Contents” :["channel1"] }, "/sensor0/channel0" : { "uuid" : "a7f63910-ddc6-11e0-8ab9-13c4da852bbc", "Readings" : [ [1315890624000, 12.5 ] ] } collections Lots of experiences validated in terms of value. Making this one change fixed a lot of things: - can import efficiently - uuid identifies data for good - metadata tags data timeseries 1/11/13 SDB Pretreat

meet data acquisition needs 6lowpan networks sMAP BMS Integration Database integration Commercial building retrofit Residential deployment and automation Large wireless network sMAP RS-485 bus BacNET/IP OPC-DA sMAP Name Sensor Type Access Method Channels ISO Data CAISO, NYISO, PJM, MISO, ERCOT Web scrape 1211 ACme devices Plug-load electric meter Wireless 6lowpan mesh 344 EECS submetering project Dent Instruments PowerScout 18 electric meters Modbus 4644 EECS steam and condensate Cadillac condensate; Central Station steam meter Modbus/TCP 13 UC Berkeley submetering feeds ION 6200, Obvius Aquisuite; PSL pQube, Veris Industries E30 Mosbus/Ethernet, HTTP 4269 Sutardja Dai, Brower Hall BMS Siemens Apogee BMS, Legrand WattStopper, Johnson Control BMS BACnet/IP 4064 UC Davis submetering feeds Misc., Schneider Electric ION OPC-DA 34 (+) Weather feeds Vaisala WXT520 rooftop weather station; Wunderground SDI-12, LabJack/Modbus, web scrape 33 CBE PMP toolkit Dust motes; New York Times BMS CSV import; serial 874 1/11/13 SDB Pretreat

1/11/13 SDB Pretreat

Architecture components outline Problem overview Extend control loops to cloud Enable pluggable control applications Maintain system properties (robustness, discoverability…) Architecture components Hardware abstraction Directory Historian Transaction manager Control processes Timeline 1/11/13 SDB Pretreat

additional layer of complexity not in a computer OS What if the bus were different on every computer? Sankey diagram from Sensys 10, Fred Jiang the authors' names: Nguyen Thi Hoang Lan the title of the work: Module 2: Top-Level View of Computer Organization the Connexions URL where the work can be found: http://cnx.org/content/m29708/1.1/ Nguyen Thi Hoang Lan, http://cnx.org/content/m29708/1.1/ 1/11/13 SDB Pretreat

Architecture components outline Problem overview Extend control loops to cloud Enable pluggable control applications Maintain system properties (robustness, discoverability…) Architecture components Hardware abstraction Directory Historian Transaction manager Control processes Timeline 1/11/13 SDB Pretreat

historian modeling requires a log of sensor data Limited real, open systems which do this well Time series systems: wavelet systems, quick computations Lookup table-based floating point compression OpenTSDB = HBase + HDFS OPC+HDA, OSI Pi, System S, Flume MRO, Spark streaming Medusa, Fjord, Telegraph[CQ] SciDB Write pattern Append data to streams Occasionally bulk-load Read pattern Range-query on timestamp Process pattern Clean, “join”, compute SQL is quite clumsy for time-series processing… Critical for empirical modeling when looking at stochastic physical systems. Learned from experience. 1/11/13 SDB Pretreat

Extract data from 100 streams Interpolate onto a 5-minute time basis Larry Ellison’s query Extract data from 100 streams Interpolate onto a 5-minute time basis Filter missing data Combine the streams into a matrix Load into MATLAB/R/numpy looks like pipes to me Looked at 20k user-submitted queries 1/11/13 SDB Pretreat

Principles for physical data storage Data is mostly array-like Efficient “views” of data: subsampled/cleaned Treat as 1st class objects Use to govern retention and privacy Flexible operators for repairing timestamps, unit conversion, time sampling Compression/materialization control Something like append-only RDD’s sum < paste < window(mean, field="hour") of data 1/11/13 SDB Pretreat

write load on readingdb6 Importing old data: 150k points/sec Continuous write load: 300-500pts/sec 1/11/13 10 billion readings, 40k streams, 3.5bytes/record on disk SDB Pretreat

What are the axes… 1/11/13 SDB Pretreat

Architecture components outline Problem overview Extend control loops to cloud Enable pluggable control applications Maintain system properties (robustness, discoverability…) Architecture components Hardware abstraction Directory Historian Transaction manager Control processes Timeline 1/11/13 SDB Pretreat

want cloud applications… with old-fashioned reliability control transactions want cloud applications… with old-fashioned reliability 1/11/13 SDB Pretreat

Use transaction metaphor to update state of the building idea Use transaction metaphor to update state of the building Adjust set points Replace control logic 1/11/13 SDB Pretreat

writer 1 value: 245cfm 245 writer 2 value: 280cfm 245 1/11/13 SDB Pretreat

BACnet priorities 280 245 writer 1 value: 245cfm priority: 3 priority array writer 2 value: 280cfm priority: 1 <time passes> writer 2 clear writer 1 crashes 16 1/11/13 SDB Pretreat present value: 245cfm present value: 280cfm

Transaction building blocks future work Transaction building blocks Lease time Priority level Abort/rollback notifications Define levels of transaction isolation Actuator: just prevent concurrent writes System: use pre-defined hierarchal locking Model-based: learn interaction model 1/11/13 SDB Pretreat

Thank You portable, robust applications for the physical environment Hardware presentation layer: sMAP Hardware abstraction layer: device-specific logic Time-series service: the archiver Reliable control inputs: the transaction manager Security: the authorization service 1/11/13 SDB Pretreat