2013 dr / istr team name design review (dr) & individual subsystem test review (istr)...

59
2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1

Upload: penelope-erika-daniels

Post on 05-Jan-2016

227 views

Category:

Documents


4 download

TRANSCRIPT

Page 1: 2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1

2013

DR / ISTR

Team NameDesign Review (DR)

& Individual Subsystem Test Review (ISTR)

University/InstitutionTeam Members

Date

1

Page 2: 2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1

2013

DR / ISTR

Deliverables

• In addition to this presentation, each school must include the following by February 18th:

• FINAL Mechanical drawings in pdf format• FINAL Electrical schematics in pdf format• FINAL Signed copies of the Power and Telemetry

ICDs in pdf format• UPDATED Power Budget in xls format• FINAL Pin Assignments in xls format• FINAL Timer Event matrix in xls format• Be sure to place all these files, including your ppt

presentation in your DropBox Pony Express folder by COB on February 18th, 2013

2

Page 3: 2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1

2013

DR / ISTR

User Notes

• You may reformat this to fit your design, but you must cover all the information requested on the following slides

• This template contains all of the information you are required to convey at this point in the project. If you have questions, please contact me directly:

[email protected] or 303-492-4750

3

Page 4: 2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1

2013

DR / ISTR

Purpose of DR/ISTR

PLEASE READ:

For RS-X 2013, I am combining details needed for the DR at Wallops in March with the ISTR review. I am doing this because even after Post-CDR, I still do not have a clear understanding of each team’s final design. The purpose of the DR with Wallops is to capture the final design of both the rocket systems and the payloads (you) that are going to fly. The purpose of the ISTR is for me to understand how much of your design is built and how much of your design is tested. During RS-X 2012, each team had to complete a second ISTR before moving onto their Full System Test Review, where all subsystems have been tested and are now being tested together as a system. This review is scheduled to take place around March 18th, one month after this review. YOU MUST ADDRESS AND FOLLOW EVERY ASPECT OF THIS TEMPLATE DURING YOUR TEAM’S REVIEW THE WEEK OF FEBRUARY 18th. PLEASE CONTACT ME IF YOU HAVE ANY QUESTIONS

4

Page 5: 2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1

2013

DR / ISTR

Presentation Outline

5

• Section 1: Mission Overview• Section 2: Final Design Description• Section 3: Project Management Update• Section 4: Hardware Procurement Status• Section 5: Individual Subsystem Testing

Results• Section 6: Full System Testing Plan• Section 7: User Guide Compliance

Page 6: 2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1

2013

DR / ISTR

1.0 Mission OverviewName of Presenter

6

Page 7: 2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1

2013

DR / ISTR

Mission Overview

• Mission statement• What do you expect to discover or

prove?• Who will this benefit and/or what will

your data be used for?

7

Page 8: 2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1

2013

DR / ISTR

Success Criteria:

– Define Minimum Success: What is the least amount of data you can collect that will still constitute a success?

– Comprehensive Success: Under ideal conditions, what would constitute comprehensive mission success?

8

Page 9: 2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1

2013

DR / ISTR

Concept of Operations

• Based on science objectives, describe what the payload will be doing during flight and highlights areas of interest

• Include all significant events during your flight• RS-X 2012 Mission timeline included on following

slide for guidance• You may used the example on following slide

updated with your mission events• Complete your Timer Events Matrix in xls format

and submit• Update the the table on the next slide of this

template

9

Page 10: 2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1

2013

DR / ISTR

Concept of Operations

10

Event Time On Dwell Event Description

GSE 1 T-180 sec 540 sec Minutes before launch. Start on the computer for the experiments.

GSE 2 T-180 sec 540 sec Minutes before launch. Start on the computer for the experiments.

TE-NR 1 T+000 sec 360 sec Launch

TE-NR 2 T+000 sec 360 sec Bring more power to RGA's.

TE-NR 3 T+000 sec 360 sec Bring more power to RGA's.

TE-R T+000 sec 360 sec Bring more power to RGA's.

• Example of Timer Events Matrix for presentation• Update this for your presentation as it applies to your team

Page 11: 2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1

2013

DR / ISTR

Example ConOps

t ≈ ???

Altitude: ?? km

Event A Occurs

t ≈ 876 sec

Splash Down

t ≈ ???

Altitude: ?? km

Event B Occurs

-G switch triggered

-All systems on

-Begin data collection

t = 0 min

t ≈ ???

