MILOPS DOMAIN & NIEM V3.0 MAY 03, 2013

DOD CIO MEMO Where is NIEM adoption by DoD codified? 2

DOD CIO MEMO / JS J6 JSAP

MILOPS DOMAIN CREATION What is the MilOps Domain process and high level architecture? 4

approves used to develop forms new MILOPS DOMAIN PROCESSES Technical Specifications Data Model Developer Support Restricted MilOps Data Model Public MilOps Data Model provides basis for Governance sharing technical & content requirements & solutions ESC NIEM PMO NBAC NTAC NCOC NIEM Domains MilOps Interim Governance Structure 1 Public IEPDs Restricted IEPDs 6 used to develop forms new forms new restricted domain model IEPDs Tools: SSGT/ ConTesA - Worked Examples - Outreach Restricted Public

NIEM HIGH LEVEL MILOPS PUBLIC DOMAIN TECHNICAL ARCHITECTURE NIEM Core MilOps (MOP) Public Ref … CBRN Domain Public MDA Domain Public Each reference schema (e.g., MOR, MOP, MDA, CBRN, etc.) is in a separate namespace (e.g., file) MOP is developed only using data components w/ a publicly releasable source 6

HIGH LEVEL MILOPS RESTRICTED DOMAIN TECHNICAL ARCHITECTURE MilOps (MOR) Restricted MilOps (MOR) Restricted NIEM Core MilOps (MOP) Public Ref … CBRN Domain Public MDA Domain Public Each reference schema (e.g., MOR, MOP, MDA, CBRN, etc.) is in a separate namespace (e.g., file) Restricted MOR data components may extend (e.g., reference) public data components NO public schema may extend (e.g., reference) restricted MOR data components 7 NIEM Note: There may be multiple restricted name spaces to accommodate FOUO, Secret, Top Secret, etc. data component sources

C2 CORE V2.0 – NIEM V2.1 CONTENT ANALYSIS How does the content in C2 Core v2.0 compare with NIEM v2.1? 8

BLUF C2 Core v2.0 content was semantically compared with content in NIEM v2.1 w/ domain updates Approximately 1/8 of C2 Core content overlapped with NIEM content –1/8 represents opportunity for harmonization –7/8 represents unique DoD requirements not currently supported by NIEM Additional SME analysis is required to validate results 9

OBJECTIVE Support accomplishing task 5 from the DoD CIO/PM-ISE Data Summit, Oct TASK 5: Assess / de-conflict any content overlaps between the C2 Core, NIEM Core and other NIEM domains as a foundational step towards creation of the C2/Warfighter Domain under NIEM. Coordinate results with the MITRE Study Team. 10

METHODOLOGY 11  A comparison of data components will be made based on the term, definition and structure (e.g., complex type, simple type, string, integer, etc.)  A concept is defined by combining a term and definition  A match exists when the concept of two data components is semantically the same and the structures are also the same  A partial match exists when the concept of two data components is semantically the same, and the structures are different

SCOPE OF CONTENT REVIEWED NIEM v2.1 CONTENT CBRN Children, Youth & Family Services Emergency Management Family Services Immigration Infrastructure Protection Intelligence International Trade Justice Maritime Screening NIEM Common Core 2,488 types; 6,548 properties 12 C2 Core v2.0 CONTENT DRRS GML GSORTS ISO JAMD JC2IEDM JOPES JP3-52 MIL-STD-2525C TSPI USMTF VMF 335 types; 673 properties Note: This is not an exhaustive list. Complete list is available from the C2 Core sources spreadsheet at the RUL below.

COMPARISON OBSERVATIONS 13  C2 Core can reuse a NIEM Core/Domain element within a C2 Core type.  C2 Core can reuse a NIEM Core/Domain type as the type of a C2 Core element.  C2 Core can extend a NIEM Core/Domain type.  C2 Core can augment a NIEM Core/Domain type.* * Type Augmentation Supplement to NDR 1.3, September 24, 2009, Version rules/1.3/type-augmentation

COMPARISON OBSERVATIONS 14 NUMBER OF COMPONENTS REVIEWED C2 Core: 1,008 data components NIEM: 9,036 data components NUMBER OF MATCHING C2 CORE CONTENT Exact Match – 16 types; 2 properties Partial Match – 37 types; 143 properties These are initial numbers based on Lead Developer evaluation and are not considered official until validated by SMEs. List of content matches on the right provides a sampling of examples and is not inclusive of all matches identified. NIEM CONTENT MATCH BY CATEGORY Where: Geospatial (Area, Arc, Circle, Lat/Long, etc.), Locations, Track What: Aircraft, Equipment, Facility, Weapons, Person, agency When: Dates, Times Other: Message Information, Events, Tasks/Activity, Status, Speed/Movement, information, Resources

CONTENT COMPARISON 15 C2 CORE UNIQUE CONTENT SUPPORTING NEW MILOPS DOMAIN EquipmentID, EquipmentName, EquipmentReadiness Event, EventName, EventDescriptionText Mission, MissionName, MissionNumberID MiiltaryPlan, MilitaryPlanID Observer, ObserverID, ObserverLocation OperationOrder, OperationPlan Package, PackageID, PackageName TargetID, TargetMovement, TargetQuantity TaskName, TaskUUID, TaskDescriptionText TrackID Unit, UnitName, UnitPointOfContact

MATCHES IN NIEM DOMAINS CBRN - (21) Children, Youth & Family Services - (03) Emergency Management - (24) Family Services - (03) Immigration - (03) Intelligence - (02) International Trade - (49) Justice - (03) Maritime - (06) Screening - (04) NIEM Common Core - (160) GML - (13) Infrastructure Protection - (00) possible NIEM property matches NIEM Common Core - (32) GML - (09) NIEM-XSD - (16) International Trade - (04) Justice - (02) Children, Youth & Family Services - (02) Family Services - (02) Immigration - (02) Intelligence - (01) Maritime - (05) CBRN - (00) Emergency Management - (00) Infrastructure Protection - (00) Screening - (00) 75 possible NIEM type matches If a match or partial match exists, the relationship between C2 Core data components and NIEM data components is one to one or one to many.

17 WRITTEN REPORT & SUPPORTING ARTIFACTS AVAILABLE UPON REQUEST

NIEM - MILOPS VERSION ARCHITECTURE Do I have to update my IEPD with every new release of NIEM or MilOps? 18

BLUF An update or new release of NIEM Core does not necessarily require changes to domain content. Domain updates occur with more frequency than updates to NIEM Core and are managed by the Domain Steward along with any associated stakeholder group(s). Published releases are persistent and versioned. An IEPD employs a given NIEM release (e.g., NIEM Core & Domains) and is therefore never forced to upgrade. IEPD upgrades to new releases can be executed during system lifecycle technology refreshes or as desired. Tools (e.g., SSGT & ConTesA) are always upgraded or extended to use each new release. The MilOps tracks data component evolution, which enables deployment of tools to assist with migration of IEPDs between releases. 19

NIEM UPDATE PROCESS Note: Blue box w/ “C 1 ” refers to NIEM Core. Blue boxes w/ “1”, “2”, etc. refers to the domains 20

approves used to develop forms new MILOPS DOMAIN PROCESSES Technical Specifications Data Model Developer Support Restricted MilOps Data Model Public MilOps Data Model provides basis for Governance sharing technical & content requirements & solutions ESC NIEM PMO NBAC NTAC NCOC NIEM Domains MilOps Interim Governance Structure 1 Public IEPDs Restricted IEPDs 6 used to develop forms new forms new restricted domain model IEPDs Tools: SSGT/ ConTesA - Worked Examples - Outreach Restricted Public

GOVERNANCE MilOps Public v1.0 OPORD.xsd v3.0 Information Exchange Package Description (IEPD) Applications that send/receive XML instances governed by PEOs/PMOs/PORs IEPDs governed by PORs / COIs OPORD xml OPORD xml Sender App v5.2 Receiver App v8.3 Conforms to MilOps Restricted Governed by DoD Reused NIEM Core and Public Domain Content Governed by NIEM PMO NIEM MilOps Restricted v1.0 MilOps Public Managed by DoD Domain Steward & governed by NIEM PMO 22

RELEASE NEW MILOPS 1.X MilOps v1.x MilOps v1.0 OPORD.xsd v3.0 No change to IEPDs or service required OPORD xml OPORD xml Sender App v5.2 Receiver App v8.3 Conforms to MilOps domain update is released Reuses Components harvested from existing IEPDs Information Exchange Package Description (IEPD) NIEM Note: To simplify this diagram “MilOps” refers to content in either the public, restricted or both areas as appropriate for the IEPD. 23

IDENTIFY NEW IEPD REQUIREMENTS OPORD.xsd v3.0 No change to previous IEPDs or service required OPORD xml OPORD xml Sender App v5.2 Receiver App v8.3 Conforms to Reuses MilOps v1.x OPORD.xsd v3.1 Reuse new components MilOps v1.0 New OPORD IEPD v3.1 adopts new MilOps v1.x for supporting new requirements Information Exchange Package Description (IEPD) NIEM Note: To simplify this diagram “MilOps” refers to content in either the public, restricted or both areas as appropriate for the IEPD. 24

