Content

Course introduction

1 s Lecturer information

System Engineering 2 Course introduction

3 Course learning outcome

4 Assessment

Lecturer: PHAN THỊ MAI HÀ

Department of Industrial Systems Engineering 5 Textbook

08 / 2022 2

Introduction General information System Engineering Introduction General information System Engineering

Lecturer – Phan Thi Mai Ha REMIND

◆Industrial Engineering is concerned with the design,
◆ Bachelor – Industrial Management (1995 – 2000) – HCMUT improvement and installation of integrated system of
◆ Master – Industrial Engineering (2000 – 2001) – Asian Institute of men, materials and equipment. It draws upon
Technology (AIT), Thailand specialized knowledge and skills in the mathematical,
physical sciences together with the principles and
◆ PhD – Industrial Engineering (2010 – 2015), Logistics System Lab
methods of engineering analysis and design to specify,
– Pusan National University (PNU), Korea predict and evaluate the results to be obtained from
◆ Lecturer in Department of Industrial Systems Engineering – 1/2002 such system (American Institute of Industrial Engineers)
◆ Email: ptmaiha@hcmut.edu.vn ◆Logistics and Supply Chain Management (https://ww
w.supplychainopz.com/2012/04/what-is-logistics-and-
◆ And you?
supply-chain-management.html)

4
3
 Introduction General information System Engineering Introduction General information System Engineering

Course introduction Course learning outcomes

Course SYSTEM ENGINEERING ◆ Explain and give examples about fundamental concepts, processes of system engineering
◼ L.O.1.1 Explain basic concepts of system engineering.
Credit 3 ◼ L.O.1.2 Explain system engineering life cycle
Hours 45 ◼ L.O.1.3 Explain system engineering process.
◆ Apply tools, techniques to conceive, design a system or solve problems related to system
◆Engineering? Engineering is the use of scientific principles to design and build engineering
◼ L.O.2.1 Demonstrate system thinking
machines, structures, and other items. The discipline of engineering encompasses a broad range
◼ L.O.2.2 Apply the system engineering process to analyze and design manufacturing or service system.
of more specialized fields of engineering, each with a more specific emphasis on particular areas ◼ L.O.2.3 Apply tools to analyze and integrate system.
of applied mathematics, applied science, and types of application. (Wikipedia) ◼ L.O.2.4 Develop system engineering management plan.
◆ Demonstrate effectively team work skill
◆System? A system is a group of interacting or interrelated elements that act according to a
◼ L.O.3.1 Demonstrate the team forming and development skills
set of rules to form a unified whole.[1] A system, surrounded and influenced by its environment, is ◼ L.O.3.2 Demonstrate the team work assessing skills

described by its boundaries, structure and purpose and expressed in its functioning. Systems are ◆ Demonstrate the effective communication skill
◼ L.O.4.1 Demonstrate the ability in reading English material.
the subjects of study of systems theory. (Wikipedia) ◼ L.O.4.2 Show ability to make presentation

◆System engineering? ◼ L.O.4.3 Show ability to write technical report.

5 6

Introduction General information System Engineering Introduction General information System Engineering

Assessment Course content

Week Chapter Content
Assessment Percent
Introduce lecturer, course, course learning outcome, assessment, …
1 0
Midterm 0%
1, 2 1 System engineering
Exercise 10% 3 2 Need analysis

Term project 30% 4 3 Need analysis tools

5,6 4 Conceptual system design

Quizzes 10%
7,8 5 Preliminary system design
Final exam 50%
9 6 Detail design

10 8 Verification & validation)

10 9 System engineering management

11,12 x Term project presentation

7 8
 Introduction General information System Engineering Introduction General information System Engineering

Textbook Team work

◆ A. Kossiakoff, W.N. Sweet, Systems Engineering: ◆ Technical: Think – pair – share
◆ Clear team role:
Principles and Practice, John Wiley, New York, 2003.
◼ Team leader – planner
◆ Blanchard Fabrycky, Systems Engineering and Analysis, ◼ Presenter
◼ Time keeper
Pearson, 2014
◼ Facilitator
◆ Hồ Thanh Phong, Nguyễn Tuấn Anh, Kỹ Thuật Hệ Thống, NX ◼ Note taker – team activity diary/log

B Đại học Quốc Gia Tp.HCM. ◆ Discussion – Note – Present for task “Is this system”: 15 mins
◆ Using: Team google meet, Zalo group, Facebook,…
◆ Video files
◆ Weakly Report/Presentation file

Introduction General information System Engineering Introduction General information System Engineering

What is system? What is system?

◆ Is this system? Why? ◆ Is this system? Why?

internet

internet
 Introduction General information System Engineering

What is system?
◆ Is this system? Why?

www.hcmut.edu.vn
 9/6/2021 9/6/2021

System System Engineering System Structure System Development Process

Chapter 1 REMIND
• Industrial Engineering is concerned with the design,
improvement and installation of integrated system of
men, materials and equipment. It draws upon
SYSTEM ENGINEERING specialized knowledge and skills in the mathematical,
physical sciences together with the principles and
methods of engineering analysis and design to
specify, predict and evaluate the results to be
obtained from such system (American Institute of
Instructor: PHAN THỊ MAI HÀ Industrial Engineers)

3
08 / 2021

System System Engineering System Structure System Development Process

CONTENT 1. System definitions and elements
System • A combination of interacting elements organized to achieved
1. System definitions and elements one or more stated purposes.
2. Classification of systems • An integrated set of elements, subsystems, or assemblies that
3. Science and systems science accomplish a defined objective. These elements include
4. Technology and technical systems products (hardware, software, firmware), processes, people,
5. Transition to the systems age information, techniques, facilities, services, and other support
System engineering elements.
6. Engineered system (Source: INCOSE Handbook)
7. System life-cycle engineering
INCOSE: International Council on Systems Engineering
8. The system engineering process
9. System design considerations • Systems include physical elements and have useful purposes;
10. System synthesis, analysis and evaluation associated with all kinds of products, structures, and services,
11. Implementing systems engineering as well as those that consist of a coordinated body of methods
or a complex scheme or plan of procedure..
2 4

1 2
 9/6/2021 9/6/2021

System System Engineering System Structure System Development Process System System Engineering System Structure System Development Process

1. System definitions and elements 1. System definitions and elements

Element of a System System - the set of components
• Component • The properties and behavior of each component of the set
have an effect on the properties and behavior of the set as
• Attribute: properties (characteristics, configuration, a whole.
qualities, powers, constraints, and state) of the • The properties and behavior of each component of the set
components and of the system as a whole depend on the properties and behavior of at least one
• Relationships other component in the set.
The state: situation (condition and location) at a point in • Each possible subset of components meets the two
requirements listed above; the components cannot be
time of the system, or of a system component, with
divided into independent subsets.
regard to its attributes and relationships

System System Engineering System Structure System Development Process System System Engineering System Structure System Development Process

1. System definitions and elements 1. System definitions and elements

System System - the set of components
• Process – objectives, purposes • structural components: static parts;
• operating components: perform the processing;
• Function: purposeful activity
• flow components: the material, energy, or information
• Attribute (characteristic, quality, configuration, being altered.
power, constraint, state,…)

Process:
Input Conversion operation Output
Add more value

3 4
 9/6/2021 9/6/2021

System System Engineering System Structure System Development Process System System Engineering System Structure System Development Process

Is this system? Why? Team work

Choose one system, define
1. Purpose/Mission of system
2. Process, function, attribute of system
3. Environment
4. Components: structure, operation, flow
5. Relationship between components
6. System problem – need to design?

9 11

System System Engineering System Structure System Development Process System System Engineering System Structure System Development Process

1. System definitions and elements 2. Classification of systems

Mission • Natural and Human-Made Systems:
– Natural systems: natural processes - high degree of order and
Users SYSTEM equilibrium (the seasons, the food chain, the water cycle,…);
no dead ends, no wastes, only continual recirculation and
Sub Border
System
regeneration

Sub System
– Human-made systems: human beings have intervened through
components, attributes, and relationships.
Sub
System – A human-modified system is a natural system into which a
human-made system has been integrated as a subsystem; led to
Stakeholders/ ENVIRONMENT a better solution
Constituents
10 12

5 6
 9/6/2021 9/6/2021

System System Engineering System Structure System Development Process System System Engineering System Structure System Development Process

2. Classification of systems 2. Classification of systems

• Physical and Conceptual Systems: • Closed and Open Systems:
– Physical systems: manifest themselves in physical form – composed of real – A closed system: no interact significantly with its environment.
components The environment provides only a context for the system
– Conceptual systems: symbols represent the attributes of components – (chemical equilibrium) - one-to-one correspondence between
Ideas, plans, concepts, and hypotheses are examples of conceptual systems. initial and final states
A proposed physical system: may be simulated in the abstract by a – An open system: allows information, energy, and matter to
mathematical or other conceptual model. Conceptual systems often play an cross its boundaries; interact with their environment (plants,
essential role in the operation of physical systems in the real world. ecological systems, and business organizations) – exhibit the
A process may be mental (thinking, planning, and learning), mental-motor characteristics of steady state, wherein a dynamic interaction
(writing, drawing, and testing), or mechanical (operating, functioning, and of system elements adjusts to changes in the environment 
producing). Processes exist in both physical and conceptual systems self-regulatory and often self-adaptive.

13 15

System System Engineering System Structure System Development Process System System Engineering System Structure System Development Process

2. Classification of systems System of systems

• Static and Dynamic Systems: • Large-scale, interdisciplinary problems often include
– A static system: one whose states do not change because it has systems in which:
structural components but no operating or flow components – Elements operate independently
(bridge) – Lifecycle of different elements
– A dynamic system exhibits behaviors because it combines – The initial requirements of the system are often not clear
structural components with operating and/or flow components – Complex
(school)
– Management-related issues often overshadow technical ones
A system is static only in a limited frame of reference. A bridge
– ...
system is constructed, maintained, and altered over a period of
time
.
14 16

7 8
 9/6/2021 9/6/2021

System System Engineering System Structure System Development Process System System Engineering System Structure System Development Process

Example 4. Technology and Technical systems

The US Coast Guard Integrated Deep water System • Technology: knowledge – mechanical & industrial arts,
concept involving multiple, independent systems applied science, and engineering, or the sum of the ways in
which social groups provide themselves with the material
objects and the services of their civilization
• Technology and Society:
– Technology  human society (people and their culture)
• Technical systems:
– human-made artifacts (technical products and processes)
• Technological Growth and Change:
– perform ongoing activities in a more effective and efficient manner

17 19

System System Engineering System Structure System Development Process System System Engineering System Structure System Development Process

3. Science and System science 5. Transition to the system age

• Cybernetics:
– Cybernetics has to do with self-regulation  all goal-seeking
behavior is controlled by the feedback of corrective
1940s
information about deviation from a desired state
The Machine Age The System Age
• General Systems Theory:
– developing a systematic framework for describing general
relationships in the natural and the human-made world.
• Systemology and Synthesis:
– The science of systems or their formation 

18 20

9 10
 9/6/2021 9/6/2021

System System Engineering System Structure System Development Process System System Engineering System Structure System Development Process

The machine age 2.1WHAT IS SYSTEM ENGINEERING?

• Systems engineering is a discipline that
• everything can be reduced, decomposed, or concentrates on the design and application of the
Reduction disassembled to simple indivisible parts whole (system) as distinct from the parts. It
involves looking at a problem in its entirety,
taking into account all the facets and all the
• independent and indivisible parts variables and relating the social to the technical
• explaining the behavior of these parts aspect.
Analytical
• aggregating these partial explanations into an
explanation of the whole • Systems engineering is an iterative process of
top‐down synthesis, development, and operation
of a real‐world system that satisfies, in a near
• simple relation, cause and effect.
Mechanism optimal manner, the full range of requirements for
• “closed-system” thinking
the system.
• (Source: INCOSE)
21 23

System System Engineering System Structure System Development Process System System Engineering System Structure System Development Process

2.1 WHAT IS SYSTEM ENGINEERING?

The System Age • Systems engineering is an interdisciplinary
approach and means to enable the realization of
• all objects and events, and all experiences of successful systems. It focuses on defining
them, as parts of larger wholes customer needs and required functionality early in
Expansionism
• attention from ultimate elements to a whole the development cycle, documenting
with interrelated parts—to system
requirements, and then proceeding with design
• sum of the functioning of the parts is seldom
synthesis and system validation while considering
Systems equal to the functioning of the whole (< , = or >) the complete problem: operations, cost and
approach schedule, performance, training and support, test,
• .
manufacturing, and disposal. SE considers both
the business and the technical needs of all
• systems that are goal seeking or purposeful
Teleologically customers with the goal of providing a quality
• concerned with
oriented
• Purpose: human domain or organization
product that meets the user needs.
(Source: INCOSE)
22 24

11 12
 9/6/2021 9/6/2021

System System Engineering System Structure System Development Process System System Engineering System Structure System Development Process

6. Engineered System 6. Engineered System

