1 JULY 1997

Technical Letter of Direction
(Project Description/Objective)

Base Period: JAN 98 - SEP 99

Option 1: OCT 99-SEP 00

Option 2: OCT 00-SEP 01

Option 3: OCT 01-SEP 02




1.1 United States Imagery and Geospatial Information

Systems (USIGS)Architecture Development ................................... 6

1.2 USIGS Architecture Implementation Support................................... 7

1.3 Imagery and Geospatial Community (IGC) Coordination................ 8


2.1 Interoperability Standards .................................................................. 9

2.2 USIGS Architecture Support .............................................................. 10

2.3 Systems Integration ............................................................................. 12


3.1 Program Engineering & Program Control ......................................... 13

3.2 Requirements Management System (RMS) ....................................... 16

3.3 Integrated Information Management (IIM). ..................................... 19


4.1 Program Control Division .................................................................. 22

4.2 Program Engineering Division ........................................................... 23

4.3 Information Delivery Division ........................................................... 25

4.4 Information Storage Division ............................................................. 27

4.5 Information Access Division ............................................................... 30

4.6 Program Support Division .................................................................. 32


5.1 Systems Engineering and Integration ................................................. 34

5.2 Digital to Plate System and Scan Systems (DTP) ............................... 38

5.3 Enhanced Imagery System (EIS) ........................................................ 39

5.4 Standard Automated Material Management System

(SAMMS)Distribution Standard System (DSS) .............................. 40

5.5 Synthetic Aperture Radar (SAR) Production Initiative .................... 42

5.6 Interferometric Synthetic Aperture Radar (IFSAR) ......................... 43

5.7 Aeronautical Migration Systems (AMS) ............................................ 45

5.8 Data Extraction Segment (DE/S) ........................................................ 46

5.9 Ruler .................................................................................................... 48

5.10 National Exploitation System (NES) .................................................. 51

5.11 Front-End Processing Environment (FPE) ....................................... 52

5.12 Exploitation Support System (ESS).................................................... 53

5.13 Multi-source Intelligence Tools (MINT) ............................................ 54

5.14 NIMA SOFTCOPY............................................................................. 55

5.15 Data Capture and Finishing Environment(DCAFE)

/Vector Product Format (VPF) ........................................................ 55

5.16 Source Analysis ................................................................................... 58

5.17 EI Tools ............................................................................................... 59

5.18 Joint Mapping Toolkit (JMTK) ......................................................... 61




7.1 Project Information Management (PIM) .......................................... 65


8.1 IR Imagery Softcopy Exploitation (IRISE) ....................................... 66

8.2 Automated Target Monitoring System (ATMS) ............................... 66

8.3 Imagery Fusion.................................................................................... 68

8.4 COTS Media Evaluation and Paper Like

Soft/Copy Device (PLSD) ............................................................... 68

8.5 Assisted Target Recognition (ATR) ................................................... 69

8.6 Semi-Automated IMINT Processing ACTD (SAIP) .......................... 70


9.1 Joint Warrior Interoperability Demonstration (JWID) ................... 71

9.2 Strategic Technology and Thrust Development ................................ 73

9.3 DoD & Intelligence Community Technology Planning ..................... 74

9.4 National Research and Development Council (NRDC) .................... 75

9.5 Imagery Derived Products(IDP) / Image Science

Validation Board (ISVB) ................................................................... 76


10.1 International Arrangements .............................................................. 79

10.2 International Customer Support ....................................................... 79


11.1 Reverse Engineering and Modeling ................................................... 83

11.2 Terrain Domain Resource Repository ............................................... 83

11.3 Dynamic Representation .................................................................... 84

11.4 TEMPO .............................................................................................. 85


12.1 Rapid Tools Insertion ........................................................................ 86

12.2 Lab Network Support ........................................................................ 87

12.3 Lab Database Development ............................................................... 88

12.4 Hardware/Software Procurement ...................................................... 89


13.1 Modeling and Simulation Compliance ............................................. 89

13.2 ASAP Operations and Maintenance ................................................ 90

13.3 Capability and Strategy Analysis Tool (CSTRAT) ......................... 91

13.4 Study Support .................................................................................. 92


14.2 Network and Enterprise Systems Office Support ............................ 93

14.2 NIMA Enterprise Network (NEN) ................................................... 93

14.3 Other Duties ......................................................................................


15.1 System Test and Verification ............................................................ 96

15.2 Engineering Review Broad ............................................................... 97

  1. Configuration Management .............................................................. 99

16.0 NSES Program Management ............................................................ 102


1.0.1 Description

The NIMA Architecture Office provides engineering support to develop, evolve, and promote implementation of the USIGS Architecture. Specifically, these tasks support the following activities:

- USIGS Architecture Development

- USIGS Architecture Implementation Support

- DoD, Intelligence Community and Imagery and Geospatial Community (IGC) Coordination

1.0.2 Deliverables

All deliverables will be provided both in reproducible paper form and on magnetic media in the format specified by the government. Periodic (at least semiannually) updates to:

- USIGS Architecture Framework (UAF)

- USIGS Architecture Management Plan (UAMP)

- USIGS Operational Architecture, consisting of:

-- Operational Concept Diagrams

-- Operational Relationship Charts

-- Activity Hierarchies

-- Activity Diagrams

-- Information Exchange Requirements Matrices

-- Node Connectivity Models

-- Operational Scenarios

- USIGS Data Architecture, consisting of:

-- USIGS Logical Data Model

-- USIGS Data Dictionary

- USIGS Technical Architecture, consisting of:

-- Technical Reference Model

-- Standards Profile

-- Emerging & Candidate Standards

-- Conventions

-- Guidelines

-- Emerging Technology & Gaps

-- Glossary

- USIGS System Architecture, consisting of:

-- Systems to Organization Overlay

-- Systems to Activities Overlay

-- Systems Element/Interface Matrix

-- Systems Element/Interface Diagrams

-- Systems to Standards Overlays

-- Systems to Nodes Overlays

-- System Performance Parameters

- USIGS Migration Plans, consisting of:

-- USIGS System Evolution Diagrams

-- USIGS System Evolution Dependency Schedules

-- Inputs to USIGS Functional Manager's Guidance (FMAG) As Required:

- Engineering reviews of key documents, including

-- Mission Needs Statements (MNS)

-- Capstone Requirements Documents (CRD)

-- Operational Requirements Documents (ORD)

-- Joint Requirements Documents (JRD)

-- Functional Requirements Documents (FRD)

-- Concepts of Operation (CONOPS)

-- System/Segment Specifications (SSS)

-- Statements of Work (SOW)

-- Interface Control Documents (ICD)

-- Engineering Change Proposals (ECP)

-- Requests For Change (RFC)

- Architecture Issue Analyses

- Communications Requirements Analyses

- Security Requirements Analyses

- Engineering Trade Studies

- Meeting Agenda & Minutes

- Consolidated Calendars & Schedules

- Architecture Integration Group (AIG) World Wide Web Page Contents (on NIMA servers)

- Updates to USIGS Integrated Road Map (IRM)

- Trip and Meeting Reports

- Briefings

1.1 USIGS Architecture Development

The Contractor shall Maintain and evolve, consistent with the DoD C4ISR Architecture Framework, the USIGS Architecture Management Plan, the USIGS Architecture Framework, and the products which constitute the operational, technical, data, and system architectures.

a. Coordinate development of the operational, technical, data, and system architectures with one another and with the USIGS migration planning activities and the imagery and geospatial community to ensure the set of USIGS architecture products is complete, consistent, and mutually supportive.

b. Coordinate evolution of the USIGS Architecture Framework and the C4ISR Architecture Framework.

c. Support development of the USIGS Operational Architecture.

d. Develop and evolve the USIGS Data Architecture.

e. Develop and evolve the USIGS Technical Architecture.

f. Develop and evolve the USIGS System Architecture.

1.2 USIGS Architecture Implementation Support

The Contractor shall assist in the use of and enforce compliance with the USIGS Architecture.

a. Review USIGS Architecture products for implementation feasibility.

b. Maintain and populate the USIGS Integrated Road Map (IRM).

c. Support system migration planning (from "as-is" to "to-be" views of USIGS).

d. Participate in acquisition program milestone reviews.

e. Participate in acquisition program requirement and design reviews.

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

g. Conduct communications analyses and trade studies to support migration planning activities.

i. Conduct security analyses and trade studies to support migration planning activities.

j. Conduct hardware analyses and trade studies to support migration planning activities.

k. Provide input to and review acquisition documents (JRD, FRD, SSS, SOW, ICD, ECP) for compliance with the USIGS Architecture.

l. Provide input to and review requirements documents (MNS, CRD, ORD) for compliance with and impact on the USIGS Architecture.

m. Provide input to and review NIMA planning documents to support USIGS migration planning.

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.

a. Develop and brief tutorial information about the USIGS Architecture

b. Identify, track, and analyze IGC architectural issues, and develop appropriate recommendations for changes to the USIGS Architecture, including but not limited to those associated with:

- Airborne/theater reconnaissance architectures and systems

- National reconnaissance architectures and systems, including the Future Imagery Architecture (FIA)

- Commercial imagery architectures, services, and systems


2.0.1 Description

This requirement is for the integration and coordination of all activities described in the SOW and Projects/Programs/Activities identified in the TLD into a coherent USIGS Program. This activity includes support at the USIGS Enterprise level and at the component level for all Projects/Programs/Activities that make up the Enterprise, ensuring that an orderly and timely execution of the USIGS Evolution/ Migration Plan occurs. For the USIGS Enterprise, appropriate interfaces (interface control documents- ICDs) that ensure interoperability and standard exchange of data among the Enterprise components will be implemented. Effectivities will be managed in order to ensure that affected components of the Enterprise are treated appropriately. Within each component, the execution of individual plans to support the Enterprise evolution milestones/effectivities will be supported. This activity will be consistent with the overall NIMA Strategic Goals and Objectives and will oversee the implementation of the operational/technical/system architectures. Functional and programmatic planning guidance will be issued to external organizations and their progress against issued guidance will be monitored and statused.

Services include Configuration Management policy formulation, scheduling at the Enterprise levels, risk assessment and resolution, life-cycle verification and readiness assessment, transition planning and execution, decomposition of functional requirements into segment/component requirements and the incorporation of those requirements into individual programs and projects, and support to the RFC process (generate, review and assess, impact statements, disposition recommendation).

2.0.2 Objective and Milestones

As noted above in section 2.1.1

2.0.3 Technical Direction

As noted above in section 2.1.1

2.0.4 Deliverables

Deliverables include but are not limited to:

Interface Control Process (documentation, development, and maintenance)

Joint Requirements Documents (development and maintenance)

Effectivity Management Process (documentation development and maintenance)

Systems Integration Management Methodology (maintain/tailor current documentation)

Configuration Management Policy (maintain/tailor current documentation)

Verification and Readiness Process (Document and maintain)

Risk Management Plan (Document and maintain)

NIMA Integrated Master Schedule (maintain/tailor current documentation)

Individual Program/Project Schedules - 3rd tier WBS (maintain/tailor current documentation)

Updates to/maintenance of the Systems Engineering Management Plan (SEMP)

Updates to/maintenance of the Program Implementation Directive (PID)

USIGS migration planning documentation (development and maintenance)

Development and continued maintenance of all deliverables are expected throughout the USIGS life-cycle.

2.1 Interoperability Standards

Interoperability Standards Division (SES)

2.1.1 Description

SES is responsible for the selection, development, testing, integration, implementation support and maintenance of standards, standards profiles, specifications, interfaces, data and metadata that are part of the United States Imagery and Geospatial System (USIGS) Technical Architecture and are needed to meet NIMA customer and user requirements. SES performs these functions within the context of broader defense and intelligence architectures as well as current policies such as the primacy of suitable commercial solutions. The NIMA Standards and Interoperability Program comprises the imagery, imagery intelligence and geospatial components of the Department of Defense (DoD) and the Intelligence Communities.

Internal SES customers include the NIMA organizations responsible for systems engineering , customer support, research and technology, executive offices, and the other directorates supporting the NIMA director. External customers include the Department of Defense, the Intelligence Community, various federal agencies; and the Allied and Combined organizations approved by the National Command Authority.

SES is responsible for the management of the standards, profiles and specifications under the NIMA purview in accordance with the Defense Standardization Program and the guidelines of the Standards Coordinating Committee (SCC) of the Military Communications and Electronics Board (MCEB) and the Standards Panel (ISS-S) of the Intelligence Systems Board (ISB). SES manages its standards activities through the Imagery and Geospatial Standards Management Committee and associated technical boards. Regarding external fora, SES participates in standards activities in the Department of Defense (DoD), Intelligence Community (IC), American National Standards Institute (ANSI), Allied Nations, International Standardization Organization (ISO), and other federal and commercial organizations.

2.1.2 Objective and Milestones

Life cycle management of USIGS standards and interoperability programs.

2.1.3 Technical Requirements

a. Manage USIGS interoperability standards development

- Life cycle management

- Develop standards specifications and interfaces

b. Provide interoperability focus

- Meet JCS requirements for deployed forces

- Extend USIGS interoperability

c. Manage Standards Process

- Incorporate DoD and Intelligence Community requirements

- Chair, attend, provide representation at management and technical boards

d. Lead/influence commercial standards fora

- Primary lead for imagery, video and geospatial committees

- Key participant in areas of multimedia, data compression, etc.

e. Provide technical assistance to program offices, vendors and users

- Consult and advise on standards implementation

- Support test and evaluation infrastructure

f. Provide for configuration management of standards documentation

2.1.4 Deliverables

Technical reports as required in the conduct of the above support.

2.2 USIGS Architecture Support

Architecture Support Division (SEA)

2.2.1 Description

USIGS Architecture support activities ensure that the USIGS Architecture and it's elemental components are properly allocated and implemented in relative NIMA and USIGS programs and projects.

2.2.2 Objective and Milestones

Define and execute the enterprise level migration plan that portrays the USIGS migration from existing or current systems to future architectural targets.

2.2.3 Technical Requirements

a. Develop the USIGS Migration Plan:

- Construct system evolution diagram(s)

- Allocate requirements to programs/projects

- Build and maintain system evolution dependency schedule(s)

  1. Build and install a System Integration Management process:

- Provide enterprise and interface analyses

- Construct and maintain integrated schedules

- Perform risk assessment studies and analyses

- Support the work-off of issues and action plans

c. Provide support to USIGS Architecture integration activities:

- Lead Migration Planning Team

- Support appropriate levels of interaction through applicable architecture teams

d. Support requirements process with requirements identification and coordination.

e. Perform engineering studies and analyses:

- Conduct USIGS performance studies

- Provide migration study support

- Act as focal point for assessment of technology transfer/insertion points

2.2.4 Deliverables

Technical plans, reports and documentation as required (development and maintenance).

2.3 Systems Integration

Systems Integration Division (SEI)

2.3.1 Description

This activity manages the execution of the USIGS Migration Plan, the interface control process to include internal and external interface control documents (ICDs) and joint requirements documents (JRDs), enterprise level effectivities and their inherent milestone events, and the maintenance of the USIGS Master Schedule. In addition, systems integration provides engineering and integration support to NIMA theater activities.

2.3.2 Objective and Milestones

Provide focus for significant events that occur across the USIGS environment and to implement the plan(s) for migrating USIGS programs/projects to architectural target goals.

2.3.3 Technical Requirements

a. Provide effectivity management for the USIGS at the enterprise level:

- Devise, apply and maintain process for effectivity management

- Ensure requirements schedule and closure throughout the acquisition cycle

- Assure readiness for all transition events or milestones

- Provide integration engineering support to affected programs/projects

- Examples of effectivity items: Year 2000 impacts, E208/209..., EIS impacts, etc.

b. Build and maintain USIGS Master Schedule.

  1. Provide enterprise level oversight for integration and interface control.:

- Define interface control process for internal and external systems interfaces

- Build and maintain custom or special interface control documents (ICDs)

- Guide enterprise level program integration

d. Manage systems theater support activities:

- Integrate USIGS capabilities into theater environments

- Support Advanced Concept Technical Demonstrations (ACTDs) where NIMA systems are involved

- Provide engineering interface between theater and USIGS program baselines

2.3.4 Deliverables

Process plans, reports, technical assessments, and interface documentation as required. Government and Contractor negotiated format and content.


3.1 Program Engineering and Program Control

Program Engineering Division (MOE)

3.1.1 Description

The Management Systems Office/Program Engineering Division provides SE/SI and technical support to the Office Chief for all programs within the business unit.

3.1.3 Objective and Milestones

The Program Engineering Division's (MOE) objective is to provide requirements analysis, definition and allocation to achieve complete integration across all Management program activities. The MOE provides the leadership in establishing the vision for

integrating disparate USIGS information management components to achieve the goals to be established for Integrated Information Management (IIM) for NIMA.

3.1.3 Technical Requirements

a. Program planning, scheduling, and management support:

- Generate and execute program plans to migrate the existing MO systems into the "to-be" architecture. The contractor shall schedule the migration efforts consistent with defined NIMA effectivities and monitor the progress of the MO divisions in the satisfaction of those milestones.

- Develop and maintain the configuration management of all MO system documentation. The MO configuration management processes will be consistent with those established by NIMA.

c. MO System Documentation Development:

- Develop of MO operations concepts and requirement documentation. MO system documentation shall be consistent with the NIMA operational, systems and technical architectures. The contractor must coordinate with appropriate user groups, program offices, and other offices within NIMA throughout the development of the system documentation. The contractor shall generate appropriate RFCs to the documentation based on comments received from document reviews, interactions with users and program offices (internal and external to NIMA), as well as other staff offices within the S&T.

d. RFC Process:

- Generating, reviewing, assessing, and recommending disposition on RFCs for impact to MO plans and functionality applications and, where required, tasking and then tracking affected office review for the division. This task also requires, as necessary, contractor participation in technical exchange meetings with staff elements and program offices to resolve any issues related to the RFCs.

e. MO System Integration Activities:

- Provide support necessary to define and resolve implementation-level functional and performance requirements, interfaces and standards to facilitate the migration of multiple MO division-level systems (RMS, DPS, ESS, etc.) to an integrated, interoperable NIMA management functionality. The migration strategy must be consistent with NIMA's strategic objectives, and the operational, systems, and technical architectures while ensuring the user community no loss in functionality or performance during migration execution.

f. Manage MO and External System Integration Activities:

- Coordinate with other NIMA offices and divisions and external organizations to define and resolve functional and performance requirements, standards and interfaces to MO division-level systems. The focus of this task is to define requirements and interfaces such that NIMA customers and consumers who use various types of support systems will be capable of acquiring information from the USIGS.

