CanSat 2016 Critical Design Review (CDR) Outline Version 1.0

CanSat 2016 Critical Design Review (CDR) Outline Version 1.0
Your Team Number Here Your Team Name Here CanSat 2016 CDR: Team ### (Team Number and Name)

Provide a simple outline of the presentation
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 Glider Science Payload component of the CanSat IMPORTANT PRESENTATION GUIDELINE: Teams should only present charts with this star icon during the teleconference. 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 2016 CDR: Team ### (Team Number and Name)

CanSat 2016 CDR: Team ### (Team Number and Name)
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 CanSat 2016 CDR: Team ### (Team Number and Name)

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 2016 CDR: Team ### (Team Number and Name)

Presenter Name(s) Go 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. System Overview Presenter Name(s) Go Here CanSat 2016 CDR: Team ### (Team Number and Name)

CanSat 2016 PDR: Team ### (Team Number and Name)
Mission Summary Overview of the mission objectives Indicate whether one or both selectable objectives (bonus) are being attempted Describe selection rationale Include any external objectives (personal, laboratory or sponsor, class, etc.) relevant to the design Presenter: Name goes here CanSat 2016 PDR: Team ### (Team Number and Name)

Summary of Changes Since PDR
Overview design changes since PDR Details of the changes are discussed in subsequent sections Presenter: Name goes here CanSat 2016 CDR: Team ### (Team Number and Name)

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 2016 CDR: Team ### (Team Number and Name)

System Concept of Operations
1 to 3 slides providing overview of CanSat operations Should include Pre-launch activities Launch and descent operations Be sure to include Glider operations Post-launch recovery and data reduction Focus on launch day activities Team member roles and responsibilities on launch day Simple flow diagrams and cartoons are a good way to present the CONOPS Absolutely no hand-drawn diagrams CanSat 2016 CDR: Team ### (Team Number and Name)

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 CanSat design Presenter: Name goes here CanSat 2016 CDR: Team ### (Team Number and Name)

Launch Vehicle Compatibility
Discussion of how the CanSat is integrated into the rocket payload section Discussion of how the CanSat 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 (no sharp protrusions) At CDR this should include measured and/or prototype dimensions Notes: In past years there were a large number of CanSats that did not deploy from the payload sections of the rocket because of protrusions or because the CanSat was too wide to fit in the rocket Lack of sharp protrusions and fit within the Launch Vehicle will also be scored at the Flight Readiness Review Presenter: Name goes here CanSat 2016 CDR: Team ### (Team Number and Name)

Sensor Subsystem Design
Presenter Name(s) Go Here CanSat 2016 CDR: Team ### (Team Number and Name)

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 2016 CDR: Team ### (Team Number and Name)

Sensor Changes Since PDR
One slide providing an overview of the CanSat sensor system changes since PDR Include rationale Clearly explain why changes were made, including things like: Power limitations Testing Component size Availability CanSat 2016 CDR: Team ### (Team Number and Name)

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 2016 CDR: Team ### (Team Number and Name)

GPS Sensor Summary Summary of altitude sensor selection and characteristics Include: Sensor accuracy and data format Overview of data processing (including equations, as appropriate) Include both Carrier and Payload, as applicable Presenter: Name goes here CanSat 2016 CDR: Team ### (Team Number and Name)

Air Pressure Sensor Summary
Summary of altitude sensor selection and characteristics Include: Sensor accuracy and data format Overview of data processing (including equations, as appropriate) Include both Carrier and Payload, as applicable Presenter: Name goes here CanSat 2016 CDR: Team ### (Team Number and Name)

Pitot Tube Summary Summary of pitot tube selection and characteristics Include: Sensor accuracy and data format Overview of data processing (including equations, as appropriate) Include both Carrier and Payload, as applicable Presenter: Name goes here CanSat 2016 CDR: Team ### (Team Number and Name)

Air Temperature Sensor Summary
Summary of air temperature sensor selection and characteristics Include: Sensor accuracy and data format Overview of data formats (including equations, as appropriate) Include both Carrier and Payload, as applicable Presenter: Name goes here CanSat 2016 CDR: Team ### (Team Number and Name)

Battery Voltage Sensor Summary
Summary of battery voltage sensor selection and characteristics Include: Sensor accuracy and data format Overview of data processing (including equations, as appropriate) Include both Carrier and Payload, as applicable Presenter: Name goes here CanSat 2016 CDR: Team ### (Team Number and Name)

