System Engineering Process Improvement In Today’s Life Cycle Context

Version 2.2

1

System Engineering Process Improvement

In Today’s Life Cycle Context

Mike Bloom, Joe Duquette

Organization: ESC/EN

Version 2.2

Version 2.2

2

“The only source of knowledge is experience”

A. Einstein

We Need to Leverage Our ProcessExperience and Use It To Succeed

Version 2.2

3

PPurposeurposeDefine the life cycle and life cycle attributes that the

EN CMMI System Engineering Process Improvement Program will apply to and operate in.

The life-cycle for the C2 Product Line is unique and complex

Version 2.2

4

Major ESC Life Cycle ChallengesMajor ESC Life Cycle Challenges

• Acquisition Environment Acquisition Environment

- Shared responsibilities• Enterprise Architecture Enterprise Architecture

- External requirements beyond the product function• Life Cycle and Spiral Life Cycle and Spiral

- Simultaneous life-cycle phases - including O&M• Stakeholders Stakeholders

- Many external stakeholders - continuously involved

Our System Engineering Processes Need to Address These Challenges

Version 2.2

5

•We are spending increasing effort on each We are spending increasing effort on each of our programs responding to daily crises of our programs responding to daily crises and asynchronous initiatives - it is and asynchronous initiatives - it is

consumingconsumingWe need to devote our energy on the programs to

product innovation not process reinvention.

•EN’s CMMI based processes are built to EN’s CMMI based processes are built to meet the Cmeet the C22 product line challenges product line challenges

ESC Life Cycle FocusESC Life Cycle Focus

Version 2.2

6

OverviewContractors

Operations

•Sustainment

Acquisition

ArchitecturesArchitectures

FLOTFLOT

Focus on Red OB

Focus on Blue OB

Neutrals

Life CycleLife CycleBusiness ModelBusiness Model

Systems Acquisition(Engineering and Manufacturing

Development, Demonstration, LRIP &Production)

Concept &Technology

Development

A

System Development& Demonstration

B

Production & Deployment

OT&E

FRPDecisionReview

C

Operations &Support

FOC

Pre - SystemsAcquisition

IOC

Sustainment

BLOCK 2

BLOCK 3

Syst

em L

ife

Cyc

le

Advocacy& Planning

AcquisitionStrategy

PackageDevelopment

MissionIntegration

Operations &Support

Funding&

Direction

ContractAward

DT&EComplete

DepotStart

SystemDisposal

Concept DefinitionDefinition

Acquisition StrategyAcquisition Strategy

Package DevelopmentPackage Development

Mission IntegrationMission Integration

Operations & SupportOperations & Support

Stakeholders Stakeholders RelationshipsRelationships

Syst

em L

ife

Cyc

le

Advocacy& Planning

AcquisitionStrategy

PackageDevelopment

MissionIntegration

Operations &Support

Funding&

Direction

ContractAward

DT&EComplete

DepotStart

SystemDisposal

II IIII

IIIIII IVIV

EnvironmentEnvironment

Version 2.2

7

Contractors

Operations

•Sustainment

Acquisition

Version 2.2

8

Acquisition Operations

Sustainment Contractors

Independent Organizations

FormalFormal

Communications

Communications

Large

Defense Budgets

80s Technology

Business Environment - 1980s

Stovepipe

Systems

Time and Money Permitted Independent Organizational Processes

Version 2.2

9

Contractors

Operations

•Sustainment

Acquisition Smaller

Defense BudgetsIPTs

COTS

Rapid TechnologyChange

Business Environment - TodayInterdependent OrganizationsInterdependent Organizations

System of SystemsIntegration

SharedData and

Responsibilities

Organizational Processes Today Must Provide for Shared Data and Responsibilities

Version 2.2

10

How Do CMMI Based Processes Help With Shared Responsibilities?

• Both industry and government are developing processesunder the same framework

• DoD will most likely encourage process improvement through CMMI - AFMC will be doing likewise

• Process Areas are envisioned to be shared or not shared- depending on the negotiated arrangement between theprogram office and the contractor

Same Language

DoD and Industry Wide

Supports Process Sharing

Version 2.2

11

Engineering

– Requirements Management

– Requirements Development

– Technical Solution

– Enterprise Integration

– Verification

– Validation

Process Management

– Process Focus

– Process Definition

– Training

– Process Performance

– Innovation & Deployment

– Quantitative Management

Project Management

– Project Planning

– Monitoring & Control

– Supplier Agreements

– Integrated Management

– Risk Management

Support

– Configuration Management

– Quality Assurance

– Measurement & Analysis

– Causal Analysis & Resolution

– Decision Analysis & Resolution

E M

S P

CMMI Process Area Categories

Version 2.2

12

Shared ResponsibilitiesRequires Process Sharing

TailoredCMMI

Project ManagementProject Planning (G)Project Monitoring and Control (S)Supplier Agreement Management (G)Integrated Project Management (S)Risk Management (S)

EngineeringRequirements Management (S)Requirements Development (G)Technical Solution (S)Product Integration (S)Product Verification (S)Validation (G)

SupportConfiguration Management (S)Process and Product Quality Assurance (C)Measurement and Analysis (S)Causal Analysis and Resolution (S)Decision Analysis and Resolution (S)

Government (G)[User, SPO, Test]

Contractor (C)

Shared (S)

Acquisition Strategy and / or

Life Cycle Phase

System EngineeringExecution Process

Allocation

Notional Allocation of Process Responsibility

Organizational Process ManagementProcess Focus (S)Process Definition (S)Innovation and Deployment (S)Training (S)Process Performance (S)Quantitative Management (S)

Core GroupInfrastructure

Responsibilities

ConsciousAllocation

Version 2.2

13

Shared Processes Require Shared Data

ProjectEngineering

Viewt

ProjectManagement

Viewt

ProjectSupport

Viewt

UserORD(s)

Viewt

AFOTECTesting

Viewt

SMFunding

Viewt

Shared Data Assures Accurate and TimelyInformation Exchange Among Stakeholders

Shared Data from Shared Processes

EngineeringProcesses

SupportProcesses Management

Processes

Version 2.2

14

FLOTFLOT

Focus on Red OB

Focus on Blue OB

Neutrals

Version 2.2

15

Architecture Is ...Architecture Is ...

•Architecture is a set of tenets used to harmonize designArchitecture is a set of tenets used to harmonize designchoices across multiple disciplines used to solve choices across multiple disciplines used to solve

problems problems in a specified domainin a specified domain

Architecture Imposes Requirements Beyonda Program’s Functional Capabilities

•Architecture is used to manage the complexity of theArchitecture is used to manage the complexity of theinformation system capability in a domaininformation system capability in a domain

•Architecture impacts the individual system by showingArchitecture impacts the individual system by showingthe required relationship to other systems in the domainthe required relationship to other systems in the domainand requiring all systems to adhere to tenets to and requiring all systems to adhere to tenets to

implementimplementthe relationshipthe relationship

Version 2.2

16

Progr

am

Require

men

ts

POM Cycle, Budget Cuts, Management Considerations,

Support Resource Inadequacy,and Political Considerations

Program Constraints

Architectures and Program Constraints Both Constrainand Define the Individual Program Approach

Packages

CONOPS

Technology

Operational Evolution

User Priority

Development Sequencing

Schedule

Risk/Opportunity

Budget

Requirements Baseline

Legacy ArchitectureImplied Legacy

Requirements

PoliticalClimate

Functional Requirements plus ...Functional Requirements plus ...

Enterprise Architecture

ProgramArchitecture

StateTransitions

StateTransitions

SystemEvaluation

SystemEvaluation

System TechForecast

System TechForecast System

RulesSystemRules

System InfoExchange

System InfoExchange

Op Activity-to-

System Func

Op Activity-to-

System Func

System Event/ Trace Desc


SystemFunctionality

SystemFunctionality

SystemPerformance

SystemPerformance

ElementIface

ElementIface

Sys NodeConnectivity


PhysicalData ModelPhysical

Data Model

Systems and interconnectionsproviding for or supportingmilitary operation

“To Be” System

StateTransitions

StateTransitions

SystemEvaluation

SystemEvaluation

System TechForecast


RulesSystemRules

System InfoExchange

System InfoExchange

Op Activity-to-

System Func

Op Activity-to-

System Func



SystemFunctionality

SystemFunctionality

SystemPerformance

SystemPerformance

ElementIface

ElementIface




Data Model


Transition

StateTransitions

StateTransitions

SystemEvaluation

SystemEvaluation

System TechForecast


RulesSystemRules

System InfoExchange

System InfoExchange

Op Activity-to-

System Func

Op Activity-to-

System Func



SystemFunctionality

SystemFunctionality

SystemPerformance

SystemPerformance

ElementIface

ElementIface




Data Model


“As Is” System

StateTransitions

StateTransitions

SystemEvaluation

SystemEvaluation

System TechForecast


RulesSystemRules

System InfoExchange

System InfoExchange

Op Activity-to-

System Func

Op Activity-to-

System Func



SystemFunctionality

SystemFunctionality

SystemPerformance

SystemPerformance

ElementIface

ElementIface




Data Model


“To Be” System

StateTransitions

StateTransitions

SystemEvaluation

SystemEvaluation

System TechForecast


RulesSystemRules

System InfoExchange

System InfoExchange

Op Activity-to-

System Func

Op Activity-to-

System Func



SystemFunctionality

SystemFunctionality

SystemPerformance

SystemPerformance

ElementIface

ElementIface




Data Model


Transition

StateTransitions

StateTransitions

SystemEvaluation

SystemEvaluation

System TechForecast


RulesSystemRules

System InfoExchange

System InfoExchange

Op Activity-to-

System Func

Op Activity-to-

System Func



SystemFunctionality

SystemFunctionality

SystemPerformance

SystemPerformance

ElementIface

ElementIface




Data Model


“As Is” System

StandardsTechnology

Forecast

StandardsTechnology

Forecast

TechnologyArchitecture

Profile


Profile

Minimal set of rules governingthe arrangement, interactionand interdependencies ofsystem parts or elements

“To Be” Technical

StandardsTechnology

Forecast

StandardsTechnology

Forecast


Profile


Profile


Transition

StandardsTechnology

Forecast

StandardsTechnology

Forecast


Profile


Profile


“As Is” TechnicalStandardsTechnology

Forecast

StandardsTechnology

Forecast


Profile


Profile



StandardsTechnology

Forecast

StandardsTechnology

Forecast


Profile


Profile


Transition

StandardsTechnology

Forecast

StandardsTechnology

Forecast


Profile


Profile


“As Is” Technical

“To Be” OperationalOperational tasks, elements andinformation flows required toaccomplish military operation

Op RulesOp RulesOp State

TransitionOp State

Transition

CommandRelationshipsCommand

RelationshipsOpNode

ConnectivityOpNode

Connectivity

Op ConceptOp Concept

Op Event/Trace

Op Event/Trace

Op InfoExchangeOp Info

Exchange

ActivityModel

ActivityModel

LogicalData

Model

LogicalData

Model

TransitionOperational tasks, elements andinformation flows required toaccomplish military operation


TransitionOp State

Transition


RelationshipsOpNode

ConnectivityOpNode

Connectivity


Op Event/Trace

Op Event/Trace


Exchange

ActivityModel

ActivityModel

LogicalData

Model

LogicalData

Model

“As Is” OperationalOperational tasks, elements andinformation flows required toaccomplish military operation


TransitionOp State

Transition


RelationshipsOpNode

ConnectivityOpNode

Connectivity


Op Event/Trace

Op Event/TraceOp Info

ExchangeOp Info

Exchange

ActivityModel

ActivityModel

LogicalData

Model

LogicalData

Model



TransitionOp State

Transition


RelationshipsOpNode

ConnectivityOpNode

Connectivity


Op Event/Trace

Op Event/Trace


Exchange

ActivityModel

ActivityModel

LogicalData

Model

LogicalData

Model



TransitionOp State

Transition


RelationshipsOpNode

ConnectivityOpNode

Connectivity