- Support interactions between NIMA/MO and external organizations (e.g., other government organizations and contractors) during the execution of studies, development of architectures, and definition of external system-level documentation that impact MO programs and projects. At the conclusion of such activities, functional requirements and interface specifications will be allocated to the affected MO programs and projects, as well as external systems interfacing with MO software. RFCs to affected MO system documentation will be written as required.

g. Evaluation of System Prototypes and Demonstrations:

- Managing and evaluating MO system prototype efforts and demonstrations for consistency with NIMA's strategic objectives, operational, system, and technical architectures, and MO requirements and integration strategies.

h. Participation in Industry Consortiums

- Participate in industry consortiums to identify leading-edge commercial technology and practices applicable to MO activities. Engineering plans for integrating and/or migrating MO activities to the commercial applications and standards shall be developed and reflected as appropriate in MO documentation.

i. Communications Requirements and Capabilities Analysis

- Evaluate existing communication capabilities available to support the flow of USIGS management information and compare them to the required volumetrics to identify shortfalls. Proposed communications configurations shall be analyzed for potential mitigation of deficiencies. This tasks includes analysis of government and commercial capabilities, performance of cost benefit analysis and trade studies to determine the most effective recommendations. The results of this task shall be coordinated with appropriate government communications providers, such as JCS, NRO, DISA, and the military services.

j. Provide financial control support to include, but not limited to, budget planning, budget execution, budget guidance and policy interpretation, maintenance of a financial database, and building the Congressional Justification Book (CJB) and Congressional Budget Justification Book (CBJB).

3.1.4 Deliverables

a. RFCs to system specifications

b. TBD/TBR work-off plans

c. MO Migration Strategy

d. Conceptual Prototypes

e. Trip Reports

f. Briefings

g. Project resource and technical status report

h. MO Master Schedule (Office and Division)

i. Ad hoc technical support

3.2 Requirements Management System (RMS)

RMS Division (MOR)

3.2.1 Description

The Requirements Management System (RMS) manages intelligence requirements for the National and DoD user community in support of the USIGS. RMS enables creation, review, and approval of imagery requests; tasks requirements for collection, production, and exploitation of imagery to appropriate locations; determines satisfaction of imagery requests; can modify imagery requests based on input form other sources of intelligence and provide a suite of analytical tools for the users to exploit. The system is central to current and future integrated imagery and geospatial information management architectures supporting national, military, and civil customers.

The RMS achieved Initial Operational Capability (IOC) on 30 June 1996 with the deployment of systems and training of operators at over 80 word-wide locations. RMS is founded on IBM technology with DB2 as the mainframe operations and UNIX, SuN Solaris and Sybase in development and at all operational locations.

Development and maintenance currently requires 300+ contractors to successfully implement the spiral development of continuous improvements for the RMS. The Integrated Development and Maintenance facility (IDMF) is co-located in Reston, VA and Valley Forge, PA. The IDMF provides nominally three major software releases per year to include enhancements and fixes to problems.

3.2.2 Objective and Milestones

Maintain RMS baseline and specifications consistent with emerging and evolving NIMA and community architectures and systems. Coordinate development/enhancement content and schedules with other activities within NIMA and external organizations. Support the migration activities associated with RMS defined within the technical, operational, and system "to-be" architectures. Work all RMS SE/SI issues to maintain the RMS at a "healthy" state of operations.

Develop evolutionary strategy for use of RMS and related systems in the context of NIMA's vision and core business areas. Use the RMS to expand the roll of information provider to the user community and allow expanded users to access of data/status.

Specific to the RMS future development is the incorporation of Enhanced Imagery Systems (EIS) architecture and compliance: IOC scheduled for 3Q 1999.

Evolutionary to the RMS development are enhancements requested by the user community to include, but not limited to, the exploration of Web technology, aircraft tasking, all-source prototyping, replication services (regional fileserver concept incorporating distributed database functionality) and laptop access to the RMS in the field. All such activities not currently baseline development activities and thus subject to funding.

3.2.3 Technical Requirements

a. Define and maintain RMS segment and Interface Requirements between RMS and NIMA programs/systems including analysis of proposed changes to the existing or planned RMS baseline for potential impacts on system performance and functionality. (Request for Change - RFC generation, analysis of all segment and system RFCs, status for impact and follow-through of implementation).

b. Anomaly and Problem Report (PR) resolution for the RMS following transition of each effectivity including coordination with external affected program/segment interfaces.

c. Conduct ESRs to analyze latent RMS related performance and functionality issues with particular emphasis on achieving satisfactory inter-segment operations.

d. Participate in RMS IDMF software release management process and configuration control board activities.

e. System/segment Design and Readiness to include preparation and coordination of RMS related development readiness criteria and checklist.

f. Coordinate the Customer's readiness activities to include on-site coordination, data collection and data analysis and lessons learned development.

g. Conduct Performance Analysis to include: preparation and coordination of updates to the RMS related portions of the Critical Performance Report; review and input to the RMS contractor's performance verification plans and reports; and modeling of critical segment design threads affected by proposed changes.

h. Conduct Test and Verification to include: Review and analysis of the RVTM and its associated software management systems; Review and disposition of requirements related PRs that arise from test activities; Draft test plans (measures of effectiveness, test procedures, data collection and analysis plans, logistics and personnel support, timelines and critical milestone identification).

i. Develop study plans, CONOPS, topical and detailed requirements for enhancements/capabilities, impacted interfaces, and other NIMA or community sponsored futures.

j. Prepare and articulate proposals to a multitude of forums, as well as, conduct extensive coordination and liaison with: program sponsors; management, technical, and policy panels; support facilities; and developers.

k. Provide industry studies, analyses, and evaluations in support of policy development, decision making, management, or administration of activities for the RMS.

l. Maintain the RMS Users Manual keep current with the exiting operational baseline and integrate the User Manual into the development baseline documentation tree. Distribute the RMS User Manual to all trained and certified users.

m. Support Software Testing internal to the development/acquisition of RMS by:

- Performance evaluation of segment testing and verification

- Review and evaluate segment documentation, test plans, and procedures at the RMS IDMF as a formal test verification monitor.

- Oversee the continuing RMS IDMF software release and emergency release process.

- Monitor and assess the overall conduct and status of the testing program to include support on software release from initial development to distribution to operations.

- Oversee problem report resolution and implementation, and provide support to the site software test development and execution.

- Support Engineering Review Boards as the customer representative assessments made during RMS/IDMF testing activities and provide recommendations.

- Document findings.

n. Provide Technical Support to the IDMF by:

- On-site engineering to the activities associated with the operation of the IDMF.

- Technical engineering assistance in high-level RMS future environment planning, issue resolution, and development management, encompassing both hardware and software technology insertion into the RMS architecture.

- Technical assistance to IPTs, IC&T, and site surveys; end-to-end system assessment in support of distributed and main sites and the future evolution of the RMS software; and strategic planning to the PO for hardware and software configurations for the RMS system from commercial vendor trade studies.

o. Manage the RMS GFE/COTS process to include: tracking and purchasing of government furnished equipment (GFE) hardware, and commercial-off-the-shelf (COTS) software; operate and maintain the RMS GFE/COTS database; perform selected site surveys to verify site data; and provide up-to-date database printouts.

p. Provide Operational Support to include concept development, support to distributed sites, support for transition planning, configuration management, operations and throughput monitoring, problem assessment and resolution, hardware and software upgrade planning and execution and logistics support planning. Coordinate with all distributes sites. Understand and communicate site and command missions and plans to predict requirements. Advocate site needs and issues in alliance with the Customer Support Office and help to evaluate impacts to main site operations. Promulgate main site operations philosophy to distributed sites. Coordinate site support actions with the Help Desk, Customer Support Office, Central Imagery Tasking Office, the RMS IDMF development team and Computer Support Branches within the RMS Main site. Operational Support may also include the requirement for:

-Complete and successful system fielding at all world-wide sites

- System stability and operability

- Smooth software and hardware transitions

- Proactive life-cycle user support

- Maintenance of the RMS Operational Agreements and Responsibilities (ROARs) master document.

3.2.4 Deliverables

a. New site security and new site installation planning documentation, as required

b. RFCs, as required

c. Technical Reports, as required

d. Meeting agendas and minutes, as required

e. Action item responses, as required

3.3 Integrated Information Management (IIM)

IIM Division (MOI)

3.3.1 Description

IIM is in the concept definition phase and specific task descriptions for the out years have not yet been defined. However, for the base period of the contract, IIM will be scoped and the program plan for the FYDP developed. IIM will be a compilation of management tools which will facilitate processes and concepts to assist managers, operators, and users in optimizing the use of USIGS resources.

3.3.2 Objective and Milestones

Define the IIM program and schedule based on the allocation of functional requirements from the USIGS architecture and migration activities. Conduct independent cost analysis and identify options for implementation.

3.3.3 Technical Requirements

a. Concept development and definition to establish the framework for developing/ procuring the integrated information management component of the USIGS.

b. Develop conceptual CONOPS.

c. Requirements definition and allocation, including segment/element interfaces.

d. Establish coherent Mission Support Applications (MSAs).

e. Ensure compliance with "to-be" architecture guidance, standards, and established effectivities.

f. Coordinate MOI plans with NIMA staff offices, Program Executive Officers (PEOs), and external organizations and customers.

g. Conduct independent cost analysis for program life-cycle costs.

Provide pre-acquisition support (RFP generation, etc...).

h. Configuration management and documentation maintenance for all IIM documentation. Maintain historical record of all establishing documentation.

i. Schedule generation, monitoring and control. Ensure activities within the schedule are coordinated with all other NIMA activities and supports the architecture and migration strategy.

j. Capture, document and track action items/TBDs/TBRs and manage their work-off and closure.

k. Plan and manage the insertion of new segment/element capabilities or emerging COTS technology into the MO development program or operational baselines.

l. Manage the transition of new segment/component capabilities or COTS

technologies insertion to operations.

m. Provide technology assessment to develop strategies for technology insertion into

"mainstream" information management programs with focus on achieving a

commercial "systems" environment to the extent possible.

3.3.4 Deliverables


b. RFCs

c. Integrated Schedules

  1. Technical Reports, as required
  2. Action Item Responses
  3. Acquisition documentation

Government and Contractor negotiated format and content.


4.0.1 Description

The Archive & Dissemination Office consists of six functional divisions responsible for managing, implementing, maintaining and supporting all the functions and requirements defined in each division's area of responsibility in support of the Archive & Dissemination mission and for providing its customers with timely services to meet their needs. The Archive & Dissemination consists of the following six divisions:

Program Control Division (SDC)

Program Engineering Division (SDE)

Information Delivery Division (SDD)

Information Storage Division SDS)

Information Access Division (SDA)

Program Support Division (SDP)

4.0.2 Objective and Milestones

The Archive & Dissemination Office mission is to define, acquire, implement, and sustain the means to store and deliver imagery, imagery intelligence, and geospatial information in support of evolving and expanding customer needs and technology capabilities.

The Archive & Dissemination Office objectives are to:

a. Provide dissemination services for delivery of source information to NIMA and NIMA's customers.

b. Provide storage services for NIMA and its customer imagery, imagery intelligence and geospatial information.

c. Provide cataloging, discovery, and retrieval services for access to NIMA and its customer information.

d. Provide integration of the disparate USIGS archive and dissemination systems to ensure their conformity with the "to-be" USIGS Architecture and migration strategy/schedule, and consistency with NIMA's strategic goals and objectives.

4.1 Program Control Division (SDC)

4.1.1 Description

The Program Control division provides financial control, information management, and plans and programs support to the Archive and Dissemination Office. The financial control support provided by SDC includes budget planning, budget execution, budget guidance and policy interpretation, maintenance of a financial database, and building the Congressional Justification Book (CJB) and Congressional Budget Justification Book (CBJB). Support to the infrastructure and personnel of SD are both included under the purview of information management. Infrastructure support includes support for space allocation, computer allocation, and supplies. SDC supports personnel management by tracking billets, training, awards, promotions, evaluations and travel. Plans and program support includes preparing briefings for Program Status Reviews, and Program Management Reviews of the SD programs, and conferences, capturing minutes and action items from the monthly SD Technical Review, and serving as the point of contact for externally-generated action items.

4.1.3 Objective and Milestones

No specific milestones are associated with the Program Control Division. The schedule for the Program Control Division includes the SD Technical Review meeting, held monthly.

4.1.3 Technical Requirements

a. Program planning, scheduling, and management support for Program Control activities.

b. Attend NIMA meetings relevant to the Program Control Division.

c. Capture and document minutes and action items at each monthly SD Technical Review meeting.

d. Track and assist in the work-off of action items.

e. Provide ad hoc support the Program Control Division as required.

4.1.4 Deliverables

a. SD Management Plan

b. Minutes from each SD Technical Review

c. Action items from each SD Technical Review

d. Briefings, as required

e. Trip reports

Government and Contractor negotiated format and content.

4.2 Program Engineering Division (SDE)

4.2.1 Description

The Archive and Dissemination Office/Program Engineering Division provides SE/SI and technical support to the Office Chief for all programs within the business unit.

4.2.2 Objective and Milestones

The Program Engineering Division's objective is to provide requirements analysis, definition and allocation to achieve complete integration across all Archive & Dissemination programs and to ensure compliance with the "to-be" USIGS architecture.

4.2.3 Technical Requirements

a. Program planning, scheduling, and management support.

b. Manage SD Configuration Management Processes:

- Develop and maintain the configuration management of all SD system documentation. The SD configuration management processes will be consistent with those established by NIMA, to include configuration control boards, support committees, and maintenance of an SD configuration management library.

c. SD System Documentation Development:

- Development of SD system operations concepts and requirement documentation. SD system documentation shall be consistent with the NIMA operational, systems and technical architectures. This task requires the contractor to coordinate with appropriate user groups, program offices, and other offices within NIMA throughout the development of the system documentation. The contractor shall generate appropriate RFCs to the documentation based on comments received from document reviews and interactions with users and program offices.

d. RFC Impact:

- Review pertinent RFCs for impact to SD systems and, where required, tasking and then tracking affected program office review for the division. This task also requires, as necessary, contractor participation in technical exchange meetings with program offices to resolve any issues related to the RFCs.

e. Engineer Internal SD System Integration Activities:

- Provide system engineering support necessary to define and resolve implementation-level functional and performance requirements, interfaces and standards to facilitate migration of multiple SD division-level systems to integrated, interoperable NIMA library and dissemination systems. The migration strategy consistent with NIMA's strategic objectives, the operational, systems, and architectures while ensuring the user community no loss in

functionality or performance.

f. Engineer External SD System Integration Activities:

- Coordinate with other NIMA offices and divisions to define and resolve functional and performance requirements, standards and interfaces to SD division-level systems. The focus of this task is to define requirements and interfaces such that NIMA customers and consumers who use various types of support systems will be capable of acquiring information from the United States Imagery and Geospatial Information System (USIGS) using common discovery and access mechanisms.

- Support interactions between NIMA/SD and external organizations (e.g., other government organizations and contractors) during the execution of studies, development of architectures, and definition of external system-level documentation that impact SD systems. At the conclusion of such activities, functional requirements and interface specifications will be allocated to the affected SD systems, as well as external systems interfacing with SD systems. to affected SD system documentation will be written as required.

g. Evaluation of System Prototypes and Demonstrations:

- Evaluate SD system prototypes and demonstrations for consistency with NIMA's strategic objectives, operational, system, and technical architectures, and SD system requirements and integration strategies.

h. Participation in Industry Consortiums:

- Participate in industry consortiums to identify leading-edge commercial technology and practices applicable to SD systems. Engineering plan for integrating and/or migrating SD systems to the commercial applications and standards shall be developed and reflected as appropriate in SD system documentation.

i. Communications Requirements and Capabilities Analysis:

- Evaluate existing communication capabilities available to support the flow of NIMA information and compare them to the required volumetrics to identify shortfalls. Proposed communications configurations shall be analyzed for potential mitigation of deficiencies. This tasks includes analysis of government and commercial capabilities, performance of cost benefit analysis and trade studies to determine the most effective recommendations. The results of this task shall be coordinated with appropriate government communication providers, such as JCS, NRO, DISA, and the military services.

j. Provide ad hoc technical support as required.

4.2.4 Deliverables

a. SD Product Improvement Plan (PIP)

b. RFCs to system specifications

c. TBD/TBR work-off plans

d. Trip Reports

e. Briefings

f. Project resource and technical status report

g. Update the SD Master Schedule

h. Update the SD TEMP

i. Provide ad hoc technical reports in support of the SDE Chief.

Government and Contractor negotiated format and content.

4.3 Information Delivery Division (SDD)

4.3.1 Description

The Information Delivery Division is responsible for the following projects: The Defense Dissemination System (DDS) and the Custom Product Activity Network.

The Information Delivery Division is responsible for electronically disseminating near original-quality digital imagery in customer-specified resolution, size and/or area, and timeliness. It also is responsible for planning, developing and integrating new dissemination architectures to meet requirements for the entire range of NIMA customers from large intelligence centers to forward deployed field units.

The Defense Dissemination System Program plans, delivers, operates, and maintains systems for the dissemination of near real-time imagery and imagery products to DoD, civil agencies, and foreign customers.

The Custom Product Activity Network Program is a softcopy dissemination effort which provides users with access to the Customer Product Activity database. This database creates and maintains products of special interest or those which require special handling or compressed production timelines and cannot be supplied through normal means. This program will be assimilated by the NIMA Libraries program in TBD.

4.3.2 Objective and Milestones

Objectives as noted in section 4.3.1.

4.3.2 Technical Requirements

a. Prepare Request for Change(s) (RFCs) as necessary to modify/update Program Office (PO) documents.

- Update PO on documentation status

- Support NIMA Configuration Control Board (CCB) process

b. Provide system engineering/system integration support to the following PO tasks:

- Coordinate with other SE/SI elements to assure end-to-end system technical compatibility

- DDS systems development, integration, test fielding and sustainment

- Future dissemination and communications architecture planning/development

c. Support national effectivity testing

- Prepare detailed demonstration plans

- Coordinate plans with other relevant agencies

- Support test execution

d. Host Quarterly TRIAD Interface Working Group (ICWG) meeting

- Develop, coordinate and publish agenda

- Capture and track action items

e. Provide continuing support to the acquisition of timely statistical data relating to the DDS

f. Program planning, scheduling, and management support

g. Technical support to Installation Planning Teams responsible for the system

delivery, installation, integration, testing, and transition to operations at all new user sites. Provide site security accreditation support.

h. Technical support for the creation, coordination, and maintenance of all program documentation.

i. Technical support to interface with the SD configuration management process.

j. Capture and track SDD action items.

k. Technical support for systems integration with other programs in the SD Office, NIMA and external programs.

l. Conduct monthly status meeting.

4.3.4 Deliverables

