cansat 2011 pdr outline version 0 2 n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
CanSat 2011 PDR Outline Version 0.2 PowerPoint Presentation
Download Presentation
CanSat 2011 PDR Outline Version 0.2

Loading in 2 Seconds...

play fullscreen
1 / 84

CanSat 2011 PDR Outline Version 0.2 - PowerPoint PPT Presentation


  • 168 Views
  • Uploaded on

CanSat 2011 PDR Outline Version 0.2. Your Team # Here Your Team Name Here. Presentation Outline. Provide a simple outline of the presentation If possible, indicate the team member(s) who will be presenting each section. Presenter: Name goes here. Team Organization.

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'CanSat 2011 PDR Outline Version 0.2' - alvaro


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
cansat 2011 pdr outline version 0 2

CanSat 2011 PDR Outline Version 0.2

Your Team # Here

Your Team Name Here

CanSat 2012 PDR: Team ### (Team Name)

presentation outline
Presentation Outline
  • Provide a simple outline of the presentation
  • If possible, indicate the team member(s) who will be presenting each section

Presenter: Name goes here

CanSat 2012 PDR: Team ### (Team Name)

team organization
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:

Sample

Presenter: Name goes here

CanSat 2012 PDR: Team ### (Team Name)

acronyms
Acronyms
  • Provide a list of acronyms used throughout the presentation.
    • DURING PRESENTATIONS – DO NOT READ THROUGH THESE ACRONYMS
      • These are here for reference only

Presenter: Name goes here

CanSat 2012 PDR: Team ### (Team Name)

systems overview

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 2012 PDR: Team ### (Team Name)

mission summary
Mission Summary
  • Overview of the mission objectives
  • Indicate which one (1) selectable objective is being attempted
    • Selection rationale?
  • Include any external objectives (personal, laboratory or sponsor, class, etc.) relevant to the design

Presenter: Name goes here

CanSat 2012 PDR: Team ### (Team Name)

system requirements
System Requirements
  • Table of system (mission) level requirements
  • This chart may be expanded to multiple charts as needed
  • See Competition Guide for more information on format and content
  • DO NOT READ THROUGH THE REQUIREMENTS DURING THE PRESENTATION – HIT HIGHLIGHT (IMPORTANT REQUIREMENTS) & GIVE A FEW MOMENTS FOR REVIEWERS TO LOOK THROUGH THE REQUIREMENTS BUT DO NOT READ THROUGH EACH REQUIREMENT
    • This holds for ALL discussion of requirements throughout the presentation

Presenter: Name goes here

CanSat 2012 PDR: Team ### (Team Name)

system level cansat configuration trade selection
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
  • Helpful to 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)
  • Should include variations on CONOPS considered
  • Attempts should be made to limit these 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 2012 PDR: Team ### (Team Name)

system concept of operations
System Concept of Operations
  • 1-3 slides (roughly) providing overview of CanSat operations
  • Should 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 2012 PDR: Team ### (Team Name)

physical layout
Physical Layout
  • Diagram(s) showing physical layout of selected CanSat configuration
  • Make sure to INCLUDE:
    • DIMENSIONS
    • PLACEMENT OF MAJOR COMPONENTS
    • RELEVANT CONFIGURATIONS
      • Carrier, lander, 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 CanSat design

Presenter: Name goes here

CanSat 2012 PDR: Team ### (Team Name)

launch vehicle compatibility
Launch Vehicle Compatibility
  • Discussion of how the CanSats are integrated into the rocket payload section
  • Discussion of how the 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 (carrier + lander)
    • 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)
  • Notes:
    • In past years there were a large number of CanSats that did not deploy from the payload sections of the rocket

Presenter: Name goes here

CanSat 2012 PDR: Team ### (Team Name)

sensor subsystem design

Sensor Subsystem Design

Presenter Name(s) Go Here

CanSat 2012 PDR: Team ### (Team Name)

sensor subsystem overview
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 carrier and lander sensors, as applicable

