1. DRAFT UNCLASSIFIED Ms. Amber Rose USJFCOM UJT OPOC (757) 203-5329 amber.rose@jfcom.mil UJTL Issues/Concerns WJTSC 10-2 Overall classification of this brief is UNCLASSIFIED.

2. DRAFT UNCLASSIFIED UJTL Issues & Recommendations: Staffing Issues and Recommendations  JSAP Staffing Concerns  Planner Level chops: Recommend reverting to black text final copy to show how the task will appear when published  Include AO level adjudication/summary of changes with JSAP  Length of time required to update JDEIS with approved UJT changes  UJTs approved and published in UTDT in Feb 2010 are still not in JDEIS as of August 2010  All UJTs must have a lead agent like joint doctrine.  Pro: Subject Matter Experts in charge of keeping the UJTs current and consistent with doctrine  Cons: Ownership issues and possible inability to be neutral to proposed changes  UJTs should reflect doctrine changes more fluidly  Entire UJTL scrub recommended

3. DRAFT UNCLASSIFIED  Systems that reference the UJTL (JDEIS/UTDT, DRRS, JTIMS, NAVY NTIMS, DRRS-N) do not share information or share outdated information  DRRS is not receiving updates from the UJTL (last push March 09)  Recommend cleanup of master JDEIS list in order (i.e. typos, missing measures, etc.)  JDEIS UJT database display should break out references as a separate data field  This will allow easier updates when new Joint Publications are approved, UJTL Issues & Recommendations: Interoperability Recommendations

4. DRAFT UNCLASSIFIED UJTL Issues & Recommendations: JDEIS  OPOC Designation  Require new JSAP to designate OPOCs with emphasis on roles and responsibilities  OPOC listing (updated) should be posted to the JDEIS UJTL Portal page on both NIPRNET and SIPRNET  Conditions  Issues & Recommendations to be discussed in “Conditions” briefing/discussion

5. DRAFT UNCLASSIFIED UTDT Voting Module:  Need a searchable text file for staffing within the organization for those individuals who are not UTDT users with line numbers which match the voting module document  The document input into UTDT by JS J7 will not match page & line numbers in UTDT  Command OPOCs conducting UJT JSAP adjudications should be able to delete subordinate generated duplicate submitted comments  Presently can only reject them and this increases the workload of the designate JS J7 and UDC adjudicators UJTL Issues & Recommendations: UTDT Functionality Issues/Recommendations

6. DRAFT UNCLASSIFIED OPOC and UDC Recommendations  UJTL Rules and Training/Education  UJTL Development Community (UDC) must understand what is expected and desired when developing/modifying UJTs and the importance  Provide front end analysis (FEA) guidance to ensure task nominations conform to published guidance to reduce UJTL Coordinator workload

7. DRAFT UNCLASSIFIED Non-authoritative components: Measures  Should measures be removed from future UJT JSAPS at both AO and Planner Level?  Pros:  Eliminates lengthy JSAPs  Eliminates adjudication effort  Reduces UTDT clutter  Cons  Subject Matter Expertise lost in creating sample measures  Duplicates may be recommended if measures absent  UC would have to adjudicate  Measures are a place in which UJT submitters may include additional information not allowed in authoritative fields (e.g. systems)  Guidance to develop “standards” would not have proper coordination  Alternate Recommendation: OPOCs do not allow administrative comments on non-authoritative fields

8. DRAFT UNCLASSIFIED Non-authoritative components  Should the ATD portion of UJTs in future JSAPs be removed?  Pros:  Eliminates lengthy JSAPs and attachment issues  Eliminates adjudication effort  Reduces UTDT clutter  Cons  Subject Matter Expertise lost in ATD  Training programs are accredited based on ATD  Alternate Recommendation: Staff certain number of ATD on a constant basis?  Alternate Recommendation: ATD Database?

9. DRAFT UNCLASSIFIED UJT Development Discussion/ Common Issues  Should duplicates be created at every LoW (with duplicate or different verbs) or should one be created at highest level in which could be selected by all commanders?  Remove LoW from UJTL?  One Strategic LoW?  Numbering: How important is numbering to development effort?  Legacy organization and mapping method  Remove Numbering/Numbers from the UJTL?  Functional Categories  Duplicate tasks should not be created across several functional categories that the task could encompass (e.g. intel and ops)?  Could JCAs replace Functional Categories?  Operations vs specific/customized tasks (too broad vs too specific) (e.g. “Perform Dirt Operations” vs “Eat Brown Icky Dirt”

10. DRAFT UNCLASSIFIED Questions? Amber Rose Universal Joint Task Lead/ OPOC amber.rose@jfcom.mil (757) 203-5329 Mike Runnals Government OPOC Alternate michael.runnals@jfcom.mil (757) 203-6008 Thomas Callan JST Task Order Lead (757) 203-7332 thomas.callan.CTR@jfcom.mil Charles Blackmon JST Analyst charles.blackmon.CTR@jfcom.mil (757) 203-5329 Thomas Brennan JST Analyst thomas.brennan.CTR@jfcom.mil (757) 203-6140

11. DRAFT UNCLASSIFIED Additional Task Detail Additional Task Detail (ATD), formerly Joint Task Articles (JTA), serve as frameworks for the identification of capability shortfalls and near-term capability improvements –Non-authoritative and optional Contains processes, procedures, and actions that address critical horizontal (between services) and vertical (service to higher joint force) elements of interoperability for a specific UJT ATDs may bridge service tasks and joint tasks Additional Task Detail (ATD) include the following components: –Critical Elements –Supporting Joint Tasks –Supporting Service Tasks –Supporting Service Doctrine –Optional: Systems View (SV), Operational View (OV) and Architecture View (AV) diagrams –Conditions and Supporting Joint Doctrine have been removed from ATDs