Decrypting the Innovation Process and Corporate Memory › ... · Unit Test Fabricate Construct...

Oct 21‐24 | Tampa, FLhttps://www.ndia.org/events/2019/10/21/22nd‐annual‐systems‐and‐mission‐engineering‐conference/[email protected] ‐ 1.513.237.9589

Decrypting the Innovation Processand Corporate Memory

Decrypting the Innovation Processand Corporate Memory

via a MBSE and Architecture

| [email protected] | +1.513.237.9589

via a MBSE and Architecture

| [email protected] | +1.513.237.9589


Agenda:

• Introduce P&G

• Problem

• Solution Strategy– Canonical systems model– IT architecture

• Strategy Realization– P&G prototype solution– “Knowledge Based Systems Engineering” (KBSE) consortium

2


What does CPG and Aero, Auto, Mil Have in Common?

3

How To Achieve a Billion $ in Sales

Product/Service Similarities:• Simple goals:

• Deliver payload• Absorb spill

• Complicated delivery• Multi‐physics (device to molecule)• Heavy use of super‐computers for simulations• Regulatory requirements

Initiative Differences:New product lifecycle: <2 years vs 10+ years


Similar “System of Systems” Complexity

4

>130Manufacturing

Plants

>130Manufacturing

Plants

>130Manufacturing

Plants

250ShippingLocations



>70,000ExternalPartners



1.5BTruck Kilometers

Per Year


Per Year


Per Year

>99,000P&G People>99,000P&G People>99,000P&G People


What else do we have in common?

StockMarket

Investment

Returns

Sales Growth

Margin Growth

Capital Efficiency

5

System of Systems of Innovation

Investment

Returns

Lethality ofEach $

Defense


Agenda

• Introduce P&G

• Problem



6


Common Challenge: Innovation Black Box

Multi‐Discipline System of Innovation

StakeholderRequirements

Tests Financials

Idea

Design

?

7

Residuals

Residuals



Common Challenge: Innovation Black Box

8

StakeholderRequirements

Tests Financials

Idea

Design

?


Residuals

Residuals

Detailed Design

UnitTest

FabricateConstruct

Design Integration Test

Architecture(Interactions)

SystemTest

NeedAnalysis

AcceptanceTest


Work Process: for Systems Lifecyle Mgmt

9

Enterprise Mgmt Processes

Project Processes Technical Processes

Environment

Agreement Processes

Investment

System Life Cycle

Resource

Quality

Acquisition

Supply

Project Planning

Project Assessment

Project Control

Decision Making

Risk Mgmt

Configuration Mgmt

Information Mgmt

Stakeholder Needs

Requirements Analysis

Architectural Design

Implementation

Verification

Transition

Validation

Operation

Maintenance

Disposal

Integration

ISO‐15288 Industry Standard Process Framework

?


Residuals

Residuals


Work Process: Carried out in silos

10

Enterprise Mgmt Processes

Project Processes Technical Processes

Environment

Agreement Processes

Investment

System Life Cycle

Resource

Quality

Acquisition

Supply

Project Planning

Project Assessment

Project Control

Decision Making

Risk Mgmt

Configuration Mgmt

Information Mgmt

Stakeholder Needs

Requirements Analysis

Architectural Design

Implementation

Verification

Transition

Validation

Operation

Maintenance

Disposal

Integration

ISO‐15288 Industry Standard Process FrameworkDiscipline Based GovernanceDiscipline Based Governance


Innovation White Box

11

Mtg Mtg Mtg

MtgMtg Mtg

Mtg

Mtg

Mtg

Mtg

Mtg

Mtg

Mtg

Mtg

Mtg

Mtg

Discipline Based GovernanceDiscipline Based Governance


V-Model: Unstructured == Encrypted

12

UnitTest

FabricateConstruct

Integration Test

SystemTest

AcceptanceTest

Detailed Design

Design


NeedAnalysis

Stakeholder Requirements

Testing

Maintenance

ScienceSystem Requirements

Concept of Operations

?

?

?

?

?

??

What happens if I make this change?

What happens if I make this change?

PLM & Discipline Specific Design ToolsPLM & Discipline Specific Design Tools

Unstructured Data


Created by Boeing

Diamond Model: Unstructured == Encrypted

Copyright © 2018 Boeing. All rights reserved.

DIGITAL THREAD

AS-OFFERED

AS-NEEDED

AS-SPECIFIED

AS-DESIGNED

AS-PLANNED AS-BUILT

AS-TESTED

AS-CERTIFIED

AS-DELIVERED

AS-SUPPORTED

VIRTUALCERTIFICATION

