Attachment_2_RADAR_POR_Perf_Spec.pdf

Doc. # PMA-266 RADAR 002 Revision: Initial Supersedes: - Date: 3 September 2015

MQ-8C FIRE SCOUT SYSTEM

PERFORMANCE SPECIFICATION

For

RADAR System Program of Record

RFP Solicitation: N00019-15-R-4000 / Attachment (2)

Prepared for:

Navy and Marine Corps Multi-Mission Tactical UAS Program

Office (PMA-266)

22707 Cedar Point Road, Bldg. 3261

Patuxent River, MD 20670-1547

Distribution Statement A - Approved for public release; distribution is unlimited.

ii

Revisions

Rev Date

Paragraph(s)

Affected

Change/Rationale

Initial 2 December 2013 All Initial Release

17 July 2015 All <DRAFT> MQ-8C Radar RFP Release

3 September 2015 All <FORMAL> MQ-8C Radar RFP Release iv

Table of Contents

1.0 INTRODUCTION

1.1 SCOPE

1.2 SYSTEM OVERVIEW

1.3 DOCUMENT OVERVIEW

1.4 INTERPRETATION

2.0 APPLICABLE DOCUMENTS

2.1 DOCUMENTS FOR CONTRACT TECHNICAL COMPLIANCE

2.2 SPECIFICATIONS

2.3 STANDARDS

2.4 PUBLICATIONS

2.5 DIRECTIVES

3.0 REQUIREMENTS

3.1 REQUIRED STATES AND MODES

3.2 SYSTEM CAPABILITY REQUIREMENTS

3.3 SYSTEM EXTERNAL INTERFACE REQUIREMENTS

3.4 SYSTEM INTERNAL INTERFACE REQUIREMENTS

3.5 SAFETY REQUIREMENTS

3.6 SYSTEM SECURITY AND ANTI-TAMPER REQUIREMENTS

3.7 SYSTEM ENVIRONMENT REQUIREMENTS

3.8 SYSTEM QUALITY FACTORS

3.9 DESIGN AND CONSTRUCTION CONSTRAINTS

3.10 LOGISTICS-RELATED REQUIREMENTS

3.11 PACKAGING REQUIREMENTS

3.12 ENVIRONMENT, SAFETY, AND OCCUPATIONAL HEALTH

3.13 AIS

3.14 [O] RADAR SYSTEM GROWTH

4.0 VERIFICATION

4.1 SCOPE

4.2 VERIFICATION METHODS

5.0 ACRONYM LIST

APPENDIX A FUTURE UPGRADES

APPENDIX B NORMALIZED SEA CLUTTER

APPENDIX C RF ATMOSPHERIC ATTENUATION MODEL

1.0 Introduction

1.1 Scope

This specification, including classified Annex A, establishes the performance and test requirements for the Radar System to be installed and integrated with the MQ-8C aircraft and the processing, control and operator display at the Tactical Control Station (TCS). Desired elements

(capabilities) and their attributes have also been included herein as “Objectives”.

This specification will function as a stand-alone document and has the highest order of precedence. Where applicable, references to the System Specification for the Vertical Take-Off and Landing Tactical Unmanned Aerial Vehicle System (VTUAV) (Doc # C72-6100-013

Revision B) are made. Only the relevant and noted exceptions to C72-6100-013 Revision B will be included.

1.2 System Overview

The Radar System will be the primary littoral search system for the Navy MQ-8C aircraft, and the payload package is intended to remain on Air Vehicle once installed. The Radar System will incorporate maritime surveillance, target tracking and imaging modes and will contain provisions for overland modes. When reference is made to the Radar System, this includes requirements flowed down to interfacing subsystems associated with the referenced requirement, unless expressly stated otherwise herein.

Baseline aircraft definition: The definition of payloads and configuration envisioned for the

MQ-8C Fire Scout system is provided in Table 1-1 Mission Configurations.

The Radar System may consist of the following components:

A radar set consisting of an antenna, pedestal, receiver-transmitter, and a data processor;

A radome to protect the antenna and pedestal;

Software residing on the host vehicle for interfacing to the radar set;

Software residing in the TCS for display of radar information and radar control for the operator.

Table 1-1 Mission Configurations

Mission

Maritime Shore Based

Kit Item ISR/SUW ASW MIW SOF ISR SOF

BriteStar II X X X X X

AIS X X X X

Radar X X X X

Note 1: BriteStar II may be mutually exclusive

Denotes current baseline

The Radar System shall provide the following threshold capabilities:

Search, detection, surveillance, and tracking of surface vessels;

Logging, displaying and tracking Automatic Information System (AIS) track files at the

TCS;

Inverse Synthetic Aperture Radar (ISAR) imaging for surface vessel classification;

Synthetic Aperture Radar (SAR) imaging and targeting with multiple resolutions;

High Range Resolution (HRR) mode for improved target separation;

Interface with the host vehicle for radar control and display of radar data;

Display and control interfaces to the operator in the TCS;

Radome, if required, to enclose MQ-8C externally mounted Radar System hardware while minimizing its effect on radar Radio Fequency (RF) and aircraft performance;

Self-test and status monitor built-in-test (BIT).

1.3 Document Overview

Section 1 contains an overview of the Radar System.

Section 2 lists the documents referenced throughout this specification.

Section 3 defines the requirements for the Radar System.

Section 4 defines the qualification provisions for the Radar System.

Section 5 contains miscellaneous notes.

Appendix A defines the future upgrades for the Radar System.

Appendix B defines the normalized sea clutter model.

Appendix C defines the RF atmospheric attenuation model.

Appendix D contains the classified Radar System performance requirements.

1.4 Interpretation

Use of “shall,” “will,” and “may” within this specification, observes the following rules:

The word SHALL denotes the imperative.

The word MAY denotes the permissive.

The word WILL denotes a declaration of purpose on the part of the contracting agency.

Threshold requirements are preceded with a tag of the form “[T].” Objective requirements are preceded by a tag of the form “[O].” Threshold requirements must be met; an objective requirement denotes a desired level or performance above the threshold requirement.

When the objective tag “[O]” is used in a section title (such as: 3.2.13 [O] Weather Detection) the section referrs to a desired capability. However, if that capabiltiy is implemented there may be both threshold and objective requirements for that capability. These are denoted by tags within the section.

2.0 Applicable Documents

2.1 Documents for Contract Technical Compliance

