JTIMS V4.0 Mockup Review Administrative Requirements

JTIMS V4.0

Mockup Review

Administrative Requirements

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.

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.

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)

JTIMS #1321

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

User decides to Search Training Objective Library to pre-populate fields on the new TO.

JTIMS #1321


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.

JTIMS #1321

System displays the Search Training Objective (TO) Library page.

User enters the search criteria and selects the Search button to query the Training Objective Templates.


User selects the Training Objective template he/she would like to use to pre-populate TO fields.

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


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.

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.

JTIMS #1321

Performance text from the selected Training Objective template.

Training Situation text from the selected Training Objective template.

Level of Performance text from the selected Training Objective template.


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

JTIMS #1321

Add/Edit Training Objective

The “Save and Return” button will save the Training Objective but will not add any data to the Training Objective Library.


From the JTIMS Welcome page, the User Group Lead selects the Manage Training Objective Library link.

JTIMS #1321

Manage Training Objective Library


Search performed for keywords contained in the Training Objective Template Performance, Training Situation, and Level of Performance fields.

Search performed for a Training Objective template system-generated ID #.

Once the search criteria is entered, the User Group Lead selects the Search button.

Search performed for all Training Objective Templates associated with a specific task.

JTIMS #1321

Manage Training Objective Library - Search


Add New Template link allows UGL to create a new TO Template (Task Number, Performance, Level of Performance, and Training Situation).

User Group Leads can Edit or Remove an existing Training Objective Template.

The last modified by and date will not be system-populated with the name and date the TO Template was created or edited.

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

JTIMS #1321

The User Group Leads can select multiple TO Library templates to remove from the Library.


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.

JTIMS #1321

Create New Training Objective Template


JTP Requirements

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.

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

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.

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

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.

JTIMS #1388


The system will highlight all of the tasks linked to the selected task . User chooses to click the link icon for a different task

User chooses to view TO’s associated with a different linked Task

JTIMS #1388


The system will clear the current highlighting and highlight those tasks associated with the newly selected linked task

User selects to view TO’s associated with a linked Task

JTIMS #1388


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.

User selects to edit data associated with a linked Task or clicks on the View Linked Tasks link.

JTIMS #1388


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


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

User selects to add a TO associated with a linked Task

JTIMS #1388


System displays the confirmation message indicating the location of the linked METs and which METs will be affected by the change.

JTIMS #1388


Clarifying the TO Count for Missions containing linked METs

JTIMS #1388


System will display (hover/mouseover) additional guidance about the Total TO Count and explain how the Mission TO Total Count was calculated.

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.

JTIMS #1388


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.

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

JTIMS #1388


Event Requirements

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.

Provide the ability to classify an Event Name from the Manage Event Names page.

JTIMS #1101


Classify the Overall Event

Event Names are preceded by the Event Name Classification set from the Manage Event Names page

Provide the ability to classify the overall Event when creating a new event.

JTIMS #1101


Update the Event Summary Page to reflect the Overall Event Classification.

JTIMS #1101


Update the Event Description Tab to clearly differentiate between the Overall Event Classification and the Event Name Classification.

JTIMS #1101


Update the Event Details Reports to include a separate “Overall Event Classification” header above the Event Name

JTIMS #1101


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.

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.


JTIMS #1253

System Administrator manages this list


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

Provide User Group Lead and Training Plan Analyst permissions to copy the JMSEL Scenario from one event to another when creating a new event.

JTIMS #1332


JTIMS #1332

Provide System Administrator permissions to copy the JMSEL Scenario and all Injects from one event to another when creating a new event.


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

Modify Radio Selection field identifiers

US Gov’t Participation Requirements

Change Available Funding field to Remarks/Comments free text field (5,000 characters)


JTIMS #1369

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

US Gov’t Participation Requirements - field hover (mouseover) content

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 the reason for the organization’s participation. Include functional area and geographical area of interest.

Identify if funding is available or any additional comments to help facilitate the request.


JTIMS #1369

These are requirements that are coordinated directly by the command with organizations within their AOR (example: US Embassy).

Identify the desired organization.

Identify the specific office (name, code, etc.) within the selected organization of desired participation.

Identify the opportunity or benefit to the Agency, as well as identify the benefit of having agency participation to the command/organization.

Identify the reason for the organization’s participation. Include functional area and geographical area of interest.

Identify if funding is available or any additional comments to help facilitate the request.

