Image Product Library

Table 3.2.2.3.7-1 Compression Schemes 10

Table 3.2.2.4.1-1 File Format Conversion Matrix 11

Table 3.2.2.4.2-1 Video Image File Format Conversion Matrix 11

Table 3.6-1 Requirements Traceability and Effectivity Matrix 26

1. Introduction

1. Purpose

This document defines the baseline system-level requirements for the National Imagery and Mapping Agency (NIMA) activities required to meet the goals and objectives of the design and development of the Image Product Library (IPL 2.x) under the United States Imagery and Geospatial Information Systems (USIGS) 2000 initiative. (note: This Requirements Document 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/)

2. Objectives

The objective of this Requirements Document (RD) is to establish a controlled document which will define the foundation of high level requirements under which NIMA develop the IPL 2.x under the USIGS.

3. Scope

This document contains the requirements for the activities of NIMA pertaining to the system development of the IPL under the USIGS.

4. Applicable Documents

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 RD, the contents of this RD shall be considered a superseding requirement.

NIMA/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

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 RD, the contents of this RD 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 2, dated 14 March 1997

ICHIPA and HIST_A as documented in NITFS TAGGED Record Extension Registry

Interim Low Bit Rate Compression as defined in ISMC document "Bandwidth Compression Guidelines for the NITFS/BIIF", dated TBD

National Imagery Transmission Format (NITF) (Version 2.0) for the National Image Transmission Format Standard (NITFS), MIL-STD-2500A, 12 October 1994, with Change Notice 1, dated 7 February 1997 (note: The NITF specification and related documentation is available via the Internet at http://www.nima.mil)

MIL-STD-2500B, National Imagery Transmission Format Version 2.1 for the Military Handbook for the National Imagery Transmission Format Standard, dated 22 August 1997 (IPL effectivity is to be specified in the UIP post 2.0)

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

Department of Defense Joint Technical Architecture (DoD JTA), Version 1.0, 22 August 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

NIMA Standards Profile for Imagery Archives (NSPIA), 23 April 1997 (To be replaced by DAGS Data Model, 30 September 1997)

USIGS Interoperability Profile (UIP) (N0102-A), per RFC N01-018, released 22 July 1997

Geospatial & Imagery Access Service (GIAS) Specification (N0101-A), version 3.0, per RFC N01-018, released 22 July 1997

USIGS Common Object Specification, v1.0, N0104, per RFC N01-0020, released 22 July 1997

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 (Version 1.2 is expected to be published October 1997)

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 1.0, dated TBD

Visible, Infrared, and Multispectral Airborne Sensor Support Data Extensions (SDE) for the National Imagery Transmission Format (Version 2.0) of the National Imagery Transmission Format Standards, version 1.0, dated TBD

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

MIL-STD-188-199, Vector Quantization Decompression for the National Imagery Transmission Format Standard, 27 June 1994, with Notice 2, 27 June 1996

IF20D08P

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

USIGS Video Standards Profile (VSP), DoD/IC Video Working Group, Ver 1.1, 26 September 1997 (TBR)

Core Video Metadata Profile, March 14, 1997

Imagery Exploitation Support System (IESS)/Common Imagery Ground Surface Systems (CIGSS) Interface Control Document (ICD), per RFC K01-014J, (scheduled for 26 August 1997 NCCB)

JIEO Circular 9008, dated 30 June 1993, with Errata Sheet, 23 February 1994

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 RD, the contents of this RD shall be considered a superseding requirement.

Motion Imagery Archive and Dissemination (Draft), 17 September 1997

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

NIMA Library Requirements Document (NLRD-A), dated 6 June 1997

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

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 RD, the contents of this RD 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

3. Programmatic Roles and Responsibilities

This section has been deleted.

 

4. System Requirements

1. NIMA Library and Dissemination System Description

NIMA 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, geospatial and anticipated video products. 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. The IPLs are scaled for size and performance, and some shall be portable. IPLs support various levels of commands, Common Imagery Ground/Surface System (CIGSS) compliant sites, and other organizations outside the command structure of the services, that require the use of libraries.

This document uses the terms imagery and imagery products to include video. Requirements for NITF, TFRD, TIFF, SunRaster, JPEG, GIF, and Postscript are applicable only to still imagery and imagery products. Requirements for MPEG-2 are applicable only to video imagery and imagery products.

 

2. NIMA 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 requirements in the remainder of section 3.

1. Data Management

1. The IPL shall be capable of importing, storing, exporting, and managing imagery, image-based products, and associated metadata.
2. The imagery and imagery based products shall consist of tactical, theater, national, civil, and commercial imagery and imagery-based products.
3. The IPL shall be able to import, store, manage, and export externally generated standalone metadata files associated with off-line imagery sources; containing zero, one, or multiple (e.g., gallery) thumbnails.
4. The IPL shall have the capability to handle multi-image NITFS 2.0 products (e.g., multispectral) as follows:

a. Generate thumbnails for each of the image files.

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

 

5. The IPL shall have the capability to handle multi-file NITFS 2.1 products as described in MIL-STD-2500B.
6. The IPL shall be capable of importing and exporting motion imagery in any of the Video Systems (Spatial and Temporal) Matrix (VSM) profiles in accordance with the USIGS Video Standards Profile (VSP).
7. The IPL shall be able to read queriable metadata as defined in the UIP and DAGS Data Model. This metadata shall be extracted from the NITFS file structure (i.e., file header, image subheader, and appropriate control tag extensions).

2. Format and Compression Schemes

1. Imagery Formats

(reference Table 3.2.2.3.8-1 for Format/Compression Types supported)

1. The IPL shall be capable of importing, exporting, storing and cataloging imagery in the Tape Format Requirement Documents (TFRD) per IF20D08P and S2025P.
2. The IPL shall be capable of importing, exporting, storing and cataloging imagery in National Imagery Transmission Format (NITF) Version 1.1.
3. The IPL shall be capable of importing, exporting, storing and cataloging imagery in National Imagery Transmission Format (NITF) Version 2.0.
4. The IPL shall be capable of importing, exporting, storing and cataloging digital video imagery in accordance with the Motion Picture Experts Group (MPEG-2) document (IOS/IEC 13818). (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-vwg.itsi.disa.mil)

2. Image-Based Product Formats

1. The IPL shall be capable of importing, exporting, storing, and cataloging image-based products in National Imagery Transmission Format (NITF) Version 1.1.
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. The IPL shall be capable of importing, exporting, storing, and cataloging image-based products in non-NITF formats when accompanied with an associated IPL data file.
4. (Combined into 3.2.2.2.3)
5. (Combined into 3.2.2.2.3)
6. (Combined into 3.2.2.2.3)
7. (Requirement superseded by 3.2.2.2.6)
8. (Combined into 3.2.2.2.3)

3. Imagery and Imagery-Based Compression Schemes

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) per IF20D08P and S2025P.
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 per IF20D08P and S2025P.
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 per IF20D08P and S2025P.
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.
5. The IPL shall be capable of importing, exporting, storing, and cataloging imagery utilizing Adaptive Recursive Interpretive Differential Pulse Code Modulation (ARIDPCM) compression.
6. The IPL shall be capable of importing, exporting, storing, and cataloging uncompressed imagery.
7. The IPL Server shall support the capability to create and store still image thumbnails in a compressed format.
9. The IPL shall support the generation and storage of compressed formatted thumbnails (TN) as shown in Table 3.2.2.3.9-1. Thumbnail generation shall occur at import.
10. The IPL shall support user requests to generate Reduced Resolution Image (RRI) files of stored, archived still image products as shown in Table 3.2.2.3.9-1. (for example, an R5 reduced resolution is a 1:32 resolution overview)

COMPRESSIONS

ARID-PCM

8 BIT JPEG

12 BIT JPEG

24 BIT JPEG

4.3 DPCM

2.3 DCT

1.29 DCT

VSM

TN

RRI

F

NITF 1.1

Y

N

N

N

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

Table 3.2.2.3.9-1 Compression Schemes

 

11. For imported images that are too large for thumbnail generation, the IPL shall substitute the thumbnail with a notification message for the user to generate an RRI.
12. The IPL shall support MPEG-2 video file compression schemes as defined in the USIGS VSP.

5. Imagery and Imagery-based Product Format Conversion Schemes

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

TO

	FORMATS	NITF 1.1	NITF 2.0	TIFF 6.0	Sun Raster	TFRD	GIF	Post- script	SRP	SVP
	NITF 1.1	N/A	Y	Y	Y	N	N	N	N	N
	NITF 2.0	N	N/A	Y	Y	N	N	N	N	N
F	TIFF 6.0	Y	Y	N/A	Y	N	N	N	N	N
R	Sun Raster	Y	Y	Y	N/A	N	N	N	N	N
O	TFRD	N	Y	N	N	N/A	N	N	N	N
M	GIF	N	N	N	N	N	N/A	N	N	N
	Postscript	N	N	N	N	N	N	N/A	N	N
	SRP	N	N	N	N	N	N	N	N/A	N
	SVP	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

 

2. The IPL shall convert MPEG-2 video data between VSM levels (To/From) in accordance with the following table:

		T	O
F		VSM5	VSM4	VSM3	VSM2
R	VSM5	N/A	Y	Y	Y
O	VSM4	Y	N/A	Y	Y
M	VSM3	Y	Y	N/A	Y
	VSM2	Y	Y	Y	N/A

Table 3.2.2.4.2-1 Video Image File Format Conversion Matrix

 

3. Data Storage

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

4. Metadata Management Services

The IPL shall provide metadata management services.

 

1. Metadata Database Maintenance Services

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

2. Metadata Population Services

1. The IPL shall have a Metadata Population Service.
2. The IPL Metadata Population Service shall provide the capability to accept, parse, and index metadata.
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/foreign imagery metadata).

1. The commercial satellite metadata shall be defined by the NIMA Standards Profile for Imagery Archives (NSPIA).

4. The IPL shall read/validate incoming metadata.

1. The IPL shall preserve NITF controlled and registered tags.

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.

1. The filter tables shall be created, implemented or modified by a site manager within an IPL provided library management application interface.
2. The filter tables will have the capability to be saved and file transferred to other IPL servers for implementation.
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. Metadata Update Service

1. The IPL Metadata Update Service shall provide the capability to update metadata index entries upon storage state changes such as movement to near-line, off-line, or purge.
2. The IPL server shall provide the capability to utilize the collocated Host Data Base System (HDBS) data to autopopulate product metadata for user-specified imported imagery products.

4. (Association Folders moved to USIGS Common Client)

1. (Requirement moved to USIGS Common Client)
2. (Requirement moved to USIGS Common Client)
3. (Requirement moved to USIGS Common Client)
4. (Requirement moved to USIGS Common Client)
5. (Requirement moved to USIGS Common Client)
6. (Requirement moved to USIGS Common Client)

5. Resource Management Services

1. Storage Management

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.
2. The IPL shall provide the capability to partition/restrict access to metadata and image files by user-defined criteria (e.g., partitioning the disk allowing a sensor to write to a specific partition; partitioning with restricted access provided for user configuration, such as private for primary, reference, and map data, yet public for secondary imagery dissemination).

2. Migration Across Hierarchical Storage

1. The IPL Resource Management Services shall provide the capability to manage the migration of data across hierarchical storage devices.
2. The IPL Resource Management Services shall provide the capability to automatically migrate data across its hierarchical storage devices.
3. The IPL shall provide the capability to migrate data across hierarchical storage devices using descriptors such as, age of data, frequency of retrieval, date of last retrieval, and user selected metadata elements.
4. The IPL shall provide the capability for an operator to manually migrate data across the hierarchical storage devices.

3. Library Service Statistics

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

4. Unitary Logon

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

5. Automatic Logoff

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

6. Metadata Database Backup

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

7. Metadata Database Recovery

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

6. Data Management Services

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

1. Import Service

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.
2. The IPL Import Service shall support user specifications of metadata to be populated into a library via the create function of the UIP/GIAS.
3. The IPL Import Service shall provide the capability to import and archive images and image products from both CD and magnetic media.
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, or username) of the imported file.
5. (Requirement expressed in 3.2.2.8 and 3.2.2.9)

2. Export Service

1. The IPL Export Service shall support requests to copy an entire image or image-based product as a file or 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 the required Exploitation Support Data (ESD) metadata.
2. The IPL Export Service shall support user specification of data to be retrieved as defined in the UIP/GIAS.
3. The IPL Export Service shall support user identification of file format and compression of data to be exported from a library as defined in the UIP/GIAS. (Note: Still needs to be further defined after refining the compression table)
4. The IPL Export Service shall allow the exporting of imagery or a portion of an image (image chip) as defined in the UIP/GIAS.
5. The IPL shall support tiling as defined in the UIP/GIAS.
6. The IPL shall allow the user to identify reduced resolution data (sub-sampled image) of unexploited still imagery to be exported from the library as defined in the UIP/GIAS.

3. Purge Service

1. The IPL Purge Service shall provide the capability to remove imagery and related metadata from library storage.
2. The IPL Purge Service capability shall be established based on user selected descriptors such as metadata elements, age of data, frequency of retrieval, linkage to other items, and date of last retrieval.
3. The IPL Purge Service shall provide the capability to sever the links between the purged item and any linked item.

7. Query Service

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 libraries based on specific metadata attributes associated with the needed image products, using either positive or negative logic query quantifiers.
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 archived image product file(s) that meet the parameters of the clients query and the library location of said file(s).
3. The IPL Query Service shall provide the capability for users to specify whether queries are submitted to all, some, or one IPL.
4. (covered in 3.2.7.5)
5. The IPL Query Service shall support queries to define a set of imagery, image-based products, and geospatial products based on a subset of image attributes as defined in the UIP and the DAGS Data Model.
6. (covered in 3.2.7.5)
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.
8. The IPL Query Service shall provide a user the capability to request the termination of an ongoing search before it completes.

1. 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.
2. Query termination 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.

9. (Replaced with 3.2.7.8.1)
10. (Replaced with 3.2.7.8.2)
11. The IPL Boolean logic shall utilize Backus-Naur Form (BNF) logic to support all queriable IPA elements.
12. Browse Support

1. (Requirement moved to USIGS Common Client)
2. (Requirement moved to USIGS Common Client)
3. The IPL Server will support the following Browse functions:

a. Return/not return thumbnails.

b. Thumbnail type:

- Individual (one thumbnail associated with one returned file)

- Multiple return for simultaneous display (Thumbnail Gallery)

- Multiple return for simultaneous overview display (video) (TBR)

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

4. Brokered Retrieval Service

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.
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. The IPL Retrieval Service shall allow the user to select the library from which the requested item is to be retrieved based on:

a. Image product file size

b. Communications capacity available.

8. System Management Services

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. (Note: A TBD portion of the above status data will be made available (via API) to remote user/manager community (need CIIF facility defined for this).
2. Each IPL shall provide a System Administrative Service to support initialization, operation, and shutdown.
3. Each IPL shall provide a Performance Management Service to measure, predict, and optimize its performance over time.
4. The IPL Server will support remote diagnostics and maintenance efforts.
5. The IPL Server shall support remote downloading of software updates.

 

9. Profile Service

1. The IPL shall have the capability to allow IPL users an API 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.
2. Notification and Retrieval profile APIs will be based on query (metadata) attributes as defined in the USIGS Interoperability Profile (UIP).
3. Profile strategies supported by the IPL Server API shall be the same as the query strategies available to users.
4. Notification and Retrieval profiles shall be easily created, or modified by a user or IPL manager.
5. (Requirement moved to USIGS Common Client)
6. Notification and Retrieval profiles shall have the ability to specify an activation/deactivation time period for the profile.
7. (Requirement moved to USIGS Common Client)
8. (Requirement is redundant)
9. Notification Profiles

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.
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. 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.)
4. The IPL Server shall support Notification Profile functions as defined in the UIP/GIAS.
5. The IPL Notification Service shall provide the user the capability to specify the frequency of notification.
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.
7. Notification at sign-on shall include new imagery and imagery products since last log-off.

10. Retrieval Profiles

1. The IPL Retrieval Profile Service shall identify and deliver (retrieve) images or image products that meet retrieval profile parameters automatically to the profiled user.
2. The IPL Retrieval Profile Service shall deliver retrieved products to the user destination provided in the profile.
3. The IPL Retrieval Profile Service shall deliver retrieved products in the user desired format/compression/resolution provided in the profile.
4. The IPL Retrieval Profile Service shall contain the capability that provides delivery and profile unification as follows:

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.) (Note: there are no CIIF facilities to do this yet). Delivery unification is primarily intended to support Global Broadcast System (GBS). (3.2.19)
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. (Note: there are no CIIF facilities to do this yet). Profile unification is primarily intended to support GBS. (3.2.19)
3. The IPL Retrieval Profile service shall have ability to specify a dissemination priority in the profile.

10. Century Roll Over

1. 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.
2. The IPL shall be capable of interpreting and converting two-digit date formats into four-digit date formats as follows:

a. All two-digit dates within the range of 00-59 will be interpreted as twenty-first century dates (20XX)

b. All two-digit dates within the range of 60-99 will be interpreted as twentieth century dates (19XX)

11. Automated Installation Process

1. The IPL Server shall support an automated installation and configuration process.
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.

12. On-Line Assistance

1. The IPL shall provide on-line documentation that is stored in a format that 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.

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

a. IPL Operations Parameters

b. Server Operational Instructions

13. USIGS Common Client Interface

The IPL Server shall provide an API as defined by the UIP. This interface will be used by the USIGS Common Client providing the primary interface to the USIGS Library users. (Note: The interface to IPL is Currently implemented via GFI HTML)

14. Backward Compatibility

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

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

1. The IPL Server shall support Softcopy Exploitation Management (SEM) tasking and staging in concert with the HDBS. The SEM IOC IPL message and transaction interface with the HDBS will be defined per the IESS/CIGSS ICD. At SEM FOC, the exploitation management interface to the HDBS will evolve into existing and newly defined UIP/GIAS services.
2. (Requirement identified in the IESS/CIGSS ICD)
3. (Requirement will be identified in the IESS/CIGSS ICD for SEM FOC)
4. (Requirement identified in the IESS/CIGSS ICD)
5. (Requirement identified in the IESS/CIGSS ICD)
6. (Requirement identified in the IESS/CIGSS ICD)
7. (Requirement identified in the IESS/CIGSS ICD)

16. (Requirement moved to USIGS Common Client)
18. Operating Systems/Platforms Supported

The IPL Server shall be compatible with the Sun, Silicon Graphics (SGI), Digital (DEC), and Hewlett-Packard (HP) hardware platforms. Operating systems supported by IPL shall be in accordance with those supported by the Defense Information Infrastructure (DII)/Common Operating Environment (COE) and/or further refined through formal design reviews and Program Office guidance.

19. Communications Server Interface

The IPL Server 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, SATCOM). (Note: this may be a non-CIIF interface)

20. Global Broadcast System (GBS)

(Note: this may be a non-CIIF interface)

 

1. The IPL shall be able to generate required wrapper for products destined for the Global Broadcast System (GBS).
2. The IPL shall be able to aggregate product requests by product/destination for GBS. (See 3.2.9.10.4.1 and 3.2.9.10.4.2)
3. Profiles shall be processed/disseminated according to a user-defined aggregation period. (3.2.9.10.4.1)
4. IPL Requests/Transfers shall be processed/disseminated according to a user-defined aggregation period. (3.2.9.10.4.2)

21. Performance Throughput

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).

 

2. The IPL shall support up to 1300 image requests per day.
3. The IPL shall support up to 900GB for on-line imagery storage.
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).

22. Security Accreditation

The IPL 2.0 security certification process will conform to the requirements of DIA Manual 50-4 (Department of Defense Intelligence Information Systems (DODIIS) Information System Security Policy), Director of Central Intelligence Directive (DCID) 1/16 (Security Policy for Uniform Protection of Intelligence Processed in Automated Information Systems and Networks), and the DODIIS Developer's Guide for Automated Information Systems (AIS) Security in DODIIS.

Certification testing will demonstrate the functionality of the safeguards identified in the System Security and Requirements and Analysis document for the IPL 2.0 system. Functionality demonstrations will be described in a series of security test sequences contained in a Security Certification Test procedures document. The test sequences will be tailored to the operating systems and platforms on which IPL will be fielded. As a minimum, the following procedures will be physcially exercised on each system undergoing security certification testing:

a. Discretionary Access Control. The test will demonstrate that system discretionary access control is sufficient to protect the IPL application from unauthorized access.

b. Identification and Authentication. The test will demonstrate that access to the IPL application is restricted to authorized users only.

c. Server Challenge and Response. The test will demonstrate that server to server verification will be completed prior to server to server communication (protected servers only).

d. Security Audits. The test will demonstrate that critical security audit events (e.g., login, failed logins, account disabling, and queries, etc.) are captured for both the the IPL application and associated database(s).

Additional testing, on an ad hoc basis, will be conducted at the discretion of the Security Certification Test Team. Such testing may consist of locally-generated procedures designed to validate the presence certain functionality or the absence of "trapdoors" or "bugs." Ad hoc testing may also consist of the running of system test and evaluation software such as Security Profile Inspector (SPI), Computer Oracle and Password System (COPS) and other such adjuncts as deemed necessary by the test team.

23. IDL Compliance

The IPL shall support future USIGS interoperability methods utilizing Interface Definition Language (IDL) as specified in the USIGS Interoperability Profile (UIP), Geospatial & Imagery Access Services (GIAS).

24. DII/COE Compliance

