2021-2022 Technical Report Requirements

Days Late

-10% per day

Applicable after 1700 EST Jan 16, 2021

Overall Presentation

Weight: 15

Notes

Grammar/Spelling

Structure/Organization

• follows structure of CONOPS

• Make sure the reader is presented with a clear story of what your system will do and how it will meet the competition requirements. Organize the paper according to the evaluation criteria

Use of Figures/Charts/Tables

• have appropriate titles and labels

• referenced from the text so reader know’s what it’s trying to show

References Provided/Correct

• includes AT LEAST 5 references other than CONOPS

Technical Description of Unmanned System

Weight: 50

Checklist:

Be Sure To Include:

Analysis of Alternate Solutions

• Frame - Brielle, Cindy, Megan

• Shrinjay

• description of alternate solutions
• decision on solution
• diagram
• how solution is relevant to problem space
• in-depth analysis

• other ways the problem was approached

• why we chose this solution

Features and Capabilities

• Zeropilot - Dhruv

• Computer Vision Architecture: Object detection - Ray

• Computer Vision Architecture: Processing and Interfacing - Shrinjay, Ray

• Camera Gimbal - Steven, Josh

• all features addressed (try to have them addressed in sequential order with reference to a diagram)
• diagram
• relevance to problem space
• refer to “updated feedback“ for “features and capabilities”

• what makes this design special

Pick-Up/ Drop-Off Methodology

• Grabber (Cindy, Kayla, Matthew)

• outline how QR codes will be read
• discuss grabber
• does the aircraft land? does it rely on Yolov5? How does it land? or Hover?

• what features this system has to allow for pickup and drop off of a range of design shapes

• how this process occur gently, accurately and at a distance

Automation

Comms & Control : Aaditya, Kaveet, Anthony, Dhruv

• Telemetry Architecture

• Inter thread communication on Autopilot

• Video streaming

BVLOS:

• Automated Takeoff and Landing

• Autonomous Identification of humans (Ray)

• should mention pilot in the case of an emergency
• outline strategy SPECIFIC TO TASKS
• include a diagram

• how we meet the requirement for automated launch/flight to the intruders

Noise Signature

• Sahil, Brielle

• what UAV and/or navigational strategies are we using to minimize noise?

Safety

• Sahil

• Consider case of comms failure
• Consider cases for system operating near the ground (should address nearby PEOPLE and objects…)

*both technical and physics safety issues should be addressed, the above considerations are just those forgotten on last years report, not all the cases.

• How we intend to avoid colliding with things

• Any other safety systems implemented

System Level Testing

• Flight tests - Sahil

• Firmware Tests (Dhruv)

• Risk Matrix
• Explanation of tests during development
• Explanation of tests during testing phase
• Ensure ALL relevant system level tests are covered and spoken about IN DEPTH

• testing process implemented during development and in preparation for practice flights and scenarios

Technical Innovation and Novelty

Weight: 10

Checklist

Be Sure To Include:

Novel Approach to Mission Requirements

• CV - Shrinjay

• How overall and individual strategy for completing tasks is novel. (NOT talking about technologies required - that’s something else)

• detailed explanation

Novel Elements

• CV - Shrinjay

• Novel technology systems in the overall system. (What does our UAS have that make sit novel in the execution of the Tasks)

Safety and Risk Management

Weight:15

Be Sure To Include

System Level Safety Issues

*will go under ‘Safety’ later

• What safety issues are important

• How we are addressing them

Single Point Failure Modes

*will go under 'Safety' later

• What failure modes we anticipate

• How we are addressing them

Risk Management Plan

• delegated across leads

• What risks exist that may affect ability to successfully compete in Southport

• How we are addressing these risks

1. Risk categories should include technical, programmatic, budget, and/or others. Risk planning must include:

   1. Identification of the risk;

   2. Likelihood that the risk will happen;

   3. Impact on the project if the risk occurs; and

   4. Measures you will take to reduce the likelihood of the risk and to mitigate its effects if it does happen.

Milestones

• Key events in the project that signal things are progressing as planned

Schedule for Design/Construction/Testing Phases

• Gantt chart (easy to read)

• Gantt chart of all significant activities in the development of the system and planning for the event

Budget

• Cost of ‘stuff’ for the system (don’t forget to include travel and other things)

• reasonable prices (not TOO high but also not excessively low)