slide1 n.
Skip this Video
Loading SlideShow in 5 Seconds..
JTIMS V4.0 Mockup Review Administrative Requirements PowerPoint Presentation
Download Presentation
JTIMS V4.0 Mockup Review Administrative Requirements

Loading in 2 Seconds...

  share
play fullscreen
1 / 113
Download Presentation

JTIMS V4.0 Mockup Review Administrative Requirements - PowerPoint PPT Presentation

upton-wong
180 Views
Download Presentation

JTIMS V4.0 Mockup Review Administrative Requirements

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. JTIMS V4.0 Mockup Review Administrative Requirements

  2. JTIMS #1321 Requirements Separate the Mission from the actual Training Objective. The system is duplicating the Training Objectives created for the same task because the TO is assigned to different missions. This duplication makes it difficult to search and maintain the TO library. Redesign the Training Objective Library. Make the Training Objective Library a list of Training Objective Templates. Assign a Training Objective Library ID # to each Training Objective Template.

  3. Problem Statement The current Training Objective library is a repository of all of the Training Objectives that exist in JTIMS. A new entry is added to the Training Objectives library whenever a new Training Objectives is created and saved. When updates are made to the Training Objectives, the corresponding Training Objective in the Training Objectives library is also updated. If the user applies the same Training Objectives across multiple missions, a separate instance/duplicate is created in the Training Objectives library for each mission. The resulting Training Objectives library has become unwieldy and difficult to manage. Since a new instance of a Training Objectives is added to the Training Objectives library whenever a Training Objectives is applied to multiple missions, there are many duplicate Training Objectives in the Training Objectives Library. It is difficult for users to locate the appropriate Training Objectives to use when searching the Training Objectives library.

  4. Solution & Business Rules The Training Objective Library will be a repository of Training Objective templates that can be used to pre-populate a standard set of fields when creating a new Training Objective in the JTP or Event. The Training Objective template will consist of the following fields: Task Number, Performance, Level of Performance, and Training Situation. User can search the Training Objective Library, select a template, and the Performance, Training Situation, and Level of Performance template fields will populate the corresponding fields in the new Training Objective page. When a Training Objective template is used to populate the Performance, Level of Performance, and Training Situation fields, updates made to these fields will not update the Training Objective template. Upon saving a new Training Objective the system will provide the user the ability to save the new Training Objective values as a new Training Objective template. If the user selects to add a new Training Objective template, only one instance of the Training Objective template will be added to the Training Objective library, regardless of whether the Training Objective being created is being applied to multiple missions. Only User Group Leads and System Administrators have the ability to edit or remove existing Training Objective templates from the Training Objective library. All other users (with rights to manage Training Objective ’s) only have the ability to add new Training Objective templates to the Training Objective library. To edit or remove an existing Training Objective Library template, the User Group Lead or Sys admin must edit or remove the template from the Manage Training Objective Library administration interface. Each Training Objective template will be assigned a system-generated Training Objective Library Number for easy identification purposes. Areas of Impact (JTP Tab E (Training Objectives), Events (Training Objectives Tab), and Administration (Manage TO Library)

  5. JTIMS #1321 This presentation contains no classified information. Data displayed is for training/test purposes only and is notional data.

  6. JTIMS #1321 User decides to Search Training Objective Library to pre-populate fields on the new TO. This presentation contains no classified information. Data displayed is for training/test purposes only and is notional data.

  7. JTIMS #1321 System displays the Search Training Objective (TO) Library page. The “Search Training Objective Library” pop-up has been redesigned to streamline the filter selection. Users can search internal to their User Group or across all User Groups. The TO Library ID provides the user the ability to search for the Training Objective ID. The Keywords field will search the Performance, Level of Performance, and Training Situation text fields and display results containing the text string in one or more of those fields. User enters the search criteria and selects the Search button to query the Training Objective Templates. This presentation contains no classified information. Data displayed is for training/test purposes only and is notional data.

  8. JTIMS #1321 The Training Objective Template Search Results page. The old Source, Mission, Method-Mode, Theme, and Focus columns have been removed from the template. The Training Objective column has been split into three separate columns (Performance, Training Situation, and Level Of Performance). User selects the Training Objective template he/she would like to use to pre-populate TO fields. This presentation contains no classified information. Data displayed is for training/test purposes only and is notional data.

  9. JTIMS #1321 The user can associate the new Training Objective to multiple missions and adds it to the TO library (see next slide), the system will only add one instance of the TO to the TO library. Performance text from the selected Training Objective template. If the user selects from the TO Library, these fields will be system-populated with the same values as the Training Objective template selected by the user. Training Situation text from the selected Training Objective template. Level of Performance text from the selected Training Objective template. This presentation contains no classified information. Data displayed is for training/test purposes only and is notional data.

  10. JTIMS #1321 Add/Edit Training Objective The “Save and Add to Library” button allows the user to save the following Training Objective data elements as a new Training Objective Template: 1. Task Number 2. Performance 3. Level of Performance 4. Training Situation The “Save and Return” button will save the Training Objective but will not add any data to the Training Objective Library. This presentation contains no classified information. Data displayed is for training/test purposes only and is notional data.

  11. JTIMS #1321 Manage Training Objective Library From the JTIMS Welcome page, the User Group Lead selects the Manage Training Objective Library link. This presentation contains no classified information. Data displayed is for training/test purposes only and is notional data.

  12. JTIMS #1321 Manage Training Objective Library - Search Search performed for all Training Objective Templates associated with a specific task. Search performed for a Training Objective template system-generated ID #. Search performed for keywords contained in the Training Objective Template Performance, Training Situation, and Level of Performance fields. Once the search criteria is entered, the User Group Lead selects the Search button. This presentation contains no classified information. Data displayed is for training/test purposes only and is notional data.

  13. JTIMS #1321 The Training Objective Template Search Results page. The old Source, Mission, Method-Mode, Theme, and Focus columns have been removed from the template. The Training Objective column has been split into three separate columns (Performance, Training Situation, and Level Of Performance). Add New Template link allows UGL to create a new TO Template (Task Number, Performance, Level of Performance, and Training Situation). The last modified by and date will not be system-populated with the name and date the TO Template was created or edited. The User Group Leads can select multiple TO Library templates to remove from the Library. User Group Leads can Edit or Remove an existing Training Objective Template. This presentation contains no classified information. Data displayed is for training/test purposes only and is notional data.

  14. JTIMS #1321 Create New Training Objective Template User Group Lead selects a Task Number and enters a Performance, Training Situation, and Level of Performance (all required fields). Select Save and Return to add the new template to the User Group’s Training Objective Library. This presentation contains no classified information. Data displayed is for training/test purposes only and is notional data.

  15. JTP Requirements

  16. JTIMS #1388 Requirements Identify "mirrored" instances of tasks in the same METL structure. When the same task is linked to multiple parent tasks within the same unit METL, the system needs to indicate to the user that changes made to the task will be applied to all instances of that task within the METL (regardless of the parent task). Currently, when the same task is linked to multiple parents in a unit METL, it is not obvious to the user that changes applied to the task will be applied to all of the tasks within the METL. Determine a way to identify to the users tasks which are copied to multiple parents within the same unit METL. When changes to one task are made, the user should be made aware that those changes will be applied to the other tasks linked to different parents as well and should indicate which tasks those are. Additionally, the Training Objective counts should be updated to accurately reflect which Training Objectives are associated with linked tasks.

  17. Problem Statement When JTIMS receives a unit’s METL from DRRS, there are some instances where identical METs (same description, task number, OPR, S/C’s, GUID, etc) are associated to multiple parents within the same Mission. In DRRS, these METs are referred to as “linked” METs. In JTIMS, when changes are applied to the data associated with a linked MET (Training Objectives (TO), TPAs) each associated linked MET will also reflect this change. It is not apparent to the JTIMS users which METs are linked and therefore which METs will be affected by changes to a particular linked MET. The Total TO count for a Mission does not reflect the sum of the TO counts displayed for each MET within the METL when linked METs exist. The Training Objectives associated with linked METs are only counted once, therefore the total count displayed may differ from the sum of all of the individual MET Training Objective counts. On all TO Count reports, it is not clear to the user why there is a discrepancy between the Mission Total TO counts and the sum of the individual TO counts for each MET. Areas of Impact: JTP > B/C/D - METL JTP > E – Training Objectives Events > Training Objectives Assessment METL View MET details Training Objectives Summary Reports containing TO Counts

  18. Solution & Business Rules Users need a way to easily identify which METs are linked to other METs within the Mission. Provide the ability for the user to quickly identify which METs are linked when viewing a unit’s METL for a specific Mission. Highlight those METs which are linked to one another. Display a warning/alert message to the user when they attempt to make changes a linked MET. Indicate which associated linked METs will be affected by changes to a MET. Provide context sensitive help to the Mission Total Training Objective (TO) Count explaining why it may differ from the sum of TO Counts for each MET within that Mission. Provide additional detail on reports which contain TO Counts that explains why there may be a discrepancy between the Mission Total TO Count and the sum of all of the TO Counts for each MET when there are linked METs.

  19. All linked tasks will display a link icon to the right of the Task Number. The user can click the link icon to highlight all the tasks within the Mission which are linked to each other. Users will be able to edit or view the data associated to a linked MET regardless of where it is located within the Mission METL JTIMS #1388 User chooses to view linked tasks associated with this task With the exception of the first instance in the Mission METL of the linked Training Objective (TO), the TO Count for linked tasks are displayed differently. To edit the TOs associated with this linked task, the user can click any of the TO counts. This presentation contains no classified information. Data displayed is for training/test purposes only and is notional data.

  20. The system will highlight all of the tasks linked to the selected task . User chooses to click the link icon for a different task JTIMS #1388 User chooses to view TO’s associated with a different linked Task This presentation contains no classified information. Data displayed is for training/test purposes only and is notional data.

  21. The system will clear the current highlighting and highlight those tasks associated with the newly selected linked task JTIMS #1388 User selects to view TO’s associated with a linked Task This presentation contains no classified information. Data displayed is for training/test purposes only and is notional data.

  22. System displays the TO Summary for MET page. The system displays a “View Linked Tasks” link which displays the task relationship of each linked task. If the user attempts to perform an add, edit, or remove action for any of the TOs associated with a linked task, the system will display a message informing them that this is a linked task and require confirmation to continue with the action. JTIMS #1388 User selects to edit data associated with a linked Task or clicks on the View Linked Tasks link. This presentation contains no classified information. Data displayed is for training/test purposes only and is notional data.

  23. System displays the following message to the user identifying the task relationships of the linked MET and which METs will be affected by any changes. Once the user selects “OK” the system will navigate back to the page where they can perform the Add, Edit, or Remove TO action. JTIMS #1388 This presentation contains no classified information. Data displayed is for training/test purposes only and is notional data.

  24. The system still provides the capability for users to add TOs to a linked MET regardless of where it is located within the Mission METL JTIMS #1388 User selects to add a TO associated with a linked Task This presentation contains no classified information. Data displayed is for training/test purposes only and is notional data.

  25. System displays the confirmation message indicating the location of the linked METs and which METs will be affected by the change. JTIMS #1388 This presentation contains no classified information. Data displayed is for training/test purposes only and is notional data.

  26. Clarifying the TO Count for Missions containing linked METs JTIMS #1388 This presentation contains no classified information. Data displayed is for training/test purposes only and is notional data.

  27. System will display (hover/mouseover) additional guidance about the Total TO Count and explain how the Mission TO Total Count was calculated. JTIMS #1388 The Mission Total Training Objective count may be different than the sum of all of the TOs for the METs listed below because the number of TOs for each linked* MET is only included once in the total TO count. *A linked MET is a single MET which has been applied to multiple parent tasks within the same Mission. A linked MET may appear multiple times within the same Mission and is identical (e.g., description, task number, OPR, S/C’s, and Training Objective information). Linked METs display a link icon to the right of the MET number. This presentation contains no classified information. Data displayed is for training/test purposes only and is notional data.

  28. All reports displaying the Mission Total TO Count and individual MET counts will have a note in the footer additional guidance about the Total TO Count and explain how the Mission TO Total Count was calculated. JTIMS #1388 “The Mission Total Training Objective count may be different than the sum of all of the TOs for the METs listed for the mission because the number of TOs for each linked MET is only included once in the total TO count. A linked MET is a single MET which has been applied to multiple parent tasks within the same Mission. Linked METs display a link icon to the right of the MET number.” This presentation contains no classified information. Data displayed is for training/test purposes only and is notional data.

  29. Event Requirements

  30. JTIMS #1101 Requirements Provide the ability to classify the Overall Event separate from the Event Name classification. Update the Manage Event Name interface to include a Classification capability/column. Update the Event Summary Page to reflect the Overall Event Classification. Update the Event Description Tab to clearly differentiate between the Overall Event Classification and the Event Name Classification. Update the Event Details Reports to include a separate “Overall Event Classification” header above the Event Name.

  31. Provide the ability to classify an Event Name from the Manage Event Names page. JTIMS #1101 This presentation contains no classified information. Data displayed is for training/test purposes only and is notional data.

  32. JTIMS #1101 Provide the ability to classify the overall Event when creating a new event. Classify the Overall Event Event Names are preceded by the Event Name Classification set from the Manage Event Names page This presentation contains no classified information. Data displayed is for training/test purposes only and is notional data.

  33. Update the Event Summary Page to reflect the Overall Event Classification. JTIMS #1101 This presentation contains no classified information. Data displayed is for training/test purposes only and is notional data.

  34. Update the Event Description Tab to clearly differentiate between the Overall Event Classification and the Event Name Classification. JTIMS #1101 This presentation contains no classified information. Data displayed is for training/test purposes only and is notional data.

  35. Update the Event Details Reports to include a separate “Overall Event Classification” header above the Event Name JTIMS #1101 This presentation contains no classified information. Data displayed is for training/test purposes only and is notional data.

  36. JTIMS #1253 Requirements Provide a Significant Military Exercise Brief (SMEB) Quick Reference capability, which will display a list of all locations requiring a SMEB. Provide the System Administrator the ability to update/maintain the SMEB library reference list.

  37. JTIMS #1253 Provide a Significant Military Exercise Brief (SMEB) Quick Reference capability, which will display a list of all locations requiring a SMEB. When the user selects the link, the system displays the .pdf file posted by the JS J7 Administrator. This presentation contains no classified information. Data displayed is for training/test purposes only and is notional data.

  38. JTIMS #1253 System Administrator manages this list This presentation contains no classified information. Data displayed is for training/test purposes only and is notional data.

  39. JTIMS #1332 Requirements Copy Events: Event Copy action should not allow a user to copy "Injects" from one event to another. Provide User Group Lead and Training Plan Analyst permissions to copy the JMSEL Scenario from one event to another when creating a new event. Provide the System Administrator the ability to copy the Scenario data or all Inject data from one event to another when creating a new event (similar to JMSEL v2.6 business rules).

  40. JTIMS #1332 Provide User Group Lead and Training Plan Analyst permissions to copy the JMSEL Scenario from one event to another when creating a new event. This presentation contains no classified information. Data displayed is for training/test purposes only and is notional data.

  41. JTIMS #1332 Provide System Administrator permissions to copy the JMSEL Scenario and all Injects from one event to another when creating a new event. This presentation contains no classified information. Data displayed is for training/test purposes only and is notional data.

  42. JTIMS #1369 Requirements Change the US Gov't Participation Interface field identifier "Federal" to reflect "Federal (Headquarters)" with mouseover definition: These are requests that are submitted to JS J7 for sourcing from non-DOD USG Federal Department and Agency Headquarters in the Washington, D.C. area (example: DoS, Bureau of Near Eastern Affairs). Change the US Gov't Participation Interface field identifier "Federal" to reflect "Federal (within AOR)" with mouseover definition: These are requirements that are coordinated directly by the command with organizations within their AOR (example: US Embassy). Modify the Available Funding field to reflect Remarks and make this a free text field (500 characters).

  43. JTIMS #1369 US Gov’t Participation Requirements Modify Radio Selection field identifiers Change Available Funding field to Remarks/Comments free text field (5,000 characters) This presentation contains no classified information. Data displayed is for training/test purposes only and is notional data.

  44. JTIMS #1369 US Gov’t Participation Requirements - field hover (mouseover) content These are requests that are submitted to JS J7 for sourcing from non-DOD USG Federal Department and Agency Headquarters in the Washington, D.C. area (example: DoS, Bureau of Near Eastern Affairs). Identify the reason for the organization’s participation. Include functional area and geographical area of interest. Identify the opportunity or benefit to the Agency, as well as identify the benefit of having agency participation to the command/organization. Identify the desired organization. Identify the specific office (name, code, etc.) within the selected organization of desired participation. Identify if funding is available or any additional comments to help facilitate the request. This presentation contains no classified information. Data displayed is for training/test purposes only and is notional data.

  45. JTIMS #1369 US Gov’t Participation Requirements - field hover (mouseover) content These are requirements that are coordinated directly by the command with organizations within their AOR (example: US Embassy). Identify the reason for the organization’s participation. Include functional area and geographical area of interest. Identify the opportunity or benefit to the Agency, as well as identify the benefit of having agency participation to the command/organization. Identify the desired organization. Identify the specific office (name, code, etc.) within the selected organization of desired participation. Identify if funding is available or any additional comments to help facilitate the request. This presentation contains no classified information. Data displayed is for training/test purposes only and is notional data.

  46. JTIMS #1369 US Gov’t Participation Requirements – Sourcing Interface Removed references to Force Requirement and Force Provider This presentation contains no classified information. Data displayed is for training/test purposes only and is notional data.

  47. JTIMS #1374 Requirement Modify the View All Force Data link to separate Force / Participation Types. Provide the ability to generate for USDoD and US Gov't a separate table for Unfilled requirements and Sourced requirements in MSExcel, as well as generate a complete summary view (which includes both requirement tables) in MSWord.

  48. JTIMS #1374 Modify the output display of the View All Force Data link. This presentation contains no classified information. Data displayed is for training/test purposes only and is notional data.

  49. JTIMS #1374 Update the View All Force Data link to separate the types of Force and Participation Requirements. Allow the user to generate a master view in MSWord and individually by Table in MSExcel. US DOD should be separated into two tables; one for Unfilled Requirements and one for Sourced Requirements. This presentation contains no classified information. Data displayed is for training/test purposes only and is notional data.

  50. JTIMS #1374 Update the View All Force Data link to separate the types of Force and Participation Requirements. Allow the user to generate a master view in MSWord and individually by Table in MSExcel. US GOVT should be separated into two tables; one for Unfilled Requirements and one for Sourced Requirements. This presentation contains no classified information. Data displayed is for training/test purposes only and is notional data.