1. Joint Training Information Management System (JTIMS)
User Advisory Group (UAG) Meeting
LTC Daniel Ray
Joint Staff J7/JETD
JTIMS Program Manager
20 March 2012

2. JTIMS UAG Agenda 1300 - 1330 Welcome LTC Dan Ray - Program Update
- Near-term Development Efforts
- Long-term Strategic Plan
v7.2 Capability Review/Scope Jane Ward
Business Rules Jane Ward
- Security Classification
- Subordinate Events (TO’s & Forces)
- Force Requests
JTIMS JMSEL Dennis Coombs
JTIMS JMSEL Strategic Migration LTC Dan Ray/Jane Ward
- JTIMS Enterprise
- JTIMS Lite
Stakeholder Open Forum LTC Dan Ray
1630 – 1700 JTIMS Issue Deck/Closing Comments LTC Dan Ray
Agenda for the JTIMS User Advisory Group.

3. JTIMS supports the Joint Training System (JTS)
JTIMS Login Page
KEY FACTS
Key Stakeholders – COCOMs, CSAs, JS, OSD, NGB, Services, Coalition Partners
Enables/Enhances the four phases of the JTS – Requirements, Plans, Execution, and Assessment
Over 5,000 unique users
Over 4,500 Joint Training Events managed
“Enterprise version” available on the SIPRNet and NIPRNET
Offline version available to support disconnect scenarios – JTIMS Lite
JTIMS
Home Page

4. JTIMS Data Integrations
KEY INTEGRATIONS
JTIMS System-of-Systems Integrations
DRRS – consume METL; share training assessments
JCRM – share force requests
UTDT – consume UJTL tasks
JLLIS – share observations; search lessons learned
TREX –share Event and TO data
JUM Update
G-TCSMIS – coordinating future integration requirements with JS J5
INTEGRATION BENEFITS
Duplicate data entry eliminated
Enhanced data quality for reports
Reduced manual entry

5. Functional Enhancements
JTIMS Near-term Development Timeline
Functional Enhancements
Where we are today in the JTIMS Development Timeline.
We deployed 2 releases since the last JTIMS User Advisory Group Meeting and have 3 updates scheduled through Sep.
Architecture Enhancements
Since 2005, significant strides have been made in achieving the program goals of an enterprise Net-Centric JTIMS application providing data visibility/integration, an integrated set of joint training tools, and global availability on both NIPR and SIPR environments.

6. JTIMS Mission and Technical Benefits
MISSION BENEFITS
Supports full end-to-end lifecycle of the JTS capturing critical information (such as training effectiveness, lessons learned, and exercise funding information)
Responsive to COCOM and Joint Staff functional needs to enhance JTS
Visibility into all Joint Training Exercises for awareness and effectiveness
Actionable data for decision support and continuous training improvements
TECHNICAL BENEFITS
Cost savings through use of open source technologies
Re-usable enterprise components based on open source technologies (full text search, messaging integration, report generation, advanced calendar tool)
Thought leadership with IA Certification and Accreditation (C&A) process for open source technologies
Looking toward the future – long-term strategic planning.
STAKEHOLDER BENEFITS
JTIMS supports: Joint C2 HD/Civil Support Exercises; COCOM Exercises, Combating WMD training; and Security Cooperation/ Engagement.
JTIMS is the software suite that fully supports and implements the four phases of the JTS.
Enables key CJCS Title 10 responsibilities; T2 guidance, & warfighters’ joint training responsibilities.
Integrated with readiness and training systems: DRRS, Force Management Integration Project, UJTL, JLLIS, TSCMIS, and Service systems.

7. Focus Areas over the next 3 years
Improve system performance and reliability through the implementation of advanced monitoring tools and focus on refactoring core components
Provide enhanced real-time data visibility and additional integration partners
Focus on data initiatives starting in Year 2 will be important as the information collected by JTIMS is exponentially growing and will require capabilities to turn data into actionable information
Enhance infrastructure and architecture
Deploy Five Eyes instance
Implement clustered application and DB servers
Refactor code as part of scheduled maintenance
Enhance user experience
Refresh user interface for usability and better self service to decrease overall support
Continue implementation of user requests – enhancements and new functionality
Three year plan includes activities scheduled for 7.2 release
Strategic Efforts are dependent on funding. Need stakeholder support to justify/validate continued funding to enhance the architecture.
Strategic enhancements will enable more effective and efficient support to the DoD Training Transformation initiative while ensuring our Warfighters are ready for live missions

8. Future JTIMS Strategic Initiatives
Functional Enhancements
Long-term strategic calendar through the Developers contract period of performance.
Architecture Enhancements
Open requirements will be worked into each software release while implementing strategic initiatives.