• Characteristics of the Engineered System • Engineering the Product and the System
– functional purposes in response to identified needs & – application of systems engineering and analysis: ensures
ability to achieve stated operational objectives. timely and balanced evaluation of all issues to harmonize
– brought into being and operate over a life cycle – from overall results from human investments, minimizing
identification of needs to phase-out and disposal. problems and maximizing satisfaction  economical use
of limited resources to achieve objectives
– increases throughout design, production, and
deployment, and then decreases throughout phase-out, – Improving method for determining scope of need, product
retirement, and disposal. and system requirement
– combination of resources - facilities, equipment, – Addressing the total system with all of its elements from a
materials, people, information, software, and money. life-cycle perspective
– composed of subsystems and related components that – Addressing the total system with all of its elements from a
interact with each other life-cycle perspective
– part of a hierarchy – Organizing and integrating the necessary engineering
– embedded into the natural world and interact with it – Establishing a disciplined approach with appropriate
review, evaluation, and feedback
25 27

System System Engineering System Structure System Development Process System System Engineering System Structure System Development Process

6. Engineered System 6. Engineered System

• Product and System Categories • Engineering for Product Competitiveness
– Systems are often known by their products – Product competitiveness
(manufacturing system)
sustainable competitive advantage in the marketplace
– Single-Entity Product Systems: bridge, house,
manufacturing plants,…  produce consumable or Suppliers and subcontractors
repairable product; a population of homogenous
entities; need must be functionally decomposed
and allocated to the subsystems and components
comprising the overall system
– Multiple-Entity Population Systems: life-cycle
phases (design, construction, production,
maintenance, support, renovation, disposal);
26 28

13 14
 9/6/2021 9/6/2021

System System Engineering System Structure System Development Process System System Engineering System Structure System Development Process

7. System life cycle engineering 7. System life cycle engineering

29 31

System System Engineering System Structure System Development Process System System Engineering System Structure System Development Process

7. System life cycle engineering 7. System life cycle engineering

• System life-cycle engineering

– simultaneously embrace the life cycle of the
production or construction subsystem, the life cycle
of the maintenance and support subsystem, and the
life cycle for retirement, phase-out, reuse, and
disposal as another subsystem.
– Parallel  Concurrent engineering: need + design +
production + using (maintenance, logistic support…)
+ retirement

30 32

15 16
 9/6/2021 9/6/2021

System System Engineering System Structure System Development Process System System Engineering System Structure System Development Process

7. System life cycle engineering 7. System life cycle engineering

33 35

System System Engineering System Structure System Development Process System System Engineering System Structure System Development Process

7. System life cycle engineering 7. System life cycle engineering

34 36

17 18
 9/6/2021 9/6/2021

System System Engineering System Structure System Development Process System System Engineering System Structure System Development Process

7. System life cycle engineering 7. System life cycle engineering

37 39

System System Engineering System Structure System Development Process System System Engineering System Structure System Development Process

7. System life cycle engineering 7. System life cycle engineering

38 40

19 20
 9/6/2021 9/6/2021

System System Engineering System Structure System Development Process System System Engineering System Structure System Development Process

7. System life cycle engineering 8. System structure

41
43

System System Engineering System Structure System Development Process System System Engineering System Structure System Development Process

8. System structure 9. System development process

Needs Solutions

Communication
gap

USERs ENGINEERs

44
42

21 22
 9/6/2021 9/6/2021

System System Engineering System Structure System Development Process System System Engineering System Structure System Development Process

System development process System engineering process models

Needs Solutions

Waterfall Process model

(Mô hình thác nước)
USERs ENGINEERs -Royce - 1970
System analyst translates user needs into the technical -Software development
requirements needed by the engineers
45 47

System System Engineering System Structure System Development Process System System Engineering System Structure System Development Process

Product life cycle System engineering process models

Spiral Process model

-Boehm, 1986

System
engineering

46 48

23 24
 9/6/2021 9/6/2021

System System Engineering System Structure System Development Process System System Engineering System Structure System Development Process

System engineering process models System engineering process models

V cycle Customer • Fig 7 Decomposing system design requirements.
Customer
satisfaction
musts/wants

49 51

System System Engineering System Structure System Development Process System System Engineering System Structure System Development Process

System engineering process models 9. The System Engineering Process

• Fig 6 Some system design considerations. • Development of Design Criteria
– Based on system requirement, operational and support
functions  “metrics” (performance, effectiveness,
cost…)  technical performance measures (TPMs)
– Design considerations (Fig. 6)
– Design-dependent parameters (DDPs): predicted or
estimated measures (design life, weight, reliability,
producibility, maintainability…)
– Design-independent parameters (DIPs): for system use as
cost
– Design-independent parameters (DIPs): from DDPs
(availability, cost, flexibility, and supportability)
– Design criteria: customer specified or negotiated target
values for technical performance measures
50 52

25 26
 9/6/2021 9/6/2021

System System Engineering System Structure System Development Process System System Engineering System Structure System Development Process

9. The System Engineering Process 9. The System Engineering Process

• Considering Multiple criteria

– Measures of effectiveness (MOEs): accomplishes its
mission objectives  system size and weight, range
and accuracy, speed of performance, capacity,
operational availability, reliability and
maintainability, supportability, cost, and so on.

53 55

System System Engineering System Structure System Development Process System System Engineering System Structure System Development Process

9. The System Engineering Process 10. System synthesis, analysis and evaluation
• Synthesis: specific set of customer needs and
requirements expressed in functional terms
• Analysis: Analysis of candidate system and product
designs
• Evaluation: evaluate each candidate design and check
for compliance with customer requirements

54 56

27 28
 9/6/2021 9/6/2021

System System Engineering System Structure System Development Process System System Engineering System Structure System Development Process

10. System synthesis, analysis and evaluation 10. System synthesis, analysis and evaluation
• Top-Down and Bottom-Up (Block 5): traditional
engineering design methodology: bottom-up approach
(defined elements  synthesize the system/product).
Top-down approach: system requirement  functional
decomposition for component
• Design Analysis (Block 6): focused on determining
values for cost and effectiveness measures generated
during estimation and prediction activities
• Physical and Economic Databases (Block 7): a resource
for the design process - “commercial off-the-shelf”
• Design Evaluation (Block 8): using life-cycle cost
• Design Decision (Block 9): trade off life-cycle cost
against effectiveness criteria subjectively
57 59

System System Engineering System Structure System Development Process System System Engineering System Structure System Development Process

10. System synthesis, analysis and evaluation 11. Implementing systems engineering
• The Technologies (Block 0): activities of engineering
research and development
• The customer (Block 1): satisfy customer (and
stakeholder) needs and expectations
• Need, Functions, and Requirements (Block 2): identify
and specify the desired behavior of the system or
product in functional terms.
• The Design Team (Block 3): organized to incorporate in-
depth technical expertise, as well as a broader systems
view.
• Design Synthesis (Block 4): creative activity that relies
on the knowledge of experts about the state of the art as
well as the state of technology.
58 60

29 30
 9/6/2021 9/6/2021

System System Engineering System Structure System Development Process System System Engineering System Structure System Development Process

11. Implementing systems engineering 11. Implementing systems engineering

Why need system engineering? Why need system engineering?

Source: Eric Honour

1997 INCOSE president
61 63

System System Engineering System Structure System Development Process System System Engineering System Structure System Development Process

11. Implementing systems engineering 11. Implementing systems engineering

Why need system engineering? • Figure 12 Life-cycle commitment, system-specific knowledge,
and incurred cost

Source: Eric Honour

1997 INCOSE president
62 64

31 32
 9/6/2021

System System Engineering System Structure System Development Process

11. Implementing systems engineering

• Figure 13 Systems engineering versus engineering discipline
influence on design

65

System System Engineering System Structure System Development Process

Teamwork

• Most important thing in this chapter? Do

you do not understand any part?
1

• What should you do with the part you have

not understand?
2

66

33
 Chapter 2 Need analysis tools
2.1 Introduction
2.2 Need analysis
2.3 Need analysis tools
Need Analysis Tools

Instructor: Dr. PHAN THỊ MAI HÀ

09 / 2021 SE – C2: Need analysis tools 2

Introduction Operation Analysis Function

Introduction Needanalysis
analysis Feasible analysis Validation Stakeholder
Need analysis tools Ana. Introduction Need analysis Need analysis tools

1. Introduction 1. Introduction
Need analysis:
Object???
Method/ Process?? Create conditions for a new system;
Proven feasibility of meeting needs at acceptable costs and
risks

Need analysis Not follow in a specific structure or time

Answer the questions;

.................. Why do we need a new system?

What capabilities does the new system represent?
Result???
How can that capability be guaranteed?

SE – C2: Need analysis tools 3 SE – C2: Need analysis tools 4

 Introduction Need analysis Need analysis tools Introduction Need analysis Need analysis tools

1. Introduction 2. Need analysis

The starting point of the need: Need
For example, the vehicle
Two directions of need: is subject to emission
Want
Demand-driven system; control according to the
new standard Demand
technology oriented system

Deficiency in Operation
operation requirement

Need analysis

New
technology New system
opportunities

SE – C2: Need analysis tools 5 SE – C2: Need analysis tools 6

Introduction Need analysis Need analysis tools Introduction Need analysis Need analysis tools

Need Need
Marlow’s hierarchy
Business needs
Customer request

Social need Market demand

Needs and demands

Technological advance
Legal requirement

SE – C2: Need analysis tools 7 SE – C2: Need analysis tools 8

 Introduction Need analysis Need analysis tools Introduction Need analysis Need analysis tools

Need analysis Need analysis method

NEED – WANT – DEMAND Need analysis process involves 5 steps (McKillip, 1998):
Needs analysis is defined as a formal process focus on how a
Define
product addresses the needs of a human (Leo Sun, 2015) audience and
purpose
Need analysis is the process of identifying and evaluating needs
in a community or other defined population of people. Description of
Communicate
the object and
The identification of needs is a process of describing results
environment

“problems” of a target population and possible solutions to these

problems.
Need analysis focuses on the future, or what should be done
Need
rather than on what was done as is the focus of most program assessment Identify needs

evaluations.
SE – C2: Need analysis tools 9 SE – C2: Need analysis tools 10

Introduction Need analysis Need analysis tools Introduction Need analysis Need analysis tools

Need analysis process – McKillip Need analysis process – McKillip

Identify the audience and purposes for the analysis Describe the target population and service environment

User reports: who will take actions on the basis of the needs Three levels of target audience and corresponding needs

analysis report. (Altschuld, 2000).

Purpose: understanding the intended use will help focus on Primary: the audience directly receiving the

the problems and solutions to the need to be analyzed. product/service;

Secondary: Audiences providing products/services;
Tertiary: suppliers and solution support
Needs analysis focuses on Primary??

SE – C2: Need analysis tools 11 SE – C2: Need analysis tools 12

 Introduction Need analysis Need analysis tools Introduction Need analysis Need analysis tools

Need analysis process – McKillip Need analysis process – McKillip

Need identification Need identification - Bradshaw
Needs are identified in detail and possible solutions are Normative needs: Expectations based on expert
proposed. determination of demand, performance and service levels;
3 methods to determine need of McKillip (1987). Felt needs: Expectations of target group members to have
Difference: compare expectations with results received; distinct outcomes;
Bad outcomes: the problem is the risk of bad outcomes Expressed needs: Expectations are based on the behavior of
happening; many target audiences and are determined by the users of the
Maintenance needs: existing products/services will be product/service;;
changed. Comparative needs: expectations based on the audience's
performance relative to the target audience.
SE – C2: Need analysis tools 13 SE – C2: Need analysis tools 14

Introduction Need analysis Need analysis tools Introduction Need analysis Need analysis tools

Need analysis process – McKillip Need analysis process – McKillip

Need identification Needs assessment

Solution: 3 criteria to evaluate the solution (McKillip, 1987) Assess identified needs;
Cost Answer the following questions:
Effect Which need is the most important?;
Feasible implementation What needs conflict with each other?;
Is there agreement among target groups on the relevance
and importance of the needs?.

SE – C2: Need analysis tools 15 SE – C2: Need analysis tools 16

 Introduction Need analysis Need analysis tools Introduction Need analysis Need analysis tools

Need analysis process – McKillip Teamwork – The truth about listening

Read following statements, circle the response you 3. Florida State studies show that, within eight hours,
Communicate results people
know is true or believe is true.
a) Forget everything they heard
The final need to be communicated to all stakeholders in the 1. University of Michigan studies show that after b) Forget one-third to one-half of what they heard
two months, people c) Forget three-quarters of what they heard
design process was identified in step 1;
a) Remember only a tenth of what they heard d) Forget nearly everything they heard
Ensure that stakeholders clearly understand and properly b) Remember a quarter of what they heard
4. Scientists say our brains can process words at a speed
of
understand the needs. c) Remember half of what they heard a) 1000 words a minute
b) 800 words a minute
d) Remember none of what they heard
c) 500 words a minute
2. They also show that immediately after listening to d) 250 words a minute
someone, people 5. University of Michigan studies show that we spend the
a) Remember everything they heard following percentage of our daily communication
time in listening
b) Remember most of what they heard a) 85 percent
c) Remember half of what they heard b) 45 percent
c) 25 percent
d) Remember little of what they heard
d) 15 percent
SE – C2: Need analysis tools 17 SE – C2: Need analysis tools ❖ 18

Introduction Need analysis Need analysis tools Introduction Operation Analysis Function
Introduction Needanalysis
analysis Feasible analysis Validation Stakeholder
Need analysis tools Ana.