Op Event/Trace

Op Event/Trace


Exchange

ActivityModel

ActivityModel

LogicalData

Model

LogicalData

Model



TransitionOp State

Transition


RelationshipsOpNode

ConnectivityOpNode

Connectivity


Op Event/Trace

Op Event/Trace


Exchange

ActivityModel

ActivityModel

LogicalData

Model

LogicalData

Model

Version 2.2

17

Decision Analysis and Resolution Requirements Development

SOS Integration & Delivery

Project Planning

Supplier Agreement Management

ProductsOutcome & Feedback

ProductVerification

ValidationMeasurementand Analysis

Deficiencies

Contracting Activity Planning

Requirements DefinitionBudgeting Priority

Assessment & Certification

Integrated ProjectManagement

Project Monitoringand Control

Risk Management

TechnicalSolution

ProductIntegration

RequirementsManagement

ConfigurationManagement

Quality Assurance

Program ManagementTechnical Execution

ProcessFocus

ProcessDefinition Training

QuantitativeMgmt

ProcessPerformance

Innovation andDeployment

Process Maturation

Organizational Process Management

Mission Area Planning

Causal Analysisand Resolution

Product Control

Enterprise IntegrationEnterprise IntegrationMission ShortfallsDirectives,

Standardization, Roadmaps

Constraints,

Processes Need to Address ...Processes Need to Address ...

Enterprise Integration is a “Custom” C2 OverarchingProcess Area Influencing Program Requirements

Version 2.2

18

KeyConcurrent

Up FrontProgramActivities



Project Planning



ProductVerification


Deficiencies






Risk Management

TechnicalSolution

ProductIntegration



Quality Assurance


ProcessFocus


QuantitativeMgmt

ProcessPerformance


Process Maturation




Product Control



Constraints,

CMMI Based Engineering Process ImprovementAddresses Key Concurrent Up Front Activities


Version 2.2

19



Project Planning



ProductVerification


Deficiencies






Risk Management

TechnicalSolution

ProductIntegration



Quality Assurance


ProcessFocus


QuantitativeMgmt

ProcessPerformance


Process Maturation




Product Control



Constraints,


ProjectPlanning

TechnicalSolution

ProductIntegration

Validation




SoS Integrationand Delivery

Risk Management


Enterprise Integration

Architecture Impact On Our CMMI Based Engineering Process Improvement


Version 2.2

20



Project Planning



ProductVerification


Deficiencies






Risk Management

TechnicalSolution

ProductIntegration



Quality Assurance


ProcessFocus


QuantitativeMgmt

ProcessPerformance


Process Maturation




Product Control



Constraints,

Requirements Development

ProjectPlanning


Risk Management

Enterprise Integration

Chief Engineer Key Process Areas Include CMMI Based Engineering Process Improvement


Version 2.2

21

CMMI Fits Our NeedsCMMI Fits Our Needs• ESC “Custom” Process Area for Enterprise Integration

• CMMI explicitly addresses key up front project processes

• CMMI accommodates Architecture impacts on the process implementation at ESC

• CMMI provides for key processes for ESC/EN execution of Chief Engineer function to include:

– Requirements Development and Management

– Risk Management

– Enterprise Integration

– Project Planning

CMMI

Version 2.2

22




Concept &Technology

Development

A


B


OT&E

FRPDecisionReview

C

Operations &Support

FOC


IOC

Sustainment

BLOCK 2

BLOCK 3

Sys

tem

Lif

e C

ycle

Advocacy& Planning

AcquisitionStrategy

PackageDevelopment

MissionIntegration

Operations &Support

Funding&

Direction

ContractAward

DT&EComplete

DepotStart

SystemDisposal






Version 2.2

23



Concept &Technology

Development

A


B


OT&E

FRPDecisionReview

C

Operations &Support

FOC


IOC

Sustainment

BLOCK 2

BLOCK 3

Sys

tem

Lif

e C

ycle

Advocacy& Planning

AcquisitionStrategy

PackageDevelopment

MissionIntegration

Operations &Support

Funding&

Direction

ContractAward

DT&EComplete

DepotStart

SystemDisposal

Program Life CycleProgram Life Cycle

Version 2.2

24

Program Life CycleProgram Life Cycle



Concept &Technology

Development

A


B


OT&E

FRPDecisionReview

C

Operations &Support

FOC


IOC

Sustainment

BLOCK 2

BLOCK 3

Sys

tem

Lif

e C

ycle

Advocacy& Planning

AcquisitionStrategy

PackageDevelopment

MissionIntegration

Operations &Support

Funding&

Direction

ContractAward

DT&EComplete

DepotStart

SystemDisposal






Version 2.2

25

In the CIn the C22 World World

Concept DefinitionDefinition • Ops ArchitectureOps Architecture• User RequirementsUser Requirements• Investment FundingInvestment Funding

• ExperimentationExperimentation• ATDs & ACTDsATDs & ACTDs• Transition DecisionsTransition Decisions

Experiment onNext Generation

Sustain theLegacy System(s)

In anyProgramAll FourPhasesCan Be

RunningConcurrently

Package DevelopmentPackage DevelopmentAcquisition Strategy andAcquisition Strategy and

• System ArchitectureSystem Architecture• Product RequirementsProduct Requirements• Technology ChangeTechnology Change• Design & TestDesign & Test

• Define, Design,Define, Design, and Test Newand Test New CapabilitiesCapabilities• FieldingFielding DecisionsDecisions


• Tech ArchitectureTech Architecture• InteroperabilityInteroperability• InfrastructureInfrastructure• CertificationCertification

• Previous VersionsPrevious Versions• Other SystemsOther Systems• Ops EnvironmentOps Environment• Shortfall FixesShortfall Fixes

Operations & SupportOperations & Support• “ “As Is” ArchitecturesAs Is” Architectures• Operational ChangesOperational Changes• User FeedbackUser Feedback• Operations BudgetingOperations Budgeting

• System EmploymentSystem Employment• Parallel OperationsParallel Operations• User FeedbackUser Feedback• Plug and PlayPlug and Play• Mission Shortfall FixesMission Shortfall Fixes

