...
Design Paper | Score | Notes |
---|
Days Late | -10% per day | Applicable after 1700 EST Jan 16, 2021 |
Overall Presentation | Weight: 15 | Checklist | Notes |
Grammar/Spelling | | | |
Structure/Organization | | - follows structure of CONOPS
| |
Use of Figures/Charts/Tables | | | |
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 Power Distribution - Kevin Flight Controller - Sahil, Kiran, Daniel
| - 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 What options exist between custom hardware and replaceable commercial products (to add, what are tradeoffs in available features and functionalities)
|
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”
| |
Pick-Up/ Drop-Off Methodology | | - 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 BVLOS: | - should mention pilot in the case of an emergency
- outline strategy SPECIFIC TO TASKS
- include a diagram
| |
Noise Signature | | | |
Safety | | - 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. | |
System Level Testing | | - 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
| |
Technical Innovation and Novelty | Weight: 10 | Checklist | Be Sure To Include: |
Novel Approach to Mission Requirements | | | |
Novel Elements | | | |
Safety and Risk Management | Weight:15 | Be Sure To Include |
System Level Safety Issues | *will go under ‘Safety’ later | |
Single Point Failure Modes | *will go under 'Safety' later | |
Risk Management Plan | | Risk categories should include technical, programmatic, budget, and/or others. Risk planning must include: Identification of the risk; Likelihood that the risk will happen; Impact on the project if the risk occurs; and Measures you will take to reduce the likelihood of the risk and to mitigate its effects if it does happen.
|
Project Management | Weight: 10 | Checklist | Be Sure To Include: |
---|
Milestones | | | |
Schedule for Design/Construction/Testing Phases | | - Gantt chart (easy to read)
| |
Budget | | | |
NOTE: Papers are limited to 15 pages total, including appendices, title page, table of contents, list of figures, etc. Pages above the 15-page limit will be ignored in the scoring
...