<Your Team # > Your Team Name Here

Slides:



Advertisements
Similar presentations
Team Logo Here CanSat 2014 PDR: Team ### (Team Number and Name)1 CanSat 2014 Preliminary Design Review (PDR) Outline Version 1.2 Your Team # Here Your.
Advertisements

CanSat 2013 PDR Outline Version 0.2
Protocol & Test Review Spaceport America Student Launch University/Institution Team Members Date.
Proposal Analysis Review NMSGC Student Launch University/Institution Team Members Date.
Data Test Review Spaceport America Student Launch University/Institution Team Members Date.
Flight Readiness Review New Mexico Space Grant Consortium University/Institution Team Members Date.
RockSat-C 2012 SITR Full Mission Simulation Report University/Institution Team Members Date.
Individual Subsystem Testing Report Team Name University/Institution Team Members Date.
RockSat-C 2011 SITR Payload Subsystem Integration and Testing Report University/Institution Team Members Date.
Team Name Final Presentation Team Members Date Fall 2010 Rev A
RockSat-C 2011 ISTR Payload Subsystem Integration and Testing Report Universities/Institutions Team Members Date.
Team Logo Here CanSat 2012 CDR: Team ### (Team Name)1 CanSat 2011 CDR Outline Version 0.4 Your Team # Here Your Team Name Here.
1 Spring 2007 CSCI 660 CSCI-660 Project Title Project team members’ names.
Team Name Final Presentation Team Members Date Rev
Vehicle Tracking/Payload Release System For Small UAV Project Team
Payload Subsystem Integration and Testing Report Team Name 1 Team Name 2 Team Name N Universities/Institutions Team Members Date.
LSU 01/18/2005Project Life Cycle1 The Project Life Cycle Project Management Unit, Lecture 2.
Team Logo Here CanSat 2014 PDR: Team ### (Team Number and Name)1 CanSat 2014 PDR Outline Version 1.1 Your Team # Here Your Team Name Here.
Design Development Image credit:
Common PDR Problems ACES Presentation T. Gregory Guzik March 6, 2003.
New Advanced Higher Subject Implementation Events Engineering Science Advanced Higher Course Assessment.
GLAST Large Area Telescope Instrument Flight Software Flight Unit Design Review 16 September 2004 Diagnostics Framework James Swain Stanford Linear Accelerator.
THE PROJECT LIFE CYCLE PROJECT MANAGEMENT LIFE CYCLE LSU 01/18/2005 PROJECT LIFE CYCLE 1.
Requirement Engineering. Recap Elaboration Behavioral Modeling State Diagram Sequence Diagram Negotiation.
2013 CoDR Team Name Conceptual Design Review University/Institution Team Members Date 1.
Payload Concept Review [Team Name Here] [High School Name Here] 1 [Team logo here]
Page 1 Aalborg University Mission Control Center Rasmus Stougaard Department of Control Engineering, Aalborg University, Denmark.
RockSat-C 2013 FMSTR Full Mission Simulation Report University/Institution Team Members Date.
Science Research Presentation Type your project title here Your name Your teacher’s name Your school.
Payload Concept Review [Team Name Here] [High School Name & Team # Here] 1 [Team logo here]
Project management Topic 2 Product based planning.
2014 CoDR Team Name Conceptual Design Review University/Institution Team Members Date 1.
Micro Arcsecond X-ray Imaging Mission Pathfinder (MAXIM-PF) Mechanical George Roach Dave Peters 17 May 2002 “Technological progress is like an axe in the.
Team Logo Here CanSat 2015 PDR: Team 6101 (NDSU Flying Bison)1 Educating NDSU AIAA Students Aerospace Engineering Practices through CanSat Competitions.
Tethered Aerostat Program Concept Design Review Team Name Conceptual Design Review University/College Team Members Date.
Tethered Aerostat Program Concept Design Review College of Menominee Nation Conceptual Design Review College of Menominee Nation Marilyn Madosh, Larry.
CS491/691: Introduction to Aerial Robotics YOUR TEAM NAME YOUR TOPIC TITLE (CONTROL, ESTIMATION, ETC)
SUPRA SAEINDIA 2016 BUSINESS PRESENTATION Place College/ Team Logo within this space Place SUPRA Logo herePlace SAE INDIA Logo here.
Team Name Ballooning Flight Readiness Review (this is a bare-bones template – reorder the slides and/or make it fancier if you wish, but be sure to address.
CanSat 2017 Preliminary Design Review (PDR) Outline Version 1.2
CanSat 2014 Post Flight Review (PFR) Outline
Planetary Lander PDR Team Name
[Team Name Here] [High School Name Here] [Team Number Here]
Chapter 11 Designing Inputs, Outputs, and Controls.
Project Reports: Written and Oral
Project Reports: Written and Oral
Payload Concept Review
Iterative design and prototyping
SYSTEMS ANALYSIS Chapter-2.
CanSat 2018 Preliminary Design Review (PDR) Outline Version 1.0
Project METEOR [P08102 RITSAT I]
Team Members Class and Date
Team Name Team Number 21 AUG 2018
Sounding Rocket PDR Team Name
Sounding Rocket CDR Team Name
E190Q – Final Project Presenation
Science Fair Poster Board Display Guidelines and Layout
Mars Rover CDR Team Name
ELEG 3124 Signals and Systems
2019 First Nation Launch – PDR Virtual Review
Team Members (Full Names) Institution Date
2019 TEKNOFEST ROCKET CONTEST PRELIMINARY DESİGN REPORT (PDR)
Basic Design Documentation
SUNDAY SLIDES TEMPLATE
How Do Scientists Use Data?
Project Reports: Written and Oral
<Your Team # > Your Team Name Here
<Your Team # > Your Team Name Here
<Your Team # > Your Team Name Here
<Your Team # > Your Team Name Here
Presentation transcript:

<Your Team # > Your Team Name Here <University Name> TÜRKSAT Model Satellite Competition 2019 Post Flight Review (PFR) Versiyon 2.0 <Your Team # > Your Team Name Here

Sample Team Organization Single slide listing the team members and their roles Team members shall be specified in which class Team members can take on more than one task in project planning Organization chart can be designed in a unique way or in a format such as the following Team Lead(s) SubSystem 1 Lead SubSystem Engineer 1 SubSystem 2 Lead SubSystem 3 Lead SubSystem 4 Lead 2 Advisor Company Advisor Sample Presenter:

<Presenter Name(s) Here> Systems Overview <Presenter Name(s) Here> Presenter:

The basic tasks are specified. Other tasks are specified; Mission Summary The basic tasks are specified. Other tasks are specified; A task determined by the team Presenter:

Components(Container, Science payload, Mechanisms) Dimensions Physical Layout Components(Container, Science payload, Mechanisms) Dimensions Relevant configurations (Mounting component and Seperation mechanism) Dimensions and positions of electronic components Presenter:

System Concept Operation & Sequence of Events <Presenter Name(s) Here> Presenter:

System Concept Operation / Planned The operation steps of the model satellite mission will be specified. Ascent and descent process Recovery and examination of data Post-mission process It will be explained how the team manages the processes. (the duties of the team members will be indicated) These processes can be shown in diagrams. Presenter:

System Concept Operation / Actualization The events that occurred during the flight process will be written. It is aimed to make a comparison between the planned and the actual events. Presenter:

Sequence of Events / Planned The planned flight summary and stages will be indicated. Presenter:

Sequence of Events / Actualization A summary of the events after the flight will be indicated. Photos can be added if necessary. Presenter:

Analysis of Post Flight Measurements <Presenter Name(s) Here> Presenter:

All obtained telemetry data will be displayed graphically. Measurements and Data All obtained telemetry data will be displayed graphically. During the flight, it will be shown that the password sent from the ground station as a telecommand is saved to the SD card. Examples of simulation images of position information on the ground station interface will be shown. Presenter:

Video Samples of video images recorded on the SD card during the flight will be presented. Presenter:

<Presenter(s) Name Here> Problems in Flight <Presenter(s) Name Here> Presenter:

Summary of Failures Topics planned before the flight but failed for various reasons after the flight will be added. The reasons for the failed topics and solutions, if any, shall be indicated. It can be specified in tabular form. Presenter:

<Presenter(s) Name Here> Gains <Presenter(s) Name Here> Presenter:

Overview Positive or negative experiences obtained during the competition will be added as a summary. Presenter:

<Presenter(s) Name Here> Conclusion <Presenter(s) Name Here> Presenter:

Presentation summary and results will be indicated. Conclusions Presentation summary and results will be indicated. Presenter: