UJTL CJCSI

1
UJTLCJCSI
Joint Staff J7Mr. Chris Reams
25-27 April 2006
2
Purpose

• The UJTL is a CJCSM
• Not truly directive in nature
• Serves well for its purposes, but not a policy
  document
• Cannot be enforced in the same manner as an
  instruction
• There is a need for a CJCSI to direct policy,
  procedures, and responsibilities for the UJTL
• Rapidly changing environment of Joint Capability
  Areas, Defense Readiness Reporting System and
  Lessons Learned require a structure under which
  the UJTL operates
• Clearly defined policies for use of the UJTL need
  to be written

3
Joint Capability Areas

• Joint Capability Areas have the potential to
  radically change the landscape of the UJTL
• Could lead to a whole new taxonomy
• The UJTL must be preserved in a form that is
  useful to the COCOMS and CSAs for Training and
  Readiness, while remaining flexible enough to
  serve as the basis for new uses (i.e. Lessons
  Learned, Acquisition, etc.)
• A directive can delineate the proper purpose and
  intent of the UJTL.
• Frees CJCSM to contain only tasks conditions and
  measures

4
Directive issues

• A new CJCSI requires input from the UJTL
  user-community
• Strawman currently written and awaiting input

5
Current Issues addressed in draft

• Purpose of the UJTL
• Guidelines for task usage in development of JMETL
• Policy for enforcement of CJCSM 3500.04D
• Joint Capability Areas Taxonomy and Lexicon

6
Discussion

• Do we need a UJTL CJCSI?
• Are we on the right track?
• What other topics and issues do we need?

7
Summary

• Draft UJTL CJCSI is in strawman form now
• J-7 JTD is coordinating with J-7 JETCD on JCAs
• Draft CJCSI enforces policies and procedures
  currently in CJCSM 3500.04D
• Includes much of policy information in the CJCSM
  and now-defunct UJTL Requirements Document

8

• Questions???