The documents listed in this section are referenced in Section 3 of this specification. While every effort has been made to ensure the completeness of this list, document users are cautioned that they must meet all specified requirements of documents cited whether or not they are listed in Sections 2.2 and 2.3. Document version numbers/letters are used in section 2.2 and 2.3 but are not used in subsequent sections. The list of applicable documents represents current series guidance and instructions. Documents shall be per revision as of date of contract award unless otherwise noted. In the event of conflict between the requirements of the documents referenced herein and the contents of this specification, the specification shall be considered the superseding requirement.

2.2 Specifications

Document

Number

Date of Issue Description / Title

C72-6100-013

Revision B

19 Apr 2013 System Specification for the Vertical Take-off And

Landing Tactical Unmanned Aerial Vehicle System

(VTUAV)

C72-2000-001

Revision B

19 Apr 2013 Payload Element (PLE) Specification for the Vertical

Take-off and Landing Tactical Unmanned Aerial Vehicle

System (VTUAV)

C72-2000-002

Revision B

06 May 2013 Mission Management Subsystem Specification for the

Vertical Take-off and Landing Tactical Unmanned Aerial

Vehicle System (VTUAV)

C72-8000-006

Revision G

16 Oct 2013 Guidance Navigation and Control (GNC) Software

Requirements Specification (SRS) for the Vertical Take-off and Landing Tactical Unmanned Aerial Vehicle

System (VTUAV)

C72-1200-100

Revision B

14 Oct 2013 Avionics Interface Description Document (IDD) for the

Vertical Take-off and Landing Tactical Unmanned Aerial

Vehicle System (VTUAV) Endurance Upgrade (EU)

C72-1100-111 24 Jul 2013 Structural Design Requirements Bulletin (DRB) for the

Vertical Take-off and Landing Tactical Unmanned Aerial

Vehicle System (VTUAV) Endurance Upgrade (EU)

C72-1100-110

Revision A

22 Jul 2013 MQ-8C RDC Environmental Design Requirements

Bulletin (DRB) for the Vertical Take-off And Landing

Tactical Unmanned Aerial Vehicle System (VTUAV)

Endurance Upgrade (EU)

C72-8000-020 See GFI list Guidance Navigation and Control (GNC) Software

Requirements Specification (SRS) for the Vertical Take-off and Landing Tactical Unmanned Aerial Vehicle

System (VTUAV)

C72-8000-012 See GFI list Avionics Interface Description Document (IDD) for the

Vertical Take-off and Landing Tactical Unmanned Aerial

Vehicle System (VTUAV) Endurance Upgrade (EU)

PMA266 11-002

Revision 4

18 Jan 2012 Performance Specification for the VTUAV Endurance

Upgrade

N/A 9 Dec 2014

(Draft)

Capability Production Document (CPD) for MQ-8C Fire

Scout System

PMA299-07000 16 Oct 2009 MH-60R / Ship Combat System Interface Design

Specification

W1006415

Revision F

(Contract No.

N00019-98-C-

0190)

20 Dec 2015 Tactical Control System (TCS)

Chameleon Software Developer’s Toolkit (SDK)

Addendum 1 - Plug-and-Play (PnP) Payload Interface

Design Description (IDD)

2.3 Standards

Document Number Date of Issue Description / Title

MIL-STD-130N 17 Dec 2007 Identification Marking of U.S. Military Property

MIL-STD-1472F 23 Aug 1999 Human Engineering Design Criteria for Military

Systems, Equipment, and Facilities

MIL-STD-1686C 25 Oct 1995 Electrostatic Discharge Control Program for

Protection of Electrical and Electronic Parts, Assemblies and Equipment

MIL-STD-810G 31 Oct 2008 Environmental Engineering Considerations And

Laboratory Tests

MIL-STD-2525C 17 Nov 2008 Common War fighting Symbology

MIL-STD-704F 12 Mar 2004 Aircraft Electric Power Characteristics

SAE AS50881D 01 Jul 2010 Wiring Aerospace Vehicle

MIL-HDBK-454B 15 Apr 2007 General Guidelines for Electronic Equipment

PDU_SD (AT&L) Sep 2007 Corrosion Prevention and Control Planning

Guidebook

MIL-STD-464C 01 Dec 2010 Electromagnetic Environmental Effects

Requirements For Systems

MIL- STD-461F 10 Dec 2007 Requirements for the Control of Electromagnetic

Interference Characteristics of Subsystems and

Equipment

MIL-HDBK-237D 20 May 2005 Electromagnetic Environmental Effects And

Spectrum Certification Guidance For The

Acquisition Process

MIL-HDBK-217F 02 Dec 1991 Reliability Prediction of Electronic Equipment

MIL-STD-411F 10 Mar 1997 Aircrew Station Alerting Systems

MIL-HDBK-1812 14 Feb 1997 Type Designation, Assignment and Method for

Obtaining

MIL-DTL-18307H 28 Apr 2006 Nomenclature and Identification for Aeronautical

Systems Including Joint Electronics Type

Designated Systems and Associated Support

Systems

MIL-STD_882E 11 May 2012 DoD Standard Practice for System Safety

IETF RFC 3032 Jan 2001 MPLS Label Stack Encoding (Proposed Standard)

IETF RFC 3262 Jun 2002 Reliability of Provisional Responses in the Session

Initiation Protocol (SIP)

IETF RFC 4601 Aug 2006 Protocol Independent Multicast – Sparse Mode

(PIM-SM): Protocol Specification (Revised)

ISO/IEC 15444-2:2004 2004 Information technology – JPEG 2000 image coding system: Extensions

BPCGM01.00 30 Jun 2004 BIIF Profile for Computer Graphics Metafile, Version 01.00

Common Data Link

Communications

Standard

Waveform Specification for the Standard Common

Data Link

ISO 19107:2003 08 May 2003 Geographic information – Spatial schema

ISO 19108:2002 with

Cor 1:2006

12 Sep 2002 with Technical

Corrigendum 1, 16 Oct 2006

Geographic information – Temporal schema

ISO 19109:2005 23 Jun 2005 Geographic information – Rules for application schema

ISO 19110:2005 11 Feb 2005 Geographic information – Methodology for feature cataloguing

ISO 19111:2007 26 Jun 2007 Geographic information – Spatial referencing by coordinates

ISO 19112:2003 21 Oct 2003 Geographic information – Spatial referencing by geographic identifiers

ISO 19123:2005 31 Aug 2005 Geographic information – Schema for coverage geometry and functions

ISO/IEC 10589 Nov 2002 Information Technology – Telecommunications and Information Exchange Between Systems –

Intermediate Systems to Intermediate Systems

Intra-domain Routing Information Exchange

Protocol for Use in Conjunction with the Protocol for Providing the Connectionless-mode Network

