Technology Program Management Model (TPMM) A Systems-Engineering Approach to Technology Development Program Management
|
|
- Nelson Gibbs
- 8 years ago
- Views:
Transcription
1 UNCLASSIFIED Technology Program Management Model (TPMM) A Systems-Engineering Approach to Technology Development Program Management Mike Ellis TPMM Development Manager Dynetics, Inc. Mike.Ellis@Dynetics.com Jeff Craver Project Manager Space and Missile Defense Technical Center Jeff.Craver@US.Army.Mil 1 1 UNCLASSIFIED
2 Space and Missile Defense, Technical Center Mission is to Successfully support the transition of evolving and mature technologies to customers. Technology Program Management Model (TPMM) 2 2
3 Introduction TPMM V2 applies a systems engineering methodology to Technology Program Management developed by the Space and Missile Defense Technical Center This presentation will highlight how a model like the TPMM can provide the Defense S&T community as a whole with the following benefits: A Systems Engineering Approach Improved Documentation Process Better Program Execution Management Decision Metrics Defensible Budgets 3 3
4 Transitioning Technology To Programs Technology Development Technology Transition ERINT MISSILE UPGRADE PAC III Ground Based Interceptor TECHNOLOGY DEMONSTRATION EKV THAAD Technology Program (HEDI) Radar Systems Technology TECHNOLOGY BASE SENSOR TECHNOLOGY Next Generation Radar THAAD System Satellite Early Warning System (SEWS) Solid State Laser Test Bed TCMP-3 SPACE AUGMENTATION HIGH ENERGY LASER TECHNOLOGY SYSTEM INTEGRATION TEST Target ABL Aegis BMD Interceptor Debris Solid State Demonstrator THAAD Target Debris JTAGS Critical Measurement & Countermeasures Program 4 4
5 SMDTC Had The Problem of Every S&T Executive Effectively managing technology development Programmatic problems Lack of Systems Engineering Principles Successfully transitioning technologies Transition not considered as part of Tech Dev Lack of Customer identification/involvement 5 5
6 Quantifying the Effects of Immature Technologies According to a GAO review of 54 DoD programs: Only 15% of programs began System Design Decision [post MS B] with mature technology (TRL 7) Programs that attempted to integrate with immature technologies averaged 41% cost growth and a 13 month schedule delay At Critical Design Review, 58% of programs demonstrated design instability (< 90% drawings releasable) Design stability not achievable with immature technologies Programs without stable designs at CDR averaged 46% cost growth and a 29 month schedule delay Source: Defense Acquisitions: Assessments of Selected Major Weapon Programs, GAO , March
7 First TRA Requirement User Needs & Technology Opportunities Process entry at Milestones A, B, or C Entrance criteria met before entering phase Evolutionary Acquisition or Single Step to Full Capability A B (Program Initiation) C IOC FOC Concept Refinement Concept Decision Technology Development Pre-Systems Acquisition TRA System Development & Demonstration Design Readiness Review LRIP/IOT&E Systems Acquisition Production & Deployment FRP Decision Review Operations & Support Sustainment DoD 5000 Metric Technology Readiness Assessment (TRAs( TRAs) - Required at MS B TRAs using Technology Readiness Levels (TRLs) 7 7
8 Perspectives Hey Buddy - I OWN The Requirements! Your next chance for funding is 5 years down the road stud! If you Push long enough they will come! I Want it All!! I Want it Cheap! I Want it Now! Gotta be small, lightweight, and 99.99% reliable I m governed by the JCIDS I NEED a REQUIRMENT (CDD)! My prime can do that!! I am governed by DoD You don t understand - This project is different from everyone else S&T does not require a process I have been doing it for years You forgot about the illities!!! Customer role is to integrate Threat Driven Soldier-Proof Fieldable Meets Mission Needs DOTMLPF USER USER Value Added Capability Probability of Success Acquisition Strategy Budget (LLC/POM) Schedule - WBS The System approach PM PM Technical break-thru Performance Goals Risk Cost Estimate. Program Plan Build a prototype S&T S&T 8 8
9 Aligning Technology with the Acquisition DoD 5000 MS s 9 9
10 Transitioning Technology Technology Management vs. Transition Management Transition an afterthought Transition Management Technologist still tinkering Not knowing when you re finished Typical Paradigm Not knowing when technology is needed Technology Management 10 10
11 1. Basic principles observed and reported. What Programmatic & System Engineering tasks should be performed during each Stage of Development? 2. Technology concept and/or application formulated. Technology Readiness Levels 3. Analytical and experimental critical function and/or characteristic proof of concept. 4. Component and/or breadboard validation in laboratory environment. When should I 5. Component know and/or what breadboard the validation requirements in relevant environment. for the 6. System/subsystem technology model or are? prototype demonstration in a relevant environment. 7. System prototype demonstration in an operational environment. How will my In what way will DoD R this technology Add Value to the Lowest level of technology readiness. Scientific research begins to be translated into technology s basic properties. End User? Invention begins. Once basic principles are observed, practical applications can be invented. The application is speculative and there is no proof or detailed analysis to support the assumption. Examples are still limited to paper studies. When should I Active research and development is initiated. This includes analytical studies and laboratory studies know who my to physically validate analytical predictions of separate elements of the technology. Examples include components that are not yet integrated or representative. Customer is? Basic technological components are integrated to establish that the pieces will work together. This is relatively low fidelity compared to the eventual system. Examples include integration of ad hoc hardware in a laboratory. Fidelity of breadboard technology increases significantly. The basic technological components are integrated with reasonably realistic supporting elements so that the technology At what can point be tested will in simulated environment. Examples include high fidelity laboratory integration of components. the technology Representative model or prototype system, which is well beyond the breadboard tested for level 5, is tested in a relevant environment. Represents a major step up in a technology s be transitioned demonstrated readiness. Examples include testing a prototype in a high fidelity laboratory a environment Customer? or in simulated operational environment. Prototype near or at planned operational system. Represents a major step up from level 6, requiring the demonstration of an actual system prototype in an operational environment. Examples include testing the prototype in a test bed aircraft. What is the definition of a 8. Actual system Technology has been proven to work in its final form and under expected conditions. In almost all progress completed be and What are the cases, this level represents the end of true system development. Examples include developmental qualified through test and measured? test and evaluation criteria of the for success? system in its intended weapon system to determine if it meets design demonstration. specs. completing a 9. Actual system proven through Actual application TRL? of the technology in its final form and under mission conditions, such as those successful mission operations. encountered in operational test and evaluation. Examples include using the system under operational mission conditions
12 Quantifying the Effects of Immature Technologies According to a GAO review of 54 DoD programs: Only 15% of programs began System Design Decision [post MS B] with mature technology (TRL 7) A System Engineering and Programs that attempted to integrate with immature technologies Programmatic-based TRL criteria set needs to be applied as a averaged 41% cost growth and a 13 month schedule delay At Critical Design Review, 58% of programs demonstrated design instability standard (< 90% earlier drawings releasable) in the process. Design stability not achievable with immature technologies Programs without stable designs at CDR averaged 46% cost growth and a 29 month schedule delay Source: Defense Acquisitions: Assessments of Selected Major Weapon Programs, GAO , March
13 Basic Stage Gate Process Stage Gate Type Process all businesses have a process Idea Task Problem Gate Gate Gate $ $ $ 1 Stage 1 2 Stage 2 3 Stage 3 Successful Product Each Gate is a decision point for the program to move to the next stage. Decision to Go / Kill / Hold / Recycle Each Stage is measured by: Metrics Goals Deliverables (Exit Criteria) Funding allocation Everything We Do is a Process 13 13
14 Aligning TRLs & DoD 5000 Concept Refinement Phase Technology Development Phase System Development & Demonstration Phase CD MS A MS B System Integration DRR System Demonstration MS C TRL 1 TRL 2 TRL 3 TRL 4 TRL 5 TRL 6 1. Basic principles observed & reported 2. Technology concept and/or application formulated S&T Community Activities 3. Analytical and experimental critical function and/or characteristic proof of concept 4. Component and/or breadboard validation in laboratory environment 5. Component and/or breadboard validation in relevant environment 6. System/ subsystem model or prototype demonstration in relevant environment 14 14
15 Aligning TRLs & DoD 5000 Concept Refinement Phase Technology Development Phase TPMM Criteria CD MS A MS B TRL 1 TRL 2 TRL 3 TRL 4 TRL 5 TRL 6 1. Basic principles observed & reported 2. Technology concept and/or application formulated 3. Analytical and experimental critical function and/or characteristic proof of concept 4. Component and/or breadboard validation in laboratory environment 5. Component and/or breadboard validation in relevant environment 6. System/ subsystem model or prototype demonstration in relevant environment Discovery Formulation Proof of Concept Refinement Development Demonstration Transition Develop an Idea Based on Threat, need, User Rqmt, Other Identify Pertinent Military Application & a Potential Customer(s) Develop a Concept Conduct Trade Studies Perform Military Utility Analysis Perform Paper Studies Identify specific customer(s) Analysis of Alternatives Proof of Concept and approach Develop General Technical Requirements ID cross technologies Develop Draft Tech Development Strategy TTA - Interest Demonstrate Key Technologies Work Together Refine Requirements System Eng Plan Update Tech Development Strategy TTA Intent Demonstrate Components Work With/as System Finalize Requirements Develop Transition Plan and Gain Customer Approval Demonstrate Prototype Ready for Operations Demonstrate Increased Capabilities Develop Transition Agreement Acquisition Strategy TTA Commitment 15 15
16 Functional View of a Systematic Development Process TDS TDS establishes common language and and vision vision DAU DAU adopted TTA TTA Program reviews reviews include include a TRA TRA and and a TAA TAA FUNCTIONAL VIEW ARCHITECTURAL VIEW Multi-Dimensional criteria criteria set set provides a comprehensive TRL TRL Assessment Programmatics System Engineering Transition Management 16 16
17 Operational View - Aligning Technology with Acquisition Partners TPMM defines the process and transition mechanisms to help tech programs align with Acquisition Milestones Alignment Mechanisms 17 17
18 Transitioning Technology Technology Management vs. Transition Management Transition Management Balanced Transition an afterthought Integrated Transition Management Paradigm Typical Technologist still tinkering Technology Paradigm Readiness Assessments Not knowing when you re finished Technology Advancement Assessments Not knowing when technology is needed Technology Transition Agreements Technology Management 18 18
19 A Systems Engineering Approach 19 19
20 TRL 3 TRL 4 TRL 5 TRL 6 Demonstration/ Refinement Development Transition AoA Understand User Requirements, Develop System Concept and Lab Validation Plan TPMM and the Systems Engineering V Lab Test Strategy IDD TDS Demonstrate and Validate System to User validation Plan Operational Prototype Validation Develop System Performance Specification And Relevant Environment Validation Plan Prelim Sys Spec Breadboard Laboratory Test results Initial Transition Plan Relevant Env Test Design Integrate System and Final Transition Plan Perform System TDS/Acq Strategy Verification to Roadmap Performance Specifications Final Sys Spec Decomposition & Design Expand Performance Tech Req Specifications into CI Functionality Anl Design-to Specifications And CI Verification Plan Initial Illities Plan Systems Engineering Design Engineering Evolve Design-to Design Codes Specifications into Build-to Documentation Exit Criteria And Inspection Plan Risk Mit Assemble CIs and Perform CI Verification to CI Design-to Specifications Inspect to Build-to Documentation Sys Config Formally Documented Interface Doc Manufacturing Plan illities Documented Integration & Qualification TPMM Recommended Documentation Fab Assemble and Code to Build-to Documentation Brassboard Relevant Environment Test results Buede, The Engineering Design of Systems,
21 Example Thread - Capability/Requirement Define Define User User Need/Utility Need/Utility TRL1 Formulate Formulate and and Prove Prove Technology Technology Concept Concept TRL2 Each Each activity activity set set is is threaded threaded to to provide provide an an evolutionary evolutionary effect effect from from Discovery Discovery through through Transition Transition Over Over Dependency Dependency Threads Threads in in Multiple Multiple Categories Categories Technical, Technical, Programmatic, Programmatic, and and Transition Transition Successor/Predecessor/Reference Successor/Predecessor/Reference Threads Threads Align Align Proven Proven Concept Concept with with Acquisition Acquisition Program Program Capability Capability TRL3 Develop Develop Functional Functional Requirements Requirements TRL4 Develop Develop Performance Performance Requirements Requirements Transition\Qualification Requirements Requirements Develop Develop Operational TRL6 Operational Requirements Requirements TRL
22 Physical View - Activity Centric Database Resources: Database: SQL Server App Environ: Windows Desktop Codebase:.NET Framework Dev Environ: Visual Studio
23 System Engineering Threads 23 23
24 Improved Documentation Process 24 24
25 TPMM Entry Process 25 25
26 TPMM High-Level Process 26 26
27 TPMM Database Activities Linked to Deliverables Resources: Database: SQL Server App Environ: Windows Desktop Codebase:.NET Framework Dev Environ: Visual Studio
28 TPMM Database Administration TTA.doc 28 28
29 Better Program Execution 29 29
30 Standardizes Tech Development, Assessment, & Transition A TRL-based, Systems Engineering Activity Model that Assists: Technology Program Definition o Identify Activities that will be performed o Identify Documents that will be produced o Provide an Environment for Tailoring the Model o Develop and Employ Best Practice Tools Technology Transition Management o Technology Transition o Technology Transfer o Technology Marketing Technology Maturity Assessments o Establishes Entry/Exit Criteria - Tailored for each Project o Provides a Framework for Performing Technology Readiness Assessments (TRA) TPMM: A Model for Technology Development and Transition 30 30
31 Establish TDS as Focal Point for Development Planning Producing a Technology Development Strategy (required at TRL3), with a focus on Systems Engineering Principles, helps Technology Managers by: Technology Goals aligning with Users, Capability Needs, and Performance Requirements Accomplishing Technology Goals drives Program Schedules Focuses program efforts on technology insertion points Develop and follow Transition Plan to execute TDS Establish transition agreements, even if informal, with transition partners Budget/Funding questions drive alignment with Sponsors/Customers Technology Readiness Assessment of the program instills confidence Gaps identified in Technology Development planning are fed directly to Risk Management & Mitigation 31 31
32 Incremental Capability Development (Excerpt from a TDS) Sample Project Office SystemA Test Tech Sensors Tech Analysis Test Event Potential System Architectures Functionality Determination Capability Alignment Sensor Evaluation Technology model dev SystemA Test Formal Test Initial Tech Capability Feedback SystemC Test SystemB Test SystemA Test Formal Test Upgraded Tech Capability Joint MOA/MOU AGREEMENT Test Event Test Event Test Event Test Event Test Event Mature Tech Capability Customer Certified Tech Capability Target SW Systems SW Nov 02 Dec 03 Feb 05 May Nov 05 Jun 05 1Q 07 1Q 07
33 Management Decision Metrics 33 33
34 Mgt Level Mgt Functions Tech Manager (Practitioner) Portfolio Manager (Director) Executive Manager TPMM as SMDTC Enterprise level solution Technology Program Definition ID activities performed by TRL ID documents that will be produced /delivered Develop and employ Best Practice Tools Portfolio Tracking Data Provides Enterprise Level Program Management Data Technology Maturity Assessment Establishes Technology Readiness Assessment Criteria Tailored to each program ID Technology Mgt Risks Standardized Measurements Aligns technologies for cross pollination ID Program Mgt Risks Supports Key Decision Points Enterprise Assessment TRLs (Push / Pull) Funding Transition Support s Key Decision Points Technology Transition Management Early Customer/USER Involvement TTA s Interest Intent Commitment Integration Opportunities Tech Transfer Opportunities Align DoD 5000 (Common Language) Transition Focus Doing The Right Things At The Right Time With The Right People Vision to have a Fully Automated Management Tool For All Managers 34 34
35 SMDTC TPMM Quad Chart (Notional) TRL Rating Based on TPMM TPMM Phase Required Criteria Met/Not-Met Gap Analysis (on Un-Met) Risk Assessment on Gaps Current TRL confidence and Statement of Risk Technology Development Strategy TPMM Requirement? (TRL3 or beyond) Status = Draft, Preliminary, Final Updated for Current Phase? Gap Analysis/Percentage Populated Programmatic Progress Transition Management Customer/User/Sponsor ID d TTA Version (Interest, Intent, Commitment) TTA Matrix Populated Signature Status Transition Planning Progress TRL Roadmap TRL Milestone Schedule to transition TPR Status Program Vision to Transition 35 35
36 Executive Dashboard Executive Dashboard Captures the Enterprise View of Technologies in S&T Status of Programs Transition Agreements in place Successful Transitions over time Program Distribution by TRL Technology Domain Science Discipline Sponsor Acquisition Customer Funding Facilitate Strategic Planning Technologies Distribution Technologies Gap Analysis Domain Analysis Skill gaps / recruiting needs (Develop/Maintain TC skill set) Diversified Portfolio Analysis Sponsor Science Discipline TTA Migration Status Metrics-driven Executive Dashboard forms the basis of a Decision Support System (DSS) 36 36
37 Promotes Defensible Budgets Effectively Communicates the Developmental Process/Methodology is working Establishes Requirements for Cost/Funding Capabilities/Performance Instill Confidence in Funding Source Documented Planning & Schedules Established Deliverable Documentation Puts Program Execution into perspective Aligns Technology with Acquisition Partners for Tech Insertion 37 37
38 Summary TPMM is a technology development activity model, partitioned into phases that are gate-qualified using TRL s. TPMM is a best practice standard that expands TRL understanding to include detailed activities, exit criteria, and deliverables. TPMM is a toolset used by the Tech Manager to plan, guide and measure a technology program s development maturity. TPMM is an alignment mechanism that promotes early focus on transitioning the technology to Acquisition Program Customers. TPMM acts as a common yardstick and provides OSD with the criteria for evaluating the Technology Development Strategy at MS A. TPMM model provides a standard TRL criteria set for performing effective Technology Readiness Assessments at MS B 38 38
39 Contact Information Mr. Jeff Craver U.S. Army Space & Missile Defense Command Huntsville, Ala Voice: or Mr. Michael Ellis Dynetics, Inc. P.O. Box 5500 Huntsville, AL Voice: Request a copy of TPMM Version 2.pdf file at:
John T. Dillard Jdillard@nps.edu 831.656.2650 GRADUATE SCHOOL OF BUSINESS & PUBLIC POLICY U.S. NAVAL POSTGRADUATE SCHOOL
John T. Dillard Jdillard@nps.edu 831.656.2650 GRADUATE SCHOOL OF BUSINESS & PUBLIC POLICY U.S. NAVAL POSTGRADUATE SCHOOL Progressive elaboration (vs. Requirements creep ) Iterative design/rapid prototyping
More informationTechnology Readiness Assessment (TRA)
DEPARTMENT OF DEFENSE Technology Readiness Assessment (TRA) Guidance April 2011 Prepared by the Assistant Secretary of Defense for Research and Engineering (ASD(R&E)) revision posted 13 May 2011 Contents
More informationManufacturing Readiness Level (MRL) Deskbook Version 2.0 May, 2011
Manufacturing Readiness Level (MRL) Deskbook Version 2.0 May, 2011 Prepared by the OSD Manufacturing Technology Program In collaboration with The Joint Service/Industry MRL Working Group This document
More informationEarly Development Planning Leads to Affordable Systems. NDIA 14 th Annual Systems Engineering Conference Track 4 Early Systems Engineering
Early Development Planning Leads to Affordable Systems presented at NDIA 14 th Annual Systems Engineering Conference Track 4 Early Systems Engineering October 25-28, 2010 Chuck Kondrack David Peterson
More informationWORKFORCE COMPOSITION CPR. Verification and Validation Summit 2010
WORKFORCE COMPOSITION CPR PEO IEW&S Organizational Assessment VCSA Brief Date 2010 October 13, 2010 This briefing is UNCLASSIFIED/FOUO PREDECISIONAL LIMITED DISTRIBUTION AS OF: 11 Sep 2010 Verification
More informationSystem (of Systems) Acquisition Maturity Models and Management Tools
System (of Systems) Acquisition Maturity Models and Management Tools Brian J. Sauser, Ph.D. Jose Ramirez-Marquez, Ph.D. Stevens Institute of School of Systems and Enterprise Readiness Level (TRL) System
More informationUsing the Technology Readiness Levels Scale to Support Technology Management in the DoD s ATD/STO Environments
Using the Technology Readiness Levels Scale to Support Technology Management in the DoD s ATD/STO Environments A Findings and Recommendations Report Conducted for Army CECOM Caroline P. Graettinger, PhD
More informationCYBERSECURITY CHALLENGES FOR DOD ACQUISITION PROGRAMS. Steve Mills DAU-South
CYBERSECURITY CHALLENGES FOR DOD ACQUISITION PROGRAMS Steve Mills DAU-South 1 Overview Questions Cybersecurity Owners and Stakeholders Cybersecurity Why It Matters to DoD Program Managers Defense Science
More informationTechnical Performance Measurement A Program Manager s Barometer
PROGRAM MANAGEMENT TOOLS Technical Performance Measurement A Program Manager s Barometer DCMA Pilots a Modified Approach to TPMs Technical Performance Measurement has been in widespread use for many years
More informationDoD Software Assurance (SwA) Overview
DoD Software Assurance (SwA) Overview Tom Hurt Office of the Deputy Assistant Secretary of Defense for Systems Engineering NDIA Program Protection Summit / Workshop McLean, VA May 19, 2014 May 19, 2014
More informationDeveloping Work Breakdown Structures
Developing Work Breakdown Structures International Cost Estimating & Analysis Association June 2014 Neil F. Albert MCR, LLC nalbert@mcri.com 703-506-4600 2014 MCR, LLC Distribution prohibited without express
More informationYour Software Quality is Our Business. INDEPENDENT VERIFICATION AND VALIDATION (IV&V) WHITE PAPER Prepared by Adnet, Inc.
INDEPENDENT VERIFICATION AND VALIDATION (IV&V) WHITE PAPER Prepared by Adnet, Inc. February 2013 1 Executive Summary Adnet is pleased to provide this white paper, describing our approach to performing
More informationPROJECT PLAN FOR. Project Name Here
PROJECT PLAN FOR Project Name Here Version # DatE Reviewed and Approved for submittal to Executive Sponsor , Project Manager Project Plan Approved for submittal to Executive Sponsor: , Project
More informationTechnology management in warship acquisition
management in warship acquisition A J Shanks B.Eng(Hons) MIET BMT Defence Services Limited SYNOPSIS Today s warship designers and engineers look to technology to provide warships and systems better, cheaper
More informationThe Application Readiness Level Metric
The Application Readiness Level Metric NASA Application Readiness Levels (ARLs) The NASA Applied Sciences Program has instituted a nine-step Application Readiness Level (ARL) index to track and manage
More informationRequirements Management John Hrastar
Requirements Management John Hrastar NASA Project Management Conference March 30-31, 2004 University of Maryland Conference Center Introduction Three aspects of requirements management Requirements in
More informationPMO Starter Kit. White Paper
PMO Starter Kit White Paper January 2011 TABLE OF CONTENTS 1. ABOUT THE PMO STARTER KIT...3 2. INTRODUCTION TO THE PMO STARTER KIT WHITE PAPER...3 3. PMO DEVELOPMENT ROADMAP...4 4. PLAN PHASE...5 4.1 CREATE
More informationBest Practices for the Acquisition of COTS-Based Software Systems (CBSS): Experiences from the Space Systems Domain
GSAW 2004 Best Practices for the Acquisition of COTS-Based Software Systems (CBSS): Experiences from the Space Systems Domain Richard J. Adams and Suellen Eslinger Software Acquisition and Process Office
More informationUpdate: OSD Systems Engineering Revitalization Efforts
Update: OSD Systems Engineering Revitalization Efforts 23 October 2007 Col Rich Hoeferkamp Ms. Sharon Vannucci Systems and Software Engineering (Enterprise Development) Office of the Deputy Under Secretary
More informationSystem Security Engineering
A Critical Discipline of SE Ms. Kristen Baldwin Director, Systems Analysis DDR&E/Systems Engineering 12th Annual NDIA Systems Engineering Conference 28 October 2009 10/28/09 Page-1 Defense Research & Engineering
More informationThe State of DoD Biometrics
The State of DoD Biometrics Biometrics Consortium Conference 22 Sep 2010 Mr Tom Dee Director, Defense Biometrics Director, JRAC OSD (AT&L), DDR&E thomas.dee@osd.mil 1 Agenda What We ve Done Biometrics
More informationCTC Technology Readiness Levels
CTC Technology Readiness Levels Readiness: Software Development (Adapted from CECOM s Software Technology Readiness Levels) Level 1: Basic principles observed and reported. Lowest level of software readiness.
More informationSoftware Engineering Framing DoD s Issues
Software Engineering Framing DoD s Issues Ms. Kristen Baldwin Director, Systems Analysis 15 September 2009 09/15/09 Page-1 DDR&E Organization WSARA 2009 - D,DT&E - D,SE - Dev Planning Director, Defense
More information6.0 Systems Integration
6.0 The Program s function provide a disciplined approach to the research, design, development and validation of complex systems to ensure that requirements are identified, verified, and met while minimizing
More informationSystem Security Engineering and Comprehensive Program Protection
System Security Engineering and Comprehensive Program Protection Melinda Reed Office of the Deputy Assistant Secretary of Defense for Systems Engineering 16th Annual NDIA Systems Engineering Conference
More informationIT Services Management Service Brief
IT Services Management Service Brief Service Continuity (Disaster Recovery Planning) Prepared by: Rick Leopoldi May 25, 2002 Copyright 2002. All rights reserved. Duplication of this document or extraction
More informationA Characterization Taxonomy for Integrated Management of Modeling and Simulation Tools
A Characterization Taxonomy for Integrated Management of Modeling and Simulation Tools Bobby Hartway AEgis Technologies Group 631 Discovery Drive Huntsville, AL 35806 256-922-0802 bhartway@aegistg.com
More informationDEPARTMENT OF DEFENSE 6000 DEFENSE PENTAGON WASHINGTON, D.C. 20301-6000
DEPARTMENT OF DEFENSE 6000 DEFENSE PENTAGON WASHINGTON, D.C. 20301-6000 NOV 1 0 2015 CHIEF INFORMATION OFFICER MEMORANDUM FOR ASSISTANT SECRETARY OF THE ARMY FOR ACQUISITION, LOGISTICS AND TECHNOLOGY ASSIST
More informationNASA Technology Roadmap Update Overview
National Aeronautics and Space Administration NASA Technology Roadmap Update Overview NASA Advisory Committee Technology, Innovation, and Engineering Committee Meeting December 4, 2014 Faith Chandler NASA
More informationIn today s acquisition environment,
4 The Challenges of Being Agile in DoD William Broadus In today s acquisition environment, it no longer is unusual for your program to award a product or service development contract in which the vendor
More informationInnovation Strategies for Affordable Readiness
Innovation Strategies for Affordable Readiness NDIA 10 th Presented to the th Annual Systems Engineering Conference 25 October 2007 Presented By Thomas C. Choinski Emergent and Transformational Systems
More informationProject Concept Proposal Guide Lines
Project Concept Proposal Guide Lines Contents 1.0 Overview 2 1.1 Background... 2 1.2 Process.. 2 2.0 Content of Proposal Main Body 3 2.1 Cover Page 3 2.2 Technical and Programmatic Background 4 2.3 Project
More informationApplying CMMI SM In Information Technology Organizations SEPG 2003
Applying CMMI SM In Information Technology Organizations Mark Servello, Vice President Jim Gibson, Senior Consultant ChangeBridge, Incorporated Page 1 Portions Copyright 2002 Carnegie Mellon University
More informationGeorgia Tech Research Institute. Translational Research Model for Creating Solutions through Innovation
Georgia Tech Research Institute Translational Research Model for Creating Solutions through Innovation GTRI_B-1 Georgia Institute Of Technology GTRI is the applied research arm of Georgia Tech and works
More informationSPAWAR HQ ARCHITECTURE AND HUMAN SYSTEMS GROUP Human-Systems Integration/Systems Engineering Support Performance Work Statement
SPAWAR HQ ARCHITECTURE AND HUMAN SYSTEMS GROUP Human-Systems Integration/Systems Engineering Support Performance Work Statement 1.0 INTRODUCTION The Department of the Navy Space and Naval Warfare Systems
More informationPM/PMO Knowledge and Tools from DAU through the AT&L Knowledge Management System
PM/PMO Knowledge and Tools from DAU through the AT&L Knowledge Management System John Hickok Director, Knowledge Management Global Learning and Technology Center November 4, 2010 Integrated Defense Acquisition,
More informationDepartment of Defense INSTRUCTION
Department of Defense INSTRUCTION NUMBER 5000.02 January 7, 2015 USD(AT&L) SUBJECT: Operation of the Defense Acquisition System References: See References 1. PURPOSE. This instruction: a. In accordance
More informationProject Management Life Cycle (PMLC)
Project Management Life Cycle (PMLC) Page 2 Project Management Life Cycle (PMLC) Introduction PMLC Working Group IT Business Process Management(BPM) IT Project Management Office (PMO) Finance System Support
More informationDATA QUALITY MATURITY
3 DATA QUALITY MATURITY CHAPTER OUTLINE 3.1 The Data Quality Strategy 35 3.2 A Data Quality Framework 38 3.3 A Data Quality Capability/Maturity Model 42 3.4 Mapping Framework Components to the Maturity
More informationRelease of the Draft Cybersecurity Procurement Language for Energy Delivery Systems
Release of the Draft Cybersecurity Procurement Language for Energy Delivery Systems Energy Sector Control Systems Working Group Supporting the Electricity Sector Coordinating Council, Oil & Natural Gas
More informationThe Need for a Systems Engineering Approach For Measuring and Predicting the Degradation of Aging Systems And How It Can Be Achieved
The Need for a Systems Engineering Approach For Measuring and Predicting the Degradation of Aging Systems And How It Can Be Achieved William Robinson Gisele Welch Gary O Neill Georgia Tech Research Institute
More informationFederal Segment Architecture Methodology (FSAM): An Overview
Information Resources Management College Federal Segment Architecture Methodology (FSAM): An Overview Dr. Stan Boddie & Prof. Matt Newman 1 a global learning community for government s most promising information
More informationSoftware and Systems Engineering. Software and Systems Engineering Process Improvement at Oerlikon Aerospace
SYMPOSIUM at Claude Y. Laporte OA - Process Engineering Nicola R. Papiccio OA - Software Engineering AGENDA Introduction Software Engineering Process s Engineering Process Management of of Change Lessons
More informationU.S. Dept. of Defense Systems Engineering & Implications for SE Implementation in Other Domains
U.S. Dept. of Defense Systems Engineering & Implications for SE Implementation in Other Domains Mary J. Simpson System Concepts 6400 32 nd Northwest, #9 Seattle, WA 98107 USA Joseph J. Simpson System Concepts
More informationSYSTEMS ENGINEERING FUNDAMENTALS
Introduction Systems Engineering Fundamentals SYSTEMS ENGINEERING FUNDAMENTALS January 2001 SUPPLEMENTARY TEXT PREPARED BY THE DEFENSE ACQUISITION UNIVERSITY PRESS FORT BELVOIR, VIRGINIA 22060-5565 i Systems
More informationSystems Development Life Cycle (SDLC)
DEPARTMENT OF BUDGET & MANAGEMENT (SDLC) Volume 1 Introduction to the SDLC August 2006 Table of Contents Introduction... 3 Overview... 4 Page 2 of 17 INTRODUCTION 1.0 STRUCTURE The SDLC Manual consists
More informationEmploying ITSM in Value Added Service Provisioning
RL Consulting People Process Technology Organization Integration Employing ITSM in Value Added Service Provisioning Prepared by: Rick Leopoldi January 31, 2015 BACKGROUND Service provisioning can oftentimes
More informationUnited States Government Accountability Office GAO. Report to Congressional Committees
GAO United States Government Accountability Office Report to Congressional Committees January 2005 TECHNOLOGY DEVELOPMENT New DOD Space Science and Technology Strategy Provides Basis for Optimizing Investments,
More informationHow To Implement Itil V3
2009 NMCI Conference: Implementing ITIL Session 1: ITSM Process ITSM COE Agenda Background ITSM Overview ITIL and Service Delivery Adopting ITIL to NGEN SE&I Activities 2 Background Develop Government
More informationProject Management Planning
The Project Plan Template The Project Plan The project plan forms the basis for all management efforts associated with the project. A project plan template is included in this document. The information
More informationAFCEA Aberdeen Luncheon. Army Common Operating Environment (COE) Update. March 11, 2015
AFCEA Aberdeen Luncheon Army Common Operating Environment (COE) Update Mr. Phillip Minor, Deputy Director, COE Directorate Assistant Secretary of the Army for Acquisition, Logistics and Technology (ASA(ALT))
More informationProgram Lifecycle Methodology Version 1.7
Version 1.7 March 30, 2011 REVISION HISTORY VERSION NO. DATE DESCRIPTION AUTHOR 1.0 Initial Draft Hkelley 1.2 10/22/08 Updated with feedback Hkelley 1.3 1/7/2009 Copy edited Kevans 1.4 4/22/2010 Updated
More informationLecture 8. Systems engineering L E C T U R E. SIMILAR process. Zuzana Bělinová. Faculty of Transportation Sciences, CTU in Prague
L E C T U R E 8 SIMILAR process LECTURE 8 - OVERVIEW Theoretical foundations of many methodologies - Typical SE process SYSTEMS ENGINEERING BASIC FACTS Systems Engineering is responsible for creating a
More informationCYBERSECURITY CHALLENGES FOR DOD ACQUISITION PROGRAMS. Steve Mills Professor of Information Technology Steve.mills@dau.mil 256.922.
CYBERSECURITY CHALLENGES FOR DOD ACQUISITION PROGRAMS 1 Steve Mills Professor of Information Technology Steve.mills@dau.mil 256.922.8761 Overview Cybersecurity Policy Overview Questions Challenge #1 -
More informationDr. David Burns Director for Science and Technology Advanced Technology Missile Defense Agency
Dr. David Burns Director for Science and Technology Missile Defense Agency DISTRIBUTION STATEMENT A. ; Distribution is UNLIMITED. 13-MDA-7174 Modeling and Today s Ballistic Missile Defense System 13-MDA-7174
More informationDepartment of Defense NetOps Strategic Vision
Department of Defense NetOps Strategic Vision December 2008 Department of Defense Chief Information Officer The Pentagon Washington, D.C. Table of Contents 1 Purpose...1 2 Introduction...1 2.1 NetOps
More informationPHASE 5: DESIGN PHASE
PHASE 5: DESIGN PHASE During the Design Phase, the system is designed to satisfy the requirements identified in the previous phases. The requirements identified in the Requirements Analysis Phase are transformed
More informationSUBJECT: Army Information Technology Service Management (ITSM) Policy
DEPARTMENT OF THE ARMY OFFICE OF THE SECRETARY OF THE ARMY 107 ARMY PENTAGON WASHINGTON DC 20310-0107 Office, Chief Information Officer/G-6 SAIS-PR MEMORANDUM FOR SEE DISTRIBUTION SUBJECT: Information
More informationPROJECT MANAGEMENT PLAN TEMPLATE < PROJECT NAME >
PROJECT MANAGEMENT PLAN TEMPLATE < PROJECT NAME > Date of Issue: < date > Document Revision #: < version # > Project Manager: < name > Project Management Plan < Insert Project Name > Revision History Name
More informationSAIC Corporate and Small Business Introduction
SAIC Corporate and Small Business Introduction April 2016 Michael A. Townsend, Sr. Director, SBLO SAIC Small Business Development and Utilization Office SAIC. All rights reserved. SAIC Overview Leading
More informationSystem/Data Requirements Definition Analysis and Design
EXECUTIVE SUMMARY This document provides an overview of the Systems Development Life-Cycle (SDLC) process of the U.S. House of Representatives. The SDLC process consists of seven tailored phases that help
More informationCareer Tracks- Information Technology Family
Career Tracks- Information Technology Family FUNCTIONAL AREA Applications Programming AV IT AV IT Engineering Bioinformatics Involved in the development of server/os/desktop/mobile applications and services
More informationENTERPRISE COMPUTING ENVIRONMENT. Creating connections THROUGH SERVICE & WORKFORCE EXCELLENCE
ITA Strategic Plan FY 2011 - FY 2016 U.S. Army Information Technology Agency REALIZING The DoD ENTERPRISE COMPUTING ENVIRONMENT Creating connections THROUGH SERVICE & WORKFORCE EXCELLENCE Provide Quality
More informationOverview of the System Engineering Process. Prepared by
Overview of the System Engineering Process Prepared by Ed Ryen, PE Maintenance ITS March 2008 Introduction This document provides a high level look at the Systems Engineering Process for ITS projects.
More informationEngineering Project Data Analysis
Session 24C Engineering Project Data Analysis By: George Graw Stuart Simon Copyright 2014 Raytheon Company. All rights reserved. Customer Success Is Our Mission is a registered trademark of Raytheon Company.
More informationIntroduction to the CMMI Acquisition Module (CMMI-AM)
Pittsburgh, PA 15213-3890 Introduction to the CMMI Acquisition Module (CMMI-AM) Module 2: CMMI-AM and Project Management SM CMM Integration, IDEAL, and SCAMPI are service marks of Carnegie Mellon University.
More informationEvolving the Enterprise Software Configuration Management Model
Evolving the Enterprise Software Configuration Management Model Successfully implementing DoD CM processes and requirements in an Agile/Xtreme programming development environment Jimmy Dyer/Stacy J. Speer
More informationJoint Capability Technology Demonstration (JCTD) Transition Desk Reference
Joint Capability Technology Demonstration (JCTD) Transition Desk Reference 1. PURPOSE. Provide guidance on Joint Capability Technology Demonstration (JCTD) Transition activities. This document will be
More informationUsing Spiral Development To Reduce Acquisition Cycle Times
Using Spiral Development To Reduce Acquisition Cycle Times Jacques S. Gansler, Ph.D. Professor and Roger C. Lipitz Chair Director, Center of Public Policy and Private Enterprise William Lucyshyn Director
More informationExascale Computing Project (ECP) Update
Exascale Computing Project (ECP) Update Presented to ASCAC Paul Messina Project Director Stephen Lee Deputy Director Washington, D.C. April 4, 2016 ECP is in the process of making the transition from an
More informationHow To Improve The Defense Communications System
Briefing to the AFCEA International Cyber Symposium 26 June 2013 Lt Gen Ronnie D. Hawkins, Jr. Director, Defense Information Systems Agency 1 1 UNCLASSIFIED Organizational Changes Command Staff Financial
More informationUNCLASSIFIED. UNCLASSIFIED Defense Information Systems Agency Page 1 of 9 R-1 Line #131
Exhibit R-2, RDT&E Budget Item Justification: PB 2015 Defense Information s Agency : March 2014 0400: Research, Development, Test & Evaluation, Defense-Wide / BA 5: Development & Demonstration (SDD) COST
More informationPROGRAM MANAGER S GUIDE
PROGRAM MANAGER S GUIDE Directory Just click on the individual directory item below or select from the bookmark tab. A Modular Open Systems Approach (MOSA) to Acquisition Forward Executive Summary MOSA
More informationBest Practices Statement Project Management. Best Practices for Managing State Information Technology Projects
State of Arkansas Office of Information Technology 124 W. Capitol Ave. Suite 990 Little Rock, AR 72201 501.682.4300 Voice 501.682.4020 Fax http://www.cio.arkansas.gov/techarch Best Practices Statement
More informationAccenture Cyber Security Transformation. October 2015
Accenture Cyber Security Transformation October 2015 Today s Presenter Antti Ropponen, Nordic Cyber Defense Domain Lead Accenture Nordics Antti is a leading consultant in Accenture's security consulting
More informationDepartment of Defense DIRECTIVE
Department of Defense DIRECTIVE NUMBER 5000.01 May 12, 2003 Certified Current as of November 20, 2007 SUBJECT: The Defense Acquisition System USD(AT&L) References: (a) DoD Directive 5000.1, The Defense
More informationRapid Prototyping: Leapfrogging into Military Utility
Headquarters U.S. Air Force I n t e g r i t y - S e r v i c e - E x c e l l e n c e Rapid Prototyping: Leapfrogging into Military Utility Mr. Randy Walden Air Force Rapid Capabilities Office (SAF/RCO)
More informationJoint Interoperability Certification
Joint Interoperability Certification What the Program Manager Should Know Chris Watson (Note: This article is an updated version of Joint Interoperability Certification: What the Program Manager Should
More informationHow to Write a Software Process Procedures and Policy Manual for YOUR COMPANY
How to Write a Software Process for YOUR COMPANY 1. Introduction MicroTools is proposing to assist YOUR COMPANY in improving the existing software process. The purpose of this project is to both improve
More informationPROJECT SCOPE STATEMENT
PROJECT SCOPE STATEMENT Note: Any work not explicitly included in the Project Scope Statement is implicitly excluded from the project. Project Name: Prepared by: BI - IT Governance Amy Winkel Date: 12/20/2010
More informationTechNet Land Forces South Small Business Opportunities. Carey Webster Director, Federal Information Solutions Deltek
TechNet Land Forces South Small Business Opportunities Carey Webster Director, Federal Information Solutions Deltek Agenda Review of Upcoming Opportunities for Small Businesses Army 8 Small Business Navy
More informationAchieving True Risk Reduction through Effective Risk Management
Achieving True Risk Reduction through Effective Pete Nolte Deputy Director, Major Program Support Office of the Deputy Assistant Secretary of Defense for Systems Engineering 16th Annual NDIA Systems Engineering
More informationODIG-AUD (ATTN: Audit Suggestions) Department of Defense Inspector General 400 Army Navy Drive (Room 801) Arlington, VA 22202-4704
Additional Copies To obtain additional copies of this report, visit the Web site of the Department of Defense Inspector General at http://www.dodig.mil/audit/reports or contact the Secondary Reports Distribution
More informationNIST Cloud Computing Program Activities
NIST Cloud Computing Program Overview The NIST Cloud Computing Program includes Strategic and Tactical efforts which were initiated in parallel, and are integrated as shown below: NIST Cloud Computing
More informationHow To Plan An Agile Project
GAO Scheduling Best Practices Applied to an Agile Setting by Juana Collymore and Brian Bothwell April 15, 2015 Outline Why is scheduling important? GAO Schedule Assessment Guide Overview Status of the
More informationINTRODUCTION: Plan and Schedule Development Create a Work Breakdown Structure (WBS) The detailed guidelines and examples start on the following page.
What This Is INTRODUCTION: Plan and Schedule Development Create a Work Breakdown Structure (WBS) The detailed guidelines and examples start on the following page. First of a series of guidelines for project
More informationFOUNDATION: Material Solution Analysis Is More Than Selecting an Alternative
Establishing the Technical FOUNDATION: Material Solution Analysis Is More Than Selecting an Alternative Aileen G. Sedmak, Zachary S. Taylor, and Lt Col William A. Riski, USAF (Ret.) Several government
More informationSummary of GAO Cost Estimate Development Best Practices and GAO Cost Estimate Audit Criteria
Characteristic Best Practice Estimate Package Component / GAO Audit Criteria Comprehensive Step 2: Develop the estimating plan Documented in BOE or Separate Appendix to BOE. An analytic approach to cost
More informationGoddard Procedures and Guidelines
Goddard Procedures and Guidelines DIRECTIVE NO. APPROVED BY Signature: Original signed by NAME: A. V. Diaz TITLE: Director Responsible Office: Title: Code 300 / Office of Systems Safety and Mission Assurance,
More informationMission Assurance for Unprecedented Missions
Mission Assurance for Unprecedented Missions Aegis Standard Missile-3 Terminal High Altitude Area Defense US Ground-Based Interceptor Forward-Based Radar With Adjunct Sensor Lt Gen (ret) Trey Obering USAF
More informationData Migration through an Information Development Approach An Executive Overview
Data Migration through an Approach An Executive Overview Introducing MIKE2.0 An Open Source Methodology for http://www.openmethodology.org Management and Technology Consultants Data Migration through an
More informationENOVIA Aerospace and Defense Accelerator for Program Management
ENOVIA Aerospace and Defense Accelerator for Program Management Through project pipeline dashboards, ENOVIA Aerospace and Defense Accelerator for Program Management provides real-time visibility into a
More informationUNCLASSIFIED Joint M&S Strategy WJTSC M&S Working Group September, 2012 COL Mark Edgren Technical Solutions Officer
Joint Staff J7 Joint M&S Strategy WJTSC M&S Working Group September, 2012 COL Mark Edgren Technical Solutions Officer Mandate for Change Why Change? Operating & Sustainment Costs Joint Force 2020 Keep
More information2015 Defense Health Information Technology Symposium Implementation of Agile SCRUM Software Development Methodology
Mr. Christopher Harrington, PM Clinical Support, Solution Delivery Division Mr. James Huber, Healthcare Data Analyst, DHA Decision Support 2015 Defense Health Information Technology Symposium Implementation
More informationINCOSE System Security Engineering Working Group Charter
1 PURPOSE Recent data breach cases and industrial control system incidents call attention to the inadequacy of current approaches to systems security [1, 2]. Each case presents more compelling evidence
More informationConsolidated Afloat Networks and Enterprise Services (CANES)
Consolidated Afloat Networks and Enterprise Services (CANES) Re-architecting the Navy s s C4I Network Infrastructure Lockheed Martin SNA Media Brief 11 January 2010 Lockheed Martin Proprietary Information
More informationMeasuring the Maturity of Robotic Planetary Mission Concepts II
SpaceOps 2010 ConferenceDelivering on the DreamHosted by NASA Mars 25-30 April 2010, Huntsville, Alabama AIAA 2010-2034 Measuring the Maturity of Robotic Planetary Mission Concepts
More informationHeadquarters U.S. Air Force
Headquarters U.S. Air Force I n t e g r i t y - S e r v i c e - E x c e l l e n c e Air Force Technology Readiness Assessment (TRA) Process for Major Defense Acquisition Programs LtCol Ed Masterson Mr
More information