Building Service Performance Buildings and the Larger Community (a situational impact perspective) Michelle Raymond Principal Research Scientist Honeywell Labs michelle.raymond@honeywell.com Ontolog Forum: Building Service Performance Project Kickoff - Michelle Raymond 14 July, 2008

Situation Management Information Needs Cleanly Cross Domains Connect correct information NOW! Information services Reasoning services Action services Data Exchange Support Sharing policies Distribution assignment Creating Common Operating Picture Scope and view accounting Focus: Emergency Response needs ability to Cleanly Cross Domains and solid Data Exchange Support Cleanly Cross Domains Connect correct information NOW! (services, services, services) Information services Reasoning services Action services Data Exchange Support (getting the right information to the right people at the right time. Sharing policies Distribution assignment Creating Common Operating Picture Scope and view accounting Ontolog Forum: Building Service Performance Project Kickoff - Michelle Raymond 14 July, 2008

Why an ontology? Having structured relationships amongst standardized information for a facility: Defines facility information exchanges and resulting BIM data in way usable by specialized service providers Organizes facility life-cycle information with associated data Provides basis for longevity to the information and improves feasiblity of multiple checkpoints for data integrity A BIM is great, but without it being standardized you could get locked into the limits of one vendors products We are encouraging the use of IFC based information exchanges which link us to the international community open standards. We need to have commonly organized information throughout the life-cycle so other software products outside our area of responsibility can find and read the data We will need to keep the data alive and usable for 50-100 years – this is no small order and it can only be accomplished with a standardized approach Ontolog Forum: Building Service Performance Project Kickoff - Michelle Raymond 14 July, 2008

NBIMS Business Processes Interfaces to business processes at the core of NBIMS Standardizing commonly-recognized relationships Identify information needing to flow through the model Make information available to appropriate parties Formalizing information flows will: Identify authoritative sources for information Ensure that correct data is collected Data need only be entered once into the model Interfaces between various sections of the National BIM Standard and business processes will be at the core of the Standard. Standardizing relationships will help to identify the information that needs to flow through the model and be made available to other parties as identified in the BIM Scope. Formalizing these information flows will help identify authoritative sources for information and help ensure that correct data is collected and need only be entered once into the model for all eventual re-use and modification. Ontolog Forum: Building Service Performance Project Kickoff - Michelle Raymond 14 July, 2008

National BIM Standard Definition of BIM – buildingSMART Official Definition: A Building Information Model (BIM) is a digital representation of physical and functional characteristics of a facility.  As such it serves as a shared knowledge resource for information about a facility forming a reliable basis for decisions during its life-cycle from inception onward. This is the agreed to “standard” definition for a BIM. Key points are: It is digital so a machine can read and analyze it It includes the entire life-cycle from inception onward It supports collaboration It is shared information and supports interoperability It is an open standard and free * All text above is directly or paraphrased from the BIM_Slide_Show. Ontolog Forum: Building Service Performance Project Kickoff - Michelle Raymond 14 July, 2008

Geospatial Information Hierarchical Information Relationships IAI-IFC Usage Space Natural Asset Linear Structure Structure Building Facility / Built Theatre / World Sub-Systems System Level Site Real Property Asset Country State / Province County Installation / Region Node Segment Room Water / Sea Land / Parcel Underground Air / Space Geospatial Information (GIS) Overlay Building information (Building Information Models) Components City The next few slides are to give you a sense of the information available in Buildings and how it might be used in the Emergency Data Exchange Language – Distribution Element. Add more data on DE This diagram identifies how information is rolled up from the facility level up to the world view. It is a joint effort from many in the industry It shows how information inside a facility links into the geospatial world. ----- * All text above is directly or paraphrased from the BIM_Slide_Show. © BIMS 2006 Ontolog Forum: Building Service Performance Project Kickoff - Michelle Raymond 6 14 July, 2008

Reports or Extracted Data from BIM (examples from all classifications) IFC objects, relationships, space BUILDING Or Structure Sub-Systems (part of systems) Level (Stories) Attributes Vertical Room Void Business Groups Financial Classifications Assets Metrics Example FCA,MDI Rentable Space Circulation Area Furniture Equipment Phone Zones Personnel SYSTEMS –Ex. Structural, MEP, Flooring, Ceiling, Exterior, Walls SPACE-Vertical Horizontal, Empty OVERLAYS – Typically associated with building hierarchy elements. Space Assignment Business Group Marketing Administration Systems represent the physical entities of the building. Systems use NA classifications such as Omni-Class and Uniformat and are transported/exchanged via IFCs Space is physical in nature, but can be unbounded (have no or cross physical boundaries) but it will always be tied to the physical structure or systems in some way Overlays are more abstract data - organizational, operational, functional, financial, non-fixed assets, resources, personnel, etc. that is data tied to the Systems and Space Secure Areas Systems SUI,CI Standards Area Volume Gross Net Reports or Extracted Data from BIM (examples from all classifications) Sq. Ftg. Surface Usable Linear Ft. Quantities Components Materials & Types Hierarchical Building Information Relationships This slide has a lot of information on it. That there is a lot of information is the main thing I want you to take away from this slide. From the geospatial slide we go down a level which is at the heart of the BIM. Industry Foundation Class objects and relationships Systems are items such as structural systems, mechanical systems, closure systems and the like. Space is the room as well as the void and adds up to the total footprint. Overlays are polygons that lay over the space and systems that could be heating zones, fire protection zones, organizations, financial cost centers, etc. It is also important to note that floor plans are only reports off the model. ----- * All text above is directly or paraphrased from the NBIMS website and the BIM_Slide_Show. © BIMS 2006 Ontolog Forum: Building Service Performance Project Kickoff - Michelle Raymond 7 14 July, 2008

One object exists in multiple contexts One concept carries the same unique identification in every language 78AF4E98C8D4406B873DBB85E1FE7DB In a CAD system In a briefing document Properties Properties BARBi - Norway LexiCon - Nederland Properties NBS - England In product catalogues Properties In a calculation system SDC - France Properties NBIMS – North America Properties Properties Properties Properties In a Facility management system In classification systems Properties Properties Industry Foundation Classes and the directory elements are molecules used in various combinations to make up compounds. IFD (Directory) provides an international harmonization of molecular elements from different countries. Many companies are multinational and the dictionary allows translations to occur. For demolition and reconstruction In building specifications Properties Properties Courtesy of Lars Bjørkhaug, Norwegian Building Research Institute © BIMS 2006 Ontolog Forum: Building Service Performance Project Kickoff - Michelle Raymond 8 14 July, 2008

oBIX – Open Building Information eXchange Emergency Management TC oBIX – Open Building Information eXchange oBIX Architecture objectives provide means for reliable, extensible, safe interoperability. Enables Building Management Systems to communicate with external services Represents information in a standardized format Enables defining specialized contracts to invoke operations based on security permission and situation awareness Provides for changing permissions based on alarm states The Open Building Information eXchange (oBIX) standard is used for the building data and operational procedures. A Distribution Element is routed to the building system with an oBIX payload. Having oBIX provide Building Information Model based knowledge in a form agreeable to all communities is an ongoing effort. Connect Facility Information and Emergency Management NBIMS Vision BIM Data Model NBIMS Process oBIX Operations Data Exchange Support oBIX Contracts and EDXL-DE header EDXL–DE payloads Other standards usage and support BIMS into NIMS Ontolog Forum: Building Service Performance Project Kickoff - Michelle Raymond 14 July, 2008

oBIX 2.0 Stack oBIX 1.0 Foundation oBIX Enterprise oBIX Building Object model XML Contracts Web Services Watches, points, histories, alarming oBIX Enterprise Distributed database: query, search, navigation, caching Ontology: site, building, story, equipment, space, relationships oBIX Building HVAC equip Fire Elevator, etc oBIX Energy Meter Price structures oBIX Security Users/badges Doors/readers Cameras/video oBIX Industrial Process 1131/1499 Batch/recipes Focusing on what we’ve shown works first data encoded as XML Ontolog Forum: Building Service Performance Project Kickoff - Michelle Raymond 14 July, 2008

Storm begins to move in

Skywarn storm spotter network triggered Data collected at Building Shared to wider community when appropiate (ex: weather, hazmat detection)

Skywarn storm spotter network triggered Building Sensors and Actuators

Skywarn storm spotter network triggered Scenario: segment 3 Weather spotter In the same building there works a trained Skywarn weather spotter. His weather radio receives an alarm from the NWS indicating the severe thunderstorm watch. He heads to the roof weather lab and monitors the weather situation visually and by sensor instrumentation. He transmits a report indicating the sighting of a rotating wall cloud via his ham radio and a secure web service. With the Doppler images, sensor data and trained storm spotter reports, the National Weather Service has enough reliable information to initiate a tornado warning.

Skywarn storm spotter at work

Skywarn storm spotter at work

System: activation 2 (Activate tornado warning) Note: show in myStateUSA service (see appendix slides for screen shots)

Ontolog Forum: Building Service Performance Project Kickoff - Michelle Raymond 14 July, 2008

Ontolog Forum: Building Service Performance Project Kickoff - Michelle Raymond 14 July, 2008

Images: local area images Images: Ontolog Forum: Building Service Performance Project Kickoff - Michelle Raymond 14 July, 2008

Management level technical: topic 3 Emergency Response Infrastructure A Tornado Path Prediction situation analysis tool defines the expected path and feeds information back into the emergency alerting system. Another situation analysis tool on the network, matches the geospatial information about the tornado’s path to a database of assets within the metro area. This information can be used to specialize messages to warn those in the path and alert emergency responders to the anticipated damage. Path prediction combined with geospatial and asset location information is an example of a Service that can be utilized within the Emergency Response Infrastructure.

oBIX payloads in Distribution Element example Emergency Management TC Rail yard Office Other Recipients Tornado Touchdown Alert Chemical Plant oBIX payloads in Distribution Element example Emergency Operations First Responders Send DE CAP oBIX proprietary protocol invoke contract “NWS Alert” Contracts Invoke “Tornado – Take Shelter Alert” requests “Safety Chemical Containment Operation” Building Management System distributionID senderID dateTimeSent distributionStatus distributionType combinedConfidentiality language senderRole * recipientRole * keyword * distributionReference * # explicitAddress * contentObject contentDescription contentKeyword * incidentID incidentDescription originatorRole * consumerRole * confidentiality other * Ontolog Forum: Building Service Performance Project Kickoff - Michelle Raymond 23 14 July, 2008

CERT response Management level technical: topic 5 Scalable and adaptable For an Incident Management System to be effective it must be scalable and adaptable. It must be capable of handling small incidents, like single events of wind damage at the beginning of the scenario. It must be able to handle separate events that tax the same resource pool. It must be able to deal with events separated through out the jurisdiction and cross jurisdiction. It must continue to evolve as the incident evolves.

Images: local area images Management level technical: topic 8 Practices and policies At each stage of the command change the personnel roles and communications structure is managed via Minnesota Incident Management System (MnIMS) policies. Registries of individuals roles, skills and privileges matched against their personalized badging aid in rapid team structuring and information transfer of existing situation awareness. The lack of availability of interoperable communication devices for the CERT responders forces them to move the Incident Command Post to a busy and distracting location. Each Emergency Response ‘best-practice’ that isn’t followed, degrades the system. At least the adaptability of the system helps mitigate the degradation – some.

Images: local area images

Scenario: segment 13 Situation assessment determines resource needs It is determined that removing debris by hand and with the limited available tools won’t get the trapped kids out fast enough from areas where the quality of air is unknown. Heavy equipment is needed.

Resource Messaging Services Local Heavy Construction Company City Emergency Management System We need heavy equipment for careful debris removal. Ham Radio Operator Request Resource Broadcast Response to Request (includes location / equip.) Incident Commander (on site) Requisition Resource Commit Resource Management level technical: topic 9 The Emergency Data Exchange Language – Resource Messaging within Emergency Response Information and Communications Architecture The primary purpose of the Emergency Data Exchange Language - Resource Messaging (EDXL_RM). Specification is to provide a set of standard formats for XML emergency messages. These Resource Messages are specifically designed as payloads of Emergency Data Exchange Language Distribution Element- (EDXL_DE)-routed messages. Together EDXL_DE and EDXL_RM are intended to expedite all activities associated with resources needed to respond and adapt to emergency incidents. The Resource Message is intended to be the payload or one of the payloads of the Distribution Element which contains it. The Resource Message is constrained to a manageable set of 16 Resource Message types related to the major communication purposes involved in the allocation of resources pertaining to preparation for, response to and remediation of emergency incidents. Example In our scenario, a request is sent from incident command for appropriate heavy equipment. A software tool installed in the command unit notes that use of heavy equipment requires a licensed heavy equipment operator. Thus, the resource request message includes both equipment and equipment operator. The resource request message is formatted according to the Emergency Data Exchange Language – Resource Messaging (EDXL-RM) standard and is distributed via protocol accepted within the metropolitan area using SOAP and HTTP. Return of the equipment and operators will also be managed by the EDXL-RM standard and the associated resource management procedural methods. Report Resource Deployment We need search and rescue support Site Emergency Management System Request Information Broadcast

Hazardous Materials Sensor Detection Triggered Does your “building” care? Do it’s occupants? It depends. A service provider shares needed information. Ontolog Forum: Building Service Performance Project Kickoff - Michelle Raymond 14 July, 2008

Situation Maps A variety of buildings and organizations are about to become involved in the situation. Ontolog Forum: Building Service Performance Project Kickoff - Michelle Raymond 14 July, 2008

Situation Maps Alert received depends on the location of the building and (optionally) on the type of facility. Ontolog Forum: Building Service Performance Project Kickoff - Michelle Raymond 14 July, 2008

Situation Maps Examples of Schools Effected by the Emergency Following pre-plans. Examples of Schools Effected by the Emergency Ontolog Forum: Building Service Performance Project Kickoff - Michelle Raymond 14 July, 2008

Situation Maps Business Building that can Cut Outside Air Intake Building system response Business Building that can Cut Outside Air Intake Ontolog Forum: Building Service Performance Project Kickoff - Michelle Raymond 14 July, 2008

Situation Maps The Eldercare System Evacuation Plan Calling other services. The Eldercare System Evacuation Plan Ontolog Forum: Building Service Performance Project Kickoff - Michelle Raymond 14 July, 2008

Knowledge Solutions needed Cleanly Cross Domains Know where to get data – SOA-RR Domain Information Structure - Ontology Reasoning Systems Ontology based Services Data Exchange Support EventTypes in Policy Management within SOA Incident Lifecycle - Ontology Ontology to Ontology – Semantic clustering Data slicing – Metadata for scope and view Connect Facility Information and Emergency Management NBIMS Vision BIM Data Model NBIMS Process and Rules oBIX Operations Data Exchange Support oBIX Contracts and EDXL-DE header EDXL–DE payloads Other standards usage and support BIMS into NIMS Ontolog Forum: Building Service Performance Project Kickoff - Michelle Raymond 14 July, 2008 - Michelle Raymond

Moving Forward Once the Framework is in place – the opportunity for beneficial services and sources are endless. Let’s discuss what services you need or can provide and how we can trust those services through good perfomance measurement. Management level technical: topic 10 cont. Conclusion

Presenter Contact is welcome via: michellearaymond@gmail.com Links and References (NBIMS) National Building Information Model Standard Project page: http://www.facilityinformationcouncil.org/bim/ BIMS Slide Show: www.facilityinformationcouncil.org/bim/docs/BIM_Slide_Show.ppt (oBIX) Open Building Information Exchange OASIS oBIX Technical Committee: http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=obix oBIX TC Press links: http://www.oasis-open.org/committees/obix/press.php (EDXL) Emergency Data eXchange Language OASIS EMTC Technical Committee: http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=emergency Associated EMTC Standards: http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=emergency#technical Presenter Contact is welcome via: michellearaymond@gmail.com Ontolog Forum: Building Service Performance Project Kickoff - Michelle Raymond 14 July, 2008