DOTmLPF-P Change Recommendations

Slides:



Advertisements
Similar presentations
Reliability Center Data Request Task Force Report WECC Board Meeting April 2009.
Advertisements

Introduction to the Joint Capabilities Integration and Development System (JCIDS) CAPT Keith Bowman, Joint Staff, J-8 Hello, I am Captain John Costello.
Capabilities and Acquisition Division
Addressing JCIDS Criticism
Lesson Objectives Review Capabilities Development documents and processes for Information Technology and Information Systems IT Box – (current JCIDS manual)
NDIA 15 th Annual SE Conference October 2012 | Page-1 Distribution Statement A – Approved for public release by OSR on 10/09/2012, SR Case # 13-S-0078.
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.
The Information Technology (IT) Box A Primer
CLR 252 Developing KPPs Note from SME:
Submitting a Proposal: Best Practices By: Anu Singh Science Assistant
DoD Acquisition Domain (Sourcing) (DADS) Analysis of Alternatives (AoA) E-Business/SPS Joint Users’ Conference November 15-19, 2004 Houston, TX.
BACKNEXT Georgia State University --- Expenditure Review Executive Summary -- Online Training Online Training for Georgia State University Expenditure.
WJTSC March 2010 JLET Way-Ahead Open Forum Discussion.
UNCLASSIFIED CJCSI Revision Update CAPT Jeff Gernand, J-8 12 November 2002.
Joint Capabilities Integration and Development System (JCIDS) Nov 2010
1 Business Communication Process and Product Brief Canadian Edition, Mary Ellen Guffey Kathleen Rhodes Patricia Rogin (c) 2003 Nelson, a division of Thomson.
D Appendix D.11. Toward Net-Centric Acquisition Oversight A Proposal for an Acquisition Community of Interest (COI) MID 905 Streamlined Acquisition.
Community Resources Assessment Training 4-1. Community Resources Assessment Training 4-2.
MPE – Enabling ALL to securely SEE, DECIDE, ACT MPE - Highlights  Establish Core Implementation Working Group  Build Joining, Membership, and Exiting.
1 BROOKHAVEN SCIENCE ASSOCIATES NSLS-II Beamline Development John Hill NSLS-II Experimental Facilities Division Director PAC Meeting November 20, 2007.
Innovations in Sustaining Weapons Systems DAU Acquisition Community Symposium RDML Jack Prendergast Vice Director of Logistics (J-4) Joint Staff 15 April.
UN UNCLASSIFIED US Government Interagency Training Coordinator Working Group 31 March 2010 Mr Gary Quay JS J-7 CEP Branch.
UN UNCLASSIFIED Individual and Staff Joint Training Working Group 29 March 2010 MAJ Bill Coryell JS J-7 Policy Integration Branch.
HR Policy Updates: Executive Summary
MORS Special Meeting: Risk, Trade Space, & Analytics for Acquisition
Joint Forces Command Working Group Brief-Backs
Lesson Objectives Determine the key Requirements Manager activities leading up to the MDD, the outputs of the MDD, and the Defense Acquisition documents.
The Information Technology (IT) Box A Primer
Requirements Executive Overview Workshop Requirements Management Certification Training Mr. Matt Ghormley.
DOTmLPF-P Change Recommendations
DOTmLPF-P Change Recommendations
Requirements Overview
Requirements Webinar 19 September 2013.
Individual and Staff Joint Training Working Group
DOTmLPF-P Change Recommendations
MDD to Milestone A Requirements Management Activities
Pre-MDD Capability Requirements Analyses
Requirements Management – Certification Training Levels Framework
Information Systems (IS) Capability Requirements: JCIDS Warfighter Information Technology (IT-Box) & Defense Business Systems Sources: CJCSI I,
Pre-MDD Military Capability Analyses
Eric Jefferies Professor, Requirements Management
Combat Support Agency Working Group
2015 JROC / JCIDS Overview and 2015 Updates 14 Jan 2015
Joint Education and Individual Training U.S. Joint Forces Command
Milestone A to Milestone B Requirements Management Activities
Capabilities-Based Assessments (CBAs)
The Information Technology (IT) Box A Primer
Requirements Dept Timeline (2006 – 07)
Performance Management Workday Module
Enterprise Content Management Owners Representative Contract Approval
DOTmLPF-P Change Recommendations
MDD to Milestone A Requirements Management Activities
Information as a Joint Function A Doctrinal Perspective
Joint Doctrine Analysis Division
Project Charter <Project Name>
13 November 2018.
Mission Command Center Excellence Directorate of Training
Mission Command Center Excellence Directorate of Training
The Information Technology (IT) Box A Primer
Defense Logistics: Integrated and Efficient
1915(i)& (k) Implementation Update
Digitization and Modernization Project
Joint DOTmLPF-P Change Recommendations (DCRs)
USMC WARGAMING CAPABILITY
AGCCC Battle Analysis Adjutant General School - Advanced Officer Training Division.
Joint DOTmLPF-P Change Recommendations (DCRs)
JTAMS PRE-MILESTONE B ANALYSIS
Radiopharmaceutical Production
2018 Joint Capabilities Integration & Development System (JCIDS)
JTAMS PRE-MILESTONE B ANALYSIS
Presentation transcript:

DOTmLPF-P Change Recommendations CDR Rob “Rooster” Loughran 23 Jul 2014 1

Objectives Define Joint DCRs and their uses Describe the Joint DCR generation and staffing process Review Joint DCR content and format requirements Describe the Joint DCR implementation process Provide best practices and common pitfalls for DCR drafting, staffing and implementation

DOTmLPF-P Change Recommendations Joint DCRs document and validate non-materiel solutions as an alternative to, or complement of, materiel solutions (JCIDS Manual, 19Jan12) Required when: A non-materiel solution addresses a capability gap A materiel solution requires changes that impact DOTmLPF-P areas outside of the materiel program A material solution exists in the joint force, but must be organic to the sponsor (i.e. cannot be satisfied by an RFF or RFC) ICD DCR CBA, Studies, Lessons Learned, JROC, JIEDDO, etc… DCR

Staffing a DCR Gatekeeper will identify the appropriate FCB (and supporting FCB if necessary) (JCIDS Manual, 19Jan12) One of 4 JSDs will be assigned (change pending in JCIDS manual rewrite) JROC Interest JCB Interest Joint Integration Joint Information

Basic Parameters and Format Maximum Length: 30 Pages, including Appendix A (NR-KPP) Structure Executive Summary: 1 Page (1) Purpose (2) Background (3) Description (4) Analysis Process (5) Joint DCR Findings and Proposed Implementation Plan Recommendation OPR Implementation Timeframe ROM Cost (6) Constraints (7) Policy (8) Issues (9) Recommendation Summary Appendices

Basic Parameters and Format Maximum Length: 30 Pages, including Appendix A (NR-KPP) Structure Executive Summary: 1 Page (1) Purpose (2) Background (3) Description (4) Analysis Process (5) Joint DCR Findings and Proposed Implementation Plan Recommendation OPR Implementation Timeframe ROM Cost (6) Constraints (7) Policy (8) Issues (9) Recommendation Summary Appendices The critical section of a DCR

Approved Alternate DCR Format Provides more logical flow with reduced redundancies Operational Context. Includes former Purpose, Background, part of Description, and part of Appendix A (Architecture Data) Threat Summary. Includes part of Description for the threat environment information and some clarifying verbiage from CJCSI 3312.01 (Intel Certification) Capability Discussion. Includes part of Description and all of Analysis Process Change Recommendations and Implementation Plans. Includes Joint DCR Findings and Proposed Implementation Plans, Constraints, Policy, Issues, part of Recommendations Summary related to recommendations and implementation, and part of Appendix A (Architecture Data) Alternatives. Includes part of Recommendations Summary related to alternative approaches and options More information available at: https://www.intelink.gov/wiki/Joint_Capabilities_Integration_and_Development_System

Approved Alternate DCR Format Provides more logical flow with reduced redundancies Operational Context. Includes former Purpose, Background, part of Description, and part of Appendix A (Architecture Data) Threat Summary. Includes part of Description for the threat environment information and some clarifying verbiage from CJCSI 3312.01 (Intel Certification) Capability Discussion. Includes part of Description and all of Analysis Process Change Recommendations and Implementation Plans. Includes Joint DCR Findings and Proposed Implementation Plans, Constraints, Policy, Issues, part of Recommendations Summary related to recommendations and implementation, and part of Appendix A (Architecture Data) Alternatives. Includes part of Recommendations Summary related to alternative approaches and options More information available at: https://www.intelink.gov/wiki/Joint_Capabilities_Integration_and_Development_System The critical section of a DCR

