Atch_10_-_DODAF_SV6_ _AV1_Draft_Documents.pdf

i

Coalition Mobility System (CMS)

Overview and Summary Information

AV-1

Version 1.0

Contents

ARCHITECTURE PROJECT IDENTIFICATION

SCOPE

BOUNDARIES

TIME FRAME ADDRESSED

VIEWS AND PRODUCTS DEVELOPED

COMPARISON WITH PREVIOUS VERSIONS

PURPOSE AND VIEWPOINT

PURPOSE

VIEWPOINT

CONTEXT

MISSION

DOCTRINE

GOALS

CONCEPT

VISION

RULES, CRITERIA, AND CONVENTIONS FOLLOWED

LINKAGES TO OTHER ARCHITECTURES

TOOLS AND FILE FORMATS USED

ANALYSIS

FINDINGS

RECOMMENDATIONS

REFERENCES

CMS Overview and Summary Information (AV-1)

Architecture Project Identification

Name: Coalition Mobility System (CMS) Tailored Information Support Plan (TISP)

Date Completed: 29 September 2013 (Final submission in EISP)

Organization Developing the Architecture: Tapestry Solutions, Inc., A Boeing Co.

Approval Authority: SES John Bartley, PEO, USTRANSCOM

Assumptions

As CMS is a system still under development, the products will require maintenance updates to remain current and accurate

The technology described represents a snapshot taken during the timeframe of the architecture

The organizational structures represent a snapshot taken during the timeframe of the architecture

Constraints

There are no constraints in the development of this architecture.

Scope

Boundaries

(Organizations, Processes, Geographical Regions Involved)

The processes/functionality covered in this architecture includes the elements in CMS v1.5.0.

Coalition Mobility System (CMS) is a tool set for the planning, executing, and monitoring of coalition movements. CMS supports the Coalition War Fighter by integrating mission data of

U.S. and coalition forces. CMS captures coalition information on air, land, and sea missions from multiple national sources and formats, then filters and fuses it into decision-ready information for members of specific coalitions of forces. Coalition information is populated through direct input into CMS, import of data from Single Mobility System (SMS), and direct import from other national systems. Coalition information can then be organized by coalition, country, and unit. CMS provides robust views of schedules and workloads; mission editing, monitoring, and reporting.

CMS and its Coalition Theater Logistics (CTL) entry portal are operational, with on-going efforts including sustainment of the system and development of emergent requirements in the system. Additional support is necessary to build and maintain administrative accounts, train customers, and build or modify CMS data filters and reports.

The following lists CMS key capabilities under the primary mission, followed by capability scenarios:

Mission: Visibility of Coalition Movement Data

Worldwide support to COCOMs, Coalitions, Services, Units, and Agencies

Warfighter: Facilitate Multinational Logistic Operations

Receive, fuse, and disseminate multiple countries’ and organizations’ road, rail, airlift, and sealift movement data through selective sharing

Web accessible and hosted outside the DoD NIPRnet to reach the greatest number of users

Commander and Staff Aggregation Reporting Tools

Airlift Visibility Scenario

Airlift Mission Schedules: Receive scheduled, estimated and actual airlift data

Airlift Passenger/Cargo Summary: Receive scheduled and actual data for each arrival and departure airlift mission leg

Airlift Mission Schedules: User enters or bulk imports scheduled and actual airlift data

Airlift Passenger/Cargo Summary: User enters or bulk imports scheduled and actual airlift data

Monitoring, tracking, and alerting airlift schedules

Customizable mission displays and/or aggregated displays of airlift mission data

Layered/drillable navigation from aggregated to airlift mission summary displays

Sealift Visibility Scenario

Ship Mission Schedules: User enters or bulk imports scheduled and actual sealift data

Ship Passenger/Cargo Summary: User enters or bulk imports scheduled and actual sealift data

Monitoring, tracking, and alerting ship schedules

Customizable mission displays and/or aggregated displays of ship mission data

