Comp Strategy Meeting 1 Template

The below is a copy of the template that is tentatively planned to be used for the first comp strategy meeting. For then real thing, we will be using google docs or possibly copies of this confluence page being filled in by leads.

Introduction

This document is meant as a template to guide the discussion in a way that has been agreed upon by team leads and system integration. Ideally this can be done only by filling in the provided text boxes.

For this meeting, we are not talking about specific designs (fixed wing, quadcopter, blimp, VTOL, etc.). The point of this meeting is to identify what possible tasks exist and which ones we want to tackle.

We have split into smaller groups for a reason, the hope here is that everyone gets to voice their thoughts in a less intimidating environment than a lecture hall full of 100 people. Unless someone is derailing the discussion, we want all voices to be heard, this is how you get a wide variety of creative ideas!

The assumption for this activity is that everyone involved has a working understanding of the conops and has either read it or went to SysInt’s presentation. If you haven’t, please take the time to read them, then join the group discussion when you are done.

Rule Clarifications (~10 mins)

This section is for group members to fill in conops questions that they still have after having read them or watched Aidan’s presentation. If group members can answer them, that’s great. If not, please write them down and bring them up with the group later.

Scoring Actions and Drone Capabilities (~25 mins)

This section is for identifying all the ways that our drone can score points and the different drone capabilities that would enable us to do it. We want to identify everything that could possibly be done so we have an all-encompassing list of drone capabilities.

The above sections should take 30-45 minutes, the exact time will be decided fluidly on the day.

After this section is completed by each group, the team will convene and each group leader will briefly present what they have come up with so far.

What should WARG do? (~30 mins)

The reality of working on student design teams is that you can’t always do everything to the highest level possible. Whether the limitation is budget, time, skill, or anything else. Are there any tasks that we don’t have the resources to do or that we want to push to the back burner to ensure we have crucial baseline functionality? Break all the drone capabilities into the categories below.

After all the above section is complete groups will all come together and present their ideas (~30 mins).