UPGRADE SEND/RECEIVE SERVICES MilOps v1.x OPORD.xsd v3.0 OPORD xml OPORD xml Sender App v5.2 Receiver App v8.3 Conforms to OPORD.xsd v3.1 OPORD xml OPORD xml Sender App v6.0 Receiver App v9.0 Conforms to Send/receive services upgraded to implement new OPORD v3.1 MilOps v1.0 Reuses PEO/PMO/POR/service owners determine when new business requirements or rules mandate IEPD migration Reuses Information Exchange Package Description (IEPD) NIEM Note: To simplify this diagram “MilOps” refers to content in either the public, restricted or both areas as appropriate for the IEPD. 25

UPGRADE SEND/RECEIVE SERVICES CONT. MilOps v1.x OPORD.xsd v3.0 Conforms to OPORD.xsd v3.1 OPORD xml OPORD xml Sender App v6.0 Receiver App v9.0 Send/receive service can also be upgraded to implement both OPORD v3.0 and v3.1 if desired MilOps v1.0 Reuses Conforms to Information Exchange Package Description (IEPD) NIEM Note: To simplify this diagram “MilOps” refers to content in either the public, restricted or both areas as appropriate for the IEPD. 26

MILOPS POA&M What is involved with creating the MilOps Domain in NIEM? 27

MILOPS DEVELOPMENT UPDATE 28 ITERATION #1 – Begins: 01 Nov Completed ITERATION #2 – Begins: 01 Feb 28 Mar: Alpha conformant Restricted Model 03 May: Alpha conformant Public Model 03 May: MilOps Domain model v0.2 ITERATION #3 – Begins: 03 May 30 Jul: MilOps Beta v0.3 ITERATION #4 – Begins: 01 Aug 25 Oct: MilOps Release Candidate v0.4 ITERATION #5 – Begins: 01 Nov 20 Dec: MilOps Domain v1.0 submission package

NIEM OVERVIEW What is NIEM all about? 29

THE NIEM FRAMEWORK What common services, governance models, processes and tools are provided by NIEM? 30

NIEM connects communities of people who share a common need to exchange information in order to advance their missions, and provides a foundation for seamless information exchange between federal, state, local, and tribal agencies. Much more than a data model, NIEM offers an active user community as well as a technical and support framework. Formal Governance Processes Online Repositories Mission-Oriented Domains Self-Managing Domain Stewards Data Model XML Design Rules Development Methodology Predefined Deliverables (IEPD) Tools for Development and Discovery Established Training Program Implementation Support Help Desk & Knowledge Center THE NIEM FRAMEWORK 31

Translation Scope-of-NIEM NIEM intentionally does not address standardizing data inside legacy systems. NIEM serves as a translation layer (providing a common understanding) between and across disparate systems. STANDARDIZING DATA MOVING ACROSS SYSTEMS INTERFACE LEGACY DATABASES LEGACY DATABASES COMMONLY FORMATTED DATA INTERFACE 32

Built and governed by the business users at Federal, State, Local, Tribal and Private Sectors THE NIEM LIFECYCLES 33

NIEM SPECIFICATIONS & PROCESSES What is the NDR and MPD Specification? What is the IEPD Development Life Cycle? 34

NORMATIVE NIEM SPECIFICATIONS 35 Naming & Design Rules (NDR), Version 1.3 Specifies principles and enforceable rules for NIEM data components and schemas. Schemas and components that obey the rules are considered to be NIEM-conformant. URI: pdfhttp://reference.niem.gov/niem/specification/naming-and-design-rules/1.3/niem-ndr- 1.3.pdf Model Package Description (MPD) Specification, Version 1.1 Defines terminology, identifies required and optional artifacts and metadata, specifies normative rules, schemes, syntax, and provides non-normative guidance to support the creation of NIEM MPDs. MPDs include IEPDs, Business Information Exchange Components (BIEC), Enterprise Information Exchange Models (EIEM), Domain Updates, and Core Updates. URI: pdfhttp://reference.niem.gov/niem/specification/naming-and-design-rules/1.3/niem-ndr- 1.3.pdf

