APPENDIX II
USIGS Operational Relationship Chart
20.1 Introduction
20.1.1 Background
USIGS Operational Architecture documentation, in accordance with the guidelines provided in the C4ISR Architecture Framework and the UAF document, describes the context (i.e., mission), activities, operational relationships, and the internal and external flow of information and services. These functions and processes, which are illustrated at a high level in the USIGS Operational Concept Diagram, are linked to organizational elements - again at a high level - in the USIGS Operational Relationship Chart.
20.1.2 Purpose
The USIGS Operational Relationship Chart presents an illustration of the operational relationships among NIMA business units (offices), with particular emphasis on the NIMA Directorate of Operations, and between those organizational elements and the Imagery and Geospatial Community.
20.1.3 Scope
According to the C4ISR Architecture Framework, the Command Relationship Chart is used to "show the operational elements involved in a particular military operation and the relationships among them." Thus, the chart identifies command, control, and coordination relationships among operational elements or organizations.
Within the context of the USIGS Operational Architecture, the Operational Relationship Chart focuses on the same relationships addressed by the Command Relationship Chart. The name of the chart was modified in the USIGS Architecture Framework document in recognition of NIMA's role as a combat support agency, as opposed to the operational / tactical organization envisioned in the C4ISR Architecture Framework.
This document presents the USIGS Operational Relationship Chart at two levels: an Organizational View and a Directorate View. The Organizational View depicts lines of "command and control" within NIMA. The Directorate View illustrates the flow of information and services between NIMA directorates, and from those directorates to the Imagery and Geospatial Community.
20.1.4 Applicability
The USIGS Operational Relationship Chart provides the foundation for the development of the USIGS Activity Diagram, which depicts information and service flows between organizational nodes. The Operational Relationship Chart also influences the USIGS Operational Scenario and Evolutionary Phase Implementation Plan and offers guidance to the planning process, requirements process, acquisition process, resource management, and community interaction.
20.2 Operational Relationship Chart: Organizational View

Figure 20-1 Operational Relationship Chart: Organizational View
Figure 20-1 represents a depiction of the Operational Relationship Chart: Organizational View, which focuses on the lines of command and control within NIMA. Essentially, NIMA is presented in a "line and block chart" format, overlaid on the Operational Concept Diagram (NIMA View). In one respect, it fulfills the purpose ascribed to the Operational Relationship Chart, in that it links information and service flows to organizational elements instead of to functional nodes. Simply stated, Figure 20-1 illustrates how NIMA is organized. What it does not illustrate, however, is how NIMA actually operates.
In order to fulfill its operational mission, NIMA increases its functionality through cross-organizational matricing, and through the establishment and maintenance of a "workgroup" environment which is not clearly captured in Figure 20-1. Illustrating the operational environment in terms of the many lines of coordination that exist between and among business units (office-level organizations) would be confusing and would have little utility in the architecture development process. An additional illustration is needed, to better capture the flow of information and services between organizational entities within NIMA, and between those entities and the Imagery and Geospatial Community in general.
20.3 Operational Relationship Chart: Directorate View

Figure 20-2 Operational Relationship Chart: Directorate View
The Operational Relationship Chart: Directorate View is used to illustrate the links from functions and high-level activities to organizational elements within NIMA, at the directorate level. It is at this level, that we can begin to assign specific functions and depict the interactions between the directorates in terms of what each directorate provides to the other two, and what each provides to the community external to NIMA. The functions and interactions are described in the following paragraphs.
20.3.1 Directorate of Operations
The Directorate of Operations is the source acquisition, exploitation, and dissemination arm of NIMA. As illustrated in Figure 20-2, it manages the following processes:
A more detailed description of the core businesses is found in the NIMA Business Plan 1997 and in the Operational Concept Diagram documentation.
The principal output of the Directorate of Operations to the Imagery and Geospatial Community is the provision of information and services in fulfillment of NIMA's operational mission. In terms of its interface with the other NIMA directorates, the Directorate of Operations provides the Corporate Affairs Directorate with feedback (both internal and from the Imagery and Geospatial Community) and requests for guidance. The Directorate of Operations also interacts with the Systems and Technology Directorate in delineating systems requirements.
20.3.2 Systems and Technology Directorate
The Systems and Technology Directorate is responsible for the development, acquisition, and sustainment of systems, standards, and technology related to the processing and dissemination of imagery intelligence and geospatial information. As depicted in Figure 20-2, this directorate manages the following processes:
20.3.3 Corporate Affairs Directorate
The Corporate Affairs Directorate provides support to NIMA and its customers through its management of the following processes:
20.3.4 Executive Management Function
Figure 20-2 includes the illustration of an executive management function, connected to each of the directorates by a double-headed arrow which depicts the two-way flow of information: the flow of management information and guidance to the directorates, and the feedback from them.
The Director, NIMA, fills two roles within the Imagery and Geospatial Community:
20.3.5 Operational Relationship Chart - Significance
As previously noted, the Operational Concept Diagram depicts the flow of information and services between functional nodes, e.g., the internal delivery of applications from Information Applications and Services to Information Production. With the high-level Operational Relationship Chart, we can begin to attribute the information and services flows to organizational entities. Thus, using the same example, the Operational Relationships Chart illustrates the internal delivery of applications from the Systems and Technology Directorate to the Directorate of Operations.
20.4 NIMA/DO: Operational Relationships
Focusing on the major interactions and information flows which support NIMA's operational mission, it is possible to illustrate operational relationships between NIMA business units. Figure 20-3 represents relationships among the offices subordinate to the Directorate of Operations, as well as between those entities and: (a) the other directorates; and (b) the Imagery and Geospatial Community.
The foundation for Figure 20-3 is the Operational Concept Diagram: NIMA View. Core businesses are overlaid on the NIMA directorates; while the supporting functions of Infrastructure and Customer Service are now imbedded, and thus not directly illustrated. The office-level organizations within the Directorate of Operations have been overlaid on the most appropriate core business(s). (Note: the Systems & Technology and Corporate Affairs Directorates are not broken out below the directorate level).

Figure 20-3 NIMA/DO: Operational Relationships
In the Operational Concept Diagram, external arrows start and end at the perimeter of the NIMA box. In this illustration, the arrows extend into, and out of, the appropriate directorates, down to the office level in the case of the Directorate of Operations.
This is done to provide an illustration of information and service flows:
The additional level of detail presented by this chart allows us to more clearly define the interactions between organizational elements. For example:
20.5 Operational Relationship Chart: Contextual View
The Operational Relationship Chart is derived from the NIMA Business Plan 1997, NIMA Strategic Plan 1997, the NIMA Operations Directorate Vision, NIMA's organizational structure, and the Operational Concept Diagram. It, in turn, provides input to the development of Activity Diagrams, which depict information and service flows between organizational nodes. The Operational Relationship Chart: Contextual View illustrates these flows at a high level. The flows are broken out in more detail in the Activity Hierarchy, which also feeds the development of the Activity Diagrams. These products are all foundation documentation for the development of perhaps the most critical product in the Operational Architecture development process, the Information Exchange Requirements Matrix.

Figure 20-4 Operational Relationship Chart: Contextual View