NATIONAL IMAGERY & MAPPING AGENCY
(NIMA)
(NSES)
1 JULY 1997
Technical Letter of Direction
(Project Description/Objective)
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
TABLE OF CONTENTS
ITEM DESCRIPTION PAGE
1.0 ARCHITECTURE OFFICE 5
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.0 SYSTEMS ENGINEERING AND INTEGRATION OFFICE 8
2.1 Interoperability Standards .................................................................. 9
2.2 USIGS Architecture Support .............................................................. 10
2.3 Systems Integration ............................................................................. 12
3.0 INFORMATION MANAGEMENT SYSTEMS OFFICE 13
3.1 Program Engineering & Program Control ......................................... 13
3.2 Requirements Management System (RMS) ....................................... 16
3.3 Integrated Information Management (IIM). ..................................... 19
4.0 ARCHIVE & DISSEMINATION OFFICE 21
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.0 EXPLOITATION MANAGEMENT OFFICE 34
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
6.0 REQUIREMENTS OFFICE AND RESOURCE
AND PROGRAMS OFFICE 62
7.0 TECHNICAL DIRECTORATE
7.1 Project Information Management (PIM) .......................................... 65
8.0 RESEARCH and DEVELOPMENT OFFICE 66
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.0 R&D PLANS & PROGRAM OFFICE 71
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.0 INTERNATIONAL PROGRAMS OFFICE 79
10.1 International Arrangements .............................................................. 79
10.2 International Customer Support ....................................................... 79
11.0 TERRAIN MODELING PROJECT OFFICE 83
11.1 Reverse Engineering and Modeling ................................................... 83
11.2 Terrain Domain Resource Repository ............................................... 83
11.3 Dynamic Representation .................................................................... 84
11.4 TEMPO .............................................................................................. 85
12.0 TECHNOLOGY ASSESSMENT & INSERTION OFFICE 86
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.0 PLANS PROGRAMS AND ANALYSIS OFFICE 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.0 NETWORK AND ENTERPRISE SYSTEMS OFFICE 93
14.2 Network and Enterprise Systems Office Support ............................ 93
14.2 NIMA Enterprise Network (NEN) ................................................... 93
14.3 Other Duties ......................................................................................
15.0 MULTI-SERVICES OFFICE 96
15.1 System Test and Verification ............................................................ 96
15.2 Engineering Review Broad ............................................................... 97
16.0 NSES Program Management ............................................................ 102
1.0 ARCHITECTURE OFFICE (AR)
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.
1.0.2.1 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)
1.0.2.2 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 SYSTEMS ENGINEERING AND INTEGRATION OFFICE (SE)
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)
- 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.
- 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.0 INFORMATION MANAGEMENT SYSTEMS OFFICE
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
a. CONOPS
b. RFCs
c. Integrated Schedules
Government and Contractor negotiated format and content.
4.0 ARCHIVE & DISSEMINATION OFFICE
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
NIMA.
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.0 EXPLOITATION MANAGEMENT OFFICE
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
c. CONOPS
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.
5.9 RULER
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.
- 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.
5.10 NATIONAL EXPLOITATION SYSTEM (NES)
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
Government and Contractor negotiated content and format.
5.11 FRONT-END PROCESSING ENVIRONMENT (FPE)
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.
5.14 NIMA SOFTCOPY
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.
b. DCAFE
- 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.
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