Section 5, Joint DCR Findings and Proposed Implementation Plan What makes a good DCR? Format and length conforms to JCIDS manual Recommendations: Discrete, actionable tasks Examples Stronger: “Update Joint Pub 3-03 to reflect…” Weaker: “Update joint doctrine to reflect…” OPR Specific organization with oversight or authority over assigned task Stronger: “STRATCOM J7” Weaker: “Combatant Commands” Implementation Timeframe Specific, realistic yet minimized to maintain momentum Stronger: “30 September 2013” Weaker: “FY2013 plus 60 months” ROM Cost Realistic, conservative Myth: DCRs don’t have a cost Section 5, Joint DCR Findings and Proposed Implementation Plan

Implementation of Validated DCRs Approved recommendations from DCR Section 5 become JROC Memo (JROCM) actions Overall lead designated in JROCM; responsible for leading completion of actions with OPRs Functional Capabilities Boards (FCBs) provide oversight of execution Extensions for action deadlines approved by Joint Staff J8 Deputy Director for Requirements via JROCM

Why DCRs Fail in Implementation Common Implementation Failures: OPRs fail to meet suspense dates Actions reported complete, yet intent is not met Causes: Failure to properly review draft DCRs Arbitrary or unrealistic action suspense dates “Lead Organization” fails to lead Recommendations: Sponsor is the Lead Organization POCs for OPRs identified prior to validation and engaged in drafting process Determine suspense dates by developing a POAM for each action Lead Organization forms an implementation working group upon validation Leverage all available resources to complete actions within suspense dates

DCR Help Joint Staff J8 Joint Capabilities Division: JCIDS Process Owners JCIDS Gatekeeper: CDR J.R. Hill, 703-697-9082, jeremy.r.hill.mil@mail.smil.mil DCR Lead: CDR Rob “Rooster Loughran, 703-695-4748, robert.e.loughran.mil@mail.smil.mil Functional Process Owners (FPOs): Provide advice to sponsors during staffing of DCRs; oversee implementation of recommended changes DOTmLPF-P Area Functional Process Owner POC Joint Doctrine Joint Staff/J-7 CDR Todd Glasser, 703-692-7255, todd.s.glasser.mil@mail.mil Joint Organizations Joint Staff/J-8 TBD Joint Training Mr. Mitchell Johnson, 703-695-5436, mitchell.r.johnson.civ@mail.smil.mil Joint Materiel Mr. Fred Gregory, 703-695-4745, frederick.d.gregory.civ@mail.smil.mil Joint Leadership and Education Mr. Jack Roesner, 703-692-7270, john.j.roesner.civ@mail.smil.mil Joint Personnel Joint Staff/J-1 Joint Facilities Joint Staff/J-4 CDR Brett Blanton, 703-571-9780, james.b.blanton.mil@mail.smil.mil Joint Policy Joint Staff/J-5 Mr. Jim Raycraft, 703-695-4752, james.w.raycraft2.civ@mail.smil.mil Functional Capabilities Boards FCB POC Battlespace Awareness Mr. Chris Hall, 703-571-0357, christopher.hall@js.smil.mil C4/Cyber Ms. Becky Gentry, 703-571-9885, rebecca.j.gentry.civ@mail.smil.mil Force Application Mr. Ben Vaught, 703-692-3842, jmaes.b.vaught.ctr@mail.smil.mil Force Support Mr. Joe Coleman, 703-692-3873, joe.t.coleman.ctr@mail.smil.mil Logistics Mr. Rick Gallagher, 703-571-9853, rick.m.gallagher.ctr@mail.smil.mil Protection Mr. Mike Shalak, 703-693-7116, michael.a.shalak.civ@mail.smil.mil KM/DS Help Desk: Mr. Mike Farmer, 703-692-5962, js.pentagon.j8.mbx.km-ds-helpdesk-mailbox@mail.smil.mil

Summary Joint DCRs document and validate non-materiel solutions as an alternative to, or complement of, materiel solutions Joint DCRs follow the standard JCIDS process for staffing (~83 days) 9 Sections (5 Sections for Alternate Format) Maximum 30 pages plus 1 page Executive Summary Critical Section: “Joint DCR Findings and Proposed Implementation Plan” Lead Organization coordinates implementation of validated Joint DCRs with FCB oversight Successful implementation is dependent on comprehensive staffing and a pro-active Lead Organization