The Central Imagery Office (CIO) and

Rome Laboratory

Joint Requirements Document

for the United States Imagery System (USIS) 2000

Accelerated Architecture Acquisition Initiative (A3I)

Version 1.0

June 24, 1996

CIO-2045

Table of Contents

1.0 Introduction

1.1 Purpose
1.2 Objectives
1.3 Scope
1.4 Applicable Documents
1.4.1 Program Documents
1.4.2 Standards Documents
1.4.3 Reference Documents
1.4.4 Security Documents

2.0 Programmatic Roles and Responsibilities

2.1 CIO
2.1.1 CIO Role
2.1.2 CIO Responsibilities
2.2 Rome Lab
2.2.1 Rome Lab Role
2.2.2 Rome Lab Responsibilities

3.0 Requirements

3.1 A3I Library and Dissemination System Description
3.2 A3I Library and Dissemination System Requirements
3.2.1 Data Management
3.2.2 Format and Compression Schemes
3.2.2.1 Imagery Formats
3.2.2.2 Image-Based Product Formats
3.2.2.3 Imagery and Imagery-Based Compression Schemes
3.2.2.4 Imagery and Imagery-based Product Format Conversion Schemes
3.2.3 Data Storage
3.2.4 Metadata Management Services
3.2.4.1 Metadata Database Maintenance Services
3.2.4.2 Metadata Population Services
3.2.4.3 Metadata Update Service
3.2.4.4 Link Service
3.2.5 Resource Management Services
3.2.5.1 Storage Management
3.2.5.2 Use of Conditions
3.2.5.3 Migration Across Hierarchical Storage
3.2.5.4 Library Service Statistics
3.2.5.5 Unitary Logon
3.2.5.6 Metadata Database Backup
3.2.5.7 Metadata Database Recovery
3.2.6 Data Management Services
3.2.6.1 Import Service
3.2.6.2 Export Service
3.2.6.3 Purge Service
3.2.7 Query Service
3.2.7.14 Browse Service
3.2.7.15 Notification Service
3.2.7.16 Retrieval Service
3.2.7.16.6 Brokered Retrieval Service
3.2.8 Management Services
3.2.9 Profile Service
3.2.10 Century Roll Over
3.2.11 Remote Software Maintenance
3.2.12 Automated Installation Process
3.2.13 On-Line Documentation
3.2.14 Negative Boolean Logic
3.2.15 Hypertext Markup Language (HTML) Interface
3.2.16 NITFS Tag Organization
3.2.17 Operator Help
3.2.18 Backward Compatibility
3.2.19 Commercial Imagery
3.2.20 Automatic Log Off
3.2.21 Interaction with the Host Data Base System (HDBS)
3.2.22 Product Replication
3.2.24 Print Capabilities
3.2.25 Tactical Communications
3.2.26 Communications Server Interface
3.2.27 Performance Throughput
3.2.28 Security Accreditation
3.2.29 Tile Brokering
3.3 Reliability, Maintainability, and Availability
3.4 Training & Demonstrations
3.5 Operations and Maintenance
3.6 Requirements Traceability and Effectivity

4.0 System Verification

4.1 A3I Verification Process
4.2 System Level Verification
4.3 Segment Level Verification

Appendix A - Acronym List

Table of Tables

Table 3.2.2.3.7-1 Compression Schemes
Table 3.2.2.4.1-1 File Format Conversion Matrix
Table 3.6-1 Requirements Traceability and Effectivity Matrix
Table 4.3-1 Requirements Verification Matrix

1.0 Introduction

1.1 Purpose

This document defines the baseline system-level requirements between the Central Imagery Office (CIO) and the Rome Laboratory (Rome Lab) in joint activities required to meet the goals and objectives of the design and development of the Image Product Archive/Library (IPA/IPL) under the United States Imagery Systems (USIS) 2000 initiative.

1.2 Objectives

The objective of this Joint Requirements Document (JRD) is to establish a controlled document which will define the foundation of high level requirements that Rome Lab, under the guidance and direction of the CIO, will be responsible for in the development of the IPA/IPL under the Library, Dissemination and Management elements of the USIS.

1.3 Scope

This document contains the requirements for the joint activities of CIO and Rome Lab pertaining to the system development of the IPA and the IPL under the Library, Dissemination and Management elements of the USIS.

1.4 Applicable Documents

1.4.1 Program Documents

The following documents of exact issue shown (identified by revision letter, date, change notice, etc., as applicable) form the applicable program documents in the development as of the IPL in accordance with the requirements herein. In the event of conflict between the documents referenced herein and the contents of this JRD, the contents of this JRD shall be considered a superseding requirement.