MPD CLASSES 36 Model Release: Contains a full set of harmonized reference schemas defining all content in a version of NIEM. Domain Update: Contains reference schemas that represent changes to NIEM domains. NIEM domains use these as the basis for incremental improvements, extensions, and proposed changes to future NIEM releases. Core Update: Contains reference schemas representing changes that apply to a specific NIEM Core version. A core update is not published to replace a NIEM Core; it adds new schemas, new data components, and new code values to a core without waiting for the next major release. Information Exchange Package Documentation (IEPD): Defines a reusable XML data exchange. A NIEM IEPD contains 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, and at least one exchange schema that defines a document element. Enterprise Information Exchange Model (EIEM): A collection of business components organized into a subset and one or more extension schemas. Constraint schemas and non-NIEM-conforming external standards schemas with type adapters are optional in an EIEM. ​​​​​​​​​​​​

THE IEPD LIFECYCLE Plan the project, establish the process, and identify information exchange business requirements Selected information exchange is further elaborated to understand and document the business context and data requirements Associate local objects with types and elements in NIEM. This process is called mapping an exchange content model to NIEM Create a set of exchange-specific NIEM conformant XML schemas that implement the data model created for the exchange Prepare and package all related files for this IEPD into a single self ‐ contained, self- documented, portable archive file Publish IEPD for search, discovery, and reuse Scenario Planning Analyze Requirements Map & Model Build & Validate Assemble & Document Publish & Implement 37

THE IEPD ARTIFACTS IEPDs contain both required and recommended artifacts Required : Bold Recommended : Italic Note: Best practices for most organizations include many of the optional artifacts listed here Business Processes Use Cases Sequence Diagrams Business RulesBusiness Requirements Exchange Content Model Mapping Document Subset Schema Exchange Schema XML Wantlist Constraint Schema Extension Schema Main Document Catalog Sample XML Instances XML Stylesheets Scenario Planning Analyze Requirements Map & Model Build & Validate Assemble & Document Publish & Implement No required artifacts. Publish the IEPD to a repository and implement the exchange 38

NIEM GOVERNANCE How is NIEM governed? How does the federated domain governance function? What are the different NIEM committees? 39

NIEM GOVERNING STRUCTURE NIEM’s governing structure is comprised of Federal, State, Local, Tribal and private organizations NIEM is jointly managed at an executive level by the Department of Homeland Security (DHS), Department of Justice (DOJ), and Department of Health and Human Services (HHS) Executive Steering Council ESC Executive Director Deputy Director Executive Director Deputy Director NIEM PMO NIEM Technical Architecture Committee NTAC NIEM Business Architecture Committee NBAC NIEM Communications & Outreach Committee NC&OC 40

WHO STEERS NIEM CURRENTLY? Voting Members Dept of Justice Dept of Homeland Security Dept of Health and Human Services Ex-Officio Members Global Justice Information Sharing Initiative Office of Management and Budget Program Manager, Information Sharing Environment NASCIO Partners Terrorist Screening Center Dept of Defense / Dept of Navy Dept of State, Consular Affairs (invited) 41

WHO GOVERNS NIEM DOMAINS? DomainExecutive Steward JusticeGlobal Justice (State & Local) ScreeningDHS/Screening Coordination Office ImmigrationDHS/Immigration & Customs Enforcement (ICE), US Citizenship and Immigration Services (USCIS) Chem/Bio/Rad/NucDHS/Domestic Nuclear Detection Office (DNDO) MaritimeDOD/Maritime Domain Awareness (MDA) CyberDHS/National Protection and Programs Directorate (NPPD)/Cyber Security & Communications (CS&C) Children, Youth & Family ServicesHHS/Administration for Children and Families (ACF) & DOJ (State & Local) Emergency ManagementDHS/FEMA, DHS/Science & Technology (S&T) Infrastructure ProtectionDHS/NPPD International TradeDHS/Customs and Border Protection (CBP) BiometricsDHS/NPPD, National Institute of Standards & Technology (NIST) HealthHHS/Office of the National Coordinator (ONC) & HHS/Office of the Chief Information Officer (OCIO) Human ServicesHHS/ACF & HHS/ONC Government Resource ManagementGeneral Services Administration (GSA) 42

NIEM V3.0 UPDATE How is the NIEM v3.0 release going? 43

UML PROFILE FOR NIEM (V2.1 ALIGNMENT) Objective of the NIEM-UML Profile To allow modelers and developers to apply NIEM-UML with minimal effort in order to create new models or change existing models and ultimately to produce NIEM MPD artifacts. NIEM-UML Implementations MagicDraw NIEM-UML Plug-in Open Source Implementation (Under Development) 44

