Agenda Framing Assumptions (FAs) Lunch and Learn, March 8, Presenter: Brian Schultz. Moderator: Lt Col Doherty

Similar documents
Developing Framing Assumptions (FAs) Job Support Tool (JST)

Performance Assessments and Root Cause Analyses

Performance Assessments and Root Cause Analyses October 11, 2016

DoD Template for Application of TLCSM and PBL In the Weapon System Life Cycle

objective: to ensure our nation can afford the systems it acquires.

TOPIC DESCRIPTION SUPPLEMENT for the SYSTEMS ENGINEERING SURVEY DESCRIPTION

Given design trade studies, interpret the results to recommend the most cost-effective concept for development.

Overview of SAE s AS6500 Manufacturing Management Program. David Karr Technical Advisor for Mfg/QA AFLCMC/EZSM

Selected Acquisition Report (SAR)

Selected Acquisition Report (SAR)

STATEMENT OF WORK SMALL SPACECRAFT PROTOTYPING ENGINEERING DEVELOPMENT & INTEGRATION (SSPEDI) Space Solutions (SpS)

Performance Based Logistics

Stephen Welby Director, Systems Engineering Office of the Under Secretary of Defense (AT&L)

DOD INSTRUCTION BUSINESS SYSTEMS REQUIREMENTS AND ACQUISITION

Major Program Support ODASD(SE)

Attachment J-4 Milestone Acceptance Criteria and Payment Schedule

Selecting Software Development Life Cycles. Adapted from Chapter 4, Futrell

Naval Set-Based Design

Selected Acquisition Report (SAR)

Complex Systems of Systems (CSOS) : Software Benefits,Risks,and Strategies

7. Model based software architecture

Open Systems: State of the Practice

Development and Validation of a Systems Engineering Competency Model

OSD's Ten DMSMS Strategic Objectives. Defense Standardization Program Office OSD DMSMS / Obsolescence Lead (703)

Information Technology Independent Verification and Validation

SOFTWARE DEVELOPMENT STANDARD

AGENCY FOR STATE TECHNOLOGY

Systems Engineering Processes Applied To Ground Vehicle Integration at US Army Tank Automotive Research, Development, and Engineering Center (TARDEC)

Air Force Materiel Command

Identifying Acquisition Framing Assumptions Through Structured Deliberation

Operational Requirements Document (ORD)

Selected Acquisition Report (SAR)

CMMI Conference November 2006 Denver, Colorado

Selected Acquisition Report (SAR)

version NDIA CMMI Conf 3.5 SE Tutorial RE - 1

Top 5 Systems Engineering Issues within DOD and Defense Industry

Concept Exploration Methods for the Small Surface Combatant

Request for Solutions: High Energy Laser (HEL) Flexible Prototype. 11 December 2018

Selected Acquisition Report (SAR)

Independent Verification and Validation (IV&V)

Department of Defense Independent Technical Risk Assessment Framework for Risk Categorization

ADM The Architecture Development Method

ISA 201 Intermediate Information System Acquisition

CMMI V2.0 MODEL AT-A-GLANCE. Including the following views: Development Services Supplier Management. CMMI V2.0 outline BOOKLET FOR print.

11th Annual Systems Engineering Conference. Reduction of Total Ownership Costs (R-TOC) and Value Engineering (VE) in the Defense System s Life Cycle

This resource is associated with the following paper: Assessing the maturity of software testing services using CMMI-SVC: an industrial case study

7. Project Management

Replacing Risk with Knowledge to Deliver Better Acquisition Outcomes

TAMING COMPLEXITY ON MAJOR RAIL PROJECTS WITH A COLLABORATIVE SYSTEMS ENGINEERING APPROACH

TenStep Project Management Process Summary

Moving Satellite Communications Program to Next Level

Selected Acquisition Report (SAR)

Physics-based Modeling in Ship Design: Where are we headed?

Mission-Level Systems Engineering

Selected Acquisition Report (SAR)

Taking Logistics Workforce Professional Development to the Next Level

TOGAF 9.1 in Pictures

CMMI Project Management Refresher Training

Selected Acquisition Report (SAR)

Selected Acquisition Report (SAR)

Response strategies to the cost escalation of defence equipment

Selected Acquisition Report (SAR)

SUBJECT: Better Buying Power 2.0: Continuing the Pursuit for Greater Efficiency and Productivity in Defense Spending

Concept Exploration of the Amphibious Combat Vehicle

I Have Had My CMMI Appraisal What Do I Do Now? How to Establish a Process Improvement WBS

Improving Acquisition in Government Requirements Management Leading Practices: CMMI-ACQ Visualization

Program managers (PMs)

CHAPTER 2 Analyzing the Business Case (Phase 1: System Planning)

Lockheed Martin Aeronautics Company. Approach to Solving Development Program Issues