Life Cycle Detail

Version 2.2

26



Concept &Technology

Development

A


B


OT&E

FRPDecisionReview

C

Operations &Support

FOC


IOC

Sustainment

BLOCK 2

BLOCK 3

Sys

tem

Lif

e C

ycle

Advocacy& Planning

AcquisitionStrategy

PackageDevelopment

MissionIntegration

Operations &Support

Funding&

Direction

ContractAward

DT&EComplete

DepotStart

SystemDisposal






Program Life Cycle - Multiple Types of SpiralsProgram Life Cycle - Multiple Types of Spirals

ATDExperiment

ACTD

ProgramDirectionChange

NewContractAction

Functional orPerformance

BaselineChange

Beta orDevelopment

OnlyCOTS

ProductIntegration

Plug & Playor Bug Fix

Version 2.2

27

Spiral N+1

User Priority

Legacy Architecture


Risk/Opportunity

Technology Schedule



PoliticalClimate

Budget

CONOPS

Implied Legacy Requirements

Individual Spiral ConsiderationsIndividual Spiral Considerations

Engineering Processes Must Accommodate A Complex Set of Variables

Version 2.2

28

System Engineering Processes Need to HaveEnterprise Focus and Life Cycle Applicability

Transitionto

Development?

Stop

ConceptDefinition

Concept Planning

Budgeting Priority

ConceptDefinition

Contracting

Activity Execution

Assessment

ExperimentPlanning

IntegrationOnly

?

Yes

Yes

No

No

No

Try Again?

Yes Plug &Play

?

Traditional System Engineering Focus

Yes

MissionIntegration

Enterprise Planning

Budgeting Priority

Contracting

Production/DeployIntegration Execution


Shortfalls?

Operations

SoS Requirementsand Ops Architecture

VersionPlanning

InfrastructureMod

Application Mod

Stop

Operations &Support

O&S Planning

MaintFix

Budgeting Priority

Mod Requirements Definition

Contracting

Mod Development Execution


Mod Deployment Planning

Deployment

Operations

Shortfalls?

Yes Stop

Yes

Acquisition & Development

DevelopmentPlanning

FieldingDecision

Budgeting Priority

Requirements Definition

Contracting

Development Execution


Package Planning

AnotherSpiral

Stop

A Program’s Engineering Scope A Program’s Engineering Scope

Version 2.2

29

Transitionto

Development?

Stop

ConceptDefinition

Concept Planning

Budgeting Priority

ConceptDefinition

Contracting

Activity Execution

Assessment

ExperimentPlanning

IntegrationOnly

?

Yes

Yes

No

No

No

Try Again?

Yes Plug &Play

?

Yes

MissionIntegration

Enterprise Planning

Budgeting Priority

Contracting



Shortfalls?

Operations


VersionPlanning

InfrastructureMod

Application Mod

Stop

Operations &Support

O&S Planning

MaintFix

Budgeting Priority


Contracting




Deployment

Operations

Shortfalls?

Yes Stop

Yes


DevelopmentPlanning

FieldingDecision

Budgeting Priority


Contracting



Package Planning

AnotherSpiral

Stop

Initial Processes Cut Across Initial Processes Cut Across The Life CycleThe Life Cycle

Version 2.2

30

Transitionto

Development?

Stop

ConceptDefinition

Concept Planning

Budgeting Priority

ConceptDefinition

Contracting

Activity Execution

Assessment

ExperimentPlanning

IntegrationOnly

?

Yes

Yes

No

No

No

Try Again?

Yes Plug &Play

?

Yes

MissionIntegration

Enterprise Planning

Budgeting Priority

Contracting



Shortfalls?

Operations


VersionPlanning

InfrastructureMod

Application Mod

Stop

Operations &Support

O&S Planning

MaintFix

Budgeting Priority


Contracting




Deployment

Operations

Shortfalls?

Yes Stop

Yes


DevelopmentPlanning

FieldingDecision

Budgeting Priority


Contracting



Package Planning

AnotherSpiral

Stop

Initial Processes Cut Across Initial Processes Cut Across The Life CycleThe Life Cycle

Version 2.2

31



Project Planning



ProductVerification


Deficiencies






Risk Management

TechnicalSolution

ProductIntegration



Quality Assurance


ProcessFocus


QuantitativeMgmt

ProcessPerformance


Process Maturation




Product Control



Constraints,

Continuous Life Cycle Process Continuous Life Cycle Process

Spiral DevelopmentIs the Cyclic Application of a Set

of Standard Engineering ProcessesOver the Entire Life Cycle

Until System Disposal

Version 2.2

32


Sys

tem

Lif

e C

ycle

Advocacy& Planning

AcquisitionStrategy

PackageDevelopment

MissionIntegration

Operations &Support

Funding&

Direction

ContractAward

DT&EComplete

DepotStart

SystemDisposal

Version 2.2

33

Contractors

• Fewer and Bigger• ID/IQ Contracts• Fewer New Starts• Out-sourced Work• View CMMI as Imperative

Operations

• Smaller Force• Coalition Operations• Interoperable Systems• Increased OPSTEMPO• Changing Missions• Changing Threats• CONUS Based• Global Commitments

•Sustainment

• Lean Logistics • Experience Drain • Technology Pace • Outsourced Work• COTS vs MILSPEC• Smaller Workforce• Just-In-Time Supply • Contractor Logistics Support• Increased “Command Support”

Stakeholder Considerations Stakeholder Considerations in Today’s Environmentin Today’s Environment

Acquisition

• System of System Demands • Spiral Development & EA• Constant Initiative Flow• Increased ACQTEMPO• Outsourced Workforce• Lifecycle Management • Impatient Customers• Acquisition Reform• “TSPR” Contracts• Experience Drain• Smaller SPOs Partnering

& SharedProcesses

2000’s2000’sInterdependentInterdependentOrganizationsOrganizations

Version 2.2

34

Must be involved

Certification Congress Contractor Customer Deployment DOD Policy Acquisition Agency Experimentation Industry Legal / Contracting Service HQ & JCS Safety Sustainment Test Training User

May be involved