Altitude: ?? km

Event C OccursApogee

t ≈ 199.7 sec

Altitude: ≈153 km

End of Malemute Burn

t ≈ 28.7 sec

Altitude: 17.2 km

t ≈ ???

Altitude: ?? km

Event D Occurs

Altitude

t ≈ 454.9 sec

Chute Deploys

Page 12: 2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1

2013

DR / ISTR

Concept of Operations

12

Page 13: 2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1

2013

DR / ISTR

- Please confirm your mounting location

Payload Location

Page 14: 2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1

2013

DR / ISTR

2.0 Final Design DescriptionName of Presenter

14

Page 15: 2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1

2013

DR / ISTR

Functional Block Diagram:

• FINAL Functional block diagram– Show all major and minor subsystems and

how they are interconnected– Show voltage levels and data lines– Show all power and data storage– Show mechanical and electrical inhibits– Show Wallops interface (power/telemetry)

• Example on following slide • I will spend a lot of time on this diagram with

each team and it will be referred to all the way up until launch so make it good

15

Page 16: 2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1

2013

DR / ISTR

Example Functional Block Diagram

Page 17: 2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1

2013

DR / ISTR

Example Functional Block Diagram

Page 18: 2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1

2013

DR / ISTR

Mechanical Design:

18

• Present your FINAL mechanical design

• Many views of your solid models (labeled)• These will be used for your pre-launch inspection by

Wallops personnel in June/August• Shared decks must also include views of solid models

for integrated, shared deck• Updated Mass Budget• List of materials used in mechanical design• Dimensioned drawings are not required in

presentation but are required as a deliverable (see slide 2 above)

• Address any Hazardous Mechanical items

Page 19: 2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1

2013

DR / ISTR

Example of Views

30

Page 20: 2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1

2013

DR / ISTR

Example of Views

30

Nitric Oxide Sensor

Piezo Dust Detector

S-Bar Release Mechanism

Waterproof Aluminum Box (without sides)

Ballast Plate

NASA Payload Plate

Page 21: 2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1

2013

DR / ISTR

Example of Views

30

Post Amp Boards Femto Amplifier

Transceiver

Memsense IMU VectorNav IMU

Power Board

Data Loggers

Page 22: 2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1

2013

DR / ISTR

Example of Views

30

Page 23: 2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1

2013

DR / ISTR

Detailed Mass Budget

23

ExampleSat Mass BudgetSubsystem Total Mass (lbf)

STR 2DEP 8EPS 12PM 9… … … … Total 31Over/Under (1.00)

• Present your subsystem masses and total mass similar to what is given at right.

• Mass of plate is 3.425 pounds

• Show how you meet your 30 pound requirement

Page 24: 2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1

2013

DR / ISTR

Materials List:

24

• Detail all materials used in your design• May use a table to capture this information• Capture all materials used in mission (i.e.

aerogel, 6061 Aluminum, etc)• Types of bolts, nuts, washers, etc (i.e. stainless

bolts)

Page 25: 2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1

2013

DR / ISTR

Hazardous Mechanical Items:

25

• Identify all materials that may be considered hazardous

• Identify all mechanical operations that may be considered hazardous (stored energy, deployments, etc)

• Identify all mechanical components that may hazardous or interfere with other payloads or rocket systems (magnets, transmitters, items that change your CG or MOI during the flight)

Page 26: 2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1

2013

DR / ISTR

Electrical Design:

26

• Present your FINAL Electrical Design• Include all electrical schematics • Include Updated Power Budget• Include Updated Pin Assignments• Identify any high voltage components• Identify any hazardous electrical items in your

design

Page 27: 2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1

2013

DR / ISTR

Example Electrical Schematics

27

Page 28: 2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1

2013

DR / ISTR

Example Electrical Schematics

28

Page 29: 2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1

2013

DR / ISTR

Example Electrical Schematics

29

Page 30: 2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1

2013

DR / ISTR

Example Electrical Schematics

30

Page 31: 2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1

2013

DR / ISTR

Updated Power Budget

31

• USE Power Budget xls file• Include a screenshot in your presentation and the actual excel file with

your CDR package• I am most interested in total amp-hours since each payload space is

allowed 1 Ah. • Voltages and currents should also be included.

ExampleSat Power BudgetSubsystem Voltage (V) Current (A) Time On (min) Amp-Hours

STR 0 0 0 0.000DEP 12 0.4 2 0.013EPS 28 0.3 20 0.100PM 28 0.9 8 0.120… … … …

Total (A*hr): 0.233Over/Under 0.77

Page 32: 2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1

2013

DR / ISTR

Pin Assignments: Power

32

Power Connector--Customer SidePin Function1 2 3 4 5 6 7 8 9

10 11 12 13 14 15

• USE Pin Assignment xls file• Include a screenshot in your

presentation and the actual excel file with your CDR package

• Fill-in the function side for your payload

• Check for consistency with User’s Guide

Page 33: 2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1

2013

DR / ISTR

Pin Assignments: Telemetry

33

• USE Pin Assignment ICD xls file

• Fill-in the function side for your payload

• Include a screenshot in your presentation and the actual excel file with your CDR package

• Check for consistency with User’s Guide

Telemetry Connector--Customer SidePin Function Pin Function

1 20 2 21 3 22 4 23 5 24 6 25 7 26 8 27 9 28

10 29 11 30 12 31 13 32 14 33 15 34 16 35 17 36 18 37 19

Page 34: 2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1

2013

DR / ISTR

Hazardous Electrical Items:

34

• Identify any high voltage items/components• Identify any operational hazards with your electrical

design

Page 35: 2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1

2013

DR / ISTR

Software Design:

35

• Give me a brief overview of your software design

• Software Flow Diagram must be included• Could include State diagrams• Could include function overviews

(input/output)

Page 36: 2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1

2013

DR / ISTR

Example Software Flow Diagram:

36

Begin collecting data from sensors

Rocket casing

off?

Extend linear actuator

Reached 95 km?

Data from proximity

sensor

Altimetry data from pressure sensor

Altimetry data from pressure sensor

Reached 95 km?

No

Yes

No

No

Yes

Yes

Retract linear

actuator

Arduino ProArduino Pro

Page 37: 2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1

2013

DR / ISTR

De-Scopes and Off-Ramps

37

• If there are portions of your project with lots of risk, do you have “off-ramps” in case you run into schedule/budget constraints?

• Describe these “De-Scopes” and “off-ramps” that may be used in the future

Page 38: 2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1

2013

DR / ISTR

3.0 Project Management Update

Name of Presenter

38

Page 39: 2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1

2013

DR / ISTR

Project Management Update:

• Include Team Picture• Updated org chart• Updated schedule

– Include details leading up to the June 18th testing in Virginia

• Biggest Worries and Concerns Slide

39

Page 40: 2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1

2013

DR / ISTR

Example Team Picture

40

Page 41: 2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1

2013

DR / ISTR

Example Organizational Chart

41

Project ManagerMarie Hepfer

Lead System Engineer + Aerogel

ScienceChris Mogni

OrganizationJHU EPS Department

Faculty AdvisorDarren Waugh

OrganizationJHU APL

MentorsEthan Miller

Jonnathan Fenske

Aerogel ScienceNick Lybarger

GPS Team LeadKrysti Papadopoulos

Aerogel Build LeadLauren Powers

Lead Aerogel Engineer

Kristy Webber

GPS Aerospace Engineer

Brianna Brassard Aerogel Aerospace Engineer

Mazi Wallace

Systems Engineer + Lead Electrical

EngineerCorrie Russell

Page 42: 2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1

2013

DR / ISTR

Example Schedule

42

12/11/2012 Critical Design Review (CDR) Teleconference12/15/2012 Post CDR Action Item Generation1/18/2013 Final Down Select—Flights AwardedTBA Wallops DR01/28/2013 Post CDR Action Item Review02/18/2013 First Installment Due02/18/2013 Individual Subsystem Testing Reports Due02/19/2013 Individual Subsystem Testing Reports Teleconference02/25/2013 Experiment Decks and Connectors Sent To Customers03/18/2013 Payload Subsystem Integration and Testing Report Due03/19/2012 Payload Subsystem Integration and Testing Report Teleconference04/08/2013 Final Installment Due04/15/2013 First DITL Test Report Due04/16/2012 DITL 1 Teleconferences05/06/2013 Weekly Teleconferences Begin05/13/2013 Weekly Teleconference 105/13/2013 Second DITL Test Report Due05/14/2013 Weekly Teleconference 2 (2nd DITL Presentations)05/20/2013 Weekly Teleconference 305/27/2013 Weekly Teleconference 4 (Travel Logistics)06/03/2013 Integration Readiness Review Packages (IRR) Due06/04/2013 Integration Readiness Review Telecons with Wallops06/18/2013 GSE Checkouts At Refuge

