1 / 20

Collecting and Managing Building Data

Collecting and Managing Building Data. Jorge Ortiz ActionWebs Weekly Meeting September 1, 2010. Buildings large electrical energy consumer. Coal consumption by sector. 72% of electrical consumption, 40% of total consumption, 42% of GHG footprint 370 B$ in US annual utility bill

mervin
Télécharger la présentation

Collecting and Managing Building Data

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Collecting and ManagingBuilding Data Jorge Ortiz ActionWebs Weekly Meeting September 1, 2010

  2. Buildings large electrical energy consumer Coal consumption by sector • 72% of electrical consumption, 40% of total consumption, 42% of GHG footprint • 370 B$ in US annual utility bill • 9.5% of GDP in bldg construction/renovation • Primarily Coal generation • 10-20% of the energy is wasted1 • Visibility and intelligence can help reduce waste2 Electricity source 1 K. W. Roth et al., Energy Impact of Commercial Building Controls and Performance Diagnostics, TIAX (http://apps1.eere.energy.gov/buildings/publications/pdfs/corporate/pnnl-15149_market_assessment.pdf, 2005).

  3. Talk overview • Building energy management goals • Cory Hall project • Simple Monitoring and Actuation Protocol (sMAP) • Live, raw data • Integrated Sensor-Stream Storage System (IS4) • Live, raw, contextualized and processed • Current state and future work

  4. Power proportionalityin buildings • Uncover underlying energy usage • What are the usage patterns and models? • Uncover available energy • How much energy is available? • Electric, solar, wind, etc. • How much does it cost? Etc. • Shed unnecessary waste • Define efficiency metrics • Schedule the remaining load • Optimization REPEAT

  5. Uncovering each layer Environments & Activity Vibration Climate Plant Load Tree CT: mains power monitoring Humidity Temperature Pressure panel level power monitoring ACme: plug load energy monitor and controller

  6. Uniform Representation of Physical Data PersonalFeedback Modeling ContinuousCommissioning Visualization Control Applications Actuation Location Storage Debugging Authentication sMAP Electrical Geographical Occupancy Water Physical Information Actuator Environmental Weather Structural

  7. sMAP Overview Application Interface • Simple Monitoring and Action Profile • JSON data format for measuring, sensing, and metering • HTTP/Restful interface to each sensor or meter HTTP Engine TCP TinyOS/BLIP HYDRO Routing 6lowpan HC 802.15.4 Link

  8. Capturing electric load tree Electrical Load Tree Physical CT mains power monitoring Circuit/breaker panel level power monitoring ACme: plug load energy monitor and controller Humidity Temperature PAR/TSR Vibration

  9. Data-Metadata BindNaming GET cory/lt /main/devices/C3/true_power http://is4/ xform REPLY { "status": "success", "pubid": "68060935-1457-414c-b330- e2220969d970", "properties": { "formatting": { "UnitofTime": "second", "UnitofMeasure": "kW", "Divisor": 10, "MeterType": "electric", "Version": 1, … } Main

  10. Cory Hall Load TreeRESTful access

  11. Capturing context Chiller Pump Zone Chiller Vent Vent Pump SF EF AHU

  12. HVAC namespace /<building>/hvac/hvac_wet /<CT_source> /devices /<device> /<publisher> /<pump_source> /devices /<device> /<publisher> /<Chiller_source> /devices /<device> …

  13. Namespace for spaces /<building>/spaces/<floor> /<area> /devices /<device> /<publisher> /<room> /devices /<device> /<publisher> /<area> /devices /<device> /<publisher> …

  14. Hierarchical composition • Resource node hierarchy rules for each namespace • i.e. Room may have area child but not a floor child • Some resource have “devices” child • “devices” contain device instances • Device instances contain publishers • Publisher map to sMAP “measurement points” • Namespaces combined through measurement devices

  15. Combining namespaces

  16. Combining query facilities

  17. IS4 ArchitecturalOverview Publish JSON CT mains power monitoring Subscribe JSON HTTP/REST Metadata Manager Publish Manager JSON Subscribe Query Processor Subscribe Manager Data processing Security Manager Subscribe Storage ACme: plug load energy monitor and controller JSON IS4 Humidity PAR/TSR Temperature Vibration

  18. Current state • 69 raw stream sources available (sMAP) • 55 contextualized stream sources available (IS4) • IS4 release available for download • Version 2.0 to be released in a few weeks

  19. (Near) future work • Direct all sMAP feeds through IS4 • Integrate modeling with querying features • Automatic device configuration

  20. Questions • More information • http://is4server.com • Quickstart tutorial: http://smote.cs.berkeley.edu:8000/tracenv/wiki/is4_quickstart • jortiz@cs.berkeley.edu

More Related