Irregularpedia

Guide to Unmanned Systems: Difference between revisions

VisualWikitext
Initial
 
removed login requirement
Tags: Manual revert 2017 source edit
 
(5 intermediate revisions by the same user not shown)
Line 1: Line 1:
<span id="leaders-guide-to-unmanned-systems"></span>
= Leader’s Guide to Unmanned Systems =
= Leader’s Guide to Unmanned Systems =


Return back to [[unmanned-systems-chat|unmanned chat]]
Return back to [[unmanned-systems-chat|unmanned chat]]


<span id="training-for-subordinates"></span>
== Training for Subordinates ==
== Training for Subordinates ==


<span id="unmanned-systems-dealing-with-vendors"></span>
== Unmanned Systems: Dealing with Vendors ==
== Unmanned Systems: Dealing with Vendors ==
This section is not intended to call out any specific vendor but to help leaders identify attributes and aspects that have been problematic in the past.


This section is not intended to call out any specific vendor but to help leaders identify attributes and aspects that have been problomatic in the past.
<blockquote>[///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. The imaging system should be shutterless for continuous capture, and the design must be built-for-purpose, tailored to [///insert specific mission needs///]. Maintenance and repair should be feasible in-house, with minimal reliance on vendor-specific services. The system must demonstrate proven performance in challenging environments and be equipped with effective security measures against electronic warfare threats.</blockquote>


<blockquote>[///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. The imaging system should be shutterless for continuous capture, and the design must be built-for-purpose, tailored to [///insert specific mission needs///]. Maintenance and repair should be feasible in-house, with minimal reliance on vendor-specific services. The system must demonstrate proven performance in challenging environments and be equipped with effective security measures against electronic warfare threats.
</blockquote>
<span id="comparison-chart-template"></span>
=== Comparison Chart Template ===
<span id="swap-c-comparison-table-for-unmanned-systems"></span>
== SWaP-C Comparison Table for Unmanned Systems ==
== SWaP-C Comparison Table for Unmanned Systems ==
 
'''SWaP-C''': Size, Weight, Power, Cost
'' '''SWaP-C''': Size, Weight, Power, Cost


{| class="wikitable"
{| class="wikitable"
Line 73: Line 64:
|}
|}


<span id="swap-c-table-key"></span>
== SWAP-C Table Key: ==
=== SWAP-C Table Key: ===
'''Size''': Dimensions of the drone (e.g., L x W x H)
 
'''Weight''': Total weight of the drone including payload (in kg or lbs)
'' '''Size''': Dimensions of the drone (e.g., L x W x H)
'''Power''': Power requirements and battery life (e.g., watts, hours of operation)
'' '''Weight''': Total weight of the drone including payload (in kg or lbs)
'''Cost''': Total cost of the drone (including maintenance and operation costs)
'' '''Power''': Power requirements and battery life (e.g., watts, hours of operation)
'''Point of Contact''': The primary contact person for the drone vendor
'' '''Cost''': Total cost of the drone (including maintenance and operation costs)
'''Remarks''': Additional notes or comments about the drone’s performance, capabilities, and limitations.
'' '''Point of Contact''': The primary contact person for the drone vendor
'' '''Remarks''': Additional notes or comments about the drone’s performance, capabilities, and limitations.
 
<span id="key-phrases-to-watch-for"></span>
=== Key Phrases to Watch For ===
 
<span id="look-for-good"></span>
==== Look For (Good) ====


'' '''Modularity and Open Architecture''': Important for flexibility and ease of maintenance.
== Key Phrases to Watch For ==
*'' Example: There are commercial UUVs where overturning a screw can lead to 6 weeks of downtime and a $30,000 fix, which must be done by the vendor.
=== Look For (Good) ===
'' '''Auto-frequency Switching''': Indicates advanced capability for frequency management.
'''Modularity and Open Architecture''': Important for flexibility and ease of maintenance.
'' '''Hardened GPS-Rx''': Suggests robustness against GPS jamming.
* Example: There are commercial UUVs where overturning a screw can lead to 6 weeks of downtime and a $30,000 fix, which must be done by the vendor.
'' '''Day/Night Capable''': Implies versatility in various lighting conditions.
'''Auto-frequency Switching''': Indicates advanced capability for frequency management.
'' '''Swappable Comms''': Indicates modular communication systems.
'''Hardened GPS-Rx''': Suggests robustness against GPS jamming.
'' '''Non-Proprietary OS/Back End''': Avoids vendor lock-in and promotes compatibility.
'''Day/Night Capable''': Implies versatility in various lighting conditions.
*'' Easily updatable firmware, software, and a DevSecOps pipeline dedicated to continually pushing out patches…timeline of weeks, not years
'''Swappable Comms''': Indicates modular communication systems.
'' '''Shutterless''': Refers to continuous image capture capability.
'''Non-Proprietary OS/Back End''': Avoids vendor lock-in and promotes compatibility.
'' '''Built-for-Purpose''': Custom solutions tailored for specific needs.
* Easily updatable firmware, software, and a DevSecOps pipeline dedicated to continually pushing out patches… timeline of weeks, not years. 
'' “comes with 5 batteries” or “runs on diesel”
'''Shutterless''': Refers to continuous image capture capability.
'' “prisoners are using our platform to drop drugs that’s how hard it is to detect”
'''Built-for-Purpose''': Custom solutions tailored for specific needs.
'' we can “reconstitute faster than they can reconstitute the countermeasure”. (these are the terms of the new DIB arms race!) #### Sounds Good But..
* “comes with 5 batteries” or “runs on diesel”
'' GPS: As for navigation in a GPS denied environment, it’s nice to have, but I haven’t seen it work too well. Buildings, city blocks, treelines, hell whole patches of forest I have seen completely disappear over the course of a few hours. #### Watch Out For (Bad)
* “prisoners are using our platform to drop drugs that’s how hard it is to detect”
'' '''Proprietary Systems''': Buzzwords indicating a lack of flexibility and potential vendor lock-in.
* “we can reconstitute faster than they can reconstitute the countermeasure” (these are the terms of the new DIB arms race!)
'' '''With enough Time and Resources we can do xyz''': Anyone could and does say this and is a pretty easy cop out to detect.
'' '''Unjammable UAS''': Any company claiming their UAS is unjammable.
'' '''Future Features''': Phrases like “''*'' feature to be implemented Q4”.
'' '''Firm Fixed Cost Plus''': Potential hidden costs.
'' '''Special Price''': “My friend, special price for you my friend.”
'' '''EW-proof''': Claims of being electronic warfare-proof without evidence.
'' '''Tested in Battlefield Conditions of Kyiv, Ukraine''': Kyiv is like bragging about being at KAIA or Bagram or Erbil, not necessarily indicative of quality.
'' “An island in the pacific.” Which island? Here’s a pen. Touch the map. Draw an icon. Now tell me what USCT will say.


<span id="questions-leaders-should-be-asking"></span>
#### Sounds Good But..
=== Questions Leaders Should Be Asking ===
* '''GPS''': As for navigation in a GPS denied environment, it’s nice to have, but I haven’t seen it work too well. Buildings, city blocks, treelines, hell, whole patches of forest I have seen completely disappear over the course of a few hours. 


'' How does the system ensure modularity and open architecture?
=== Watch Out For (Bad) ===
'''' Can you provide examples of how the system can be easily modified or upgraded?
'''Proprietary Systems''': Buzzwords indicating a lack of flexibility and potential vendor lock-in. 
'' What are the specific capabilities and limitations of the system in terms of auto-frequency switching and hardened GPS-Rx?
'''With enough Time and Resources we can do xyz''': Anyone could and does say this and is a pretty easy cop out to detect. 
'' Is the system day/night capable, and can you provide details on its performance in various lighting conditions?
'''Unjammable UAS''': Any company claiming their UAS is unjammable. 
'' Does the system support swappable communication modules?
'''Future Features''': Phrases like “''*'' feature to be implemented Q4”. 
*'' Can you demonstrate the process of swapping out comms?
'''Firm Fixed Cost Plus''': Potential hidden costs. 
'' What operating system and backend does the system use?
'''Special Price''': “My friend, special price for you my friend.” 
*'' Is it non-proprietary, and how easily can it be integrated with other systems?
'''EW-proof''': Claims of being electronic warfare-proof without evidence. 
'' Is the imaging system shutterless, and how does this benefit continuous image capture?
'''Tested in Battlefield Conditions of Kyiv, Ukraine''': Kyiv is like bragging about being at KAIA or Bagram or Erbil, not necessarily indicative of quality.
'' Is the system built-for-purpose, or is it designed to be a general-purpose solution?
* “An island in the pacific.” Which island? Here’s a pen. Touch the map. Draw an icon. Now tell me what USCT will say. 
'''' Can you provide case studies where the system was used 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 are the security measures in place to protect the system from electronic warfare (EW) threats?
'''' How has the system been tested against EW threats?
'' Can you provide real-world examples or case studies of the system’s performance in challenging environments, such as adverse weather conditions?
'' What are the total costs associated with the system, including hidden costs?
'''' Are there any firm fixed cost plus arrangements?
'' What is the expected lifespan of the system, and what are the maintenance requirements over its lifespan?
'' What kind of support and service do you offer post-purchase?
'''' Can you provide details on your customer support and service level agreements (SLAs)?
'' Have any of your systems been tested in battlefield conditions?
*'' If so, can you provide specific locations and details on the testing environment?
'' How does this system work in the total absence of links to SVs - no GNSS, no Starlink, etc?
*'' What is the CE90 of this system, under such conditions?
'' What does end-game look like for this system? How does it guide to target?
'' (PACOM specific use cases) Explain the concept of employment.
''' Emphasis on survival v. known threats and geopolitical realities of whatever land is involved in the CONEMP.
''''' What agreements do we currently have with that country?
**'' What have they said about their willingness to allow us to use their land in use cases that don’t directly involve their own territorial integrity?


<span id="actions-for-technical-section-or-consultant-to-validate-suas-claims"></span>
== Questions Leaders Should Be Asking ==
=== Actions for Technical Section or Consultant to Validate SUAS Claims ===
# 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?
# Is the system day/night capable, and can you provide details on its performance in various lighting conditions?
# Does the system support swappable communication modules?
# Can you demonstrate the process of swapping out comms?
# 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 built-for-purpose, or is it designed to be a general-purpose solution?
# Can you provide case studies where the system was used 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 are the security measures in place to protect the system from electronic warfare (EW) threats?
# How has the system been tested against EW threats?
# Can you provide real-world examples or case studies of the system’s performance in challenging environments, such as adverse weather conditions?
# What are the total costs associated with the system, including hidden costs?
# Are there any firm fixed cost plus arrangements?
# What is the expected lifespan of the system, and what are the maintenance requirements over its lifespan?
# What kind of support and service do you offer post-purchase?
# Can you provide details on your customer support and service level agreements (SLAs)?
# Have any of your systems been tested in battlefield conditions?
# If so, can you provide specific locations and details on the testing environment?
# How does this system work in the total absence of links to SVs - no GNSS, no Starlink, etc?
# What is the CE90 of this system, under such conditions?
# What does end-game look like for this system? How does it guide to target?
# (PACOM specific use cases) Explain the concept of employment.
# Emphasis on survival v. known threats and geopolitical realities of whatever land is involved in the CONEMP.
# What agreements do we currently have with that country?
# What have they said about their willingness to allow us to use their land in use cases that don’t directly involve their own territorial integrity?


'' '''EW Testing''': Bring in EW aggressors to attempt to break the system. Use basic TTPs found in Ukraine and see if the system passes.
== Actions for Technical Section or Consultant to Validate SUAS Claims ==
'' '''Field Testing''': Test the system in real-world conditions, including challenging environments and battlefield conditions, to ensure reliability and performance.
* '''EW Testing''': Bring in EW aggressors to attempt to break the system. Use basic TTPs found in Ukraine and see if the system passes.
'' '''Hardware and Software Validation''': Ensure the system’s hardware and software are as barebones as possible to reduce failure points. Verify the claimed functionalities, such as GPS hardening and auto-frequency switching.
* '''Field Testing''': Test the system in real-world conditions, including challenging environments and battlefield conditions, to ensure reliability and performance.
'' '''Signal Resilience''': Test the system’s ability to operate without GPS and in the presence of signal jamming and spoofing.
* '''Hardware and Software Validation''': Ensure the system’s hardware and software are as barebones as possible to reduce failure points. Verify the claimed functionalities, such as GPS hardening and auto-frequency switching.
'' '''Maintenance and Repair''': Validate that maintenance and repair can be performed in-house and are not overly reliant on vendor-specific services.
* '''Signal Resilience''': Test the system’s ability to operate without GPS and in the presence of signal jamming and spoofing.
'' '''Cost Analysis''': Conduct a thorough cost analysis to uncover any hidden costs and verify the total cost of ownership, including maintenance and upgrades.
* '''Maintenance and Repair''': Validate that maintenance and repair can be performed in-house and are not overly reliant on vendor-specific services.
'' '''Integration Testing''': Test the integration of the system with existing technology and workflows to ensure compatibility and ease of use.
* '''Cost Analysis''': Conduct a thorough cost analysis to uncover any hidden costs and verify the total cost of ownership, including maintenance and upgrades.
'' '''Performance Metrics''': Establish and measure key performance metrics, such as CE90, to validate the system’s accuracy and effectiveness in various conditions.
* '''Integration Testing''': Test the integration of the system with existing technology and workflows to ensure compatibility and ease of use.
* '''Performance Metrics''': Establish and measure key performance metrics, such as CE90, to validate the system’s accuracy and effectiveness in various conditions.


<span id="telltale-signs-leaders-should-be-aware-of"></span>
== Telltale Signs Leaders Should Be Aware Of ==
=== Telltale Signs Leaders Should Be Aware Of ===
'''Modularity and Open Architecture''':
* Commercial UUVs might have stringent vendor-dependent maintenance requirements, such as a $30,000 fix for overturning a screw, which can result in 6 weeks of downtime.
* Similar to the “John Deere problem,” where maintenance and part replacements are highly controlled by the vendor.
* Around 60% of the parts in expendable UUV electronics are sourced from the air market to allow resourcing and repurposing from the air wing depot.
* Lack of knowledge or focus on robotics/theory by company leadership, instead emphasizing product and marketing.
* High turnover of solid engineers, often due to leadership losing focus on the product.
'''Actionable Insight''': Consider hiring an OSINT professional to investigate why ex-employees left the company. Even with potential negativity bias, this can provide significant insights into the company’s problems.
* Potential impacts of regulatory changes, such as the upcoming FTC non-compete dismissal, which might reveal underlying issues within companies.
'''Red Flags''':
* No mention of how the system will prevail against EW. Reliance on having a signal in an unknown/future environment.
* Anything in a tube: Expensive and can’t be easily modified, leading to an inability to adapt post-manufacture.
* Testing environments where failure is bad for someone’s career: If designed to look good or demonstrate readiness, it’s a bad sign. If nobody invites EMS aggressors to try and stop it, it’s a bad sign. If there’s a grandstand with FOGOs watching, that’s a demonstration - not a test.


'' '''Modularity and Open Architecture''':
[[Category:Unmanned Systems]]
''' Commercial UUVs might have stringent vendor-dependent maintenance requirements, such as a $30,000 fix for overturning a screw, which can result in 6 weeks of downtime.
''' Similar to the “John Deere problem,” where maintenance and part replacements are highly controlled by the vendor.
*'' Around 60% of the parts in expendable UUV electronics are sourced from the air market to allow resourcing and repurposing from the air wing depot.
'' Lack of knowledge or focus on robotics/theory by company leadership, instead emphasizing product and marketing.
'' High turnover of solid engineers, often due to leadership losing focus on the product.
'''' '''Actionable Insight''': Consider hiring an OSINT professional to investigate why ex-employees left the company. Even with potential negativity bias, this can provide significant insights into the company’s problems.
'' Potential impacts of regulatory changes, such as the upcoming FTC non-compete dismissal, which might reveal underlying issues within companies.
'' '''Red Flags''':
''' No mention of how the system will prevail against EW. Reliance on having a signal in an unknown/future environment.
''' Anything in a tube: Expensive and can’t be easily modified, leading to an inability to adapt post-manufacture.
''* Testing environments where failure is bad for someone’s career: If designed to look good or demonstrate readiness, it’s a bad sign. If nobody invites EMS aggressors to try and stop it, it’s a bad sign. If there’s a grandstand with FOGOs watching, that’s a demonstration - not a test.
Retrieved from "https://irregularpedia.org/index.php/Guide_to_Unmanned_Systems"