OpenFloorPlanDisplay

Parent Page BuildingServicePerformance    (1WEO)

Child Page FloorplanMarkupLanguage    (1WEP)

Standards bodies    (1WEQ)

• NEMA SB30    (1WER)
• NFPA 1620    (1WES)
• ISO 16739, 15926,10303, 12006, 11179    (1WG9)
• Relevant standards by    (1WEU)
  • ASTM    (1WEV)
  • UL    (1WEW)
  • ASHRAE    (1WEX)
• NIST Policy on Traceability.    (1WGA)

Use cases    (1WF1)

• Undertaken by San Francisco Map Lab    (1WF2)
  • Open Floor Plan Display Intro Video    (1WF3)
  • OFPD Demonstration Siterequires Firefox, contact for password    (1WF4)
  • OFPD Project Prospectus    (1WF5)
• Sample Comparison of a Facility Type - Healthcare    (2BGN)
  • Omniclass 11 versus Sutter Health    (2BGO)
    • Hospital-----------Hospital    (2BH4)
    • Clinic-------------Express Care Clinics    (2BH5)
    • Rehabilitation-----Cancer Centers    (2BH6)
    • Geriatric----------Ambulatory Surgery    (2BH7)
    • Psychiatric--------Long Term Care Centers    (2BH8)
    • Maternity----------Research Institutes    (2BH9)
    • Veterinary---------Home Health and Hospice    (2BHA)

Demonstration of benefits/impacts    (1WF6)

• San Jose Water Company Emergency GPS Tracking    (1WF7)
• NIST BFRL Building Emergency Response Scenario    (1WF8)
• Project Specific Scenario: Adequate knowledge of the layout of a hospital is needed in emergency response:    (1WF9)
  • to a fire or security incident within the hospital facility    (1WFA)
  • to a mass casualty incident where the capacity of the hospital is exceeded services.    (1WFB)
• Scenario: St. Mary's Hospital as Generic Hospital System Case Study    (1WFC)
  • Location: San Francisco    (1WFD)
  • Objectives: Formal EXPRESS, UML, OWL based Ontologies for Terminologies & Requirements.    (1WFE)
    • Discover Existing Information Resources & Techs - [IFCs] [BIEFER (NIST)]    (1WFF)
    • Utililize OmniClass space types to describe interior space polygons    (1WFG)
      • Develop Requirements for Open Floor Plan Display Ontology;    (1WFH)
        • Space Names Taxonomy (e.g. Entrance, Foyer, etc);    (1WFI)
        • Function Names Taxonomy (e.g. Emergency Intake, etc);    (1WFJ)
        • Building Feature Names Taxonomy (e.g. Standpipes, etc);    (1WFK)
      • Develop Requirements for Building Information Response Services;    (1WFL)
        • Sensor Reporting Information;    (1WFM)
        • Alarm Systems;    (1WFN)
        • Evacuation Plans;    (1WFO)
      • Develop Requirements for Building Energy Information Ontology;    (1WFP)
      • Develop Requirements for Building Water Information Ontology.    (1WFQ)
    • Fire in Hospital - Access to Floor Plan Based Common Operating Picture    (1WFR)
      • Survey Existing Building Information Resources    (1WFS)
      • Develop Requirements Ontology    (1WFT)
    • Use of Emergency Data Exchange Language (EDXL) Hospital AVailability Exchange(EDXL-HAVE) in St. Marys during Mass Casualty Emergency Incident    (1WFU)
      • Discover Reporting Systems ability to assemble Time-Critical Capabilities Snapshot    (1WFV)
• Additional Considerations:    (1WFW)
  • OASIS Common Alerting Protocol CAP used for emergency alerts    (1WFX)
  • EDXL-DE used to package and route Emergency Message Payloads such as    (1WFY)
    • EDXL-HAVE in IP Messaging    (1WFZ)
    • EDXL-RM used for resource logistics information exchange.    (1WG0)

Existing ontologies    (1WG6)

• A complete survey and interoperability matrix will be a deliverable.    (1WG7)