BY ORDER OF THE COMMANDER USTRANSCOM INSTRUCTION UNITED STATES TRANSPORTATION COMMAND 9 JUNE 2015 COMPLIANCE WITH THIS PUBLICATION IS MANDATORY

Transcription

1 BY ORDER OF THE COMMANDER USTRANSCOM INSTRUCTION UNITED STATES TRANSPORTATION COMMAND 9 JUNE 2015 Communications and Information JOINT DEPLOYMENT AND DISTRIBUTION ARCHITECTURE POLICY AND RESPONSIBILITIES COMPLIANCE WITH THIS PUBLICATION IS MANDATORY NOTICE: This publication is available electronically on the USTRANSCOM electronic library. RELEASIBILITY: There are no releasibility restrictions on this publication OPR: TCJ6 Approved By: TCCS (Major General David Clarkson, USA) Supersedes: USTRANSCOMI 33-46, 30 Oct 2003 Pages: 16 Distribution: e-publishing This instruction establishes command policies, roles, and responsibilities for developing and implementing the enterprise efforts as defined in the Joint Deployment and Distribution Architecture (JDDA). This instruction implements the architecture-related mandates of the Clinger-Cohen Act of 1996 and the Office of Management and Budget (OMB) Circular A-130, Management of Federal information Resources. This instruction applies to all United States Transportation Command (USTRANSCOM) directorates and its Component Commands, as described in and complies with USTRANSCOMI 90-9, to include Military Surface Deployment and Distribution Command (SDDC), Military Sealift Command (MSC), Air Mobility Command (AMC) and the Sub-Component Commands to include the Joint Enabling Capabilities Command (JECC), and the Joint Transportation Reserve Unit (JTRU). As referenced in the DODI , the JDDA is an authoritative source for the JDDE Community of Interest (COI) to coordinate and synchronize JDDE capabilities development. Refer recommended changes and questions about this instruction to the office of primary responsibility using Air Force Form 847, Recommendation for Change of Publication. Ensure that 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 instruction establishes command policies, roles, and responsibilities for developing and implementing the enterprise efforts as defined in the JDDA and its scope including the purpose of enterprise architecture (EA) and JDDA segments for USTRANSCOM, its directorates and Component Commands. It also establishes a governance process for the JDDA and updates roles, responsibilities, and policy. 1. References and Supporting Information. References, related publications, abbreviations, acronyms, and terms used in this instruction are listed in Attachment Purpose. This instruction is to establish the governance process, roles, responsibilities and policies for the JDDA. The JDDA artifacts, primitives, documents, and taxonomies describe and display the current and future relationships between processes, performance metrics,

2 2 USTRANSCOMI 33-46, 9 JUNE 2015 information, information systems, technologies, and governance processes. The JDDA provides an information-centric EA that: 2.1. Enables the alignment of JDDE resources with the Command s mission, vision, goals, and objectives through EA with the USTRANSCOM Strategies and Roadmaps, Operational Blueprint, and the Unified Command Plan (UCP) Enables the Mission Area Manager (MAM) to integrate, synchronize, and coordinate requirements to ensure alignment to strategic priorities and Joint Mission Essential Task List (JMETL) per the USTRANSCOMI As described in the DODI , the JDDA supports business processes by identifying gaps, seams, and redundancies based on risk tolerance levels, potential returns, outcome goals and performance for the warfighter Identifies opportunities for consolidation and reuse of information and technology within and across the Enterprise by identifying gaps and duplication Documents the relationship between enterprise initiatives and the Command s as is, transition, and to-be architecture Provides business, information, and technical guidance and standards to inform solution architecture development Provides the foundation for implementing Service-Oriented Architecture (SOA) through defining business process and the systems and services while providing a common vocabulary Documents a pathway for the Enterprise to create such an environment that replaces pointto-point system interfaces with Enterprise services, as defined within DOD Architecture Framework (DODAF) V JDDA Achitectural Structure. An architectural framework is a method of organizing architecture components into useful artifacts and/or Reference Models that serves the architecture s designed purpose. The DODAF and Federal Enterprise Architecture (FEA) framework are the two primary frameworks used throughout the DOD. DODAF also serves as the principal guide for development of integrated architectures as defined in DOD Instruction , which defines an integrated architecture as "An architecture consisting of multiples views or perspectives facilitating integration and promoting interoperability across capabilities and among integrated architectures". The DODAF promotes reuse of information that architecture artifacts can be shared with common understanding. The FEA framework promotes shared development for common Federal processes, interoperability, and sharing of information among the Agencies of the Federal Government and other Governmental entities through the use of a set of reference models and practices that apply to all Federal Agencies. DOD leverages the FEA construct and core principles to provide the Department with the enterprise management information it needs to achieve its own strategic transformation goals and respond to upward reporting requirements of OMB.

