WJTSC 082 Master Issue Deck Joint Training Assessment

1
WJTSC 08-2Master Issue DeckJoint Training
Assessment Readiness Issues
Pre Conference as of 20 Aug 08
2
Joint Training Assessment and Readiness

• Monthly Training Assessment Update Requirement
• Joint Training Trends and Assessment
• JTIMS Force Requests Units and Individuals
• GFMB Process for Joint Exercises
• Joint Lessons Learned Information System (JLLIS)
  
• Joint Training Program Assessments

2
3
Monthly Training Assessment Update Requirement
Issue 07-019 Inconsistent updates of training
assessments in the Joint Training Information
Management System (JTIMS) Discussion JTIMS is
an integral part of a larger system, including
DRRS, that will identify readiness deficiencies
and help develop solutions. Yet JTIMS data update
requirements do not support timely identification
of deficiencies and issues. Joint training
readiness has been identified as a priority
issue by T2 leadership, and use of JTIMS is being
reviewed as part of the 2007 T2 Block Assessment.
Policy (JTM) states the commanders assessment
will be published as part of the annual JTP. A
recent review indicated that 60 of combatant
command JMET assessments are not published in
JTIMS. Policy also states it is critical to
have a linkage between Joint readiness and
training. Part of the T2 Block Assessment is
examining the linkage between DRRS and JTIMS.
DRRS requires assessments every 30 days whereas
JTIMS doesnt have the same rigor. Therefore it
appears there is a disconnect between training
and overall readiness assessments. The linkage
that will send TPAs and MTAs from JTIMS to DRRS
is the technical part of the solution. WJTSC
08-1 Update JTIMS currently provides the
capabilities to enter and approve assessments.
DRRS currently displays TPAs and will, in the
future, display MTAs. No additional requirements
identified for JTIMS. Endstate JTIMS
assessments will be synchronized with DRRS
requirements to provide a reliable, timely, and
consistent element of the system. CJCS policy
requiring periodic update of JTIMS assessment
data. POAM DRRS currently pulls TPAs from
JTIMS and displays the training assessment data
in the Training Tab of DRRS (Mission Assessment
Module). JS/J-7 revise policy language to
require monthly training assessment updates in
JTIMS. Monitor compliance with monthly
assessment requirement by Combatant
Commands. OPR Joint Staff J7 JETD OCR OSD
(Readiness and Training) / RTPP
FEB - MAR 08
APR 07
APR 08
MAY 08
SEP 08
NOV 07
Adjudicate JSAP Comments
JS/J-7 provided proposed policy update to JTIMS
UAG for review
JS/J-7 staffs Policy change Via JSAP
JTPG Updated
Update at WJTSC 08-2
DRRS displays JTIMS TPA
3
4
Joint Training Trends and Assessment

• 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. The JTPG (CJCSI 3500.01C) stated
  USJFCOM is responsible for annually assessing
  the effectiveness of joint training, to include
  describing emerging training trends in the joint
  community briefing training trends at the
  September WJTSC and reporting results of the
  training assessment to the Chairman. Combatant
  Commands/CSAs will annually provide USJFCOM with
  their joint training trends by 30 June for
  integration into USJFCOMs annual training trends
  brief presented at the September WJTSC.
• Endstate Joint training trends are identified
  and briefed annually.
• POAM JTIMS v2.3 will provide initial Training
  Trends reporting capabilities. Additional
  Training Trend reports capabilities have been
  scoped for JTIMS v2.4. Reassess enhanced
  reporting capabilities during the WJTSC 08-1
  conference. JTIMS v2.4 currently provides
  Training Trends Reporting Capabilities and this
  requirement will be analyzed and reviewed for
  additional enhancements semi-annually. JS J-7
  to brief first Trend Analysis reports during
  WJTSC 08-2.
• OPR JS J-7 JETD

