Attachment A_C-UAS Characteristics Spreadsheet.xlsx
XLSX spreadsheet 94 KB Posted
- Attached to
- Request for Information (RFI) - U. S. Coast Guard (USCG) Counter - Unmanned Aircraft Systems (C-UAS)
- Solicitation number
- 70Z02325IRASX0001
About this file
This document is a Request for Information (RFI) from the U.S. Coast Guard (USCG) seeking market research on Counter-Unmanned Aircraft Systems (C-UAS) with detailed technical specifications. The RFI requires vendors to complete a comprehensive 131-question spreadsheet covering physical descriptions, detection capabilities, tracking, mitigation, power requirements, communications, and environmental operational limitations for C-UAS systems across four configuration modes: Fixed, Temporary, On-The-Move, and Portable.
The USCG is specifically seeking C-UAS technologies with a Technology Readiness Level (TRL) of 7 or greater, targeting systems capable of detecting, identifying, tracking, and mitigating unauthorized unmanned aerial vehicles. Vendors must submit Attachment A (C-UAS Characteristics Spreadsheet), Attachment B (Frequency Allocation form), and a five-page capabilities statement by July 25, 2025. The research aims to evaluate potential C-UAS solutions for various operational scenarios, with particular interest in systems that can detect multiple UAVs simultaneously, operate in challenging environmental conditions, and provide comprehensive threat mitigation capabilities.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Attachment B_DD-1494.pdf | ||
| USCG C-UAS RFI 2025_Final.pdf |
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
Instructions
ATTACHMENT A
COUNTER UNMANNED AIRCRAFT SYSTEM (C-UAS) CHARACTERISTICS
MARKET RESEARCH INSTRUCTIONS
| Instructions: | |
| Step 1. Complete 1.0 Technical Characteristics and Questions by creating a tab for EACH applicable C-UAS employment product. | |
| Enter organization name, submitter name, and submitter contact information. |
Identify the C-UAS Product Name where response to questions below applies. This allows for vendor having more than one employment product.
Enter the response to the question in Column D relevant to the designated C-UAS employment product.
| Step 2. Complete 2.0 Production: Technology Readiness Level (TRL) for EACH C-UAS employment product. |
| Step 3. Complete 3.0 System Rough Order of Magnitude (ROM) for EACH C-UAS employment product. |
| Step 4. Complete 4.0 System Configuration Context for EACH C-UAS employment product. |
| Step 5. Complete 5.0 C-UAS Environmental Operational Limitations for EACH C-UAS employment product. |
| Step 6. Complete 6.0 Photos and/or Video Clips for EACH C-UAS employment product. |
| Step 7. Complete 7.0 Demonstration |
GRM Dispositioned Change Request Tracker 20161101 Activities+Scenarios_v1.0 &N &D
Notes and Definitions
1.1 NOTES AND DEFINITIONS
| Configurations: | Fixed | Temporary | On-The-Move | Portable |
| The C-UAS is intended to be a mix of configurations to cover various operational scenarios and needs. While the defined configurations are not yet finalized, they may include a Fixed, Temporary, On-The-Move, and Portable version. |
• Fixed - System has a permanent installation and cannot be moved unless the vendor or trained government technicians relocate the system. Installation may require extra infrastructure to be installed. Installation may require precise site surveying or measurement of the electromagnetic spectrum that must be repeated if the system is moved to another location.
• Temporary - System can be moved by operators of the system, requiring some non-permanent positioning and stabilization. The System cannot be moved by a single person and is only operable while stationary. Minimal detailed site surveys or environmental measurements are needed when moving to a new location.
• On-The-Move - System is part of a moving platform such as a Coast Guard Cutter or boat. The system requires automated detection, classification, and tracking of UAS threats with the potential to integrate into existing combat systems for coordinated responses.
• Portable - System is light and compact enough to be carried at length by a single operator.
| UAS Groups: |
| Based on existing Department of Defense (DoD) classification guidance and Federal Aviation Administration (FAA) registration criteria, the following weight criteria apply to drone groups: |
| UAS Group | Max UAS Weight (lbs) | Notes |
| Group 1 | 0 - 20 | Includes Nano, Micro, Very Small, and Small UAS |
| Group 2 | 21 - 55 | |
| Group 3 | 55 - 1320 |
Definitions of Capability:
The core mission capabilities of the C-UAS include the following:
Figure 1: Core Mission Capabilities
| Detect: The ability to discover the presence of an unmanned airborne object within a defined reaction time and within a defined volume of airspace during all weather, day/night, 24x7x365. |
| Identify: The ability to positively ascertain a detected Target of Interest (TOI) with a unique identifier and aircraft characteristics, to determine the level of threat, risk, and/or intent of a detected TOI. |
| Monitor: The ability to receive updated and continuous flight information, intelligence, and other advance and historical information of a TOI. |
| Track: The ability to follow the progress or movements of a TOI continuously from detection through response for total airspace situational awareness. |
| Warn: The ability to warn the operator of the unmanned aircraft system or unmanned aircraft, including by passive or active, and direct or indirect physical, electronic, radio, and electromagnetic means. |
| Disrupt: The ability to disrupt control of the unmanned aircraft system or unmanned aircraft, without prior consent, including by disabling the unmanned aircraft system or unmanned aircraft by intercepting, interfering, or causing interference with wire, oral, electronic, or radio communications used to control the unmanned aircraft system or unmanned aircraft. |
| Seize: The ability to seize or exercise control of the unmanned aircraft system or unmanned aircraft, or otherwise confiscate the unmanned aircraft system or unmanned aircraft and use reasonable force, if necessary, to disable, damage, or destroy the unmanned aircraft system or unmanned aircraft. |
DEMONSTRATION
1.0 Tech Char & Questions
ATTACHMENT A
COUNTER UNMANNED AIRCRAFT SYSTEM (C-UAS) CHARACTERISTICS
MARKET RESEARCH
| 1.0 TECHNICAL CHARACTERISTICS AND QUESTIONS | |||
| Organization Name | |||
| Submitter Name | |||
| Submitter Email | |||
| Submitter Phone Number | |||
| C-UAS Product Name | (e.g., Product Mode 1 - Xxxxxxx xxxxxxx xxxxxxxxxx) | ||
| Entry # | Question ID | Question | Response |
| PHYSICAL DESCRIPTION | |||
| 1 | PHYSD-001 | Is the system considered Fixed, Temporary, On-The-Move (Cutters), or Portable Employment Mode (see tab, Notes and Definitions)? | |
| 2 | PHYSD-002 | Volume and Weight: Provide the volume (LxWxH) and weight (Lbs) of the fully operational system both in operational and shipping configuration. Provide the number of packing cases for the system. | |
| 3 | PHYSD-003 | Material: List the manufacturing materials used in the system. | |
| 4 | PHYSD-004 | Sensors: What types of sensors are included in the system? List them all and their type (e.g., Radar, EO/IR) | |
| 5 | PHYSD-005 | Mitigation: What types of mitigation components and techniques are included? List components and technique (e.g., RF Jamming, GNSS Jamming, Kinetic) | |
| PERFORMANCE | |||
| DETECT | |||
| 6 | DTCT-001 | What is the maximum detection range for a UAV, and (if known) accuracy of detection? Provide conditions for detection range. | |
| 7 | DTCT-002 | Specify the detection ranges for different radar cross-sections (RCS), different RF signal strengths, and different group/size UAV (see tab, Notes for definitions) | |
| 8 | DTCT-003 | How was the maximum range determined (e.g., lab test, operational test, M&S)? | |
| 9 | DTCT-004 | What is the probability of detection? Does it vary by RCS, RF signal strength, and/or size of UAV? | |
| 10 | DTCT-005 | What is the probability of false detection? Does it vary by RCS, RF signal strength, and/or size of UAV? | |
| 11 | DTCT-006 | What range of UAV radio frequencies can the C-UAS cover for detection? Provide conditions for detection range. | |
| 12 | DTCT-007 | Can more than one UAV be detected simultaneously? What is the max number of simultaneous detections? What is the system impact when the # of targets exceeds the detection capability? | |
| 13 | DTCT-008 | How is the operator alerted to a detected UAV? What information is shown/displayed regarding a detection? | |
| 14 | DTCT-009 | Is there a minimum detection count before displaying the information to the user? | |
| 15 | DTCT-010 | If system provides location information for detected target, what is the accuracy of location information? | |
| 16 | DTCT-011 | Can the system detect the ground control station/UAV operator? | |
| 17 | DTCT-012 | What is the field of view of the detection sensors? Azimuth (in degrees)? Elevation (in degrees)? Provide conditions for detection range. | |
| 18 | DTCT-013 | What combination of sensors is used during detection? | |
| 19 | DTCT-014 | If multiple sensors are used for detection, how is display order selected? Can user prioritize system detections based on desired primary/secondary/tertiary systems? | |
| 20 | DTCT-015 | Is the system limited to detecting certain makes/models/brands of UAV? Provide Signal of Interest (SOI) list. | |
| 21 | DTCT-016 | For library based systems, can signals be added by user? If so, what is the process? If not, how can signals be added to existing SOI list? | |
| 22 | DTCT-017 | Can the system detect UASs that are not in its library? | |
| 23 | DTCT-018 | Can the system detect dark drones? | |
| 24 | DTCT-019 | For mitigation systems only: Are detection capabilities compromised during mitigation? | |
| 25 | DTCT-020 | For system of systems: Are detections consolidated? If so, what logic is used? | |
| 26 | DTCT-021 | Load: What is the extreme but manageable volume of detected targets? | |
| 27 | DTCT-022 | Stress: What is the detected target saturation overload? | |
| IDENTIFY/CLASSIFY | |||
| 28 | IDCL-001 | What is the maximum classification/ID range for a UAV and (if known) accuracy of classification/ID? | |
| 29 | IDCL-002 | Specify the classification/ID ranges for different radar cross-sections (RCS), different RF signal strengths, and different group/size UAV (see tab, Notes and Definitions) | |
| 30 | IDCL-003 | What is the probability of classification/ID of a UAV once a target is detected and/or tracked? Does it vary by RCS, RF signal strength, and/or size of UAV? | |
| 31 | IDCL-004 | What is the probability of false classification/ID of a UAV once a target is detected and/or tracked? Does it vary by RCS, RF signal strength, and/or size of UAV? | |
| 32 | IDCL-005 | How was the maximum range determined (e.g., lab test, operational test, M&S)? Provide conditions for identification/classification. | |
| 33 | IDCL-006 | Can more than one UAV be classified/ID simultaneously? What is the max number of simultaneous classified/ID? What is the system impact when the number of targets exceeds the simultaneous classification capability? | |
| 34 | IDCL-007 | How is the operator alerted to a classified/ID UAV? What information is shown/displayed regarding a classified/ID? | |
| 35 | IDCL-008 | What are the number of detections or time needed for system to classify/ID? | |
| 36 | IDCL-009 | Load: What is the extreme but manageable volume of ID/classify targets? | |
| 37 | IDCL-010 | Stress: What is the classification/ID target saturation overload? | |
| TRACK | |||
| 38 | TRK-001 | What is the maximum tracking range for a UAV and (if known) accuracy of tracking? Provide conditions for tracking. | |
| 39 | TRK-002 | Specify the tracking ranges for different radar cross-sections (RCS), different RF signal strengths, and different group/size UAV (see tab, Notes and Definitions) | |
| 40 | TRK-003 | What is the probability of tracking once a UAV is detected? Does it vary by RCS, RF signal strength, and/or size of UAV? | |
| 41 | TRK-004 | What is the probability of false tracking once a UAV is detected? Does it vary by RCS, RF signal strength, and/or size of UAV? | |
| 42 | TRK-005 | How was the maximum range determined (e.g., lab test, operational test, M&S)? Provide conditions for range. | |
| 43 | TRK-006 | How long from detection until the system declares a track? What is the longest the system has maintained a track on a UAV? What is the average time the system maintains a track on a UAV? | |
| 44 | TRK-007 | Can more than one UAV be tracked simultaneously? What is the max number of simultaneous tracking's? What is the system impact when the number of targets exceeds the tracking capability? | |
| 45 | TRK-008 | How is the operator alerted to a tracked UAV? What information is shown/displayed regarding a tracking? | |
| 46 | TRK-009 | Can the system locate or track the ground control station/UAV operator? What is the accuracy of the location data? | |
| 47 | TRK-010 | Can the system track targets resulting from track fusion of long and short range radar data? | |
| 48 | TRK-011 | Load: What is the extreme but manageable volume of tracked targets? | |
| 49 | TRK-012 | Stress: What is the tracked target saturation overload? | |
| RESPOND/MITIGATE | |||
| 50 | RESPM-001 | What is the maximum mitigation range for a UAV? Provide conditions for range. | |
| 51 | RESPM-002 | Specify the mitigation ranges for different radar cross-sections (RCS), different RF signal strengths, and different group/size UAV (see tab, Notes and Definitions) | |
| 52 | RESPM-003 | What is the process for mitigation? Describe how the mitigation will occur. | |
| 53 | RESPM-004 | What is the probability of mitigation effect? Does it vary by RCS, RF signal strength, and/or size of UAV? | |
| 54 | RESPM-005 | What is the probability of false mitigation effect? Does it vary by RCS, RF signal strength, and/or size of UAV? | |
| 55 | RESPM-006 | What is the range of mitigation (if known)? Does it vary by RCS, RF signal strength, and/or size of UAV? | |
| 56 | RESPM-007 | How was the maximum range determined (e.g., lab test, operational test, M&S)? Provide conditions for range. | |
| 57 | RESPM-008 | What is the time needed to prepare mitigations (from response initiation to effects on target)? | |
| 58 | RESPM-009 | What are the mitigation types? Does it vary by RCS, RF signal strength, and/or size of the UAV? | |
| 59 | RESPM-010 | Can more than one UAV be mitigated simultaneously? What is the max number of simultaneous mitigations? What is the system impact when the number of targets exceeds the mitigation capability? | |
| 60 | RESPM-011 | Can the system mitigate non-library based targets? | |
| 61 | RESPM-012 | How is the operator alerted to a mitigated UAV? What information is shown/displayed regarding a mitigated UAV? | |
| 62 | RESPM-013 | How does the system assess mitigation? How long does it take to make that assessment? | |
| 63 | RESPM-014 | Does the operator have an option to mitigate manually and is there an option to mitigate automatically? | |
| 64 | RESPM-015 | What is the maximum mitigation duration? What, if any, are the mitigation constraints? | |
| 65 | RESPM-016 | Load: What is the extreme but manageable volume of mitigated targets? | |
| 66 | RESPM-017 | Stress: What is the mitigated target saturation overload? | |
| RADAR (If applicable) | |||
| 67 | RDR-001 | Is the Radar omnidirectional or sector? | |
| 68 | RDR-002 | For Radar: |
What Bandwidth and Power levels does the radar emit?
69 RDR-003 For Radar:
What spectrum certifications does the radar have?
70 RDR-004 For Radar:
What are the safety precautions when the radar is active, such as safe standoff distance, fuel, ordnance?
71 RDR-005 For Radar:
How will profiles be created? Will user require radar basics or will vendor travel to each of the sites needed?
| PASSIVE RF (If applicable) | ||
| 72 | PASRF-001 | For Passive RF: |
What is the range of frequencies, RF signatures, and communication protocols as part of the current library?
73 PASRF-002 For Passive RF:
Which UAV models are covered in RF detection?
74 PASRF-003 For Passive RF:
What information can be extracted from RF detection of UAVs (UAV location, altitude, heading, serial number, flight times, takeoff position, etc.)?
75 PASRF-004 For Passive RF:
How is the system library updated to include new UAVs?
| 76 | PASRF-005 | Does the system have a white-listing capability or ability to distinguish known, friendly UAVs from unknown adversary UAVs? |
| EO/IR SENSOR (If applicable) | ||
| 77 | EOIR-001 | For EO/IR sensors, Day operation (if applicable): |
What are the Field of Views in wide-view and max zoom separately), Azimuth, Elevation?
| 78 | EOIR-002 | What are the Field of Views in wide-view and max zoom (separately), Azimuth, Elevation? |
| 79 | EOIR-003 | For EO/IR sensors, Night operation (if applicable): |
What are the Field of Views in wide-view and max zoom separately), Azimuth, Elevation?
80 EOIR-004 For EO/IR sensors, Day operation (if applicable):
Does the camera have pan/tilt/zoom capability for UAV tracking?
81 EOIR-005 For EO/IR sensors, Night operation (if applicable):
Does the camera have pan/tilt/zoom capability for UAV tracking?
82 EOIR-006 For EO/IR sensors, Day operation (if applicable):
What is the Image Resolution (in pixels)?
83 EOIR-007 For EO/IR sensors, Night operation (if applicable):
What is the Image Resolution (in pixels)?
84 EOIR-008 For EO/IR sensors, Day operation (if applicable):
What is the Scan Rate?
85 EOIR-009 For EO/IR sensors, Night operation (if applicable):
What is the Scan Rate?
86 EOIR-010 For EO/IR sensors, Day operation (if applicable):
What is the low light sensitivity of the EO sensor?
87 EOIR-011 For EO/IR sensors, Night operation (if applicable):
What is the low light sensitivity of the EO sensor?
88 EOIR-012 For EO/IR sensors, Day operation (if applicable):
What are the sensing wavelengths of the IR sensor?
89 EOIR-013 For EO/IR sensors, Night operation (if applicable):
What are the sensing wavelengths of the IR sensor?
| 90 | EOIR-014 | Can the EO/IR sensor zoom-to-range? If so, are there set intervals or can the zoom be set to any valid range? If intervals, what are the set range intervals for UAV-sized targets? |
| 91 | EOIR-015 | Can the EO/IR sensor focus-to-range? If so, are there set intervals or can the focus be set to any valid range? If intervals, what are the set range intervals for UAV-sized targets? |
| 92 | EOIR-016 | Does the camera have an integrated GPS system? |
| 93 | EOIR-017 | Can the camera be networked for remote access and control? |
| 94 | EOIR-018 | Does the camera have automatic object identification capability for UAVs? What types/sizes of UAVs, and at what ranges can it automatically identify the different types/sizes of UAVs. |
| ACOUSTIC (If applicable) | ||
| 95 | ACSTC-001 | For Acoustic: |
What is the range of acoustic signatures and communication protocols as part of the current library?
96 ACSTC-002 For Acoustic:
How is the system library updated to include new UAVs?
| 97 | ACSTC-003 | What is the maximum background noise floor for proper sensor operation? |
| POWER | ||
| 98 | PWR-001 | Power Category: How is the system powered? Battery, Shore Power, or other? What are the power requirements (Watts)? What are peak and average power? |
| 99 | PWR-002 | Is there a single source of power or various power sources for each component? Is there a primary and backup power source? List the power sources. |
| 100 | PWR-003 | What are the input power requirements for the system to operate (e.g., VAC, Amps)? List the power requirements for the following functions, as applicable: nominal, idle, detection, tracking, mitigating, and reporting. |
| 101 | PWR-004 | For Vehicle mounted systems and On-The- Move systems what operating time limitations are there based on generator/ alternator/ battery power system requirements? If powered by batteries, can batteries be hot swapped? What is the run time per battery? |
| 102 | PWR-005 | Effective Radiated Power: What is the effective radiated power (Watts) for the system? |
| SUITABILITY | ||
| 103 | SUIT-001 | Does the system rely on an RF communication link between the UAV and ground control station/UAV operator to detect/track/classify/ID/mitigate? Can the system detect/classify/ID/etc. UAVs if this RF link is not present? |
| 104 | SUIT-002 | Can the system operate and detect/track/classify/ID/mitigate during dark nighttime operation? |
| 105 | SUIT-003 | Can the system operate and detect/track/classify/ID/mitigate during inclement weather such as thunderstorms, snowstorms, etc.? |
| 106 | SUIT-004 | What is the range of environmental conditions the system can operate (e.g., temperature, wind, humidity, and sand/dust)? |
| 107 | SUIT-005 | How many operators are required to operate the system? |
| 108 | SUIT-006 | How many operators are required to setup and breakdown the system for transport? |
| 109 | SUIT-007 | How many people are required to setup and breakdown the system? Approximately how long does it take to setup and breakdown the system for transport? |
| 110 | SUIT-008 | Can the system be broken down and transported over rough terrain without damage? |
| 111 | SUIT-009 | What is the operating time on a full charge and the time required to fully recharge (if battery powered)? |
| 112 | SUIT-010 | Are there any demonstrated Reliability, Maintainability, and Availability metrics for the system (e.g., Operational Availability (Ao), Mean Time Between Failure (MTBF), Mean Time to Restore Function (MTRF))? |
| 113 | SUIT-011 | Are there any cybersecurity or physical security features included with the system, such as network security or data encryption? |
| 114 | SUIT-012 | Are there any previous certifications (with government agencies) with this system such as Authority to Operate (ATO), Request for Authorization (RFA) approval or other? |
| 115 | SUIT-013 | What training is available for the system (e.g., operator, maintainer, system administrator, setup/breakdown, configure)? How long is each training course? What maintenance/training/operating guides (technical data) are included with the system? |
| 116 | SUIT-014 | Is there a recommended preventative maintenance schedule with the system? How are software and hardware updates incorporated? Are there additional costs for future updates? |
| 117 | SUIT-015 | What maintenance actions are required to be done by the vendor versus the owner/operator? Is there a need for any specialized servicing tool kits? If so, please provide the list of items (i.e., spec-an, attenuator, etc.). |
| 118 | SUIT-016 | What is the frequency of software/hardware updates? |
| 119 | SUIT-017 | Are there any safety issues or potential hazards associated with the system? How are they handled? |
| 120 | SUIT-018 | For devices placed on rooftops: Is 20 pounds per square foot metric met for anything concentrated 300+ lbs.? |
| 121 | SUIT-019 | For On-The-Move systems, does the system have its own GPS locator or does it require external position information? If the system performance is dependent on the ship’s motion, does it have its own inertial navigation unit to correct for ship’s motion or does it require external motion information? |
| COMMUNICATIONS/INTEROPERABILITY | ||
| 122 | COMIO-001 | Are there any unique or innovative capabilities included with this system (e.g., autonomous operation, machine learning, AI, automated target recognition, multi-phenomenology fusion, correlation, remote software updates, or adapt to changes in UAV technology)? |
| 123 | COMIO-002 | Are there any unique or innovative capabilities planned in the future (e.g., autonomous operation, machine learning, AI, automated target recognition, multi-phenomenology fusion, correlation, remote software updates, or adapt to changes in UAV technology)? |
| 124 | COMIO-003 | Is this system capable of integrating with other systems? If so, list the interface standards supported or APIs implemented? If applicable, how much of each standard is implement (in percent)? |
| 125 | COMIO-004 | Please describe any internal or external networks as part of the system? Can the system be operated remotely? |
| 126 | COMIO-005 | Does the system communicate with an external information network and server? |
| 127 | COMIO-006 | Is the external communication encrypted (such as TLS/SSL or https://) for security? |
| 128 | COMIO-007 | Does the system log historical data on detections? What type of UAV information is captured (e.g., frequency, make/model, lat/long, timestamp)? |
| 129 | COMIO-008 | Does the system have an auto-purge capability to delete information older than a certain age? (i.e. will it self-delete at the 180 day mark as required by 124n?) |
| 130 | COMIO-009 | Is there a data extraction, reporting, or visualization capability included with the system? |
| 131 | COMIO-010 | Does the system have audio-visual alert for the operator (on-site and/or remote site) when a UAV is detected? |
| TRANSPORTABILITY | ||
| 132 | TRNSP-001 | Approximately how long does it take to setup and break down the system for transport? |
| 133 | TRNSP-002 | For mobile systems, can the system fit in the bed of a pickup truck? Backpack-able? Limitations to air transport/shipment? |
| 134 | TRNSP-003 | For temorary systems, can the system fit in the rear of a medium sized SUV? If not what size vehicle is appropriate? |
&F &N &D
2.0 Production
ATTACHMENT A
COUNTER UNMANNED AIRCRAFT SYSTEM (C-UAS) CHARACTERISTICS
MARKET RESEARCH
2.0 PRODUCTION: TECHNOLOGY READINESS LEVEL (TRL)
For this RFI, the USCG is requesting C-UASs with a Technology Readiness Level (TRL) of 7 or greater. Select the configuration from the drop down, enter the TRL provide the justification. For systems that can be used for multiple configurations fill out multiple lines (ex. System #1 is TRL 8 for Fixed Site configuration but TRL5 for On-the-Move configuration). If a C-UAS product is stated as having a TRL of 8 or greater, then it will be necessary to reference operational test results conducted under a US Government Operational Test Authority. Please note if you have any existing contracts for the system.**CONTRACTING craft better language and specific information you would want for existing contracts**
| Please provide an estimated TRL and a brief justification for each rating. refer to the Government Accountability Office Technology Readiness Assessment Guide of Jan 2020, which provided key objectives for meeting each level of technology. (https://www.gao.gov/assets/gao-20-48g.pdf) | ||||
| Product Name | Configuration | TRL | TRL Justification | Existing Contract(s) or Strategic Vehicles |
| C-UAS Employment Product Name/Model Number 1 | ||||
| C-UAS Employment Product Name/Model Number 2 | ||||
| C-UAS Employment Product Name/Model Number 3 | ||||
| C-UAS Employment Product Name/Model Number 4 | ||||
| C-UAS Employment Product Name/Model Number 5 |
&F &N &D
3.0 System ROM
ATTACHMENT A
COUNTER UNMANNED AIRCRAFT SYSTEM (C-UAS) CHARACTERISTICS
MARKET RESEARCH
3.0 SYSTEM ROUGH ORDER OF MAGNITUDE (ROM)
Provide the System Rough Order of Magnitude (ROM) for each C-UAS employment product.
| C-UAS Product 1 | C-UAS Product 2 | C-UAS Product 3 | C-UAS Product 4 | C-UAS Product 5 | |
| a) Product Name / Model Number | |||||
| b) Product Employment Mode |
(e.g., Drop-down List Values*: Fixed, Temporary, On-The-Move, Portable) *Reference Tab Notes and Definitions
| c) Unit Cost: $0.00 (Please provide Bill of Material comprising this Unit Cost) |
| d) Unit Cost: $0.00 at quantity break points (e.g., cost of purchasing ≤ 10 units = $0.00 per unit, Cost of purchasing ≥ 11 units to ≤ 25 units = $0.00 per unit, etc.) |
| e) Delivery date (lead-time in months) of unit number 1 after date of Contract Award: |
(e.g., ______months )
| f) Deliveries per month after delivery of unit number 1: (e.g., ______units) |
| g) Training Class Cost: (e.g., $______per Class per Operator (or # of Operators)) |
| h) Train the Trainer Class Cost: (e.g., $______per Class per Trainer (or # or Trainers)) |
| i) Operating and Maintenance Manuals and Technical Drawings: (e.g., $______per set) |
| j) Annual Maintenance (Hardware and Software updates, other maintenance, etc.): |
(e.g., $______per year
| k) Tech Refresh Cycle (Recommended # years for tech refresh of the system): (e.g., ______years) |
| l) Estimate Tech Refresh Cost: (e.g., $______per tech refresh) |
| m) Operational Cost (Resources needed to operate system): (e.g., ______operators) |
| n) Modification Cost (Estimated modifications needed to meet technical characteristics identified): |
(e.g., $______estimated non-recurring cost)
o) Integration and Test (Estimated integration and test cost required to be fielded):
(e.g., $______estimated non-recurring cost)
&F &N &D
4.0 System Config Context
ATTACHMENT A
COUNTER UNMANNED AIRCRAFT SYSTEM (C-UAS) CHARACTERISTICS
MARKET RESEARCH
4.0 SYSTEM CONFIGURATION CONTEXT
| The vendor shall provide: | |
| 1) A diagram and explanation of the system configuration context for each C-UAS employment configuration (Fixed, | Temporary, On-The-Move, and Portable), |
2) A Technical Data Sheet/Specifications for each C-UAS employment product,
3) The enviornmental operating limitations,
4) The deployment and setup procedures for each C-UAS employment product.
| C-UAS Product 1 | C-UAS Product 2 | C-UAS Product 3 | C-UAS Product 4 | C-UAS Product 5 |
| Product Name/Model Number: Xxxxxxxxx xxxxxxxxxx | Product Name/Model Number: Xxxxxxxxx xxxxxxxxxx | Product Name/Model Number: Xxxxxxxxx xxxxxxxxxx | Product Name/Model Number: Xxxxxxxxx xxxxxxxxxx | Product Name/Model Number: Xxxxxxxxx xxxxxxxxxx |
| C-UAS Employment Configuration: | C-UAS Employment Configuration: | C-UAS Employment Configuration: | ||
| Diagram and Explanation of System Configuration Context | Diagram and Explanation of System Configuration Context | Diagram and Explanation of System Configuration Context | Diagram and Explanation of System Configuration Context | Diagram and Explanation of System Configuration Context |
Technical Data Sheet/Specifications Technical Data Sheet/Specifications Technical Data Sheet/Specifications Technical Data Sheet/Specifications Technical Data Sheet/Specifications
Deployment and Setup Procedures (and estimated durations) Deployment and Setup Procedures (and estimated durations) Deployment and Setup Procedures (and estimated durations) Deployment and Setup Procedures (and estimated durations) Deployment and Setup Procedures (and estimated durations)
&F &N &D
5.0 Environmental Limits
ATTACHMENT A
COUNTER UNMANNED AIRCRAFT SYSTEM (C-UAS) CHARACTERISTICS
MARKET RESEARCH
| 5.0 C-UAS Environmental Operational Limitations | |||||
| This table should be completed by the vendor to clearly define the environmental limitations of their Counter-UAS (C-UAS) system. Please be as specific as possible, providing quantifiable data where available. Example at the bottom | |||||
| C-UAS Product 1 | |||||
| Product Name/Model Number: Xxxxxxxxx xxxxxxxxxx | |||||
| C-UAS Employment Configuration: | On-The-Move | ||||
| Environmental Factor | Operational Limitation Description | Impact on System Performance | Mitigation Strategy (if applicable) | Notes/Comments | |
| Temperature | |||||
| Humidity | |||||
| Precipitation | |||||
| Wind | |||||
| Visibility | |||||
| Altitude | |||||
| Electromagnetic Interference (EMI) | |||||
| Solar Radiation | |||||
| Terrain | |||||
| Shock/Vibration | |||||
| Other Environmental Factors | |||||
| EXAMPLE | |||||
| C-UAS Employment Configuration: | On-The-Move | ||||
| Environmental Factor | Operational Limitation Description | Impact on System Performance | Mitigation Strategy (if applicable) | Notes/Comments | |
| Temperature | Operating Temperature Range (e.g., -20°C to +50°C) | Performance degradation outside optimal range (specify how, e.g., reduced detection range, increased false alarms) | Heated/cooled enclosures, thermal management system | Specify any temperature-related calibration requirements. | |
| Humidity | Operating Humidity Range (e.g., 0% to 95% non-condensing) | Performance degradation outside optimal range (specify how, e.g., reduced detection range, system malfunction) | Sealed enclosures, desiccant packs | Specify condensation limits. | |
| Precipitation | Rain, Snow, Hail (e.g., maximum rainfall rate, snow accumulation) | Performance degradation or system failure (specify how, e.g., reduced detection range, obscured vision) | Protective covers, hydrophobic coatings, automated cleaning systems | Specify impact of different precipitation types. | |
| Wind | Maximum operating wind speed (e.g., gusts and sustained) | System instability, reduced accuracy, potential damage (specify thresholds and impact) | Stabilization mechanisms, anchored deployments | Specify wind direction sensitivity. | |
| Visibility | Fog, Dust, Smoke (e.g., visual range limitations) | Reduced detection range, impaired tracking performance | Alternative detection methods (e.g., radar, RF), environmental monitoring systems | Specify impact on different sensor types (e.g., optical, RF). | |
| Altitude | Operational Altitude Range (e.g., sea level to 5,000 ft) | Performance degradation outside optimal range (specify how, e.g., reduced detection range, power limitations) | Altitude compensation mechanisms | Specify any altitude-related calibration requirements. | |
| Electromagnetic Interference (EMI) | Susceptibility to EMI from other sources (e.g., radar, radio communications) | False alarms, interference with system operation | EMI shielding, filtering, frequency agility | Specify frequency bands affected. | |
| Solar Radiation | Impact of direct sunlight or solar flares | Sensor saturation, reduced detection performance | Optical filters, shading | Specify impact on different sensor types (e.g., optical, thermal). | |
| Terrain | Impact of terrain features (e.g., mountains, urban canyons) | Signal blockage, multipath propagation, reduced detection range | Terrain following radar, networked deployments | Specify limitations on terrain slope, vegetation density. | |
| Other Environmental Factors | (e.g., icing, lightning, corrosive atmospheres) | Describe impact on system | Mitigation strategies | Provide specific details |
6.0 Photos-Video Clips
ATTACHMENT A
COUNTER UNMANNED AIRCRAFT SYSTEM (C-UAS) CHARACTERISTICS
MARKET RESEARCH
6.0 PHOTOS and/or VIDEO CLIP
The vendor shall provide links to photos and/or videos for each C-UAS employment product name/model number:
| Photos: No more than 2 of the system and 5 showing sensor capabilities. |
| Video: No more than 1 minute of the system and 4 minutes showing sensor capabilities. |
| Photo Links | Video Links | |
| [Add Employment Product Name/Model Number 1] | ||
| [Add Employment Product Name/Model Number 2] | ||
| [Add Employment Product Name/Model Number 3] | ||
| [Add Employment Product Name/Model Number 4] | ||
| [Add Employment Product Name/Model Number 5] |
&F &N &D
7.0 Demonstration
ATTACHMENT A
COUNTER UNMANNED AIRCRAFT SYSTEM (C-UAS) CHARACTERISTICS
MARKET RESEARCH
7.0 DEMONSTRATION
| a) Complete production unit available for product demonstration? | |||
| A complete production unit would be one in which all components, including the field transportation trailer, are included. | |||
| [Add Employment Product Name/Model Number 1] | YES | NO | (Place "X" in applicable response) |
| [Add Employment Product Name/Model Number 2] | YES | NO | (Place "X" in applicable response) |
| [Add Employment Product Name/Model Number 3] | YES | NO | (Place "X" in applicable response) |
| [Add Employment Product Name/Model Number 4] | YES | NO | (Place "X" in applicable response) |
| [Add Employment Product Name/Model Number 5] | YES | NO | (Place "X" in applicable response) |
| b) If requested, demonstrate at no cost to the Government? | YES | NO | (Place "X" in applicable response) |
| Demonstration, if scheduled, would consist of a series of exercises, day and night, of the full range of system characteristics and technical capabilities. The demonstration would occur at a government-defined test range. |
&F &N &D
8.0 Acronyms
ATTACHMENT A
COUNTER UNMANNED AIRCRAFT SYSTEM (C-UAS) CHARACTERISTICS
MARKET RESEARCH
| 7.0 ACRONYMS | |
| ACRONYM | DEFINITION |
| Ao | Operational Availability |
| AI | Artificial Intelligence |
| Amps | Ampere |
| ATO | Authority to Operate |
| BOM | Bill of Materials |
| CoT | Cursor-on-Target |
| DHS | Department of Homeland Security |
| DoD | Department of Defense |
| DOE | Department of Energy |
| DOJ | Department of Justice |
| EO/IR | Electro-Optical/Infrared |
| FAA | Federal Aviation Administration |
| FCC | Federal Communications Commission |
| GCS | Ground Control Station |
| GNSS | Global Navigation Satellite System |
| ID | Identification |
| LOB | Line of Bearing |
| MRL | Manufacturing Readiness Level |
| MTBF | Mean Time Between Failure |
| RF | Radio-frequency |
| RFA | Request for Authorization |
| RFI | Request for Information |
| ROM | Rough Order of Magnitude |
| sUAS | Small Unmanned Aircraft System |
| S&T | Science and Technology |
| TAK | Android Team Awareness Kit |
| TLS/SSL | Transport Layer Security/Secure Sockets Layer |
| TRL | Technology Readiness Level |
| UAS | Unmanned Aircraft System |
| UAV | Unmanned Aerial Vehicle |
| USCG | U.S. Coast Guard |
| VAC | Voltage (AC) |
&F &N &D
DropdownList
| Employment Mode |
| Fixed |
| Temporary |
| Mobile |
| Portable |
image1.png
File details come from the government source that posted it. Updated .