Model Request and Proposal for small UAS development

ASCI 530 – Unmanned Aerospace Systems
Systems Development and Test & Evaluation (T&E)
Activity 7.4 – Assignment: Request for Proposal
John Van Geem

Mission Overview
Develop a hand launched, small UAS, which may use used to identify and geolocate victims involved in flooding or equally un-traversable terrain due to natural disasters. UAS must be able to be transported in the bed of a standard pick-up truck, and launched by a single individual.  Conceptual Design, Research, and Detailed designs should take more than five years. Another five years may be allocated to build the prototype, modify and implement all developments, and obtain a certification from the Regulatory Authority. 

1.   Transportability - Entire system should be able to fit in the back of one standard civilian pick up truck. 
1.1.  The Control station and Air Vehicle Element may transported in two separate cases
1.2.  The control station case must not exceed 50 abs
1.3.  The Air Vehicle Element case must not exceed 100 lbs.
1.4.  Any case with the weight of over 30 lbs must have built in wheels to assist in transportation.
1.4.  Air Vehicle Element case must house everything needed to achieve air operability.
1.5.  Cases must be durable and tough to take impacts without damaging equipment. 
1.6.  Cases also must be shock resistant to any outside electrical charge

2. Data-link requirements
2.1.  UAS should have communications operability in all standard United States emergency frequency radio bands
2.2.  UAS should be able to link with Standard U.S. telecommunications networks
2.2.1. To include command and control information being set over 3G and 4G data networks
2.2.2.  Once line-of-site is broken, UAS should be made to operate through telecommunication networks.
2.3.  UAS should be able to scan an area and determine what electrical bandwidths are being used in the area
2.4. Line-of-site communication should be made to last at least two miles under clear conditions. 
2.5. All communication power should be supplied via on platform battery, powered before launch.
2.6.  Data links must be protected again intentional and unintentional EM threats.
2.6.1 This includes an encryption capability on C2 control for uplink and downlink
2.7.  Research with the Federal Communications Commission will be done to determine the best purchase of bandwidth for communication use.

3. Command and Control must be operable from a single laptop and EM amplifier.
3.1.  C2 system must have a user friendly GUI to simplicity of use.
3.2.   C2 must be configurable to support multiple versions of UAS platforms.
3.3.  Must have a diagnostic capability for maintenance
3.4.  Must be Ergonomically designed to assist C2 operator in harsh environments.
3.5.  Must be waterproof to operate in the rain.
3.6.  Must be have sufficient backlighting to be seen on bright days. 

Testing Requirements
  1. Testing for Transportability
1.1. Weight tests will be conducted with all equipment.
2.2. Containers with systems will be drop tested to insure durability of mission systems
2.3. Single operator performance test will be conducted.
2.3.1.  a solo operator must be able to set up the equipment alone
2.3.2.  a solo operator must be able to launch the Airborne Element alone.
2.3.2.  a solo operator music be able to dismantle shut down and pack up everything alone.
2.  Testing of Data Link communication structors
2.1.  Radio communication bands must be tested with real relays and networks
2.2.  Data links will be tested against intentional and unintentional threats
2.2.1 This includes, malicious interference, jamming, and deceptive control

 2.3.  Encoding themes will be tested to insure the operability of relay links
2.4.  Distance of the data-links will be tested and ensured to reach minimum distance.

2.5.  Latency and control abilities will be tested for smooth operability of the platform. 

3. Testing for Command and Control Systems 
3.1.  Test must be conducted to within C2 interface to ensure the proper flow of data
3.2.  Maximum and minimum Voltage and amps test for system crash or failure.
3.3.  If third party interfaces are used, test will be conducted to ensure the proper messing of all software capabilities.
3.4.  C2 interface will be tested for the upload of multiple mission plans, and data sets.

       New UAS will go through the 10 phase development process. Concept Design, Research, Preliminary Design, and Detailed Design, will exceed no longer than five years in duration. At which time, a test specimen and prototype will be created an tested to determine the validity of all UAS specifics. Prototype and Development phases will last no longer than five years, culminating with the certification of the small UAS with the Regulatory Agency. Upon certification, steady production and support will continue until product is no longer in service. 
Rational


      The purpose of designing such a UAS as detailed in the requirements above is to bring a sensory operation capability to a single persons, whom is trying to reach out to the victims of a natural disaster. In early stages of disaster, it is impassive to find the people who need medical attention, or who are still in harms way, as fast as possible. The best opportunity for those people to get help, are from people just outside the impact zone of the natural disaster. It is our hope that singular person UAS capability can then help jump start the process to early relief for any victim of a natural disaster. 

Comments

Post a Comment

Popular posts from this blog

UAS in the National Airspace System ASCI 530  John Van Geem April 14, 2017 The Traffic Collision Avoidance System (TCAS) is a common collision avoidance detection system used by aircraft within the National Airspace System (NAS). TCAS can give an early alert or warning if two aerospace platforms are on imminent trajectory for mid-air crash or collision. In order for a airframe to use TCAS, it has to be fitted with a transponder that emits a specific frequency for detection amongst other TCAS systems. However, TCAS is only a requirement on aircraft with a weight of over 12,600 lbs or above (FAA, 2009). According to the Department of Defense UAS Groups, which designates they type of UAS according to size and operating altitude capabilities, only groups 4 and 5 could even be close to TCAS standards, though Group 3 is able to reach altitudes just under flight level 180.  Examples of the types of UAS in group 3 are the RQ-7B Shadow, RQ-21 Blackjack, and ...
Read more
Scenario: Two subsystems – 1) Guidance, Navigation & Control [flying correctly] and 2) Payload delivery [spraying correctly] have attempted to save costs by purchasing off-the-shelf hardware, rather than a custom design, resulting in both going over their originally allotted weight budgets. Each team has suggested that the OTHER team reduce weight to compensate. The UAS will not be able to carry sufficient weight to spread the specified (Marketing has already talked this up to customers) amount of fertilizer over the specified area without cutting into the fuel margin. The safety engineers are uncomfortable with the idea of changing the fuel margin at all. How would you go about fixing the problem? Solution: Both the Guidance, Navigation, Control team, and Payload delivery team need to draft up a new proposal on how much it would cost if they built their own units in house. Within the proposals I would have them provide options for construction outlines for the lightest po...
Read more