The Parable of the Program Baseline

Similar documents
Manufacturing Readiness Assessment Overview

Gerald G. Boyd, Tom D. Anderson, David W. Geiser

Technology Readiness Assessment of Department of Energy Waste Processing Facilities: When is a Technology Ready for Insertion?

Vector-Based Metrics for Assessing Technology Maturity

Debrief of Dr. Whelan s TRL and Aerospace & R&D Risk Management. L. Waganer

Manufacturing Readiness Levels (MRLs) Manufacturing Readiness Assessments (MRAs) In an S&T Environment

GAO. NUCLEAR WEAPONS DOE Needs to Improve Oversight of the $5 Billion Strategic Computing Initiative

Kurt Gerdes, and Steven P. Schneider Office of Engineering and Technology Office of Environmental Management U.S. Department of Energy

SYSTEMS ENGINEERING MANAGEMENT IN DOD ACQUISITION

A Theory-Based Logic Model for Innovation Policy and Evaluation

April 10, Develop and demonstrate technologies needed to remotely detect the early stages of a proliferant nation=s nuclear weapons program.

National Institutional Model for Presenting Accurate Relevant Nuclear Science Information for People of all Ages and Interests 9476

On November 8, 2002, the Nonproliferation

Digital Engineering. Ms. Philomena Zimmerman. Deputy Director, Engineering Tools and Environments OUSD(R&E)/Systems Engineering

Nuclear Safety and Security Culture Roles and Responsibilities of Individuals. Middle East Scientific Institute for Security (MESIS)

U.S. Department of Energy Office of Inspector General Office of Audits and Inspections

Chemical-Biological Defense S&T For Homeland Security

Manufacturing Readiness Levels (MRLs) and Manufacturing Readiness Assessments (MRAs)

Special Notice # N R-S002 - Frequently Asked Questions #1

Advancing the Use of the Digital System Model Taxonomy

Senate Committee on Armed Services Subcommittee on Strategic February 25, 2000 Brigadier General Thomas Gioconda

Our Acquisition Challenges Moving Forward

National Policy Implications

Digital Engineering Support to Mission Engineering

Module 1 - Lesson 102 RDT&E Activities

Best Practices for Technology Transition. Technology Maturity Conference September 12, 2007

Quick Reaction Capability for Urgent Needs

Model Based Systems Engineering (MBSE) Business Case Considerations An Enabler of Risk Reduction

PROGRAM UPDATEPDATE. Has anyone heard any good rumors lately? Steve Guilfoos AF SBIR/STTR Program Manager Spring 2007

Reducing Manufacturing Risk Manufacturing Readiness Levels

Interoperable systems that are trusted and secure

Technology & Manufacturing Readiness RMS

Autonomous weapons systems as WMD vectors a new threat and a potential for terrorism?

CWA Containing Nuclear Power Overview

Statement of John S. Foster, Jr. Before the Senate Armed Services Committee October 7, 1999

Panel 3: Technology Transfer and Development

Information Warfare Research Project

Science and Technology for Naval Warfare,

Office for Nuclear Regulation

This presentation runs on its own. No user intervention is needed.

Space and Missile Systems Center

Moving from R&D to Manufacture

The Partnership Process- Issue Resolution in Action

ODU CEEVC and SAME Fall 2009 Seminar

Modeling Enterprise Systems

Other Transaction Authority (OTA)

Department of Energy Technology Readiness Assessments Process Guide and Training Plan

Manufacturing Readiness Level (MRL) Deskbook Version 2016

Moving from R&D to Manufacture

WHO WE ARE: Private U.S. citizens who advocate at our own expense for a bold and well-reasoned space agenda worthy of the U.S.

Lesson 17: Science and Technology in the Acquisition Process

The Role of the Communities of Interest (COIs) March 25, Dr. John Stubstad Director, Space & Sensor Systems, OASD (Research & Engineering)

High Explosive Radio Telemetry System. Federal Manufacturing & Technologies. R. Johnson, FM&T; B. Mclaughlin, FM&T;

Presented at the 2017 ICEAA Professional Development & Training Workshop. TRL vs Percent Dev Cost Final.pptx

RAPID FIELDING A Path for Emerging Concept and Capability Prototyping

Technology readiness applied to materials for fusion applications

New Approaches to Manufacturing Innovation in DOE

[This is a rush, unofficial transcript provided by National Security Reports.]

on-time delivery Ensuring

GAO Technology Readiness Assessment Guide: Best Practices for Evaluating and Managing Technology Risk in Capital Acquisition Programs

SYSTEM ANALYSIS & STUDIES (SAS) PANEL CALL FOR PAPERS

DoD Research and Engineering

ABSTRACT. Keywords: ESSP, Earth Venture, program management, NASA Science Mission Directorate, Class-D mission, Instrument-first 1.

Innovative Weapon Technology Solutions for the Current & Future Fight

Dedicated Technology Transition Programs Accelerate Technology Adoption. Brad Pantuck

TECHNICAL RISK ASSESSMENT: INCREASING THE VALUE OF TECHNOLOGY READINESS ASSESSMENT (TRA)

APPLICATIONS OF VIRTUAL REALITY TO NUCLEAR SAFEGUARDS

Transitioning Technology to Naval Ships. Dr. Norbert Doerry Technical Director, SEA 05 Technology Group SEA05TD

Commercial vs. Government Satellite Cost Drivers

The Role of Technical Authority at the U.S. Department of Energy Office of Environmental Management (EM) 9467

Cost Estimation as an Intensive Human Interactive Systems Engineering Problem

Empirical Research on Systems Thinking and Practice in the Engineering Enterprise

Voters Attitudes toward Science and Technology Research and the Role of the Federal Government

2009 Space Exploration Program Assessment

Thomas Jefferson High School for Science and Technology INTRODUCTION TO SCIENCE POLICY Program of Studies

Air Force Small Business Innovation Research (SBIR) Program

Intellectual Property, Vaccine Production and Technology Transfer

I N F O L O G I C The logical approach to harness innovation

Roadmapping. Market Products Technology. People Process. time, ca 5 years

Flexibility for in Space Propulsion Technology Investment. Jonathan Battat ESD.71 Engineering Systems Analysis for Design Application Portfolio

Arshad Mansoor, Sr. Vice President, Research & Development INNOVATION SCOUTS: EXPANDING EPRI S TECHNOLOGY INNOVATION NETWORK

FUTURE IAEA ROLES IN SUPPORT OF SUSTAINABLE NUCLEAR ENERGY. Roberto Cirimello Argentina

An Assessment of Acquisition Outcomes and Potential Impact of Legislative and Policy Changes

UNCLASSIFIED. R-1 Program Element (Number/Name) PE F / NAVSTAR Global Positioning System (User Equipment) (SPACE) Prior Years FY 2013 FY 2014

Follow the Yellow Brick Road

The Stockpile Stewardship Program

Jerome Tzau TARDEC System Engineering Group. UNCLASSIFIED: Distribution Statement A. Approved for public release. 14 th Annual NDIA SE Conf Oct 2011

Software Project Management 4th Edition. Chapter 3. Project evaluation & estimation

It recently published its results. It cited four commonly heard complaints with the DOD business environment. Those were

Acknowledging Jackson s Challenges for Growth The Significance of People & Place

2017 AIR FORCE CORROSION CONFERENCE Corrosion Policy, Oversight, & Processes

Technology readiness evaluations for fusion materials science & technology

Tren ds i n Nuclear Security Assessm ents

Steven P. Andreasen Bruce G. Blair Matthew Bunn Sidney D. Drell

5th International Symposium - Supercritical CO2 Power Cycles March 28-31, 2016

TERMS OF REFERENCE FOR CONSULTANTS

National Nuclear Security Administration Defense Nuclear Nonproliferation (DNN) R&D

Collaboration Agreement

Kevin Lesko LBNL. Introduction and Background

NextFlex: Enabling a Domestic Manufacturing Ecosystem for Flexible Hybrid Electronics (Extended Abstract)

Transcription:

The Parable of the Program Baseline August 7, 2012 Enchantment Chapter Regina M Griego, Ph.D. Sandia National Laboratories SAND Number: 2012-6603C Sandia is a multiprogram laboratory operated by Sandia Corporation, a Lockheed Martin Company, for the United States Department of Energy s National Nuclear Security Administration under contract DE-AC04-94AL85000.

Abstract Establishing the Program Baseline especially for government programs is an emergent process. The program baseline includes scope, schedule, and resources, but is paced and swayed by the timing of budget process and political maneuvering. How does a program team maintain integrity of right action on behalf of the nation in the midst of ambiguity? What is the role of requirements and the requirements process that most Systems Engineers know and love? This talk presents the story of the ambiguous nature of establishing a program baseline for a nuclear weapon program. It will present the hard questions that frame the conversation about nuclear weapons at the national level. 2

Nuclear Security Enterprise (NSE) Evolving Nuclear Security Enterprise (NSE) The enterprise has been significantly downsized and consolidated since the end of the Cold War. Government oversight Management change over time Hanford Site Richland, WA Lawrence Livermore National Laboratory Sandia National Laboratories Livermore, CA Laboratories Production Testing Materials Nevada Test Site Las Vegas, NV Rocky Flats Plant Golden, CO Sandia National Laboratories Albuquerque, NM Los Alamos National Laboratory Los Alamos, NM Pantex Plant Amarillo, TX Kansas City Plant Kansas City, MO Mound Plant Miamisburg, OH Y-12 Plant Oak Ridge, TN Pinellas Plant Largo, FL FMPC Fernald, OH Savannah River Plant Aiken, SC 1946 1974 1977 2000 3

NNSA Defense Programs Programs within NNSA (27% of DOE Budget) Defense Programs; $7.6 B Naval Reactors; $1.2 B Defense Nuclear Nonproliferation; $2.5 B Programs under Defense Programs Directed Stockpile Work Campaigns RTBF STA Workforce Eight agencies Eight DOE site offices Federal Program Management staff in DC and Albuquerque The FY 2012 President s Budget Request provides $11.78 billion to invest in a modern, 21st century nuclear security enterprise, implement the President s nuclear security agenda, and improve the way the NNSA does business and manages its resources. Mar 2, 2011, testimony by NNSA Administrator D Agostino 4

The Program Baseline Resources Budget People Infrastructure Dependant Systems Schedule Qualification schedule First Production Unit (FPU) Production schedule Initial Operating Capability (IOC) Scope Military requirements Surety requirements Architectural themes Historical approaches to assurance 5

The Parable of a Program Baseline The stewards gathered and decided what needed to be done on high-reliability, oneof-a kind systems, including a system that was designed originally in the early 60s. They were asked to be responsive after a disruptive change in the world. A new approach was conceived that called for a fundamental shift to an architected system that could be used on multiple systems. A rumor started that the stewards were violating the nothing new rule. Partisan politics reared its ugly head. The stewards were stopped in their tracks. The system that was originally designed in the early 60s was losing life, it was time to make decisions. Everybody knew this time was coming and all that was planned and budgeted was a tune-up because they expected the new approach would be used over the long term. Thwarted, the day came to decide exactly what was going to happen for this system. A tune-up wouldn t due. The stewards talked and talked and talked. They talked themselves into a program they believed they could stand behind as stewards. Unfortunately, the planned program differed greatly from what the stewards felt they needed to do. As the program baseline became clear, time passed. Programs get canceled or significantly down-scoped as a result 6

Non-linear Nature of the Program Baseline Politics Operating in the tension seek the peace and security of a world without nuclear weapons and as long as nuclear weapons exist, the United States will maintain a safe, secure, and effective arsenal Nothing new No Phase 1-5, only 6.1-6.6 Language is everything RRW, Modernization, Military characteristics Technical basis vs. Political reality Who are the stewards? It s now or never It will die under it s own weight Budgeting Process FYNSP (Future Years Nuclear Security Program) vs. Life-of-Program Continuing the continuing resolutions (CR) The gated appropriations language 7

Phase 1 Product Realization using Integrated Phase Gates Source Requirements Work of this stage is to elicit and analyze the source/ stakeholder requirements, and to understand the risks and implications to system requirements. A Study This gate documents the agreement of the gatekeepers as to source/ stakeholder requirements. Conceptual Design Work of this stage is to mature the design and assure it meets stakeholder requirements. B Program Plan C At this gate, the gatekeepers agree that the conceptual design meets the requirements from the first gate. Also at this gate, the associated risks and risk handling are agreed to and a plan is bought off for when technology maturity must be at certain levels. Program authorization Work of this stage is to create a program scope, schedule, and cost. The programmatic information goes into change control after this gate. Design & Integration Work of this stage is to validate, with system tests, that the design concept will function as required. System testing also provides cost validation. Note that for 6.X PRP efforts, there are activities and interactions between Gate C and the start of Stage D. Gate C will help the NNSA ensure that its information is ready for further integration with the DoD (into the JIPP). Also, decisions made at program authorization may impact scope and funding. Stage D includes an assessment of what was authorized. 8 D Full Scale Development & Production Engineering Final Design & Process Development Work of this stage is to further develop component definition and evaluate performance to requirements. Processes are also developed and characterized. E At this gate, the definition has been completely documented, and component, subsystem, and system functionality has been evaluated. The definition phase is largely complete, and the program is ready to proceed with process prove-in and qualification activities. Prod. Readiness & Qualification Steady-state production Work of this stage includes component process finalization and qualification. The activities integrate up to system qualification and delivery of the final product. F

Recommended Minimum TRLs and MRLs Phase 2 / 2A or 6.2 / 6.2 A Study Phase 3-5 or 6.3-6.5 Full Scale Development & Production Engineering A: Source Req s B: Concept Design C: Program Plan D: Baseline Design E: Final Design & Process Development F: Production Readiness & Qualification Final Tech Down-Selects System Final Design Review Qualification Evaluation Start First Production Unit, FPU Stable Production Weapon System MRL MRL 3 MRL 3 MRL 4 MRL 5 MRL 6 MRL 7 MRL 8 MRL 9 *Subassembly / Component TRL MRL TRL 5 MRL 2 TRL 5 MRL 3 TRL 6 MRL 4 TRL 6 MRL 5 TRL 7 MRL 6 TRL 7 MRL 7 TRL 8 MRL 8 TRL 9 MRL 9 9

Requirements Process to Date 2008 Full Scope became official, though not completely understood 2009 Gate A (Source Requirements) Collected and scrubbed the requirements... challenged where appropriate Requirements in flux, but some technical decisions were made Budget commitments made to technology maturation were not realized 2010 Major Scope on Hold by Congress Nuclear Posture Review (NPR) in progress funding gated by congress Difficult to determine budget estimates First schedule slip final schedule remained 2011 Gate B (Concept Design) Back to full scope, ramp-up required With technical teams engaged, a better FYNSP estimate made, still not final Program Authorization estimate Sticker shock-wave Gate B Budget disconnect with trade-offs necessary 2012 Gate C (Program Plan) and 6.3 Authorization Weapon Design and Cost Report (WDCR) Program Baseline does not add up Let the compromises begin! 10

Nuclear Conversation What do we consider to be our Nuclear Deterrent? People with critical skills? Infrastructure to develop and produce systems? Delivery platforms and nuclear payloads? Rumbling the ground? Non-proliferation systems? Is the Nation committed to a Nuclear Deterrent? Yes? If so, what could change that commitment? No? What would inspire commitment? Deterrent no longer relevant? What is the nation willing to pay for a Nuclear Deterrent? Pay on a system by system basis? Does not scale linearly Pay for the deterrent capability?... ante up Ambiguous or luke-warm commitment is not a good idea 11