Attachment_1-_SOW_-_Revision_1.pdf

Solicitation Number: N00173‐15‐R‐SE04 Attachment 1

Combined EO/IR Surveillance and Response System Program

(CESARS) – Multispectral EO/IR Countermeasures for Advanced Threats (MEIRCAT)

Revision 1 – 7/7/2015

Background

The Combined EO/IR Surveillance and Response System (CESARS) program is an ONR Future Naval Capabilities (FNC) effort scheduled to start in FY16 that provides comprehensive shipboard defense against optically guided anti-ship missile threats. The program objective is to develop a TRL6 maturity level system suitable for limited testing onboard a naval vessel. It includes an enhanced electro-optic/infrared (EO/IR) countermeasure (CM) and situational awareness capability. There are two distinct functions defined within the FNC that constitute CESARS: Shipboard Panoramic EO/IR Cueing and Surveillance System (SPECSS) and Multispectral EO/IR Countermeasures for Advanced Threats (MEIRCAT).

The primary function of SPECSS is to perform wide field-of-view target detection and tracking, with subsequent cueing of MEIRCAT high-resolution sensors. The primary threats that define the requirements for SPECSS are anti-ship missiles and FAC/FIAC (Fast Attack Craft/Fast Inshore Attack Craft). The threats of secondary importance are unmanned aerial vehicles

(UAV).

The functions of the MEIRCAT system are target acquisition, tracking, classification/identification, 3-D ranging, threat assessment, CM execution and CM effectiveness assessment (CMEA). Multi-band capability against multiple targets in rapid sequential engagements in a single test run is required for MEIRCAT. The threats, timelines, field of regard coverage, threat assessment, CM execution, and CMEA will be specified in a classified MEIRCAT document.

Scope

The Department of Defense (DoD) has a Modular Open Systems Approach (MOSA) vision in order to control costs and minimize logistic demands for future systems. Modular, open-systems hardware and software architectures that are scalable to different platforms are required under this effort. The overall system design approach is expected to leverage common imaging components and technologies to the largest extent possible. The end goal of this more flexible design strategy is to reduce the total cost of ownership (maintenance and repair), as well as to provide a simpler, more cost effective approach to upgrade the system as newer technologies become available. All interface specifications and data formats for this effort shall be non-proprietary and government owned. The government seeks Government Purpose Rights (DFARS 252.227-7013 Rights in Technical Data--Noncommercial Items) for software and technical data associated with this effort.

The overall CESARS system must provide the following basic capabilities:

Wide field-of-view (WFOV) situational awareness across multiple wavebands Automated multi-target detection, tracking, and cueing algorithms Video data acquisition, dissemination, recording, processing, and display High resolution classification, identification and tracking in multiple wavebands Integrated, precise, and real-time, active-and-passive fine tracking (including range) in multiple wavebands Enhanced CM capability against current and advanced multi‐band EO/IR threats

Precise 3‐D ranging and CMEA information to the shipboard combat system

This procurement activity addresses the development of the sensors, lasers and the fully integrated MEIRCAT beam control, pointing, and processing systems related to the CESARS EOIR countermeasures capability. These capabilities are provided by three primary technology development efforts to be funded as described in the subsequent Work Requirements sections 1-

3. A block diagram detailing how these efforts relate to the overall CESARS system architecture is provided in Fig. 1. Award(s) will be based on responses to one or more of the technology product descriptions detailed in the accompanying Work Requirements section. In some instances technical performance metrics in the Work Requirements section are categorized as a baseline (B) and an extended (E) capability. These values are intended to communicate what the government believes are a realistic range of values that are consistent with the overall required system performance. Single values for performance metrics are to be interpreted as baselines.

Proposals that offer an approach with minor deviations from the baseline metrics with compelling technical, risk, or cost justification will be considered. In all cases, finalization of these metrics within the scope and design concept described by the original proposal will occur in consultation with the government after contract award as the result of a performance / technical risk / acquisition cost trade study performed by the chosen supplier. System design parameters that are to be considered as part of that analysis shall be identified in the proposal.

Offerors are invited to respond to any or all products. If an offeror responds to more than one product a single proposal may be submitted, but each task must be priced separately. In the event that an offeror is selected for more than one task a single contract may be awarded to cover multiple topics. Proposals for any product must provide the full complement of capabilities described. Teaming arrangements as part of a proposal to achieve full compliance are acceptable. NRL reserves the right to make multiple awards for the same task with subsequent down selection.

Figure 1

Full System Integration

The integration of the SPECSS and MEIRCAT subsystems to achieve the full CESARS system realization will be executed by the government. Therefore, the SPECSS and MEIRCAT technology product providers shall work with the government to ensure reliable and robust data exchange between individual products. This shall entail establishing hardware and data interchange standards which are non-proprietary and government-owned. NRL will not be soliciting a separate performer for this task as part of this procurement.

Work Requirements

1. MEIRCAT high-resolution target identification and tracking cameras - The contractor shall design, build or procure, and test high resolution LWIR, MWIR, and visible spectrum sensors in accordance with the performance requirements described below. In addition to a single copy of each complete sensor the contractor shall also provide a shop replaceable spare subassembly for each sensor. The spare sub-assemblies shall include at a minimum a detector module capable of interfacing to the camera optics and generating the required electrical input signal to the camera video electronics. In preparation for the program kickoff/concept design review meeting the contractor shall perform a performance/technical risk/projected acquisition cost trade study to guide refinement of the details for the proposed approach.

MEIRCAT sensing shall include a multi-band, high-resolution, high-frame-rate capability to support the target classification/identification, active and passive tracking, and CMEA functions carried out by the processing performed by the integrated MEIRCAT system (not part of this task, see Figure 1). The sensor(s) line-of-sight (LOS) shall be directed by the MEIRCAT hardware tracking system (see Figure 1) which will orient the MEIRCAT sensor(s) toward the target queue received from the SPECSS system. To meet program goals, it is desired that the sensor(s) must possess the following capabilities:

Wavebands: 400 - 700 nm (RGB) (B) and 550 - 950 nm panchromatic (E), 3.0 - 5.3 m with CO2 notch filter (MWIR), & 8.0-12 m (LWIR). Additional spectral bands (e.g.

SWIR) may be proposed with adequate justification for the enhanced capability and explanation of the additional cost and risk resulting from their inclusion.

IFOV: ≤ 12 rad (VIS), ≤ 12 rad (MWIR), ≤ 50 rad (LWIR) FOV (degrees): 2.5 V x 2.5 H (B), 4 V x 3 H (E) Sensitivity: NEDT ≤ 25 mK (MWIR & LWIR); NEI ≤ 8.0x10-15 W/cm2 (B) ≤ 2.0x10-15

W/cm2 (E) (MWIR), ≤ 2.0x10-14 W/cm2 (B) ≤ 5.0x10-15 W/cm2 (E) (LWIR), ≤3x10-9 lux (visible)

Dynamic range: 60dB (VIS), 75dB (MWIR & LWIR)

ROIC:

o Gating: Capable of receiving external frame start (trigger) pulse; Integration start time delay from frame start programmable from 0-200 sec; Timing jitter must be ≤ ½ (B), ≤ 1/10 (E) of the gate-timing resolution: ≤ 100 ns (B), ≤ 0.1 ns (E) o Full-frame output: 60 Hz (B), 120 Hz (E) o Windowed output: ≥ 10 kHz (B), ≥ 20 kHz (E), for ≥ 32x32 (B), ≥ 64x64 (E) (all wavebands) o Integration time: 1 sec up to 16 msec o Bit depth: ≥14 bit (single frame)

Preferred digital output: 10 Gigabit Ethernet over fiber with required simultaneous NTSC analog output

The following table details the method by which the contractor is to verify conformance to the MEIRCAT High Resolution Sensor hardware requirements as part of the effort.

TABLE 3 MEIRCAT High Resolution Sensor Hardware Performance Verification Matrix

Attribute Verification Method Design Analysis Inspection Test Wavebands: 400-700 nm (RGB) (B) and 550-950 nm panchromatic (E), 3.0-5.3 m (MWIR), & 8.0- 12 m (LWIR)

X X

IFOV: ≤ 12 rad (VIS), ≤ 12 rad (MWIR), ≤ 50 rad (LWIR)

X X

FOV (degrees): 2.5 V x 2.5 H (B), 4 V x 3 H (E) X X Sensitivity: ≤ 25 mK NEDT (MWIR & LWIR), NEI ≤ 8.0x10-15 W/cm2 (B) ≤ 2.0x10-15 W/cm2 (E) (MWIR), ≤ 2.0x10-14 W/cm2 (B) ≤ 5.0x10-15 W/cm2

(E) (LWIR), ≤3x10-9 lux (visible)

X X

Dynamic range: 60 dB (VIS), 75 dB (MWIR &

LWIR)

X X

Full-frame output: 60 Hz (B), 120 Hz (E) X X Windowed output: ≥ 10 kHz (B), ≥ 20 kHz (E), for ≥ 32x32 (B), ≥ 64x64 (E) (all wavebands)

X X

Integration time: 1 sec up to 16 msec X X Bit depth: ≥ 14 bit (single frame) X Gating: Capable of receiving external frame start pulse; Integration start time delay from frame start programmable from 0-200 sec

X X

Gate-timing resolution: ≤ 100ns (B), ≤ 0.1ns (E) X X The jitter must be less than 1/2 (B), 1/10 (E) of the gate-timing resolution

X X

Interface requirements (e.g., mechanical, electrical, etc.) will be jointly determined by the sensor provider as well as the MEIRCAT PI and MEIRCAT integrator post contract award. All interface specifications shall be non-proprietary, government owned, and as modular as possible.

As with the panoramic SPECSS sensor, an emphasis will be placed on proposals that address the issue of common components and a modular architecture that could potentially enable other, stand-alone, high resolution shipboard imaging applications. To this end it is expected that the performer will make every effort to develop components (e.g., sensor chip assemblies, integrated dewar-cooler assemblies, video electronics, camera cores, etc.) that can be shared with the SPECSS Product 1.

2. MEIRCAT lasers - The contractor shall design, build or procure, and test laser sources in accordance with the detailed classified performance specifications described in the MEIRCAT hardware, software, integration, and testing specification, which will be available by request to approved contract facilities. See the attached DD 254 for additional information.

3. MEIRCAT Beam Control, Pointing and Processing - The contractor shall provide the overall systems engineering activities required for the MEIRCAT system. The contractor shall design, build, and test the turret/gimbal, including the optical bench, and window(s) required for the MEIRCAT system. The contractor shall supply Inertial Measurement Unit(s) required for tracking ship motion so that the target tracking is maintained. The contractor shall provide an environmental enclosure suitable for shipboard testing for the entire system (see CESARS Field Test Description). The contractor shall develop software architecture, write or procure the underlying code, procure supporting computing and network hardware, and test the integrated processing suite to support the MEIRCAT hardware.

The MEIRCAT software shall include countermeasure processing, transceiver to gimbal control, and system control processing. The MEIRCAT software must maintain relative coordinates of both imaging systems and targets in the ship coordinate system and provide high repetition rate line-of-sight (LOS) angular and range data for potential targets to Fire Control. The contractor shall be responsible for MEIRCAT target acquisition (from SPECSS queuing), image tracking, threat assessment, 3-D ranging, CM execution, and CMEA. The software shall have the ability to accept target queuing from the SPECSS system and interface with other ship’s systems.

The contractor shall interface with the government MEIRCAT PI and MEIRCAT component manufacturers (sensors, lasers, and processing) to define common interface requirements.

The contractor shall integrate the hardware developed under this product with the Government Furnished Equipment (GFE) MEIRCAT high-resolution sensor (see Figure 1, Product 1) and laser (Product 2) with the system software and perform testing of the integrated MEIRCAT subsystem. The MERICAT integrator will be responsible for the physical architecture of the beam director and the integrated optical bench, beam alignments, stabilization, environmental protections, pointing / tracking, and 3-D tracking. This pointing system shall provide LOS inertial stabilization, alignment, and pointing control of the lasers and cameras. To do this, the pointing system will require inertial sensors, turret/gimbal, optical bench, beam optics, pointer controller, and output window(s). The MEIRCAT integrator must provide the appropriate environmental protection (see CESARS Field Test Description) for the MEIRCAT hardware during testing and storage.

The MEIRCAT integrator shall demonstrate the capability to accept cues from SPECSS.

Additionally, the contractor is responsible for the detailed performance specifications as described in a document titled MEIRCAT hardware, software, integration, and testing specification, which will be available by request to approved contract facilities. See the attached DD 254 for additional information.

The MEIRCAT integrator shall coordinate with the MEIRCAT PI to satisfy Safety, and Predictive Avoidance compliance for field testing (see CESARS Field Test Description).

To satisfy the safety and Predictive Avoidance compliance, MEIRCAT integrator shall coordinate with the MEIRCAT PI to support development of a safety and test plan that must be approved by the Navy Laser Safety Review Board (LSRB) and other compliance agencies. The MEIRCAT PI will perform the predominate amount of the safety and test plan writing. Based on the guidance of the Navy LSRB, a Predictive Avoidance system may need to be developed by the MEIRCAT integrator for compliance.

Supplemental information applicable to all CESARS products:

All CESARS components shall be accompanied with full documentation. The contractors shall coordinate with the CESARS PIs to satisfy the following requirements as they apply to shipboard systems. CESARS shall be designed to meet the environmental, mechanical, and electrical requirements during the duration of the CESARS field testing and demonstration (see CESARS Field Test Description), specifically:

Support MIL-STD-167-1A Type 1 and MIL-STD-810G, Method 514.5, Categories 2 and 21 (Transportation and Shipboard vibration) requirements (B);

All systems and components shall be electrically compatible with both shore-based and shipboard power generation systems (B);

Support minimum shock requirements for CESARS field testing on a Navy vessel for a sea-state of 4 (B), support minimum MIL-S-901D Grade B, Type A, Class I or II Shock (E);

Support EMI requirements for CESARS field testing on a Navy vessel for a sea-state of 5 (B), and as defined by MIL-STD-461F (E);

Environmental o Component storage: -20C to 60C (B), -40C to 70C (E);

o Ambient operating temperature: -10C to 40C (B), -28C to 65C (E);

o Solar radiation: 350 BTU/hr/ft2 (B);

o System shall survive exposure to the following conditions during testing:

Blowing rain during the duration of the CESARS field testing (B) and using MIL-STD-810G section 506.5 Procedure I at 4.7 in/hr (E);

Hot-humid and absolute humidity during the duration of the CESARS field testing (B) and using MIL-STD-810G section 507.5 (E);

Salt fog during the duration of the CESARS field testing (B) and using MIL-STD-810G section 509.5 (E);

Blowing dust during the duration of the CESARS field testing (B) and using MIL-STD-810G section 510.5 Procedure I at 18 knots (E);

Blowing sand during the duration of the CESARS field testing (B) and using MIL-STD-810G section 510.5 Procedure II at 35 knots (E);

Stabilization at sea state 4 (B), 5 (E);

Wind speed of 40 (B), 55 (E) knots (E);

Functional shock during the duration of the CESARS field testing (B) and using MIL-STD-810G section 516.6 Procedure I at 40 Gs sawtooth for 23 ms on all three (3) axes (E);

Vibration during the duration of the CESARS field testing (B) and using MIL-STD-810G section 514.6 Category 14, Table 514.6D-III, General Material Location and Figure 514.6D-3 (E);

Cabling o The interface cable assemblies shall comply with MIL-DTL-24643C and MIL-

STD-461F (B);

o If Fiber Optic cables are used the cable assemblies shall comply with MIL-STD-

2042B Note 1 and MIL-PRF-85045G (B);

o As an objective the total number of cables shall be kept to a minimum without a reduction in system performance (E);

CESARS Field Test Description

NRL will design and direct field tests of CESARS at NRL or other Navy facilities in the Washington, DC area. Contractor support for this from the product providers is expected to be required, but will be the subject of a future procurement activity. CESARS testing will be conducted on land, followed by at-sea, against static and dynamic targets. The primary land test site will be NRL/Chesapeake Bay Detachment (CBD) where CESARS will be located. A Navy vessel will be used to install CESARS for over-the-water testing on the Chesapeake Bay and/or in a Navy controlled test site such as the Virginia Capes. Static targets will mainly be installed in a tower at Tilghman Island on the Chesapeake Bay. Dynamic targets could include airborne captive-carry and aircraft towed as well as boat mounted systems. The predominance of the CESARS field testing will be conducted on the MEIRCAT subsystem. The final CESARS field testing and demonstration will be conducted on the entire CESARS hardware and software.

To protect CESARS optics and EO/IR components from the harsh land-based (salty air) and shipboard environment (sea spray) when CESARS is not operational or between tests, a system design that incorporates retractable MEIRCAT (and possibly SPECSS) transceiver components in the CESARS enclosure (an example, but not a required approach, a standard shipping container is shown in Figure 2) is required. The production of the CESARS enclosure will be the responsibility of the MEIRCAT system integrator.

At least one of the extended requirement MEIRCAT sources will require an independent land-based testing to evaluate its effectiveness against various targets at tactical ranges. It is anticipated that this source(s) will be integrated into MEIRCAT after the evaluation test is completed. For further description of CESARS testing and a plausible CESARS housing design and shipboard installation, please see P. Mak et al, “SHIELDS Field Test Results (U),” Proc.

2009 MSS IRCM Symposium (2009).

Figure 2 Security Requirements

All Contractor personnel who require NRL base access or access to NRL unclassified material and/or unclassified systems shall possess a favorably completed DoD National Agency Check with Law and Credit (NACLC). Contractors who require access to Secret material must have, at a minimum, a favorably completed DoD National Agency Check with Law and Credit (NACLC) and final DoD granted Secret security clearance the time of proposal submission. Foreign Nationals are not authorized to work on the contract. The Contractor shall ensure that all classified material is handled in accordance with the issued DD 254, the National Security Program Operating Manual (NISPOM) (DoD 5220.22M) and all NRL and applicable Security Program Guides/Directives.

Combined EO/IR Surveillance and Response System Program

(CESARS) – Multispectral EO/IR Countermeasures for Advanced Threats (MEIRCAT)

Data Item # Product 1 Product 2 Product 3 A001

(KICKOFF slides) X X X

A002 (PDR slides)

X X X

A003 (CDR slides)

X X X

A004

(ATP)

X X X

A005

(ATR)

X X X

A006

(CFSR)

X X X

A007 (Monthly status)

X X X

A008 (User Manual)

X X X

A009 (Software source code)

X

A010 (Sys Spec)

X X X

A011 (Syst ICD)

X X X ericsogard Typewritten Text

N00173-15-R-SE04

Attachment (1) Exhibit (A) ericsogard Typewritten Text ericsogard Typewritten Text ericsogard Typewritten Text ericsogard Typewritten Text ericsogard Typewritten Text X ericsogard Typewritten Text X ericsogard