BY ORDER OF THE COMMANDER USTRANSCOM INSTRUCTION 33-48 UNITED STATES TRANSPORTATION COMMAND 22 JUNE 2015 Communications and Information DATA MANAGEMENT POLICY AND RESPONSIBILITIES COMPLIANCE WITH THIS PUBLICATION IS MANDATORY NOTICE: This publication is available electronically on the USTRANSCOM electronic library. RELEASABILITY: There are no releasability restrictions on this publication OPR: TCJ6-S Approved By: TCJ6 (Brig Gen Mitchel H Butikofer, USAF) Supersedes: USTRANSCOMI 33-48, 10 Aug 2006 Pages: 7 Distribution: e-publishing This instruction establishes USTRANSCOM and its Transportation Component Commands (TCCs) policy and responsibilities for managing data as a USTRANSCOM enterprise asset. Refer recommended changes and questions about this publication to the Office of Primary Responsibility using AF FORM 847, Recommendation for Change of Publication. Ensure all records created as a result of processes prescribed in this publication are maintained in accordance with USTRANSCOM Instruction 33-32, USTRANSCOM Records Management Program. SUMMARY OF REVISIONS This revision updates data standards implementation procedures and establishes procedures to maintain the USTRANSCOM Distribution Process Information Exchange Data Model (DPIEDM). It also broadens the scope of data management to include the concepts of metadata and reference data management, the adoption of common industry standards, common vocabulary, and a data quality management process. It describes the roles and responsibilities of data management organizations and offices created since the publication of the previous instruction to include Data Governance. It also removes reference to the obsolete USTRANSCOM Data Management Handbook and the Corporate Data Office Outreach Program. 1. References and Supporting Information. References, abbreviations, acronyms, and terms used in this instruction are listed in Attachment 1. 2. Background. 2.1. This Instruction is based on guidance from the Department of Defense (DOD) Instruction 8320.02 [Reference (a)] and USTRANSCOM s Data Strategy [Reference (b)]. It aligns with and is influenced by USTRANSCOM s Operational Blueprint [Reference (c)], Operations Strategy [Reference (d)], Information Technology (IT) Enterprise Strategy [Reference (e)], and Cybersecurity Strategy [Reference (f)].
2 USTRANSCOMI 33-48, 22 JUNE 2015 2.2. Enabling standard enterprise data exchange is critical to USTRANSCOM and the TCCs for successful data management. By leveraging existing joint tools, processes, and capabilities, USTRANSCOM s approach focuses on key enablers - data must be visible, accessible, trusted, interoperable, discoverable, understandable, protected, and governed. The key enablers are outlined in detail in References (a) and (b). 3. Purpose. The purpose of this document is to provide a guide to achieve USTRANSCOM policy compliance. It mandates Command-managed IT systems, programs, and initiatives (SPI) will apply standardization, quality control, and configuration management functions to ensure data interoperability and quality. It also encourages the use of USTRANSCOM data management guidance by non-ustranscom Defense Transportation System developers to facilitate interoperability. 4. Policy. USTRANSCOM will manage data as an enterprise asset; a critical element to accomplishing the DOD transportation mission. This Instruction establishes the roles and responsibilities for management of USTRANSCOM data. All USTRANSCOM SPIs are required to follow the guidance established by this instruction through the implementation of provided policies and standards to aggressively implement data administration in ways that provide clear, concise, unambiguous, and easily accessible data throughout the enterprise. USTRANSCOM is committed to full compliance with the overall DOD data management policy [Reference (a)]. Accordingly, USTRANSCOM s policy is to: 4.1. Record all Defense Logistics Management Standards (DLMS) and non-dlms compliant data exchanges used by USTRANSCOM in the USTRANSCOM DPIEDM. USTRANSCOM data exchanges include all data types passed between systems regardless of the method of exchange and supports DOD Directive 8190.01E [Reference (g)]. 4.2. Standardize all data exchanges to include Electronic Data Interface (EDI) and Extensible Markup Language (XML) exchanges. Register all standard XML information resources (XML Schema and XML Schema Definitions) in the DOD Metadata Registry (when available) and in the USTRANSCOM Defense Transportation Electronic Business (DTEB) XML Gallery in support of information sharing, visibility, and reuse among USTRANSCOM, DOD, and other government and commercial systems. The XML Gallery is on the Information Tool Suite DTEB Web Site located at https://its.ustranscom.mil/cris/dteb/documentation/gallery.cfm. DTEB registers, approves, and makes available all standard data exchanges used for DOD transportationrelated purposes. 4.3. Require the capture, storage, and management of enterprise-wide metadata. 4.4. Promote data quality and utilize USTRANSCOM/J6 support for assistance in the resolution and tracking of data quality efforts. 4.5. Augment and amplify DOD data management policy and procedures in support of the USTRANSCOM Data Strategy [Reference (b)] and Integrated Roadmap [Reference (h)].
USTRANSCOMI 33-48, 22 JUNE 2015 3 4.6. Mandate USTRANSCOM s and its TCCs SPIs use and subscribe to reference data managed and distributed by USTRANSCOM Reference Data Management (TRDM). 5. Concept. 5.1. Management of USTRANSCOM data must be implemented in ways that enhance mission performance through the effective and economic acquisition and use of data. Objectives of USTRANSCOM data management are to: 5.1.1. Support DOD transportation operations and decision making with data that meets the need in terms of the key enablers described in the USTRANSCOM Data Strategy [Reference (b)]. 5.1.2. Structure the USTRANSCOM data architecture in ways that allow horizontal as well as vertical sharing of data within the DOD, other government agencies, private sector organizations, and allied nations. 5.1.3. Ensure adherence to applicable national security and privacy requirements. 5.2. The data management activities described in this instruction are supported by well-defined guidelines and methods in artifact documents. The artifacts may be accessed at https://intellipedia.intelink.gov/wiki/ustranscom_joint_deployment_and_ Distribution_ Architecture_-_Enhanced. This structured approach will enable effective planning, analysis, standardization, quality assurance, modeling, configuration management, storage, retrieval, protection, validation, and documentation of USTRANSCOM data. 5.3. The key components of USTRANSCOM data management are: 5.3.1. Metadata Management. Currently, Program Managers have access to the DPIEDM which contains all of the required data dictionary metadata. The DPIEDM may be accessed at https://intellipedia.intelink.gov/wiki/ustranscom_enterprise_data_models. Future efforts include defining required metadata as well as establishing and maintaining a USTRANSCOM Metadata Registry that will contain all required metadata. Program Managers will have access to this registry for metadata analysis and reuse purposes. 5.3.2. DPIEDM Development. The DPIEDM is the enterprise logical data model. It is a required architecture product (DIV-2) that defines business rules and data requirements for the enterprise. DPIEDM is used in schema development, web service development, and data gap and redundancy analysis. The DPIEDM serves as an enterprise reference for all new schema development detailed in the I06 artifact DPIEDM Manuel (Enterprise Logical Data Model) [Reference (i)]. 5.3.3. Information Exchange Standards Implementation. Implementation of information exchange standards is done in compliance with the Office of the Secretary of Defense policies on standard data exchange found in Reference (g). Data exchanges using XML is one of several standard interface implementations available to USTRANSCOM SPIs. All USTRANSCOM SPIs engaged in XML implementation shall use approved standard terms within their XML
4 USTRANSCOMI 33-48, 22 JUNE 2015 schema. Standard terms are mapped to the DPIEDM, and the process for managing standard terms is detailed in the I05 artifact Standard Term Creation, Approval, and Maintenance Manual [Reference (j)]. 5.3.4. Reference Data Management. Data quality problems are often due to disagreement on reference data between systems. These problems can be greatly reduced through the use of standard reference data. Processes for the management of reference data can be further reviewed within the I07 artifact Enterprise Reference Data Management Process Guide [Reference (k)]. 5.3.5. Enterprise Data Initiatives. Data initiatives are projects planned, prioritized, and resourced supporting data issues identified in strategic plans, lessons learned, gap analyses, and data quality reports. 5.3.6. Data Quality. The DOD core set of data quality requirements includes accuracy, completeness, consistency, timeliness, uniqueness, and validity. USTRANSCOM shall encourage and support data quality projects at the highest level consistent with available resources to achieve the level of quality necessary to meet mission requirements. The J6 data management office is USTRANSCOM s focal point for reporting data quality problems and managing integrated technology roadmap data tasks. Implementation details for data quality projects are available in the I11 artifact Data Quality Manual [Reference (l)]. 6. Data Governance. 6.1. Objectives of the Data Management Governance Process are located in Reference (b). Data governance is the execution of authority over data matters. It includes setting up rules and regulations for enterprise data; enforcing rules and regulations (roles, responsibilities, and accountability); establishing data processes and procedures; establishing data sharing and reference data standards; establishing and tracking metrics; managing data conflicts; promoting data privacy and security; promoting data quality; enforcing metadata documentation and other data documentation; and allocating resources within its purview. 6.2. The data governance process (Figure 1) is derived from USTRANSCOM s corporate governance process. The Enterprise Data Working Group (EDWG) is an O-6/GS-15 level advisory group providing support to the Chief Information Officer (CIO). The CIO or the CIO s representative provides requests for financial enterprise information-related funding to the Mission Area Management (MAM)/Sub-MAM group and acts as the technical advisor for the MAM/Sub-MAM group under the USTRANSCOM Oversight Council (TOC). Therefore, within the USTRANSCOM corporate governance process, the advice of the EDWG can influence both the MAM/Sub-MAM group via the CIO representative and the TOC, where the CIO is a member.
USTRANSCOMI 33-48, 22 JUNE 2015 5 Figure 1: USTRANSCOM Data Governance Process 6.3. The EDWG advocates sustainable processes to ensure appropriate levels of data integrity and quality. The EDWG will achieve this by adjudicating policy and resource issues that cannot be resolved at a lower level, i.e., DTEB, Standard Terms, Data Quality Working Group. The EDWG is chaired by USTRANSCOM/J6-S with representatives from AMC/A6, SDDC/G6, MSC/N6, USTRANSCOM/J3, USTRANSCOM/J5-4, and USTRANSCOM/AC. 7. Responsibilities. 7.1. The USTRANSCOM CIO shall: 7.1.1. Establish data management policy for USTRANSCOM and the TCCs. 7.1.2. Manage applicable enterprise metadata. 7.1.3. Monitor and support efforts to improve data quality throughout the enterprise. 7.1.4. Perform management reviews to evaluate the effectiveness of data management programs. 7.1.5. Identify and make recommendations for resolving multi-system data quality issues. 7.1.6. Pursue involvement in DOD-level data organizations. 7.1.7. Ensure data integration programs are aligned to the Joint Distribution and Deployment Architecture [Reference (m)]. 7.2. The USTRANSCOM/J6 Directorate shall:
6 USTRANSCOMI 33-48, 22 JUNE 2015 7.2.1. Maintain a comprehensive data management program to ensure data formats, data sources, data quality, data availability, data interfaces/interchanges and other data-related attributes support the Command s mission. 7.2.2. Manage data as an enterprise asset by managing and making available the USTRANSCOM data standards. 7.2.3. Develop and oversee the implementation of the policies and procedures associated with the Data Strategy [Reference (b)]. 7.2.4. Manage the ongoing development and maintenance of the DPIEDM. 7.2.5. Participate in DOD-level data organizations (i.e., DTEB Committee; Ocean, Rail, and Motor Automated Carrier Interface Task Groups; and Federal EDI standards community). 7.2.6. Manage TRDM, the TRDM Requirements Review Board, Configuration Control Board, and system support to synchronize data exchanges across Command-managed IT systems. 7.3. Program Managers of Command-managed SPI under USTRANSCOM purview shall: 7.3.1. Follow all policies in this instruction and coordinate any proposed supplements through the USTRANSCOM/J6. 7.3.2. Provide coordination and input to existing and new data management policies. 7.3.3. Identify and make recommendations for resolving multi-system data quality issues. 7.3.4. Ensure USTRANSCOM data standards are applied in their SPIs according to the guidance in this instruction. 7.3.5. Maintain metadata on all system data. Make this metadata available on a need to know basis to the USTRANSCOM metadata registry when it becomes available. MITCHEL H BUTIKOFER Brigadier General, USAF Director, Command, Control, Communications and Cyber Systems Attachment: 1. Glossary of References and Supporting Information
USTRANSCOMI 33-48, 22 JUNE 2015 7 References Attachment 1 GLOSSARY OF REFERENCES AND SUPPORTING INFORMATION (a) DOD Instruction 8320.02, Sharing Data, Information, and Information Technology (IT) Services in the Department of Defense, 5 Aug 13 (b) USTRANSCOM Data Strategy, 2 Dec 14 (c) USTRANSCOM Operational Blueprint, Current Edition (d) USTRANSCOM Operations Strategy, 29 May 14 (e) USTRANSCOM Information Technology Enterprise Strategy, 2 Dec 14 (f) USTRANSCOM Cybersecurity Strategy, 2 Dec 14 (g) DOD Directive 8190.01E, Defense Logistics Management Standards, 9 Jan 15 (h) USTRANSCOM Integrated Roadmap, Current Edition (i) I06 artifact, DPIEDM Manual (Enterprise Logical Data Model), 10 Feb 12 (j) I05 artifact, Standard Terms Manual, 16 Dec 10 (k) I07 artifact, Enterprise Reference Data Management Process Guide, 6 Nov 12 (l) I11 artifact, Data Quality Manual, 20 Oct 11 (m) Joint Distribution and Deployment Architecture, 25 Jan 15 Abbreviations and Acronyms CIO DLMS DOD DPIEDM DTEB EDI EDWG IT MAM SPI TCC TCJ6 TOC TRDM USTRANSCOM XML Chief Information Officer Defense Logistics Management Standards Department of Defense Distribution Process Information Exchange Data Model Defense Transportation Electronic Business Electronic Data Interface Enterprise Data Working Group Information Technology Mission Area Management r Systems, Programs, and Initiatives Transportation Component Command Command, Control, Communications and Cyber Systems Directorate toc USTRANSCOM Oversight Council USTRANSCOM Reference Data Management United States Transportation Command Extensible Markup Language Terms This section not used.