BIM, Open Standards, and Pre-Plans

1. BIM, Open Standards, and Pre-Plans Golden Gate Safety Network Building Service Performance Project @ NYC BIM Interest Group 18-Feb-2009

2. Questions from Greg Jakubowski, P.E., CSP, FSFPE, Principal and Chief Engineer, Fire Planning Associates Q: …must have pre-incident information about buildings, how can we achieve that through BIM? Q: Who will use this information and what do they need to know? Q: Who has that information? Capturing through design and construction, annotated pictures and diagrams, must be a common format.

3. How Can the Open Floor Plan Display Project Help? Q: …must have pre-incident information about buildings, how can we achieve that through BIM? A: By limiting building information exchanges to only what is needed by fire services and useful to police. By easing terminology differences ~ developing a process and definitions at a level the basic concepts belong to everyone. Q: Who will use this information and what do they need to know? A: In this case, Fire Departments, Owners, and Inspectors. Where possible, use existing ISO, IBC, IFC, NFPA standards to facilitate efficient documentation and strong communication chains. Q: Who has that information? Capturing through design and construction, annotated pictures and diagrams, must be a common format. A: Construction Operations Building Information Exchange (COBIE) can already perform many of these tasks. A deliverable of the Open Floor Plan Display Project is a set of recommendations, guidelines and mapping to relevant code citations, standards, and best practices using XML and COBIE.

4. What is COBIE? “… not for working, only for the exchange” Bill East USACE on the phone

5. Talking to the Building • Where are you located? • What kind of building are you? • Who are the occupants? • Where are the exits, elevators, stairs ? • Where is the fire? • How has the fire progressed? • What else is in this building?

6. Locating the Building using BIG web standards Geoconcepts Ontology v1.2 & v1.2_swrl at Geospatial Meaning: Geospatial Semantic Web Research. GeoWeb Trends

7. Limiting Building Information What do fire service organizations want to know? Meet Local Code! Additionally and consistently mentioned: Storage or Use of Flammable or Combustible Materials Structures susceptible to early collapse Hazardous openings Heavy Items Potential Traps such as swimming pools Lobbies on multiple floors Counterflow in stairway lower levels

8. Open Floor Plan Display Problem Space STATIC - Prepared ahead of time, each building and jurisdiction may be different DYNAMIC - Interoperable, Systematic Any vendor or public safety organization can use SVG OSHA's Interactive Floorplan Demonstration Recognizable Symbol Current Future

9. Functional Display Requirements Refer to http://ontolog.cim3.net/cgi-bin/wiki.pl?FloorplanMarkupLanguage “… some people are passionate about access flooring” Mark Kalin SCIP at Specifiers Property Sets Kickoff 2006 International Fire Code, Section 509 The fire command center shall comply with NFPA 72 and contain the following features: Schematic building plans indicating the typical floor plan and detailing the building core, means of egress, fire protection systems, fire-fighting equipment and fire department access.

10. Anyone can, Sign up, Log In, and Work On

11. Format Preparation Guidelines • The proposed floor plan data exchange format is meant to be general purpose irrespective of the size, shape, or age of the building. Therefore it is important to recognize the starting point for deriving this format may vary greatly from one building to the next. Several examples, from old to new, are as follows: • Old Building, No Floor Plans • Old Building, Paper Plans • Recent Building, Un-conformed CAD • Recent Building, Good CAD Practices • Current and Future Buildings, Advanced CAD Practices

12. Designing to a Fully Functional City Fire Department of New York Selects IBM for Intelligent Fire Safety System Monday January 12, 2009, 10:20 am EST A single, unified view of a property; Improved resource deployment and utilization for inspections; Expanded management, Analysis and preparedness planning; A risk-based inspection system for field inspections. NIST BFRL Scenario has some common goals

13. Creating Templates Standardizing GIS Symbology

14. Open path we think will work: SVG, JavaScript, AJAX, EDXL-DE, CAP Combining NIST BFRL and OGCBuilding 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. Comparison SVG vs Flash PBS Beware evil pop-ups, New Scientist

15. The scenario begins in a large commercial building

16. at 321 Prince Street

17. Note: Each concept Falls into the place Where it belongs in a section of the third floor

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

19. The explosion disables the smoke alarm in the room

20. but this generates a trouble condition at the fire panel.

21. The fire panel generates a Common Alerting Protocol CAPalert

22. Note: Elements that Are already known Are fixed and stay. that is passed to the BISACS Base Server (BBS)

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

24. that monitors the building

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

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

27. reporting a smoke alarm from the hallway outside 310

28. STOPPED @ ALERTS GROUPED TOGETHER IN A MESSAGE: The equivalent of Fire Department Digital Keybox is outside the scope of the Open Floor Plan Display Project. Fitting and adapting NIST Diagram to Fit OGC / NBIMS hierarchy is currently Incomplete. Remainder of the scenario Is parallel work by NIST Workshop participants and Subject Matter Experts Advising on this project “Open Floor Plans are Before Security and Access”

29. Nevertheless, an Open Standard Context will help whole systems work together better sooner or later. Today, Open2D only. An Easy Rapid Prototyping Technique with Point Cloud Data by Pralay Pal in the Rapid Prototyping Journal Current Future

30. Useful Sooner Linking BIM to GIS

31. Sooner: Building A Limited Dictionary

32. Sooner: Lightweight Stand Alone Floor Plans

33. A Beneficial Case Study: Worst Case Scenario Agreement on Floor 0 GINA MARIE>Around Auckland (and Kapa Haka Performance)

34. A Beneficial Program: Architect / Owner / AHJ “Imagine a volunteer program, We’re here to help you with your building documentation” David Coggeshall on the phone “Should work with a fully Functional AHJ such As Arlington County” “Someone has to pay for All of this” Discussions at WDG Current Future

35. Turn over to David Coggeshall SFC MapLab Common Operating Picture Concept Open Floor Plan Display Demonstration