Camera Summary Summary of camera selection and characteristics Include: Sensor accuracy and data format Overview of data processing (including equations, as appropriate) Include both Carrier and Payload, as applicable Ensure your camera meets the requirement of 640x480 pixels in color Presenter: Name goes here CanSat 2016 CDR: Team ### (Team Number and Name)

Descent Control Design

Descent Control Overview
One slide providing an overview of the Container and Glider descent control system Include overview of the selected configurations and components necessary Include diagrams outlining descent control strategy for various flight altitude ranges CanSat 2016 CDR: Team ### (Team Number and Name)

Descent Control Changes Since PDR
List changes since the PDR Include rationale Prototype testing CanSat 2016 CDR: Team ### (Team Number and Name)

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 2016 CDR: Team ### (Team Number and Name)

Container Descent Control Hardware Summary
Summary of DCS component selection and characteristics Shock force survival Preflight Review testability For passive components, discuss: Component sizing Key design considerations Color selection(s) For active components, discuss: Sensor accuracy and data formats Overview of sensor data processing Actuator control, command rates, and data formats CanSat 2016 CDR: Team ### (Team Number and Name)

Payload Descent Control Hardware Summary
Summary of Glider Science Payload DCS sensors, flight surfaces, software, etc Include details on glider operation such as configuration, wing dimensions, and glide ratios Preflight review testability Include deployment trigger and mechanism For passive components, discuss: Component sizing Key design considerations Color selection(s) For active components, discuss: Sensor accuracy and data formats Overview of sensor data processing Actuator control, command rates, and data formats This discussion can carry over to multiple slides if necessary CanSat 2016 CDR: Team ### (Team Number and Name)

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 Glider 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 2016 CDR: Team ### (Team Number and Name)

Mechanical Subsystem Design

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 CanSat 2016 CDR: Team ### (Team Number and Name)

Mechanical Subsystem Changes Since PDR
Highlight mechanical changes since PDR. Details should be discussed on subsequent slides CanSat 2016 CDR: Team ### (Team Number and Name)

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 2016 CDR: Team ### (Team Number and Name)

Mechanical Layout of Components
Dimensioned diagrams showing: Major structural elements Overall dimensions of the CanSat Component presentation Presenter: Name goes here CanSat 2016 CDR: Team ### (Team Number and Name)

Camera Pointing Mechanism
Selectable objective – only required if Selectable Bonus 1 (camera pointing) is selected Details on mechanism that will be used to point the camera Dimensioned diagrams showing: Major mechanism components Location and orientation on the CanSat Mechanism operation details Presenter: Name goes here CanSat 2016 CDR: Team ### (Team Number and Name)

Material Selections Discussion of what materials will be used for the mechanical components and why Presenter: Name goes here CanSat 2016 CDR: Team ### (Team Number and Name)

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 2016 CDR: Team ### (Team Number and Name)

Structure Survivability
As applicable for the 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 Descent control attachments Presenter: Name goes here CanSat 2016 CDR: Team ### (Team Number and Name)

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 compared to requirement(s) Margins Must clearly distinguish between Container and Payload masses Presenter: Name goes here CanSat 2016 CDR: Team ### (Team Number and Name)

Communication and Data Handling Subsystem Design

CDH Overview One slide providing overview of the CDH subsystem Should include selected components (with brief mention of what each component is for) CanSat 2016 CDR: Team ### (Team Number and Name)

CDH Changes Since PDR List changes to the CDH since PDR. Details of the changes should be discussed in subsequent slides Presenter: Name goes here CanSat 2016 CDR: Team ### (Team Number and Name)

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 2016 CDR: Team ### (Team Number and Name)

Processor & Memory Selection
Include processor speed Include data interfaces (types and numbers) Include memory storage requirements, if applicable Presenter: Name goes here CanSat 2016 CDR: Team ### (Team Number and Name)

CanSat 2016 PDR: Team ### (Team Number and Name)
Real-Time Clock Describe design for payload and container real-time clock functions Hardware or software Reset tolerance Presenter: Name goes here CanSat 2016 PDR: Team ### (Team Number and Name)

Antenna Selection Description and characteristics of the antenna selected for the CanSat Discuss: Performance Mass CanSat 2016 CDR: Team ### (Team Number and Name)

Start Radio Prototyping and Testing Early!
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 2016 CDR: Team ### (Team Number and Name)

