Section 6
USIGS MIGRATION PLAN
 

6.1 Description

USIGS migration products outlined in this section support the evolution of multiple imagery and geospatial systems into an integrated USIGS. The primary emphasis of migration is to develop a dynamic system that will provide immediate response to diverse customer needs. Key evolution elements are:

In order to fulfill these objectives, the USIGS migration must encompass more than a traditional replacement of older systems and capabilities with newer ones. It must evolve today's individual imagery and geospatial system capabilities into an integrated system-USIGS, defined by common services and customer-derived mission applications.

6.2 Major Influences

Migration planning products are the road map that will enable NIMA to move away from today's standalone capabilities to the USIGS envisioned in the IGC Operations Vision, the NIMA Operations Directorate Vision, and the USIGS "To-Be" Systems Architecture. The major influences on migration planning are:

6.3 Migration Process

Migration will be achieved through an iterative process of analysis, definition and reengineering that will drive the evolution of the USIGS architecture from the "As-Is" state, defined by current system operating capabilities, to the "To-Be" state defined by the USIGS System and Operational Architectures.

It will replace monolithic system designs with USIGS interoperable software applications packaged to meet user-defined mission needs (Figure 6-1). The migration process reduces system redundancies and moves USIGS towards the ability to provide users with seamless access to data. As a part of the process, existing systems are decomposed into functional requirements that are then bundled into USIGS elements. USIGS Elements consist of mission specific applications operating on a common infrastructure which provides all required common support services, communications, and computing platforms.

The migration process is marked by the continuous integration of additional capabilities into the baseline. Effectivities define the functional capabilities that will be stood up to meet defined evolutionary requirements within a specified period of time. They are described in terms of their impact on current operating capabilities within each of the USIGS program elements. Early USIGS capabilities will focus on the implementation of standard data access and elimination of redundant data catalogs and information stores. Establishment of this initial USIGS capability will provide an interoperable environment for softcopy imagery and geospatial workstations. The UAF migration products provide the tools for effecting the analysis, definition, and integration processes that will continually feed new capabilities into USIGS.

 

 
Figure 6-1 USIGS Migration

6.4 USIGS Migration Products

The USIGS migration products are:

6.4.1 USIGS Evolutionary Phase Implementation Plan (EPIP)

Central to the evolution of an integrated USIGS, is the development of an iterative document that captures those planned migrations of each fiscal year. The USIGS EPIP provides basic guidance and establishes the path for the evolution of USIGS. The EPIP is designed to facilitate the transition from a closed, proprietary information architecture into an open architecture, that leverages commercial off the shelf (COTS) products to facilitate standards-based information exchange. This allows for more rapid insertion of new technologies that produce a more flexible architecture with increased performance capabilities.

The primary purpose of the EPIP is to document and gain agreement on a solid, executable migration plan. It provides information to support both POM and IPOM builds. It also provides the information needed to defend budget items related to migration. The EPIP defines high-level migration plans for the next five years and defines a detailed executable plan for the next 2 years. Figure 6-2 depicts the coverage of each EPIP. The EPIP will receive a major revision annually. There will be a minor revision at mid-cycle, which will focus on updating the detailed two-year plan.

Figure 6-2 Annual Coverage of USIGS EPIP

The USIGS Evolution Diagram describes the migration steps identified in the EPIP. It is functionally based and depicts the integration of current system functions into the USIGS through multiple effectivities (or migration cycles). Evolution diagrams may be used in the EPIP as an aid to illustrate the plan. An example is provided in Figure 6-3.

Figure 6-3 USIGS Evolution Diagram (sample)

 
Table of Contents

1.0 INTRODUCTION

1.1 Purpose

1.2 Scope

1.3 Roles and responsibilities

1.3.1 NIMA Migration Planning Team (SE, PEOs, AR, DO)

1.3.2 NIMA Program Executive Officers (PEOs)

1.3.3 NIMA PRogram Managers (PMs)

1.3.4 NIMA Effectivity Managers/Functional Managers

1.3.5 Customer Advocates

2.0 High-Level migration Plan (5-year view) 2.1 Overall goals of USIGS migration

2.2 Concept of Operations- FY99

  • Critical Drivers
  • Basis for prioritizing functions into effectivities
  • major changes (e.g., facilities closing)
2.3 Concept of operations- fy00

2.4 Concept of operations- fy01

2.5 Concept of operations- FY02

2.6 Concept of operations- FY03

3.0 Detailed Migration plan (2-year view) 3.1 Effectivity 1.5 3.1.1 Detailed Concept of Operations
  • Critical Drivers
  • Basis for prioritizing functions into effectivity
  • ops con diagram
  • Assumptions
3.1.2 Functional Description
  • E1.5 function matrix with traceability to current system, MSA, PEO, target system/capability
  • Dependent functions/interfaces
  3.1.3 Plans for migration of Functions
  • Modifications to existing capabilities 
  • New capabilities
  • planned data flows
  • legacy data holdings that require migration
3.1.4 Other major impacts
  • Major changes in test and training strategies being driven by migration plan
3.1.5 Risks and mitigation strategies 3.2 Effectivity 2.0

3.3 Effectivity 2.5

3.4 Effectivity 3.0

 

 
Figure 6-4 USIGS Evolutionary Phase Implementation Plan (sample)
 
 
 
 
 
Table 6-1 USIGS Evolutionary Phase Implementation Plan
 
 

Name: USIGS Evolutionary Phase Implementation Plan (EPIP)
 

Description and Purpose of Documentation: The USIGS EPIP documents the evolution of the USIGS "to-Be" Architecture from the "As-Is" Architecture and describes the incorporation of multiple system capabilities into the emerging USIGS. The EPIP bundles functions into effectivities and allocates them to a program element. It identifies deliveries of function for NIMA sites and external sites. It provides an executable migration plan that will be implemented by the PEOs.
 

Audience: USIGS senior and mid-level managers, resource managers, program managers, system architects, NIMA DO, CA, ST
 

Creator/Maintainer: NIMA ST/SE
 

Format: Text document with annotated graphics
 

Applicable Tools: Major milestones and related capabilities from the EPIP can extend into DOORS to be linked to the acquisition and development efforts, and to show where dependencies exist between efforts. Word processor and scheduling tools are also utilized.
 

Dependencies:, USIGS Operational Architecture, USIGS Technical Architecture, USIGS System Architecture, USIGS Conceptual Data Model
 

Processes Influenced: 

Planning Process - Mandatory

Requirements Process - Mandatory

Resource Management - Mandatory

Acquisition Process - Mandatory

Community Interaction - Dependent

 
Revision Cycle: Major revision annually; minor revision at mid-cycle
Controlling Authority: NCCB
Classification: Unclassified
 

6.4.2 Functional Manager's Guidance for the Imagery and Geospatial Community Input Form

 
 

Functional Manager's Guidance for the Imagery and Geospatial Community
Input Form

Individual Functional Manager's Guidance items will be developed by appropriate NIMA OPRs in accordance with annual tasking from NIMA/CF. Internal guidance inputs will be submitted through the NIMA Integration Board (NIB). External guidance inputs will be submitted through the Imagery and Geospatial Community Senior Steering Group (processes TBD).

NIMA OPRs will provide their guidance items to NIMA/CF in one (per Business Unit) coordinated and approved list of guidance items, through their management chain. Individual guidance items will be provided in a short paragraph format that contains each of the following components:

WHO: NIMA, CIA, DIA, DISA, NRO, DARO, The Services, The Service Centers, The Unified Commands, The JICs/JAC, The Theater and Tactical units, and/or Development Offices, etc. (as appropriate)

WILL DO WHAT: 

Either: 

A. Program $______million of Research and Development (R&D), $______million of Procurement, $______million of Military Pay, $______million of Military Construction and/or $______million of Operations and Maintenance (O&M) funds, etc. (as appropriate)

Or: 

B. Submit an initiative to program $______million of Research and Development (R&D), $______million of Procurement, $______million of Military Pay, $______million of Military Construction and/or $______million of Operations and Maintenance (O&M) funds, etc. (as appropriate)

FOR WHAT PURPOSE: To design, develop, field, implement, man, operate and/or maintain, ______________ system, application, communications bandwidth, capability, organization, unit, etc. (as appropriate)

IN WHAT YEAR (S): In FY2000, 2001, 2002, 2003, 2004, 2005, or any appropriate combination of years (i.e.: 2000-2001, 2000-2005, etc.), (as appropriate)*

IN WHAT DOCUMENT: FY2000-2005 Intelligence Program Objectives Memorandum (IPOM) submission

IN RESPONSE TO WHICH NIMA OPR: Mr./Ms. ____ ________, NIMA/____, phone________

EXAMPLES:

A. NIMA will program $500K/year/Command of O&M funds to support the implementation of CILs at EUCOM, ACOM and PACOM in FY2000 and 2001 in the FY2000-2005 NIMAP IPOM submission. Continuing O&M funding beyond the first two years of CIL operation will be the responsibility of the operating Commands. OPR: Ms. ____ ________, NIMA/SE, (___) ___-______

B. EUCOM, PACOM and ACOM will submit initiatives to the GDIP Program Manager to program $500K/year/ Command of O&M funds to support the recurring maintenance of CILs at EUCOM, ACOM and PACOM in FY2002 through 2005 in the FY2000-2005 GDIP IPOM submission. OPR: Ms. ____ ________, NIMA/SE, (___) ___-______

*NOTES: For development projects, funding must be programmed through Final Operational Capability (FOC) plus one year, even if that year is beyond the current Future Years Defense Program (FYDP), (e.g., FY02-FY10, etc.) 

 
Figure 6-5 Functional Manager's Guidance for the Imagery and Geospatial Community
Input Form (sample)
 
 
 
 
Table 6-2 Functional Manager's Guidance for the Imagery and Geospatial Community
Input Form
 
Name: Functional Manager's Guidance for the Imagery and Geospatial Community Input Form

 
Description and Purpose of Product: This input format is used to develop the annual Functional Manager's Guidance for the IGC which provides programming and budgeting guidance for the annual Intelligence Program Objectives Memorandum (IPOM) program build. Functional Manager's Guidance is applicable to all imagery and mapping organizations, programs, systems, applications and support infrastructure and communications funded in the National Foreign Intelligence Program (NFIP), the Joint Military Intelligence Program (JMIP) and the Tactical Intelligence and Related Activities (TIARA) aggregation.

 
Audience: Imagery and mapping developers, collectors, producers, users and consumers within the Department of Defense and the Intelligence Community (e.g., the Services, Service Intelligence Centers, Unified Command Joint Intelligence Centers, theater operational and tactical intelligence units, Combat Support Agencies such as NIMA, and National Agencies and Offices such as CIA, NRO, DARO, etc.); NIMA DO, CA, ST

 
Creator/Maintainer: NIMA CA/CF, ST/ARE

 
Format: Single or multiple page(s)

 
Applicable Tools: Word processor

 
 

Dependent On: Deputy Secretary of Defense/Director of Central Intelligence Joint Intelligence Guidance and Fiscal Guidance

 
Processes Influenced: Planning Process - Mandatory

Requirements Process - Guidance

Resource Management - Mandatory

Acquisition Process - Mandatory

Community Interaction - Dependent

 
Revision Cycle: Annual, developed July - December

 
Controlling Authority: Director, NIMA

 
Classification: UNCLASSIFIED, SECRET, and/or SENSITIVE COMPARTMENTED INFORMATION (as appropriate, based on content)
 

 

 

6.5 Migration Planning Product Linkages with USIGS Architecture Products and

Enterprise Planning Products

The migration planning products draw from the USIGS architecture products as their primary sources. Figure 6-6 portrays the migration planning product linkages.

Figure 6-6 Migration Planning Product Linkages

The linkages that exist with the Migration Planning Products are explained as follows:

  1. The As-Is System Architecture provides the USIGS EPIP with definition of the current baseline from which migration occurs, existing systems/segments that comprise the baseline, and existing interfaces.
  2. The To-Be System Architecture provides the USIGS EPIP with the definition of the goal architecture for USIGS migration a well as planned relationships among architectural products and components.
  3. 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.
  4. 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.
  5. The USIGS EPIP provides the USIGS Training Plan with the definition of effectivities and any changes to training strategy driven by the migration planning.
  6. The USIGS EPIP provides the NIMA Master Schedule with dates of the effectivities.
  7. The USIGS Migration Plan provides the Functional Manager's Guide with the plan for migration for the following IPOM/POM cycle.
  8. The Functional Manager's Guide provides programming and budgeting guidance to the IPOM and POM.
 
Table of Contents ; Preface ; 1. Overview and Summary Information ; 2. USIGS Operational Architecture ; 3. USIGS Technical Architecture ; 4. USIGS System Architecture ; 5. USIGS Conceptual Data Model ; 6. USIGS Migration Plan ; 7. USIGS Architecture Compliance ; Appendix 1. Acronym List ; Appendix 2. C4ISR Architecture Framework Compliance ; Appendix 3. USIGS Glossary Extract ; Appendix 4. USIGS Architecture Compliance Checklist
Point of Contact: Mark Owens
Last updated by Mark Owens on 9 June 1999.