Combining NIST BFRL and OGC

Building Emergency Response Scenario

Following is a use case scenario of a building fire incident and covers alert generation and propagation to dispatch followed by the first responder use of building data. In addition, a table is presented that collects previous work with public safety representative in defining useful building data. This table categorizes the building data.

The scenario begins in a large commercial building

at 321 Prince Street

in a section of the third floor

that is undergoing renovation. Contractors left out some vapor-producing chemicals that have ignited after-hours, producing a small explosion and starting a fire.

The explosion disables the smoke alarm in the room

but this generates a trouble condition at the fire panel.

The fire panel generates a Common Alerting Protocol CAP alert

that is passed to the BISACS Base Server (BBS)

The alert is then passed to the subscribing central station alarm (CSA) company

that monitors the building

Upon receipt at the CSA, a representative attempts to contact the building personnel to verify the alert (smoke alarm trouble in room 310)

While the CSA representative follows procedures to verify the alert, another alert arrives

reporting a smoke alarm from the hallway outside 310

Alan Vinh NIST BFRL: “I'm not clear what you're trying to distinguished between "passing" and "transmitting" the alerts between these systems. What we are trying to work towards is some form of standard access point (SAP) between the various emergency computing facilities/networks such as the BBS, the CSA, the NG9-1-1 and the PSAP systems. Having the SAP in place and most likely it will be implemented as a web services interface, we don't really "transmit" alerts (ala radio signals) but rather connect to the various SAPs and send in the alerts via IP connections/communications (either via land lines or mobile communication).”

The CSA representative then immediately transmits these two alerts to 9-1-1 dispatch electronically, with both CAP alerts grouped together in a message. The 9-1-1 dispatch center receives the CAP alerts with data fields from the message loaded into form fields

At this point the dispatcher will see that there is a suspected fire in a commercial building at 321 Prince Street with smoke alarm trouble and alarm signals on the third floor.

Alan Vinh NIST BFRL ….that is why SAP Standard Access Point is important, if one bubble is not there, go to the next one, back to square one and no body knows about it. Eventually they talk back to the building….

Michelle Raymond Honeywell…there is alert information that can come from any level, it gets aggregated at any level, each information provider has an identifier, some will have access and will be made available when its appropriate, then would have access. What can be retrieved may be policy based, and the incident needs an identifier, is a part of the identifier you need…

Alan Vinh NIST BFRL “…the SAP is like the electrical outlets, if I want electricity for my lamp then my lamp must have the proper plug to fit into the wall to get the electricity. Without the proper plug, the lamp is useless and can not get its electricity. With the proper plug, the lamp can be used with any electrical outlet that supports its plug. All public safety computers/gateways must support the same type of outlet so that other computers can "plug" in to communicate. To communicate with any of the computers that is the gateway into a computing facility such as the CSA or the PSAP or the building, the software (e.g., the plug) must communicate via a common interface (e.g., the common shaped electrical outlet) that we are calling the SAP (Standard Access Point).”

STATIC - prepared ahead of time, each building and jurisdiction may be different

1 Floorplan from building owners, fire department goes out to validate

2 Naming conventions for buildings, levels, spaces etc

3 Information content, discrete elements relevant to safety and response

OSHA's Interactive Floorplan Demonstration

DYNAMIC - interoperable, systematic

4 Spatial temporal is when an incident starts, elements that change state, real time updates

For a work in progress demo, seehttp://www.maplab.org/harney1/By David Coggershell at SF MapLab

Fire Department Digital KeyboxA work in progress for Building Emergency Response Scenario comments

By Deborah MacPherson, Specifications and Research WDG Architecture, Projects Director Accuracy&AestheticsDebmacp@gmail.com

Remainder of the slides will be from the BuildingInformation Model point of view as the scenariocontinues on. Final slide will be just the scenariocomponents and arrows with relevant standards

overlaid - Ex: NFPA 70 and 72

Towards a Common Operating Picture