Statement of Work



29 Jun 97




1.1 Background 4

1.1.1 NIMA Mission 5

1.1.2 NIMA Charter 5

1.1.3 United States Imagery & Geospatial Information Systems (USIGS) 5

1.2 Scope 6

1.2.1 Overview 7

1.2.2 Technical Direction 8

2.0 APPLICABLE DOCUMENTS (Attachment 1 to SOW) 9

2.1 Compliance Documents

2.2 Reference Documents


3.1 Program Management 9

3.1.1 Program Management Review 10

3.1.2 Staffing 10

3.1.3 Program Planning, Monitoring and Control 10

3.1.4 Subcontractor/Teaming Management 11

3.1.5 Schedule Development 11

3.1.6 Reporting Risk Assessment and Mitigation 12

3.1.7 Security Control 12

3.1.8 Transition Execution 12

3.1.9 Formal and Informal Reviews and Meetings 12

3.1.10 Work Breakdown Structure (WBS) Development 13

3.2 Training 13

3.3 Life Cycle Cost Modeling 13

3.4 Pre Acquisition Support 13

3.5 Limited Hardware & Software Procurement 13

3.6 Deliverables 14

3.7 Travel 14


4.1 USIGS Architecture Definition and Migration Planning 15

4.1.1 USIGS Architecture Development 15

4.1.2 USIGS Architecture Implementation Support 16

4.1.3 Imagery and Geospatial Community (IGC) Coordination 17

4.1.4 Systems Engineering Operations Concept 17

4.1.5 Enterprise (Element & Interface) Requirements

Development and Allocation 17

4.1.6 Migration Planning 19


4.3 USIGS Systems Configuration Management Control 21

4.3.1 Infrastructure 21

4.3.2 Configuration Management Support to USIGS Architecture,

Elements, Systems, Programs, & Projects 22

4.4 USIGS Transition, Readiness, Upgrades, & Evolution 23


5.1 Studies 24

5.2 Modeling and Simulation 24


6.1 USIGS Standards and Interoperability 25

6.2 Standards Integration Management 26








1.1 Background

The National Imagery and Mapping Agency (NIMA) is a combat support agency of the Department of Defense (DoD), supporting the Secretary of Defense, the Director of Central Intelligence (DCI), and other national-level policymakers in the areas of imagery, imagery intelligence, and geospatial information. NIMA is a member of the national Intelligence Community and the single entity upon which the U.S. Government relies to coherently manage the disciplines of imagery and mapping.

Since the late 1980's, the threat to our national security has become more diverse and less predictable. To deal with this change in the nature of the threat decision makers require: more precise information, at a faster rate, provided in easily-understood formats, that can be adapted to satisfy unique requirements.

NNIMA was established on 1 October 1996 to address these expanding requirements. It was created from the former Defense Mapping Agency (DMA), Central Imagery Office (CIO), and the Defense Dissemination Program Office (DDPO) in their entirety; the missions and functions of the National Photographic Interpretation Center (NPIC); and the imagery exploitation, dissemination and processing capabilities of the National Reconnaissance Office (NRO), Defense Intelligence Agency (DIA), and the Defense Airborne Reconnaissance Office (DARO).

1.1.12 NIMA Mission

The NIMA mission is to provide timely, relevant, and accurate imagery, imagery intelligence, and geospatial information in support of national security objectives. NIMA is responsible for providing support to military operations, defense agencies, the Central Intelligence Agency (CIA), the Defense Intelligence Agency (DIA), and other Federal Government Agencies on matters concerning imagery and geospatial information relating to national security. NIMA was created by consolidating several agencies into a single entity which requires consolidating several distinct missions into the NIMA mission. Under this mission NIMA is assigned the responsibility to prescribe and mandate standards and end-to-end technical architectures related to imagery, imagery intelligence, and geospatial information for the DoD Components and for non-DoD elements of the Intelligence Community.

1.1.23 NIMA Charter

NIMA is chartered to provide management and operation (collection tasking, imagery analysis and geospatial information production) of the imagery and geospatial services for National customers and for support to military operations, planning, training, and weapons systems. It is to ensure access and dissemination of primary and secondary imagery, imagery intelligence, and geospatial information. NIMA is responsible for the acquisition, design, development, implementation, installation, transition, and sustainment of systems, standards, and technology pertaining to the United States Imagery and Geospatial Information Systems (USIGS) for the imagery, imagery analysis, and geospatial information community. NIMA ensures that imagery intelligence, geospatial information, and other needs for imagery are managed effectively and efficiently in a manner conducive to national security and consistent with the authorities and duties of the Secretary of Defense and the DCI.

1.1.34 United States Imagery and Geospatial Information Systems (USIGS)