Presenter: Name goes here

CanSat 2012 PDR: Team ### (Team Name)

sensor subsystem requirements
Sensor Subsystem Requirements
  • Examples of what these requirements should include:
  • Required sensor data ranges and resolutions
  • Operating voltage ranges
  • Data interfaces
  • Data rates

Presenter: Name goes here

CanSat 2012 PDR: Team ### (Team Name)

carrier gps trade selection
Carrier GPS Trade & Selection
  • Summary of GPS sensor trade studies and selection

See slide discussing trade studies

Presenter: Name goes here

CanSat 2012 PDR: Team ### (Team Name)

carrier non gps altitude sensor trade selection
Carrier Non-GPS Altitude Sensor Trade & Selection
  • Summary of altitude sensor trade study and selection

See slide discussing trade studies

Presenter: Name goes here

CanSat 2012 PDR: Team ### (Team Name)

carrier air temperature trade selection
Carrier Air Temperature Trade & Selection
  • Summary of air temperature sensor trade study and selection

See slide discussing trade studies

Presenter: Name goes here

CanSat 2012 PDR: Team ### (Team Name)

lander altitude sensor trade selection
Lander Altitude Sensor Trade & Selection
  • Summary of lander altitude sensor trade study and selection

See slide discussing trade studies

Presenter: Name goes here

CanSat 2012 PDR: Team ### (Team Name)

lander impact force sensor trade selection
Lander Impact Force Sensor Trade & Selection
  • SELECTABLE OBJECTIVE – ONLY REQUIRED IF SELECTED

See slide discussing trade studies

Presenter: Name goes here

CanSat 2012 PDR: Team ### (Team Name)

carrier camera trade selection
Carrier Camera Trade & Selection
  • SELECTABLE OBJECTIVE – ONLY REQUIRED IF SELECTED

See slide discussing trade studies

Presenter: Name goes here

CanSat 2012 PDR: Team ### (Team Name)

carrier video camera trade selection
Carrier Video Camera Trade & Selection
  • SELECTABLE OBJECTIVE – ONLY REQUIRED IF SELECTED

See slide discussing trade studies

Presenter: Name goes here

CanSat 2012 PDR: Team ### (Team Name)

lander video camera trade selection
Lander Video Camera Trade & Selection
  • SELECTABLE OBJECTIVE – ONLY REQUIRED IF SELECTED

See slide discussing trade studies

Presenter: Name goes here

CanSat 2012 PDR: Team ### (Team Name)

descent control design

Descent Control Design

Presenter Name(s) Go Here

CanSat 2012 PDR: Team ### (Team Name)

descent control overview
Descent Control Overview
  • ONE slide providing an overview of the carrier and lander descent control system
  • Include overview of the selected configurations and components necessary

Presenter: Name goes here

CanSat 2012 PDR: Team ### (Team Name)

descent control requirements
Descent Control Requirements
  • Examples of what these requirements should include:
  • Volume constraints
  • Packaging
  • Masses
  • Target descent rates
  • Deployment mechanisms
  • There should be separate requirements for the carrier, lander, and
  • CanSat system, as applicable.

Presenter: Name goes here

CanSat 2012 PDR: Team ### (Team Name)

carrier descent control strategy selection and trade
Carrier Descent Control Strategy Selection and Trade
  • Summary of carrier DCS strategy trade studies and selection
  • Include:
    • Color selection
    • Shock force survival
    • Preflight review testability

See slide discussing trade studies

Presenter: Name goes here

CanSat 2012 PDR: Team ### (Team Name)

lander descent control strategy selection and trade
Lander Descent Control Strategy Selection and Trade
  • Summary of lander DCS strategy trade studies and selection
    • Include color selection

See slide discussing trade studies

Presenter: Name goes here

CanSat 2012 PDR: Team ### (Team Name)