The IPL Server shall be Defense Information Infrastructure (DII)/Common Operating Environment (COE) Level 5 (at a minimum) Compliant, with a goal of Level 8 Compliance.

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.

 

4. Training and 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.

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.

6. Requirements Traceability and Effectivity

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

Table 3.6-1 - Requirements Traceability and Effectivity Matrix

RD Requirement	Source	Effectivity
3.2.1
3.2.1.1	Pilot A3I Requirement	Existing Capability
3.2.1.2	DIA (Commercial Archives)	Existing Capability
3.2.1.3	DIA (Commercial Archives)	Existing Capability
3.2.1.4	Rome Lab SI	IPL 2.0
3.2.1.5	MIL-STD-2500B	IPL 2.0
3.2.1.6	Video Working Group	IPL 2.0
3.2.1.7	ISMC	IPL 2.0
3.2.2
3.2.2.1
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
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
3.2.2.2.5
3.2.2.2.6
3.2.2.2.7
3.2.2.2.8
3.2.2.3
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 2.1.4.2.2.2.1	Existing Capability
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	Existing Capability
3.2.2.3.8	Pilot A3I Requirement 213	Existing Capability
3.2.2.3.9	SEM/CIG/SS	Existing Capability
3.2.2.3.10	Rome Lab SI	IPL 2.0
3.2.2.3.11	NIMA Video Working Group	IPL 2.0
3.2.2.4
3.2.2.4.1	NITF/TIFF/SunRaster TFRD/Postscript/SRP/SVP	Existing Capability IPL 2.0
3.2.2.4.2	NIMA Video Working Group	IPL 2.0
3.2.3
3.2.3.1	On-line/Off-line Near-line	Existing Capability IPL 2.0
3.2.3.2	Pilot A3I Requirement	Existing Capability
3.2.3.3	CIGSS/Rome Lab SI	IPL 2.0
3.2.3.4	CIGSS/Rome Lab SI	IPL 2.0
3.2.3.5	On-line/Off-line(Pilot) Near-line (CIG/SS)	Existing Capability IPL 2.0
3.2.3.6	DIA (Commercial Archives)	Existing Capability
3.2.3.7	CIGSS/SEM	IPL 2.0
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	ARD 2.1.4.4.1.1	Existing Capability
3.2.4.2.2	ARD 2.1.4.4.1.1.1	Existing Capability
3.2.4.2.3	ARD 2.1.4.4.1.1.3	Existing Capability
3.2.4.2.3.1	NSPIA	Existing Capability
3.2.4.2.4	ARD 2.1.4.4.1.1.4.2	Existing Capability
3.2.4.2.4.1	Rome Lab SI	Existing Capability
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	Existing Capability
3.2.4.4
3.2.4.4.1
3.2.4.4.2
3.2.4.4.3
3.2.4.4.4
3.2.4.4.5
3.2.4.4.6
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	IPL 2.0
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
3.2.6.2
3.2.6.2.1	ARD 2.1.4.6.2 (entire image) ARD 2.1.4.6.2 (image subset)	Existing Capability IPL 2.0
3.2.6.2.2	ARD 2.1.4.6.2.1	IPL 2.0
3.2.6.2.3	ARD 2.1.4.6.2.3	IPL 2.0
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.6.3
3.2.6.3.1	ARD 2.1.4.6.3	IPL 2.0
3.2.6.3.2	ARD 2.1.4.6.3	IPL 2.0
3.2.6.3.3	ARD 2.1.4.6.3	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
3.2.7.5	Rome Lab SI	IPL 2.0
3.2.7.6
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.8.1	ARD 2.1.4.7.1.3.2.3	IPL 2.0
3.2.7.8.2	ARD 2.1.4.7.1.3.2.4	IPL 2.0
3.2.7.9
3.2.7.10
3.2.7.11	USIGS Interoperability Profile	Existing Capability
3.2.7.12
3.2.7.12.1
3.2.7.12.2
3.2.7.12.3a 3.2.7.12.3b	Pilot A3I Requirement Video Working Group/DIA	Existing Capability IPL 2.0
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.8.5	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	USIGS Interoperability Profile	IPL 2.0
3.2.9.3	USIGS Interoperability Profile	IPL 2.0
3.2.9.4	ARD 2.1.4.9	IPL 2.0
3.2.9.5
3.2.9.6	Rome Lab SI	IPL 2.0
3.2.9.7
3.2.9.8
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	USIGS Interoperability Profile	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.4.3	ARD 2.1.4.9.4	IPL 2.0
3.2.10