The USIGS Architecture establishes a set of requirements and guidelines that must be followed when acquiring new capabilities or modifying existing capabilities. Compliance with these requirements and guidelines, as defined in the USIGS Operational Architecture, USIGS System Architecture, USIGS Technical Architecture, and USIGS Conceptual Data Model, will result in an integrated, interoperable system, with minimal redundant functionality that supports the sharing of data, services and resources among the IGC. A USIGS Architecture Compliance Checklist is provided as Appendix IV.

The USIGS architecture products and migration products drive the remaining USIGS documents either directly or indirectly. Figure 7-1 depicts these document linkages, while Table 7-1 provides descriptions of the Enterprise Planning and Program Element documents depicted in Figure 7-1.

Figure 7-1 USIGS Architecture and Migration Planning Product Linkages to Enterprise Planning and Program Element-Level Documents

The linkages identified in Figure 7-1 are explained as follows:

A. The USIGS Interoperability Profile provides the Program Element Test, Evaluation, Transition, and Integration Plan and Procedures with interface requirements that require verification.

B. The USIGS Interoperability Profile provides the Program Element Requirements Specification with the profile for interface standards, application program interfaces for OGE services, and communication protocols.

C. The USIGS Interoperability Profile provides the USIGS Test, Evaluation, Transition, and Integration Plan with interface requirements that require verification.

D. The USIGS Interoperability Profile/Application Program Interface Specifications/USIGS Common Object Specification provides the USIGS Enterprise Requirements Specification with the profile for interface standards, application program interfaces for OGE services, and communication protocols. The USIGS Enterprise Requirements Specification provides the USIGS Interoperability Profile/Application Program Interface Specifications/USIGS Common Object Specification with requirement changes that impact interfaces.

E. The USIGS Technical Architecture provides the USIGS Enterprise Requirements Specification with the USIGS profile for the JTA, USIGS Standards and Specifications, Conventions, Guidelines, MSAs, CSAs, OGEs, Common Facilities, and Platform Services.

F. The USIGS Conceptual Data Model provides the Logical Data Models with the data structures, definitions, and relationships of all USIGS data types, data names, and data characteristics.

G. The USIGS Conceptual Data Model provides the USIGS Enterprise Requirements Specification with the data structures, definitions, and relationships of all USIGS data types, data names, and data characteristics.

H. The As-Is Systems Architecture provides the USIGS Enterprise Requirements Specification with the current baseline from which migration occurs, it identifies existing systems/segments and functionality that comprise the baselines, and it identifies existing interfaces.

I. The "As-Is" Systems Architecture provides the system baseline for establishing migration of USIGS functionalities defined within the EPIP.

J. The To-Be Systems Architecture provides the USIGS Enterprise Requirements Specification with the definition of the goal of USIGS migration; it defines planned relationships between components, functionality and data.

K. The "To-Be" Systems Architecture provides the target architecture that provides the build-to functional requirements that define USIGS Effectivities within the EPIP.

L. The Functional Manager's Guidance Input Forms provide a standard template for developing and providing inputs to the Director, for inclusion in NIMA's Functional Manager's Guidance for the Imagery and Geospatial Community.

M. The Director of Central Intelligence and Deputy Secretary of Defense's Joint Intelligence Guidance, and other like guidance external to NIMA, provide Intelligence Community and Department of Defense-wide guidance that establishes the overarching framework for NIMA's Functional Manager's Guidance for the Imagery and Geospatial Community.

N. The USIGS EPIP provides the USIGS Enterprise Requirements Specification with a high-level plan for migration of major functionality by effectivity; detailed functionality binned by effectivity and program element.

O. The USIGS EPIP provides the USIGS Test, Evaluation, Integration and Transition Plan with the definition of effectivities and any changes to the test, evaluation, integration, and transition strategies driven by the migration planning.

P. The USIGS EPIP provides the USIGS Training Plan with the definition of effectivities and any changes to training strategy driven by the migration planning.

Q. The USIGS EPIP provides the NIMA Master Schedule with dates of the effectivities.

R. The USIGS Enterprise Requirements Specification provides the USIGS Test, Evaluation, Transition, and Integration Plan with enterprise level requirements and associated verification methods (i.e., test, demo, analysis, or inspection).

S. The USIGS Enterprise Requirements Specification provides the ICDs with requirements changes that affect existing interfaces. The ICDs provide the USIGS Requirements Specification with the detailed definitions of existing interfaces.

T. The USIGS Enterprise Requirements Specification provides the Program Element Requirements Specifications with enterprise-level requirements allocated to program elements.

U. The ICDs provide the USIGS Interoperability Profile with the definition of existing interfaces.

V. The ICDs provide the USIGS Test, Evaluation, Transition, and Integration Plan with interface requirements that require verification.

W. The USIGS Test, Evaluation, Transition, and Integration Plan (TETIP) provides the Program Element Test, Evaluation, Transition, and Integration Plan and Procedures with the overall structure and objectives of USIGS TETIP activities.

X. The USIGS Test, Evaluation, Transition, and Integration Plan provides the NIMA Master Schedule with test, evaluation, transition, and integration activities, milestones, and dependencies.

Y. The USIGS Training Plan provides the Program Element Training Management Plan with high level training plans by effectivity.

Z. The USIGS Training Plan provides the NIMA Master Schedule with training activities and dependencies.

AA. The Program Element Schedule provides the NIMA Master Schedule with program element-level and acquisition activities, milestones, and dependencies. The NIMA Master Schedule provides the Program Element Schedule with enterprise-level activities, milestones, dependencies, and constraints.

BB. The Program Element Training Management Plan provides the Program Element Schedule with training activities and dependencies, including training coordination with users and planned updates of the Program Element Training Management Plan.

CC. The Program Element, Test, Evaluation, Transition, and Integration Plan and Procedures provides the Program Element Schedule with program element test, evaluation, transition, and integration activities, milestones, and dependencies.

DD. The ICDs provide the Program Element Test, Evaluation, Transition, and Integration Plans and Procedures with interface requirements that require verification.

EE. The Program Element Requirements Specification provides the Program Element Test, Evaluation, Transition, and Integration Plan and Procedures with program element requirements and associated verification methods (i.e., test, demo, analysis, or inspection) and verification phases (e.g., FAT or SAT).

FF. The Program Element Requirements Specification provides the Logical Data Model with data requirements.

GG. The Program Element Requirements Specification provides acquisition program with program requirements.

HH. The Existing System/Segment Requirements Documents provide the Program Element Requirements Specification with existing functional and performance requirements.

I I. The Legacy System/Segment Requirements Documents provide the USIGS Enterprise Requirements Specification with existing functional and performance requirements.

JJ. The ICDs provide the Legacy System/Segment Requirements Documents with the definition of existing interfaces. The Legacy System/Segment Requirements Documents provide the ICDs with requirement changes that impact existing interfaces.

KK. The ICDs provide the Program Element Requirements Specifications with the definition of existing interfaces.

Table 7-1 Descriptions of Enterprise Planning and Program Element-Level Documents