6/20/2005RBG Brief to QDR1 Presentation of Recommendations from the IT Acquisition Management Transformation Rapid Improvement Team (RIT) Pilot Report.

Slides:



Advertisements
Similar presentations
DoD Logistics Human Capital Strategy (HCS) Executive Overview 1 October 2008.
Advertisements

Introduction to the Joint Capabilities Integration and Development System (JCIDS) CAPT Keith Bowman, Joint Staff, J-8 Hello, I am Captain John Costello.
C2 Integration Division Marine Corps Combat Development Command
Capabilities and Acquisition Division
BENEFITS OF SUCCESSFUL IT MODERNIZATION
Continuous Process Improvement (CPI) Program Update Colonel Ric Sherman, United States Army Office of the Assistant Deputy Under Secretary of Defense for.
1 May 2009 ver. 5.5 Materiel Development Decision (MDD) MDA: Approves AoA Study Guidance Determines acquisition phase of entry Identifies initial review.
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 Headquarters U.S. Air Force AFRB MDD Template Rank, Name Office Symbol Date See footnotes on each.
Connecting People With Information DoD Net-Centric Services Strategy Frank Petroski October 31, 2006.
1 LBNL Enterprise Computing (EC) January 2003 LBNL Enterprise Computing.
Recent DoD Trends & System and Software Process Implications
Secure System Administration & Certification DITSCAP Manual (Chapter 6) Phase 4 Post Accreditation Stephen I. Khan Ted Chapman University of Tulsa Department.
CLR 252 Developing KPPs Note from SME:
Implementing Risk-based Oversight (RBO) Experiences during a 2 year Pilot of 10 DoD IT Programs Leonard Sadauskas.
9/11/ SUPPORT THE WARFIGHTER DoD CIO 1 Sample Template Community of Interest (COI) Steering Committee Kick-off Date: POC: V1.0.
Unit 5:Elements of A Viable COOP Capability (cont.)  Define and explain the terms tests, training, and exercises (TT&E)  Explain the importance of a.
DoD Acquisition Domain (Sourcing) (DADS) Analysis of Alternatives (AoA) E-Business/SPS Joint Users’ Conference November 15-19, 2004 Houston, TX.
NIST Special Publication Revision 1
Why is BCL Needed? BCL addresses long-standing challenges that have impacted the delivery of business capabilities The DepSecDef directed increasing the.
Relationships July 9, Producers and Consumers SERI - Relationships Session 1.
CoCom Involvement in the Joint Capabilities Process November 4, 2003.
A Combat Support Agency Defense Information Systems Agency UNCLASSIFIED UNCLASSIFIED Spectrum Access: The Tools to Connect GEMSIS 15 Aug 2011.
1 Clinger Cohen Act (CCA) (Title 40): An Emerging New Approach to Oversight – Overview and Program Pilot June 27, 2006 Mr. Edward Wingfield Commercial.
UNCLASSIFIED CJCSI Revision Update CAPT Jeff Gernand, J-8 12 November 2002.
Joint Capabilities Integration and Development System (JCIDS) Nov 2010
TITLE 40 CCA Outcome Measures of Effectiveness (MOEs) Revision of mission-related and administrative processes (BPR) Post Implementation Review (PIR) Briefing.
Power to the Edge A Net-Centric DoD NII/DoD CIO Performance and Results-based Management of IT and NSS Investments Measures of Effectiveness (MOEs) and.
Life Cycle Logistics.
D Appendix D.11. Toward Net-Centric Acquisition Oversight A Proposal for an Acquisition Community of Interest (COI) MID 905 Streamlined Acquisition.
Power to the Edge MDAP and IT/NSS Requirement to Develop Outcome Measures of Effectiveness and Conduct PDPR/PIR Leonard Sadauskas DASD(DCIO) CP/O
CAPT Joe Spruill Office of Deputy Assistant Secretary of the Navy (Logistics) September 29, 2005 Managing Obsolescence within a Performance Based Logistics.
A Net-Centric DoD NII/CIO 1 Sample Template Community of Interest (COI) Steering Committee Kick-off Date: POC:
Verification and Validation — An OSD Perspective — Fred Myers Deputy Director, Test Infrastructure Test Resource Management Center November 4, 2009.
Perspectives on the Analysis M&S Business Plan Dr. Tom Allen, IDA Mr. James Bexfield, PA&E, OSD Dr. Stuart Starr, IDA June 19, 2008.
Connecting People With Information Transforming the Way the DoD Manages Data M. David Allen OASD(NII)/DoD CIO May 23, 2006 “The.
ILW Panel: Army Institutional Adaptation Readiness Core Enterprise U.S. Army Forces Command General Hondo Campbell 6 October 2009 As of Oct09.
Evaluate Phase Pertemuan Matakuliah: A0774/Information Technology Capital Budgeting Tahun: 2009.
0 2 Nov 2010, V1.4 Steve Skotte, DAU Space Acquisition Performance Learning Director New Space Systems Acquisition Policy.
CCA LSS Support Slides1 Draft The Defense Acquisition Management Framework. Post Implementation Review (PIR) Capability Needs Satisfaction & Benefits.
Search Engine Optimization © HiTech Institute. All rights reserved. Slide 1 Click to edit Master title style What is Business Analysis Body of Knowledge?
NSA MOE-PIR Outcome Measures of Effectiveness (MOEs) and their Measure During a Post Implementation Review (PIR) Leonard Sadauskas OASD(CIO) CP&O.
IT Acquisition Management Transformation Rapid Improvement Team (RIT) PM / Pilot Team Meeting 19 November 2002.
| 1 Weapon System Acquisition Reform- Product Support Assessment DAU SYMPOSIUM 13 April 2010 Presented by: Basil Gray Where Innovation.
Power to the Edge A Net-Centric DoD NII/DoD CIO IT Acquisition Management Transformation Rapid Improvement Team (RIT) Principals Meeting November 18, 2003.
Leadership Guide for Strategic Information Management Leadership Guide for Strategic Information Management for State DOTs NCHRP Project Information.
Environment, Safety, and Occupational Health Opportunities in DoD Business Transformation May 4, 2006.
Integrated Product Team (IPT) Process Training
DoD Template for Application of TLCSM and PBL
Agile Culture Instructor Pilot ISA 301 March 2017 Robert Thomas.
Lesson Objectives Determine the key Requirements Manager activities and the role of the ICD leading up to the MDD and during Materiel Solution Analysis.
Lesson Objectives Determine the key Requirements Manager activities leading up to the MDD, the outputs of the MDD, and the Defense Acquisition documents.
Materiel Development Decision (MDD) to Milestone A Requirements Management Activities July 12, 2016.
DoDAF 2 Was Designed to Support DoD’s 6 Core Processes
Life Cycle Logistics.
Materiel Development Decision (MDD) to Milestone A Requirements Management Activities April 25, 2017.
MDD to Milestone A Requirements Management Activities
ISA 201 Intermediate Information Systems Acquisition
Milestone A to Milestone B Requirements Management Activities
JTAMS MILESTONE A ANALYSIS
Identify the Risk of Not Doing BA
ISA 201 Intermediate Information Systems Acquisition
Architecture Tool Vendor’s Day
ISA 201 Intermediate Information Systems Acquisition
AT&L Hot Topics in Acquisition
MDD to Milestone A Requirements Management Activities
Materiel Development Decision (MDD) to Milestone A (MS A)
Materiel Development Decision (MDD) to Milestone A (MS A)
GAO’s Approach to Assessing an Organization’s Investment Maturity:
The Department of Defense Acquisition Process
Presentation transcript:

6/20/2005RBG Brief to QDR1 Presentation of Recommendations from the IT Acquisition Management Transformation Rapid Improvement Team (RIT) Pilot Report Blueprint for Establishing Risk-based Governance of IT Investments in a Net-centric Department of Defense Presented to: COTS IT Acquisition Barrier WG 2005 QDR

6/20/2005RBG Brief to QDR2 Purpose Present recommendations of the IT Acquisition Management Transformation Rapid Improvement Team (RIT) Pilot Determine if the recommendations are appropriate for the 2005 QDR IT Working Group or should be referred to another QDR IPT

6/20/2005RBG Brief to QDR3 Issue and Recommendations It takes too long to implement IT solutions needed by the warfighters. How can we shorten the time? –Restructure the PPBE process to finance IT solutions through working capital funds and avoid the current POM process –Enable self-organization of the IT/NSS investment community –Institute Risk-based Governance

6/20/2005RBG Brief to QDR4 RIT Pilot Summary

6/20/2005RBG Brief to QDR5 Restructure the PPBE process to finance IT solutions through working capital funds Recommended by the RIT but not employed by the pilot programs because each had already gone through the POM process Comptroller agreed to take for action Remains unresolved

6/20/2005RBG Brief to QDR6 Enable self-organization of the IT investment community What is self organization? –Originated from observation of biological systems –Just as the warfighters’ exploitation of net-centricity achieved information superiority and in turn enabled self-synchronization, exploitation of net-centricity by the business community can achieve business information superiority and enable self-organization. Why does the business community need self-organization? –US industry leaders are already exploiting self-organization to maintain agility in a global marketplace –Since 9-11, the Department has not adequately met the warfighter’s need for information superiority. –GAO Comptroller General gives warfighter support poor grades Can self-organization work in DoD? –Observed in high performance IT investment organizations such as GCSS-AF and GCSS CC/JTF –DoD Data Strategy Communities of Interest (COI) is an example

