The National Imagery and Mapping Agency (NIMA) and

Rome Laboratory

Joint Requirements Document

for the United States Imagery and Geospatial

Information System (USIGS) 2000

Accelerated Architecture Acquisition Initiative (A3I)

Version 1.1

March 25, 1997

NRLJRD

1. Introduction

1.1. Purpose

This document defines the baseline system-level requirements between the National Imagery and Mapping Agency (NIMA) 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 Library (IPL) under the United States Imagery and Geospatial Information Systems (USIGS) 2000 initiative. (note: This JRD is available via the Internet under the "Documentation" portion of the IPA/IPL Program Office Home Page at http://web1.irr.rl.af.mil/ipl/)

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 NIMA, will be responsible for in the development of the IPL under the Library, Dissemination and Management elements of the USIGS.

1.3. Scope

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

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.

CIO/Rome Lab Memorandum of Understanding (MOU), dated 25 September 1995

Image Product Archive (IPA) Requirements Document for the Pilot A3I, Revision C, dated 12 July 1995

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.

Military Standard for Software Development and Documentation (MIL-STD-498) dated 5 December 1994 (note: MIL-STD-498 is available via the Internet at http://diamond.spawar.navy.mil/498/mil-498.html)

Computer Graphics Metafile (CGM) Implementation Standard for the National Imagery Transmission Format Standard (NITFS), MIL-STD-2301, 18 June 1993, with Change Notice 1, dated 12 October 1994

Joint Photographic Experts Group (JPEG) for the National Imagery Transmission Format Standard (NITFS), MIL-STD-188-198A, 15 December 1993, with Change Notice 1, dated 12 October 1994

National Imagery Transmission Format (NITF) (Version 2.0) for the National Image Transmission Format Standard (NITFS), MIL-STD-2500A, 12 October 1994 (note: The NITF specification, and related documentation is available via the Internet at http://www.cio.dma.gov/nitfs/)

Military Handbook for the National Imagery Transmission Format Standard (NITFS), MIL-HDBK-1300A, 12 October 1994

National Imagery Transmission Format Standard Profile for Imagery Archive Extensions (NITFS PIAE), Version 2.0, 25 April 1996

USIGS Standards and Guidelines, Update 2 (CIO-2008), dated 12 April 1996

USIGS Standards Profile for Imagery Archives (SPIA), Version 1.0, dated 20 July 1994

USIGS Standards Profile for Image Distribution (SPID) (CIO-2019), Version 1.0, dated 20 July 1994

Common Imagery Interoperability Profile (CIIP) for Imagery Access (CIO-2069), dated 24 June 1996

Defense Information Infrastructure (DII) Common Operating Environment (COE) Integration & Run Time Specification (I&RTS) Preliminary - Version 2.0, dated 23 October 1995

Support Data Extensions (SDE) (Version 1.1) for the National Imagery Transmission Format (Version 2.0) of the Standard (NITFS), of the National Imagery Transmission Format Standard (NITFS), (CIO-2047), TCS-037-011/95, dated 15 April 1995

Airborne Synthetic Aperture Radar (SAR) Support Data Extensions (SDE) for the National Imagery Transmission Format (Version 2.0) of the National Imagery Transmission Format Standards, Version 0.9, dated 20 May 1996

Capstone Test and Evaluation Master Plan (TEMP) for the Accelerated Architecture Acquisition Initiative (A3I), (CIO-2039), dated 1 July 1996 (DRAFT)

Tape Format Requirements Document S2025P (TFRD) (BA93-02767), TCS-005B-BA02767-93

Common Imagery Ground/Surface System (CIGSS) Acquisition Standards Handbook (CIGSS-Hdbk), Ver. 1.0. dated 19 July 1995

Tagged Image File Format (TIFF) Version 6.0

JIEO Circular 9008, dated 30 June 1993

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.

A3I Requirements Document (ARD) Revision 2 (CIO-2054), dated 7 May 1996

A3I User's Concept of Operations (CONOPS), (CIO-2052), dated 10 October 1995

USIS Management Plan, Version 3 (CIO-2000), dated 12 April 1996

USIS Objective Architecture Definition and Evolution, Version 3 (CIO-2003), dated 12 April 1996

USIS Technical Architecture Requirements, (TARD), Version 3, (CIO-2004) dated 12 April 1996

USIS 2000 (Target 1) Concept of Operations, (CIO-2065), Version 3.0, dated 12 April 1996

National Image Transmission Format Implementation Requirements Document (NITFIRD), S2035A, TCS055B-BA00039-95

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.

Director of Central Intelligence Directive (DCID) 1/16, Security Policy for Uniform Protection of Intelligence Processed in Automated Information Systems and Networks, dated 19 July 1988

DoD Directive 5200.28, DoD Trusted Computer System Evaluation Criteria, dated December 1985

Defense Intelligence Agency Manual (DIAM) 50-4, Security of Compartmented Computer Operations, dated 24 June 1980

Security Requirements for System High and Compartmented Mode Workstations, DDS 2600-5502-87, dated November 1987

CIO Security Policy Manual for the Accelerated Architecture Acquisition Initiative (A3I), dated 30 September 1995

2. Programmatic Roles and Responsibilities

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

2.1. NIMA

2.1.1. NIMA Role

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

2.1.2. NIMA Responsibilities

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

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

NIMA will coordinate demonstration activities.

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

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

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

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

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

NIMA will provide USIGS funding to Rome Lab for 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 IPL is consistent with the A3I Requirements Document (ARD), the NIMA-Rome Lab JRD, as well as USIGS 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 NIMA.

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

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

Rome Lab will develop a Test and Evaluation Master Plan (TEMP) for RL support of A3I A3I development efforts and provide to NIMA/APMO in accordance with the A3I TEMP.

3. System 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 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 IPL shall be capable of importing, storing, exporting and managing imagery, image-based products, and associated metadata.
3.2.1.2. The imagery and imagery based products shall consist oftactical, theater, national, civil, and commercial imagery and imagery-based products.
3.2.1.3. The IPL shall be able to import, store, manage, and export standalone metadata files associated with off-line imagery; containing zero, one, or multiple (e.g. gallery) thumbnails .
3.2.1.4. The IPL shall have the capability to handle multi-file NITFS 2.0 products as follows:

a. Generate thumbnails for each of the image files.

b. Allow for selective retrieval of each image files contained in the multi-file.

3.2.2. Format and Compression Schemes

3.2.2.1. Imagery Formats

3.2.2.1.1. The IPL shall be capable of importing, exporting, storing and cataloging imagery in the Tape Format Requirement Documents (TFRD).
3.2.2.1.2. The IPL shall be capable of importing, exporting, storing and cataloging imagery in National Imagery Transmission Format (NITF) Version 1.1.
3.2.2.1.3. The IPL shall be capable of importing, exporting, storing and cataloging imagery in National Imagery Transmission Format (NITF) Version 2.0.
3.2.2.1.4. The IPL shall be capable of importing, exporting, storing and cataloging digital video imagery in the Motion Picture Experts Group (MPEG) 2 format as specified in the USIGS Standards and Guidelines. (note: The most current information about the Imagery Standards Management Committees (ISMC) efforts with regard to video format and metadata standardization and related documentation is available via the Internet at http://www-ismc.itsi.disa.mil/video/vwg.html)

3.2.2.2. Image-Based Product Formats

3.2.2.2.1. The IPL shall be capable of importing, exporting, storing and cataloging image-based products in National Imagery Transmission Format (NITF) Version 1.1.
3.2.2.2.2. The IPL shall be capable of importing, exporting, storing and cataloging image-based products in National Imagery Transmission Format (NITF) Version 2.0.
3.2.2.2.3. The IPL shall be capable of importing, exporting, storing and cataloging image-based products in Tagged Image File Format (TIFF) Version 6.0 when accompanied with an associated IPL data file.
3.2.2.2.4. The IPL shall be capable of importing, exporting, storing and cataloging image-based products in Sun Raster when accompanied with an associated IPL data file.
3.2.2.2.5. The IPL shall be capable of importing, exporting, storing and cataloging image-based products in Graphic Interchange Format (GIF) when accompanied with an associated IPL data file.
3.2.2.2.6. The IPL shall be capable of exporting image-based products in postscript format.
3.2.2.2.7. The IPL shall be capable of importing image-based products utilizing the Kodak 7700 interface.
3.2.2.2.8. The IPL shall provide a limited capability to import, store, export and query MC&G Metadata and products in Standard Raster Product (SRP) format, Standard Vector Product (SVP) format, and associated Digital Terrain and Elevation Data (DTED).

3.2.2.3. Imagery and Imagery-Based Compression Schemes

3.2.2.3.1. The IPL shall be capable of importing, exporting, storing and cataloging 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 IPL shall be capable of importing, exporting, storing and cataloging imagery compressed using the 2.3 bpp Discrete Cosine Transfer (DCT) as documented in the TFRD.
3.2.2.3.3. The IPL shall be capable of importing, exporting, storing and cataloging imagery compressed using the 1.29 bpp DCT as documented in the TFRD.
3.2.2.3.4. The IPL shall be capable of importing, exporting, storing and cataloging image-based products compressed using Joint Photographic Experts Group (JPEG) 8, 12, and 24 bit color JPEG for those formats that are compatible.
3.2.2.3.5. The IPL shall be capable of importing, exporting, storing and cataloging imagery utilizing Adaptive Recursive Interpretive Differential Pulse Code Modulation (ARIDPCM) compression.
3.2.2.3.6. The IPL shall be capable of importing, exporting, storing and cataloging uncompressed imagery.
3.2.2.3.7. The IPL shall provide the capability to compress thumbnails on the IPA Server and decompress thumbnails on the IPA Client
3.2.2.3.8. The IPL will support these compression schemes with respect to imagery and imagery-based product formats, as well as 256 by 256 pixel Thumbnail (TN) and Overview (typically 1K by 1K) (OV) creation in accordance with the following table:
                                       COMPRESSIONS                     
                   ARID-  8 BIT    12     24     4.3     2.3   1.29    VQ   TN   OV  
                    PCM    JPEG    BIT    BIT    DPCM    DCT    DCT                  
                                  JPEG   JPEG                                        
  F     NITF 1.1     Y      N       N      Y      N       N      N     N    Y    N   
  O    NITF 2.0      N      Y       Y      Y      N       N      N     N    Y    Y   
  R     TIFF 6.0     N      N       N      N      N       N      N     N    Y    N   
  M    Sun Raster    N      N       N      N      N       N      N     N    Y    N   
  A       TFRD       N      N       N      N      Y       Y      Y     N    Y    Y   
  T       GIF        N      N       N      N      N       N      N     N    Y    N   
  S    Postscript    N      N       N      N      N       N      N     N    Y    N   
          SRP        N      N       N      N      N       N      N     Y    Y    Y   
          SVP        N      N       N      N      N       N      N     Y    Y    Y   
         MPEG 2      N      N       N      N      N       N      N     N    N    N   

Table 3.2.2.3.8-1 Compression Schemes

3.2.2.4. Imagery and Imagery-based Product Format Conversion Schemes

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

     FORMATS    NITF   NITF   TIFF   Sun    TFRD   XL     GIF  Post-    SRP    SVP  
                 1.1    2.0   6.0   Raste         7700         script               
                                      r                                             
    NITF 1.1     N/A     Y     Y      Y      N      N     N      N       N     N    
     NITF 2.0     N     N/A    Y      Y      N      N     N      N       N     N    
F    TIFF 6.0     Y      Y    N/A     Y      N      N     N      N       N     N    
R   Sun Raster    Y      Y     Y     N/A     N      N     N      N       N     N    
O      TFRD       N      Y     N      N     N/A     N     N      N       N     N    
M     XL7700      N      Y     N      N      N     N/A    N      N       N     N    
       GIF        N      N     N      N      N      N    N/A     N       N     N    
    Postscript    N      N     N      N      N      N     N     N/A      N     N    
       SRP        N      N     N      N      N      N     N      N      N/A    N    
       SVP        N      N     N      N      N      N     N      N       N    N/A   

NOTE: N/A = Not Applicable

Table 3.2.2.4.1-1 File Format Conversion Matrix

3.2.3. Data Storage

3.2.3.1. The IPL shall have the capability to retain digital imagery data in on-line, near-line, and off-line storage media. Each IPL shall maintain a catalog populated with metadata of its imagery and imagery product holdings.
3.2.3.2. The IPL shall have the hardware/software capability to retain digital imagery data on-line.
3.2.3.3. The 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 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 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 IPL catalog will also contain all metadata transferred to the IPL as standalone files from external library sources.
3.2.3.7. The IPL shall be capable of selectively placing off-line the total product database.

3.2.4. Metadata Management Services

The IPL shall provide metadata management services.

3.2.4.1. Metadata Database Maintenance Services

3.2.4.1.1. The IPL shall provide Metadata Database Maintenance Services that provide functionality to populate, update, and link metadata items.

3.2.4.2. Metadata Population Services

3.2.4.2.1. The IPL shall have a Metadata Population Service.
3.2.4.2.2. The IPL Metadata Population Service shall provide the capability to accept, parse, and index metadata.
3.2.4.2.3. The IPL Metadata Population Service shall provide the capability to accept, parse, and index metadata as input in a metadata formatted file (i.e., DIA provided commercial/foriegn imagery metadata).
3.2.4.2.4. The IPL shall validate the metadata of incoming items.
3.2.4.2.5. The IPL will have the capability to allow users to create validation tables, against both global and product specific metadata element values and ranges, that will allow configuration control and/or filtering of product input to the server.
3.2.4.2.5.1. The filter tables shall be created, implemented or modified by a site manager within an IPL provided library management application interface.
3.2.4.2.5.2. The filter tables will have the capability to be saved and file transfered to other IPL servers for implementation.
3.2.4.2.5.3. Products that fail filter table validations can initiate the following kinds of user selected server actions:
a. Move to Problem Records (typically a data error)

b. Discard (Outside of Users Area of Interest)

3.2.4.3. Metadata Update Service

3.2.4.3.1. The IPL Metadata Update Service shall provide the capability to update metadata index entries upon storage state changes such as purge and migrate upon accepting metadata entries.
3.2.4.3.2. The IPL server shall provide the capability to utilize Host Data Base System (HDBS) Installation Identification Elements (IIE) data to autopopulate user-specified imported imagery products.

3.2.4.4. Association Folders

3.2.4.4.1. The IPL shall provide the users the capability to create, maintain, and navigate (i.e. browse) "Association Folders" wherein metadata linkages among images and products are stored. Example of such Association folders include, but are not limited to, Target Folders, Topic Folders, Equipment Folders, Event Folders, Order of Battle Folders, and Person Folders, wherein metadata linkages to images and products related to the subject of the folder can be maintained.
3.2.4.4.2. The IPL User Association Folders will group metadata pointers to imagery and products of special interest to a user or group of users.
3.2.4.4.3. The IPL users shall have the capability to review and edit the pointer lingages within the Association Folders.
3.2.4.4.4. The IPL users shall have the ability to share Association Folders that they have created. For example, a member of a counter-terrorist team may desire to share a Person Folder with other team members.
3.2.4.4.5. Creators of shared Association Folders shall be given the ability to set the folder to "read only" or "read/write" permissions for other users who are given access.
3.2.4.4.6. The IPL shall provide the users with the capability to use the Association Folders in conjunction with the different aplications to query, browse, import, and export images or image-based products.

3.2.5. Resource Management Services

3.2.5.1. Storage Management

3.2.5.1.1. The IPL Resource Management Services shall provide the IPL Manager the capability to monitor data on available storage space, and to manage it on-line.
3.2.5.1.2. The IPL shall provide the capability to partition/restrict access to metadata and image files by user-defined criteria.

3.2.5.2. Migration Across Hierarchical Storage

3.2.5.2.1. The IPL Resource Management Services shall provide the capability to manage the migration of data across hierarchical storage devices.
3.2.5.2.2. The IPL Resource Management Services shall provide the capability to automatically migrate data across its hierarchical storage devices.
3.2.5.2.3. The IPL shall provide the capability to migrate data across hierarchical storage devices based on age of data, frequency of retrieval, date of last retrieval, and user selected metadata elements.
3.2.5.2.4. The IPL shall provide the capability for an operator to manually migrate data across the hierarchical storage devices.

3.2.5.3. Library Service Statistics

The IPL Resource Management Services shall provide the capability to compile statistics on library services.

3.2.5.4. Unitary Logon

The IPL Resource Management Services shall provide for a unitary logon for shared data into the A3I libraries. Unitary logon allows the users of a library trusted access, via the user's home server, to other libraries in the A3I network.

3.2.5.5. Automatic Logoff

The IPL shall have the capability of automatically logging off inactive users after a programmable time-out period.

3.2.5.6. Metadata Database Backup

The IPL Resource Management Services shall provide for metadata database backup.

3.2.5.7. Metadata Database Recovery

The IPL Resource Management Services shall provide for metadata database recovery.

3.2.6. Data Management Services

The IPL shall provide Data Management Services to manage import, export, and purging of imagery and imagery products.

3.2.6.1. Import Service

3.2.6.1.1. The IPL Import Service shall provide the capability to allow storage of imagery and image-based products in the libraries either manually or automatically.
3.2.6.1.2. The IPL Import Service shall provide an Application Program Interface (API) for both a graphical and a keyboard interface to support user specifications of metadata to be populated into a library.
3.2.6.1.3. The IPL Import Service shall provide the capability to import and archive images and image products from both CD and magnetic media.
3.2.6.1.4. The IPL import service shall be capable of selected metadata field population for imported image files based on the source (i.e., IP address) of the imported file.
3.2.6.1.5. The IPL Import Service will support the generation of a thumbnail for each archived image (or image product) imported in the following formats: NITF 1.1, NITF 2.0, TFRD, TIFF 6.0, GIF, and Sun Raster. The thumbnail will be linked to the associated image metadata for use by the IPL Query/Browse service.

3.2.6.2. Export Service

3.2.6.2.1. The IPL Export Service shall support requests to copy an entire image or image-based product as a fileor an image subset as a file-based image extraction from a library into user-specified location. Image subsets can be extracted from only those imagery files that provide Exploitation Support Data (ESD) metadata.
3.2.6.2.2. The IPL Export Service shall provide an API for both a graphical and a keyboard interface to support user specification of data to be retrieved from the NIL, CILs, and IPLs.
3.2.6.2.3. The IPL Export Service shall support user identification of file format, and compression of data to be exported from a library.
3.2.6.2.4. The IPL Export Service shall allow the exporting of imagery, or a portion of an image (image chip), based on a user defined "stretchy box" overlaid on a map or image.
3.2.6.2.5. The IPL shall allow the exporting of imagery, or a portion of an image (image chip) to COTS/GOTS tile brokering software.
3.2.6.2.6. The IPL shall allow the user to identify the Reduced Resolution Data Set (RRDS) of unexploited imagery to be exported from the library.

3.2.6.3. Purge Service

3.2.6.3.1. The IPL Purge Service shall provide the capability to remove imagery and related metadata from library storage.
3.2.6.3.2. The IPL Purge Service capability shall be established based on user selected metadata elements , frequency of retrieval, linkage to other items, and date of last retrieval.
3.2.6.3.3. The IPL Purge Service shall provide the capability to sever the links between the purged item and any linked item.

3.2.7. Query Service

3.2.7.1. The IPL shall provide a Query Service which provides interface to support user queries and aggregates query responses. The Query Service provides the capability for users to submit queries to a local library or to search multiple A3I libraries based on specific metadata attributes associated with the needed image products, using either positive or negative logic query quantifiers.
3.2.7.2. The IPL Query Service shall support user discovery of imagery and/or image-based products that meet specified query criteria or parameters by providing a list of image product file(s) that meet the parameters of the clients query and the library location of said file(s).
3.2.7.3. The IPL Query Service shall provide the capability for users to specify whether queries are submitted to all, some, or one IPL.
3.2.7.4. The IPL Query Service shall provide an API for both a graphical and a keyboard interface to support user queries.
3.2.7.5. The IPL Query Service graphical and keyboard interfaces shall support associative queries to define a set of imagery or image-based products based on a subset of image attributes as defined in the Standards Profile for Imagery Archives as augmented by the CIIP (e.g.) target identifier, target name, date, country code, mission number.
3.2.7.6. The IPL Query Service graphical and keyboard interfaces shall support navigational queries to define a set of imagery or imagery-based products based on relative temporal or geo-spatial image characteristics.
3.2.7.7. The IPL Query Service shall have the capability to aggregate the query responses and return the aggregate as a single response to the client.
3.2.7.8. The IPL Query Service shall provide a user the capability to request the termination of an ongoing search before it completes.
3.2.7.9. Query termination shall be capable of being specified based on user-specified elapsed time, the number of item satisfying the query options, or the manual intervention of the user.
3.2.7.10. The IPL Query Service shall provide the capability to aggregate the completed query responses and return the aggregate as specified by the user when the search is prematurely terminated.
3.2.7.11. The IPL boolean logic shall include negative logic to support all queryable IPA elements.
3.2.7.12. Browse Service

3.2.7.12.1. The IPL shall provide a Browse Service to support a user's interactive review of data such as that returned in a query response. This data includes thumbnail overviews of images, imagery products, or metadata associated with the imagery or imagery product.
3.2.7.12.2. The IPL Browse Service shall present thumbnail overviews (sub-sample imagery pixels, or textual) of images or image-based products in the query result.
3.2.7.12.3. The IPL Browse Service will provide the following view capabilities and options/defaults for query responses:
a. Return/not return thumbnails.

b. Compress/not compress thumbnails.

c. Thumbnail type:

- Individual ((1) thumbnail associated with (1) returned file)

- Multiple return simultaneous display (Thumbnail Gallery)

- Single return with multiple thumbnails (Multi-Spectrum Gallery)

d. Provide a map footprint option of the browsed product by providing the returned corner coordinate metadata to a library providing map application.

e. Allow the client to sort and arrange (by column & row) the display of metadata that satisfied the query.

f. Allow the client to view all metadata fields associated with the returned image file.

g. Allow the client to print or save

- The query list of image files

- The complete metadata display for a returned image file

h. Allow the client to retrieve/pull the full image being browsed.

i. Allow the client to retrieve & view the R5 linked overview, if available, for FAF/sub scene extraction (via export services).

j. Allow the Client to direct the Server to implement user provided software (i.e. MC&G) to aggregate multiple maps (satisfying a geo-query) into a single map product for retrieval.

3.2.7.12.4. Brokered Retrieval Service
3.2.7.12.4.1. The IPL Retrieval Service shall provide a brokering capability between a user and multiple libraries that contain requested imagery or imagery products such that the retrieval is directed to a library that provides potentially, the most timely response.
3.2.7.12.4.2. The IPL Retrieval Service shall accept a Library Retrieval Request that identifies the items and the libraries at which the requested items are stored.
3.2.7.12.4.3. The IPL Retrieval Service shall allow the user to select the library from which the requested item is to be retrieved based on :image product file size and communications capacity available.

3.2.8. System Management Services

3.2.8.1. The IPL shall provide administrators with the ability to monitor and effect the use and behavior of its internal data, storage, and processing resources.
3.2.8.2. Each IPL shall provide a System Administrative Service to support initialization, operation, and shutdown.
3.2.8.3. Each IPL shall provide a Performance Management Service to measure, predict, and optimize its performance over time.
3.2.8.4. The IPL Server and Client will support remote diagnostics and maintenance efforts. The IPL Server and
3.2.8.5. Client shall support remote downloading of software updates from the IPL Customer Service Center (ICSC).

3.2.9. Profile Service

3.2.9.1. The IPL shall have the capability to allow IPL users the capability to easily create notification and/or retrieval profiles and support the registration and management of these profiles at any single or multiple IPL servers.
3.2.9.2. Notification and Retrieval profiles will be based on query (metadata) attributes as defined in the Common Imagery Interoperability Profile (CIIP).
3.2.9.3. Profile strategies supported by the IPL server shall be the same as the query strategies available to clients (i.e. geo-coordinates), Boolean condition statements, wild carding, etc.)
3.2.9.4. Notification and Retrieval profiles shall be easily created, or modified by a client or IPL manager within a simple, interactive, GUI or text base (form) interface.
3.2.9.5. The Notification and Retrieval profiles will have the capability to be saved (templates) for later use.
3.2.9.6. Notification and Retrieval profiles shall have the ability to specify an activation/deactivation time period for the profile.
3.2.9.7. The IPL will have the ability to share saved Notification & Retrieval profiles with other users at other A3I Libraries.
3.2.9.8. The IPL shall accept externally generated profiles.
3.2.9.9. Notification Profiles

3.2.9.9.1. The IPL Notification Service shall alert the user when new imagery or imagery products that satisfy a given profile's criteria are available for access from imagery libraries.
3.2.9.9.2. Product Notification to users will include the library location, and library specific product ID for each item falling within a user's profile conditions.
3.2.9.9.3. Product Notification to users will include user specified partial or full metadata display schema (i.e., "include metadata that matched the profile conditions", or "include thumbnail with notification", etc.)
3.2.9.9.4. Product Notification to user will include the ability to easily select and request a product being notified from the notification screen/pane.
3.2.9.9.5. The IPL Notification Service shall provide the user the capability to specify the frequency of notification.
3.2.9.9.6. The IPL Notification Service shall provide the capability to specify that notification shall occur at client log-on or at a specific time of day.
3.2.9.9.7. Notification at sign-on shall include new imagery and imagery products since last log-off.

3.2.9.10. Retrieval Profiles

3.2.9.10.1. The IPL Profile Service shall identify and deliver (retrieve) images or image products that meet retrieval profile parameters automatically to the profiled user.
3.2.9.10.2. The IPL Profile Service shall deliver retrieved products to the user destination provided in the profile.
3.2.9.10.3. The IPL Profile Service shall deliver retrieved products in the user desired format/compression/resolution provided in the profile.
3.2.9.10.4. The IPL Profile Service shall contain the capability that provides delivery and profile unification as follows:
3.2.9.10.4.1. Delivery Unification - The unified delivery of products aggregated by recipient or group of recipients. The Library shall aggregate for unified delivery, products that meet a given profile for a given user, or group of users, over a user specified time frame. (For example, user (or user group) A, in his/her profile, shall have the capability to specify that hits against profile XYZ be saved until the user-specified period has been satisfied and then be sent to A as multiple products in a single data package at the end of the specified time period.)
3.2.9.10.4.2. Profile Unification - The aggregation of identical profiles from different users to create a user group. The IPL shall provide the capability to identify and unify identical profiles from different users and profile the resultant hits against this unified profile to the collective group of users as a single data package with multiple addresses.
3.2.9.10.4.3. The IPL Retrieval Profile service shall have ability to specify a dissemination priority in the profile.

3.2.10. Century Roll Over

The IPL shall be able to accurately process date data (including, but not limited to, calculating, comparing, and sequencing) from, into, and between the twentieth and twenty-first centuries, including leap year calculations.

3.2.11. Automated Installation Process

3.2.11.1. The IPL shall provide an automated installation process for both the Server and the Client enabling users (which includes everyone who uses an IPA client) to install and configure clients at their sites.
3.2.11.2. The IPL shall provide documentation, both hard copy and on-line, for the automated install process. On-line install process documentation shall not be in a format that requires the IPL software be installed in order to view.

3.2.12. On-Line Assistance

3.2.12.1. The IPL shall provide on-line documentation that is stored in a format that is optimized for the IPL Servers. On-line documentation shall consist of the following:

a. Computer Software Operators Manual

b. Software Users Manual

c. Software Data Dictionary

d. Software Installation Guide

e. Terms and Acronyms

f. IPL Training Guide

g. COTS/GOTS system documents (e.g., DEC, Sybase) as licenses and formats allow.

3.2.12.2. The IPL shall provide the IPL System Administrator with on-line display of:

a. IPL Operations Parameters

b. Server Operational Instructions

3.2.13. Hypertext Markup Language (HTML) Interface

The IPL Server shall provide a Client API to allow an interface to a GFI HTTP Server application. This HTTP Server will provide the primary interface to the users.

3.2.14. Backward Compatibility

All versions of IPL shall be backward compatible with the previous version.

3.2.15. Interaction with the Host Data Base System (HDBS)

3.2.15.1. The IPL shall support tasking and staging in concert with the HDBS. The IPL message & transaction interface with the HDBS as described below will initially be defined via the IPL API/ICD.
3.2.15.2. The IPL will notify the HDBS upon successful archiving of imagery files that meet a site defined IPL profile-identifying "new imagery" requiring HDBS dissemination & tasking. The "new imagery" notification message will include the IPL identification number and IMP ID of the file (to support subsequent HDBS retrieval for IA).
3.2.15.3. The IPL will notify the HDBS upon successful archiving of image product that meet a site defined IPL profile-identifying image products requiring internal HDBS linkage to an area or target requirement (reference imagery). This "reference imagery" notification message will include the IPL identification number of the file and those metadata elements required to allow linkage (to support subsequent IA tasking).
3.2.15.4. The IPL shall accept and process the "Archive Manifest Message" from the HDBS and provide the corresponding image "Archive Response Message.
3.2.15.5. The IPL shall support HDBS transactions initiating an image file transfer (retrieval) from the IPL to a HDBS defined workstation location.
3.2.15.6. The IPL shall provide status messages to the HDBS, to include any failures due to insufficient workstation storage, on all imagefileretrievals initiated by the HDBS.
3.2.15.7. The IPL shall have the capability to receive/process "Exploitation Complete" notifications from the HDBS indicating that an archived image has been exploited and can be migrated to near-line/off-line/purge status.

3.2.16. Print Capabilities

The IPL shall provide print capabilities to include a report writing capability that allows for the printing of full or partial portions of a product or query response list to a manageable report file for softcopy storage or hardcopy printer output.

3.2.17. Operating Systems/Platforms Supported

The IPL shall be compatible with the following operating systems/platforms in accordance with the folowing table:

  Server OS/Platform         Client OS/Platform           Effectivity       
       Supported                 Supported                                  
                                DEC OSF 2.0                                 
      DEC OSF 2.0               SUNOS 4.1.3                IPA 1.2.2        
      SOLARIS 2.4               SOLARIS 2.4                                 
                                 HP_UX 9.05                                 
                               DEC UNIX 3.2f                                
     DEC UNIX 3.2f              SUNOS 4.1.3                 IPL 1.X         
     SOLARIS 2.5.1              SOLARIS 2.51                                
                                 HP_UX 9.05                                 
      HP_UX 10.1                                            IPL 2.X         
  SGI Power Challenge                                                       

Table 3.2.17.1 - Operating Systems/Platforms Supported

Note: Beginning with IPL 2.0, the A3I Common Client will replace the IPL Client, and the IPL Developer will not be responsible for development of an IPL Client for delivery to the IPL Program Office.

3.2.18. Communications Server Interface

The IPL shall provide the capability to push imagery and/or products to existing site communications server interfaces that comply with the TCP/IP protocol. The communications servers will then push the imagery and/or products to the tactical users (e.g. TACO II, Success Radio, TRITAC, STACOM).

3.2.19. Global Broadcast System (GBS)

3.2.19.1. The IPL shall be able to generate required wrapper for products destined for the Global Broadcast System (GBS).
3.2.19.2. The IPL shall be able to aggregate product requests by product/destination for GBS.
3.2.19.3. Profiles shall be processed/disseminated according to a user-defined priority/provided algorithm.
3.2.19.4. IPL Requests/Transfers shall be processed/disseminated according to a user-defined priority/provided algorithm.

3.2.20. Performance Throughput

3.2.20.1. The IPL Server shall support, at a minimum, 40 simultaneous TCP/IP file transfer transactions (10 imports and 30 retrievals) in addition to 25 Client queries as described below:

a. A minimum of 10 simultaneous image file input transfers, each at a minimum transmission rate of 25 Mbps (assuming single Asynchronous Transfer Mode, ATM interface and no LAN contention). With each file completing the storage process no later than 5 minutes after file transfer completion to the IPL (assuming "auto input/trusted" source with no validation errors encountered).

b. A minimum of 30 simultaneous image file request transfers, each at a minimum transmission rate of 16 Mbps (assuming Fiber Distributed Data Interface, FDDI interface(s) and no LAN contention). With each retrieval file transfer starting no later than 2 minutes after request received by IPL Server (assuming conversion/compression required on a 12 bit/930MB image).

c. A minimum of 25 simultaneous client queries (assuming non-geo queries with an average of 10 hits/returns for each query and with thumbnails returned).

3.2.20.2. The IPL shall support up to 1300 image requests per day.
3.2.20.3. The IPL shall support up to 900GB for on-line imagery storage.
3.2.20.4. The IPL shall not take longer than eight minutes to transfer a full frame (930MB) national image to any requesting Client (assuming Fiber Distributed Data Interface, FDDI interface(s) and no LAN contention).

3.2.21. Security Accreditation

The IPL must meet C2 System High security accreditation criteria.

3.2.22. IDL Compliance

The IPL shall support future USIGS interoperability methods utilizing Interface Definition Language (IDL) as specified in the Common Imagery Interoperability Profile (CIIP).

3.2.23. DII/COE Compliance

The IPL Server shall be Defense Information Infrastructure (DII)/Common Operating Environment (COE) Level 5 (at a minimum) Compliant.

3.3. Reliability, Maintainability, and Availability

The IPL system design shall employ Best Commercial Practices for Reliability, Maintainability, and Availability (RMA).

The IPL will use an evolutionary design approach providing incremental capabilities over the USIGS Target One time span, incorporating COTS solutions into design where applicable.

For any new software development required in the development of the IPL, the IPL development contractor must comply with the Software Engineering Institute (SEI) Capability Maturity Model (CMM) level three certification criteria.

3.4. Training & Demonstrations

NIMA will provide definition of NIMA required tests and demonstrations for interoperability and developed capabilities.

NIMA will orchestrate Distributed Library (NIL/CIL/IPL) demonstration activities for sites via the NIMA Capstone Test and Evaluation Master Plan (TEMP), Demonstration Plan (TBS), and joint TEMs and message exchange.

3.5. Operations and Maintenance

The NIMA IPL Customer Support Center (ICSC) will be responsible for the management, planning, and scheduling of IPL Operations and Maintenance (O&M) activities.

3.6. Requirements Traceability and Effectivity

The following table provides "origin" traceability for each of the requirements in this Joint Requirements Document (JRD), as well as planned implementation effectivities.

Table 3.6-1 - Requirements Traceability and Effectivity Matrix

  JRD Requirement                Source                    Effectivity         
3.2.1.1                  Pilot A3I Requirement         Existing Capability     
3.2.1.2                            ?                         IPL 2.0           
3.2.1.3                       Rome Lab SI                    IPL 1.1           
3.2.1.4                            ?                   Existing Capability     
3.2.2.1                       Rome Lab SI                    IPL 2.0           
3.2.2.1.1                  ARD 2.1.4.2.1.1.1                 IPL 2.0           
3.2.2.1.2                Pilot A3I Requirement         Existing Capability     
3.2.2.1.3                  ARD 2.1.4.2.1.1.2           Existing Capability     
3.2.2.1.4                    MC&G/CIGSS/ARD                  IPL 2.0           
3.2.2.2.1                Pilot A3I Requirement         Existing Capability     
3.2.2.2.2                  ARD 2.1.4.2.1.1.2           Existing Capability     
3.2.2.2.3                  ARD 2.1.4.2.2.1.2           Existing Capability     
3.2.2.2.4                  ARD 2.1.4.2.2.1.23          Existing Capability     
3.2.2.2.5                  ARD 2.1.4.2.1.1.4                 IPL 2.0           
3.2.2.2.6                  ARD 2.1.4.2.1.1.5                 IPL 2.0           
3.2.2.2.7              Pilot A3I Requirement 212             IPL 2.0           
3.2.2.2.8                    MC&G/BC2A/BADD                  IPL 2.0           
3.2.2.3.1                  ARD 2.1.4.2.1.2.1                 IPL 2.0           
3.2.2.3.2                  ARD 2.1.4.2.1.2.2                 IPL 2.0           
3.2.2.3.3                  ARD 2.1.4.2.1.2.3                 IPL 2.0           
3.2.2.3.4              Pilot A3I Requirement ARD     Existing Capability IPL   
                             2.1.4.2.2.2.1                     1.0             
3.2.2.3.5                Pilot A3I Requirement         Existing Capability     
3.2.2.3.6                Pilot A3I Requirement         Existing Capability     
3.2.2.3.7              Pilot A3I Requirement 213             IPL 1.1           
3.2.2.3.8              Pilot A3I Requirement ARD     Existing Capability IPL   
                            2.1.4.2.1.2 ARD                1.1 IPL 1.1         
                             2.1.4.2.2.2.1                                     
3.2.2.4.1                Pilot A3I Requirement       Existing Capability IPL   
                                ARD/SEM                        2.0             
3.2.3.1                       ARD 2.1.4.3                    IPL 2.0           
3.2.3.1.1                Pilot A3I Requirement         Existing Capability     
3.2.3.1.2                  CIGSS/Rome Lab SI                 IPL 2.0           
3.2.3.1.3a               Pilot A3I Requirement         Existing Capability     
3.2.3.1.3b                 CIGSS/Rome Lab SI                 IPL 2.0           
3.2.3.1.4             Pilot A3I Requirement CIGSS    Existing Capability IPL   
                                                               2.0             
3.2.3.1.5                         DIA                        IPL 1.1           
3.2.3.1.6                      CIGSS/SEM                     IPL 1.1           
3.2.4                                                                          
 3.2.4.1                                                                       
3.2.4.1.1                Pilot A3I Requirement         Existing Capability     
3.2.4.2                                                                        
3.2.4.2.1                          ?                         IPL 2.0           
3.2.4.2.2                Pilot A3I Requirement         Existing Capability     
3.2.4.2.3                  ARD 2.1.4.4.1.1.3                 IPL 1.1           
3.2.4.2.4                          ?                         IPL 2.0           
3.2.4.2.5                Pilot A3I Requirement         Existing Capability     
3.2.4.2.5.1                   Rome Lab SI                    IPL 2.0           
3.2.4.2.5.2                   Rome Lab SI                    IPL 2.0           
3.2.4.2.5.3              Pilot A3I Requirement         Existing Capability     
 3.2.4.3                                                                       
3.2.4.3.1                Pilot A3I Requirement         Existing Capability     
3.2.4.3.2                 CIGSS SEM USCENTCOM                IPL 1.0           
3.2.4.4                                                                        
3.2.4.4.1                  ARD 2.1.4.4.1.2.1                 IPL 2.0           
3.2.4.4.2                   ARD 2.1.4.4.1.3                  IPL 2.0           
3.2.4.4.3                  ARD 2.1.4.4.1.3.1                 IPL 2.0           
3.2.4.4.4                  ARD 2.1.4.4.1.3.2                 IPL 2.0           
3.2.5                                                                          
3.2.5.1                                                                        
3.2.5.1.1                   ARD 2.1.4.5.1.1                  IPL 2.0           
3.2.5.1.2                        CIGSS                       IPL 2.0           
3.2.5.2                                                                        
3.2.5.2.1                   ARD 2.1.4.5.1.3            Existing Capability     
3.2.5.2.2                  ARD 2.1.4.5.1.3.1                 IPL 2.0           
3.2.5.2.3                  ARD 2.1.4.5.1.3.4                 IPL 2.0           
3.2.5.2.4                  ARD 2.1.4.5.1.3.2           Existing Capability     
3.2.5.3                     ARD 2.1.4.5.1.4                  IPL 2.0           
3.2.5.4                     ARD 2.1.4.5.1.5            Existing Capability     
3.2.5.5                      ARD 2.1.4.5.1                   IPL 2.0           
3.2.5.6                     ARD 2.1.4.5.1.6            Existing Capability     
3.2.5.7                     ARD 2.1.4.5.1.7            Existing Capability     
3.2.6                                                                          
3.2.6.1                                                                        
3.2.6.1.1                    ARD 2.1.4.6.1             Existing Capability     
3.2.6.1.2                   ARD 2.1.4.6.1.1            Existing Capability     
3.2.6.1.3                   ARD 2.1.4.6.1.3            Existing Capability     
3.2.6.1.4                      CIGSS/SEM                     IPL 2.0           
3.2.6.1.5                   ARD 2.1.4.7.2.1                  IPL 2.0           
3.2.6.2                                                                        
3.2.6.2.1                 ARD 2.1.4.6.2 a ARD        Existing Capability IPL   
                              2.1.4.6.2 b                      2.0             
3.2.6.2.2                   ARD 2.1.4.6.2.1            Existing Capability     
3.2.6.2.3                   ARD 2.1.4.6.2.3            Existing Capability     
3.2.6.2.4                   ARD 2.1.4.6.2 b                  IPL 2.0           
3.2.6.2.5                   ARD 2.1.4.6.2 c                  IPL 2.0           
3.2.6.2.6                     ARD 2.1.4.10                   IPL 2.0           
3.2.7                                                                          
3.2.7.1                    ARD 2.1.4.7.1.1.1           Existing Capability     
3.2.7.2                     ARD 2.1.4.7.1.3            Existing Capability     
3.2.7.3                    ARD 2.1.4.7.1.1.1           Existing Capability     
3.2.7.4                     ARD 2.1.4.7.1.2            Existing Capability     
3.2.7.5                    ARD 2.1.4.7.1.2.1           Existing Capability     
3.2.7.6                    ARD 2.1.4.7.1.2.2           Existing Capability     
3.2.7.7                  Pilot A3I Requirement         Existing Capability     
3.2.7.8                    ARD 2.1.4.7.1.3.2           Existing Capability     
3.2.7.9                  ARD 2.1.4.7.1.3.2 ARD         Existing Capability     
                          2.1.4.7.1.3.2.2 ARD                                  
                            2.1.4.7.1.3.2.1                                    
3.2.7.10                  ARD 2.1.4.7.1.3.2.4                IPL 2.0           
3.2.7.11                 CR From Pilot Demo 14               IPL 1.1           
3.2.7.12                                                                       
3.2.7.12.1                   ARD 2.1.4.7.2                   IPL 2.0           
3.2.7.12.2             Pilot A3I Requirement ARD     Existing Capability IPL   
                              2.1.4.7.2.1                      2.0             
3.2.7.12.3            Pilot A3I Requirement Pilot    Existing Capability IPL   
                        A3I Requirement 213 ARD        1.1 IPL 1.1 IPL 2.0     
                         2.1.4.7.2.2.2 MC&G/ARD      Existing Capability IPL   
                           2.1.4.7.2.2.4 ARD         2.0 Existing Capability   
                           2.1.4.7.1.3.1 ARD        IPL 2.0 IPL 2.0 Existing   
                           2.1.4.7.2.2.5 ARD         Capability IPL 2.0 IPL    
                        2.1.4.7.2.2.3 Pilot A3I                2.0             
                       Requirement 211 Pilot A3I                               
                          Requirement 211 ARD                                  
                      2.1.4.7.4.6 ARD 2.1.4.7.4.6                              
                            ARD 2.1.4.7.4.6                                    
3.2.7.12.4                                                                     
3.2.7.12.4.1                ARD 2.1.4.7.4.5                  IPL 2.0           
3.2.7.12.4.2               ARD 2.1.4.7.4.5.1                 IPL 2.0           
3.2.7.12.4.3               ARD 2.1.4.7.4.5.2                 IPL 2.0           
3.2.8                                                                          
3.2.8.1                       ARD 2.1.4.8                    IPL 2.0           
3.2.8.2                       ARD 2.1.4.8                    IPL 2.0           
3.2.8.3                       ARD 2.1.4.8                    IPL 2.0           
3.2.8.4                       ARD 2.1.4.8                    IPL 2.0           
3.2.9                                                                          
3.2.9.1                      ARD 2.1.4.9.1             Existing Capability     
3.2.9.2                       Rome Lab SI                    IPL 2.0           
3.2.9.3                       Rome Lab SI                    IPL 2.0           
3.2.9.4                       ARD 2.1.4.9                    IPL 2.0           
3.2.9.5                       Rome Lab SI              Existing Capability     
3.2.9.6                       Rome Lab SI                    IPL 2.0           
3.2.9.7                       Rome Lab SI                    IPL 2.0           
3.2.9.8                       Rome Lab SI                    IPL 2.0           
3.2.9.9                                                                        
3.2.9.9.1                   ARD 2.1.4.9.1.1                  IPL 2.0           
3.2.9.9.2                     Rome Lab SI                    IPL 2.0           
3.2.9.9.3                     Rome Lab SI                    IPL 2.0           
3.2.9.9.4                     Rome Lab SI                    IPL 2.0           
3.2.9.9.5                  ARD 2.1.4.9.1.1.1                 IPL 2.0           
3.2.9.9.6                  ARD 2.1.4.9.1.1.1                 IPL 2.0           
3.2.9.9.7                  ARD 2.1.4.9.1.1.1                 IPL 2.0           
3.2.9.10                                                                       
3.2.9.10.1                   ARD 2.1.4.9.2             Existing Capability     
3.2.9.10.2                   ARD 2.1.4.9.8             Existing Capability     
3.2.9.10.3                   ARD 2.1.4.9.8                   IPL 2.0           
3.2.9.10.4                   ARD 2.1.4.9.4                   IPL 2.0           
3.2.9.10.4.1                 ARD 2.1.4.9.4                   IPL 2.0           
3.2.9.10.4.2                 ARD 2.1.4.9.4                   IPL 2.0           
3.2.9.10.5                    Rome Lab SI                    IPL 2.0           
3.2.10                        ARD 2.1.4.11                   IPL 2.0           
3.2.11                                                                         
3.2.11.1                     ARD 2.1.5.5.2                   IPL 2.0           
3.2.11.2               Pilot A3I Requirement 217             IPL 2.0           
3.2.12                                                                         
3.2.12.1               Pilot A3I Requirement 214             IPL 2.0           
3.2.12.2               Pilot A3I Requirement 214             IPL 2.0           
3.2.13                        Rome Lab SI              Existing Capability     
3.2.14                        Rome Lab SI              Existing Capability     
3.2.15                                                                         
3.2.15.1                  SEM Design Topicals                IPL 2.0           
3.2.15.2                  SEM Design Topicals                IPL 2.0           
3.2.15.3                  SEM Design Topicals                IPL 2.0           
3.2.15.4                  SEM Design Topicals                IPL 2.0           
3.2.15.5                  SEM Design Topicals                IPL 2.0           
3.2.15.6                  SEM Design Topicals                IPL 2.0           
3.2.15.7                  SEM Design Topicals                IPL 2.0           
3.2.16                 Pilot A3I Requirement 211             IPL 2.0           
3.2.17                Pilot A3I Requirement CIGSS    Existing Capability IPL   
                                                           1.0 IPL 2.0         
3.2.18                 Pilot A3I Requirement 001             IPL 1.1           
                                 CIGSS                                         
3.2.19                                                                         
3.2.19.1                      Rome Lab SI                    IPL 1.1           
3.2.19.2                      Rome Lab SI                    IPL 1.1           
3.2.19.3                      Rome Lab SI                    IPL 1.1           
3.2.19.4                      Rome Lab SI                    IPL 1.1           
3.2.20                                                                         
3.2.20.1                   Rome Lab SI CIGSS                 IPL 2.0           
3.2.20.2                         CIGSS                       IPL 2.0           
3.2.20.3                         CIGSS                       IPL 2.0           
3.2.20.4                         CIGSS                       IPL 2.0           
3.2.21                   Pilot A3I Requirement         Existing Capability     
3.2.22                          NIMA SI                      IPL 2.0           
3.2.23                          NIMA SI                      IPL 2.0           

4. System Verification

4.1. A3I Verification Process

The A3I verification process is the method used to assure that the System requirements identified in section 3 of this document are satisfied. The A3I requirements are allocated into two verification categories:

a. Requirements verified at the System Level - Verification shall be by analysis provided by the System Integrator.

b. Requirements verified at the Segment Level - Verification shall be by test, demonstration, analysis or inspection and performed by the Segment Contractor. Interface requirements shall also be verified as part of Segment verification and by Intersegment Demonstrations.

The completion of the Intersegment Demonstrations, System analysis and segment verification constitute verification of the System.

4.2. System Level Verification

Table 4.1 identifies the Section 3 requirements that shall be verified at the A3I System level by system analysis.

System analysis may be stand alone or may be combined with segment analysis or test results.

Preliminary system analysis shall be available at the System Preliminary Design Review (PDR), or equivalent review, and the final versions shall be available at the System Critical Design Review (CDR), or equivalent review.

4.3. Segment Level Verification

Table 4.1 also identifies the Section 3 requirements that shall be verified at Segment level. These requirements are allocated to appropriate Segment specifications and Interface Control Documents (ICD). Verification of Segment level requirements shall be described in the Contractor's Segment Verification Plans. The Contractor's Preliminary Segment Verification Plans shall be available at Segment Preliminary Design Reviews, or equivalent reviews, and the final versions shall be available at the Segment Critical Design Reviews, or equivalent reviews.

Table 4.3-1 Requirement Verification Matrix

   JRD Requirement                   Requirement Verification                
3.2.1.1                                    Segment Level                     
3.2.1.2                                    Segment Level                     
3.2.1.3                                    Segment Level                     
3.2.1.4                                    Segment Level                     
3.2.2.1                                    Segment Level                     
3.2.2.1.1                                  Segment Level                     
3.2.2.1.2                                  Segment Level                     
3.2.2.1.3                                  Segment Level                     
3.2.2.1.4                                  Segment Level                     
3.2.2.2.1                                  Segment Level                     
3.2.2.2.2                                  Segment Level                     
3.2.2.2.3                                  Segment Level                     
3.2.2.2.4                                  Segment Level                     
3.2.2.2.5                                  Segment Level                     
3.2.2.2.6                                  Segment Level                     
3.2.2.2.7                                  Segment Level                     
3.2.2.2.8                                  Segment Level                     
3.2.2.3.1                                  Segment Level                     
3.2.2.3.2                                  Segment Level                     
3.2.2.3.3                                  Segment Level                     
3.2.2.3.4                                  Segment Level                     
3.2.2.3.5                                  Segment Level                     
3.2.2.3.6                                  Segment Level                     
3.2.2.3.7                                  Segment Level                     
3.2.2.3.8                                  Segment Level                     
3.2.2.4.1                                  Segment Level                     
3.2.3.1                                    Segment Level                     
3.2.3.1.1                                  Segment Level                     
3.2.3.1.2                                  Segment Level                     
3.2.3.1.3a                                 Segment Level                     
3.2.3.1.3b                                 Segment Level                     
3.2.3.1.4                                  Segment Level                     
3.2.3.1.5                                  Segment Level                     
3.2.3.1.6                                  Segment Level                     
3.2.4                                                                        
3.2.4.1                                                                      
3.2.4.1.1                                  Segment Level                     
3.2.4.2                                                                      
3.2.4.2.1                                  Segment Level                     
3.2.4.2.2                                  Segment Level                     
3.2.4.2.3                                  Segment Level                     
3.2.4.2.4                                  Segment Level                     
3.2.4.2.5                                  Segment Level                     
3.2.4.2.5.1                                Segment Level                     
3.2.4.2.5.2                                Segment Level                     
3.2.4.2.5.3                                Segment Level                     
3.2.4.3                                                                      
3.2.4.3.1                                  Segment Level                     
3.2.4.3.2                                  Segment Level                     
3.2.4.4                                                                      
3.2.4.4.1                                  Segment Level                     
3.2.4.4.2                                  Segment Level                     
3.2.4.4.3                                  Segment Level                     
3.2.4.4.4                                  Segment Level                     
3.2.5                                                                        
3.2.5.1                                                                      
3.2.5.1.1                                  Segment Level                     
3.2.5.1.2                                  Segment Level                     
3.2.5.2                                                                      
3.2.5.2.1                                  Segment Level                     
3.2.5.2.2                                  Segment Level                     
3.2.5.2.3                                  Segment Level                     
3.2.5.2.4                                  Segment Level                     
3.2.5.3                                    Segment Level                     
3.2.5.4                                    Segment Level                     
3.2.5.5                                    Segment Level                     
3.2.5.6                                    Segment Level                     
3.2.5.7                                    Segment Level                     
3.2.6                                                                        
3.2.6.1                                                                      
3.2.6.1.1                                  Segment Level                     
3.2.6.1.2                                  Segment Level                     
3.2.6.1.3                                  Segment Level                     
3.2.6.1.4                                  Segment Level                     
3.2.6.1.5                                  Segment Level                     
3.2.6.2                                                                      
3.2.6.2.1                                  Segment Level                     
3.2.6.2.2                                  Segment Level                     
3.2.6.2.3                                  Segment Level                     
3.2.6.2.4                                  Segment Level                     
3.2.6.2.5                                  Segment Level                     
3.2.6.2.6                                  Segment Level                     
3.2.7                                                                        
3.2.7.1                                    Segment Level                     
3.2.7.2                                    Segment Level                     
3.2.7.3                                    Segment Level                     
3.2.7.4                                    Segment Level                     
3.2.7.5                                    Segment Level                     
3.2.7.6                                    Segment Level                     
3.2.7.7                                    Segment Level                     
3.2.7.8                                    Segment Level                     
3.2.7.9                                    Segment Level                     
3.2.7.10                                   Segment Level                     
3.2.7.11                                   Segment Level                     
3.2.7.12                                                                     
3.2.7.12.1                                 Segment Level                     
3.2.7.12.2                                 Segment Level                     
3.2.7.12.3                                 Segment Level                     
3.2.7.12.4                                                                   
3.2.7.12.4.1                               Segment Level                     
3.2.7.12.4.2                               Segment Level                     
3.2.7.12.4.3                               Segment Level                     
3.2.8                                                                        
3.2.8.1                                    Segment Level                     
3.2.8.2                                    Segment Level                     
3.2.8.3                                    Segment Level                     
3.2.8.4                                    Segment Level                     
3.2.9                                                                        
3.2.9.1                                    Segment Level                     
3.2.9.2                                    Segment Level                     
3.2.9.3                                    Segment Level                     
3.2.9.4                                    Segment Level                     
3.2.9.5                                    Segment Level                     
3.2.9.6                                    Segment Level                     
3.2.9.7                                    Segment Level                     
3.2.9.8                                    Segment Level                     
3.2.9.9                                                                      
3.2.9.9.1                                  Segment Level                     
3.2.9.9.2                                  Segment Level                     
3.2.9.9.3                                  Segment Level                     
3.2.9.9.4                                  Segment Level                     
3.2.9.9.5                                  Segment Level                     
3.2.9.9.6                                  Segment Level                     
3.2.9.9.7                                  Segment Level                     
3.2.9.10                                                                     
3.2.9.10.1                                 Segment Level                     
3.2.9.10.2                                 Segment Level                     
3.2.9.10.3                                 Segment Level                     
3.2.9.10.4                                 Segment Level                     
3.2.9.10.4.1                               Segment Level                     
3.2.9.10.4.2                               Segment Level                     
3.2.9.10.5                                 Segment Level                     
3.2.10                                     Segment Level                     
3.2.11                                                                       
3.2.11.1                                   Segment Level                     
3.2.11.2                                   Segment Level                     
3.2.12                                                                       
3.2.12.1                                   Segment Level                     
3.2.12.2                                   Segment Level                     
3.2.13                                     Segment Level                     
3.2.14                                     Segment Level                     
3.2.15                                                                       
3.2.15.1                                   Segment Level                     
3.2.15.2                                   Segment Level                     
3.2.15.3                                   Segment Level                     
3.2.15.4                                   Segment Level                     
3.2.15.5                                   Segment Level                     
3.2.15.6                                   Segment Level                     
3.2.15.7                                   Segment Level                     
3.2.16                                     Segment Level                     
3.2.17                                     Segment Level                     
3.2.18                                     Segment Level                     
3.2.19                                                                       
3.2.19.1                                   Segment Level                     
3.2.19.2                                   Segment Level                     
3.2.19.3                                   Segment Level                     
3.2.19.4                                   Segment Level                     
3.2.20                                                                       
3.2.20.1                                   Segment Level                     
3.2.20.2                                   Segment Level                     
3.2.20.3                                   Segment Level                     
3.2.20.4                                   Segment Level                     
3.2.21                                     Segment Level                     
3.2.22                                     Segment Level                     
3.2.23                                     Segment Level                     

Appendix A - Acronym List

A3I Accelerated Architecture Acquisition Initiative

ARIDPCM Adaptive Recursive Interpretive Differential Pulse Code Modulation

API Application Program Interface

APMO A3I Project Management Office

ARIDPCM Adaptive Recurvice Differential Pulse Code Modulation

ATM Asynchronous Transfer Mode

BADD Battlefield Awareness & Data Dissemination

BC2A Bosnia Command & Control Augmentation

5D Demand Driven Direct Digital Dissemination

C3I Command, Control, Communications, and Intelligence

CSE Client/Server Environment

CD Compact Disc

CDR Critical Design Review

CIGGS Common Imagery Ground/Surface System

CIO Central Imagery Office

CIP Common Imagery Processor

CMM Capability Maturity Model

CONOP Concept of Operations

COTS Commercial-Off-The-Shelf

CSOM Computer Software Operators Manual

DCT Discrete Cosine Transfer

DIA Defense Intelligence Agency

DII/COE Defense Information Infrastructure/Common Operating Environment

DoD Department of Defense

DPCM Differential Pulse Code Modulation

DTED Digital Terrain and Elevation Data

EI Exploitation Initiative

ETRAC Enhanced Tactical Radar Correlator

FDDI Fiber Distributed Data Interface

FOC Full Operational Capability

GFI Government Furnished Information

GIF Graphical Interchange Format

HDBS Host Data Base System

HTML Hypertext Markup Language

HTTP Hypertext Transfer Protocol

IAW In Accordance With

ICD Interface Control Document

ICSC IPL Customer Support Center

IIE Installation Identification Elements

IIM Integrated Imagery Management

IOC Initial Operational Capability

IPA Image Product Archive

IPL Image Product Library

JITC Joint Interoperability Testing Center

JITF Joint Integration Testing Facility

JPEG Joint Photographic Experts Group

JRD Joint Requirements Document

LAN Local Area Network

MIES Modernized Imagery Exploitation System

MOU Memorandum of Understanding

MPEG Motion Picture Experts Group

NIMA National Imagery and Mapping Agency

NITFS National Imagery Transmission Format Standard

PDR Preliminary Design Review

PGM Product Group Manager

PIAE Profile for Imagery Archive Extensions

PO Program/Project Office

REFIMG Reference Image

RFC Request For Change

RIGS Reconnaissance Intelligence Ground Systems

RL Rome Laboratory

RMA Reliability, Maintainability, and Availability

SCI Sensitive Compartmented Information

SDE Support Data Extensions

SEI Software Engineering Institute

SEM Softcopy Exploitation Management

SPIA Standards Profile for Imagery Archives

SPID Standards Profile for Image Distribution

SRP Standard Raster Product (MC&G format)

SVP Standard Vector Product (MC&G format)

TARD Technical Architecture Requirements

TEM Technical Exchange Meeting

TES Tactical Exploitation System

TIFF Tagged Image File Format

USIGS United States Imagery and Geospatial Information System