1. Using BIM Geometry and GIS Symbology in Onuma Open Architecture to Leverage Linked Open Data Slideshow for Kimon Onuma Onuma Planning System Pasadena California 2008-12-18 Presented by: DeborahMacPherson BobSmith Jay MacPherson Collaborators: SF MapLab - David Coggeshall BSP Project - Rex Brooks, Toby Considine, Michelle Raymond NIST BFRL - Alan Vinh, David Holmberg, Jason Averill

2. Spectrum of Open Information Exchange Needs Over Time Shape of Song, Martin Wattenberg Physical World Digital World Before After Now

3. Spectrum of Open Information Exchange Needs Over Time Shape of Song, Martin Wattenberg Physical World Digital World Before After Now Change Belt

4. Spectrum of Open Information Exchange Needs Over Time Shape of Song, Martin Wattenberg Physical World Digital World Before After Now Change Belt Replace Fan Coil Unit

5. Spectrum of Open Information Exchange Needs Over Time Shape of Song, Martin Wattenberg Physical World Digital World Before After Now Change Belt Replace Fan Coil Unit Upgrade HVAC System

6. Shape of Song, Martin Wattenberg Physical World Digital World Before After Now Immediate Example: Standard Floorplans for Emergency Response Long Term Example: Sustainable Clean Water

7. BIMstorm: First Opportunity for Modular Repeatable Data Structures on Large Scale

9. Code Mapping Templates Based on Building Type and Location

10. Service of Buildings Vs Building Types Geometric Boundaries of AHJs Systematic Exchange

11. Michelle Raymond Information drill down Hierarchy of data – Based on physical containment – Example: Sites contain Buildings; Buildings contain Areas Need common terminology ExpeditionWorkshop/ExploringVirtualOrganizationLandscape CyberinfrastructureReadinessForEmergencyResponse 2008 10 07

12. Firemans Digital Keybox A work in progress for Building Emergency Response Scenario comments By Deborah MacPherson, Specifications and Research WDG Architecture, Projects Director Accuracy&AestheticsWDG ArchitectureAccuracy&Aesthetics Debmacp@gmail.com

13. Combining NIST BFRL and OGC Building Emergency Response ScenarioNIST BFRLOGC 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

14. at 321 Prince Street

15. in a section of the third floor

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

17. The explosion disables the smoke alarm in the room

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

19. The fire panel generates a Common Alerting Protocol CAP alert

20. that is passed to the BISACS Base Server (BBS)

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

22. that monitors the building

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

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

25. reporting a smoke alarm from the hallway outside 310

26. Alan Vihn 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

27. 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.

28. Suggested Areas of Responsibility 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 Space System Level Sub-Systems Room Water / Sea Land / Parcel Underground Air / Space Overlay Components City GIS TC 211 IFC ISO/PAS 16739 TC184/SC4 Process ISO 15926 TC184/SC4 ISO 16739 – Most buildings and many structures related to smaller scale projects ISO 15926 – Process industry including large infrastructure projects From Deke Smith, Presented at AEC-ST Conference Session S608

29. Focus on 10 Types David Coggershall Volunteer Program Were here to help you with your building documentation Swirling data together Getting it to grow certain ways

30. Towards the Definition of an Open Architectural Domain in Open Cyc and Ifd:Ifd In A Nutshell by Lars Bjorkhaug Upper Mapping and Binding Exchange Layer A lightweight, subject concept reference structure for the Web

31. The Hairnet Over the Basketball Mike Bergman. Zeitgist http://www.umbel.org/role.html 20,000 Docking Ports for an Open World Zitgist is pleased to host this demo sandbox.

32. Metadata Architectural Contents of Europe - Want to Collaborate with Open Cyc. Next step, Subset Extraction, Explain Architectural Domain

33. 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, see http://www.maplab.org/harney1/ By David Coggeshall at SF MapLab What can be done first? What can be done first to address immediate need? 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

35. Fire Department Digital Keybox A work in progress for Building Emergency Response Scenario comments By Deborah MacPherson, Specifications and Research WDG Architecture, Projects Director Accuracy&AestheticsWDG ArchitectureAccuracy&Aesthetics Debmacp@gmail.com Remainder of the slides will be from the Building Information Model point of view as the scenario continues on. Final slide will be just the scenario components and arrows with relevant standards overlaid - Ex: NFPA 70 and 72 Towards a Common Operating Picture

36. Coverage, Reference Points, and New OPS Time Clock

37. Smart Grid

38. Coverage, Reference Points, and New OPS Time Clock Smart Grid Open SVG

39. Coverage, Reference Points, and New OPS Time Clock Smart Grid Open SVG Tracking and Negotiating Tools for the General Public EX: Sustainability, Water Rights, Improved Services Tracking and Negotiating Tools for the General Public EX: Sustainability, Water Rights, Improved Services