SEP 08
APR 08
MAR 08
OCT 06
JUL 06
MAR 07
OCT 07
MAY 07
MAY 08
Discuss/resolve way ahead at WJTSC 06-2
Feasibility Studies forwarded to DRRS JTIM
PMs for action
Deploy JTIMS v2.4
CJCSI 3500.01E Published with monthly update
requirement
First trend brief at WJTSC 08-2 issues linked to
JLLIS/CAP/JTFCB
Brief v2.4 enhanced Trend Report mockups at WJTSC
08-1
JTIMS Spiral 5 provides TPA archiving.
JTIMS v2.3 upgrade includes Training Trend
capability. Mockups briefed at WJTSC 07-2
Training Trend changes published in JTPG
version 3500.01D
JTIMS Spiral 4 provides TPO/TPE archiving.
Update brief at WJTSC 07-1
4
5
JTIMS Force Requests Units and Individuals
Issue 07-013 A business rule (process) is
needed to enable sourcing of all exercise force
requirements via Joint Training Information
Management System (JTIMS). Discussion USJFCOM
J3 receives and processes force requirements that
sponsoring GCCs are unable to source. Presently,
only units may be inserted and resourced via
JTIMS. Many exercises require specialty skills
(or partial staffs) that cannot be defined as a
unit. These will be referred to as Below UIC
(BUIC) level requirements. Though the current JTM
states that these requirements should be filled
via Service channels, a change has been submitted
to reflect that USJFCOM J3 will assist in
sourcing BUICs. As articulated in the Joint
Training, Policy and Guidance (CJCSI 3500.01D),
Joint Training Manual (CJCSM 3500.03B) and on JS
J7 issue slide 07-006, JTIMS is the system of
record for requesting forces. Multiple GCCs
believe that a business rule (process) should be
established to avoid using disparate systems when
JTIMS can and should serve as the single system
of record for force requests. Endstate
USJFCOM J3 work with stakeholders to establish
straight-forward business rules (process) that
enables all force requirements (unit and BUIC)
via JTIMS. Additionally, USJFCOM J3 develop
JTIMS enhancements to support new process. POAM
Near term Create/address BUIC Business Rules
and capture JTIMS requirements (request combatant
command input). Brief business rules, and scope
any future JTIMS requirements, during the WJTSC
08 conferences. Long term Update 3500.01D and
3500.03B to reflect new Below UIC level (BUIC)
training requirements and established business
rules. JTIMS currently provides the capability to
identify Individual Augmentee Requirements. JTIMS
v3.0 (FY09, Q1) deployment will provide enhanced
IA Force Request/Sourcing capabilities. Issue
remains open until enhanced capabilities are
designed, developed, and deployed. Brief design
concepts during WJTSC 08-2. OPRs JS J7 JETD,
USJFCOM J3.
MAR 08
DEC 07
SEP 08
Brief update to JTIMS UAG during WJTSC 08-1.
Discuss future JTIMS requirements / business rules
JFCOM Submitted change to Joint Training Manual
that enables JTIMS users to request below UIC
support via JTIMS
Brief update to JTIMS UAG during WJTSC 08-2.
Finalize/submit JTIMS requirements / business
rules
5
5
6
Global Force Management Board (GFMB) Process for
Joint Exercises
Submitted by USNORTHCOM

• Issue 08-012 Out-year fidelity of GFMB exercise
  data exported from JTIMS is less than GFMB tool
  calls for.
• Discussion The GFMB process specifies that force
  management data for joint exercises be entered in
  JTIMS and then migrated to the GFMB tool until
  database sharing is functional. However, the
  out-year information available for exercises
  beyond the current Fiscal/Calendar year is, at
  best, only a rough order of magnitude
  representation of what will be needed/deployed
  for a given long-range exercise.
• Planning Endstate GFMB process accounts for
  normal uncertainty in long-range exercise
  calendars.
• POAM
• combatant commands ensure JTIMS is as fully
  populated as practicable to match the GFMB
  planning horizon
• Exercise data is migrated from JTIMS to GFMB tool
• GFMB processes are applied to combatant command
  Joint exercise data
• JTIMS-to-GFMB-tool export capability is
  functional
• GFMB steady-state planning cycle supports force
  management requirements for joint exercises
• Status New Issue.
• OPR JS GFMB OCR JS J7 JETD

. . .
JUN 08
TBD
TBD
SEP 08
TBD
APR 08
TBD
combatant command GFMB Training
JTIMS populated with Joint Exercise data
Brief Issue at WJTSC 08-2
JTIMS data migrated to GFMB tool
Steady State GFMB Exercise process
GFMB Cycle
JTIMS database auto-feeds GFMB tool
6
7
Joint Training Program Assessments
Issue 08-010 Currently no means to inform
CE2T2 leadership of training program impacts and
trends. Discussion Past Block Assessments with
data and analysis by JAEC provided limited
feedback to T2 leadership (snapshot every two
years). Guidance following the 2007 assessment is
to conduct quarterly output assessments at by
combatant commanders and Services, with an annual
enterprise level assessment of outcomes by JAEC.
Leverage available resources, including a process
for collecting data, and many data elements in
JTIMS. Emerging concerns include revising
metrics optimizing data collection including
using existing data sources to supplement JTIMS
including CSAs in assessment. The assessment will
be codified in policy as appropriate. Current
quarterly data submissions continue until new
plan is approved and implemented. Endstate An
enterprise-wide system (tools and processes) that
supports CE2T2 assessment at the strategic level
and the stakeholder level, and is more
transparent. POAM JAEC hosted a workshop 27-28
March 2008, briefed leadership on proposed way
ahead in April. Additional activities are
required. OPR OSD(RT) OCRs JS J-7,
Combatant Command J-7s, Service Trainers, CSAs
MAR 08
SEP 08
APR 08
MAY 08
AUG 08
OCT 08
JUN-JUL 08
Workshop at JAEC
Update at WJTSC 08-2
Present draft assessment concept to leadership
Refine asmt concept
JAEC commence quarterly reporting interim
analysis, progress, trends
Coordinate with Services and combatant commanders
Brief leadership update JSAP guidance (until
policy is published)
8
Joint Lessons Learned Information System (JLLIS)

• Issue 06-010 The Joint community lacks a single
  automated support system to discover, apply,
  share and research joint lessons.
• Discussion The DoD Lessons Learned Community
  lacks a repository capability as well as the
  input support tools vital to effective knowledge
  management. Funding projected to support these
  requirements is inadequate.
• JS alternate funding obtained 4QFY07 there has
  been no funding in FY08.
• Approved POM for FY09-FY13 POM funding is
  inadequate to support further development and
  sustainment costs.
• OSD and / or JS J-5 take lead for Foreign
  Disclosure policy which is unclear and lacks
  standardized implementation across DoD. Varied
  interpretation of current guidance by both the
  combatant commands and Services is a barrier to
  sharing of lessons learned across DoD, the
  Interagency and with Foreign Nationals. This is
  not only a JLLIS issue.
• JLLIS baseline implementation started in Aug 07.
• The following have the JLLIS combatant commands
  All Services to include the NGB but not the USCG
  most of the CSAs and the DOS, USAID and USDA
  and others like the JPME community are TBD.
• CJCSN 3150.25, 22 Jan 08 codified JLLIS as the
  DoD System of Record for the Joint Lessons
  Learned Program.
• Endstate Enterprise, web based, Global
  Information Grid (GIG) compliant JLLIS with input
  and management tool, with a federated/distributed
  database for all JLLIS stakeholders.
• POAM JLLIS capability using an open
  architecture is being fielded to Combatant
  Commands and requesting Services, CSAs,
  Interagency, and other organizations JLLIS is
  GIG-compliant, net-centric, web-services enabled
  and will be linked to other DOD systems as JTIMS,
  JDEIS, and DRRS.
• OPRs JS J-7 JETD, JS J-5, OSD Policy, MCCLL
  OCR USJFCOM/JCOA

APR 07
SEP 09
MAY 09
OCT 08
AUG 07
SEP 07
MAR 08
SEP 08
JAN 08
MAR 09
Pending OSD FD policy document, determine JLLIS
way ahead
CRB
MOA JS/J7 MCLL JCOA
POM funding begins FY09
FY07 CCIF funding approved
CRB
JLLIS IOC
DoD System of Record
CRB
JLLIS FOC
8
CRB