Layered/drillable navigation from aggregated to ship mission summary displays

Convoy Visibility Scenario

Truck Convoy Schedules: User enters or bulk imports scheduled and actual convoy data

Convoy Passenger/Cargo Summary: User enters or bulk imports scheduled and actual convoy data

Monitoring, tracking, and alerting convoy schedules

Customizable mission displays and/or aggregated displays of convoy mission data

Layered/drillable navigation from aggregated to convoy mission summary displays

Rail Visibility Scenario

Train Schedules: User enters or bulk imports scheduled and actual rail data

Train Passenger/Cargo Summary: User enters or bulk imports scheduled and actual rail data

Monitoring, tracking, and alerting train schedules

Customizable mission displays and/or aggregated displays of rail mission data

Layered/drillable navigation from aggregated to rail mission summary displays

Reference Data Scenario

Provide station location workloads for airlift, sealift and land modes

Country Administrator manually enters\edits transportation location reference information

Provide searchable location reference information

All essential CMS components are included as well as an interface to the external system with which CMS transmits and receives data/information.

Users understand the product will continue to evolve to support new releases, updated hardware, added functional capabilities, and the broadening scope of the operational coalition communities.

Time Frame Addressed

This architecture describes CMS as it will exist by October 2013.

Views and Products Developed

The products to be developed are primarily those, which are required for Information Support

Plan (ISP) development (ref: DODI 4630.8).

AV-1 Overview and Summary Information

AV-2 Integrated Dictionary

OV-1 High-level Operational Concept Graphic

OV-3 Operational Information Exchange Matrix

OV-5 Activity Model

OV-6c Operational Event-Trace Description

SV-1 Systems Interface Description

SV-5 Operational Activity to Systems Function Traceability Matrix

SV-6 Systems Data Exchange Matrix

StdV-1 Standards Profile

StdV-2 Standards Forecast

Data Exposure Verification Tracking Sheet

Service Exposure Verification Tracking Sheet

Comparison with previous versions

Not Applicable. This is the first version.

Purpose and Viewpoint

Purpose

The purpose of this architecture is to identify and illustrate communications and information support requirements for the successful implementation of the Coalition Mobility System (CMS).

Specifically, the architecture is required to produce DoD Architecture Framework (DoDAF) products.

Viewpoint

The viewpoint of the architecture is that of the functional community—USTRANSCOM, COCOMs, and Coalition Partners as well as U.S. Governmental and non-Governmental agencies and organizations. Users of CMS at all levels should understand the operational views.

Maintainers/designers should be able to understand and apply the systems views.

Context

Mission

The CMS mission is to allow transportation logistics information sharing between the DoD and its partners by bridging the gap between the Internet and the NIPRnet in support of multinational logistics operations.

Doctrine

CMS was created to provide a capability for dissemination of coalition movement execution information at appropriate levels within each unique coalition environment. CMS is to provide access to coalition movement information in a timely automated manner for U.S. decision makers and coalition partners, including those who plan, execute, and use movement data, in order to facilitate movement coordination and multinational cooperation.

Goals

From a functional perspective, the goals of the CMS program are to:

Improve and enhance coordination and cooperation of coalition operations for

USTRANSCOM, COCOMs, services, units, DoD agencies, participating nations, and

U.S. Government (USGO) and non-Government (NGO) organizations.

Provide authorized users a capability to observe data for aircraft, ship, road and rail movements (Military and commercial) in support of coalition operations.

Provide users a capability to create, revise, update, delete, save, and import mission schedules for real-world coalition air, convoy, and rail or ship movements.

Provide users a capability to search for specific airport, seaport, rail and convoy terminal locations and determine the workload at that location.

Provide users a capability to add, edit, and delete specific airport, seaport, rail and convoy terminal locations from the CMS database.

Enhance reporting and analysis of coalition movement and distribution activities.

Respond to emerging requirements of DoD and coalition users through improved capabilities.

From a design perspective, the goals of the CMS program are to:

Deploy CMS on a commercial network to allow for the greatest level of accessibility via the Internet

Integrate CMS into the Coalition Theater Logistics (CTL) Portal, to provide account management and coalition security based on the user’s national affiliation and coalition participation

Maintain the CMS database in such a manner that it guarantees national data sovereignty, and includes the ability to identify which coalition operation the data pertains to

Provide multiple methods for coalition partners and U.S. users to populate the CMS database through automated updates, manual download/upload of aggregated transportation files, or manual entry through use of a graphical user interface from a U.S.

logistic system(s), a coalition partner’s national system(s), or a U.S. or coalition partner user

Provide a database query capability, with a similar look and feel, for U.S. and coalition partners, at any level, in order for them to present, update, and modify data as needed

Use standard data elements to expose data to and facilitate the exchange of data with other

U.S. systems as required by U.S. system managers

Concept

CMS supports a Coalition Joint Task Force (CJTF) by merging transportation information from multiple sources (military and commercial) into a single database to facilitate and synchronize coalition force movements. CMS is designed to aid in informing decision makers regarding the location of logistics assets and their actual operational movements.

CMS provides a means of sharing logistics data with non-U.S. DOD coalition partners who deploy, redeploy, or sustain forces using the U.S. Defense Transportation System or their own or another nation’s transportation assets. CMS provides partners with timely access to operationally relevant movement information without requiring direct access to U.S. DoD information systems. The same information may be viewed by decision makers at the CJTF location and by contributing nations’ parent headquarters.

CMS is integrated into the Coalition Theater Logistics (CTL) portal, which provides controlled access to authorized users. The CTL Portal possesses the ability to limit a user’s access to information based on the user’s national affiliation and coalition participation.

Vision

The CMS vision is to continually improve the ability of USTRANSCOM, the DoD and its coalition partners, to manage, control, and coordinate multinational coalition operations through innovative and effective data exchange methods, data retrieval and data fusion practices, and graphical user interface design.

Rules, Criteria, and Conventions Followed

The architecture is compliant with the guidance provided by the DoDAF, Version 2.02, August

2010. Specific product formats and content for DoDAF Views follow standards developed for

USTC architectures.

Data for architectural products will be developed using the data stored in existing sources. The following is the list of existing sources of information which could be used in the development of the CMS Ver 1.0 architecture or in storing architecture products.

The DoDAF Architecture Framework Version 2.02