6/20/2005RBG Brief to QDR7 Institute Risk-based Governance What is Risk-based Governance? –It is the extension of the current policy that states: Responsibility for the acquisition of systems shall be decentralized to the maximum extent practicable, consistent with the risk of the investment and the capability of the investing organization to manage the risk. How is Risk-based Governance different from delegation? –The covenant between the Sponsor, the Acquiring Agency headquarters and the subordinate acquiring echelon is that the delegation of milestone decision authority to the subordinate echelon will add no unacceptable risk to the investment. –Enables fast track initiation of IT solutions to warfighter needs What are the prerequisites for Risk-based Governance? –The same as for self-organization

6/20/2005RBG Brief to QDR8 Model of Risk-based Oversight The hypothesis for the Insight element of RBG is: Headquarters staff due diligence can be accomplished through timely and transparent insight into JCIDS & PMO work products.

6/20/2005RBG Brief to QDR9 Basis for Risk-based Governance Observation of high performance RIT Pilots revealed five common traits: –Full awareness of the program’s objectives within all levels of the Sponsor, PEO and PMO organizations –A thorough understanding of the ultimate users’ (changing) needs –Direct communications with the ultimate users and user surrogates –A leadership climate that valued innovation and aggressive management –Maximum employment of available net-centric management tools Compares with Alberts and Hayes assumptions for self- synchronization –Clear and consistent understanding of command intent –High quality information and shared situational awareness –Competence at all levels of the force –Trust in the information, subordinates, superiors, peers, and equipment

6/20/2005RBG Brief to QDR10 Attributes of Risk-based Governance 1.A clear understanding of desired investment outcomes 2.Institutionalized risk assessment and management 3.A collaborative environment with provision for insight into selected investment information sets 4.Process for assessing organizational investment capability 5.Organizational support for capability improvement 6.A trusting relationship between corresponding headquarters and subordinate oversight actors Correlating the RIT Pilot observations with Alberts’ self- synchronization assumptions leads to six attributes essential for creating a self-organizing environment we call Risk-based Governance:

6/20/2005RBG Brief to QDR11 Recommendations for consideration by the QDR IT Working Group for achieving the six attributes of Risk-based Governance and Self-organization

6/20/2005RBG Brief to QDR12 General Recommendations 1.Change DODD paragraph Streamlined and Effective Management. From, –“Responsibility for the acquisition of systems shall be decentralized to the maximum extent practicable.” To, –“Responsibility for the investment in systems shall be decentralized to the maximum extent practicable, consistent with the risk of the investment and the capability of the investing organization to manage the risk.”

6/20/2005RBG Brief to QDR13 General Recommendations (con’t) 2.Legislative recommendation: Propose that Congress change the definition of a major program from solely a cost threshold basis to one that includes both cost and the risk of achieving a needed capability or transformation.

6/20/2005RBG Brief to QDR14 A clear understanding of desired investment outcomes 1.That the instruction governing warfighter functional capability boards, CJCSI and CJCSI , include as part of FCB responsibilities the articulation of outcome measures of effectiveness as exit criteria for a functional needs analysis, and a commitment to conduct a post implementation review against those measures at appropriate points after the system is fielded. 2.That the portfolio management directives and instructions now being developed by OASD(NII) include provisions for Business Domain Owners to conduct functional area, needs and solutions analyses such as required by CJCSI , and that those analyses result in the establishment of outcome measures of effectiveness and the commitment to conduct post implementation reviews against those measures

6/20/2005RBG Brief to QDR15 A clear understanding of desired investment outcomes (cont) 3.That the DoD Enterprise Architecture Performance Reference Model include a process for developing measures of effectiveness (MOEs) and a requirement for an assessment of the MOEs after implementation in a post implementation review (PIR).

6/20/2005RBG Brief to QDR16 Institutionalized Risk Assessment and Management 1.OSD implement risk-based governance and resource an OSD organization to assess OSD and Component IT investment capability. 2.Adopt a generic set of IT acquisition project risk factors, such as is currently being piloted by the US Army, or as has been adopted by the State of Texas Department of Information Resources. Such an inventory of risk factors would be initiated during the Functional Solution Analysis phase and updated as the program evolved 3.Require, as part of Milestone and Decision Reviews, a uniform presentation of investment risk assessment and management using the probability-consequence display format of the DAU Risk Guide

6/20/2005RBG Brief to QDR17 Institutionalized Risk Assessment and Management (cont) 4.Update the DoD Chief Information Officer October 24, 2001 Memorandum, Subject: Policy and Procedures for the Fast Track Deployment of Information Technology, to reflect Risk-based Governance, and urgent program initiation 5.Charter an IPT of OSD and JS gatekeepers and Component representatives to reach agreement about the minimum content and approval process for consolidated acquisition information for Fast Track IT programs

