Home / News and Events / sUAS Innovation Challenge / sUAS Innovation Challenge Preliminary Design Review

sUAS Innovation Challenge Preliminary Design Review

Purpose: The purpose of the Preliminary Design Review is to review the design outlined in the proposal, how it will function, and the team’s technical approach to develop the design.

Goal: The PDR is an opportunity for the Review Committee to provide teams with perspective based feedback on their system and potential risks prior to starting a more detailed design phase.

Attendance: All teams shall take part in the design reviews though not all team members have to be present. Team members that are taking part in the PDR should well versed in the project and able to answer review committee questions. Teams only have to attend their selected briefing slot.

Pre-reviews: Pre-reviews with the ASURE team can be requested prior to the 28th of November. Don’t wait till the last minute.

Briefing Date: November 29, 2017

Briefing Location: Fulton Center (Tempe Campus) Wilson Conference Room, 6th Floor.

Presentations Due: Presentations are due via email in Power point or PDF format NLT 28 Nov 2017. Your presentation will be posted to the display system in the briefing room. Name the file “Your Teams Name PDR”. Please email your presentations to ASUREBD@asu.edu.

Preliminary Design Review Presentation Structure:

Presentations should be clear and concise. Teams will only have 15 minutes to present their materials followed by 10 minutes for questions.

There is no set format or template for the briefing, we recommend the following structure.

Team Summary

  • Team name
  • Team members and role.

System and Key Capability overview, potential topics include (note, team’s key topics should be addressed):

  • Brief description of system, focusing on the key capability
  • Concept of Operation or key use case
  • Needs statements

Status of the Design, potential topics include (note, team’s key topics should be addressed):

  • Analysis (or similar) that demonstrated key capability meets the teams design goals
  • What key components are being designed, modified, or procured
  • Software plan (if developing software), what will be developed and how it will be tested
  • Provide evidence (estimates or similar) of the performance of key components to support system capabilities

Development Plans, potential topics include (note, team’s key topics should be addressed):

  • How the team plans to implement the design and what metrics are tracked
  • Development schedule, key internal milestones
  • Identify major problems or risks, and describe how you plan to deal with them

Other topics, other things you want to inform the review committee with respect to your design

Presentation Considerations. Additional topics should enhance one of the three areas above:

  • Practice the presentation and do not read the power point slides
  • You only have ten minutes, focus on key topics
  • Listen to questions, answer directly and professionally
  • Maintain a professional demeanor
  • Recommended dress is business casual
  • The proposal is the baseline design description document, changes from the proposal should be clearly defined
  • Graphics should have suitable explanations
  • Units of Measure are correct and consistent
  • All graphics and videos should be embedded in presentation
  • Arrive ten minutes early

Scheduling: Teams are responsible for scheduling the specific time for their review. The scheduling portal will be open and active on the 13th of November. The following schedule indicates the available briefing time slots. Scheduling is on a first come first select basis.

Schedule your briefing time here

Start Time

End Time

Briefing Slot


































Post Review: During the review you will receive feedback from the Review Committee. ASURE will provide this information to the team leads by 1 Dec 2017. The feedback is experienced based recommendations for teams to evaluate or consider as it relates to their system. Items indicated as “safety” related shall be resolved in coordination with Jon Klane.