Teamwork– Voice of customer 3. Need analysis tools

“The truth about listening” Need analysis tools
Present
Share with your team members about a dish you enjoyed Affinity diagram – Team 1
What is it?
Force-field analysis – Team 2
10 mins
Fishbone diagram – Team 3 What do it be used for?
Food
Pugh chart – Team 4 How do it use?
Place to enjoy the food- time of eating
QFD (Quality Deployment Give example
The reason or the object or the circumstances leading to the enjoyment of
Function) – Team 5, 9
the food
Functional decomposition –
How to present the dish
Team 6, 10
Detailed description of ingredients in the dish
Surveys – Team 7, 11
Feelings about the food
Interview – Team 8, 12

SE – C2: Need analysis tools 19 SE – C2: Need analysis tools 20

 Introduction Need analysis Need analysis tools Introduction Operation Analysis Function
Introduction Needanalysis
analysis Feasible analysis Validation Stakeholder
Need analysis tools Ana.

3. Need analysis tools 3. Need analysis tools

Techniques Good for Kind of data Advantage Disadvantage
Questionnaires Answering Quantitative Can reach many people Design is crucial and
specific and with low resource response rate may be
questions qualitative data low. Responses may
not be useful
Interviews Exploring Some Interviewer can guide Time consuming.
issues quantitative interviewee if necessary. Artificial environment
Observation Questionnaires but mostly Encourages contact may intimidate
qualitative between developers and interviewee
data users.
Studying Learning Quantitative No time commitment Day-to-day working
documentation about from users required will differ from
procedures, documented
regulations procedures
Focus Documentation and
Interviews Groups standards

SE – C2: Need analysis tools 21 SE – C2: Need analysis tools 22

Introduction Need analysis Need analysis tools

3. Need analysis tools

Techniques Good for Kind of data Advantage Disadvantage
Focus groups Collecting Some Highlights areas of Possibility of dominant
and multiple quantitative consensus and characters
workshops viewpoints but mostly conflict.
qualitative Encourages contact
data between developers
and
users
Naturalistic Understanding Qualitative Observing actual work Very time consuming.
observation context of user gives insights that Huge amounts of
activity other data.
techniques can’t give

SE – C2: Need analysis tools 23

 Chapter 3 NEED ANALYSIS
3.1 Introduction
3.2 Operation analysis
3.3 Functional analysis
Need Analysis 3.4 Feasibility analysis
3.5 Need validation
3.6 Stakeholder requirement document

Instructor: Dr. PHAN THỊ MAI HÀ

09 / 2021 SE – C3: Need analysis 2

Introduction Operation Analysis Function analysis Feasible analysis Validation Stakeholder Ana. Introduction Operation Analysis Function analysis Feasible analysis Validation Stakeholder Ana.

1. Introduction 1. Introduction
Need analysis: The starting point of the need:
For example, the vehicle
Create conditions for a new system; Two directions of need: is subject to emission
Proven feasibility of meeting needs at acceptable costs and Demand-driven system; control according to the

risks technology oriented system new standard

Not follow in a specific structure or time

Deficiency in Operation
Answer the questions; operation requirement

Why do we need a new system?

Need analysis
What capabilities does the new system represent?
New
How can that capability be guaranteed? technology New system
opportunities

SE – C3: Need analysis 3 SE – C3: Need analysis 4

Introduction Operation Analysis Function analysis Feasible analysis Validation Stakeholder Ana. Introduction Operation Analysis Function analysis Feasible analysis Validation Stakeholder Ana.

1. Introduction 1. Introduction
The starting point of the need: Systems engineering method in Need analysis:
Need analysis phase in system life cycle: Input come from different sources
Same four steps of system engineering method
Operation analysis – requirements analysis
Functional analysis – functional definition
Feasibility definition – physical definition
Needs validation – design validation

SE – C3: Need analysis 5 SE – C3: Need analysis 6

Introduction Operation Analysis Function analysis Feasible analysis Validation Stakeholder Ana. Introduction Operation Analysis Function analysis Feasible analysis Validation Stakeholder Ana.

2. Operation analysis 2. Operation analysis

Object: addressed is the existence of a valid need (potential Analyze from:
market) for a new system. 1. Deficiencies in Current Systems
Analyze (1) Operation; (2) Maintenance; (3) support systems ❖ In virtually all cases, the need addressed by a projected new system
is already being fulfilled, at least in part, by an existing system
In the commercial sector, market studies are continuously carried
✓ detailed identification of the perceived deficiencies in the current
out to assess the performance of existing products and the system
potential demand for new products. The strengths and ✓ continually extrapolate the conditions in which the system operates
weaknesses of competing systems and their likely future growth and re-evaluate system operational effectiveness in the life
are analyzed. 2. Obsolescence:
❖ Reason: operating environment may change, current system become
too expensive to maintain, the parts necessary for repair may be no
longer available, competition may offer a much superior product, or
technology may have advanced to the point where substantial
improvements are available for the same or lower cost
SE – C3: Need analysis 7 SE – C3: Need analysis 8
Introduction Operation Analysis Function analysis Feasible analysis Validation Stakeholder Ana. Introduction Operation Analysis Function analysis Feasible analysis Validation Stakeholder Ana.

2. Operation analysis 3. Functional analysis

Definition of Operational Objectives Object: an extension of operational studies, directed to
balance between operational performance and technical risk, cost, establishing whether or not there may be a feasible technical
and other developmental factors approach to a system that could meet the operational objectives
specific, complete, and quantitative as practicable, even though Translation of Operational Objectives into System Functions
their initial values may be changed numerous times ❖ carry out certain actions in response to its environment that would
meet the projected operational objectives
❖ May use operation of current system to image new system
❖ Approach: consider the type of primary media (signals, data,
material, or energy) → physical subsystem as sensor, computer,..
❖ visualize the entire system life cycle, including its non-operational
phases
Allocation of Functions to Subsystems

SE – C3: Need analysis 9 SE – C3: Need analysis 10

Introduction Operation Analysis Function analysis Feasible analysis Validation Stakeholder Ana. Introduction Operation Analysis Function analysis Feasible analysis Validation Stakeholder Ana.

4. Feasibility analysis 5 . Need validation

The feasibility of a system concept based on: Operational effectiveness model
❖ functional design
To animate the engagements between the system model and the
❖ physical implementation scenarios, an effectiveness model is designed with the
❖ external constraints and interactions, including compatibility with capability of accepting variable system performance
other systems parameters from the system model.
Consider:
System performance parameters: values of performance
❖ Relation to current system or application of advanced technology
characteristics that define the system’s response to its
❖ Assessment of cost environment → MOE - measures of effectiveness

SE – C3: Need analysis 11 SE – C3: Need analysis 12

Introduction Operation Analysis Function analysis Feasible analysis Validation Stakeholder Ana. Introduction Operation Analysis Function analysis Feasible analysis Validation Stakeholder Ana.

5 . Need validation 6. SRD (Stakeholder Requirement Document)

Result of need analysis
Validation of Feasibility and Need
Other name: operational concept document, concept of
The effectiveness analysis described above is mainly directed
operations document, system design document
to determining whether or not a system concept, derived in the
functional and physical definition process, is (1) feasible and SRD :
(2) satisfies the operational objectives required to meet a ❖ System’s mission and application
projected need. ❖ System operation function, constraint
❖ Boundary
❖ Support and environment concept
Should be written by users’ language

SE – C3: Need analysis 13 SE – C3: Need analysis 14

Introduction Operation Analysis Function analysis Feasible analysis Validation Stakeholder Ana. Introduction Operation Analysis Function analysis Feasible analysis Validation Stakeholder Ana.

Stakeholder definition Some constraint of project

▪ Stakeholder Company constraints:
▪ Payer ❖ Organizational policies, procedures, standards, or
▪ User guidelines on how to develop the company's system, its
▪ Professor
customers
▪ System designer
Constraints from the project: Project resources, time
constraints, project reporting regulations
External constraint:
▪ Recursive approach ❖ Industry, national, international standards
▪ Initial stakeholder → ❖ Laws and conventions
second stakeholder
❖ Communicating with other systems

SE – C3: Need analysis 15 SE – C3: Need analysis 16

Introduction Operation Analysis Function analysis Feasible analysis Validation Stakeholder Ana. Introduction Operation Analysis Function analysis Feasible analysis Validation Stakeholder Ana.

Structure of SRD Context diagram

Scope: Name – general about system
❖ System scope or project
❖ design constraints
❖ interface with external systems
❖ system boundary
Referenced document
Operations: requirement of stakeholders
Operation need: mission
System overview: interface, boundary, system operation
states
Operation environment and support
SE – C3: Need analysis 17 SE – C3: Need analysis 18

Introduction Operation Analysis Function analysis Feasible analysis Validation Stakeholder Ana.

Complete and approved SRD Term project – Need analysis

Complete SRD through: seminars, surveys, interviews, models...Note Identify stakeholders involved in the system: multiple groups, specify how to
that the opinions of all stakeholders should be collected find these stakeholders.
Approve SRD: Important step to take before moving on to the next Planning stakeholder outreach and information collection
step Set up questionnaires for each stakeholder
Traceability: Conduct interviews and analyze data
❖ Forward traceability: each SRD request will be traced to at least
Convert analysis information into system requirements (logic, compatibility,
one system request. For example: top amenities → inflight etc.)
entertainment
Determine the constraints of the system as well as the environment
❖ Backward traceability: each system request will trace back to at
least one stakeholder requirement. Example: accommodates 100 Build system function
passengers → midsize aircraft Feasibility analysis of these functions in the form of giving a response
❖ Traceability ensures that the system meets the needs of the Pay attention to the feasibility analysis of response solutions and efficiency
customer as there is no redundant function scales
SE – C3: Need analysis 19 SE – C3: Need analysis 20
 Chapter 4 Conceptual system design
❑ Identifying and translating a problem or deficiency into a definition of need
for a system → provide a preferred solution;

Conceptual System ❑

❑
Accomplishing advanced system planning and architecting in response to
the identified need;
Developing system operational requirements – functions accomplish its

Design ❑
intended purpose(s) or mission(s);
Conducting exploratory studies leading to the definition of a technical
approach for system design;
❑ Proposing a maintenance concept for the sustaining support of the system
throughout its planned life cycle;
Instructor: Dr. PHAN THỊ MAI HÀ
❑ Identifying and prioritizing technical performance measures (TPMs) and
related criteria for design;
❑ Accomplishing a system-level functional analysis and allocating
requirements to various subsystems and components;
❑ Performing systems analysis and producing trade-off studies;
09 / 2021 SE – C4: Conceptual system design 2

Conceptual system design Conceptual system design

4.1 Problem definition and need identification
4.2 Advanced systems planning and architecting
4.3. System design and feasibility analysis
4.4. System operational requirements
4.5 System maintenance and support
4.6. Technical performance measures
4.7 Functional analysis and allocation
4.8 System trade-off analysis
4. 9. System specification
4.10. Concept design review – validation
4.11 Risk analysis
SE – C4: Conceptual system design 3 SE – C4: Conceptual system design 4
1. Problem definition and need identification 2. Advanced systems planning and architecting

Problem definition: program management plan (PMP):

A comprehensive statement of the problem should be guides the development of requirements for implementation of a

presented in specific qualitative and quantitative terms and systems engineering program and the preparation of a systems

in enough detail to justify progressing to the next step; engineering management plan (SEMP)

defining a “real” problem and its importance system-level architecture

Need identification development of system operational requirements,

determination of a functional architecture,
need for a specific system capability;
proposing alternative technical concepts,
need analysis: describe the customer requirements in a
performing feasibility analysis of proposed concepts,
functional manner to avoid a premature commitment to a
selecting a maintenance and support approach;
specific design concept or configuration → define “WHAT”
→ System specification (type A)
SE – C4: Conceptual system design 5 SE – C4: Conceptual system design 6

2. Advanced systems planning and architecting 2. Advanced systems planning and architecting

SE – C4: Conceptual system design 7 SE – C4: Conceptual system design 8

 3. System design and feasibility analysis 4. System operational requirements

justified the need for a new system Some questions may be asked:
identify various system level design approaches or alternatives What are the anticipated types and quantities of equipment,
that could be pursued in response to the need; software, personnel, facilities, information, and so on, required,
evaluate the feasible approaches to find the most desirable in and where are they to be located?
terms of performance, effectiveness, maintenance and sustaining How is the system to be utilized, and for how long?
support, and life-cycle economic criteria; and What is the anticipated environment at each operational site
recommend a preferred course of action (user location)?
What are the expected interoperability requirements (i.e.,
interfaces with other “operating” systems in the area)?
How is the system to be supported, by whom, and for how long?

SE – C4: Conceptual system design 9 SE – C4: Conceptual system design 10

4. System operational requirements 4. System operational requirements

Defining System Operational Requirements: Illustrating System Operational Requirements:

Mission definition – system Illustration 1: River Crossing Problem
Performance & physical parameters - critical system performance Illustration 2: Aircraft System
parameters; How are they related to the mission scenario(s)? Illustration 3: Communication System
Operational deployment or distribution/build Illustration 4: Commercial Airlines Upgrade
Operational life cycle (horizon) Illustration 5: Community Hospital
Utilization requirements (#/day, %/capacity…) Illustration 6: Lemon powder system
Effectiveness factors: cost, availability, MTBM, failure rate, logistic Illustration 7: Information system
support effectiveness,..
Environmental factors

SE – C4: Conceptual system design 11 SE – C4: Conceptual system design 12

 5. System maintenance and support 5. System maintenance and support

Maintenance and support concept:

Definition of reliability, maintainability, human factors and safety,
constructability and producibility, supportability, sustainability,
disposability, and related requirements for design
requirements for corrective and/or preventive maintenance at any
time and throughout the system life cycle
the levels of maintenance, functions to be performed at each level,
responsibilities for the accomplishment of these functions, design
criteria pertaining to the various elements of support (spares,..)

SE – C4: Conceptual system design 13 SE – C4: Conceptual system design 14

5. System maintenance and support 5. System maintenance and support

Maintenance and support concept include:

Leve of maintenance: organizational, intermediate, and
manufacturer/depot/supplier
Repair policies: nonrepairable, partially repairable, or fully
repairable
Organizational responsibilities: customer, the producer (or
supplier), a third party, or a combination thereof
Maintenance support elements: supply support, test and support
equipment, personnel and training,…
Effectiveness requirements: support capability
Environment: impact of external factors, as temperature, shock,…
SE – C4: Conceptual system design 15 SE – C4: Conceptual system design 16
 5. System maintenance and support 6. Technical performance measures

The measures value:

Technical performance measures (TPMs): quantitative values
(estimated, predicted, and/or measured) that describe system
performance → attributes and/or characteristics that are inherent
within the design.
Design-dependent parameters (DDPs): quantified and are the
bases for the determination of TPMs.

SE – C4: Conceptual system design 17 SE – C4: Conceptual system design 18

6. Technical performance measures 6. Technical performance measures

TPM identification and evolution: Relative importance

Technical Performance Quantitative Requirement Current "benchmark"
(customer desires)
TPMs: quantitative factors as reliability MTBF, maintainability Measure (“Metric”) (competing systems)
(%)
MTBM, logistics response time, information processing time, Process time (days) 30 days (maximum) 45 days (system M) 10

facility utilization rate, … from system operational requirements Velocity (mph) 100 mph (minimum) 115 mph (system B) 32
Availability
and the maintenance and support concept 98.5% (minimum) 98.9% (system H) 21
(operational)
10 feet long 9 feet long
traceability of requirements 6 feet wide 8 feet wide
Size (feet) 17
4 feed high 4 feed high
(maximum) (system M)
Less than 1% error rate
Human factors 2% per year (system B) 5
per year
Weight (pounds) 600 pounds (maximum) 650 pounds (system H) 6
Maintainability(MTB
300 miles(minimum) 275 miles(system H) 9
M)
SE – C4: Conceptual system design 19 SE – C4: Conceptual system design 20
 6. Technical performance measures 7. Functional analysis and allocation

Quality function deployment: Functional analysis:

House of Quality (HOQ): ensure that the “voice of the customer” functional description of the system: action to achieve
is reflected in the ultimate design. Matrix “WHAT-HOW” objective
Each customer attribute is then satisfied by a technical solution process of translating system requirements into detailed
design criteria and the subsequent identification of the
resources required for system operation and support →
system architecture: requirement and structure

SE – C4: Conceptual system design 21 SE – C4: Conceptual system design 22

7. Functional analysis and allocation 7. Functional analysis and allocation

Functional flow block diagram

SE – C4: Conceptual system design 23 SE – C4: Conceptual system design 24

7. Functional analysis and allocation 7. Functional analysis and allocation

SE – C4: Conceptual system design 25 SE – C4: Conceptual system design 26

7. Functional analysis and allocation 7. Functional analysis and allocation

Functional allocation ❑ Functional View ❑ Physical View

❑ Described in terms of functions ❑ Described in terms of physical objects
System elements may be grouped by geographical location, (hardware, software, etc.)
a common environment, or by similar types of items ❑ Input Control Commands ❑ Ethernet Interface

Individual system packages should be as independent as ❑ Control Radar ❑ Control Processor

❑ Transmit Radar Signals ❑ Transmitter
possible with a minimum of “interaction effects” with other
❑ Receive Radar Signals ❑ High Power Amplifier
packages ❑ Process received radar signal ❑ Receiver

Individual system packages should be as independent as ❑ Output Targets ❑ Signal Processor

❑ Manage Power ❑ Target Processor
possible with a minimum of “interaction effects” with other
❑ Detect Faults ❑ Antenna
packages
An objective is to pursue an open-architecture
SE – C4: Conceptual system design 27 SE – C4: Conceptual system design 28
System Requirement Operation R. Performance R. Iĩmplementation Validation
7. Functional analysis and allocation
Những yêu cầu vận hành
Functional to Physical Mapping Decomposition
❑ Physical objects perform functions
❑ Process of breaking down high level items into smaller components
❑ Hardware component
❑ Key uses in Systems Engineering
❑ Software component
❑ Decompose Requirements:
❑ Basic Rule
❑ Create lower level elements within the system:
❑ A function must at some level, only be performed by one
physical item System → Subsystem →Components → Subcomponent → Part
❑ If a function crosses physical items, divide it up into two ❑ Decompose Functions:
functions and establish an interface between them if needed Create sub-functions that can implemented in a single physical item

SE – C4: Conceptual system design 29 SE – C4: Conceptual system design 30

7. Functional analysis and allocation 7. Functional analysis and allocation

Decomposing a Requirement
❑ Decide on a logical subdivision (system → subsystem)
❑ Assign each lower level item some or all of the responsibility to meet
the higher level requirement
❑ Example: Top level requirement – “The widget shall weigh less than
500 lbs.”

SE – C4: Conceptual system design 31 SE – C4: Conceptual system design 32

 7. Functional analysis and allocation 8. System trade-off analyses

Decomposing a Requirement Trade-off analyses

❑ Some performance requirement allocations can have many interactions define the problem and identify the design criteria or
❑ These provide opportunities for design trades
measures against which the various alternatives will be
❑ Example: The vehicle shall have a top speed of at least 150 mph
evaluated (i.e., the applicable TPMs),
❑ Engine power
❑ Body shape Select the appropriate evaluation techniques,
❑ Power train Select/develop a model to facilitate the evaluation process,
❑ Overall weight acquire the necessary input data,
❑ Wheels/tires
evaluate each of the candidates under consideration,
❑ Steering
perform a sensitivity analysis to identify potential areas of
❑ Fuel
risk, and finally recommend a preferred approach.
SE – C4: Conceptual system design 33 SE – C4: Conceptual system design 34

9. System specification – Type A 10. Conceptual design review – validation

All level of specification Validation

System – Type A Fig 27 (page 96) informal day-to-day project coordination and data/
Development – Type B documentation review and the formal design review -
Product – Type C
Design information is released and reviewed for compliance
Process – Type D
with the basic system-equipment requirements
Material – Type E
If the requirements are satisfied, the design is approved as is.
Understand the scope of the system & sub system to be designed
If not, recommendations for corrective action are initiated and
Requirements discussed as part of the formal design review.
System functions
System interfaces
Other constraints
SE – C4: Conceptual system design 35 SE – C4: Conceptual system design 36
11. Risk analysis 11. Risk analysis

Definition Systems Engineer - key person to manage risk

“Risk a measure of the potential inability to achieve overall Understands the technical breadth of the project
program objectives within defined cost, schedule, and Requirements
Technical approach
technical constraints”
Is close to the program manager
“possibility of loss or injury”
Cost, schedule considerations
Risk is a core competency in Systems Engineering
Access to make decisions
A risk is expressed as an “IF….THEN” statement
Three components:
IF the new power amplifier we are designing does not put out enough power,
An event that might occur
THEN the radar performance will not meet its range requirement.
A probability that the event will occur
IF the test aircraft is not available when the program is ready for flight testing,
THEN the test program be delayed until a suitable replacement can be acquired. A consequence resulting from the occurrence of the event
SE – C4: Conceptual system design 37 SE – C4: Conceptual system design 38

11. Risk analysis Probability assessment

Type of risk ❑ Experience with the part/vendor/technology/developer staff
Technical ❑ Failure rates
❑ New or proven? (new startup part supplier, proven part, etc.)
Critical technology development fails to meet expectations
Failure to meet a requirement – design error, software bug
❑ Number of dependencies
❑ Interfaces
A component failure occurs (e.g., in the prototype)
❑ Suppliers
Needed assets are not available
❑ Weather, time windows for lab/test-range access, etc.
Programmatic
❑ Margin
Critical personnel leave the project or are not available when needed
❑ Easy to meet requirement?
Other project that your project depends on does not provide a
❑ Is there excess “X” (time, power, budget, space, etc.) available
suitable product when it is needed
Loss of funding/budget

SE – C4: Conceptual system design 39 SE – C4: Conceptual system design 40

Consequence assessment Risk management
❑ Effects of the consequences depends on the situation 1) Identify the Risks
❑ Low-Medium-High consequence assessment will usually be defined by 2) Assign probabilities and consequences
the specific project 3) Rank the risks in order of importance
❑ Technical 4) Determine candidate risk mitigations
❑ Priority of requirement 5) Select and implement risk mitigations
❑ Pass/Fail requirement vs. level of performance 6) Monitor progress….does the risk go down over time?
❑ Special considerations: safety, catastrophic project failure 7) start again……
❑ Example: What value is assigned to a consequence of harm/death?
❑ Cost
❑ Increase in cost vs. total cost of the project
❑ Schedule
❑ Delay in schedule vs. total time of the project
❑ Critical milestones (major event or for completing project)
SE – C4: Conceptual system design 41 SE – C4: Conceptual system design 42

Risk management Reduce risk by reducing probability

❑ Develop an alternate backup design
❑ Consider relief of requirements
❑ Scale back on high risk requirements in development

❑ Prototype – do testing and get feedback early

❑ Perform analysis and testing of critical design items
❑ Add special oversight to high risk subsystems/components
❑ Perform additional technical and management reviews
❑ Plan ahead – arrange for needed resources early
❑ Parts (especially long lead parts), staffing, vendors

SE – C4: Conceptual system design 43 SE – C4: Conceptual system design 44

Reduce risk by reducing consequences Risk analysis in conceptual design
❑ Be prepared to relieve requirements if necessary ❑ One of the criteria that is evaluated for each concept is risk
❑ Close user involvement, prioritized requirements ❑ Identify are the sources of risk (technical, programmatic)
❑ Develop project plans that allows for recovery of failures ❑ Perhaps there is something that can be done to manage the risk
❑ Include time/resources for second iteration of design ❑ Helps to assess the likelihood the project will fail
❑ Incremental design approach ❑ Sponsors do not want to end up with a failed project
❑ Plan to address high risk issues early ❑ What happens if a candidate solution is considered to be
❑ Plan a management reserve of schedule and budget “Higher” risk?
❑ Likely will have a larger uncertainty factor added to the cost/
❑ Choose flexible design approaches
schedule estimate to account for the uncertainty
❑ Standards, commodity components
❑ Development plan may include additional investigation efforts or
experiments to provide confidence the concept will succeed
❑ Add decision points in the schedule to continue or stop depending
on the experimental results
SE – C4: Conceptual system design 45 SE – C4: Conceptual system design 46

Risk analysis in conceptual design

❑ Risk is considered as a criteria in comparing alternatives
❑ A concept may be rejected as a viable concept purely on the basis of
risk
❑ Depends on the customer’s risk tolerance

❑ Risk tolerance often depends on the urgency of the need and number
of available concepts that can provide a solution

SE – C4: Conceptual system design 47

 Chapter 5 Preliminary System Design
❑ Identifying and translating a problem or deficiency into a definition of need
for a system → provide a preferred solution;

Preliminary System ❑

❑
Accomplishing advanced system planning and architecting in response to
the identified need;
Developing system operational requirements – functions accomplish its

Design ❑
intended purpose(s) or mission(s);
Conducting exploratory studies leading to the definition of a technical
approach for system design;
❑ Proposing a maintenance concept for the sustaining support of the system
throughout its planned life cycle;
Instructor: Dr. PHAN THỊ MAI HÀ
❑ Identifying and prioritizing technical performance measures (TPMs) and
related criteria for design;
❑ Accomplishing a system-level functional analysis and allocating
requirements to various subsystems and components;
❑ Performing systems analysis and producing trade-off studies;
10 / 2021 SE – C5: Preliminary system design 2

Preliminary System Design Preliminary system design

1 Problem definition and need identification

2 Development, product, process, and material specifications

3 Functional analysis and allocation (subsystem)

4 Preliminary design criteria

5 Trade-off studies and design definition

6 Design review, evaluation and feedback

SE – C5: Preliminary system design 3 SE – C5: Preliminary system design 4

1. Preliminary system design phase 1. Preliminary system design phase

Definition: Major task:

definition and development of the preferred system concept Developing design requirements for subsystems and major
and the allocated requirements for subsystems and the system elements from system-level requirements;
major elements thereof Preparing development, product, process, and material
System will conform to performance and design specifications applicable to subsystems
specifications, and that it can be produced and/or Accomplishing functional analysis and allocation to and
constructed with available methods, and that established below the subsystem level;
cost and schedule constraints Establishing detailed design requirements and developing
functional analysis and allocation of requirements at the plans for their handoff to engineering domain specialists;
subsystem level and below,
SE – C5: Preliminary system design 5 SE – C5: Preliminary system design 6

