1 Application of a Model Based Systems Engineering Method to Manage Project Risk Fred Rojek Booz...

39
1 Application of a Model Based Systems Engineering Method to Manage Project Risk Fred Rojek Booz Allen Hamilton Advanced Risk Management Seminar Applications to Systems Engineering November 8–9

Transcript of 1 Application of a Model Based Systems Engineering Method to Manage Project Risk Fred Rojek Booz...

Page 1: 1 Application of a Model Based Systems Engineering Method to Manage Project Risk Fred Rojek Booz Allen Hamilton Advanced Risk Management Seminar Applications.

1

Application of a Model Based Systems Engineering Method to Manage Project Risk

Fred Rojek Booz Allen Hamilton

Advanced Risk Management Seminar Applications to Systems Engineering

November 8–9

Page 2: 1 Application of a Model Based Systems Engineering Method to Manage Project Risk Fred Rojek Booz Allen Hamilton Advanced Risk Management Seminar Applications.

2

Thesis

Application of a Model Based Systems Engineering method can contribute to the implementation of an effective risk management program because…

Page 3: 1 Application of a Model Based Systems Engineering Method to Manage Project Risk Fred Rojek Booz Allen Hamilton Advanced Risk Management Seminar Applications.

3

Agenda

Systems Engineering Objective

Systems Engineering Challenge

Essential Elements of a Model Based Systems Engineering Method

MBSE Application Example

Conclusion

Page 4: 1 Application of a Model Based Systems Engineering Method to Manage Project Risk Fred Rojek Booz Allen Hamilton Advanced Risk Management Seminar Applications.

4

Systems Engineering’s Objective

Translate user operational needs into an efficient and cost-effective system solution

Capture the solution in a complete and coherent* system documentation** needed to design, integrate, test, operate and logistically support a system that fully meets user operational needs

– Specification

– Design

– Test

– Operation

– Support

– Other Supporting Work Products: Trade Studies, Analyses, Technical Reports, Meeting Minutes…

* Coherent: Composed of mutually dependent parts; making a logical whole; consistent; as a coherent plan, argument, or discourse. Webster Dictionary** Also known as work products

Page 5: 1 Application of a Model Based Systems Engineering Method to Manage Project Risk Fred Rojek Booz Allen Hamilton Advanced Risk Management Seminar Applications.

5

Systems Engineering’s Challenge

Capture the solution in a complete and coherent system documentation needed to design, integrate, test, operate and logistically support a system…

User Operational

Needs &Constraints

Concept of Operations Concept of Operations

SystemPerformance

Spec

SystemPerformance

Spec

HardwareRequirementsSpecification

HardwareRequirementsSpecification

HardwareRequirementsSpecification

HardwareRequirementsSpecification

HardwareRequirementsSpecification

HardwareRequirementsSpecification

SoftwareRequirementsSpecification

SoftwareRequirementsSpecification

SoftwareRequirementsSpecification

SoftwareRequirementsSpecification

Test PlanTest PlanTest

PlanTest Plan

LogisticSupport

Plan

LogisticSupport

Plan

System/SegmentDesign

Description

System/SegmentDesign

Description

Interface Control

Documents

Interface Control

Documents

StandardOperating Practices

& Procedures

StandardOperating Practices

& Procedures

SystemsEngineeringProcesses

DevelopmentSpecificationDevelopmentSpecificationDevelopment

SpecificationDevelopmentSpecificationDevelopment

SpecificationDevelopmentSpecification

Page 6: 1 Application of a Model Based Systems Engineering Method to Manage Project Risk Fred Rojek Booz Allen Hamilton Advanced Risk Management Seminar Applications.

6

Systems Engineering’s Challenge

System requirements, design data, and information relevant to a wide variety of engineering, technical and domain disciplines

– Totality of requirements in the thousands (possibly tens of thousands); Often changing, sometimes well into design

– Dozens (possibly hundreds) of scientists, specialists, engineers, designers, testers, manufacturers…, from multiple & diverse technical disciplines

– Customers, operators, maintainers, suppliers… with great domain expertise, little engineering expertise (and vice versa)

– Should tie together into a unified whole

– Should always be traceable to User Operational Needs

Hundreds to thousands of components employing a wide variety of technologies manufactured throughout the country, possibly the world (ex. International Space Station)

Never ending issues and risks associated at varying development levels that span a wide range of technical and domain expertise

Page 7: 1 Application of a Model Based Systems Engineering Method to Manage Project Risk Fred Rojek Booz Allen Hamilton Advanced Risk Management Seminar Applications.

7

Application of a MBSE Method to Partially Address the Challenge

SystemsEngineeringProcesses

User Operational

Needs &Constraints

Model BasedSystems Engineering

Method

sup

po

rts

Concept of Operations Concept of Operations

SystemPerformance

Spec

SystemPerformance

Spec

HardwareRequirementsSpecification

HardwareRequirementsSpecification

HardwareRequirementsSpecification

HardwareRequirementsSpecification

HardwareRequirementsSpecification

HardwareRequirementsSpecification

HardwareRequirementsSpecification

HardwareRequirementsSpecification

HardwareRequirementsSpecification

HardwareRequirementsSpecification

HardwareRequirementsSpecification

HardwareRequirementsSpecification

SoftwareRequirementsSpecification

SoftwareRequirementsSpecification

SoftwareRequirementsSpecification

SoftwareRequirementsSpecification

SoftwareRequirementsSpecification

SoftwareRequirementsSpecification

SoftwareRequirementsSpecification

SoftwareRequirementsSpecification

Test PlanTest PlanTest

PlanTest Plan

Test PlanTest PlanTest

PlanTest Plan

LogisticSupport

Plan

LogisticSupport

Plan

System/SegmentDesign

Description

System/SegmentDesign

Description

Interface Control

Documents

Interface Control

Documents

StandardOperating Practices

& Procedures

StandardOperating Practices

& Procedures

DevelopmentSpecificationDevelopmentSpecificationDevelopment

SpecificationDevelopmentSpecificationDevelopment

SpecificationDevelopmentSpecification

DevelopmentSpecificationDevelopmentSpecificationDevelopment

SpecificationDevelopmentSpecificationDevelopment

SpecificationDevelopmentSpecification

Page 8: 1 Application of a Model Based Systems Engineering Method to Manage Project Risk Fred Rojek Booz Allen Hamilton Advanced Risk Management Seminar Applications.

8

Essential Elements of a MBSE Method

1. Use of models as the central and unifying element to the development of a system*

2. Application across SE processes

3. Application down and up development levels

4. Application throughout system lifecycle

5. Use of computerized SE tools to support the method