US Gov’t Participation Requirements - field hover (mouseover) content


JTIMS #1369

Removed references to Force Requirement and Force Provider

US Gov’t Participation Requirements – Sourcing Interface


JTIMS #1369

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.

JTIMS #1374

Modify the output display of the View All Force Data link.


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.

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.

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.

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.

JTIMS #1374


Master US DoD view in MSWord. System defaults to Landscape Mode

JTIMS #1374


Sample Unfilled Force Requirement in MS Excel.

JTIMS #1374

Sample Sourced Force Requirement in MS Excel.


JTIMS #1386

Requirements

Separate the GEF Classification from the Event classification. Users would like to be able to add GEF Category information (which is classified S information) but not be required to classify the Event. Currently if an Event requires STRATLIFT or has an Event Type which requires a GEF Category, the user is required to enter a GEF Category. GEF Categories require the Event to be classified as Secret.

Allow users to enter GEF Category information but do not require the Event classification to be Secret as a result. Determine a way which will allow the users the ability to add GEF Category information to an Event but hide that data from view of the reports, Event details, and etc.

The Event Details query is the only report which should allow the user to choose whether to display GEF Category/Subcategory information in the output results.

GEF Display Modifications - Event Module – Event Summary Table

Update the GEF Category field to display a “View Category” link.

Remove the GEF Priority field.

Link should only appear if a GEF Category has been recommended or assigned. Otherwise this should show “No GEF Category Assigned”


JTIMS #1386

GEF Display Modifications - Event Module – Event Summary Table

Update the Sort By option to reflect just GEF Category.

Remove the option to sort by GEF Priority.

When the user selects to sort by GEF Category, the system should sort by Category # (& then by the associated Subcategory #).

Link should only appear if a GEF Category has been recommended or assigned. Otherwise this should show “No GEF Category Assigned”


JTIMS #1386

Update the GEF Category field to display a “View Category” link.

When selected displays the Recommended or Assigned GEF Category and Subcategory as shown.

Change title of Popup to reflect “View GEF Category” vs “View GEF Priority”

GEF Display Modifications - Event Module – Event Details Tab – Read Only View

View GEF Category


JTIMS #1386

GEF Display Modifications - Event Module – Event Details Tab – Edit View

If the event requires STRATLIFT or is a CEP, JEP, or TSC then the system will require the completion of the Recommended GEF Categories however the following modifications were made in the Details tab:

Removed the Recommended GEF Priority field. This information is not contained in a separate popup page.

Removed the Security Banner stating the Overall Event Classification must be classified.


JTIMS #1386

When the user selects STRATLIFT Required or an event type of CEP, JEP, or TSC then the system will require the completion of the Recommended GEF Categories.

The system will automatically display a Recommended GEF Category Popup.

Security Classification automatically defaults to Secret due to GEF classification guidance.

Recommended GEF Category

GEF Display Modifications - Event Module – Event Details Tab – Edit View


JTIMS #1386

GEF Category

View Category

GEF Display Modifications - Event Summary Popup Display

Update the GEF Category display to show a hyperlink rather than the two categories.

If no GEF Category as been recommended or assigned the display should reflect “No GEF Category Assigned”


JTIMS #1386

GEF Display Modifications - Event Details Report

Remove the GEF Category and GEF Priority Fields from the Event Details Report


JTIMS #1386

GEF Display Modifications - Event Conference Report

Remove the GEF Category and GEF Priority Fields from the Event Details Report


JTIMS #1386

GEF Display Modifications - Event Details Query

Retain the GEF Category and Subcategory fields in the Data To Output section of the Event Details Query. This will allow the user to generate an event report with the GEF fields if required, and classify the output accordingly.

Change the GEF Priority identifier in the Data to Output to reflect GEF Subcategory

Force Requirements GEF GEF CategoryGEF SubcategoryInclusive Dates


JTIMS #1386

GEF Display Modifications - Force Provider Response

View GEF Category

Link will appear if a GEF Category has been recommended or assigned. Otherwise this should show “No GEF Category Assigned”


JTIMS #1386

Requirements

Add the Primary Event Team Lead and MSEL Manager to the Event Summary and Public View. Names should be hyperlinked so other users can contact.

JTIMS #1393

Public View – Event Summary Table

Add a column to display the Primary Event Team Lead and the Primary MSEL Manager. When the name link is selected the system will display the user’s contact information in a new window. If a MSEL Scenario has been created the system will display the Primary MSEL Manager Name. If the scenario has not been created, the system will display a notice that the MSEL has not been developed yet.


JTIMS #1393

Event Module – Event Summary Table

Add the Primary Event Team Lead and Primary MSEL Manager to the Events Module Event Summary Table.

Display “No Scenario Structure” next to the Primary MSEL Manager if the Event Scenario has not been developed.


JTIMS #1393

Event Module – Event Summary Table

Add the Primary Event Team Lead and Primary MSEL Manager to the Sort By capability.


JTIMS #1393

Event Module – JMSEL Tab

Relocate the Employment Dates to the left

• Display the Primary ETL and Primary MSEL Manager name on the MSEL Tab.

• Display “No Scenario Structure” next to the Primary MSEL Manager if the Event Scenario has not been developed.

• Display the Primary ETL name at the top of the remaining event tabs.

Update the content of the permissions prompt.


JTIMS #1393

Manage Scenarios – My Enrollments

Add a Primary MSEL Manager column. Name link displays the POC contact information in a new window.


JTIMS #1393

Requirements

Add the CSAs to the Force Provider List and enable the capability to send USDoD Force Requirements to the identified email address.

JTIMS #1398

With the exception of DTRA (an existing value in the current list of Providers), there will be no corresponding Recommended Source value(s) for DIA, DLA, NGA, NSA, DISA, and DCMA.


CSA Force Requirements - Force Requirement

JTIMS #1398


CSA Force Requirements - Force RequiremenT

JTIMS #1398

CSA Force Requirements - Force Requirement Summary

Requesting Organization can select to “Send” the CSA Force Requirement to DIA.


JTIMS #1398

Top portion of the page displays the Requestor’s contact information and the Force Request Data.


CSA Force Requirements - Force Provider’s View / Summary

JTIMS #1398

CSA Force Requirements - Force Provider’s View / Summary

Bottom portion of the page displays the Provider’s section. The provider can identify the sourced Unit or Individual(s).


JTIMS #1398

HomeCustom QueriesForces/Participants Summary Query


JTIMS #1398

Execution Requirements

JTIMS #1001

Requirements

Expand the JTIMS JMSEL color palette to allow the selection of more than 70. New capability will provide 200 color selections.

If a color has already been selected, the system will display an X indicating the color is not available for reuse and display a hover message containing information about the entry using that color.

Add a “View colors used by other Cells” link, which displays the cell details as well as colors in use by other cell entries.

If a color has already been selected for another entry within the tab, the system will display an X indicating the color is not available for reuse and display a hover message containing information about the entry using that color.

JTIMS #1001


When the MSEL Manager selects the “View colors used by other Cells” link the system displays the cell details as well as colors in use by other cell entries.

JTIMS #1001


JTIMS #1003

RequirementsRedesign the Status Report layout to maximize space. Move the “Subject” label and value down one row into its own row. Move the “Theme” label and value to align with the left margin. Add a “Storyline/ Thread” label and display the value of the selected Storyline/ Thread in the same row as the Theme.

Add time filters in addition to the day.

Display the Advanced Search criteria options at the top of the Status Report, which indicates the current filters and provide the user the capability to “Clear” the filters within the Status report.

Provide the ability to sort the Status Report by Cell, Classification, Drafter, DTG, Inject Number, Send To, Send From, and Status.

Add Page numbers at the top and bottom of the Status Report.

Persist the pages on the Status Report. System shall return the user to the same page within the status report where they were prior to making the update. For example, the MSEL Manager is on page 7 and updates the status of 2 injects on the page. When the page refreshes with the modifications the system will return to page 7 of the status report.

Provide the user the ability to determine how many injects should display per page. Provide the user the ability to display 5, 10, 25, 50, 100 or All Injects in a single list rather than separated by pages (View All). Default is 25. System retains setting until the user navigates away from the status report.

Provide the ability to view the Implementer for a selected Inject from the Status Report. If no Implementor exists the system will display N/A.

JTIMS #1003

Add time filters in addition to the Day

Redesigned Status Report


JTIMS #1003

User has ability to determine how many injects should display per page. Default is 25. System retains setting until the user navigates away from the status report.


JTIMS #1003


JTIMS #1281

Requirements

Add/Edit Inject. Modify the Search Training Objectives Library results page to display the entire Training Objective when a user performs a search rather than truncating the text.

User clicks Link Training Objective link.

JTIMS #1281


