2.1 Description
The USIGS Operational Architecture describes the tasks, operational elements, and information flows required to accomplish or support customer organizations' planning and operations. USIGS Operational Architecture products describes the context (mission), activities, operational relationships, and information flows within USIGS and to and from its customers and suppliers. It reflects NIMA's mission to support DoD's wartime missions, national policy-making, and civil organization operations and research. The Operational Architecture supports IGC mission requirements as articulated in directives, policy, doctrine, procedures, and organizational concepts of operation. Information Exchange Requirements (IERs) identified in the Operational Architecture provide the basis for technical requirements, standards, conventions, and new technological capabilities, which provide a foundation for defining systems capabilities and requirements.
2.2 Major Influences
USIGS Operational Architecture products describes the basic conditions under which the overall architecture applies. These conditions include the missions, operational concepts, and functions the architecture must support, the organizational relationships and major operational elements to which the missions and functions are assigned, the functions and the activities derived from the mission and operations concept, and the information types and resulting information flows and functional topology. USIGS Operational Architecture documentation has been compiled into a single document, the USIGS Operational Architecture Description (UOAD). Each product represents a separate appendix or addendum to the primary document.
Operational Architecture products includes:
|
Name: USIGS Operational Concept Diagram |
|
Description and Purpose of Product: The USIGS Operational Concept Diagram is used to depict the "big picture" view of the operational environment. It features a high-level description of the operational concept, and a graphic portrayal oriented to senior-level management. The figure shows the production within the USIGS environment; the production organization is portrayed in terms of its major, mission-related functions. The relationship between USIGS and its customer and supplier/co-producer communities is depicted in generic terms. The lines connecting the activity boxes within the production organization represent internal information movement. The central theme of this diagram is the flow of information, both internal (within the production organization) and external (between the production organization and its customers and suppliers).
|
| Audience: USIGS senior and mid-level
managers, program managers, system architects, system developers; NIMA
DO, ST, CA
|
| Creator/Maintainer: NIMA DO,
CA/CF
|
| Format: Multiple page annotated
graphics with supporting text
|
| Applicable Tools: Future versions
of the Joint C4ISR Architecture Planning/Analysis System (JCAPS) plan to
have the capability to generate some, or all, of this product from data
provided in the other USIGS products.
|
| Dependent On: National Imagery
and Mapping Agency (DoDD 5105.60); NIMA Business Plan; NIMA Operations
Directorate Vision, IGC Operations Vision. May include inputs
from the NIMA FY97 Work Plan. May also be influenced by the USIGS Operational
Relationship Chart, the USIGS Activity Hierarchy, USIGS Activity Diagram,
USIGS Information Exchange Requirements Matrix.
|
| Processes Influenced: Planning
Process - Mandatory (i.e., Must be considered in this process to
ensure
USIGS Architecture compliance) Resource Management - Guidance (i.e., Should be considered in this process to ensure USIGS Architecture compliance) Acquisition Process - Guidance
|
| Revision Cycle: Annual |
| Controlling Authority: NIMA Configuration Control Board (NCCB) |
| Classification: UNCLASSIFIED |
|
Name: USIGS Operational Relationship Chart |
|
Description and Purpose of Product: The USIGS Operational Relationship Chart identifies operational elements and their relationships. The chart depicts lines of command and coordination among operational elements. The basic purpose of this chart is to illustrate "how business is done." (This sample of the chart focuses on the operational elements within NIMA, and addresses elements external to NIMA in generic terms.)
|
|
Audience: USIGS senior and mid-level managers, program managers, system architects, and system developers; NIMA DO, CA, ST
|
|
Creator/Maintainer: NIMA DO, CA/CF
|
|
Format: Multiple page annotated graphics with supporting text
|
|
Applicable Tools: Future versions of the Joint C4ISR Architecture Planning/Analysis System (JCAPS) plan to have the capability to generate some, or all, of this product from data provided in the other USIGS products.
|
|
Dependent On: National Imagery and Mapping Agency (DoDD 5105.60); NIMA Business Plan; NIMA Operations Directorate Vision, IGC Operations Vision. May include inputs from the NIMA FY97 Work Plan. May also be influenced by the USIGS Operational Concept Diagram, the USIGS Activity Hierarchy, USIGS Activity Diagram, USIGS Information Exchange Requirements Matrix.
|
|
Processes Influenced: Planning Process - Mandatory Requirements Process - Mandatory Resource Management - Guidance Acquisition Process - Guidance Community Interaction - Dependent
|
| Revision Cycle: Annual
|
| Controlling Authority: NCCB
|
| Classification: UNCLASSIFIED |
2.3.3 USIGS Activity Hierarchy
The activity hierarchy is used to describe activities associated with specific tasks, the relationship among activities, and the decomposition of tasks.
| A0 Manage the United States Imagery and Geospatial System
A1 Provide USIGS Leadership support A11 Provide USIGS Policy Direction A111 Develop USIGS Policies and Procedures A112 Establish USIGS Priorities and Strategies A1121 Develop the USIGS Strategic Plan/Vision A1122 Publish/Brief the USIGS Strategic Plan/Vision A113 Develop and Maintain USIGS Technology, Data, and Product Specifications and Standards A114 Develop and Maintain International Agreements A115 Develop and Maintain Legal Agreements A12 Provide USIGS Guidance and Advocacy A121 Define USIGS Architecture A1211 Develop and Maintain Architecture Framework A1212 Develop and Maintain Operational Architecture A12121 Develop and Maintain Operational Architecture Products A12122 Produce USIGS Shortfall Analysis Report A1213 Develop and Maintain Technical Architecture A1214 Develop and Maintain System Architecture A1215 Develop and Maintain Conceptual Data Model A1216 Develop and Maintain Migration Plan A12161 Develop and Maintain Migration Products A12162 Brief/Publish USIGS Migration Plan to IGC A122 Provide Program and Budget Guidance A1221 Review IGC POM Submissions A1222 Provide Functional Manager's Decision Support (Publish FMGC) A1223 Issue Guidance as Appropriate A123 Provide Guidance to Collection, Processing, Analysis and Dissemination Resources A1231 Establish Projections of Future USIGS Imagery and
A1232 Develop and Disseminate Policies and Procedures to Guide USIGS Collection, Processing, Analysis, and Dissemination Assets
|
| Name: USIGS Activity Hierarchy |
| Description and Purpose of Product:
The purpose of the activity hierarchy is to describe activities associated
with specific tasks, the relationship among activities, and the decomposition
of tasks. For a given architecture perspective, the activity hierarchy
starts by using one of the tasks at the top of the hierarchy. This top-level
task is then broken down into lower level tasks until the tasks at the
lowest level can be clearly identified with a particular operational element
or node responsible for accomplishing the task. The activity hierarchy
should be refined only to the level necessary to meet the needs of the
architecture being developed. Some levels of the hierarchy may be refined
to a lower level of detail so as to address some specific objectives of
the architecture being developed.
|
| Audience: USIGS program managers,
mid-level managers, system architects, system developers; NIMA DO, CA,
ST
|
| Creator/Maintainer: NIMA DO,
CA/CF
|
| Format: Multiple pages of text
in outline format
|
| Applicable Tools: The requirements
management process (as implemented in DOORS) will use the Activity Hierarchy
to determine if an incoming need is within the scope of the USIGS. In addition,
DOORS will show traceability from each activity up to the driving documentation
that requires that activity and down to the systems architecture and the
ongoing acquisition efforts to support that activity. Future versions of
the Joint C4ISR Architecture Planning/Analysis System (JCAPS) plan to have
the capability to ingest and/or generate some, or all, of this product
from data provided in the other USIGS products.
|
| Dependent On: National Imagery
and Mapping Agency (DoDD 5105.60), NIMA Business Plan, NIMA Operations
Directorate Vision, IGC Operations Vision, USIGS Operational
Concept Diagram
|
|
Acquisition Process - Guidance
|
| Revision Cycle: Annually, or
as directed in response to organization and/or mission changes
|
| Controlling Authority: NCCB
|
| Classification: UNCLASSIFIED
|
2.3.4 USIGS Activity Diagram
The purpose of the USIGS Activity Diagram is to describe the functional activities required to provide imagery, imagery intelligence, and geospatial information in support of USIGS customers. This analysis will use Unified Modeling Language (UML) Use-Case methodology. Use-Case notation will: depict interactions by which external "actors" engage the services of the USIGS; provide a means to identify and document classes of users and the external systems that interact with the USIGS; provide a means to specify required transaction-based USIGS services; and facilitate the allocation of services/capability requirements to USIGS software architecture components.
|
Name: USIGS Activity Diagram
|
|
Description and Purpose of Product: The purpose of the USIGS Activity Diagram is to describe the functional activities required to provide imagery, imagery intelligence, and geospatial information in support of USIGS customers. This analysis utilizes the Unified Modeling Language (UML) Use-Case methodology for modeling. Use-Case notation will: depict interactions by which external "actors" engage the services of the USIGS; provide a means to identify and document classes of users and the external systems that interact with the USIGS; provide a means to specify required transaction-based USIGS services; and facilitate the allocation of services/capability requirements to USIGS software architecture components.
|
|
Audience: USIGS program managers, mid-level managers, system architects, data modelers, system developers; NIMA ST
|
| Creator/Maintainer: NIMA DO,
CA/CF
|
| Format: Multiple annotated graphics
|
| Applicable Tools: Future versions
of the Joint C4ISR Architecture Planning/Analysis System (JCAPS) plan to
have the capability to ingest and/or generate some, or all, of this product
from data provided in the other USIGS products.
|
| Dependent On: USIGS Operational
Relationship Chart, USIGS Activity Hierarchy
|
|
Processes Influenced: Planning Process - Mandatory Requirements Process - Mandatory Resource Management - Guidance Acquisition Process - Guidance Community Interaction - Dependent
|
|
Revision Cycle: Annual, or as required by modifications to the USIGS Activity Hierarchy
|
|
Controlling Authority: NCCB
|
|
Classification: UNCLASSIFIED |
2.3.5 USIGS Information Exchange Requirements Matrix
Based on the activity hierarchy and activity diagrams, the Operational Architecture will define USIGS Information Exchange Requirements (IERs). An IER Matrix consists of a defined activity, a sender, a recipient, a specific information element, type of media, and appropriate classification and handling instructions. Performance information such as a measure of volume (transactions per time), the minimum time required to accomplish a specific activity/transaction, and a quality measure may also be included in the IER Matrix.
|
|
|
|
|
|
|
|
|
|
|
| 1.0 Information and Services Acquisition | |||||||||
| 1.1 Monitor, Assess, and Report USIGS Status | Operational Support Data/References | Collectors, processors, analysis and production centers, libraries, dissemination centers | Executive manager | ||||||
| - 1.1.1 Provide system-level assessments | |||||||||
| - 1.1.1.1 Perform imagery systems assessment | Status/Feedback Messages | National collectors | Executive manager | Electronic,
Voice
|
TOP SECRET | LIMDIS | X per time | X minutes
|
Accepted/
Rejected |
| Status/Feedback Messages | Theater collectors
|
Executive manager | Electronic | SECRET | None | X per time | XX minutes | Accepted/ Rejected | |
| Status/Feedback Messages | Tactical collectors | Executive manager | Electronic | SECRET | Nome | X per time | XX minutes | Accepted/ Rejected | |
| Status/Feedback Messages | Commercial collectors | Executive manager | Electronic | UNCLASSIFIED | None | X per time | XX minutes | Accepted/ Rejected | |
| Status/Feedback Messages | Civil collectors | Executive manager | Electronic | UNCLASSIFIED | None | X per time | XXX minutes | Accepted/ Rejected | |
| Status/Feedback Messages | Foreign collectors | Executive manager | Electronic, Voice | UNCLASSIFIED | Rel CAN, UK, AUS | X per time | XX minutes | Accepted/ Rejected | |
| Status/Feedback Messages | National processors | Executive manager | Electronic | TOP SECRET | LIMDIS | X per time | X minutes | Accepted/ Rejected | |
| Status/Feedback Messages | Theater processors | Executive manager | Electronic | SECRET | None | X per time | XX minutes | Accepted/ Rejected | |
| Status/Feedback Messages | Tactical processors | Executive manager | Electronic | SECRET | None | X per time | XX minutes | Accepted/ Rejected | |
| Status/Feedback Messages | Commercial processors | Executive manager | Electronic, media | UNCLASSIFIED | None | X per time | XXX minutes | Accepted/ Rejected |
|
Name: USIGS Information Exchange Requirements Matrix |
|
Description and Purpose of Product: The USIGS Information Exchange Requirements Matrix is based on the USIGS Activity Hierarchy and USIGS Activity Diagrams. IER line entries consists of a defined activity, a sender, a recipient, a specific information element, type of media, and appropriate classification and handling instructions. Performance information such as a measure of volume (transactions per time), the minimum time required to accomplish a specific activity/transaction, and a quality measure may also be identified.
|
|
Audience: USIGS program managers, mid-level managers, system architects, data modelers, system developers; NIMA ST
|
|
Creator/Maintainer: NIMA DO, CA/CF
|
|
Format: Multiple page table with text
|
|
Applicable Tools: Future versions of the Joint C4ISR Architecture Planning/Analysis System (JCAPS) plan to have the capability to ingest and/or generate some, or all, of this product from data provided in the other USIGS products.
|
|
Dependent On: USIGS Activity Hierarchy, USIGS Activity Diagrams
|
|
Processes Influenced: Planning Process - Mandatory Requirements Process - Mandatory Resource Management - Guidance Acquisition Process - Guidance Community Interaction - Dependent
|
| Revision Cycle: Annual, or as
required by modifications to USIGS Activity Diagrams
|
| Controlling Authority: NCCB
|
| Classification: UNCLASSIFIED
|
|
The Story below shows how the several USIGS initiatives come together to allow the responsive, accurate imagery and geospatial information support which users will require in 2003. As the information cycle proceeds -- from the establishment of a requirement to a user's having the answer to his question, the initiatives work together, and without the capabilities embodied in each, the others will not function as designed or required. The Situation A joint task force has been formed in early July, 2003, as the US component of a multinational operation to quell a rebellion in a third-world nation. US citizens and citizens of the other nations participating in the operation are being held hostage in several areas of the capital city. The multinational force has been given the mission of rescuing the hostages and restoring the elected government to power. The commander of the US joint task force has entered the area of operations with a robust C4I structure, including a deployable NIMA Imagery Library as part of the NIMA Library Initiative, populated with baseline imagery and geospatial information on the area of operations. US amphibious forces, supported by US and coalition special operations forces and tactical air assets, are scheduled to make an opposed landing as part of the rescue force tomorrow at first light. Intelligence Preparation of the Battle Space is virtually complete. The theater commander's intelligence plan for federated intelligence support was activated in the planning phases of the operation. The NMJIC has organized the JICs and JACs of supporting commands, and NIMA, DIA in a federated intelligence support structure. NIMA has provided the necessary policy framework to permit essential sharing of imagery-derived information with coalition partners. A Critical Operational Question Is Asked On the eve of the rescue operation, the US joint task force commander received a tip-off from SIGINT that a group of US hostages would be moved from the US embassy to a newly constructed office building two miles away. The JTF commander needs the latest imagery of the building to which the hostages are being moved, including floor plans and the areas in which his troops would be most vulnerable to insurgent attack during the rescue operation. His is also concerned about potential insurgent opposition to the rescue operation, and has levied a requirement for information on military movements and changes in the defenses in the vicinity of the building and its approaches. The deployable NIMA library on his flagship has complete imagery and digital geospatial information on the area of the capital city in which the building sits, but it has no imagery of the building after completion, nor is there historical coverage which would give the building's interior layout. His J2 passes the information requirement to the theater JIC, with a request that the information be provided before 0400 local time, to allow the landing force time to factor it into their planning. Upon receipt of the JTF commander's requirement, the JIC determines that some new collection will be required to satisfy the requirement, and that the imagery part of the answer can be provided by a combination of UAV's and national systems. The collection manager at the JIC enters the national requirement in RMS, including the requirements for exploitation and distribution. New Imagery Is Collected, Existing Information is Pulled Together At the theater Joint Reconnaissance Center, the requirement for advisory tasking of theater UAVs against the building where the hostages will soon be is received. The JRC accepts the tasking and arranges for UAV coverage of the area two hours before first light. UAV video will be sent from the UAV to a Common Imagery Ground Station and then fed to the JIC for injection into the Joint Broadcast System (JBS) video channel. NIMA's Central Imagery Tasking Office receives the collection requirement for national imagery and determines that . . . At the JIC, imagery analysts, working with their all-source counterparts, have determined that . . . the building was obtained as "bonus" coverage a day earlier. Coverage is obtained by a national system as tasked. . . and the coverage is received at the JIC and supporting JICs . . . before 0100. Simultaneously, the imagery enters the National Imagery Library. The Pieces of the Puzzle Are Put Together - Analysis and Production By the time the national system coverage arrives at the theater JIC, analysts at softcopy workstations have already begun their work. The capabilities of the Exploitation Support System have allowed the analysts to begin work with baseline data already pre-staged at their workstations. The JIC's imagery analyst cadre has reaped the benefit of the Imagery Analyst Initiative, and the command not only has increased its IA numbers, but has also seen the experience level rise with the cross-fertilization of IA's with NIMA and the career development which the initiative allowed. . . The exploitation tools provided by the Exploitation Tools Initiative will also allow the IA's to do the in-depth analysis the commander requires. One IA has already begun to provide an Image Perspective Transformation (IPT) view of the building, using imagery and geospatial data provided as a result of the GIIPT Initiative to provide a ground-level view of the approaches to the building from the harbor area. When the exploitation and analysis tasks were apportioned as a collaborative exploitation effort, NIMA IA's were assigned the task of providing in-depth analysis of the building. Using imagery of the building in various stages of construction available in the National Imagery Library, NIMA's had the information available before 0200 (theater time) and injected on GBS through the Joint Information Management Center (JIMC) in the Pentagon. Throughout the analysis process, IA's and all-source analysts at the theater JIC, supporting JICs, NIMA, and DIA worked together, in many cases using whiteboard and video teleconferencing. The Information Gets to the User - On Time By 0300, all of the pieces of the puzzle had come together. The theater JIC had completed its portion of the analysis. The IPT was on the Image Product Library (IPL) server and had been sent to the theater information management center for injection on the GBS broadcast to the JTF commander afloat. NIMA's in-depth analysis of the building was also in the hands of both the JTF commander and the theater JIC. In the meantime, the UAV had arrived on station at 0245, well in advance of first light. At 0330, the JTF commander received a HUMINT report through his National Intelligence Support Team (NIST) that the insurgents were moving the US hostages to the new office building, just as SIGINT had predicted. As the landing force completed its preparations, man-portable IPLs provided under the NIMA Library Initiative were being loaded with the information just received on the building and its approaches. At 0430, the assault force helos lifted off the LPH on their way to the port area. At 0515, as dawn was breaking, the force entered the office building, overwhelmed the still groggy guards, and evacuated the hostages even as the main body of the multinational force began their assault on the capital. |
|
Name: USIGS Operational Scenario
|
|
Description and Purpose of Product: Operational scenarios provide brief textual and graphic descriptions of specific operational needs, activities, and/or processes which are intended to illustrate how tasks are, or will be, performed in order to accomplish a given mission, or missions, within a particular architecture perspective. Operational scenario are often composed of one or more "threads" which are usually described in a temporal sequence to demonstrate, in a real-world sense, the validity of a given architecture.
|
|
Audience: USIGS senior and mid-level managers, program managers, system architects, data modelers, system developers; NIMA DO, ST, CA
|
|
Creator/Maintainer: NIMA CA/PAS, DO
|
|
Format: Multiple pages of text with graphic(s)
|
|
Applicable Tools: Word Processor
|
|
Dependencies: Joint Vision 2010, NIMA Business Plan, NIMA Operations Directorate Vision, IGC Operations Vision, USIGS Operational Concept Diagrams, USIGS Operational Relationship Charts
|
|
Processes Influenced: Planning Process - Guidance Requirements Process - Guidance Resource Management - Guidance Acquisition Process - Guidance Community Interaction - Dependent
|
|
Revision Cycle: Annual, or as required to illustrate a significant mission change or need
|
|
Controlling Authority: NCCB
|
|
Classification: SECRET, as required by classified scenario references |
2.4 USIGS Operational Architecture Product Linkages
B: DoD Directive 5105.60 establishes NIMA's responsibility to define how the agency intends to do business in the future to support its customers.
C: The NIMA Strategic Plan outlines NIMA's corporate roadmap to the future and will be the basis for its decision-making process. This plan supports movement from traditional imagery and geospatial hardcopy products to a more efficient and timely digital information service. These key concepts are included in the IGC Operations Vision and the NIMA Operations Directorate Vision.
D: NIMA's planned execution of its wide-ranging charter to produce imagery and geospatial information in support of national, defense, and civil community customers has a direct and significant impact on the how the IGC and USIGS will function in the future.
E: Joint Vision 2010 establishes the initial conceptual template for channeling resources and leveraging technology to achieve new levels of effectiveness in joint warfighting. The Concept for Future Joint Operations expands the new operational concepts to provide a more detailed foundation for follow-on capabilities assessments. Various Joint Command, Service, Agency, and Command operational architectures identify more specific and specialized applications of these concepts. The Universal Joint Task List contributes to the understanding of the tasks that can be performed by a joint military force. The operational concepts, mission tasks, and technology approaches contained in these documents must be encompassed by, and reflected in the IGC Operations Vision, if information superiority is to be achieved.
F: The IGC Operations Vision is a conceptual document which describes how the United States and foreign governments, together with their respective commercial and academic sectors, plan to establish a collaborative imagery and geospatial production environment to leverage strengths and share resources, and to exchange information in support of common interests and security objectives. This document serves to complement and align the internal visions of IGC organizations including NIMA's Operations Directorate Vision. These documents provide guidance for the development of the USIGS Operational Concept Diagram which is used to depict the "big picture" view of the operational environment.
G: The IGC Operations Vision, in concert with NIMA's Operations Directorate Vision, provide context for the USIGS Operational Relationship Chart which depicts lines of command and coordination among operational elements , and illustrate "how business is done."
H: IGC organizations are structured to support their individual missions. Organization structures impact the IGC Operations Vision by providing context for that vision and supporting functionalities.
I: IGC organization structures, both individually and collectively, must be documented and considered in describing how these organizations function and relate to each other, now and in the future.
J: The Operational Concept Diagram forms the basis for mapping functions to NIMA offices in the Operational Relationship Chart.
K: The Operational Concept Diagram provides the functions which constitute the top level entries in the Activity Hierarchy.
L: By depicting the information and service flows between organizational nodes, the Operational Relationship Chart provides the foundation for the development of the Activity Diagram.
M&N: The Activity Hierarchy drives the Information Exchange Requirements Matrix (IERM) and the Activity Diagram by providing the "Activities" which are depicted.
O&P: The Activity Diagram depicts the typical relationships between activities identified in the Activity Hierarchy, and thereby, provides the Sender & Recipient information for the IERM.
Q&R: The Activity Diagram and the IERM both provide information to develop the Operational Scenario, which in turn, validates the activities and relationships presented in those documents.