|

| |
LECTURE NOTES
FOR SYSTEMS ENGINEERING AND ANALYSIS
as presented for
ISU - AeroE/EE/IE 565
by
Michael J. McCann, Ph.D.
Copyright (C) Michael John McCann, 1994. All rights reserved.
Iowa State University
IE 565 Systems
Engineering and Analysis
NETWORKING AND PROFESSOR ACCESS
COURSE DESCRIPTION
COURSE SYLLABUS
CLASS PROCEDURES
TEXT BOOK
INSTRUCTOR BACKGROUND
STUDENT INTRODUCTIONS
INTRODUCTION
Instructor Access
The instructor will maintain an "open door" policy encouraging phone calls
and visits. The reason for this policy are:
1. Often students will become frustrated over small details that prevent understanding
the subject.
2. The instructor's major source of feedback is through student questions. Often during
the class period students hold back questions waiting to review the material at a later
date. Without questions the instructor is guessing as to what areas of the material are
not getting across.
3. Material not understood by one student is often missed by others.
4. The exams determine a major portion of the grade. Repeated phone calls or visits
will NOT lower a students grade. It is better to frustrate the instructor before the exam,
and do well on the exam, than to argue for a higher grade after the exam.
The student has paid a fee for the educational service and has the right to ask for
assistance. The student should utilize this assistance as much as possible.
Course Description
AerO/EE/IE 565 is the INTRODUCTORY course for the Master's degree in systems
engineering. A program of study designed to apply an iterative process of definition,
optimization, synthesis, analysis, design, test and evaluation to transform an operational
need into a system configuration. Included are the concepts of reliability,
maintainability, safety, survivability, economic feasibility, human factors, and
management.
Course Syllabus
The course is divided into three parts. The first part is a summary of systems
engineering METHODOLOGIES and how they apply to the environment of the student. The second
part is a review of the basic economic, mathematical, and statistical CONCEPTS utilized in
systems engineering. The third part is a overview of the PRACTICES utilized by systems
engineering and their basic procedures.
Syllabus - Fall 1999
Professor: Michael J. McCann Ph.D. Phone: Hm.(515)-753-5195 ISU
(515)-294-4056
Text: Systems Engineering and Analysis by Benjamin S. Blanchard, third
edition
Methodology
Tape# |
Date |
Chapter |
Topic |
Problems |
| 1 |
Aug 24 |
1 |
Introduction to
systems |
1.2,3,7,8,10 |
| 2 |
26 |
2 |
The life cycle
process |
2.3,7,17 |
| 3 |
28 |
3 |
Conceptual
design |
3.2,4,7,9,18,20 |
| 4 |
31 |
3.5,6,7 |
Preliminary design -
FAST |
3.17 |
| 5 |
Sept 2 |
4 |
Preliminary design -
FFBD |
4.3,4*,8,9,13 |
| 6 |
4 |
5 |
Detail design - computer
integration |
5.1,14,16,18 |
| 7 |
9 |
6 |
Systems test and
evaluation |
6.2,3,4,10,13,17 |
| |
11 |
|
Quiz 1 |
|
Theory and Conceptual Models
| Tape# |
Date |
Chapter |
Topic |
Problems |
| 8 |
Sept 14 |
8 |
Economic evaluation -
sums & worths |
8.1,2,3,4,5,6,7 |
| 9 |
16 |
" |
Economic evaluation -
equivalence |
8.9,10,11,12a,16 |
| 10 |
18 |
" |
Economic evaluation -
comparisons |
8.15,17,18,20,22 |
| 11 |
21 |
" |
Economic evaluation -
break-even |
8.25,27 |
| 12 |
23 |
7 |
Decision making - tables |
7.28,29,30,31 |
| 13 |
25 |
" |
Decision making - trees |
8.14 |
| 14 |
28 |
11.4 |
Project control -
schedule networks |
|
| 15 |
30 |
" |
Project control - CPM
analysis |
11.12,13,15ab,16ab |
| 16 |
Oct 2 |
" |
Project control - PERT |
11.17,18 |
| 17 |
5 |
B.1 |
Probability theory |
|
| 18 |
7 |
B.2 |
PDF - binomial and
Poisson |
|
| 19 |
9 |
" |
PDF - exponential and
normal |
|
| 20 |
12 |
" |
Statistics and inference |
|
| 21 |
14 |
" |
Null hypothesis |
|
| 22 |
16 |
" |
notes Regression - least
squares fit |
|
| 23 |
19 |
" |
Regression - statistics |
|
| 24 |
21 |
11 |
Shewhart charts - X and R
charts |
11.5,6,7,8,9,10 |
| 25 |
23 |
" |
Shewhart charts - p chart |
11.8 |
| 26 |
26 |
" |
Shewhart charts - c chart |
11.8,9,10 |
| 27 |
28 |
|
Review |
|
| 30 |
|
|
Quiz 2 |
|
Design Procedures
| Tape# |
Date |
Chapter |
Topic |
Problems |
| 28 |
Nov 2 |
18 |
Management - project control |
18.6,11,12 |
| 29 |
4 |
19 |
Management - cost control |
|
| 30 |
6 |
" |
Management - C/S integration |
|
| 31 |
9 |
17 |
Management - life cycle costs |
17.6,8,13,19 |
| 32 |
11 |
12 |
Reliability - distributions |
12.1,6,7,8,9 |
| 33 |
13 |
" |
Reliability - allocation |
12.12,28,26 |
| 34 |
16 |
" |
Reliability - test and evaluation |
|
| 35 |
18 |
13 |
Maintainability - terminology |
13.4,5,7,8,9 |
| 36 |
20 |
" |
Maintainability - allocation |
13.11,13,25,26 |
| 37 |
30 |
" |
Maintainability - test and evaluation
|
|
| 38 |
Dec 2 |
14 |
Human factors |
14.1,2,4,5,8,11 |
| 39 |
4 |
" |
Methods time measurements |
|
| 40 |
7 |
" |
Job design |
14.14,17 |
| 41 |
9 |
notes |
Concurrent engineering |
|
| 42 |
11 |
|
Review |
|
| |
14-18 |
|
Final exam week |
|
*Try
CLASS PROCEDURE
Course Content: The course reviews the methodologies, the
conceptual models,
and the basic design practices of systems engineering and analysis.
Text: Systems Engineering and Analysis by Benjamin S. Blanchard,
Third edition
Teaching emphasis: The class is assumed comprised of managers and
engineers.
Grading procedures: Two 100 point quizzes and one 200 point final
exam will be given. The final exam will cover all course materials. Final letter grades
will be calculated by adding all exam scores and dividing by 4 where A = 100 to 85, B = 84
to 75, C = 74 to 65, D = 64 to 55, F = 54 to 0. The instructor reserves the right to
adjust individual final scores by plus or minus 5 points based on class performance.
Exams: Exams will cover the use of course procedures for solving
written problems. Approximately 10 minutes will be given for each assigned problem. The
points scored on any test problem is based on the demonstrated solution procedure. As a
result, the final answer for a problem is only worth 20% of the problem's points.
If the average class score for an exam is below 75 points, the
difference between the average score and 75 points will be added to all of the individual
scores. This means that on some occasions some individuals might score greater than 100
points on an exam.
Before an exam, the instructor will give all possible assistance. When the exam is
started, the student is competing with the other students and is graded accordingly.
After completion of the exam the student will bring the exam to the
front of the room where all work submitted will be stapled together. Any material not
stapled in the exam packet will not be used for grading.
Make up exams will be given if requested, but the exams will be new
exams. Any exam not taken will be considered to have a zero score.
Failure on one exam does NOT mean an A is impossible in the course.
Several students in the past have gotten As with one failed exam.
Homework: Home work will be voluntary. If the homework is turned
in before
each exam, the work may be used to mitigate the effects of a "panic" on the
exam. Otherwise, the instructor will assume the exam reflects the knowledge of the
student.
Text Book
The text for the course is Systems Engineering and Analysis by Benjamin S. Blanchard.
As an INTRODUCTORY text the book has several handicaps:
1. The book covers too much material in too little time.
2. As a result, the book simplifies too many topics.
3. The book utilizes too much jargon especially from the military.
4. The book has too much of a focus on maintenance.
On the other hand, as an introduction, the book does quickly cover many of the topics
of interest and provides a starting point for other courses in the systems engineering
degree.
SYSTEMS APPROACH
HISTORICAL FIGURES
A. ADAM SMITH
B. ELI WHITNEY
C. FREDERICK TAYLOR
D. LORD MOUNTBATTEN
E. JAY FORRESTER
F. W. EDWARD DEMING
SYSTEMS DEFINED
A. DEFINITION
B. PROPERTIES
C. CLASSIFICATIONS
SYSTEM ENGINEERING
A. DEFINITION
B. PROCESS
C. MANAGEMENT
SYSTEMS APPROACH
History of Systems Approach
The easiest way to gain an understanding of the methodology of systems engineering is
to understand the historical development of the process. Major characters, but not all, in
the development of systems engineering history would be:
Adam Smith - Product-reduction (analysis)
Adam Smith developed the idea that a PRODUCT could be reduced to COMPONENTS
(reductionism). The components then could be manufactured cheaply and efficiently by many
skilled craftsmen manufacturing just one component each rather than the whole product.
Eli Whitney (LeBlanc) - Product-systems (synthesis)
Eli Whitney viewed a product as a SYSTEM of components or the synthesis of parts, that
not only could be manufactured efficiently but also could be repaired and updated after
the product system was in use.
Frederick Taylor (Char.Babbage) - Management Science (analysis)
Fredrick Taylor developed the idea that WORK could be reduced to COMPONENTS. Taylor did
not believe in using skilled labor since the component tasks to be performed were reduced
to the basic motor skills of the average laborer. He developed the concept of the
"functional organization" and the science of management.
Lord Louis Mountbatten - Operations Research (synthesis)
Mountbatten was in charge of the operations research team for the invasion of Europe.
Although Taylor's concepts worked well for large manufacturing systems, the invasion of
Europe required the coordination of disciplines or a management SYSTEM not found in
American industry. The result of Mountbatten's efforts was the military planning strategy
called combined operations.
Jay Forrester - Systems Dynamics (synthesis of all aspects of systems)
Forrester was one of the early computer designers who came to the realization that
computers could be used to model dynamic social and product systems. His work was often
used to challenge conventional economic theories by demonstrating unexpected RELATIONSHIPS
between components of systems. His ideas led to the development of system modeling and
system design on the total system level.
W. Edward Deming - Total Quality Management
Deming carried the systems approach to quality control to Japan and set the world
standard for manufacturing quality.
Careful observations of the history of systems analysis will show a repeated cycle of
ANALYSIS, or study of the parts, to SYNTHESIS, or studying the affect of the part on the
whole. This is the result of two basic philosophies. REDUCTIONISM believed everything
could be reduced to simpler components and MECHANISM believed everything is controlled by
cause and effect relationships.
The objective of systems engineering is to understand the whole relative to its parts
by studying the synthesis of systems.
Systems defined
A SYSTEM is an assemblage of components forming a unity based on the functional
relationships between the components.
- COMPONENTS are the elements of a system. Components can often be divided to smaller
elements or components.
- ATTRIBUTES are the properties or discernible manifestations of the components.
- RELATIONSHIPS are the mechanistic links between the components and attributes of the
components.
Properties of Unity
- The attributes of any component has an affect on the attributes of the whole system.
- The attributes of any component depend on the attributes of at least one other component
of the system.
- The components cannot be divided into independent subsystems based on attributes.
These properties ensure that the set of components comprising a system has some overall
attribute that cannot be exhibited by any of its subsystems.
Classifications of systems
- ENVIRONMENT is the total system of the universe.
- CLOSED SYSTEM is a system that does not interact with or have relationships with the
environment. In most cases these systems are conceptual only.
- OPEN SYSTEM is a system that interacts with the environment and has relationships and
components, called INPUTS and OUTPUTS, shared with the environment. The shared
relationships define the BOUNDARIES of the system. Open systems often from
SUBSYSTEMS of other systems.
- STATIC SYSTEMS are systems that do not change over time. These systems are often
conceptual or subsystems of larger systems.
- DYNAMIC SYSTEMS are systems that change over time.
- NATURAL SYSTEMS are systems that come into being in the natural environment.
- MAN-MADE SYSTEMS are systems devised by mankind to provide the desired outputs for
the given inputs.
- FUNCTION is the purposeful attributes of a man-made system.(The buzzers and
whistles we want to see or hear.)
- ENTROPY consists of the components and relationships of the system that do not
contribute to its function. It can be viewed as the unusable functions and components
- Relationships between components can be classified using the system function.
- FIRST ORDER relationships are necessary for the system to performs its function.
- SECOND ORDER relationships are complimentary or add to the system function.
- REDUNDANT relationships are duplicate relationships present to assure system function.
- PROCESS (noun) is the cumulative effect of all aspects of a dynamic system over time.
This is often further defined as an adjective for a type of systems:
- PROCESSING SYSTEM is a man-made system consisting of components that ALTER materials,
energy, or information.
- A convenient classification of components is:
- FLOW COMPONENTS are the material, energy, or information being
altered. Many times the flow components that are both inputs and
outputs are called THROUGHPUTS.
- STRUCTURAL COMPONENTS are the static components of a system or
any component that is not altered over time.
- OPERATING (PROCESSING, ACTIVITY) COMPONENTS
are the dynamic components of the system that alter flow components. Operations are often
described by their effect on the flow components of the system. In this manner many
operations are actual described as functions. As an example, a "baking"
operation is actually the operation that changes the attributes of the flow component pie
in the structural component oven with flow component heat.
- PRODUCT-SYSTEM - is a processing system that is related to some
commercial product such as a military system and a tank, transportation system and a car,
electrical system and a television, information system and a computer. The function of
most product-system is to provide a social benefit beyond simply the production of the
product.
- CYBERNETIC SYSTEMS are subsystems that govern a system toward its function. (In natural
systems unity is considered its function.)
Describing a systems is often an ART that imposes arbitrary boundaries and assumptions.
The greater the success in determining the components and relationships that determine the
system function, the better the understanding of the system.
SYSTEMS ENGINEERING AND MANAGEMENT
ENGINEERING is the profession in which a knowledge of
the mathematical and natural sciences gained by study, experience, and practice is applied
with judgment to develop ways to utilize, ECONOMICALLY, the materials and forces of nature
for the benefit of mankind.
SYSTEM ENGINEERING is the iterative PROCESS employed
in the evolution of man-made SYSTEMS from the point when a need is identified through
deployment of that system for use. Systems engineering involves the application of effort
to:
- TRANSFORM a need into technical performance parameters
(TPM) and system configurations through the iterative process of NEED DEFINITION,
FUNCTIONAL ANALYSIS and SYNTHESIS, OPTIMIZATION, SPECIFICATION, DESIGN, TEST and
EVALUATION.
- assure COORDINATION of all physical, financial, and
program interfaces.
- assure INTEGRATION of all engineering specialties into
the overall engineering effort.
Systems engineering in many ways is the synthesis of
the engineering design disciplines as defined by modern industry. A list of disciplines
covered in just this course are:
Reliability Engineer Maintenance Engineer Human Factors Engineer
Manufacturing Engineer Logistics Engineer Industrial Engineer
When dealing with systems, some, or all, of the
engineering disciplines might play a role. Although most engineering practitioners would
prefer to be isolated (closed system) in their particular field, the reality is that an
integration is necessary for a successful synthesis of a system.
SYSTEM ENGINEERING MANAGEMENT is the bringing of
scientific and engineering talent (people) systematically to bear on the evolution of a
man-made system. The effort is accomplished primarily through team building and the
systematic integration of multiple disciplines and skills.
For the remainder of this course systems engineering
will be limited to the manufacturing disciplines. This will allow for the development of a
methodology relative to the PRODUCT-SYSTEM most commonly found in manufacturing. This does
not imply that the same approach can not be used for a wider set of system using the
principles.
QUESTIONS 1
- The work of Frederick Taylor was a great contribution
to the success of American business. What aspects of the "game", if any, have
changed making the classical functional organization, utilizing minimum skill labor,
obsolete?
- Is a clock a system? If so, what
are the components, the relationships, and the attributes? Since the clock is man-made,
what is the useful attribute or function of the clock? Is the clock an open or closed
system, static or dynamic system. If the owner of the clock is included in the system,
describe the cybernetic aspects of the total system.
- You have a battery attached to a
light bulb. View the system as a processing system. What are the flow components, the
structural components, the inputs, the outputs? What is the process component of the
system?
- Your professor claims that all
objects fall toward earth with the same acceleration. You have taken your favorite beach
ball and bowling ball to the top of the leaning tower of Pisa to duplicate the original
Galileo experiment. Describe the system that your professor is envisioning. Describe the
system you are going to experiment with? Will the predicted system attributes be the same?
Who is correct and who is wrong?
- In structural engineering, one
approach to analyzing structural systems is called statics. This approach often fails when
structures are static indeterminate. From a systems engineers point of view, what type of
conceptual system is involved and what type of real world system? How did the boundaries
set for the conceptual system fail to provide system unity.
- You are reading this question on
the final exam. As a systems engineer, what are the transformation steps or the
engineering process your are going through to answer the question?
- Systems engineering is often
coordinated with team building. What aspects of the systems engineering procedures
compliment team organization development?
CASE STUDY 1 - Instant
Photography
Eastman Kodak Company attempted to compete with
Polaroid in the instant photography market. The Company designed the cameras, produced the
film, and set up the marketing organization with the plan of marketing the product for the
holiday season of 1976. One month before the product was to be released to the public,
Consumer's Guide reported that the color stability of the product was poor. Eastman Kodak
pulled its total inventory from the dealers only to find that the the new Polaroid camera
filled the market sector created by the Kodak advertising. This mistake cost Eastman Kodak
over one billion dollars and the whole instant photography market.
Look at this situation from the systems approach.
ANSWERS 1
- Taylor believed in Scientific Management or the
reduction by management of production systems to the lowest labor components that can be
effectively performed by unskilled labor. The idea was the product of 1900s America and
now finds difficulty in the 1990s because of:
- The cheap unskilled immigrant labor of the 1900s that
Taylor's system worked well with is no longer available.
- Customers are demanding quality products rather than
commodity products. As a result, Taylor's top down management structure fails to innovate
and adapt to the rapidly moving standards required by quality seeking customers.
- Product liability and social responsibilities have
forced manufactures to view a broader picture of their operations.
- The confrontational situation between labor and
management "experts" has proven counter productive.
- Organizations utilizing Taylor's function lines have
become top heavy with redundant staff.
- The gears are the components and
the inter-mesh of the gears are the relationships. The attribute of the clock is the
relative positioning of the hands over time. The useful attribute of the clock or its
function is the synchronization of the hands with the motion of the earth. The clock, like
all systems, is an open system with the winding the input and the motion of the balance
wheel the output. If there is an owner using the clock, then the output of the clock is
also the information passed to the owner. In this case the owner is also a feedback loop
acting as a cybernetic subsystem.
- The light circuit is a
processing system in which the electrons are flow components, the wire, bulb, battery are
structural components, and transformation of chemical energy to electron motion and the
transformation of electron motion to light are the processes.
- The professors system is a
closed system considering only the balls and the gravitational field of the earth. Your
system is an open system including the air resistance. The two systems views will give
contradictory attributes. Both people are correct within their definition of the system.
- The structural analysis approach
using statics is too limited a system to provide useful results in the indeterminate
world. The best way to check if the static system is a true system is to see if enough
relationships exist to define a complete or stable structural system - unit.
- NEED or what does the guy want?
ANALYSIS or what is given in the question? SYNTHESIS or what can I dream up? OPTIMIZATION
or which idea will he buy? SPECIFICATION or how can I say this? PRODUCTION or can he read
what I am writing? TEST or turn in the exam? EVALUATION or what is my grade?
- Systems engineering develops the
mathematical models and procedures necessary to study complex interrelated problems. Team
building develops the organizational and personal skills required to utilize the systems
engineering procedures.
PRODUCT-SYSTEM
CONSUMER-TO-CONSUMER PROCESS
PRODUCT-SYSTEM LIFE-CYCLE
A. COST ENGINEERING
B. DESIGN
C. MANUFACTURING
D. SUPPORT
SYSTEMS ENGINEER'S INTEGRATED
LIFE-CYCLE
A. CONCEPTUAL DESIGN
B. PRELIMINARY DESIGN
C. DETAIL DESIGN
D. PRODUCTION
E. UTILIZATION AND SUPPORT
F. DISPOSAL
PRODUCTS VIEWED AS A SYSTEMS
The
Consumer-to-Consumer Process
For the course we will concentrate on a type of
processing system that we find in most engineering applications, or the PRODUCT-SYSTEM.
The first step in studying any system is the definition of the components of the system.
One approach is to view a product-system from the limited point of view of the business
school by reducing the product "process" to components such as:
Identification of need Planning
Research Design
Production Evaluation
Use Logistic support
The component, when linked by their relationships,
form a subsystem called the CONSUMER-TO-CONSUMER PROCESS.

The systems engineer must consider a larger boundary
for the PRODUCT-SYSTEMS than the business manager, in other words a product -system must
include the product and all processes related to the product over time. Such an approach
is dynamic or has a set of components called a "LIFE-CYCLE" relative to TIME.
Different View of the
Product-System Life-cycle
One obvious example of the components of a life-cycle
is the cost engineer's REVENUE CURVE or the graph of the cash flow generated by a
product-system over time.

The cost engineer's point of view of a product-system
has components called "phases" defined by MILESTONES such as the "break
even point", "payback" or "economic life". Since in most cases
the termination of a product-system is set at the economic life when other sources of
revenue become more attractive, the economic life for a product-system is often accepted
as the end of the product-system life-cycle.
(Note: At a later time we will discuss life-cycle
costing or LCC. The LCC procedure is the cost engineer's analysis of the product-system
over the phases of the economic life-cycle.)
The cost engineers economic life-cycle is not the
only life-cycle system, or SUBSYSTEM, associated with a product-system. There is also a
design life-cycle, manufacturing life-cycle, logistic support life-cycle, etc. When these
different professional functions are viewed together, the following diagram can be
constructed of interrelated (open dynamic) subsystem life-cycles.
From the view of a systems engineer, the many
life-cycles must be considered simultaneously in order to TRANSFORM, COORDINATE, and
INTEGRATE their components functions as a whole.
Product-system
Life Cycle Process
In engineering a product-system, it is often
convenient to consider a set of STANDARDIZED life-cycle phases or accepted groupings of
processes that most product-system progress through over time. Although many different
approached have been formulated for the product-system life-cycle (see illustrations), the
formalized structure defined by Blanchard and used extensively is:
1) Design and development
2) Production or construction
3) Operational use and support
(Note: This approach is heavily biased toward the
design engineers view of systems and one must continually consider the other interrelated
systems.)
Blanchard's structure can be further refined by
considering phases between major milestones or reviews within the system life-cycle.
6 images will be added later
.
Design and
development
CONCEPTUAL PHASE - defining the NEED and FEASIBILITY
of a system, its technical performance parameters (TPM), operational requirements (DDP) or
MISSION, and support polices. The primary documentation for the phase is the systems
specification (A) and the initial program management plans (PMP, SEMP, TEMP).
PRELIMINARY DESIGN PHASE - performing the FUNCTIONAL
analysis of the system, EVALUATING different alternative design approaches for the best
approach. The primary documents for this phase are the development plan (SEMP), process
FAST diagram, and performance specifications (B).
DETAIL DESIGN PHASE - preparing functional design
layouts and etc., developing system prototypes, and performing design modifications to
correct deficiencies and /or improve design. The primary document out of this phase is the
product (C), material (D), and performance specifications (E).
Production or construction
PRODUCTION PHASE - combining operations, materials,
and personnel resources in such a manner as to provide the necessary product-system output
in an effective and efficient manner.
Operational use and support
UTILIZATION AND SUPPORT PHASE - providing consumer
use of the product-system throughout its life-cycle, incorporating product modifications
for improvements, and providing logistical support.
PHASE OUT AND DISPOSAL PHASE - disposing or replacing
of a product system due to obsolescence or wear.
Within the phases are a series of iterative
procedures diagrammed as follows:
Product-System Life-Cycle Process



*Note: the book in places will use these expressions
to mean the same thing.
QUESTIONS 2
- Great emphasis has been placed on the
customer-to-customer process. What market conditions today make this approach so
important? Does it adequately represent the product-system from the systems engineer's
point of view?
- The driving factor for most
product-systems is revenue. What is the expected revenue curve associated with a
product-system life-cycle? What are major decision points along the revenue curve. What is
the most common definition of the end of the product-system life-cycle?
- Using your own functional area,
describe the product-system life-cycle from your point of view?
- Every functional discipline
within a company has a different concept of the product-system life-cycle. What is the
goal of systems engineering when defining the product-system life-cycle?
- The consumer-to-consumer process
has an acquisition phase and utilization phase. Product-system life-cycle is divided into
three major phases. What are they? These phases are often divided again for a total of six
phases. What are they? What is the motivation for using these phases?
- Each phase of the system
life-cycle are followed by a reporting and approval process. What documentation and
results should be expected at the end of each phase?
CASE STUDY 2 - The Weapons
Program
The Peter Kiewit Company constructed the Oak Ridge
Atomic Facility and most of the Hanford Weapons Facility. From the point of view of the
Kiewit Company the facilities were construction projects. From the point of view of the
Department of Defense the facilities were weapons systems. From the point of view of the
Department of Energy the facilities are clean-up projects. In fact during each
"situation" of the facilities life, each governing agency or contractor had
total control.
What has been the result of this "situational
management style" and how would the product-system life-cycle apply to the atomic
project using twenty-twenty hindsight.
Health Care Legislation
The currently proposed national health care
legislation will follow a series of planning steps as required by law. It is possible to
view these steps in terms of a product-system life-cycle.
CONCEPTUAL DESIGN PHASE - White house
staff study with President's approval

Phase completed with Presidential submittal to Congress

PRELIMINARY DESIGN PHASE - Committee actions in the House and Senate

Phase completed with Committee votes

DETAIL DESIGN PHASE - Debate of full House and Senate

Phase completed with vote of House and Senate

PRODUCTION PHASE - Executive orders in the Executive Branch

Phase completed with approval of the President

USAGE AND SUPPORT - Care administered by health care system

Phase completed with support of public and medical profession

PHASEOUT - Undefined
ANSWERS 2
- With the focus on quality in todays markets the
products must be closely tied to consumer needs. The consumer-to-consumer process is based
on this requirement. What the consumer-to-consumer process does not consider is the time
element of the product-system that is required for the coordination of the product-system
life-cycle.
- The revenue curve, maintained by
the cost engineer, which starts at a loss, reaches a positive return, a payback, and then
finally declining to a diminishing return, is usually the driving force in most
product-systems. As such, the economic life is considered the termination of most
product-systems life-cycles.
- Discuss.
- The systems engineer is
developing a framework on which to coordinated all subsystems or disciplines involved in
the product-system. As such, the phases defined are often inadequate when viewed by any
one discipline.
- The book has been dividing
product-systems into smaller and smaller phases. First for the consumer-to-consumer
process there was the acquisition phase and utilization phase. Then the design and
development phase, production phase, and operational phase. Then the conceptual design
phase, preliminary design phase, detail design phase, production phase, utilization phase,
and phase out.
- Discuss. The most common reports
are the system specification, program management plan (PMP) for the end of the conceptual
phase. The development and performance specification and the systems engineering plan
(SEMP) at the end of the preliminary design phase. The product, material, and performance
specifications at the end of the detail design phase. The statistical process control SPC
reports (Shewart) and cost reports during the production phase. And the cost reports at
the phase out.
CONCEPTUAL DESIGN PHASE
DEFINITION OF NEED
FEASIBILITY STUDY
SYSTEM OPERATIONAL SPECIFICATION
A. OPERATIONAL CONCEPT
B. PRELIMINARY SYSTEM ANALYSIS
C. SYSTEM SPECIFICATION
SYSTEM PLANNING
A. PROGRAM MANAGEMENT PLAN - PMP
B. SYSTEM ENGINEERING MANAGEMENT PLAN - SEMP
C. TEST AND EVALUATION MASTER PLAN - TEMP
CONCEPTUAL DESIGN REVIEW - CDR
CONCEPTUAL
DESIGN PHASE
Conceptual design is an iterative process with the objective of defining a SYSTEMS
specification (A) for the product-system. The actual product configuration is not defined,
only the requirements and mission that the product-system must satisfy. Conceptual design
usually progresses through the following processes.
DEFINING THE NEED - the first step in conceptual design is defining a need from a set
of desires and researched information. These "needs" might not be realistic on
the first iteration of the conceptual design phase and can be adjusted as more is learned
about the product-system as a whole.
FEASIBILITY STUDY - the feasibility study defines the stated need in terms of known
technical approaches in order to predict whether the need can be satisfied. In many cases
the need will be modified and the feasibility study repeated. The idea is to reject or
modify "needs" as quickly as possible without getting involved in a hardware
design.
SYSTEM OPERATIONAL SPECIFICATION - is the process of establishing the OPERATIONAL
CONCEPT for a system compatible with known technical approaches, conducting a PRELIMINARY
ANALYSIS to establish operational alternatives, and specifying design criteria for a
preliminary system design.
The basic steps in defining the OPERATIONAL CONCEPT are:
- Identify the primary operating MISSION of the system along with secondary missions.
- Define the operating ENVIRONMENT.
- Define the USAGE of the system in the operating environment.
- Define the TECHNICAL PERFORMANCE MEASURES (TMP) or metrics. (speed, output, weight,
accuracy, etc.)
- Anticipate DEPLOYMENT and maintenance requirements and operating life cycle.
Note: The book breaks out the MAINTENANCE CONCEPT from the deployment, I think this is
a bit of over kill.
Define EFFECTIVENESS FACTORS (actual
performance/TPM).
The PRELIMINARY SYSTEM ANALYSIS (advance design) consists of:
- REFINING the definition of the need. This step is often the most difficult because the
temptation is to rework the need to fit the alternatives that are available.
- Selecting feasible alternatives systems.
- Establishing evaluation or design dependent parameters. (DDP)
- Applying modeling techniques. These studies rely heavily on conceptual models such as:
- Economic models - Budget planning, Benefit/cost
- Decision models - Games, scenarios
- Statistical models - Reliability, process control
- Physical models - mockups,
- Generating input data that represents the operating environment.
- Manipulating or optimizing the model.
Establishing the design criteria for the system is accomplished using a
SYSTEM SPECIFICATION (A) that usually covers the following areas:
- General system description.
- Operational requirements.
- Maintenance concept definition.
- Performance characteristic. (TPM)
- Physical characteristics.
- Effectiveness characteristics.
- Design characteristics.
- Logistic support.
- Design documentation.
- Construction requirements.
SYSTEM PLANNING is defining the organizational requirements to manage the system
development and usually consists of:
- Technical program planning and control which describes the program tasks that must be
planned and developed relative to the system life-cycle to ensure system engineering
objectives. The most common conceptual model for this planning is the CPM method.The three
major areas of planning (and reports) are:
- Program management plan (PMP) established the organization authority for the program and
the commitment of resources by the total organization.
- System engineering management plan (SEMP) defines the engineering requirements of the
system in terms of tasks derived from the system life-cycle process. In this manner the
resources required for the program can be developed as well as a tentative schedule.
- Test and evaluation master plan (TEMP) coordinates the testing program through the
different phases of the system life-cycle.
- Organizational development and team building to structure the organizational resources
to satisfy the technical program.
CONCEPTUAL DESIGN REVIEW (CDR) is the organizational and technical review of the
conceptual design required before any further effort can be expended on the system. The
formal review consists primarily of:
- A formalized record of agreed upon SPECIFICATIONS.
- Establishing a design BASELINE.
- Promoting INTEGRATION of disciplines.
- Fostering group participation and COORDINATION.
QUESTIONS 3 - Conceptual Design
- One of the most difficult tasks facing any organization is acquiring new ideas. What
systems are available within your company for promoting and capitalizing on new ideas?
- What is the basic yardstick or criterion used to measure the
feasibility of new ideas?
- What are the basic steps in establishing the OPERATIONAL CONCEPT?
- "Specing" a SYSTEM requires developing alternative
SYSTEMS rather than alternative products. What is the importance of this distinction?
- What is the model used in preliminary analysis most often used by
upper management to decide on system alternatives.
- System PLANNING can be viewed from three points of views as
reflected in the conceptual plan. What are the three management plans formulated in the
conceptual design phase?
- The formal review and approval at the completion of the conceptual
phase has several major objectives. What are they?
CASE STUDY 3 - Household Fire Safety System
Need
A need has been established for a system to prevent household injuries from fire.
Feasibility
Under current technologies there are three alternatives. The first alternative is
defensive, utilizing protective clothing and materials. The second alternative is
offensive, utilizing fire extinguishers and smoke barriers, and the third alternative is
avoidance, utilizing warning devices.
The first alternative would be infeasible because of the burden placed upon occupants
wearing protective clothing. The second alternative is feasible, but rather costly; and
the third alternative is practical given that the warning device can be made reliable and
timely.
Revised Need
A need for a system that can cheaply and reliably warn of household fire hazards.
System Specification
operational concept
(mission) The mission of the system is to provide warning of fire in a timely manner.
The environment in which it will operate is the typical household. (usage) The system must
detect fire before the fire is lethal and warn the residents of the house. (parameters)
This means that the system must detect either toxic smoke or intense heat and
(effectiveness) sound an alarm that is detectable by sleeping individuals at any location
in a house. (deployment) The system must be easily installed and maintained by the average
handyman and (effectiveness) operate as a warning system for a period of at least on year
without maintenance.
preliminary analysis
Fire detection can be accomplished by sensing heat, sensing smoke, or light. The
alternative of sensing light is subject to interference from outside sources. The
alternative of sensing heat is cheap but does not take into consideration the toxic effect
of smoke. The alternative of sensing smoke appears to be the most desirable if the cost to
purchase and operate the system can be reduced to the affordable range of a typical
household.
system specification
The planned system must detect fire and warn residence at any location in the house 99%
of the time, even when the residents are sleeping. The system must operate for one year
without failure and be maintainable by the average handyman. The purchase cost and
operating expense of the system must be less that $5.00 per year for an expected system
life of 10 years.
System Engineering Management Plan (SEMP)
The planning schedule for the system will be to develop a product-system design within
six months, a satisfactory prototype within the year and start manufacture by next year.
The sales plan should be established by the time the product design is completed. Trial
installations should be reviewed by 18 months.

The organization requirements for the design team will include safety,
electrical, industrial, manufacturing engineers and lawyers. The team must then be
expanded to include sales and accounting for the prototype testing and evaluation.
ANSWER 3
- Research and purchasing were the lines of Taylor's functional organization responsible
for "new ideas". The next improvement thought of was the suggestion box. Modern
times have changed the thinking a bit so we have team participation and idea development
programs. The true integration of employee creativity with the structured organization
still has a ways to go.
- The yardstick against which needs or ideas are measured is
existing technologies and applications.
- The steps in establishing the operational concept is defining the
system MISSION, the system ENVIRONMENT, system USAGE, and the system DEPLOYMENT. Form
these should evolve system PARAMETERS and measure of EFFECTIVENESS.
- At the conceptual design phase the SYSTEM is specified. Any
reference to a final product would be short circuiting the design process by disregarding
alternative, and possible more effective, system approaches.
- Upper management most often uses cost models to evaluate
proposals.
- A critical aspect of any design process is establishing
organizational authority with a Program Management Plan, technical coordination with a
System Engineering Management Plan, and technical review with a Test and Evaluation
Management Plan.
- The objective of the formal review process is to establish a
formalized record of agreed upon specifications, a design baseline, an integration of
multiple system disciplines, and group participation.
PRELIMINARY DESIGN PHASE
FUNCTIONAL ANALYSIS
A. FUNCTIONAL ANALYSIS SYSTEMS TECHNIQUE - FAST
B. FUNCTIONAL FLOW BLOCK DIAGRAM - FFBD
ALTERNATIVE DEVELOPMENT
A. SCHEMATIC BLOCK DIAGRAM - SBD
B. ALLOCATION OF RESOURCES
OPTIMIZATION AND TRADE-OFFS
A. MODELING
B. VERIFICATION
C. VALIDATION
PRODUCT DEVELOPMENT SPECIFICATION
PRELIMINARY DESIGN REVIEW - PDR
PRELIMINARY DESIGN PHASE
The preliminary design phase converts the system operational specification into a
product development specification. It is a process of going from operational requirements
to functional requirements. This phase is accomplished through an iterative cycling
through FUNCTIONAL ANALYSIS and ALTERNATIVE SELECTION until a PRODUCT SPECIFICATION (B) is
created.
(Note: The function of a man-made system is the purposeful attributes of the systems.
Any function can be divided into subfunctions defining subsystems.)
SYSTEM FUNCTIONAL ANALYSIS - is the process of defining the functions
or the specific or discrete attributes required to achieve the SYSTEM objective. The
analysis is TOP-DOWN with ever increasing definitions of subsystem functions and
sub-subsystem functions. The objectives of the approach is to assure that:
- All aspects (components and relationships) of the system are DEFINED from design to
manufacture to logistics to consumer use.
- That all product sub-systems, manufacturing sub-systems and support sub-systems in the
system are INTEGRATED.
- That all system processes are carried out in the proper SEQUENCE.
FAST Diagramming
The primary tools of functional analysis is the FUNCTIONAL ANALYSIS SYSTEMS TECHNIQUE
(FAST) diagram and the FUNCTIONAL FLOW BLOCK DIAGRAM. The FAST diagram is a tree diagram
that defines all levels of subsystem function from the TOP DOWN until the system
boundaries are reached. As an example, take the function of "replace tire"
(attribute of new tire on car). This forms a hierarchy of subfunctions such as:

open trunk(what) unlock Jack handle(how) install device lift car which eventually
reaches a known function (what) or equipment component (how) at the boundaries of the
system.
Functional Flow Block Diagramming
The FUNCTIONAL FLOW BLOCK DIAGRAM (FFBD) is a more comprehensive technique. Not only
does it contain the concept of functional hierarchy, but it also models sequences and
alternatives to the decision process. The basic elements of the diagram are the function
blocks that model the functions (what) or components (how):
the function sequencing arrows that indicate the sequence in which function can be
achieve;
2.The functional sequence
--------------->
the logic flow that indicates alternative functions or multiple functions that can be
achieved simultaneously given that adequate resources are available;

and the go/no go alternative paths from a function that demand a decision.

All of these diagram elements can be illustrated using the example of a flat tire. The
function "Determining flat tire" requires a go/no go decision after which the
car can be stopped. The next function in sequence is either "call service" or
"repair the flat" which are mutually exclusive.
All of these functions are considered on the first level. A lower level can be
diagrammed for the "Replace tire". The "Replace tire", when analyzed
at a lower level, consists of the replacement sequence of functions (raise, remove,
replace, lower), the "warning signals", and the "clothing change".
Another example of a functional analysis would be the childhood dream of flight on the
magic carpet.
From the functional analysis we know that the subfunctions of flight are elevate,
translate, descend, and carry. The hierarchical detail of the FAST diagram is inadequate
to describe the desired relationships. For our analysis of the magic carpet we want to
elevate, then translate, then descend, while carrying a passenger. This can be represented
in the FUNCTIONAL FLOW BLOCK diagram using the sequence of elevate-->translate---
>descend AND carry.
For the subfunction of translate, the system must be able to either accelerate OR
decelerate AND maintain directional control at all times. The subfunction of directional
control requires three axis control of roll AND pitch AND yaw. Finally at the system
boundary it is decided to maintain yaw control using the "how" of a rudder.
Functional Flow Block Diagram (FFBD)- Flight