Institutionalizing Modular Adaptable Ship Technologies SNAME Annual Meeting October 24-26, 2012 Providence, RI

Big Data in Army Test and Evaluation

Selected Acquisition Report (SAR)

Changing Landscape. Contractors perform vital services in support of the entire DoD mission and team

Integrated Test: Challenges & Solutions. Honorable Dr. Michael Gilmore Director, Operational Test & Evaluation Presentation to NDIA March 15, 2011

Large Federal Agency Leverages IV&V to Achieve Quality Delivery for Critical Modernization Initiative

Implementation of the Reliability & Maintainability (R&M) Engineering Body of Knowledge (BoK)

Selected Acquisition Report (SAR)

Addressing the Barriers to Agile Development in DoD

Good Governance and Anti-Corruption: The Role of Supreme Audit Institutions (SAIs)

Analysis of Alternatives from a Cost Estimating Perspective. Kirby Hom and Kenny Ragland

TECHNICAL REVIEWS AND AUDITS

Complex Systems (Systems of Systems) Technology and What s Next!

Design, Integration and Project Management of Complex Engineering Projects. Alexander Walsh Executive General Manager Engineering at ASC Pty Ltd

Network Optimization Handbook. Your Guide to a Better Network

Requirements Analysis and Design Definition. Chapter Study Group Learning Materials

CHAPTER 2: IMPLEMENTATION PHASES AND OFFERINGS

Standards Harmonization Process for Health IT

Capacity building supporting long-range sustainable nuclear energy system planning

Everything You Need to Know About PMOs

Program Lifecycle Methodology Version 1.7

COMPLIANCE WITH THIS PUBLICATION IS MANDATORY

HOW TO DO BUSINESS WITH Lockheed Martin. Copyright 2015, Lockheed Martin Corporation. All rights reserved 0000.PPT 1/5/2016 1

Intermediate Systems Acquisition Course. Lesson 3.15 Full Rate Production ADE-3. Supporting ADE-3

Selected Acquisition Report (SAR)

Selected Acquisition Report (SAR)

Considering Cost in Requirements Generation

QUALITY AUDIT TRACKING: THE KEY TO EFFICIENCY, EFFECTIVENESS AND VALUE

Selected Acquisition Report (SAR)

A Data Item Description for System Feasibility Evidence

Transcription:

Agenda Framing Assumptions (FAs) Lunch and Learn, March 8, 2017 Presenter: Brian Schultz Moderator: Lt Col Doherty

Overview Background Definition and Guidance Why are they Important? Exercise How Do We Develop FAs? How Do We Test FAs Summary 2

Background Framing Assumptions (FAs) fairly new to acquisition lexicon: Introduced by Program Assessment and Root Cause analysis Office (PARCA) in USD AT&L PARCA analyzes root causes of Nunn-McCurdy program breaches Identified false assumptions as cause of significant cost growth that eventually led to cost growth and Nunn-McCurdy breaches Program management failed to recognize invalid assumptions early and did not take actively address disconnect until it was too late to avoid further issues Now recognized as a source of risk that must be managed PMs expected to document FAs early in the program lifecycle and to gather knowledge to validate and/or address changes needed 3

Definition Any supposition (explicit or implicit) that is central in shaping cost, schedule, or performance expectations of an acquisition program Typically should have a small number (3-5) of FAs with the following attributes: Critical: Significantly affects program expectations No work-arounds: Consequences cannot be easily mitigated Foundational: Not derivative of other assumptions Program specific: Not generically applicable to all programs PM Owns FAs! Should identify, continuously monitor their validity (and adjust as needed), and use them in assessments Source: PARCA, 11/15/2012 4

DoDI 5000.02 Guidance At the Milestone A Review: The Program Manager will present the approach for acquiring the preferred materiel solution including: the Acquisition Strategy, the business approach, framing assumptions, an assessment of program risk and how specific technology development and other risk mitigation activities will reduce the risk to acceptable levels, and appropriate Should Cost management targets At the Development RFP Release Decision Point, the Program Manager will summarize TMRR Phase progress and results, and review the Acquisition Strategy for the EMD Phase. Specific attention will be given to overall affordability; the competition strategy and incentive structure; provisions for small business utilization; source selection criteria including any best value determination; framing assumptions; 5

Why Are FAs Important? Used to help develop cost estimate for the program Used to help develop the acquisition strategy, which includes the: - Technical Strategy (scope, technical architecture, requirements, testing, etc.) - Support Strategy (R&M, maintenance concepts, depot, etc.) - Business Strategy (contract type, incentives, payments, etc.) Significant Implications, including Nunn-McCurdy Breaches if FAs are invalid 6