Telemetry Format What data is included? Include fields for bonus objectives Data rate of packets? Continuous or burst How is data formatted? Include example frames with complete descriptions Does the presented format match the Competition Guide requirements? Presenter: Name goes here CanSat 2016 CDR: Team ### (Team Number and Name)

Electrical Power Subsystem Design

EPS Overview ONE slide providing overview of EPS components (with purposes) Include a diagram Presenter: Name goes here CanSat 2016 CDR: Team ### (Team Number and Name)

EPS Changes Since PDR List changes to the EPS subsystem since PDR. Details of changes should be discussed in subsequent slides. CanSat 2016 CDR: Team ### (Team Number and Name)

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 2016 CDR: Team ### (Team Number and Name)

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 Include diagrams for Container and Payload in one or two slides Umbilical power source for use in test and safety inspection Presenter: Name goes here CanSat 2016 CDR: Team ### (Team Number and Name)

Payload Battery Selection
Describe payload battery Presenter: Name goes here CanSat 2016 PDR: Team ### (Team Number and Name)

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 sources and total power available Power storage devices and strategy Graphical representation of charge / discharge cycles Margins Include potential one hour wait on the launch pad for the Container Presenter: Name goes here CanSat 2016 CDR: Team ### (Team Number and Name)

Power Bus Voltage Measurement
Details of how the power bus voltage is measured This should include a discussion of the measurement range and resolution, data conversions, etc. Presenter: Name goes here CanSat 2016 CDR: Team ### (Team Number and Name)

Flight Software (FSW) Design

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 Focus on glider operations Presenter: Name goes here CanSat 2016 CDR: Team ### (Team Number and Name)

FSW Changes Since PDR Overview of the CanSat FSW changes since the PDR. Details of the changes should be discussed in subsequent slides. CanSat 2016 CDR: Team ### (Team Number and Name)

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 2016 CDR: Team ### (Team Number and Name)

CanSat FSW State Diagram
Software state diagrams for Payload and Container (as applicable) 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 Power management FSW recovery to correct state after processor reset during flight What data is used to recover? Presenter: Name goes here CanSat 2016 CDR: Team ### (Team Number and Name)

Glider FSW Plan Include details on how the Glider Flight Software will accomplish the objectives (glide for 2 minutes in a circular pattern not to exceed 1000m in diameter) This can be shown with block diagrams, pseudocode, or by another display method Presenter: Name goes here CanSat 2016 CDR: Team ### (Team Number and Name)

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 Discuss progress since PDR CanSat 2016 CDR: Team ### (Team Number and Name)

Ground Control System (GCS) Design

GCS Overview Include a simple context diagram showing major components (computers, antenna, adaptors, etc.) CanSat 2016 CDR: Team ### (Team Number and Name)

GCS Changes Since PDR List changes to the GCS subsystem since PDR. Details of changes should be discussed in subsequent slides. CanSat 2016 CDR: Team ### (Team Number and Name)

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 (portability requirements) Computational requirements Analysis SW requirements Mission operations sequence of events Presenter: Name goes here CanSat 2016 CDR: Team ### (Team Number and Name)

GCS Antenna Discussion of the selection of the GCS antenna Make sure to include: Antenna construction, portability, and coverage Diagram is recommended Antenna compliance with hand-held requirement Distance link predictions and margins CanSat 2016 CDR: Team ### (Team Number and Name)

GCS Software Telemetry display screen shots How will Telemetry be displayed in real time and how will it be recorded? Commercial off the shelf (COTS) software packages used Real-time plotting software design Data archiving and retrieval approach Command software and interface Progress since PDR Testing CanSat 2016 CDR: Team ### (Team Number and Name)

CanSat Integration and Test

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 Discuss subsystem integration Sequence (which subsystems are needed prior to others) Test equipment necessary Test environments necessary The goal(s) at CDR are Convey integration plans Convey plans of how the CanSat is tested as a unit Presenter: Name goes here CanSat 2016 CDR: Team ### (Team Number and Name)

Sensor Subsystem Testing Overview
Discuss tests being performed in order to verify the sensor subsystem. The test selection should demonstrate an understanding of what is important for testing each sensor at the subsystem and system levels. It is not necessary to go through each test in detail, but provide: What each test is to accomplish? Constraints on testing (necessary operational subsystems, ground support equipment, etc.) Pass/fail criteria and expected results – what are you looking for? (not just “it works” – discuss how you know it works) Presenter: Name goes here CanSat 2016 CDR: Team ### (Team Number and Name)

