Академический Документы
Профессиональный Документы
Культура Документы
One View of the Architecture - The Product Breakdown Structure The framework and interrelationships of elements of a system. Typically illustrated by both a pictorial and a decomposition diagram depicting the segments and elements and their interfaces and interrelationships.
Architecture is described by the System Hierarchy or Product Breakdown Structure (PBS)
Examples
Needs + Objectives + Operation of Everything Necessary to Meet the Objectives Total System = Spacecraft + Launch Vehicle + Ground Support Equipment + Communications Systems (TDRSS, etc.) + NASCOM + POC + Science Data Center + ...+ Personnel Flight = Spacecraft Bus + Instruments + Launch Vehicle +... Spacecraft = Structure + Power + C&DH + Thermal + ... Power = Solar Arrays + Electronics + Battery + Fuses + ... Solar Arrays = Solar Cells + Interconnects + Cover Glass + ... Solar Cells
* Any given system can be organized into a hierarchy composed of segments and/or
elements of succeedingly lower and less complex levels, which may in themselves be termed systems by their designers. In order to avoid misunderstandings, hierarchical levels for a given mission must be defined early.
System
Segment
Element
Subsystem
11
System Subsystem A Subsystem B Subsystem C Management Systems Engineering Integration, Test & Verification Logistics Support
PBS
The Product Breakdown Structure shows the components from which the system was formed. The PBS reflects the work to produce the individual system components.
The Work Breakdown Structure shows all work components necessary to produce a complete system. The WBS reflects the work to integrate the components into a system.
WBS
Space Systems Engineering: System Hierarchy Module 12
Work Breakdown Structure (WBS) A Work Breakdown System (WBS) is used for:
Task or work package planning and scheduling Cost estimating or budget formulation Product development documentation, e.g., documentation tree, systems engineering management plan (SEMP), drawings Project status reporting and assessment
Flight Development
Project
Systems
Science /
Payload(s)
Management
Engineering
Assurance
Technology
Spacecr aft06
Aircraft / Spacecraft 05 06
Mission
Operations
01
02
03
04
07
Launch Vehicle /
Ground
Systems Integration
Education and
Services
System(s)
& Testing
Public Outreach
08
09
10
11
14
T e le s c o p e E le m e n t
T e le s c o p e S u b s y s te m c tro n ic s S u b s y s te m E le
WBS
S ofia Project M anagem ent S ystem s Engineering Project O perations Integration & and Logistics Test Planning S cience S upport M ission Assurance O bservatory S ystem G round S upport S ystem
15
View the James Webb Space Telescope (JWST) WBS & Dictionary Baseline document for example implementation.
(JWST WBS & Dictionary (Baseline).pdf)
The work breakdown structure (WBS) extends the PBS in that it captures all of the work necessary for a project by adding the non-product work necessary for a successful project (e.g., integration, test, logistics support, systems engineering and management).
Space Systems Engineering: System Hierarchy Module 18
20
21
22
23
Planetary Protection 02.06 Launch Sys Eng 02.07 Project V&V 02.08
Telecomm Subsys 06.05 Mechanical Subsys 06.06 Thermal Subsys 06.07 Propulsion Subsys 06.08 GN&C Subsys 06.09 Spacecraft Flt SW 06.10 Testbeds 06.11 Spacecraft assembly test & verification 06.12
24
Error 1: Functions without products. The WBS describes functions not products. This makes the project manager the only one formally responsible for products.
26
27
Examples:
Exploration Systems (see next chart)
30
Level 1
NASA Headquarters Exploration Systems Mission Directorate Washington, DC Constellation Program Office Johnson Space Center (JSC) Houston, TX CEV/Orion Project Office JSC Houston, TX Prime Contractor Lockheed-Martin National Subcontractor National Ares 1 Launch Vehicle Project Office MSFC Huntsville, AL Launch Systems Project Office KSC Florida
Level 2
Level 3
Level 4
Suppliers National
Example for NASA human spaceflight effort. Reflects derivation of authority from HQ to Program to Projects. Requirements flow in same top-down direction.
31
32
Deputies
Vertical Integration
Burt Laws/ Steve Meacham (M)/ Renee Cox (M) Level I & Level 3 Projects
Steve Meacham (M) -Technical Mgr Integ. MSFC* Jerry Hill (M) - Ares 1-X SE&I Interface & SERP Rep
Technical Staff
PSE Office CoST/CxAT Focal - John Baker (M) Chief Architect: Bret Drake** Verification: John Kennedy SIP/Time Phased Capability: Keith Williams Avionics & SW: Jeff Stephenson
CxAT
ZF211
ZF311
ZF411
ZF511
PTI Forum
CSCP/M&SWG DSILWG
AWG
RICWG
* = Technical Mgr for all MSFC Level II Program SEI activities in support of SE Office Chiefs. ** = Post LAT 2 Team Assignment M = Matrixed A = Acting In these Numbers: C = Contractor Partial funding provided by NASA HQ & some Procurement S (converted to Eps here) ALL to be scrubbed as apart of Pending PPBE/ITA revision
33