NIEM is a data exchange model used across federal, state, local, and tribal governments. Business Architecture Committee (NBAC) June 2009 through November 2013. OmniClass facility types built in to advance public safety.

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 00nc:FacilityType
A data type for a building, place, or structure that
provides a particular service.
11 00 00 00nc: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:
OrganizationOperatesFacilityAss
ociation / Type
34 00 00 00
nc:
OrganizationSupervisesFacilityAs
sociation / Type
34 00 00 00
nc:FacilityPersonAssociation /
Typenc:
PersonResidesAtFacilityAssociati
on / Typenc:
PersonWorksAtFacilityAssociatio
n / Type
11 00 00 00nc: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:
OrganizationOperatesFacilityAss
ociation / Type
34 00 00 00
nc:
OrganizationSupervisesFacilityAs
sociation / Type
34 00 00 00
nc:FacilityPersonAssociation /
Type
11 00 00 00nc: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

27. 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?

28. Define 3 Facility Types
Civil / Justice Hospital / Healthcare K-12 / University

29. Thank You
Contact Information
Deborah MacPherson
Specifications and Research
Cannon Design
dmacpherson@cannondesign.com
703 907 2353