L E C T U R E 8 SE typical process SE applications Today‘s

Systems engineering

Zuzana Bělinová Faculty of Transportation Sciences, CTU in Prague

Lecture 8

L E C T U R E

8 L E C T U R E

SE typical process

SE applications

– Today‘s

management methods

Systems engineering


Lecture 8

LECTURE 8 - OVERVIEW

Systems engineering

Typical systems engineering proces according INCOSE

Examples of today‘s management methods

Systems engineering


Lecture 8

LECTURE 11 - OVERVIEW

Systems engineering

• Many attitudes, many methodologies

• Similar principles

Systems engineering


Lecture 8

SYSTEMS ENGINEERING –

BASIC FACTS

Systems Engineering is responsible for creating a product

and also a process for producing it

Many processes have been proposed to map the basic

recommendations

Some are bigger, some are smaller

The SIMILAR process (consensus of the INCOSE - International

Council on Systems Engineering) consolidates the most important

- most processes are similar to it

Systems engineering


Lecture 8

BASIC SYSTEMS

ENGINEERING PROCESS

The Systems Engineering Process is not sequential: it is parallel and

iterative!

Source: INCOSE

Customer

Needs

State the

Problem

Launch the

System

Investigate

Alternative

s

Model the

System Integrate

Assess

Performance

The SIMILAR Process

Output

Re-

evaluate

Re-

evaluate

Re-

evaluate

Re-

evaluate

Re-

evaluate

Re-

evaluate

Systems engineering


Lecture 8

BASIC SYSTEMS

ENGINEERING PROCESS

Description of phases of SIMILAR process

Systems engineering


Lecture 8

INPUT – CUSTOMER NEEDS

Very important

Demanding:

Necessary to find out all involved customers

To collect all the needs and requirements

(necessary to find mutual language with the customer)

Systems engineering


Lecture 8

STATE THE PROBLEM

description of the top-level functions, e.g. using:

• mission statement,

• concept of operations

• description of the deficiency that must be ameliorated.

Most mandatory and preference requirements should be traceable to this problem statement.

Acceptable systems must satisfy all the mandatory requirements.

what must be done, not how to do it.

in functional or behavioral terms

Inputs come from end users, operators, maintainers, suppliers, acquirers, owners, regulatory agencies, victims, sponsors, manufacturers and other stakeholders.

Systems engineering


Lecture 8

INVESTIGATE ALTERNATIVES

Alternative designs created and evaluated - based on

• performance,

• schedule,

• cost

• risk

multicriteria decision-aiding techniques used

Analysis redone whenever more data are available

Models constructed and evaluated, simulation data should be derived, prototypes built and measured

Alternatives judged for compliance of capability against requirements

alternative designs reduce project risk

helps clarify the problem statement

Systems engineering


Lecture 8

MODEL THE SYSTEM I.

Models will be developed for most alternative designs.

The model for the preferred alternative will be expanded and used to help manage the system throughout its entire life cycle.

types of system models

• physical analogs,

• analytic equations,

• state machines,

• block diagrams,

• functional flow diagrams,

• object-oriented models,

• computer simulations

• mental models

Models constructed for both the product and the process.

Systems engineering


Lecture 8

MODEL THE SYSTEM II.

Models constructed for both the product and the process.

Process models allow

• to study scheduling changes,

• create dynamic PERT (program evaluation and review technique)

charts

• perform sensitivity analyses to show the effects of delaying or

accelerating certain subprojects.

Running the process models reveals bottlenecks and fragmented

activities, reduces cost and exposes duplication of effort

It is not sequential: it is parallel and iterative! - models must be created

before alternatives can be investigated

Systems engineering


Lecture 8

INTEGRATE

Means bringing things together so they work as a whole

Interfaces between subsystems designed

Subsystems defined along natural boundaries

Subsystems should be defined to minimize the amount of

information to be exchanged between the subsystems

Feedback loops around individual subsystems are easier to

manage than feedback loops around interconnected subsystems

Result: system that is built and operated using efficient

processes

Remember

Topological

decomposition

Systems engineering


Lecture 8

LAUNCH THE SYSTEM

Launching the system means allowing the system do what it was intended to do

Might mean buying hardware or software, or might mean actually making things

preferred alternative is designed in detail; the parts are built or bought (COTS – commercial off-the-shelf), the parts are integrated and tested at various levels leading to the certified product.

In parallel, the processes necessary for this are developed and applied

Consideration is given to its interfaces with operators (humans, who will need to be trained) and other systems with which the product will interface

Result: running the system and producing outputs

Systems engineering


Lecture 8

ASSESS PERFORMANCE

Figures of merit, technical performance measures and metrics are

all used to assess performance.

Figures of merit are used to quantify requirements

Technical performance measures are used to mitigate risk during

design and manufacturing.

Metrics (including customer satisfaction comments, productivity,

number of problem reports, ...) are used to help manage a

company's processes.

Measurement is the key

• If you cannot measure it, you cannot control it.

• If you cannot control it, you cannot improve it.

Systems engineering


Lecture 8

RE-EVALUATE

Re-evaluate is arguably the most important of these functions.

Using feedback to help control systems and improve

performance

Continual process with many parallel loops

Means observing outputs and using this information to modify the

system, the inputs, the product or the process.

Systems engineering


Lecture 8

VARIATIONS

Ideally Systems Engineering process at any company should be

• documented

• measurable

• stable

• of low variability

• used the same way by all

• adaptive

• tailorable

- May be a contradiction!

Systems engineering


Lecture 8

GENERAL RECOMMENDATIONS

by Briar Mar

Understand the whole problem before you try to solve it

Translate the problem into measurable requirements

Examine all feasible alternatives before selecting a solution

Make sure you consider the total system life cycle. The birth to

death concept extends to maintenance, replacement and

decommission. If these are not considered in the other tasks,

major life cycle costs can be ignored.

Make sure to test the total system before delivering it.

Document everything.

Systems engineering


Lecture 8

MANAGEMENT METHODS

Systems engineering


Lecture 8

MANAGEMENT METHODS

Examples of today‘s management methods

- Quality management

- Process management

- Product management

- Risk management

- ..... and many others

Systems engineering


Lecture 8

QUALITY MANAGEMENT –

methods - examples

• APQP (Advanced Product Quality Planning)

• CAF (Common Assessment Framework)

• Deming cycle (PDCA)

• DMAIC

• EFQM Excellence Model

• Kaizen

• Quality circle

• Lean

• Poka-yoke

• Six Sigma

• TQM – Total Quality Management

• 5S method

https://managementmania.com/cs/rizeni-kvality

Systems engineering


Lecture 8

APQP (ADVANCED PRODUCT

QUALITY PLANNING)

• Goal: to devolop products

• Used in industrial and manufacturing (e.g. automotive industry – Ford, GM, ….)

• Set of techniques and procedures

• Similar to six sigma concept, derived from ISO 9000

• Process for quality deployment:

• Planning

• Product design and development

• Process design and development

• Product and process validation

• Production

https://managementmania.com/en/apqp-advanced-product-quality-planning

Systems engineering


Lecture 8

CAF (COMMON ASSESSMENT

FRAMEWORK)

• Developped by European Foundation for Quality Management

• Designed for usage in the public sector in all administration

levels

• Helps with

• Self-assessment

• Improvement plan

• Implementation of improvement

actions

• Looks at organisation

from different viewpoints,

emphasizes holistic approach

http://www.aqs.gr/?cat_id=564&lang=en

Systems engineering


Lecture 8

CAF (COMMON ASSESSMENT

FRAMEWORK)

• Based on 8 principles of excellence

• Results orientation

• Citizen/Customer focus

• Leadership & constancy of purpose

• Management of processes & facts

• Involvement of people

• Continuous improvement & innovation

• Mutually beneficial partnerships

• Corporate social responsibility

•Based on 9 criteria

• Enabler ones: Leadership, Strategy & Planning, People, Partnerships & Resources and Processes

• Result-ones: Citizen/Customer Oriented Results, People Results, Society Results and Key Performance Results

http://www.aqs.gr/?cat_id=564&lang=en

Systems engineering


Lecture 8

PDCA – DEMING CYCLE

• Method for gradual improvement of services, processes,

products, etc.

P - Plan - planning proposed improvement

D - Do . plan implementation

C - Check - check the result from the original plan

A - Act - plan adjustments and the actual implementation based

on the verification, and space implementation of the

improvements in practice

https://managementmania.com/en/deming-cycle-pdca

Systems engineering


Lecture 8

DMAIC

• Improvement method, part of Six sigma,

D (Define) - objectives are defined, it is described subject and

improvement objectives (product, service, process, data, etc.)

M (Measure) - measurement of initial conditions in term of the

principle “what I don’t measure, that I don’t control”

A (Analyze) - analysis of the facts, causes of deficiencies

I (Improve) - key phase of the whole cycle, in which the

improvement is based on analyzed and measured facts

C (Control) - improved deficiency should be introduced - to

manage and maintain the improvements in life

https://managementmania.com/en/dmaic-improvement-cycle

https://managementmania.com/en/objective

https://managementmania.com/en/product

https://managementmania.com/en/service

https://managementmania.com/en/process

https://managementmania.com/en/data

https://managementmania.com/en/analyses-analytical-techniques

Systems engineering


Lecture 8

EFQM EXCELLENCE MODEL

• For implementation of quality management methods in

organizations

• Practical tool for self-evaluation

• Guidelines for improving

• Framework for the management system of the organization

• Way of the terminology unification

https://managementmania.com/en/efqm-excellence-model

Systems engineering


Lecture 8

KAIZEN

• Name means „improvement“ in Japan

• Method prefers small improvements instead of large ones –

origin during WW2

• Involves all employees

• Two approaches

• Focus on materials and information flow

• Focus on process – improvement for all employees

https://en.wikipedia.org/wiki/Kaizen

Systems engineering


Lecture 8

QUALITY CIRCLE

• Define and solve quality of performance

• Comes from Japan (culture of lifetime employment, high loyalty)

• decentralized, enterprise-oriented system

• Principles:

• Small teams of volunteers

• Each participant should be representative of a different

functional activity

• Problems chosen by the circle

• Requires management support

• Particpants must recieve problem solving training

http://www.businessdictionary.com/definition/quality-circle-QC.html

Systems engineering


Lecture 8

LEAN

• continuously improvement in all areas

• avoid unnecessary wastage

• Combined with other methods

• focusing on the value stream and increasing this value

• Focuses on speed, simplicity, clarity

• Creating products and services without unnecessary activities

and inventories

• Waste reduction

https://managementmania.com/en/lean

Systems engineering


Lecture 8

POKA-YOKE

• helps to prevent unnecessary errors

• mechanism or device which helps the workers to avoid

mistakes

• using prevention, correction and warnings on the human

mistakes

https://managementmania.com/en/poka-yoke

Systems engineering


Lecture 8

TQM – TOTAL QUALITY

MANAGEMENT

• management system for a customer-focused organization that involves all employees in continual improvement. It uses strategy, data, and effective communications to integrate the quality discipline into the culture and activities of the organization

• Main principles

• Customer-focused

• Total employee involvement

• Process-centered

• Integrated system

• Strategic and systematic approach

• Continual improvement

• Fact-based decision making

• Communications

http://asq.org/learn-about-quality/total-quality-management/overview/overview.html

Systems engineering


Lecture 8

5S METHOD

• to improve the working environment in the organization and the

quality

• Comes from Japan

• Seiri (Separate) - separate needed and unneeded things

• Seiton (Sort) - sort or locate needed and used things that

they can be easily and quickly applied

• Seiso (Still clean) - maintaining cleanliness in the workplace

and its srroundings

• Seiketsu (Standardize) - continuous and repeated

improvement of the organizational work

• Shitsuke (Self-discipline) - maintaining perfect order and 4

previous S in the workplace at the time

https://managementmania.com/en/5s-method

Systems engineering


Lecture 8


analytical tools - examples

• DOE (Design of Experiments)

• Ishikawa diagram

• Kano model

• Paretovo charts

• FMEA (Failure Mode and Effect

Analysis)

• FTA (Fault Tree Analysis) -

• QFD (Quality Function

Deployment)

• Global Eight Disciplines

• Measurement System Analysis

• Production Part Approval Process

• Statistical process Control

• Flowchart

• Histogram

• Run chart

• Control chart

• Scatter diagram

• Regression Analysis

• WIBI (Would I Buy It?)


Systems engineering


Lecture 8

DOE (DESIGN OF

EXPERIMENTS)

