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
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
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
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
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
NOTE: N/A = Not Applicable
Table 3.2.2.4.1-1 File Format Conversion Matrix
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
3.2.3.
Data Storage
3.2.4.1.
Metadata Database Maintenance Services
b. Discard (Outside of Users Area of Interest)
3.2.4.3.
Metadata Update Service
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
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.
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.
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.
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.
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).
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.
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
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