Service (ISO 8473)

ISO/IEC 12087-5:1998 01 Dec 1998 Information Technology – Computer graphics and image processing – Image Processing and

Interchange (IPI) Functional specification – Part 5:

Basic Image Interchange Format (BIIF)

ISO/IEC 14772-1 1998 Computer Graphics and Image Processing – The

Virtual Reality Modeling Language – Part 1:

Functional specification and UTF-8 encoding

ISO/IEC 15444-1:2004,

ITU-T Rec. T.800

2004 Information Technology – JPEG 2000 image coding system: Core coding system

ISO/IEC 8632-1:1999

with Cor 1:2006

16 Dec 1999 with

Corrigendum 1, 24 Mar 2006

Information technology – Computer graphics –

Metafile for the storage and transfer for picture description information – Part 1: Functional specification

ISO/IEC 8632-3:1999

(Updated citation)

16 Dec 1999 Information Technology – Computer Graphics –

Metafile for the storage and transfer for picture description information – Part 3: Binary encoding

ISO/TS 19139:2007 17 Apr 2007 Geographic information – Metadata –XML schema implementation

ITU-T T.81 Sep 1992 Digital Compression and Coding of Continuous-tone Still Images – Requirements and Guidelines

MIL-STD-2500C 01 May 2006 National Imagery Transmission Format (Version

2.1) for the National Imagery Transmission Format

Standard

STANAG 4586, Ed. 2 08 Nov 2007 Standard Interfaces of UAV Control System (UCS) for NATO UAV Interoperability

STANAG 4607, Ed. 2 02 Aug 2007 NATO Ground Moving Target Indicator Format

(GMTIF)

STDI-0002 v3 01 Aug 2007 The Compendium of Controlled Extensions (CE) for the National Imagery Transmission Format

(NITF)

ARINC 706-6 15 Nov 1991 “Airborne Weather Radar (WXR)" standard

DO-173 19 Nov 1980 Minimum Operational Performance Standards for

Airborne Weather and Ground Mapping Pulsed

Radars

DO-178C 13 Dec 2011 Software Considerations in Airborne Systems and

Equipment Certification

DO-254 19 Apr 2000 Design Assurance Guidance For Airborne

Electronic Hardware

2.4 Publications

Document Number Date of Issue Description Title

NAVSEA OP 3565/

NAVAIR 16‐1‐529,

Vol. 1

01 Jun 2007 "Electromagnetic Radiation Hazards (Hazards to

Personnel, Fuel and Other Flammable Material)"

N/A 25 Oct 2007 Naval Open Architecture Contract Guidebook v1.1

MTMCTEA PAM 70-1 Transportability for Better Deployability

DFARS 252.211-7003 Unique Item Identification Requirements of DFARS

RTCA DO-173 1980 Minimum Operational Performance Standards for

Airborne Weather and Ground Mapping Pulsed

Radars

NAVSES TM S9310-

AQ-SAF-010

Aug 2004 Technical Manual for Batteries, Navy Lithium

Safety Program Responsibilities and Procedures.

A1-MQ8CA-NFM-000 TBD NATOPS Flight Manual Navy Model MQ-8C

Unmanned Aerial Vehicle

A1-MQ8CA-NFM-500 TBD NATOPS Pocket Checklist Navy Model MQ-8C

Unmanned Aerial Vehicle

A1-MQ8CA-NFM-700 TBD NATOPS Functional Checkflight Checklist Navy

Model MQ-8C Unmanned Aerial Vehicle

NTRP 3-22.4 MQ8BA 15 Feb 2012 with Change 1

(01Apr 2012)

Naval Tactical Reference Publication

2.5 Directives

DoDD 8500.1 24 Oct 2002 Information Assurance (IA)

DoD Inst 8500.2 06 Feb 2003 Information Assurance (IA) Implementation

DoD Inst 8510.01 28 Nov 2007 DoD Information Assurance (IA) Certification and

Accreditation Process (DIACAP)

CJCSI 6510.01F 09 Feb 2011 Information Assurance (IA) and Computer Network

Defense (CND)

DoDD 5200.39 10 Sep 1997 Security, Intelligence, and Counterintelligence

Support to Acquisition Program Protection

DoD Inst 5200.39 28 Dec 2010 Critical Program Information (CPI) Protection

Within the Department of Defense

DoD Inst 5000.2 08 Dec 2008 Operation of the Defense Acquisition System

DoD Inst S-5230.28 26 May 2005 Low Observable (LO) and Counter Low Observable

(CLO) Programs

DoD Interim Defense

Acquisition Guidebook, (formerly 5000.2-R)

30 Oct 2002 DoD Interim Defense Acquisition Guidebook

DON CIO

Memorandum

03 Jul 2007 Encryption of Sensitive Unclassified Data at Rest on

Mobile Computing Devices and Removable Storage

Media

OPNAV Inst 2400.20F 19 Jul 2007 Electromagnetic Environmental Effects (E3) and

Spectrum Supportability Policy and Procedures

NAVAIRINST

13034.1E

30 Mar 2015 Flight Clearance Policy for Air Vehicles and

Aircraft Systems

NAVSEAINST

9310.1B

13 Jun 1991 Naval Lithium Battery Safety Program

NAVAIRINST

13280.1A

17 Aug 1989 Battery Standardization Program

3.0 Requirements

Unless otherwise specified, values set forth herein establish the requirements of satisfactory performance and apply to performance while installed on the host vehicle (including radome effects) under the conditions specified herein.

Unless otherwise specified, requirements set forth herein apply to the entire Radar System

(ground and airborne segments, external and internal components).

Unless otherwise specified, requirements are threshold requirements.

The Radar System shall provide all necessary operations during the following mission profiles:

1) Pre-Launch/Maintenance. The functions required to prepare the Air Vehicle for flight, including but not limited to:

a) Power up and BIT of the Radar System and associated peripherals.

b) Full system operations using the Weight on Skids (WOS) Bypass Switch as a safety interlock for full power transmit on the deck or in the hangar.

c) Initiated BIT

2) Launch/Post-Launch. The functions required to control and monitor the Radar System status after launch, during transit to the mission area, and during on-station loiter, search, and surveillance. The processes include but are not limited to:

a) Continuous BIT

b) Initiated BIT

c) Radar mode selection

d) Radar control

3) Egress/Descent/Landing. The functions required to control and monitor the Radar System during egress, return-to-base transit, descent and field or ship landing, including but not limited to:

a) Continuous BIT

b) Initiated BIT

3.1 Required States and Modes

3.1.1 Mission Modes

