Reformatted Feedback

 

Report Section

Feedback

What to do:

Report Section

Feedback

What to do:

Structure/Organization

Formatting

  • No section was made for Technical Description and Novelty (some sections missing)

FOLLOW CONOPS suggested format

  • No acronyms section and page 9 wrong figure used

include acronyms section (are we allowed an appendix?)

  • formatting could be better

 

  • some labels on wrong page. Figure 3.2 flowchart has 2 yes’s from one box. Some figure hard to read

pay attention to figures in editing process!

  • limited number of figures/charts/tables

be sure to include a lot of diagrams…

References

  • only one besides conops

LIST MORE REFERENCES

Grammar

  • A few mistakes or awkward wordings but nothing major

grammarly.

System Level Testing

 

  • More details required - risk matrix, expanded deliverables on testing each phase i.e. ID of package & transport

include risk matrix

  • limited system tests implemented in development process

talk about general tests during dev process

  • As above, they identified high level firmware testing, and that some flight testing will be done. Not  a lot of details here

have each subteam lead talk about their respective testing processes

Novel Approach to mission requirements

 

  • Included at the beginning but not detailed

HIGHLIGHT NOVEL APPROACH

  • seems like an interesting approach, doesn't explicitly highlight anything novel

  • section missing, some points awarded for use of fixed-wing to prioritize range and endurance

 

  • Not specifically addressed. Comms could be the strength on this team and custom controller

Pretty much, just brag about everything we think is novel or really just cool about the system.

  • All in one system is interesting, rather than having a separate ground vehicle

 

Description of system level safety issues

 

  • More details required

 

  • named 2 but with minimal detail

 

  • Two IDd, only one described limited. No personnel, response to crashes. ecy

Be sure to mention safety of PEOPLE et cetera within certain situations, not just technical ones.

  • Provided some info but not many details on mitigations other than what they do when it happens. No mention of COVID safety

Identification of single point failure modes

 

  • More details required (too short)

  • limited analysis. of SPFMs (single point failure modes)

Figure out all possibilities for SPFM and talk about them. IN DEPTH.

  • Only comms link failures, limited details

  • Not specifically addressed, expect these will become prevalent as testing begins

  • They identified some areas, but didn't give many details on how they would prevent them. More operational risks.

List of milestones

 

  • Not detailed, not long enough

 

Schedule

 

  • Diagram not clear

  • can’t tell what the Gantt says but it looks pretty basic

Make sure chart is readable..

  • no discussion of schedule

  • text unreadable

Project Budget

 

  • Underestimated for something that can lift 10 kg payload

Be realistic!! They don’t care too much about having a low budget… apparently.

  • extremely limited, sparse

  • Not sure this is realistic - $500 for entire system, no cost on gimbal, dropper, neural training etc

Alternate Solutions

 

  • does discuss alternate solutions, but it’s pretty basic

 

  • not clear on decision of solution

 

  • Heavy focus on comms and very limited on aircraft. No diagram dimensions - will it fit in the tent? Package mechanism not compared

Be sure to consider more REASONS as to why a particular solution was chosen

  • They provided different options and a very basic analysis

 

Features & Capabilities

 

  • talk about some aspect and why they chose them, but seems like that can’t be everything

  • lacking in detail about UAV airframe and ground station

leads should all contribute. The features and capabilities should flow through each subteam so that the judges get the bigger picture.

  • Details of autopilot - but it’s just an autopilot. Own gimbal design at high level, but why?

 

  • Comms addressed. Package logistics not addressed to enough detail. Noted they will deliver 3 packages instead of 4

 

  • They really only talk to the computer vision system, nothing on the aircraft itself. Seems like the A/C is a bed for their novel software

 

Communications and Control

 

  • missing team communication

  • some c2 links not identified(FPV?). No mention of checklists/team comms.

  • high level explanation of telemetry and comms, nothing unique

  • 900 MHz link, but not clear if that is used for telemtery and video and manual control or how it is being implemented

INCLUDE TEAM COMMUNICATION

BVLOS Strategy

  • missing team communication

  • does not address long-range communication concerns.

 

  • Auto guidance, little details

 

  • No ADSB reference in BVLOS

 

  • Resonably detailed on how the autopilot is integrated with the various sensors, but only really focuses on the CV and not much else

 

Pickup/Drop-off Methodology

 

  • needs more detail

  • Does not outline how QR codes will be read

 

  • FW will fly, but will it deliver a package? Will it fit in a tent? Relying on CV -Yolo, no mention of reading QR codes

 

  • Figure is nice and seems like a nice simple solution, but lacking detail

 

Navigation Strategy

 

  • needs diagram

Include Diagram

  • does not outline navigation strategy specific to tasks

Discuss how specific to task

  • Auto by waypoints, limited details, nothing new

Highlight novelty.

  • no mention of pilot in emergency. BVLOS flight will be strong for this team w/o packaged delivered

mention pilot in emergency

  • Standard waypoint following, via GPS, but no mention of how it works (I assume it's just through their Flight Management Software) or other details

Explain how the system works. IN DEPTH.

Safety

 

  • nothing about safety at the depot/clinics

Just … write more about safety. Consider more cases where safety need to be talked about.

  • Safety considerations for operating near ground personnel not addressed (not addressing people/clinics)

  • Limited comms failure info

  • Is there an 'overconfidence' around comms system, lacking attention to safety?

  • I would have wanted to see a lot more here. They identified some very high level issues, but no details

Project Risk Mitigation Plan

 

  • only 3 risks

  • three tech and programmatic risks, limited details

Consider risks and mitigation plan over all subteams.

  • If comms and effective BVLOS is goal then those risks seem prepared, activity, people, tents needs attention

Â