Concept &Technology

Development

A


B


FRPDecision

CIOC

Support

FOCB

Production &

C

Stakeholders

Spiral Development Involves the Same Set of Stakeholders in the Conduct of Standard

Engineering Processes Over the Entire Life CycleUntil System Disposal

Concept &Technology

Development

A


B


OT&E

FRPDecisionReview

C

Operations &Support

FOCIOC

Pre-Award Post-Award

Version 2.2

35

TailoredCMMI

Project ManagementProject Planning (G)Project Monitoring and Control (S)Supplier Agreement Management (G)Integrated Project Management (S)Risk Management (S)

EngineeringRequirements Management (S)Requirements Development (G)Technical Solution (S)Product Integration (S)Product Verification (S)Validation (G)

SupportConfiguration Management (S)Process and Product Quality Assurance (C)Measurement and Analysis (S)Causal Analysis and Resolution (S)Decision Analysis and Resolution (S)

Government (G)[User, SPO, Test]

Contractor (C)

Shared (S)

Acquisition Strategy and / or

Life Cycle Phase

System EngineeringExecution Process

Allocation

Notional* Allocation of Process Responsibility

Organizational Process ManagementProcess Focus (S)Process Definition (S)Innovation and Deployment (S)Training (S)Process Performance (S)Quantitative Management (S)

Core GroupInfrastructure

Responsibilities

ConsciousAllocation

* Can be changed depending on business model or acquisition strategy

Shared ResponsibilitiesRequires Sharing Process

Version 2.2

36

Transitionto

Development?

Stop

ConceptDefinition

Concept Planning

Budgeting Priority

ConceptDefinition

Contracting

Activity Execution

Assessment

ExperimentPlanning

IntegrationOnly

?

Yes

Yes

No

No

No

Try Again?

Yes Plug &Play

?

Yes

MissionIntegration

Enterprise Planning

Budgeting Priority

Contracting



Shortfalls?

Operations


VersionPlanning

InfrastructureMod

Application Mod

Stop

Operations &Support

O&S Planning

MaintFix

Budgeting Priority


Contracting




Deployment

Operations

Shortfalls?

Yes Stop

Yes


DevelopmentPlanning

FieldingDecision

Budgeting Priority


Contracting



Package Planning

AnotherSpiral

Stop

Stakeholders Cut Across Stakeholders Cut Across The Life CycleThe Life Cycle

Congress Customer DOD Policy Acquisition Agency Experimentation Service HQ & JCS Safety User

Certification Congress Contractor Customer Deployment DOD Policy Experimentation Acquisition Agency Industry Legal/Contracting Service HQ & JCS Safety Sustainment Test Training User

Certification Contractor Deployment Experimentation Acquisition Agency Industry Service HQ & JCS Safety Sustainment Test Training User

Customer Contractor Acquisition Agency Experimentation Industry Legal/Contracting Safety Sustainment Test Training User

Version 2.2

37

Transitionto

Development?

Stop

ConceptDefinition

Concept Planning

Budgeting Priority

ConceptDefinition

Contracting

Activity Execution

Assessment

ExperimentPlanning

IntegrationOnly

?

Yes

Yes

No

No

No

Try Again?

Yes Plug &Play

?

Yes

MissionIntegration

Enterprise Planning

Budgeting Priority

Contracting



Shortfalls?

Operations


VersionPlanning

InfrastructureMod

Application Mod

Stop

Operations &Support

O&S Planning

MaintFix

Budgeting Priority


Contracting




Deployment

Operations

Shortfalls?

Yes Stop

Yes


DevelopmentPlanning

FieldingDecision

Budgeting Priority


Contracting



Package Planning

AnotherSpiral

Stop

Stakeholders Cut Across Stakeholders Cut Across The Life CycleThe Life Cycle

Congress Customer DOD Policy Acquisition Agency Experimentation Service HQ & JCS Safety User

Congress Contractor Customer Deployment DOD Policy Experimentation Acquisition Agency Industry Legal/Contracting Service HQ & JCS Safety Sustainment Test Training User

Certification Contractor Deployment Experimentation Acquisition Agency Industry Service HQ & JCS Safety Sustainment Test Training User

Contractor Acquisition Agency Experimentation Industry Legal/Contracting Safety Sustainment Test Training User

Version 2.2

38

ConclusionContractors

Operations

•Sustainment

Acquisition


FLOTFLOT

Focus on Red OB

Focus on Blue OB

Neutrals




Concept &Technology

Development

A


B


OT&E

FRPDecisionReview

C

Operations &Support

FOC


IOC

Sustainment

BLOCK 2

BLOCK 3

Syst

em L

ife

Cyc

le

Advocacy& Planning

AcquisitionStrategy

PackageDevelopment

MissionIntegration

Operations &Support

Funding&

Direction

ContractAward

DT&EComplete

DepotStart

SystemDisposal







Syst

em L

ife

Cyc

le

Advocacy& Planning

AcquisitionStrategy

PackageDevelopment

MissionIntegration

Operations &Support

Funding&

Direction

ContractAward

DT&EComplete

DepotStart

SystemDisposal

II IIII

IIIIII IVIV


Version 2.2

39

Conclusion Conclusion Acquisition EnvironmentAcquisition Environment

Contractors

Operations

•Sustainment

Acquisition


• Acquisition Environment ChallengeAcquisition Environment Challenge- Interdependent Organizations- Shared Responsibilities- Shared Data- Organizational Processes Today Must Provide for Shared Data and Responsibilities

• How Does CMMI HelpHow Does CMMI Help- Provides a Common Language- Developed by Both DoD and Industry- Used by Both DoD and Industry- Supports Process Sharing

EN CMMI-Based Processes Facilitate Shared Responsibilities

Version 2.2

40


FLOTFLOT

Focus on Red OB

Focus on Blue OB

Neutrals

Conclusion Conclusion Enterprise ArchitectureEnterprise Architecture

• Enterprise Architecture ChallengeEnterprise Architecture Challenge- Architecture Imposes Requirements Beyond a Program’s Functional Capabilities- Architectures Constrain and Define the Individual Program Approach- Need “Custom” C2 Enterprise Integration Process