What is a Nunn-McCurdy Breach? Amendment to Title 10 introduced by Senator Sam Nunn and Congressman Dave McCurdy in the National Defense Authorization Act (NDAA) for Fiscal Year (FY) 1982. Requires that Acquisition Category I PMs maintain current estimates of Program Acquisition Unit Cost (PAUC) and Average Procurement Unit Cost (APUC). If the PAUC or APUC increases by 25 percent or more over the current Acquisition Program Baseline (APB) objective, or 50 percent or more over the original APB objective, the program must be terminated unless the Secretary of Defense (SECDEF) certifies to Congress that the program is essential to national security. Source: DAU Glossary 7

FAs in Nunn-McCurdy Breaches When an invalid framing assumption is embraced: Evidence of problems will accumulate Cost and schedule estimates will need to be changed But, the amount of growth will depend on How promptly management recognizes the issues How effectively management responds Further cost growth if the full Breach #1 implications of the invalid framing assumption are not addressed Breach # 2 It ain't what you don't know that gets you into trouble. It's what you know for sure that just ain't so. - Mark Twain Source: PARCA, 11/15/2012 8

Cost Estimating Assumptions Flow from Framing Assumptions Framing Assumptions Design is mature (Prototype design is close to Production-Ready) Consequences Production and development can be concurrent Weight (critical for vertical lift) is known Design can now be refined for affordability Estimating Assumptions Responsible Communities: Requirements, Technical, & Program Management Schedule will be more compact than historical experience Weight will not grow as usual for tactical aircraft Cost and Schedule Estimates Affordability initiatives will reduce production cost Cost Estimators Source: PARCA, 11/15/2012 9

Assumptions Drive Key Decisions Design is mature (Prototypes demonstrated key issue/trades) Government requirements have been defined Integration will be straightforward Conditions for FFP EMD are satisfied Confidence in system definition Resolution of SWaP issues Soundness of approach to contract management RFP Release Decision Source: PARCA, 11/15/2012 Not easy to recover without big impacts after RFP is released 10

Example of a FA The government program office has sufficient knowledge, data, expertise, and resources to execute successfully as the overall system integrator for the sensor upgrade program on the XX-51 armored vehicle program Does it meet these criteria? 1. Critical: Significantly affects program expectations 2. No work-arounds: Consequences cannot be easily mitigated 3. Foundational: Not derivative of other assumptions 4. Program specific: Not generically applicable to all programs 11

Exercise The next chart will provide some sample framing assumptions. Answer the following questions: Is it a good assumption? Why? 12

Examples 1. Cost (or Affordability), schedule, and/or performance goals can be achieved with minimal risk 2. The contractor and government program office will perform well 3. System deficiencies will be identified and fixed during testing 4. The system will be effective, suitable, and survivable 5. The program office has the resources it needs 6. Software development will stay on track because we plan to use a CMMI level IV company What, if anything is wrong with these? Source: PARCA Info paper, 9/13/2013 13

Are These Good Examples? X, Y or Z sub-systems (or other integral components) can be developed independently The prototype design is very close to production ready and will require few changes Commonality between variants will be at least X%. Significant purchases by joint, interagency, or international customers will reduce unit cost. Production at contractor s facility will not drop below X% of current levels, keeping overhead costs manageable Open system architecture and available technical data rights allow for competition Source: PARCA Info paper, 9/13/2013 14

How do FAs Get Identified? No cookbook approach but consider reviewing the following as a starting point: Operational environment and interfaces System dependencies and inter-relationships of other programs Industrial capabilities Technology Maturity Organizational landscape Deliverables needed for program success Existing plans and documents Use seed questions to examine program beliefs 15

How do we Develop FAs? Start by examining both explicit and implicit beliefs about your program The next set of charts contain examples of seed questions to help with this assessment Technical, Management, Requirements, Schedule, and Cost Questions Answering yes indicates a possible FA for the program in that area. These questions should be tailored to the program General questions to help identify assumption and questions to help assess criticality Source: RAND Identifying Acquisition Framing Assumptions Through Structures Deliberation, 2014041250 16

Sample Technical Questions Have the technologies planned for the system been demonstrated successfully in a similar application or environment? Is there commercial technology that is being used for the first time in a military application? Who has the data rights? Has the technology worked successfully under the same operating conditions? Does the system depend on COTS solutions, other commercial technologies and services, or a non-developmental item? Is this a novel integration of standard systems? Will these systems require modification for environment? How long might the manufacturer support such an item? Is the commercial availability stable? Have all the technologies been demonstrated or successfully operated at the scale planned (e.g,. power density, number of sensors, bandwidth)? Source: RAND Identifying Acquisition Framing Assumptions Through Structures Deliberation, 2014041250 17

Sample Management Questions Novel management structures Is the government acting as system integrator? Are multiple PEOs/PMs involved? Do industry partners participate through new commercial partnerships or JVs? Is the program dependent on the progress of other programs? Are there unique legal, diplomatic, or security issues? Does the program have an experienced workforce? Will there be issues retaining this workforce? Source: RAND Identifying Acquisition Framing Assumptions Through Structures Deliberation, 2014041250 18