descent rate estimates
Descent Rate Estimates
  • Cover estimates for the following CanSat configurations
    • Carrier + lander post separation (prior to deployment of the lander)
    • Carrier following deployment of the lander
    • Lander following separation from the carrier
  • Include discussion of
    • Calculations used
    • Assumptions
  • This discussion can carrier over to multiple slides if necessary

Presenter: Name goes here

CanSat 2012 PDR: Team ### (Team Name)

mechanical subsystem design

Mechanical Subsystem Design

Presenter Name(s) Go Here

CanSat 2012 PDR: Team ### (Team Name)

mechanical subsystem overview
Mechanical Subsystem Overview
  • ONE slide providing overview of the mechanical subsystem
    • Include overview of major structural elements, material selection, and interface definitions

Presenter: Name goes here

CanSat 2012 PDR: Team ### (Team Name)

mechanical system requirements
Mechanical System Requirements
  • Examples of what these requirements should include:
  • Mass allocations
  • Volume and dimensions constraints
  • Structural strength/load requirements
  • There may be separate requirements for the carrier, lander, and
  • CanSat system, as applicable.

Presenter: Name goes here

CanSat 2012 PDR: Team ### (Team Name)

lander egg protection trade selection
Lander Egg Protection Trade & Selection
  • Egg protection system trade studies and selection

See slide discussing trade studies

Presenter: Name goes here

CanSat 2012 PDR: Team ### (Team Name)

mechanical layout of components trade selection
Mechanical Layout of Components Trade & Selection
  • Key trade issues related to mechanical layout and component selection
  • Structural material selection(s)

See slide discussing trade studies

CanSat 2012 PDR: Team ### (Team Name)

material selections
Material Selections
  • Discussion of what materials will be used for the mechanical components and why

CanSat 2012 CDR: Team ### (Team Name)

carrier lander interface
Carrier-Lander Interface
  • DESCRIBES HOW THE LANDER WILL BE CONNECTED TO AND RELEASED (MECHANICALLY) FROM THE CARRIER
    • Needs to include discussion of how descent control apparatus will be accommodated

Presenter: Name goes here

CanSat 2012 PDR: Team ### (Team Name)

structure survivability trades
Structure Survivability Trades
  • For both Carrier and Lander discuss:
    • Electronic component mounting methods
    • Electronic component enclosures
    • Acceleration and shock force requirements and testing

See slide discussing trade studies

CanSat 2012 PDR: Team ### (Team Name)

mass budget
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
    • Margins
  • Must clearly distinguish between carrier and lander masses
    • Include allocated mass for egg payload

Presenter: Name goes here

CanSat 2012 PDR: Team ### (Team Name)

communication and data handling subsystem design

Communication and Data Handling Subsystem Design

Presenter Name(s) Go Here

CanSat 2012 PDR: Team ### (Team Name)

cdh overview
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 2012 PDR: Team ### (Team Name)

cdh requirements
CDH Requirements
  • Examples of what these requirements should include:
  • Processor speeds
  • Memory requirements
  • I/O ports (number & types)
  • There should be separate requirements for the carrier, lander, and
  • CanSat system, as applicable.

Presenter: Name goes here

CanSat 2012 PDR: Team ### (Team Name)

processor memory trade selection
Processor & Memory Trade & Selection
  • Include processor speed
  • Include data interfaces (types and numbers)
  • Include memory storage requirements, if applicable
  • Discussion for Carrier and Lander
  • May be more than one slide if necessary

See slide discussing trade studies

Presenter: Name goes here

CanSat 2012 PDR: Team ### (Team Name)

carrier antenna trade selection
Carrier Antenna Trade & Selection

See slide discussing trade studies

Presenter: Name goes here

CanSat 2012 PDR: Team ### (Team Name)

radio configuration
Radio Configuration
  • Demonstrate an understanding of the protocol 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 2012 PDR: Team ### (Team Name)

carrier telemetry format
Carrier Telemetry Format
  • What data is included?
  • Data rate of packet?
  • How is data formatted?
    • Include example frames with descriptions

Presenter: Name goes here

