theory and practice of systems engineering in … · theory and practice of systems engineering in...

Theory and Practice of Systems Engineering in KongsbergProjects

by Gerrit Muller University of Southeast Norway-NISEe-mail: [email protected]

www.gaudisite.nl

Abstract

The Systems Engineering Body of Knowledge provides many means to createproducts and to run project creating systems. We discuss the theory and reflecton experiences from practice, focusing on Kongsberg industry.

Distribution

This article or presentation is written as part of the Gaudí project. The Gaudí projectphilosophy is to improve by obtaining frequent feedback. Frequent feedback is pursued by anopen creation process. This document is published as intermediate or nearly mature versionto get feedback. Further distribution is allowed as long as the document remains completeand unchanged.

June 5, 2018status: preliminarydraftversion: 0.1

SE theory in a nutshell

some examples from Kongsberg

SE revisited

CAFCR+

more examples from Kongsberg

size considerations

one more example from

Kongsberg SE conclusions in a nutshell

questions from Kongsberg?

start

finish

Figure Of ContentsTM



SE revisited

CAFCR+


size considerations




start

finish

Theory and Practice of Systems Engineering in Kongsberg Projects2 Gerrit Muller

version: 0.1June 5, 2018

TPSEPlogo

Summary SE theory

Systems Engineering theory

Follow phase model

needs > requirements > concepts > detailed design

SMART Requirements

Evaluate multiple concepts

Think "Functional'', What versus How

typical buzzwords

stakeholders, concerns, life cycle,

risks, reviews, V-model



TPSEPtheorySE

Phase Model for Development

0.

feasibility

1.

definition

2.

system

design

3.

engineering

4.

integration

& test

5.

field

monitoring

tender execution deployment

reviews

requirement

specification

working

system



TPSEPphases

V-Model

needs

specification

system design

subsystem design

component design

component realization

component test

subsystem test

system test

verification

validation



TPSEPvModel

The SMART acronym

• Specific

• Measurable

• Assignable (Achievable, Attainable,

Action oriented, Acceptable, Agreed-upon, Accountable)

• Realistic (Relevant, Result-Oriented)

• Time-related (Timely, Time-bound, Tangible, Traceable)

quantified

verifiableacronym consensus

variation of meaning



FFTSsmartList

Concept Selection “Pugh” Matrix

fuel cell battery generator

peak power

efficiency

weight

pollution

infra structure

needs

5 4

4

44

4

41

1

2

2

3

333

18 1712



TPSEPconceptSelection

“Functional” Thinking; What and How

How

What

sense

position

sense

orientation

sense

speed

determine

setpoints

control

engine

control

rudders

determince

trajectory

GPS

gyros ARM CPU

DL2128V

CAN master256MB

DDR III

256MB

NAND Flash

8 12 bit DA

CAN



TPSEPwhatAndHow

Examples from Kongsberg



SE revisited

CAFCR+


size considerations




start

finish



TPSEPlogoExample1

Typical Tendering with Navy

tender project execution installation,

operation, and maintenance

requirements from customer

bid spec

order

want

must yes yes yes

yes no yes no no

yes yes' no no no yes" no no

by definition! spec changes real discussion after order new insights

customer understanding required

updated spec



KDAWSbidSpec

Rigor may Back Fire

needs

specification

design test

verify

validate

realization

fine-grain prioritization

formal precise

concise

very good

OK

perfect

confused customers

missing feedback

Change proposal caused that multiple

alarms could be visible at console for single

signal

Change was introduced in the field.

Field change was required later to repair.



KMWSvModelAnnotated

Latency of Introduction, Detection and Repair

change

request

fine-grain

prioritization

release change

request

to repair

fine-grain

prioritization

release

repair

how much customer credit has been lost?

time



TPSEPalarmTimeLine

SE revisited; CAFCR+ model



SE revisited

CAFCR+


size considerations




start

finish



TPSEPlogoCAFCR

CAFCR+ model

Customer

What

Customer

How

Product

What

Product

How

What does Customer need

in Product and Why?

drives, justifies, needs

enables, supports

Customer

objectives

Application Functional Conceptual Realization

Life cycle



CAFCRplusAnnotated

SE activities in CAFCR

Customer

objectives


multi-disciplinary engineering

subsystems and components

functionsapplicationsvalue drivers

qualities



TPSEPannotatedCAFCR

SE revisited

Customer

objectives


multi-disciplinary engineering

subsystems and components

functionsapplicationsvalue drivers

qualities

understand

customer and

business (value)

help to transform

into specification

multi-displinary design

ensuring functionality

and qualities



TPSEPdefinitionSE

Continuous Iteration

Customer

objectives


ask needs get solution as answer

build

proto

validateverify

spec

integrate

reconstruct

needs explore solutions

explore

use casesdraft

specdraft

design

why why why

use protodesign build

and iterate and evolve further....



UAVViterativeCAFCR

More Examples from Kongsberg



SE revisited

CAFCR+


size considerations




start

finish



TPSEPlogoExample2

Example: K-Master

thruster levers

alarm and

utility panel

independent DP joystick

touch panel

seat adjustments

thruster levers

joystick

touch control

panels

Dynamic Positioning

Independent DP joystick

Thruster control

Machinery automation and

cargo control

Chart radar and conning

display

Bridge auxiliaries

Designed for efficiency and

safety

source:

http://www.km.kongsberg.com/ks/web/nokbg0240.nsf/

AllWeb/F6D8ACE8F32AE306C12575C500323661?OpenDocument



TPSEPkMaster

Integration of Existing Products

Anchor Handling ship

K master

Anchor Handling

Dyn

am

ic P

ositio

nin

g

Au

tom

atio

n

Na

vig

atio

n

tra

inin

g

do

cu

me

nta

tio

nTheory and Practice of Systems Engineering in Kongsberg Projects20 Gerrit Muller


TPSEPappsVsProducts

Software Stack

Anchor

Handling ship

computing hardware

qualified and configured OS

real-time control

I/O

Anchor

Handling

DP services

applications

systems

?

?

technology

products

projects

Rbus

AIM

AK



TPSEPmaritimeStack

Understanding Stakeholder Needs

geographical

example of

anchor placement

rig

work flow



TPSEPanchorHandling

Example of System Quality: Configurability

Anchor Handling ship

K master

Anchor Handling

Na

vig

atio

n

Au

tom

atio

n

tra

inin

g

do

cu

me

nta

tio

n

emerging

configurability:

multiple configuration

utilities configuring

similar data in

different ways D

yn

am

ic P

ositio

nin

g



TPSEPconfigurabilityAH

Concept Selection Examples from Subsea

connectors in hub with roll-off

connectors in hub

wireless connection

two sided connectors

EDP

LRP

XT

RIG

Workover Stack

concept for connection



FMCconcepts

Quality and Understanding Improves by Iteration

value of

concept

understanding

of needs and

solutions

time

concept 1

concept 2

concept 3

concept 4

we learn by evaluating concepts; multiple iterations are

needed



TPSEPconceptsLearning

Size considerations



SE revisited

CAFCR+


size considerations




start

finish



TPSEPlogoSize

Level of Abstraction Single System

100

101

106

105

104

103

102

107

static system definition

monodisciplinary

nu

mb

er o

fd

etai

ls

system

requirements

multidisciplinary

design


version: 0.1June 5, 2018RAPpyramid

From system to Product Family or Portfolio

nu

mb

er

of

de

tails

system

multidisciplinary

monodisciplinary

100

101

106

105

104

103

102

107

100

101

106

105

104

103

102

107

108

109

systems

multidisciplinary

monodisciplinary

system portfolio

increase



DRALpyramidGrowth

Product Family in Context

100

106

103

109

systems

multidisciplinary design

parts, connections, lines of code

103

109

106

stakeholders

enterprise

enterprise contextn

um

be

r o

f

de

tails


version: 0.1June 5, 2018RAPdiabolo

Frequently observed gaps

10 0

10 6

10 3

10 9

systems

multidisciplinary

monodisciplinary

10 3

10 9

10 6

stakeholders

enterprise

enterprise context

num

ber o

f de

tails

multidisciplinary

gap

context gap

marketing gap



DRALgaps

One More Example from Kongsberg



SE revisited

CAFCR+


size considerations




start

finish



TPSEPlogoExample3

Highly Successful Remote Weapon Station

Extreme fast growing business: Remote Weapon Station

* PROTECTOR Hellfire

* PROTECTOR Javelin

* PROTECTOR Lite

* PROTECTOR NM221

* Sea PROTECTOR

* PROTECTOR M151

* PROTECTOR CROWS

* PROTECTOR Training Systems

source:

http://www.kongsberg.com/en/KPS/Products/RemoteWeaponStation.aspx



TPSEPprotector

Growth in many directions

profit

turnover

customers

syste

ms in

th

e fie

ld



TPSEPprotectorGrowth

Consequences of Growth

employees

configurations

sites

nationalities

platform

s

weapons

sensors



TPSEPprotectorGrowthConsequences

Conclusions Systems Engineering



SE revisited

CAFCR+


size considerations




start

finish



TPSEPlogoConclusions

What I Hope that you will Remember

Know your stakeholders and their needs and concerns.

The specification must fit the needs.

Concepts and technology must be appropriate.

The system must fulfill all qualities.

And all of this has to happen in time. no analysis paralysis



TPSEPconclusionsSE

Colophon

This presentation is partially based on the master project work of:

Ola Gustav Kalager

Håvard Ruden

under supervision of Thor Hukkelås

and on research work within the Kongsberg Group

where many employees contributed thorugh interviews or work shops.

One example is based on the master project of Dag Jostein Klever (FMC)



TPSEPcolophon

Questions from Kongsberg



SE revisited

CAFCR+


size considerations




start

finish It is your turn!



TPSEPlogoQuestions

theory and practice of systems engineering in … · theory and practice of systems engineering in...

Documents