• Aims to explain variations under different conditions

• Testing different combinations of factors (input) influencing the output

• Predicting outcome

• Establishment of validity, reliability, and replicability

• Benefits

• Better product design and development

• Improvement of quality

• Lowering costs

• Reduction of non-conforming products

• Solving quality problems

• Etc.

https://en.wikipedia.org/wiki/Design_of_experiments

Systems engineering


Lecture 8

ISHIKAWA DIAGRAM

• Cause and effect diagram

• Technique for display and analysis of cause and effects

• Known as fishbone diagram

• Causality principle

• Typical causes:

• Man power - People - causes caused by people

• Methods - causes caused by rules, regulation, legislation or standards

• Machines - causes caused by equipment such as machinery, computers, tolls

• Materials - causes caused by defect or material properties

• Measurements - causes caused by improper or poorly chosen measurement

• Mother nature - Environment - causes caused by the environment - temperature, humidity or the culture

• Management - causes caused by improper management

• Maintenance - causes caused by improper maintenance

https://managementmania.com/en/ishikawa-diagram

http://asq.org/learn-about-quality/cause-analysis-tools/overview/fishbone.html

Systems engineering


Lecture 8

KANO MODEL

• Not all improvements leads to higher customers safisfaction

• 3 groups of service parameters

• Passive (expected)

• Customer

• Active (somethig extra)

https://managementmania.com/en/kano-model

Systems engineering


Lecture 8


standards - examples

• ISO 9001 Quality management systems

• ISO/TS 10004:2010 - Quality management -- Customer satisfaction -- Guidelines for monitoring and measuring

• ISO 13485 - Medical devices -- Quality management systems -- Requirements for regulatory purposes

• ISO/TS 16949 - Quality management systems -- Particular requirements for the application of ISO 9001:2008 for automotive production and relevant service part organizations

• QS 9000

• MSA (Measurement System Analysis)

• VDA (VDA 1, VDA 2, VDA 3, VDA 4, VDA 5, VDA 6, VDA 7) - German quality management system standard - extension of ISO 9001 for automotive industry requested of automotive


Systems engineering


Lecture 8

PROCESS MANAGEMENT –

methods - examples

• BCM (Business Continuity Management)

• BPM (Business Process Management)

• ITIL (ICT process management)

• Six Sigma

• Deming cycle (PDCA cycle)

• DMAIC – improement cycle

• Statistical methods

• ISO 9001

• Total Quality Management (TQM)

Source: https://managementmania.com/en/process-management

Systems engineering


Lecture 8

PRODUCTION MANAGEMENT –

methods - examples

• ABC-D

• BOA (Belastungorientiere Auftragsfreigabe)

• CIM (Computer Integrated Management)

• CRP (Capacity Resource Planning)

• DBR

• JIT (Just-in-Time)

• MRP (Manufacturing Resource Planning)

• ERP (Enterprise Resource Planning)

• KANBAN (management system of production logistics (material flow in production) using simple cards for material flow management)

• Lean Production

https://managementmania.com/en/production-management

Systems engineering


Lecture 8

RISK MANAGEMENT –

Frameworks - examples

• RMF (Risk Management Framework)

•

• M_o_R ® (Management of Risk)

• RiskIT (Risk IT Framework)

https://managementmania.com/en/risk-management

Systems engineering


Lecture 8

RMF (RISK MANAGEMENT

FRAMEWORK)

• information security framework for the US federal government

• Main activities

• Categorize

• Select

• Implement

• Assess

• Authorize

• Monitor

http://csrc.nist.gov/groups/SMA/fisma/framework.html

Systems engineering


Lecture 8

M_O_R ®

• Framework for the management of risk across all parts of an

organisation

• Strategic

• Programme

• Project

• Operational

• to identify and control the exposure to any type of risk, positive

or negative, which may have an impact on the achievement of

your organisation's business objectives


Systems engineering


Lecture 8

M_O_R ®

• Principles

• Approach - how to adopt

• Processes

• Inputs

• Outputs

• Activities

• Evaluation and control


Systems engineering


Lecture 8

RISKIT (RISK IT FRAMEWORK)

• To identify and manage IT risks

https://managementmania.com/en/riskit-risk-it-framework

www.isaca.org

Systems engineering


Lecture 8

