Attachment 0003 - CUAS Mid Range Sensing Requirements Dev OPSEC.xlsx

XLSX spreadsheet 24 KB Posted

Attached to
Ground Vehicle System Center (GVSC) Commercial Solutions Opening (CSO)
Solicitation number
W912CH-24-S-0002
Issued by

About this file

This file is a requirements development document for Counter-Unmanned Aircraft System (CUAS) mid-range sensing capabilities, prepared with operational security (OPSEC) considerations for the Ground Vehicle Systems Center (GVSC) Commercial Solutions Opening solicitation W912CH-24-S-0002.

The spreadsheet outlines technical requirements and specifications for mid-range sensing systems intended to support CUAS integration on ground vehicles. The document addresses sensor performance parameters, detection ranges, target classification capabilities, and integration standards necessary for identifying and tracking unmanned aircraft threats at operational distances. The requirements are structured to support GVSC's modernization priorities in autonomous systems and advanced ground vehicle capabilities. As part of the broader CSO managed by the Department of the Army Materiel Command TACOM Life Cycle Management Command, this requirements document establishes the technical baseline for commercial solutions proposals that may be awarded through FAR Part 12 contracts, 10 U.S.C. 4022 transaction agreements, or Cooperative Agreements under 31 U.S.C. 6305. The document reflects Army priorities for accelerating delivery of ground system capabilities through commercial innovation and demonstrates the specific technical focus areas that respondents should address in their proposals to support Army modernization and warfighter readiness objectives.

View the file

Other files

File Type Posted
W912CH-24-S-0002 Amendment 27.docx DOCX document
W912CH-24-S-0002 Amendment 26.docx DOCX document
W912CH-24-S-0002 Amendment 25.docx DOCX document
W912CH-24-S-0002 Amendment 24.docx DOCX document
Area of Interest - Unified Combat Teaming.docx DOCX document
W912CH-24-S-0002 Amendment 23.docx DOCX document
W912CH-24-S-0002 Amendment 22.docx DOCX document
W912CH-24-S-0002 Amendment 21.docx DOCX document
W912CH-24-S-0002 Amendment 20 OPSEC10806.docx DOCX document
W912CH-24-S-0002 Amendment 19 OPSEC10703.docx DOCX document
W912CH-24-S-0002 Amendment 18 OPSEC10645.docx DOCX document
W912CH-24-S-0002 Amendment 17 OPSEC10576.docx DOCX document
W912CH-24-S-0002 Amendment 16 OPSEC10498.docx DOCX document
W912CH-24-S-0002 Amendment 15 OPSEC10431.docx DOCX document
W912CH-24-S-0002 Amendment 14 OPSEC10404.docx DOCX document
W912CH-24-S-0002 Amendment 13 OPSEC10322.docx DOCX document
W912CH-24-S-0002 Amendment 12 OPSEC10281.docx DOCX document
GVSC CSO W912CH-24-S-0002 AMD 11.docx DOCX document
GVSC CSO W912CH-24-S-0002 AMD 10.docx DOCX document
GVSC CSO W912CH-24-S-0002 AMD09.pdf PDF
GVSC CSO W912CH-24-S-0002 AMD 08.docx DOCX document
Attachment 0001 GEN2 VBK DATA SHEET 2 OPSEC.pdf PDF
Attachement 0002 GEN3 VBK DATA SHEET 2 OPSEC.pdf PDF
GVSC CSO W912CH-24-S-0002 AMD 07.docx DOCX document
GVSC CSO W912CH-24-S-0002 AMD 06.docx DOCX document
GVSC CSO AMD 05.docx DOCX document
GVSC CSO AMD 04 FG 07102025.pdf PDF
GVSC CSO AMD 03 KS 05122025.pdf PDF
GVSC CSO AMD 02 KS 04302025.pdf PDF
GVSC CSO - REV 01 - FINAL.docx DOCX document
CSO AOI AMD 01 Final.docx DOCX document
GVSC CSO - W912CH-24-S-0002.pdf PDF
Show all 32

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

CSO Rqts 2026_0513

CUAS Sensor Requirements Definition
Req IDDescriptionTextType-Formal SpecType - For July EventStatusRationale
Threat SensingCUAS-Sense-001Definition - Primary Relevant EnvironmentThe CUAS sensor should operate with full performance in the un-obscurred battlefield environment in all lighting (Day/Night) conditions.
Note: In all environments during test, the sensor will have Line of Sight to the threat.InformationInformationApprovedIt is desired to baseline the performance of each sensor in an unobscured environment. Gathering this information will provide insight into the best case performance of the technology under test.
CUAS-Sense-003Definition - Relevant ThreatThe CUAS Sensor must detect and recognize all threats defined as Group 1 and Group 2 UAS as per document {TBD} with a critical dimension no smaller than 0.165 m . For purposes of this document, this threat set will be referred to as the relevant threat.InformationInformationReviewThe minimum size was chosen to accomodate UAS threats with a side profile of 9 inches x 5 inches (resulting in a critical dimension of 0.165 m).
CUAS-Sense-005Defintion - RecognitionFor purposes of this document, the term recognition is defined as the ability of the sensor under test to classify and declare an object within the scene as a UAS.InformationInformationApprovedThe definition herein references the common understanding from the Johnson criteria DRI model. Recognition capability demonstrates the sensor subsystem's ability to bin a detected object as a UAS.
CUAS-Sense-006Object Recognition - Primary Relevant EnvironmentThe CUAS Sensor shall recognize relevant threats at a minimum range of {XX} m while operating within the Primary Relevant Environment.ThresholdTechnical Performance AssessmentApprovedRecognition range included in classified annex.

Note: This will be an assessed parameter during the test event. The threshold requirement is not a barrier to entry for the July event, but rather a target for industry to understand the PdM VPS office objective.