Descent Control Subsystem Testing Overview
Discuss tests being performed in order to verify the DCS Demonstrate an understanding of what is important for testing each components at the subsystem and system levels It is not necessary to go through each test in detail, but provide: What each test is to accomplish? Constraints on testing (necessary operational subsystems, ground support equipment, etc.) Pass/fail criteria and expected results – what are you looking for? (not just “it works” – discuss how you know it works) Drop testing / simulation CanSat 2016 CDR: Team ### (Team Number and Name)

Mechanical Subsystem Testing Overview
Discuss tests being performed in order to verify the Mechanical Subsystem. Demonstrate an understanding of what is important for mechanical testing at the subsystem and system levels. What each test is to accomplish? Constraints on testing (necessary operational subsystems, ground support equipment, etc.) Pass/fail criteria and expected results – what are you looking for? (not just “it works” – discuss how you know it works) Deployment / separation testing Acceleration / shock / survivability requirement testing CanSat 2016 CDR: Team ### (Team Number and Name)

CDH Subsystem Testing Overview
Discuss tests being performed in order to verify the CDH Subsystem Demonstrate an understanding of what is important for testing each component at the subsystem and system levels It is not necessary to go through each test in detail, but provide: What each test is to accomplish? Constraints on testing (necessary operational subsystems, ground support equipment, etc.) Pass/fail criteria and expected results – what are you looking for? (not just “it works” – discuss how you know it works) Simulation test beds / ground system checkout tests CanSat 2016 CDR: Team ### (Team Number and Name)

EPS Testing Overview Discuss the test being performed to verify the EPS Demonstrate an understanding of what is important for testing each component at the subsystem and system levels It is not necessary to go through each test in detail, but provide: What each test is to accomplish? Constraints on testing (necessary operational subsystems, ground support equipment, etc.) Voltage sensor testing Pass/fail criteria and expected results – what are you looking for? (not just “it works” – discuss how you know it works) CanSat 2016 CDR: Team ### (Team Number and Name)

FSW Testing Overview Discuss tests being performed in order to verify the flight software Test selection should demonstrate an understanding of what is important for software at subsystem and system levels It is not necessary to go through each test in detail, but provide: What each test is to accomplish? Constraints on testing (necessary operational subsystems, ground support equipment, etc.) Pass/fail criteria and expected results – what are you looking for? (not just “it works” – discuss how you know it works) Simulation test beds / ground system checkout tests CanSat 2016 CDR: Team ### (Team Number and Name)

GCS Testing Overview Discuss tests being performed in order to verify the GCS. Demonstrate an understanding of what is important for testing each sensor at the subsystem and system levels It is not necessary to go through each test in detail, but provide: What each test is to accomplish? Constraints on testing (necessary operational subsystems, ground support equipment, etc.) Pass/fail criteria and expected results – what are you looking for? (not just “it works” – discuss how you know it works) Simulation test beds / ground system checkout tests CanSat 2016 CDR: Team ### (Team Number and Name)

Mission Operations & Analysis

Overview of Mission Sequence of Events
Launch-day sequence of events Should start with 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 Delivery of telemetry data file to field judge for review Presenter: Name goes here CanSat 2016 CDR: Team ### (Team Number and Name)

Field Safety Rules Compliance
Discuss development and content of the Missions Operations Manual for your CanSat Two copies of the Mission Operations Manual are due at the Flight Readiness Review the day before launch Assemble in three ring binders (the Texas launch site may be windy) One copy is for the Flight Coordinator Discuss development status Presenter: Name goes here CanSat 2016 CDR: Team ### (Team Number and Name)

CanSat Location and Recovery
Discuss how you will find your CanSats in the field Presenter: Name goes here CanSat 2016 CDR: Team ### (Team Number and Name)

Mission Rehearsal Activities
Description of mission operations rehearsal activities including: Details of activities rehearsed to date Ground system radio link check procedures Loading the egg payload Powering on/off the CanSat Launch configuration preparations (e.g., final assembly and stowing appendages) Loading the CanSat in the launch vehicle Telemetry processing, archiving, and analysis Recovery Description of written procedures developed/required CanSat 2016 CDR: Team ### (Team Number and Name)

