1 / 6

Design Alternative Week: Mission Requirements and Team Meeting

This week's tasks include analyzing mission requirements, discussing mission architecture, and selecting design alternatives. The team meeting will cover important topics such as the CDR, design freeze requirements, and group name/logo selection.

efuller
Download Presentation

Design Alternative Week: Mission Requirements and Team Meeting

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Week 7 • PDR Updated! • Check the website if you have any mission requirement questions! [Solomon Westerman] [PM]

  2. Week 7 • Design Alternative Week (Last One!) • POC’s: Good job getting analysis done on time • Make a lot of pots! • Don’t let your job description limit you! • Team Meeting • Thursday, 8:30 PM ARMS1021 • Discuss CDR, pick mission architecture, set Design Freeze requirements • Group Name / Logo • Collecting ideas for Thursday’s Meeting • Not necessarily name/logo selection on Thursday

  3. Week 7 • Start collecting your references together • Reference list will be due at time of Rough Draft (Wed. after Spring Break) • Saves you a lot of time/annoyance later • Final report grade • Highly dependent on both quality and quantity • Make sure to document all the analysis you have completed to include in main report or appendix • Your work will NOT go to waste! • Presentations • Make sure you are citing people you work with • You are responsible for making sure the team knows what you are doing • CDR at END OF THIS WEEK • Mission architecture chosen for three payload sizes • Designs should be ~75% maturity and ready to implement • Any major issues with design need to be voiced on/by Thursday’s meeting • Design Freeze in 2.5 weeks (then Spring Break) • Expect fast turn around times on ALL numbers! Be ready! • Final analysis on our designs will be complete before Spring Break • Mass/Power/Volume/Architecture numbers set

  4. Exercise • Write three payload cases on Board • Just a test, no decisions just yet • List design alternatives considered for each phase (should be short for TLI, longer for Landing / Locomotion) • Discuss Launch/Purchase/Integration cost • Need overall system mass and costs and complexity numbers for each phase • Any conflicts with mission requirements? Any problems with the system in general?

  5. Future Structure • Integration manager for each payload size • Responsible for all mass, power, volume, etc. bookkeeping • Need to have a big picture overview of your payload size • Attend phase group meetings • Go-to person for up to date numbers, actively getting numbers from team • Expert on mission architecture for your payload size • Different from Structures role of designing for volume constraints • Very active role • Need one or two people (Talk to me if interested, will begin role after Thursday’s meeting)

More Related