3.1.1.1 [T] The Radar System shall be capable of executing real-time mission commands as directed by the operator. This includes Radar System power on/off functions.

3.1.2 Payload States and Modes

3.1.2.1 [T] The Radar System shall meet its performance requirements within 5 minutes of being powered on.

3.2 System Capability Requirements

3.2.1 Built-in Test

3.2.1.1 [T] The Radar System, upon power application, shall perform a Power-up BIT

(PBIT).

3.2.1.1.1 [T] The PBIT shall detect and report to the Maintenance Portable Electronic

Display Device (MPEDD), Mission Payload Operator (MPO), and maintenance log file

Radar System failures/faults that would prevent the Radar System from meeting its mission requirements.

3.2.1.1.2 [T] PBIT shall isolate faults to the Weapon Replaceable Assembly (WRA) level.

3.2.1.1.3 [T] PBIT shall complete within 5 minutes of power application.

3.2.1.2 [T] The Radar System shall automatically execute a Continuous BIT (CBIT) while it is operational.

3.2.1.2.1 [T] The CBIT shall execute such that it does not degrade Radar System performance.

3.2.1.2.2 [T] The CBIT shall detect and report to the MPEDD, MPO, and maintenance log file Radar System failures/faults that would prevent the Radar System from meeting its mission requirements.

3.2.1.2.3 [T] The CBIT shall isolate faults to the WRA level.

3.2.1.3 [T] The Radar System shall perform an Initiated BIT (IBIT) upon operator command.

3.2.1.3.1 [T] The Radar System shall perform an IBIT upon command from the MPEDD.

3.2.1.3.2 [T] The IBIT shall detect and report to the MPEDD, crew, and maintenance log file Radar System faults that would prevent the Radar System from meeting its mission requirements.

3.2.1.3.3 [T] IBIT shall isolate faults to the WRA level.

3.2.1.3.4 [T] The IBIT shall complete within two minutes of its initiation.

3.2.1.4 [T] The Radar System’s BIT Fault Detection Rate shall be at least 0.80. BIT

Fault Detection Rate is defined as the total number of failures correctly detected by BIT divided by the number of actual failures. This rate only applies to the electronic WRAs with inherent BIT capabilities.

3.2.1.4.1 [T] The Radar System’s BIT Mean Flight hours between False Alarms shall be greater than or equal to 10 hours. This is a measure of how many fault detection false alarms occur during system operation. It is defined as the total operate hours divided by the total number of false alarms. False alarm in this context is a condition whereby the aircraft system or subsystem's BIT indicates a failure when none has occurred.

3.2.1.5 [T] The Radar System’s BIT Fault Isolation Rate to a WRA shall be at least 0.90 of the faults detected by BIT. This is defined as the total number of failures correctly isolated to the faulty WRA by BIT divided by the total number of failures detected by BIT.

This rate only applies to the electronic WRAs with inherent BIT capabilities

3.2.1.6 [T] All Radar System’s BIT shall be recorded in a BIT maintenance log for download by maintenance.

3.2.1.7 [T] BIT maintenance log format shall be Text File or delimited text strings and shall not require additional tools to view.

3.2.2 Field of Regard

3.2.2.1 [T] The Radar System shall have a forward looking surveillance field of regard

(FOR) of ±120 degrees in azimuth from the nose of the MQ-8C. [O] The Radar System shall have a surveillance FOR of 360 degrees in azimuth from the MQ-8C centerline.

3.2.2.2 [T] As installed, the Radar System shall have a surveillance FOR of -18 degrees to 0 degrees in elevation relative to the horizon (or as limited by airframe obstructions). [O] The Radar System shall have a surveillance FOR of -25 degrees to +15 degrees in elevation relative to the horizon (or as limited by airframe obstructions).

3.2.2.3 Unless otherwise specified, the Radar System shall meet full performance while operating within the following set of "standard flight/operating conditions”:

3.2.2.3.1 [T] The platform attitude is within ±15 degrees of roll, ±5 degrees of pitch, and

±5 degrees of yaw with respect to straight and level flight.

3.2.2.3.2 [T] The roll, pitch, and/or yaw rates are within ±5 degrees per second.

3.2.2.3.3 [T] The forward ground velocity of the platform is between 0 to 150 knots.

3.2.2.3.4 [T] The forward velocity is >50 knots ground speed during SAR imaging modes.

3.2.2.3.5 [T] Nominal 8,000 ft Above Ground Level (AGL).

3.2.2.4 [T] Full performance shall be achieved in regions of unobstructed FOR.

3.2.3 Surface Search

3.2.3.1 Surface Search Capability

3.2.3.1.1 [T] The Radar System shall provide a surface search capability.

3.2.3.1.2 [T] The Radar System shall maintain track on 500 surface targets within the

Radar System FOR. The Radar System shall provide operator selectability to coast (dead reckon) established tracks, which are no longer supported by radar detections. [O] The

Radar System shall automatically terminate dead reckon tracks after 2 minutes, with an operator initiated extension up to a maximum of 12 minutes. [O] The Radar System shall maintain track on 1,000 surface targets within the Radar System FOR.

3.2.3.1.3 [T] The Radar System shall filter radar tracks from targets that are on land, when operating in any of the maritime surveillance modes. The effects of shoreline objects in the surf are allowable.

3.2.3.1.4 [T] The land-sea boundary shall be determined either by an internally stored

World Vector Shoreline Database (or comparable database) and/or in an automated fashion based on radar return characteristics and shall be incorporated in signal processing and display.

3.2.3.1.4.1 [T] The Radar System shall be capable of being loaded with updated World

Vector Shoreline Database or comparable database.

3.2.3.1.5 [T] The Radar System shall maintain track updates as the Air Vehicle maneuvers and the contact is in the Radar System field of view range.

3.2.3.1.6 [T] The radar shall have a short-range search mode with a minimum range of 3 nmi and a maximum range of not less than 30 nmi.

3.2.3.1.7 [T] The radar shall have a long-range search mode with a minimum range of 25 nmi and maximum range of not less than 100 nmi.

3.2.3.1.8 Reserved.

3.2.3.1.9 [T] The radar shall have selectable scan sectors that include raster scans covering

180 deg., 90 deg, 45 deg, 30 deg., and 15 deg sectors for all search modes. [O] The radar shall have selectable scan sectors that include a full 360 deg continuous scan and raster scans covering 270 deg, 180 deg., 90 deg, 45 deg, 30 deg., and 15 deg sectors for all search modes.

3.2.3.1.10 Reserved.