* “…model-based [systems] engineering is about elevating models in the engineering process to a central and governing role in the specification, design, integration, validation, and operation of a system.” Estefan, J.A., Survey of Model Based Systems Engineering Methodologies, INCOSE MBSE Focus Group (http://syseng.omg.org/MBSE_Methodology_Survey_RevA.pdf)

Page 9: 1 Application of a Model Based Systems Engineering Method to Manage Project Risk Fred Rojek Booz Allen Hamilton Advanced Risk Management Seminar Applications.

9

1. Models as Central and Unifying Element

Well defined, unambiguous language/notation, understood by all stakeholders, to describe and analyze the system

Multiple system views to fully communicate system requirements and design

– Requirements, Behavioral, Structure, Performance, Data, Managerial…

– Integrated/Traceable; Complimentary; Consistent…non contradictory

Underlying structure (or schema) to define model elements, attributes and relationships – Information Model

Executability

Models are the primary means of communication with clients, builders, and users; models are the language of the architect. The Art of Systems Architecting, Maier, M., Rechtin, E., CRC Press, 2002

Page 10: 1 Application of a Model Based Systems Engineering Method to Manage Project Risk Fred Rojek Booz Allen Hamilton Advanced Risk Management Seminar Applications.

10

AND

OA.1.1.1.1

Produce FDS

OA.1.1.1.2

Request Training(via Request

Field Services)

AND

OA.1.1.1.3

Review FDS

OA.1.1.10.1

Receive andDisposition Waste

AcceptanceRequirements (u...

AND

OA.1.1.10.2

Develop andDisseminate SiteCampaign Plan

(using the Opera...

OA.1.1.10.3

Develop andDisseminate

Annual ShipmentPlan

AND

FinalDelivery ...

FieldServices ...

FDS,Reviewed...

FDS,Finalized/...

SiteCampaign ...

AnnualShipment ...

Schedule

AND

OA.1.1.1.1

Produce FDS

OA.1.1.1.2

Request Training(via Request

Field Services)

AND

OA.1.1.1.3

Review FDS

OA.1.1.10.1

Receive andDisposition Waste

AcceptanceRequirements (u...

AND

OA.1.1.10.2

Develop andDisseminate SiteCampaign Plan

(using the Opera...

OA.1.1.10.3

Develop andDisseminate

Annual ShipmentPlan

AND

FinalDelivery ...

FieldServices ...

FDS,Reviewed...

FDS,Finalized/...

SiteCampaign ...

AnnualShipment ...

Schedule

documents documents documents documents documents documents documents documents documents

verified by verified by verified by verified by verified by

Doc.6

TransportationRequirements Doc

Document

Sys.1

TransportationSystem (TSRD4)

Component

TSRDCO.4.1

CommunicationEquipment Com...

Requirement

CommunicationEquipment Com...

VerificationRequ...

TSRDCO.4.2

CommunicationsEquipment Inde...

Requirement

CommunicationsEquipment Inde...

VerificationRequ...

TSRDCO.4.4

CommunicationsEquipment Reliabi...

Requirement

CommunicationsEquipment Reliabi...

VerificationRequ...

TSRDF.4.10

Space for ConsistAssembly

Requirement

Space for ConsistAssembly

VerificationRequ...

TSRDF.4.11

TransportationPackage Decon...

Requirement

TSRDF.4.13

Rolling StockDecontamination

Requirement

Rolling StockDecontamination

VerificationRequ...

TSRDF.4.17

Train Assemblyand Disassembly...

Requirement

TSRDF.4.18

Brake SystemSafety Standards

Requirement

documents documents

refined by refined by refined by refined by refined by refined by

Doc.1

WMSRequirements D...

Document

CRD.7.3.2

Command &Control

Requirement

TSRD.4.94

Rail ConsistTracking

Requirement

TSRD.4.135

Truck ConsistTrasking

Requirement

TSRDT.4.1

Rail ConsistCommunications

Requirement

CRD.7.3.3

TransportationRates

Requirement

TSRD.4.7

Special WasteContainer Capabi...

Requirement

TSRDF.4.8

Storage ofContainer Inven...

Requirement

TSRDF.4.9

Storage of RollingStock Inventory

Requirement

Multiple System Views to Communicate Requirements & Design*

Physical Hierarchy(System Structure)

Physical Block Diagram (System Interconnection)

Requirements Hierarchy(System Traceability)

*Views produced by CORE

Verification Requirements

R

built from built from built from built from built from built from

built from built from built from built from built from built from built from built from built from

Sys.1

TransportationSystem

Component

Sys.1.1

MaintenanceFacility

Component

Sys.1.3

Operation Center

Component

Sys.1.3.1

C2 Equip

Component

Sys.1.3.2

Comm Equip

Component

Sys.1.3.3

Ops Center

Component

Sys.1.4

Containers

Component

Sys.1.4.1

Outer Shell

Component

Sys.1.4.2

Storage Container

Component

Sys.1.4.3

TransportationSkid

Component

Sys.1.5

Rail Equipment

Component

Sys.1.5.1

Container Car

Component

Sys.1.5.2

Crew Car

Component

Sys.1.5.3

Buffer Car

Component

Sys.1.6

Truck Equipment

Component

Sys.1.12

Other SupportSystems

Component

NRC - CRWMS/Transportation/C3

State Authority - CRWMS/Transportation/C3

DH

S -

CRW

MS/

Tran

spor

tatio

n/C3

Commercial Rail Business Ops -- CRWMS/Transportation/C3

FBI - CRWMS/Transportation/C3

Coast Guard - CRWMS/Transportation/C3

Rail Consist - C2, Comm (Primary) NWS - CRWMS/Transportation/C3

Local Authority - CRWMS/Transportation/C3

Fede

ral A

utho

rity

-CR

WM

S/Tr

ansp

orta

ti...

Truck Consist - C2,Tracking Data (Primary)

Commercial Rail Ops Center -CRWMS/Transportation/C3

Rail Consist - C2, Tracking Data (Primary)

PIO - CRWMS/Transportation/C3

CRWMS/WA - CRWMS/Transportation/C3

Commercial Truck Business Ops -- CRWMS/Transportation/C3

Seciurity Contractor - CRWMS/Transportation/C3

Origin Site - CRWMS/Transportation/C3

CRWMS/MGR - CRWMS/Transportation...

Commercial Truck Ops Center -CRWMS/Transportation/C3

Truck Consist - C2, Comm (Primary)

Transportation Barge - CRWMS/Transportation/C3, Tracking Data

DOE EOC -- CRWMS/Transportation/C3

Trib

al A

utho

ritie

s -

CRW

MS/

Tran

spor

tatio

n/C3

Cask MaintenanceFacility

Node

Command & Control

Node

TransportationOperations Center

Node

Nevada RailInfrastructure

Node

Transportation Casks(Other than TADTransportation

Overpack, AgingOverpack)

Node

Cask Rail Car

Node

Buffer Rail Car

Node

TAD System

Node

Other SupportSystems

Node

Ex.1

Nuclear RegulatoryCommission (NRC)

External

Ex.2

Local Authority

External

Ex.3

State Authority

External

Ex.4

Federal Authority

External

Ex.5

Tribal Authority

External

Ex.6

Department ofHomeland Security

(DHS)

External

Ex.7

Federal Bureau ofInvestigation (FBI)

External

Ex.8

Public InformationOffice (PIO)

External

Ex.9

National WeatherService (NWS)

External

Ex.11

Origin Site (OS)

External

Ex.12.b

Commercial RailBusiness Operations

External

Ex.14.b

Commercial TruckBusiness Operations

External

Ex.16

Transportation Barge

Node

Ex.20

Coast Guard

External

Ex.21

Security Contractor

External

Ex.22

DOE EmergencyOperations Center

External

Op.2

Waste Acceptance

Node

Op.3

Monitored GeologicRepository

Node

Ex.12.a

Commercial RailOperations Center

External

Ex.14.a

Commercial TruckOperations Center

External

Ex.13

Rail Consist

External

Ex.15

Truck Consist

External Operations & Logical/Functional(System Behavior)

Page 11: 1 Application of a Model Based Systems Engineering Method to Manage Project Risk Fred Rojek Booz Allen Hamilton Advanced Risk Management Seminar Applications.

11

AND

OA.1.1.1.1

Produce FDS

OA.1.1.1.2

Request Training(via Request

Field Services)

AND

OA.1.1.1.3

Review FDS

OA.1.1.10.1

Receive andDisposition Waste

AcceptanceRequirements (u...

AND

OA.1.1.10.2

Develop andDisseminate SiteCampaign Plan

(using the Opera...

OA.1.1.10.3

Develop andDisseminate

Annual ShipmentPlan

AND

FinalDelivery ...

FieldServices ...

FDS,Reviewed...

FDS,Finalized/...

SiteCampaign ...

AnnualShipment ...

Schedule

AND

OA.1.1.1.1

Produce FDS

OA.1.1.1.2

Request Training(via Request

Field Services)

AND

OA.1.1.1.3

Review FDS

OA.1.1.10.1

Receive andDisposition Waste

AcceptanceRequirements (u...

AND

OA.1.1.10.2

Develop andDisseminate SiteCampaign Plan

(using the Opera...

OA.1.1.10.3

Develop andDisseminate

Annual ShipmentPlan

AND

FinalDelivery ...

FieldServices ...

FDS,Reviewed...

FDS,Finalized/...

SiteCampaign ...

AnnualShipment ...

Schedule

documents documents documents documents documents documents documents documents documents

verified by verified by verified by verified by verified by

Doc.6

TransportationRequirements Doc

Document

Sys.1

TransportationSystem (TSRD4)

Component

TSRDCO.4.1

CommunicationEquipment Com...

Requirement

CommunicationEquipment Com...

VerificationRequ...

TSRDCO.4.2

CommunicationsEquipment Inde...

Requirement

CommunicationsEquipment Inde...

VerificationRequ...

TSRDCO.4.4

CommunicationsEquipment Reliabi...

Requirement

CommunicationsEquipment Reliabi...

VerificationRequ...

TSRDF.4.10

Space for ConsistAssembly

Requirement

Space for ConsistAssembly

VerificationRequ...

TSRDF.4.11

TransportationPackage Decon...

Requirement

TSRDF.4.13

Rolling StockDecontamination

Requirement

Rolling StockDecontamination

VerificationRequ...

TSRDF.4.17

Train Assemblyand Disassembly...

Requirement

TSRDF.4.18

Brake SystemSafety Standards

Requirement

documents documents

refined by refined by refined by refined by refined by refined by

Doc.1

WMSRequirements D...

Document

CRD.7.3.2

Command &Control

Requirement

TSRD.4.94

Rail ConsistTracking

Requirement

TSRD.4.135

Truck ConsistTrasking

Requirement

TSRDT.4.1

Rail ConsistCommunications

Requirement

CRD.7.3.3

TransportationRates

Requirement

TSRD.4.7

Special WasteContainer Capabi...

Requirement

TSRDF.4.8

Storage ofContainer Inven...

Requirement

TSRDF.4.9

Storage of RollingStock Inventory

Requirement

Integrated!

built from built from built from built from built from built from

built from built from built from built from built from built from built from built from built from

Sys.1

TransportationSystem

Component

Sys.1.1

MaintenanceFacility

Component

Sys.1.3

Operation Center

Component

Sys.1.3.1

C2 Equip

Component

Sys.1.3.2

Comm Equip

Component

Sys.1.3.3

Ops Center

Component

Sys.1.4

Containers

Component

Sys.1.4.1

Outer Shell

Component

Sys.1.4.2

Storage Container

Component

Sys.1.4.3

TransportationSkid

Component

Sys.1.5

Rail Equipment

Component

Sys.1.5.1

Container Car

Component

Sys.1.5.2

Crew Car

Component

Sys.1.5.3

Buffer Car

Component

Sys.1.6

Truck Equipment

Component

Sys.1.12

Other SupportSystems

Component

NRC - CRWMS/Transportation/C3

State Authority - CRWMS/Transportation/C3

DH

S -

CRW

MS/

Tran

spor

tatio

n/C3

Commercial Rail Business Ops -- CRWMS/Transportation/C3

FBI - CRWMS/Transportation/C3

Coast Guard - CRWMS/Transportation/C3

Rail Consist - C2, Comm (Primary) NWS - CRWMS/Transportation/C3

Local Authority - CRWMS/Transportation/C3

Fede

ral A

utho

rity

-CR

WM

S/Tr

ansp

orta

ti...

Truck Consist - C2,Tracking Data (Primary)

Commercial Rail Ops Center -CRWMS/Transportation/C3

Rail Consist - C2, Tracking Data (Primary)

PIO - CRWMS/Transportation/C3

CRWMS/WA - CRWMS/Transportation/C3

Commercial Truck Business Ops -- CRWMS/Transportation/C3

Seciurity Contractor - CRWMS/Transportation/C3

Origin Site - CRWMS/Transportation/C3

CRWMS/MGR - CRWMS/Transportation...

Commercial Truck Ops Center -CRWMS/Transportation/C3

Truck Consist - C2, Comm (Primary)

Transportation Barge - CRWMS/Transportation/C3, Tracking Data

DOE EOC -- CRWMS/Transportation/C3

Trib

al A

utho

ritie

s -

CRW

MS/

Tran

spor

tatio

n/C3

Cask MaintenanceFacility

Node

Command & Control

Node

TransportationOperations Center

Node

Nevada RailInfrastructure

Node

Transportation Casks(Other than TADTransportation

Overpack, AgingOverpack)

Node

Cask Rail Car

Node

Buffer Rail Car

Node

TAD System

Node

Other SupportSystems

Node

Ex.1

Nuclear RegulatoryCommission (NRC)

External

Ex.2

Local Authority

External

Ex.3

State Authority

External

Ex.4

Federal Authority

External

Ex.5

Tribal Authority

External

Ex.6

Department ofHomeland Security

(DHS)

External

Ex.7

Federal Bureau ofInvestigation (FBI)

External

Ex.8

Public InformationOffice (PIO)

External

Ex.9

National WeatherService (NWS)

External

Ex.11

Origin Site (OS)

External

Ex.12.b

Commercial RailBusiness Operations

External

Ex.14.b

Commercial TruckBusiness Operations

External

Ex.16

Transportation Barge

Node

Ex.20

Coast Guard

External

Ex.21

Security Contractor

External

Ex.22

DOE EmergencyOperations Center

External

Op.2

Waste Acceptance

Node

Op.3

Monitored GeologicRepository

Node

Ex.12.a

Commercial RailOperations Center

External

Ex.14.a

Commercial TruckOperations Center

External

Ex.13

Rail Consist

External

Ex.15

Truck Consist

External

allocated to

functional I/O implemented by

trace to

verified by

Additional Views used as required to communicate other relevant system characteristics

Page 12: 1 Application of a Model Based Systems Engineering Method to Manage Project Risk Fred Rojek Booz Allen Hamilton Advanced Risk Management Seminar Applications.

12

Information Model Example*

* Partial View of CORE Schema

Risk

causes

Organization

assigned to

ProgramActivity

resolved by

Document

documented by

causescauses

basisof

performedby

Component

built from

Interface

joinedto

Function

decomposedby

Requirement

refined by

causes

results in results in

R

VerificationRequirement

verified by

causes

VerificationEvent

fulfilled by

Page 13: 1 Application of a Model Based Systems Engineering Method to Manage Project Risk Fred Rojek Booz Allen Hamilton Advanced Risk Management Seminar Applications.

13

Information Model Example*

* Partial View of CORE Schema

Issue

generates

Organization

assigned to

ProgramActivity

resolved by

Document

documented by

generatesgenerates

basisof

performedby

Component

built from

Interface

joinedto

Function

decomposedby

Requirement

refined by

generates

R

VerificationRequirement

verified by

generates

VerificationEvent

fulfilled by

results in results in

Page 14: 1 Application of a Model Based Systems Engineering Method to Manage Project Risk Fred Rojek Booz Allen Hamilton Advanced Risk Management Seminar Applications.

14

* Trade-off Studies, Risk Management, Interface Management, Configuration Management…

2. Application Across SE Processes

RequirementsModels

BehavioralModels

PhysicalModels

AssessmentResults

RequirementsAnalysis

FunctionalAnalysis

Design/Synthesis

Assessment

Systems Engineering Process ModelSystemPerformanceSpecification

orDevelopmentSpecification

SystemPerformanceSpecification

orDevelopmentSpecification

System Analysis & Control*

To Next Development

Level

Concept of Operations Concept of Operations

ContractorStatement of

Work

ContractorStatement of

Work

.

.

.

Safety AnalysisHuman FactorsRAM AnalysisLogistic AnalysisEMI Analysis…

SystemPerformanceSpecification

orDevelopmentSpecification

SystemPerformanceSpecification

orDevelopmentSpecification

Page 15: 1 Application of a Model Based Systems Engineering Method to Manage Project Risk Fred Rojek Booz Allen Hamilton Advanced Risk Management Seminar Applications.

15

3. Application Down & Up Development Phases

Decom

position & D

esign Inte

grat

ion

& V

erifi

catio

n

SystemPerformance

Spec

SystemPerformance

Spec

SystemDesign

ProductDesign

SubsystemDesign

ComponentDesign

HW Fab &Assembly; SW Code

Part & CSU Verification

ComponentIntegration &Verification

SubsystemIntegration &Verification

ProductIntegration &Verification

SystemIntegration &Verification

ProductDevelopmentSpecifications

ProductDevelopmentSpecifications

ProductDevelopmentSpecifications

ProductDevelopmentSpecificationsProduct

DevelopmentSpecifications

ProductDevelopmentSpecifications

SubsystemDevelopmentSpecifications

SubsystemDevelopmentSpecifications

SubsystemDevelopmentSpecifications

SubsystemDevelopmentSpecifications

SubsystemDevelopmentSpecifications

SubsystemDevelopmentSpecifications

SoftwareRequirementsSpecification

SoftwareRequirementsSpecification

SoftwareRequirementsSpecification

SoftwareRequirementsSpecification

HardwareRequirementsSpecification

HardwareRequirementsSpecification

HardwareRequirementsSpecification

HardwareRequirementsSpecification

Verification Requirements

Verification Results

Verification Requirements

Verification Results

VerificationRequirements

VerificationResults

VerificationRequirements

Verification

Results

ConceptOperational

Test

Validation Requirements

Validation Results

RequirementsModels

BehavioralModels

PhysicalModels

AssessmentResults

RequirementsAnalysis

FunctionalAnalysis

Design/Synthesis

Assessment

Systems Engineering Process Model

SRDSRDConcept of Operations Concept of Operations

Page 16: 1 Application of a Model Based Systems Engineering Method to Manage Project Risk Fred Rojek Booz Allen Hamilton Advanced Risk Management Seminar Applications.

16

4. Application Throughout Acquisition Lifecycle

ConceptRefinement

SyS

Prod 3Prod 2Prod 1

AdvancedDevelopment

Engineering Design

Integration &Evaluation

ProductionOperation & Support

Increasing Model Complexity

Sys

Prod 3Prod 2Prod 1

Subsys 3.1Subsys 1.2Subsys 1.1 Subsys 3.2

Sys

Prod 3Prod 2Prod 1

Subsys 3.1Subsys 1.2Subsys 1.1 Subsys 3.2

Comp 3.1.1Comp 1.1.2Comp 1.1.1 Comp 3.1.2

……

Sys

Prod 3Prod 2Prod 1

Subsys 3.1Subsys 1.2 Subsys 3.2

Comp 3.1.1Comp 1.1.2 Comp 3.1.2.a

Comp 3.1.3

Subsys 1.1

Comp 1.1.1

Page 17: 1 Application of a Model Based Systems Engineering Method to Manage Project Risk Fred Rojek Booz Allen Hamilton Advanced Risk Management Seminar Applications.

17

System Development History Maintained

Accumulated System Data & Information

(History)

ConceptRefinement

AdvancedDevelopment

Engineering Design

Integration &Evaluation

ProductionOperation & Support

Sys

Prod 3Prod 2Prod 1

Subsys 3.1Subsys 1.2 Subsys 3.2

Comp 3.1.1Comp 1.1.2 Comp 3.1.2.a

Comp 3.1.3

Subsys 1.1

Comp 1.1.1

Page 18: 1 Application of a Model Based Systems Engineering Method to Manage Project Risk Fred Rojek Booz Allen Hamilton Advanced Risk Management Seminar Applications.

18

5. Use of Computerized SE Tools to Support the MBSE Method

Modeling

– Support the modeling language and schema; produce the needed system views

– Maintain horizontal and vertical traceability

Data Management

– Single, central repository to manage all related system data and information

Document Generation

– Automated generation of formal documentation & work products (drawn from central model repository)

System/Segment Specification (SSS); Interface Requirements Specification (IRS); Test & Evaluation Plan (TEP); Software Requirements Specification (SRS)...

Integral to the SE Environment to support the MBSE method

See Survey of Model Based Systems Engineering Methodologies (http://syseng.omg.org/MBSE_Methodology_Survey_RevA.pdf) for a discussion of commercial tools available that could be used to support MBSE method application

Page 19: 1 Application of a Model Based Systems Engineering Method to Manage Project Risk Fred Rojek Booz Allen Hamilton Advanced Risk Management Seminar Applications.

19

MBSE Application Example

Page 20: 1 Application of a Model Based Systems Engineering Method to Manage Project Risk Fred Rojek Booz Allen Hamilton Advanced Risk Management Seminar Applications.

20

Waste Management System (WMS)

System Mission* - Accept, transport, & dispose of hazardous material in a manner that protects health, safety and the environment; and merits public confidence

System Concept

Interface between Waste Production Sites

& Disposal System

Receive and dispose of hazardous material

Transport hazardous material from Waste Generation Sites to Disposal System

WMS

TransportationSystem

WasteAcceptance

System

DisposalSystem

*Documented in WMS Requirements Document

Page 21: 1 Application of a Model Based Systems Engineering Method to Manage Project Risk Fred Rojek Booz Allen Hamilton Advanced Risk Management Seminar Applications.

21

WMS Concept of Operations

Maintenance Facility

DisposalSystem

WasteGeneration

Site

OperationsCenter

Unloaded waste containers

Loaded waste containers

Unloaded waste containers*

Equipment flow

Information flow

*Transportation modes include rail, truck, barge; possibly a combination of all three depending upon OS location

Page 22: 1 Application of a Model Based Systems Engineering Method to Manage Project Risk Fred Rojek Booz Allen Hamilton Advanced Risk Management Seminar Applications.

22

Transportation SystemConcept Model Maintenance

Facility

DisposalFacility Ops

WasteGenerationSite Ops

OperationsCenter

ExistingInfrastructure

utilizes

maintains

coordinates/controls

Waste

xports loadedcontainers to

stores

generates

coordinates/controls

Transportation System Components

DisposalFacility

xports unloaded containers to

WasteGeneration

Site

Waste Container

Rail or TruckEquipment

Transport Equip

carries

contains

Page 23: 1 Application of a Model Based Systems Engineering Method to Manage Project Risk Fred Rojek Booz Allen Hamilton Advanced Risk Management Seminar Applications.

23

WMS Transportation System Development Phase

Decom

position & D

esign Inte

grat

ion

& V

erifi

catio

n

SystemPerformance

Spec

SystemPerformance

Spec

SystemDesign

ProductDesign

SubsystemDesign

ComponentDesign

HW Fab &Assembly;SW Code

Part & CSUVerification

ComponentIntegration &Verification

SubsystemIntegration &Verification

ProductIntegration &Verification

SystemIntegration &Verification

ProductDevelopmentSpecifications

ProductDevelopmentSpecifications

ProductDevelopmentSpecifications

ProductDevelopmentSpecificationsProduct

DevelopmentSpecifications

ProductDevelopmentSpecifications

ProductDevelopmentSpecifications

ProductDevelopmentSpecifications

ProductDevelopmentSpecifications

ProductDevelopmentSpecificationsProduct

DevelopmentSpecifications

ProductDevelopmentSpecifications

SubsystemDevelopmentSpecifications

SubsystemDevelopmentSpecifications

SubsystemDevelopmentSpecifications

SubsystemDevelopmentSpecifications

SubsystemDevelopmentSpecifications

SubsystemDevelopmentSpecifications

SubsystemDevelopmentSpecifications

SubsystemDevelopmentSpecifications

SubsystemDevelopmentSpecifications

SubsystemDevelopmentSpecifications

SubsystemDevelopmentSpecifications

SubsystemDevelopmentSpecifications

SoftwareRequirementsSpecification

SoftwareRequirementsSpecification

SoftwareRequirementsSpecification

SoftwareRequirementsSpecification

HardwareRequirementsSpecification

HardwareRequirementsSpecification

HardwareRequirementsSpecification

HardwareRequirementsSpecification

SoftwareRequirementsSpecification

SoftwareRequirementsSpecification

SoftwareRequirementsSpecification

SoftwareRequirementsSpecificationSoftware

RequirementsSpecification

SoftwareRequirementsSpecification

SoftwareRequirementsSpecification

SoftwareRequirementsSpecification

HardwareRequirementsSpecification

HardwareRequirementsSpecification

HardwareRequirementsSpecification

HardwareRequirementsSpecification

HardwareRequirementsSpecification

HardwareRequirementsSpecification

HardwareRequirementsSpecification

HardwareRequirementsSpecification

Verification Requirements

Verification Results

Verification Requirements

Verification Results

VerificationRequirements

VerificationResults

VerificationRequirements

VerificationResults

ConceptOperational

Test

Validation Requirements

Validation ResultsSRDSRD

Concept of Operations Concept of Operations

Page 24: 1 Application of a Model Based Systems Engineering Method to Manage Project Risk Fred Rojek Booz Allen Hamilton Advanced Risk Management Seminar Applications.

24

System Model Views

* All views produced by the CORE SE Tool

Page 25: 1 Application of a Model Based Systems Engineering Method to Manage Project Risk Fred Rojek Booz Allen Hamilton Advanced Risk Management Seminar Applications.

25

System Requirements (sample)

The system shall be capable of:

– Accepting and receiving 400 tons of waste in 1st year of operations

– Accepting and receiving 3800 tons in 2nd year of operations

– …

Shall be capable of accommodating a range of waste storage and transportation technologies

Shall comply with the applicable provisions of:

– Legislation

– Code of Federal Regulations (CFR)

– EPA Standards

– DoT Regulations

– Association of American Railroads (AAR) Regs

– …

Page 26: 1 Application of a Model Based Systems Engineering Method to Manage Project Risk Fred Rojek Booz Allen Hamilton Advanced Risk Management Seminar Applications.

26

documents documents

refined by refined by refined by refined by refined by refined by refined by refined by refined by

Doc.1

WMSRequirements D...

Document

CRD.7.3.3

TransportationRates

Requirement

TSRD.4.7

Special WasteContainer Capabi...

Requirement

TSRDF.4.8

Storage ofContainer Inven...

Requirement

TSRDF.4.9

Storage of RollingStock Inventory

Requirement

TSRDN.4.32

EOL Storage ofRolling Stock

Requirement

TSRDS.4.2

SNF and HLWTransportation ...

Requirement

CRD.7.3.2

Command &Control

Requirement

TSRD.4.94

Rail ConsistTracking

Requirement

TSRD.4.135

Truck ConsistTrasking

Requirement

TSRDT.4.1

Rail ConsistCommunications

Requirement

TSRDT.4.4

Truck ConsistCommunications

Requirement

Requirements Model Development

“The WMS shall be capable of receiving waste, mostly by rail, at the system operating conditions and receipt rates specified in…”

The Transportation System shall have the capability to store (TBD)% of the waste container inventory.

RequirementsModels

BehavioralModels

PhysicalModels

AssessmentResults

RequirementsAnalysis

FunctionalAnalysis

Design/Synthesis

Assessment

Systems Engineering Process

“The WMS shall comply with the waste material transportation practices documented in the …”

The Transportation System shall have the capability to store (TBD)% of the rolling stock inventory.

The Transportation System shall be capable of voice communications with rail consists at all times throughout shipment operations.

Page 27: 1 Application of a Model Based Systems Engineering Method to Manage Project Risk Fred Rojek Booz Allen Hamilton Advanced Risk Management Seminar Applications.

27

System Behavior ModelDevelopment

RequirementsModels

BehavioralModels

PhysicalModels

AssessmentResults

RequirementsAnalysis

FunctionalAnalysis

Design/Synthesis

Assessment

Systems Engineering Process

AND

OA.1Perform

TransportationSystem

Operations

OA.2

Perform WasteAcceptanceOperations

OA.3

Perform DisposalFacility

Operations

C.1

Perform WasteGeneration Site

Activity

C.2Perform

Commercial RailOperations

Center Activity

C.3Perform

Commercial TruckOperations

Center Activity

C.4

Perform RailConsist Activity

C.5

Perform TruckConsist Activity

C.6

Perform CoastGuard Activity

C.7

Perform StateAuthority Activity

AND

Transportation System Functional Context Diagram

Page 28: 1 Application of a Model Based Systems Engineering Method to Manage Project Risk Fred Rojek Booz Allen Hamilton Advanced Risk Management Seminar Applications.

28

AND

OA.1Perform

TransportationSystem

Operations

OA.2

Perform WasteAcceptanceOperations

OA.3

Perform DisposalFacility

Operations

C.1

Perform WasteGeneration Site

Activity

C.2Perform

Commercial RailOperations

Center Activity

C.3Perform

Commercial TruckOperations

Center Activity

C.4

Perform RailConsist Activity

C.5

Perform TruckConsist Activity

C.6

Perform CoastGuard Activity

C.7

Perform StateAuthority Activity

AND

Transportation System Functional Context Diagram

System Behavior ModelDevelopment – Decomposition

RequirementsModels

BehavioralModels

PhysicalModels

AssessmentResults

RequirementsAnalysis

FunctionalAnalysis

Design/Synthesis

Assessment

Systems Engineering Process

Retire System

Continue Operation

Continue Annual Waste Shipment

OA.1.1

DevelopTransportation

System

OA.1.2

ProduceTransportation

System

OA.1.3

DeployTransportation

System

LP OR

AND

OA.1.4Operate &Maintain

TransportationSystem

OA.1.5

SupportTransportation

System

AND

OA.1.7

RetireTransportation

System

LE

OR LP

Perform Transportation System Operations

AND

OA.1.4.3

Assemble &Dispatch Consist

[2.0]

OA.1.4.4

Transport EmptyContainers to Site

[3.0]

OA.1.4.5

Handle & LoadContainers at Site

[4.0]

OA.1.4.6Transport Loaded

Containers toDisposal Facility

[5.0]

OA.1.4.7

Retrieve UnloadedContainers from

Facility [6.0]

OA.1.4.8

Return RollingStock & Aux

Equipment [7.0]

OA.1.4.9ReassembleContainers &Equipment &

Prepare for Next...

OA.1.4.1

PerformCommand &

Control

OA.1.4.2

Perform DailyPlanning &

Management

AND

Operate & Maintain Transportation System

Page 29: 1 Application of a Model Based Systems Engineering Method to Manage Project Risk Fred Rojek Booz Allen Hamilton Advanced Risk Management Seminar Applications.

29

System Behavior ModelDevelopment – Functional I/O

Functional I/O Includes Data, Information, Material

AND

OA.1

PerformTransportation

SystemOperations

OA.2

Perform WasteAcceptanceOperations

OA.3

Perform DisposalFacility

Operations

C.1

Perform WasteGeneration Site

Activity

C.2

PerformCommercial Rail

Operations CenterActivity

C.3

PerformCommercial

Truck OperationsCenter Activity

C.4

Perform RailConsist Activity

C.5

Perform TruckConsist Activity

C.6

Perform CoastGuard Activity

C.7

Perform StateAuthority Activity

AND

Empty Containers

LoadedContainers

DeliveryRequirements

Comm Rail OpsCenter C2 Messa...

Comm Truck OpsCenter C2 Messa...

PreparedContainers

7 Day AdvanceNotification of Sh...

Rail ConsistLocation

Truck ConsistLocation

RequirementsModels

BehavioralModels

PhysicalModels

AssessmentResults

RequirementsAnalysis

FunctionalAnalysis

Design/Synthesis

Assessment

Systems Engineering Process

Page 30: 1 Application of a Model Based Systems Engineering Method to Manage Project Risk Fred Rojek Booz Allen Hamilton Advanced Risk Management Seminar Applications.

30

Physical Model Development

RequirementsModels

BehavioralModels

PhysicalModels

AssessmentResults

RequirementsAnalysis

FunctionalAnalysis

Design/Synthesis

Assessment

Systems Engineering Process

Transportation System Physical Context Diagram

built from built from built from built from built from built from built from built from

Sys

WasteManagement Sy...

System of Syst...

Ex.11

WasteGeneration Sites

External System

Ex.13

Truck Consist

External System

Ex.12

Rail Consist

External System

Ex.14

Comm Truck OpsCenter

External System

Ex.15

Comm Rail OpsCenter

External System

Sys.1

TransportationSystem

System

Sys.2

WasteAcceptance

External System

Sys.3

Disposal Facility

External System

Page 31: 1 Application of a Model Based Systems Engineering Method to Manage Project Risk Fred Rojek Booz Allen Hamilton Advanced Risk Management Seminar Applications.

31

Physical Model Development

Transportation System Physical Hierarchy

RequirementsModels

BehavioralModels

PhysicalModels

AssessmentResults

RequirementsAnalysis

FunctionalAnalysis

Design/Synthesis

Assessment

Systems Engineering Process

built from built from built from built from built from built from

Sys.1

TransportationSystem

System

Sys.1.1

MaintenanceFacility

Subsystem

Sys.1.3

Operation Center

Subsystem

Sys.1.4

Containers

Subsystem

Sys.1.5

Rail Equipment

Subsystem

Sys.1.6

Truck Equipment

Subsystem

Sys.1.12

Other SupportSystems

Subsystem

Page 32: 1 Application of a Model Based Systems Engineering Method to Manage Project Risk Fred Rojek Booz Allen Hamilton Advanced Risk Management Seminar Applications.

32

built from built from built from built from built from built from

performs performs performs performs

Sys.1

TransportationSystem

Component

Sys.1.1

MaintenanceFacility

Component

Sys.1.3

Operation Center

Component

f.1.4.3.1

Communicatewith Rail Consist

Function

f.1.4.3.2

Communicatewith Truck Consist

Function

f.1.4.3.3

Track Rail Consist

Function

f.1.4.3.4

Track Truk Consist

Function

Sys.1.4

Containers

Component

Sys.1.5

Rail Equipment

Component

Sys.1.6

Truck Equipment

Component

Sys.1.12

Other SupportSystems

Component

Functional Allocation

Functions from Behavior Model Allocated to the Operations Center Subsystem

RequirementsModels

BehavioralModels

PhysicalModels

AssessmentResults

RequirementsAnalysis

FunctionalAnalysis

Design/Synthesis

Assessment

Systems Engineering Process

SubsystemSubsystemSubsystemSubsystemSubsystemSubsystem

Page 33: 1 Application of a Model Based Systems Engineering Method to Manage Project Risk Fred Rojek Booz Allen Hamilton Advanced Risk Management Seminar Applications.

33

built from built from built from built from built from built from

performs performs performs performs

based on based on based on based on

Sys.1

TransportationSystem

Component

Sys.1.1

MaintenanceFacility

Component

Sys.1.3

Operation Center

Component

f.1.4.3.1

Communicatewith Rail Consist

Function

TSRDT.4.1

Rail ConsistCommunications

Requirement

f.1.4.3.2

Communicatewith Truck Consist

Function

TSRDT.4.4

Truck ConsistCommunications

Requirement

f.1.4.3.3

Track Rail Consist

Function

TSRD.4.94

Rail ConsistTracking

Requirement

f.1.4.3.4

Track Truk Consist

Function

TSRD.4.135

Truck ConsistTracking

Requirement

Sys.1.4

Containers

Component

Sys.1.5

Rail Equipment

Component

Sys.1.6

Truck Equipment

Component

Sys.1.12

Other SupportSystems

ComponentSubsystemSubsystemSubsystemSubsystemSubsystemSubsystem

Requirements Traceability

RequirementsModels

BehavioralModels

PhysicalModels

AssessmentResults

RequirementsAnalysis

FunctionalAnalysis

Design/Synthesis

Assessment

Systems Engineering Process

Requirements from Requirements Model Trace to Operations Center Functions

Page 34: 1 Application of a Model Based Systems Engineering Method to Manage Project Risk Fred Rojek Booz Allen Hamilton Advanced Risk Management Seminar Applications.

34

Structural Model Development – Interconnection Diagram

Functional I/O Items from Behavior Model Transferred by Interface Links

NRC - CRWMS/Transportation/C3

State Authority - CRWMS/Transportation/C3

DH

S -

CRW

MS/

Tran

spor

tatio

n/C3

Commercial Rail Business Ops -- CRWMS/Transportation/C3

FBI - CRWMS/Transportation/C3

Coast Guard - CRWMS/Transportation/C3

Rail Consist - C2, Comm (Primary) NWS - CRWMS/Transportation/C3

Local Authority - CRWMS/Transportation/C3

Fede

ral A

utho

rity

-CR

WM

S/Tr

ansp

orta

ti...

Truck Consist - C2,Tracking Data (Primary)

Commercial Rail Ops Center -CRWMS/Transportation/C3

Rail Consist - C2, Tracking Data (Primary)

PIO - CRWMS/Transportation/C3

CRWMS/WA - CRWMS/Transportation/C3

Commercial Truck Business Ops -- CRWMS/Transportation/C3

Seciurity Contractor - CRWMS/Transportation/C3

Origin Site - CRWMS/Transportation/C3

CRWMS/MGR - CRWMS/Transportation...

Commercial Truck Ops Center -CRWMS/Transportation/C3

Truck Consist - C2, Comm (Primary)

Transportation Barge - CRWMS/Transportation/C3, Tracking Data

DOE EOC -- CRWMS/Transportation/C3

Trib

al A

utho

ritie

s -

CRW

MS/

Tran

spor

tatio

n/C3

Cask MaintenanceFacility

Node

Command & Control

Node

TransportationOperations Center

Node

Nevada RailInfrastructure

Node

Transportation Casks(Other than TADTransportation

Overpack, AgingOverpack)

Node

Cask Rail Car

Node

Buffer Rail Car

Node

TAD System

Node

Other SupportSystems

Node

Ex.1

Nuclear RegulatoryCommission (NRC)

External

Ex.2

Local Authority

External

Ex.3

State Authority

External

Ex.4

Federal Authority

External

Ex.5

Tribal Authority

External

Ex.6

Department ofHomeland Security

(DHS)

External

Ex.7

Federal Bureau ofInvestigation (FBI)

External

Ex.8

Public InformationOffice (PIO)

External

Ex.9

National WeatherService (NWS)

External

Ex.11

Origin Site (OS)

External

Ex.12.b

Commercial RailBusiness Operations

External

Ex.14.b

Commercial TruckBusiness Operations

External

Ex.16

Transportation Barge

Node

Ex.20

Coast Guard

External

Ex.21

Security Contractor

External

Ex.22

DOE EmergencyOperations Center

External

Op.2

Waste Acceptance

Node

Op.3

Monitored GeologicRepository

Node

Ex.12.a

Commercial RailOperations Center

External

Ex.14.a

Commercial TruckOperations Center

External

Ex.13

Rail Consist

External

Ex.15

Truck Consist

External

Operations Center

RequirementsModels

BehavioralModels

PhysicalModels

AssessmentResults

RequirementsAnalysis

FunctionalAnalysis

Design/Synthesis

Assessment

Systems Engineering Process Model

Page 35: 1 Application of a Model Based Systems Engineering Method to Manage Project Risk Fred Rojek Booz Allen Hamilton Advanced Risk Management Seminar Applications.

35

System Specification

*Document generated by Computerized SE tool (CORE), drawing data from Central Repository

SYSTEM SPECIFICATION

FOR THE

Transportation System

Prepared For:

Prepared By:

1 Scope 1

1.1 Identification.................................................................................................................................1 1.2 System Overview..........................................................................................................................1 1.3 Document Overview .....................................................................................................................1

2 Applicable Documents 2

2.1 Government Documents ...............................................................................................................2 2.2 Non-Government Documents .......................................................................................................2

3 System Requirements 3

3.1 Definition......................................................................................................................................3 3.2 Characteristics...............................................................................................................................5

3.2.1 Performance Characteristics...............................................................................................5 3.2.2 System Capability Relationships........................................................................................5 3.2.3 External Interface Requirements ........................................................................................5 3.2.4 Physical Characteristics .....................................................................................................6 3.2.5 System Quality Factors ......................................................................................................6 3.2.5.1 Reliability........................................................................................................................7 3.2.5.2 Maintainability ................................................................................................................7 3.2.5.3 Availability .....................................................................................................................7 3.2.5.4 Additional Quality Factors ..............................................................................................7 3.2.6 Environmental Conditions .................................................................................................7 3.2.7 Transportability..................................................................................................................8 3.2.8 Flexibility and Expansion ..................................................................................................8 3.2.9 Portability ..........................................................................................................................8

3.3 Design and Construction ...............................................................................................................8 3.3.1 Materials ............................................................................................................................8 3.3.2 Electromagnetic Radiation .................................................................................................8 3.3.3 Nameplates and Product Marking ......................................................................................8 3.3.4 Workmanship.....................................................................................................................8 3.3.5 Interchangeability ..............................................................................................................8 3.3.6 Safety .................................................................................................................................8

3.3.6 Safety .................................................................................................................................8 3.3.7 Human Engineering .........................................................................................................10 3.3.8 Nuclear Control................................................................................................................10 3.3.9 System Security ...............................................................................................................10 3.3.10 Government Furnished Property Usage .........................................................................11 3.3.11 Computer Resource Reserve Capacity ...........................................................................11

3.4 Documentation............................................................................................................................11 3.5 Logistics......................................................................................................................................11 3.6 Personnel and Training ...............................................................................................................12

3.6.1 Personnel..........................................................................................................................13 3.6.2 Training............................................................................................................................13

3.7 Characteristics of Subordinate Elements .....................................................................................13 3.8 Precedence ..................................................................................................................................14 3.9 Qualification ...............................................................................................................................14 3.10 Standard Sample .......................................................................................................................14 3.11 Preproduction Sample, Periodic Production Sample, Pilot, or Pilot Lot ...................................14

4 Quality Assurance Provisions 15

4.1 Responsibility for Inspection ......................................................................................................15 4.2 Special Tests and Examinations ..................................................................................................15 4.3 Requirements Cross Reference ...................................................................................................15

5 Preparation for Delivery 16

6 Notes 17

6.1 Intended Use ...............................................................................................................................17 6.1.1 Missions ...........................................................................................................................17 6.1.2 Threat ...............................................................................................................................17

6.2 Acronyms and Abbreviations......................................................................................................17 6.3 Glossary ......................................................................................................................................17

10 Appendix A - Requirements Traceability Matrix 18

20 Appendix B - Behavior Diagrams 21

RequirementsModels

BehavioralModels

PhysicalModels

AssessmentResults

RequirementsAnalysis

FunctionalAnalysis

Design/Synthesis

Assessment

Systems Engineering Process ModelSystem

PerformanceSpecification

orDevelopmentSpecification

SystemPerformanceSpecification

orDevelopmentSpecification

System Performance Specification Documents Requirements*

Page 36: 1 Application of a Model Based Systems Engineering Method to Manage Project Risk Fred Rojek Booz Allen Hamilton Advanced Risk Management Seminar Applications.

36

Conclusion

Application of a Model Based Systems Engineering methodology can contribute to the implementation of an effective Risk Management program because:

– Models can effectively communicate system requirements and design detail to all disciplines, at all system levels; Simultaneously accessible to all team members (IPTs, special study groups, analysis teams, etc.) (identification)

Executable models allow analysis of system behavior (assessment and analysis)

– Risk documentation products - identified risks, assessment results, mitigation plans etc. – can become an integral part of the system models, maintained in central repository (management)

– Risk documentation products can be automatically generated from tools supporting SE environment drawing model data from central repository (management)

MBSE methodology allows Risk Management to become an integral part of the overall system development effort, throughout all development phases/levels, throughout the system lifecycle (management)

Page 37: 1 Application of a Model Based Systems Engineering Method to Manage Project Risk Fred Rojek Booz Allen Hamilton Advanced Risk Management Seminar Applications.

37

Questions

Page 38: 1 Application of a Model Based Systems Engineering Method to Manage Project Risk Fred Rojek Booz Allen Hamilton Advanced Risk Management Seminar Applications.

38

Backup

Page 39: 1 Application of a Model Based Systems Engineering Method to Manage Project Risk Fred Rojek Booz Allen Hamilton Advanced Risk Management Seminar Applications.

39

Other Model Based Initiatives (you may have heard of)

Model Driven Engineering (MDE)

Model Driven Architecture (MDA)1,2

Model Driven Development (MDD)1,2

Model Based Application Development1

Model Based Programming1

Object Oriented Systems Engineering Method (OOSEM) using SySML1

Rational Unified Process for Systems Engineering (RUP SE)3

1. Object Management Group (OMG) trademarks (http://www.omg.org/legal/tm_list.htm)

2. MDA & MDD are actually implementations of MDE

3. IBM Rational trademark

How do these differ from MBSE?or MBE or MDSD