EW Testing
Bring in EW aggressors to attempt to break the system. Use basic TTPs found in Ukraine.
Guide to Unmanned Systems
Regulatory Updates (January 2026)
Section titled “Regulatory Updates (January 2026)”Key Exemptions:
- Blue UAS Cleared List: UAS and components on the DIU’s Blue UAS Cleared List.
- “Domestic End Product” Compliant: UAS and components that meet the Buy American Act standard.
These exemptions allow manufacturers of qualifying secure and domestic drones to continue seeking FCC equipment authorization until January 1, 2027.
Documents:
Leader’s Guide to Unmanned Systems
Section titled “Leader’s Guide to Unmanned Systems”Return back to Unmanned Systems
Training for Subordinates
Section titled “Training for Subordinates”Unmanned Systems: Dealing with Vendors
Section titled “Unmanned Systems: Dealing with Vendors”This section helps leaders identify attributes and aspects that have been problematic in the past.
[insert unit org or other] requires an unmanned system that ensures modularity and open architecture for easy modifications and upgrades, with capabilities such as auto-frequency switching and hardened GPS-Rx for robust operation against jamming. The system must be day/night capable, support swappable communication modules, and run on a non-proprietary operating system and backend to avoid vendor lock-in and ensure compatibility.
SWaP-C Comparison Table for Unmanned Systems
Section titled “SWaP-C Comparison Table for Unmanned Systems”SWaP-C: Size, Weight, Power, Cost
| Model | Size | Weight | Power | Cost | Point of Contact | Remarks |
|---|---|---|---|---|---|---|
| Model A | ||||||
| Model B |
Key Phrases to Watch For
Section titled “Key Phrases to Watch For”- Modularity and Open Architecture: Important for flexibility and ease of maintenance.
- Auto-frequency Switching: Indicates advanced capability for frequency management.
- Hardened GPS-Rx: Suggests robustness against GPS jamming.
- Non-Proprietary OS/Back End: Avoids vendor lock-in.
- Built-for-Purpose: Custom solutions tailored for specific needs.
- Proprietary Systems: Buzzwords indicating a lack of flexibility.
- “With enough Time/Resources”: Easy cop-out for missing features.
- Unjammable UAS: Any company claiming their UAS is unjammable.
- Future Features: Phrases like ”*** feature to be implemented Q4”.
- EW-proof: Claims of being electronic warfare-proof without evidence.
Questions Leaders Should Be Asking
Section titled “Questions Leaders Should Be Asking”- How does the system ensure modularity and open architecture?
- Can you provide examples of how the system can be easily modified or upgraded?
- What are the specific capabilities and limitations of the system in terms of auto-frequency switching and hardened GPS-Rx?
- What operating system and backend does the system use?
- Is it non-proprietary, and how easily can it be integrated with other systems?
- Is the imaging system shutterless, and how does this benefit continuous image capture?
- Is the system day/night capable?
- Does the system support swappable communication modules?
- How does this system work in the total absence of links (no GNSS, no Starlink)?
- What is the CE90 of this system under such conditions?
- How does it guide to target (end-game)?
- Can you provide case studies for specific missions?
- How does the system handle maintenance and repair?
- Are there any vendor-specific maintenance requirements?
- Can we perform basic maintenance and repairs in-house?
- What kind of support and service do you offer post-purchase?
- Can you provide details on your customer support and SLAs?
- What are the security measures against electronic warfare (EW) threats?
- How has the system been tested against EW threats?
- Have any of your systems been tested in battlefield conditions?
- Can you provide specific locations and details on the testing environment?
Actions for Technical Section or Consultant to Validate SUAS Claims
Section titled “Actions for Technical Section or Consultant to Validate SUAS Claims”Signal Resilience
Test the system’s ability to operate without GPS and in the presence of signal jamming and spoofing.
Integration Testing
Test the integration of the system with existing technology and workflows.
Cost Analysis
Conduct a thorough cost analysis to uncover any hidden costs.
Ukraine Combat Lessons Learned
Section titled “Ukraine Combat Lessons Learned”| Factor | US/Western Approach | Ukrainian Approach |
|---|---|---|
| Development Cycle | Years (acquisition process) | Weeks/months |
| Testing Environment | Simulated (Yuma) | Active combat against peer EW |
Telltale Signs Leaders Should Be Aware Of
Section titled “Telltale Signs Leaders Should Be Aware Of”Modularity and Open Architecture:
- Commercial UUVs might have stringent vendor-dependent maintenance requirements (e.g., $30k fix for a screw).
- “John Deere problem” - maintenance highly controlled by the vendor.
- Lack of focus on robotics/theory by company leadership.
Red Flags:
- No mention of how the system will prevail against EW.
- Anything in a tube: Expensive and can’t be easily modified.
- Testing environments where failure is bad for someone’s career.