N00019-15-R-4000_Att_2_PBS_DRAFT_FBO_20150717.docx
DOCX document 419 KB Posted
- Attached to
- MQ-8C Maritime Search Radar
- Solicitation number
- N00019-15-PMA266-0029
About this file
Attachment 2 Performance Specification for RADAR OEM DRAFT RFP
View the file
Other files
Show all 33
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Doc. # PMA-266 RADAR 002 Revision: Initial Supersedes: - Date: 02 Dec 2013
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 D: Further dissemination only as directed by the Navy and Marine Corps Multi-Mission Tactical UAS Program Office (PMA-266).
“WARNING - This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., Sec 2751 et seq.) or Executive Order 12470. Violation of these export laws is subject to severe criminal penalties.”
“DESTRUCTION NOTICE For unclassified, limited documents, destroy by any method that will prevent disclosure of contents or reconstruction of the documents.”
CAGE CODE 03640
6953778G 01 August 1999
Date: 17 July 2015
Revisions
| Rev |
| Date |
Paragraph(s) Affected Change/Rationale
| Initial |
| 17 July 2015 |
| All |
| Initial Release |
PREPARATION AND APPROVAL SIGNATURES
| Approved : | Date: | |
| Title: | APEO (E) |
| Approved : | Date: | |
| Title: | APEO (L) |
| Approved : | Date: | |
| Title: | APEO (T&E) |
| Approved : | Date: | |
| Title: | Program Manager, PMA-266 |
Table of Contents
| 1.0 | Introduction | 1 |
| 1.1 | Scope | 1 |
| 1.2 | System Overview | 1 |
| 1.3 | Document Overview | 2 |
| 1.4 | Interpretation | 3 |
| 2.0 | Applicable Documents | 4 |
| 2.1 | Documents for Contract Technical Compliance | 4 |
| 2.2 | Specifications | 4 |
| 2.3 | Standards | 5 |
| 2.4 | Publications | 9 |
| 2.5 | Directives | 9 |
| 3.0 | Requirements | 12 |
| 3.1 | Required States and Modes | 12 |
| 3.2 | System Capability Requirements | 13 |
| 3.3 | System External Interface Requirements | 31 |
| 3.4 | System Internal Interface Requirements | 33 |
| 3.5 | Safety Requirements | 34 |
| 3.6 | System Security and Anti-Tamper Requirements | 34 |
| 3.7 | System Environment Requirements | 35 |
| 3.8 | System Quality Factors | 43 |
| 3.9 | Design and Construction Constraints | 44 |
| 3.10 | Logistics-related Requirements | 46 |
| 3.11 | Packaging Requirements | 46 |
| 3.12 | Environment, Safety, and Occupational Health | 47 |
| 3.13 | AIS | 50 |
| 4.0 | Verification | 52 |
| 4.1 | Scope | 52 |
| 4.2 | Verification Methods | 52 |
| 5.0 | Notes | 87 |
| 5.1 | Acronym List | 87 |
PMA-266 RADAR
Date: 17 July 2015
Introduction Scope This specification 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).
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.
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 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: Table 1-1 Mission Configurations provides the definition of payloads and configuration envisioned for the VTUAV system.
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 1 |
| 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 at the TCS;
· Radome to enclose MQ-8C externally mounted Radar System hardware while minimizing its effect on radar RF and aircraft performance;
· Self-test and status monitor built-in-test (BIT).
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.
Appendix E defines the ground clutter scattering model.
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.
Applicable Documents Documents for Contract Technical Compliance Unless otherwise specified, the following documents shall be used to determine technical compliance as specified in this specification. Documents referenced within those documents shall be used for guidance only. Documents apply only to the extent of the issues and revisions of these documents as specified herein 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.
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-2000-006 |
| 30 Nov 2012 |
| Modular Payload Architecture Integration Description Document (MPA IDD) for the Vertical Take-off and Landing Tactical Unmanned Aerial Vehicle System (VTUAV) |
| 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) |
| 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 |
W1006679 - Rev C (Contract No. N00019-98-C-0190)
| 16 Mar 2010 |
| Tactical Control System (TCS) - Block 2 Version 4 (B2V4) - Software Developer’s Kit (SDK) Plug-and-Play (PnP) Payload |
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 |
| 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 |
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-MQ8BA-NFM-000 |
| 15 Feb 2012 with Change 3 (15 Jul 2012) |
| NATOPS Flight Manual Navy Model MQ-8B Unmanned Aerial Vehicle |
| NTRP 3-22.4 MQ8BA |
| 15 Feb 2012 with Change 1 (01Apr 2012) |
| Naval Tactical Reference Publication |
Directives
| Document Number |
| Date of Issue |
| Description Title |
| 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.01 |
| 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.1D |
| 15 Mar 2010 |
| Flight Clearance Policy for Air Vehicles and Aircraft Systems |
NAVSEAINST 9310.1B
Naval Lithium Battery Safety Program
NAVAIRINST 13280.1A
Battery Standardization Program
Requirements [T] Unless otherwise specified, values set forth herein establish the requirements of satisfactory performance and shall 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 will 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/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 Required States and Modes Mission Modes [T] The Radar System shall be capable of executing real-time mission commands as directed real-time by the operator.
Payload States and Modes [T] The Radar System shall be capable of meeting its performance requirements within 5 minutes of turning it on.
System Capability Requirements Built-in Test (BIT) [T] The Radar System, upon power application, shall perform a Power-up BIT (PBIT).
[T] The PBIT shall detect and report to the PEMA, MPO, and maintenance log file Radar System failures/faults that would prevent the Radar System from meeting its mission requirements.
[T] PBIT shall isolate faults to the WRA level.
[T] PBIT shall complete within 5 minutes of power application.
[T] The Radar System shall automatically execute a Continuous BIT (CBIT) while it is operational.
[T] The CBIT shall execute such that it does not degrade Radar System performance.
[T] The CBIT shall detect and report to the PEMA, MPO, and maintenance log file Radar System failures/faults that would prevent the Radar System from meeting its mission requirements.
[T] The CBIT shall isolate faults to the WRA level.
[T] The Radar System shall perform an Initiated BIT (IBIT) upon command from the MPO.
[T] The Radar System shall perform an Initiated BIT (IBIT) upon command from the PEMA.
[T] The IBIT shall detect and report to the PEMA, MPO, and maintenance log file Radar System faults that would prevent the Radar System from meeting its mission requirements.
[T] IBIT shall isolate faults to the WRA level.
[T] The IBIT shall complete within two minutes of its initiation.
[T] The Radar System’s BIT Fault Detection Rate shall be at least 0.80.
[T] The Radar System’s BIT Mean Flight hours between False Alarms (MFHBFA) shall be greater than or equal to 500 hours.
[T] The Radar System’s BIT Fault Isolation Rate to an Organizational Removable Assembly (ORA) shall be at least 0.90 of the faults detected by BIT.
[T] All Radar system’s BIT shall be recorded in a BIT maintenance log for download by maintenance.
[T] BIT maintenance logs format shall be Text File or delimited text strings and shall not require additional tools.
Field of View [T] The Radar System shall be capable of a forward looking surveillance field of view (FOV) of ±120 degrees in azimuth from the nose of the MQ-8C. [O] The Radar System shall be capable of a surveillance field of view (FOV) of 360 degrees in azimuth from the MQ-8C centerline.
[T] As installed, the Radar System shall be capable of a surveillance field of view (FOV) of -18 degrees to 0 degrees in elevation relative to the horizon (or as limited in by the airframe obstructions). [O] The Radar System shall be capable of a surveillance field of view (FOV) of -25 degrees to +15 degrees in elevation relative to the horizon (or as limited by airframe obstructions).
[T] Unless otherwise specified, the Radar System shall meet full performance while operating within the following set of "standard flight/operating conditions”:
[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.
[T] The roll, pitch, and/or yaw rates are within ±5 degrees per second.
[T] The forward ground velocity of the platform is between 0 to 150 knots.
[T] The forward velocity is >50 knots ground speed during SAR imaging modes.
[T] Nominal 8,000 ft AGL.
[T] Full performance shall be achieved in regions of unobstructed FOV.
Surface Search Surface Search Capability [T] The Radar System shall provide a surface search capability.
[T] The Radar System shall be capable of maintaining track on 500 surface targets within the Radar System FOV. 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. [O] The Radar System shall be capable of maintaining track on 1,000 surface targets within the Radar System FOV.
[T] The Radar System shall have the capability to eliminate 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.
[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.
[T] The Radar System shall be capable of being loaded with updated World Vector Shoreline Database or comparable database.
[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.
[T] The radar shall have a short-range search mode with a minimum range of 3 nmi and a maximum range of 30 nmi.
[T] The radar shall have a long-range search mode with a minimum range of 25 nmi and maximum range of 100 nmi.
[T] The radar shall be capable of supporting selectable PRFs ranging from 500 Hz to 2500 Hz.
[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.
[T] 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.
[T] The radar will have a raster scan turn-a-round time less than or equal to 0.35 sec.
[T] The search waveform will be selectable with compressed pulse time IPRs (3 dB) of 60 nsec, 80 nsec, and 100 nsec, with range time sidelobes less than or equal to 25 dB down from the peak.
Short Range Detection [T] The Radar System shall be capable of detecting and tracking maritime surface contacts with a median 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% Pd averaged over range and look direction at 8,000 ft AGL and 80 kts. [O] The Radar System shall be capable of detecting and tracking 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.
[T] The Radar System shall be capable of meeting the detection requirements when the surface vessel is traveling at speeds between 0 to 50 kts inclusive. [O] The Radar System shall be capable of meeting the detection requirements when the surface vessel is traveling at speeds between 0 to 70 kts inclusive.
[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.
[T] False alarm mitigation may occur over multiple scans but must be completed within 45 seconds of the beginning of the first dwell.
[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 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.
[T] This performance shall be achieved with a revisit time less than or equal to 5 seconds over the entire 60 degree sector.
[T] The normalized sea clutter RCS and atmospheric attenuation models given in Appendix B and C respectively shall be used in assessing this performance.
[T] The Radar System shall be capable of detecting and tracking 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 between 0 to 50 kts inclusive in Douglas SS3 . 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 be capable of detecting and tracking 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 between 0 to 50 kts inclusive in Douglas SS3 .
[O] The Radar System shall be capable of detecting and tracking exposed submarine periscopes with a median RCS of x square meters from an MQ-8C altitude of 8,000 ft AGL and MQ-8C ground speed of 80 kts over a ground range extending from x nmi to y nmi. The allowable operator mitigated false alarm rate is x false alarms per hour with a minimum of x% Pd for an x second periscope exposure. The Radar System shall be capable of supporting a periscope detection coverage rate of x square nmi/hour.
Long RangDetection [T] The Radar System shall be capable of acquiring and tracking 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.
[T] The Radar System shall be capable of meeting the detection requirements when the medium/large craft is traveling at radial speeds between 0 to 50 kts inclusive. [O] The Radar System shall be capable of meeting the detection requirements when the medium/large craft is traveling at radial speeds between 0 to 70 kts inclusive.
[T] The effective single scan dwell probability of detection shall be greater than or equal to 0.80 at the output of the tracker.
[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.
[T] False alarm mitigation may occur over multiple scans but must be completed within 45 seconds of the beginning of the first dwell.
[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 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 100 nmi over the search area within ±90 degrees off the MQ-8C nose.
[T] The normalized sea clutter RCS and atmospheric attenuation models given in Appendix B and C respectively shall be used in assessing this performance.
ISAR Capability [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.
[T] The radar shall have selectable ISAR dwell durations from 5 sec to 90 sec in 5 sec increments.
[T] The radar will be capable of accepting one ISAR command message per scan. The message shall contain the latitude, longitude, dwell time, and a unique identifier (UUID) for every target to be ISARed 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 from search to and from ISAR mode shall not exceed 450 msec. [O] The radar shall remain in its current search mode for as long as possible before switching to an ISAR mode. The mode transition from search to and from ISAR mode shall not exceed 225 msec.
[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.
[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.
[T] The Radar System shall be capable of 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. The radar will be capable of accepting one ISAR command message per scan. The message shall contain the latitude, longitude, dwell time, and a unique identifier (UUID) for every target to be ISARed in the next scan. [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.
[T] The Radar System ISAR modes shall have the capability to provide magnitude-only data.
[T] The Radar System ISAR modes shall have the capability to provide, according to the current user-selection, 1) magnitude-only data, 2) The ISAR data shall consist of signed 12-bit pulse compressed I/Q data in National Imagery Transmission Format (NITF) 2.1 format, or 3) both.
[T] All ISAR image products shall use all applicable controlled support data extensions listed in STDI 0002, Compendium of Controlled Extensions for NITF.
[T] All complex data products shall also use the Complex Metadata (CMETA) extensions listed in STDI 0002.
[T] The Radar System shall provide the ability to perform ISAR length estimation.
[O] The Radar System shall be capable of providing Maritime Classification Aids (MCA) including ISAR classification and decision aids tools that assist the operator to rapidly and accurately classifying ships and small boats in the littoral.
[O] The classification and decision aids shall provide assisted image selection for operator viewing and further analysis by decision aids and automatic feature extraction.
[O] Critical features shall include target height, width and length estimation.
[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.
[O] Semi-automated target classification shall be facilitated through the use of a stand-alone target database representative of combatants, non-combatants of the world along with general non-naval vessels. For 80% of ISAR dwells the MCA shall identify the proper ship class is ranked as 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 be able to 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.
[O] The operator shall be able to identify targets of particular interest to the classification and decision aids.
HRR Capability [T] The radar shall be capable of generating 25 HRR signatures per scan, [O] The radar shall be capable of generating 100 HRR signatures per scan.
[T] The radar shall be capable of interleaving (without any change of antenna rotation rate) HRR waveforms within all search modes with a switching time not exceed 10 msec.
[T] The radar shall be capable of accepting one HRR command message per scan that contains the number of HRR signatures to be performed in the next scan. The command messages shall be capable of containing the latitude, longitude, and a unique identifier for every target to be interrogated by the HRR waveform.
[T] The radar shall be capable of incorporating a HRR waveform with a selectable slant range for each target with resolutions of 0.3M, 1M, 2M, and 5M.
[T] The radar shall be capable of incorporating HRR’s with a selectable number of range cells (300, 600, 1200 and 1800) and a selectable number of consecutive PRIs (8, 16, 32, 64).
[T] The radar shall be capable of centering the HRR signature at the specified latitude/longitude within +/- 1 PRI and +/- 1M.
[T] The radar shall be capable of including unique identifiers (UUID) specified in the HRR command message with associated signatures.
[T] The radar shall be capable of generating coherent PRIs during collection at the search mode PRF.
[T] The HRR signatures shall consist of signed 12-bit pulse compressed I/Q data.
[T] The radar shall capable of incorporating a fixed R4 STC function to control dynamic range.
Payload Control [T] The payloads shall be capable of being pointed to a target location, using any of the following methods:
[T] Entering target’s latitude, longitude, and elevation.
[T] The payloads operator shall be able to extract latitude, longitude, and elevation from map display for commands to the radar payload.
[T] The payloads shall be capable of being pointed at a specified azimuth and elevation relative to the airframe’s axes.
[T] If the air vehicle detects loss of payload control via TCDL, the Radar System shall stop radiating.
[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.
Radar System Cueing External Sensor [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.
[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.
[T] The Radar System cueing data shall allow the EO/IR Payload to cue to the radar target such that the radar target is within the EO/IR sensor’s Medium Field of View (MFOV) [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.
1.1.1.1.1 [T] When multiple payloads are installed, the VTUAV System (including TCS) shall determine which payloads may be cued. [T] Once initiated, cueing between the two selected sensors shall be maintained by the airborne avionics, without further TCS input or processing [T] The Radar System tracking shall provide target heading with an error of less than or equal to 15 degrees of true 95% under the following conditions: Target range rate is greater than or equal to 3 kts, target length over all greater than or equal to 40 meters, the single look SNR is greater than or equal to 17.5 dB, the track settling has required 8 or less updates, and the AV pitch rate yaw rate roll rate all are less than or equal to 1 deg per sec during track settling time.
Radar Cueing the EO/IR Payload [T] The VTUAV System shall automatically point the appropriate EO/IR payload (see 3.2.7 Radar System Cueing) at a radar target designated by the MPO, where a “radar target” can be the following:
[T] A location on the radar display, [T] A target currently being tracked by the Radar System.
[T] The VTUAV 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.
Motion Compensation
1.1.1.2 [T] If a motion-measuring unit is necessary, it shall be part of the Radar System.
[T] The Radar System shall be capable of accepting navigation and motion measurement data from the air vehicle's INS/GPS via the PIU.
Ground Control Station Display and Control [T] The radar control station shall be capable of receiving and displaying radar information as well as controlling radar operation.
[T] The Radar System shall provide the operator the capability to command the following functions:
Radar mode control and parameter control including ISAR scheduling, Display of maritime vessels radar tracks; track database management including the ability to selectively filter the display of tracks to remove undesired tracks by characteristic.
Profiling of high-track-density areas to reduce system track volume and operator load, Radar imagery collection management, track manipulation and annotation, Inverse Synthetic Aperture Radar (ISAR) and Synthetic Aperture Radar (SAR) control and image display, Operator control of track persistence, Ability to link previously-dropped radar tracks to newly-initiated radar tracks, Operator ability to pan left or right, zoom in or out, Ability to hook tracks and display attributes, Ability to choose the map background to include World Vector Shoreline (WVS), World Mercator Map (WMM), Digital Nautical Chart (DNC) and Operational Navigation Chart (ONC), Ability to choose what units will be displayed on the map for Latitude and Longitude, Range and bearing and Military Grid Reference System, Ability to orient the display to be either Center Anywhere, Center on Air Vehicle, or Center on Air Vehicle w/Heading.
The Radar System shall provide automatic AIS track-to-radar track associations (as available).
The Radar System shall provide automatic digital nautical chart data-to-radar track associations.
The Radar System shall provide integrated operator displays and controls for real-time situational understanding.
The Radar System shall provide automatic imagery-to-track associations and imagery exploitation tools.
1.1.1.2.1.1.1 [T] The radar shall display information necessary for operators to correctly identify the air vehicle under control.
1.1.1.2.1.1.2 [T] The radar shall co-locate related information and controls.
1.1.1.2.1.1.3 [T] The radar shall be designed to allow the operator to understand the state and function of a user interface control at any given time.
1.1.1.2.1.1.4 [T] The radar shall be designed such that all control actions provide consistent presentation of feedback with regard to initiated control actions, initiated but not completed control actions, and completed control actions.
1.1.1.2.1.1.5 [T] The radar shall be designed to have consistent labels, controls, alert message syntax, terminology, and user interface functionality across the entire system.
1.1.1.2.1.1.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.
1.1.1.2.1.2 [T] The current VTUAV Route and Payload Planner (RPP) function shall be expanded to allow the operators to pre-plan Radar employment on stationary targets and search areas.
1.1.1.2.1.3 [T] While operating via Secondary Datalink (SDL), the operator shall be able to issue the following commands:
1.1.1.2.1.3.1 Power On/Off,
1.1.1.2.1.3.2 IBIT,
1.1.1.2.1.3.3 BIT Data Request.
1.1.1.2.1.4 [T] When the TCS detects that the AV 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 Power Off.
1.1.1.2.1.5 [T] The TCS shall receive and display SAR Strip mode NITF 2.1 (in compliance with MIL-STD-2500C) data received via VTUAV AV data links.
1.1.1.2.1.6 [T] The TCS shall receive and display ISAR Strip mode NITF 2.1 (in compliance with MIL-STD-2500C) data received via VTUAV AV data links.
1.1.1.2.1.7 [T] The TCS shall provide capability for intelligent query, retrieval and display of SAR Mission Data.
1.1.1.2.1.8 [T] The TCS shall provide capability for intelligent query, retrieval and display of ISAR Mission Data.
1.1.1.2.1.9 [T] The TCS shall provide sensor collection planning for SAR Spot mode.
1.1.1.2.1.10 [T] The TCS shall provide sensor collection planning for ISAR Spot mode.
1.1.1.2.1.11 [T] The TCS shall provide sensor collection planning for SAR Strip mode.
1.1.1.2.1.12 [T] The TCS shall provide sensor collection planning for ISAR Strip mode.
1.1.1.2.1.13 [T] The TCS shall provide AV navigation planning in support of SAR, ISAR, GMTI, MMTI Radar modes.
1.1.1.2.1.14 [T] The TCS shall provide capability for re-planning of Radar collection plan during mission to support pop up target surveillance.
1.1.1.2.1.15 [T] Detected weather shall be displayed in color.
1.1.1.2.1.15.1 [T] Turbulence shall be displayed in magenta if greater than Level 1.
1.1.1.2.1.15.2 [T] Colors for weather targets shall be as specified in DO-173.
[O] The radar shall be capable of interfacing with an integrated Resource Manager (RM) via the TCDL 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 (RSR) from the RM will have a unique identifier (UUID) 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. Upon request, SAU 07000 messages - 143, 160, 162, 191, and 192 shall be provided.
[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.
1.1.1.2.1.16 [O] 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.
1.1.1.2.2 [T] The VTUAV TCS shall be able to transmit and display both radar and EO/IR payload data simultaneously.
Real-time Payload Control [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.
Exporting and Storage of Data [T] Radar System processing to include but not limited to detection and tracking, image formation, resource management and maritime classification shall be capable of being performed aboard the MQ-8C or at the TCS. The system shall be capable of performing Radar System processing to include but not limited to detection and tracking, image formation, resource management and maritime classification. Implementation methods of Radar System messages transmitted over the VTUAV High Speed Data Link Interface for the RDC shall not prohibit future compliance to STANAG 4586 messages. Additionally, the Radar System shall transmit, over the VTUAV High Speed Data Link 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.
[T] The Radar System messages transmitted over the VTUAV High Speed Data Link Interface shall comply with the requirements of STANAG 4586.
[O] In addition, the airborne RSS may also provide the capability to record radar imagery, maritime and GMTI detections and tracks for a 10-hour mission.
[T] Still imagery files generated by the VTUAV system shall comply with the requirements stated in NATO STANAG 4545.
TCS Hardware Modification [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 VTUAV.
TCS Software Modification [T] The Radar System shall conform to the Modular Payload Architecture (MPA) software design to provide for the separation of air vehicle control and Radar Payload control in the VTUAV Air Vehicle.
SAR Capability Synthetic Aperture Radar [T] The Radar System shall provide a SAR capability over a ground range extending to at least 30 nmi.
[T] The Radar System SAR modes shall have the capability to provide magnitude-only data.
[T] The Radar System SAR modes shall have the capability to provide, according to the current user-selection, 1) magnitude-only data, 2) 32-bit complex data in NITF 2.1 format, or 3) both.
[T] All SAR image products shall use all applicable controlled-support data-extensions listed in STDI‐0002, Compendium of Controlled Extensions for National Imagery Transmission Format (NITF).
[T] All complex-data products shall also use the Complex Metadata (CMETA) extensions listed in STDI‐0002.
Spot Mode [T] The Radar System shall provide a Spotlight capability.
[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. (RDC PM) [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.
[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.
[T] The minimum spot-image size in SAR Spot Mode at 1 m resolution shall be no less than 150 m x 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 be capable of providing a National Imagery Interpretability Rating Scale (NIIRS) 2 image rating at a stand-off distance of 23 km.
Strip Mode [T] The Radar System shall provide a Strip capability.
[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 is to an absolute geo-location and is inclusive of INS/GPS, radome, airframe structural, and installation errors; and exclusive of terrain contributions.
[T] The resolution of each image produced in SAR Strip Mode shall be user-selectable from a discrete set of values including 1, 2, and 4 m. [O] The resolution of each image produced in SAR Strip Mode shall be user-selectable from a discrete set of values including 0.3, 1, 2, and 4 m.
[T] The Radar System range swath shall be at least 1 km wide at 2 m resolution.
1.1.2 Ground Moving Target Indicator (GMTI) [O]
1.1.2.1 [T] The Radar System shall support the detection and targeting of high value, time-sensitive, fixed and re-locatable targets.
1.1.2.2 [T] The Radar System shall be capable of detecting moving land vehicles of 5 square meter or greater RCS moving at a minimum of 3 knots utilizing a wide area, sector and staring GMTI modes with an 80% probability of detection.
1.1.2.2.1 [T] In the wide area mode coverage with a 20 second revisit rate shall be achieved over ±90 degrees in azimuth from air vehicle’s longitudinal axis and from 5 to 15 nmi when the air vehicle is operating at 8,000 ft AGL and 65 knots ground speed. In this mode the target location accuracy for a 5 square meter RCS vehicle moving at 4 knot velocity is x.x degrees.
1.1.2.2.2 [O] The sector mode shall be capable of detecting moving land vehicles of 5 square meter or greater RCS moving at a minimum of 2 knots and a dismount (1 square meter RCS) moving at minimum 3 knots utilizing an average 5 second revisit rate and be achieved over ±15 degrees in azimuth from air vehicle’s longitudinal axis and from 5 to 15 nmi when the air vehicle is operating at 3,000 ft AGL and 65 knots ground speed. In this mode the target location accuracy for a 5 square meter RCS vehicle moving at 2 knot velocity is x.x degrees for a 90 degree look angle. In this mode the target location accuracy for a 1.0 square meter RCS dismount moving at 3 knot velocity is x.x degrees for a 90 degree look angle.
1.1.2.2.3 [O] In the staring mode the radar shall provide coverage over a 2 km by 2 km region when operating from an altitude of 3,000 ft and 65 knot ground speed.
1.1.2.2.4 [O] The staring mode shall be capable of detecting moving land vehicles of 5 square meter or greater RCS moving at a minimum of 0.7 knots and a dismount (1 square meter RCS) moving at minimum 1 knots. In this mode the target location accuracy for a 5 square meter RCS vehicle moving at 1.5 knot velocity is x.x degrees for a 90 degree look angle.
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .