红领巾瓜报

Judges from a variety of organizations, including Lockheed Martin, will play a critical role in the competition. Competition participation will be virtual. 

Unique methods of illustrating your solution may be appropriate and are allowed. For example, physical demonstrations and simulations could be very effective. However, be extremely careful to stay within the competition time and virtual presentation format (Zoom) limits.

Short videos and references* on 鈥�design thinking鈥� and how to do effective 鈥�elevator pitches,鈥� to help participants prepare before the competition starts, are available in the following links:

"Crash Course in Pitching" - 

"Design Thinking Part 1" - 

"Design Thinking Part 2" - 

"Design Thinking Part 3" - 

"Design Thinking Part 4" - 

The following documents* will also prove useful:

Basic_Pitch_Rules.PDF           
A_Crash_Course_in_Design_Thinking.PDF

(*Special thanks to Maggie Koops, a WSU alum, for her efforts preparing this material.)

- A helpful breakdown of what an elevator speech is and the elements that go into it. While teams will not be presenting research during this competition, the ability to convey an idea in a succinct manner is critical.

Judges score teams, as the competition progresses, based on the below noted specific categories:

1. The team鈥檚 problem understanding
2. The team鈥檚 solution uniqueness
3. The demonstrated value of the team鈥檚 solution
4. The practicality of the team鈥檚 solution
5. The team鈥檚 overall effectiveness communicating
   
   (*Note: Not all categories will be active in all sessions.)

Scores use the following scale:

• 0-points means the specific category result is missing or unacceptable
• 2-points means the specific category result is just acceptable or adequate
• 4-points means the specific category result is very good
• 6-points means the specific category result is truly extraordinary

Point values other than 0, 2, 4, or 6 are not allowed.

The category scores from the judges are averaged and used in the following equation to determine a team鈥檚 session score:

Session Score* = Average of Category 1 Scores + Average of Category 2 Scores + Average of Category 3 Scores + Average Category 4 Scores

(*Note: Not all categories will be active in all sessions.)

In order to provide valuable feedback, session category average scores will be shared with teams as soon as is possible.

Session scores combine to determine a team鈥檚 final competition score using the following equation:

Final Score = (0.1 * Session 1 Score) + (0.2 * Session 2 Score) + (0.7 * Session 3 Score)

 

Each session will progressively address different parts of a team鈥檚 efforts and results, specifically:

• Session 1 is where the team identifies a problem as they see it and their specific focus area
• Session 2 is where the team presents their initial idea for a solution to the problem
• Session 3 is where the team presents their evolved and final overall result

The following competition rules apply: 

1. Contest participants must compete as a team, composed of at least three and no more than four full-time WSU students (for this competition, full-time student status means each undergraduate or graduate student is currently enrolled, respectively, in at least 12 or 6 credit hours). 
2. Multi-disciplinary teams are encouraged but at least one member must be a current engineering major. Due to the nature of the competition theme, it would be in the best interests of the teams to have atleast one member from School of Computing.
3. A maximum of twelve teams can compete. As a result, a pre-contest entry and review process will be used to invite the most promising teams to participate. 
4. Participants will interact virtually. Zoom will be the primary communications tool. 
5. Each team member is required to present at least once during the event. 
6. Contest events, activities, presentations, etc. will be tightly scheduled and time-limited. Competitors must meet these limits. There will be no exceptions, unless in rare and unavoidable cases (e.g., WSU ITS services go down). 
7. The principal competition efforts and results must be those of the student team. Outside assistance of any kind or amount must be formally and completely identified in a submitted List of References. 
8. Proper referencing of any and all sources or assistance (e.g., periodicals, conference papers, books, web pages, conversations, emails, etc.) is required. 
9. Failure to submit a complete List of References by the stated deadline may result in disqualification. 
10. Be sure to monitor the competition web page and your emails for updates, changes, and other information. 
11. It is the team鈥檚 responsibility to check the schedule and to be on time for their presentation in each session. 
12. Teams that are late for a presentation time slot will not be given additional time, but are eligible for scoring. 
13. Teams totally missing a presentation time slot receive a zero for that session score. 
14. The is no automatic requirement to award a first, second, or third place winner (e.g., if there were only three competitors). Winning teams must deliver high-quality and innovative solutions with acceptable final team scores. There are no default wins. 
15. Generalized unofficial results, if available, may be shared during the Closing Session. Final results will be posted on the web page as soon as they are made official. 
16. All competition related aspects (e.g., rules, requirements, constraints, schedules, awards, etc.) are subject to interpretation and change at any time by the contest director (Dr. Keshavanarayana, WSU Aerospace). 

OPENING SESSION 鈥� Friday, 11/8 @ 4:00pm Central

SESSION 1 鈥� Saturday, 11/9 (all times are Central)
This session focuses on the team鈥檚 identification of a problem and their specific focus area.

Team/Time	10:00am	10:15am	10:30am	10:45am	11:00am	11:15am	11:30am	11:45am	12:00pm
1	X
2		X
3			X
4				X
5					X
6						X
7							X
8								X
9									X

 SESSION 2 鈥� Saturday, 11/9 (all times are Central)
This session focuses on the team鈥檚 initial idea for a solution to the problem.

Team/Time	4:00pm	4:15pm	4:30pm	4:45pm	5:00pm	5:15pm	5:30pm	5:45pm	6:00pm
1	X
2		X
3			X
4				X
5					X
6						X
7							X
8								X
9									X

SESSION 3 鈥� Sunday, 11/10 (all times are Central)
This session focuses on the team鈥檚 final overall result.

Team/Time	2:00pm	2:15pm	2:30pm	2:45pm	3:00pm	3:15pm	3:30 pm	3:45 pm	4:00 pm
1									X
2								X
3							X
4						X
5					X
6				X
7			X
8		X
9	X

CLOSING SESSION 鈥� Sunday, 11/10, @ 5:00pm Central

Opening Session Link: e-mailed to registered participants

Session 1 Zoom Link (Saturday): e-mailed to registered participants

Session 2 Zoom Link (Saturday): e-mailed to registered participants

Session 3 Zoom Link (Sunday): e-mailed to registered participants

Closing Session Zoom Link(Sunday): e-mailed to registered participants

As seen in the recent war in Ukraine and in the middle-east conflicts, Unmanned Aerial Systems (UAS), also referred to as drones, are changing the way we approach defense. Low cost, often innovative yet crude autonomous or semi-autonomous UAS create confusion and place soldiers and civilians at risk. Counter-UAS is a field that tries to prevent these drones from completing their mission. UAS can be countered through multiple mechanisms (kinetic / non-kinetic / cyber) across multiple phases of operation (takeoff / cruise / loiter / attack).

Your challenge is to learn as much about UAS systems that can threaten people on the ground. Then, propose a Counter-UAS solution that addresses multiple UAS types (size, speed, altitude, etc.), affordability, flexibility and resiliency.

Cyber Physical Systems for Aviation

The recent technological advances in Cyber Physical Systems (CPS) are opening new frontiers in a wide range of applications. Leveraging the capabilities of CPS  might be beneficial to aviation applications including civilian, combat, and reconnaissance.

Your challenge is to, first, learn as much as you can about Cyber Physical Systems and their usage for one specific aviation area.  Then you need to identify a new and innovative idea or concept to advance your choice of aviation area involving Cyber Physical Systems

Acoustic detection of UAS

(Team 6) Rylan Fay, Spencer Hermann, Edwin Ordonez

Session 1 :

Session 2:

Session 3 :

 HIVE

(Team 2) Dhruv Roy, Manuel Salamanca, Caleb Perkins, Isai Waboshi

Session 1:

Session 2:

Session 3:

Counter UAS using high power microwaves

(Team 1) Osakuade Emmanuel, Boluwatito Adesina, Erondu Chimdi, Amiegbebhor-Onikolase Joshua

Session 1:

Session 2:

Session 3: