K gallagher tosborne

  • Published on
    22-Apr-2015

  • View
    13.602

  • Download
    0

Embed Size (px)

DESCRIPTION

 

Transcript

<ul><li> 1. Overview of GAO Quicklook PM Challenge February 2012Katie Gallagher and Tracy Osborne OCFO/SID </li> <li> 2. Outline Background Why is this important? GAOs Approach What projects are involved? Why does GAO request technical data? What should I expect if my project is in Quicklook? What does NASAs data say? Agency Messages1/22/2012 2 </li> <li> 3. Background The GAOs Assessment of Large-Scale [NASA] Projects is Congressionally-mandated GAO sends its findings to Congress in an annual QuickLook Book (QLB) Report focusing on changes in project cost and schedule and providing GAOs explanations for these changes GAO is frequently called upon to testify about the results. Engagement objective: Identify and gauge the progress and potential risks associated with selected NASA acquisitions. (i.e., projects) GAO uses data from QuickLook Book (QLB) in other audits, such as the ongoing High Risk audit, and vice versa. 1/22/2012 3 </li> <li> 4. Why the Stakeholder Interest? NASAs historical inability to control cost and schedule growth JWST, CxP, MSL growth cited in several provisions establishing new reports. A 2004 GAO finding that NASA lacks discipline in cost estimation. Multiple Operating Plans per year to address cost growth or phasing. Based on past Performance NASA is required to report to OMB, Congress and GAO routinely on Project cost and schedule. All appropriations since FY 2008 have included direction for GAO to Identify and gauge the progress and potential risks associated with selected NASA acquisitions.1/22/2012 4 </li> <li> 5. Typical Results from Quicklook Reports Most of NASAs cost growth for the current portfolio is attributed to projects baselined prior to 2009 NASA projects do not meet GAO-identified best practice standards for technology maturity and design stability Other challenges that affect NASA project outcomes include Funding, Launch Vehicle, Development Partners, Parts Quality, Contractor Management1/22/2012 5 </li> <li> 6. Why do they ask about TRLs and drawings? GAOS APPROACH1/22/2012 6 </li> <li> 7. GAOs Report is in Two Parts Agency Observations Examines adherence to NASA policies such as 7120.5E and 1000.5A Examines potential systemic reasons for NASAs cost growth Assesses NASAs efforts to improve cost and schedule growth, including JCL policy Project Assessments Provides an update on status of each project included in the audit Outlines challenges specific to each project that GAO believes may lead to cost growth GAO Quicklook assesses performance of NASAs major projects and the Agencys management of those projects. 1/22/2012 7 </li> <li> 8. How does a project get picked? GAO evaluates all spaceflight projects in formulation if a contract is released that has development content and is greater than $25 M Can include projects in Phase A and Pre-Phase A if they have such a contract GAO evaluates all spaceflight projects in development with a life cycle cost greater than $250 M GAO continues to track projects in Operations until NASA negotiates removal from Quicklook Minimal data collection on Operations projects; main focus is cost and scientific results For projects in formulation, GAO expects NASA to provide cost and schedule ranges For projects in development, GAO expects NASA to provide baseline cost, schedule, design and technical information1/22/2012 8 </li> <li> 9. Projects Included in Audit 2008 2009 2010 2011 Requirement for Inclusion * Estimated Lifecycle Cost * Estimated Lifecycle Cost * Estimated Lifecycle Cost * Estimated Lifecycle Cost &gt;$250M &gt;$250M close to $250M (if it is called close to $250M (if it is called Lifecycle * In development * In development out in the budget as a out in the budget as a * In formulation if it also has * In formulation if it also has discreet project then it may discreet project then it may Phase as of released a development released a development be included) be included) Project Entrance contract valued at &gt;$50M contract valued at &gt;$25M * In development * In development Conference * If in operations, it is not * In formulation if it also has * In formulation if it also has (April 2011) (consistent with other included released a development released a development external reporting contract valued at &gt;$50M contract valued at &gt;$50M requirements) * In operations, in the prime * In operations, in the prime mission phase mission phase 1 Aquarius Development X X X X 2 Ares Formulation X X X 3 Dawn Operations X X X 4 Fermi/GLAST Operations X X X 5 GPM Development X X X X 6 Glory Development X X X X 7 GRAIL Development X X X 8 Herschel Operations X X X X 9 ICESat II Formulation X X10 JWST Development X X X X11 Juno Development X X X12 Kepler Operations X X X X13 LADEE Development X X14 LDCM Development X X X X15 LRO Operations X X X X16 MAVEN Development X X17 Mars 2016 (TGO) Formulation X18 MMS Development X X X19 MPCV Pre-Formulation X20 MSL Development X X X X21 NPP Development X X X X22 OCO/OCO-2 Development X X X23 Orion Formulation X X X24 Phoenix Closed Out X25 RBSP Development X X X26 SDO Operations X X X X27 SLS Pre-Formulation X28 SMAP Formulation X X29 SOFIA Development X X X X30 Solar Probe Plus Formulation X X31 TDRS Development X X32 Wise Operations X X X X1/22/2012 9 </li> <li> 10. GAO Business Case Model PDR CDR SIR Production Pre- Phase Phase Rarely Applies NASA phase A A B Phase C Phase D Phase E to NASA KDP-B KDP-C KDP-D Projects KDP-A KDP-D DOD Technology Development Engineering Manufacturing and Development Production and Deployment Operations and Support PDR MS-B CDR MS-C Concept and Technology Engineering Manufacturing and GAO Development Development Production Knowledge Knowledge Knowledge Point 1 Point 2 Point 3 Knowledge Point 1: Resources and Requirements Match Indicated by a high level of technology maturity Heritage is technology is appropriate in form, fit and function New Technologies at least at TRL-6 (for NASA) Knowledge Point 2: Product Design is stable about midway through development Best practice is to achieve design stability by midpoint of development GAO cites 90% of eng...</li></ul>