• How Does CMMI HelpHow Does CMMI Help- Provides for ESC “Custom” Process Area for Enterprise Integration- Explicitly Addresses Key up Front Project Processes- Accommodates Architecture Impacts on ESC Process Implementation- Provides for Key Processes for ESC/EN Execution of Chief Engineer Function

EN CMMI-Based Processes Accommodates Requirements Beyond the Product Function

Version 2.2

41




Concept &Technology

Development

A


B


OT&E

FRPDecisionReview

C

Operations &Support

FOC


IOC

Sustainment

BLOCK 2

BLOCK 3

Syst

em L

ife

Cyc

le

Advocacy& Planning

AcquisitionStrategy

PackageDevelopment

MissionIntegration

Operations &Support

Funding&

Direction

ContractAward

DT&EComplete

DepotStart

SystemDisposal






Conclusion Conclusion Life Cycle and SpiralLife Cycle and Spiral

• Life Cycle and Spiral ChallengeLife Cycle and Spiral Challenge- Ability to Accommodate All Four Life Cycle Phases Running Concurrently- Accommodate A Complex Set of Variables- System Engineering Processes Need Enterprise Focus and Life Cycle Applicability

• How Does CMMI HelpHow Does CMMI Help-Provides for a Cyclic Application of a Set of Standard Engineering Processes Over the Entire Life Cycle Until System Disposal

EN CMMI-Based Processes Provide For Simultaneous Life-Cycle Phases - Including O&M

Version 2.2

42


Syst

em L

ife

Cyc

le

Advocacy& Planning

AcquisitionStrategy

PackageDevelopment

MissionIntegration

Operations &Support

Funding&

Direction

ContractAward

DT&EComplete

DepotStart

SystemDisposal

Conclusion Conclusion StakeholdersStakeholders

• Life Cycle and Spiral ChallengeLife Cycle and Spiral Challenge- Interdependent Organizations Require Shared Responsibilities- Shared Responsibilities Require Shared Processes- Shared Processes Require Maximum Stakeholder Involvement

• How Does CMMI HelpHow Does CMMI Help- Provides Common Processes That Incorporate The Stakeholders Across the Life Cycle and Insures That The Appropriate Stakeholders Are Involved As Appropriate As the Program Spirals

EN CMMI-Based Processes Provide For The Many External Stakeholders and Continuous Involvement

Version 2.2

43

Major ESC Life Cycle ChallengesMajor ESC Life Cycle Challenges

• Acquisition Environment Acquisition Environment

- Shared responsibilities• Enterprise Architecture Enterprise Architecture

- External requirements beyond the product function• Life Cycle and Spiral Life Cycle and Spiral

- Simultaneous life-cycle phases - including O&M• Stakeholders Stakeholders

- Many external stakeholders - continuously involved

EN CMMI-Based Processes Address These Challenges

Version 2.2

44

“Not everything that can be counted counts, and not everything that counts can be counted”

A. Einstein

Like Today’s Life Cycle Context

Version 2.2

45

CMMIProcessAreas

Version 2.2

46

CMMI Based Process ImprovementProcess Life Cycle Context Engineering Process Area

(Part 1of 2)

Version 2.2

47

This Process Area … Contains Practices to …Enterprise Integration Ensure that activities needed to integrate an enterprise

release with its previous releases, new systemcomponents, and other external systems are planned andcoordinated with the necessary stakeholders. Activitiesinclude: define the enterprise and its system components;maintain configuration control of the enterprise; developenterprise release roadmaps; define operational andtechnical architectures; establish an integration strategyand environment; transition legacy systems; maintainconsistency among enterprise interface control and/orinteroperability requirements, certification requirements,evolving standards and infrastructure; integrate and testthe system components; and install enterprise releases inthe operational environment. The result is a package thatintegrates the enterprise release seamlessly into theintended operational environment.

Verification Plan and perform Development Test & Evaluation(DT&E) activities. Track deficiencies and their retest.

Validation Plan for and participate in Operational Test & Evaluation(OT&E) and certification testing. Analyze results andfollow-through on corrective actions.

CMMI Based Process ImprovementProcess Life Cycle Context Engineering Process Area

(Part 2of 2)

Version 2.2

48

CMMI Based Process ImprovementProcess Life Cycle Context

Project Management Process Area (Part 1of 2)

Version 2.2

49


Project Management Process Area (Part 2of 2)

Version 2.2

50


Support Process Area

Version 2.2

51


Process Management Process Area

Version 2.2

52

RequirementProducts

Life CyclePhase

Expansions

Version 2.2

53

StandardsTechnology

Forecast

StandardsTechnology

Forecast


Profile


Profile


Technical

StateTransitions

StateTransitions

SystemEvaluation

SystemEvaluation

System TechForecast

System TechForecast

SystemRules

SystemRules

System InfoExchange

System InfoExchange

Op Activity-to-

System Func

Op Activity-to-

System Func



SystemFunctionality

SystemFunctionality

SystemPerformance

SystemPerformance

ElementIface

ElementIface



PhysicalData Model

PhysicalData Model


System

OperationalOperational tasks, elements andinformation flows required toaccomplish military operation

Op RulesOp Rules

Op StateTransition

Op StateTransition

CommandRelationships


OpNodeConnectivity

OpNodeConnectivity


Op Event/Trace

Op Event/Trace

Op InfoExchange

Op InfoExchange

ActivityModel

ActivityModel

LogicalData

Model

LogicalData

Model

Concept Definition Transition Baseline Planning and Control

CMMI Process Life Cycle ContextAn Enterprise Spiral Development Model

Operational Baseline Planning and Control

Operational Baseline

Operations & Support

Operational

Shortfall

Mission Integration Level

Enterprise

Shortfall

Integrate and Field Enterprise Increment 1

Integrate and Field Enterprise Increment 2

Component System Baseline Planning and Control

Enterprise and Infrastructure Baseline Planning and Control

COTS/Technology Insertion

User Requirements Definition

Process Reengineering

CONOPS

Subsequent Spiral

NoIntegration