JTIMS #1281

Enter Training Objective search criteria and select the Search button.


JTIMS #1281

System will provide a “more…” link which will display all text associated with the selected Performance, Training Situation, or Level of Performance field.


Manage Scenarios – My Enrollments

Add a Primary MSEL Manager column. Name link displays the POC contact information in a new window.

Change column header of Scenario Class to read “Set Overall Scenario Classification”

JTIMS #1394


Assessment Requirements

JTIMS #1311

Requirements

Provide users the ability to view (read-only) the TPA Details associated with subordinate tasks.

JTIMS #1311

Provide users the ability to view (read-only) the TPA Details associated with subordinate tasks.


JTIMS #1322

Requirements

Training Proficiency Assessments (TPAs) - Provide the user the ability to copy a TPA to other tasks and Missions within the METL structure . The system should allow the user to copy the Approved TPA to another mission task without selecting the "Edit" capability. The capability to Copy a TPA to another Mission / Task should be available from both the Edit and Approve features.

Provide users the ability to copy TPAs from the Edit TPA Details page or directly from a Mission Assessment Summary.

Assessment Home

User selects the TPA to be copied.

JTIMS #1322


The system displays the TPA Details

User clicks the Edit button.

JTIMS #1322


Edit Task Proficiency Assessment (TPA)

User selects the Save and Copy button in order to access the Copy TPA pop-up.

JTIMS #1322


Alternate method for Copy TPA

User selects he Copy link to access the Copy TPA pop-up directly.

JTIMS #1322


Copy TPA Interface

When the user selects a Mission, the MET drop-down box will filter out all invalid Mission Essential Tasks.

or

When the user selects a Mission Essential Task, the Mission drop-down will filter out all invalid Missions.

Defaults to the classification of the original TPA.

Defaults to the TPA rating of the original TPA.

Select the Copy button to perform the Copy TPA function.

JTIMS #1322


(U) Untrained

What data is copied?

• TPA Rating

• TPA Classification

• TPA Issues

– Issue Type

– Issue

– Resolution

– Validation Training Objectives

– HITI

What else happens?

• A new entry is made into the TPA Archive for the selected destination Mission/MET combination in order to archive the TPA data prior to the copy action.

• The status of the new TPA is set to “Unapproved”.

• Last Modified Date of the new TPA is updated to display the current date.

• Last Modified By of the new TPA is updated to display the user who initiated the TPA copy.

• The system returns to the Copy Training Proficiency Assessment pop-up page which will allow the user to copy the same TPA to another Mission/MET or close the pop-up.

JTIMS #1322

Copy TPA Business Rules

STRATLIFT Requirements

JTIMS #0978

Requirement

Provide the Stratlift Manager the ability to view data in the Transportation Tabs and ROM when populating the ROM Worksheet.

View Transportation Requirements

View Transportation Requirements link generates the Transportation Requirements Annual Report for the User Group and Fiscal Year currently being displayed on the ROM Worksheet.

Stratlift Manager needs the ability to view data in the Transportation Tabs and ROM

when populating the ROM Worksheet.

JTIMS #0978


JTIMS #0978

Stratlift Manager needs the ability to view data in the Transportation Tabs and ROM

when populating the ROM Worksheet.


JTIMS #0979

Requirement

Provide the Stratlift Manager the ability to view data in the Transportation Tabs and ROM when populating the ROM Worksheet.

View ROM link generates the ROM Worksheet Report for the User Group and Fiscal Year currently being displayed on the Estimated Actual Worksheet.

View Transportation Requirements link generates the Transportation Requirements Annual Report for the User Group and Fiscal Year currently being displayed on the Estimated Actual Worksheet.

Stratlift Manager needs the ability to view data in the Transportation Tabs and ROM when populating the Estimated Actual Worksheet.

JTIMS #0979


Reports Requirements

JTIMS #1365

Requirements

Reformat the Training Trend Reports to differentiate between which Mission Essential Tasks are pending an assessment (White background) and those tasks that do not apply to a specific mission (Grey background).

Update the METL Training Assessment Report and the Organizational METL Training Assessment Report.

JTIMS #1365

METL Training Assessment Report Tasks are Not Applicable to the selected Mission


JTIMS #1365


JTIMS #1365

METL Training Assessment Report Tasks are Not Applicable to the selected Mission


JTIMS #1365


Documents

JTIMS V4.0 Mockup Review Administrative Requirements