OSD Earned Value Management Activities Update Larry L

OSD Earned Value Management Activities Update Larry L. Axtell Senior Program Analyst Office of the Under Secretary of Defense (Acquisition, Technology and Logistics) Acquisition Resources and Analysis February 8, 2005

Agenda Ø Revised Earned Value Management (EVM) Policy/Guidance Ø Work Breakdown Structure (WBS) Handbook Update Ø Government/Industry EVM Working Group 2

Revised Earned Value Management (EVM) Policy/Guidance

Revised EVM Policy/Guidance: Summary of Changes Ø New dollar thresholds for cost/incentive contracts (no differentiation between development and procurement) Ø Revise Cost Performance Report (CPR) Data Item Description (DID) - rename “Contract” Performance Report Ø Eliminate Cost/Schedule Status Report (C/SSR) and CPR-No Criteria Ø Expand application of Integrated Master Schedule (IMS) and link to CPR Ø Integrated Baseline Reviews (IBRs) required when EVM required Ø EVM on Firm-Fixed Price (FFP) contracts is riskbased decision 4

Revised EVM Policy/Guidance: Status Overview Ø Actions Completed: § Released policy changes for government and industry comment § Adjudicated comments; modified policy documents accordingly § Conducted business case analysis § Formally coordinated revised policy within Do. D § Finalized the CPR and IMS DIDs Ø Actions in Progress: § Revising DFARS clauses § Updating EVMIG (adding tailoring guidance and focusing on how to contract for EVM) § Updating Work Breakdown Structure (WBS) Handbook § Updating the Do. DI 5000. 2 and Defense Acquisition Guidebook 5

Revised EVM Policy/Guidance: Status Overview Ø Next Steps: § § § § Obtain USD(AT&L) approval of revised policy Release interim policy memorandum Publish revised DIDs (CPR and IMS) Publish changes to Do. DI 5000. 2 Publish changes to Defense Acquisition Guidebook Publish updated EVMIG Publish updated WBS Handbook Publish revised DFARS clauses (consider EVMS FAR clause) Ø Changes not retroactive, apply to contracts awarded in response to solicitations or RFPs issued on or after 30 days from the date of the signed policy memorandum 6

Work Breakdown Structure (WBS) Handbook Update Neil Albert MCR, LLC

Update MIL-HDBK 881 - Requirements Ø Update for Do. D 5000 changes Ø Identify how the WBS can support each acquisition phases and the actions necessary to enter and exit successfully Ø Reflect changes to new and improved approaches to product development (i. e. , spiral/evolutionary) Ø Show WBS is developed and maintained throughout the life cycle to meet program management goals as well as cost, schedule, and technical objectives Ø Show the WBS is the common link which will unify the planning, scheduling, estimating, budgeting, configuration management, and performance reporting disciplines 8

Task 1: Add/Improve upon WBS Definitions Ø Update definitions to reflect advancement of technology in design, development and manufacturing § Heavier reliance on software § Commercial-off-the-shelf items (Status: Completed) Ø Establish a Working Group consisting of Government and Industry to review at least the following appendices and provide comments and potential revisions § Aircraft – specifically UAVs (Status: Will be separate Appendix. Draft being coordinated in UAV Working Group) § Space – Multiple definitions – NASA, NRO, Do. D, etc. (Status: Final draft in coordination with Space Systems Working Group) § Ships – Waived for CSDR – no longer (Status: Final draft in coordination with Ship Systems Working Group) § Other Appendices modified (Status): • • • Aircraft to include Crew Station and Human Systems Integration Ordnance to include multiple stage frame Ground UV – consistent with Ground Vehicle Appendix Sea UV – To be determined Common Elements to include specific definitions for Aircraft, Space, Ships common elements unique to those systems 9

Task 2: Clarify how WBS is used with newer terms and processes Ø System of Systems/Family of Systems § Clarify terminology and highlight examples of how the WBS is created given the requirement for system interaction and interoperability § Show example of Systems WBS (Status: Working with OSD Systems Engineering staff to finalize definitions) Ø Spiral/Evolutionary Development (Hardware/Software) § Each spiral provides new functionality which could be considered product oriented, but better definition is required § Will define terminology and provide examples of how the WBS is created given an evolutionary requirement. (Process is already defined in the software WBS description --- most software engineers used spiral development to create software in the early 1990’s) (Status: Working with OSD Systems Engineering staff to finalize definitions) Ø Risk Analysis § Description of risk analysis use with WBS § System Engineering use to trade cost, schedule and technical risk of the system to meet end-item requirements (Status: Working with OSD Systems Engineering and PMI Risk SIG to to include appropriate definitions) 10

Task 3: Ensure the WBS is characterized as an Acquisition tool Ø To decrease the use of multiple WBSs used by different functional areas, define the WBS for all practical uses: § § § Cost Estimating EVM Database Scheduling Requirements planning, etc. Ø Establish group of system engineers, cost analysts, logisticians, earned value management technicians, program managers and contracts personnel to agree and commit to one approach defining and using the WBS for program support § Maintain a product oriented WBS reporting at level 3 (except for high cost, high risk or technology driving elements) § Communicate result by follow on training (Status: Coordinating with appropriate functions/associations and Government Reps) 11

Task 4: Support Budget, Cost, Schedule, Technical, Contractual and Performance Management Ø Identify Do. D 5000 has mandated certain reporting functions that rely on the WBS § Contract Funds Status Report § Contractor Cost Data Reporting § Earned Value Management (Status: Implementing into Draft documentation) Ø Use example § Demonstrate how acquisition reports will track to each other if a single WBS is used § Show relationship to • CLIN • SOW • Requirements • IMP/IMS (Status: Finalizing flow diagram to show relationships) 12

Task 5: Integrates with PM and SE Documents, Contracts and Cost Estimating Ø Re-enforce the use of the WBS via example § Show that without the WBS, the IMP/IMS relationship to other acquisition artifacts would not be possible (Status: Implementing into Draft documentation considering new DID requirements) 13

Other Activities Ø Effort being extended to account for full Do. D coordination effort § Required MIL-STD coordination § Expectation of completion – April 30, 2005 Ø Briefing major organizations on changes § § § ASC/Industry Workshop NDIA Program Management Subcommittee CSDR Focus Group SCEA PMI – College of Performance Management 14

Government/Industry EVM Working Group

Government/Industry EVM Working Group Ø Established in response to DAEC tasking Ø Working-level forum to “assess EVM and broader program management issues and concerns by sharing improvement ideas and recommending solutions, capitalizing on existing industry practices” Ø Standing body that meets at least quarterly or as required Ø Membership includes representatives from OSD, military services, defense and intelligence agencies, National Defense Industrial Association, and large defense contractors Ø Meetings held in July, August, and November: § Discussed main concerns regarding policy changes § Developed draft action plan to address overarching Do. D and industry issues Ø Next meeting scheduled for February 10, 2005 16

Government/Industry EVM Working Group Ø Major Issues Identified by Government/Industry EVM Working Group: 1. 2. 3. 4. 5. 6. 7. Policy, Validation, and Surveillance Contract Requirements Training Contract Definitization Management Acceptance Process Integrity Subcontractor Management Ø Working Group developing plan to define issues and strategies for implementing corrective actions § Revisions to EVM policy/guidance respond to Issue 1 § EVM Functional Integrated Product Team activity underway to address Issue 3—will have ancillary benefits in other areas § NDIA Program Management Systems Committee teams actively working related initiatives from industry perspective Ø Working Group is a standing body that will continue to dialogue on concerns, share improvement ideas, and recommend and implement solutions 17

Government/Industry EVM Working Group Ø Next Steps: § Complete action plan § Seek appropriate approvals of near-term improvement actions § Assist in implementing improvement actions § Assess progress and update plan § Continue to dialogue on concerns, share improvement ideas, and recommend solutions 18

Back-Up Slides

Background Ø Contemporary EVM is the product of a technique formalized by Do. D in the 1960’s Ø Criteria-based approach to management (Cost/Schedule Control Systems Criteria) was used for more than 35 years Ø 1996 was a year of change… § Transitioned from C/SCSC (35 government criteria) to EVM (32 industry guidelines) § Compliance responsibility transferred from military services to DCMA § Do. D recognized industry’s “ownership” of EVM Ø In 2003 problems came to light… § Industry concerns communicated in letter to USD(AT&L) (April 2003) § Do. D concerns discussed at executive-level meeting (July 2003) § Concerns presented to Defense Acquisition Excellence Council (DAEC); action resulted to establish team to work the issues and provide periodic status to DAEC (October 2003) Ø OSD actions in response to concerns: § Established Government/Industry EVM Working Group § Developed proposed revised Do. D EVM policy Ø Status update presented to DAEC on November 9, 2004 20

Revised EVM Policy/Guidance: New Application Thresholds Contracts Thresholds Cost or Incentive Equal to Or Above Threshold Cost or Incentive Less Than Threshold Plus All FFP Requirements > $50 M - Compliance with industry EVM standard - Formal validation of contractor’s EVM system - Contract Performance Report - Integrated Master Schedule - Integrated Baseline Review - Ongoing surveillance > $20 M - Compliance with industry EVM standard - Formal system validation not required - Contract Performance Report (tailored) - Integrated Master Schedule (tailored) - Integrated Baseline Review (scope tailored) - Ongoing surveillance - EVM optional (risk-based decision) - Ongoing surveillance < $20 M 21

Revised EVM Policy/Guidance: Tailoring Guidance Ø Guidance for tailoring CPR and IMS for cost or incentive contracts <$50 M but >$20 M Ø Considerations when making a risk-based decision to require EVM on cost or incentive contracts <$20 M; guidance for tailoring reporting Ø Considerations when making a risk-based decision to require EVM on FFP contracts; guidance for tailoring reporting Ø Will reside in Defense Acquisition Guidebook and Earned Value Management Implementation Guide (EVMIG) 22

Revised EVM Policy/Guidance: Business Case Analysis Ø Used contracts data supplied by Do. D and industry; applied proposed new EVM application thresholds § Increase in lower threshold from $6. 3 M to $20 M results in decrease in number of contracts requiring EVM (Do. D data = 2, 156; industry data = 1, 297) § Decrease in upper threshold from $315 M/$73 M to $50 M results in increase in number of contracts requiring a CPR and validated EVM system (Do. D data = 535; industry data = 261) Ø Used incremental cost algorithm to establish equivalency between difference in level of effort for CPR, Tailored CPR (replacement for C/SSR), and C/SSR (C/SSR = 0. 33 CPR; TCPR = 1. 1 C/SSR) § Do. D data – eliminate CPRs on 326 contracts § Industry data – eliminate CPRs on 235 contracts Ø Conclusion: § Policy changes will result in relatively significant cost avoidance; cost of eliminating C/SSRs more than offsets cost of additional CPRs § Few, if any, additional system validations will be required under the revised policy 23

Government/Industry EVM Collaboration Framework DAEC - Discussion forum - Oversees/promotes process Industry Executive Management Do. D Executive Management - Inputs to decisions - Approves/implements solutions - Inputs to decisions - Implements solutions OUSD(AT&L) - Prioritizes problems - Approves solutions NDIA - Represents industry - Prioritizes problems - Develops solutions Government/Industry Working Group - Identifies/defines problems - Recommends solutions - Assists in implementing solutions 24