RISK MANAGEMENT

– methods - examples

• BASEL I, BASEL II, BASEL III - capital adequacy rules for banks’ operational risk

• CCA (Cause-Consequence Analysis) - FTA and ETA Combination

• CLA (Checklist analysis)

• Cognitive modeling structures in the identification and risk assessment

• CorIA (Core Impact Assessment)

• CPQRA (Chemical Process Quantitative Risk Analysis

• CRAMM (CCTA Risk Analysis and Management Method)

• CRI (Continuous Risk Improvement)

• ETA (Event Tree Analysis)

• EWRM (Enterprise-Wide Risk Management)

• FMEA (Failure Modes and Effects Analysis)

• FMECA (Failure Mode, Effects and Critically Analysis)

• Forecasting

• FTA (Fault Tree Analysis)

• HAZID (Hazard Identification Study

• HAZOP (Hazard and Operability Study)

• HRA (Human Reliability Analysis)

• PHA (Preliminary Hazard Analysis)

• PPAP (Production Part Approval Process)

• Probabilistic Methods

• RIPRAN (RIsk PRoject ANalysis)

• RR (Relative ranking)

• SA (Safety Audit)

• SR (Safety Review)

• VaR (Value at Risk)

• W-I (What-if Analysis)

• Winterling Crisis Matrix


Systems engineering


Lecture 8

RISK MANAGEMENT

– analytical technigues - examples

• Five Forces Analysis (Five Forces Model)

• Brainstorming

• Brainwriting

• Forecasting

• Pareto Principle

• PESTLE Analysis

• Scenario technique

• SMART – objectives suggestion

• SWOT Analysis

• VRIO Analysis

• Winterling Crisis Matrix


Systems engineering


Lecture 8

RISK MANAGEMENT

– standards - examples

• ISO 14971 (Medical devices) - Global Harmonization Task Force (GHTF)

• ISO 16085:2006 - Systems and software engineering - Life cycle processes - Risk management

• ISO 31000 Risk management – Principles and guidelines

• IEC/ISO 31010 Risk management – Risk assessment techniques

• ISO Guide 73:2009 Risk management – Vocabulary

• ISO/IEC TR 13335-1:1999

• ISO/EIC Guide 73:2002

• OHSAS 18001 Occupational Health and Safety Assessment Series

• AS/NZS 4360:2004 - Risk Management

• SOX (Sarbanes-Oxley Act)


Systems engineering


Lecture 8

FURTHER USAGE OF SYSTEMS

ENGINEERING PRINCIPLES

• Human Resources Management

• Economy & Finance Management

• Informatics & IT Management

• Facility Management

• Organizational Management

• Crisis Management

• Innovation Management

Systems engineering


Lecture 8

FURTHER USAGE OF SYSTEMS

ENGINEERING PRINCIPLES

• Service Management

• Project Management (e.g. PRINCE2 methodology, PMBOK

(Project Management Body of Knowledge), Agile Project

Management™ (AgilePM®), Managing Successful Programmes

(MSP®)

• Change Management

• Knowledge Management

• Strategic Management

• Security Management

Systems engineering


Lecture 8

EXAMPLES OF MORE

METHODOLOGIES

Management of Value (MoV®) - value management

across many sectors

Management of Portfolios (MoP) how to apply

principles, practices and techniques which help to

optimise an organisation investment in change

Systems engineering


Lecture 8

Thank you for your attention

Systems engineering


Lecture 8

REFERENCES

retrieval date December 2014

•ILX Training Programmes https://www.ilxgroup.com/uk/training/m-o-r

• Management mania. Retrieved from:


• https://managementmania.com/en/quality-management

• https://managementmania.com/en/process-management

• https://managementmania.com/en/risk-management

• https://managementmania.com/en/production-management

•International Organization for Standarčdization web pages.

http://www.iso.org/iso/catalogue_detail?csnumber=38063

http://www.iso.org/iso/home/search.htm?qt=16949&published=on&active_

tab=standards&sort_by=rel

http://www.iso.org/iso/home/search.htm?qt=13485&published=on&active_

tab=standards&sort_by=rel

L E C T U R E 8 SE typical process SE applications Today‘s

Documents

Transcript of L E C T U R E 8 SE typical process SE applications Today‘s