6/20/2005RBG Brief to QDR18 A collaborative environment with provision for insight into selected investment information sets The hypothesis for the Insight element of RBG is: –Headquarters staff due diligence can be accomplished through timely and transparent insight into JCIDS & PMO work products. 1.Form an IT investment COI that includes JS, OSD and Component investment actors and exploits NCES 2.Charter an IPT to identify investment information objects needed to conduct insight in a Net-centric investment environment and develop a plan for implementation 3.Identify NCES compatible applications to provide the desired investment insight

6/20/2005RBG Brief to QDR19 Process for Assessing Organizational Investment Capability 1.Integrate RBG capability assessment appraisals with the requirement of the FY 03 National Defense Authorization Act for the Defense Services and specified Agencies to establish Software Acquisition Process Improvement Programs and associated assessments 2.Validate and adopt the Software Engineering Institute CMMI-AM be as the standard IT acquisition capability assessment model for PEO and PM organizations. 3.Each OSD investment gatekeeper develop a process for appraising their Component counterpart organizational capability

6/20/2005RBG Brief to QDR20 Organizational Support for Capability Improvement 1.Adopt a proactive posture for quality management that includes continuous capability improvement throughout the Department and articulate it within the directive system 2.Identify the Quality Management Office within the Office of the Secretary of Defense to serve as the focal point for investment performance excellence 3.Establish a Quality Management Community of Practice

6/20/2005RBG Brief to QDR21 Engender a Trusting Relationship Between Corresponding OSD, JS and Component IT Investment Gatekeepers 1.Implementation of the preceding recommendations supports a trust but verify relationship amongst gatekeeper counterparts –The culture of the Department is one of information hoarding rather than sharing. –Changes in the JCIDS and Acquisition processes that enable decentralization of responsibility engender trust –The RIT Pilot undertook a trust building exercise with capability assessments that resulted in broad publication of the reports –Transformation to a net-centric data sharing environment creates transparency that engenders trust –Component portals are providing investment decision and progress transparency

6/20/2005RBG Brief to QDR22 The full report of the IT Acquisition Management Transformation Rapid Improvement Team (RIT) Pilot Report Blueprint for Establishing Risk-based Governance of IT Investments in a Net-centric Department of Defense is available electronically in the IT Community of Practice at URL: IT Community of Practice

6/20/2005RBG Brief to QDR23 BACK UP

6/20/2005RBG Brief to QDR24 Making Fast Track Feasible by Calibrating RBG with Outcomes PIR ICD (MOEs) CDD (KPPs) CPD Deployment IOC-FOC OT&E JCIDS Analysis FAA*FNA*FSA RBG

6/20/2005RBG Brief to QDR25 Overlay of CCA on JCIDS Existing and Proposed JCIDS Processes for Satisfying CCA JCD Joint Capabilities Document DCR DOTMLPF Change Recommendation ICD Initial Capabilities Document CDD Capability Development Document CPD Capability Production Document PIRD Post Implementation Review Document CPDPIRD Functional Area Analysis Functional Needs Analysis Alternative N Alternative 2 DCR Functional Solution Analysis CDD CPD Alternative 1 Joint Operations Concepts DOTMLPF Analysis (non-materiel Approaches) JCD ICD Joint Operating Concepts Joint Functional Concepts Joint Integrating Concepts Functional Area Analysis Functional Needs Analysis Ideas for Materiel Approaches Analysis of Materiel/ Non-Materiel Approaches Alternative N Alternative 2 DCR Functional Solution Analysis DOD Strategic Guidance CDD CPD Alternative 1 Joint Operations Concepts DOTMLPF Analysis (non-materiel Approaches) JCD ICD Integrated Architectures Post Independent Analysis Facilitates development of measures of effectiveness (MOEs) Contains MOEs BPR Analysis No private or other government organization better performs function Core function need to be performed by government Identifies functional area metrics and submits MOEs Output is capabilities and their associated tasks & attributes IT Architecture PROPOSED Assessment of Outcomes Provides fundamental tasks and measures required for CBA Prioritized COCOM Needs May satisfy MAIS A of Alternatives MISSING Measurement of the MOEs Initiates non- materiel BPR Execution

6/20/2005RBG Brief to QDR26 Post Implementation Review (PIR) in the JCIDS ICD Life Cycle ICD MS AMS B CPD DT&E OT&E MS C TEMP MISSION PERFORMANCE MEASURES PLAN CandidatePIR Information Sources FOT&E Platform Readiness Assessments COCOM Exercise results User Satisfaction Surveys Annual CFO Report Input Mission Readiness Assessments ROI Computation PIR SEP Integration & Test Contract IOC FCB/PSA MOE PIR Build FCB: Functional Capabilities Board ICD: Initial Capabilities Document CDD: Capability Development Document CPD: Capability Production Document CDD