ESoS 1 Loughborough University, 2012MEGS III Lecture: Henshaw Professor Michael Henshaw Loughborough University, UK Managing the systems lifecycle: systems

ESoS

1 Loughborough University, 2012 MEGS III Lecture: Henshaw

Professor Michael Henshaw

Loughborough University, UK

Managing the systems lifecycle: systems engineering competencies and

approaches

ESoS


Content

Competency in Systems Engineering System lifecycles Standards

ISO15288 the systems engineering lifecycle standard

ESoS


Systems Thinking for Energy

CO2

Bio Fuels for cars

Increase Bio Fuel Production

De -forestation

Processing

Food shortages

NegativeBehavioural

Change

Example from Geoff Robinson, of Atkins, Keynote at ieee SoSE

2010

Systems Thinking: Understand complex problemsExplore wider set of options

ESoS


INCOSE Competency Framework

Systems ThinkingSystems conceptsSuper system capability issuesEnterprise and technology environment

Holistic Lifecycle ViewDetermine and manage stakeholder requirementsSystems designArchitectural designConcept generationDesign for...Functional analysis

Interface management

Maintain design integrityModelling and simulationSelect preferred solutionSystem robustnessSystems integration and verificationValidationTransition to operation

Systems Engineering ManagementConcurrent engineeringEnterprise integrationIntegration of specialismsLifecycle process definitionPlanning, monitoring and controlling

ESoS


Typical stages of lifecycle management

Initiation

Closing

Planning & Design

ExecutionMonitoring &

Control

ESoS


Holistic lifecycle view

Whole life costs Maintaining performance, safety, security, etc. Retaining knowledge of the system Upgrades Risks over time Disposal

Image: Hunt Emerson

ESoS


A System

Definition of a system A system is a construct or collection of different

elements that together produce results not obtainable by the elements alone.

The elements, or parts, can include people, hardware, software, facilities, policies, and documents; that is, all things required to produce systems-level results. ......... (Rechtin, 2000). INCOSE definition (first part)

Image: AP

ESoS


Systems Engineering and the Systems Life Cycle Standard

2. System Life cycles

1. Standards

3. System of interest

4. ISO15288-scope-structure-use

5. Tailoring

6. Case studies

1. Systems Eng. and systems thinking

7. Limitations

Required by

Mindset and approach

for

Defines

Constrains

Applies std.

Is an appropriate

illustrates

Requires

Enables mgt of

ESoS


Standards - why they are important

The need for standards and Systems Engineering

ESoS


Standards: Benefits and Applicability

Benefits Safety Interoperability Quality Upgradeability

Applicability Business Trade Technical Engineering Finance Etc.

ESoS


Application to project phases

Design Operation

Manufacture

Construction

ISO ISO

IECASME

SAE DIN BSI

ASTM

ITU

ASMEAPI

ISO - International Standards Organization

IEC - International Electrotechnical Commission

ASME - American Society of Mechanical Engineers

SAE - Society of Automotive Engineers

DIN - Deutsches Institut für Normung eV

BSI - British Standards Institution

ASTM – American Society for the Testing of Materials

ITU – International Telecommunications Union

API – Application Programming Interface

From ‘Why Standards are Important’, IHS Whitepaper, www.ihs.com

ESoS


Compliance

Regulation A regulation is a legal requirement and compliance is,

therefore, compulsory. A regulation is usually developed by Government and specifies what must be done, but without specifying how it must be done.

Code A code is a standard (developed by an appropriate body) and

adopted by a Government entity. Compliance is compulsory. Standard

A specification of best practice developed by experts and based on consensus. It is recognised by an appropriate standards development organisation. Compliance is voluntary.

Based on ‘Why Standards are Important’, IHS Whitepaper, www.ihs.com

ESoS


Part 4 – ISO 15288

Origin of ISO 15288 Application and characteristics of the standard Basic content of the standard

ESoS


Origin of ISO 15288

1960

1970

1980

1990

2000

2010

Increasing complexity

Space systems

Complex manufacture

Software

Military and civilian std. in US

Std. In EU

ISO 15288 (2002)

ISO 15288 (2008)

Software std.

Systems context Emerging Standards

ESoS


Characteristics of 15288 (1)

Product/service Although described as applicable to service

systems, the language and approach is strongly product based

Description Standard is a comprehensive list of processes for

life cycle management, but none is specified in detail

Cannot be used without tailoring High-tech. Organisations recognise the standard,

but don’t usually seek rigid compliance

ESoS


Characteristics of 15288 (2)

Uses As an outline framework from which organisation

engineering and project management processes may be derived

As a checking procedure for extant processes Level of compliance can indicate areas for process

improvement Compliance is seen as meritorious, but not essential

ESoS


Significant INCOSE Publications based on 15288

INCOSE Handbook INCOSE 2010 systems engineering handbook,

version 3.2. San Diego, CA, USA: International Council on Systems Engineering (INCOSE), INCOSE-TP-2003-002-03.2

INCOSE UK Systems Engineering Competency Framework INCOSE UK 2010

ESoS


Application

Organisation

ProjectEnterprise

Enduring

Long term

Short term

Single project

General across all projects

Enterprise

Tailoring General/high level – slowly changingProcedures : Processes

Processes Specific/detailed – as & when required

Consistency

ESoS


Generic Lifecycle

A system progresses through specific stages during its life In reality stages overlap

Enabling systems are required at each stage All stages should be considered at design time

and lifecycle features incorporated

Concept stage

Development stage

Production stage

Retirement stage

Utilisation stage

Support stage

ESoS


ISO 15288 Content

Agreement Processes

Acquisition

Supply

Organizational Project-Enabling Processes

Life Cycle Model Mgt

Infrastructure Mgt

Project Portfolio Mgt

Human Resource Mgt

Quality Mgt

Project Processes

Project Planning

Project Assessment & Control

Decision Mgt

Risk Mgt

Configuration Mgt

Information Mgt

Measurement

Technical Processes

Stakeholder Req. Definition

Req. Analysis

Architecture Design

Implementation

Integration

Verification

Transition

Validation

Operation

Maintenance

DisposalSystem Life Cycle Processes

Based on ISO/IEC, 2008 figure 4

ESoS


Agreement Processes

Provides symmetric processes for supplier and customer Supply process Acquisition process

Largely concerned with commercial matters Not necessarily executed by engineers Covers selection of or as supplier, acceptance

criteria of product/service, financial arrangements

ESoS


Organizational Project-Enabling Processes

Processes put underlying plan and resources in place Selection/creation of appropriate life cycle model provides

underlying assumption for whole project E.g. CADMID underpins all UK defence acquisitions

Creation and maintenance of appropriate infrastructure for project

Note that different organizations have different definitions of infrastructure (buildings, communication channels, computer networks, ...)

Business decisions about portfolio of projects (sub-projects) Skills and human resources planned Quality procedures for project

Note that these will often be defined at the organization level, rather than at the individual project level

ESoS


Project Processes

Mostly concerned with project management Considerable overlap between systems

engineering and project management Need to be consistent with standard project managment

processes of the organization

Standard distinguishes between Project management and project support Management: planning and assessment/control Support: decision, risk, information, measurement, and

configuration control

ESoS


Technical Processes

Focused on classic Systems Engineering aspects Vee-model Stakeholder analysis and Requirements Design (architecture) Implementation and Integration Verification, Transition, and Validation Operation, Maintenance Disposal

ESoS


(Typical) Vee-Model

Concept of Operation

Requirements

Architecture

Detailed Design

Implementation

Integration

Test, and verification

Systems Verification

Validation

Operation & maintenanceVerification

and Validation

Project Definition

Project test & integration

Time

ESoS


(Typical) Vee-Model + 15288 Technical Processes

Concept of Operation

Requirements

Architecture

Detailed Design

Implementation

Integration

Test, and verification

Systems Verification

Validation

Operation & maintenanceVerification

and Validation

Project Definition

Project test & integration

Time

Stakeholder Req. Definition

Requirements analysis

Architecture Design

Implementation

Integration

Verification

Transition

Validation

Operation Maintenance

Disposal

ESoS


Use

To some extent, ISO 15288 represents the collation of good practice Organisations that develop complex systems may

have procedures and processes that follow 15288 implicitly

Compliance may be advised but rarely (never?) compulsory

ESoS


Limitations: SoS Properties - Emergence

Emergence is a phenomenon ascribable to the whole system and not to any of its individual parts.

Some maintain it is only applied to something that has not been predicted, others that it may be either planned or unexpected

Traditional systems engineering; well understood subsystems etc.; V&V

Components

Subsystems

Systems

Desirable properties are designed to emerge

Desirable/ predicted

Desirable/ unpredicted

Undesirable/ unpredicted

Systems of systems engineering; incomplete knowledge of interactions, complexity, strong emergence

ESoS


Managing and Engineering

Members of the SoS owners’ club have partial knowledge and influence Need to engineer for compliance (interoperability)

Standards Manage own system (part) through control Manage other parts of SoS through influence, protective

measures, collaboration, … (not at all) If systems thinking tells us that we should make our

systems behave in certain ways to maximise benefit, why don’t we do it? From the single-system community’s perspective, its part of

the SoS capability represents additional obligations, constraints and complexities. Rarely is participation in an (sic) SoS seen as a net gain from the viewpoint of single-system stakeholders.

George Rebovich, Jr., 2009

ESoS


Table 1. SE versus SoSE

Traditional SE versus SoSE

From Neaga Henshaw and Yue, 2009

SoS

ESoS


Limitations of the Standard

What worked in the past will not always work in the future.

ESoS


Systems Engineering

New publication available: Guide to the Systems Engineering Body of

Knowledge (SEBoK) at http://www.sebokwiki.org

https://email.lboro.ac.uk/owa/redir.aspx?C=q7FyDQPKA0i6Kdj-y94DT8dBMJ3LaM8IYqW0ZUdN6V2vvKiyQeWxoNIGmi3wjPBRvdn2MQxlGco.&URL=http://www.sebokwiki.org/

ESoS


Back-up slides

ESoS

34 Loughborough University ISO 15288 Lectures: Henshaw

Example of use

Large defence related organisation has recently carried out a skills audit using the INCOSE Competency Framework

This provides health check for systems engineering skills and marketing information for use with clients

Documents

ESoS 1 Loughborough University, 2012MEGS III Lecture: Henshaw Professor Michael Henshaw Loughborough University, UK Managing the systems lifecycle: systems