One warning is called for at this point. As stated by David DeMarle of Kodak:
"A [functional analysis] diagram by itself is not very useful and may appear
confusing and formidable to those not involved in its construction. The main value of the
diagram lies in the intensive questioning and penetrating analysis required for its
development."
The functional diagrams provide a tool with which the detail design can be specified.
From the diagram will be identified:
- The systems and subsystems that comprise a product-system.
- Methods and equipment necessary for accomplishing the functions of the diagram.
- The resource required for the product system.
- A BASELINE set of functional requirements for future design and development.
ALTERNATIVE DEVELOPMENT - is the translating of system specifications
(B) into development specifications (B) or design CONFIGURATION ITEMS (CI) that satisfy
the system operational requirements. The system level parameters (TPM) can in many cases
be allocated to lower levels or subsystems. These parameters, such as weight or cost, are
often called ALLOCATABLE PARAMETERS. Other parameters are not allocatable, such as speed,
and are called NON-ALLOCATABLE.
The first step is the ALLOCATION OF RESOURCES (requirements) to satisfy the allocatable
parameters using RESOURCE ANALYSIS SHEETS (RAS) by translating the system operational
requirements into specific design requirements for the HIERARCHICAL LEVELS of the
product-system.
Schematic Block Diagrams
The definition of the levels of the product-system is loosely derived from the FAST
diagram. This allows for alternative allocations. Some analysis redefine the FAST levels
into alternative MODULAR units with a SCHEMATIC BLOCK DIAGRAM (SBD). The schematic block
diagram shows grouped functions and interfaces (relationships) within a system. Its goal
is to develop modular units that can be characterized such as:
- Implements a singular, independent function.
- Performs a singular logic task.
- Has a single entry and exit relationship.
- Can be separately tested.
The desirable attributes of the modular units include low COUPLING, high COHESION, and
low CONNECTIVITY where:
- Coupling is a measure of the interdependence between modules.
- Cohesion is the similarity of tasks with a module such as:
- Functional cohesion.
- Sequential cohesion.
- Communication cohesion.
- Procedural cohesion.
- Temporal cohesion.
- Logical cohesion.
- Connectivity is the relationships from internal components within one module to internal
components within another module.
An example of modular approach can be illustrated with the flight example:
Schematic Block Diagram (SBD) - Flight
No matter which approach is taken, functional levels or modular units, the product
specifications are derived by allocating the system parameters derived in the conceptual
phase through the functional levels down to the lowest levels.
Each function or modular at each level of the system has a operational specification
that can be allocated from the level above. As an example using "replace tire",
if the tire must be changed in ten minutes then the combined time to raise the car, remove
the old tire, install new tire, and lower car must be less or equal to ten minutes. Taking
the idea one step further, it is possible to estimate that the trunk lid must be opened
in.1 minutes, the locking mechanism for the jack must be removable in .3 minutes, the
handle of the jack must be installed in the jack in .1 minute, the jack must be installed
on the car in .5 minutes and the jack must lift the car in 2 minutes.
The allocation process is often aided by assigning COMPLEXITY FACTORS (Cf) that are
assigned as a weight to each module or function for allocating the systems parameters.
This demonstrates only one parameter. Many other parameters can be allocated in a like
manner.
- System effectiveness factors such as operational availability Ao, readiness,
reliability R(t), maintainability, supportability.
- System performance and physical parameters such as range, accuracy, speed, capacity,
power.
- System cost factors.
- System support capability factors such as transportation requirements.
The above is also only an estimation process of the allocation of requirements. There
are a number of different allocation schemes that are technically feasible. These
different schemes often form different alternatives for product specifications.
OPTIMIZATION AND TRADEOFFS is the adjustment of the allocations of
resources (requirements) to maximize the system function. On the system level this is
often viewed as benefit to cost. The primary tool for optimization is the MODEL or a
simplified representation of the real system in some form other the original system. The
model includes the following features:
- Should represent the dynamics of the real system.
- Focus on the relevant aspects of the real system.
- Should be simple enough to allow for timely implementation.
- Should be easy to modify.
There are several categories of models such as:
- Physical (iconic) models that look, in some sense, like the real system. These models
include picture representations and scale models.
- Schematic models that graphically describe by chart or diagram. These models include
electrical diagrams or schedule graphics.
- Analog models that share physical properties with the real system.
- These include analog electrical or hydraulic simulations.
- Symbolic (mathematical) models in which the properties and characteristics of the real
system are captured in symbolic and/or mathematical form. These include computer
simulators and mathematical formulations.
The most commonly used model is the symbolic or mathematical model. The advantages of
the model is:
- The model forces the real system to be quantified because of the model's analytical
structure (cause-effect).
- The model is very flexible and adaptable.
- The model model often indicates needed information.
- The model can predict or describe system behavior and effectiveness.
- The model can predict abstract parameters such as risk and uncertainty.
The major task associated with every model is the VERIFICATION that the model
adequately represents the system and VALIDATION that the inferences drawn from the model
are correct and applicable to the real system. If these two conditions are satisfied, then
the model will provide a major tool for the synthesis of the real system.
DEVELOPMENT SPECIFICATION (B) is the synthesis and specification of
design parameters to the functional units or lowest level processes of the system in such
a manner as to guarantee the function of the system. This has been achieved when
sufficient trade-offs and preliminary design have been accomplished to confirm and assure
the completeness of the system performance and design requirements allocated for detail
design.
PRELIMINARY DESIGN REVIEW (PDR) is the organizational and technical
review of the preliminary design required before any further effort can be expended on the
product design. The formal review consists primarily of:
- A formalized record of agreed upon specifications.
- Establishing a design baseline.
- Promoting integration of disciplines.
- Fostering group participation.
QUESTIONS 4
- The conceptual phase of systems engineering is an iterative process consisting of need
definitions, feasibility studies, system specification and program management. What is the
iterative process for preliminary design?
- The FAST diagram is a powerful tool for analyzing the hierarchical functional
requirements of a system, but it falls short of providing all the necessary functional
relationships. What are the added relationships provided by the functional flow diagram?
- The functional analysis continues to the boundaries of a system where either a piece of
equipment or a process is defined. How is this structure used to develop alternative
development specifications given that the conceptual design defined system parameters.
- Engineering at the preliminary design level is interested in "modeling"
alternative product specifications at minimum cost. What are four types of models for
doing this and what method is the most commonly used?
- Equipment is often named in such a manner as to reflect the functional diagram. An
example of this would be a carburetor which is part of the power plant which is part of
the drive train which is part of the vehicle. What equipment in your operations is named
to follow the FAST diagram nomenclature?
- Creating a development specification from the best alternative is the goal of the
preliminary design phase. What must be guaranteed in the development specifications
relative to the system specification?
- At the formal review the program management plan is open for revision. What information
is now available that makes the original plans somewhat obsolete?
CASE STUDY 4 - Replace Tire Allocation Model
An example of "replace tire" using a
mathematical model is the linear goal programming model. Say that the time estimate of
"replace tire" is only a target value of 10 minutes. Let the next level down
have the target times, costs per unit and minimum times of:
| Function |
TIME |
$/minute to
reduce |
change time
increase |
| target |
min |
| Raise car |
3 |
1 |
$12 |
-$10 |
| Remove tire |
2 |
.5 |
20 |
-5 |
| Install tire |
2 |
.5 |
20 |
-5 |
| Lower car |
3 |
.5 |
5 |
-5 |
The problem is to refine the allocation of 10 minutes
to the next level so as to reduce cost and still perform the same system function.
For the model, define the following symbols:
X1 = reduction in raising time
X2 = increase in raising time
X3 = reduction in removal time
X4 = increase in removal time
X5 = reduction in install time
X6 = increase in install time
X7 = reduction in lower time
X8 = increase lower time
then the marginal cost (negative is reduced cost) of
the reallocated time is modeled as:
Minimize
12X1-10X2+20X3-5X4+20X5-5X6+5X7-5X8
subject to:
3-(X1-X2) >= 1 raise car
time limit
2-(X3-X4) >= .5 remove tire time limit
2-(X5-X6) >= .5 install tire time limit
3-(X7-X8) >= .5 lower car time limit
(3-X1+X2)+(2-X3 |