O NI

SFS OF

LTC Daniel RayJoint Staff J7/JETD

JTIMS Program Manager20 March 2012

Joint Training Information Management System (JTIMS)

User Advisory Group (UAG) Meeting

O NI

SFS OF

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

O NI

SFS OF

JTIMS supports the Joint Training System (JTS)

KEY FACTSKEY 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

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

3

JTIMS Login Page

JTIMSHome Page

O NI

SFS OF

JTIMS Data Integrations

JTIMS System-of-Systems IntegrationsKEY INTEGRATIONSKEY 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

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 BENEFITSINTEGRATION BENEFITS

Duplicate data entry eliminated

Enhanced data quality for reports

Reduced manual entry

Duplicate data entry eliminated

Enhanced data quality for reports

Reduced manual entry4

O NI

SFS OF

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.

O NI

SFS OF

JTIMS Mission and Technical Benefits

6

MISSION BENEFITSMISSION 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

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

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

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.

O NI

SFS OF

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

O NI

SFS OF

Architecture Enhancements

Open requirements will be worked into each software release while implementing strategic initiatives.

Future JTIMS Strategic Initiatives

Functional Enhancements

O NI

SFS OF

Breakdown of All Open 250 Requirements

O NI

SFS OF

v7.2 Design Concept Review

O NI

SFS OF

JTIMS v7.2 Requirements

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

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

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

Summary

O NI

SFS OF

JTIMS v7.2 Requirements

JTIMS1542 JTIMS Lite: Provide the ability to edit imported Training Objectives.

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

Summary

O NI

SFS OF

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.

O NI

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

JTIMS #1668

O NI

SFS OF

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)

JTIMS #1668

Search Injects

O NI

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

JTIMS #1668

O NI

SFS OF

JTIMS #1401

Display Force Requestor/Force Provider Contact Information and comments where available for all statuses.

O NI

SFS OF

Forces Change History Query

JTIMS #1540

O NI

SFS OF Export Change Log functionality added next to existing ‘View Change Log’ Button

JTIMS #1540

O NI

SFS OF

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

JTIMS #1540

O NI

SFS OF

Delegate Force RequirementsJTIMS #1678

O NI

SFS OF

JTIMS #1678

COMBATANT COMMAND VIEWDelegate US DoD command Force Requests to

subcomponent commands for sourcing.

O NI

SFS OF

JTIMS #1678

O NI

SFS OF

JTIMS #1678

Delegated requirement is moved from the Assigned Requirements Table.

O NI

SFS OF

JTIMS #1678

O NI

SFS OF

JTIMS #1678

O NI

SFS OF

JTIMS #1678

O NI

SFS OF

Business Rules

O NI

SFS OF

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)

JTIMS Business Rules

O NI

SFS OF

JTIMS-JMSELVersion 7.1.0

Enhancements andEnhancements andIssuesIssues

Mr. Dave Coombs,USSTRATCOM/J73, Joint Plans and After

Action DivisionUNCLASSIFIED

This presentation is UNCLASSIFIED

UNCLASSIFIED

O NI

SFS OF

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

UNCLASSIFIED

O NI

SFS OF

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

UNCLASSIFIED

O NI

SFS OF

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

UNCLASSIFIED

O NI

SFS OF

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.

O NI

SFS OF

Issue Review

• 10-012 – JTIMS JMSEL

O NI

SFS OF

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

Finalized JTIMS JMSEL application requirements with

stakeholders

FEB 12

JTIMS JMSEL version upgrade

and finalize migration

timeline

JTIMS JMSEL operational system of

record for MSEL development/execution

MAR 13OCT 10 JUN 11

JTIMS JMSEL Legacy data

migration capability fielded

Updated 23 Feb 12Initiated 22 Sep 10

MAR 12

TransitionPlan way ahead

discussedwith UAG

TransitionPlan implemented

JUL12 SEP 12

Status of implementation briefed to UAG

O NI

SFS OF

JTIMS Point of Contacts

LTC Daniel RayJTIMS Program ManagerJoint Staff J-7Office: (703) 697-1133DSN: 227-1133NIPR: daniel.ray@js.pentagon.milSIPR: daniel.ray@js.smil.mil

Ms Jane WardJoint Staff J-7 Office: (703) 693-4015DSN: 223-4015NIPR: jane.ward@js.pentagon.milSIPR: jane.ward@js.smil.mil

Support/ Configuration ManagementNIPR: jtimscoord@js.pentagon.milSIPR: jtimscoord@js.smil.mil

Mr. Mark CooneyJoint Staff J-7 Office: (703) 614-8161DSN: 224-8161NIPR: mark.cooney@js.pentagon.milSIPR: mark.cooney@js.smil.mil

Mr. Joseph MazonJoint Staff J-7 Office: (571) 256-4648DSN: 260-4648NIPR: joseph.mazon@js.pentagon.milSIPR: joseph.mazon@js.smil.mil