9. Breakdown of All Open 250 Requirements
250 Open Requirements. We will send the full list to the stakeholders for re-validation. This will incorporate our recommendations for sustaining or cancelling OBE requirements.

10. v7.2 Design Concept Review

11. JTIMS v7.2 Requirements Summary JTIMS0680
Allow users the ability to add hyperlink bookmarks in the Events Module. This information should be available in the Event Summary so public users can access the website to obtain additional supporting event data.
JTIMS1108
Modify the order of the Execution sub-actions: CMP, OCT, CSR, etc & add mouse over text
JTIMS1284
Add Inject #, Observer info, and DTG to OCF.  Provide more space between the fields for the user to add details. 
JTIMS1285
Provide the ability for the user to generate a batch Observation Collection Form (OCF) report for each Event.  The user should have the ability to generate the OCF report for 1, many, or all TOs associated to the Event.
JTIMS1401
Display Force Requestor/Force Provider Contact Information.  Include comments where available for those statuses as well.
JTIMS1432
Update the TPO/TPE Report to include the Inject #'s linked/associated with each Training Objective.  Provide the ability to generate a TPO or TPE separately in addition to updating the existing TPO/TPE report.  All reports should include the Inject #'s linked/associated with each Training Objective and should also indicate which Training Objectives have TPOs completed, TPEs completed and which do not - i.e. "No Data"
JTIMS1540
Provide a query capability that would allow a Force Provider the ability to search for (filter) and generate JTIMS force sourcing data.  This report should display the Change Log for a Range of Force Requests within an exercise or selected exercises.   Right now they have to generate the history individually with each force request line item.   An unformatted XLS report of this data would provide Providers data to conduct analysis such as Lead Times for Sending, Acknowledging, and Sourcing.
V7.0 will focus on SMEB modifications, outlined here, and Event Forces enhancements.
SMEB Enhancement: The major enhancement will provide the ETL the ability to generate the SMEB Executive Overview in .ppt format, post the .ppt as an attachment to the event, and notify the SMEB Coordinator (via an ).

12. JTIMS v7.2 Requirements Summary JTIMS1542
JTIMS Lite: Provide the ability to edit imported Training Objectives.
JTIMS1668
Link inject numbers associated to TPO’s. When a user creates a TPO for a Training Objective, the system should display all the linked inject numbers. 
JTIMS1675
Remove the link between HITRs and METs. Currently in JTIMS, when users create HITRs, they have the ability to link it to a task from the UJTL task library or to a MET within the user groups METL.
When users choose to link it to a MET, the system is associating that data to that specific MET.  When changes are made in DRRS to that MET and perpetuated to JTIMS, the corresponding HITR data in JTIMS is affected.  When creating HITRs, the data should NOT be tied to the METL, instead HITRs should be linked to a task.  Users should continue to be able to use the JTIMS METL to find the MET they need but once selected, the system should not reference the MET - but instead should reference the corresponding Task information only.
JTIMS1678
Command Force Providers should be able to delegate force requests sent to their Command to their subcomponents for sourcing. The commands have a requirement to "send" force requirements to their components to source...vs. having the components log into the commands organization. 
V7.0 will focus on SMEB modifications, outlined here, and Event Forces enhancements.
SMEB Enhancement: The major enhancement will provide the ETL the ability to generate the SMEB Executive Overview in .ppt format, post the .ppt as an attachment to the event, and notify the SMEB Coordinator (via an ).

13. JTIMS #0680
Ability to add an external link will be on the Event Module - Attachments/Links tab.
External Hyperlink Information will appear on the Event Details Report and Event Summary Views.

14. Link inject numbers associated to TPOs
JTIMS #1668
Link inject numbers associated to TPOs
Users will also be able to search injects by Inject Number, Subject, and Description (see next slide) Users may link one, multiple or all injects. 14

15. JTIMS #1668
Search Injects
User will search for Inject(s) by Inject Number and/or Keyword Users will be able to select one, multiple or All injects. (All Injects only available for TPOs) 15

16. Task Performance Observation Details View
JTIMS #1668
Task Performance Observation Details View
All associated injects are displayed for each TPO. If there are more than 2 linked injects, a “more” link displays opening a new window which displays all the associated injects. 16

17. JTIMS #1401
Display Force Requestor/Force Provider Contact Information and comments where available for all statuses.
Force Response for Requirement
The Point of Contact Information for the Force Requestor should be displayed for the following statuses: Acknowledged, Not Available, Not Actionable, Sourced and De-Assigned. (existing)
The Point of Contact Information for the Force Provider should be displayed for the following statuses: Acknowledged, Not Available, Not Actionable, Sourced and De-Assigned. (existing)
Comments display for the following statuses: Not Available and Not Actionable. If available, Comments display for the following statuses: Acknowledged, Sourced and De-Assigned. (existing) 17

