Presentation on theme: "Joint Training Information Management System (JTIMS)"— Presentation transcript:
1Joint Training Information Management System (JTIMS) User Advisory Group (UAG) MeetingLTC Daniel RayJoint Staff J7/JETDJTIMS Program Manager20 March 2012
2JTIMS UAG Agenda 1300 - 1330 Welcome LTC Dan Ray - Program Update - Near-term Development Efforts- Long-term Strategic Planv7.2 Capability Review/Scope Jane WardBusiness Rules Jane Ward- Security Classification- Subordinate Events (TO’s & Forces)- Force RequestsJTIMS JMSEL Dennis CoombsJTIMS JMSEL Strategic Migration LTC Dan Ray/Jane Ward- JTIMS Enterprise- JTIMS LiteStakeholder Open Forum LTC Dan Ray1630 – 1700 JTIMS Issue Deck/Closing Comments LTC Dan RayAgenda for the JTIMS User Advisory Group.
3JTIMS supports the Joint Training System (JTS) JTIMS Login PageKEY FACTSKey Stakeholders – COCOMs, CSAs, JS, OSD, NGB, Services, Coalition PartnersEnables/Enhances the four phases of the JTS – Requirements, Plans, Execution, and AssessmentOver 5,000 unique usersOver 4,500 Joint Training Events managed“Enterprise version” available on the SIPRNet and NIPRNETOffline version available to support disconnect scenarios – JTIMS LiteJTIMSHome Page
4JTIMS Data Integrations KEY INTEGRATIONSJTIMS System-of-Systems IntegrationsDRRS – consume METL; share training assessmentsJCRM – share force requestsUTDT – consume UJTL tasksJLLIS – share observations; search lessons learnedTREX –share Event and TO dataJUM UpdateG-TCSMIS – coordinating future integration requirements with JS J5INTEGRATION BENEFITSDuplicate data entry eliminatedEnhanced data quality for reportsReduced manual entry
5Functional Enhancements JTIMS Near-term Development TimelineFunctional EnhancementsWhere 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 EnhancementsSince 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.
6JTIMS Mission and Technical Benefits MISSION BENEFITSSupports 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 JTSVisibility into all Joint Training Exercises for awareness and effectivenessActionable data for decision support and continuous training improvementsTECHNICAL BENEFITSCost savings through use of open source technologiesRe-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 technologiesLooking toward the future – long-term strategic planning.STAKEHOLDER BENEFITSJTIMS 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.
7Focus Areas over the next 3 years Improve system performance and reliability through the implementation of advanced monitoring tools and focus on refactoring core componentsProvide enhanced real-time data visibility and additional integration partnersFocus 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 informationEnhance infrastructure and architectureDeploy Five Eyes instanceImplement clustered application and DB serversRefactor code as part of scheduled maintenanceEnhance user experienceRefresh user interface for usability and better self service to decrease overall supportContinue implementation of user requests – enhancements and new functionalityThree year plan includes activities scheduled for 7.2 releaseStrategic 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
8Future JTIMS Strategic Initiatives Functional EnhancementsLong-term strategic calendar through the Developers contract period of performance.Architecture EnhancementsOpen requirements will be worked into each software release while implementing strategic initiatives.
9Breakdown 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.
11JTIMS 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.JTIMS1108Modify the order of the Execution sub-actions: CMP, OCT, CSR, etc & add mouse over textJTIMS1284Add Inject #, Observer info, and DTG to OCF. Provide more space between the fields for the user to add details. JTIMS1285Provide 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.JTIMS1432Update 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"JTIMS1540Provide 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 ).
12JTIMS v7.2 Requirements Summary 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. JTIMS1675Remove 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.JTIMS1678Command 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 ).
13JTIMS #0680Ability 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.
14Link inject numbers associated to TPOs JTIMS #1668Link inject numbers associated to TPOsUsers 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
15JTIMS #1668Search InjectsUser 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
16Task Performance Observation Details View JTIMS #1668Task Performance Observation Details ViewAll 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
17JTIMS #1401Display Force Requestor/Force Provider Contact Information and comments where available for all statuses.Force Response for RequirementThe 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
18Forces Change History Query JTIMS #1540Forces Change History Query18
19JTIMS #1540Export Change Log functionality added next to existing ‘View Change Log’ Button19
20JTIMS #1540From the Manage Force Assignments page, Force Providers can select specific events to include in the export.20
22COMBATANT COMMAND VIEW JTIMS #1678COMBATANT COMMAND VIEWDelegate US DoD command Force Requests to subcomponent commands for sourcing.22
23COMBATANT COMMAND VIEW JTIMS #1678COMBATANT COMMAND VIEWForce Provider Review (Delegate)System assigns logged in user as Provider POCSystem returns user to previous screen23
24JTIMS #1678 COMBATANT COMMAND VIEW Manage Force Assignments (US DoD) – Assigned Requirements ViewSystem displays confirmation messageRequirement no longer displays in Assigned viewUser can click View Delegated Requirement link to view delegated requirementsDelegated requirement is moved from the Assigned Requirements Table.24
25COMBATANT COMMAND VIEW JTIMS #1678COMBATANT COMMAND VIEWManage Force Assignments (US DoD) – View Delegated Requirements LinkManage Force Assignments (US DoD) – View Delegated RequirementsRequirement from REMSCOM now displays in Delegated viewDisplays any requirement that the HQ TRANSCOM Force Provider has delegatedUser can click View Assigned Requirement link to return to previous screen25
26SUBCOMPONENT COMMAND VIEW JTIMS #1678SUBCOMPONENT COMMAND VIEWManage Force Assignments (US DoD)Manage Force Assignments (US DoD) – Subcomponent Provider’s ViewDelegated requirement from REMSCOM appears in Subcomponent Force Provider assigned requirementsOnly lists force requirements that have been delegated to own unitSubcomponent Provider may only Respond and Review26
27SUBCOMPONENT COMMAND VIEW JTIMS #1678SUBCOMPONENT COMMAND VIEWForces/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
29JTIMS Business Rules Security Classification Use the JTIMS Classification Module to portion mark JTIMS data.Force RequirementsJoint vs Service EventsJoint Events will display Joint Force ProvidersService Training Events will display the Service Force Providers (FORSCOM, ACC, FFC, MARFORCOM)Subordinate Force RequestsIdentify a Force Provider – when submitted these are sent to the higher headquarters for further review/processing to the Force Provider.Joint Staff Force RequestsJS J3 – selected for all JS J3 force sourcing requirementsJS J7 – selected when Joint Staff Directorate participation is required (J1, J2, J4, J5, J7, J8)
30USSTRATCOM/J73, Joint Plans and After Action Division UNCLASSIFIEDJTIMS-JMSELVersion 7.1.0Enhancements andIssuesThis presentation is UNCLASSIFIEDMr. Dave Coombs,USSTRATCOM/J73, Joint Plans and After Action DivisionUNCLASSIFIED
31UNCLASSIFIEDJTIMS-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
32JTIMS-JMSEL—Pros; continued…. UNCLASSIFIEDJTIMS-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
33UNCLASSIFIEDJTIMS-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 developmentUNCLASSIFIED
34JTIMS JMSEL Strategic Migration DiscussionPhase in JTIMS JMSEL EnterpriseMaintain JMSEL Legacy (2.6) in place until such time that JTIMS JMSEL has demonstrated a definitive successFunding for legacy v2.6 comes out of the overall JTIMS budget (CE2 dollars)Merging JMSEL is directed in the JS IT AssessmentWay aheadMigrate legacy JMSEL v2.6 exercisesDevelop a rigorous JTIMS JMSEL Test PlanTest/validate in medium/large scale exercise (side-by-side)End StateRetire legacy JMSEL v2.6 when stakeholders concur with migration test results.
36Joint Training Information Management System (JTIMS) Joint Master Scenario Event List (JMSEL) Initiated 22 Sep 10Briefer: LTC RayUpdated 23 Feb 12Issue : 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, ServicesBackground: 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 10JUN 11FEB 12MAR 12JUL12SEP 12MAR 13Finalized JTIMS JMSEL application requirements with stakeholdersJTIMS JMSELLegacy datamigrationcapabilityfieldedJTIMS JMSELversion upgradeandfinalize migration timelineTransitionPlan way ahead discussedwith UAGTransitionPlan implementedStatus of implementation briefed to UAGJTIMS JMSELoperational system of record for MSEL development/execution36
37JTIMS Point of Contacts LTC Daniel RayJTIMS Program ManagerJoint Staff J-7Office: (703)DSN:NIPR:SIPR:Ms Jane WardJoint Staff J-7Office: (703)DSN:NIPR:SIPR:Mr. Mark CooneyJoint Staff J-7Office: (703)DSN:NIPR:SIPR:Mr. Joseph MazonOffice: (571)DSN:NIPR:SIPR:Support/ Configuration ManagementNIPR:SIPR: