Joint Lessons Learned Program Working Group 29-30 March 2010 LCDR Sam Tanner JS J-7 JLLP Branch
JLLP Brief-back • Purpose: The purpose of the JLLWG is to enhance the US joint capabilities by improving lessons learned (LL) program processes; and contributing to improvements in doctrine, organization, training, materiel, leadership and education, personnel, facilities, and policy (DOTMLPF-P). The purpose of the JLLWG 10-1 breakout sessions targeted specific JLLP issues and the refinement of the draft CJCSM 3150.25. • Discussion: • JLLWG participants received information on the following topics: • The Joint Special Operations Command LL program and Before Action Review process • The FEMA remedial action management program and improving national-level operations • The Interagency LL Program focus on integration with DOD • The Joint Center for International and Security Force Assistance information environment to enable joint, interagency, intergovernmental and multinational users • The USJFCOM issue resolution process and perspective on the ‘change ‘agent’ process • The Peacekeeping and Stability Operations Institute process for data-mining for lessons learned and best practices • Update on the Joint Lessons Learned Information System (JLLIS) • Status of the JLLIS configuration review board • JLLIS is migrating from MCCLL to Fort Huachuca this May. • Accomplished JLLIS user and administrator training
JLLP Brief-back (cont’d) • Break-out Sessions: -- Purpose: Clarify current procedures in the CJCSM to align with the Joint Issue Resolution Tracking Process, LL Information Sharing, and Synchronization of Collection Efforts. -- Discussion:Reviewed, defined, and introduced line-in/line-out specific language to clarify, realign, and build on processes and procedures being established in the CJCSM. Outcome: • Redefined joint corrective action process to the joint issue resolution tracking process. • Established the JLL information sharing process framework and defined common terms of reference. • Defined the use of JLLIS as the tool to capture and synchronize ongoing contingency operation collection efforts. Integrated Operations Training: The group targeted and refined specific processes within the JLLP which support the synchronization of efforts and benefit integrated operations. • Issues: Issue 09-004, Joint Issue Resolution Tracking Process • Issue 06-010, Joint Lessons Learned Information System • Issue 09-005, JTIMS and JLLIS Integration • No new issues to present to the plenary.
Joint Issue Resolution Tracking Process (Joint Corrective Action Process) Briefer: LCDR Tanner • Issue 09-004: Combatant Commands, Services and Combat Support Agencies (CSAs) need a joint issue resolution tracking process, supported by an automated collaboration tool within JLLIS, for tracking resolutions of joint issues generated through the JLLP. • Discussion: In Mar 09 the Joint Lessons Learned Working Group (JLLWG) voted in favor of standing up the sub-working group, the Joint Issue Resolution Working Group (JIRWG) to address this issue. • Combatant Commands, Services and CSAs require a collaborative, transparent process to efficiently resolve issues resultant from exercises and operations. • The Joint Lessons Learned Program (JLLP) defines issues as validated observations that require corrective action but does not provide a process for how joint issues should be resolved in a collaborative environment. • The JLLP, to include thejoint issue resolution tracking process, should support the after action processes specified in DODI 3020.47, DOD Participation in National Exercise Program (NEP). • The proposed joint issue resolution tracking process should capitalize on and use Joint and Interagency established procedures currently in existence. • Endstate: An automated joint issue resolution tracking process integral to the JLLP and JLLIS that provides the ability to collaborate on and resolve joint issues in a transparent and efficient manner with proper authorities identified to approve and execute the recommended corrective action plan. • POA&M: Codify policies and procedures in CJCSM 3150.25, The Joint Lessons Learned Program. • OPRs: JS/J7, NORAD and USNORTHCOM/J7 OCRs: DUSD(P&R), DOD APR 09 MAY 09 MAR 09 AUG 09 JAN11 MAR 10 OCT 09 SEP 10 AUG 10 MAY 10 WJTSC 09-1, JLLWG Charter of JIRWG CJCSM 3150.25 Preliminary Coordination WJTSC 10-1 JIRWG CJCSM Approved WJTSC 10-2 JIRWG JIRWG JIRWG Teleconference JIRWG DCO Session WJTSC 09-2 JIRWG Outbrief To WJLLWG CJCSM Final Coordination
Joint Lessons Learned Information System (JLLIS) AUG 09 JUL 10 SEP 10 MAR 11 MAY 11 OCT 08 MAR 09 JUL 09 POM’D FY09 CRB JLLIS MOA Terminated CRB JLLIS Migrated to Ft Huachuca WJTSC 10-2 Next Generation JLLIS WJTSC 11-1 Briefer: LCDR Tanner • Issue 06-010: The Joint community lacks a single automated support system to discover, apply, share and research joint lessons. • Discussion: The Department of Defense (DOD) Lessons Learned Community lacks a repository capability as well as the input support tools vital to effective knowledge management. • JLLIS is POM’d for FY11-15 • JLLIS is being migrated from MCCLL to Fort Huachuca NLT Jul 2010. • The Joint Lessons Learned Working Group uses the Configuration Review Board (CRB) process to identify and prioritize requirements for incorporation into the JLLIS. • The following have JLLIS: Combatant Commands, Services, National Guard, but not the Coast Guard; some Combat Support Agencies (CSA); the Department of State, United States Agency for International Development and the United States Department of Agriculture; others in education community are TBD. • Endstate: Enterprise, web based, Global Information Grid (GIG) compliant JLLIS with input and management tool, with a federated/distributed database for all JLLIS stakeholders. • POA&M: JLLIS capability using an open architecture is being fielded to Combatant Commands, Services, CSAs, Interagency, and other organizations; JLLIS is GIG-compliant, net-centric, web-services enabled and will be linked to other DOD systems like the Joint Doctrine, Education and Training Electronic Information System; Joint Training Information Management System, and the Defense Readiness Reporting System. • OPRs: JS J-7 JETD, OSD Policy; OCRs: DOD components NOV 09 MAR 10 JTIMS Hyperlink Established WJTSC 10-1 5
JTIMS and JLLIS Integration Briefer: LCDR Tanner Issue 09-005:No capability exists to automatically transfer data between Joint Training Information Management System (JTIMS) and Joint Lessons Learned Information System (JLLIS). Discussion: JTIMS Task Performance Observations (TPOs) may have joint lessons learned applicability. TPOs may identify an issue requiring joint issue resolution; per definitions of the Joint Lesson Learned Program (JLLP), final resolution of an issue would provide a lesson learned, which should be included in the joint lessons learned data base. JLLIS observations may provide additional information to better enable the development of a Training Objective, Training Proficiency Evaluation (TPE) or Training Proficiency Assessment (TPA). DoDI 3020.47 states that each combatant command, CSA, and Military Department (Service) shall determine which performance observations should be elevated in status to a lesson learned, and that these lessons learned should be included in the JLLP through JLLIS. Endstate: Near real-time data integration between JTIMS and JLLIS POA&M: Nov 23, 2009, JTIMS provides capability to nominate observation & evaluation data and export to JLLIS. JLLIS to determine the requirements and develop capability to import JTIMS data. OPR: JS J-7 JETD AUG 09 TBD NOV 09 Brief phased integration process to JLLIS/JTIMS Working Groups Deploy JTIMS v4.0 with export capability to JLLIS Deploy JLLIS import capability of JTIMS Lessons Identified data 6
Joint Assessment – Observations, Best Practices, and Issues Issue 06-007: Consensus has not been achieved in the joint training community regarding how joint training trends and joint training assessment taskers will be achieved. Discussion: JS J7 will develop an annual Joint assessment brief at WJTSC. CJCSI 3500.01E was updated to require monthly Task Proficiency Assessment (TPA) reporting, which will help to support the development of training trend information. CJCSI 3500.01E states it is critical to have a linkage between Joint readiness and training; DRRS requires assessments every 30 days. Therefore it is necessary for JTIMS training assessments to match DRRS 30-day readiness assessment requirements. Endstate: Joint Training Assessments are approved in JTIMS on a monthly basis in accordance with CJCSI 3500.01E and then analyzed and briefed annually. Analysis of assessment data results in the identification of joint training / resource requirements for consideration / validation and advocacy in joint requirement / resource forums; reports to senior leadership; risk mediation forums; policy and doctrinal development; and for potential inclusion in the Chairman's Annual Joint Training Guidance and identification as a Chairman's High Interest Training Issue. POA&M: Establish a Process Action Team/Working Group to define standardized process and select community-wide system for issue tracking and resolution (review best practices and capabilities currently implemented by commands). Develop DoD/CJCS Notice and update existing Policy, Instructions, and Manuals. OPR: JS J-7 JETD; OCR’s: Combatant Commands, CSAs, Services Briefer: LCDR Tanner SEP 09 APR 10 SEP 10 MAR 09 APR – AUG 09 Select FY 08 trends binned to Working Groups and addressed during WJTSC 09-1 Assessment data briefed at WJTSC 10-2; issues linked to JLLIS Establish an Assessment PAT/WG Trends briefed at WJTSC 09-2; issues linked to JLLIS/CAP/etc Trend data collected and analyzed after JTIMS v3.1 release