3.2.1.5 Support ( Auxiliary) Data Services
3.2.1.6 System Capability Relationships
3.2.1.7 Simultaneity of Inputs
3.2.1.8.4 Management Element Interface
3.2.2 External Interface Requirements
3.2.2.1.1 Sensor Data Inputs (Baseline)
3.2.2.1.2 Sensor Data Inputs (Growth)
3.2.2.3.1 Image Data Output Formats
3.2.3 Physical Characteristics
3.2.5 Environmental Requirements
3.2.7 System Flexibility and Expansion
4.0 Quality Assurance Provisions
4.1.1 Responsibility for Tests
4.2 Preliminary Acceptance Tests
Appendix A, USA P-CIP Requirements
Appendix B, USAF P-CIP Requirements
Appendix C, USMC P-CIP Requirements
Appendix D, USN-CIP Requirements
Figure 3-1 CIP in CIGSS Architecture
This document provides the technical requirements for a Prototype - Common Image Processor (P-CIP). The objective of the P-CIP development is to achieve a hardware and software architecture that is modular, scaleable, and extensible. The P-CIP goals are to use Commercial Off The Shelf (COTS), Government Off The Shelf (GOTS) components, have an Open Systems concepts; and a high degree of commonality and interoperability across the services. It is intended that the P-CIP possess those qualities that will ensure that it is capable of being adapted to changing user needs, sensor modifications and upgrades, and new sensors with minimal impact to the design of the Common Imagery Ground / Surface Systems (CIG/SSCIG/SS) or the installed base of imagery ground stations. Consequently there will be significant emphasis on those qualities that reduce P-CIP life cycle costs. This document describes the requirements for the processing of Electro-Optical (EO), Infrared (IR), Synthetic Aperture Radar (SAR), Multi-Spectral Imagery (MSI), and other data from national, theater, and tactical sources. The objective is to process data from the baseline sensors defined in this document, while ensuring the ability to accommodate the specific user configurations and environmental requirements and growth sensors via hardware scaling and the addition of software modules for the specific sensor. Requirements for the Service implementations of the P-CIP are contained as Appendixes A-D.
The objectives of the P-CIP prototype development are twofold. The primary objective is to achieve a hardware and software architecture that is; modular, scaleable, extensible, has inherent interoperability, minimizes life cycle costs, uses COTS and GOTS and has an open architecture. The second objective is to demonstrate the prototype P-CIP implementation in the CIG/SS Testbed.
The P-CIP is the primary sensor processing element of the CIG/SS. The function of the P-CIP is to accept imagery and support data and, if necessary, process it into an exploitable image and output it to other elements of the CIG/SS. The P-CIP includes the hardware and software to connect to each of the data links, recorder subsystems and data files (as defined in section 3.2.2 of this document), extract the data from the incoming signal, process the data into exploitable imagery and transfer the imagery for exploitation and/or storage. The P-CIP will accept auxiliary data and exploitation support data associated with the input. The P-CIP will interface with existing baseline sensor systems via the DCRSi and ANSI ID-1 recorders and the Common Data Link (CDL) (in all channelization and data rates used by the target sensors). In addition, as a growth requirement, the P-CIP will interface with and process the growth systems listed in Section 3.2.2.1.2 and other sources of imagery.
The P-CIP must incorporate the functions required to support the objectives of the CIG/SS. These include the ability to adapt to new sensors, new processing and exploitation techniques, new or modified equipment, and new or extended users of data over the life of the system. The P-CIP will take advantage of the rapid evolution of Commercial Off-The-Shelf (COTS) and Government Off-The-Shelf (GOTS) hardware and software. The terms COTS and GOTS are intended to describe hardware and software which have many users and for which equivalent elements, not necessarily identical, are available from more than one source. The appropriate use of COTS and GOTS is desired to ensure the tactical user has the best performance / cost ratio that industry can deliver. The P-CIP design will be based on the need to support expandability and interoperability requirements. Interoperability, in particular, is critical to ensure the continued capability of the P-CIP to support new tactical deployments and users.
When the requirement of the contract, this document, or applicable documents are in conflict, the contracting agency shall be notified. The following order of precedence shall apply for conflict resolution:
a. The Contract
b. The Statement of Work
c. This Technical Requirements Document
d. Other documents
| MIL-S-901 | Shock Tests, High (High Impact) Shipboard Machinery, Equipment and Systems, Requirements for Navy |
| MIL-STD-167-1 | Mechanical Vibration of Shipboard Equipment (Type 1 - Environmental and Type 1 i - Internally Excited) |
| MIL-STD-810 | Environmental Test Methods and Engineering Guidelines |
| DOD-STD | Interface Standards for Shipboard Systems |
| MIL-STD-2500 | National Imagery Transmission Format (NITF) Version 2.0 |
| JIEO Circular 9008 | NITF Certification Test and Evaluation Program Plan |
| DIAM 50-4 | Security of Compartmented Computer Operations 24 June 80 |
| CIG/SS Handbook | Common Imagery Ground/Surface System Acquisition Standards Handbook (CIG/SS-Hdbk) Version 1.0 Dtd. 19 July 1995 |
| *ANSI X3.175-1990 | 19 MM Type ID-I Recorded Instrumentation Digital Cassette Tape Format |
| *EIA NTSC 1.13 | National Television Standards Committee (US Composite B/W and Color TV System |
| *PAL | Phase Alternate Lock (European TV) |
* = Need to reference in section 3 or Appendixes
| ICD-F/A-18-064 | F/A-18D(RC) TAC RECCE To Joint Service Imagery Processing System (JSIPS) ICD dtd 31 May 95 |
| *S7633603 Rev B | CARS U2 ICD |
| *DS32123-179 | Airborne Radio Set ICD dtd Oct 1993 (S) |
| *RWE-07-85D | CARS U2 ICD |
| *RWE-83-01B | Airborne Radio Set System Spec. Dtd Aug 84 |
| *101X0003 | Tier III Team Terrestrial Data Communications System to Launch, Control and Recovery Station Interface Definition Document dtd 20 Dec 94 |
| *S7633603 Rev B | External ICD for MIST dtd 16 Sep 87/CHBDL-ST Interface Control Document |
| IF20K22 | Imagery Exploitation Support System ICD Dtd. (TBD-1) |
* = Need to reference in section 3 or Appendixes
The P-CIP is the primary sensor processing element of the CIG/SS. The functions of the P-CIP are: accept imagery and auxiliary data, process the data into an exploitable image (if necessary), format the data into a common output format and output the data to other elements of the CIG/SS (See Figure 3.1). The P-CIP effort, defined in this section, will result in a COTS hardware and software sensor processing subsystem to be integrated into the CIG/SS Testbed. P-CIP integration into operational systems will be accomplished by the individual services or their acquisition agencies. The P-CIP prototype design must demonstrate a capability to be scaled to support the individual service requirements called out in Appendixes A through D.
The P-CIP shall have four primary states; Processing, Standby, Maintenance and Off.
The Processing State of the P-CIP shall support all of the required sensors and their modes. While in the processing state the P-CIP shall respond to commands and have the capability to change sensors or sensor modes without manual intervention and with minimal or no loss of data from either the sensor or data being processed. The command to change states shall be accepted by the P-CIP and acknowledged to the CIG/SS Management Element.
While in the Standby State, the P-CIP shall automatically accept and respond to commands from the CIG/SS Management Element to reconfigure the P-CIP for processing data from a particular sensor. While the P-CIP is in the Standby State it will be provided with power as necessary, and shall respond to commands and provide health and status data as requested or scheduled.
In the maintenance state the P-CIP shall have the capability to perform maintenance diagnostics as specified in paragraph 3.2.1.8.2.1
The P-CIP shall have provisions for retaining support data, such as calibration data, in nonvolatile storage while in the Off State.
The P-CIP shall have the capability to remap the sensor data such that it corresponds to a defined map projection (e.g. slant plane, ground plane).
The P-CIP will minimize processing latencies for exploitation, sensor dynamic retasking and real time screening.
The P-CIP processing capability shall be sized to support the incoming data streams of the baseline sensors in near real time, and expandable to support the growth sensors.
The P-CIP shall format the received support data in accordance with the NITF 2.0 ( as described in MIL-STD-2500) with CIG/SS support data extensions and add it to all output files.
Within the Processing State, the P-CIP shall respond to a command from the CIG/SS Management Element to change the sensor type to be processed without manual intervention and with minimal or no loss of data. The command shall be accepted and acknowledged via the interface to the Management Element.
The P-CIP will be capable of accepting and processing, in real or near-real time, sensor data from at least one sensor while simultaneously accepting and recording sensor data from at least one additional source. The P-CIP architecture shall be capable of being scaled and extended to allow expansion of capabilities to simultaneously process data from multiple sources.
The P-CIP shall be capable of supporting a CIG/SS Commercial Analyst Workstation (CAWS) screening function. The P-CIP shall perform the functions to support automatic, semiautomatic and manual screening by providing the required image and support data to a CIG/SS CAWS external to the P-CIP and the host database system. Automatic screening is defined as working totally from coordinates, semiautomatic screening identifies coordinates and displays the applicable image and manual screening works completely from operator inputs.
The P-CIP shall support screening of the processed imagery data. The screening, when enabled shall occur in one of three modes: automatic, semiautomatic and manual. The P-CIP shall, when required by the mode, provide an external output to a Screening workstation (SWS) external to the P-CIP. This output shall be in addition to the complete P-CIP imagery output specified in Section 3.2.2.3.1. The screening function will produce a Screener Data Set (SDS) consisting of representations of imagery selected from the complete P-CIP imagery output.
In the automatic mode, the P-CIP shall generate the SDS based on geographic coordinates and output it to the local storage and shall not generate an output to the SWS. In the semiautomatic mode , the P-CIP shall output the SDS to the SWS. In all three modes, the P-CIP shall output appropriate ESD (Exploitation Data) as part of the SDS.
The P-CIP shall accept and acknowledge the following from the Management Element; commands to enable /disable screening , commands to set the screening mode, and geographic coordinate data for the screening.
The SWS for the P-CIP shall be the (TBD-2) Workstation. For the Service specific version, the SWS shall be specified in the Appendixes. The P-CIP shall provide a data interface compatibly with the SWS. The interface may be a dedicated interconnection, separate from the CIG/SS LAN(s). The SWS output is not required to be NITF file; no specification on the file format is made.
The output to the SWS is required to a latency adequate to meet the screening function timeliness requirements, including the real time control of the sensor.
On command from the CIG/SS Management Element the P-CIP will perform a confidence check of its components to include the hardware and software subsystems, the connection to datalinks and the connection to any other CIG/SS interface(s) to the extent feasible within the constraints of the COTS hardware. On command from the CIG/SS Management Element the P-CIP shall be capable of performing a processing capability test, which will consist of accepting and processing image data and outputting the resultant image for review at a CIG/SS CAWS.
On command, from the Management Element, the P-CIP shall generate and output Status Information to the CIG/SS interface. This data shall identify the processing currently in effect, the status of the data link and the processing hardware and any detected faults in the P-CIP.
Appropriate error messages and operator alerts shall be generated upon detection of a failure of any subsystem within the P-CIP. These shall be output to the CIG/SS Management Element as well as written into a log file local to the P-CIP.
The P-CIP shall be capable of setting and changing configuration parameters and supporting power on, sensor change, sensor mode change and standby commands, status checks and changes based on direction received through the interface to the CIG/SS Management Element. The P-CIP will interface with the Imagery Exploitation Support System (IESS) ICD over the CIG/SS LAN in accordance with IF20K22 (TBR-3) ICD.
The P-CIP shall accept and process image data, in all modes from the following sensors:
a. U-2 ASARS-2
b. U-2 SYERS
c. F/A-18 ATARS
d. LO HAE UAV EO
e. LO HAE UAV SAR
The P-CIP architectural design shall be expandable and capable of being scaled to accept image data from the following sensors as growth requirements:
a. F/A-18 APG-73/RUG
b. National Sources
c. MAE UAV SAR
d. Conv HAE UAV EO
e. Conv HAE UAV SAR
f. U-2 / MSI
g. U-2 H-SIP. U-2 ASARS-2 (Improved)
i. LANDSAT
j. SPOT
k. RS-170 (NTSC and PAL) video
The P-CIP shall accept data from the following physical sources as appropriate for each sensor/ground station and provide command and control functions as necessary:
a. CDL (up to 274 Mbits/sec)
b. T-1 and T-3 links (Note: Need to specify type of interface.)
c. The CIG/SS imagery LAN in NITF 2.0 level 6 Format
d. ANSI ID-1 and DCRSi tape recorders
e. The CIG/SS Management Element via the CIG/SS LAN
The P-CIP shall be able to output imagery in the following data formats:
a. To the screener workstation
b. Special output in a format to be defined (TBD-4)
c. A NITF 2.0 level 6 imagery format with associated set of NITF CIG/SS support data extensions for each image.
The P-CIP shall support all NITF compression modes. All exploitable images will be output in an addressable format.
The P-CIP shall provide the capability for real time/near real time transfer of processed imagery for screening external to the P-CIP. This interface is not required to be a LAN or to be in accordance with NITF 2.0.
The P-CIP shall meet the following physical requirements:
| Design goal of one standard 72 inch.
Maximum of no more than two racks using less than 117 inches of vertical height. | |
| Standard 19 inch computer rack | |
| Not more than 27 inches including cables and connectors | |
| 945 lbs including cables | |
The P-CIP shall meet the following electrical requirements:
| 9900 watts steady state power dissipation | |
The P-CIP shall operate reliably in the CIG/SS Testbed environment and shall meet the following environmental requirements:
| 900 cu ft/min, 1 inch of water (minimum) and 55 degrees maximum inlet air temperature. (Provided by the CIG/SS | N/A | |
| 20% to 95% (Non-condensing) | 20% to 95% (Non-condensing) | |
The design goal is that the P-CIP image processing capability provide improved image quality over existing systems with a design threshold of no degradation in image quality from existing processing systems.
The P-CIP hardware and software shall be functionally and operationally modular to allow for system modification and expansion. The system hardware and software shall accommodate the initial baseline processing requirement with the capability to support growth requirements. The system architecture must be open to allow continued use as hardware processors and operating systems are upgraded. The desire is to minimize the need for software "rewrites" as processor technology improves.
The P-CIP shall use Commercial Off the Shelf (COTS) components to the maximum extent possible and be constructed to best commercial practices.
The P-CIP design shall comply with the requirements for processing Sensitive Compartmented Information (SCI), as defined in DIAM 50-4, up to TS/SI/TK but be capable of operating at the COLLATERAL classified level. The P-CIP shall be capable of being sanitized and downgraded to the UNCLASSIFIED level as a goal with a threshold of SECRET collateral level for transport, storage and maintenance. The Service implementation requirements are addressed in the Appendixes A through D of this document.
The P-CIP shall implement a POSIX compliant system architecture in accordance with the CIG/SS Handbook.
No modification will be made to the COTS operating system.
The P-CIP software shall be designed to be portable between different hardware platforms having similar architectures. The design will accommodate major changes in the applications software, such as new processing functions, and support different/upgraded hardware over its life cycle. The software design shall minimize life cycle maintenance costs.
All code shall be portable, documented in accordance with best commercial practice, and maintainable. Portability of newly developed software shall be maximized and interfaces to hardware elements will be isolated and replaceable. Software will be developed and documented in accordance with a contractor proposed software development methodology. Software for formatting and compressing the image data shall be certifiable to NITF 2.0 level 6 per JIEO Circular 9008.
Documentation shall be generated and delivered in accordance with the Statement of Work and the Contract Data Requirements List (CDRL).
Prior to final Government acceptance the P-CIP will be tested to ensure both physical and functional compatibility between the hardware and software and between external and internal interfaces. Testing shall be done to determine compliance with the requirements in Section 3 of this document.
The Contractor shall be responsible for the performance of all verification requirements of this specification. Government representative(s) designated by the Responsible Test Organization through the Procuring Contracting Officer will witness all verification activities and will certify test data.
The contractor shall conduct Preliminary Acceptance Tests in accordance with procedures developed by the contractor and approved by the Government. Testing shall be done to determine compliance with the requirements in Section 3 of this document.
The contractor shall conduct Final Acceptance Tests to verify the P-CIP's ability to support the requirements called out in Section 3 of this document. The contractor shall conduct tests to verify the P-CIP's ability to support the external interfaces called out in paragraphs 3.2.2.1.2, 3.2.2.2, 3.2.2.3.1 and 3.2.2.3.2. The Final Acceptance Tests will be conducted at the CIG/SS Testbed.
The P-CIP shall be packaged for delivery according to best commercial practices. Packaging shall protect the equipment against damage when shipped by normal commercial or military means, e.g. military truck or aircraft, etc.
AF-CIP United States Air Force CIP
USA-CIP United States Army CIP
ASARS Advanced Synthetic Aperture System - 2
ATM Asynchronous Transmission Mode
ATARS Advanced Tactical Air Reconnaissance System
ATR Automatic Target Recognition
ANSI American National Standards Institute
B/W Black and White
C Centigrade
CARS Contingency Airborne Reconnaissance System
CAWS Commercial Analysis Workstation
CDL Common Data Link
CFM Cubic Feet per Minute
CHBDL-ST Common High Bandwidth Data Link - Shipboard Terminal
CIG/SS Common Imagery Ground/Surface System
CIP Common Imagery Processor
COMINT Communications Intelligence
COTS Commercial Off The Shelf
dB Decibel
dBa Weighted noise power in decibels referred to 3.16 picowatts
(-85dBm) which is 0 dBa
DCSRi Digital Cassette Recorder System improved
EMI Electromagnetic Interference
ELINT Electronic Intelligence
EO Electro-optical
Expl Exploitation
FDDI Fiber Data Distributed Interface
GENSER General service
GOTS Government Off The Shelf
HAE High Altitude Endurance
H-SIP
Hz Hertz
ICD Interface Control Document
IFSAR
IPA
IESS Imagery Exploitation Support System
IR Infrared
JIEO Joint Interoperability and Engineering Office (DISA)
JSIP Joint Service Imagery Processor
JSIPS-N Joint Service Imagery Processing System - Navy
LAN Local Area Network
LO HAE Low Observable High Altitude Endurance
MAE Medium Altitude Endurance
MC-CIP United States Marine Corps CIP
MM Millimeters
ms millisecond
MSI Multi-Spectral Imagery
N/A Not Applicable
NIS National Input Segment
NITF National Imagery Transmission Format
PAL Phase Alternate Lock
P3I Preprogrammed Product Improvement
P-CIP Prototype Common Imagery Processor
POSIX Portable Operating System Interface
RMS Root Mean Square
RUG Radar Upgrade Program
SAR Synthetic Aperture Radar
SCI Sensitive Compartmented Information
SPA Strike Planning Achieve
SYERS Senior Year Electro-optical Reconnaissance System
TBD To Be Determined
TBR To Be Resolved
TES Tactical Exploitation System
TIS Tactical Input Segment
UAV Unattended / Unmanned Aerial Vehicle
UPS Uninterruptable Power Supply
USA United States Army
USAF United States Air Force
USMC United States Marine Corps
USN United States Navy
USN-CIP United States Navy CIP
This appendix addresses requirements for the Army specific implementation of the CIP. The U.S. Army CIP (USA-CIP) implementation shall include all functionality required in the baseline P-CIP Technical Requirements Document in addition to the requirements called out in this appendix.
A.3.2.1 Performance Requirements
A.3.2.1.8.1 Screener Workstation
The USA-CIP shall interface to (TBD-5) COTS screener workstation(s). The workstation(s) will perform image quality control functions. The workstation(s) will support dynamic retasking functions and dynamic assignment of exploitation to other workstations. The workstations will perform dynamic ad-hoc exploitation and reporting in support of time sensitive battlefield exploitation requirements.
A.3.2.1.9 Automatic Target Recognition Support
The USA-CIP shall provide processed imagery, complex SAR data and support data to the Tactical Exploitation Station (TES) Automatic Target Recognition processor in accordance with ICD (TBD-6).
The USA-CIP shall process all modes of all baseline sensors and be capable of supporting Pre-Planned Product Improvement (P3I)s to process (TBD-7) growth sensors. USA-CIP P3I's will be planned to support; IFSAR (TBR-8), and SAR data processing to provide ground elevation (TBR-9), ELINT and COMINT External Parametric data from the (TBD-10) sensor.
A.3.2.2.2 Interface Requirements
The USA-CIP shall interface to the following:
a. ATM (TBR-11) imagery LAN
b. Ethernet (TBR-12) data LAN
c. IESS Host Data Base via the data LAN in accordance with ICD 20K22 (TBR-13)
d. MIST CDL
e. T-1 SATCOM or terrestrial circuit to receive unprocessed and processed data from the U-2, UAV and ATARS sensors
f. Tactical Exploitation System (TES) System Manager (TBR-14) via the data LAN for transfer of status and data.
g. DCRSi tape recorder for replay of data from the CDL and for play of sensor data recorded on board the ATARS.
h. ANSI ID-1 tape recorder for replay of data from the CDL and for play of sensor data recorded on board the ATARS.
A.3.2.3 Physical Characteristics
The USA-CIP shall occupy no more than one 72" height standard 19" rack with a threshold of no more than two 72" height standard 19" racks. The equipment depth shall be no greater than 27" including cables and connectors.
The USA-CIP shall be packaged for installation in standard 19" racks. Form factor shall be specified in ICD (TBD-15) Operating Conditions
A.3.2.5 Environmental Requirements
COTS capabilities. The TES will provide (TBD-16) cubic feet per minute (cfm) of air flow, a minimum of 1 (TBR-17) inch of water, and a maximum inlet floor (TBR-18)) air temperature of 55 degrees F (TBR-19). Cooling air distribution shall be as specified in ICD (TBD-20).
Nonoperating Conditions:
The TES will provide a controlled temperature and humidity environment to support the USA-CIP COTS requirements in accordance with ICD (TBD-21). The USA-CIP shall withstand pressures from sea level to 40,000 feet in a nonoperating environment.
The TES will provide controlled temperatures ( 22 +/ - 2 degrees C (TBR-22)) and humidity (45% +/-10%(TBR-23)) operating environments to support USA-CIP requirements in accordance with ICD (TBD-24). The USA-CIP shall be capable of operating from sea level to 10,000 feet.
The USA-CIP shall provide COTS capability with protection provided by shock mounts between the USA-CIP equipment and the rack(s) and between the rack(s) and the shelter. The USA-CIP equipment when rack mounted in the TES shelter shall not require any special securing devices or transport cases for transportation. Equipment shock isolation shall be as specified in ICD (TBD-25).
The USA-CIP shall not generate acoustic noise as measured at ear level in excess of 56 dBa.
The USA-CIP design shall comply with the requirements for processing of Sensitive Compartmented Information SCI as defined in DIAM 50-4, up to TS/SI/TK within the TES which will be accredited to operate at the SCI System High level. The USA-CIP shall be capable of being sanitized and downgraded to the UNCLASSIFIED level as a goal with a threshold of SECRET collateral level for transport, storage and maintenance.
B3.2.2 External Interface Requirements
The United States Air Force CIP (AF-CIP) shall interface with the following systems:
a. CDL
b. DCRSi
c. ANSI-ID-1 Helical Tape
d. ATM/OC3/OC12 with TCP/IP
B3.2.3 Physical Characteristics
The AF-CIP shall meet the following physical requirements:
| Depth - Racks | 28 inches max |
| Height - Racks | 65 inches max height including shock mount |
| Height AF-CIP | Not more than 60 inches of rack space |
| Width - Racks | Standard 19 inch computer rack |
| Max Weight - AF-CAP | 200 (TBR-26) lbs. |
B3.2.4 Electrical Requirements
The AF-CIP shall meet the following electrical requirements:
| Power | 2 KW (supplied protection - voltage regulation, transients, over/under voltage |
B3.2.5 Environmental Requirements
The AF-CIP shall meet the following environmental requirements:
| Altitude | 8,000 ft | 40,000 ft | |
| Cooling | (TBD-27) Btu/hr | N/A | |
| Humidity | 20% to 80% (Non-condensing) | 20% to 80% (Non-condensing) | |
| Acoustic Noise | 75 dB total | NA | |
| Shock Transporting |
| ||
| External Temperature Range | -40 C to +49 C | -46 C to +63 C | |
| Internal Temperature Range | 18 C to +30 C | ||
| Vibration | N/A | 2 Gís RMS, random, across frequency range 1-200 Hz | |
B3.2.8 Reliability/Availability Requirements
The AF-CIP shall provide a MTBF of 5000 hours or greater.
The AF-CIP shall provide the following function needs as applied to current /future sensors (framing type sensors, ATARS LAEO/MAEO/IRLS followed by APG-73 SAR and others as identified herein.
The AF-CIP hardware shall be capable of meeting the following requirements;
a. Pixel data type (8-11 b/p)/operators
b. Integer data type/operators
c. String data type (variable) / operators
d. Addressing modes
e. Memory management/ protection and memory hierarchy (cache, MM)
f. Multi-computer with non-blocking memory / device access
g. Expandability in all dimensions (slots, cache, MM, CPU's, ports, buses)
h. Non-blocking I/O with error detection / correction
i. Modular design
j. Programmable timer support
k. Power failure support
The AF-CIP shall exist as a back end subsystem and shall be serviced by a workstation based front end system(s) using the client - server mode.
The AF-CIP shall support a pipelined data flow within the AF-CIP elements.
The system shall be shock mounted in transit cases.
C.3.2.2.1 Sensor Interface Requirements
The United States Marine Corps CIP (MC-CIP) shall interface with the following sensors:
a. CDL/ATARS
b. CDL/ASARS-2
c. ATM (TBR-28)
C.3.2.2.2 Tape Recorder Interfaces
The MC-CIP shall interface with an ANSI ID-1 helical tape recorder
C.3.2.3 Physical Characteristics
The MC-CIP shall meet the following electrical requirements:
| Depth - Racks | 28 inches maximum |
| Height - Racks | 65 inches maximum including shock mounts |
| Width - Racks | Standard 19 inch racks |
| Noise - Acoustic | 75 dB Maximum (TBR-29) |
| Max Weight | 200 lbs |
C.3.2.4 Electrical Requirements
The MC-CIP shall meet the following electrical requirements:
| Frequency | |
| Power | 2 KW maximum - supplied with protection - voltage regulation, transients, over/under voltage |
C.3.2.5 Environmental Requirements
The MC-CIP shall meet the following environmental requirements:
| Altitude | 8,000 ft | 40,000 ft |
| Cooling - External Temperature Range | -40 to +49 degrees C | -46 to +63 degrees C |
| Cooling - Internal Temperature Range | 18 to +30 degrees C |
|
| Humidity | 20 - 80% non condensing | 20 - 80% non condensing |
| Inclination | ||
| Shock Operating | ||
| Shock Transporting | ||
| Temperature | ||
| Vibration | 2 Gís RMS, random, across frequency range 1-200 Hz | |
D.3.1 Definition and Requirements
The United States Navy CIP (USN-CIP) will become an integral part of the Tactical Input Segment (TIS) of the Joint Services Imagery Processing System - Navy (JSIPS-N). Due to severe space limitations on some platforms where the TIS will be installed size is a very important consideration. This TIS will include a COTS screener/ exploitation workstation and an Uninterruptable Power Supply (UPS).
D3.2.1.8.4 Management Element Interface.
Management functions for the USN-CIP will be performed by the IESS in the Navy National Input Segment (NIS).
The USN-CIP shall interface to an FDDI (TBR-30) Imagery/ data LAN.
D3.2.2.1.1 Sensor Interface Requirements
The USN-CIP shall interface to the Common High Bandwidth Data Link - Shipboard Terminal (CHBDL-ST) in all modes and channelization of the target sensor. It will receive all processed and unprocessed EO/IR/SAR and video data from the U-2, UAVs and ATARS sensors.
The USN-CIP shall accept and process all baseline sensor modes and in addition be capable of processing F/A-18 RUG Phase II SAR data.
D3.2.2.2 Input Interface Requirements
The USN-CIP shall output data to the Strike Planning Archive (SPA) in NITF 2.0 format with data extensions.
D3.2.2.2 Tape Recorder Interfaces
The USN-CIP shall interface to an ANSI ID-1 tape recorder for the replay of data recorded from the CHBDL-ST and for play of sensor data recorded onboard the ATARS platform in accordance with ICD F/A-18-0064.
D3.2.2.3.2 Exploitation Screener Interface Requirements.
The USN-CIP shall interface to at least 1 and as many as (TBR-31) COTS screener/ exploitation workstation(s). This workstations will be a Navy TAC series computer.
D3.2.3 Physical Characteristics
The USN-CIP shall be sized such that it meets the following physical requirements:
| Depth - Racks | 27 inches maximum, including cables and retractors |
| Height - Racks | Maximum rack height of 72 inches including shock mounting |
| Height - CIP | The USN-CIP design goal is that it occupy no more than a total of 74 inches of vertical rack space |
| Width - Racks | Standard 19 inch computer rack |
| Max Component Size | Modular components shall be sized so that during transport they fit through a standard shipboard hatch |
| Max Weight - components | Shall not exceed the 2-man lift weight limits |
D3.2.4 Electrical Requirements
The USN-CIP shall be designed to meet the following electrical requirements:
| Power | MIL-STD-1399 Section 300 |
| EMI | FCC Part 15, Subpart J, Class B |
D3.2.5 Environmental Requirements
The USN-CIP shall be designed to meet the following environmental
requirements:
| Altitude | 0 to 6,000 ft | 0 to 40,000 ft |
| Cooling | Ambient Air CoolingThe temperature differential from intake to exhaust shall not exceed 10 degrees F | N/A |
| Humidity | 20 - 80% (Non-condensing) | 5 - 95% (Non-condensing) |
| Inclination | 10 Degrees | 30 Degrees |
| Noise | The USN-CIP shall not generate noise (as measured at ear level) higher than 56 dBa |
|
| Shock Operating (When rack mounted) | MIL-S-901, Grade B; 20G, 11ms half - sine wave 3 times each axis | |
| Shock Transporting | MIL-STD-810D, Procedure I, using 20G, 11ms sine wave pulse | |
| Temperature | 10 degrees to 40 degrees C | -10 C to 54 degrees C |
| Vibration | MIL-STD-167-1 Type 1 | MIL-STD-167-1 Type 1 |
D3.3.1 Security
The USN-CIP will operate as a GENSER piece of equipment and shall provide and demonstrate an accreditable mechanism for isolating SCI processing, storage and exploitation elements from unclassified input circuits. The USN-CIP shall be capable of being sanitized and downgraded to the Unclassified level. Additionally, the USN-CIP shall:
a. Demonstrate isolation from the unclassified CHBDL-ST antenna
b. Demonstrate isolation from the SCI imagery LAN.