1.4.2 Standards Documents

The following documents of exact issue shown (identified by revision letter, date, change notice, etc., as applicable) form the applicable non-program documents in the development of the IPL in accordance with the requirements herein. In the event of conflict between the documents referenced herein and the contents of this JRD, the contents of this JRD shall be considered a superseding requirement.

1.4.3 Reference Documents

The following documents form the applicable reference documents in the development of the IPL in accordance with the requirements herein. In the event of conflict between the documents referenced herein and the contents of this JRD, the contents of this JRD shall be considered a superseding requirement.

1.4.4 Security Documents

The following documents form the applicable security documents in the development of the IPL in accordance with the requirements herein. In the event of conflict between the documents referenced herein and the contents of this JRD, the contents of this JRD shall be considered a superseding requirement.

2.0 Programmatic Roles and Responsibilities

The following section detail the key USIS programmatic roles and responsibilities allocated to both CIO and Rome Lab.

2.1 CIO

2.1.1 CIO Role

The CIO role is that of the USIS functional architect and A3I project integrator. As such, the CIO shall provide mitigation and configuration management for the A3I interfaces.

2.1.2 CIO Responsibilities

CIO will provide integration across government development organizations, initiatives, and targets of the USIS. The program milestones will determine the development organization's schedules. Periodic reviews will be accomplished IAW Department of Defense (DoD) Directive 5000 guidelines.

CIO will provide a forum for, and will host, periodic meetings.

CIO will coordinate demonstration activities.

CIO will coordinate activity across the A3I community through program milestones and reviews.

CIO will provide organizational, functional, and performance requirements for the distributed archives.

CIO will determine and provide security policy for archive and dissemination operations at the lowest security level possible.

CIO will be a voting member at site-related transition readiness reviews.

CIO will be a voting member on all program status reviews, expectancy tests, and source selection evaluation review associated with the IPA/IPL program. The CIO reserves the right to waive this requirement on a case by case basis.

CIO will provide USIS funding to Rome Lab for IPA/IPL development.

2.2 Rome Lab

2.2.1 Rome Lab Role

The Rome Lab role is to provide acquisition and programmatic oversight to ensure the development of the IPA and the IPL is consistent with the A3I Requirements Document (ARD), the CIO-Rome Lab JRD, as well as USIS Standards and Guidelines. Rome Lab shall also participate in risk mitigation and configuration management.

2.2.2 Rome Lab Responsibilities

Rome Lab will develop a Life Cycle Plan, detailing aspects of operations and maintenance; software metrics and full operational capability (FOC) through the end of 2001.

Rome Lab will define project(s) execution budgets across fiscal years.

Rome Lab will perform selection of contractors for IPL development and acquisition.

Rome Lab will structure an evolutionary design approach providing incremental capabilities through the end of 2001, incorporating Commercial Off the Shelf (COTS) solutions into the design where applicable.

Rome Lab will identify issues and risk areas to CIO.

Rome Lab will coordinate risk reduction work-off plans and status with CIO.

Rome Lab has executive agency to ensure the development of an A3I Client in close coordination with the CIL/NIL Program Office.

3.0 Requirements

3.1 A3I Library and Dissemination System Description

A3I Libraries are composed of three types: Product, Command, and National. The three types are differentiated by content, storage size, performance, and responsibility for operations and management. They are alike in that each type may contain digital imagery or digital imagery products from all sources including tactical, theater, national, civil, and commercial collection systems. All libraries share common digital imagery standards.

Image Product Libraries (IPLs) contain shared, restricted, or both types of data. IPLs shall be based upon the existing Demand Driven Direct Digital Dissemination (5D) and the Imagery Product Archive (IPA) capabilities, scaled for size and performance, and some shall be portable. IPLs support various levels of commands, Common Imagery Ground/Surface System (CIGSS) sites, and other organizations outside the command structure of the services, that require the use of libraries.

3.2 A3I Library and Dissemination System Requirements

The IPL (beginning with IPA version 1.2.2) functional requirements baseline shall be developed based on the IPA Requirements Document for the Pilot A3I, Revision C, dated 12 July 1995 in addition to the following requirements:

3.2.1 Data Management

3.2.1.1 The IPA/IPL shall store and manage metadata for each image and imagery product stored in the IPA/IPL.

3.2.1.2 The IPA/IPL shall be capable of importing, storing, managing and exporting processed tactical, theater, national, civil, and commercial imagery and imagery-based products.