18. Forces Change History Query
JTIMS #1540
Forces Change History Query 18

19. JTIMS #1540
Export Change Log functionality added next to existing ‘View Change Log’ Button 19

20. JTIMS #1540
From the Manage Force Assignments page, Force Providers can select specific events to include in the export. 20

21. Delegate Force Requirements
JTIMS #1678

22. COMBATANT COMMAND VIEW
JTIMS #1678
COMBATANT COMMAND VIEW
Delegate US DoD command Force Requests to subcomponent commands for sourcing. 22

23. COMBATANT COMMAND VIEW
JTIMS #1678
COMBATANT COMMAND VIEW
Force Provider Review (Delegate)
System assigns logged in user as Provider POC
System returns user to previous screen 23

24. JTIMS #1678 COMBATANT COMMAND VIEW
Manage Force Assignments (US DoD) – Assigned Requirements View
System displays confirmation message
Requirement no longer displays in Assigned view
User can click View Delegated Requirement link to view delegated requirements
Delegated requirement is moved from the Assigned Requirements Table. 24

25. COMBATANT COMMAND VIEW
JTIMS #1678
COMBATANT COMMAND VIEW
Manage Force Assignments (US DoD) – View Delegated Requirements Link
Manage Force Assignments (US DoD) – View Delegated Requirements
Requirement from REMSCOM now displays in Delegated view
Displays any requirement that the HQ TRANSCOM Force Provider has delegated
User can click View Assigned Requirement link to return to previous screen 25

26. SUBCOMPONENT COMMAND VIEW
JTIMS #1678
SUBCOMPONENT COMMAND VIEW
Manage Force Assignments (US DoD)
Manage Force Assignments (US DoD) – Subcomponent Provider’s View
Delegated requirement from REMSCOM appears in Subcomponent Force Provider assigned requirements
Only lists force requirements that have been delegated to own unit
Subcomponent Provider may only Respond and Review 26

27. SUBCOMPONENT COMMAND VIEW
JTIMS #1678
SUBCOMPONENT COMMAND VIEW
Forces/Participants Tab (US DoD)
Forces/Participants Tab (Requestor View)
When a requirement has been delegated, a letter “D” will be appended to the Requirement ID to indicate that it has been delegated.
The Provider value remains the same. The Subcomponent Provider name will not be displayed as the Provider.
Status of delegated force request will display as ‘Acknowledged’ unless the Subcomponent Provider sources it or the Parent Force Provider responds to it (Not Available, Not Actionable, Sourced, De-Assigned). When either of these actions occur, the letter “P” will be appended to the Requirement ID. 27

28. Business Rules

29. JTIMS Business Rules Security Classification
Use the JTIMS Classification Module to portion mark JTIMS data.
Force Requirements
Joint vs Service Events
Joint Events will display Joint Force Providers
Service Training Events will display the Service Force Providers (FORSCOM, ACC, FFC, MARFORCOM)
Subordinate Force Requests
Identify a Force Provider – when submitted these are sent to the higher headquarters for further review/processing to the Force Provider.
Joint Staff Force Requests
JS J3 – selected for all JS J3 force sourcing requirements
JS J7 – selected when Joint Staff Directorate participation is required (J1, J2, J4, J5, J7, J8)

30. USSTRATCOM/J73, Joint Plans and After Action Division
UNCLASSIFIED
JTIMS-JMSEL
Version 7.1.0
Enhancements and
Issues
This presentation is UNCLASSIFIED
Mr. Dave Coombs,
USSTRATCOM/J73, Joint Plans and After Action Division
UNCLASSIFIED

31. UNCLASSIFIED
JTIMS-JMSEL—Pros…
Part of the JTIMS suite—a one stop shop for almost all of your JELC requirements.
JMETs are real-time, current with the DRRS database.
Current Training Objectives easily inserted, created, or linked from the JTP—no copy and paste over—full version of TOs displayed.
All the fields and features of the Version 2.6 stand-alone and then some….
Summary View feature can display all MSELs associated with a given: Training Objective, Theme, JMET, or Storyline.
Manage Scenario function now allows quick access back to the actual database (via JMSEL Overview)
UNCLASSIFIED

32. JTIMS-JMSEL—Pros; continued….
UNCLASSIFIED
JTIMS-JMSEL—Pros; continued….
Can now navigate easily from one common display (Calendar, Concept Map, Status Report, etc.) to another without having to first return to JMSEL Overview.
UNCLASSIFIED

