system dynamics of sustainment · suggested sustainment scenariossuggested sustainment scenarios...

19
System Dynamics of Sustainment Sustainment Sarah A. Sheard, Ph.D. Robert Ferguson Andrew P. Moore, Ph.D. © 2013 Carnegie Mellon University

Upload: others

Post on 07-Oct-2020

10 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: System Dynamics of Sustainment · Suggested Sustainment ScenariosSuggested Sustainment Scenarios • New threat or opportunity involving a technology change is requested by planners

System Dynamics of SustainmentSustainment

Sarah A. Sheard, Ph.D.Robert FergusonAndrew P. Moore, Ph.D.

© 2013 Carnegie Mellon University

Page 2: System Dynamics of Sustainment · Suggested Sustainment ScenariosSuggested Sustainment Scenarios • New threat or opportunity involving a technology change is requested by planners

SEI Objectives

The SEI works to:•Identify, research, evaluate, and advise on software y, , ,engineering technologies, trends, and practices •Collaborate with and leverage work found in industrial research, academia, and government laboratories•Mature promising software engineering technologies to enable standards, transition, and adoption•Enable government & industry organizations to make measured improvements in their software engineeringmeasured improvements in their software engineering practices

2© 2013 Carnegie Mellon University

Page 3: System Dynamics of Sustainment · Suggested Sustainment ScenariosSuggested Sustainment Scenarios • New threat or opportunity involving a technology change is requested by planners

Agenda

Background: The problemWhat Generates the Need for Sustainment Work?The system dynamics model and gaps as forcesScenarios (threat, support technology, workforce)Outcomes of scenariosOutcomes of scenariosPlans

3© 2013 Carnegie Mellon University

Page 4: System Dynamics of Sustainment · Suggested Sustainment ScenariosSuggested Sustainment Scenarios • New threat or opportunity involving a technology change is requested by planners

BackgroundDoD: Rising cost of software sustainment

Big, complicated problem• Multiple stakeholders with different value systems decide budgets• Constantly changing technology• Constantly changing threat space

I ti di i li ti f d t• Inventive users discovering new applications for products• Highly coupled, interdependent environment (systems talk to each other)• Unstructured and not well-managed portfolio of products

Making progress requires• Portfolio approach to management• Better funding budgeting processesBetter funding, budgeting processes• Better system architecture• Better and improving sustainment processes• ...

4© 2013 Carnegie Mellon University

Page 5: System Dynamics of Sustainment · Suggested Sustainment ScenariosSuggested Sustainment Scenarios • New threat or opportunity involving a technology change is requested by planners

Research Questions

How can sustainment organizations constantly learn and adapt1. How can we identify the funding needs?2. What has to be learned for the next release?3. What happens if/when funding is delayed?

What are the connections between stakeholders?

What are the opportunities to measure the business processes?What are the opportunities to measure the business processes?

5© 2013 Carnegie Mellon University

Page 6: System Dynamics of Sustainment · Suggested Sustainment ScenariosSuggested Sustainment Scenarios • New threat or opportunity involving a technology change is requested by planners

Need for Sustainment WorkU d t t fUpdate requests come from many sources Program: fighter aircraft• User community (warfighter, logistics)• External systems (C4I, supplies, maintenance)

Demand types:• Feature enhancement (new users, different uses, coalitions, new threat)• Performance improvement (technology opportunity or threat)• “Real options” – opportunity to invest for future value• Preventative measures: Information Assurance, security• Bug Fixes • Respond to External Change: New OS, new processor, new sensor

6© 2013 Carnegie Mellon University

Page 7: System Dynamics of Sustainment · Suggested Sustainment ScenariosSuggested Sustainment Scenarios • New threat or opportunity involving a technology change is requested by planners

Gaps as Sustainment System ForcesSystem Gap: Difference between strategy and operations• Mission Planning: effectively “strategic management” determines which

battles are to be fought with what operational capabilities. The measure of interest is the capacity of current operational capability.– Capacity: how much work can be done (battles can we fight)?– Capability: what are the skills, tools and methods we can bring to the fight?

• Operations: Operational performance as a percentage of total capability and the measures of successful performance.

S t i t G Diff b t ti d t i tSustainment Gap: Difference between operations and sustainment• Sustainment: Close the gap between potential capacity and available

capacity. Also update operational capability with new capabilities.

[Sustainment] Improvement Gap: Funds needed – Funds available• Funds required to update sustainment capability to address operational

capability and capacity concerns Funding is often deferred or delayed

7© 2013 Carnegie Mellon University

capability and capacity concerns. Funding is often deferred or delayed.

Page 8: System Dynamics of Sustainment · Suggested Sustainment ScenariosSuggested Sustainment Scenarios • New threat or opportunity involving a technology change is requested by planners

8© 2013 Carnegie Mellon University

Page 9: System Dynamics of Sustainment · Suggested Sustainment ScenariosSuggested Sustainment Scenarios • New threat or opportunity involving a technology change is requested by planners

How Gaps Act as ForcesSystem Gap (Strategy - Operations) Causes…• Operations to request additional support from Sustainment.

– Greater throughput = Increase your capacity to do sustainment; and do itGreater throughput Increase your capacity to do sustainment; and do it faster.

– Fix bugs that compromise operational capacity and capability.– Add enhancement to improve operational capability and capacity. y y

• Alternative: Go for a “Modernization Project” or new product..Sustainment Gap (Operations – Sustainment) Causes …• Sustainment organization to request updates to tools, skills and processes. g q p , p

Some internal improvement efforts will cover some of the work.• Requests that require changes to technology of product or development

process result in capital requests and training requests.Improvement Gap (Improvement need – Funding) Causes …• Both the sustainment gap and the systems gap to grow.• Delays in funding or partial funding have the same effect on sustainment.

9© 2013 Carnegie Mellon University

Page 10: System Dynamics of Sustainment · Suggested Sustainment ScenariosSuggested Sustainment Scenarios • New threat or opportunity involving a technology change is requested by planners

Systems Dynamics: Reinforcing and Balancing

Reinforcing and Balancing loops: “Limits to Growth Archetype”

“R” Reinforcing loops cause geometric growth rates.“B” Balancing loops create exponential decay rates.

10© 2013 Carnegie Mellon University

Page 11: System Dynamics of Sustainment · Suggested Sustainment ScenariosSuggested Sustainment Scenarios • New threat or opportunity involving a technology change is requested by planners

Growth and Underinvestment “Archetype”

Our “loops” are Operations, Sustainment, Sustainment InvestmentSystem Performance Gap=DemandSustainment Performance =Performance

11© 2013 Carnegie Mellon University

Page 12: System Dynamics of Sustainment · Suggested Sustainment ScenariosSuggested Sustainment Scenarios • New threat or opportunity involving a technology change is requested by planners

Sustainment = Growth and UnderinvestmentThree Gaps but more processes to define the loops.

12© 2013 Carnegie Mellon University

Page 13: System Dynamics of Sustainment · Suggested Sustainment ScenariosSuggested Sustainment Scenarios • New threat or opportunity involving a technology change is requested by planners

Simplified View of Simulation Model

13© 2013 Carnegie Mellon University

Page 14: System Dynamics of Sustainment · Suggested Sustainment ScenariosSuggested Sustainment Scenarios • New threat or opportunity involving a technology change is requested by planners

Testing the Simulation with Scenarios

Test a Simulation by 1. Create a stable model with all forces and flows in equilibrium.2 Pl i t t t th2. Plan scenarios to test the response.3. Run scenarios and validate the responses (data or interviews).4. Revise equations if needed.

Suggested Sustainment ScenariosSuggested Sustainment Scenarios• New threat or opportunity involving a technology change is requested by

planners.– Sustainers recognize requirement for changes to skills, tools and process.g q g , p– Sustainers request capital funds to improve capability.– Test scenarios with different funding delays

• Sequestration leads to furloughs resulting in loss of sustainment capacity.– What are the responses?– Do responses match actuals

• Funding Delays

14© 2013 Carnegie Mellon University

Page 15: System Dynamics of Sustainment · Suggested Sustainment ScenariosSuggested Sustainment Scenarios • New threat or opportunity involving a technology change is requested by planners

OutcomesAvg Sustainment PerformanceAvg Sustainment Performance

1

0.85 33

3 3 3 3 3

0.73 3

32 2 2 2 2 2 2 2 2 21 1 1 1 1 11

11

1

fract

ion

0.55

0.40 6 12 18 24 30 36 42 48 54 60

Time (Month)Avg Sustainment Performance : low training - steady staff 1 1 1 1 1Avg Sustainment Performance : med training - steady staff 2 2 2 2 2Avg Sustainment Performance : high training - steady staff 3 3 3 3 3

Shows what happens as we increase or decrease trainingShows what happens as we increase or decrease training.If we train less, productivity temporarily increases before attrition drains skills.If we train more, we get an increase until we get to a new steady state.

15© 2013 Carnegie Mellon University

Page 16: System Dynamics of Sustainment · Suggested Sustainment ScenariosSuggested Sustainment Scenarios • New threat or opportunity involving a technology change is requested by planners

Plans

Calibrate the model with a real sustaining organization• Sequestration and new technology changes will both help

Extend the model to investigate the additional problems of a portfolio• More projects create more opportunities for changep j pp g• More projects help to balance resources without dependence on consultants

16© 2013 Carnegie Mellon University

Page 17: System Dynamics of Sustainment · Suggested Sustainment ScenariosSuggested Sustainment Scenarios • New threat or opportunity involving a technology change is requested by planners

Benefits of Working with the SEI

Direct access to leading edge software engineering technologyg g g g gy

Opportunity for transition of technology for competitive advantage

Non-disclosure policies protect proprietary information

Potential for licensing technology developed as a result of collaboration

Fast-track contracting for Federal organizationsg g

17© 2013 Carnegie Mellon University

Page 18: System Dynamics of Sustainment · Suggested Sustainment ScenariosSuggested Sustainment Scenarios • New threat or opportunity involving a technology change is requested by planners

Contact

Bob FergusonSoftware Engineering InstituteC i M ll U i itCarnegie Mellon UniversityPittsburgh, PA [email protected]

Sarah Sheard, PhDSoftware Engineering InstituteCarnegie Mellon UniversityCarnegie Mellon UniversityPittsburgh, PA [email protected]

Institute Web Addresshttp://www.sei.cmu.edu

18© 2013 Carnegie Mellon University

Page 19: System Dynamics of Sustainment · Suggested Sustainment ScenariosSuggested Sustainment Scenarios • New threat or opportunity involving a technology change is requested by planners

Copyright 2013 Carnegie Mellon University

This material is based upon work funded and supported by the Department of Defense d C t t N FA8721 05 C 0003 ith C i M ll U i it f th tiunder Contract No. FA8721-05-C-0003 with Carnegie Mellon University for the operation

of the Software Engineering Institute, a federally funded research and development center.

Any opinions, findings and conclusions or recommendations expressed in this material are those of the author(s) and do not necessarily reflect the views of the United Statesthose of the author(s) and do not necessarily reflect the views of the United States Department of Defense.

NO WARRANTY. THIS CARNEGIE MELLON UNIVERSITY AND SOFTWARE ENGINEERING INSTITUTE MATERIAL IS FURNISHEDON AN “AS-IS” BASISENGINEERING INSTITUTE MATERIAL IS FURNISHEDON AN AS IS BASIS. CARNEGIE MELLON UNIVERSITY MAKES NO WARRANTIES OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AS TO ANY MATTER INCLUDING, BUT NOT LIMITED TO, WARRANTY OF FITNESS FOR PURPOSE OR MERCHANTABILITY, EXCLUSIVITY, OR RESULTS OBTAINED FROM USE OF THE MATERIAL. CARNEGIE MELLON UNIVERSITY DOES NOT MAKE ANY WARRANTY OF ANY KIND WITH RESPECT TO FREEDOM FROM PATENT, TRADEMARK, OR COPYRIGHT INFRINGEMENT.

This material has been approved for public release and unlimited distribution.

This material may be reproduced in its entirety, without modification, and freely distributed in written or electronic form without requesting formal permission. Permission is required for any other use. Requests for permission should be directed to the Software Engineering Institute at permission@sei cmu edu (DM 0000672)

19© 2013 Carnegie Mellon University

Institute at [email protected]. (DM-0000672)