Only?

Stop

YesConcept Definition

Level

Planning and Experimentation

Transitionto

Development?

Yes

No

No

Plug &Play

?

Yes

NoExperimentation

Try Again ?

Yes

Yes

Development Increment 3

Transition? No

Beta Testor

Defer FieldingAcquisition & Development Level

Program Office



All 4 Levels Exist Simultaneously

Version 2.2

54

S y s t e m s A c q u i s i t i o n( E n g i n e e r i n g a n d M a n u f a c t u r i n g

D e v e l o p m e n t , D e m o n s t r a t i o n , L R I P &P r o d u c t i o n )

Sys

tem

Lif

e C

ycle

A d v o c a c y& P l a n n i n g

A c q u i s i t i o nS t r a t e g y

P a c k a g eD e v e l o p m e n t

M i s s i o nI n t e g r a t i o n

O p e r a t i o n s &S u p p o r t

F u n d i n g&

D i r e c t i o n

C o n t r a c tA w a r d

D T & EC o m p l e t e

D e p o tS t a r t

C o n c e p t &T e c h n o l o g y

D e v e l o p m e n t

A

S y s t e m D e v e l o p m e n t& D e m o n s t r a t i o n

B

P r o d u c t i o n & D e p l o y m e n t

O T & E

F R PD e c i s i o nR e v i e w

C


F O C

P r e - S y s t e m sA c q u i s i t i o n

S u s t a i n m e n t

S y s t e mD i s p o s a l

I O C

B L O C K 2

B L O C K 3

CMMI Process Life Cycle ContextProgram Life Cycle

Concept DefinitionConcept Definition

Vision & GoalsJV 2020JV 2020

ExperimentationEFX, ATD, ACTD

Spiral Feedback

Threat ChangeSTARSTAR

Mission ShiftEAFEAF

Existing Direction

ORD

Process Modeling

CapstoneArchitecture

Shortfalls &Opportunities

PPBS

Budgeting & Tradeoffs

Requirement Feasibility

User RequirementsDefinition

Program DirectionProgram DirectionProgram DirectionProgram Direction

Mission AreaPlanning

Operational &Technical

Architecture(s)

Program Planning IPT

Version 2.2

55



Sys

tem

Lif

e C

ycle






F u n d i n g&

D i r e c t i o n



D e p o tS t a r t



A


B


O T & E


C


F O C




I O C

B L O C K 2

B L O C K 3


Form Program Office

SRD/TRDDevelopment (1)

RequirementsFeasibility

PMDAPB

M e d ica l

B u s in e ss A pp lica tio n s

G lo b a l C o m b a t

S u p p o rt S ys tem (G C S S )

S o ftw a re D is trib u tio nfro m C e n tra l F ile s

W e b S e rv ices

M e g a cen te r S e rv ice s

E le c tro n ic M a il D e live ry

S A T C O M

C o m m erc ia l F ib e r

M S S

R F N e ts

T e le p o rts

W ire le ssC o m m

D octrin eP o licy

E n gin eerin g

S tan d ard sA rch itectu res

S p ectru m

G overn an ce

D IS N

M e d ica l



S u p p o rt S ys tem (G C S S )


W e b S e rv ices



S A T C O M


M S S

R F N e ts

T e le p o rts

W ire le ssC o m m

D octrin eP o licy

E n gin eerin g


S p ectru m

G overn an ce

D IS N

Ops & TechArchitectures

UserRequirements

Funding

Acquisition StrategyAcquisition StrategyM e d ica l



S u p p ort S ys tem (G C S S )


W e b S e rv ices



S A T C O M


M S S

R F N e ts

T e le p o rts

W ire le ssC o m m

D octrin eP o licy

E n gin eerin g


S p ectru m

G overn an ce

D IS N

ArchitectureCapstone

RFPPreparation (2)

Acquisition StrategyDevelopment

ASP

Source Selection

ContractContractAwardAward


Version 2.2

56



Sys

tem

Lif

e C

ycle






F u n d i n g&

D i r e c t i o n



D e p o tS t a r t



A


B


O T & E


C


F O C




I O C

B L O C K 2

B L O C K 3




Post AwardConference

SystemArchitectureDevelopment

Define Post Award Work Packages and IPTs

Form Working Level

IPT


Product Integration

DT&E

Partial

Full

Back toDevelopment Test

Ready?

TestTestArticlesArticlesTestTest

ArticlesArticles

ProductionReadiness

Package Design & Development

Package Design & DevelopmentPackage Design & Development ProductIntegration

RequirementsRefinement

Package Consensusand Contract Action

Spiral “n”Design

Package Tradeoffand Decision

Spiral “n”Development

Version 2.2

57



Sys

tem

Lif

e C

ycle






F u n d i n g&

D i r e c t i o n



D e p o tS t a r t



A


B


O T & E


C


F O C




I O C

B L O C K 2

B L O C K 3



Form Test & Integration

Working Group

TestTestArticlesArticlesTestTest

ArticlesArticles

Establish TestEnvironments

Certification andAccreditation

OT&E

ProductionDecision

Back toDevelopment

No

OT&ESystem Fixes

Yes

Conduct Training, Connectivity,Installation, Deployment

InfrastructureReadiness

DepotDepotStartStart


Finalize ProductionReadiness

IOC

Version 2.2

58



Sys

tem

Lif

e C

ycle






F u n d i n g&

D i r e c t i o n



D e p o tS t a r t



A


B


O T & E


C


F O C




I O C

B L O C K 2

B L O C K 3


Form UserGroup

Phase Out & DisposalPhase Out & DisposalPhase Out & DisposalPhase Out & Disposal

BeginOperations

BeginSustainment

Operateand

Maintain


Spiral N+1 (e.g. TCTOs, Reprocurement, Modifications, SLEP Engineering, Mission Shift)

O&M Planning



Version 2.2

59

EnterpriseArchitectureExpansions

Version 2.2

60

Enterprise ArchitectureEnterprise Architecture

• Enterprise Architecture is an Information Technology Approach Enterprise Architecture is an Information Technology Approach

- Our business is a mixture of IT and Weapons Systems

