Design Reviews�“30 minute mentoring sessions”��Agenda
Design Reviews - Why they are done
Design Reviews - Tone and expectations
Notes for Hubs & Teachers - Planning the reviews
Outlines - Our Targeted Topics
Risks vs Opportunities - the Difference Explained
Templates -
Preliminary Design Review
Critical Design Review
Summary Points
Design Reviews – Why are they done
In business, reviews are Program Control Points to make sure things run smoothly.�Experienced technical and business leaders ask questions about requirements, design trade offs and design details to verify alignment. They query material choices and staff workloads to identify schedule risks. They discuss alternate approaches to mitigate risk.
Event | Schedule | Team �Participation |
Kickoff | 1st event Starts the 8-week clock. | Required |
Preliminary Design Review | Nominally week 2 | Optional1 |
Critical Design Review 2 | Nominally week 5 | Required |
Practice Day3 | Nominally week 7 | Required |
Game Day | Final event At the end of 8-weeks | Required |
1Check to verify this is offered by the hub.
2Format is at the hub’s discretion. Template available.
3Additional practice days are allowed and included at the hub’s discretion.
Program Leadership, Management, & Control
X
X
Game Day
Week8
X
X
Practice Day3
X
Kickoff
Day 1
Preliminary Review1
Critical Design Review2
Optional PDR and Required CDR are offered as mentoring opportunities, especially for less experienced teams.
Read the rules
Determine requirements
Research similar designs
Inventory resources available
Brainstorm strategy and designs
Select
Simple models and prototypes
Fail early and fail often
Simple design = Easy manufacturing
Fabricate components
Bring smaller pieces together
Assemble components
Test, test, and test some more!
Understand the Problem
Concept Exploration and Selection
Analyze & Prototype
Detailed Design and Manufacturing
Integration and Test
PDR here
CDR here
Design Reviews… Tone and Expectations� “30 minute Mentoring”
This is a Q&A milestone to make sure you have a good start.
PDR Expectations - 2nd week, after you realize what questions you have. Target 30 minutes
CDR Expectations - Usually about two-thirds way through development.
Notes for Hubs & Teachers - Planning
Not formally scored, since it is not an element of the BEST Award calculation., �This is a Q&A / Mentoring opportunity. Reviewers help identify overlooked items, �poke at design details, suggest corrections, alternatives, improvements. �Discuss: Requirements, Status, Key Features, Accomplishments, are there any issues?
Mentor, Encourage and Redirect as needed.
Hints for the Hub Leads
Retiree volunteers usually give you the most time flexibility. It is much easier if you get one or two retired engineers to manage all the teams. They have experience with review processes, know questions to ask, have the time available, can make referrals, and can draft others if needed.
Scheduling can be done through Registry Workflow. Set a wide range of slots, let Teams choose.
Schedule 60-75 Minute blocks, then slide start times to fit class schedules as needed. Gives times for breaks, and lets you adjust to late starts or ending times.
With a larger hub, some reviews may roll into the next week. That is OK.
�
When possible, Do try to accommodate a team’s regular class, club, or after school meeting times.
(move the day, or recruit one more Reviewer).
Figure out conflicts, update timeslots as they fill up.
Schools send the meeting link. This maintains positive security for the school, since each may have different district procedures.
TO: “TBD” @bestinc.org �Subject: PDR, XYZ HS, Wed 10:15 AM
URL Hotlink from the school
Example time slots
Critical Design Review (Required)
CDR Slide template follows
- Title Slide
- Requirements
- Robot Functions
- HARDWARE Design Specifications/ Details, Sketches or CAD
- SOFTWARE Design Specifications/ Details, Tools, Special Functions �- Human Interface Driver Training and Practice time
- Risks Gaps you already know about
- Opportunities Stretch goals to WOW the Reviewers
Preliminary Design Review (optional)
PDR Slide template
The Team OWNS the design. It does not have to implement any suggestions…
CDR & PDR Templates
For reference… Modify, Add, Use your own, �or just discuss with a checklist. ��You can mix slides from the PDR and CDR templates.�They are simply provided as examples.��First slides tell us what you are doing. ~5-10 minutes�Risk / Opportunities are discussion starters.
Teams can use the template as a checklist. You do not even have to prepare.
The importance is that Teachers/Teams have a Q&A and Re-focus opportunity.
Risks v Opportunities - the Difference Explained
Your Planned Capabilities and Performance
Opportunities
Risks
Obstacles to your current plan
Gaps you already know about
Things that might go wrong
Things that are still concerns
What and how bad is the consequence if it happens?
What is your plan B or alternative?
What would be a disaster?
Stretch goals to WOW the Judges
Improvements to your plan
How can you score more points
Difference between 1st and 2nd
PDR-Title Page
Team Name Here
School Logo or
Robot Sketch
Other Artwork,
if desired
BEST Preliminary Design Review
PDR1 - Introductions
President
or Team Lead
Hardware
Software
Finance or Treasurer
Marketing Presentation Lead
Notebook Lead
Exhibit Booth
Members
Student #1
Student # 2
…
Student # N
Teacher
Mentor
Members
Student #1
Student # 2
…
Student # N
Members
Student #1
Student # 2
…
Student # N
Members
Student #1
Student # 2
…
Student # N
Members
Student #1
Student # 2
…
Student # N
Members
Student #1
Student # 2
…
Student # N
PDR2 - Schedule
Sept 10 Kickoff
TBD Brainstorming
TBD Task 1
TBD PDR
TBD Task 2
TBD Tasks 3
TBD CDR
TBD Task 4
Oct 29 Demo Day
Oct 29 Notebook Due
Nov 5 Game Day
CDRs
PDRs
Competition
A “todo List” list ,
Or a calendar.
or a detailed schedule and action plan.
PDR3 - Requirements and Brainstorming�
Do you understand? Let’s discuss.�This is a Q&A opportunity. (Official Answers will be in the BEST FAQs).
Objectives - scoring piece strategy including priorities � What is the problem to solve?
What do we want to accomplish to score points?
Constraints - rules, schedule, kit, � What limits what we do when building our robot?
Functions - What actions must the robot (HW & SW), the Driver, and Spotter do?
e.g. move forward/back, joystick easy to learn, time for objectives ��Requirements - game field and pieces dimensions, � What are the important characteristics that your robot must meet � to successfully score the points you intend to score?��How did Brainstorming work for you?
PDR4 - Hardware and Software�Think of these as discussion points, don’t make this alot of work.
Hardware & Tools - Laptops? Basic engineering design process chosen?
What CAD Tools, which software? Version control? ��Do you expect to use 3D Printing? Library?
Software Design Discussion
- Have you selected and installed your basic Software tool?
- Does your team have access to the SW supplier’s on-line training?
- Engineering notebook assignments?
- Do you plan on any special SW features or capabilities?
For More advanced teams
Here is the starting point for learning Mathworks/ Simulink
BEST Robotics - MATLAB & Simulink (mathworks.com)
https://www.mathworks.com/academia/student-competitions/best-robotics.html
Good place for Sketches
More than one slide OK.
PDR5 - Risks
Gaps you already know about
Things that might go wrong, things that are still concerns
What and how bad is the consequence if it happens
What is your plan B or alternative
Risk�Main concern | Consequence�What if you do, what if you don’t ? | Improvement/Action�What is your initial strategy |
No IR Sensor | Makes game play more complex | Investigate this feature |
One Person Too many jobs | Design Closure and Training Issues | Backups and Successors |
Not enough People | Forced to short-change efforts. | Recruitment Ideas |
Core SW not loaded | Can’t get a basic robot function | Ask for help. |
| | |
| | |
| | |
If these turn into actions,
you can add What, Who, When.
Examples… �Make your own list
PDR6 - Opportunities
Stretch goals to WOW the Reviewers
Possible Improvements
Things you could change to score more points
Opportunity | Benefits, Cost |
Batteries | Recharge Time? a battery charging plan and responsibility established |
IR Sensor | Improve performance by converting multi-action control to a SW routine. |
Alternate Component | Better traction, more speed, more reliable? |
Driver Training | Time Trails, more practice and training for slowest drivers. |
If these turn into actions,
you can add What, Who, When.
Examples… �Make your own list
CDR -Title Page
Team Name Here
BEST Critical Design Review
CAD Image or Sketch of proposed Robot
Other Artwork
e.g. Game Field
CDR1 Requirements
Show us any Key brainstormed Ideas or Trade Matrices.
Describe how specification limits (e.g. power, size, speed) bound the design
Discuss how your design and game strategy work together.
Add graphics that help you explain…
These are just an examples.
CDR2 - Robot Functions
Requirements, Constraints, Functions
Describe and trades and prototyping.
What kinds of calculations were done to analyze performance.
Add Tables or images that help you explain… This is just an example.
CDR3 – Hardware Status
Good place for Sketches, and 2d or 3D artwork
Explain drive chain, size advantages, weight savings
Discuss updated hardware design details
especially the unique features of your design (e.g. reach, grip, speed, weight)
Prototype photos, CAD drawings
CDR4 – Software Status
Software Design Discussion
What special features and capabilities
Do you use the Infrared IO for control
Address any simulations
Discuss how you implemented functions
Any Autonomous features?
CDR4a – human interface
human interface (driver and spotter)
Do you have a training and practice plan?
Can drivers practice in simulation?
CDR5 Risks
Gaps you already know about
Things that might go wrong, things that are still concerns
What and how bad is the consequence if it happens
What is your plan B or alternative
Risk | Consequence | Improvement |
Low Batteries | Slow or sluggish movements, �Loss of RF Control | a battery charging plan and responsibility established |
String tangling | Few or No points scored | Add guides |
Tire Slipping | Poor control, can’t move over inclines | Rubber tread needs to be added |
Infrared IO | Alignment, thoroughly debugged? | How have you tested? |
One Person Too many jobs | Design Closure and Training Issues | Backups and Successors |
If these turn into actions,
you can add What, Who, When.
Examples… �Make your own list
CDR6 Opportunities
Stretch goals to WOW the Reviewers
Possible Improvements
Things you could change to score more points
Opportunity | Benefits, Cost |
Batteries | Recharge Time? battery charging plan and responsibility established |
Infrared Sensor | Can you simplify movements by improving software Control? |
Alternative designs | Better traction, more speed, improved power? |
Driver Training | Time Trails, more practice and training for slowest drivers. |
Last Minute Ideas | Is there any “aha” idea that can still work? Is there enough time? |
If these turn into actions,
you can add What, Who, When.
Examples… �Make your own list
Design Reviews �Summary Points for Teachers and Hubs.
Teachers - Check with your hub on PDR and CDR plans
Teams can use the template as a checklist. You do not even have to prepare.
The importance is that Teachers/Teams have a Q&A and Re-focus opportunity.
Rookie Teams struggle.. This is our best chance to help.
Newer teams need these… they may skip, but it helps them organized.
These are only reviews. We expect they help, but
The Team OWNS the design,
and does not have to implement any suggestions.