3.2.3.1.11 [O] The radar shall have selectable scan rates of 6 deg/sec, 12 deg/sec, 24 deg/sec, 36 deg/sec, 48 deg/sec, and 72 deg/sec for all search modes.

3.2.3.1.12 [T] The radar will have a raster scan turn-a-round time less than or equal to 0.35 sec.

3.2.3.1.13 Reserved.

3.2.3.2 Short Range Detection

3.2.3.2.1 [T] The Radar System shall detect and track maritime surface contacts with a median RADAR Cross Section (RCS) of 10 square meters, from an MQ-8C altitude of

8,000 ft AGL and MQ-8C ground speed of 80 kts. Note: Allowable false alarm rate is 1 false alarm per hour with a minimum of 80% Probability of Detection (Pd) averaged over range and look direction at 8,000 ft AGL and 80 kts. [O] The Radar System shall detect and track maritime surface contacts with a median RCS of 4 square meters from an MQ-

8C altitude of 8,000 ft AGL and MQ-8C ground speed of 80 kts.

3.2.3.2.1.1 [T] The Radar System shall meet the detection requirements when the surface vessel is traveling at radial speeds of 0 to 50 kts inclusive. [O] The Radar System shall meet the detection requirements when the surface vessel is traveling at radial speeds of 0 to

70 kts inclusive.

3.2.3.2.1.2 [T] The false alarm rate shall be less than or equal to 1 per hour as displayed to the operator by an established target track.

3.2.3.2.1.3 [T] False alarm mitigation may occur over multiple scans but shall be completed within 45 seconds of the beginning of the first dwell.

3.2.3.2.1.4 [T] The performance shall be calculated as an average over upwind and crosswind directions in Douglas sea state 3 for this target and then averaged over all ground ranges from 5 nmi to 30 nmi within 60 degree sectors located ±90 degrees off the

MQ-8C nose. Note: Based on a Swerling II target without multipath or rain attenuation.

[O] The performance shall be calculated as an average over upwind and crosswind directions in Douglas sea state 3 for this target and then averaged over all ground ranges from 5 nmi to 30 nmi within 60 degree sectors located ± 180 degrees off the MQ-8C nose using a range resolution of 7.5 meters or greater.

3.2.3.2.1.5 [T] This performance shall be achieved with a revisit time less than or equal to 5 seconds over the entire 60 degree sector.

3.2.3.2.1.5.1 [T] The normalized sea clutter RCS and atmospheric attenuation models given in

Appendix B and C respectively shall be used in assessing this performance.

3.2.3.2.2 [T] The Radar System shall detect and track maritime surface contacts with a median RCS of 100 square meters at a ground range of 20 nm from an MQ-8C altitude of

8,000 ft AGL and MQ-8C ground speed of 80 kts in 4 mm/hr rain present over the entire propagation path when the surface vessel is traveling at speeds of 0 to 50 kts inclusive in

Douglas sea state 3. Note: Allowable false alarm rate is 1 false alarm per hour with a minimum of 80% Pd averaged upwind and crosswind look directions. [O] The Radar

System shall detect and track maritime surface contacts with a median RCS of 50 square meters at a ground range of 20 nm from an MQ-8C altitude of 8,000 ft AGL and MQ-8C ground speed of 80 kts in 4 mm/hr rain present over the entire propagation path when the surface vessel is traveling at speeds of 0 to 50 kts inclusive in Douglas sea state 3.

3.2.3.2.3 Periscope Detection. See Classified Annex A.

3.2.3.3 Long Range Detection

3.2.3.3.1 [T[ The Radar System shall detect and track maritime surface contacts with a median RCS of 1,000 square meters, from an MQ-8C altitude of 8,000 ft AGL and MQ-8C ground speed of 80 kts.

3.2.3.3.1.1 [T] The Radar System shall meet the detection requirements when the medium/large craft is traveling at radial speeds of 0 to 50 kts inclusive. [O] The Radar

System shall meet the detection requirements when the medium/large craft is traveling at radial speeds of 0 to 70 kts inclusive.

3.2.3.3.1.2 [T] The probability of detection shall be greater than or equal to 0.80 at the output of the tracker.

3.2.3.3.1.3 [T] The false alarm rate shall be less than or equal to 1 per hour as displayed to the operator by an established target track.

3.2.3.3.1.4 [T] False alarm mitigation may occur over multiple scans but shall be completed within 45 seconds of the beginning of the first dwell.

3.2.3.3.1.5 [T] The performance shall be calculated based on an average over upwind and crosswind directions in Douglas sea state 3 for this target and then averaged over all ground ranges from 50 nmi to 80 nmi over the search area within ±90 degrees off the MQ-

8C nose. Note: Based on a Swerling II target without multipath or rain attenuation. [O]

The performance shall be calculated as an average over upwind and crosswind directions in Douglas sea state 3 for this target and then averaged over all ground ranges from 50 nmi to 100 nmi over the search area within ±90 degrees off the MQ-8C nose.

3.2.3.3.1.5.1 [T] The normalized sea clutter RCS and atmospheric attenuation models given in

Appendix B and C respectively shall be used in assessing this performance.

3.2.4 ISAR Capability

3.2.4.1 [T] The ISAR waveform shall have a slant range resolution that is selectable from 1 meter, 2 meters, and 5 meters. [O] The ISAR waveform shall have a slant range resolution that is selectable from 0.3 meters, 1 meter, 2 meters, and 5 meters.

3.2.4.2 [T] The radar shall have selectable ISAR dwell durations from 5 sec to 90 sec in

5 sec increments.

3.2.4.3 [T] The radar shall be capable of accepting one ISAR command message per scan. The message shall contain the latitude, longitude, dwell time, and a unique identifier for every target to be ISAR’d in the next scan. The radar shall remain in its current search mode for as long as possible before switching to an ISAR mode. The mode transition between search and ISAR modes shall not exceed 450 msec. [O] The mode transition between search and ISAR modes shall not exceed 225 msec.

3.2.4.4 [T] The Radar System shall be capable of ISAR Mode operation over a ground range of 3 nmi to 60 nmi for targets having a median RCS of 300 square meters. [O] The

Radar System shall be capable of ISAR Mode operation over a ground range of 3 nmi to

100 nmi for targets having a median RCS of 300 square meters.

3.2.4.5 [T] The minimum spot-image size in ISAR Mode at the nominal 1.0 m resolution shall be not less than 150 m in range by 0.25 Hz to 1 Hz x 150 pixels in cross range as selected by the operator. [O] The minimum spot-image size in ISAR Mode at the nominal

0.3 m resolution shall be not less than 150 m in range by 0.25 Hz to 1 Hz x 150 pixels in cross range as selected by the operator.

3.2.4.6 [T] The Radar System shall have a range of integration times over at least a span from 1.0 second to 4.0 seconds at a frame rate of one scene per second. The radar shall have selectable ISAR dwell durations from 5 sec to 90 sec in 5 sec increments. [O] The

Radar System shall be capable of a range of integration times over at least a span from 0.5 seconds to 4.0 seconds at a frame rate of one scene per second.

3.2.4.7 [T] The Radar System ISAR modes shall provide, according to the current user-selection: 1) magnitude-only data, 2) ISAR data consisting of signed 12-bit pulse compressed In-Phase / Quadrature (I/Q) data in National Imagery Transmission Format

