DOT Implementing the Surface Transportation Domain Daniel Morgan 26 October 2015

What is NIEM? NIEM a community-driven, government-wide, standards-based approach to exchanging information NIEM connects communities of people who share a common need to exchange information in order to advance their mission. 2 NIEM provides a Common Language NIEM users at Federal, State, Local, Tribal and Private Sectors define agreed upon terms, definitions, and formats - independent of the way information is stored in individual agency systems NIEM provides a Structured Approach NIEM provides a repeatable, reusable process for business users to document information exchange requirements in an implementation ready format

How is NIEM structured? NIEM is made up of NIEM Core and Domains – NIEM Core contains elements common to all domains – Domains are based on mission areas 3

How does NIEM help? 4

How does a domain operate? Domains have two key artifacts: – Domain data model - a set of data elements and definitions specific to the NIEM mission area that are used to build information exchanges – Information Exchange Package Descriptions (IEPDs) - a set of valid XML schemas that may include portions of NIEM Core schemas, portions of domain schemas, enterprise-specific or IEPD-specific extension schemas The Community of Interest organizes workshops to manage and update the domain data model Exchange partners put the data model into action by developing IEPDs 5

What is the status of the domain? Formal approval of surface transportation domain is complete – NIEM Business Architecture Committee (NBAC) unanimously approved on June 30, 2015 – NIEM Executive Steering Council (ESC) unanimously approved on August 19, 2015 – NIEM Domain Stewardship Agreement signed on September 9, 2015 Domain content development is in process 6

What is the timeline? NIEM follows a versioning scheme – The next release of NIEM (version 3.2) will occur in June 2016 – Input for that release is due November PhaseDescriptionTime Period Input deadline Major domain content additions, changesNov 2, 2015 Alpha Phase Major domain content additions, changes Integrate domain updates and make code table updates Internal domain and committee review Last chance to raise new, subjective issues New issues, bugs, harmonization, public requests Nov 2015 – Feb 2016 Beta Phase Minor domain content additions, changes Internal and public review of 3.2 changes, bugs Minor new issues; harmonization work NBAC vote and NTAC review Feb 2016 – Apr 2016 Release Candidate Phase Internal and public conformance reviews and bug fixes Funnel status: Conformance errors and bug fixes only May ReleaseJune 2016

What content will be included? Existing external standards and guidelines – ANSI D20 is already available in NIEM – FIPS codes and other building blocks are already available in NIEM Updates to MMUCC elements to reflect MMUCC4 – Most MMUCC elements are part of an “external guideline” that is expressed in NIEM and will remain there – Some MMUCC elements (e.g., roadway) will be a part of surface transportation 8

How will content be governed? Maintain existing governance processes for standards and guidelines – Governance for standards like ANSI D16 and ANSI D20 follow the processes established by the relevant standards development organization(s) – Governance for guidelines like MMUCC and MIRE follow existing processes through NHTSA and FHWA programs As standards and guidelines are adopted/ updated, DOT rolls content into next logical NIEM version 9

How to get involved? If you have XML-based exchanges for your traffic records data, consider making them NIEM- conformant If you don’t have XML-based exchanges, give NIEM a try! If your State participates in any NIEM domains, connect with your partners 10

Where to learn more? Learn about information exchanges – Exchange.aspx Exchange.aspx Get training – Ask us anything! – 11