Requirements Compliance
The purpose of this section is to summarize and cross reference the compliance to the CanSat Competition Mission Guide requirements. Requirements Compliance Presenter Name(s) Go Here CanSat 2016 CDR: Team ### (Team Number and Name)

Requirements Compliance Overview
State current design compliance to requirements Summarize content of the detailed slides that follow If the design does not comply to the requirements, that is a serious issue – why? Presenter: Name goes here CanSat 2016 CDR: Team ### (Team Number and Name)

Requirements Compliance (multiple slides, as needed)
Provide a table demonstrating compliance to all competition base requirements Use the following format in as many slides as required Rqmt Num Requirement Comply / No Comply / Partial X-Ref Slide(s) Demonstrating Compliance Team Comments or Notes 1 Total mass of CanSat, container, and all descent control devices shall be 700 grams. Mass shall not vary more than +/-10 grams. Comply x, y, z Everything should be green by CDR. 2 The cansat must be installed in a container to protect it from deployment out of the rocket. -- 3 The container shall fit inside the cylindrical payload section of the rocket defined by the cylindrical payload envelope of 130 mm x 250 mm length control system including the descent Partial Medium problem: why? 4 The container must use a descent control system. It cannot free fall. No Comply Big problem: why? 5 The container shall not have any sharp edges that could cause it to get stuck in the rocket payload section. 6 The container must be a florescent color, pink or orange. Use the Green (Comply), Yellow (Partial Compliance), and Red (No Comply) color codes as shown in the examples above for each requirement Presenter: Name goes here CanSat 2016 CDR: Team ### (Team Number and Name)

Presenter Name(s) Go Here
Management Presenter Name(s) Go Here CanSat 2016 CDR: Team ### (Team Number and Name)

Status of Procurements
Provide status of sensor and component procurements What has been ordered, when it arrives, etc. This should include flight and GCS hardware (and software if being ordered) This information should be reflected in the overall schedule Presenter: Name goes here CanSat 2016 CDR: Team ### (Team Number and Name)

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 Total expenses and compare to requirement(s) CanSat 2016 CDR: Team ### (Team Number and Name)

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 CanSat 2016 CDR: Team ### (Team Number and Name)

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 on one slide 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 2016 CDR: Team ### (Team Number and Name)

Shipping and Transportation
Discuss plans for shipping/transporting the CanSat hardware to the launch site In past competitions, CanSat hardware checked with airlines was lost Consider options for shipping hardware to the launch site (typical for a satellite and ground system program) Consider carry-on restrictions Consider shipping/transportation of tools and equipment Antenna mast and assembly Presenter: Name goes here CanSat 2016 CDR: Team ### (Team Number and Name)

Conclusions Presentation summary and conclusions In general include the following: Major accomplishments Major unfinished work Testing to complete Flight software status Presenter: Name goes here CanSat 2016 CDR: Team ### (Team Number and Name)

Presentation Scoring & Additional Information
Do Not Include the Following Charts in the Presentations Presentation Scoring & Additional Information The following slides provide additional information regarding presentation scoring, as well as recommendations for the presentations and slides CanSat 2016 CDR: Team ### (Team Number and Name)

Presentation Scoring CDR Scoring System Overview 5% Sensor Subsystem Design 10% Descent Control Design Mechanical Subsystem Design Communication and Data Handling Subsystem Electrical Power Subsystem Design Flight Software Design Ground Control System Design CanSat Integration and Test Mission Operations and Analysis Requirements Compliance Management Overall Presentation Quality Total: 100% 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 requirement(s) 2 = complete and demonstrates requirement(s) met Each section of the presentation (System Overview, Sensor Subsystems, 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 2016 CDR: Team ### (Team Number and Name)

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 2016 CDR: Team ### (Team Number and Name)

Presentation Template Update Log (Do not include in presentation)
1.0 – Initial version for 2016 2.0 – Corrected GCS section, removed power storage slide 3.0 – Corrected GCS antenna requirements CanSat 2016 CDR: Team ### (Team Number and Name)

CanSat 2016 Critical Design Review (CDR) Outline Version 1.0

Similar presentations

Presentation on theme: "CanSat 2016 Critical Design Review (CDR) Outline Version 1.0"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

CanSat 2016 Critical Design Review (CDR) Outline Version 1.0

Similar presentations

Presentation on theme: "CanSat 2016 Critical Design Review (CDR) Outline Version 1.0"— Presentation transcript:

Similar presentations

About project

Feedback