Framework for mapping systems to spaces and spaces to floor plans    (2O1S)

Thursday February 17 Noon to 2pm EST (9 to 11 am PST)    (2NY1)

Please note anyone may edit the contents here through their Ontolog wiki account (if you don't have one it is easy to set one up). Please feel free to fix any errors in these notes or add additional comments.    (2O18)

Agenda    (2NY2)

Attendees    (2O1T)

Notes    (2O27)

Notes will be cleaned up and updated    (2O28)

Presentations:    (2O2A)

Framework Concept - TobyConsidine    (2NZ3)

We need a framework to support information exchange about 3D space with systems and services in and for buildings.    (2NZ4)

Framework to support:    (2NZA)

Energy usage cannot be understood by building inhabitants if the information they are given is by equipment name (chiller 7, roof top unit 3). Building occupants relate to their environment by space (conference room 3301, Joe's office)    (2NZ7)

We need a lightweight BIM to show how things relate to each other within building spaces.    (2NZ8)

Current standards that are close to meeting the need: BIMXML, and GBxml    (2O2C)

Standards development must be an open collaborative process.    (2NZD)

The question we need to address with a framework is: How do we get from the building systems information to the building spaces to Open Floor Plan Display?    (2NZE)

Green Building Energy Demo - MikeLavelle    (2O2F)

Fire Alarm Context - RodneyFox    (2O2H)

Architecture of how iLinkx functions. (Notes on this topic are missing in places due to working through technical difficulties during the presentation - please feel free to flesh out this or any other part of these notes.)    (2O2I)

Alarms in graphic display have been around for many years - typically customer is a proprietary site using a proprietary system at a large site or big business.    (2O2J)

Additional message features:    (2O2L)

The laptop display will be as secure as an email box that requires a login.    (2NZK)

About the pdf file:    (2O2O)

iLinkx motto is that life can change in the blink of an "i".    (2O2V)

When using a web browser front end, the standard navigation buttons work (example: the back button.)    (2NZN)

iLinkx in the energy domain iLinkx boiler demo:    (2O30)

Cost:    (2O33)

Open Floor Plan Demo - DavidCoggeshall    (2O6L)

Golden Gate Safety Network    (2O6M)

Open Floor Plan began after a BIEFR NIST workshop in 2008    (2NZV)

The GGSN Portfolio pages has:    (2O6O)

The demonstrations:    (2O6R)

USF demo take aways:    (2O6X)

UCSF display take aways:    (2O72)

BIM-GIS-EM-FM Integration - KimonOnuma' {nid 2O29} Onuma System    (2O03)

Buildings are constantly changing - so want to keep the plans up to date.    (2O06)

IFC complexity sometimes gets in the way of display.    (2O07)

Apps for iphone and android.    (2O08)

Work to connect real-time data visualization, sensor data access... supported through web services.    (2O09)

Google Earth can connect to the data from the Onuma System.    (2O0A)

System tracks the design and display of spaces through simple update tools.    (2O0B)

Can connect to other systems via web services (energy, community college database, GIS data, demographics data, emergency shelter locations.    (2O0C)

Updates of buildings or maps can be done through live connections via the web.    (2O0D)

With the right access level you can view or edit the interface.    (2O0E)

Onuma system can pull data from other servers (ex: Washington D.C. arc GIS server)    (2O0F)

Zoom can go from the satellite to a piece of equipment within a room.    (2O0G)

Don't think of building data as static. They may be changing and updated real-time (sensor data, layout of rooms...)    (2O0H)

Example: Graphic display may have a background gif with overlaid spaces and sensor locations. Viewer can be live or can pull-up a preset view.    (2O0I)

Data for this demo is from the Onuma server but it can be a mash-up with floorplan data from Onuma server pulling in data from Levelle energy or other web-services. The combined graphic is dynamic.    (2O0J)

The sensor could have the real-time value sent to system and the core system may have the appropriate range data, triggering an email when the sensor goes out of range.    (2O0K)

Pricing is multi-leveled: free viewer editor view is $45 a month per user. With reduced rates for multiple editors.    (2O0L)

For the fire responder - free viewer.    (2O0M)

Can you do multiple levels of access view? - can give someone a link to just a publicly accessible link.    (2O0N)

SOAP and REST connections are feasible.    (2O0O)

Can pull data from the Onuma system into other systems (local filemaker....)    (2O0P)

Consider floor plans as dynamic as sensor data. Example: update views for renovation of a building as it is being completed.    (2O0Q)

Discussion:    (2O0R)

Need a neutral floor plan format.    (2O0S)

Cannon Design has taken on some facilities management work.    (2O0T)

bSA for down the road direction    (2O0U)

consider California Community College district data for digitization of floor plans and connecting to other data.    (2O0V)

FEMA has some funding for interoperability and school data.    (2O0W)

At DMI there are MOUs with Dept of Pub Health, Cal EPA, and others to get to data but not allowed to show some of it publicly.    (2O0X)

All spaces would have an identifier and data (including geometry) could be updated, at least partially, automatically.    (2O0Y)

Consider Small Business Innovation proposal to DHS.    (2O0Z)

There is a DHS BAA rolling funding process with an initial 5 page whitepaper request.    (2O10)

iLinkx is currently used in 12 different states within border protection vault buildings. Some of the systems in the buildings were quite old, so connecting with legacy systems was appropriate.    (2O11)

Framework for energy Existing facilities have multiple control systems.    (2O12)

Finith and Kimon to put together a case study approach.    (2O13)

Connections through web services.    (2O14)

For emergency notification this would be a supplemental communication according to NFPA 72.    (2O15)

Discussion:    (2O1E)

Next Steps:    (2O1F)