Your SlideShare is downloading. ×
  • Like
NIEM for NBAC
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Now you can save presentations on your phone or tablet

Available for both IPhone and Android

Text the download link to your phone

Standard text messaging rates apply

NIEM for NBAC

  • 919 views
Published

 

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
919
On SlideShare
0
From Embeds
0
Number of Embeds
1

Actions

Shares
Downloads
21
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • Slides for NIEM . Seminar organized by Jim Pingel Meeting held at
  •     Can NIEM be used by an organization to harmonize data and standardize naming conventions for a logical data model not only regarding outside data transfers but within the individual entity itself   At the minimum, you need to consider your information exchange requirements as a proper subset of your future state enterprise information architecture. While considering national standards, I think it's important to add that your own unique enterprise requirements need to "drive the show" and take precedence where applicable -- in that we can't sacrafice an important enterprise information requirement, at the expense of NIEM standardization. Mitchell Ummel Owner and President/CEO, UmmelGroup International, Inc.   ______________   a) You can take any schema import it into a template and then use the Tools / Create dictionary to make NIEM-style dictionaries. b) You can run the Template Evalution tool to apply NIEM-style NDR rules to check your names and type definitions for conformance. c) You can use the Renamer utility to rename everything to NIEM conformance. d) You can import an XSD of a data model from a tool such as ERwin - build a generic template of all those entities and then check your namings and types in the model and create dictionary from that. David R.R. Webber Enterprise Architect & Project Manager; CTO OpenVotingSolutions Inc; XML visionary; ebXML / NIEM & eBusiness advocate   ______________   Data standardization for an external information exchange or external service interface architecture (NIEM) needs to be distinguished from an internal enterprise data or information architecture that is a proper component of enterprise software systems architecture. NIEM IEPDs standardize the external data interfaces as well as help to provide some lifecycle process methodology for external system exchanges that is often lacking at many organizations not focussed on IT systems as their primary mission. James Otis Systems Engineer at Z-Otis Associates Inc.
  •   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.    
  • Global Office locations, Gary McLeod and Liz Chodosh for BIMForum http://www.bimforum.org/  
  • http://www.geographicguide.com/north-america-map.htm  
  • http://lehdmap3.did.census.gov/
  • Country2008 Census PopulationTypeMunicipalityState / ProvinceZip BuildingsEmergency        (Typ. Fire)Public Safety   (Typ. Police) USA 1609,023City Boston Mass.02114Inspection ServicesCity of Boston Fire DepartmentCity of Boston Police DepartmentCity of Boston Maps GISEmergency Medical ServicesB-SMART InitiativeHousing AuthorityEmergency Preparedness Redevelopment Authority   Water and Sewer Commission   Public Health Commission           Zoning    USA 18,363,710City New York City New York10017Dept of BuildingsFDNYNYPDUSA 216,626,000MetroNew York City MetroBuildings Information SystemOffice of Emergency ManagementPublic Safety Answering CenterNYCityMap GIS Dept. of IT and Telecomm.Citywide Incident Management SystemFaçade Law EnforcementDepartment of (Building) InvestigationsIncident Monitoring   Buildings Enforcement Safety TeamField Operations   Buildings Special Investigations UnitVehicles   Certificate of Occupancy OfficeEmergency Operations Center Construction InspectionsPublic Information   LandmarksRecovery and Relief   Elevator, Escalator, Amusement Rides    Environmental Control   Plan Examination   Special Projects   Waterfront Permitting   Landmarks   Property Information           Zoning    USA 1636,919City Baltimore  Maryland 21201Permits & Building InspectionsCity of Baltimore Fire DepartmentCity of Baltimore Police DepartmentUSA 2785,618CountyBaltimore CountyEnterprise Geographic Information System Office of the Fire MarshallCriminal Justice DepartmentPlanningOffice of Emergency Management         Zoning   
  • Try an exercise, similar to Golden Gate Safety Network's Common Operating Picture, or Onuma Planning System BIM storm

