LTC Daniel Ray Joint Staff J7/JETD JTIMS Program Manager 20 March 2012

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 1330 - 1400 v7.2 Capability Review/Scope Jane Ward 1400 - 1430 Business Rules Jane Ward - Security Classification - Subordinate Events (TO’s & Forces) - Force Requests 1430 - 1500 JTIMS JMSEL Dennis Coombs 1500 - 1530 JTIMS JMSEL Strategic Migration LTC Dan Ray/Jane Ward - JTIMS Enterprise - JTIMS Lite 1600 - 1630 Stakeholder Open Forum LTC Dan Ray 1630 – 1700 JTIMS Issue Deck/Closing Comments LTC Dan Ray

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 INTEGRATION BENEFITS • Duplicate data entry eliminated • Enhanced data quality for reports • Reduced manual entry

5. JTIMS Near-term Development Timeline Functional Enhancements 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 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 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 Architecture Enhancements Open requirements will be worked into each software release while implementing strategic initiatives.

9. Breakdown of All Open 250 Requirements

10. v7.2 Design Concept Review

11. JTIMS v7.2 Requirements Summary

12. JTIMS v7.2 Requirements Summary

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 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.

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)

16. Task Performance Observation Details View JTIMS #1668 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.

17. JTIMS #1401 Display Force Requestor/Force Provider Contact Information and comments where available for all statuses.

18. JTIMS #1540 Forces Change History Query

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

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

21. Delegate Force Requirements • JTIMS #1678

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

23. JTIMS #1678 COMBATANT COMMAND VIEW Force Provider Review (Delegate)

24. JTIMS #1678 Delegated requirement is moved from the Assigned Requirements Table. COMBATANT COMMAND VIEW Manage Force Assignments (US DoD) – Assigned Requirements View

25. JTIMS #1678 • COMBATANT COMMAND VIEW Manage Force Assignments (US DoD) – View Delegated Requirements Link

26. JTIMS #1678 SUBCOMPONENT COMMAND VIEW Manage Force Assignments (US DoD)

27. JTIMS #1678 • SUBCOMPONENT COMMAND VIEW Forces/Participants Tab (US DoD)

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. • 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. 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. 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 1000+ (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 • 10-012 – JTIMS JMSEL

36. Joint Training Information Management System (JTIMS) Joint Master Scenario Event List (JMSEL) Issue 10-012: Transition from legacy JMSEL v2.6 to JTIMS JMSEL Enterprise contingent upon system reliability and functionality. Discussion: Transition plan discussed during JTIMS UAG, WJTSC 10-2. 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 Briefer: LTC Ray Updated 23 Feb 12 Initiated 22 Sep 10 OCT 10 JUN 11 FEB 12 MAR 12 JUL12 SEP 12 MAR 13 JTIMS JMSEL Legacy data migration capability fielded Finalized JTIMS JMSEL application requirements with stakeholders Transition Plan way ahead discussed with UAG JTIMS JMSEL version upgrade and finalize migration timeline Transition Plan implemented Status of implementation briefed to UAG JTIMS JMSEL operational system of record for MSEL development/execution

37. JTIMS Point of Contacts LTC Daniel Ray JTIMS Program Manager Joint Staff J-7 Office: (703) 697-1133 DSN: 227-1133 NIPR: daniel.ray@js.pentagon.mil SIPR: daniel.ray@js.smil.mil Ms Jane Ward Joint Staff J-7 Office: (703) 693-4015 DSN: 223-4015 NIPR: jane.ward@js.pentagon.mil SIPR: jane.ward@js.smil.mil Mr. Mark Cooney Joint Staff J-7 Office: (703) 614-8161 DSN: 224-8161 NIPR: mark.cooney@js.pentagon.mil SIPR: mark.cooney@js.smil.mil Mr. Joseph Mazon Joint Staff J-7 Office: (571) 256-4648 DSN: 260-4648 NIPR: joseph.mazon@js.pentagon.mil SIPR: joseph.mazon@js.smil.mil Support/ Configuration Management NIPR: jtimscoord@js.pentagon.mil SIPR: jtimscoord@js.smil.mil