Proposal Analysis Review NMSGC Student Launch University/Institution Team Members Date.

Slides:



Advertisements
Similar presentations
RockSat-C 2012 CoDR Minnesota Sound Wreckers Conceptual Design Review University of Minnesota Alexander Richman Jacob Schultz Justine Topel Will Thorson.
Advertisements

Protocol & Test Review Spaceport America Student Launch University/Institution Team Members Date.
Data Test Review Spaceport America Student Launch University/Institution Team Members Date.
Critical Analysis Review NMSGC Student Launch Program University/Institution Team Members Date.
Flight Readiness Review New Mexico Space Grant Consortium University/Institution Team Members Date.
RockSat-C 2012 LRR Launch Readiness Review University/Institution Team Members Date.
Team Name Conceptual Design Review Team Members Date Fall 2011 Rev A
Colorado Space Grant Consortium Virginia Space Grant Consortium 1 University A University B Team # Logo 1 Logo 2.
RockSat-C 2012 SITR Full Mission Simulation Report University/Institution Team Members Date.
Individual Subsystem Testing Report Team Name University/Institution Team Members Date.
Team Name Conceptual Design Review 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
University of Wyoming Charles Galey, Nicholas Roder, Peter J. Jay, William Ryan 10/14/
RockSat-C 2011 ISTR Payload Subsystem Integration and Testing Report Universities/Institutions Team Members Date.
Team Name Conceptual Design Review Team Members Date Fall 2010 Rev A
Good Vibrations Conceptual Design Review University of Wyoming James Richey, Justin Thornton, Luke Voss, Jake Thatcher, Tony Allais Oct 27, 2008.
Team Name Critical Design Review Team Members Date Fall 2011 Rev A
Full Mission Simulation Test Report Team Name University/Institution Team Members Date.
Comments on this template -Leave time for questions -Leave time for demonstration -Use your actual hardware in the presentation -Practice your presentation.
Space Cowboys. Mission Overview Objective – Accurately measure flight parameters including ambient and skin temperatures, pressure, acceleration, spin.
Team Name Launch Readiness Review Team Members Date Fall 2011 Rev A
Team Name Final Presentation Team Members Date Rev
2011 CoDR Team Name Conceptual Design Review University/Institution Team Members Date 1.
NORTHWEST NAZARENE UNIVERSITY CHAD LARSON, BEN GORDON, DAVID VINSON, SETH LEIJA, ZACH THOMAS, DREW JOHNSON NNU Team Conceptual Design Review.
RockSat-C 2011 CoDR CSU RocketSat-C Conceptual Design Review Colorado State University Isaiah Franka Jordan Rath Abby Wilbourn Mike Yeager 10/1/10 1.
Team Name Final Presentation Team Members Date. User notes –You may reformat to fit your design but make sure you cover the following points –You may.
Payload Subsystem Integration and Testing Report Team Name 1 Team Name 2 Team Name N Universities/Institutions Team Members Date.
Conceptual Design Review Metro State College of Denver Daniel Bass, Matt Hanley
LSU 10/09/2007System Design1 Project Management Unit #2.
(PDR ) University of Northern Colorado Nathan and Casey 11/14/08.
Critical Design Review Team Name University/Institution Team Members Date.
Miscellaneous Notes: This is a bare-bones template – make it fancier if you wish, but be sure to address at least the items listed here. Basically this.
New Mexico Space Grant Consortium Student Launch Program Provide annual access to space for student experiments from Spaceport America.
2014 CDR Team Name Critical Design Review CDR CDR Delieverables 1.Mechanical drawings in pdf format 2.Electrical schematics in pdf format 3.Completed.
RamRack Preliminary Design Review Colorado State University Zach Glueckert Christopher Reed Timothy Schneider Brendan Sheridan Christina Watanuki Advisor:
MINNROCK CONCEPTUAL DESIGN REVIEW University of Minnesota William Ung Scott Balaban Tom Thoe Bryce Doug Carlson 11/14/2008.
Team Name Flight Readiness Review (this is a bare-bones template – make it fancier if you wish, but be sure to address at least the items listed here)
Common PDR Problems ACES Presentation T. Gregory Guzik March 6, 2003.
User notes: –Please use this template to create your Proposal Analysis Review –You may reformat this to fit your design, but make sure you cover the information.
Critical Design Review Team Name University/Institution Team Members Date.
Hy-V.1 Skin Friction Sensor Experiment Presenters: Ryan F. Johnson Mitchell Foral-Systems November 24, 2008 University of Virginia.
User notes: –The purpose of the flight readiness review is to determine if your experiment is ready to fly. If it is not ready – it will not fly –You must.
TREADS Semester Review Dec. 14, Objectives Assess and Communicate Current Design Identify interfaces Approve the System Requirement Specification.
Team Name Final Presentation Team Members Date. User notes –You may reformat to fit your design but make sure you cover the following points –You may.
P16221 – FSAE Shock Dynamometer Preliminary Detailed Design Review November 13, 2015.
Solar Probe Plus A NASA Mission to Touch the Sun March 2015 Instrument Suite Name Presenter's Name.
MNROCK CONCEPTUAL DESIGN REVIEW University of Minnesota William Ung Scott Balaban Bryce Schaefer Tom Thoe 11/3/2008.
2013 CoDR Team Name Conceptual Design Review University/Institution Team Members Date 1.
RockSat-C 2013 FMSTR Full Mission Simulation Report University/Institution Team Members Date.
Notes on this template You may reformat this to fit your design, but make sure you cover the information requested in this template. Presentations should.
2014 CoDR Team Name Conceptual Design Review University/Institution Team Members Date 1.
Preliminary Design Review Metro State College of Denver Matthew Hanley, Daniel Bass 14 November 2008.
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.
2016 PDR Team Name Preliminary Design Review University/Institution Team Members Date 1.
RamRack Conceptual Design Review Colorado State University Zach Glueckert Christopher Reed Timothy Schneider Brendan Sheridan Christina Watanuki Advisor:
RockSat-C 2013 SITR Payload Subsystem Integration and Testing Report University/Institution Team Members Date.
Team Name Preliminary Design Review
Critical Design Review Team Name
Team Name Critical Design Review
Individual Subsystem Testing Report
Team Members Class and Date
Launch Readiness Review
Team Name Conceptual Design Review
Team Name Conceptual Design Review
FRIDAY SLIDES TEMPLATE
Launch Readiness Report West Virginia University
<Your Team # > Your Team Name Here
Project Management Unit #2
Presentation transcript:

Proposal Analysis Review NMSGC Student Launch University/Institution Team Members Date

User Notes –You may reformat this to fit your design, but make sure you cover the information requested in this template. –This template is the barebones of what is needed.

Mission Overview (spend a lot of time here-Multiple Slides) –What is your objective? –What do you expect to prove, discover, or learn from your experiment? –Brief overview of underlying science/theory –What other related research/experimentation has been done in the past? Results? –Mission Requirements

System Requirements (Multiple Slides) -What systems do you have: Microprocessor (PC104) -What requirements do you have for your system. -What requirements does the system have for the subsystems: how do they interface. -You should have quantifiable requirements in this section. -Which requirements are design drivers?

Subsystem Requirements (Multiple Slides) -What subsystems do you have: power, C&DH, thermal, etc. -What requirements do you have for each subsystem. -What requirements do each subsystem impose on each other. -You should have quantifiable requirements in this section. -Power subsystem shall supply 2W to… -Power subsystem shall remain at or above 72 F at all times during the flight. -Which requirements are design drivers?

Block Diagrams (Multiple Slides) -Block Diagrams of each of the major subsystems shall be included. -Use these as visual queues to explain the connections between subsystems -Don’t skimp on details… if there is a power switch or a g-switch, make sure that it is included -This is where you explain the design of you system and how it operates. -NOTE: Some Customers were close to this level at CoDR… others still need to do some work to get here. Your block diagrams and accompanying explanations should leave an engineering audience convinced that your design will work and that you have considered all connections between subsystems.

Schematic/Drawings/Analysis (Multiple Slides) -This section is reserved for electrical schematic and mechanical drawings. -These show the reviewers that you have begun to understand the physical dimensions and the electrical characteristics of the system -Any analysis that has been completed so far shall also be contained in this section. -Computer models -Any component tests or research that may have been completed

Commands and Sensors (Multiple Slides) -This section contains charts that show the flow of data and commands. -What states can your payload be in? -Active, Active/Safe, Idle… etc. -The key items that we are looking for are data flow diagrams and budgets -Memory budgets -How many samples, how long, do you have enough memory? -Where is data stored? -How does the data get there? -What commands queue data acquisition? -General software flow chart for “main” code -Be sure to include sensor specifications -Will they meet your need?

Test Plans (Multiple Slides) -What type of testing can be performed on your payload pre-flight? -What is required to complete testing?: -Support Hardware -Purchase/produce? -Software -Purchase/in-house? -Potential points of failure -Testing/Troubleshooting/Modifications/Re-Testing Schedule

Parts List (Multiple Slides) -MAJOR Components lists -Not at the nut and bolt level… just major hardware that will be purchased or built in house -Lead times (This can make or break a project) -Distributors -Manufacturers -Cost (Don’t forget to consider shipping and tax)

PTS-10 Payload Canister User Guide Compliance (Could be one slide) –Mass, Volume Estimated fraction of allotment vs. assigned fraction –Payload activation? What have you planned for? How does it comply with Wallops “no volt” requirement –Rocket Interface Shorting wires

Shared Can Logistics Plan (Could be one slide) –Institutions/Universities in can –Plan for collaboration on interfacing Know relative locations in can –Especially important for payloads needing ports –Structural interfacing to each other To the top and bottom bulkheads

Management –Updated Organizational Chart –Updated Schedule –Updated mass/monetary budgets

Conclusions –Issues and concerns –Closing remarks