1. Preliminary system design phase 1. Preliminary system design phase

Major task: Starting points for preliminary system design:

Identifying and utilizing appropriate engineering design Initial definition of system requirements
tools and technologies; Candidate system solution concepts
Conducting trade-off studies to achieve design and Also needed: Value decision makers place on the solution
operational effectiveness; and Resources that will be made available
Constraints identified (especially cost & schedule)
Conducting design reviews at predetermined points in time.
Take what you have learned in Preliminary design and go to
the next level of detail → Focus is to flesh out the
alternatives to enough detail so one can make a choice
between them
SE – C5: Preliminary system design 7 ;
SE – C5: Preliminary system design 8
 1. Preliminary system design phase 2. Development, product, process, & material specifications

Preliminary design requirements: development of a specification tree:

“system” design requirements from conceptual design development specification (Type B), product specification (Type

(whats) → hows in preliminary design C), and so on, must include the appropriate TPM

“what the system is intended to do before determining what System specification (Type A): includes technical, performance,
operational, & support characteristics for the system as an entity
the system is”
Development specification (Type B): technical requirements
(qualitative and quantitative) for any new item below system level
where research, design, & development are needed (equipment,
assembly, computer program, facility, critical item of support,
data item, …). Each specification must include the performance,
effectiveness, and support characteristics
SE – C5: Preliminary system design 9 SE – C5: Preliminary system design 10

2. Development, product, process, & material specifications 2. Development, product, process, & material specifications

development of a specification tree:

Product specification (Type C): qualitative & quantitative for any
item below system level that is currently in inventory & can be
procured “off the shelf.”, commercial off-the-shelf (COTS)
equipment, software module, component, item of support,…
Process specification (Type D): qualitative & quantitative
associated with a process and/or a service performed on any
element of a system or in the accomplishment of some functional
requirement (manufacturing process; logistics process - materials
handling and transportation; an information handling process,…)
Material specification (Type E):
SE – C5: Preliminary system design 11 SE – C5: Preliminary system design 12
 3. Functional analysis and allocation (subsystem) 3. Functional analysis and allocation (subsystem)

The functional analysis process

Functional flow block diagram (FFBD)
What – How (how will each function be accomplished)
Defining necessary inputs & expected outputs,
describing external controls & and constraints,
determining mechanisms or physical resources required for
accomplishing function.
May involve equipment, software, people, facilities,
data/information, or various combinations thereof

SE – C5: Preliminary system design 13 SE – C5: Preliminary system design 14

3. Functional analysis and allocation (subsystem) 3. Functional analysis and allocation (subsystem)

# Activity Required Inputs Expected Outputs Resource Requirements

Descripti
on
1. Need Customer surveys; A specific qualitative and quantitative Benchmarking; statistical
0 identifica marketing inputs; needs statement responding to analyses of data (i.e., data
tion shipping and a current deficiency. Care must be collected as a result of
servicing department taken to state this need in functional surveys and consolidated
logs; market niche terms. from shipping and servicing
studies; competitive logs, etc.).
product research.
2. Needs A specific Qualitative and quantitative factors Quality function deployment
1 analysis qualitative and pertaining to system performance (QFD), input–output matrix,
and quantitative needs levels, geographical distribution of checklists; value
requirem statement expressed products, expected use profiles, engineering; statistical data
ents in functional terms. user/consumer environment; analysis; trend analysis;
definition operational life cycle, effectiveness matrix analysis; parametric
s requirements, the levels of analysis; various categories
maintenance and support, of analytical models and
consideration of the applicable tools for simulation studies,
elements of logistic support, the trade-offs, etc.
support environment, and so on.
SE – C5: Preliminary system design 15 SE – C5: Preliminary system design 16
 3. Functional analysis and allocation (subsystem) 3. Functional analysis and allocation (subsystem)
# Activity Required Inputs Expected Outputs Resource Requirements
Description
2. Synthesis of Results from needs Identification and description Pugh’s concept generation
2 conceptual analysis and requirements of candidate conceptual approach; brainstorming;
system definition process; system design alternatives analogy; checklists.
design technology research and technology applications.
alternatives studies; supplier
information
2. Analysis of Candidate conceptual Approximation of the Indirect system
3 conceptual solutions “goodness” of each feasible experimentation (e.g.,
system and technologies; results conceptual solution relative mathematical modeling and
design from the needs analysis to the pertinent parameters, simulation); parametric
alternatives and requirements both direct and indirect. analyses; risk analyses.
definition process This goodness could be
expressed as a numeric
rating, probabilistic measure,
or fuzzy measure.
2. Evaluation Results from the analysis A single or short-listed set of Design-dependent parameter
4 of task in the preferred conceptual system approach; generation of
conceptual form of a set of feasible designs. hybrid
system conceptual Further, a “feel” for how numbers to represent
design system design alternatives much better the preferred candidate solution
alternatives approach(es) is relative to all “goodness”; conceptual
SE – C5: Preliminary system design other feasible alternatives. system design evaluation 17 SE – C5: Preliminary system design 18

3. Functional analysis and allocation (subsystem) 3. Functional analysis and allocation (subsystem)

Requirements allocation
Lower-level elements of the system are defined through the
functional analysis and subsequently by partitioning (or grouping)
similar functions into logical subdivisions, identifying major
subsystems, configuration items, units, assemblies, modules,…
requirements then lead to the incorporation of the appropriate
design characteristics (attributes) in the design of Units A, B, C.
Use allocation matrix/allocation tree

SE – C5: Preliminary system design 19 SE – C5: Preliminary system design 20

 3. Functional analysis and allocation (subsystem) 3. Functional analysis and allocation (subsystem)

SE – C5: Preliminary system design 21 SE – C5: Preliminary system design 22

3. Functional analysis and allocation (subsystem) 4. Preliminary design criteria

Applications of the functional analysis Some questions may be asked:

breaking the system (and its elements) down into functional Design for functional capability
entities through functional packaging and the development of an Design for interoperability
open-architecture configuration Design for sustainability
Reliability analysis Design for reliability
Maintainability analysis - Maintenance and logistic support Design for maintainability
Human factors analysis: operator task analysis (OTA); operational Design for usability and safety
sequence diagrams (OSDs) Design for security
Producibility, disposability, and sustainability analysis. Design for supportability and serviceability
Affordability analysis: life-cycle and total ownership cost. Design for producibility and disposability
Design for affordability
SE – C5: Preliminary system design 23 SE – C5: Preliminary system design 24
 4. Preliminary design criteria 4. Preliminary design criteria

Design objectives: Addition emphasis:

be compatible with system operational requirements, Design for functional capability

maintenance & support concept, & the prioritized TPMs; Design for interoperability: system - environment

comply with the allocated design-to criteria Design for sustainability – life cycle
Design for reliability - MTBF
meet all of requirements in various applicable specifications
Design for maintainability: ease, accuracy, safety & economy
Design for usability and safety: interfaces human – elements
Design for security: prevent faults that destroy system, harm human
Design for supportability and serviceability
Design for producibility and disposability
Design for affordability: Economic feasibility
SE – C5: Preliminary system design 25 SE – C5: Preliminary system design 26

5. Trade-off studies and design definition 5. Trade-off studies and design definition

SE – C5: Preliminary system design 27 SE – C5: Preliminary system design 28

 6. Design review, evaluation and feedback

Review:
conceptual design review: requirements & functional baseline
System design reviews: functional requirements and allocations:
layout, overall system configuration,
Equipment/software design reviews (detail): product, process, &
material specifications (product, process, & material specifications)
Critical design review: production and/or construction

SE – C5: Preliminary system design 29

 Chapter 6 Detail Design & Development
❑ Developing design requirements for all lower-level
components of the system;
Detail Design & ❑ Implementing the necessary technical activities to fulfill all
design objectives;

Development ❑

❑
Integrating system elements and activities;
Selecting and utilizing design tools and aids;
❑ Preparing design data and documentation;
Instructor: Dr. PHAN THỊ MAI HÀ ❑ Developing engineering and prototype models;
❑ Implementing a design review, evaluation, and feedback
capability; and
❑ Incorporating design changes as appropriate.
10 / 2021 SE – C6: Detail design & Development 2

Detail Design & Development Detail Design & Development

1 Detail design requirements

2 The evolution of detail design

3 Integrating system elements and activities

4 Design tools and aids

5 Trade-off studies and design definition

6 Design review, evaluation and feedback

7 Incorporating design changes

SE – C6: Detail design & Development 3 SE – C6: Detail design & Development 4
 1. Detail design requirements 1. Detail design requirements

