4.1 Description

The C4ISR Architecture Framework describes the primary purpose of a system architecture as enabling or automating operational activities through physical processes. Today within the USIGS and NIMA, operational requirements are met through the combined efforts of a number of tailored individual systems which are each designed to meet very specific requirements. While this network of discrete systems has the advantage of providing focused local support capabilities, and redundant capabilities USIGS-wide, it lacks the ability to rapidly reconfigure in response to changing customer needs, or to systematically incorporate technology advances. It also lacks the characteristics needed to support future compliance with USIGS Operational and Technical Architectures, and the Conceptual Data Model. Key future USIGS characteristics include: interoperability, seamless data access, and JTA/DII COE compliance.
 
As NIMA, and other USIGS imagery and geospatial production organizations, transition from their current role as providers of "products" to providers of "information and services," the USIGS System Architecture must also evolve to reflect this paradigm shift. The USIGS Migration Plan describes the approach for evolving multiple "As-Is" systems into a single, integrated "To-Be" system, the USIGS. USIGS System Architecture products with multiple views are needed to facilitate this transition.
 
"As-Is" System View

The "As-Is" USIGS System Architecture describes operational capabilities in terms of existing NIMA systems. This view of the system architecture is critical to establishing the baseline starting point for executing near term migration goals. "As-Is" system products describe interface relationships and interoperability profiles and standards (USIGS System/Segment Element Interface Diagram and USIGS System/Segment Element Interface Matrices).

"To-Be" System View

The "To-Be" USIGS System Architecture Description (USAD) view reflects the paradigm shift as multiple systems are replaced by interoperable software services comprised of common and mission specific software applications. "To-Be" system architecture products describe the USIGS functional components, their configurations and linkages (System Element Interface Description), system interface relationships (System Information Exchange Matrices), and interoperability profiles and standards (USIGS Interoperability Profile).

4.2 Major Influences

• NIMA Business Plan
• NIMA Operations Directorate Vision
• IGC Operations Vision
• USIGS Operational Architecture Description
• USIGS Technical Architecture
• USIGS Conceptual Data Model

The USIGS is the single, integrated system evolving from multiple systems to support the Imagery and Geospatial Community (IGC) for acquisition and production of imagery, imagery intelligence, and geospatial information. USIGS System Architecture products describe the system architecture comprising the USIGS, and define implementation requirements that must be met by vendors and development contractors providing the components of the USIGS in support of the IGC.

The USIGS System Architecture Description is a three-volume set that documents the System Architecture products. It provides USIGS Architecture direction to NIMA organizations, supporting development offices, and contractors. For organizations outside NIMA, these products provide information and guidance to enable them to plan and program technical and infrastructure capabilities that will ensure responsive, interoperable access to imagery, imagery intelligence, and geospatial information.

Volume I is the "To-Be" System Architecture Description. It provides graphic depiction's of the USIGS functional components, their configurations and linkages, and details internal and external information exchanges, processing, and storage requirements. Volume I describes the "To-Be" USIGS architecture through two products: the System Element Interface Description (SEID) and the System Information Exchange Matrix (SIEM). In addition, this volume explains the architectural concepts being implemented in compliance with the DII COE and the JTA, and the relationship among these components and various USIGS products.

System Architecture products build upon information documented by the Operational and Technical Architectures, and the Conceptual Data Model. These relationships are illustrated in Figure 4-1.

The information flowing on the numbered lines of Figure 4-2 represents the following information flows:

A: The Technical Architecture mandates the use of the USIGS Conceptual Data Model, which standardizes data element usage in the USIGS.

B: The UOAD identifies information needs to the UCDM

C: The UOAD identifies requirements for which services must be provided. The USIGS Technical Architecture identifies the standards specifications that are necessary to satisfy those requirements.

D: IERM Information Element maps to the Data models in the UCDM.

E: Information Exchange Requirements Matrix (IERM) Activity Name maps directly to the System Information Exchange Matrix (SIEM) Operations Activity.

F: IERM Information Element maps directly to the SIEM Information Element.

G: IERM Media maps directly to the SIEM Media: E, D, H, T, F, V.

H: IERM Classification maps directly to the SIEM Security Attributes: TS/SCI, S, U.

I: IERM Caveat maps to the SIEM Security Caveat.

J: IERM Minimum Time to Accomplish and Volume will map to the SIEM Performance Attributes.

K: IERM Minimum Time to Accomplish and Volume will map to the SIEM Performance Attributes.

L: SIEM Applicable Mission Specific Application Categories and Applicable Common Support Services are selected from the Technical Reference Model (TRM) and perform the functions necessary to achieve the Operations Activity.

M: The Standards Profile identifies the specifications and standards (current mandates and basic rules/guidelines) that drive the SIEM Applicable API/ICD, Media and Data Format.

N: The Conceptual Data Model is the foundation for SIEM interface data and UIP to build upon.