VIRTUAL ECOSYSTEM

VIRTUAL OPERATIONS

VIRTUALIMPLEMENTATION

VIRTUAL QUALIFICATION

BUSINESS MODEL

IMPLEMENTATIONMODEL

MARKET (MISSION) MODEL

PHENOMENA MODEL

SYSTEMSMODEL

NEEDS SOLUTIONS

PHYSICAL SYSTEMS

DIGITAL TWINS

Stakeholder Requirements

Testing

Maintenance

ScienceSystem Requirements

Concept of Operations

?

?

?

?

??

Unstructured Data

?



Costs of Lack of Structure & Traceability

14

Mtg Mtg Mtg

MtgMtg Mtg

Mtg

Mtg

Mtg

Mtg

Mtg

Mtg

Mtg

Mtg

Mtg

Mtg

Mtg

• Requirements Mgmt• awareness trade spaces • incorrect requirements• overlooked requirements• overly constrained requirements • pre‐mature convergence on solution

• Knowledge Re‐Use• ”why” knowledge• “how to” knowledge

Decision models struggle with

emergent behavior

Translation errors

Check‐list driven vs tailored plans


Agenda

• Introduce P&G

• Problem



15


Discipline Based GovernanceDiscipline Based Governance

Each discipline re-inventing system description schema to provide requirements context

System of SystemsSystem of Systems

Discipline 1 Discipline 2 Discipline 3

Discipline 6Discipline 5Discipline 4


System Driven Initiative Plans

17

Mtg Mtg Mtg

MtgMtg Mtg

Mtg

Mtg

Mtg

Mtg

Mtg

Mtg

Mtg

Mtg

Mtg

Mtg

Mtg

CurrentState

Mtg

Mtg

Mtg

Mtg

Systems Pattern


Bene

fit

Complexity

Structured Data Options?

18

Subject Predicate Object

Requirement Assigned To Design Component

Requirement Verified By Test

etc etc etc

Triple Store for “Linked Data”SysML

Metamodel Complexity Continuum

Detailed Design

UnitTest

FabricateConstruct



SystemTest

NeedAnalysis

AcceptanceTest

Realityvs

What People Want

Realityvs

What People Want


Detailed Design

UnitTest

FabricateConstruct



SystemTest

NeedAnalysis

AcceptanceTest

Requirement: Cross Discipline, Concurrent

19

Org3Org3 Org4Org4



Agenda

• Introduce P&G

• Problem



20


Subject System

Canonical Systems Knowledge Model

21

Interaction

Stakeholder

Feature

Satisfies

AttributeAttributeAttribute

Functional Role

Functional RoleAttribute

Attribute

Attribute

Attribute

Attribute

Attribute

Design Component

Attribute

Attribute

Attribute

Attribute

Delivers

Coupling

Coupling

Design Component

Attribute

Attribute

Fulfills

Force, Mass, Energy or Information

Design Component

Syst

em P

erfo

rman

ce

Component Performance

Amp-Hr/Use

Behavior Requirement

* The “Canonical” model above isWilliam Schindel’s (of ICTT) “Systematica” method.

Mis

sion

Met

ric

System Performance

FulfillsFulfills

Functional Role


Subject System

Canonical Systems Knowledge Model

22

Interaction

Stakeholder

Feature

Satisfies

AttributeAttributeAttribute

Functional Role


Attribute

Attribute

Attribute

Attribute

Attribute

Design Component

Attribute

Attribute

Attribute

Attribute

Delivers

Design Component

Attribute

Attribute

Fulfills


Design Component


FulfillsFulfills

Functional Role


Canonical Systems Model: Fractal

23

InteractionFunctional Role

Functional Role


Attribute

Attribute

Attribute

Attribute

Attribute



Coupling

Detailed Design

UnitTest

FabricateConstruct



SystemTest

NeedAnalysis

AcceptanceTest

Derived Requirements


Canonical Systems Model: Fractal

24


Agenda

• Introduce P&G

• Problem



25


MechanicalMechanical

IT Architecture Implications

26

ElectricalElectrical

“Systems” Model“Systems” Model“Systems” Model“Systems” Model

Interaction

Stakeholder

FeatureA ib

eAttribut

eAtt ib t

eAttribut

eAtt ib t

eAttribut

e

Functional Role

Functional Role

Functional Role

Attribute

Attribute

Attribute

Attribute

Attribute

Attribute

Coupling



Project/Program Processes

Discipline Specific Technical Work Processes

OSLCOSLC OSLCOSLC

First Principles Simulation

IP / Paten

tIP / Paten

t

Project M

gmt

Project M

gmt

Proc