3 USTRANSCOMI 33-46, 9 JUNE USTRANSCOM interfaces with Combatant Commands (CCMDs), Military Services, DOD Agencies, Federal Agencies, and Commercial Partners while executing transportation and distribution missions. To provide the flexibility to interface with both federal and commercial entities, the JDDA adopts a DODAF approach that is consistent and complementary to FEA guidance as provided by OMB along other government and commercial best practices. The JDDE is defined in DODI , and the Joint Logistics (Distribution) Joint Integrating Concept (JL(D)JIC) as, the complex of equipment, procedures, doctrine, leaders, technical connectivity, information, shared knowledge, organizations, facilities, training, and materiel necessary to conduct joint distribution operations. The JDDE is not defined by organizational boundaries. The JDDA is the EA for the JDDE. The DODAF defines EA as a strategic information asset base, which defines the mission, the information necessary to perform the mission, the technologies necessary to perform the mission, and the transitional processes for implementing new technologies in response to changing mission needs. The JDDA was formally recognized by DOD in DODI , Distribution Process Owner, 30 July 2007, in which USTRANSCOM was assigned responsibility for, collecting and coordinating appropriate processes, systems, and technical information needed to build and maintain the integrated JDDA for the DOD The JDDA shall be used as an authoritative source for USTRANSCOM and Component Command processes that coordinate and synchronize JDDE capabilities development to attain DOD strategic deployment and distribution objectives (e.g., MAM, Process Improvement Initiatives, Distribution Steering Group (DSG), Integrated Priority List (IPL), Joint Capabilities Technology Demonstrations (JCTD), Logistics Functional Capabilities Board (Log FCB), Joint Capabilities Integration & Development System (JCIDS), and other such processes). The JDDA is an authoritative information resource for the as-is, the transition, and the to-be states of the JDDE. The Corporate Governance Process (CGP) described in USTRANSCOM Instruction 90-6, USTRANSCOM Corporate Governance Process, may use the JDDA to align enterprise resources with the Command s mission, vision, goals, and objectives. JDDA shall be used for USTRANSCOM s support to Joint Command and Control (JC2) Architecture and Business Enterprise Architecture (BEA). 4. JDDA Architectural Principles. Architecturally significant concepts are foundational principles that shape the development and direction of the JDDA, delineated in the JDDA Architecture, signed by the commander in Trusted and Reliable Establishes trust and reliability, and provides results that meet the expectations and operational needs across the enterprise Governed Aligns enterprise requirements with the enterprise strategic plan, provide organizational structures that facilitate the implementation of strategy and goals, measures the enterprise performance, manages risk, and ensures compliance with legal statutes and federal regulations Cooperative Initiates and promotes collaboration, cooperation, and coordination with business and Information Technology (IT) partners.

