© Telelogic AB [1] Sandia is a multiprogram laboratory operated by Sandia Corporation, a Lockheed...

1 © Telelogic AB

[1] Sandia is a multiprogram laboratory operated by Sandia Corporation, a Lockheed Martin Company for the

United States Department of Energy’s National Nuclear Security Administration under contract DE-AC04-94AL85000. SAND 2007-6454C

SysML Modeling for a Business Process – Product Realization

Georgia Artery

Mark De Spain

2 © Telelogic AB



Outline

• Background

• Problem Statement

• Approach

• Behavioral Diagrams

• Structure Diagrams

• Benefits

• Conclusions and Next Steps

3 © Telelogic AB



Background

• Large, complex business utilizing legacy product realization process

• Multiple sites/organizations trying to utilize one process

– Many handoffs

– Changing roles and responsibilities

– Various interpretations of process

• NNSA initiative to revitalize technical business practices

• Sandia named as Systems Integration support

4 © Telelogic AB



Problem Statement

• Problem:

– Existing Product Realization Process results in delays, cost overruns due to lack of clear roles and responsibilities, poor execution of program plans, and discipline around deliverables.

• Goal:

– Define a standardized and formal business operating process that maximizes the integration between stakeholders, engineering, and production personnel throughout the product realization process.

– Create phase-gate process based upon Systems Engineering principles

5 © Telelogic AB



Approach

• Process Improvement event to identified inefficiencies in the process tasks and developed a “future state” process

– Included limited design agency and production agency support

• NWC adopted improved process as initial starting point

– Demonstrated concept and usefulness

• Developed functional model (IDEF0) of the process

– Realized the structural piece was missing

– First step to stakeholder buy-in of modeling

• Created SysML model based on functional modeling

6 © Telelogic AB



Project Driver for Requirement

Dev_and_Prod_Manual«block»

*

Tech_Bus_Prac tices«block»

QC_1«block»

Product_Realizat ion_Process_IPG«block»

1

Owner1

NNSAOwner

1

Owner 1

NWC

Owner

1

*

DSW_Procedure«block»

*Owner*

SNL

Creator 1 MOU«block»

Led_to

1

7 © Telelogic AB



Use Case of Top Level Process

Integrated Phase Gate Process

Def ineStakeholder

Requirements

ConceptualDesign Phase

Product andProgram Baseline

Phase

Baseline DesignValidation Phase

ProductionReadiness and

Qualif ication PhaseProduction_Agencies

Design_Lab

NNSA

Final Design andProcess

Development phase

Production_Agencies

Design_Lab

NNSA

Customers

DoD Contractor

8 © Telelogic AB



Stakeholders Identification

Stakeholder

Internal Stakeholder

External Stakeholder

DesignLabs

NNSA

*

1

Design Contractor

Controlling Agency

Production Agencies

*

1

Production Contractor

Controlling Agency

* *

Customers

DoD ContractorNWC

1

1

Supplier

Supplies Needs

Air ForceNavy

1

SNL

1

1

Partner - w arhead

Partner - launch vehicle

Multiple stakeholders and Users of the System

9 © Telelogic AB



Block Relationships of Process

Gate«block»

1..*itsRev iewer

Rev iewer«block»

Phase«block»

statusCorporatePolicyNumber

BeginPhaseMeetsAcceptanceCriteria

1..*itsGate

1itsNextPhase

Tasks«block»

TaskNameTaskStatusCorporatePolicyNumber

PerformT ask

1..*itsTasks

*itsInputDocs

Documents«block»

*itsOutputDocs

*itsDocuments

Engineer«block»

*

myTasksTaskName

*

assignedTeamname

Representation of the key elements of the Model

10 © Telelogic AB



Process Artifacts

Risk_Management_Plan«block»

Requirements_Mngt_Plan«block» Qual_Cert_Plan

«block»Communication_Plan«block»

Configuration_Management_Plan«block»

Stockpi le_Evaluation_Plan«block»

Integration_T est_Plan«block»

Maintenance_Plan«block»

Document«block»

Classification_Guide«block»

Concept_of_Ops«block»

Des ign_Doc«block»

MOE«block»

Surety_Doc«block»

Review«block»

Des ign_Review«block»

Gate_Review«block»

InterAgency_Peer_Review«block»

Program_Review«block»

Theme«block»

Surety«block»

Use_Control«block»

Assessment«block» Manufacturing_Assessment

«block»

Surety_Assessment«block»

Report«block»

Final_Weapon_Dev_Report«block»

Product_Realization_Report«block»

Program_Plan«block»

Product_Plan«block»

Project_Plan«block»

Plan«block»

Product_Doc«block»

Requirements_Doc«block»

System_Design_Doc«block»

Program_Doc«block»

Mission_and_Needs«block»

Program_Direction_Doc«block»

Plan_Review«block»

Product_Review«block»

Technical_Review«block»

Product_Report«block»

Program_Report«block» Technical_Review_Report

«block»

Stage_Closure_Report«block»

Source_Req«block»

11 © Telelogic AB



Use Case for Phase A

DefineStakeholder

Requirements

Initiate s tudyper tasking

letter

«inc lude»

Obtain Cusotmer andStakeholder miss ion

needs, operationsal needsexpectations, and

objectives

«inc lude»

«inc lude»

Define andDocumentProblem

statement

Form Programteams

«inc lude»

Negotiate, provideinput, and Create

Concept ofOperation, and

SourceRequirement docs

«inc lude»

«inc lude»

Develop ProcessPlan for program to

inc lude cost,schedule, and

performance ROM

«inc lude»Review Project

Plan

Stakeholders::External Stakeholders::DOD

«inc lude»

Createschedule &

charter

«inc lude»

Define anddocument boundary

and scope ofsystem and

subsystem, andexternal interfaces

«inc lude»

DefineMeasures of

Effectiveness

Review &prioritize

concept ofoperations with

stakeholders

«inc lude»

Subteams evaluate andscreen candidate

technologies, refinetrade space and option

reqts

«inc lude»

«inc lude»

InitiateProject

ManagementApproach

Use case is taken to the next level which will be expanded into activity diagram

12 © Telelogic AB



Source Requirements

Create_Source_Rqmts«b lock»

Negotiate, provide input, and Create Concept of Operation, and Source Requirement docs

1

NNSA

1

Stakeholder

1Source_Req

«b lock»

1

NWC_Core_Team

1

NWC_Tech_Rev_Team

13 © Telelogic AB



NNSANWC - Core Team

Reviewed:Source_Req

evSrcRq_Validated to itsSource_Req

Evaluate program based on source requirements and technical analysis

tm(DAY)

tm(DAY)

NWC - Technical Review Team

Technically review source requirements

evSrcRq_Reviewed to itsSource_Req

tm(DAY)

Stakeholder

Draft:Source_Req

tm(DAY)

Identify and document source requirements

evSrcRq_Initial to itsSource_Req

Analyze and negotiate source requirements

evSrcRq_Draft to itsSource_Req

tm(2 * DAY)

Requirements_Technical_Support

Import all source documents into Requirements Repository

tm(WEEK)

Initial:Source_Req

Program_Doc:Technical_Review_Report

Validated:Source_Req

Requirement:SrcRq_Review_Criteria

Program_Document:Prog ram_Direction_Doc

tm(DAY)

Program_Report:Stage_Closure_Report

Executable Model

Initial

evSrcRq_Draft

Draft

Undefined

evSrcRq_Initial

evSrcRq_Reviewed

Reviewed

evSrcRq_Validated

Validated

Use Case Activity Diagram drives the state changes in the artifact

14 © Telelogic AB



Benefits• Utilized Systems Engineering approach – used a “process” to develop a “process

– The more precision you have in a process, the better you can institutionalize the process

effectively

• Functional architecture clarified the relationships between tasks and enabled good cohesion

• Understand the relationships of the inputs and outputs to the phase /gates

– Create clarity in tasks and document deliverables (artifacts) needed at each phase

– Prevent unnecessary, non-value added tasks

– Clear understanding of roles and responsibilities

• Balanced the tasks (leveling) and assure they rollup to the right level

• Visual representation of the relationships between tasks and gate outputs in subsequent

phases

• Established connectivity to artifacts and activities – making sure the behaviors are tied to the

structure of the process

• Flow and intent of process is more explicit and understandable when represented graphically

15 © Telelogic AB



Conclusions / Next Steps

Conclusions

• It is critical that you follow format and structure that will enable the model to be executable

– Understanding the fundamental model structure was critical for complex process

• Assuring completeness was key in developing the next level of the model

• Understand the value of static versus dynamic model

Next Steps

• Model is still being tested and will continue to build on the key artifacts and elements in other phases

• Pilot executable on specific elements of the process for upcoming development program

© Telelogic AB [1] Sandia is a multiprogram laboratory operated by Sandia Corporation, a Lockheed...

Documents

Transcript of © Telelogic AB [1] Sandia is a multiprogram laboratory operated by Sandia Corporation, a Lockheed...