The United States Imagery and Geospatial Information System (USIGS) is an umbrella term for the suites of systems formerly called the United States Imagery System (USIS) and the Global Geospatial Information and Services (GGIS). USIGS will be defined by the migration of the former USIS and GGIS architectures, with the goal of common graphical interfaces, and seamless information exchanges. In addition to the former USIS and GGIS framework, USIGS will include new capabilities, and leverage the pre-existing architecture work. USIGS will use the DII/COE C4ISR Architecture Framework, and the Joint Technical Architecture as its baseline.

1.2 Purpose and Scope of Work

This Statement of Work (SOW) and the accompanying Technical Letter of Direction (TLD) describe the activities tasksand deliverables associated with the executionof the contract, to of the system engineering and integration activities for NIMA in the performance of its mission to support imagery and geospatial information users.

On 1 October 1996, NIMA inherited multiple engineering and integration support contracts with respective parochial approaches and methodologies as well as legacy organization goals and objectives. This has resulted in the government spending an inordinate amount of time trying to integrate disparate, redundant and/or conflicting efforts.

NIMA is currently defining a USIGS architecture that will accommodate the overall agency mission of providing timely and relevant imagery, imagery intelligence, and geospatial data to the right user at the right time and classification level. NIMA requires a single end-to-end engineering and integration services contract to develop, manage, and execute the migration of the USIGS from today's disjointed and complex array of "stovepipe" programs and projects to tomorrow's efficient and interoperable architecture for the provision of imagery, imagery intelligence and geospatial data to USIGS customers. A strong top-down, end-to-end systems engineering and integration process is required to provide not only high level design and architectural constructs, but also program/project level requirements, design, interfaces, and systems and standards baselines which adhere to the constructs of the USIGS architecture. To accomplish this objective, the following major activities must be executed in concert with one another.

A) The overall "to-be" USIGS architecture must be defined and maintained. This will be based on NIMA and community operations concepts, the C4ISR Architecture Framework, the Joint Technical Architecture and/or other like sources of guidance and direction as appropriate. The elements of the USIGS (Management, Archive and Dissemination, Exploitation, and Infrastructure) must migrate from the current state of independent and non-interoperable systems to complementary activities which ensure high levels of functionality and interoperability within the NIMA, the USIGS and any external operations, architectures and/or systems to which the USIGS must be compatible.

B) Each of the organizations responsible for elements of the USIGS must take their delegated functionality and decompose it into coherent Mission Support Applications (MSAs) while migrating their legacy programs and projects away from independent systems to a functional application environment.

C) Evolutionary steps (effectivities) must be defined and executed that evolve the "as-is" architecture to a "to-be" USIGS architecture in definable and achievable temporal target states by providing enterprise level engineering and integration across the entirety of the USIGS.

In addition to these activities, the entire process must be flexible enough to accommodate: (1) changing and new requirements, (2) incorporation of emerging technology, (3) analysis and trade studies to achieve balance between cost, schedule, and requirements, and (4) ever evolving systems solutions and migration plans which maximize the use and reuse of COTS/GOTS hardware and software.

NIMA intends to forge a partnership between itself and the eventual SE/SI vendor(s) who will be responsible for providing the expertise to design, engineer, and integrate all facets of the USIGS enterprise.

1. 2.1 Overview

In the meeting the NSES requirements, the Contractor shall utilize a systems engineering approach which will assist NIMA in the design, implementation and management of its total systems environment involving hardware and software, as well as other system life-cycle elements. These programs, projects, and activities may be modified in the future, to accommodate surge, crisis, and additional related efforts as identified by the Government as well as other projects and programs which may emerge at a later date and shall be considered within the scope of this SOWas well as other projects and programs which may emerge at a later date and shall be considered within the scope of this SOW, as required by the Government. The Government's focus in this SOW is upon a disciplined system engineering approach and the quality of value added Systems Engineering/ Integration services rendered in a comprehensive and cohesive manner, which will result in the accomplishment of the Government's requirements. NSES requirements include: proof of concept, operational concepts development, prototyping, modeling & simulation, risk analysis, risk assessment, risk mitigation, system integration, integration planning, engineering, development, acquisition support, requirements definition, requirements allocation, requirements verification, system verification, system transitions, upgrades, implementation, systems configuration management and control, standards development, studies and analysis, functional analysis, resource allocation, and analyses of problems to support the development, implementation and improvement of the USIGS and its programs, projects, and activities. The Contractors' engineering/integration process executed in the conduct of these activities shall be a structured, disciplined, and documented technical effort through which systems products and processes are simultaneously defined and developed. The Contractor's systems engineering process efforts shall be directed at providing support for all programs, projects, and activities identified in the TLD.

1.2.27 Technical Direction