a. Updated JRDs and/or MOUs between NIMA and external organizations

b. Status report on RFC that are in the CCB process

c. Technical reports on imagery and video archive and dissemination technologies

d. White papers and/or action item responses

e. Technical performances analyses and study reports

f. TBD/TBR workoff plans

g. Trip Reports

h Briefings

i. Project resource and technical status reports

j. Verification and testing reports.

k. Updates (RFC change pages) to requirements and interface documents.

l. Draft/Final RFC documentation

Government and Contractor negotiated format and content.

4.4 Information Storage Division (SDS)

4.4.1 Description

The Information Storage Division is responsible for the following projects: Image Product Archive (IPA), Demand Driven Direct Digital Dissemination (5D), Image Product Library (IPL) (v1.0 and v2.0), NIMA Library (to include current IDEX sites and current MC&G production locations).

The NIMA Libraries Program is chartered to plan, deliver, and operate a scaleable systems capability for the archive of imagery, imagery products, and geospatial information used by DoD components and civil agencies. It is the capstone program within NIMA/SDS and will incorporate capabilities and functionality developed both by Data Architecture and Gateway Services (DAGS) and IPL v2.0. The program began in 1993 as the Accelerated Architecture Acquisition Initiative (A3I). Upon NIMA stand-up in October, 1996, the program scope was broadened to include data and information elements commensurate with the new organization.

This effort is currently in the O&M phase. The Image Product Library program plans, delivers, and maintains a system which provides users with tools to archive, store, and retrieve imagery products to and from organizations of all levels and is scheduled to be assimilated under the NIMA Libraries program in 1QFY99. As part of the A3I program, a new system element was introduced under the Pilot A3I (PA3I). The new element was the IPA. As the PA3I system matures, the Image Product Archive will migrate to the Image Product Library. IPLs will contain shared and restricted imagery and imagery products required to support individual organizations. Each organization will determine the population of its IPLs and manage its IPLs. Most of the data stored on IPLs will be imagery products with the owner determining the mix between imagery and imagery products. The size of their IPLs, their interfacing organizations, and the products requiring storage. NIMA will provide the update IPL management software.

In addition, the program interfaces with other organizations such as the Defense Airborne Reconnaissance Office (DARO). Specific tasks include the integration of the Airborne Reconnaissance ground stations with the NIMA Library and USIGS architecture. The program involves integrating IPL into the 17+ Common Imagery Ground/Surface System (CIGSS) ground station architectures. Processed tactical imagery (still or motion) is fed to an IPL, acting as an imagery buffer, at the ground station. Stored imagery is then pulled or pushed to the exploitation workstations, exploited, then sent to the "public access" IPL for dissemination. The program also includes the identification, documentation, and inclusion of video (motion imagery) requirements into the appropriate library requirements document. In conjunction, the identification of existing and emerging video archive and dissemination technology is accomplished. Assessments are made with recommendations on the applicability and feasibility of incorporating that video technology into the NIMA Library and IPL functional baselines.

4.4.2 Objective and Milestones

Objectives as noted in section 4.4.1.

4.4.3 Technical Requirements

a. Provide program planning, scheduling, and management support.

b. Technical support to Installation Planning Teams responsible for the system delivery, installation, integration, testing, and transition to operations.

c. Attend meetings and conferences relevant to NIMA Library and IPL fielding effort.

d. Create, coordinate, and maintain program documentation:

- NIMA Library System Requirements Development.

- Video Functional and Performance Requirements Document and allocation of new requirements into the appropriate requirements document(s).

- NIMA Library-DARO Joint Requirements Document.

e. Technical support to the SDS configuration management process.

f. Plan and implement the NIMA Libraries training effort.

g. Conduct NIMA Library system performance analyses and documents.

h. Topical requirements and study reports for NIMA USIGS studies

i. Manage and track IPL fielding from initial request to completion.

j. Provide technical assistance to DARO ground station program offices' for IPL integration efforts.

k. Coordinate IPL installations and requirements with the DARO IPL integration manager.

l. Identify and document video functional and performance requirements from the user community.

m. Provide technical assistance to airborne reconnaissance program offices and users in the areas of video archive/dissemination, integration and operation.

n. Perform technical analyses on NIMA Library to CIGSS integration designs presented by program offices and coordinate analyses with the other program SIs.

o. Schedule and conduct Video Archive and Dissemination TEMs.

p. Coordinate Video archive and dissemination activities and technical matters with the Video Working Group and its other sub-working groups.

4.4.4 Deliverables

a. Updated JRDs and/or MOUs between NIMA and external organizations

b. Updated (RFCs through change pages) requirements documents

c. Technical reports on imagery and video archive and dissemination technologies

d. White papers and/or action item responses

e. Technical performance analysis and study reports

f. TBD/TBR workoff plans

g. Trip Reports

h. Briefings

i. Project resource and technical status reports

Government and Contractor negotiated format and content.

4.5 Information Access Division (SDA)

4.5.1 Description

The Information Access Division is responsible for five programs:

the Hydrographic Source Assessment System (HYSAS), the Navigation Safety

System (NSS), the Laser Airborne Bathymetry Survey System (LABS), the Client

Server Processing Environment (CSPE), and the Data Architecture and Gateway

Services (DAGS).

HYSAS is a NIMA-sponsored program whose purpose is to catalog, retrieve,

evaluate, assess, fuse, model, de-conflict, and distribute bathymetric and

hydrographic source data in support of the following agencies: NIMA, the Naval

Oceanographic Office (NAVO) and the NOAA National Geophysical Data Center

(NGDC). The mission of HYSAS is to modernize and enhance the management

and dissemination of bathymetric and hydrographic data through advanced

digital data processing techniques, and to populate the Master Sea-floor Digital

Database (MSDDB) to support product generation. Modernizing the data

handling capability provides more efficient utilization of NIMA, NAVO and

NOAA/NGDC source data to support internal product generation.

NSS is a NIMA sponsored program to replace and upgrade the functions and

capabilities of the existing heritage system operating within the Marine

Navigation Department of NIMA. The heritage system is a major Hydrographic

production system which produces the U.S. Notice to Mariners (NTM), NIMA

Navigation Publications, and U.S. Coast Guard Light Lists and supports other

NIMA production systems in the production and maintenance of hardcopy and

digital charts. The heritage system maintains other vital marine and air navigation safety

information data files and allows for remote query access into selected databases

by standard and encrypted communication devices.

LABS is envisioned as a system of commercial-off-the-shelf (COTS) based

hardware and software providing a capability for measuring depths in relatively

clear, shallow water from an airborne platform. It will process those

measurements to a quality suitable for use, and the data will be stored in the

HYSAS MSDDB. This is a joint effort between the U.S. Navy (NAVO) and


CSPE will replace the UNISYS mainframes which currently provide mapping, charting, and geodesy digital data sets and services to DoD organizations in an open systems Client Server Environment. It will be the host for re-engineered production and distribution process flows, and employ a new Digital Product Database (DPDB) that will interface with emerging and existing systems.

DAGS will provide users (NIMA and external) with timely and efficient access to global geospatial information and services. Access will be via defense, intelligence, and public networks, with a scaleable architecture to support a growing user community. Users will be able to query the NIMA holdings, as well as holdings of other agencies which are tied into the DAGS system. Users will also be able to send value-added data back to the DAGS for storage in the appropriate system.

4.5.2 Objective and Milestones

Objectives as noted in section 4.5.1.

4.5.3 Technical Requirements

a. Program planning, scheduling and management support.

b. Factory acceptance testing (FAT) and verification activity support..

c. Security architecture and accreditation support.

d. Communication architecture design and implementation support.

e. Database design (relational and object oriented) support.

f. Exercise, rehearsal activities, and site acceptance testing (SAT) support.

g. Develop and document the interface designs to existing NIMA systems.

4.5.4 Deliverables

a. Evaluation reports of communications and security architecture provided by development contractors

b. Evaluation reports of database designs provided by development contractors

c. Research reports on hardware/software being considered by development contractor in systems designs

d. Verification and testing reports

e. Participation in TEMs, program reviews as required by the Program Manager

f. Updates (RFCs thru change pages) to requirements and interface documents

g. Technical reports on imagery and video archive and dissemination technologies

h. White papers and/or action item responses.

i. Technical performances analyses and study reports

j. TBD/TBR workoff plans

k. Trip Reports

l. Briefings

m. Project resource and technical status reports

Government and Contractor negotiated format and content.

4.6 Program Support Division (SDP)

4.6.1 Description

The Program Support Division (SDP) is responsible for the following projects: IDEX, RL/RE/RDS, DPS, 5D/IPA, and Installation Planning Team (IPT) Planning Support. The objective of the Program Support Division is to provide installation, maintenance and customer support for Archive & Dissemination delivered services.

The IDEX program provides softcopy exploitation capability to 12 NIMA and DoD intelligence centers. This system allows the DoD and NIMA to satisfy critical time sensitive intelligence requirements. The capability includes imagery ingest, cataloging, display, storage, and secondary dissemination of imagery products to over 1,000 customers. The IDEX system has the ability to store and retrieve numerous images at each site. The system has nearly completed the process of evolving the originally defined custom architecture into a more open commercially based architecture.

The IDEX program is supported by on-site O&M personnel, factory personnel providing limited development and O&M labor; and the Customer Systems Support Center (Newington, Virginia) which provides O&M, configuration management, hardware and software maintenance, and a complete laboratory facility that allows alpha testing, community demonstration support, and discrepancy report work-off.

The RL/RE RDS program develops and delivers systems in support of imagery product transmission and receipt by many DoD commands. The program supports O&M, systems upgrade installation, depot, support, and system engineering.

The Image Product Archive /Image Product Library (IPA/IPL) is the migration system to replace the legacy Demand Driven Direct Digital Dissemination (5D) System.

IPA/IPL is a scaleable , modular, flexible and open system using the client/server environment and HTML technology designed to improve the accessibility and dissemination of imagery and imagery products with appropriate infrastructure, systems management and user upgrades to support the warfighter.

The IPT Planning Support Program process will provide system engineering labor in support of the entire installation process for IPL, DE, and the NIL/CIL development.

The Installation Planning Team process will monitor each contractor presentation for milestone events, factory acceptance test validation and verification, site installation planning and actual site installation and transition of major NIMA SD development programs.

This activity will include understanding the relationships and interfaces between all intelligence production systems, active participation in configuration control, security, and personnel issues, as well as supporting all major community reviews and milestone demonstrations.

4.6.2 Objective and Milestones

Objectives as noted in section 4.6.1.

4.6.3 Technical Requirements

a. Provide program planning, scheduling, and management support.

b. Briefing package preparation and support.

c. Community coordination and interface activities such as the ICWG, Demos, documentation, and standards development.

d. RFC preparation, review and tracking.

e. Program conference coordination.

f. Program requirements review and validation.

g. Support to verification working groups.

h. Program milestone schedule review.

i. Support PMR, POR, and any other softcopy events as scheduled.

j. Site visits in support of program activities such as IPTs upgrades, and future enhancements review for IDEX, CIL/NIL, IPA/IPL, and DE installation planning requirements

4.6.4 Deliverables

a. Briefing packages as required

b. Trip reports

c. Updates (RFCs thru change pages) to requirements and interface documents.

d. White papers and/or action item responses

e. Technical performances analyses and study reports

f. TBD/TBR workoff plans

Government and Contractor negotiated format and content.


5.1 Program Engineering and Program Control

5.1.1 Description

The Exploitation Systems Office/Program Engineering division provide SE/SI and technical support to the Office Chief for all programs within the business unit.

5.1.2 Objective and Milestones

The Program Engineering Division's (ESE) objective is to provide requirements analysis, definition, and allocation to achieve complete integration across all exploitation Program Activities.

- Development of an ES Configuration Management Plan - 2nd Quarter 98.

5.1.3 Technical Requirements

a. Program Planning:

- Develop program plans for ES initiatives and programs, monitor progress of programs, and develop corrective actions when programs deviate from plans. The Contractor shall define program objectives, define technical and management processes and products, estimate resources required (financial, staffing, facilities, and equipment), develop program schedules, identify risks and propose mitigation strategies, monitor program status (cost, schedule, and technical), and propose methods for program control.

b. Acquisition Support:

- Develop Acquisition Plans, Statements of Work (including attachments), proposal preparation instructions, proposal evaluation criteria, and special contractual requirements for solicitations. The Contractor shall evaluate technical, management, and cost proposals against the evaluation criteria. The Contractor will develop independent cost and schedule estimates in support of proposal evaluation. The Contractor shall provide Rough Order of Magnitude (ROM) costs for engineering efforts, hardware/software acquisitions, Requests for Change (RFC) impacts, and new programs and project initiatives.

c. System Requirements Definition:

- Work with NIMA operations and NIMA customers to develop requirements (functional, interface, performance, design, and quality assurance) for ES systems. The Contractor shall conduct the activities (e.g., modeling, simulation, and prototyping) necessary to demonstrate that the detailed requirements set is complete, consistent, achievable, and testable. The Contractor shall assess commercial technology and tailor requirements such that commercial technology can be used to the maximum extent possible - consistent with meeting mission critical requirements. The Contractor shall correct errors, incorporate missing or incomplete requirements, delete redundant or unnecessary requirements, eliminate ambiguities, ensure feasibility of implementation, ensure testability of requirements, eliminate design from the requirements statements, verify correct allocation to NIMA baseline, and conduct the analyses and modeling necessary to validate the requirements. Coordinate with the appropriate architecture organizations within NIMA to ensure ES programs and projects comply with USIGS systems, technical and operational architectures. The Contractor shall support in the identification of problems, issues, and design drivers that evolve a working knowledge of the USIGS architecture so that impacts can be assessed and evaluated.

d. Interface Control:

- Develop interface requirements and design interfaces between ES systems and between ES systems and external systems. Define the physical, electrical, communications, security, facility, environmental, and other special interface requirements between interfacing systems. Participate in interface control working groups and other forums associated with the definition and control of interfaces. Develop, asses, and coordinate RFCs as appropriate for internal/external Configuration Control Boards and aid in solving interface issues. Participate in readiness activities associated with demonstrations, tests, and implementation activities which involve external interfaces.

e. Design Evaluation:

- Conduct reviews and analyses to assess the adequacy of system, subsystem, and software and database designs. The Contractor shall predict design performance against requirements, identify risks relating to the design, and propose corrective action when the design is determined to be inadequate. The Contractor shall develop functional models, performance simulations, and prototypes in support of the analyses. The Contractor shall ensure Technical Architecture compliance with standards. The Contractor shall review ES system level documentation and other documentation across NIMA business units that could impact ES systems.

f. Specialty Engineering:

- The Contractor shall support the requirements definition and technical oversight efforts by providing expertise in the engineering disciplines of: local area networks (LAN), human factors, reliability, maintainability, availability, software, security, logistics, facilities, and training. Analyses shall be performed to identify, develop, and validate the networking, human factors, reliability, maintainability, availability, software, security, logistics, facilities, and training requirements between ES systems and external users and systems. System design, subsystem and component specifications, and software and hardware designs shall be reviewed to ensure that requirements are satisfied and that adequate design margins exist for all equipment. Test plans, procedures, and test results will be reviewed to ensure that adequate

testing is performed and that requirements are verified and validated.

g. Lift Cycle Cost Modeling:

- Develop ES system life cycle cost (LCC) models and cost analyses shall be performed. LCC models and analyses shall be used to estimate the impact of requirements changes, the introduction of new technologies, and program delays on total system cost. The LCC models shall be calibrated to reflect actual costs as cost data is accumulated. LCC modeling shall support trade studies. Life cycle costs will be considered in establishing trade study evaluation criteria and in identifying alternatives in order to minimize life cycle cost.

h. Trade Studies:

- Conduct trade studies to identify and quantify the trade-offs among risks, stated operational needs, technical requirements, program schedule and cost, supportability, and life cycle costs. The trade studies shall identify design alternatives including: reallocation of requirements, relaxation of requirements, redesign (e.g., selection of higher capacity hardware, replacement of custom components with COTS components), and procedural workarounds. The Contractor shall perform trade studies in support of make (custom) or by (COTS) decisions, to evaluate standard compliant versus non-standard components, and decisions to introduce new technology into systems.

i. Systems Integration:

- Conduct those activities to integrate new ES systems with other (new or legacy)

systems to support NIMA and NIMA customer mission requirements. The Contractor shall verify the interfaces between systems, end-to-end functionality across systems, and end-to-end performance across systems. Integration Plans will be prepared to define the scope, tasks, organizational roles and responsibilities, methods, schedule, and general procedures for the integration of systems. The Contractor shall ensure maintenance of current user functionality during transition or migration activities. The Contractor shall develop test cases, test procedures, develop (or procure) test tools, develop test databases, conduct testing, manage the test facilities (at site), document test results, and support Operational Readiness Reviews.

j. Configuration Management:

- Prepare a Configuration Management Plan for ES, and conduct and provide administrative support for a configuration management program in accordance with that plan. The configuration management program will provide for Formal Configuration Management (the control of baselines (functional and allocated) during system development; Developmental Configuration Management (control of software, data, and documents during integration with other systems); and Operational Configuration Management (control of operational systems).

5.1.4 Deliverables

a. ES Configuration Management Plan

b. Meeting Agendas

c. Meeting Minutes

d. Technical reports

e. Program Plans

f. Acquisition Plans

g. Statements of Work

h. Rough Order of Magnitude (ROM)

i. System/Segment Specifications

j. specification Change documents

k. Interface Control Documents (ICD)

l. Interface Requirements specifications

m. Interface Design Specifications

n. Requests for Change (RFC)

o. study Plans

p. Integration Plans

q. Test Procedures

r. Test Reports

s. ES Master Schedule

t. ES Management Plan

Government and Contractor negotiated format and content.

5.2 Digital to Plate System and Scan Systems (DTP)

Extraction & Finishing Division (ESF)

5.2.1 Description

The two major initiatives included under this activity are the Repromat Scanning Initiative (RSI) and the DTP Initiative.

The RSI addresses the needs associated with converting the reproduction material (usually film) used during the printing process to a digital format. Under this initiative, contracts were established with scan contractors, scanners and workstations were procured and integrated, a system was established to prepare the repromat for the scan area, and a system was established to review the completed scan data for quality control. Coordination efforts were initiated with other programs such as Vector Product Format (VPF).

The DTP Initiative was closely coordinated with the RSI, since the data created from the scan process would be used in the new DTP system. The DTP initiative involved a market study of the technology to generate plates directly form digital raster files. An existing contract provides for internal integration, i.e. integration of the raster manipulation software provided by DALIM at the front-end with a Krause image setter at the back-end. The contract does not provide for integration with other NIMA programs.

5.2.2 Objective and Milestones

DTP will be delivered in phased installations as indicated below:

Phase 1 - Initial hardware delivery and integration (St. Louis, Bldg. 36 & 37)

Phase 2 - Additional hardware (including 63" press) delivered and integrated at CPDF

Phase 3 - Initial hardware moved to CPDF and integrated

The Voyager software and server were acquired in October 1996 and the software loaded onto the server in November 1996. Primary focus now is on outfitting the NIMA Research Division (ISL) staff with Pentium workstations to access the Voyager system. Initial load of the database with unclassified test metadata should have been completed by Spring 1997. Additional databases will be migrated to Voyager in a phased approach as resources permit. Anyone with a web browser and connectivity to the appropriate network will be able to search the NIMA Research Division holdings.

It is anticipated that eventually all the collections currently maintained by the ISL staff will be available to the NIMA community via the Voyager system, including books, maps, charts, documents, serials, videotapes, ground photos, film, repromat, CD-ROMS, etc. These collections are largely maintained at the four primary NIMA sites

5.2.3 Technical Requirements

a. Perform analysis of problems and/or candidate solutions, using commercially available equipment, software and standards-based open architecture whenever possible.

b. Perform and conduct studies and analysis that results in the selection of a solution

to meet the specified constraints of results of studies and analysis.

5.2.4 Deliverables

a. Technical Report-Study/Services-Study Proposal

b. Technical Report-Study/Services-Ad hoc Technical Report

c. Technical Report-Study/Services-Prototyping

d. Technical Report-Study/Services-Modeling & Simulation

e. Technical Report-Study/Services-Analysis

f. Computer Software Product End Items

g. Requirements Databases & Database Tools

h. Traceability Matrix and Tables

i. Controlled Documentation updates.

Government and Contractor negotiated format and content.

5.3 Enhanced Imagery System (EIS)

Source Management Division (ESM) St. Louis

5.3.1 Description

The Enhanced Imaging System (EIS) will represent the next generation of raw source material for exploitation within the USIGS Architecture, NIMA and NIMA's external customers. EIS consists of two effectivities, E-300 and E-305, that will provide new capabilities to the USIGS. USIGS must be capable of tasking, processing, archiving, disseminating, and exploiting EIS data. Many aspects of E-300 and E-305 will impact NIMA USIGS systems and programs which must be carefully assessed for proper integration throughout its entire life-cycle.

5.3.2 Objective and Milestones

Data format changes (E-300-Enhanced Collection System (ECS)) and new capabilities (E-305-new radar capability) will result from these two effectivities. NIMA must insure that the imagery, imagery intelligence, and geospatial production systems incorporate the required interface changes to assure minimum impact to its imagery, imagery intelligence, and geospatial production capability and associated external customer systems.

Critical Design Review February 1998

Monthly Program Reviews every 4 to 6 weeks.

5.3.3 Technical Requirements

a. Technical and programmatic integration support of EIS into USIGS including support for the evolving evolving electronic and operational EIS interfaces.

b. Support the development of EIS system-level Operational Concepts, interfaces definition, requirements definition, and identify EIS impacts (allocation and nature of impact) on DPS, DPS Migration and other USIGS production systems and other USIGS migration concepts.

c. Support EIS pre-development activity support to the EIS program manager; provide insight on source program issues for EIS; understand and convey essential changes required for successful incorporation of EIS into USIGS; understand DPS and impacts of EIS on each DPS segments and system-level DPS; and then, incorporate engineering solutions and recommendations into the draft EIS RFC and other per-development documentation.

d. Support at source program meetings (MC&G requirements Working Group (MRWG); support includes capturing essential issues to NIMA and the EIS program manager, and providing engineering and technical solutions to action items/issues/ Meetings are expected to occur every 4-6 weeks in Valley Forge, PA, and Northern Virginia and FPE TEMs in San Diego, CA for FAT/SAT and SLV.

e. Monitor EIS requirements at the program level to ensure USIGS integrates system requirements as required.

f. Flow EIS program-level requirements down to the applicable USIGS documents via Request for Change (RFC) documentation.

g. Incorporate redlines as requested by the Government in preparation for boarding at the appropriate NIMA Configuration Control Board(s).

h. Monitor EIS requirement growth/changes on the source side to ensure requirements are flowed into the applicable USIGS documents.

5.3.4 Deliverables

a. Technical Reports Study/Services Analysis, as necessary

b. Monthly Status Report, end of each month

c. Requests for Changes (RFCs), as necessary

d. Meeting Agendas

e. Meeting Minutes

f. Briefings, as necessary

Government and Contractor negotiated format and content.

5.4 Standard Automated Material Management System (SAMMS)

Distribution Standard System (DSS)

Extraction & Finishing Division (ESF)

5.4.1 Description

The SAMM/DSS provides NIMA with the capability for requisition processing, forecasting, on-line ordering, inventory management, receiving, storage, transportation and workload planning. All these functions are related to the management, storage and distribution of NIMA standard MC&G hard copy products. The SAMMS/DSS converts NIMA data distribution services to that of the standard logistics systems of the Defense Logistics Agency (DLA).

5.4.2 Objective and Milestones

Provide the necessary system modifications to the Standard Automated Materiel Management System (SAMMS) and the Distribution Standard System (DSS) to enable the Defense Logistics Agency (DLA) to manage the inventory and distribution of NIMA hard-copy products.

5.4.3 Technical Requirements

a. Provide analysis of DLA's System Change Requests and proposed design of the

SAMMS and DSS systems, as compared to NIMA's distribution requirements.

b. Review interface requirements between NIMA (to include NIMA services contractors) and DLA to assess impact on systems design.

c. Represent NIMA technical interests at joint community forums, working groups, and Technical Exchange Meetings.

d. Provide analytical review of test, conversion, and training plans.

e. Act as consultant during systems testing; participate in functional and environmental testing.

f. Provide analysis of test results for functional and environmental tests, to include a list of deficiencies/discrepancies/problems.

g. Identify disconnects in systems design for input into future increments of systems development.

5.4.4 Deliverables

Technical Progress Report - Analysis and Studies. Reports are on as-needed basis. Formal reports required two weeks after the conclusion of each of the following two test periods: Functional Test and Environmental Test.

a. Government and Contractor negotiated content and format.

b. Deliverables Schedule: See above. Deliverables must be tied to milestones rather than specific dates. Milestones are TBD

5.4.5 Travel

Continuous. On-site at NIMA, Bethesda or DLA headquarters, Ft. Belvoir -- with travel to SAMMS site in Columbus OH, to DSS sites in Ogden UT and New Cumberland PA, and to the SAMMS/DSS functional site in Richmond VA, as needed.

Jan-Jul '98: four 5-day trips to Columbus

three 5-day trips to Ogden

seven 2-day trips to the Washington D.C. area

seven 5-day trips to the Washington D.C. area

Aug-Dec '98: ten 5-day trips to Richmond

five 5-day trips to the Washington D.C. area

Jan-Mar '99: three 5-day trips to Richmond

six 3-day trips to the Washington D.C. area

5.5 Synthetic Aperture Radar (SAR) Production Initiative

5.5.1 Description

The Synthetic Aperture Radar (SAR) development program represents an effort to generate mapping and terrain data products in high-priority areas where NIMA has been unable to previously satisfy requirements. Because radar wavelengths penetrate cloud cover, SAR can generate imagery in the tropical cloud-belt, where optical sensors have a poor history of successful collection. NIMA is currently managing a SAR program to develop an in-house processing capability to ingest, orthorectify and mosaic SAR images. These image mosaics serve as an extraction base for cartographic workstations that produce geospatial products. The production capability will include such items as: targeting products, control points, digital elevation data, image maps, TLMs, GIP/GAPs, fly-thrus, and city graphics. The SAR program also manages research initiatives related to SAR feature and terrain extraction capabilities.

5.5.2 Objective and Milestones

The R&D initiatives related to SAR imagery and other sensors will directly support the improvement of NIMA's mapping and targeting program.

SAR Terrain Test:

Imagery Collection, Oct97- Dec-97

Terrain Extraction, Jan 98-Apr98

Analysis, May98-Aug98

Report Generation, Oct 98

SAR Targeting Evaluation: Oct97-Jan 98

SAR Mensuration Evaluation: Feb98-Apr98

CONOPS Development: Oct97-Jan98

5.5.3 Technical Requirements

a. Provide assistance in the development of the pertinent production con-ops

b. Provide requirements development and analysis to support the establishment of a SAR production system

c. Provide support to TEMs and analyses as necessary.

5.5.4 Deliverables

Reports, briefing packages, and con-ops will be required as necessary. Government and Contractor negotiated content and format.

5.6 Interferometric Synthetic Aperture Radar (IFSAR)

5.6.1 Description

The Interferometric Synthetic Aperture Radar (IFSAR) program represents an effort to ingest and process high-resolution elevation data produced through a technique called radar interferometry. The main source of these data will be the Shuttle Radar Topography Mission (SRTM), which is an IFSAR mission to be flown aboard the Space Shuttle in September 1999. The SRTM will image 80% of the Earth's land surface and will produce approximately 14,300 Cells (1 degree by 1 degree) of terrain height data. This data will provide NIMA with the means to meet the standing requirement to provide Level 2 DTED to its external customers.

5.6.2 Objective and Milestones

The IFSAR program within NIMA is investigating characteristics of IFSAR elevation data along with methodologies for on-site validation and processing of raw terrain elevation data.

This effort should result in a NIMA production capability to process IFSAR and develop data sets that satisfy improved user requirements and provide worldwide DTED coverage.

CONOPS complete: 31 Dec 97

Systems Requirements Documents complete: 1 Feb 98

Statement of Work/Production Package complete: 1 Jun 98

IFSAR Production System Delivery: May 99

Installation, Checkout & Test : Jul 99

5.6.3 Technical Requirements

a. Provide oversight of NASA/JPL during the development of the SRTM payload and during NASA flight operations of the SRTM.

b. Support TECH in the direction of DARPA sponsored IFSAR contracts to ERIM and Norden systems.

c. Assist the IFSAR development community in creating the capability to produce USIGS data with improved absolute and relative accuracy. The process should result in a USIGS production capability to process IFSAR and develop data sets that satisfy improved user requirements.

d. Develop Operational Concept for process IFSAR.

e. Develop ground truth data sets to evaluate prototype and production quality collected data.

f. Evaluate IFSAR data for conformance to desired accuracy and completeness, acquire IFSAR production capability, and implement production of IFSAR data.

5.6.4 Deliverables

a. Acquisition documents

b. Test Plans and Procedures


d. System Requirements Documents

e. Transition Plans

f. Technical Reports

Government and Contractor negotiated content and format.

5.7 Aeronautical Migration Systems (AMS)

Extraction and Finishing Division (ESF) St. Louis

5.7.1 Description

The Aeronautical Migration Systems (AMS) project is being implemented by the NIMA Systems and Technology Directorate (S&T), in conjunction with other NIMA components, to reduce the hardware, software, operations and maintenance costs associated with current production operations while increasing the quality of aeronautical products.

5.7.2 Objective and Milestones

The objective of the AMS project are to migrate the aeronautical data storage, data maintenance and product finishing functionalities from existing digital platforms and hardcopy maintenance applications. This effort will take advantage of existing technology improvements associated with state-of-the-art automated capabilities using a client/server architecture to increase efficiency and enhance functional performance. This effort will also provide the foundation for and fully support current and follow-on NIMA activities to establish a NIMA digital warehouse (Data Architecture Gateway Services (DAGS)). The NIMA digital warehouse will provide users the capability to query and extract digital aeronautical products and product information (metadata).

The AMS program will continue development on future phases of aeronautical migration through calendar year 1998. The migration of the Flight Information Publication (FLIP) is a significant milestone during this performance period. The FLIP Text Products have a system delivery milestone of March 1998 and the initial phase of FLIP Graphics migration should occur in October 1998.

AMS will continue use of Object Databases for the application of graphics from a Relational Database.

5.7.3 Technical Requirements

a. Configuration management for source code and engineering activities and Interface Control Document (ICD) support.

b. Schedule development and maintenance assistance.

c. Unit, integrated, and operational testing assistance.

d. Visual Basic, MapInfo, and Sybase technical assistance.

e. Metrics support, specifically in the use of the McCabe tool.

f. SGML, DTD, and Database Publishing technical assistance for the Desktop Publishing needs of AMS Phase II (Test Aeronautical Data System - TADS).

g. Perform industry study to evaluate graphic publishing software/methodologies.

h. Perform industry study to evaluate Object Database Technology and its implication to relational graphic generation.

i. NSES resources will be required to support maintenance and sustainment of the AMS (five systems) baseline in the out years. Configuration management, regression testing, software libraries maintenance, software delivery Scheduling.

j. Support interfaces with DIA and other federal/commercial entities are anticipated.

5.7.4 Deliverables

a. Engineering Reports

b. RFCs

c. Engineering Studies

d. Project plans and schedules

e. Interface Control documents and Specifications

Government and Contractor negotiated content and format.

5.8 Data Extraction Segment (DE/S)

Extraction & Finishing Division (ESF)

5.8.1 Description

The Data Extraction Segment (DE/S) is a VAX-based production segment of the NIMA DPS providing NIMA customers with productivity enhancements and crisis support improvements to the DPS. DE/S populates the MC&G database in support of the generation of soft and hardcopy products to support a crisis environment. DE/S is comprised of custom stereo work stations, grouped in clusters of eight for digital data extraction. DE/S provides the capability to extract terrain and feature data from digital stereo imagery, to attribute the extracted data with MC&G significant information, to edit, manipulate, and merge newly extracted data with existing MC&G data, and to perform quality checks to ensure that the extraction process has conformed to specifications. DE/S populates the MC&G Data Base with the terrain and feature data captured during stereo extraction.

5.8.2 Objective and Milestones

DE/S is planned to upgrade to an Alpha based platform in the 1997 to 1998 time frame to significantly improve the throughput time of the data extraction process. The functionality in DE/s does not currently exist in COTS applications. The Alpha upgrade is seen as a first step toward migrating to the future and out of the DPS environment. Additional studies will be necessary to determine other parts of the SDS/S which are/will be obsolete and could potentially be replaced by COTS products.

Complete the planned phased approach: May 97 - Sept 98

Phase 1 - Development of mini-DE/S: Many/Jul 97 - Dec 97/Feb98

Phase 2 - Development/integration of Alpha to DSE: Jan 97 - May/Jul 98

Phase 3 - Complete upgrade option: Feb/Apr98 - Sep/Nov 98

5.8.3 Technical Requirements

a. Analysis of segment throughput (pre-processing, extraction, global edit, post a. processing) once upgraded to the Alpha platform.

b. Investigation of the next logical step towards a COTS replacement for DE/S:

- Independent studies/monitoring of the state of commercially available software packages to replace existing application software maintained on the segment.

- Independent studies to investigate the state of commercially available hardware to replace obsolete and or old technology to state-of-the-art equipment on the segment.

c. Independent studies for improvements to the overall DE segment to include alternative approaches for interfacing to the DPS baseline.

d. Periodic review of DRs and enhancements to conduct trend analysis

e. Assistance with review of RFCs and ECPs and/or other initiatives which affect or could be affected by the segment (FPE, EIS, DCAFE, Y2K, etc.)

f. Verification of the Data Extraction Segment and DCAFE interface requirements.

Many extraction requirements were levied on DE/S due to the Product Generation Segments finishing requirements. Some requirements could be "OBE" with the onset of DCAFE. Findings could result in process improvements in the extraction process.

g. Technical support must have a thorough understanding of the segments technical and functional requirements as well as DPS interface requirements as related to the segment.

5.8.4 Deliverables

a. Technical reports/studies

b. Independent studies

c. Trend Analysis

d. Meeting Agendas

e. Meeting Minutes

f. RFCs

g. Engineering Change Proposals

h. Test Plans and Procedures.

Government and Contractor negotiated content and format.


Geospatial & Exploitation Tools Division (EST)

5.9.1 Description

The Ruler project is creating a portable mensuration application that can be used to support both hardcopy and softcopy mensuration. As a hardcopy tool, Ruler will replace the existing Precision Mensuration System (PMS) and the Light Table Mensuration System (LTMS). To support softcopy mensuration, a Ruler Public Interface Specification has been created to allow softcopy exploitation systems to access Ruler mensuration capabilities through a well-defined Application Programming Interface (API). Ruler provides mensuration support for the current national sensors and their associated imagery formats. Because of its ability to support both hardcopy and softcopy mensuration, Ruler is the mensuration software standard product for the Intelligence Community.

Ruler 3.0 was released on 7 February 1996 to approximately 56 sites for use as a hardcopy exploitation tool. An additional 18 government organizations have contracted with commercial vendors developing softcopy exploitation tools to access Ruler as a mensuration service via the Ruler Public Interface Specification.

5.9.2 Objective and Milestones

Completed Ruler 7.0 Master Schedule: 28 Feb98

Completed Ruler 8.0 Master Schedule: 28 Oct 98

5.9.3 Technical Requirements

a. Implement the Ruler configuration management plan (as described in the Ruler Project Plan) that will support both operations and maintenance, and development of Ruler. Configuration management tasks will include, at a minimum, the following tasks:

- Source Code Control:

Monitor, track, and coordinate the disposition of Ruler source code. NIMA has chosen Aide-De-Camp as the source code control system for Ruler. The contractor shall use Aid-De-Camp to automate both the control of source code as well as the generation of the Ruler application.

- Problem Tracking:

Monitor, track, and coordinate the disposition of Ruler RFCs (Requests For Change) and PRs (Problem Reports). NIMA has chosen DDTS (Distributed Defense Tracking System) as the problem tracking application for Ruler. The contractor shall use DDTS to automate the ingest and tracking of RFCs and PRs.

b. Quality Assurance/Testing:

- Develop and implement test procedures for Ruler. Test procedures will be based upon test plans developed by the programming staff as part of the design of each component task and integrate new test procedures into existing test documentation. NIMA has chosen Xrunner as its automated testing tool. Transition existing test procedures into Xrunner scripts. Support the Integration and Test phase of development prior to the shipment of the application.

c. User's Groups:

- Provide organizational and administrative support for both the Ruler's User Group and the Ruler Developers Conference. These working groups shall be held twice a year. Tasks associated with this effort shall include, at a minimum, the following:

Notification of participants

Generation of Agendas

Site coordination

Action Item generation and tracking

Generation and distribution of minutes

d. Ruler Master Schedule:

- The master schedule will be a combination of schedules for deliveries through Ruler 9.0 (November 1999). NIMA has chosen Digital Tool's AutoPLAN II as the program management application for Ruler. The contractor will be responsible for updating this schedule with respect to project status meetings and related community schedules.

  1. RFC/PR Coordination:

- Generate, track, monitor, and coordinate Ruler related RFCs and PRs. Coordinate with community boards with respect to impacts on the Ruler project.

e. Community Support:

- Support the Program Office at community meetings. Track Ruler related action items, and coordinate their eventual work-off. Support and coordinate the releases of the Ruler application. Develop an unclassified database of Ruler users. Information to be included in this database shall include, at a minimum, the following information:

User profile

Ruler version now running

Point of Contact (POC)

Phone number

User list

Installed platform description

f. Providing direct support to Ruler users through problem reporting, problem work- off status, customer support and help-desk operations.

g. Coordinate and conduct the Metric Accuracy Working Group (MAWG), quarterly.

5.9.4 Deliverables

a. MAWG Agendas

b. MAWG Minutes

c. RFC Status Reports, monthly

d. PR Status Report, monthly

e. Ruler Master Schedules

Government and Contractor negotiated content and format.


Exploitation Support Systems Division (ESS)

5.10.1 Description

The National Exploitation System (NES) is the next-generation imagery exploitation management and reporting system replacement for the Aires Life Extension (ALE) and the NPIC Data System (NDS). ALE and NDS will migrate into this single system. NES will support a collaborative community exploitation environment, providing products to consumers in a timely manner in an appropriate format, and support a variety of organizations and ways of doing business. It will also be an interim migration system for the Exploitation Support System (ESS).

5.10.2 Objective and Milestones

NIMA Navy Yard components of the Exploitation Systems Office (ES) and Corporate Networks (CN) are responsible for developing and integrating new capabilities into the NES and supporting infrastructure; providing system planning and engineering support for modifications to existing systems (hardware, software, and data bases); performing trade studies on commercial off-the-shelf (COTS) hardware and software products; providing communications engineering support to internal and external systems; and providing technical support to special projects. A major focus is to ensure that development, commercial-off-the-shelf (COTS) products and operational components of the former NPIC Information Systems (NIS) are integrated into the NIMA planned operating environment. ES and CN are supported by configuration management, hardware and software transition activities, ADP security policy, readiness activities associated with hardware/software deliveries and installation.

System Testing: Apr 98-Aug 99

5.10.3 Technical Requirements

The contractor shall support such activities as; acquisition planning, requirements definition, readiness, transition planning, engineering change review, requirements (including interface requirements) definition and allocation, demonstration coordination, configuration management activities (preparing and tracking RFCs, impacting RFCs, attending CCBs), project management and schedule support, user review support, and support to TEMs.

5.10.4 Deliverables

a. Interface Control Documents (ICDs) and specifications

b. Meeting agendas and minutes

c. RFCs

d. Technical Reports

e. Engineering Change Proposals (ECPs)

f. Acquisition Documentation

  1. Briefings
  2. Transition Plans

Government and Contractor negotiated content and format.


Exploitation Support Systems Division (ESS)

5.11.1 Description

The Front-End Processing Environment allows NIMA to use a variety of commercial, DoD, and intelligence sources as production sources of digital imagery within the DPS for terrain, elevation, feature, and attribute data extraction. The FPE provides the capability to convert alternate sources of imagery and support data to a data structure that DPS can support. The FPE hardware and software suite will be the same at each NIMA production site, but the volume and type of alternate sources will vary dependent upon the production load at each center.

5.11.2 Objective and Milestones

Site Acceptance Testing: May 97 - May 98

First site ready for use: Nov 97

5.11.3 Technical Requirements

a. Provide requirements development, traceability and analysis to support the Alternate Source Exploitation initiative.

b. Provide expertise to review hardware and software designs to ensure compatibility and conformance to requirements and the latest standards.

c. Provide support to the test and verification of the Alternate Source Exploitation which will include stand alone, factory, and site testing of the USIGS production segments changes and the testing of the FPE requirements.

5.11.4 Deliverables

a. Technical Reports, as necessary

b. Monthly Status Report, end of each month

c. Integrated Program Schedule, updated monthly at the end of each month

d. Requests for Change (RFC), as necessary

Government and Contractor negotiated content and format.

5.12 Exploitation Support System (ESS)

Exploitation Support Systems Division (ESS)

5.12.1 Description

The Exploitation Support System (ESS) will ensure the continued migration of exploitation support capabilities recommended in the Exploitation Process Re-engineering Study (ExPRes). ESS will support all national, theater, and tactical imagery exploitation units of the intelligence and geospatial imagery exploitation units of the intelligence and geospatial community.

5.12.2 Objective and Milestones

The ESS development will migrate existing imagery exploitation capabilities into a single system with the technical and business process enhancements required to meet future imagery exploitation needs. The development of ESS is consistent with the national vision and with NIMA's strategic direction to rapidly migrate legacy imagery intelligence and geospatial information systems into a common, open, interoperable architecture based on commercial technology. This approach, based on extensive study with active community participation, will implement recommendations of the ExPRes to promote cross-community integrated management, timely access to information, creation of an interoperable environment, enhanced collaboration of software tools that will operate within the existing site infrastructure, will provide functionality to process imagery information needs, support selection of imagery and data for exploitation, manage image dissemination, manage exploitation. and support exploitation and reporting. The ESS development contract is expected to be awarded mid-1998 with completion by 2002-2003.

5.12.3 Technical Requirements

The contractor shall support such activities as; acquisition planning, requirements definition, readiness, transition planning, engineering change review, requirements (including interface requirements) definition and allocation, demonstration coordination, configuration management activities (preparing and tracking RFCs, impacting RFCs, attending CCBs), project management and schedule support, user review support, and support to TEMs,.

5.12.4 Deliverables

a. Interface Control Documents (ICDs) and specifications

b. Meeting agendas and minutes

c. RFCs

d. Technical Reports

e. Engineering Change Proposals (ECPs)

f. Acquisition and Acquisition Support Documentation

g. Briefings

h. Program Planning Documentation

i. Engineering and Technical Evaluation Reports

j. Configuration Management Documentation.

Government and Contractor negotiated content and format.

5.13 Multi-Source Intelligence Tools (MINT)

Geospatial & Exploitation Tools (EST)

5.13.1 Description

The Multi-Source Intelligence Tools (MINT) is a development and integration activity that provides for an open, distributed, object oriented architecture with documented interfaces to MINT compatible services. The MINT program will encapsulate and reuse modules, components, and algorithms developed by the legacy MATRIX and MET programs and will integrate these objects into the MINT services in such a manner so as to be compliant with the specified MINT open architecture. The MINT program shall utilize services available from COTS suppliers, from existing Government assets, or from other Government contractors.

5.13.2 Objective and Milestones

To complete MINT integration by 30 September 1998.

5.13.3 Technical Requirements

The contractor shall provide technical analysis, review of software architecture, review of software design and code, requirements specification on interface and definition of tools, support test evaluations and certification of tools development and deployment.

5.13.4 Deliverables

a. Analysis briefings

b. Reports as required

Government and Contractor negotiated content and format.


NIMA Softcopy Division (ESC)

5.14.1 Description

The NIMA Softcopy program provides a softcopy exploitation capability for NIMA and Community imagery and geospatial analysts, including IDEX workstation replacement and additional workstations for approximately 2500 analysts at worldwide sites. NIMA Softcopy provides a complete softcopy system that includes a fiber optic ATM network, a storage system capable of retaining two years of imagery on line for NIMA analysis to access efficiently, and a fully integrated imagery data management system that combines the information of the NDS and the softcopy system on one or two terminals for imagery analysis and intelligence production.

5.14.2 Objective and Milestones

Procure, design, integrate, and deliver softcopy exploitation capability to NIMA imagery analysts and geospatial information analysts and to imagery analysts at 26 sites world-wide. The NIMA Softcopy development contract is expected to be awarded mid-1998 with completion by 2002-2003.

5.14.3 Technical Requirements

As integrated members Softcopy Program Office, the Contractor shall assist the Government with systems engineering and integration functions such as but not limited to; pre-acquisition, requirements definition, readiness, transition, RFCs, external interface requirements, system demonstrations, configuration management, and program and project scheduling.

5.14.4 Deliverables

Technical/engineering reports, RFCs, and white papers as assigned.

Government and Contractor negotiated format and content.

5.15 Data Capture and Finishing Environment(DCAFE)/Vector Product Format (VPF)

Extraction & Finishing Division (ESF)

5.15.1 Description

The Data Capture and Finishing Environment (DCAFE) provides customers with primarily COTS based GGI&S data capture and finishing systems. It will use the PG/S R&D contract to upgrade existing software and integrate UNIX software to a Windows-NT environment. The functions of seven aging hardware and software systems will be combined into one DCAFE system.

The Vector Product Format (VPF) program provides a standard format representation of vector features to NIMA customers for data interoperability. VPF provides NIMA with an end-to-end production capability to produce vector products on 114 UNIX-based workstations. Vector products are comprised of a suite of digital products that conform to the specifications of the VPF Military Standard. These products are designed to support Geographic Information System Applications. The VPF uses both hardcopy graphic and digital sources. The data is revised and converted to the VPF. A pre-mastering tape is generated that can be used to master a final VPF product on Compact Disc-Read only Memory (CD-ROM).

5.15.2 Objective and Milestones

a. Effectivity 8.1 is currently in development with Pre-Ship Review (PSR) 20 October 1997. Production start date is 16 January 1998.

- Interface to MC&G DB (interactive) and HYSAS

VPF product finishing

FE/S data input - direct

DTED finishing (COTS)

DE/S tape input

b. Effectivity 8.2 currently in development with PSR 15 April 1998. Production start date is 26 June 1998.

- Refined MC&G DB interface (auto seg/gen)

Interface with CSPE, FPE, and NSS

Names processing

c. Effectivity 9.1 is currently TBD

5.15.3 Technical Requirements

The SE/SI support required will include such functions as studies and analysis, requirements definition, analysis, allocation and documentation, system factory test verification and validation, risk management, quality assurance, etc. Specifically, SE/SI support is required for the following areas:

a. VPF Production System

- Implementation of VPF product update capability and a production database

for the storage of production data and for maintenance of updates.

- Provide enhancements to the Interactive Compilation System Upgrade (ICSU), and Revision Segment (R/S).

- Modify baseline system documentation to reflect the removal of VPF/PS

functionality and hardware from the system baseline associated with the production turnover of DCAFE effectivities.


- Develop and implement E8.1, E8.2, and E9.1 production functionality.

- Workoff of E8.1, E8.2, and E9.1 TBD requirements for interfaces, products,

and functionality.

- Add object environment heads-down digitizing functionality.

- Add interface to Remote Replication System (RRS).

- Add interface to Digital to Plate (DTP) system.

- Establish and update hardware and software CIIs for each effectivity.

- Acquisition support (COTS market analysis and technical evaluation)

for hardware and software to expand system capacity.

- Addition of database management system to support VPF data maintenance.

c. Product Generation Segment (PG/S)

- Modify baseline system documentation to reflect the removal of PG/S

functionality and hardware from the DPS baseline.

d. DCAFE Re-Engineering

- Evaluation of candidate replacement systems to meet existing and evolving

new requirements for DCAFE.

5.15.4 Deliverables

Conference agendas and minutes - as directed

Monthly Progress & Status Report - end of each month

RFCs- as required

Integrated program/planning schedule - update monthly and provide at the end of

each month

Technical report - Study/Services - Ad hoc Technical Report - as directed

Requirements Databases & Database Tools

Traceability Matrix and tables - as directed

Documentation updates - as directed

Government and Contractor negotiated format and content.

5.16 Source Analysis

Source Analysis Division (ESM)

5.16.1 Description

As noted in section 5.16.3.

  1. Objective and Milestones

As noted in section 5.16.3.

5.16.3 Technical Direction

Support Source Analysis, Community imagery Needs Forecast modeling, and source Usage, and provide impact assessments to the of joint requirement changes upon USIGS.

a. Provide and maintain the community historical collection information for NIMA and the community. Provide and maintain CINF shelf deck resources. Using community standard Proteus, STATSIM, MAXBOX, and Turbo Isis software tools, and the unique 10-year historical collection requirements information and profiles.

b. Collect, analyze and report on NIMA source acquisition to include collection monitoring, trend analysis, tasking and NIMA production implications, assessment of system operations, replenishment planning and NIRC support data generation, ad hoc projection of source availability, production program, source acquisition synchronization, PAP status reporting, and periodic management overview briefings.

c. Collect, analyze, and report production data related to system operations, and acquisition of global source inventory.

d. Assess impacts of source Program initiatives which relate to NIMA production and source program acquisition/production.

e. Develop and provide initial population for a geographic tasking information engineering database in support of Agency imagery requirement planning and tasking. This database shall be compatible and interoperable with the database used by the Intelligence Community for tasking and tracking.

f. Perform analysis in support of near-term and long-term program source requirements definition to include CINF conceptualization and development, construction and delivery of Geospatial Information, , MC&G and database component, and study s-specific simulation database requirements.

g. Prepare and deliver analysis results via briefings, report and/or RFC.

5.16.4 Deliverables

a. CINF Analysis Reports - Four times per year, and as required

b. CINF MC&G Input - Four times per year, and as required

c. Briefings as required

d. Conference Minutes as required

e. Analysis reports as required

Government and Contractor negotiated format and content.

5.17 Exploitation Initiative (EI) Tools

Geospatial & Exploitation Tools Division (EST)

5.17.1 Description

The EI Tools is an effort to identify, procure, and distribute selected exploitation tools to augment NIMA and community exploitation capabilities. This activity includes both imagery intelligence and geospatial tools.

The EI Tools Project Plan for FY98-03 is being prepared in FY97 and will serve as the basis for FY98-03 planning and execution efforts. Candidate Tool identification will focus upon recommendations stemming from the Pathfinder process in coordination with exploitation sites throughout the community. Additional tool nominations may be accepted, as appropriate.

5.17.2 Objectives and Milestones

The objective of the FY98 support is two-fold:

a. Planning and execution phase of the FY98 procurement efforts

b. Planning for the FY99 procurement efforts

FY98 Milestones include:

FY98 Program Planning and Execution

Completion of site coordination for tool nominations (recurring milestones as sites come on line); first completion by 1 February 98

Completion of all interagency agreements associated with final site/tool selections, including appropriate CM and CCB support (recurring milestones as sites come on line, but first site completed by 28 February 1998)

Project support associated with procurement actions (recurring milestones for tools as they are identified - beginning in March 1998, ending September 1998

Post installation coordination with sites (begins 60 days after delivery, continues until all deliveries have been accomplished)

Development/Revision of milestone schedule to reflect detailed execution strategy and forecast for future planning efforts (integrated FY98-03 schedule with appropriate levels of detail) - recurring milestone with first delivery 1 February 98

FY99 Program Planning

Review/Amend Program Plan, as appropriate. (March - June 98, iterative process)

Support for presentation at ETS98 (integrated FY98-03 presentation) (April 98, TBR)

Attendance/Participation in Pathfinder 99 study (user requirements, functional crosswalks sessions plus pre-planning meetings) (Dates TBD)

Begin site coordination (begins July 98, coordination with multiple sites through end of FY or until all sites identified)

Build/Maintain Internet/Intelink input data regarding status of all program efforts (recurring milestone, beginning Jan 98)

5.17.3 Technical Requirements

a. Provide support for development of required program documentation leading to site participation and procurement of selected tools.

b. Participation in meetings with users/sites in regards to program objectives.

c. Prepare briefings and reports related to program plan/status for presentation at various technical meetings and input into Internet/Intelink home page.

a. Support/Participate in TDY to sites to facilitate program coordination, execution of agreement documents, post installation reviews, etc.

b. Provide integration support to coordinate efforts between EI Tools and other programs such as NIMA Softcopy as well as external site programs.

5.17.4 Deliverables

Note: All documents delivered in hard copy must also be delivered in soft copy format for PC (specific s/w applications TBR, but MS Word for textual reports, MS Powerpoint for vu-graphs, etc.).

Updated Program Plan

Drafts/Final Agreement Documents

Supporting CM and CCB Documents

Briefings/Reports related to program plans/status

High/Mid/Detailed milestone schedules (FY98-03)

Internet/Intelink homepage input

Government and Contractor negotiated content and format.


Geospatial & Exploitation Tools Division (EST)

5.18.1 Description

The JMTK is a common support application within the Defense Information/Common Operating Environment (DII/COE). It provides the functions necessary to render a common view of the battlespace and standardizes the import, display and manipulation of digital geospatial information. JMTK will ultimately replace the legacy mapping toolkits for DII/COE mission applications.

5.18.2 Objectives and Milestones

NIMA is the executive agent for MCG&I for GCCS and the DII/COE and JMTK will be deliver for both.

Version # 3.2 3 Oct 97

3.3 3 Apr 98

4.0 3 Oct 98

4.1 3 Apr 99

4.2 3 Oct 99

5.18.3 Technical Requirements

Provide NIMA with program management support, systems integration and technical support, and development support for all phases of the project, to include: requirement definition, detailed design, DII/COE and JMTK integration planning, testing, verification and validation, and implementation.

5.18.4 Deliverables

a. Program Management Documentation

b. Meeting agendas and minutes

c. Technical reports

d. Requirements documentation

e. Request for changes

f. Test plans and procedures

  1. Transition documentation

Government and Contractor negotiated content and format.


6.1 Description

Resources and Programs (RP) and the Requirements Office (RO) are responsible for managing the requirements and program control concepts using an integrated information technology approach to satisfy program managers, senior ST management needs, as well as external NIMA information requests. RP manages, assesses and defends NIMA ST resources and is responsible for the information management of those financial and programmatic activities. RO leads the definition and management of the processes for documenting, validating, approving, verifying and reporting new system and information requirements for both NIMA and the USIGS.

6.2 Objective and Milestones

Development and implementation of program control concepts, information management, cost analysis, requirements definition and training support for all NIMA/ ST resources and programs.

6.3 Technical Requirements

a. Update the ST Program Control Plan (PCP), which is the baseline document that defines the ST Program Control environment. The update shall incorporate the role of Resource and Programs Office (RP) at the enterprise level and at the project/program level as well as the roles of all NIMA elements involved in the program control process.

b. Develop a strategy to manage the necessary information as it pertains to the Program Control Environment and the Requirements process.

c. Develop and assist in implementing an integrated solution for retrieval of the necessary information from existing data bases in use by ST to manage resources and programs.

d. Support activities such as the Technical Planning Information Base (TPIB), Decision Support Environment (DSE), Integrated Road Map (IRM), or other management/engineering efforts.

  1. Provide cost analysis and related engineering support:

- Provide programmatic control and cost estimation techniques in support of the ST formal and informal program reviews and budget preparation for formal submissions to OSD. Cost analysis will use requirements as defined by RP and/or the program managers and perform computer aided parametric or other analysis methodologies to determine total life-cycle costs includes software, hardware, engineering, and infrastructure costs. Price Systems Software will be used in accordance with DoD/PA&E guidance.

- Assist in preparing quick responses to ST and related NIMA/USIGS resource issues raised by Congressional staffs or the Intelligence Program Review Group.

- Gather technical and programmatic information on ongoing ST activities.

- Identify, develop and document methodologies for estimating resources required by the programs identified by RP. Store estimates in a repository for historical information to assist in comparison of estimated versus actual costs during the programs execution.

- Provide Risk Assessments, in accordance with the Program Implementation Directive (PID), to assess potential cost impacts to the ST program. Assist in developing the necessary cost benefit analysis and return on investment to support inputs to the ST engineering/programming/budgeting decision making process. Maintain configuration management and traceability between estimates.

- Provide system and database support for the Program Control network to include networking and software tool support. Assist in the identification of the best integrated information tool set and a supporting strategy to satisfy the Program Control implementation.

f. Support Requirements Definition through documentation and definition of the requirements management process:

- Develop and document a Concept of Operations which define a requirements management system with controllable access via NIMA intranet, the Internet, and Intelink. Develop and demonstrate an initial version of a requirements data model with intelligent tools supporting analysis and decision-making activities. Evaluate, modify and format information currently stored on separate information systems which can be linked and/or integrate for accessibility (e.g., dissemination and retrievability).

- Identify and provide linkage between requirement requester information, associated programs/projects, statuses, resources, schedules and a capability to capture priority and/or status changes for each requirement.

g. Assist the developer of the existing IRM in identifying any specific enhancements to meet RP and RO information management requirements.

h. Provide technical support in the defining, implementing, and reporting of a performance measurement process in support of the Program Control Plan and in the evaluation of performance measurement results.:

- Work with the existing contractor performing the work on the Technical Planning Information Base (TPIB) to incorporate any existing performance measurement tools into the Program Control Plan Measurement Process. Ensure implemented Performance Measurement Process is consistent with the overall NIMA Performance Measurement Process and the ST performance reporting requirements.

i. Develop resources and program control and requirements management process training requirements documentation for NIMA ST personnel. Identify initial, follow-on, and refresher training. Assist in coordinating final training requirements with the National Imagery and Mapping College (NIMC)to ensure that NIMA/ST training requirements are incorporated into the broader NIMC curriculum.

6.4 Deliverables:

1. Monthly status report (2 copies), one each for RP and RO.

2. Program Control

a. Updated Program Control Plan with supporting implementation plan in format to be provided by the Government.

b. Concept of Operations for Program Control and the IRM.

c. Management strategy briefing and documentation for Program Control and the Requirements process.

d. Meeting summaries for support to TPIB, DSE, IRM and related resource management efforts.

3. Cost Estimates and Analysis

a. Cost estimates as required, in format provided by the Government.

b. Issue papers as required to respond to congressional QFRs and a the IPRG process.

c. Risk assessments, as required in format to be provided.

4. Requirements management

a. Concept of Operations documenting requirements management process.

b. Demonstration and documentation for an initial requirements data model.

5. Document the training program for resource and program control and requirements management training for the ST directorate.


7.1 Project Information Management (PIM)

7.1.1 Description

This project provides ST/Technology and its seven offices with an operational and accessible project information system, and with the system administration and project review support needed to maintain and use the system.

7.1.2 Objective and Milestones

To provide the Technology Directorate with one system or source for managing, scheduling and tracking project information and resources, and for answering external requests for information.

7.1.3 Technical Requirements

Implement and maintain a project information system for the Technology Directorate and shall provide support for project management reviews. Major tasks are:

a. Design linkages with other NIMA systems

b. Modify system to meet evolving Technology Directorate and NIMA requirements.

c. Design reporting and search capabilities.

d. Complete automated data population from existing data and systems.

e. Provide initial procedures and training at multiple Technology Directorate sites.

f. Provide ongoing system administration and quality control of data submissions.

g. Support project management reviews.

i. System administration of the PIM system.

j. Implement project information management system

k. Support the auto-population of existing data to the PIM system.

7.1.4 Deliverables

a. Initial PIM operating procedures and training documentation.

b. Technical reports as required.

Government and Contractor negotiated format and content.


8.1 IR Imagery Softcopy Exploitation (IRISE)

R&D Navy Yard Division (TRN)

8.1.1 Description

The IR Imagery Softcopy Exploitation (IRISE) program is to develop a set of validated methods for use in extracting intelligence form IR imagery.

8.1.2 Objective and Milestones

The major program activities are the development of algorithms and techniques that will assist the analyst in deriving intelligence and making decisions based on the temperature of objects.

8.1.3 Technical Requirements

a. Provide support in coordinating meetings, action item generation, tracking, and closure, technical summary generation, schedule maintenance, and support to the IRISE COTR.

b. Provide support to test activities including collection and evaluation of data for the blind test, formal test witnessing, test analysis, and results briefings.

c. Provide coordination and analytical support at user interface TEMs.

8.1.4 Deliverables

a. Technical summaries - as required

b. Project status reports - as required

c. Test briefings results - as required

Government and contractor negotiated content and format.

8.2 Assisted Target Monitoring System (ATMS)

R&D Navy Yard Division (TRN)

8.2.1 Description

The Assisted Target Monitoring System (ATMS) is a proof-of-concept/demonstration system that applies the state-of-the-art in Automated Target Recognition (ATR) technology to assist imagery analysts in monitoring intelligence targets.

8.2.2 Objective and Milestones

The objectives of this proof-of-concept/demonstration system are to demonstrate the utility of the current ATMS to support softcopy imagery exploitation; gain insight necessary to migrate ATMS into operations.

8.2.3 Technical Requirements

a. Program Support: Program support including (PMRs, TEMs, TIMs, etc.), action item generation and closure, technical summary generation, schedule maintenance, and COTR support (PMGs & PSRs). Coordinate TEMs

b. Configuration Management: Development and maintenance of ATMS Program documentation:

- Requirements specifications

- Operational Concepts

c. Program Acquisition: Project planning, brainstorming, Statement of Work development, Request for Proposal development, source selection process, bidders conference, technical and management proposal evaluation.

d. Readiness Process: Design review activities (readiness reviews, question consolidation, issue identification, technical summary of reviews, review closure coordination and follow-thru).

e. Test and Verification: Verification tasks including assessment and input on the RVTM and test procedures, test data preparation and truthing, test witnessing/requirements verification and test analysis and closure briefs.

f. Requirements Analysis: Data requirements analysis including evaluation and search for representative data interfacing with contractor for additional data and support data needs.

8.2.4 Deliverables

a. Technical summaries - as required

b. Project status reports - as required

c. Test briefings results - as required

d. SOW and RFP development - as required

Government and contractor negotiated content and format.

8.3 Image Fusion

R&D Navy Yard Division (TRN)

8.3.1 Description

Image fusion is the process of combining multiple independently collected images of the same scene to improve the exploitation value.

8.3.2 Objective and Milestones

Leverage from the developments of the Multiple Frame Date Fusion and the Cross-Sensor Resolution Enhancements to improve the exploitation value of fused imagery.

8.3.3 Technical Requirements

a. Provide support in coordinating meetings, action item generation, tracking, and closure, technical summary generation, schedule maintenance, and support to the Fusion COTR.

b. Provide support to test activities including collection and evaluation of data for the blind test, formal test witnessing, test analysis, and results briefings.

c. Provide coordination and analytical support at user interface TEMs.

8.3.4 Deliverables

a. Technical summaries - as required

b. Project status reports - as required

c. Test briefings results - as required

Government and contractor negotiated content and format.

8.4 COTS Media Evaluation and Paper Like Soft/Copy Device (PLSD)

R&D Navy Yard Division (TRN)

8.4.1 Description

The COTS Media Evaluation and Paper like Soft/Copy Device programs are an evaluation process for determining the suitability of an IR-sensitive dry COTS film process as a replacement for the wet film currently used.

8.4.2 Objective and Milestones

As stated in section 8.4.1

8.4.3 Technical Requirements

Pre-acquisition support, technical and programmatic support at all major reviews and TEMs, performance analysis, and requirements updates.

8.4.4 Deliverables

  1. Acquisition documentation, as required
  2. Meeting minutes
  3. Technical reports, as required

Government and contractor negotiated content and format.

8.5 Automated Target Recognition (ATR)

R&D Navy Yard Division (TRN)

8.5.1 Description

Assisted/Automated Target Recognition (ATR) is a research and development focus area aimed at developing technology to extract information from imagery with little or no human intervention. Currently, and for the foreseeable future, ATR technology is envisioned as a tool for the human analyst, due to robustness issues. The NIMA ATR program will provide a comprehensive strategy to achieve transition of ATR technologies quickly to have maximum impact for the warfighter. Cooperative efforts in progressive, high payoff research will be pursued under the Break-Through Research facet of the ATR Program. And finally, ATR Outreach and Concept development will engage the community to provide Imagery Intelligence and Geospatial focus to DoD ATR development activities.

8.5.2 Objective and Milestones

The main goal of this program is the transitional development to expeditiously move technology out of the laboratory and into the field. It is also to increase the productivity and decreases cycle time of the analysts extracting intelligence and geospatial information from imagery. Crucial to that goal will be assessment to identify applicable technology and quantify it's potential impact to imagery intelligence and geospatial data production.

8.5.3 Technical Requirements

Support is required assess and determine the fundamental utility of technological solutions to a particular ATR application in its most rudimentary form; support breakthrough research efforts and select ATR based technologies for assessments and prototyping; support transitional development activities for ATR solutions; and investigate spectral technology applications to ATR problems.

a. ATR R&D with experience in imagery exploitation applications of ATR technology to assist in planning and execution of this program. ACTD experience required.

b. Assist NIMA in developing strategies, plans, milestones and budgets for the NIMA ATR program.

c. Develop briefings, presentations, and papers on ATR technology and strategies to effectively execute ATR R&D across DoD and other agencies.

d. Community ATR focus/coordination and technology transfer. Pre-acquisition support as required, strategic planning, and technical assessment and analysis of ongoing ATR programs.

8.5.4 Deliverables

a. Developing strategies, plans, milestones and budgets for the NIMA ATR program.

b. Develop briefings, and papers on ATR technology and strategies to effectively execute ATR R&D across DoD and other agencies.

c. Present and demonstrate the ATR techniques.

Government and contractor negotiated content and format.

8.6 Semi-Automated IMINT Processing ACTD (SAIP)

R&D Navy Yard Division (TRN)

8.6.1 Description

The Semi-Automated IMINT Processing (SAIP) Advanced Concept Technology Demonstration (ACTD) focuses on near term applications of automated image examination tools, specifically Automatic Target Cueing (ATC) applications, as well as interactive Automated Target Recognition (ATR), cluster analysis, template based ATR (model-based and multispectral-based), terrain analysis (site monitoring and automated site modeling), advanced human/computer interface applications, object level change detection and image/map registration. Most applications in the SAIP ACTD use U-2 and Tier III(minus) with SAR imagery. Tools being integrated into this ACTD come from the past several years of R&D projects.

8.6.2 Objective and Milestones

There will be three major exercise events during FY98-FY99. In addition, there will be multiple interim laboratory assessments.

- 01 Feb 1998, ACOM military technical exercise

- 15 Aug 1998, MIS upgrade insertion/demonstration

- 01 Sep 1998, split-Based CONUS demonstration

- 01 Jan 1999, ACOM Operational transition

8.6.3 Technical Requirements

NIMA specific SI/SE support requirements include subject matter expertise in ATR for consulting and planning, thorough background of imagery analysis processes and tactical military operations that are affected by imagery, and experience in utility assessment of imagery exploitation technology. SI/SE personnel will be required to plan and execute Military Operational Utility Assessments under NIMA and USACOM guidance to quantify "value-added" of this advanced technology's affect on battlefield operations.

8.6.4 Deliverables

a. Produce and present briefings, reports, and papers on Technology Assessment methodologies and results.

b. Produce, in cooperation with contractor/government team, various Assessment plans.

c. Lead various working groups to determine assessment metrics and methodologies.


9.1 Joint Warrior Interoperability Demonstration (JWID)

Strategic Technology Planning Division (TDS)

9.1.1 Description

The Joint Warrior Interoperability Demonstration is comprised of a series of annual joint interoperability demonstrations sponsored by the Joint Staff with participation from the services and CINCs. Each year a CINC is identified as the sponsor with a service lead. This team (Joint Staff, CINC and Lead Service) determines the specific objectives for JWID and solicits government and industry participation via a Commerce Business Daily (CBD) announcement with the intent to identify early implementation of off-the-shelf technology which will improve the warrior's operational capability/mission. Demonstrations are evaluated by operational personnel resulting in the selection of technologies/systems(Golden Nuggets) for fast track procurement. Planning for this activity begins early each fiscal year with the demonstration executing late the following summer.

9.1.2 Objective and Milestones

The following is a reoccurring schedule for each JWID yearly cycle:


Oct Participate in JWID 98 Call

Nov Prepare NIMA Demo Plan (draft)

Jan JWID 98 Initial Planning Conference

Mar JWID 98 Mid Planning Conference

May JWID 98 Final Planning Conference

Jun NIMA demonstration Integration / Test

Jul On site integration, installation and test

Aug VIP Week

Jul-Sep Develop NIMA JWID 99 Demonstration Plan

9.1.3 Technical Requirements

a. JWID Planning. This addresses the current and next year planning for JWID. It encompasses the:

- Identification and readiness assessment of NIMA technologies for participation in JWID.

- Preparation of JWID demonstration specific documentation.

- Develop and maintain JWID master schedule.

- Technical Exchange Meetings (TEMs) - schedule and document.

- Interface with JWID Senior Management Group (SMG) and demonstration.

- Establish the demonstrations.

b. Provide the necessary systems and technical engineering required to integrate the NIMA demonstration(s) into the current year operational environment and scenario.

c. Provide for the acquisition of necessary system elements and interfaces required to support NIMA's current year demonstration.

9.1.4 Deliverables

a. Generation of JWID specific documentation such as:

- demonstration plan

- demonstration sub-plans

b. JWID demonstration

c. JWID Master Schedule

d. Technical support documentation

e. JWID after action report to reflect the success and lessons learned for each


Government and Contractor negotiated format and content.

9.1.5 Travel

JWID planning conferences (3 annually), interaction with other demonstrations, TEMs and with Allied participants/partners.

9.2 Strategic Technology and Thrust Development

Strategic Technology Planning Division (TDS)

9.2.1 Description

NIMA Strategic Thrusts have been identified as the foundation for managing NIMA's technology program. Four thrust areas have been developed to support NIMA's mission with specific technologies (subthrusts) under each Thrust. This activity will provide for a detailed identification and roadmap of technology development needs to support the thrusts for specific time frames (near, mid and long term).

9.2.2 Objective and Milestones

The following is a reoccurring schedule to coincide with NIMA FY Business Cycle:

Q1 Integrated current year roadmap / program

Q2 Draft FY98 TAP / Intel TAP

Q3 Final TAP / ITAP

Q4 FY 99 Planning Conference

9.2.3 Technical requirements

a. Provide current and follow-on FYDP year planning for the Strategic Thrusts and Sub-thrusts. It will provide support to Thrust managers in developing thrust specific "Area Plans" for input into the Technology Area Plans (TAP) and Associated Intelligence FY documentation.

b. Provide the necessary technical analysis and forecasts required to support the development of technical and investment strategies.

c. Provide the development of technology roadmaps (in soft copy) and associated documentation to support the thrust manager in integrating and documenting the technical program. In addition it will include the development and maintenance of a technology and requirements database and provide a linkage to the softcopy generation of technology roadmaps.

9.2.4 Deliverables

a. Maintenance of the NIMA Strategic Thrust

b. Development of technology roadmaps for each Strategic Thrust and


c. Development of associated technology analysis

d. Development of investment strategies

e. Development of TAPs

Government and Contractor negotiated format and content.

9.3 DoD and Intelligence Community Technology Planning

Community R&D Interface Division (TDC)

9.3.1 Description

The High Resolution Terrain Information (HRTI) project is in response to the Joint Requirements Oversight Council (JROC) decision to support the development of a high resolution digital terrain capability. The purpose is to reaffirm and further clarify the need for HRTI, as documented by the JROC DTED Study Group of 1995, and to develop a process and procedures for satisfying the HRTI requirements. A high Resolution Working Group (HRWG) has been formed with NIMA and the external user community participating to address the issues related to HRTI.

The work of the HRWG will be to specify the production requirements for HRTI, deriving methodologies and procedures for evaluating the conformity of HRTI data to specifications, and communicating the efforts to interested parties.

9.3.2 Objective and Milestones

The objective is to determine how to specify, collect, produce and evaluate HRTI data so that it will best meet the needs of the end user.

9.3.3 Technical Requirements

a. Capturing and tracking actions items.

b. Configuration management support.

c. Maintain HRTI project schedule.

d. Working group/conference/meeting coordination and support.

e. R&D community support.

f. Coordinate with GIIPT and community fora.

9.3.4 Deliverables

a. Technical reports as required.

b. Briefings as required.

c. Update HRTI project schedule.

Government and Contractor negotiated format and content.

9.4 National Research and Development Council (NRDC)

Community R&D Interface Division (TDC)

9.4.1 Description

The National Research and Development Council (NRDC) provides the opportunity and means for NIMA and other imagery and geospatial R&D stakeholders to coordinate and collaborate in the full range of R&D activities. The NIMA Associate Deputy Director for Technology will chair the NRDC. Membership includes senior level experts from DOD and U.S. Government, Commonwealth R&D partners, special industry experts, and NIMA business units. The NRDC meets twice annually with working groups and other activities executing under the NRDC.

9.4.2 Objective and Milestones

Provide technology outreach and coordination for the Imagery and Geospatial R&D community and stakeholders.

Reoccurring meetings are as follows.

a. FY 98 (Execution Year)

b. NRDC meeting: Twice yearly (June and December 1998)

c. Working Groups: 4 working groups; 2 meeting once every two months, and 2 meeting on quarterly basis.

9.4.3 Technical Requirements

a. NRDC Activities Planning. Coordinate the NRDC meetings, the agenda for the NRDC Chair and Executive Secretary, and coordinate the working groups

b. Conducts two meeting per year and working group meetings that meet on monthly basis.

c. Responsible for coordination and integration of other government and contractor activities involved in the planning and execution of NRDC activities.

- Meeting minutes (6 copies) for courier distribution and sent via fax (without enclosures).

- Agendas.

- Coordination and preparation of presentations to semi-annual NRDC meetings,

- Action items.

- Schedule of upcoming activities.

- Technical integration support to Working Groups and Panels formed under the - NRDC, and the NIMA Strategic Technology R&D Thrusts.

- Meeting facilities for NRDC planning.

9.4.4 Deliverables

a. NRDC: Minutes of NRDC meetings, NRDC agenda, NRDC Imagery and Geospatial Technology Activities Schedule, database of NRDC members/attendees, file of presentations.

b. Working Groups and Technical Panels: Reports from meetings, tracking actions, support to R&D Community Fora, including the Exploitation Technology Symposium.

Government and Contractor negotiated format and content.

9.5 Imagery Derived Products(IDP) / Image Science Validation Board (ISVB)

Community R&D Interface Division (TDC)

9.5.1 Description

The Image Science Validation Board (ISVB) conducts technical studies and analysis of technique requests to produce unclassified Imagery Derived Products (IDP) from classified imagery. IDPs may be literal images or non-literal line drawings. Technique requests are reviewed by the ISVB to ensure that IDP techniques meet technical thresholds specified in the DCI's IDP policy. Technical support is provided to the Imagery Policy Security Committee (IPSCOM), chaired by the National Geospatial and Information Office (NP).

9.5.2 Objective and Milestones

FY98 (Execution Year)

ISVB Meeting minutes monthly

Technique Book update monthly

Technical Reference Book update monthly

Summary of IDP Techniques & Uses update monthly

ISVB Directory update as required.

Master Schedule update as required

Special Study (Other) November 97

Statistical Report quarterly

IPSCOM Use-Review monthly

INTELINK Posting as required

R&D Watermarking Initiative Phase 1, Sept 98

Conduct technical validation of IDP techniques through the ISVB and other studies in support of National Geospatial and Information security policy. Develop, evaluate and implement the capability insert electronic "watermarks" into digital images or imagery derived products to ensure proper classification, use and handling.

9.5.3 Technical Requirements

a. ISVB Activities Planning. Coordinates the formulation of the agenda with the ISVB Chair and the NIMA Geospatial Policy point of contact for Imagery Derived Products (IDP)

b. Conduct two meeting per month, one for the ISVB Technique Review, usually on the first Wednesday of each month, and the follow-on Use-Review meeting, usually the following Wednesday, preceding the Imagery Policy Security Committee (IPSCOM) meeting.

c. Maintain IDP Library:

- Technique and Use Requests: Maintain a working file of Technique and Use Requests and IDP examples, in hardcopy original and softcopy form. Average 3 per month.

- Voting Forms with Criteria: Maintain and update as required.

- ISVB Directory: Maintain list of ISVB members, technique requesters and - contractors. Includes phone/fax numbers, addresses, security clearances, etc.

- Necronomicron Book: Maintain Necronomicron from studies, publications and other sources of information on protocols and public awareness that are relevant to ISVB interest.

d. Support IDP technique and use review processes.

e. Conduct special studies.

9.5.4 Deliverables:

1. ISVB Monthly Meeting reports (6 copies) for courier distribution and sent via fax (without enclosures). Includes table of techniques, action items, table of approved/pending techniques and uses.

2. Technique Book: 12 copies of all approved or pending technique requests. Updated monthly.

3. Technical Reference Book: Contains latest version of IDP policy, Technical Validation Guidelines, abstracts from R&D projects, ISVB monthly meeting reports. Updated monthly.

4. Summary of IDP Technique and Use Requests: Updated as required.

5. Endorsement Letters: Generate and staff SR level endorsement letter to ISVB Technique Request findings.

6. Softcopy of IDP Example: Acquire softcopy example or digitized example of IDP from technique requester, along with technique request and updated image chain description (figure and narrative). Part of IDP Library maintenance task.

7. ISVB Directory: Update every two months, maintain in softcopy.

8. Notification and Read Ahead Materials: Notify ISVB members telephonically of ISVB meeting and faxes sent in preparation of upcoming ISVB activities. Fax advance copies of the agenda, and new/updated technique requests to ISVB members prior to monthly meeting.

9. Master Schedule: Track level one action items for special studies and major milestones.

10. Special Studies: Arrange for meetings and materials required to conduct one special study per year.

11. Statistical Reports: Generate statistical reports of technique and use request by IDP type, sensor type, organization, and projection of trends.

a. ISVB Technical Support to IPSCOM Use-Reviews:

b. Maintain table of technique and use request for the IPSCOM

c. Provide support to generate and issue upcoming Use-Review agenda and fax read ahead materials.

d. Maintain Use-Review Criteria Voting Sheets

e. Generate and distribute Use-Review meeting minutes

f. Maintain the IPSCOM/Use-Review Address List

g. Maintain a file of approved Use Requests.

12. INTELINK Posting: Provide electronic compatible input for posting approved and pending Techniques and Uses, and other information to help users obtain needed information on IDPs. Options for additional technical support may be required.

13. Transition Support: Provide technical integration support for transitioning approved Techniques into NIMA production systems, demonstration of capabilities, development of new concept of operations, and identification of requirements and impacts.

14. R&D Initiatives: Provide technical support for new R&D initiatives, such as digital watermarking techniques.

Government and Contractor negotiated content and format.


10.1 International Arrangements

10.1.1 Description

R&D collaboration with international partners.

10.1.2 Objective and Milestones

Outreach to international partners to identify opportunities for synergy in R&D projects, formation of standing and special technical working groups to advance the USIGS technology base and technology transfer.

10.1.3 Technical Requirements

Support NIMA in fulfilling its obligations to collaborate with our current and future international R&D partners.

a. Plan, attend, and document meetings.

b. Track action items.

c. Prepare policy documentation.

d. Work with other Government agencies.

10.1.4 Deliverables

Minutes to meetings and preparation of policy documentation.

Government and Contractor negotiated content and format.

10.2 International Customer Support

10.1.1 Description

This activity represents the functional identification and design/adaptation of USIGS components to support foreign government partners. This requires systems engineering and integration support involving tasks such as: assisting customers to identify functional requirements; assess translation of functional requirements to design requirements in terms of technical approach and compliance to USIGS enterprise standards and architectures; assist in resolution of issues, documentation, and promulgation of AIS and physical security documentation; support logistics, maintenance and configuration management issue resolution and documentation.

10.2.2 Objective an Milestones

One major system will be field in all years except the second contract year during which two systems will be fielded.

10.2.3 Technical Requirements

a. Program Management Support:

- Execute Critical Path Method (CPM) and Program Evaluation Review Technique (PERT) event planning methodologies. Approximately ten projects are involved and bi-monthly updates are required.

- Develop and maintain (bi-monthly) program/project planning schedules. Ensure dependencies, both internal and external, and that conflicts and risks are minimized.

- Conduct quantitative Risk Management Analyses (RMA) for the ten programs that identify risks and recommend mitigation strategies. Update these risk analyses at appropriate program decision points.

- Plan and determine proper training methodologies for international customers on imagery systems. Approximately 4 programs will require training support.

- Establish Integrated Logistics Support (ILS) plans for all projects.

- Recommend support options for the operations and maintenance of all software, hardware and firmware components provided to the foreign countries.

- Identify facility requirements for all systems supplied/provided to foreign customers.

- Provide financial management support to financially manage all ten supported programs.

- Provide acquisition support on the application of different contracting methods and procurement vehicles for all ten programs.

- Maintain ten project schedules and Division-level schedules currently incorporated into the Office-level Master Schedule.

b. System Integration and Engineering:

- Conduct software and hardware engineering studies, trade analyses and current state-of-the-art informational support in the development of software imagery systems for authorized foreign customers.

- Conduct in-depth requirements analysis (3 per year) and impact (3 per year) studies.

- Provide technical software engineering support (approximately four issues per year) to identify and resolve potential problems with APIs and other interfaces between system components of all elements of the integrated systems provided to foreign customers.

- Generate SOWs (approximately two per year) for system integration of various US systems such as RMS, IESS, NES, ESS, DE, 5D, IPL, IDEX and similar existing or migration systems.

- Provide software diagnostic capability to identify problems or issues in the functional integration of systems into one entity for use by foreign governments. Approximately one system per year will be handled.

c. Configuration Management:

- Provide configuration management support to the International Configuration Management (CM) process ensuring all documentation for foreign country architectures are generated, reviewed, assessed, and submitted within NIMA and counterpart imagery organizations. Approximately twenty CM actions per year will be managed.

- Recommend alternatives for an acceptable configuration management process that adequately mesh approximately ten NIMA and host country existing configuration and document control processes together.

d. Customer Support:

- Develop two Statements of Need, two Concepts of Operations, two systems requirements documents, two Statements of Work and other documents for each foreign government activity.

- Provide technical information to visiting teams of foreign governments on all supported systems. Major host country teams visit two times per year on the average. Document all activities (agreements, actions, etc.) that occur during meetings.

e. Security:

- Provide AIS information security support to total program. This includes the evaluation of security risks/issues for recommendations for resolution: encryption, firewalls, selected access software and hardware features and also the physical requirements necessary for the facilities housing the computer systems.

- Generate and coordinate system certification and accreditation requirements.

f. TEMS/Meetings/Briefings/Action Items

- Provide support to briefings, symposia, conferences and similar events for all

supported programs. One International Division sponsored annual conference and two symposia are conducted. Additionally, approximately two major briefings are given to various other conferences and symposia.

- Recommend disclosure/release determinations on documentation and information to a foreign country. Approximately three such disclosure packages are prepared per month.

- Document, track, and close action items, suspense actions and other issues to insure timely program management decisions. Approximately 45 action items are tracked for each of three major programs. Other programs have approximately three action items.

- Support/conduct video teleconferencing (VTC) and other communication methods with each foreign program. Each project has approximately one VTC per month.

10.2.4 Deliverables

a. Site installation plans as required.

b. Technical reports as required.

c. Integrated schedules.

d. RFCs as required.

e. Security plans required.

f. Action items responses as required.

Government and Contractor negotiated format and content.


11.1 Reverse Engineering and Modeling

11.1.1 Description

The Reverse Engineering and Modeling project began in FY96 to develop data and process models for modeling and simulation (M&S) systems to identify and certify the runtime terrain databases used. This information will be used in DISA data standardization, SEDRIS, and NIMA USIGS programs to better support the M&S community. This analysis continues in FY98 and will include other commonly used M&S systems that transform terrain data. Feedback (certification) will be provided upon completion of the analysis. The data will be used to populate the product and extraction database for analysis with other terrain products and provide information to related projects (SEDRIS, DISA Standards, USIGS). This project is expected to continue through FY02 as additional systems are analyzed and data is provided to support certification and standardization.

11.1.2 Objective and Milestones

The FY98 objectives for the Reverse Engineering and Modeling activity are: to institute a methodology for reverse engineering and modeling simulation systems; extend the database for the new systems; FY99 reverse engineer and model selected joint systems; FY00-02 continue modeling of new and transitional system; and expand the effort to C3I systems.

11.1.3 Technical Requirements

11.1.4 Deliverables

a. Monthly progress reports.

b. Yearly Final Project Reports.

c. IDEF0 and IDEF1X Models - as required

d. Database documentation - annually

e. Documentation for submission of new data elements to the DDS - as required

11.2 Terrain Domain Resource Repository

11.2.1 Description

The Terrain Domain Resource Repository is the terrain portion of a virtual repository of environmental data residing at numerous sites connected via the INTERNET. It is a subset of the Master Environmental Library (MEL). The MEL is the environmental portion of the Defense Modeling and Simulation Office (DMSO) Modeling and Simulation Resource Repository (MSRR). The MEL is a three tiered architecture using primarily COTS and GOTS software. The program will provide metadata, modify software for specific sites, and connect sites holding different terrain data. MEL sites will be established on multiple networks of varying classification to allow ready access to NIMA data, much of which is restricted. The MEL will be interfaced to the NIMA USIGS to provide access to multiple sources of geospatial and imagery data.

11.2.2 Objective and Milestones

In FY98, the objective is to interface with NIMA Data Architecture and Gateway Services (DAGS), enhance tools and ordering processes; interface with NIMA Libraries and external sources in FY99; update interfaces, tools, and delivery methodology in FY00; and upgrade and add new internal and external interfaces in FY01-02.

11.2.3 Technical Requirements

  1. Interface requirements definition and verification.
  2. Schedule maintenance.
  3. Program plan development

11.2.4 Deliverables

a. Monthly progress reports

b. Integrated/modified software tools - annually

c. Software Documentation - annually

d. Modified/new metadata records - as required

e. Briefings and demonstrations - as required

Government and Contractor negotiated format and content.

11.3 Dynamic Representation

11.3.1 Description

Dynamic Agents/Mobile Objects (DYNAMO) is an object oriented dynamic terrain repository tool. In summer 1996, a proof of concept tool and architecture for this physics-based dynamic terrain analysis system was developed and demonstrated. DYNAMO in FY97 is being enhanced to include specific, real NIMA datasets for use in demonstrations by incorporating into simulation exercises. The FY97 effort focuses on high fidelity physics modeling of the Fort Benning data collected in FY96. It is developing template terrain objects and enhanced visualization, including non-visual analytical data. A web-accessible demonstration capability which will leverage emerging INTERNET technology is to be made available on the TMPO home page in the fall 1997.

11.3.2 Objective and Milestones

This effort will continue into FY98 and beyond to reach full operational capability, provide the user with the ability to create specific structures, become High Level Architecture (HLA) compliant, and expand its usefulness with regard to other simulations.

The objective for FY98 is to integrate the structure creation tool into DYNAMO; in FY99, Interface DYNAMO to HLA; in FY00, extend data base and capability of DYNAMO; in FY01-02, upgrade interface for evolving simulations.

11.3.3 Technical Requirements

Modify software tools to create and modify physics-based object models (i.e. data bases) and templates to support DoD-wide simulations; integrate these models and templates into simulations operating under the HLA framework.

11.3.4 Deliverables

a. Monthly progress reports

b. Quarterly progress briefings

c. Integrated/modified software tools (annual)

d. Software documentation (annual)

e. Test Cases (annual)

f. Verification and Validation (V&V) cases (annual)

Government and Contractor negotiated format and content.

11.4 Terrain Modeling Project Office (TMPO)

11.4.1 Description

Terrain Modeling Project Office (TMPO), as the DoD Executive Agent for Terrain is responsible for providing systems engineering and integration support for Modeling and Simulation (M&S) community activities, particularly for the Joint M&S testbed activities. In FY96, the Concept of Operations for the TMPO testbed has been developed and approved to serve as a testbed for test and evaluation of algorithms and existing technical capabilities, and evaluation of procedures for Verification, Validation and Accreditation/Certification (VV&A/C). In FY97, this testbed concept was expanded and extended to include two other Executive Agents (EAs), i.e., Ocean, , and Air and Space EAs as an integral component for the M&S EA Integration Consortium (MIC).

11.4.2 Objective and Milestones

The MIC effort will continue into FY98 and beyond with a focus on developing and testing of VV&A/C procedures, rapid terrain data and database construction in coordination with other MIC partners, and expanding M&S requirements and capabilities database.

11.4.3 Technical Requirements

a. Development and testing of Verification, Validation, Accreditation and Certification (VVA&C) procedures.

b. Expansion of modeling and simulation (M&S) requirements & capabilities database.

c. Management for Modeling & Simulation Executive Agent (MSEA) integration consortium activities.

11.4.4 Deliverables

a. M&S requirements and capabilities database updates.

b. VVA/C procedural documentation

c. Monthly status reports.

Government and Contractor negotiated format and content.


Technical Assessment Division (TAA)

12.1 Rapid Tools Insertion

12.1.1 Description

Development of applications and tools for consideration of technology transfer and rapid insertion into operations.

12.1.2 Objective and Milestones

As noted in section 12.1.1.

12.1.3 Technical Requirements

a. Assist in assessing, identifying and making recommendations during rapid tools

selection process.

b. Assist NIMA in meeting technology transfer objectives.

c. Provide support on and identify appropriate transfer mechanisms, implementation, measurements of success, and executing technology transfer


d. Plan and execute meetings/TEMs with customers (e.g. Pathfinder)

e. Provide technical solutions to customers.

f. Assist in collecting metrics/evaluations.

g. Provide for the execution of plans.

12.1.4 Deliverables

Technical reports as required

Government and Contractor negotiated format and content.

12.2 Lab Network Support

12.2.1 Description

Facilitate networking of lab systems (Washington, Northern Virginia, Bethesda, and

St. Louis), and these systems to external networks such as Internet/NIPRNet, JWICS, and SIPRNet.

12.2.2 Objective and Milestones

Ensure NIMA Technology Directorate has appropriate network access to ensure connectivity to all internal and external customers, and community partners.

12.2.3 Technical Requirements

a. Assist in assessing, identifying, and managing a collaborative lab network.

b. Assist NIMA in maintaining a collaborative work space for numerous R&D programs, as well as rapid prototyping development.

c. Provide planning, integration, and engineering support for lab networking.

d. Provide expertise on emerging capabilities (e.g. ATM as it relates to NTVL).

e. Plan and execute meetings and TEMs with NIMA personnel and external support

organizations (e.g. DISA).

f. Assist NIMA in developing, identifying, and rapidly providing technical solutions

to customers.

g. Provide support on and identify appropriate transfer mechanisms, implementation, measurements of success, and executing technology transfer


h. Assist in collecting metrics/evaluations.

i. Provide for the execution of plans.

12.2.4 Deliverables

Technical reports as required.

Government and Contractor negotiated format and content.

12.3 Lab Database Development

12.3.1 Description

Database integration and development for NIMA labs which includes Oracel on PC and SUN equipment as well as FileMaker Pro and any other software packages developed for database utility in support of data sharing among the geographically dispersed NIMA R&D labs.

12.3.2 Objective and Milestones

As noted in section 11.4.1

12.3.3 Technical Requirements

a. Assist in assessing, identifying, recommending appropriate database management


b. Assist NIMA in rapid development of database tools.

c. Ensure NIMA Technology directorate has appropriate capabilities to manage

corporate information.

d. Provide planning, integration, and engineering support for various database


e. Provide expertise on emerging capabilities (i.e. Object Oriented, COBRA).

f. Plan and execute meeting and TEMs with NIMA personnel.

g. Assist NIMA in identifying, developing, and implementing solutions for Technology Directorate database users, and external customers.

h. Identify appropriate demonstration mechanisms, plans, and implementation tasks.

12.3.4 Deliverables

Technical reports as required.

Government and Contractor negotiated format and content.

12.4 Hardware/Software Procurement

12.4.1 Description

Acquisition and procurement of prototype hardware and software to meet NIMA's strategic thrust projects.

12.4.2 Objective and Milestones

As noted in section 12.4.1

12.4.3 Technical Requirements

a. Provide planning, integration and engineering support to procure prototype hardware and software configuration solutions after receipt of direction from the Government. Procurement will be defined as "Urgent" or "Regular".

b. Assist in identifying and recommending appropriate hardware and software to

meet NIMA Technology strategic thrust projects.

c. Provide expertise on emerging hardware capabilities (e.g. software compilers).

d. Plan and execute procurement milestones/tasks.

12.4.4 Deliverables

a. Develop acquisition plans.

b. Provide acquisition status reports as required.

c. Provide technical reports as required.

Government and Contractor negotiated format and content.


13.1 Modeling and Simulation Compliance

13.1.1 Description

Ensure NIMA compliance with Department of Defense (DoD) modeling and simulation (M&S) directives and policy. Provide authoritative and faithful representation of NIMA systems and processes within DoD and Intelligence Community (IC) M&S activities. Represent NIMA in forums centered on the advancement of technology and applications for simulated and synthetic environmental representations of terrain. Specifically, the primary focus is to ensure accurate representation of NIMA systems, processes, and organizational relationships in support of DoD training and exercises activities, and development of the Joint Simulation System (JSIMS). A key element of this activity is interfacing with DIA as a partner in their overall formal role as JSIMS Executive Agent for Intelligence.

13.1.2 Objective and Milestones

As noted in section 12.1.1

13.1.3 Technical Requirements

Support the Governments efforts as noted in section 11.1.1

13.1.4 Deliverables

Monthly M&S Intelligence Program overview reports and briefings as required. Government and Contractor negotiated format and content.

13.2 Architecture Simulation and Analysis Platform (ASAP) Operations and Maintenance

13.2.1 Description

The Architecture Simulation and Analysis Platform (ASAP) is a graphical model-building environment that requires users to possess modeling and analysis skills. The model includes the processes and activities that start when users identify their intelligence and imagery needs, and end when those users declare their needs satisfied.

13.2.2 Objective and Milestones

Provide user needs analysis.

13.2.3 Technical Requirements

a. Assist in defining and establishing the O&M phase for ASAP for FY 99.

b. Provide support the ASAP Engineering Review Board.

c. Maintain ASAP

d. Provide training of personnel to execute ASAP.

13.2.4 Deliverables

Monthly status reports. Government and Contractor negotiated format and content.

13.3 Capability and Strategy Analysis Tool (CSTRAT)

13.3.1 Description

The Capability and Strategy Analysis Tool (CSTRAT) allows for an assessment of the USIGS end-to-end architecture performance through a database and spread sheets. The concept is to develop a rapid reaction capability to integrate and analyze Community Imagery Need Forecast (CINF) user needs and USIGS strategies. The objective is allow a desktop system to operate a tool that allows for rapid turnaround to modify data input and provide new data outputs and minimize resources needed to sustain and operate the tool. To assess the total performance of architecture from end-to-end, the capability starts with the use of the CINF Planning Deck and Other CINF Extracts as authoritative statements of user needs. It uses key principles of the SIGS CONOPS and architectural concepts to develop alternative strategies. It applies resource capability and operational CONOPS constraints to project 'realistic' expectations. CSTRAT produces a product flow and volumetric data among USIGS "providers", "suppliers", and "customers". CSTRAT then provides data to support resource performance simulation and modeling techniques.

13.3.2 Objective and Milestones

As noted in section 12.3.1

13.3.3 Technical Requirements

a. Maintain the CSTRAT

b. Support CSTRAT development, test and delivery.

c. Support the CSTRAT engineering review board.

d. Install and demonstrate CSTRAT P.1

e. Install and demonstrate FLOW-E, version E.1

f. Provide CSTRAT training program.

13.3.4 Deliverables

a. Monthly status reports and briefings.

b. Develop CSTRAT training program documentation

Government and Contractor negotiated format and content.

13.4 Study Support

13.4.1 Description

Studies and analysis in support of such topics as; peace time scenarios (natural disaster relief, terrorist threats, ect.), military scenarios, civil and commercial imagery assessments, budget review, functional management review, decision support, user needs analysis from sensor to exploiter.

13.4.2 Objective and Milestones

As noted in section 12.4.1 and 12.4.3.

13.4.3 Technical Requirements

a. Provide modeling and simulation support for both internal and external studies on an as-required basis.

b. Assist in the planning and execution of NIMA study management support functions. This includes support to coordinate and deconflict substantive efforts in studies and analysis being conducted by NIMA offices and by intra-agency study teams. This effort shall be performed in conjunction with community members and through participation on government-contractor teams. The contractor shall use tailored analytic approaches, techniques, and approved tools to respond to study issues. The scope of these studies spans scenario development, analysis of USIGS system capabilities, quick reaction analysis in response to D/NIMA issues and support to resource and functional management assessments.

13.4.4 Deliverables

Interim and final White paper (monthly) and briefings. The emphasis shall be placed on the briefings.

Government and Contractor negotiated format and content.


14.1 Networks and Enterprise Systems Office (NES)

The Contractor shall support the NES Office (CN) with a variety of tasks in support of major NES projects and strategic plans and goals. These tasks require the coordination, maintenance, and update of NES strategic and tactical plans, and management planning activities in coordination with NIMA plans. The management of NES projects involves data collection, analysis, and reporting. To accomplish this, information must be culled, coordinated, and maintained in a NES accomplishments databases that will be created for this purpose. Reports generated from these databases will provide insight and focus for management overview and decision making.

14.2 NIMA Enterprise Network (NEN)

14.2.1 Description

With the standup of NIMA in October 1996, a variety of disparate enterprise network capability were joined. The NES Office was assigned responsibility to provide and integrated network services NIMA-wide called the NIMA Enterprise Network (NEN). NEN is the hardware, software and communications that comprise the NIMA-wide backbone for mission systems, office automation for desktop computers at all classification levels and provides connectivity between all NIMA sites whether for mission requirements or business unit requirements. It currently provides support to the USIGS and its imagery, imagery analysis, and geospatial information community.

14.2.2 Objective and Milestones

The NIMA Enterprise Network (NEN) is to provide NIMA with a robust, high capacity, multi-level, secure Enterprise Network (EN) capable of supporting all NIMA electronic communication requirements. Enable the NIMA Enterprise Network (NEN) to comply with DISA Defense Information Infrastructure (DII) Common Operating Environment (COE) directives, improve communication systems responsiveness and reliability, provide increased capacity and functionality and, support reduced agency staffing levels. Future NEN expansions must be in correlation with NIMA's production requirement trends as stated in the NIMA Migration Plan. The NEN must support the delivery of refined data and specific products in a digital format to customers. As production requirements become routinely driven by short-notice military operations world wide, the requirement for the NEN to support immediate, real time delivery of USIGS products and information to its customers becomes increasingly critical. The NEN is subject to change to accommodate mandated Federal and DoD telecommunication regulatory policies and guidelines and to the capabilities of supporting interoperability and integration with customer systems. The NEN will:

a. Provide a long-haul telecommunication system capable of supporting NIMA's USIGS communication requirements.

b. Provide a long haul telecommunication system capable of supporting NIMA's administrative systems and processes.

c. Provide secure telecommunications capability, voice and video.

d. Provide secure telecommunication interfaces, voice and video, to other DoD Services and Agencies, civilian Government agencies, and private and commercial networks.

e. Provide detailed specifications required for a reliable, cost-effective network management operations.

f. Develop detailed operational concept and system design specifications needed to provide cryptographic support for USIGS in accordance with mandated National Security Agency guidelines.

g. Develop and publish NIMA telecommunication System Configuration Management Guidance.

14.2.3 Technical Requirements

The contractor shall provide NIMA with Telecommunication Systems Engineering and Integration support services which are include in but not limited to the following:

a. Program Management

b. Integration Program Management and Development

c. Integration and Migration Strategy

d. Assessment Support

e. Assist the integration Prototyping and Testing

f. Training, Documentation, and Information Dissemination

g. Integration Engineering

h. Technical Management Planning


a. Coordinate, maintain, and update CN strategic and tactical plans and coordinate these with NIMA plans.

b. Develop a CN accomplishments database to track accomplishments and provide insight and focus for management overview and decision making.

c. Review, evaluate, define, and validate user's long-haul communication requirements.

d. Perform studies and analyses that will result in selection, acquisition and implementation of required communication requirements.

g. Engineer, acquire, manage, and coordinate the installation of telecommunication equipment and software to support NIMA's mission requirements.

h. Develop and coordinate detailed USIGS interface specifications with all

affected NIMA internal and external customers.

i. Perform comprehensive communication system evaluations to ensure that it will satisfy agency requirements and troubleshoot, as required, NEN problems.

j. Enhance existing networks with equipment/software and technologies in order

to support growing and expanding requirements when they are deemed beneficial

to the Government.

k. Develop and provide a plan for the establishment of a NIMA COMSEC equipment inventory and accountability system.

l. Prepare a configuration management plan for the NEN activities and perform CM on its documents and development deliverables. Document the as-is NEN configuration (via computer-aided design/computer-aided modeling equipment) details/specifications of the current NEN systems/components and changes occur. The configuration management effort shall start at the highest/broadest level which requires DoD participation and go down to the last networking device prior to the user's terminals. Develop and maintain, as required, in accordance with the following six (6) system integration levels, comprehensive communication cable distribution drawing for each NIMA site.

- Level 0, between Global and Enterprise

- Level 1, between Enterprise and Mission

- Level 2, between Mission and Function

- Level 3, between Function and Application

- Level 4, between Application and Local

- Level 5, between Local and Users

14.2.4 Deliverables

a. Provide configuration management plan for NEN activities.

b. Status reports as required.

c. Technical assessment reports as required.

Government and Contractor negotiated format and content.

14.3 Other Duties

FTE Estimates: 12.0


15.1 System Test and Verification (STV)

USIGS Integrated Test Division (AZT)

15.1.1 Description

To provide independent SE support to the NIMA Systems Test and Verification activities for USIGS as directed by AZT.

15.1..2 Objective and Milestones

Support the test and verification process to any or all future systems USIGS systems as directed by AZ which may require support to program managers outside AZ that require independent analysis and verification..

15.1.3 Technical Requirements

Support the USIGS Systems Test and Verification (STV) activities to include:

- Test planning and execution.

- Configuration management.

- Risk assessment and mitigation.

- Independent requirements verification.

- Integration planning.

- Functional requirements analysis and verification.

- Analysis, impact, and risk assessment of engineering change proposals (ECP) and Requests for Change (RFCs) to the USIGS.

- R&D and O&M engineering analysis.

- Crisis support.

- Re-engineering support.

- System verification and validation.

- Discrepancy Report (DR) investigation and resolution; perform studies and analysis of systems and segments to resolve problems, and/or candidate solutions and to establish the corrective actions that result in the selection of a solution..

- Integrate new initiatives into the systems.

15.1.4 Deliverables

a. STV plans upon request.

b. Risk-based analysis report upon request.

c. Technical reports upon request.

d. Report study results as Technical Investigation (TI) in DRs, or as technical reports (white papers) when requested.

e. STV status reports upon request

15.2 Engineering Review Boards

CM Support Division (AZC)

15.2.1 Description

Execution of the Engineering Review Boards for the geospatial production and geospatial production support systems.

15.2.2 Objective and Milestones

Support the AZ Engineering Review Boards (ERBs) to include: assisting the ERB Chair(s) in the execution and operation of the ERB process and providing recommendations, performing technical investigations of discrepancy reports (DRs), responding to action items, preparing RFCs and engineering change Proposals (ECPs), technical review and evaluation of RFCs and ECPs, configuration management, systems integration planning, risk management, identification and recommendation for internal/external interface issues, system issues, data flows, constraints, work around identification, and problem resolution definition and DR adjudication for the geospatial production and geospatial production support systems of AZ.

15.2.3 Technical Requirements

a. ERB Coordination:

- Coordinate ERBs and ERB sponsored forums. Schedule meetings, facilities, develop and coordinate agendas, publish and disseminate preliminary and final agendas, prepare and present briefings, prepare and disseminate minutes, identify all action items and track their closure.

b. Requirements Management:

- Focal point for supporting the ERB Chair(s) in the identification, definition, and refinement of requirements for the geospatial production and production support systems.

- Support RFC development, requirements analysis, technical reviews and evaluation of proposed changes (RFCs, ECPs and SCNs) to the geospatial production and geospatial production support systems. Evaluation of changes

shall include internal and external impacts, including USIGS compliance assessment, cost, schedule and resource implications proposed by both

efforts and users to ensure technical consistency and compatibility with existing

systems(s) and other initiatives.

- Analyze and evaluate new system development and system transition progress and

schedule performance, as directed by AZ ERBs. Assess schedule options, propose risk mitigation strategies, and evaluate milestones for all activities from a AZ ERB perspective. Determine critical paths and assess progress against those schedules for the AZ ERBs. Track the interactions and impacts.

c. Assist ERB Chair(s) in evaluating proposed solutions to AZ systems

discrepancies and identifying relative priorities among problems to facilitate their work-off.

d. Configuration Management:

- Track status of change activity from identification of need through


- Review, prepare, coordinate and distribute RFCs.

- Prepare and present briefings.

- Provide quality control over the RFCs to ensure compliance with established


- Maintain board controlled documentation.

15.2.4 Deliverables

a. RFCs upon request by the AZ ERB Chair(s)

b. Risk-based analysis reports upon request by the AZ ERB Chair(s)

c. Technical and status reports upon request by the AZ ERB Chair(s)

d. Provide schedule data to AZ ERBs.

e. Provide inter-initiative dependencies and production related dependencies.

e. Provide input to the NIMA USIGS Master Schedule as appropriate.

15.3 Configuration Management Infrastructure

Configuration Management Support Division (AZC)

15.3.1 Description

Provide Configuration Management (CM) support to the National Imagery and Mapping Agency (NIMA), Systems and Technology (ST), Systems Directorate (ST/S), Multi-Services Office (AZ), and attendant database/softcopy engineering, documentation maintenance and publication, and configuration control board (CCB) and engineering review board (ERB) administrative tasks.

15.3.2 Objective

As noted in section 15.3.1.

15.3.3 Technical Requirements

a. Engineering Support:

- Provide engineering support needed for the definition of requirements to facilitate the development and implementation of configuration management documentation as identified in this section.

- Provide support to define requirements for the revision or development, and implementation of the NIMA Configuration Management Plan (NCMP) and related policies and procedures; concept of operations (CONOPS); Information Management and Dissemination Plan (IMDP); and other programmatic documents.

- Develop and publish an AZ Office-level CM CONOPS or CMP. Perform issue resolution, as needed, to establish baseline documentation. Provide technical guidance to government and contractor personnel relative to the implementation of approved configuration management documentation.

b. Configuration Management (CM) Support:

- Provide a point of contact (CPOC) to the Government for daily interactions and information sharing for the purposes of planning activities, and preparation of reports and presentations to Government forums concerning the status of CM in this program.

- Provide support for configuration identification, change control, status accounting and tracking, configuration audits, and the NIMA Configuration Control Board (NCCB) and the NIMA Engineering Review Board (NERB).

c. Configuration Identification:

- Define configuration identification requirements for configuration items and associated interfaces.

- Maintain the NCCB user library to include all NCCB and office-level configuration controlled documentation to include NIMA standards, programmatic documentation (e.g. schedules, CMPs, and PMPs), program/system requirements specifications, and interface control documents, as required.

d. Configuration Change Control:

- Develop configuration control forms and change control procedures to manage configuration change processing for NIMA programs/systems.

e. Configuration Status Accounting and Reporting:

- Provide status accounting and tracking of all current and historical NIMA RFCs, ECPs, SCNs, Action Items (AI), TBD/TBR, modification transmittal memorandum (MTM), effectivity, waiver, and Programmatic Documentation to support Configuration Control Board activities. Provide status accounting and tracking system, and reports as appropriate in accordance with the NCMP and the CDRL.

f. Configuration Audits:

- Perform configuration management and security related audits once a year. All audits will be directed by the Government.

- Perform CM documentation and procedural audit to ensure systems/segments satisfy program requirements, and configuration management policies and procedures are properly implemented. Publish results of the audit.

- Perform security audit to ensure proper handling, storage, and destruction of NIMA documentation in accordance with established NIMA and contractor security procedures. Publish results of the audit.

g. Configuration Control Board Support:

- Participate in and provide support to the NCCB, NERB, and other external, or internal Office level configuration management boards defined in the NCMP. The NCCB and the NERB each meet once a month.

- Provide NCCB support to include the development of the agenda, recommendation and results messages, and participate in NCCB pre-brief (NERB) meetings to obtain and record Organization/Office recommendations to support the NCCB.

- Serve as the NCCB secretariat to include preparation of precis packages, briefing charts and associated cost packages, presentation of agenda items, and recording and reporting of agenda and action item dispositions.

- Develop, implement, and maintain the NCCB/NERB calendar and schedule, and perform coordination activities to ensure that meetings support established NCCB timelines and Directorate requirements of both on-going development and operational activities.

- Participate in external CCB meetings to provide CM input and perform external CCB to NIMA CCB coordination activities to ensure impacts and issues are identified and addressed.

- Perform coordination activities with NIMA Office-level Configuration Management Board (CMB), as appropriate.

h. Database/Softcopy Engineering Support:

- Provide database maintenance and enhancements to existing NIMA CM Databases used for CCB-level status accounting and tracking; and participation in designated NIMA studies/evaluations relative to the procurement and development of an overall NIMA database capability.

- Develop and implement enhancements, as required, and maintain existing softcopy database(s). Provide the capability for status accounting and tracking of configuration items and proposed changes of those items from conception through implementation, to include:

-RFCs and associated cost information

-ECPs (technical and cost) as appropriate


-Action Items

-CCB Baselines Configuration Item Lists (CILS)

-NIMA User Library Documentation

-Distribution/Dissemination List and Requirements

- Assist in system evaluation studies/assessments/evaluations as required, to identify and define CM requirements relative to the procurement and implementation of a NIMA status accounting and tracking system.

i. Documentation Maintenance and Publication Support:

- Prepare initial baseline documentation in both hardcopy and softcopy; prepare appropriate change packages resulting from approved RFCs/ECPs; establish a NIMA CM home page and ST/S newsletter (TBR).

- Maintain CM softcopy documentation baseline and prepare change packages, as required, for the following documents:




- Establish the ST/S CM home page and prepare web browser/reader copy of all ST/S CM documentation generated in support of ST/S, as required. This includes the CCB agenda, recommendation and results messages, the CMP.

- Prepare design and layout of ST/S Newsletter, coordinate topics for publication and distribution requirements.

j. CCB Administrative Support:

- Provide CCB administrative support to include preparation of memoranda, reproduction services, preparation and dissemination of both secure and unclassified faxes; distribution/dissemination activities relative to RFCs/ECPs, status reports, documentation, etc.; maintenance of ST/S/CM chronological and archive files; perform coordination activities with security and document control/registry organizations.



FTE Estimates: 15.0