O: The SEID identifies the Functional Component Name and maps it directly to the SIEM.

P: SIEM Functional Component Name maps to the USIGS Interoperability Profile (UIP) Functional Component.

Q: The UIP will profile SIEM Applicable Mission Specific Application Categories mapped from the TRM to ensure interoperability when implemented.

R: The SEID identifies the Interface Line ID and maps it directly to the SIEM.

S: The UIP will profile SIEM Applicable Common Support Services mapped from the TRM to ensure interoperability when implemented.

T: SIEM Applicable API/ICD maps to the UIP method.

U: SIEM Interface Line ID identifies the existence of interfaces and the UIP will ensure their consistency with the UTA Standards Profile for interoperability.

V: SIEM Applicable API/ICD maps to the UIP method.

W: The Standards Profile identifies the specifications and standards (as in line 13) that are implemented by the UIP and identified in the SIEM.

Volume II, the USIGS Interoperability Profile (UIP), is designed to facilitate interoperability and seamless access between multiple clients and services within the IGC. The UIP provides a tailored, system-specific interface (system-to-system) standards profile through selection of common interface standards required for implementation in specific USIGS systems. Key interfaces are defined along with critical interface data interchange standards necessary to insure interoperability and connectivity between heterogeneous systems.

Volume III, the "As-Is" System Architecture Description, describes the current USIGS architecture through two products: the USIGS System/Segment Element Interface Diagram and the USIGS System/Segment Element Interface Matrix. The USIGS System/Segment Element Interface Diagram indicates which As-Is USIGS Architecture Systems/Segments share an interface. The USIGS System/Segment Element Interface Matrix provides details of that interface.

System Architecture products include:

• USIGS System Element Interface Description "To-Be" (Volume I)
• USIGS System Information Exchange Matrix "To-Be" (Volume I)
• USIGS Interoperability Profile (UIP) (Volume II)
• USIGS System/Segment Element Interface Diagram "As-Is" (Volume III)
• USIGS System/Segment Interface Matrix "As-Is" (Volume III)

4.3.1 USIGS System Element Interface Description "To-Be" (Volume I)

The USIGS System Element Interface Descriptions (SEIDs) are top level pictorial depictions of the USIGS Elements, their configurations, and linkages. These views provide a pictorial realization of the Operations Vision and Operations Architecture which allows early analysis of internal and external information exchanges, processing, storage requirements, and operational concept feasibility.

4.3.2 USIGS System Information Exchange Matrix "To-Be" (Volume I)

The System Information Exchange Matrices (SIEMs) are tabular format depiction's of applications/services and their information exchanges between nodes. This product traces the path of an information exchange from its source to its destination describing system specific details such as protocols, data or media formats, security constraints, and performance characteristics. Its purpose is to link together the Operational, System, and Technical Architectures by mapping Applications/Services to Operational Architecture Activities and to expose information exchange requirements.

4.3.3 USIGS Interoperability Profile (UIP) (Volume II)

The USIGS Interoperability Profile (UIP) defines profiles of interface standards used to achieve interoperability between multiple clients and servers within the USIGS Architecture. Key interfaces are defined along with critical data interchange standards to assure interoperability and connectivity among the various functional components. By outlining a set of standards and standards profiles, the UIP details specific interface behavior, thereby defining the minimum requirements for access and connectivity among these components.

4.3.4 USIGS System/Segment Element Interface Diagram "As-Is" (Volume III)

The USIGS System/Segment Element Interface Diagram displays all the system/segments that comprise the As-Is USIGS architecture along its diagonal and illustrates an interface between two systems/segments with a symbol along the intersection of a column and a row. For each marked interface, at least one USIGS System/Segment Element Interface Matrix (one for each interface) will exist that describes the interface in detail.

4.3.5 USIGS System/Segment Element Interface Matrix "As-Is" (Volume III)

The USIGS System/Segment Element Interface Matrices provide details to the interfaces illustrated in the USIGS System/Segment Element Interface Diagram. They provide information on the hardware and software of the receiver and sender systems/segments and the networks that are being used. They also give the communication standards that are being used as well as the data that will be exchanged. If an ICD controls the interface, then it will be referenced.

4.4 USIGS System Architecture Product Linkages

A: The "As-Is" Systems/Segment Element Interface Diagram is used to indicate where interfaces exist between systems which may be profiled in the UIP.

B: UIP compliant systems are indicated in the Interface control document column of the System/Segment Element Interface Matrices.

C: The "As-Is" System/Segment Element Interface Diagram is used to provide insight into where interfaces need to exist in system elements depicted in the "To-Be" System Element Interface Descriptions.

D: The "As-Is" System/Segment Element Interface Matrices are used to provide insight into the details of the interfaces depicted in the "To-Be" System Information Exchange Matrices.

E: The "To-Be" System Information Exchange Matrices are used to indicate where interfaces exist between system elements which may be profiled in the UIP.