(NITF) 2.1 format, or 3) both.

3.2.4.7.1 [T] All ISAR image products shall use all applicable controlled support data extensions listed in STDI 0002, Compendium of Controlled Extensions for NITF.

3.2.4.7.2 [T] All complex data products shall also use the Complex Metadata (CMETA) extensions listed in STDI 0002.

3.2.4.8 [T] The Radar System shall provide the ability to perform ISAR length estimation.

3.2.5 Maritime Classification Aids

[O] The Radar System shall provide Maritime Classification Aids (MCA) including ISAR classification and decision aids that assist the operator to rapidly and accurately classify ships and small boats in the littoral.

3.2.5.1 [O] The classification and decision aids shall provide assisted image selection for operator viewing and further analysis by decision aids and automatic feature extraction.

3.2.5.2 [O] Critical features shall include target height, width and length estimation.

3.2.5.3 [O] Additional functionality shall include identification of point scatters and linear features that can be attributed to masts and decks as well as identification of rotating antennas.

3.2.5.4 [O] Semi-automated target classification shall be facilitated through the use of a stand-alone target database representative of combatants and non-combatants of the world along with general non-naval vessels. For 80% of ISAR dwells, the proper ship class shall be one of the top five options produced from the database (which maybe geographically tailored) given the following conditions: aspect angle from 0-45 or 135-180 degrees, the vessel is completely illuminated, sufficient Doppler Resolution (5 pixels for a mast), SCR>

20dB, heading information must be accurate to 2 degrees at 30-45 degree aspect, more than

5 good images in a dwell, and combatant or non-combatant length overall must be greater or equal to 60m. Vessels less than 60m shall be classified at least as a generic small ship class and non-naval vessels greater or equal to 60m shall be classified as a generic non-naval class. The MCA shall identify and reject ISAR images with multiple overlapping ships, clutter only images, images that contain only partial ships, bad acquisition of ships

(ships leave the range swath) and images dominated by clutter.

3.2.6 HRR Capability

3.2.6.1 [T] The radar system shall generate and provide at least 25 HRR signatures per scan. [O] The radar shall generate and provide 100 HRR signatures per scan.

3.2.6.2 [T] The radar system shall provide interleaving (without any change of antenna rotation rate) HRR waveforms, within all search modes, with a switching time not to exceed 10 msec.

3.2.6.3 [T] The radar system shall accept one HRR command message per scan that contains the number of HRR signatures to be performed in the next scan. The command messages shall contain the latitude, longitude, and a unique identifier for every target to be interrogated by the HRR waveform.

3.2.6.4 [T] The radar system shall incorporate a HRR waveform with a selectable slant ranges for each target. [O] The selectable slant range resolutions shall be 0.3M, 1M, 2M, and 5M.

3.2.6.5 [T] The radar system shall incorporate HRR signatures with a selectable number of range cells and a selectable number of consecutive Pulse Repitition Intervals (PRIs).

[O] The selectable number of range cells shall be 300, 600, 1200 and 1800, and a selectable number of consecutive PRIs shall be 8, 16, 32, 64.

3.2.6.6 [T] The radar shall center the HRR signature at the specified latitude/longitude within +/- 1 PRI and +/- 1M.

3.2.6.7 [T] The radar system shall provide a unique identifierspecified in the HRR command message with associated signatures.

3.2.6.8 [T] The radar system shall generate coherent PRIs during collection at the search mode Pulse Repitition Frequency.

3.2.6.9 [T] The HRR signatures shall consist of signed 12-bit pulse compressed I/Q data.

3.2.6.10 [T] The radar system shall incorporate a fixed R4 STC function to control dynamic range.

3.2.7 Payload Control

3.2.7.1 [T] The payloads shall be capable of being pointed to a target location, using any of the following methods:

3.2.7.1.1 [T] Entering target’s latitude, longitude, and elevation,

3.2.7.1.2 [T] Extracting latitude, longitude, and elevation from map display for commands to the radar payload.

3.2.7.2 [T] The payloads shall be capable of being pointed at a specified azimuth and elevation relative to the airframe’s axes.

3.2.7.3 [T] If the Air Vehicle detects loss of payload control via Tactical Common Data

Link (TCDL), the Radar System shall stop radiating.

3.2.7.3.1 [T] If communication is reestablished after a lost comms event, the Radar System shall remain in the non-emitting state until the operator commands it to do otherwise.

3.2.8 Radar System Cueing

3.2.8.1 External Sensor

3.2.8.1.1 [T] The Radar System shall be capable of being cued by a sensor external to the

Radar System. This may be achieved by providing lat/long data, pointing angles, etc. to the Radar System.

3.2.8.1.2 [T] The Radar System shall provide the data output necessary to cue other sensors external to the Radar System. This may be achieved by outputting lat/long and elevation data, pointing angles, etc. to the external system.

3.2.8.1.3 [T] When multiple payloads are installed, the MQ-8C Fire Scout System

(including TCS) shall determine which payloads are to be cued. [T] Once initiated, cueing between the two selected sensors shall be maintained by the airborne avionics, without further TCS input or processing.

3.2.8.1.4 [T] The Radar System maneuvering target tracking shall provide target course with an error of less than or equal to 15 degrees of true, for 95% of the attempts, under the following conditions: target range rate is greater than or equal to 3 kts; the single look SNR is greater than or equal to 17.5 dB; the track settling has required 8 or less updates; and the

Air Vehicle pitch rate, yaw rate, and roll rate all are less than or equal to 1 deg per sec during track settling time.

3.2.8.2 Radar Cueing the EO/IR Payload

3.2.8.2.1 The MQ-8C Fire Scout System shall automatically point the appropriate Electro-

Optic/Infrared (EO/IR) payload at a radar target designated by the MPO, where a “radar target” can be the following:

3.2.8.2.1.1 [T] A location on the radar display,

3.2.8.2.1.2 [T] A target currently being tracked by the Radar System.

3.2.8.2.2 [T] The MQ-8C Fire Scout System shall provide the capability to cue the EO/IR sensor to a target or track position identified by the radar subsystem. The EO/IR sensor cueing shall not require the Operator to input latitude, longitude, and altitude.

3.2.8.2.3 [T] The MQ-8C Fire Scout System shall utilize Radar System cueing data to enable the EO/IR Payload to cue to the radar contact to within the EO/IR sensor’s Medium

Field of View (MFOV) in [T] 65% [O] 90% of the cuing attempts at 5,000 ft AGL. Note:

Success is defined as any part of the target in EO/IR MFOV at handoff. Minimum 5 nmi range.

3.2.9 Motion Compensation

3.2.9.1 [T] If a motion-measuring unit is necessary, it shall be part of the Radar System.

3.2.9.2 [T] The Radar System shall accept navigation and motion measurement data from the Air Vehicle's Inertial Navigation System (INS) / Global Positioning System

(GPS) via the Payload Interface Unit.

3.2.10 Ground Control Station

3.2.10.1 Display and Control

3.2.10.1.1 [T] The radar control station shall receive and display radar information as well as controlling radar operation.

3.2.10.1.1.1 [T] The Radar System shall provide the operator the capability to command the following functions:

3.2.10.1.1.1.1 Radar mode control and parameter control including ISAR scheduling;

3.2.10.1.1.1.2 [T] Display of maritime vessel radar tracks and track database management, including the ability to selectively filter the display of tracks to remove undesired tracks by characteristic;

3.2.10.1.1.1.3 [T] Profiling of high-track-density areas to reduce system track volume and operator load;

3.2.10.1.1.1.4 [T] Radar imagery collection management, track manipulation and annotation;

3.2.10.1.1.1.5 [T] ISAR and SAR control and image display;

3.2.10.1.1.1.6 [T] Operator control of track persistence;

3.2.10.1.1.1.7 [T] Ability to link previously-dropped radar tracks to newly-initiated radar tracks;

3.2.10.1.1.1.8 [T] Operator ability to pan left or right, zoom in or out;

3.2.10.1.1.1.9 [T] Ability to hook tracks and display attributes;

3.2.10.1.1.1.10 [T] Ability to choose the map background to include World Vector Shoreline, CIB satellite imagery for SAR data, World Mercator Map, Digital Nautical Chart and

Operational Navigation Chart;

3.2.10.1.1.1.11 [T] Ability to choose what units will be displayed on the map for Latitude and

Longitude, Range and bearing, and Military Grid Reference System;

3.2.10.1.1.1.12 [T] Ability to orient the display to be either Center Anywhere “on track”, Center on Air Vehicle, or Center on Air Vehicle w/ Heading.

3.2.10.1.1.2 [T] The Radar System shall provide AIS track-to-radar track associations (as available).

3.2.10.1.1.3 [T] The Radar System shall provide automatic digital nautical chart data-to-radar track associations.

3.2.10.1.1.4 [T] The Radar System shall provide integrated operator displays and controls for real-time situational understanding.

3.2.10.1.1.5 [T] The Radar System shall provide automatic imagery-to-track associations and imagery exploitation tools.

3.2.10.1.1.5.1 [T] The Radar System shall display information necessary for operators to correctly identify the Air Vehicle under control.

3.2.10.1.1.5.2 [T] The Radar System shall co-locate related information and controls.

3.2.10.1.1.5.3 [T] The Radar System shall allow the operator to understand the state and function of a user interface control at any given time.

3.2.10.1.1.5.4 [T] All Radar System control actions shall provide consistent presentation of feedback with regard to initiated control actions, initiated but not completed control actions, and completed control actions.

3.2.10.1.1.5.5 [T] The Radar System shall have consistent labels, controls, alert message syntax, terminology, and user interface functionality across the entire system.

3.2.10.1.1.5.6 [T] Additional map functionality (e.g., displaying tracks, scan sector indication, etc.), due to the addition of the Radar System, shall be integrated into the existing

TCS map architecture.

3.2.10.1.1.6 [T] The MQ-8C Fire Scout Route and Payload Planner functions shall be expanded to allow the operators to pre-plan Radar employment on stationary targets and search areas.

3.2.10.1.1.7 [T] While operating via Secondary Datalink, the Radar System shall allow the operator to issue the following commands:

3.2.10.1.1.7.1 Power On/Off,

3.2.10.1.1.7.2 IBIT,

3.2.10.1.1.7.3 BIT Data Request,

3.2.10.1.1.7.4 Configuration Request,

3.2.10.1.1.7.5 Detailed Status Request.

3.2.10.1.1.8 [T] When the TCS detects that the Air Vehicle has a Radar payload installed, the mission planner shall inhibit mission plan upload that does not contain an action point on the C1 route for Radar in Standby.

3.2.10.1.1.9 [T] The TCS shall receive and display SAR Strip mode NITF 2.1 (in compliance with MIL-STD-2500C) data received via MQ-8C Fire Scout Air Vehicle data links.

3.2.10.1.1.10 [T] The TCS shall receive and display ISAR Strip mode NITF 2.1 (in compliance with MIL-STD-2500C) data received via MQ-8C Fire Scout Air Vehicle data links.

3.2.10.1.1.11 [T] The TCS shall provide for intelligent query, retrieval and display of SAR

Mission Data.

3.2.10.1.1.12 [T] The TCS shall provide for intelligent query, retrieval and display of ISAR

Mission Data.

3.2.10.1.1.13 [T] The TCS shall provide sensor collection planning for SAR Spot mode.

3.2.10.1.1.14 [T] The TCS shall provide sensor collection planning for ISAR Spot mode.

3.2.10.1.1.15 [T] The TCS shall provide sensor collection planning for SAR Strip mode.

3.2.10.1.1.16 [T] The TCSshall provide sensor collection planning for ISAR Strip mode.

3.2.10.1.1.17 [T] The TCS shall provide Air Vehicle navigation planning in support of SAR and ISAR Radar modes. [O] The TCS shall provide Air Vehicle navigation planning in support of the Ground Moving Target Indicator (GMTI) Radar mode.

3.2.10.1.1.18 [T] The TCS shall provide for re-planning of Radar collection plan during missions to support pop up target surveillance.

3.2.10.1.1.19 [T] Detected weather shall be displayed in color.

3.2.10.1.1.19.1 [T] Turbulence shall be displayed in magenta if greater than Level 1.

3.2.10.1.1.19.2 [T] Colors for weather targets shall be as specified in DO-173.