CanSat 2012 PDR: Team ### (Team Name)

activation of telemetry transmissions
Activation of Telemetry Transmissions
  • Discuss how telemetry transmissions are enabled via remote command on the launch pad

Presenter: Name goes here

CanSat 2012 PDR: Team ### (Team Name)

locator device trade selection
Locator Device Trade & Selection
  • This include locator devices for Carrier and Lander
  • 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)

See slide discussing trade studies

Presenter: Name goes here

CanSat 2012 PDR: Team ### (Team Name)

electrical power subsystem design

Electrical Power Subsystem Design

Presenter Name(s) Go Here

CanSat 2012 PDR: Team ### (Team Name)

eps overview
EPS Overview
  • ONE slide providing overview of EPS components (with purposes)
  • Consider a diagram

Presenter: Name goes here

CanSat 2012 PDR: Team ### (Team Name)

eps requirements
EPS Requirements
  • Examples of what these requirements should include:
  • Voltage requirements (including regulation as necessary)
  • Battery requirements
  • Measurement accuracy & resolution
  • There should be separate requirements for the carrier, lander, and
  • CanSat system, as applicable.

Presenter: Name goes here

CanSat 2012 PDR: Team ### (Team Name)

carrier electrical block diagram
Carrier 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

Presenter: Name goes here

CanSat 2012 PDR: Team ### (Team Name)

lander electrical block diagram
Lander 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

Presenter: Name goes here

CanSat 2012 PDR: Team ### (Team Name)

carrier power budget
Carrier 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
    • Power available
    • Battery capacity
    • Margins
      • Including potential one hour wait on the launch pad

Presenter: Name goes here

CanSat 2012 PDR: Team ### (Team Name)

lander power budget
Lander 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
    • Power available
    • Margins

Presenter: Name goes here

CanSat 2012 PDR: Team ### (Team Name)

power source trade selection
Power Source Trade & Selection
  • Discussion of power source selection
  • Include power source selection of Carrier and Lander

See slide discussing trade studies

Presenter: Name goes here

CanSat 2012 PDR: Team ### (Team Name)

battery voltage measurement trade selection
Battery Voltage MeasurementTrade & Selection
  • Discuss voltage measurements for both carrier AND lander

See slide discussing trade studies

Presenter: Name goes here

CanSat 2012 PDR: Team ### (Team Name)

flight software design

Flight Software Design

Presenter Name(s) Go Here

CanSat 2012 PDR: Team ### (Team Name)

fsw overview
FSW Overview
  • 1-2 slides providing 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 2012 PDR: Team ### (Team Name)

fsw requirements
FSW Requirements
  • Examples of what these requirements should include:
  • Data sample rates
  • Interface software
  • Mission states and sequence
  • Testing configurations and code
  • Data storage interfaces
  • There should be separate requirements for the carrier, lander, and
  • CanSat system, as applicable.

Presenter: Name goes here

CanSat 2012 PDR: Team ### (Team Name)

carrier cansat fsw overview
Carrier CanSat FSW Overview
  • Software flow diagram (high level at PDR) for carrier CanSat
  • Things to be included:
    • Sampling of sensors (including rates)
    • Communications
    • Data storage (if applicable)
    • Hardware interfaces
    • Major decision points in the logic
    • Preliminary (high-level) flow diagram(s)

Presenter: Name goes here

CanSat 2012 PDR: Team ### (Team Name)

lander cansat fsw overview
Lander CanSat FSW Overview
  • Software flow diagram (high level at PDR) for lander CanSat
  • Things to be included:
    • Sampling of sensors (including rates)
    • Communications
    • Data storage (if applicable)
    • Hardware interfaces
    • Major decision points in the logic
    • Preliminary (high-level) flow diagram(s)

Presenter: Name goes here

CanSat 2012 PDR: Team ### (Team Name)