33. UNCLASSIFIED
JTIMS-JMSEL—Issues….
Needs to be evaluated on a large database with (eg, Terminal Fury) records or more.
Reassure COCOM staffs that program will rapidly process and display data.
Will the program slow down if multiple COCOMs are accessing multiple scenarios simultaneously?
Joint Staff needs to specify and guarantee recall and repair times, if the JTIMS server(s) go offline during a major exercise.
Not yet available on SIPRnet on a REL server.
COCOMs cannot have allies directly participate in MSEL development
UNCLASSIFIED

34. JTIMS JMSEL Strategic Migration
Discussion
Phase in JTIMS JMSEL Enterprise
Maintain JMSEL Legacy (2.6) in place until such time that JTIMS JMSEL has demonstrated a definitive success
Funding for legacy v2.6 comes out of the overall JTIMS budget (CE2 dollars)
Merging JMSEL is directed in the JS IT Assessment
Way ahead
Migrate legacy JMSEL v2.6 exercises
Develop a rigorous JTIMS JMSEL Test Plan
Test/validate in medium/large scale exercise (side-by-side)
End State
Retire legacy JMSEL v2.6 when stakeholders concur with migration test results.

35. Issue Review
– JTIMS JMSEL

36. Joint Training Information Management System (JTIMS) Joint Master Scenario Event List (JMSEL)
Initiated 22 Sep 10
Briefer: LTC Ray
Updated 23 Feb 12
Issue : Transition from legacy JMSEL v2.6 to JTIMS JMSEL Enterprise contingent upon system reliability and functionality.
Discussion: Transition plan discussed during JTIMS UAG, WJTSC Legacy JMSEL v2.6 data migration to JTIMS JMSEL (Enterprise); enhanced system availability and support; and costs associated with maintaining a separate JMSEL standalone environment. All commands and Combat Support Agencies agree that community needs to migrate to JTIMS JMSEL (Enterprise) but some expressed concerns that supporting organizations rely heavily on JMSEL v2.6.
Endstate: Complete data migration from legacy JMSEL v2.6 to JTIMS JMSEL (Enterprise); JTIMS failover and backup capabilities deployed, tested and validated; JTIMS JMSEL application enhancements developed and deployed in FY11; and a timeline established, in coordination with commands/agencies, for shut down legacy JMSEL v2.6.
POA&M: JS J-7 develop a timeline and plan to import legacy JMSEL v2.6 data into JTIMS JMSEL (Enterprise); complete hardware/architecture improvements, and complete deployment of JTIMS JMSEL application enhancements in FY12 . Conduct JTIMS JMSEL transition planning and training with stakeholders.
OPR: JS J-7 SP (JETD); OCRs: Combatant Commands, CSAs, Services
Background: The development of training trends was a USJFCOM J7 tasker IAW Joint Training Policy and Guidance (CJCSI C) which assigned responsibility to USFCOM to collect Training Trends from all sources. JS J7 directed JFCOM J7 to conduct a feasibility study on JTIMS and DRRS to determine their possible utility in trend analysis. Feasibility studies were completed and results forwarded to JS J7 (Capt Miller). Study revealed that JTIMS and DRRS (as they currently exist) did not support this task.
Discussion: Capt Melcher met with Capt Miller in Aug 06 to discuss the results of the feasibility studies. Capt Miller acknowledged the results and indicated that this was an issue for the JS J7 and not JFCOM J7.
Resource implications: None Internal POCs: CDR Bob Clark, Capt Chuck Melcher Recommended positions: Undetermined, awaiting guidance/direction from the JS J7 on future trend analysis and JFCOM J7 requirements to support.
OCT 10
JUN 11
FEB 12
MAR 12
JUL12
SEP 12
MAR 13
Finalized JTIMS JMSEL application requirements with stakeholders
JTIMS JMSEL
Legacy data
migration
capability
fielded
JTIMS JMSEL
version upgrade
and
finalize migration timeline
Transition
Plan way ahead discussed
with UAG
Transition
Plan implemented
Status of implementation briefed to UAG
JTIMS JMSEL
operational system of record for MSEL development/execution 36

37. JTIMS Point of Contacts
LTC Daniel Ray
JTIMS Program Manager
Joint Staff J-7
Office: (703)
DSN:
NIPR:
SIPR:
Ms Jane Ward
Joint Staff J-7
Office: (703)
DSN:
NIPR:
SIPR:
Mr. Mark Cooney
Joint Staff J-7
Office: (703)
DSN:
NIPR:
SIPR:
Mr. Joseph Mazon
Office: (571)
DSN:
NIPR:
SIPR:
Support/ Configuration Management
NIPR:
SIPR: