treads semester review dec. 14, 2007. objectives assess and communicate current design identify...

11
TREADS Semester Review Dec. 14, 2007

Upload: lorraine-skinner

Post on 04-Jan-2016

212 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: TREADS Semester Review Dec. 14, 2007. Objectives Assess and Communicate Current Design Identify interfaces Approve the System Requirement Specification

TREADSSemester Review

Dec. 14, 2007

Page 2: TREADS Semester Review Dec. 14, 2007. Objectives Assess and Communicate Current Design Identify interfaces Approve the System Requirement Specification

Objectives• Assess and Communicate Current Design

• Identify interfaces

• Approve the System Requirement Specification

• Formalize the design

• Obtain approval to purchase parts and begin assembly

Page 3: TREADS Semester Review Dec. 14, 2007. Objectives Assess and Communicate Current Design Identify interfaces Approve the System Requirement Specification

Agenda

• Mission Concept of Operations

• Subsystem Briefs– Structures

• Design, Analysis. Vibration Analysis

– Thermal Analysis– DIB/SMB– Power System

• Architecture, Power Budget

– Communications

• Schedule

Page 4: TREADS Semester Review Dec. 14, 2007. Objectives Assess and Communicate Current Design Identify interfaces Approve the System Requirement Specification

Mission Statement• Provide mission Objectives

• Why are you doing this?

• At a high level, how will you do this.

• What are you major mission requirements or limitations

Page 5: TREADS Semester Review Dec. 14, 2007. Objectives Assess and Communicate Current Design Identify interfaces Approve the System Requirement Specification

Falcon 1 User’s Guide, SpaceX

Launch TREADS Operations (1 Year)

Concept of Operations

Page 6: TREADS Semester Review Dec. 14, 2007. Objectives Assess and Communicate Current Design Identify interfaces Approve the System Requirement Specification

Ground Ops S/C Ops

LV Activities

Laun

chP

rimar

y P

aylo

adR

elea

se

TRE

AD

S P

ower

On

Sec

onda

ry P

aylo

adR

elea

seTe

rtiar

y P

aylo

adR

elea

se

Mis

sion

Sta

rtFC

Boo

t Up

Sys

tem

Che

ckou

t

Exec. DUT Test(s)

Data Downlink

Charge Batteries

Customer Feedback

Exec. ScheduleSchedule Uplink

Nominal Timeline

Nom

inal

Ope

ratio

ns

Firs

t Gro

und

Con

tact

Page 7: TREADS Semester Review Dec. 14, 2007. Objectives Assess and Communicate Current Design Identify interfaces Approve the System Requirement Specification

System Level Review• Functional Block Diagram Examples

• Major System level capabilities and requirements.

• Give enough context for the sub-system sections to make sense.

• Full System review at the end– Mass, Volume…..

Page 8: TREADS Semester Review Dec. 14, 2007. Objectives Assess and Communicate Current Design Identify interfaces Approve the System Requirement Specification

•List major requirements and capabilities.

•List major components.

•List major concerns.

Sub Systems Review

Page 9: TREADS Semester Review Dec. 14, 2007. Objectives Assess and Communicate Current Design Identify interfaces Approve the System Requirement Specification

•Total System Level requirement Compliance

•Power, Mass, Volume

Systems Review

Page 10: TREADS Semester Review Dec. 14, 2007. Objectives Assess and Communicate Current Design Identify interfaces Approve the System Requirement Specification

Mass budget Mass(kg)

Test Flight box (box design to accommodate 4 C6713) 3.54 DUTs 2Flight computer 0.5Heater, screws, bolts etc.. 1

Comm box 3Antenna 1RF feed to antenna 0.2antenna deployment structure 2Power 1.5Power board 0.3Batteries 1.3Solar pannels (18.7*19in) 2Wiring harness 1Total 19.3Margin 3.86Total 23.16

Acceptable Mass Budget

Page 11: TREADS Semester Review Dec. 14, 2007. Objectives Assess and Communicate Current Design Identify interfaces Approve the System Requirement Specification

Electronics Risks

5

PW3

4

COMM1 PW2

3

DIB1

2

ASS1SMB1, PW1

1

1 2 3 4 5

Severity

Likelihood

Subsystem Severity Rating Likelihood Rating Risk Rating DescriptionSMB1 5 1 5 SMB does not work/irreparable damagePW1 5 2 10 Not enough power to last the night (<6W)PW2 4 1 4 power system cannot supply power due to component failure due to reasons other than radiationPW3 5 2 10 battery failure DIB1 3 3 9 DIB failure!

COMM1 4 3 12 see note 1ASS1 2 2 4 component lead time is high and/or cost very high

Risks

12345

12345 > 90% Certain

Very rare, < 25% Certain> 25% Certain> 50 % Certain> 75% Certain

Significant reduction in capabilityMay cause mission failure

Mission-killer: cannot complete mission

Likelihood*

ScalesSeverity

Minimal, will not jepardize missionMay delay mission success