lander cansat fsw overview1
Lander CanSat FSW Overview
  • Software flow diagram (high level at PDR) for lander CanSat
  • Things to be included:
    • Sampling of sensors (including rates)
    • Communications
    • Data storage (if applicable)
    • Hardware interfaces
    • Major decision points in the logic
    • Preliminary (high-level) flow diagram(s)

Presenter: Name goes here

CanSat 2012 PDR: Team ### (Team Name)

lander cansat fsw overview2
Lander CanSat FSW Overview
  • Software flow diagram (high level at PDR) for lander CanSat
  • Things to be included:
    • Sampling of sensors (including rates)
    • Communications
    • Data storage (if applicable)
    • Hardware interfaces
    • Major decision points in the logic
    • Preliminary (high-level) flow diagram(s)

Presenter: Name goes here

CanSat 2012 PDR: Team ### (Team Name)

software development plan
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 2012 PDR: Team ### (Team Name)

ground control system design

Ground Control System Design

Presenter Name(s) Go Here

CanSat 2012 PDR: Team ### (Team Name)

gcs overview
GCS Overview
  • Include a simple context diagram showing major components (computers, antenna, adaptors, etc.)

Presenter: Name goes here

CanSat 2012 PDR: Team ### (Team Name)

gcs requirements
GCS Requirements
  • Examples of what these requirements should include:
  • Antenna placement (field-of-view requirements)
  • Computational requirements
  • Analysis SW requirements
  • Mission operations sequence of events

Presenter: Name goes here

CanSat 2012 PDR: Team ### (Team Name)

gcs antenna trade selection
GCS Antenna Trade & Selection
  • Make sure to include:
    • Antenna placement and coverage
      • Diagram is recommended
    • Antenna height and mounting strategy
      • Launch day construction
    • Distance link predictions and margins

See slide discussing trade studies

Presenter: Name goes here

CanSat 2012 PDR: Team ### (Team Name)

gcs software
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

CanSat 2012 PDR: Team ### (Team Name)

cansat integration and test

CanSat Integration and Test

Presenter Name(s) Go Here

CanSat 2012 PDR: Team ### (Team Name)

cansat integration and test overview
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 2012 PDR: Team ### (Team Name)

mission operations analysis

Mission Operations & Analysis

Presenter Name(s) Go Here

CanSat 2012 PDR: Team ### (Team Name)

overview of mission sequence of events
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 2012 PDR: Team ### (Team Name)

mission operations manual development plan
Mission Operations Manual Development Plan
  • Discuss development and content of the Missions Operations Manual for your CanSat

Presenter: Name goes here

CanSat 2012 PDR: Team ### (Team Name)

cansat location and recovery
CanSat Location and Recovery
  • Discuss how you will find your CanSats in the field
    • Discuss Carrier and Lander recovery

Presenter: Name goes here

CanSat 2012 PDR: Team ### (Team Name)

management

Management

Presenter Name(s) Go Here

CanSat 2012 PDR: Team ### (Team Name)

cansat budget hardware
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

Presenter: Name goes here

CanSat 2012 PDR: Team ### (Team Name)

cansat budget other costs
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 2012 PDR: Team ### (Team Name)

program schedule
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 Gantt chart showing task start and stop dates and durations is recommended
    • 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 2012 PDR: Team ### (Team Name)

conclusions
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 2012 PDR: Team ### (Team Name)

presentation scoring additional information

Presentation Scoring & Additional Information

The following slides provide additional information regarding presentation scoring, as well as recommendations for the presentations and slides

CanSat 2012 PDR: Team ### (Team Name)

presentation scoring
Presentation Scoring
  • Each slide is scored on a scale of 0 to 10 points
  • 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

CanSat 2012 PDR: Team ### (Team Name)

ppt template use
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 2012 PDR: Team ### (Team Name)

trade studies
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
  • Recommended that 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 2012 PDR: Team ### (Team Name)

update log
Update log
  • 0.1 Initial version
  • 0.2
    • Page 45, removed mistaken requirement for telemetry transmission termination

CanSat 2012 CDR: Team ### (Team Name)