GIG Technical Guidance Federation (https://gtg.csd.disa.mil/uam/homepage)

Command and Control Interface Design Documents (C2IDDs)

DoD IT Standards Registry (DISR Online)

Enterprise Architecture Database (EAD)

Linkages to Other Architectures

For the current CMS architecture, there are no explicitly expressed linkages to other architectures.

Tools and File Formats Used

Architecture Product Development Tool(s) Format

AV-1 Microsoft Word .pdf

AV-2 Microsoft Word .pdf

OV-1 Microsoft Powerpoint .pdf

OV-3 Microsoft Excel .pdf

OV-5 Microsoft Visio .pdf

OV-6c Microsoft Visio .pdf

SV-1 Microsoft Visio .pdf

SV-5 Microsoft Excel .pdf

SV-6 Microsoft Excel .pdf

StdV-1 Standards Profile Adobe Portable Document Format .pdf

StdV-2 Standards Forecast Adobe Portable Document Format .pdf

Data Exposure Verification Tracking Sheet Microsoft Powerpoint .pdf

Service Exposure Verification Tracking Sheet Microsoft Powerpoint .pdf

Analysis

No analysis was conducted for this version of the architecture.

Findings Not Applicable.

Recommendations Not Applicable.

References

DoD Architecture Framework Version 2.02, DoD Deputy CIO, http://dodcio.defense.gov/dodaf20.aspx https://gtg.csd.disa.mil/uam/homepage

System

ID

Sending

System System Data Exchange

Sending System

Function(s)

Receiving

System ID Receiving System

Receiving System

Function(s)

Security

Requirements

CMS Data::Fused ON1 CMS Fused Data

Obtain Data

Provide Data

Fuse Data

ON3 Coalition Users

Create Queries

Manage Queries

Run Queries

Unclassified

External::SMS ON2 SMS Mission Data ON1 CMS Data::Fused

Obtain Data

Provide Data

Fuse Data

Unclassified

Coalition Users ON3 CMS Mission Data ON1 CMS Data::Fused

Obtain Data

Provide Data

Fuse Data

Unclassified

Coalition Mobility System Architecture

Operational Information Exchange Matrix (SV-6) v1.0

Single Mobility System (SMS)

Overview and Summary Information

(AV-1)

Version 2.0

Contents

ARCHITECTURE PROJECT IDENTIFICATION

SCOPE

BOUNDARIES

TIME FRAME ADDRESSED

VIEWS AND PRODUCTS DEVELOPED

COMPARISON WITH PREVIOUS VERSIONS

PURPOSE AND VIEWPOINT

PURPOSE

VIEWPOINT

CONTEXT

MISSION

DOCTRINE

GOALS

CONCEPT

VISION

RULES, CRITERIA, AND CONVENTIONS FOLLOWED

LINKAGES TO OTHER ARCHITECTURES

TOOLS AND FILE FORMATS USED

ANALYSIS

FINDINGS

RECOMMENDATIONS

REFERENCES

i

SMS Overview and Summary Information (AV-1) 29 Sept 2013

Architecture Project Identification Name: Single Mobility System (SMS) Tailored Information Support Plan (TISP)

Date Completed: 30 September 2013 (Final submission in EISP)

Organization Developing the Architecture: Tapestry Solutions, Inc., A Boeing Co.

Approval Authority: SES John Bartley, PEO, USTRANSCOM

Assumptions:

• As SMS is a system still under development, the products will require maintenance updates to remain current and accurate

• The technology described represents a snapshot taken during the timeframe of the architecture

• The organizational structures represent a snapshot taken during the timeframe of the architecture

Constraints: There are no constraints in the development of this architecture.

Scope

Boundaries (Organizations, Processes, Geographical Regions Involved) The processes/functionality covered in this architecture includes the elements in SMS v9.10.6.

SMS is a globally-oriented system designed to be used at any location worldwide to support a wide variety of DoD logistics operations. The system supports all organizations involved in providing visibility of DoD logistics operations, and these organizations are within the scope of the architecture.

The key capabilities of SMS are listed below under the primary mission, followed by capability scenarios:

Mission: Visibility of Joint Deployment and Distribution Enterprise (JDDE)

• Provides worldwide support to all Combatant Commands (COCOMs), Services, Units, and Agencies

• Facilitates Combat Power Projection for the Warfighter

• Receives, fuses, and disseminates multiple systems’ data

• Web accessible

• Provides Commander Decision Support Tools

• Provides Staff Analysis Tools

Force Deployment and Redeployment Scenario

• Receives COCOM Force Planning Data

• Receives Estimated and Actual Airlift and Sealift Scheduling Data

• Fuses Planning and Actual data to determine on-time force closure metrics

• Assists users in organizing data into meaningful units

• Graphically displays customized/aggregated data

• Provides layered/drillable navigation from aggregated-to-detail displays

• Alerts, tracks, and monitors schedules

• Provides research tools, briefing displays for staff to advise commander

Airlift Visibility Scenario

• Airlift Schedules: Receive Airlift Estimated, Scheduled, and Actual data

• Airlift Cargo: Receive Airlift manifest data

• Airlift Reference: Receive Airlift type reference data

• Alerts, tracks, and monitors airlift schedules

• Creates customizable/aggregated displays of data

• Provides layered/drillable navigation from aggregated-to-detail displays

• Creates and provides Air Force Reserve Command (AFRC) planning, and scheduling data to Airlift System of Record

Sealift Visibility Scenario

• Vessel management: Creates customizable displays supporting vessel selection, planning and activations

• Vessel schedules:

– Military: Create and provide military sealift planning, scheduling, allocation, and actual arrivals data to JDDE

– Commercial: Receive commercial sealift schedules

• Sealift Cargo: Receive sealift manifest data

• Sealift Reference Data: Receive sealift ship characteristics reference data

• Tracks and monitorssealift schedules

• Facilitates coordination of sealift activities between Transportation Component

Commands (TCCs), i.e., Surface Deployment and Distribution Command (SDDC) and Military Sealift Command (MSC).

Reference Data Scenario

• Provide customizable and calculated transportation cost estimates for airlift, sealift and land modes

• Receive transportation location reference information

• Provide searchable location reference information

All essential SMS components are included as well as interfaces to those external systems with which SMS transmits and receives data/information.

Users understand the products will continue to evolve to support newer releases, updated hardware, increased functional capabilities, and the broadening scope of the operational community.

Time Frame Addressed This architecture describes SMS as it will exist by October 2013.

Views and Products Developed The products to be developed are primarily those which are required for Information Support Plan (ISP) development (ref: DODI 4630.8).

AV-1 Overview and Summary Information AV-2 Integrated Dictionary OV-1 High-level Operational Concept Graphic OV-3 Operational Information Exchange Matrix OV-5 Activity Model OV-6c Operational Event-Trace Description SV-1 Systems Interface Description SV-5 Operational Activity to Systems Function Traceability Matrix SV-6 Systems Data Exchange Matrix StdV-1 Standards Profile StdV-2 Standards Forecast

Comparison with previous versions SMS DoDAF documents, Version 1.0, were based on conformance to DoD Architecture Framework (DoDAF), Version 1.0, Aug 2003. Version 2.0 reflects the updates/changes as prescribed by the DoDAF, Version 2.02, August 2010.

Purpose and Viewpoint

Purpose The purpose of this architecture is to identify and illustrate communications and information support requirements for the successful implementation of the Single Mobility System (SMS).

Specifically, the architecture is required to produce DoD Architecture Framework (DoDAF) products.

Viewpoint The viewpoint of the architecture is that of the functional community—USTRANSCOM and its Transportation Component Commands (TCCs). Users of SMS at all levels should understand the operational views. Maintainers/designers should be able to understand and apply the systems views.

Context

Mission The SMS mission is to provide deployment, redeployment, transportation, and logistics data visibility for the Joint Deployment and Distribution Enterprise (JDDE) user community. SMS also assists USTRANSCOM in execution of their DPO responsibilities.

Doctrine SMS was created to innovate the access of mobility mission information from the TCCs to USTRANSCOM, between COCOMs and for units worldwide, ultimately aiding the logistical decision making process in support of the Warfighter.

Goals From a functional perspective, the goals of the SMS program are to:

• Improve and enhance collaborative C2 planning and decision making for USTRANSCOM, TCCs, COCOMs, and units

• Provide near real-time access with automatic updates of planning and actual data via a single, automated system that interfaces with the multiple planning tools and systems currently throughout the DoD

• Enhance planning and analysis of operational deployment and distribution activities

• Respond to evolving requirements of TCCs and JDDE users through improved capabilities From a design perspective, the goals of the SMS program are to:

• Satisfy Joint Staff concepts of horizontal and vertical communications to plan and execute missions

• Migrate C2 systems to comply with DoD/DISA/USTRANSCOM architecture, communications and security standards in order to reduce risk and maintain currency

• Use DoD standard data elements to facilitate the exchange of data and ensure interoperability with other C2 systems.

Concept SMS is a central component of USTRANSCOM's command and control system. As an automated C2 system, its success relies on the availability of C2 information. SMS queries various C2 and mobility systems to gather information for displaying to functional users for monitoring, tracking, analysis, research, and decision-making.

SMS provides functional users and mission planners a unified method to access mobility information by providing a single-screen, integrated view of USTRANSCOM and TCC C2 systems’ data. The unified information access supports enchanced management of essential mobility resources’ efficient allocation to missions, and thus increasing mission effectiveness.

Vision The SMS vision is to continually improve USTRANSCOM's command and control capability as an enhanced multi-system environment used for managing mobility systems through innovative and effective data retrieval methods, data fusion practices, and graphical user interface design.

Rules, Criteria, and Conventions Followed The architecture is compliant with the guidance provided by the DoDAF, Version 2.02, August 2010. Specific product formats and content for DoDAF Views follow standards developed for USTC architectures.

Data for architectural products will be developed using the data stored in existing sources.

The following is the list of existing sources of information which could be used in the development of the SMS Ver 2.0 architecture or in storing architecture products.

• The DoDAF Architecture Framework Version 2.02

• https://gtg.csd.disa.mil/uam/homepage

• Command and Control Interface Design Documents (C2IDDs)

• DoD IT Standards Registry (DISR Online)

• Enterprise Architecture Database (EAD)

Linkages to Other Architectures For the current SMS architecture, there are no explicitly expressed linkages to other architectures.

Tools and File Formats Used Architecture Product Development Tool(s) Export Format AV-1 Microsoft Word .docx AV-2 Microsoft Word .docx OV-1 Microsoft Powerpoint .pptx OV-3 Microsoft Excel .xlsx OV-5 Microsoft Visio .pptx OV-6c Microsoft Visio .vsd SV-1 Microsoft Visio .vsd SV-5a Microsoft Excel .xlsx SV-5b Microsoft Excel .xlsx SV-6 Microsoft Excel .xlsx StdV-1 Standards Profile Adobe Portable Document Format .pdf StdV-2 Standards Forecast Adobe Portable Document Format .pdf

Analysis No analysis was conducted for this version of the architecture.

Findings Not Applicable.

Recommendations Not Applicable.

References USTC SMS, Concept of Operations (CONOPS), version 1.0, 1 October 1998

DoDAF, Version 2.02, August 2010

Single Mobility System Operational Requirements Document (ORD), December 22, 1999

SMS Systems Data Exchange Matrix (SV-6) for JOPES (S) Data Description Producer Consumer Nature of Transaction

Interface Identifier

Data Exchange Identifier

Name Content Format Type

Media Type Accuracy

Sending System

Name/Id

Sending System

Function

Receiving System

Name/Id

Receiving System

Function

Transaction Type

Triggering Event Criticality

ITF-1.01 DE-1 SQL TPFDD SQL Network 95% JOPES/

ON19

SQL

Database SMS/ON17 DataImport SQL SQL 2

ITF-1.01 DE-2 BDEX TPFDD XML Network 95% JOPES/ ON19 JDNETS SMS/ON17 DataImport Query

Response Update Request 2

ITF-1.01 DE-3 TDEX TPFDD

Changes XML Network 95% JOPES/

ON19 JSUB SMS/ON17 DataImport Update JOPES Request 2

Performance Attributes Information Awareness Security

Interface Identifier

Data Exchange Identifier

Periodicity Timeliness Throughput Size Access Control Availability Integrity Releasability Protection Classification

ITF-1.01 DE-1 As Required

<= 12 hours 2 Mbps 10 KB-

500 MB 3 Always Guaranteed US Only 3 Secret

ITF-1.01 DE-2 As Required <= 4 hour 2 Mbps 10 KB –

500MB 3 Always Guaranteed US Only 3 Secret

ITF-1.01 DE-3 As Required <= 1 hours 150 Kbps 1KB-

50MB 3 Always Guaranteed US Only 3 Secret

NOTES

Criticality Codes are defined in DOD Architecture Framework (DODAF) 1.5 DEX: Refers to a file format used for transportation data BDEX: DEX file containing related movement data (usually a single transportation plan in its entirety) TDEX: DEX file used to updated individual pieces of a transportation plan

Sending System Function Description

SQL Database: JOPES will maintain the capability to allow SMS to connect directly to the JOPES SQL database to download complete TPFDDs.

JDNETS: JOPES will provide SMS the ability to access JDNETS web services to download complete TPFDDs (BDEX).

JSUB: JOPES will provide SMS the ability to access the JSUB web service to download updates to TPFDDs (TDEX).

System ID Sending System System Data Exchange Sending System Function(s) Receiving System ID Receiving System Receiving System Function(s) Security

Requirements

SMS Data (S) :: HorseBlanket ON1 SMS (S) ULN Allocations

Manage Ship Allocations Track Seaport Workload Submit Ship Allocations ON9 External (S) :: GTN Secret

SMS Data (U) :: Denton ON2 SMS (U) Donor Requirements Manage Humanitarian Donor Shipments and Requirements ON18 SMS Data (U) :: Fused

Obtain Data Provide Data Fuse Data Unclassified

SMS Data (U) :: Denton ON2 SMS (U) Donor Shipments Manage Humanitarian Donor Shipments and Requirements ON18 SMS Data (U) :: Fused

Obtain Data Provide Data Fuse Data Unclassified

SMS Data (U) :: Opportune ON3 SMS (U) Opportune Requirements Manage Opportune Requirements ON18 SMS Data (U) :: Fused Obtain Data Provide Data Fuse Data Unclassified

SMS Data (U) :: AFRC ON4 SMS (U) AFRC Requirements Manage AFRC Requirements Manage AFRC Missions ON18 SMS Data (U) :: Fused

Obtain Data Provide Data Fuse Data Unclassified

SMS Data (S) :: FMT ON5 SMS (S) Force Movements Manage FMTs ON17 SMS Data (S) :: Fused Obtain Data Provide Data Fuse Data Secret

External (U) :: GDSS ON7 GDSS (U) Mission Data ON18 SMS Data (U) :: Fused Obtain Data Provide Data Fuse Data Unclassified

External (U) :: GDSS ON7 GDSS (U) Station Data ON18 SMS Data (U) :: Fused Obtain Data Provide Data Fuse Data Unclassified

External (U) :: GDSS ON7 GDSS (U) SAAM Request Data ON18 SMS Data (U) :: Fused Obtain Data Provide Data Fuse Data Unclassified

External (U) :: GDSS ON7 GDSS (U) Channel Planset Data ON18 SMS Data (U) :: Fused Obtain Data Provide Data Fuse Data Unclassified

External (U) :: GTN ON8 GTN (U) GATES Airlift Manifest Data ON18 SMS Data (U) :: Fused Obtain Data Provide Data Fuse Data

External (U) :: GTN ON8 GTN (U) IBS Booking Data ON18 SMS Data (U) :: Fused Obtain Data Provide Data Fuse Data

External (U) :: GTN ON8 GTN (U) IBS Schedule Data ON18 SMS Data (U) :: Fused Obtain Data Provide Data Fuse Data

External (U) :: GTN ON8 GTN (U) DAASC Requistion Data ON18 SMS Data (U) :: Fused Obtain Data Provide Data Fuse Data

External (U) :: GTN ON8 GTN (U) EDI214 MCM Transaction Data ON18 SMS Data (U) :: Fused Obtain Data Provide Data Fuse Data

External (U) :: GTN ON8 GTN (U) Container Data ON18 SMS Data (U) :: Fused Obtain Data Provide Data Fuse Data Unclassified

External (S) :: GTN ON9 GTN (S) MSC IC3 Ship Schedule Data ON17 SMS Data (S) :: Fused Obtain Data Provide Data Fuse Data Secret

External (S) :: GTN ON9 GTN (S) MSC IC3 Ship Tracking Data ON17 SMS Data (S) :: Fused Obtain Data Provide Data Fuse Data Secret

External (S) :: GTN ON9 GTN (S) IC3 Location Data ON17 SMS Data (S) :: Fused Obtain Data Provide Data Fuse Data Secret

External (S) :: GTN ON9 GTN (S) Ocean Moved Container Transaction Data ON17 SMS Data (S) :: Fused

Obtain Data Provide Data Fuse Data Secret

Single Mobility System Architecture v0.1 Operational Information Exchange Matrix (SV-6)

External (U) :: USTC ON10 USTC (U) GEMS Data ON18 SMS Data (U) :: Fused Obtain Data Provide Data Fuse Data Unclassified

External (U) :: USTC ON10 USTC (U) FAA Flight Data ON18 SMS Data (U) :: Fused Obtain Data Provide Data Fuse Data Unclassified

External (U) :: USTC ON10 USTC (U) WPS Manifest Data ON18 SMS Data (U) :: Fused Obtain Data Provide Data Fuse Data Unclassified

External (U) :: USTC ON10 USTC (U) DTTS Transaction Data ON18 SMS Data (U) :: Fused Obtain Data Provide Data Fuse Data Unclassified

External (S) :: GDSS ON12 GDSS (S) Mission Data ON17 SMS Data (S) :: Fused Obtain Data Provide Data Fuse Data Secret

External (S) :: GDSS ON12 GDSS (S) Station Data ON17 SMS Data (S) :: Fused Obtain Data Provide Data Fuse Data Secret

External (S) :: USTC ON13 USTC (S) FAA Flight Data ON17 SMS Data (S) :: Fused Obtain Data Provide Data Fuse Data Secret

External (U) :: SDDC ON14 SDDC (U) SITREP Data ON18 SMS Data (U) :: Fused Obtain Data Provide Data Fuse Data Unclassified

External (U) :: SDDC ON14 SDDC (U) SPOTREP Data ON18 SMS Data (U) :: Fused Obtain Data Provide Data Fuse Data Unclassified

External (U) :: JALIS ON15 JALIS (U) Mission Data ON18 SMS Data (U) :: Fused Obtain Data Provide Data Fuse Data Unclassified

External (U) :: CMS ON16 CMS (U) Mission Data ON18 SMS Data (U) :: Fused Obtain Data Provide Data Fuse Data Unclassified

SMS Data (S) :: Fused ON17 SMS (S) Fused Data Obtain Data Provide Data Fuse Data ON11 JDDE Users (S)

Create Queries Manage Queries Run Queries Secret

SMS Data (U) :: Fused ON18 SMS (U) Fused Data Obtain Data Provide Data Fuse Data ON6 JDDE Users (U)

Create Queries Manage Queries Run Queries Unclassified

SMS Data (U) :: Fused ON18 SMS (U) CMS Mission Data Obtain Data Provide Data Fuse Data ON17 SMS Data (S) :: Fused

Obtain Data Provide Data Fuse Data Unclassified

SMS Data (U) :: Fused ON18 SMS (U) JALIS Mission Data Obtain Data Provide Data Fuse Data ON17 SMS Data (S) :: Fused

Obtain Data Provide Data Fuse Data Unclassified

SMS Data (U) :: Fused ON18 SMS (U) SDDC SITREP Data Obtain Data Provide Data Fuse Data ON17 SMS Data (S) :: Fused

Obtain Data Provide Data Fuse Data Unclassified

SMS Data (U) :: Fused ON18 SMS (U) WPS Manifest Data Obtain Data Provide Data Fuse Data ON17 SMS Data (S) :: Fused

Obtain Data Provide Data Fuse Data Unclassified

External (S) :: JOPES ON19 JOPES (S) OPLAN Data ON17 SMS Data (S) :: Fused Obtain Data Provide Data Fuse Data Secret

External (S) :: SDDC ON20 SDDC (S) SITREP Data ON17 SMS Data (S) :: Fused Obtain Data Provide Data Fuse Data Secret

External (S) :: SDDC ON20 SDDC (S) SPOTREP Data ON17 SMS Data (S) :: Fused Obtain Data Provide Data Fuse Data Secret

References