Definition:
top-down approach for establishing requirements at each
level in the system hierarchical structure → product baseline
integration, test, and evaluation steps constitute a bottom-up
approach
design activities be accomplished on a concurrent basis
→ simultaneous engineering, concurrent engineering,
integrated product development (IPD

SE – C6: Detail design & Development 5 SE – C6: Detail design & Development 6

2. The evolution of detail design 2. The evolution of detail design

Conceptual design – preliminary design – detail desi

Requirements: top – down
Basic requirement (element - construction): bottom-up

SE – C6: Detail design & Development 7 SE – C6: Detail design & Development 8
2. The evolution of detail design 2. The evolution of detail design

SE – C6: Detail design & Development 9 SE – C6: Detail design & Development 10

3. Integrating system elements and activities 3. Integrating system elements and activities

Objective: determine the best way to respond to the hows

Select a standard component that is commercially available
and for which there are a number of viable suppliers (COST)
→ reduce cost, assurance for maintenance and support
Modify COST for purposes as installation, adapter cable of
compatibility, software interface module,.. → objective:
inexpensive and simple
Design and develop a new and unique component to meet a
specific functional requirement → integrated into the overall
system design and development process
SE – C6: Detail design & Development 11 SE – C6: Detail design & Development 12
4. Design tools and aids 5. Design data, information and integration

Tools & design aids → effective & efficient manner Design documentation:
computer-aided engineering (CAE) & computer-aided design Design drawings: assembly drawings, control drawings, logic
(CAD) or simulation methods → a robust design more diagrams, structural layouts, installation drawings,..
quickly, while reducing the overall program technical risks. Material & part lists: part lists, material lists, long-lead-item
physical three-dimensional scale models or mockups → lists, bulk-item lists, provisioning lists, and so on.
realistic simulation of a proposed system configuration. Analyses & reports: trade-off study reports supporting design
software development building of “one-of-a-kind” software decisions, reliability & maintainability analyses & predictions,
packages human factors analyses, safety reports, supportability
analyses, configuration identification reports, computer
documentation, installation and assembly procedures, ...
SE – C6: Detail design & Development 13 SE – C6: Detail design & Development 14

5. Design data, information and integration 5. Design data, information and integration

Objective of design data review: Objective of design data review:

depth and extent of definition necessary to enable product depth and extent of definition necessary to enable product
manufacture. manufacture.
reviewed against design standards and checklist criteria. reviewed against design standards and checklist criteria.

SE – C6: Detail design & Development 15 SE – C6: Detail design & Development 16
5. Design data, information and integration 5. Design data, information and integration

System design review checklist: should YES

System operational requirements System engineering management plan

defined completed
System engineering management plan
Effectiveness factors established
completed
System maintenance concept defined
Design documentation completed
Functional analysis and allocation
Logistic support requirements defined
accomplished
Ecological requirements met
System trade-off studies documented
Societal requirements met
System specification and supporting
Economic feasibility determined
specifications completed
Sustainability requirements met

SE – C6: Detail design & Development 17 SE – C6: Detail design & Development 18

5. Design data, information and integration 6. Design review, evaluation and feedback

Design Features—Does the design reflect adequate consideration of Tracking and controlling to TPMs:
Accessibility Packaging & mounting
TPM about availability, life cycle cost, maintenance labor
Adjustment & alignments Panel displays & controls
hours per operating hour, MTBF, weight → system design
Cables & connector Producibility
Calibration Reliability review, based on a prediction associated with the design
Disposability Safety configuration at the time
Environment Selection of pasts/materials To ensure that all of the requirements are met, or at least
Fasteners Servicing & lubrication
seriously addressed, various design team members may be
Handling Software
assigned to “track” specific TPMs throughout the design
Human factors Standardization
Interchangeability Supportability process.
Maintainability Testability
SE – C6: Detail design & Development 19 SE – C6: Detail design & Development 20
6. Design review, evaluation and feedback 6. Design review, evaluation and feedback

Tracking of other design considerations:

conduct of the essential trade-off analyses leading to the
selection of specific components
→ consideration:
expected life of each of the components (that affect
maintenance plan or component replace plan
implementing the overall system design process effectively, in
a limited amount of time, and at reduced cost.

H: high interest; M: medium interest, L: low interest

SE – C6: Detail design & Development 21 SE – C6: Detail design & Development 22

6. Design review, evaluation and feedback 7. Incorporating design changes

Conducting design reviews: schedule the design review Change reasons:

Identification of the items to be reviewed. correct a design deficiency,
A selected date for the review. improve a product,
The location or facility where the review is to be conducted. incorporate a new technology,
An agenda for the review (including objectives). improve the level of sustainability,
Determine design review board respond to a change in operational requirements,
Equipment and/or software requirements for the review. compensate for an obsolete component, …
Design data requirements (specifications, drawings,…) Change:
Funding requirements. design of a prime equipment item, a software modification, a
Reporting requirements (recommendation) data revision, and/or a change in some process.
SE – C6: Detail design & Development 23 SE – C6: Detail design & Development 24
7. Incorporating design changes

SE – C6: Detail design & Development 25

 Chapter 7 SE Planning & Organization
System Engineering
Planning and
Organization
Instructor: Dr. PHAN THỊ MAI HÀ

11 / 2021 SE – C7: SE Planning and Organization 2

SE Planning & Organization 1. System engineering program planning

1 Systems engineering program planning Definition:

description of the tasks that need to be accomplished for
2 Systems engineering management plan
bringing the system into being along with applicable
3 Organization for system engineering
schedules, program resource requirements, and
organizational approach

SE – C7: SE Planning and Organization 3 SE – C7: SE Planning and Organization 4

 1. System engineering program planning 2. Systems engineering management plan

Objective:
provide the structure, policies, and procedures to foster the
integration of the engineering and support activities needed
for system design and development
facilitates the integration of all design-oriented plans and
provides the necessary communication links with other key
planning activities

SE – C7: SE Planning and Organization 5 SE – C7: SE Planning and Organization 6

2. Systems engineering management plan - example 2. Systems engineering management plan - example

1. Title Page, Table of Contents, Scope, Applicable Documents 3. Transitioning Critical Technologies—activities, risks, criteria for selecting technologies and
2. Systems Engineering Process for transitioning these technologies.
2.1 Systems Engineering Process Planning—decision database (deliverables), process inputs, 4. Integration of the Systems Engineering Effort—team organization, technology verifications,
technical objectives, work breakdown structure, training, standards and procedures, resource process proofing, manufacturing of engineering test articles, development test and
allocation, constraints, work authorization, verification planning. evaluation, implementation of software designs for system end items, sustaining engineering
2.2 Requirements Analysis—reliability and availability; maintainability, supportability, and and problem solution support, other systems engineering implementation tasks.
integrated logistics support (ILS); survivability; electromagnetic compatibility; human 5. Additional Systems Engineering Activities—long-lead items, engineering tools, design to
engineering and human systems integration; safety, health hazards, and environmental impact; cost/cost as an independent variable, value engineering, system integration plan,
system security; producibility; test and evaluation; testability and integrated diagnostics; compatibility with supporting activities, other plans and controls.
computer resources; transportability; infrastructure support; other engineering specialties.
6. Systems Engineering Scheduling—systems engineering master schedule (SEMS), systems
2.3 Functional Analysis—scope, approach, methods, procedures, tools (system-level functional
engineering detailed schedule (SEDS).
block diagram).
7. Systems Engineering Process Metrics—cost and schedule performance measurement, other
2.4 Synthesis—approach, methods to transform the functional architecture into a physical
architecture, to define alternative system concepts, to define physical interfaces, and to select process control techniques (control charts).
preferred product and process solutions. 2.5 Systems Analysis and Control—trade studies, 8. Role and Function of Reviews and Audits.
system/cost effectiveness analyses, risk management, configuration management, interface 9. Notes and Appendices.
management, data management, systems engineering master schedule (SEMS), technical
performance measurement (TPM), technical reviews (design reviews), supplier control,
requirements traceability.
SE – C7: SE Planning and Organization 7 SE – C7: SE Planning and Organization 8
2. Systems engineering management plan – example 2. Systems engineering management plan

Statement of work (SOW):

A summary statement of the tasks to be accomplished.
An identification of the input requirements from other
tasks.
References to applicable specifications (Type A), standards,
procedures, and related documentation.
A description of the specific results to be achieved
(equipment, software, design data, reports,… along with the
proposed schedule of delivery.

SE – C7: SE Planning and Organization 9 SE – C7: SE Planning and Organization 10

2. Systems engineering management plan 2. Systems engineering management plan

Statement of work (SOW): guideline System engineering program tasks

short (< two pages), clear & precise manner. Perform a needs analysis and conduct feasibility studies
Every effort must be made to avoid ambiguity and the Define system operational requirements and the
possibility of misinterpretation by the reader. maintenance concept, and identify and prioritize the
requirements in sufficient detail (practical applications & technical performance measures
legal interpretations). Do not underspecify or over-specify. Accomplish a functional analysis at the system level and
Avoid unnecessary repetition & incorporation of extraneous allocate requirements to the next lower level
material and requirements. Prepare system specification, Type A.
Do not repeat detailed specifications & requirements (in Prepare the test and evaluation master plan (TEMP)
referenced documentation) Prepare the systems engineering management plan (SEMP).
SE – C7: SE Planning and Organization 11 SE – C7: SE Planning and Organization 12
2. Systems engineering management plan 2. Systems engineering management plan

System engineering program tasks Work breakdown structure

Accomplish synthesis, analysis, and evaluation product-oriented family tree that leads to the identification of
Plan, coordinate, and conduct formal design review meetings the functions, activities, tasks, subtasks, work packages, and
Monitor and review system test and evaluation activities so on, that must be performed for the completion of a given
Coordinate and review all formal design changes and program
modifications for improvement not an organizational chart in terms of project personnel
Initiate and establish the necessary ongoing liaison activities assignments and responsibilities, but does represent an
throughout the production/ construction, utilization and organization of work packages prepared for the purposes of
sustaining support, and retirement and material disposal program planning, budgeting, contracting, and reporting.
phases.
SE – C7: SE Planning and Organization 13 SE – C7: SE Planning and Organization 14

2. Systems engineering management plan 2. Systems engineering management plan

Work breakdown structure Work breakdown structure

Level 1. Identifies total anticipated scope of work related to
the design and development, production, distribution,
operation, support, and retirement of a system.
Level 2. Identifies the various projects, or categories of
activity, that must be completed in response to program
requirements.
Level 3. Identifies the functions, activities, major tasks, or
components of the system that are directly subordinate to
Level 2 items. Program schedules are prepared at this level.
SE – C7: SE Planning and Organization 15 SE – C7: SE Planning and Organization 16
2. Systems engineering management plan 3. Organization for systems engineering

The scheduling of tasks Definition:

scheduling methods: bar charts, milestone charts, Gantt
Organization: combining of human resources in such a
charts, program networks, …
manner as to fulfill a need.
program evaluation and review technique (PERT), the critical Organizations constitute groups of individuals of varying
path method (CPM),
levels of expertise combined into a social structure of some
form to accomplish one or more functions.
Organizational structures: depend on established goals and
objectives, the resources available, the communications and
working relationships among the individual participants, the
motivation of the personnel, and many other factors.
SE – C7: SE Planning and Organization 17 SE – C7: SE Planning and Organization 18

3. Organization for systems engineering 3. Organization for systems engineering

Developing the organizational structure:

Structure: functional model, a project orientation, a matrix
approach or a combination thereof
Consumer, producer, and supplier relationships:
needs to understand the environment in which systems
engineering functions are performed

SE – C7: SE Planning and Organization 19 SE – C7: SE Planning and Organization 20

3. Organization for systems engineering 3. Organization for systems engineering

Producer organization and functions:

functional approach: grouping of functional specialties or
disciplines into separately identifiable entities.
pure project: planning, design & development, production,
operational use, and support of a unique/single system
matrix configuration with a mix of the pure functional
organization and the project organization
project-staff organizational configuration: a project includes a
systems engineering group while many of engineering support
activities provided on a task-by-task basis by staff functions
SE – C7: SE Planning and Organization 21 SE – C7: SE Planning and Organization 22

3. Organization for systems engineering 3. Organization for systems engineering

SE – C7: SE Planning and Organization 23 SE – C7: SE Planning and Organization 24

3. Organization for systems engineering 3. Organization for systems engineering

SE – C7: SE Planning and Organization 25 SE – C7: SE Planning and Organization 26

3. Organization for systems engineering 3. Organization for systems engineering

Major systems engineering communication links: A Major systems engineering communication links: A
1. Marketing and sales—to acquire and sustain the necessary 4. Human resources—to solicit assistance in the initial
communications with the customer → “contractual” channel. recruiting and hiring of qualified project personnel for system
2. Accounting—to acquire both budgetary and cost data in engineering, and in the subsequent training and maintenance
support of economic analysis efforts (e.g., life-cycle cost of personnel skills.
analysis). 5. Contract management—to keep abreast of contract
3. Purchasing—to assist in the identification, evaluation, and requirements (of a technical nature) between the customer
selection of component suppliers with regard to technical, and the contractor.
quality, and life-cycle cost implications.

SE – C7: SE Planning and Organization 27 SE – C7: SE Planning and Organization 28

3. Organization for systems engineering 3. Organization for systems engineering

Major systems engineering communication links: B Major systems engineering communication links: C
To establish and maintain on-going liaison and close To provide an input relative to project requirements for
communications with other projects with the objective of system support, & to solicit assistance in terms of the
transferring knowledge that can be applied for the benefit of functional aspects associated with the design, development,
Project Y. To solicit assistance from other company-wide test & evaluation, production,… through system life cycle.
functionally-oriented engineering laboratories & departments Major systems engineering communication links: D
relative to the application of new technologies in support of To provide an input relative to project requirements for
system design and development. production (manufacturing, assembly, inspection…), & solicit
assistance to design for producibility & implementation of
quality engineering requirements.
SE – C7: SE Planning and Organization 29 SE – C7: SE Planning and Organization 30

3. Organization for systems engineering 3. Organization for systems engineering

Major systems engineering communication links: E Staffing the Systems Engineering Organization:
To establish and maintain close relationships and the
Important factor: culture, capabilities, environment.
necessary on-going communications with such project
Choose person
activities as scheduling; configuration management; data
- be highly professional senior-level individuals with varied
management; and supplier management
backgrounds and a wide breadth of knowledge (research,
Major systems engineering communication links: F
design & development, manufacturing, …)
To provide an input relative to system-level design
- conversant with some of different design-related technologies
requirements, and to monitor, review, evaluate → technical
and specific applications throughout system design &
lead in definition of system requirements, accomplishment of
development process
functional analysis, conductance of trade-off studies, …
SE – C7: SE Planning and Organization 31 SE – C7: SE Planning and Organization 32
3. Organization for systems engineering

Staffing the Systems Engineering Organization:

Important factor: culture, capabilities, environment.
Choose person
- have vision & be creative in selection of technologies

- teamwork approach, committed to objectives of organization;

a certain degree of interdependence is required,

- high degree of communication (written, verbal, and/or
nonverbal means).

SE – C7: SE Planning and Organization 33

 Chapter 7 Requirement in System Engineering
1. Design for Reliability

Requirement in 2. Design for Maintainability

3. Design for Usability (Human factors)

System Engineering 4. Design for Logistics and Supportability

5. Design for Producibility, Disposability & Sustainability

Instructor: Dr. PHAN THỊ MAI HÀ
6. Design for Affordability (Life-cycle Costing)

11 / 2021 SE – C8: Requirement in SE 2

1. Design for reliability 1. Design for reliability

Definition: Definition:
ability of a system to perform its intended mission when Reliability: probability that a system/ product accomplish its
operating for a designated period of time, or through a designated mission in a satisfactory manner/ specifically for a
planned mission scenario, in a realistic operational given period when used under specified operating conditions.
∞
environment → satisfy all of the operational objectives The Reliability Function: 𝑅 𝑡 = 1 − 𝐹 𝑡 = න 𝑓 𝑡 𝑑𝑡 = 𝑒 −𝜆𝑡
𝑡
desired and specified in a true user’s environment With: F(t): probability that system will fail by time

Need measures reliability—the reliability function, the failure : instantaneous failure rate

rate, & component relationships; Reliability analysis methods 𝑛𝑢𝑚𝑏𝑒𝑟 𝑜𝑓 𝑓𝑎𝑖𝑙𝑢𝑟𝑒𝑠

𝜆=
Consider reliability in the system life cycle 𝑡𝑜𝑡𝑎𝑙 𝑜𝑝𝑒𝑟𝑎𝑡𝑖𝑛𝑔 ℎ𝑜𝑢𝑢𝑟𝑠

SE – C8: Requirement in SE 3 SE – C8: Requirement in SE 4

1. Design for reliability 1. Design for reliability

Component Relationships:
Reliability – series network
R = (RA) (RB) (RC)
Reliability – parallel network
R = 1 - (1 - RA) (1 - RB) (1 - RC)

SE – C8: Requirement in SE 5 SE – C8: Requirement in SE 6

1. Design for reliability 1. Design for reliability

Reliability requirements: define

System performance & effectiveness factors, mission profile, & system
functional requirements (use conditions, duty cycles, how system is to be
operated).
Operational life cycle (anticipated time that system will be in the
inventory and in operational use).
Environment - system is expected to operate & be maintained
(temperature, humidity, shock and vibration, levels of noise and toxicity,
etc.) - a range of values as applicable & should cover all operational,
transportation & handling, maintenance & support, & storage modes.
Operational & supporting interfaces likely to impact the system as it
performs its mission(s) throughout its planned life cycle.
SE – C8: Requirement in SE 7 SE – C8: Requirement in SE 8
1. Design for reliability 1. Design for reliability

Reliability model Component Selection and Application

the functional analysis Selection of standardized components & materials depend on
lead to the development of
physical characteristics, known reliabilities, and so on
a reliability block diagram
The test and evaluation of all components and materials prior
and a model that can serve
as the basis for to design acceptance: evaluation of component operating
accomplishing reliability features, physical tolerances, sensitivity to certain stresses,
allocation, reliability physics-of-failure characteristics, & other specific ones of
prediction, stress–strength
component(s) related to its intended application..
analysis, and subsequent
design analysis and
evaluation tasks.
SE – C8: Requirement in SE 9 SE – C8: Requirement in SE 10

1. Design for reliability 1. Design for reliability

Design Review and Evaluation – design review checklist
1. Have reliability quantitative & qualitative requirements for system been adequately defined from beginning? Reliability analysis methods
2. Have these requirements been properly allocated to various subsystems (& downward) as applicable? Is there
a top-down/bottom-up “traceability” of these requirements?
FMECA: Failure Mode, Effects, and Criticality Analysis
3. Are reliability requirements realistic? Are they compatible with other system requirements? Define system (product or
4. Has system design complexity been minimized; for example, number of components/parts?
5. Have system failure modes and effects been identified?
process) requirements
6. Are system, subsystem, unit, and component-part failure rates known? Accomplish functional analysis Identify failure detection means
7. Are failure characteristics (i.e., physics of failure) known for each applicable component part?
Accomplish requirements Rate failure mode severity
8. Has the system or product wear out period been defined?
9. Have component parts with excessive failure rates been identified? allocation Rate failure mode frequency
10. Have all critical-useful-life items been identified and eliminated where possible?
Identify failure modes. Rate failure mode detection
11. Have fail-safe characteristics been incorporated where applicable (i.e., protection against secondary
/dependent failures resulting from primary failures)? Determine causes of failure probability
12. Has the utilization of adjustable components been minimized (if not eliminated)? Determine the effects of failure Analyze failure mode criticality
13. Have cooling provisions been incorporated in design “hot-spot” areas?
14. Have all hazardous conditions been eliminated? Initiate recommendations for
15. Have all system reliability requirements been met? product/process improvement
SE – C8: Requirement in SE 11 SE – C8: Requirement in SE 12
1. Design for reliability 1. Design for reliability

Reliability analysis methods Reliability analysis methods

FTA: Fault-tree analysis Stress–Strength Analysis
❖ 1. For selected components, determine nominal stresses as a function of loads,
temperature, vibration, shock, physical properties, and time.
❖ 2. Identify factors affecting maximum stress, such as stress concentration
factors, static and dynamic load factors, stresses as a result of manufacturing
and heat treating, environmental stress factors, and so on.
❖ 3. Identify critical stress components and calculate critical mean stresses (e.g.,
maximum tensile stress and shear stress).
❖ 4. Determine critical stress distributions for the specified useful life. Analyze
the distribution parameters and identify component safety margins.
❖ 5. For those components that are critical and where the design safety margins
are inadequate, corrective action must be initiated. This may constitute
component-part substitution or a complete redesign of the system element in
question.
SE – C8: Requirement in SE 13 SE – C8: Requirement in SE 14

1. Design for reliability 2. Design for maintainability

Reliability analysis methods Definition:

Reliability prediction: Maintainability is a design characteristic (a design dependent
Based on the analysis of similar equipment parameter) pertaining to ease, accuracy, safety, and economy
Based on an estimate of active element groups
in the performance of maintenance functions
accomplished from an equipment parts count
Maintainability, as a characteristic of design, can be expressed
based on a stress analysis (discussed earlier)
in terms of maintenance times, maintenance frequency
factors, maintenance labor hours, and maintenance cost.

SE – C8: Requirement in SE 15 SE – C8: Requirement in SE 16

2. Design for maintainability 2. Design for maintainability

Considering: Measures of maintainability:

Measures of maintainability—elapsed times, frequencies, Corrective maintenance: unscheduled maintenance
accomplished, as a result of failure, to restore a system or
labor hours, and cost; product to a specified level of performance → initial detection
Availability and effectiveness factors; of failure(s), localization and fault isolation (diagnostics),
disassembly (access), removal and replacement (or repair) of
Maintainability in life cycle — system requirements, faulty component, reassembly, adjustment and/or alignment
maintainability allocation, component selection and (as required), and final checkout and verification of proper
system performance; that is, the corrective maintenance cycle.
application, design participation, and design review; Preventive maintenance.: Scheduled maintenance
Maintainability analysis methods accomplished to retain a system at a specified level of
performance by providing systematic inspection, detection,
Maintainability demonstration servicing, or the prevention of impending failures through
periodic item replacements.
SE – C8: Requirement in SE 17 SE – C8: Requirement in SE 18

2. Design for maintainability 2. Design for maintainability

Measures of maintainability: Measures of maintainability:

Mean corrective maintenance Mean preventive maintenance time: actions required to retain
time. a series of steps for a system at a specified level of performance. It may include
repair or restore system to its such functions as periodic inspection, servicing, scheduled
full operational status: failure replacement of critical items, calibration, overhaul,…
detection, fault isolation,
disassembly to gain access to
the faulty item, repair,..

SE – C8: Requirement in SE 19 SE – C8: Requirement in SE 20

2. Design for maintainability 2. Design for maintainability

Measures of maintainability: Measures of maintainability:

Median active corrective maintenance time: value that divides Mean active maintenance time: mean or average elapsed time
all of the downtime values so that 50% are equal to or less required to perform scheduled (preventive) & unscheduled
than the median & 50% = or greater than the median. (corrective) maintenance (logistics & administrative delay time)

Median active preventive maintenance time Maximum active corrective maintenance time: value of
maintenance downtime below which a specified percentage of
all maintenance actions can be expected to be completed

SE – C8: Requirement in SE 21 SE – C8: Requirement in SE 22

2. Design for maintainability 2. Design for maintainability

Measures of maintainability: Maintenance labor hour factors:

Logistics Delay Time (LDT)
Administrative Delay Time (ADT).
Maintenance Downtime (MDT)

SE – C8: Requirement in SE 23 SE – C8: Requirement in SE 24

2. Design for maintainability 2. Design for maintainability

Maintenance labor hour factors : Maintenance frequency factors:

Maintenance labor hours per system operating hour (MLH/OH) Mean Time Between Maintenance (MTBM). MTBM is the mean
Maintenance labor hours per cycle of system operation or average time between all maintenance actions (corrective
(MLH/cycle) and preventive) and can be calculated as
Maintenance labor hours per month (MLH/month)
Maintenance labor hours per maintenance action (MLH/MA)
With: MTBMu: mean interval of unscheduled maintenance
MTBMs: maintenance rates in terms of maintenance actions
per hour of system operation, approximate MTBF

SE – C8: Requirement in SE 25 SE – C8: Requirement in SE 26

2. Design for maintainability 2. Design for maintainability

Maintenance frequency factors: Maintenance cost factors:

Mean Time Between Replacement (MTBR) – factor of MTBM – 1. Cost per maintenance action ($/MA)
mean time between item replacements and is a major parameter 2. Maintenance cost per system operating hour ($/OH)
in determining spare part requirements. 3. Maintenance cost per month ($>month)
4. Maintenance cost per mission or mission segment ($ mission)
5. The ratio of maintenance cost to total life-cycle cost

SE – C8: Requirement in SE 27 SE – C8: Requirement in SE 28

2. Design for maintainability 2. Design for maintainability

Related maintenance factors: Related maintenance factors:

1. Supply responsiveness or the probability of having a spare part
available when needed, spare part demand rates, supply lead times for
given items, levels of inventory, and so on
2. Test and support equipment effectiveness (reliability and availability of
test equipment), test equipment use, system test thoroughness, and so on
3. Maintenance facility availability and use
4. Transportation modes, times between maintenance facilities, and
frequency
5. Maintenance organizational effectiveness and personnel efficiency
6. Data and information processing capacity, time, and frequency
SE – C8: Requirement in SE 29 SE – C8: Requirement in SE 30

2. Design for maintainability 2. Design for maintainability

Availability and effectiveness measures: Availability and effectiveness measures:

Availability: “the probability that a system or equipment, when Operational availability (Ao): used under stated conditions in an
used under stated conditions in an ideal support environment actual operational environment
will operate satisfactorily at any point in time as required.”
Inherent availability (Ai): excludes preventive or scheduled System Effectiveness (SE): “Probability that a system can
maintenance actions, logistics delay time, and administrative successfully meet an overall operational demand within a given
delay time time when operated under specified conditions” or “the ability
of a system to do the job for which it was intended.”
Achieved availability (Aa): excludes logistics delay time and
administrative delay time
SE – C8: Requirement in SE 31 SE – C8: Requirement in SE 32
2. Design for maintainability 2. Design for maintainability

Availability and effectiveness measures:

Cost-Effectiveness (CE) relates to measure of a system in terms
of mission fulfillment (system effectiveness) & total life-cycle
cost & can be expressed in various ways, depending on specific
mission or system parameters that one wishes to evaluate

SE – C8: Requirement in SE 33 SE – C8: Requirement in SE 34

2. Design for maintainability 2. Design for maintainability

Maintainability analysis methods:
Maintainability in the system life cycle:
Reliability And Maintainability Trade-Off Evaluation: trade-off
to satisfy the requirement (availability, MTBF, Mct) and cost
(R&D, investment, manufacturing, O&M)
Maintainability Prediction: early assessment of maintainability
characteristics → predict MTBM, Mct, Mpt, MLH/OH, …
Maintenance Resource Requirements (personnel & training
requirements, test & support equipment, supply support, transportation &
handling requirements, facilities, computer software, and data)

SE – C8: Requirement in SE 35 SE – C8: Requirement in SE 36

2. Design for maintainability 2. Design for maintainability
Maintainability analysis methods: Maintainability analysis methods:
Reliability-Centered Maintenance (RCM): systematic approach Total Productive Maintenance (TPM): integrated life-cycle
to developing a focused, effective, & cost-efficient preventive approach to maintenance & support of a manufacturing plant:
maintenance program & control plan for a system or product. Maximize the overall effectiveness of manufacturing equipment and
processes.
Level-of-Repair Analysis (LORA): determine whether it is
Establish a life-cycle approach in the accomplishment of preventive
economically feasible to repair certain assemblies or to discard
maintenance
them when failures occur Involve all operating departments/groups
Maintenance Task Analysis (MTA) Involve employees from the plant manager to the workers
Identify the resources required for sustaining maintenance and support Initiate a program based on the promotion of maintenance through
Provide an assessment of the configuration relative to the incorporation “motivation management” and the development of autonomous small-
of maintainability characteristics in design group activities
SE – C8: Requirement in SE 37 SE – C8: Requirement in SE 38

2. Design for maintainability 3. Design for Usability (Human factors)

Maintainability analysis methods:
Content:
Total Productive Maintenance (TPM):
A definition of human factors and human systems integration;
Overall equipment effectiveness
The common measures in human factors;
(OEE) = (availability) (performance rate)(quality rate)
Human factors in system life cycle—system requirements,
requirements allocation, design participation, & design review;
Human factors analysis methods—operator task analysis
(OTA), operational sequence diagrams (OSDs), error analysis,
and safety/hazard analysis;
Personnel training requirements; and
Personnel test and evaluation.
SE – C8: Requirement in SE 39 SE – C8: Requirement in SE 40
3. Design for Usability (Human factors) 3. Design for Usability (Human factors)

A definition and explanation of human factors: A definition and explanation of human factors:
Requirements for the human: (what – how) Human factors
Job operation: Completion of a function normally includes a Anthropometric factors: consider the physical dimensions of the
combination of duties and tasks. human body as weight, height, arm reach, hand size,… and workspace
Duty. Defined as a set of related tasks within a given job operation dimensions
Task - Subtask: Constitutes a composite of related activities Human sensory factor: human–machine interface in system design →
(informational, decision, & control activities) performed by an vision, hearing, other senses (smell, feeling – touch, balance)
individual in accomplishing a prescribed amount of work in a specified Physiological factors: Temperature extremes., Humidity, Vibration,
environment Noise, Other factors (cause stress on the body: radiation, gas or toxic
Task element. categorized as per the smallest logically definable facet substances in the air, sand and dust, and so forth
of activity (perceptions, decisions, & control actions) that requires Psychological factors: pertain to the human mind and the aggregate of
individual behavioral responses in completing a task or a subtask emotions, traits, & behavior patterns as they relate to job performance
SE – C8: Requirement in SE 41 SE – C8: Requirement in SE 42

3. Design for Usability (Human factors) 3. Design for Usability (Human factors)

Measures in human factors: Human factors in the system life cycle:

quantity of personnel required for operation, maintenance,
elapsed time to accomplish operation, maintenance
number of human errors committed by the operator per
mission, maintainer per maintenance action
Personnel training rate, quantity of personnel training days
per period of time
cost of operator personnel per hour or maintenance personnel
cost of training per individual, per organization, or per time
period
SE – C8: Requirement in SE 43 SE – C8: Requirement in SE 44
3. Design for Usability (Human factors) 3. Design for Usability (Human factors)

Human factors analysis methods: Human factors analysis methods:

Operator Task Analysis (OTA):
Identify system operator functions
Determine specific information necessary for operator
each action, determine the adequacy of the information fed back to the
human as a result of control activations, operational sequences, …
Determine time requirements, frequency, accuracy requirements
Determine the impact of the environmental and personnel factors
Determine the human skill-level requirements
Task – subtask – action stimulus – required action – feedback – task
classification – potential errors – time (allowable, necessary) – work station –
skill level → timeline and workload analysis
SE – C8: Requirement in SE 45 SE – C8: Requirement in SE 46

3. Design for Usability (Human factors) 3. Design for Usability (Human factors)

Human factors analysis methods: Human factors analysis methods:

Operational Sequence Diagram (OSD): evaluating the flow of Error Analysis: error occurs when a human action exceeds
information some limit of acceptability. Reason:
Inadequate workspace and work layout—poor workstation design
Inadequate design of facilities, equipment, and control panels for
human factors
Poor environmental conditions
Inadequate training, job aids, and procedures
Poor supervision—lack of communications, no feedback, and lack of
good planning resulting in overtime

SE – C8: Requirement in SE 47 SE – C8: Requirement in SE 48

3. Design for Usability (Human factors) 3. Design for Usability (Human factors)

Human factors analysis methods: Personnel and training requirements: training entry-level
Safety/Hazard Analysis: fundamentals of system operation - basic skill level
Description of hazard performance of operator & maintenance functions -
Cause of hazard
intermediate skill-level requirements
Identification of hazard effects
performance of operator and maintenance functions - high
Hazard classification: negligible, marginal, critical, catastrophic
Anticipated probability of hazard occurrence skill-level requirements for the system.
Corrective action or preventive measures

SE – C8: Requirement in SE 49 SE – C8: Requirement in SE 50

4. Design for Logistics and Supportability 4. Design for Logistics and Supportability

Definition: Logistics in the system-of-system (SOS) environment:

The logistics and supply chain activities associated with the Design a new system within the context of a SOS network:
initial purchasing and acquisition, manufacture and/or specified logistics & maintenance support infrastructure for this new
system is both effective & efficient & is completely responsive to new
production, transportation and distribution, & installation of
system requirements
system & its elements at appropriate customer (user)
newly developed maintenance and support infrastructure is
operational site(s); and compatible and does not in any way degrade the equivalent
The subsequent sustaining maintenance and support of the capabilities of the other systems with the same SOS configuration

system throughout its entire life cycle

SE – C8: Requirement in SE 51 SE – C8: Requirement in SE 52

4. Design for Logistics and Supportability 4. Design for Logistics and Supportability

Elements of logistics and system support Elements of logistics and system support
Resource: personnel, transportation (ground, sea, and/or air),
spares/repair parts & related inventories, test & support
equipment, facilities (maintenance, warehousing, utilities),
information/data (documentation), computer software, and
various combinations thereof

SE – C8: Requirement in SE 53 SE – C8: Requirement in SE 54

4. Design for Logistics and Supportability 4. Design for Logistics and Supportability

Measures of logistics and supportability Measures of logistics and supportability

Supply Chain Factors: capability, availability, quality Purchasing and Material Flow Factors
Purchasing: time & process a order, quantity of order/time, quality of
purchasing process (delivered complete, delivered on time, complete &
accurate documentation of order, perfect condition and configuration)
Flow of material: quantity, time, quality, cost

Transportation and Packing factors

Transportation: route, capability, time, cost
Quality: response time, total processing time, total cost of processing Packing for transportability or mobility: desired strength-of-material
an item through the logistics and maintenance support infrastructure, characteristics; stand rough handling and/or long-term storage;
process time for removing an obsolete item from the inventory, defect adequate protection against environmental conditions; compatible
rate in terms of products delivered
SE – C8: Requirement in SE 55
with existing transportation and handling methods; safety and security56
SE – C8: Requirement in SE
4. Design for Logistics and Supportability 4. Design for Logistics and Supportability

Measures of logistics and supportability Measures of logistics and supportability

Warehousing and Distribution Factors Maintenance Organization Factors
Time to ship a product (from the initial notification of a requirement). Direct maintenance labor time
Cost for product shipment (from storage to delivery at customer site). Indirect labor time required to support system maintenance activities
Cost of inventory holding & management (for the warehouse overall). Personnel attrition rate or turnover rate
Value of the products shipped/value of the overall inventory. personnel training rate or the worker-days of formal training per year
Percentage of space utilization and the cost per area of utilization. number of maintenance work orders processed per unit of time
Volume of products handled, or the total number of products average administrative delay time, or the average time from when an
processed per year. item is initially received for maintenance to the point when active
maintenance on that item actually begins.

SE – C8: Requirement in SE 57 SE – C8: Requirement in SE 58

4. Design for Logistics and Supportability 4. Design for Logistics and Supportability

Measures of logistics and supportability Logistics and maintenance support in system life cycle
Spares, Repair Parts, and Related Inventory Factors
Probability of Success with Spares Availability Considerations
Probability of Mission Completion
Spare-Part Quantity Determination
Inventory System Considerations

SE – C8: Requirement in SE 59 SE – C8: Requirement in SE 60

5. Design for Producibility, Disposability & Sustainability 5. Design for Producibility, Disposability & Sustainability

Introduction
Technological and Ecological Services:
Technological system: source of technological services – substitution of
energy for human effort (foods independent of season or local climate,
supplying potable water, modifying the climate in buildings,…)
Ecosystem services: functions of ecosystems that people desire,
including the maintenance of atmospheric balance, carbon storage,
flood control, production of food and fiber, and maintenance of air and
water quality.

SE – C8: Requirement in SE 61 SE – C8: Requirement in SE 62

5. Design for Producibility, Disposability & Sustainability 5. Design for Producibility, Disposability & Sustainability

Introduction Producibility, disposability & sustainability in life cycle

Factors Promoting Green Engineering:

objective of producers to continuously reduce environmental impact of
products, production operations, utilization, & disposal practices
Primary drivers encouraging “green”: Competitive differentiation,
Customer consciousness, Regulatory pressures, Profitability
improvement, International standards

Ecology-Based Manufacturing
eco-factory are low-energy consumption, limited use of scarce natural
resources, recycling, and reuse.

SE – C8: Requirement in SE 63 SE – C8: Requirement in SE 64

5. Design for Producibility, Disposability & Sustainability 5. Design for Producibility, Disposability & Sustainability

Measures of producibility & production progress Measures of producibility & production progress
Measures of Producibility: Measures Manufacturing Progress: Production and related
Manufacturability Measures - manufacturing lead time (MLT): the time
operations require a coordinated and integrated set of activities
needed for a product to be in the manufacturing process.
that are often repeated over time. This repetition makes
MLT = total (TSUi / QTOi + Toi + TNOi , i = 1 to nm
product process on nm machines for Q product/batch
possible improvements in the production process such as a
TO: average operational time in machine i reduction in the time to produce a unit, an increase in the rate
TSU: set up time ; TNO: nonoperational time at which selected activities are performed with a corresponding
Tp = [batch time/ machine / Q = TSU / Q + TO
increase in the number of units produced, a reduction in
Market Measures: (1) The time that it takes to move a product from the
overall time in process, and a reduction in the cost per unit of
source of manufacture to the ultimate customer and (2) The cost of
processing an item from the source of manufacture to the customer
output → learning curve
SE – C8: Requirement in SE 65 SE – C8: Requirement in SE 66

5. Design for Producibility, Disposability & Sustainability 5. Design for Producibility, Disposability & Sustainability

Design for producibility Design for producibility

A Classification of Manufacturing Processes: 5 categories Manufacturability Principles:
Forming processes. Processes in which an original shape is created from Use gravity: easier to work with lighter components, with up & down
a molten or gaseous state, or from solid particles of an undefined shape. movements… → save human & natural energy.
Deforming processes. Processes that convert the original shape of solid Use fewer parts → decrease design and manufacturing cost; purchase,
to another shape without changing its mass or material composition. assemble, & test
Removing processes. Processes in which material removal occurs during Design for ease of fabrication
the process itself. Reduce nonstandard parts
Joining processes. Processes that unite individual workpieces to make Add more functionality per part
subassemblies or final products.
Material properties modification processes: change material properties
of a workpiece to achieve characteristics without changing its shape.
SE – C8: Requirement in SE 67 SE – C8: Requirement in SE 68
5. Design for Producibility, Disposability & Sustainability 5. Design for Producibility, Disposability & Sustainability

Design for producibility Design for producibility

Manufacturability Principles: assembly for sustainability Manufacturability and Demanufacturing Issue:
Employ automatic inserters Assemble to a foundation
Employ “preoriented” parts Assemble from as few positions
Minimize sudden & frequent as possible
changes in assembly direction Make parts independently
Maximize process compliance replaceable
Maximize accessibility Order assembly so that most
Minimize handling reliable goes in first, with the
least reliable last
Assure commonality in design

SE – C8: Requirement in SE 69 SE – C8: Requirement in SE 70

5. Design for Producibility, Disposability & Sustainability 5. Design for Producibility, Disposability & Sustainability

Design for disposability Design for disposability

Disposability, Sustainability, and Industrial Ecology: Manufacturing with Recycling Applications: Recycling of
products to obtain raw materials or reusable components is an
important means of reducing disposal costs and increasing
total product value.

SE – C8: Requirement in SE 71 SE – C8: Requirement in SE 72

5. Design for Producibility, Disposability & Sustainability 6. Design for Affordability (Life-cycle Costing)

Life cycle value cost diagram Introduction to life-cycle costing

SE – C8: Requirement in SE 73 SE – C8: Requirement in SE 74

6. Design for Affordability (Life-cycle Costing) 6. Design for Affordability (Life-cycle Costing)

Introduction to life-cycle costing Introduction to life-cycle costing

Cost growth resulting from engineering changes
Cost growth resulting from changing suppliers
Cost growth resulting from system production or
construction changes
Cost growth resulting from changes in the logistic support
capability
Cost growth resulting from initial estimating inaccuracies and
from changes in estimating procedures
Cost growth resulting from unforeseen problems
SE – C8: Requirement in SE 75 SE – C8: Requirement in SE 76
6. Design for Affordability (Life-cycle Costing) 6. Design for Affordability (Life-cycle Costing)

Introduction to life-cycle costing Cost considerations over the system life cycle

SE – C8: Requirement in SE 77 SE – C8: Requirement in SE 78

6. Design for Affordability (Life-cycle Costing) 6. Design for Affordability (Life-cycle Costing)

Generic life-cycle costing process Cost considerations over the system life cycle
1. Define system requirements and TPMs: Define operational 3. Develop a cost breakdown structure. Provide a top-
requirements and the maintenance concept. Identify down/bottom-up cost structure. Include all categories for the
applicable technical performance measures (TPMs) and initial allocation of costs (top-down) and the subsequent
describe the system in functional terms, using a functional collection and summary of costs (bottom-up).
analysis at the system level. 4. Identify input data requirements. And all possible sources
2. Specify the system life cycle & identify activities by phase. of input data. The type and amount of data will depend on the
Establish a baseline for development of a cost breakdown nature of the problem, the phase of the life cycle, and the
structure (CBS) & for estimation of cost for each year of depth of analysis.
projected life cycle, should involve all life-cycle activities.
SE – C8: Requirement in SE 79 SE – C8: Requirement in SE 80
6. Design for Affordability (Life-cycle Costing) 6. Design for Affordability (Life-cycle Costing)

Cost considerations over the system life cycle Cost considerations over the system life cycle
5. Establish costs for each category in the CBS. Develop the 7. Develop a cost profile and summary. Construct a cost
appropriate cost-estimating relationships and estimate the profile showing the flow of costs over the life cycle. Provide a
costs for each category in the CBS on a year-by-year basis over summary identifying the cost for each category in CBS &
the life cycle. Be sure all costs are included. calculate the percentage contribution in terms of the total.
6. Select a cost model for analysis and evaluation. Select (or 8. Identify high-cost contributors and establish cause-and-
develop) a mathematical or computer-based model to effect relationships. Highlight those functions, system
facilitate the life-cycle costing process. The model must be elements, or segments of processes that should be
valid for and sensitive to the specific system being evaluated. investigated for possible opportunities for design
improvement and/or cost reduction.
SE – C8: Requirement in SE 81 SE – C8: Requirement in SE 82

6. Design for Affordability (Life-cycle Costing) 6. Design for Affordability (Life-cycle Costing)

Cost considerations over the system life cycle Cost considerations over the system life cycle
9. Conduct a sensitivity analysis. Evaluate the model input– 11. Identify additional alternatives. After developing an
output data relationships and the results of the baseline approach for the LCC evaluation of a given baseline
analysis to ensure that the overall LCC analysis process is configuration, it is then appropriate to extend the LCC
valid and that the model itself is well constructed and analysis to the evaluation of multiple design alternatives.
sensitive. 12. Evaluate feasible alternatives and select a preferred
10. Identify priorities for problem resolution. Construct a approach. Develop a cost profile for each feasible design
Pareto diagram and conduct a Pareto analysis to identify alternative, compare the alternatives equivalently, perform a
priorities for problem resolution (i.e., those problems that are break-even analysis, and select a preferred design approach.
most important to remove in terms of their impact on value).
SE – C8: Requirement in SE 83 SE – C8: Requirement in SE 84