• Enterprise Architecture Addresses Systems of Systems Complexity Enterprise Architecture Addresses Systems of Systems Complexity

- A common approach for IT and Weapons Systems

• Enterprise Architecture Models Describe Operational Behavior Enterprise Architecture Models Describe Operational Behavior

- System of Systems “Business Models”

• Transition Plans from “As Is” to “To Be” for Enterprise Planning Transition Plans from “As Is” to “To Be” for Enterprise Planning

- Powerful enterprise investment planning & management tool

Enterprise Architecture is the Key to Enterprise Integration

• Enterprise Architecture Models Describe Required Interfaces Enterprise Architecture Models Describe Required Interfaces

- Permits standardization required for interoperability

Version 2.2

61

Tech Sys

Ops

Transition

TechSys

Ops

Target

Architecture CycleArchitecture Cycle

TechSys

Ops

Oversightand

Control

Baseline

Version 2.2

62

OperationalSy

stem

s Technical



TransitionOp State

Transition


RelationshipsOpNode

ConnectivityOpNode

Connectivity


Op Event/Trace

Op Event/Trace


Exchange

ActivityModel

ActivityModel

LogicalData

Model

LogicalData

Model

StateTransitions

StateTransitions

SystemEvaluation

SystemEvaluation

System TechForecast

System TechForecast

SystemRules

SystemRules

System InfoExchange

System InfoExchange

Op Activity-to-

System Func

Op Activity-to-

System Func



SystemFunctionality

SystemFunctionality

SystemPerformance

SystemPerformance

ElementIface

ElementIface

Sys NodeConnectivitySys Node

Connectivity


Data Model

Systems and interconnectionsproviding for or supporting

military operation

“To Be” System

StandardsTechnology

Forecast

StandardsTechnology

Forecast


Profile


Profile



StateTransitions

StateTransitions

SystemEvaluation

SystemEvaluation

System TechForecast

System TechForecast

SystemRules

SystemRules

System InfoExchange

System InfoExchange

Op Activity-to-

System Func

Op Activity-to-

System Func



SystemFunctionality

SystemFunctionality

SystemPerformance

SystemPerformance

ElementIface

ElementIface


Connectivity


Data Model


military operation

Transition

StateTransitions

StateTransitions

SystemEvaluation

SystemEvaluation

System TechForecast

System TechForecast

SystemRules

SystemRules

System InfoExchange

System InfoExchange

Op Activity-to-

System Func

Op Activity-to-

System Func



SystemFunctionality

SystemFunctionality

SystemPerformance

SystemPerformance

ElementIface

ElementIface


Connectivity


Data Model


military operation

“As Is” System



TransitionOp State

Transition


RelationshipsOpNode

ConnectivityOpNode

Connectivity


Op Event/Trace

Op Event/Trace


Exchange

ActivityModel

ActivityModel

LogicalData

Model

LogicalData

Model



TransitionOp State

Transition


RelationshipsOpNode

ConnectivityOpNode

Connectivity


Op Event/Trace

Op Event/Trace


Exchange

ActivityModel

ActivityModel

LogicalData

Model

LogicalData

Model

StandardsTechnology

Forecast

StandardsTechnology

Forecast


Profile


Profile


Transition

StandardsTechnology

Forecast

StandardsTechnology

Forecast


Profile


Profile


“As Is” Technical

TechSys

Ops

Tech Sys

Ops

TechSys

Ops

“As Is”

EnterpriseProgram

OfficeTransition

“To Be”

TechSys

Ops

Tech Sys

Ops

TechSys

Ops

“As Is”

SystemProgram

OfficeTransition

“To Be”

TechSys

Ops

Tech Sys

Ops

TechSys

Ops

“As Is”

SystemProgram

OfficeTransition

“To Be”

TechSys

Ops

Tech Sys

Ops

TechSys

Ops

“As Is”

SystemProgram

OfficeTransition

“To Be”

Version 2.2

63

OperationalOperational tasks, elements andinformation flows required toaccomplish military operation

Op RulesOp Rules

Op StateTransition

Op StateTransition



OpNodeConnectivity

OpNodeConnectivity


Op Event/Trace

Op Event/Trace

Op InfoExchange

Op InfoExchange

ActivityModel

ActivityModel

LogicalData

Model

LogicalData

Model

StateTransitions

StateTransitions

SystemEvaluation

SystemEvaluation

System TechForecast

System TechForecast

SystemRules

SystemRules

System InfoExchange

System InfoExchange

Op Activity-to-

System Func

Op Activity-to-

System Func



SystemFunctionality

SystemFunctionality

SystemPerformance

SystemPerformance

ElementIface

ElementIface



PhysicalData Model

PhysicalData Model


System

StandardsTechnology

Forecast

StandardsTechnology

Forecast


Profile


Profile


Technical

Program Space

POM Cycle, Budget Cuts, Management Considerations,

Support Resource Inadequacy,and Political Considerations

Program Constraints

Req

uire

men

ts

Req

uire

men

tsPackages

CONOPS

Technology


User Priority


Schedule

Risk/Opportunity

Budget


Legacy ArchitectureImplied Legacy

Requirements

PoliticalClimate

Architectures and Program Constraints Both Constrainand Define the Individual Program Approach

TechSys

Ops

Tech Sys

Ops

TechSys

Ops

Baseline

Oversightand

ControlTransition

Target

Version 2.2

64

TechSys

Ops

Tech Sys

Ops

TechSys

Ops

Baseline

Oversightand

Control Transition

Target

A Notional Enterprise Architecture ProcessA Notional Enterprise Architecture Process

Develop / Revise Transition Plan

Develop / Revise Target Enterprise Architecture

Develop / ReviseBaseline Enterprise

Architecture

Define /Revise

ArchitectureProcess &Approach

Establish / Revise Management Structure & Control

Obtain / RenewExecutive Buy-In

and Support Monitor & Use EnterpriseArchitecture

Version 2.2

65

A Notional Enterprise Architecture ProcessA Notional Enterprise Architecture Process

Documents

System Engineering Process Improvement In Today’s Life Cycle Context