3.2.10.1.1.20 [O] The radar shall interface, via the TCDL, with an integrated Resource

Manager (RM) that can be configured pre-mission or during mission prosecution (i.e., modified) using configuration tools that are accessible within the primary radar operator interface. The RM shall have the ability to dynamically control the switching between all radar modes (e.g., search, HRR, ISAR, SAR operation with scan rate and waveform selectivity) in accordance with operator configured priorities and constraints. Each radar service request from the RM will have a unique identifier that will be sent with all data requests to facilitate retrieval and transmission of data over the link. Upon request, track reports in STANAG 4607 and Images in NITF / JPEG 2000 shall be provided.

3.2.10.1.1.21 [T] The Radar System shall coast (dead reckon) established tracks, which are no longer supported by radar detections for a minimum of 2 minutes, operator adjustable up to a maximum of 12 minutes before they are automatically terminated.

3.2.10.1.1.22 [T] Upon request, SAU 07000 messages 101, 103, 107, 110, 130, 131, 140, 141, 143, 160, 162, 191, and 192 shall be generated and sent by the Radar TCS software and

SAU 07000 messages 201,203, 207, 210, 230, 240 and 241 shall be received and processed by the Radar TCS software.

3.2.10.1.2 [T] The MQ-8C Fire Scout TCS shall be able to transmit and display both radar and EO/IR payload data simultaneously.

3.2.10.2 Real-time Payload Control

3.2.10.2.1 [T] Radar System operations that are common to other payload operations shall be implemented in a manner consistent with other existing payloads and/or operations.

3.2.10.3 Exporting and Storage of Data

3.2.10.3.1 [T] The Radar System processing shall include but not be limited to detection and tracking, image formation, resource management and maritime classification. Radar

System processing shall be performed aboard the MQ-8C and/or at the TCS.

3.2.10.3.1.1 [T] The Radar System messages transmitted over the MQ-8C Fire Scout High

Speed Data Link Interface shall comply with the requirements of STANAG 4586.

Additionally, the Radar System shall transmit, over the MQ-8C Fire Scout TCDL

Interface, track reports in compliance with STANAG 4607 and still imagery in NITF 2.1 format with SDEs per MIL-STD-2500C and STDI-0002.

3.2.10.3.2 [O] The airborne Radar Sub-System shall provide the capability to record radar imagery, maritime and GMTI detections and tracks for a 10-hour mission.

3.2.10.3.3 [T] Still imagery files generated by the MQ-8C Fire Scout system shall comply with the requirements stated in NATO STANAG 4545.

3.2.10.3.4 [T] The Radar System generated data files, which are downlinked to TCS, shall not exceed 2 Mbps.

3.2.10.3.5 [T] Track data contents for 1 track report shall consist of at least the following:

a. Track ID number, use count, status and type

b. Time in dead reckoning and dead reckoning indication

c. Track data convergence indication

d. Small Target Indicator

e. Track Latitude and Longitude

f. Data Time Tag

g. Discriminator Labels

h. Target numbers

i. Track Range Extent

j. Track length estimate

3.2.10.3.6 [O] Track data contents for 1 track report shall include the following:

a. Track Conflict indication.

b. Track covariance data

c. Maneuvering target indicator.

d. Identification Friend or Foe (IFF) Attributes

e. IFF Mode C Track Altitude

f. Interference Alert

g. Track length confidence.

3.2.10.4 TCS Hardware Modification

3.2.10.4.1 [T] In the event any new hardware is required to be installed at the TCS for the radar payload, it shall be compatible with existing interfaces for the baseline MQ-8C Fire

Scout .

3.2.10.5 TCS Software Modification

3.2.10.5.1 [T] The Radar System shall conform to the Modular Payload Architecture (MPA) software design, as described within C72-8000-012 Payload Inteface Unit Software

Requirements Specification for the VTUAV, to provide for the separation of Air Vehicle control and Radar Payload control in the MQ-8C Fire Scout Air Vehicle.

3.2.11 SAR Capability

3.2.11.1 Synthetic Aperture Radar

3.2.11.1.1 [T] The Radar System shall provide a SAR capability over a ground range extending to at least 30 nmi.

3.2.11.1.2 [T] The Radar System SAR modes shall provide, according to the current user-selection: 1) magnitude-only data, 2) 32-bit complex data in NITF 2.1 format, or 3) both.

3.2.11.1.3 [T] All SAR image products shall use all applicable controlled support data extensions listed in STDI‐0002, Compendium of Controlled Extensions for NITF.

3.2.11.1.4 [T] All complex data products shall also use the CMETA extensions listed in

STDI‐0002.

3.2.11.2 Spot Mode

3.2.11.2.1 [T] The Radar System shall provide a Spot capability.

3.2.11.2.2 [T] The Radar System shall provide a geo-location accuracy with Circular-Error

Probable (CEP50) of 25 m at any point within the image at a ground range of 5 nmi. [O]

The Radar System shall have a geo-location accuracy with Circular-Error Probable

(CEP50) of 5 m at any point within the image at a ground range of 5 nmi. This requirement

(both [T] and [O]) is to an absolute geo-location and is inclusive of INS/GPS, radome, airframe structural, and installation errors; and exclusive of terrain contributions. Digital

Terrain Elevation Data (DTED) Level 1 will be available for overland geo-location calculations.

3.2.11.2.3 [T] The resolution of each image produced in SAR Spot Mode shall be user-selectable from a discrete set of values including 1.0 and 2.0 m. [O] The resolution of each image produced in SAR Spot Mode shall be user-selectable from a discrete set of values at 0.15, 0.3, 1.0, 2, 4, and 8 m.

3.2.11.2.4 [T] The minimum spot-image size in SAR Spot Mode at 1 m resolution shall be no less than 150 m by 150 m for ranges beyond 3 nmi. [O] The minimum spot-image size in SAR Spot Mode at 0.3 m resolution shall be no less than 500 m by 500 m for ranges beyond 3.5 nmi.

3.2.11.2.5 [T] The Radar System shall provide a National Imagery Interpretability Rating

Scale 2 image rating at a stand-off distance of 23 km.

3.2.11.3 Strip Mode

3.2.11.3.1 [T] The Radar System shall provide a Strip capability.

3.2.11.3.2 [T] The Radar System shall have a geo-location accuracy with Circular-Error

Probable (CEP50) of 25 m at any point within the image at a ground range of 5 nmi. [O]

The Radar System shall have a geo-location accuracy with Circular-Error Probable

(CEP50) of 5 m at any point within the image at a ground range of 5 nmi. This requirement

(both [T] and [O]) is to an absolute geo-location and…