Transcript

  • 1. FACILITY STANDARDS and NIEM National Information Exchange Model (NIEM) Business Architecture Committee 21-22 July 2009 Deborah L. MacPherson Specifications and Research, Cannon Design, NBIMS Ad-hoc Multihop by the University of Aachen Communication and Distributed Systems Department
  • 2. First Heard of NIEM through NIST ~ wonder   What fills in:   Building UsageText ?   Building Type - Description ?   Image courtesy Scott Parker IJIS, Data Elements Resolution Effort
  • 3. 11 00 00 00 nc:FacilityType A data type for a building, place, or structure that provides a particular service. 11 00 00 00 nc:FacilityIdentification / Type An identification assigned to a facility. nc:FacilityAssociation / Type A data type for an association between facilities. nc:FacilityDocumentAssociation / Type An association between a facility and a document nc:FacilityImageAssociation / Type An association between a facility and an image 34 00 00 00 nc:FacilityOrganizationAssociation / Type An association between a facility and an organization 34 00 00 00 nc:OrganizationOperatesFacilityAssociation / Type 34 00 00 00 nc:OrganizationSupervisesFacilityAssociation / Type 34 00 00 00 nc:FacilityPersonAssociation / Type nc:PersonResidesAtFacilityAssociation / Type nc:PersonWorksAtFacilityAssociation / Type 11 00 00 00 nc:FacilityName / Type A name of a facility 11 00 00 00 nc:FacilityCategoryText / nc:TextType A kind of facility 11 17 00 00 nc:FacilityCommercialIndicator / niem-xsd:boolean True if a facility is for commercial purpose; false otherwise nc:FacilityLocation / nc:LocationType 34 00 00 00 nc:FacilityContactInformation / nc:ContactInformationType A method of contact for a facility First Step: NIEM Facility Subset Extraction
  • 4. 11 00 00 00 nc:FacilityType A data type for a building, place, or structure that provides a particular service. 11 00 00 00 nc:FacilityIdentification / Type An identification assigned to a facility. nc:FacilityAssociation / Type A data type for an association between facilities. nc:FacilityDocumentAssociation / Type An association between a facility and a document nc:FacilityImageAssociation / Type An association between a facility and an image 34 00 00 00 nc:FacilityOrganizationAssociation / Type An association between a facility and an organization 34 00 00 00 nc:OrganizationOperatesFacilityAssociation / Type 34 00 00 00 nc:OrganizationSupervisesFacilityAssociation / Type 34 00 00 00 nc:FacilityPersonAssociation / Type nc:PersonResidesAtFacilityAssociation / Type nc:PersonWorksAtFacilityAssociation / Type 11 00 00 00 nc:FacilityName / Type A name of a facility 11 00 00 00 nc:FacilityCategoryText / nc:TextType A kind of facility 11 17 00 00 nc:FacilityCommercialIndicator / niem-xsd:boolean True if a facility is for commercial purpose; false otherwise nc:FacilityLocation / nc:LocationType 34 00 00 00 nc:FacilityContactInformation / nc:ContactInformationType A method of contact for a facility OmniClass Table 11 could work in NIEM
  • 5. I believe the simple answer to Deborah's question is certainly "YES." OmniClass codes for buildings and facilities could easily fit into NIEM. All we really need are the unique code values, definitions for each, and the name for the data type that will carry these enumerations (the codes).     Question Reference #090526-000000 ---------------------------------------------------------------   Product Level 1: NIEM   Category Level 1: Technical Questions   Category Level 2: Model Structure   Category Level 3: Namespaces      Date Created: 05/26/2009 09:43 AM      Last Updated: 05/26/2009 11:25 AM            Status: Escalated
  • 6. http://manyeyes.alphaworks.ibm.com/manyeyes//manyeyes/visualizations/nbims-background National Building Information Modeling Standard  (NBIMS) is a Work in Progress - OmniClass is One Component
  • 7. 11 00 00 00 nc:FacilityType 11 00 00 00 nc:FacilityIdentification / Type nc:FacilityAssociation / Type nc:FacilityDocumentAssociation / Type nc:FacilityImageAssociation / Type 34 00 00 00 nc:FacilityOrganizationAssociation / Type 34 00 00 00 nc:OrganizationOperatesFacilityAssociation / Type 34 00 00 00 nc:OrganizationSupervisesFacilityAssociation / Type 34 00 00 00 nc:FacilityPersonAssociation / Type 11 00 00 00 nc:FacilityName / Type 11 00 00 00 nc:FacilityCategoryText / nc:TextType 11 17 00 00 nc:FacilityCommercialIndicator / niem-xsd:boolean nc:FacilityLocation / nc:LocationType 34 00 00 00 nc:FacilityContactInformation / nc:ContactInformationType Census OnTheMap could work in NIEM Namespace Prefix: census URI: http://niem.gov/niem/census/2.0 Schema Location: http://niem.gov/niem/census/2.0/census.xsd nc:PersonResidesAtFacilityAssociation / Type nc:PersonWorksAtFacilityAssociation / Type
  • 8. GML has a place in NIEM Namespace Prefix: gml URI: http://niem.gov/niem/external/ogc-gml/3.1.1/dhs-gmo/1.0.0 Schema Location: http://niem.gov/niem/external/ogc-gml/3.1.1/dhs-gmo/1.0.0/gml.xsd Description: A profile of Geography Markup Language (GML) version 3.1.1 schemas for niem. See http://www.opengeospatial.org for documentation, http://schemas.opengis.net/gml/ for schemas./
  • 9. EDXL has a place in NIEM Namespace Prefix: edxl URI: http://niem.gov/niem/edxl/2.0 Schema Location: http://niem.gov/niem/edxl/2.0/edxl.xsd Description: Emergency Data Exchange Language Types in Namespace edxl:ContentCategoryCodeSimpleType edxl:ContentCategoryCodeType edxl:ResponseCodeSimpleType edxl:ResponseCodeType Namespace Prefix: de URI: urn:oasis:names:tc:emergency:EDXL:DE:1.0 Schema Location: http://niem.gov/niem/external/de/1.0/de.xsd Description: This Distribution Element specification describes a standard message distribution framework for data sharing among emergency information systems using the XML-based Emergency Data Exchange Language (EDXL). This format may be used over any data transmission system, including but not limited to the SOAP HTTP binding. Namespace Prefix: edxl-cap URI: http://niem.gov/niem/edxl-cap/2.0 Schema Location: http://niem.gov/niem/edxl-cap/2.0/edxl-cap.xsd Description: Common Alerting Protocol
  • 10. Data Owner Metadata has a place in NIEM Agency ID Data Item ID Data Item Status Persons Full Name System ID Organization name Contact Details Text Dissemination Criteria Text   Data Submitter Metadata has a place in NIEM Contact Details Text Organization Name Persons Full Name System ID Agency ID     Exchange Metadata has a Placeholder
  • 11. Try Facility Exchanges Using NBIMS Hierarchy Note: Move through the next 12 slides quickly
  • 12. The scenario begins in a large commercial building
  • 13. at 321 Prince Street
  • 14. in a section of the third floor
  • 15. that is undergoing renovation . Contractors left out some vapor-producing chemicals that have ignited after-hours, producing a small explosion and starting a fire.
  • 16. The explosion disables the smoke alarm in the room
  • 17. but this generates a trouble condition at the fire panel .
  • 18. The fire panel generates a Common Alerting Protocol CAP alert CAP has a place in NIEM Namespace Prefix: cap URI: urn:oasis:names:tc:emergency:cap:1.1 Schema Location: http://niem.gov/niem/external/cap/1.1/cap.xsd Description:  Common Alerting Protocol (CAP) is a simple but general format for exchanging effective warning messages based on best practices identified in academic research and real-world experience.
  • 19. The alert is then passed to the subscribing central station alarm ( CSA ) company Demonstrated in Richmond VA Milestone Reached in Alarm Data Transmission Successful Conversion to National Information Exchange Model   The Public Safety Data Interoperability (PSDI) Program announces the successful conversion of the External Alarm Interface Information Exchange Packet Documentation (IEPD) to the National Information Exchange Model (NIEM) Version 2.0. NIEM is designed to develop, disseminate, and support information sharing standards and processes across the whole of the public safety, justice, emergency and disaster management, intelligence, and homeland security enterprise at all levels and across all branches of government. The PSDI program and the IEPD conversion project were funded by the Bureau of Justice Assistance , US Department of Justice . The PSDI program is co-managed by the IJIS Institute and the Association of Public-Safety Communications Officials (APCO) International . The External Alarm IEPD has been in development since 2004, and has been tested extensively through partnerships with APCO International , York County, Virginia, Emergency Communications Division , City of Richmond, Virginia, Department of Information Technology and Richmond Police Department’s Division of Emergency Communications , the Central Station Alarm Association (CSAA) , and Vector Security . The purpose of the External Alarm Interface IEPD is to provide a standard data exchange for electronically transmitting information between an Alarm Monitoring Company and a Public Safety Answering Point (PSAP). There are three primary uses for this IEPD: initial notification of an alarm event, bi-directional update of status between an alarm monitoring company and the PSAP, and bi-directional update of other events between an alarm monitoring company and a PSAP. The upgrade of the exchange from the Global Justice Data XML Model (GJXDM), a reference model for the exchange of information within public safety and justice communities, to NIEM 2.0 enables the emergency communications community to more easily adopt NIEM as a national data exchange standard.
  • 20. that monitors the building
  • 21. Upon receipt at the CSA, a representative attempts to contact the building personnel to verify the alert (smoke alarm trouble in room 310)
  • 22. While the CSA representative follows procedures to verify the alert, another alert arrives
  • 23. reporting a smoke alarm from the hallway outside 310
  • 24. 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 Progress Stopped
  • 25.  
  • 26. No Consistent Authority Having Jurisdiction (AHJ) Contact Cannon Design Offices AHJ Survey
  • 27. Zoom Representation to Real Maps of North America
  • 28. Select  3 Cities Get Census Data
  • 29. Note the Differences Between City Departments
  • 30.  
  • 31. nc:FacilityType nc:FacilityIdentification / Type nc:FacilityAssociation / Type nc:FacilityDocumentAssociation / Type nc:FacilityImageAssociation / Type nc:FacilityOrganizationAssociation / Type nc:OrganizationOperatesFacilityAssociation / Type nc:OrganizationSupervisesFacilityAssociation / Type To Resolve: Began the Facility Standards IEPD External Emergency Geometry Foundation FPML Static FPML Dynamic FPML Fire Department OmniClass Building Codes Open Geospatial Scale & Units of Measure Foundation & Geometry
  • 32. FPML Static Need a Demo to Get this IEPD to Work OntologWiki: Floorplan Markup Language
  • 33. FPML Static FPML Dynamic Namespace Prefix: ifc URI: http://niem.gov/niem/external/iai-ifc/RC2/ifc/dhs-gmo/1.0.0 Schema Location: http://niem.gov/niem/external/iai-ifc/rc2/dhs-gmo/1.0.0 /IFC2X2_FINAL . xsd Description: International Foundation Classes (IFC) Schema by the International Association for Interoperability (IAI). See http://www.iai-international.org and http://www.iai-na.com/ for documentation and schemas. IFC2x Edition 4
  • 34. Define 3 Levels of Detail 1. Public Data Example: Address Google Maps 2) Inside the Building Owner coordination with local Authorities Having Jurisdiction (AHJ) Example: Fire and Police Departments 3) Full connections to NG9-1-1 Agency wide, nationwide planning/coordination Example: Which jail was the  prisoner taken to?
  • 35. Define 3 Facility Types   Civil / Justice        Hospital / Healthcare      K-12 / University
  • 36. Emergency
  • 37. External The Best Standards Are Built-In
  • 38. Thank You     Contact Information Deborah MacPherson Specifications and Research Cannon Design [email_address] 703 907 2353