06/19>24/2013Testing and Environmental With Wallops

07/01/2013 Weekly Teleconferences Resume07/22/2013 Launch Readiness Review Packages (LRR) Due

07/23/2013Launch Readiness Review Telecons with Wallops

08/01/2013 GSE Checkouts at Refuge Inn08/02>07/2013 Final Integration at Wallops08/08/2013 LAUNCH08/09/2013 Contingency Launch

Page 43: 2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1

2013

DR / ISTR

Worries and Concerns

43

• List your biggest worries and concerns related to you project at this moment

• Discuss your plans for mitigating these items

Page 44: 2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1

2013

DR / ISTR

4.0 Hardware Procurement Status

Name of Presenter

44

Page 45: 2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1

2013

DR / ISTR

Mechanical Elements

45

• What has been manufactured/purchased?

• What has not been manufactured/purchased?

Page 46: 2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1

2013

DR / ISTR

Electrical Elements

46

• What has been manufactured/solderd?• What still needs to be

manufactured/soldered?• PCB revision status? • What electrical components are in

house? • What electrical components still need to

be procured?

Page 47: 2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1

2013

DR / ISTR

Software Elements

47

• What discrete blocks of code are completed?•Recommend refer to your software

flow diagram above

Page 48: 2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1

2013

DR / ISTR

5.0 Individual Subsystem Testing Results

Name of Presenter

48

Page 49: 2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1

2013

DR / ISTR

Subsystem Review

49

• List all the subsystems in your payload• Must match subsystems called out in your

Functional Block Diagram above• You MUST use slides 50, 51, and 52 for each of

the subsystems listed above• Don’t forget to discuss your software

Page 50: 2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1

2013

DR / ISTR

Subsystem Name

50

• Quick Status– What is complete/what has been tested?– What has not yet been checked out

• Be honest because we all know things happen

• Pictures!

USE these 3 slides fo

r each subsystem

Page 51: 2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1

2013

DR / ISTR

Subsystem Name

51

• What tests were completed?• Pictures!

USE these 3 slides fo

r each subsystem

Page 52: 2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1

2013

DR / ISTR

Subsystem Name

52

• What were the results– Show data, interpret success/failure

of the tests

• Data!• Pictures!

USE these 3 slides fo

r each subsystem

Page 53: 2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1

2013

DR / ISTR

6.0 Plan for Full System Testing

Name of Presenter

53

Page 54: 2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1

2013

DR / ISTR

Full System Testing Plan

54

• Based on where you are now, what is your team’s plan to ensure the subsystems discussed in Section 5 of this presentation will be integrated and tested for the Full Systems Testing Review in March?

• What are the major hurdles doing to be?• Would you like to hold a second ISTR in

March?• Would you like to delay your FSTR until

April?

Page 55: 2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1

2013

DR / ISTR

7.0 User Guide ComplianceName of Presenter

55

Page 56: 2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1

2013

DR / ISTR

User Guide Compliance

56

• Use the following example to show your compliance with the RS-X 2013 User’s Guide

• Teams that are sharing, please fill out your school’s compliance only

Page 57: 2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1

2013

DR / ISTR

User Guide Compliance

57

Requirement Status/Reason (if needed)Center of gravity in 1" plane of

plate?1.2" currently

Max Height < 12"

Within Keep-Out

Using < 10 A/D Lines

Using/Understand Parallel Line Not Being Utilized

Using/Understand Asynchronous Line

9600 Baud

Using X GSE Line(s) 1 (per requirement)

Using X Redundant Power Lines 1 (per requirement)

Using X Non-Redundant Power Lines

2 (one extra)

Using < 1 Ah 1.1 (working on reducing)

Using <= 28 V 200 V (Will conformal coat)

Page 58: 2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1

2013

DR / ISTR

Sharing Logistics

58

• Update on collaboration– Want to see an integrated model of both teams on

one deck– Want to see plan for integration of two payloads in

June– Want to hear about who is machining mounting

holes for each school– Want to understand how this work will be verified

before arriving in June.• Discuss how regular meeting/communication is

occurring between sharing schools

Page 59: 2013 DR / ISTR Team Name Design Review (DR) & Individual Subsystem Test Review (ISTR) University/Institution Team Members Date 1

2013

DR / ISTR

• Please list questions and concerns you would like to discuss

Conclusion

59