3.2.21.1 The IPA/IPL shall interface with Host Data Base System (HDBS) for the purpose of obtaining and auto-populating the product data file with installation identification elements (IIEs) on non-NITFS formatted products being loaded into IPL.

3.2.21.2 The IPA/IPL shall support tasking and staging in concert with the HDBS. The IPA/IPL message & transaction interface with the HDBS as described below will initially be defined via the IPA/IPL API/ICD.

3.2.21.2.1 The IPA/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.21.2.2 Upon IPA/IPL notification to the HDBS of "new imagery" archiving, the HDBS will provide Installation Identification Elements (IIEs) associated with the new image to the IPA. The IPA/IPL shall update the cataloged metadata file with the IIEs

3.2.21.2.3 The IPA/IPL will notify the HDBS upon successful archiving of image product that meet a site defined IPA/IPL profile-identifying image products requiring internal HDBS linkage to an area or target requirement (reference imagery). The "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.21.2.4 The IPA/IPL shall support HDBS transactions initiating an image file transfer (retrieval) from the IPL to a HDBS defined workstation location.

3.2.21.2.5 The IPL shall provide status messages to the HDBS, to include any failures due to insufficient storage, on all full/sub scene file transfers (retrievals) initiated by the HDBS.

3.2.21.2.6 The IPA/IPL shall support HDBS transactions initiating an image file transfer (import) from a workstation to the IPL/IPA.

3.2.21.2.7 The IPA/IPL shall provide import status messages to the HDBS, to include any failures.

3.2.21.2.8 The IPA/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.21.3 The IPA/IPL shall be capable of processing the "Exploitation Complete" input message, and the "Manifest Message" output message. Inputting of reference image (REFIMG) messages to the HDBS, or inputting of site selectable product short names will trigger Manifest Message creation.

3.2.21.4 The IPA/IPL shall support a Transactional Manifest list based on site configurable Product Short Names Reference Material (identified by a product short name, those products linked with unexploited images). The IPA/IPL shall support a new NITF Product Short NameA. HDBS IIE data will overwrite RE/DE inputs for specified product short names and replace NITFS header data with HDBS data for selected product short names.

3.2.21.5 The IPA/IPL shall support the generation of a library manifest of primary imagery and reference material (site configurable product short names) to the HDBS upon receipt. Sending the HDBS notification of receipt of reference material and unexploited imagery shall be site configurable with the product.

3.2.21.6 The IPA/IPL Client shall allow queries based on a user defined "stretchy box", overlaid on a map or image, representing the corner coordinates of an area to be searched for data . The interface between the IPA/IPL and the HDBS shall support the implementation of the stretchy box capability.

3.2.21.7 The IPA/IPL shall provide an interface between the HDBS and the Library Transfer image request for imagery or overview imagery to be transferred from the library to the requesting Client.

3.2.22 Product Replication

3.2.23.1 The IPA/IPL shall provide the capability to replicate products and product metadata.

3.2.23.2 The IPA/IPL product replication shall be based on autoprofiling based on all query elements.

3.2.23.3 The IPA/IPL shall have the capability for the end user to nominate autoprofile criteria to the IPA/IPL Manager for validation before it is active.

3.2.24 Print Capabilities

The IPA/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.25 Tactical Communications

3.2.25.1 The IPA/IPL shall support image transfers over tactical communications for the purposes of product dissemination to users. (No tactical user query capability is provided)

3.2.25.2 TACO II shall be implemented in accordance with MIL-STD-2045-44500, 18 June 1993 with Change Notice 1, 29 July 1994 and the National Imagery Transmission Format Standard (NITFS), MIL-HDBK-1300A, 12 October 1994.

3.2.25.3 The IPA/IPL shall have the capability of supporting inputs from the following tactical circuits:

• SATCOM/Fiber (UAV)
• Common Data Link (CDL)
• ETRAC

• Success Radio
• TRITAC

The IPA/IPL shall have a configurable communications option to direct all communication transmission requests through an external Communications Server.

3.2.27 Performance Throughput

3.2.27.1 The IPA/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 minimum of 10 simultaneous image file input transfers 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 IPA/IPL (assuming "auto input/trusted" source with no validation errors encountered).
• A minimum of 30 simultaneous image file request transfers 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 IPA/IPL Server (assuming conversion/compression required on a 12 bit/930MB image).
• 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.27.3 The IPA/IPL shall support, at a minimum, simultaneous image requests from 30 clients from the following clients:

• Reconnaissance Intelligence Ground Systems (RIGS) Product Group Manager (PGM): 6-18 Client IP Addresses
• PACAF: 20 (minimum) Client IP Addresses
• Modernized Imagery Exploitation System (MEIS): 6-12 Client IP Addresses
• Enhanced Tactical Radar Correlator (ETRAC): 3-6 Client IP Addresses
• Tactical Exploitation System (TES) Forward: 6-18 Client IP Addresses
• TES MAIN: 12-30 Client IP Addresses

3.2.27.5 The IPA/IPL shall not take longer than eight minutes to transfer a full frame (930MB) national image to any requesting Client.

3.2.28 Security Accreditation

The IPA/IPL must meet C2 System High security accreditation criteria.

3.2.29 Tile Brokering

The IPA/IPL will integrate COTS/GOTS tile brokering software into the library Client.

3.3 Reliability, Maintainability, and Availability

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

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

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

3.4 Training & Demonstrations

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

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

3.5 Operations and Maintenance

The CIO A3I Customer Support Center (ACSC) will be responsible for the management, planning, and scheduling of IPA/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.

Continue....