CUAS-Sense-007Object Recognition - Primary Relevant EnvironmentThe CUAS Sensor shall recognize relevant threats at a minimum range of {XX} m while operating within the Primary Relevant Environment.ObjectiveObjectiveApprovedObjective recognition range included in classified annex.
Threat TrackingCUAS-Sense-009Threat Recognition- False Alarm RateThe CUAS Sensor false recognition rate shall be no greater than an average of {XX} per hour in a continuous 48 hour period in a relevant environment.ThresholdTechnical Performance AssessmentApprovedFalse alarm number included in classified annex.
CUAS-Sense-010Definition - Threat Recognition ProbabilityThe Prec will be calculated for each independent threat classification category based on:
Prec = N/T where N is the number of threats correctly recognized and T is the number of total threats presented to the sensor in the given test scenario.InformationInformationApproved
CUAS-Sense-011Threat Recognition- Probability of RecognitionThe CUAS Sensor shall meet a minimum Prec of {XX.XX}%.ThresholdTechnical Performance AssessmentApprovedThreat recognition probability included in classified annex.
CUAS-Sense-012Threat Recognize and Track - Simultaneous ThreatThe CUAS sensor shall recognize and track up to {XX} simultaneously occuring threats.ThresholdTechnical Performance AssessmentApproveThreshold number of simultaneously tracked threats included in classified annex.
CUAS-Sense-013Threat Recognize and Track - Simultaneous ThreatThe CUAS sensor shall recognize and track up to {XX} simultaneously occuring threats.ObjectiveObjectiveApproveObjective number of simultaneously tracked threats included in classified annex.
CUAS-Sense-014Threat Recognize and Track - Angular SeparationThe CUAS sensor shall recognize and track threats that are separated by greater or equal to {XX} degrees. See CUAS Sensor Classified Appendix.ThresholdTechnical Performance AssessmentApproveThreat angular separation number incluced in classified annex.
CUAS-Sense-015Threat Tracking - Update RateThe CUAS sensor shall, while an identified threat remains in its field of view, update the location of the threat at a rate of not less than 15 Hz.ThresholdThresholdApprovedIt is critical that the requested sensor technology be capable of updating threat parameters at a frequency suitable for bringing fine tracking sensors on target.
On the MoveCUAS-Sense-017On the Move - Average Speed Paved RoadThe CUAS sensor shall meet all threat recognition requirements while operating at a speed of 48 KPH / 30 MPH on paved road.ThresholdTechnical Performance AssessmentApprovedSpeed profile numbers leveraged from MRAP OMS/MP.
CUAS-Sense-018On the Move - High Speed Paved RoadThe CUAS sensor shall meet all threat recognition requirements while operating at a speed of 112 KPH / 70 MPH on paved road.ObjectiveObjectiveApprovedSpeed profile numbers leveraged from MRAP OMS/MP.
CUAS-Sense-019On the Move - TrailsThe CUAS sensor shall meet all threat recognition requirements while performing evasive maneuvers at a speed of 30 KPH / 19 MPH on an unpaved desert road.ThresholdTechnical Performance AssessmentApprovedSpeed profile numbers leveraged from MRAP OMS/MP.
CUAS-Sense-020On the Move - Cross CountryThe CUAS sensor shall meet all threat recognition requirements while performing evasive maneuvers at a speed of 8 KPH / 5 MPH on a cross country course.ObjectiveObjectiveApprovedSpeed profile numbers leveraged from MRAP OMS/MP.
Sensor OutputCUAS-Sense-021Sensor Output - Bearing AccuracyThe CUAS Sensor shall provide the angular bearing to a detected UAS threat with a maximum allowable error of {XX} degrees.ThresholdTechnical Performance AssessmentApprovedBearing accuracy number included in the classified annex.
CUAS-Sense-022Sensor Output - RangeThe CUAS Sensor shall provide a range to a detected threat.ObjectiveObjectiveApproved
CUAS-Sense-023Sensor Output - Range AccuracyThe CUAS sensor shall determine the range to threat with an accurracy of +/- {XX} meters.ObjectiveObjectiveApprovedRange accuracy specification included in the classified annex.
Threat VarietyCUAS-Sense-024Definition - Threat VarietyThe CUAS sensor is required to detect all UAS devices classified in the US Army Group 1 and Group 2 categories. The following requirements seek to clarify that the sensor must detect these UAS threats regardless of the control mechanism that they employ.InformationInformationApproved
CUAS-Sense-025Threat Variety - RF Control LinkThe CUAS sensor shall detect relevant threats operating via Radio Frequency control link from a base station.ThresholdThresholdApprovedThe candidate solution must be capable of detecting group 1 and group 2 threats if they are controlled via radio link.
CUAS-Sense-026Threat Variety - Autonomous OperationThe CUAS sensor shall detect autonomously operating UAS relevant threats.ThresholdThresholdApprovedThe candidate solution must be capable of detecting group 1 and group 2 threats if they are waypoint guided/operating autonomously.
CUAS-Sense-027Threat Variety - Fiber Optic Control LinkThe CUAS Sensor shall detect relevant threats that employ Fiber Optic control links.ThresholdThresholdApprovedThe candidate solution must be capable of detection group 1 and group 2 threats if they are controlled via fiber optic control link.
CUAS-Sense-028Threat Variety - ATGMThe CUAS Sensor shall detect Anti-Tank Guided Missile (ATGM) threats in the primary relevant environment.ObjectiveObjectiveApprovedThe candidate solution can, ideally, provide some level of detection of ATGM threats.
CUAS-Sense-029Threat Variety - Recoiless RifleThe CUAS Sensor shall detect Recoiless Rifle threats in the primary relevant environment.ObjectiveObjectiveApprovedThe candidate solution can, ideally, provide some level of detection of recoilless rifle threats.
CUAS-Sense-030Threat Variety - RPGThe CUAS Sensor shall detect Rocket-Propelled Grenade (RPG) threats in the primary relevant environment.ObjectiveObjectiveApprovedThe candidate solution can, ideally, provide some level of detection of RPG threats.
CUAS-Sense-031Threat Variety - Tank FiredThe CUAS Sensor shall detect Tank Fired threats in the primary relevant environment.ObjectiveObjectiveApprovedThe candidate solution can, ideally, provide some indication of Tank Fired kinetic energy threats.
External InterfaceCUAS-Sense-032Hardware Req - External InterfaceThe CUAS Sensor shall integrate a Gigabit Ethernet Data Link compliant with IEEE 802.3{TBD}.ThresholdThresholdApprovedThreats are communicated external to the candidate solution via a UDP or TCP/IP Ethernet link.
CUAS-Sense-033Hardware Req - External InterfaceThe CUAS Sensor shall integrate a deterministic Gigabit Ethernet Data Link compliant with IEEE 802.1 AVB/TSN.ObjectiveObjectiveApproved
CUAS-Sense-034Threat Reporting - External Interface - DefinitionThreat report information, to the extent possible by the sensing modality, should include azimuth bearing to threat, elevation bearing to threat, range to threat, velocity of threat, acceleration of threat, size of threat.InformationInformationApproved
CUAS-Sense-035Threat Reporting - External InterfaceThe CUAS Sensor shall report threat data via the Gigabit Ethernet Data Link.ThresholdThresholdApproved
CUAS-Sense-036Input PowerThe sensor shall exhibit full performance within the electrical power contstraints defined in MIL-STD-1275{E}.ThresholdThresholdApprovedFor purposes of the initial sensor demonstration event in July, compliance to the rev. E version of the MIL-STD-1275 specification will be evaluated but not required for participation.
EnvironmentalCUAS-Sense-039Environmental - High Operating TemperatureThe CUAS Sensor, if not exposed to power pack temperatures