4 4 USTRANSCOMI 33-46, 9 JUNE Optimized Synchronizes the execution of distribution activities in time, space, and purpose to optimize delivery of required forces and sustainment to designated points of need Knowledge-Focused Designs solutions that leverage intelligent systems to generate and evaluate courses of action to allow human users to focus on decision support as opposed to repetitive labor-intensive activities Information-Centric Creates an information-centric environment which ensures all data is available, visible and understandable through accessible, context-based data relationships in support of effective decision making Transparent Provides timely, reliable, and assured information to all members of the enterprise about decision making processes, standards, and available services Service-Oriented Shares capabilities across enterprise organizations through standard interfaces that reduce duplication and inconsistency Engineered Designs modular, loosely-coupled, and re-useable solutions that meet mission requirements Open Standards and Sources Uses non-proprietary, open source, or Government off-theshelf software wherever possible Performance Measures all elements within the EA to foster continuous improvement to better meet strategic objectives Federated A framework for EA development, maintenance, and use that aligns, locates, and links separate but related architectures and architecture information to deliver a seamless outward appearance to users Integrated Architecture Framework Provides strong focus on the need to understand business requirements and drivers, and the need for all aspects of the architecture and all architectural decisions to be traceable back to these business priorities. 5. JDDA Scope. The JDDA incorporates the USTRANSCOM EA s as Segments of the JDDA (Figure 1). Segments are described in the FEA Practice Guide, Appendix A, and OMB Circular No. A-11, Preparation, Submission, and Execution of the Budget July 2010, as, an architecture pertaining to individual elements of the enterprise describing core mission areas and common or shared business services and enterprise services. Segments are defined by the EA. As a minimum, the JDDA includes the following EA s as Segments: USTRANSCOM, AMC, SDDC, and MSC. Other segment architectures may be added as appropriate to meet the needs of the JDDA. As such, all references to the JDDA, USTRANSCOM, or the USTRANSCOM Enterprise include the USTRANSCOM Component Commands and respective architectures.

5 USTRANSCOMI 33-46, 9 JUNE Segment Scope USTRANSCOM: Is defined as the complex of equipment, procedures, doctrine, leaders, technical connectivity, information, shared knowledge, organizations, facilities, training, and materiel necessary to conduct joint Defense Transportation System Operations, DPO operations, and USTRANSCOM missions delineated in the Unified Command Plan AMC: Is defined as the Air Force Component Major Command (C-MAJCOM), and as such is designated as Air Forces Transportation (AFTRANS). Accordingly, the AMC Commander (AMC/CC) is Commander of AFTRANS (AFTRANS/CC). AMC/CC delegates operational control and appropriate authorities to 18 AF/CC to execute the AFTRANS mission. The nomenclature 18 AF (AFTRANS) is used to designate 18 AF as the subordinate Component-Numbered Air Force (C-NAF) to the C-MAJCOM. AMC provides airlift, air refueling, air mobility support, and aero-medical evacuation capability MSC: Is defined as the Navy Component Command of USTRANSCOM and is also organized as a component of Fleet Forces Command. MSC provides ocean transportation and strategic sealift for mission areas funded by the TWCF (per SECNAVINST F, Prescribing Channels of Responsibility for the Military Sealift Command combined with COMUSFLTFORCOMINST , Mission, Functions and Tasks of Commander, Military Sealift Command) SDDC: Is defined as an operational-level Army force designated by the Secretary of the Army as the Army Service Component Command of USTRANSCOM and a major subordinate command of Army Materiel Command to provide global deployment C2 of forces as designated and such distribution operations as required to meet national security objectives. 7. Policy. Figure 1 USTRANSCOM EA Segment of the JDDA 7.1. The JDDA shall be governed by its managers within the enterprise it represents. DOD Instruction , DPO, appoints USTRANSCOM as the responsible manager of the JDDA. Therefore, USTRANSCOM as the DPO shall provide JDDA management and governance leadership in collaboration with the JDDE COI Each respective Segment of the JDDA will manage and maintain their EA artifacts in accordance with JDDA principles along with DOD and USTRANSCOM, standards, policy, services, and guidance.

6 6 USTRANSCOMI 33-46, 9 JUNE Roles And Responsibilities USTRANSCOM TCJ6 Shall: As the USTRANSCOM Chief Information Officer (CIO) and Chief Architect, be responsible for the establishment and management of the JDDA EA and chairing the JDDA EA Artifact Configuration Control Board (CCB) and JDDA EA Implementation Planning Team (IPT). TCJ6 may delegate responsibilities as deemed appropriate Provide EA capabilities to USTRANSCOM, as specified in USTRANSCOMI 90-9, Roles and Functions, USTRANSCOMPD 33-32, CIO Roles and Responsibilities, and USTRANSCOM 38-1, Organization and Functions, and serve as the primary technical proponent and champion and/or process owner for any issues or modifications associated with the JDDA Serve as the Office of Primary Responsibility (OPR) for the JDDA. Ensure all JDDA artifacts are in alignment with USTRANSCOM strategic objectives Ensure JDDA EA s are integrated horizontally and vertically to ensure information sharing, information visibility, and information interoperability Execute management of the JDDA in compliance with USTRANSCOM and DOD policy and guidance, according to accepted architecture frameworks and industry best practices, (e.g., FEA, DODAF, and BEA) Establish and manage the JDDA Integrated Architecture Governance Process as depicted in Figure 2. Develop Governance Charter to accurately manage the Integrated Architecture Governance Process As the USTRANSCOM CIO, act as the final decision making authority for, and provide representation to, the JDDA Integrated Architecture Governance Process Serve as the primary Functional Proponent and Champion and/or Process Owner for the USTRANSCOM EA Ensure Architectures are integrated from the enterprise level down through the solution level, across each respective Enterprise, and governed through the JDDA Integrated Architecture Governance Process. This governance process can be visualized as in Figure 2. Each JDDA Segment Architecture will be represented in the AO level working group where JDDA architecture governance issues can be discussed. When necessary, these issues can be raised to the Stakeholders and Chief Architects governance entity for decisions and direction. The CIO Council exists as the highest level architecture governance entity. Funding decisions that affect the enterprise may need to be elevated higher to the MAM or the EA General Officer Steering Committee (GOSC) will do so as deemed necessary by their requirements and the CIO Council.

7 USTRANSCOMI 33-46, 9 JUNE Additional decision scope, membership, information sharing, business rules, escalation criteria, scope and impact will be further described in the EA Charter and Handbook for the CIO Council, EA IPT, EA CCB, Enterprise Architecture Sub Group (EASG), and Enterprise Architecture Working Group (EAWG). Figure 2 JDDA Integrated Transportation Architecture Governance Process Define and document the relevant technical standards supporting the engineering requirements required to implement SOA within the JDDE Ensure all new capability development efforts, funded with Transportation Working Capital Funds or other funding controlled by USTRANSCOM and are documented in the JDDA Ensure JDDA aligns with all DOD CIO Compliance criteria, such as the Clinger- Cohen Act, DOD CIO, DODD , and USTRANSCOMP 38-1, Volume TCJ1, TCJ2, TCJ3, TCJ8, TCAQ, JECC, JTRU shall: Validate the accuracy and completeness of information within the various JDDA artifacts and products. Ensure that those artifacts and products are in alignment with USTRANSCOM strategic, tactical, and operational objectives and documented within the USTRANSCOM EA Provide SMEs to support architecture development of respective processes and information including updates to the JDDA artifacts, products, and other documentation TCJ3 shall serve as the primary functional proponent and Champion/Process Owner supporting Deployment/Redeployment (discrete movement) activities TCJ5/J4 shall: Manage distribution and distribution-related (DDR) system information in compliance with this instruction, JDDA governance, and other direction provided by the USTRANSCOM Chief Architect. Validate the accuracy and completeness of DDR system information within the

8 8 USTRANSCOMI 33-46, 9 JUNE 2015 various JDDA artifacts and products. Ensure that those artifacts and products are in alignment with USTRANSCOM strategic, tactical, and operational objectives Serve as the primary Functional Proponent and Champion and/or Process Owner for the DDR in the Strategy, Policy, Programs, and Logistics area of responsibility and the owner supporting the Sustainment/Retrograde activities. This is in line with serving as the USTRANSCOM DPO Portfolio Management (DPfM) Manager DPfM Coordinator responsibilities stated in USTRANSCOMI 90-9 and in the, Immediate Actions to Align DPO IT- Related Responsibilities, 16 November 2012, in accordance with the Office of Management and Budget Circular A Provide SMEs to support architecture development of respective processes and information including updates to the JDDA artifacts, products, and items in support of the USTRANSCOM Enterprise Monitor the DDR system compliance with the JDDA processes, governance and guidelines. Advise USTRANSCOM Chief Architect and bring relevant issues to the JDDA governance process TCAC shall: Validate the accuracy and completeness of JDPAC-related Architecture within the various JDDA artifacts and products. Ensure that those artifacts and products are in alignment with USTRANSCOM strategic, tactical, and operational objectives Serve as primary enterprise technical consultant on analytic and optimization service capabilities and technology standards for analytics and optimization supporting operational planning and scheduling/rescheduling processes Provide SMEs to support architecture development of respective processes and information including updates to the JDDA artifacts and products in support of the USTRANSCOM Enterprise Monitor JDPAC Analytic Architecture compliance with the JDDA processes, governance and guidelines. Keep the USTRANSCOM Chief Architect informed and bring relevant issues to the JDDA governance process AMC shall: In accordance with USTRANCOMI 90-9, AMC, designated as Air Forces Transportation (AFTRANS) will serve as the primary Functional Proponent and Champion and/or Process Owner for AMC EA Validate the accuracy and completeness of the AMC EA information within the various JDDA artifacts and products. Ensure that those artifacts and products are in alignment with USTRANSCOM strategic, tactical, and operational objectives.

9 USTRANSCOMI 33-46, 9 JUNE Provide SMEs to support architecture development of respective processes and information including updates to the JDDA artifacts Provide representation to the JDDA Integrated Architecture Governance Process Monitor AMC compliance with the JDDA processes, governance and guidelines Ensure respective architectures are integrated horizontally and vertically to ensure information sharing, information visibility, and information interoperability SDDC shall: Serve as the primary Functional Proponent and Champion and/or Process Owner for the SDDC EA Validate the accuracy and completeness of the SDDC EA information as part of the JDDA. Ensure those artifacts and products are in alignment with USTRANSCOM strategic, tactical, and operational objectives Provide SMEs to support architecture development of respective processes and information including updates to the JDDA artifacts Provide representation to the JDDA Integrated Architecture Governance Process Monitor SDDC compliance with the JDDA processes, governance and guidelines Ensure respective architectures are integrated horizontally and vertically to ensure information sharing, information visibility, and information interoperability MSC shall: Serve as the primary Functional Proponent and Champion and/or Process Owner for the MSC EA Validate the accuracy and completeness of the MSC EA information within the various JDDA artifacts and products. Ensure that those artifacts and products are in alignment with USTRANSCOM strategic, tactical, and operational objectives Provide SMEs to support architecture development of respective processes and information including updates to the JDDA artifacts Provide representation to the JDDA Integrated Architecture Governance Process Monitor MSC compliance with the JDDA processes, governance and guidelines.

10 10 USTRANSCOMI 33-46, 9 JUNE Ensure respective architectures are integrated horizontally and vertically to ensure information sharing, information visibility, and information interoperability. DAVID G. CLARKSON Major General, U.S. Army Chief of Staff