NIEM-UML Subset of the Unified Modeling Language (UML) Set of UML constructs & Stereotypes –Extends UML to represent NIEM concepts –NIEM concepts are augmented with NIEM-Platform mapping information –NIEM Naming & Design Rules enforced by leveraging the Object Constraint Language A valid NIEM-UML model will produce a valid MPD 45 NIEM Logical Concepts Not the XSD and NIEM Naming & Design Rules Details –Platform Independent Model (PIM) Profile –Common Profile –Model Package Description Profile UML Tooling/Development Environment WHAT IS NIEM-UML?LEARNING REQUIREMENTS? ` ` ` `

NIEM-UML GOALS Represent the semantics of NIEM while being agnostic of its structural representation To leverage standards and standards based tools To reduce complexity and lower the barrier for entry To facilitate reuse of NIEM models and as a result schemas To embrace accepted UML modeling styles and constructs To enable use of NIEM-PIM models for use with other standards, technologies and layers To support deterministic mapping to and from the NIEM technology layers based on NIEM rules Clarity: Ensure that a UML representation of a NIEM model produced by one developer can be interpreted as expected by another. Completeness: Ensure that a developer can produce a UML representation of any NIEM concept, including semantics, XML Schema structure, and metadata. Practicality: With minimal effort, a developer can employ the profile in current UML development tools to develop and use a NIEM model. 46

NIEM 3.0 HIGH-LEVEL BASELINE SCOPE * Code List Decoupling & Updates Optional Code List Complexity Solution New Augmentation Solution Integrate Latest Version of IC-ISM Unify Reference & Content-Bearing Elements Ability to Subset structures.xsd and appinfo.xsd Conformance Target Declaration Attributes in appinfo.xsd Local Terminology and Acronym Capability in appinfo.xsd Resolved Architectural NIEM Configuration Control Tool (NCCT) Issues Newly Identified Architectural NCCT Issues Domain Content Change Requests NCCT Content Harmonization Solutions Newly Identified NCCT Content Issues TECHNICAL ARCHITECTURE ENHANCEMENTS AND BUG FIXES HARMONIZED CONTENT, & DOMAIN CONTENT CHANGE REQUESTS NIEM.GOV TOOLS UPDATES SSGT (Updates & NIEM-UML Alignment) ConTesA Code List Generator * Scope is subject to change

NIEM 3.0 TIMELINE (13 MONTHS) Sep 2012 Oct 2012 Nov 2012 Dec 2012 Jan 2013 Feb 2013 Mar 2013 Apr 2013 May 2013 Jun 2013 Jul 2013 Aug 2013 Sep 2013 REQUIREMENTS & PREPARATION PHASEDEVELOPMENT & EXECUTION PHASE R ELEASE A LPHA 1 R ELEASE B ETA R ELEASE RC 1 R ELEASE NIEM 3.0 KICKOFF MEETING PMONBACNTACGTRICommunity Alpha 1 Alpha 2 Beta RC 1 RELEASE AUDIENCE 90- DAY D EADLINE 48 Today R ELEASE A LPHA 2

WEBSITE/PUBLIC COMMUNICATIONS 49 NIEM 3.0 URL: soon/Pages/version-3.aspx

UPDATED ONLINE TRAINING 50

NIEM COURSES 51 NIEM 100: Introduction to NIEM - Provides an overview of NIEM, its role in information-sharing and exchange, as well as the organizational benefits of using NIEM. NIEM 101: Technical Introduction to NIEM - Along with an overview of NIEM and its role in information-sharing and exchange, this course provides a summary of NIEM’s technical structure and how NIEM is used across organizations. The role of Information Exchange Package Documentation (IEPDs) is discussed along with their use in the development of NIEM-conformant information exchanges. NIEM 200: NIEM Lifecycle for Program and Project Managers - Provides participants with the information necessary to create and manage projects involving NIEM-conformant information exchanges. IEPD development is discussed in the context of managing a NIEM-based information exchange. NIEM 300: IEPD Discovery and Development - Equips NIEM project managers and architects with the skills necessary to analyze, plan and build IEPDs. Participants will develop artifacts associated with scenario planning and requirements analysis. NIEM 301: NIEM Advanced Technical Concepts - Provides implementers with the technical knowledge necessary to develop NIEM-conformant XML schemas and artifacts. Participants will be provided with detailed information about NIEM Naming and Design Rules, XML schema and artifacts, and governance and conformance standards. NIEM 302: Construct and Validate an IEPD - Enables implementers to convert business processes and requirements to the technical artifacts associated with IEPD development. Provides participants with detailed knowledge on exchange content models, mapping documents, the process of mapping data objects to NIEM, and the process of developing and validating XML schema. NIEM 303: Publish and Implement an IEPD - Provides project managers, architects and implementers with the skills necessary to assemble, publish, and implement an IEPD.

END 52