WJTSC 09-2 Aug 2009.  Key Points from Working Group meetings  Flow diagrams  Required Documentation  IMS Example  Way Ahead.

Slides:



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

After Action Report & Improvement Plan (AAR/IP) Elizabeth Jane Tangwall Office of Emergency Preparedness.
Gaining Senior Leadership Support for Continuity of Operations
Process and Product Quality Assurance (PPQA)
PRESENTATION TO THE JOINT RULES COMMITTEE 15 MARCH 2012 ON THE PROGRESS ON IMPLEMENTATION OF THE INDEPENDENT ASSESSMENT PANEL ADOPTED RECOMMENDATIONS ADOPTED.
Directions for this Template  Use the Slide Master to make universal changes to the presentation, including inserting your organization’s logo –“View”
Global Congress Global Leadership Vision for Project Management.
 To facilitate the implementation of employment equity and the communication to employees of matters relating to employment equity and diversity.
UN UNCLASSIFIED 1 DOD Participation Challenges in the National Exercise Program Issue : DOD Participation Challenges in the National Exercise Program.
Introduction to the Joint Capabilities Integration and Development System (JCIDS) CAPT Keith Bowman, Joint Staff, J-8 Hello, I am Captain John Costello.
More CMM Part Two : Details.
Exercises and Training Directorate Integrated Operations Training
IS 700.a NIMS An Introduction. The NIMS Mandate HSPD-5 requires all Federal departments and agencies to: Adopt and use NIMS in incident management programs.
UN UNCLASSIFIED Joint Lessons Learned Program Working Group March 2010 LCDR Sam Tanner JS J-7 JLLP Branch.
State/Urban Area Improvement Planning Conference.
Training for Implementation of CEC§ Creating AA-T and AS-T (SB 1440 Transfer Degrees) Spring 2011 February 1, 2011.
What Is It And How Will We Measure It?
11 A presentation on A-16 Themes for The FGDC Steering Committee June 5, by Wendy Blake-Coleman US EPA Lifecycle Management Work Group.
Release & Deployment ITIL Version 3
April 2, 2013 Longitudinal Data system Governance: Status Report Alan Phillips Deputy Director, Fiscal Affairs, Budgeting and IT Illinois Board of Higher.
Training for Integrated Operations
HQ NORAD and USNORTHCOM JETP Exercise Brief COL Matt Brady N-NC/J71 This Briefing is Classified UNCLASSIFIED.
Agenda 1. Definition and Purpose of Data Governance
1 Contractors on the Battlefield Mr. Gary Motsek Assistant Deputy Secretary of Defense (Program Support) November 12, 2009.
PMP® Exam Preparation Course
Commissioning of Fire Protection and Life Safety Systems Presented by: Charles Kilfoil Bechtel National Waste Treatment Plant Richland WA.
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.
DASD (Plans) Directorate for Interagency Planning and Assessments UNCLASSIFIED.
UNCLASSIFIED Joint and Coalition Warfighting Mr. John Vinett March 2012 Technical Baseline Capability.
DoDI  Review of Para 3 of Encl 3 of DoDI  NEP Exercise After Action Activities  Information Flow  Decision Points.
Organize to improve Data Quality Data Quality?. © 2012 GS1 To fully exploit and utilize the data available, a strategic approach to data governance at.
Capability Cliff Notes Series PHEP Capability 3—Emergency Operations Coordination What Is It And How Will We Measure It? For sound, click on the megaphone.
UN UNCLASSIFIED Chairman’s Exercise Program / National Exercise Program Synchronization Working Group 29 March 2010 LTC Geoff Fuller JS J-7 CEP Branch.
Certification and Accreditation CS Phase-1: Definition Atif Sultanuddin Raja Chawat Raja Chawat.
CJCSM DRAFT OUTLINE II 25 Aug 09
10/16/2015Bahill1 Organizational Innovation and Deployment Causal Analysis and Resolution 5 Optimizing 4 Quantitatively Managed 3 Defined 2 Managed Continuous.
Text. #ICANN49 Data & Metrics for Policy Making Working Group Thursday 27 March 2014 – 08:00.
Apply Project Scope Management Techniques Project Scope Processes – Part 2 Certificate IV in Project Management Qualification Code BSB41507 Unit.
Georgia Institute of Technology CS 4320 Fall 2003.
1 UNCLASSIFIED Integration of Statistics and Metrics into the Lessons Learned Program Operational Plans and Joint Force Development Directorate (J-7),
IRTP Part D PDP WG Items for Review. Items for Review Policy Development Process WG Charter GNSO WG Guidelines.
Project Kick-off Meeting Presented By: > > > > Office of the Chief Information Officer.
D Appendix D.11. Toward Net-Centric Acquisition Oversight A Proposal for an Acquisition Community of Interest (COI) MID 905 Streamlined Acquisition.
Implementation Strategy July 2002 STANDARDS DEVELOPMENT LIFECYCLE PROCESS ORP Publishes & Maintains 8 Standing Committee Recommends Approval / Disapproval.
OMB Circular A-16 Supplemental Guidance (Endorsed) Ivan DeLoatch, Staff Director Lew Sanford Jr. & Wendy Blake-Coleman NGAC Meeting, February 4, 2009.
State of Georgia Release Management Training
UN UNCLASSIFIED US Government Interagency Training Coordinator Working Group 31 March 2010 Mr Gary Quay JS J-7 CEP Branch.
Presented by Eliot Christian, USGS Accessibility, usability, and preservation of government information (Section 207 of the E-Government Act) April 28,
Apply Project Scope Management Techniques Project Scope Processes – Part 2 Week 4 Certificate IV in Project Management Qualification Code BSB41507.
UN UNCLASSIFIED Individual and Staff Joint Training Working Group 29 March 2010 MAJ Bill Coryell JS J-7 Policy Integration Branch.
1 CCSAS Governance An Overview 2007 Annual Child Support Training Conference and Expo September 18, :30 – 12:00.
UNCLASSIFIED Joint Individual Training and Education Program (JITEP) Individual & Staff Joint Training Working Group WJTSC 09-2 CONFERENCE Mr. Herb Warden/Mr.
UN UNCLASSIFIED 1 Issue : Combatant Commanders require a distributed, integrated, synthetic Missile Warning (MW) and Ballistic Missile Defense (BMD)
BSBPMG501A Manage Project Integrative Processes Manage Project Integrative Processes Project Integration Processes – Part 2 Diploma of Project Management.
1 UNCLASSIFIED Welcome to the 2009 Joint Lessons Learned Working Group 25 August 2009 Operational Plans and Joint Force Development Directorate (J-7),
Civilian Casualty Institutionalization Mr. Shelby Ball Joint Staff J7 Joint Lessons Learned Division 21 May 2014 UNCLASSIFIED.
Data Coordinating Center University of Washington Department of Biostatistics Elizabeth Brown, ScD Siiri Bennett, MD.
Joint Forces Command Working Group Brief-Backs
Individual and Staff Joint Training Working Group
CBP Biennial Strategy Review System
Combat Support Agency Working Group
WJLLWG 09-1 JLLIS CRB Items Revalidation for CRB 09-2
Joint Education and Individual Training U.S. Joint Forces Command
TechStambha PMP Certification Training
Description of Revision
CMMI – Staged Representation
CBP Biennial Strategy Review System
GENERAL SERVICES DEPARTMENT Facilities Management Division PROOF –NM (Process Reengineering & Optimization of O&M Functions for New Mexico) Phase II.
Executive Order No. 23 Update Air & Waste Management Association Conference November 16, 2018 Presentation will focus on the latest policy development.
{Project Name} Organizational Chart, Roles and Responsibilities
Presentation transcript:

WJTSC 09-2 Aug 2009

 Key Points from Working Group meetings  Flow diagrams  Required Documentation  IMS Example  Way Ahead

 Need to incorporate existing requirements processes (JCIDS)  Need to develop standard lexicon for Joint Issue Resolution  Exploit previous processes developed for Remedial Action Program (RAP)  Adhere to DoDI , DoD Participation in NEP  Coordinate with other agency corrective action programs, such as DHS CAP  Any compulsory collaboration requires appropriate authorities  Joint issue resolution is applicable above the COCOM/CSA/Service level; each COCOM/CSA/Service will employ local practices/processes/tools to identify and resolve issues at the internal level

 COCOM/CSA/Service resolution programs will transfer issues to joint issue resolution system when applicable  Still undetermined whether advisory group or steering committee is necessary, or whether automated tool would suffice  Question raised whether JLLIS was determined to be the system to support the yet undefined process. JLLIS is the JS system of record for lessons learned. JLLIS is also identified in the DoD instruction for the National Exercise Program (NEP) as the collection mechanism for the DoD after action review. By definition, issue resolution is part of the Joint Lessons Learned Program.

“Bottom-Up”: Issue Resolution starts at lowest level using a transparent and universally accessible common resolution tool, with the ability to elevate issues to higher levels while maintaining resolution efforts at all previous levels Joint, Strategic Internal to COCOM, CSA, or Service Internal to COCOM, CSA, or Service Functional Area Escalation and Increased Collaboration OPR and OCR Assignment, Delegation Interagency DirectorateComponent COCOM, CSA Service GOSC “Top-Down”: Issues initiated at Interagency are presented to GOSC for OPR and OCR assignments; OPR and OCRs solicit input in common tool from appropriate subject matter experts DoD

COCOM, CSA, Service Issue Resolution lead (CoS?) would direct the inclusion of issue into JLLIS as O&R CJCS designated representative collects joint observations, prepares issues, briefs decision authority Decision Authority submits to USD(P) for sharing with Interagency, or submits directly to GOSC for DoD collaboration Issues from Interagency requiring DoD collaboration are submitted to GOSC GOSC representative creates issue resolution template inside joint issue resolution system COCOMs, CSAs, Services assigned as OPR or OCRs collaborate inside joint issue resolution system OPRs and OCRs obtain SME input via internal processes, provide necessary input into joint issue resolution system GOSC approves corrective action completion; OPR updates JLLIS

 Review issues from Operational level (COCOM, CSA, Service)  Determines Validity  Sets Priority  Recommends OPR and OCRs  Briefs CJCS  Opens Joint Issue Resolution Template for approved issues Joint Issue Resolution Executive Steering Committee

