Using BIM Geometry and GIS Symbology in Onuma Open Architecture to Leverage Linked Open Data

Slideshow for Kimon OnumaOnuma Planning System

Pasadena California 2008-12-18

Presented by:DeborahMacPherson

BobSmithJay MacPherson

Collaborators:SF MapLab - David Coggeshall

BSP Project - Rex Brooks, Toby Considine, Michelle RaymondNIST BFRL - Alan Vinh, David Holmberg, Jason Averill

Spectrum of Open Information Exchange Needs Over Time

Shape of Song, Martin Wattenberg

Physical WorldDigital World

Before After

Now

Spectrum of Open Information Exchange Needs Over Time

Shape of Song, Martin Wattenberg

Physical WorldDigital World

Before After

Now

Change Belt

Spectrum of Open Information Exchange Needs Over Time

Shape of Song, Martin Wattenberg

Physical WorldDigital World

Before After

Now

Change Belt

Replace Fan Coil Unit

Spectrum of Open Information Exchange Needs Over Time

Shape of Song, Martin Wattenberg

Physical WorldDigital World

Before After

Now

Change Belt

Replace Fan Coil Unit

UpgradeHVAC System

Shape of Song, Martin Wattenberg

Physical WorldDigital World

Before After

Now

Immediate Example: Standard Floorplans for Emergency Response

Long Term Example: Sustainable CleanWater

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

Code Mapping Templates Based on Building Type and Location

Code Mapping Templates Based on Building Type and Location

Service of BuildingsVs Building Types

GeometricBoundaries ofAHJs

Systematic Exchange

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

Firemans Digital KeyboxA work in progress for Building Emergency Response Scenario commentsBy Deborah MacPherson, Specifications and Research WDG Architecture, Projects Director Accuracy&AestheticsDebmacp@gmail.com

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

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.

Suggested Areas of Responsibility Suggested Areas of Responsibility

Space

Natural Asset

Linear Structure

Structure

Building

Facility / Built

Theatre / World

Sub-SystemsSystem

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

Overlay

Components

Components

City

GISTC 211

IFCISO/PAS 16739TC184/SC4

ProcessISO 15926TC184/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

Focus on 10 Types

David Coggershall Volunteer Program “We’re here to help you with your building documentation”

Swirling data togetherGetting it to grow certain ways

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 LayerA lightweight, subject concept reference structure for the Web

The Hairnet Over the BasketballMike Bergman. Zeitgisthttp://www.umbel.org/role.html

20,000 Docking Ports for an Open World

Zitgist is pleased to host this demo sandbox.

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

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

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

Coverage, Reference Points, and New OPS Time Clock

Coverage, Reference Points, and New OPS Time Clock

Smart GridSmart Grid

Coverage, Reference Points, and New OPS Time Clock

Smart GridSmart Grid

Open SVGOpen SVG

Coverage, Reference Points, and New OPS Time Clock

Smart GridSmart Grid

Open SVGOpen SVG

Tracking and Negotiating Tools for the General PublicEX: Sustainability, Water Rights, Improved ServicesTracking and Negotiating Tools for the General PublicEX: Sustainability, Water Rights, Improved Services