Sample Requirements Questions Is there joint/foreign involvement? Are the program requirements compatible between the stakeholders? Does each participant require a customized version? Is there uncertainty with respect to quantities for partners? Are the requirements stable, well defined, and unambiguous? Will capability be met through an evolving design or series of upgrades? Are there unknown major areas of scope, e.g., facilities locations, operational availability, support equipment/infrastructure? Could another system substitute for this one? Can some of the requirements be deferred or met at a lower level? Source: RAND Identifying Acquisition Framing Assumptions Through Structures Deliberation, 2014041250 19

Sample Cost and Schedule Questions Does the program rely on sole source(s)? Are there known cost drivers? Have the intellectual property and data rights been resolved? Are there workforce supply or demand issues? Are key workforce skills/ trades in short supply? Can we hire at the rate based in our plans? Is the stability of the supplier base understood? Are there key suppliers who are at risk? Has the prime contractor executed a similar program (either in complexity or system/commodity type) before? Source: RAND Identifying Acquisition Framing Assumptions Through Structures Deliberation, 2014041250 20

Illustrative Sources for Framing Assumptions Program Environment future now Pre-MS B activities: The design is very similar to the ACTD Technical base: Modular construction will result in significant cost savings Policy implementation: The conditions are met for a firm, fixed price contract Organizational: Arbitrating joint-service requirements will be straightforward Program dependencies and constraints: System will facilitate easy solution of size, weight, and power issues Threat or operational needs: The need for precision strike of urban targets will not decline Industrial base/market: The satellite bus will have a substantial commercial market for the duration of program Source: PARCA, 11/15/2012 Program Program 21

How Can We Test FAs? Does information exist that: Disconfirms or is contradictory to the FA? Was previously dismissed but might now be relevant? Is new and could change the FA? Has it been properly adjusted? How accurate and reliable is information upon which the FA is based? Was incomplete, imprecise, or ambiguous information used? Could certain circumstances (e.g., social, technological, economic, environmental, political, organizational) affect the FA? Does the judgment account for these circumstances? How sensitive is it to these circumstances? Could circumstances proceed differently than expected? For what circumstances would this judgment be abandoned? Have all plausible but unpredictable circumstances been considered? Sources: Straus, Parker, and Bruce, 2011; CIA 2009; Kebell, Muller, and Martin, 2010. 22

Framing Assumptions Template Candidate Assumption Program Specific? No Workarounds? Foundational? Priority Metrics to Monitor FA 1 FA 2 FA 3 FA 4 FA 5 23

Source: PARCA, 11/15/2012 24

QTY & Cost Schedule Design Seaframe capability Early program 55 seaframes $220 million per seaframe 64 mission packages, $2.3 billion total cost Ships rapidly fielded, IOC in 2007, 3 years after initiation Leverage existing designs to enable a low-cost, rapidly fielded platform Sprint speed: 40-50 knots Range: 4,300-nautical-mile range when operated at speed of 16 knots and 1,000-nautical miles at 40 knots Mission packages capability New capabilities would be rapidly fielded as the Navy would integrate existing technologies on to the three types of mission packages mine countermeasures, surface warfare, and anti- submarine warfare Source: GAO-17-279T Evolution of Expectations for Navy s Littoral Combat Ship (LCS) Updated program 40 seaframes (includes 12 frigates) $478 million per seaframe 64 mission packages, $5.8 billion IOC (partial capability) in 2013, 9 years after program initiation Designs required considerable change and were under revision throughout the first several ships built Speed: Freedom variant can meet speed reqts but Independence variant did not meet speed reqts; frigate will have reduced speed Range: In 2009, endurance requirement reduced to 3,500-NM range at a speed of 14 knots. Freedom variant cannot meet these reduced reqts with a 2,138- NM range at a speed of 14 knots and 855 nautical miles at 43.6 knots; Independence variant can meet range requirements Some technologies ultimately less mature than envisioned, leading to significant difficulty developing mission capabilities Only 1 of 3 packages (surface warfare) has demonstrated required performance. However, IOC achieved at a temporarily reduced minimum capability requirement 25

Summary Development of valid framing assumptions is critical to establishing sound program parameters such as cost estimates, schedule baselines, contracting strategy, and performance expectations The PM owns these assumptions and thus, must ensure these assumptions are properly formulated and tested for realism periodically Ensure information used to base assumptions is relevant, recent, and accurate - Adjust program plans as soon as possible when FAs change or are determined to be invalid 26

Resources and Survey Resources: Framing Assumptions Job Support Tool: https://www.dau.mil/tools/t/framing-assumptions-job-support-tool WSM 014 Acquisition Strategy Development Workshop Please complete end of event survey: Link provided in chat area 27