2.Intro_What-is-SE_V1.0.ppt

8/14/2019 2.Intro_What-is-SE_V1.0.ppt

1/30

Space Systems Engineering: Introduction Module

Int roduct ion Module:

What is Sys tems Eng ineer ing?

SpaceSystems Eng ineering , version 1.0


2/30

Space Systems Engineering: Introduction Module 2

Modu le Purpose: What is Systems Eng ineer ing?

Provide some common definitions of systems

engineering in the context of space project

development.

Motivate the need for systems engineering and

demonstrate the consequences of poor systemsengineering.

Describe how systems engineering adds value to

the development of large projects. Develop some common systems engineering

process models and show how they are related.


3/30


What is Systems Engineer ing?

Systems eng ineer ingis a robust approach to the

design, creation, and operation of systems.

The approach consists of:

identification and quantification of system goals creation of alternative system designconcepts performance of designtrades

selection and implementation of the best design verification that the designis properly built and

integrated, and assessment of how well the system meets the goals

This approach is iterative, with several increases in the

resolution of the system baselines (which containrequirements, design details, verification plans and costand performance estimates).

Ares 1


4/30


5/30


There is tremendous potential for wasted effort on

large projects, since their development requires thatmany subsystems be developed in parallel.

Without a clear understanding of what must be done

for each subsystem the development team runs therisk of inconsistent designs, conflicting interfaces orduplication of effort.

Systems engineering provides a systematic,disciplined approach to defining, for each member ofthe development team, what must be done forsuccess.

More Mot ivat ion fo r Systems Engineer ing


6/30


Today Aerospace System Developers Are

Cal l ing Fo r Moreand BetterSystems Engineers

Why?

Trends in the development and design of new spacesystems require more systems engineering.

Large space projects struggle with cost, scheduleand technical performance.

Demographics - aging workforce and skill retention.

New space systems are larger and more complex -requiring a higher percentage of systems engineers.


7/30Space Systems Engineering: Introduction Module 7

Systems Eng ineer ing is The Response to TrendsIn

The Design and Development of New Space Systems

New space systems are more likely to have:

Technology development

A variety of subsystem technical maturities

Consider and reuse existing designs

Consider and incorporate COTS subsystems

Mandated implementations or subsystem vendors

Greater dependence on system models for design decisions

More stakeholders, institutional partners, constraints andambiguity

More customer oversight and non-advocate review System-of-systems requirements

More people - project sizes are growing

Physically distributed design teams



NASA, DOD and Indus try Cal l For

Moreand BetterSystems Engineers

Allof the factors identified by NASA that contributed to programfailure and significant cost overrun are systems engineeringfactors, e.g.,

Inadequate requirements managementPoor systems engineering processesInadequate heritage design analyses in early phasesInadequate systems-level risk management

Reference: NASA, Office of Program Analysis and Evaluation, Systems Engineering and Institutional

Transitions Study, April 5, 2006. Reproduced in National Academies book - Building a Better NASA

Workforce: Meeting the Workforce Needs for the National Vision for Space Exploration.



Systems Eng ineer ing is

Bu i l t on th e Lesson s o f the Past

Systems engineering is a relatively new engineering

discipline that is rapidly growing as systems getlarger and more complex.

Most of the foundations of systems engineering arebuilt on the lessons of past projects.

Recurring mission success is codified in techniquesand guidelines (e.g., the NASA Systems EngineeringHandbook).

Since mission failures are each unique, their lessons

retain their identity.

NASA Lessons Learned Resources:

http://www.appel.nasa.gov/ask/archives/lessons.php

http://pbma.nasa.gov/lessonslearned_main_cid_3

http://ildp1.nasa.gov/offices/oce/llis/home/

http://klabs.org/DEI/lessons_learned/
http://www.appel.nasa.gov/ask/archives/lessons.phphttp://pbma.nasa.gov/lessonslearned_main_cid_3http://ildp1.nasa.gov/offices/oce/llis/home/http://klabs.org/DEI/lessons_learned/http://klabs.org/DEI/lessons_learned/http://ildp1.nasa.gov/offices/oce/llis/home/http://pbma.nasa.gov/lessonslearned_main_cid_3http://www.appel.nasa.gov/ask/archives/lessons.php



Decl in ing Systems Engineer ing Expert ise

Con tr ibu tes to a Spectacu lar Satel l i te Failure

Future Imagery Architecture - FIA - a $5 billion (award) spy satellite systemwas behind schedule and expected costs to complete were $13 billion

over budget.The optical satellite system of FIA was canceled in 2005 after 6 years and

spending more than $4 billion.

(a) factor was a decline of American expertise in systems

engineering, the science and art of managing complex engineeringprojects to weigh risks, gauge feasibility, test components and ensurethat the pieces come together smoothly.NYT, 11/11/07



Pause and Learn Opportun i ty

Pre-assign the class to read the NYT article:FAILURE TO LAUNCH; In Death of Spy Satellite

Program, Lofty Plans and Unrealistic Bids; New YorkTimes, page 1; November 11, 2007; Philip Taubman

Ask the class:

What are the top 10 reasons why the FIA Programfailed?

See notes for additional discussion points.



Defini t ion Phase Investment is Cri t ical to

Managing Cos t Overruns

Total Program Overrun32 NASA Programs

R2

= 0.5206

0

20

40

60

80

100

120140

160

180

200

0 5 10 15 20

Definition Percent of Total Estimate

ProgramOverr

un

Definition $

Definition Percent = ----------------------------------

Target + Definition$

Actual + Definition$

Program Overrun = ----------------------------------

Target + Definition$

GRO76OMV

GALL

IRAS

TDRSS

HST

TETH

LAND76

MARS

MAG

GOES I-M

CEN

ACT

CHA.REC.

SEASAT

DE

UARS

SMM

EDO

ERB77

STS

LAND78

COBE

GRO82

ERB88

VOY

EUVE/EP

ULYS

PIONVENIUE ISEE

HEAO

(Percent)



Most of the NASA project data used for the Werner Gruhl plot aremore than 20 years old.

A study of 40, more recent NASA missions (including those below)showed an average cost growth of 27% and an average schedulegrowth of 22%.

Cost and Schedule Overruns Cont inueto be a Prob lem on Space Projects

DiscoveryNEARLunar ProspectorGenesisMessengerMars PathfinderStardustContourDeep Impact

Mars ExplorationMGSMCO/MPLMERMRO

New MillenniumDS-1EO-1

ExplorerFASTACETRACESWASWIREFUSEIMAGEMAPHESSIGALEXSWIFTHETE-IITHEMIS

Great Observatory Class

SpitzerGravity Probe B

FlagshipEOS-AquaEOS-AuraTRMM

Solar Terrestrial Probe

TIMEDSTEREO

OtherLANDSAT-7SORCEICESAT



Systems Engineer ing Process Models

Begin wi th Reduct ion ism

Reductionism, a fundamental technique of systems

engineering, decomposes complex problems intosmaller, easier to solve problems - divide andconquer is a success strategy.

Systems engineering divides complex development

projects by product and phase. Decomposing a product creates a hierarchy of

progressively smaller pieces; e.g.,

System, Segment, Element, Subsystem, Assembly,Subassembly, Part

Decomposing the development life of a new projectcreates a sequence of defined activities; e.g.,

Need, Specify, Decompose, Design, Integrate, Verify,Operate, Dispose

A T di t i l Vi f th S t E i i



A Tradi t ional View of th e Systems Engineer ing

Process Begins with Requ irements Analysis

Systems Analysis,Optimization & Control

RequirementsAnalysis

FunctionalAllocation

Synthesis/Design

Requirements Loop

Design Loop

Verification Loop

Understand the requirements andhow they affect the way in which

the system must function.

Identify a feasible solutionthat functions in a way thatmeets the requirements

Show that the synthesizeddesign meets all requirements

Measure progress and effectiveness;assess alternatives; manage configuration,

interfaces, data products and program risk


16/30Space Systems Engineering: Introduction Module

The Systems Engineering Vee Model Extends the Traditional

View w ith Expl ic i t Decomposit ion and Integrat ion

MissionRequirements& Priorities

SystemDemonstration& Validation

Develop SystemRequirements &

System Architecture

Allocate Performance

Specs & BuildVerification Plan

DesignComponents

Integrate System &Verify

Performance Specs

Component

Integration &Verification

VerifyComponentPerformance

Fabricate, Assemble,Code &

Procure Parts

Th NASA S t E i i E i Add t



The NASA Systems Engineer ing Engine Adds to

the Vee By Add ing Opt im izat ion and Contro l

Optimization and ControlProcesses 10 - 17



NASA Systems Eng ineer ing EngineNASA Sy stems En gineering Hand boo k SP-6105, 2007

Good Systems Engineer ing Requires



Good Systems Engineer ing Requires

Competency in at Least 3 Domains

The NASA systems engineering engine has 17 processactivities or systems engineering functions for system design,

realization and management.

But good systems engineering alsorequires technical domainand personal attribute competency. This view is captured by theJPL system engineering competency model.

Systems Engineering Functions

Captured by the 17 process activities

Personal Behaviors

Domain Specific Technical Knowledge



What is a System?

Simply stated, a system is an

integrated composite of people,products, and processes that

provide a capability to satisfy a

stated need or objectives.

What are examples of a system in the

aerospace industry?

Personnel

Facilities

Processes

Hardware



Examples of Systems

Space Shuttle Main Engine vs. a collection of parts

Space Shuttle Orbiter with engines and avionics

Space Shuttle Orbiter with solid rocket boosters andexternal fuel tank

Space Transportation System (STS) with payload,launch pad, mission controllers, vehicle assemblyfacilities, trainers and simulators, solid rocket boosterrescue ships

System of Systems

STS + International Space Station + TDRSS communicationsatellites +



Modu le Summary: What is Systems Engineer ing?

Systems engineeringis a robust approach to the design,

creation, and operation of systems.

Systems engineering is a ubiquitous and necessary part of the

development of every space project.

The function of systems engineering is to guide the engineering

of complex systems.

Most space projects struggle keeping to their cost and schedule

plans. Systems engineering helps reduce these risks.

Systems engineering decomposes projects in both the product

and time domain, making smaller problems that are easier tosolve.

System decomposition and subsequent system integration are

foundations of the Vee and the NASA systems engineering

process models.


23/30Space Systems Engineering: Introduction Module

Backup Sl ides

for Introduct ion Module

Supplemental thoughts on Systems Engineering fromvarious sources, as specified in the notes section.



What is Systems Engineer ing?

Systems engineering is an interdisciplinary engineering

management process to evolve and verify an

integrated, life-cycle balanced set of system solutionsthat satisfy customer needs.

Accomplished by integrating 3 major activities:

1. Development phasing that controls the design process andprovides baselines that coordinate design efforts.

2. A systems engineering process that provides a structure forsolving design problems and tracking requirements flow throughthe design effort.

3. Life cycle integration that involves the customers in the designprocess and ensure that the system developed is viablethroughout its life.

The function of systems engineering is to guide the

engineering of complex systems.

Systems Engineering


25/30


Systems Engineering -

Further Considerat ions

Systems engineering is a standardized, dis cip l ined

management processfor development of systemsolutions that provides a constant approach tosystem development in an environment of changeand uncertainty.

It also provides for simultaneous product and processdevelopment, as well as a common bas is fo rcommunica t ion.

Systems engineering ensures that the correcttechn ical tasksget done during developmentthrough planning, tracking and coordinating.


26/30


Systems Eng ineer ing Process

The systems engineering process is a top-down,comprehensive, and iterative problem-solvingprocess, applied through all stages of development,that is used to: Transform needs and requirements into a set of system

product and process descriptions (adding value and more

detail with each level of development) Generate information for decision makers, and

Provide input for the next level of development.

The fundamental systems engineering activities are Requirements analysis

Functional analysis/allocation

Design synthesis


27/30


SystemThe combination of elements that function together to produce thecapability required to meet a need. The elements include all hardware, software,equipment, facilities, personnel, processes, and procedures needed for this purpose.

Systems EngineeringA disciplined approach for the definition, implementation,integration and operation of a system (product or service). The emphasis is onachieving stakeholder functional, physical and operational performance requirementsin the intended use environments over its planned life within cost and scheduleconstraints. Systems engineering includes the engineering processes and technicalmanagement processes that consider the interface relationships across all elementsof the system, other systems or as a part of a larger system.

The discipline of systems engineering uses techniques and tools appropriate for useby any engineer with responsibility for designing a system as defined above. Thatincludes subsystems.

Project ManagementThe process of planning, applying, and controlling the use offunds, personnel, and physical resources to achieve a specific result

Unless specifically noted hereafter we willuse Systems Engineering to refer to the

discipline not the organization.

System , Systems Eng ineering , and Project Management

Common Techn ical Processes to Manage the Techn ical


28/30


Common Techn ical Processes to Manage the Techn ical

Aspect o f the Projec t Life Cyc le - NASA Model ( 7123.1A)

The Systems Engineering Engine


29/30


Systems Engineer ing

The systems engineering discipline shall be applied throughoutthe project life cycle as a comprehensive, iterative technical and

management process to: Translate an operational need into a solution through a systematic, concurrent

approach to integrated design and its related downstream processes

Integrate the technical input of the entire development community and alltechnical disciplines

Ensure the compatibility of all interfaces

Ensure the integration, verification, and validation processes are consideredthroughout the life cycle starting with system concept selection

Identify, characterize and mitigate risks

Provide information for management decisions

Ensure and certify system integrity

With Process Comes


30/30

Interface Control Harness & Connectors Structural connections Software protocols & signal processing

With Process Comes

Systems Engineer ing Pract ices

Acquisition strategies Purchase In-house

Contribution Other

Documentation OrganizationRequirements (!!)Materials ListsCAD drawingsSafety documentsInterface controls

Configuration management

Set up a plan for each ofthese EARLY!

Identify design drivers

CostSchedulePerformance

Execute a risk

management plan

Design Budgets Power Memory/data

Communications Mass $$$ Other resources

Documents

2.Intro_What-is-SE_V1.0.ppt