Team Logo
Here
CanSat 2013 PDR Outline
Version 0.2
Your Team # Here
Your Team Name Here
CanSat 2013 PDR: Team ### (Team Name)
1
Team Logo
Here
(If You Want)
Presentation Outline
• Provide a simple outline of the presentation
• If possible, indicate the team member(s) who will be
presenting each section
• Terms:
– Container refers to the Re-entry Container component
of the CanSat
– Payload refers to the Science Payload component of
the CanSat
IMPORTANT PRESENTATION GUIDELINE FOR CANSAT 2013:
Teams should focus on charts with this star icon during the presentation.
Other charts should be skipped to save time; they will be reviewed by the
judges off line.
Presentations are to be 30 minutes in length.
Presenter: Name goes here
CanSat 2013 PDR: Team ### (Team Name)
2
Team Logo
Here
(If You Want)
•
•
Team Organization
Single slide listing the team members and their roles
– If possible, please include year (freshman, sophomore, etc.) for reference
– This only needs to be provided once for team members showing up multiple
times on the org chart
Good format is the use of an organization chart, such as below:
Team Lead(s)
Name(s)
Faculty Advisor
SubSystem 1 Lead
Name(s)
Subsystem
Engineer 1
SubSystem 2 Lead(s)
Name(s)
Subsystem
Engineer 1
SubSystem 3 Lead(s)
Name(s)
Subsystem
Engineer 1
Subsystem
Engineer 2
Presenter: Name goes here
CanSat 2013 PDR: Team ### (Team Name)
3
Team Logo
Here
(If You Want)
Acronyms
• Provide a list of acronyms used throughout the
presentation
– During presentations, do not read through these
acronyms
• These are for reference only
Presenter: Name goes here
CanSat 2013 PDR: Team ### (Team Name)
4
Team Logo
Here
The purpose of this section is to introduce the reviewer to the overall requirements
and configuration of the CanSat. This provides a basis for the details presented in
the subsystem sections.
Systems Overview
Presenter Name(s) Go Here
CanSat 2013 PDR: Team ### (Team Name)
5
Team Logo
Here
(If You Want)
Mission Summary
• Overview of the mission objectives
• Indicate which one (1) selectable objective is being
attempted
– Describe selection rationale
• Include any external objectives (personal, laboratory or
sponsor, class, etc.) relevant to the design
Presenter: Name goes here
CanSat 2013 PDR: Team ### (Team Name)
6
Team Logo
Here
(If You Want)
System Requirement Summary
• Overview of system (mission) level requirements
– Use bullets or a table to demonstrate an understanding
of the mission requirements
• This chart may be expanded to multiple charts as
needed
• The purpose of the chart is to demonstrate the team
understands the system-level requirements
Presenter: Name goes here
CanSat 2013 PDR: Team ### (Team Name)
7
Team Logo
Here
(If You Want)
System Level CanSat Configuration
Trade & Selection
• Present preliminary system-level concepts considered
– What configurations were considered
• Present criteria for final configuration selection
– Include discussion of why the final configuration was selected
• Include sketches and diagrams of various concepts considered
– Diagrams of non-selected configurations can include sketches of
physical layouts (e.g. scans of hand sketches rather than CAD
drawings)
• Include variations on CONOPS considered
• Limit discussions to 1-2 slides per preliminary configuration
– Presentation of the material may be at a cursory level (hit the
highlights)
Presenter: Name goes here
CanSat 2013 PDR: Team ### (Team Name)
8
Team Logo
Here
(If You Want)
System Concept of Operations
• 1-3 slides providing overview of CanSat operations
• Include:
– Launch and descent operations
– Post-launch recovery and data reduction
– Focus on selected configuration CONOPS
• Focus on how the CanSat will operate, not what
everyone on the team will be doing (to be discussed at
CDR)
• Simple flow diagrams and cartoons are a good way to
present the CONOPS
Presenter: Name goes here
CanSat 2013 PDR: Team ### (Team Name)
9
Team Logo
Here
(If You Want)
Physical Layout
• Diagram(s) showing physical layout of selected CanSat
configuration
• Make sure to include:
– Dimensions
– Placement of major components
– Relevant configurations
• Container, Payload, launch configuration, deployed, etc.
• The goal is to present the physical idea of what the
CanSat will look like for reference prior to getting into
details of the design
Presenter: Name goes here
CanSat 2013 PDR: Team ### (Team Name)
10
Team Logo
Here
(If You Want)
Launch Vehicle Compatibility
• Discussion of how the CanSats are integrated into the rocket
payload section
• Discussion of how the rocket payload section compatibility will be
verified prior to launch day
• Include a dimensioned drawing that shows clearances with the
payload section
– Focus on launch configuration (Container + Payload)
– Include all descent control apparatus
– At PDR this may be allocated dimensions (if this is the case, these
should be requirements at the system and subsystem levels)
• Note:
– In past years there were a large number of CanSats that did not
deploy from the payload sections of the rocket because of
protrusions
Presenter: Name goes here
CanSat 2013 PDR: Team ### (Team Name)
11
Team Logo
Here
Sensor Subsystem Design
Presenter Name(s) Go Here
CanSat 2013 PDR: Team ### (Team Name)
12
Team Logo
Here
(If You Want)
Sensor Subsystem Overview
• One slide providing an overview of the CanSat sensor
system
– Include summary of the selected sensors (type &
models)
– Include brief discussion of what the sensors are used for
– Focus on selected component (not all components
trades)
– Include overview of both Container and Payload sensors,
as applicable
Presenter: Name goes here
CanSat 2013 PDR: Team ### (Team Name)
13
Team Logo
Here
(If You Want)
Sensor Subsystem Requirements
• Overview of sensor subsystem requirements
– Use bullets or a table to demonstrate an understanding
of the requirements for this subsystem
• This chart may be expanded to multiple charts as
needed
• The purpose of the chart is to demonstrate to the
judges an understanding of the requirements that apply
to the subsystem
• Clearly indicate:
– Which Competition Guide Requirements are allocated to
this subsystem
– Any derived requirements for the subsysytem
Presenter: Name goes here
CanSat 2013 PDR: Team ### (Team Name)
14
Team Logo
Here
(If You Want)
GPS Trade & Selection
• Summary of GPS sensor trade studies and selection
Presenter: Name goes here
CanSat 2013 PDR: Team ### (Team Name)
15
Team Logo
Here
(If You Want)
Non-GPS Altitude Sensor
Trade & Selection
• Summary of altitude sensor trade study and selection
Presenter: Name goes here
CanSat 2013 PDR: Team ### (Team Name)
16
Team Logo
Here
(If You Want)
Air Temperature Trade & Selection
• Summary of air temperature sensor trade study and
selection
Presenter: Name goes here
CanSat 2013 PDR: Team ### (Team Name)
17
Team Logo
Here
(If You Want)
Video Camera
Trade & Selection
• SELECTABLE OBJECTIVE – ONLY REQUIRED IF
SELECTED
Presenter: Name goes here
CanSat 2013 PDR: Team ### (Team Name)
18
Team Logo
Here
(If You Want)
Impact Force Sensor
Trade & Selection
• SELECTABLE OBJECTIVE – ONLY REQUIRED IF
SELECTED
Presenter: Name goes here
CanSat 2013 PDR: Team ### (Team Name)
19
Team Logo
Here
Descent Control Design
Presenter Name(s) Go Here
CanSat 2013 PDR: Team ### (Team Name)
20
Team Logo
Here
(If You Want)
Descent Control Overview
• ONE slide providing an overview of the Container and
Payload descent control system(s)
• Include overview of the selected configurations and
components necessary
• Include diagrams outlining descent control strategy for
various flight altitude ranges
Presenter: Name goes here
CanSat 2013 PDR: Team ### (Team Name)
21
Team Logo
Here
(If You Want)
Descent Control Requirements
• Overview of subsystem requirements
• Use bullets or a table to demonstrate an understanding
of the DCS requirements
• This chart may be expanded to multiple charts as
needed
• The purpose of the chart is to demonstrate to the
judges that the team understands the system-level
requirements
• Clearly indicate:
– Which Competition Guide Requirements are allocated to
this subsystem
– Any derived requirements for the subsystem
Presenter: Name goes here
CanSat 2013 PDR: Team ### (Team Name)
22
Team Logo
Here
(If You Want)
Container Descent Control Strategy
Selection and Trade
• Summary of container DCS strategy trade studies and
selection
• Include:
– Color selection
– Shock force survival
– DCS connections
– Preflight review testability
Presenter: Name goes here
CanSat 2013 PDR: Team ### (Team Name)
23
Team Logo
Here
(If You Want)
Payload Descent Control Strategy
Selection and Trade
• Summary of Science Payload DCS strategy trade
studies and selection
– Include color selection
Presenter: Name goes here
CanSat 2013 PDR: Team ### (Team Name)
24
Team Logo
Here
(If You Want)
Descent Rate Estimates
• Present estimates for the following CanSat
configurations
– Container + Payload post separation (prior to deployment
of the Payload)
– Container following deployment of the Payload
– Payload following separation from the Container
• Include discussion of
– Calculations used
– Assumptions
• This discussion can carry over to multiple slides if
necessary
Presenter: Name goes here
CanSat 2013 PDR: Team ### (Team Name)
25
Team Logo
Here
Mechanical Subsystem Design
Presenter Name(s) Go Here
CanSat 2013 PDR: Team ### (Team Name)
26
Team Logo
Here
(If You Want)
Mechanical Subsystem Overview
• One slide providing overview of the mechanical
subsystem
– Include overview of major structural elements, material
selection, and interface definitions
– Include Container and Payload mechanical
configurations
Presenter: Name goes here
CanSat 2013 PDR: Team ### (Team Name)
27
Team Logo
Here
(If You Want)
Mechanical Sub-System
Requirements
• Overview of mechanical sub-system requirements
– Use bullets or a table to demonstrate an understanding
of the mission requirements
• This chart may be expanded to multiple charts as
needed
• The purpose of the chart is to demonstrate to the
judges that the team understands the requirements that
apply to this sub-system
• Clearly indicate:
– Which Competition Guide Requirements are allocated to
this subsystem
– Any derived requirements for the subsytem
Presenter: Name goes here
CanSat 2013 PDR: Team ### (Team Name)
28
Team Logo
Here
(If You Want)
Egg Protection Trade & Selection
• Egg protection system trade studies and selection
Presenter: Name goes here
CanSat 2013 PDR: Team ### (Team Name)
29
Team Logo
Here
(If You Want)
Mechanical Layout of Components
Trade & Selection
• Key trade issues related to mechanical layout and
component selection
• Structural material selection(s)
CanSat 2013 PDR: Team ### (Team Name)
30
Team Logo
Here
(If You Want)
Material Selections
• Discussion of what materials will be used for the
mechanical components and why
CanSat 2013 PDR: Team ### (Team Name)
31
Team Logo
Here
(If You Want)
Container - Payload Interface
• Describe how the Payload will be connected to and
released (mechanically) from the Container
– Include:
• Discussion of how descent control apparatus will be
accommodated
• Diagrams
• Method of operation
Presenter: Name goes here
CanSat 2013 PDR: Team ### (Team Name)
32
Team Logo
Here
(If You Want)
Structure Survivability Trades
• For both Container and Payload discuss:
– Electronic component mounting methods
– Electronic component enclosures
– Acceleration and shock force requirements and testing
– Securing electrical connections (glue, tape, etc.)
• Consider required judge verification during pre-flight check in
CanSat 2013 PDR: Team ### (Team Name)
33
Team Logo
Here
(If You Want)
Mass Budget
• Table(s) providing the following:
– Mass of all components
– Mass of all structural elements
– Sources/uncertainties – whether the masses are
estimates, from data sheets, measured values, etc.
– Total mass
– Margin
• Must clearly distinguish between Container and Payload
masses
– Include allocated mass for egg payload
Presenter: Name goes here
CanSat 2013 PDR: Team ### (Team Name)
34
Team Logo
Here
Communication and Data Handling
(CDH) Subsystem Design
Presenter Name(s) Go Here
CanSat 2013 PDR: Team ### (Team Name)
35
Team Logo
Here
(If You Want)
CDH Overview
• One slide providing overview of the CDH subsystem
– Should include selected components (with brief mention
of what each component is for)
Presenter: Name goes here
CanSat 2013 PDR: Team ### (Team Name)
36
Team Logo
Here
(If You Want)
CDH Requirements
• Overview of CDH sub-system requirements
– Use bullets or a table to demonstrate an understanding
of the mission requirements
• This chart may be expanded to multiple charts as
needed
• The purpose of the chart is to demonstrate to the
judges that the team understands the requirements that
apply to this sub-system
• Clearly indicate:
– Which Competition Guide Requirements are allocated to
this subsystem
– Any derived requirements for the subsystem
Presenter: Name goes here
CanSat 2013 PDR: Team ### (Team Name)
37
Team Logo
Here
(If You Want)
Processor & Memory
Trade & Selection
• Include processor speed
• Include data interfaces (types and numbers)
• Include memory storage requirements, if applicable
Presenter: Name goes here
CanSat 2013 PDR: Team ### (Team Name)
38
Team Logo
Here
(If You Want)
Antenna Trade & Selection
• Antenna selection criteria
• Antenna range and patterns
Presenter: Name goes here
CanSat 2013 PDR: Team ### (Team Name)
39
Team Logo
Here
(If You Want)
Radio Configuration
• Demonstrate an understanding of the protocol and configuration
(e.g., mode and NETID) required to initialize and utilize the XBEE
radio module
• Provide description of the impact those requirements have on the
CanSat design
• Include transmission control
– How is this managed during each mission phase?
• Note:
– Communications failures have occurred often over the past several
years of the competition
– You are encouraged to use your radios in all of your development
and testing to better ensure mission success
• Ideally you have started working with the radio and communications
protocol
Start Radio Prototyping and Testing Early!
Presenter: Name goes here
CanSat 2013 PDR: Team ### (Team Name)
40
Team Logo
Here
(If You Want)
Telemetry Format
• What data is included?
• Data rate of packet?
• How is data formatted?
– Include example frames with complete descriptions
Presenter: Name goes here
CanSat 2013 PDR: Team ### (Team Name)
41
Team Logo
Here
(If You Want)
Activation of Telemetry
Transmissions
• Discuss how telemetry transmissions are enabled via
remote command on the launch pad
Presenter: Name goes here
CanSat 2013 PDR: Team ### (Team Name)
42
Team Logo
Here
(If You Want)
Audible Locating Device Trade &
Selection
• Describe the audible locating device
• How will audible locator devices be activated and
deactivated?
– (e.g. how and when the locators are activated and how
they will be deactivated upon recovery)
Presenter: Name goes here
CanSat 2013 PDR: Team ### (Team Name)
43
Team Logo
Here
Electrical Power Subsystem (EPS)
Design
Presenter Name(s) Go Here
CanSat 2013 PDR: Team ### (Team Name)
44
Team Logo
Here
(If You Want)
EPS Overview
• One slide providing overview of EPS components (with
purposes)
• Consider using a diagram
Presenter: Name goes here
CanSat 2013 PDR: Team ### (Team Name)
45
Team Logo
Here
(If You Want)
EPS Requirements
• Overview of EPS subsystem requirements
• Use bullets or a table to demonstrate an understanding
of the mission requirements
• This chart may be expanded to multiple charts as
needed
• The purpose of the chart is to demonstrate to the
judges that the team understands the requirements that
apply to this sub-system
• Clearly indicate:
– Which Competition Guide Requirements are allocated to
this subsystem
– Any derived requirements for the subsystem
Presenter: Name goes here
CanSat 2013 PDR: Team ### (Team Name)
46
Team Logo
Here
(If You Want)
Electrical Block Diagram
• High-level schematic (not down to the resistor level)
showing power connections
– Include required voltages
– Include all major components
• Include overview of how power will be controlled and
verified externally without disassembling the CanSat
– I.e., an easily accessible external switch
Presenter: Name goes here
CanSat 2013 PDR: Team ### (Team Name)
47
Team Logo
Here
(If You Want)
Power Budget
• Power budget in tabular format which includes:
– Power consumption (W) of all components
– Expected duty cycles for all components
– Source/uncertainty for each line item
• Estimate, data sheet, measurement, etc.
– Total power consumed (mAh)
– Power available/ battery capacity (mAh)
– Margins
• Include potential one hour wait on the launch pad
Presenter: Name goes here
CanSat 2013 PDR: Team ### (Team Name)
48
Team Logo
Here
(If You Want)
Power Source Trade & Selection
• Discussion of power source selection
• Do not consider or select lithium polymer (LiPo)
batteries, which are not allowed because of fire risk
Presenter: Name goes here
CanSat 2013 PDR: Team ### (Team Name)
49
Team Logo
Here
(If You Want)
Battery Voltage Measurement
Trade & Selection
• Discuss voltage measurements technique / circuit
Presenter: Name goes here
CanSat 2013 PDR: Team ### (Team Name)
50
Team Logo
Here
Flight Software (FSW) Design
Presenter Name(s) Go Here
CanSat 2013 PDR: Team ### (Team Name)
51
Team Logo
Here
(If You Want)
FSW Overview
• Overview of the CanSat FSW design
• Should discuss
– Basic FSW architecture
– Programming languages
– Development environments
– Brief summary of what the FSW has to do
Presenter: Name goes here
CanSat 2013 PDR: Team ### (Team Name)
52
Team Logo
Here
(If You Want)
FSW Requirements
• Overview of mechanical sub-system requirements
• Use bullets or a table to demonstrate an understanding
of the mission requirements
• This chart may be expanded to multiple charts as
needed
• The purpose of the chart is to demonstrate to the
judges that the team understands the requirements that
apply to this sub-system
• Clearly indicate:
– Which Competition Guide Requirements are allocated to
this subsystem
– Any derived requirements for the subsytem
Presenter: Name goes here
CanSat 2013 PDR: Team ### (Team Name)
53
Team Logo
Here
(If You Want)
CanSat FSW State Diagram
• Software state diagram (high level at PDR) defining the
states and transition conditions of the flight software
• Things to include:
– Sampling of sensors (including rates)
– Communications (command and telemetry)
– Data storage (if applicable)
– Mechanism activations
– Major decision points in the logic
• FSW recovery to correct state after processor reset
during flight
– What data is used to recover?
Presenter: Name goes here
CanSat 2013 PDR: Team ### (Team Name)
54
Team Logo
Here
(If You Want)
Software Development Plan
• A common CanSat problem is late software
development
• Present a slide describing the plan for software
development and plans to reduce the risk of late
software development
• Include:
– Prototyping and prototyping environments
– Software subsystem development sequence
– Development team
– Test methodology
Presenter: Name goes here
CanSat 2013 PDR: Team ### (Team Name)
55
Team Logo
Here
Ground Control System (GCS) Design
Presenter Name(s) Go Here
CanSat 2013 PDR: Team ### (Team Name)
56
Team Logo
Here
(If You Want)
GCS Overview
• Include a simple context diagram showing major
components (computers, antenna, adaptors, etc.)
Presenter: Name goes here
CanSat 2013 PDR: Team ### (Team Name)
57
Team Logo
Here
(If You Want)
GCS Requirements
• Overview of GCS requirements
• Use bullets or a table to demonstrate an understanding
of the requirements for the GCS
• This chart may be expanded to multiple charts as
needed
• The purpose of the chart is to demonstrate to the
judges that the team understands the requirements that
apply to the GCS
Examples of requirements to include:
•Antenna placement (field-of-view requirements)
•Computational requirements
•Analysis SW requirements
•Mission operations sequence of events
Presenter: Name goes here
CanSat 2013 PDR: Team ### (Team Name)
58
Team Logo
Here
(If You Want)
GCS Antenna Trade & Selection
• Make sure to include:
– Antenna placement and coverage
• Diagram is recommended
– Antenna mast height and mounting strategy
• Launch day construction
• Launch day verification of height
– Distance link predictions and margins
Presenter: Name goes here
CanSat 2013 PDR: Team ### (Team Name)
59
Team Logo
Here
(If You Want)
GCS Software
• Telemetry display prototypes
• Commercial off the shelf (COTS) software packages
used
• Real-time plotting software design
• Data archiving and retrieval approach
• Command software and interface
• Telemetry data recording and media presentation to
judges for inspection
CanSat 2013 PDR: Team ### (Team Name)
60
Team Logo
Here
CanSat Integration and Test
Presenter Name(s) Go Here
CanSat 2013 PDR: Team ### (Team Name)
61
Team Logo
Here
(If You Want)
CanSat Integration and Test
Overview
• 3-5 slides
• Discussion of how the CanSat subsystems will be integrated
• Discussion of system-level tests to be performed on the integrated
CanSat
• At PDR this should include concepts for how subsystems will be
integrated
– Sequence (which subsystems are needed prior to others)
– Test equipment necessary
– Test environments necessary
• The goal(s) at PDR are
– Get teams thinking about how to put all the pieces together
– Get teams thinking about how to test the integrated assembly to
make sure it works as a unit
Presenter: Name goes here
CanSat 2013 PDR: Team ### (Team Name)
62
Team Logo
Here
Mission Operations & Analysis
Presenter Name(s) Go Here
CanSat 2013 PDR: Team ### (Team Name)
63
Team Logo
Here
(If You Want)
Overview of Mission Sequence of
Events
• Preliminary launch-day sequence of events
– Should start w/arrival at the launch site and proceed
through recovery and data analysis
• Include:
– Flow chart of events
– Team member roles and responsibilities
– Antenna construction and ground system setup
– CanSat assembly and test
• Preliminary at PDR
Presenter: Name goes here
CanSat 2013 PDR: Team ### (Team Name)
64
Team Logo
Here
(If You Want)
Mission Operations Manual
Development Plan
• Discuss development and content of the Missions
Operations Manual for your CanSat
Presenter: Name goes here
CanSat 2013 PDR: Team ### (Team Name)
65
Team Logo
Here
(If You Want)
CanSat Location and Recovery
• Discuss how you will find your CanSats in the field
– Discuss Container and Payload recovery
– Color selection of visible components
– CanSat return address labeling
Presenter: Name goes here
CanSat 2013 PDR: Team ### (Team Name)
66
Team Logo
Here
Management
Presenter Name(s) Go Here
CanSat 2013 PDR: Team ### (Team Name)
67
Team Logo
Here
(If You Want)
CanSat Budget – Hardware
• Provide a table listing the costs of the CanSat flight
hardware
• Table should include
– Cost of major components and hardware
– Indication of whether these costs are actual, estimates,
or budgeted values
– Indication of hardware re-use from previous years
• The current market value for re-used components should be
included
• Note: re-used flight hardware has been known to be more likely
to fail
Presenter: Name goes here
CanSat 2013 PDR: Team ### (Team Name)
68
Team Logo
Here
(If You Want)
•
CanSat Budget – Other Costs
Table(s) (same format as Hardware Budget) showing
– Ground control station costs
– Other costs
•
•
•
•
•
Prototyping
Test facilities and equipment
Rentals
Computers
Travel
– Income
• Sources of project income
•
The goal(s) of this budget are
– To provide an understanding of the overall design and development costs
– Get the teams thinking about the overall costs including necessary funds for
travel
– Identify shortfalls in the budget that require attention
• In the past some teams have not been able to attend the competition due to a
lack of funds
• If caught early enough, there are a number of resources for funding that may
available to teams
– THE COMPEITION DOES NOT PROVIDE ANY DEVELOPMENT FUNDING OR
DONORS
Presenter: Name goes here
CanSat 2013 PDR: Team ### (Team Name)
69
Team Logo
Here
(If You Want)
•
•
•
•
•
Program Schedule
Overview of development schedule to include
– Competition milestones
– Academic milestones and holidays
– Major development activities
– Component/hardware deliveries
– Major integration and test activities and milestones
The schedule should be “wrapped up” to 1-2 levels
– Show high-level tasks only in order to make the schedule readable
– It is recommended a schedule at lower levels is developed in order to provide the
team with tools for tracking progress and assessing trouble areas
The goals of this schedule are to
– Provide a tool for the team to track progress of CanSat design and development
– Provide tool for judges to assess trouble areas and offer ways for the team to best
meet the objectives of the competition
A one page Gantt summary chart showing task start and stop dates and durations
shall be presented
– Schedule should include linkages between tasks to provide the team with an idea of
what happens in the overall flow when milestones are not met on time
Make sure the schedule is readable in the presentation
– This may require the schedule to be broken between multiple slides
• Failure to do so will result in a loss of points
Presenter: Name goes here
CanSat 2013 PDR: Team ### (Team Name)
70
Team Logo
Here
(If You Want)
Conclusions
• Presentation summary and conclusions
• In general include the following:
– Major accomplishments
– Major unfinished work
– Why you are ready to proceed to next stage of
development
Presenter: Name goes here
CanSat 2013 PDR: Team ### (Team Name)
71
Team Logo
Here
Presentation Scoring &
Additional Information
Do Not Include
the Following
Charts in the
Presentations
The following slides provide additional information
regarding presentation scoring, as well as
recommendations for the presentations and slides
CanSat 2013 PDR: Team ### (Team Name)
72
Team Logo
Here
(If You Want)
Presentation Scoring
• Each slide in this template is scored
on a scale of 0 to 2 points
– 0 = missing or no compliance to the
intent of the requirement
– 1 = topic incomplete or partial
compliance to requirements
– 2 = complete and demonstrates
requirement is met
• Each section of the presentation
(Systems Overview, Sensor
Systems, etc.) is weighted
according to the table
• Each team will receive a link to a
summary score sheet that will
contain all their competition scores
PDR
Systems Overview
Sensor Subsystem Design
Descent Control Design
Mechanical Subsystem Design
10.00%
10.00%
10.00%
10.00%
Communication & Data Handling
Subsystem Design
Electrical Power Subsystem
Design
Flight Software Design
Ground Contol System Design
10.00%
10.00%
10.00%
10.00%
CanSat Integration & Test
5.00%
Mission Operations & Analysis
5.00%
Management
5.00%
Quality
5.00%
Total: 100.00%
CanSat 2013 PDR: Team ### (Team Name)
73
Team Logo
Here
(If You Want)
PPT Template Use
• All teams shall use this presentation template
• Team logos
– A team logo can be inserted into the placeholder location (and size)
on the master slide
– If no logo is to be used, remove the placeholder from the master
slide
• Team numbers in the footer should be updated in the footer
information view
– REMEMBER TO PUT YOUR TEAM NUMBER IN THE FOOTER
– Team names are optional – if no team name is used, please delete
from footer text
• On each slide, replace the “Name goes here” in the bottom left corner
with the name of the person(s) presenting that slide
– This will allow the judges to know the person to address any
questions or comments to
CanSat 2013 PDR: Team ### (Team Name)
74
Team Logo
Here
(If You Want)
•
Trade Studies
The following recommendations are made with regards to trade studies
and selections
– Tabular formats listing configurations/components being considered are
helpful
– Need to include a discussion of the criteria being used to make the selection
• What are the components/configurations being assessed on
• How are values ascribed to the criteria
– Are high values good or low values (if a ranking system is chosen)
– Why are different ranking selected
• Data sources for information impacting the criteria and rankings
•
•
– Make sure it is clear which final component/configuration was selected
Teams using hardware from previous years are still expected to do a trade
to ensure the components are the most appropriate for the task
– Already having a component or past experience with a component can be
criteria used in the trade space
– Note that in past years re-used components have a higher failure rate
The same format (whether table are used or not) and criteria (consistent
rankings, etc.) be use for all trades to make it easier to review the various
trades in a timely manner
CanSat 2013 PDR: Team ### (Team Name)
75
Team Logo
Here
(If You Want)
•
•
Presentation Template Update Log
(Do not include in presentation)
0.1 Initial version for 2013
0.2 Minor updates before release to the teams
CanSat 2013 PDR: Team ### (Team Name)
76