The Contracting Officer (CO) will appoint, in writing, a Contracting Officer's Representative (COR) to provide written technical direction within the scope or work defined herein. The CO will also appoint technical monitors to provide more detailed technical direction and clarification within the scope of work for each of the general areastasks defined in this SOW and the Technical Letter of Direction (TLD).

The COR through the Contracting Officer will provide a written Technical Letter of Direction on the specific programs, projects, and activities to be performed upon contract award. Update and /or modification to theAdditional TLD will thereafter be provided on an FYly thereafter basis at the beginning of each Option Year, if exercised by the Government. This TLD will cite specific requirements and deliverables for each program, project, and activity.

The Contractor shall begin work immediately upon contract award based upon the requirements specified in this SOW and the TLD. The Contractor shall deliver a draft work plan within 10 working days after receipt of the TLD. The draft work plan shall contain detailed definition and applicable schedules for the implementation of associated events for programs, projects, /program and activities to be conducted as contained in the TLD. This plan will be considered draft and will be reviewed and commented on by the COR within 10 days after receipt. The Contractor will have 10 working days to negotiate and revise the draft work plan based on the COR's comments. This revised work plan shall be submitted to the COR for final approval. The approved work plan will form the basis for the Monthly Status and Progress Report status defined in paragraphs 3.1 of this SOW.


SEE Section J, Attachment 2



The Contractor shall provide all services and supplies to accomplish work specified in the SOW, the Technical Letter of Direction (TLD), and other additional documents as required by the contract.

3.1 Program Management

The Contractor shall establish a formal organization responsible for executing the total effort required by this activity. A clear line of management authority shall exist among all organizational elements (including subcontractors/partners). Roles, responsibilities, and reporting requirements shall be established for each organizational element.

It is the responsibility of the Contractor's management organization to ensure that all of the contractor's efforts are integrated and that the integrity of the engineering process is maintained. The contractor is expected to aggressively pursue the elimination of redundant efforts, better integration of disparate efforts, resolution of conflicts in direction, and other NIMA enterprise deficiencies in the management of the NSES effort.

It is the responsibility of the PM to provide a monthly Status and Progress Report and conjunction with the conduct of a monthly Program Managers Review (PMR)Reports. The Monthly Status and Progress Report shall summarize the contractors accomplishments during the previous month, forecast major non-routine activities for the current month, identify hours worked and costs incurred, and identify any significant issues or problem areas requiring resolution by either the Government or the Contractor. Any proposed changes in contractor personnel or personnel assignments shall be highlighted. It is the Government's intent that this report be concise, current, economically prepared, and focused on major items. This report shall be provided in both hardcopy and on a NIMA LAN compatible 3.5 inch floppy disk in DOS, Microsoft Word compatible format. (CDRL A001)

3.1.1 Program Management Review (PMR)

The Contractor shall conduct a Program Management Review (PMR) at the Contractor's facility on a monthly basis unless otherwise directed by the CO/COR. The Contractor shall provide status on all contract activities. The Contractor PMR shall summarize the technical activities, labor productivity data, and status of funds. The Contractor shall PMR will identify problem areas as well as general and technical issues and accomplishments. The Ccontractor shall present the status of all work recently completed, all ongoing work, and all work planned, and identify corrective actions for the resolution of discrepancies. The Contractor shall brief, at a summary level, the information contained in the CFSR. Detailed CFSR information shall be briefed to the CO/COR at an Executive Session as required.

3.1.2 Staffing

a.The Contractor shall appoint will appointa dedicated full time Program Manager (PM) who has responsibility for accomplishment of all tasks to be performed under this contract and who shall will exercise technical and management leadership of the all contractor personnel.'s team. The PM shall be responsible for the contractor's technical, cost, and schedule performance. The PM shall be the principal interface between the program and the contractor's corporate organization, the program and associate contractors, and between the contractor and the Government for all matters relating to the contract.

In addition to the Program Manager, the Contractor shall provide a qualified team consisting of Key Personnel and Other Personnel to effectively plan, implement, manage, and support all programs, projects, and activities identified in this SOW and the TLD.

3.1.3 Program Planning, Monitoring and Control

The Contractor shall plan, monitor, and control technical, cost, and schedule performance of all NSES engineering efforts in accordance with the SOW and TLD. The Contractor shall establish budgets and schedules for the expenditure of contract funds and shall monitor, control, and report on expenditures versus budgets and planned resources and schedule versus actuals, and report associated variances, (plus or minus 10%). The Contractor shall provide a Cost Funds Status Report (CFSR) in accordance with CDRL A002.

The contractor shall implement procedures to monitor technical, cost, and schedule performances. The contractor shall employ metrics (cost, schedule, quality, performance, complexity, etc...) to assess and report program status relative to applicable NIMA systems engineering efforts, as required by the CO/COR. These metrics and procedures should enable the contractor to detect and predict deviations from planned or required performance in time to take effective corrective action. The contract shall implement corrective action procedures to prevent, circumvent, or mitgate the consequences of deviations from planned or required performance. The Contractor shall present metrics analysis and data reports and support data in conjunction with each monthly PMR.

3.1.4 Subcontractor/Teaming Management

The Contractor shall manage their subcontractor, teaming, and/or partnership arrangements in accordance with the terms and conditions of these arrangements that were submitted as part of the offeror's proposal. The Contractor shall provide cost data, and technical specifications (when applicable) for any subcontractor and/or vendor supplied efforts or items. Any changes in the Contractor subcontractor/teaming agreements shall be fully disclosed to and coordinated with the Government (COR) and approved by the Contracting Officer prior to their execution.

3.1.5 Schedule Development

The Contractor shall develop and maintain the NIMA Master Schedule which defines the schedules for all activities, tasks, milestones, and deliverables. The Contractor shall provide a briefing at the Program Managers Review (PMR) of the status and progress of all NIMA systems engineering efforts against the Master Schedule identified in the TLD as part of the monthly PMR. The Master Schedule shall consist of a top-level schedule and lower tier schedules showing increasing levels of detail down to and including the work package level. The contractor shall implement controls to ensure that only authorized changes are made to the Master Schedule.

3.1.6 Risk Assessment and Mitigation

The Contractor shall develop and implement risk management mechanisms and associated activities that will form the basis for identifying, assessing and monitoring risks for the USIGS enterprise to avoid unsatisfied user requirements and cost and schedule impacts. The Contractor shall identify, propose, assess, monitor and report on alternatives to mitigate risks to the success of both the systems engineering activities and the overall technical effort throughout the life cycle of the elemental USIGS and its components. The Contractor shall identify areas of cost, technical, and schedule risk associated with Management of the overall effort in the PMR agenda and provide the status of risk reduction and risk mitigation planning in a briefing during the monthly PMR.

3.1.7 Security Control

The Contractor shall conduct program security in accordance with the Contract Security Classification Specification, DD Form 254. The Contractor shall provide security control and support for all classified activities within this contract including but not limited to control of accesses, communications, publications, travel by contractor personnel, and visits to Government and other Government contractor locations and facilities.

3.1.8 Transition Execution

The Contractor shall execute the Transition of services in accordance with the Contractor provided, Government approved plan for all NSES engineering/

integration efforts being transitioned from current on-going NIMA SE/SI related efforts. The Contractor shall be responsible for an efficient and effective transition of all work efforts within six (6) weeks following contract award.

3.1.9 Formal and Informal Reviews and Meetings

The Contractor shall support formal and informal reviews and meetings as required by the CO, COR, or technical monitors. The Contractor shall support NIMA enterprise business areas in scheduling, coordinating and recording technical exchange meetings, technical information meetings, design reviews, and other formal or informal reviews or meetings as directed by the CO, COR, and/or technical monitors.

3.1.10 Work Breakdown Structure (WBS) Development

The Contractor shall develop, implement, and maintain a Contract WBS using the NIMA NSES WBS (see SOW Table of Contents) as a baseline. The Contract WBS shall be the key reference document in defining the program structure and organization for planning, controlling, and reporting requirements. The Contractor WBS and NSES baseline may be modified upon approval of the Government at the third tier or higher level (levels below the third tier may be modified by the Contractor without Government approval through coordination with the Government.).

b. The Program Manager will work closely with the COR and the CO to facilitate the planning and accomplishment of critical objectives, both general and specific, rapidly and effectively, taking maximum advantage of all available resources.

** c. If the Contractor enters into a teaming partnership, this relationship shall be managed in accordance with partner's approved agreement(s).

** d. The Contractor shall manage any sub-contractors in accordance with the its approved sub-contracting plans.

e. The Contractor shall provide a standard method of generating (determining, developing, and producing) reliable Labor Productivity Data (metrics) for the contract presentation at the Program Managers Review (PMRs) (see paragraph 3.2). Labor Productivity Data shall be provided during PMRs and within the Monthly Progress and Status Report (see paragraph 3.1).

f. The Contractor shall provide all services and adequate staffing to effectively plan for, implement, perform, and manage the activities in this SOW and the Technical Direction.

g. The Contractor shall manage schedules for all tasks performed under this SOW. Schedule status shall be made available to NIMA as required to maintain management tracking and oversight.

h. The Contractor shall manage cost for all work performed under this SOW. Cost data shall be made available to NIMA as required to maintain management tracking and oversight.

i. The Contractor shall provide and ensure accountability.

j. The Contractor shall monitor and control the technical effort.

k. The Contractor shall direct, track, and review the SOW, Management Plan's, and Technical Direction's accomplishments, results, and risks against their published estimates, commitments, and plans.