and not mounted above the recoil portion of a weapon, shall meet its full performance requirements without performance or physical degradation during its worst case thermal operating cycle at ambient air temperatures of

49 °C (120 °F).ThresholdObjectiveApprovedFor purposes of the initial sensor demonstration event in July, compliance to this requirement will be evaluated but not required for participation.
CUAS-Sense-040Environmental - High Operating TemperatureThe CUAS Sensor, if not exposed to power pack temperatures

and not mounted above the recoil portion of a weapon, shall meet its full performance requirements without performance or physical degradation during its worst case thermal operating cycle at ambient air temperatures of

71 °C (160 °F).ObjectiveObjectiveApprovedFor purposes of the initial sensor demonstration event in July, compliance to this requirement will be evaluated but not required for participation.
CUAS-Sense-041Environmental - Low Operating TemperatureThe System shall meet its full performance requirements

without performance or physical degradation during continuous operation immediately after power up at an

ambient temperature of ‐40 degrees C.ThresholdObjectiveApprovedFor purposes of the initial sensor demonstration event in July, compliance to this requirement will be evaluated but not required for participation.
SafetyCUAS-Sense-043Safety - Dual ActionThe CUAS Sensor, if hazardous, shall employ a two independent action sequence by the operator before a hazardous state is entered.ThresholdThresholdApproved
CUAS-Sense-044Safety - Hazardous IndicationThe CUAS Sensor, if hazardous, shall provide indication when the hazardous condition is active.ThresholdThresholdApproved
Sensor CoverageCUAS-Sense-048Field of Regard (Azimuth) - SubsystemThe CUAS Sensor Subsystem shall provide 360 degree azimuth coverage.ThresholdObjectiveApproved
CUAS-Sense-049Field of Regard (Elevation) - SubsystemThe CUAS Sensor Subsystem shall provide {XX} degrees of elevation coverage measured from vehicle waterline.ThresholdObjectiveApprovedElevation minimum FoV is included in the classified annex.
CUAS-Sense-050Sensor OverlapThe CUAS Sensor Subsystem shall have sufficient overlap between sensor units to meet FoR coverage without overdeclaring the number of threats in the scene.ThresholdThresholdApprovedIt is desired that the sensor subsystem not overdeclare threats that are detected within sensor overlap regions.

File details come from the government source that posted it. Updated .