Framework for mapping systems to spaces and spaces to floor plans (2O1S)
- Call Convener: DeborahMacPherson (2O17)
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)
- Moderator DeborahMacPherson (2NY3)
- Brief Introductions (2NY4)
- Framework Concept - TobyConsidine (2NY5)
- Green Building Energy Demo - MikeLavelle (2NYY)
- Fire Alarm Context - RodneyFox (2NYZ)
- Open Floor Plan Demo - DavidCoggeshall (2NZ0)
- BIM-GIS-EM-FM Integration - KimonOnuma (2NZ1)
- Group Discussion (2NZ2)
Attendees (2O1T)
- Attended: (2O1A)
- DeborahMacPherson, Cannon Design (2NYC)
- ChuckBrands, Green Building Energy (2NYD)
- DavidCoggeshall, Golden Gate Safety Network (2NYE)
- FinithJergnigan, Design Atlantic (2NYF)
- KimonOnuma, Onuma Systems {nid 2NNE}D} (2NYG)
- Michael Hauck (2NYH)
- MichaelLavelle, Levelle Energy (2NYI)
- MichelleRaymond (2NYJ)
- RodneyFox, iLinkx (2NYK)
- ThomasDalbert, Onuma Systems (2NYL)
- TracyPaladino Cannon Design (2NYM)
- TobyConsidine (2NYN)
- Anticipated: (2O1B)
- BobSmith (2NYR)
- DavidCoggeshall, Golden Gate Safety Network (2O1U)
- DeborahMacPherson, Cannon Design (2O1V)
- DougPoffinbarger, Green Building Energy (2NYS)
- ChuckBrands, Green Building Energy (2O1W)
- FinithJergnigan, Design Atlantic (2O1X)
- KimonOnuma, Onuma Systems {nid 2NNE}D} (2O1Y)
- LizChodosh Cannon Design (2NYP)
- MichaelLavelle, Levelle Energy (2O1Z)
- Michael Hauck (2O20)
- MichelleRaymond (2O21)
- RexBrooks - Ontolog Meeting Champion same time? (2NYQ)
- RodneyFox, iLinkx (2O22)
- TobyConsidine (2O23)
- ThomasDalbert, Onuma Systems (2O24)
- TracyPaladino Cannon Design (2O25)
- YongKuKim, Onuma Systems (2NYT)
- Regrets: (2O26)
- PeterHourihan Cannon Design (2NYV)
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)
- Response to smart energy data (2NZB)
- Understanding next generation LEED models (2NZC)
- Buildings reconfiguring themselves based on the energy needs and energy market (2NZ5)
- Users of energy made aware of their energy consumption (2NZ6)
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)
- Neither fully supports energy model needs (2O2D)
- Neither has gone through NTTAA (National Technology Transfer and Advancement Act) process. (2O2E)
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)
- No presentation. Content will be covered by Kimon. (2O2G)
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)
- iLinkx is in a cloud and supports the customer w/ system infrastructure. This customer can be a small building or smaller budget organization such as a pizza parlor or a school complex. (2NZG)
- iLinks receives alarm from the building and sends out text message with an attached pdf file. The pdf can show where the alarm is located on a floor plan map. (2NZH)
- The message is CAP (Common Alerting Protocol) compliant. (2O2K)
- iLinkx is supplementary signaling NFPA 72 code-compliant - Supplemental transmission systems are noted in the NFPA 72 standard. (2NZI)
Additional message features: (2O2L)
- Can send the alert to designated recipients via a standard cell phone/Blackberry device as a SMS message. (2O2M)
- Can send the alert to designated recipients' smart phones w/ the PDF attachment. (2NZJ)
- Can send to a service vehicle's laptop or other IP based visual display (2O2N)
The laptop display will be as secure as an email box that requires a login. (2NZK)
About the pdf file: (2O2O)
- When you click on the pdf attachment, the file opens for display (2O2P)
- iLinkx reduces the file size substantially (2O2Q)
- The graphics have no visual distortion as you zoom in or pan on the image (2O2R)
- The image has no white space margins (2O2S)
- The level of detail can be zoomed repeatedly and retain the image quality (2O2T)
- The lag time in zoom and restore is nearly instantaneous (2O2U)
- There is no blinking capability so a heavy border box surrounds the alarm icon and its location on the floor plan map (2NZL)
iLinkx motto is that life can change in the blink of an "i". (2O2V)
- It takes 15-20 seconds to build the image. (2O2W)
- To get to additional displays, links may be embedded in the pdf. The links can go to any IP available address: ex: webpage, camera feed, audio message, web-application. (these can require a login). {nid 2NZM} Examples: (2O2X)
- Link to a map with arrows showing exit paths or a map of protected "safe" areas within a floor plan. (2O2Y)
- If want a ladder truck to see an external view of the building, link to an exterior building image that has a highlighted box where the truck may be needed for building access. (2NZO)
- Connect to prerecorded audio messages. (2O2Z)
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)
- After input of password goes to the control panel for the boiler (2O31)
- The top of the display shows the current data with a timestamp (2NZR)
- Button navigation can take you to detail pages or camera feeds (2O32)
Cost: (2O33)
- The end user bears the cost of the display. (Note: not certain what this statement means.) (2O34)
- The fire responder just needs to have a designated email address. (2NZS)
- Graphic fee - $49 per page and $2? per sensor contact setup, plus $3 per month service fee. (2NZT)
Open Floor Plan Demo - DavidCoggeshall (2O6L)
Golden Gate Safety Network (2O6M)
- Provides standards based demonstrations (2O6N)
- SVG based so supported by most modern web browsers, including IE9 (2NZU)
Open Floor Plan began after a BIEFR NIST workshop in 2008 (2NZV)
The GGSN Portfolio pages has: (2O6O)
- In the left column, a link to a presentation on Open Floor Plan given at USF (2NZW)
- In the center column, a link to the Open Floor Plan demonstrations (2O6P)
- Genentec Mapps can be seen by clicking the V in the title of the demonstrations page (2O6Q)
The demonstrations: (2O6R)
- floor plan maps have area designator polygons (2O6S)
- interface will show the room identifiers as you scroll the mouse over the polygons (2O6T)
- clicking in a room's polygon will produce a pop-up with more room information (2O6U)
- the rainbow colors fill the smart polygons based on the room classification. (2O6V)
- this is done dynamically through JavaScript (2O6W)
- runs through the list of all room polygons to assign colors (2NZX)
USF demo take aways: (2O6X)
- Programmable display is lightweight and cost free (2O6Y)
- JavaScript based (2O6Z)
- Floor plans of each floor can be accessed (2NZY)
- The viewer shows the A,B,C and D oblique views of the building sides (2NZZ)
- The incident commander designates the "front" of the building for an incident as "A" (2O70)
- The floor plan can show the polygon for the room/zone in red for where the alarm went off (2O00)
- On the site plan, the hydrants or other site resources can be highlighted and provide more info in a pop-up window (2O71)
UCSF display take aways: (2O72)
BIM-GIS-EM-FM Integration - KimonOnuma' {nid 2O29} Onuma System (2O03)
- Web-based, cloud-based system that facilitates real-time collaboration (2O74)
- From Room to Site level details - BIM to GIS (2O75)
- Clients are all web based. (2O76)
- Uses both SVG and Flash (2O04)
- Every visual object has a (Lat, Lon) down to the equipment in a bldg. (2O05)
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)