11 USTRANSCOMI 33-46, 9 JUNE References Attachment 1 GLOSSARY OF REFERENCES AND SUPPORTING INFORMATION DOD Architecture Framework (DODAF), Version 2.02, August 2010 DOD Directive , Management of DOD Information Resources and IT DOD Directive , Information Technology (IT) Portfolio Management DOD Directive , Interoperability of IT, Including National Security Systems, May 2014 DOD Instruction , Procedures for Interoperability and Supportability of (IT and National Security Systems (NSS) DOD Instruction , Distribution Process Owner DOD Instruction , IT Portfolio Management Implementation Federal Enterprise Architecture Practice Guidance, Federal Enterprise Program Management office, OMB, November 2007 JDDA Conceptual Architecture, Overview and Summary Information, (AV-1) Joint Publication National Defense Authorization Act for Fiscal Year 1996, Division E, the Information Technology Management Reform Act of 1996 (Clinger-Cohen Act) National Defense Authorization Act for Fiscal Year 2014, Title VIII Acquisition Policy, Acquisition Management, and Related Matters Office of Management and Budget (OMB) Circular A-130, Management of Federal Information Resources OMB A-11, Preparation, Submission, and Execution of the Budget, Sections 55 and 240 and Exhibits 53 and 300 OMB A-130, Management of Federal information Resources OMB Federal Enterprise Architecture Program EA Assessment Framework 3.1, June 2009 USTRANSCOM Instruction 90-6, Corporate Governance Process USTRANSCOM Instruction 90-9, Roles and Functions USTRANSCOM Memorandum from TCCC, Changes in USTRANSCOM and Component Command Structure, Roles and Processes as a Foundation for Achieving IT Management Excellence, 16 November 2012 USTRANSCOM Memorandum from TCCC, Immediate Actions to Align Distribution Process Owner (DPO) IT-Related Responsibilities, 16 November 2012 USTRANSCOM Memorandum from TCCC, Alignment of USTRANSCOM DPO IT Related Responsibilities, DPO Portfolio Management (DPfM) Manager, 16 November 2012 USTRANSCOM Pamphlet 38-1, Organizations and Functions, Volume 5, 08 March, USTRANSCOM Policy Directive 33-32, Chief Information Officer Program Abbreviations and Acronyms AFTRANS Air Forces Transportation AMC Air Mobility Command BEA Business Enterprise Architecture CCB Configuration Control Board CCMD Combatant Commands

12 12 USTRANSCOMI 33-46, 9 JUNE 2015 CGP Corporate Governance Process CIO Chief Information Officer CM Configuration Management COI Community of Interest DOD Department of Defense DODAF Department of Defense Architecture Framework DODI Department of Defense Instruction DOTMLPF-P Doctrine, Organization, Training, Material, Leadership, Personnel, Facilities and Policy DPfM Distribution Portfolio Management DPO Distribution Process Owner DSG Distribution Steering Group EA Enterprise Architecture EASG Enterprise Architecture Sub Group EAWG Enterprise Architecture Working Group FEA Federal Enterprise Architecture GOSC General Officer Steering Committee IPL Integrated Priority List IPT Implementation Planning Team IT Information Technology JCIDS Joint Capabilities Integration & Development System JDDA Joint Deployment and Distribution Architecture JDDE Joint Deployment and Distribution Enterprise JDPAC Joint Distribution Process Analysis Center JECC Joint Enabling Capabilities Command JL(D)JIC Joint Logistics (Distribution) Joint Integrating Concept JMETL Joint Mission Essential Task List JTRU Joint Transportation Reserve Unit MAM Mission Area Management MSC Military Sealift Command OMB Office of Management and Budget SDDC Military Surface Deployment and Distribution Command SME Subject Matter Expert SOA Service Oriented Architecture TCCS Transportation Component Command Staff TWCF Transportation Working Capital Fund UCP Unified Command Plan USTRANSCOM United States Transportation Command Terms Air Mobility Command (AMC). AMC is the Air Force Component Major Command (CMAJCOM), and as such designated as Air Forces Transportation (AFTRANS). Accordingly, the AMC Commander (AMC/CC) is Commander of AFTRANS (AFTRANS/CC). AMC/CC delegates operational control and appropriate authorities to 18 AF/CC to execute the AFTRANS mission. The nomenclature 18 AF (AFTRANS) is used to designate 18 AF as the subordinate

13 USTRANSCOMI 33-46, 9 JUNE Component-Numbered Air Force (C-NAF) to the C-MAJCOM. AMC provides airlift, air refueling, air mobility support, and aero-medical evacuation capability. (USTRANSCOMI 90-9) Artifact. A product that demonstrates relationships between components and conveys knowledge or facilitates decision making. Capability. The ability to execute a specified course of action under specified standards and conditions through combinations of means and ways across the doctrine, organization, training, materiel, leadership and education, personnel, facilities and policy (DOTMLPF-P) spectrum. It is defined by an operational user and expressed in broad operational terms in the format of an initial capabilities document or a joint DOTMLPF-P change recommendation. In the case of materiel proposals/documents, the definition will progressively evolve to DOTMLPF-P performance attributes identified in the capability development document and the capability production document. (CJCSM D) (AFI ) Capability Requirement. A capability required to meet an organization s roles, functions, and missions in current or future operations. To the greatest extent possible, capability requirements are described in relation to tasks, standards, and conditions in accordance with the Universal Joint Task List or equivalent DOD Component Task List. If a capability requirement is not satisfied by a capability solution, then there is also an associated capability gap which carries a certain amount of risk until eliminated. A requirement is considered to be draft or proposed until validated by the appropriate authority. (CJCSI I) (USTRANSCOMI 90-6) Champion. Person or entity that advocates (verbal or written) in favor of, supports or urges by compelling argument, and recommends the subject matter publically. Chief Architect. An appointed position responsible for developing and managing all aspects of the EA. Community of Interest. A collaborative group of users who exchange information in pursuit of their shared goals, interests, missions, or business processes, and who therefore must have a shared vocabulary for the information they exchange. The group exchanges information within and between systems to include security domains. (DODI ) (DOD Net-Centric Data Strategy) Corporate Governance Process (CGP). The CGP is the capital planning and investment control process linking budget formulation, execution, and management of IT. It is the process through which capability-based decisions are made. The CGP construct optimizes capability investments assuring the effective application of resources to realize world-class transportation related services and enabling capabilities. Distribution Process. The networks, relationships, and procedures used by the Department of Defense to control the flow and distribution of military forces and materiel between the point of receipt into the military system and the point of issue to using activities and units. (DODD )

14 14 USTRANSCOMI 33-46, 9 JUNE 2015 Distribution Process Owner. The USTRANSCOM Commander was assigned the responsibility by the Secretary of Defense to oversee the overall effectiveness, efficiency, and alignment of DOD-wide distribution activities, including force projection, sustainment, and redeployment/retrograde operations. The Distribution Process Owner has the responsibility for coordinating, sustaining, and improving distribution processes; coordinating the creation of new processes, where appropriate; and being accountable for their outcomes. The Distribution Process Owner advocates improvements for and across all DOD Components for effectiveness, efficiency, and alignment relevant to distribution processes. (DODI ) Enterprise Architecture (EA). The Department of Defense Architectural Framework defines an EA as a strategic information asset base, which defines the mission, the information necessary to perform the mission, the technologies necessary to perform the mission, and the transitional processes for implementing new technologies in response to changing mission needs. EA supports planning and decision-making through documentation and information that provides an abstracted view of an enterprise at various levels of scope and detail. The Common Approach promotes increased levels of mission effectiveness by standardizing the development and use of architectures within and between Federal Agencies. This includes principles for using EA to help agencies eliminate waste and duplication, increase shared services, close performance gaps, and promote engagement among government, industry, and citizens as defined within the Enterprise Architecture Framework (FEAF) V FEA Principles. Structure A segment architecture inherits the framework used by the EA, although it may be extended and specialized to meet the specific needs of a core mission area or common or shared service. Each Segment of the broader Enterprise that comprises the JDDA will federate to the DOD EA and will integrate and align to achieve the objectives of the JDDA. Reuse A segment architecture reuses important assets defined at the enterprise level including: data; common business processes and investments; and applications and technologies. Alignment A segment architecture aligns with elements defined at the enterprise level, such as business strategies, mandates, standards, and performance measures. (FEA Practice Guide) Functional Proponent. The advocate for enterprise capabilities across the DOTMLPF-P spectrum. With respect to IT, the functional proponent identifies the need, champions the need throughout its lifecycle and is responsible for accepting a delivered solution. Capability Gap. The inability to execute a specified course of action. The gap may be the result of no existing capability, lack of proficiency or sufficiency in an existing capability solution, or the need to replace an existing capability solution to prevent a future gap. (DODI ) (AFI ) Information Centric. An assured, dynamic, and shared information environment that provides access to trusted information for all users, based on need, independent of time and place. It is characterized by assured services, infrastructure transparency (to the user), independence of data consumers and producers, and metadata supported by information discovery, protection and producers, mediation. (DOD Information EA Version 1.1, 2009) (Realizing the Army Net- Centric Data Strategy (ANCDS) in a Service Oriented Architecture (SOA))

15 USTRANSCOMI 33-46, 9 JUNE Information Technology. Any equipment or interconnected system or subsystem of equipment that is used in the automatic acquisition, storage, manipulation, management, movement, control, display, switching, interchange, transmission, or reception of data or information. The term IT includes computers, ancillary equipment, software, firmware and similar procedures, services (including support services), and related resources. (DODI ) Joint Deployment and Distribution Architecture (JDDA). The JDDA is the EA for the JDDE. It consists of the Joint Distribution Architecture, Joint Deployment Enterprise Architecture, and JDDE COI Distribution Architectures (Source: DODI , DPO). As such, the CIO is responsible for the Joint Distribution Architecture, Joint Deployment Enterprise Architecture and JDDE COI Enterprise Architectures. Also define how the Joint Transportation Architecture fits into this family. Joint Distribution Process Analysis Center (JDPAC) Enterprise Architecture. The JDPAC EA depicts the relationship of JDPAC transportation analysis and engineering support to the USTRANSCOM enterprise and other DOD customers. It describes the internal data requirements, analytic tools, analysis process and methodologies, and the resulting products that support that mission." Joint Enabling Capabilities Command (JECC). The JECC serves as the U.S. Transportation Command subordinate joint command responsible for providing forces to newly established joint force headquarters that can rapidly deploy critical command and control capabilities. The JECC provides mission-tailored, joint capability packages to Combatant Commanders in order to facilitate rapid establishment of Joint Force Headquarters, fulfill Global Response Force execution and bridge joint operational requirements. The JECC s role in supporting the USTRANSCOM mission is identified within the Unified Command Plan as the Joint Enabling Capabilities Provider. The JECC combines capabilities across seven unique functional areas to deliver tailored, mission-specific support (Operations, Plans, Logistics, Intelligence Support, Knowledge Management, Communications, and Public Affairs). Joint Transportation Reserve Unit (JTRU). The mission of the JTRU is to augment the United States Transportation Command in providing air, land, and sea transportation for the Department of Defense, both in times of peace and war. Integrated Architecture Governance Process. The overarching EA governance process, which includes the Distribution Steering Group (DSG), Distribution Oversight Council (DOC), and Distribution Executive Board (DEB), for the JDDA (and its segments) that develop proposals, recommendations, and direct the appropriate courses of action mechanism for defining, implementing, managing and measuring the effectiveness toward specified and implied end-states. Joint Deployment and Distribution Enterprise (JDDE). The complex of equipment, procedures, doctrine, leaders, technical connectivity, information, shared knowledge, organizations, facilities, training, and materiel necessary to conduct joint distribution operations. (DODI )

16 16 USTRANSCOMI 33-46, 9 JUNE 2015 JDDE Community of Interest. The collaborative network of JDDE partner organizations, to include DOD Components, sharing common distribution-related goals, interests, missions, and business processes, which comprise end-to-end distribution, in support of Combatant Commands and/or Joint Force Commanders. (JP 4-09, Distribution Operations) Process Owner. The process owner has the responsibility for coordinating, sustaining and improving processes; coordinating the creation of new processes where appropriate; and being accountable for their outcomes. Process owners advocate for and across the Command for effectiveness, efficiency, and alignment relevant to a particular process. (DODI ) Service-Oriented. Shares capabilities across JDDE organizations through standard services that reduce duplication and inconsistency. Service-Oriented Architecture. Shares capabilities across JDDE organizations through standard services that reduce duplication and inconsistency. Transportation Working Capital Funds (TWCF). TWCF is a revolving industrial fund for defense transportation. It uses business-like cost accounting to determine the total cost of a business activity. TWCF is an expense authority and not an appropriation. (USTRANSCOM HANDBOOK 65-2) Transition Strategy. Serves as the foundation to modernize and transform activities by describing an organization s plan to migrate from its baseline architecture as described in the current architecture to its target architecture as outlined in the Architectural Vision, by defining projects, programs, timelines and milestones in the context of transition and sequencing plans. USTRANSCOM Enterprise. The complex of equipment, procedures, doctrine, leaders, technical connectivity, information, shared knowledge, organizations, facilities, training, and materiel necessary to conduct joint Defense Transportation System Operations, DPO operations, and USTRANCOM missions delineated in the Unified Command Plan. Organizationally, the USTRANSCOM Enterprise includes USTRANSCOM and its Component Commands. (JP4-01) (USTRANSCOM J3 Mission Statement)