urem

ent

Proc

urem

ent

Regu

latory

Regu

latory

Facilities En

gine

ering

Facilities En

gine

ering

Cost E

ngineering

Cost E

ngineering

Relia

bility En

gine

ering

Relia

bility En

gine

ering

Ope

ration

sOpe

ration

s

IP / Paten

t

Project M

gmt

Proc

urem

ent

Regu

latory

Facilities En

gine

ering

Cost E

ngineering

Relia

bility En

gine

ering

Ope

ration

s

OSLCOSLC

SysML(Rhapsody)

Design Component Design

Component

Design Component

Design Component

OSLC(FMI)OSLC(FMI)


Agenda

• Introduce P&G

• Problem



27


Systems of Systems Context for Planning

28

System 1.1(Role)

Feature B

Stakeholder2

Interaction

System 1

Interaction System 1.3(Role)

System 1.2(Role)

Feature C

Stakeholder3

Requirement

Requirement

RequirementRequirement

Requirement Requirement

Requirement

Requirement Requirement

Requirement

Requirement

Feature A

Stakeholder1

System 2.2(Role)

System 2.1(Role)

Feature D

Stakeholder4

Requirement

Requirement

Requirement

Requirement

Requirement

Requirement

System 2

Interaction

Interaction

Requirement

Requirement

Requirement

Requirement

Requirement

Requirement

Interaction

Requirement

Requirement

Requirement

System 1.3(Role)

Requirement

Requirement

Requirement

Feature E

Stakeholder5

Knowledge Gapsand/or

Competitive Activityand/or

Simulations Needed

Current activitiesand/or

Strengths To Exploit

Part: 192034(Design Component)

Material: A‐123.1(Design Component)

Device: 283432(Design Component)

Material: CGAS123(Design Component)

Cross FunctionalChange Impact Analysis

Material: A‐123.1(Design Component)


A Real Model: Four System Features Decomposed

29


Mod

el In

tera

ctio

n De

mo

30


Agenda

• Introduce P&G

• Problem



31


So systems knowledge modeling it’s easy... right?

32

Detailed Design

UnitTest

FabricateConstruct



SystemTest

NeedAnalysis

AcceptanceTest

P&G internal review of work processes indicates >400 document types produced by a large initiative.

SAIC estimates >400 types of artifacts are intimated by ISO15288 “activities”

Gartner Hype Cycle?

What uses are here?What uses are here?

What should we avoid?

What should we avoid?


Systems Engineering Hype Cycle

33

Focus Initial Promises HereFocus Initial

Promises Here


KBSE Consortium Analysis

Sub Activity Type n.1Sub Activity Type n.2Sub Activity Type n.3

Sub Activity Type 1.1

15288 Process Type B

Sub Activity Type 1.2Sub Activity Type 1.3

Sub Activity Type n.1Sub Activity Type n.2Sub Activity Type n.3

Activity Type 1

Activity Type n

AutomationUse Cases

Use Case Step 1

Use Case Step 2

Use Case Step 3

Use Case Step 1

Use Case Step 2

Use Case Step 3

AUC-A

Use Case Step 3

AUC-B

Use Case Step 2

Use Case Step 1

AutomationObjectives

Use Case A

Use Case B

Use Case A

Use Case C

Objective 1

Objective 2

Sub Activity Type 1.1

15288 Process Type A

ISO_15288+SAIC

Data Representations (SAIC)

Data: A Data: C

Data: D

ISO_15288

Outcome 1

15288 Process Type AOutcomes~50 KBSE

Common Future Business Capability

RequirementsBusiness Change 1Business Change 2Business Change 3

AutomationRequirementsRequirement 1Requirement 2Requirement 3

Role 1Role 2Role 3

Roles (SAIC)

Outcome n

Activity 1Activities

Activity n

Outcome 1

15288 Process Type BOutcomes

Outcome n

Activity 1Activities

Activity n

Step 1

Step 2

Step 3

Work Process A

Work Process BStep 1

Step 2

Step 3

Work Processes (TBD)

Sub Activity Type 1.2Sub Activity Type 1.3

Roles

Activity Type 1

Canonical System Knowledge Model

Data: A Data: B

Data: C

Activity Type n

AUC-C

Data: E

Data: B

34

Influence Standards

Co-investInfluence Suppliers


Please reach out to collaborateif you have similar needs/plans

| [email protected] | +1.513.237.9589

3535

Decrypting the Innovation Process and Corporate Memory › ... · Unit Test Fabricate Construct...

Documents

Transcript of Decrypting the Innovation Process and Corporate Memory › ... · Unit Test Fabricate Construct...