3.2.1.3 The IPA/IPL shall be capable of importing, storing, exporting and managing imagery and image-based products.

3.2.1.4 The IPA/IPL shall provide a limited capability to import, store, export and query DMA Metadata and products in standard raster product format, standard vector product format, and Digital Terrain and Elevation Data (DTED) format.

3.2.1.5 The IPA/IPL shall have the capability to create and/or store Reduced Resolution Data Sets (RRDS) for all archived, unexploited imagery.

3.2.1.6 The IPA/IPL shall be able to import, store, manage, and export standalone thumbnail and/or metadata files.

3.2.1.7 The IPA/IPL upon request, shall have the capability of generating an R5 overview of stored unexploited imagery.

3.2.1.8 The IPA/IPL shall import, store, manage and export, video (to include Predator and other video).

3.2.2 Format and Compression Schemes

3.2.2.1 Imagery Formats

3.2.2.1.1 The IPA/IPL shall be capable of importing and exporting imagery in the Tape Format Requirement Documents (TFRD).

3.2.2.1.2 The IPA/IPL shall be capable of importing and exporting imagery in National Imagery Transmission Format (NITF) Version 2.0.

3.2.2.2 Image-Based Product Formats

3.2.2.2.1 The IPA/IPL shall be capable of importing and exporting image-based products in National Imagery Transmission Format (NITF) Version 2.0.

3.2.2.2.2 The IPA/IPL shall be capable of importing and exporting image-based products in Tagged Image File Format (TIFF) Version 6.0.

3.2.2.2.3 The IPA/IPL shall be capable of importing and exporting image-based products in Sun Raster.

3.2.2.2.4 The IPA/IPL shall be capable of importing and exporting image-based products in Graphic Interchange Format (GIF).

3.2.2.2.5 The IPA/IPL shall be capable of importing and exporting image-based products in postscript format.

3.2.2.2.6 The IPA/IPL shall be capable of importing image-based products from the Kodak 7700 format.

3.2.2.3 Imagery and Imagery-Based Compression Schemes

3.2.2.3.1 The IPA/IPL shall be capable of importing and exporting imagery compressed using the 4.3 bpp Differential Pulse Code Modulation (DPCM) as documented in the Tape Format Requirements Document (TFRD).

3.2.2.3.2 The IPA/IPL shall be capable of importing and exporting imagery compressed using the 2.3 bpp Discrete Cosine Transfer (DCT) as documented in the TFRD.

3.2.2.3.3 The IPA/IPL shall be capable of importing and exporting imagery compressed using the 1.29 bpp DCT as documented in the TFRD.

3.2.2.3.4 The IPA/IPL shall be capable of importing and exporting image-based products compressed using Joint Photographic Experts Group (JPEG) 8 and 12 bit JPEG for those formats that are compatible.

3.2.2.3.5 The IPA/IPL shall be capable of importing and exporting uncompressed imagery.

3.2.2.3.6The IPA/IPL shall provide the capability to compress thumbnails on the IPA Server and decompress thumbnails on the IPA Client.

3.2.2.3.7 The IPA/IPL will support these compression schemes with respect to imagery and imagery-based product formats, as well as Thumbnail (TN) and Overview (OV) creation in accordance with the following table:

Table 3.2.2.3.7-1 Compression Schemes

3.2.2.4 Imagery and Imagery-based Product Format Conversion Schemes

3.2.2.4.1 The IPA/IPL shall support imagery file format conversion (To/From) in accordance with the following table:

Table 3.2.2.4.1-1 File Format Conversion Matrix

3.2.3 Data Storage

3.2.3.1 The IPA/IPL shall have the capability to retain digital imagery data in on-line, near-line, and off-line storage media. Each IPA/IPL shall maintain a catalog populated with metadata of its imagery and imagery product holdings.

3.2.3.2 The IPA/IPL shall have the hardware/software capability to retain digital imagery data on-line.

3.2.3.3 The IPA/IPL shall be designed to allow for image data transfer, retrieval, and management to/from an external, near-line storage device (i.e., tape tower, Jukebox).

3.2.3.4 The IPA/IPL shall have a hardware/software capability to allow for image data transfer, retrieval, and management to/from off-line tape/CD media.

3.2.3.5 The IPA/IPL shall maintain a catalog populated with the metadata of its archived imagery to include on-line, near-line & off-line holdings.

3.2.3.6 The IPA/IPL catalog will also contain all metadata transferred to the IPA/IPL as standalone files from external library sources.

Continue....


This Code Created by John Pike
Maintained by K. Merrill (Science Applications International Corporation)