DHS NEP ESC includes DASD(HD &DSCA) and CJCS NEP AAR Process USD(P) DHS NEP Improvement Plan (IP) and DHS Corrective Action Program (CAP) E&E sub- PCC, DRG PCC, HSC DC GOSC DoD AAR Process OPR and OCR Assignment and Corrective Action Timeline CJCS DASD (HD&DSCA) ASD(HD&ASA) DHS NEP ESC COCOM, CSA, Service observation submissions GOSC Tracking GOSC Update via CJCS JTIMS JLLIS

12345 Decision Points COCOM, CSA, Service submit issues with joint applicability to JS JLLIS JS (ESC) approves joint issues for formal resolution JS (ESC) routes approved joint issues accordingly DOD issues submitted to GOSC and assigned OPRs/OCRs GOSC approves completion of issues, updates NEP if necessary Issues from NEP requiring DOD action submitted to GOSC

Inclusion of IMS 1.Issues requiring joint collaboration are submitted to JS J7 2.JS J7 (ESC) approves/disapproves 3.JS J7 (ESC) forwards approved issues to GOSC 4.GOSC assigns OCRs as Gatekeepers 5.GOSC representative (JS J7?) assigned as Decision Point 6.Necessary issue resolution collaboration takes place in IMS 7.GOSC determines when issue is closed

Joint Issue Resolution tool would employ standard terminology for various templates : internal resolution at directorate/special staff level : resolution across component of subordinate command (to COCOM or MAJCOM) : resolution across COCOM, CSA, or Service : resolution involving multiple COCOMs, CSA, and/or Services : resolution involving multiple departments or agencies outside DoD Functional Operational Joint Strategic Interagency Functional Joint Operational Strategic Interagency

 CJCSI/CJCSM  Update CJCSI D, JLLLP  Per CJCSI D, an observation isn’t a lesson learned until corrective action implemented and verified to solve deficiency  Create new document  Incorporate CJCSM B, Joint Training Manual, and CJCSI B, Joint Training Policy

 Part of JLLIS  Use a single O&R, or group of O&Rs (via binders) as source documents which can be linked to the created issue  Can apply additional templates while maintaining work done in previous templates  Each additional template increases the breadth of collaboration  Directorate/component/subordinate template  COCOM, CSA, Service template  DoD template

 Aug 09  Provide presentation at Worldwide Joint Training and Scheduling Conference 9-2  Joint Lessons Learned Working Group results  Intent of presentation 1.Define joint process for issue resolution 2.Identify system alternatives (tools) 3.Recommend documentation 4.Recommend way ahead  Document preparation  System configuration

 Draft process into CJCSI/CJCSM  Submit JSAP for review  Determine tool to support process  Two phase implementation  Phase 1: Use of restricted binders or Communities of Practice within JS JLLIS for collaboration following DoD hotwash  Phase 2: Incorporation of tool to collaborate on issue resolution following DoD hotwash  Incorporate Phase 1 for 2009 Hurricane Season and VIGILANT SHIELD 10  Incorporate Phase 2 for ARDENT SENTRY 10

 According to GAO Report on USNORTHCOM Exercise Program:  “We are recommending…the Chairman of the Joint Chiefs of Staff direct the Joint Staff to revise the joint lessons learned operating instruction to include procedures to ensure that corrective actions are implemented and verified in a subsequent exercise or operation before being closed.”

Back-up Slides

UN UNCLASSIFIED Issue : Combatant Commands and Services need an automated collaboration tool for joint issue resolution. Discussion: a. Current process does not provide effective collaboration between combatant commands, combat support agencies (CSA), and Services, with well defined decision points. b. Issues requiring joint resolution do not have sufficient transparency to allow stakeholders to maintain visibility of resolution progress and allow continuous updating of issue through final resolution. c. The Joint Lessons Learned Program (JLLP) defines issues as validated observations that require corrective action. This validated observation does not become a lesson learned until the corrective action is employed and verified to solve the noted deficiency. However, the JLLP does not provide a system for how joint issues should be resolved in a collaborative environment. d. A joint issue resolution system needs to include existing requirements process, such as Joint Capabilities Integration and Development System. e. DoDI , DoD Participation in National Exercise Program (NEP), includes the interaction of the DoD and NEP After Action Review. The DoD process to support this instruction, to include collaboration and information sharing requirements between DoD and the interagency, and use of existing joint tools to enable this process, needs to be codified. Endstate: An automated joint issue resolution system integrated into the JLLP providing the ability for all combatant commands, CSAs, and Services to recommend issues for joint resolution, collaborate on existing issues, and maintain visibility on the progress of all existing issues, with decision points and authorities identified to approve and execute the corrective action plan. This issue resolution system should be compatible with interagency resolution systems, such as the Department of Homeland Security Corrective Action Program. POA&M: OPRs: OCRs: Joint Issue Resolution System TBD 09AUG 09TBD Briefer: Mr Ball