Appendix_B_ICD.pdf

Defense Information Systems Agency Global Combat Support Systems - Joint Interface Control Document

GCSS-J Consumer ICD with Data Source (XXX) Page 1

INTERFACE CONTROL DOCUMENT

BETWEEN

THE DEFENSE INFORMATION SYSTEMS AGENCY

GLOBAL COMBAT SUPPORT SYSTEM – JOINT

AND

XXX AGENCY

XXX PROGRAM

XXX DATA SOURCE

DATE

GCSS-J Consumer ICD with Data Source (XXX) Page 2

TABLE OF CONTENTS

1 General

1.1 Interfacing Systems Names

1.2 Purpose

1.3 Revision History

1.4 Scope

1.5 Business Requirement

1.6 Points of Contact

1.7 Roles and Responsibilities

1.8 Reference Documents

2 Interface Overview

2.1 Interface Description

2.2 Connectivity Details

3 Change Management 4 XXX Tables Used Within GCSS-J

TABLE OF TABLES

Table 1 – Revision History Table 2 – XXX Points of Contact Table 3 – GCSS-J Points of Contact Table 4 – Interface Description

GCSS-J Consumer ICD with Data Source (XXX) Page 3

1 General

1.1 Interfacing Systems Names

Providing System Name: Data Source (XXX) Consuming System Name: Global Combat Support System Joint (GCSS-J)

1.2 Purpose

This Interface Control Document (ICD) outlines the functional and technical exchange between GCSS-J and XXX. This document outlines interface points of contact, interface specifications, and data processing workflow. This document also supplements the Memorandum of Agreement (MOA) established for XXX and GCSS-J.

1.3 Revision History

Version Revision Date Description Entered By

1.0 GCSS-J ICD

Table 1 – Revision History

1.4 Scope

This document details the interactions between the XXX and GCSS-J PMO. Areas of focus for the document include:

• Description of the data exchanges

• Data formats

• Change management to maintain consistent, integration, and operation between programs

• Required interface mappings and specifications

1.5 Business Requirement

The Joint Staff J4, the GCSS-J functional sponsor, has identified XXX as an authoritative data source to provide strategic assessments and national policy decision-making data. As the authoritative data source, XXX provides the primary repository of intelligence data to the Department of Defense and allied forces mission planners and war-fighters.

GCSS-J Consumer ICD with Data Source (XXX) Page 4

1.6 Points of Contact

XXX Points of Contact

Name Role Phone Email

Table 2 – XXX Points of Contact

DISA/ GCSS-J Points of Contact

Name Role Phone Email

Table 3 – GCSS-J Points of Contact

1.7 Roles and Responsibilities

Refer to the MOA for specific responsibilities.

1.8 Reference Documents

MOA between DISA/GCSS-J and DISA/GCCS-J/XXX

2 Interface Overview

XXX provides intelligence information from the Defense Intelligence Agency (DIA) XXX to the Global Command and Control System-Joint Integrated Intelligence and Imagery (GCCS-J I3) application. XXX is a structured relational database. Data elements are highly structured in American Standard Code for Information Interchange (ASCII) format. Data is replicated between XXX and Intelligence Shared Data Server (ISDS) databases, sharing the same schema. Data sources are DIA tactical message (Order of Battle Report (OBREP), Imagery Interpretation Report (IIR), Intelligence Report (INTREP)) via Automated Message Handling System (AMHS)/Joint Message Handling System (JMHS).

GCSS-J Consumer ICD with Data Source (XXX) Page 5

2.1 Interface Description

Interface Name: GCSS-J/ XXX

Interface Type: Web service

Interface Short Description:

XXX provides integration of various text, images, and maps from the intelligence community to GCSS-J (SIPRNET) via a web service request.

Source Application: XXX

Destination Application: GCSS-J

Functional Requirement References: Combatant Command 129 Requirements

Table 4 – Interface Description

2.2 Connectivity Details

The GCSS-J/XXX interface is a SOAP application protocol from the GCSS-J Data Mediator, Enterprise Data Service (EDS) to the views created in the XXX database. The connection allows GCSS-J EDS to execute against the XXX Web service. The data access capability will:

• Be restricted to Read-Only.

• Be implemented using standard web services through Hyper Text Transfer Protocol

(HTTP) and Extensible Markup Language (XML) protocols compatible with GCSS-J EDS interface.

• Allow the use of the data by the GCSS-J user community.

• Allow the release of the data via GCSS-J produced web services.

The following table details basic connectivity information only. Sensitive connectivity data such as IP addresses, port numbers, usernames and passwords, database connection strings, and the like will be transferred between the provider and the XXX administrative personnel during the implementation of this interface

3 Change Management

Prior to ICD approval, all changes will be considered part of the normal development process.

After approval, any changes to the interface which may affect the successful transmission, receipt, and processing of data specified in this ICD must go through the Change Management Procedures. Such changes include:

GCSS-J Consumer ICD with Data Source (XXX) Page 6

1. Change of large magnitude in data/query volumes.

2. Change in the source or destination server configuration which may affect transmission or reception of the data.

3. Change in the source or destination location on a server or the account used to access the data on either server.

4. Change in any database configuration that would affect access to database tables.

5. Change in style of record format, for instance going from ASCII delimited to fixed field.

6. Any syntactical change in a record format including:

a. length of a field

b. type of a field

c. addition or deletion of fields

d. change in delimiter or positioning of fields

e. change in format (numeric or date) for a field

7. Any semantic changes in records or fields that may affect the business rules associated with the data.

8. Any changes to previously specified constraints to fields or records such as not-null changed to nulls allowed or a primary key constraint.

4 XXX Files Used Within GCSS-J