l. The Contractor shall provide visibility of actual progress and risks. Direct, track and review NIMA project's accomplishments, results, and track against their documented estimates, commitments, and plans.

m. The Contractor shall Direct technical effort in accordance with the Technical Direction.

n. The Contractor shall Track actual use of resources against the Technical Direction.

o. The Contractor shall Track and review performance against the established technical parameters.

p. The Contractor shall take corrective actions when actual results deviate from plans.

3.2 Training

The Contractor shall provide Training as required by the Government, and as specified in the TLD.

3.3 Life Cycle Cost Modeling

The Contractor shall provide Life Cycle Cost Modeling support as required by the Government and as described in the TLD.

3.4 Pre-Acquisition Support

The Contractor shall provide Pre-Acquisition Support when required by the Government and as described in the TLD.

3.5 Limited Hardware & Software Procurement

The Contractor shall utilize limited hardware & software procurement when it is determined to be in the best interest of the Government and the associated program, project, or activity.

3.6 Deliverables

During the performance of the work specified in this SOW and in subsequent Technical Directions, Tthe Contractor shall provide periodic and/or one-time deliverables as specified in this SOW and in subsequent Technical DirectionTLD. During the period of this contract, and as described in Sections 4.0 through 8.0 of this SOW and in the subsequent Technical Directions, Tthe contractor shall

provide all reports and documentation required within the time period specified in the SOW, TLD or in accordance with written guidance from the CO/COR.

3.4 NSES Transition Activities

3.7 Travel

a. The Contractor shall be required to travel in the performance of the NSES contract. The following may be among the destinations required for travel:

Headquarters of all Unified Commands, and related sites in given Command's Area of Responsibility (AOR); components of the Army, Navy, Air Force, and Marine Corps; and all/any intelligence agency facilities; all NIMA locations; and Government contractor facilities.

No First Class travel accommodations are permitted while traveling under this contract. Travel will be reviewed by the Government based on FAR 31.205-46, Travel Costs. b. The contractor shall coordinate as required with the COR, at the beginning of each month, projected travel to be initiated by the contractor under this contract.


The Government requires the Contractor to provide selective application of scientific and engineering efforts to:

a. Transform an operational need into a description of a system configuration which best satisfies the operational need according to applicable measures of effectiveness.

b. Integrate related technical parameters and ensure compatibility of all physical, functional, and technical program interfaces in a manner which optimizes the total system definition and design at both the USIGS and program/project level.

c. Integrate the efforts of all engineering disciplines and specialties into the overall engineering effort.

4.1 USIGS Architecture Definition and Migration Planning

The Government requires the Contractor to develop, evolve, and promote implementation of the USIGS Architecture and migration plan as described in this Statement of Work and further defined in the Technical Letter of direction

4.1.1 USIGS Architecture Development

The Contractor shall:

a. Maintain and evolve, remaining consistent with the DoD C4ISR Architecture Framework as it evolves, the USIGS Architecture Manangement Plan, and the USIGS Architecture Framework.

b. Maintain and evolve the products which constitute the operational, technical, data, and system architectures as defined in the USIGS Architecture Framework using a well-defined system engineering process.

c. Coordinate development of the operational, technical, data and systems architectures with one another and ensure the set of USIGS Architecture products is complete, consistent, and mutually supportive.

d. Coordinate development of the USIGS Architecture products with the other systems engineering activities defined in this Statement of Work and ensure the USIGS Architecture describes an implementable, cost-effective, and complete solution to the needs of NIMA and the Imagery and Geospatial Community.

e. Ensure the USIGS Architecture complies with the appropriate DoD and Intelligence Community policies, regulations, directives, processes, and procedures. This includes but is not limited to the Defense Information Infrastructure (DII) Master Plan, the Joint Technical Architecture (JTA), the C4ISR Architecture Framework, the DII Common Operating Environment (COE), and the DII Shared Data Environment (SHADE).

4.1.2 USIGS Architecture Implementation Support

The Contractor shall enforce compliance with the USIGS Architecture by:

a. Reviewing USIGS Architecture products for implementation feasibility;

b. Maintaining and populating the USIGS Integrated Road Map (IRM);

c. Performing system migration planning (from "as-is" to "to-be" views of USIGS) using a well-defined system engineering process;

d. Reviewing acquisition program milestone documents for architectural compliance and impact;

e. Reviewing acquisition program requirement documents and specifications for architectural compliance;

f. Reviewing NIRB, NERB, NCCB RFCs for architectural compliance and impact;

g. Reviewing requirements documents (MNS, CRD, ORD, etc.) for compliance with, and impact on the USIGS Architecture;

h. Reviewing NIMA planning documents to support USIGS migration planning;

I. Conducting communications analyses and trade studies to support migration planning activities;

j. Conducting security analyses and trade studies to support migration planning activities; and

k. Conducting hardware and software applications analyses and trade studies to support migration planning activities.

4.1.3 Imagery and Geospatial Community (IGC) Coordination

The Contractor shall coordinate USIGS Architecture development and use with the DoD C4ISR community, intelligence community and imagery and geospatial community and international partners by:

a. Developing and briefing tutorial information, for various audiences, about the USIGS Architecture;

b. Identifying, tracking, and analyzing DoD, IC, and IGC architectural issues, and developing appropriate recommendations for changes to the USIGS Architecture, including but not limited to those associated with:

(1) airborne reconnaissance architectures and systems,

(2) national reconnaissance architectures and systems, including the Future Imagery Architecture,

(3) commercial imagery architectures, services, and systems.

4.1.4 Systems Engineering Operations Concept

The Contractor shall refine existing concepts of operations (CONOPS) and develop new CONOPS to address evolving business processes, imagery and mapping integration, and emerging technologies across NIMA and its enterprise. The Contractor shall develop and support implementation of concepts and procedures to define changes to future systems requirements.

4.1.5 Enterprise (Element and Interface) Requirements

Development and Allocation

The Contractor shall develop, derive, define, and allocate the USIGS systems architecture requirements to the USIGS Elements and Interfaces. The Contractor shall:

a. Develop, maintain and update the technical architecture elements of system(s) and segment(s) requirements in response to NIMA and customer needs.

b. Define future USIGS element level requirements to be incorporated into follow-on capabilities.

c. Investigate options and applicability of methodologies to develop future system requirements.

d. Develop and maintain requirements traceability for the architectures', user's, interfaces, segments, and systems requirements.

e. Define and refine architecture-level and interface requirements, and resolve requirements issues for implementation.

f. Maintain and evolve element functional-level requirements baselines in response to the integration of new community systems and the expanded requirements of user organizations.

g. Evaluate proposed designs to satisfy element functional-level requirements. Support design review processes by coordinating NIMA input and participating in the reviews.

h. Maintain requirements status as systems, programs, projects and activities evolve.

i. Identify, develop, derive, define, and allocate internal and external interface requirements for the USIGS architecture, the elements of the USIGS, and related external systems.

j. Define site infrastructure and communications interfaces and associated protocols that will facilitate interoperability among imagery and mapping systems.

k. Understand, define, refine, and allocate community organization's requirements for AIS in the context of the current and projected security environment, as part of the site infrastructure and global communications elements.

l. Understand, define, refine and allocate customer requirements for collection, processing, dissemination, archive, and exploitation system services.

m. Develop and prioritize new and existing imagery and geospatial information systems requirements by working with the program management offices, the Requirements Office, the Architecture Office and the System Engineering Office.

4.1.6 Migration Planning

The contractor shall establish and update Migration Plans for the USIGS based on a defined system engineering process:

a. Perform system migration planning for evolution of existing systems into the USIGS and the continued evolution of the USIGS.

b. Review Architecture products and operations concepts for development of Migration Strategies throughout the evolution of USIGS.

c. Identify and develop methodologies for estimating all elements of the cost analysis for the USIGS.

d. Recommend and perform modeling and analysis for USIGS in support of migration alternatives.

e. Conduct trade studies to support migration planning activities.


The Contractor shall perform Systems Integration as a part of Systems Engineering in accordance with the Contractor's approved Systems Engineering Process against all programs, projects, and activities as defined in the SOW or TLD. The Contractor shall ensure project and program development efforts converge to achieve the NIMA Strategic Goals and Objectives. The Contractor shall:

a. Develop a methodology and strategy for, and perform systems integration management that is compatible with the Command, Control, Communications, Computing, and Intelligence, Surveillance and Resonance (C4ISR) Architectural Framework and Department of Defense Intelligence Information System (DoDIIS) community System Integration practices and processes. Provide Systems Integration support to ensure that the systems elements of NIMA (to include internationally fielded systems) will function as a whole.

b. Conduct integration methodology activities throughout the entire USIGS systems life cycles.

c. Conduct system/segment/element program design reviews, community forums, and technical exchange meetings.

d. Analyze critical operational problems. Develop and implement integrated problem resolution plans.

e. Ensure that the USIGS will function as a whole. This involves identifying, defining, and controlling interfaces, as well as verifying system functions that require multiple systems/elements. These activities occur throughout the entire USIGS systems life cycle.

f. Support the readiness review process. Develop questions/comments/issues, and respond to questions/comments/issues. Prepare summary reports.

g. Track and review performance against established technical parameters, schedules and milestones.

h. Maintain and monitor a three tiered consolidated NIMA Master Schedule for NIMA programs, projects, and activities showing select events to complete development of the USIGS. Maintain and monitor lower-level USIGS milestones and schedules for USIGS programs, projects, and activities. The schedules shall show dependencies with other NIMA and external programs and identify factors that are key to critical paths.

i. Plan, develop, organize and provide administrative support to community-level conferences and other fora sponsored by NIMA. Coordinate on issues such as logistics, security, action items, pre- /post-conference publications, and provide associated documentation to the USIGS/NIMA user community.

j. Support system development, evolution, and fielding through field demonstrations and exercises designed to evaluate new concepts of operation, clarify requirements, support systems analysis, and evaluate emerging technology and proposed technology insertions. Participate in exercise planning activities, identify exercise objectives, develop scenarios, participate in evaluations, and "quick looks", conduct post-exercise analysis, and write after action reports.


The Contractor shall provide assistance and support in the performance of Configuration Management efforts.

4.3.1 Infrastructure

The Contractor shall develop and refine the Configuration Management infrastructure for NIMA (internal, external and international) systems. The infrastructure shall include all configuration control boards, (both internal and external), and the roles and responsibilities of the Government Configuration Management Office that supports each board. In addition the Contractor shall:

a. Provide for the administration of control board activities to include; logging and distribution of Request for Change (RFCs) and Engineering Change Proposals (ECPs).

b. Establish the schedule and coordinate the agenda for each of these Boards.

c. Capture and track action items from each Board.

d. Publish and disseminate minutes, final reporting results, and changes from each Board.

e. Prepare TWX/DoD format message for each Board as required.

f. Maintain a comprehensive RFC status monitoring system covering all actions from RFC issuance through change page distribution.

g. Provide support functions as required to ensure effective program configuration control.

h. Publish, distribute, control, and maintain USIGS documents, plans, procedures, and directives.

i. Prepare and issue authorized changes to NIMA controlled documents for which the contractor is the custodian.

j. Develop and support control procedures required for CM, as well as, the accounting and disposition of proposed changes to future systems requirements databases.

k. Establish and maintain a configuration management technical library for the USIGS architecture and its' systems.

l. Establish and maintain procedures, processes, and policy for the technical library.

m. Log, update, and maintain associated documentation or manuals in the library.

4.3.2 Configuration Management Support to USIGS Architecture, Elements, Systems, Programs, and Projects

The Contractor shall:

a. Provide support as necessary to insure the successful integration of new and modified requirements into the USIGS architecture. Support shall include identification and documentation of customer requirements, CDRL review and analysis, attendance and participation at program design reviews, issue identification and resolution, RFC generation, review, analysis, and redline.

b. Maintain the configuration management functions for maintenance, status, analysis, and control for data changes to the USIGS architecture and its' component systems or subsystems. Maintain traceability of system requirements through the life cycle of each system. Manage the USIGS architecture and its subsystems by providing accurate and current configuration data and status.

c. Coordinate changes which may impact internal and external organizations.

d. Support the development and maintenance of Joint Requirements Documents (JRDs), Interface Control documents (ICDs), and development of Memorandum of Agreements (MOAs) with external system interfaces.

4.4 USIGS Transition, Readiness, Upgrades and Evolution

The Contractor shall provide support in the following areas:

a. Develop and support a readiness process and Requirements Verification and Traceability Matrix (RVTM) for managing select program and projects within NIMA. The process shall be in concert with DODD5000.1 and 5000.2-R.

b. Integrate, update, and maintain readiness plans for critical system transitions, and ensure the ability of USIGS deliveries to utilize or interface with existing/planned systems.

c. Support imagery and geospatial system upgrade (s), transition (s), and related technical exchange meetings, to include participation in resolution of USIGS system transition issues.

d. Support definition, coordination and implementation planning of imagery and geospatial systems operations and maintenance activities.

e. Provide support to and coordination of user organization actions for the USIGS which are required to meet applicable security accreditation standards.

f. Analyze and provide special studies to identify requirements for post transition upgrades.

g. Support the demonstration of systems and software during the test and verification process. Execute verification and validation of requirements through demonstration and test.

h. Collect and evaluate demonstration and test data. Provide formal test witnessing and test analysis.

i. Provide the infrastructure planning support, including security considerations, in preparation for the transition of systems to NIMA and community users.

j. Support the installation check-out and test (IC&T) of hardware and software and the integration of systems into NIMA sites and at community user locations.



The Contractor shall develop a standard study process for Government approval, that shall be used as the framework for initiating, planning, coordinating, executing, and providing oversight of study and analysis activities. The process shall define the approach and evaluation criteria for the analysis, as well as for the studying, and selection of alternatives. Examples of the type of studies are:

System Upgrades; End-to-End Architecture; Community Proposals; Exploitation Functions; Business Process Standards; Business Process Reengineering; Open System Architecture; Future Initiatives; Pre-Acquisition Engineering; Short -term architectures; Long-term Architectures; Requirements Definition Studies; Independent Cost Analyses; Special Studies; ad hoc efforts; etc.


The Contractor shall conduct modeling and simulation necessary to validate USIGS requirements. The objective of these efforts is to identify changes to USIGS requirements which are necessary to: correct errors, incorporate missing or incomplete requirements, accomodate new requirements, delete redundant or unnecessary requirements, eliminate ambiguities, ensure feasibility of implementation, ensure testability of requirements, and eliminate design from the requirements statements.

The Contractor shall ensure NIMA Compliance with DoD modeling and simulation (M&S) directives and policy; provide authoritative and faithful representation of NIMA systems and processes within DoD and Intelligence Community M&S activities (specifically the organizational relationships supporting DoD training and exercise activities and the Joint Simulation System development); and represent NIMA in forums centered on the advancement of technology and applications for simulated and synthetic environmental representations of terrain.

To execute the above activities, the contractor shall:

a. Perform development (next version software modifications and required documentation), test, delivery, maintenance, and training for NIMA M&S tools.

b. Provide functional and product representations of NIMA's intelligence processes.

c. Maintain and present the monthly M&S briefing to the Intelligence Community Modeling and Simulation Coordinating Group (IC M&S CoG). The monthly M&S briefing is a summary of key activities across the DoD and Intelligence modeling and simulation communities.

d. Coordinate the development and capabilities of Image Perspective Transformation technologies.

f. Capture data required for the modeling and simulation tools employed for specific tasks.

e. Use, or support the use of , existing modeling and simulation tools and support tools. Execute simulations and assess post-processing simulation output data.



The Contractor shall support the NIMA Standards and Interoperability Program which comprises the imagery, imagery intelligence and geospatial components of the Department of Defense and the Intelligence Community, and the IGC.

The contractor shall:

a. Support NIMA in meeting USIGS requirements through life cycle management of its interoperability standards.

b. Manage the standards, profiles, and specifications under NIMA in accordance with the Defense Standardization Program, the guidelines of the Standards Coordinating Committee (SCC) of the Military Communication and Electronics Board (MCEB), and the Standards Panel (ISS-S) of the Intelligence Systems Board (ISB) or their successor(s).

c. Support NIMA in the selection, development, testing, integration, implementation, and maintenance of standards, standards profiles, specifications, interfaces, interoperability, data and metadata that are part of the USIGS Technical Architecture and needed to satisfy NIMA customer and user requirements. The performing of these functions will be done within the context of broader defense and intelligence architectures as well as current policies such as, "the primacy of suitable commercial solutions".

d. Assess and provide recommendations on emerging standards, technologies, and related documentation.

e. Review and provide recommendations on new user or system requirements for new standards and impacts to existing ones.

f. Develop technical papers, and prepare and present technical briefings, to national and international fora.

6.2 Standards Integration Management

The Contractor shall provide integration management support to ensure that all NIMA activities pertaining to standards and interoperability are synchronized across programs, projects, activities, and organizations. The contractor shall:

a. Monitor and report on internal and external imagery and geospatial standards activities.

b. Input Standards data/milestones into the NIMA Master Schedule.

c. Ensure Standards consistency across documents under NIMA control.

d. Monitor technology advances that can benefit NIMA systems and identify candidates for standardization or adoption in the community supported by NIMA.


The contractor shall provide support in the following areas:

a. System/Subsystem/Tool Evaluation including but not limited to: technology assessments; prototyping proposed new capabilities; lab infrastructure support; technology insertion process development and implementation with insertion opportunities shown in future systems architectures and operations by identifying appropriate schedule milestones during the system's planning/development cycles.

b. Imagery delivery support, and imagery exploitation process support through the evaluation and/or prototypes of COTS and GOTS applications and tools to advance the production of imagery analysis (imagery intelligence - IMINT) and enhance the production of geospatial information.

c. Extend the collaboration and value-added services of imagery analysis and cartography in support of NIMA's customer base.

d. User and technical assessment and evaluation of advanced applications (tools) and advanced infrastructure technology.

e. Analysis, assessment, and recommendations for improvements to the components of the USIGS architecture to enhance productivity.

f. Coordination and collaboration with the imagery-based research and development community to support common understanding of technology interfaces to DoD and other laboratories - including DARPA, NRO, DARO, and other Military Service Laboratories, and associated Industry, Research Institutes, and Academic communities.

g. Develop an orderly classification for technologies critical to the formation of NIMA R&D programs.

h. Develop technology roadmaps.

i. Support outreach to community members, partners, and industry to identify opportunities for synergy in R&D projects.

j. Support standing and special technical working groups to advance the USIGS technology base and technology transfer.

k. Support field demonstrations and exercises.