graduate training integration management system (gtims) · 2017-05-23 · may 19, 2017 document #...
TRANSCRIPT
May 19, 2017 Document # GTIMS 17-052
Northrop Grumman Corporation (NGC)
Graduate Training Integration Management System (GTIMS)
Version 1.7.33.1 Release Notes
1
TABLE OF CONTENTS
Table of Contents
1. GTIMS CONTENT FOR TMS VERSION 1.7.33.1 ............................................................................................... 4
1.1. AETC (KC-46 INTEGRATION SUPPORT) ENHANCEMENT REQUEST ........................................................................ 4
1.1.1. ER16542 KC-46 ATS STUDENT RECORD EXCHANGE ....................................................................... 4
1.2. USAACE ENHANCEMENT REQUEST ............................................................................................................... 5
1.2.1. ER16659 REMOVE LEGACY COMPONENTS FROM GTIMS .............................................................. 5
2. GTIMS CONTENT FOR TMS VERSION 1.7.33 .................................................................................................. 7
2.1. AMC ENHANCEMENT REQUESTS ................................................................................................................... 7
2.1.1. ER 15064 – INSPECTIONS AND TRENDS - DATA WIDGET - S/E GRADESHEET COMMENTS ............. 7
2.1.2. ER 15176 - ADD VIRTUAL COLUMN IN GNG................................................................................... 7
2.1.3. ER 15454 - CREATION, SIGNING, PRESERVATION, AND DISPLAY OF GROUP NMR LETTER ............. 8
2.1.4. ER 15761 - ENHANCEMENT REQUEST - EXECUTING INDIVIDUAL SCHEDULE LINES ...................... 10
2.1.5. ER 15843 - INSPECTIONS AND TRENDS WAIVER WIDGET ONLY SHOWS TBT WAIVERS ............... 11
2.1.6. ER 15976 - UNIT INTERFLY ORG SELECTION ................................................................................. 11
2.1.7. ER 16000 - WAIVER MANAGEMENT NEEDS TO ALLOW ATTACHMENTS ...................................... 12
2.1.8. ER 16203 - ARMS REQUIREMENT TRACKER (CUSTOM FILTER SAVE LAYOUT) .............................. 12
2.1.9. ER 16211 - BEANS DISPLAY CURRENCY INDICATOR ON SUMMARY TAB ...................................... 13
2.1.10. ER 16220 – INTEGRATION MISSIONS FROM SCHEDULE MODULE WITH TASK BASED TRAINING . 14
2.1.11. ER 16318 - ARMS INTERFACE - ABILITY TO PUSH “ZERO ACCOMPLISHED” TO ARMS FROM
DOTSHEETS ................................................................................................................................................. 15
2.1.12. ER 16397 SUPPORT MEIS 4 DEVELOPMENT WORK ...................................................................... 15
2.1.13. ER 16520 - ARMS ROLLOVER OVERWRITING HISTORICAL DATA – ALLOW FOR MANUAL CONTROL
FOR WHEN ROLLOVER OCCURS .................................................................................................................. 16
2.2. AMC FLEX CONTENT ................................................................................................................................ 17
2.2.1. ER 14658 - TASK-BASED TRAINING GRADING MODULE ENHANCEMENTS- ADD FILES AT
TEMPLATE TASK LEVEL ................................................................................................................................ 17
2.2.2. ER 15168 - FILTER NEEDED FOR FLIGHT AUTHORIZATION DUTY CODE ........................................ 18
2
2.2.1. ER 15392 - TBT TIME LOGGING MODIFICATION .......................................................................... 18
2.2.2. ER 15425 - TRAINING WAIVER ACKNOWLEDGEMENT ................................................................. 18
2.2.3. ER 15723 – 129 – AMC SME CONF 2015-09 -USER REQUESTS THE ABILITY TO LAUNCH CLICKONCE
CLIENT FROM DESKTOP .............................................................................................................................. 19
2.2.4. ER 15995 - CHANGE ORGANIZATION SCHEDULE VIEW ................................................................ 19
2.2.5. ER 16244 - ADD INCORRECT DATE WARNINGS TO STANEVAL STATUS PAGE ............................... 20
2.2.6. ER 16253 - ENHANCEMENT REQUEST - ARMS REQUIREMENT TRACKER (EXCEL EXPORT)............ 20
2.2.7. ER 16277 - ARMS REQUIREMENTS TRACKER - CHANGE APPROACH TO BEANS COLORATION ..... 21
2.2.8. ER 16309 - LETTER OF XS - HIGHLIGHT CHANGES ON FTL COLUMN ............................................. 21
2.2.9. ER 16315 - EVENT NOTIFICATION EDITOR - ADD ADDITIONAL FORM 4324 NOTIFICATION.......... 21
2.2.10. ER 16363 - TBT LOAD TEMPLATES – EDITING .............................................................................. 22
2.2.11. ER 16383 - WAIVER SETUP/MANAGEMENT ENHANCEMENT REQUEST ....................................... 22
2.2.12. ER 16447 - 4324 - CHANGE SIGNATURE REQUIREMENT .............................................................. 22
2.2.13. ER 16452 ARMS INTERFACE - ADD "ARMS LAST SUCCESSFULLY UPDATED" APP TO OPS
MANAGER .................................................................................................................................................. 22
2.3. AETC FLEX CONTENT ............................................................................................................................... 23
2.3.1. ER 16266 - ADD FILTER TO MOST SUPERVISORY DISPLAYS .......................................................... 23
2.3.2. ER 16543 - USER REQUESTS A 4293 ENHANCEMENT TO ALLOW AT LEAST 6 PEOPLE TO DIGITALLY
SIGN 4293'S, CURRENTLY LIMIT IS 3 PEOPLE ............................................................................................... 24
2.3.3. ER 16544 - STAN EVAL SIGNATURE STATUS PAGE ENHANCEMENT REQUEST .............................. 24
2.4. ACC FLEX CONTENT ................................................................................................................................. 25
2.4.1. ER 16071 - FLIGHT RECORD NEEDS TO BE MODIFIED TO HANDLE TWO FIELDS WHICH ARE USED
BY THE RPAS ............................................................................................................................................... 25
2.4.2. ER 16458 - PUSH OF RPA SPECIFIC FLIGHT RECORD DATA LRE AND MCE TO ARMS ..................... 25
2.5. USAACE ENHANCEMENT REQUESTS ............................................................................................................ 25
2.5.1. ER 14462 – ENHANCEMENT TO THE ARMY STANDARD GRADESHEET ......................................... 25
2.5.2. ER 14463 – ENHANCEMENT TO ACADEMIC ROSTER FOR OVERALL GRADES ................................ 26
3. ENHANCEMENT REQUESTS/DISCREPANCY REPORTS .................................................................................. 26
3.1. GTIMS 1.7.33.1 ER LIST ........................................................................................................................ 26
3.2. GTIMS 1.7.33 ER LIST ........................................................................................................................... 27
3
3.3. GTIMS 1.7.33.1 DR LIST ........................................................................................................................ 28
3.4. GTIMS 1.7.33 DR LIST ........................................................................................................................... 29
4. DATABASE .................................................................................................................................................. 30
4
1. GTIMS CONTENT FOR TMS VERSION 1.7.33.1
SUMMARY
TMS version 1.7.33.1 includes the following additional issue resolutions discovered in previous releases.
DR16624 - Manual Flight Record Issue
DR16649 - ARMS Requirement Tracker Excel Export Icon Distortion
DR16685 - Task Based Training Grading – Reviews – Center Slider between Review Signoff and TraineeSignoff text boxes
DR16686 - Differentiate Between Icons for Click Once Clients
DR16687 - Add a ‘not editable’ warning level to the TBT Attachment Enhancement
DR16696 - Organization for Person Resources Display as N/A in Personnel Management
DR16698 - Change information icon in TBT Grading when the original completion date is different
DR16699 - Alter Last ARMS Retrieval Date Text
DR16708 - Gradesheet Details Display Issue
DR16729 - Start Menu Launches VB Version of Timeline App
DR16730 - GNG Status – Filter Combo is too Narrow Making it Impossible to See Differences in Orgs and isnot Ordered
DR16740 - Qual Mgr – Qual Levels Dialog Issues
DR16741 - Qual Mgr –Edit Qual Activity dialog hides Quantity and Expiration drop down is Scrunched
DR16742 - Qual Mgr –Add/Edit Qual Dialog Issues
DR16743 - Qual Mgr –Grids Use Nonstandard Way of Forcing Initialized Row that Caused a SmotheredException
DR16744 - Qual Mgr –Qual Def Date
DR16745 - Qual Mgr –Add/Edit Qual Does Not Require Abbreviation
DR16773 - AF781 Report Back Page has Text that Overlaps
1.1. AETC (KC-46 INTEGRATION SUPPORT) ENHANCEMENT REQUEST
1.1.1. ER16542 KC-46 ATS STUDENT RECORD EXCHANGE
ER Description: Transfer student data from standalone KC-46 databases to the AMC Enterprise database
and vice/ versa.
Administrative personnel should have the ability to choose students and data sets for transfer, and be
able to perform the transfer procedure.
The Personnel Transfer Tool has been created to facilitate transfer of students between training
organizations. The tool contains three tabs; one for exporting, one for importing, and one for viewing
logs.
Exporting is done by selecting personnel to export and a location to save the encrypted file. The file
contains personal information, training jacket and syllabus data, Stan/Eval data, and task based training
data. The file will also contain any reference data needed to maintain data integrity for the selected
personnel. Once personnel have been exported, they are deactivated in the system and moved to the
TRANSFERORG organization to prevent accidental changes from occurring that would cause data
synchronization issues.
Note: Exporting large numbers of individuals or individuals with extensive training records can be a
lengthy process.
Exported files may be stored on the local operating system, shared network drive, or removable media,
and transmitted through approved means between points. Approved means is determined by the
information security chain of command.
5
Importing is done by selecting a file to import. Files may only be imported once, though personnel can
be transferred back and forth between systems multiple times by exporting to a new file for each move.
Logs may be viewed by a selected date range. Imported Personnel may be assigned to a new
organization during import.
A setting available only in the Personnel Transfer Tool allows administrative users to specify the
certificate thumbprint. The certificate thumbprint is the identifier of the certificate that will be used by
the system to encrypt and decrypt the exported file. This should be the same certificate used by all
parties expecting to export/import data. The certificate used is not provided with the software, but
must be issued by a certificate authority that all parties can trust and authenticate. This certificate must
be installed on all servers where the GTIMS application service runs, and permission to access the
certificate must be granted to the service account that runs the GTIMS application service.
Notes:
The importing and exporting database must be on the same GTIMS baseline.
PII is transferred. Data media for transfer should be protected accordingly.
Database size will grow as supporting reference data from other organizations enters the
importing database. This data will not affect day to day operations, but is required to fully
describe the transferred personnel’s training history
Task Based Training data viewing requires at a minimum the “Task-Based Training Grading View”
permission for the organization that conducted the training. The data would not be visible
otherwise.
Only the current syllabus is transferred; other copies/ versions remain in the originating
database.
Current assigned tests for personnel are listed, but may not be accessible. To access the test,
the test must reside on the importing system; the transfer tool does not transfer anything but
completed test to ensure that unapproved tests are not transferred in error.
New reference/lookup data may be imported with personnel data. Any open applications
(other than the transfer tool) will not pick up this new reference data. Attempting to work with
an imported person without refreshing the lookup data may cause errors. Close and reopen any
applications before working with imported personnel.
Imported personnel will need roles and permissions assigned prior to their use of the system.
Roles and permissions do not transfer with the individual.
Personnel should only be active in one GTIMS instance at a time. Exported personnel are
transferred to a holding organization for this very purpose. Operations performed on personnel
in two different GTIMS database instances will lead to data loss when further imports/ exports
are performed involving the affected personnel.
The personnel transfer tool is best suited for temporary or permanent transfers between GTIMS
database instances. This tool should not be utilized for routine synchronization purposes.
1.2. USAACE ENHANCEMENT REQUEST
1.2.1. ER16659 REMOVE LEGACY COMPONENTS FROM GTIMS ER Description: As a mitigation for IA scanning, there is a desire to evaluate removal of legacy and
unused components from GTIMS. These components may include unused VB applications, unused C++
6
applications, applications that use a vendor that no longer supports the product, and any services with
VB or C++ code
This effort includes identifying the applications, determining the best method to remove them from the
code base, and making then inaccessible, while not removing them from the baseline. This ER will be
followed by another effort to complete the removal process.
• Write data scripts to update T_TIMS_COMPONENT_LU table (and child tables) to disable legacy
components from access via the GTIMS Browser.
• Write data script to disable all VB reports and wizards in T_RPT.
• Update build script so that unneeded legacy components are no longer built.
The users will see the following changes across GTIMS:
- Browser: Removed buttons for launching Bulletin Board & Weather
- OpsManager Resource Browser: Removed ability to launch legacy components from the context
menu
o GBTS Maint
o Legacy Allocation Details
o Resource Availability
o Copy Setup
o Resource Definition
o Modify Characteristics
- OpsManager Training Calendar Management: Removed "Print" buttons from both the
Management form & the Edit dialog because there is no C# equivalent to the VB Training
Calendar Report
- OpsManager: Removed the ability to launch legacy tools from the toolbar and the explorer bar
o Resource List
o GBTS Maint
o Mission Effectiveness
o Resource Availability
o Resource Definition
o Student Manager
- OpsManager New Person Control: Launch Person Manager button no longer requires that the
legacy Resource Definition be installed to be enabled
- ReportBrowser: Refactored wizard launch code & removed all ability to launch legacy report
wizards
- SchedulePlanner Swap Sched Lines View: Previously hard-coded to launch VB version of
ResourceSchedulingReports, now launches C# version
- SchedulePlanner: Removed Resource Availability tool from the toolbar
- SyllabusDesigner: Removed ability to launch the Rule Editor, CAI Configuration, and Policy Editor
- SystemManager: Removed ability to launch Resource Type Definition
- TileBrowser: Clicking on the Weather tile will now show a MessageBox saying "The Weather
application is no longer supported."
7
- Training Jacket EP Dialog & SSR Dialog: Previously hard-coded to launch VB Commander's
Review report, now launches C# version
- Training Jacket: Toolbar buttons for Aviation Tracking Summary & Category Grade Summary
Reports previously hard-coded to launch VB versions now launch C# versions
- Resource Scheduling Report: Internal refactoring to allow for optional parameters
- ATJ Report: Previously allowed the VB Weapons Log report to be included, support was
remarked out for future use
- Commanders Review Report: Refactored to remove unused references to Legacy Report code
- ATJ Report Wizard: Disabled the Weapons Log checkbox on the wizard
- Elimination Report Wizard: Previously enabled/disabled checkboxes based on user's permissions
to legacy reports. Now looks at user's permission to C# reports.
o Category Grade Summary
o Summary Record of Training
o Completed Academic Events
o Full Jacket Summary
- Elimination Report Wizard: Previously hard-coded to run the VB version of Category Grade
Summary Report, now coded to run C# version
- In the application framework and database the following changes were performed:
- C# Reporting Framework: Support for Legacy Reports removed
- InteropHelper (generalized component launching tool): Support for legacy components
removed
- Components and reports have been disabled thru modification to T_TIMS_COMPONENT_LU,
T_RPT and the Tile browser tables.
2. GTIMS CONTENT FOR TMS VERSION 1.7.33
SUMMARY
TMS version 1.7.33 contains 35 GTIMS Enhancement Requests (ER) and 14 GTIMS Discrepancy Reports (DR).
2.1. AMC ENHANCEMENT REQUESTS
2.1.1. ER 15064 – INSPECTIONS AND TRENDS - DATA WIDGET - S/E GRADESHEET COMMENTS
ER Description: Users are requesting a change to the Inspections and Trends module to add a data
widget that will pull all comments from a Stan/Eval Gradesheet, regardless of whether a grade of Q-, U
or CMD was entered for that item. This would be similar to, or possibly a modification of, the
Discrepancies data widget to include the requested information.
Additional comments have been included into the FEF Comments widget. Memo for Record, Mission
Description, and Additional Comments can now be selected from the parameters dialog and the
information will be displayed within the widget. An Overall Grade column is now present and will be
displayed as a fixed column located after the Duty Code.
2.1.2. ER 15176 - ADD VIRTUAL COLUMN IN GNG
ER Description: Add a virtual column in GNG. This ER has a dependency on ER15015.
8
053 - AMC SME CONF 2015-03 – Need Ability to Configure Which Go/No Go Requirement Categories are
Applicable in Scheduler
User requests the ability, to define by organization, which Go/No Go requirement categories (e.g. Reads,
Tests, Quals, etc.) are utilized within the scheduler by the Go/No Go status virtual columns for schedule
lines and crewmembers. For example, a user could disable the Reads requirements category from being
presented by the scheduler Go/No Go virtual columns.
Added a new virtual column that shows a subset of Go/ No Go categories in the scheduler
The virtual column shows a Go/ No Go status on only the categories selected in system manager, and
ignores any categories not enabled.
Tooltip shows which categories are taken into account by the Virtual column
The Go/ No Go category subset for the virtual column is defined in System Manager\ Scheduler Planner
Options\ Behavior Cont.\Go /No Go Filter categories
Virtual Column is enabled for an organization, but can be hidden per individual preference.
Recommend that Go/ No Go Virtual column is always next to regular Go/ No Go status, for full
situational awareness
2.1.3. ER 15454 - CREATION, SIGNING, PRESERVATION, AND DISPLAY OF GROUP NMR LETTER
ER Description: Adrian Arthur makes the following request per AMC/A3 SMEs:
AMC requires a Non Mission Ready (NMR) capability that allows an authorized individual to group and
digitally sign for aircrew members (individual aircrew, multiple aircrew, or multiple Squadrons within an
Operations Group). This capability crosses into a display, database, and print functionality. In all cases,
the below functionality is required:
- Ability to display single/multiple - Names, Events for each individual, Training Date, Instructors Name
and Instructor Signature
- Additional data elements for each person listed as NMR - Crew Member Position, Unqualified date,
Remarks
- All of these data elements (see attached NMR letter) combined on one display/document for an
authorized person to digitally sign that all of the individuals are NMR.
GTIMS may have a display that captures all NMR individuals and allows the digital signature within the
database so the individuals NMR status is reflected in all modules that need it. GTIMS also needs to
produce a printed product that displays all of the data with a representation of the digital signature. If
the authorized user groups the NMR aircrew members with the NMR reason/data and digitally signs
that NMR status the database will store the digital signature and the data elements may be used to
create a printed memo if needed.
The following ERs have been added to the effort of ER15454 due to their relation and little additional
effort required:
9
ER 16560 – NMR LETTER - ADD POPUP REMINDER NOTICE.
ER Description: When creating NMR Letters request GTIMS remind users via popup that reads; "Be sure
SARMS completed all prorations prior to creating NMR letters. Would you like to continue?"ER 16455 –
ENHANCEMENT REQUEST - MCCONNELL (NMR)
For customer ease of use, they require the ability of the “Select NMR Letter" box to remain available for
selection of multiple individuals without having to completely start over within the module to select
another individual.
ER 15865 – NMR - MULTI-SELECT PERSONNEL IN FIND/CREATE LETTER
Need the ability to select multiple people in the Find/Create Letter and all of the letters will open in
separate tabs (similar to assigning a TBT template to multiple people). Single digital signature will assign
all of the opened letters.
ER 15863 – NMR - MODIFICATION TO NMR LETTER REPORT
Need to add the following information to the NMR letter report for each
activity added to the letter
- Number not completed in previous cycle
- Number required to accomplished
- Change the DOD insignia to USAF insignia
The NMR Letter interface functionality has been expanded to allow multiple NMR letters to be
consolidated onto a single Group NMR Letter report. Also, the NMR Letter reports have been expanded
to include a ‘dynamic’ NMR Letter report which reflects the latest completion updates based on the
NMR Letter events assigned.
Through the NMR Letter interface, when using the NMR Letter’s ‘Find Letters By Unit’ tab to
manage a single letter or multiple letters, the letter can be selected as a group and the new Manage
Status button will be enabled when the letters share the same NMR status of ‘Pending’ or ‘Recommend
Approval’. This Manage button brings up the Manage State dialog where the group of letters can be
moved into the next status together. In the case of a ‘Pending’ status, the letters can move into either
the ‘Recommend Approval’ or ‘Reject Letter’ state. In the case of ‘Recommend Approval’ state, the
options to ‘Approve Letter’ or ‘Reject Approval’ are available to the group. The ‘Approve Letter’ action
will start the NMR Letter report signing process by showing a draft group letter before asking for an
official signature. This draft letter will have a shaded DRAFT watermark and no signature section since it
is simply a preview report. Once the letter is signed, the individual letters are formally considered a
group. Finally, a new ‘State’ filter dropdown is available in this tab which allows for filtering the NMR
Letter list based on an ‘Assigned’, ‘Pending’, or ‘Recommend Approval’ status.
A new ‘Find Letters By Group’ tab allows the user to search for all of the signed Group NMR
Letters, based on the same filtering criteria available in the ‘Find Letters by Unit’ tab. This new tab
displays how many individual NMR letters are included in each group, lists the names connected with
each letter, and the individual NMR letters’ status. The officially signed report or new dynamic report of
each group letter can be opened directly from this tab. These reports can also be launched through
icons in the Ops Manager ribbon when a person's NMR Letter is open within Ops Manager.
10
The signed letter report will have no watermark and contains the signature section as this is the
official signed letter. The signed letter report is fixed in time once the report is signed and generated. In
other words, information on a signed report will not change over time.
On the other hand, the dynamic NMR Letter report’s data can change showing a person’s latest
completion dates and instructors of their accomplished NMR events. The dynamic view of the letter has
a shaded REPORT watermark in the background of the report, no signature section, and shows the
current state of the tasks which change as they are completed.
Lastly, when a user clicks on an NMR Letter icon within the ARMS Requirements Tracker, Go/No Go
Status Summary, or the Scheduler, the NMR application will open directly instead of only opening the
signed NMR letter. When the NMR application opens, it will be pre-loaded with the target person's
NMR Letter details.
2.1.4. ER 15761 - ENHANCEMENT REQUEST - EXECUTING INDIVIDUAL SCHEDULE LINES
ER Description: Need to have the ability to execute an individual schedule line instead of executing entire day or week (in the case for a mission). When the first leg of a mission is executed all legs of the mission need to be executed along with associated missions. This is a mission critical change due the dynamic scheduling of AMC
Provided a new method of managing missions/sorties when a customer does not approve schedules on a daily basis, but instead constructs and approves at a mission or sortie level. This is intended for AMC use only and must be specifically enabled in Schedule Planner Options. If NOT enabled then the user will see no difference in system behavior or appearance.
Changes to Schedule Planner Options in System Manager:
1. Added a new combo box “Mission Management” on the Behavior tab. By default this isset to “Never” and this implies no change to current behavior. The administrator may select either “Optional” which provides the individual Scheduler users an opportunity to select on a line by line or mission by mission basis whether to manage by mission or to use the default management by schedule day, or “Always” which enables Mission management for all missions and sorties and does not allow the scheduler users to make a choice. 2. On the Views and Tools page a new Scheduler mode has been added called MissionScheduler which allows for a custom UI to be configured for the new Mission Scheduler mode of the scheduler. The default configuration is intended for AMC mission and crew scheduling.
Changes to the Scheduler:
1. Added a new Scheduler mode called Mission Scheduler. This scheduler mode will beavailable to any user holding the “Schedule – Mission Scheduler” permission and appear in the Scheduler Build section of the TIMS Browser. 2. Added a “Manage by Mission” checkbox to both Insert Mission and Insert Line dialogsthat is visible when the Mission Management setting is either Optional or Always. It is only editable when the setting is Optional. 3. Mission Managed Schedule Missions and Sorties are displayed on grids in a distinctiveKhaki background color to differentiate them from standard missions and sorties. This coloration approach has been used previously when depicting MEIS and Distributed Mission
11
Operations (DMO) schedule missions/sorties to provide differentiation when viewing the schedule. 4. Provided a local approval mechanism that can be used to indicate local approval of missions and/or sorties. a. Right click on any mission or sortie (line) and the scheduler can select Locally Approved or Not Locally Approved. b. Alternatively, the administrator may configure the schedule grids to include the new local approval column on a schedule line or the new virtual approval column at the mission level and the scheduler can then simply check the checkbox on the line or mission to indicate the local approval state. These cells will display Green if locally approved, orange if not approved, and for missions Yellow if only a subset of the contained sorties have been locally approval. c. Only a user with “Schedule – Approve Mission” permission may change the local approval state of a line or mission. 5. Added the capability on the Organization and Resource Schedule view of visualizing the local approval state of lines and missions. By toggling a toolbar button to Show Local Approval colored blocks will be drawn at the right edge of mission and line bars to indicate the local approval state. Colors are as described before on the schedule grid. A user may also right click on mission or sorties on the Gantt and modify the local approval state using the pop up menu (with permission). System Changes: 1. Mission Managed sorties and missions are available on all reports and queries that were previously looking for “top-level” schedule lines. This extends how externally managed schedule lines (e.g., MEIS sourced missions/sorties, Distributed Mission Operations (DMO) lines) are displayed across the system. 2. Some calendar displays (e.g., Report wizards, Manage Schedules dialog) will display a khaki colored background for days where only Mission Managed schedule missions and/or sorties exist
2.1.5. ER 15843 - INSPECTIONS AND TRENDS WAIVER WIDGET ONLY SHOWS TBT WAIVERS
ER Description: In Inspections and Trends module, Waivers, when the widget is run it only returns
waivers that are associated with TBT training. Waivers submitted that are either Stan/Eval or training
(NOT TBT) do not show on display. User should be able to select TBT, Not TBT, Stan/Eval or any
combination for display.
Created a new Widget called “All Waivers” to capture every waiver in the GTIMS system
Renamed the Waivers widget to the TBT Waivers Widget as that widget contains functionality
specific to TBT Waivers
2.1.6. ER 15976 - UNIT INTERFLY ORG SELECTION
ER Description: When users are selecting personnel for Interfly, they have access to ALL units under
“owning org” but only their own unit under “gaining org.” This is backwards, as most of the units “push”
crewmembers to other units rather than the gaining unit “pulling” them. I would suggest either having
all units available for both owning and gaining, or having only the user’s permissioned unit in Owning,
and all units available under Gaining. The preferred fix would be for all units to be available for both the
OWNING org and the GAINING org.
12
In the Unit Interfly Request, all units are now available for selection for Owning org and Gaining org. The
user’s permission does not limit the orgs listed. The Owning org uses a single select combo box and the
Gaining org uses an organization selector which allows for multiple orgs to be selected.
2.1.7. ER 16000 - WAIVER MANAGEMENT NEEDS TO ALLOW ATTACHMENTS
ER Description: On behalf of the 437th OST the attached is an ER request. This request would enable
the user to add attachments to a Waiver thru the Waiver Management Module.
Waiver Management will now accept attachments to a waiver. There is a new tab in the same area as
the justification text box. This is where attachments may be added or deleted. Attachments may be
added by anyone with permissions to access the waiver. Attachments may be deleted when the waiver
is still in draft by anyone with permissions to access the waiver, but may only be deleted by personnel
with the appropriate approval level when the waiver has been submitted. In addition, a log tab can be
accessed to allow users to see who added or deleted attachments.
2.1.8. ER 16203 - ARMS REQUIREMENT TRACKER (CUSTOM FILTER SAVE LAYOUT)
ER Description: Observation/Problem:
1. Cpt. Badinski requests the ability within the ARMS Requirement Tracker to save filters created to
accomplish processes that are required on a continual basis. It may look or feel like something similar to
the option that Inspection and Trends has with setting up Layouts. Attached are visuals of one process
he has to accomplish weekly. After he completes his filtering he then has to export it to MS-Excel and
complete this for every crew position.
-His request would entail a run filter/layout drop-down on the main page and a save filter/layout
available on subsequent pop-ups.
"I would like to submit a ticket to gain the ability for users to save "custom filters" on the ARMS Requirements Tracker. This will save a ton of time continuously setting the filters to get the information we need displayed. I would like this ability to be available on both the "main filter" button, as well as the sort buttons over the columns.
i.e. To display the "Big 15" Metrics, we have to filter out all tasks, and manually search/check for the items we need displayed (this is one area where being able to save the filter set would be extremely helpful).We then have to create individual custom filters for the columns to sort out unqualified aircrew and those currently in MCT to gain the metrics we are looking for The ability to save these user created custom filters would greatly ease the amount of random sort and filing that we have to do weekly.
This product still has to be exported into a massive excel calculator to produce our end product."
Fix Action: 1. Refer to ESD
13
Layout Management capabilities have been added to the ARMS Requirements Tracker. These capabilities allow users to customize the display of the ARMS Requirements Tracker and then save those customizations as a named Layout. The Layout can be reloaded and the customizations quickly reapplied in a later session, saving the user from having to manually repeat the customization process. Multiple Layouts can be saved by each user.
A Layout Management section has been added to the ARMS Requirements Tracker menu ribbon, containing toolbar buttons to allow the user to select a layout, save a layout, save a layout under a new name, delete a layout, and reset a layout (resetting the display to its default state). The following settings for the display are saved as part of a layout:
The state of each of the display option toolbar buttons in the View section of the ARMS Requirements Tracker menu ribbon:
o Display Percentages
o Display Completed Tasks
o Display Tasks with No Requirements
o Display Quarterly Requirements
o Display Semi-Annual Requirements
o Display Annual Requirements
o Display Only Not Prior Complete
o Display Only Way Behind
o Display Beans Summaries
o Display Overall On/Off Track Coloring
o Display Proration Coloring
The task filtering applied to the display using the Filter toolbar button in the View section of the
menu ribbon
The column filters applied to the grids in the Beans View, Previous Cycle, and Status Overview
tabs in the main display area
Layouts are saved on a per-user basis. Layouts are not shared between users.
2.1.9. ER 16211 - BEANS DISPLAY CURRENCY INDICATOR ON SUMMARY TAB
ER Description: User requests a visual indicator when the quantity remaining is ZERO, but a task will be
overdue if not accomplished in the current cycle. User suggests possibly a different color check mark.
The ARMS Requirements Tracker does not display expired and “within threshold” visual indicators for
currencies. It is proposed that small colored triangles will be overlaid on top of beans to show currency
state. For tasks that do not have requirements, large colored triangles will be used to show currency
state when applicable. Individual Status Summaries will show currency state via background colors in
the Expiration Date column.
The following change was made to the System Manager | ARMS Requirements Tracker Options:
Currency Indicator Thresholds settings were added which allow the user to set the number of days, i.e.
threshold, prior to an activity's currency expiration date before an indicator appears (see chart below).
14
(Expiration Date) minus (Last Accomplished Date) Default Value (days) Min - Max (days)
< 31 days 7 1 - 30
31 - 180 days 30 1 - 90
181 days - 12 months 45 1 - 330
> 12 months 60 1 - 360
The following changes were made to the ARMS Requirements Tracker application:
1. Beans View tab - The following rules apply if the current day is within the specified threshold. Beans (colored balls) are overlaid with a small amber triangle (top, right corner). A large amber triangle is displayed if no requirement applies to a given activity. Finally, green check marks are replaced by amber check marks.
Notes – If the expiration date has passed, amber triangles and check marks will turn red. Historical data will not show currency indicators.
2. Status Overview tab - If the current day is within the specified threshold, the
background color of the Expiration Date column will change to amber for the
respective activity; red, if the expiration date has passed.
3. The legend now displays the Currency Indicator Thresholds settings for each
organization selected in the Parameters dialog.
2.1.10. ER 16220 – INTEGRATION MISSIONS FROM SCHEDULE MODULE WITH TASK BASED
TRAINING
ER Description: Allow a user to add a mission by selecting a schedule line in Task-Based Training Grading. When adding a Mission/Sortie/Event the ‘Create from Schedule’ button can be clicked on to add the Mission/Sortie/Event from the schedule. This will bring up a search dialog to enter criteria to search for a mission line or sortie/event/schedule line by a specific date and organization for the current person open in grading. The ability to clear the start date and pick blank for the organization exists if all missions and sortie/events for the current person would like to be displayed. Click on the ‘Find’ button to display mission lines and sortie/event/schedule lines matching requested criteria. If a mission line is picked to fill in the data for the Mission/Sortie/Event then the Mission Alias, Start Date, End Date, Training Platform and Duration fields will be populated with information from the mission. The Duration will be calculated by adding total time for all sorties/events associated to this mission that the current person is a crew member on. If a sortie/event/schedule line is picked to fill in the data for the Mission/Sortie/Event then the Mission Alias, Start Date, End Date, Training Platform, Duration and Instructor fields will be populated with information from the sortie/event and mission. The Duration will be calculated by the sortie/event Total Time.
15
All fields remain editable for adjustments or additional input. A warning will be displayed next to the
duration field that it was calculated using overall time unless the field is manually changed.
2.1.11. ER 16318 - ARMS INTERFACE - ABILITY TO PUSH “ZERO ACCOMPLISHED” TO ARMS FROM
DOTSHEETS
ER Description: Users request the ability to push “zero” accomplishment number from GTIMS Dotsheets
to the ARMS system. Current functionality requires a minimum of “1” accomplished. With this, there
should be a notification window that appears when Dotsheets with zero accomplished are saved. User
would have to acknowledge that those items are ok with no accomplishments.
The ARMS Interface has been updated to allow the user to push activities to ARMS that have “zero”
accomplishments. This is intended to allow the SARM to update currency within ARMS, without having
to increment the overall accomplishment quantity. Users may set the quantity accomplished to “zero”
within their Dotsheets (using the Dotsheet Editor, Flight Record, or 1522 applications) and the activities
will appear in the ARMS Interface.
2.1.12. ER 16397 SUPPORT MEIS 4 DEVELOPMENT WORK
ER Description: Develop MEIS 4 interfaces
GTIMS will now interface with MEIS/GDSS for retrieving mission data. This mission data will be added to
the appropriate organization’s schedule. From the schedule, the mission detail information may be
access through GTIMS, coming from MEIS/GDSS.
MEIS/GDSS services must be setup through a database script and/or System Manager before they can
be used. Users expecting to request mission details must contact MEIS/GDSS to ensure they have an
active account with MEIS. A certificate issued by MEIS will be necessary for the application server to pull
the mission information into the schedule. This certificate must be issued by MEIS for each location
wanting to interface with MEIS in addition to setting up the services in System Manager.
The MEIS certificate’s thumbprint and store location are specified in the
TmsSystemTaskService.exe.config file for the TmsSystsemTaskService:
<MeisInterfaceTask>
<add key=” CertStoreLocation” value=”{location entered here default LocalMachine}”
<add key =”MeisCertificateThumbprint” value=”{certificate thumbprint value}”
</MeisInterfaceTask>
Additionally, in the <MeisInterfaceTask> element the value for the key PollForMissions
must be true. For example,
<add key="PollForMissions" value = "true"/>
The scriptLocation attribute must be changed the site’s proxy script location in the application service
configuration file:
<system.net>
16
<defaultProxy>
<!--
The proxy scriptLocation must be changed at the production site to the sites setting.
The change is required for any application that must access the internet will running in
appserver or webservice mode. For example, any application using the MEIS Interface in those
modes.
-->
<proxy usesystemdefault="true" scriptLocation="{site proxy script location}" />
</defaultProxy>
</system.net>
Once services have been setup with a database script, and the above configuration items changed to the
appropriate operational values, System Manager can be used to specify the URL that will be used to
contact the MEIS services. The URL will be provided by the MEIS/GDSS organization. Connectivity can
be tested from the System Manager MEIS Service detail screen.
Within System Manager, administrators may also setup the organization, aircraft, and aircraft
family/series reference data. Linking the MEIS values for this reference data to the appropriate GTIMS
values is required for mission data to be imported correctly. For example, if an aircraft is listed in the
mission data from MEIS but a matching value has not been setup in GTIMS, the mission data cannot be
imported. This is true for all the value types that can be mapped in System Manager.
2.1.13. ER 16520 - ARMS ROLLOVER OVERWRITING HISTORICAL DATA – ALLOW FOR MANUAL
CONTROL FOR WHEN ROLLOVER OCCURS
ER DescriptionARMS pulls can overwrite historical data during the semi-annual rollover process. The
system instead needs to allow the user to manually indicate when a rollover occurs. There are several
potential COAs in discussion to resolve this issue - ONE of these three COAs may be a viable solution,
depending on the needs of AMC.
COA #2 - ARMS "Down" Window Specified by Enterprise and Rollover Complete Specified by Unit
A timeframe where ARMS is down during the rollover process, and retrievals are not occurring,
is specified by the enterprise (e.g. HQ AMC)
Each unit must manually indicate via a UI control that rollover is complete, re-enabling ARMS
pulls for that unit
Customer has selected COA #2 for this effort. Per Norm Maloy.
GTIMS now includes a new application, ARMS Rollover Management, which can be accessed
from Ops Manager under External Systems. This new application is used to manage and view
scheduled rollovers in the past present and future
o In the Scheduled Rollovers grid, the user can see info for the enterprise rollovers: the
enterprise organization, the start and end dates, the prior cycle end month, and the
person who created it
o Active rollovers are highlighted in yellow
17
o If the user has the ARMS Interface – Schedule Rollover permission, a new rollover can be
added, rollovers that have not completed can be edited, and rollovers that have not
completed and are not active can be deleted
o In the Add Enterprise Rollover dialog, when adding a rollover the user can select a
permitted enterprise organization, start and end dates for the rollover, and a prior cycle
end month; a rollover cannot be scheduled during an existing rollover and must be
scheduled in the future
o In the Edit Enterprise Rollover dialog, the user cannot edit the enterprise organization,
and can only edit the start date and prior cycle end month if the rollover is not currently
active; however, the end date can be edited if the rollover is currently active
o Selecting a rollover in the Scheduled Rollovers grid will load into the Rollover Status grid
all individual sub-organizations of the selected enterprise that the user has any ARMS
Interface permission for
o In the Rollover Status grid, the user can see the status of the rollover for individual
organizations by examining the info in the grid: the organization, the date the rollover
was closed for the organization and, if it was manually closed, the person who closed it
o Organizations actively in a rollover are highlighted in yellow
o If actively in a rollover, the user can manually close multiple organizations (if user has
the ARMS Interface – End Rollover permission for all the orgs selected) at once by
clicking on the Close Rollover button
Changes to ARMSInterface application in OpsManager
o For organizations that are in the rollover period all processing has been disabled. When
the user launches the ARMS Interface application during a rollover period and any of the
organization the user has ARMS interface permission to is in rollover, a dialog will be
display organizations’ rollover statuses. If there are organizations for which the rollover
is closed, access to the application will be allowed and the parameters dialog on those
organizations will be displayed and processed.
Changes to the ARMUpdate Task in the TmsSystemTaskService
o During a rollover period an organization for the rollover period has been closed and will
ARMS tasks be processed.
2.2. AMC FLEX CONTENT
2.2.1. ER 14658 - TASK-BASED TRAINING GRADING MODULE ENHANCEMENTS- ADD FILES AT
TEMPLATE TASK LEVEL
ER Description: The customer requests that the following enhancement be incorporated into the Task-
Based Training grading module.
For a given task defined in the template, users would like to be able to attach a link to a file used to train
that task (e.g., like a link to a power point file)
The ability to Add and Remove Attachments (files), File Locations, and Links (URLs) to TBT Tasks was
added to the Template creation screen. The standard Attachments UI was used and the addition of File
Locations and Links was designed to follow the same UI pattern.
Any items added to a task in the Template section will be added to any instance of the template when it
is assigned.
18
The ability to add to tasks was also added in the Assignments screen as well. Items added in this area
will apply to all people assigned to a given template that in a single session.
Lastly items can be added to a task in the Grading screen at the task level as well. This differs from the
existing ability to add Attachments to specific attempts as this is at the generic task level, not specific to
an attempt.
Help files were updated to reflect the enhancements that were made to all screens.
2.2.2. ER 15168 - FILTER NEEDED FOR FLIGHT AUTHORIZATION DUTY CODE
ER Description: Users would like the drop down list of Flight Authorization Duty Codes to be filtered. The
list is in Person Manager, Scheduler and 781.
The Flight Authorization Duty Code dropdowns in Person Manager and Scheduler, and the Flight Record
781 template are now using the data from the filter configuration under Training Organization instead of
displaying all the duty codes. If an organization does not have filter configuration setup, it will display all
the duty codes. All dropdowns will contain the current assigned duty code even if it isn’t in the filter
configured list.
In Person Manager, the dropdown is based on the individuals Training Organization. If they do not have
an organization designated, it will display all the duty codes.
In Flight Record, the drop down is based on the Schedule organization. If no organization is selected, it
will display all duty codes.
In Scheduler, the drop down is based on the Assigned organization, if there isn’t an assigned
organization, it will then be based on the owning organization.
2.2.1. ER 15392 - TBT TIME LOGGING MODIFICATION
ER Description: During 1.7.27 ER14651 Task-Based Training verification, a change would be needed to
existing functionality of Task-Based Training (TBT), Time-Based Task. A new label needs to be added for
the checkbox that permits time logging to read "Time logging enabled". The existing "time required"
label pertains to the numeric input field.
In the Add New Training Task window, a new label was added for the checkbox that permits time logging
to read, "Time Logging Enabled". Located within Task Based Training Setup in Ops Manager. The
existing, "Time Required" label pertains to the numeric input field, and is aligned to better represent the
field.
2.2.2. ER 15425 - TRAINING WAIVER ACKNOWLEDGEMENT
ER Description: During verification 1.7.27 ER14782 Training Waivers, it was noted that there was no
clear indication in TBT that a crewmember already had an approved waiver. This ER will add an indicator
to TBT required completion date that an approved waiver is active for a crewmember and will show
original completion date.
19
An indicator/icon was added to Task Based Training required completion date in Task Based Training
Grading that an approved waiver is active for a crewmember and shows the original completion date in
a tooltip. Clicking on the indicator/icon will open up the waiver.
2.2.3. ER 15723 – 129 – AMC SME CONF 2015-09 -USER REQUESTS THE ABILITY TO
LAUNCH CLICKONCE CLIENT FROM DESKTOP
ER Description: User Requests the Ability to launch the ClickOnce client from their desktop.
This ER provides a local installation capability to the GTIMS ClickOnce distribution by adding Desktop
and Start Menu icons for the application to users’ computers. In addition, an entry is made to the
Change/Remove Programs list in Windows to allow the user to optionally remove these icons. The
installed icons will launch the startup application as specified in the Web.config file on the web server
hosting the ClickOnce distribution. Upon launching, the Windows ClickOnce framework will check the
web server for updates, automatically downloading any new versions of the GTIMS software as with
prior versions. If the web server is not accessible, the current version of GTIMS will continue to launch
as normal, providing the users the ability to use GTIMS regardless of the operational state of the web
server.
2.2.4. ER 15995 - CHANGE ORGANIZATION SCHEDULE VIEW
ER Description: Currently the Organization Schedule View shows sortie legs as separate events on the
display. It needs to show the overall mission times instead. Each Mission block should be a solid block
for the entire duration of the mission.
Made the following changes to the Schedule Template Editor Descriptors tab:
1. Added the capability of adding Mission Descriptors for calendar and Gantt displays. You will be required to select Mission or Line when clicking the Add buttons.
2. Added the display of a readable descriptor type in the grid replacing the numerical values. 3. Added indicators on the descriptors grid to show required data based on the selected database
table and column. 4. Added validations to warn or prevent save when descriptor data may have been incorrectly
configured. Made the following changes to the Organization and Resource Schedule Views in the Scheduler:
1. Changed the Timeblock Chooser on the toolbar to allow for separate selection of Duties, Events (Sorties), and Missions.
2. When Mission Timeblocks are selected a Mission bar will be displayed from first sortie start to last sortie end.
3. If the user has specified to “Show Detail” on the bars, the mission bar will use the Gantt Mission descriptor for the information to display. If no descriptor has been constructed then the Mission number and Itinerary will be displayed.
4. In the Resource Schedule View you may now select Organization as a resource grouping to display activities by organization (as in the Organization Schedule View).
5. Modified the drawing algorithm to draw Mission related Timeblocks in a group to clarify the relationship.
6. Modified the drawing algorithm to draw Missions from earliest to latest from left to right and top to bottom on the Gantt. Best fit analysis is still performed to make sure minimum space is used to provide a concise display.
20
2.2.5. ER 16244 - ADD INCORRECT DATE WARNINGS TO STANEVAL STATUS PAGE
ER Description: Currently, when a Qual Expiration Date does not equal 17 months from the
Accomplished date, a warning appears on the StanEval Management Page, Quals/Waivers/Certs/MFRs
tab. Users (several users) have asked to have this warning repeated near the affected Qual on the
StanEval Status page. This way it would be readily visible when doing monthly DOV reviews. This
warning being clearly displayed on the status page would have prevented several occurrences of
crewmembers flying while unqualified, as the warning would have alerted them to a discrepancy. In its
present location it is not widely visible and would only been seen if DOV digs into an FEF. This is
considered a high priority by 60 OG/OGV.
When a qualification expiration date does not match the calculated expiration date, a warning indicator
icon now appears next to the expiration date for the qualification in the Expires On column of the
Qualifications grid on the Quals/Waivers/Certs/MFRs tab of the Stan/Eval Management application. The
same warning indicator icon now also appears in the Stan/Eval Status display, next to the expiration
date in the Expires column of the grid. In both cases, when the user hovers the mouse over the warning
icon, a tooltip appears which states that the expiration date does not match the calculated expiration
date.
2.2.6. ER 16253 - ENHANCEMENT REQUEST - ARMS REQUIREMENT TRACKER (EXCEL EXPORT)
ER Description: Problem
1. ARMS Requirement Tracker: Data that is reflected in the ARMS Requirement Tracker is being
exported to MS-Excel as pictures and general "text" where no value is associated to tell MS-
Excel that the numbers are numerical integers or dates.
2.
The values sent are a true description of the data, but once loaded in MS-Excel it is of no value
to the customer for management purposes (tallying totals) unless a formula can be built to
designate it as either a number or date.
3. Justification: The requirement comes as unit commanders require the ability to manipulate the
data to form/create unique management tools
Fix Action:
1. Submitted for ESD adjudication
When exported to MS-Excel the values in the cells have been updated to be more meaningful to the end
user. The data in the cells have been updated from strings to actual numbers and dates based on the
exported ARMS Requirements Tracker tab. Exported columns can now be sorted based on the data in a
particular cell, i.e. Dates can be sorted from newest to oldest, numbers can now be sorted from smallest
to largest, etc.
21
2.2.7. ER 16277 - ARMS REQUIREMENTS TRACKER - CHANGE APPROACH TO BEANS
COLORATION
ER Description: The coloration of Beans currently is approached from a starting position of 'bad' and
looks for 'good' to upgrade the colors. This causes frustration for the users as all personnel are 'Red' for
all beans at the beginning of every cycle. Customer requests that we change the approach for coloration
to a starting position of 'good' and look for 'bad' to degrade the colors.
For instance, a semi-annual (SA) requirement with a volume of '1' currently starts the cycle as red (bad)
and doesn't upgrade to green (good) until the task is accomplished. The display would have more value
if at the beginning of the cycle the requirement started as green (good) and the bean turning yellow (uh-
oh) or red (bad) only if milestones (# completed vs # expected complete at time in cycle) are not met.
Rather than using the current customer-defined '% behind' Warning Thresholds, we could allow a
customer-defined '% of deviation from expected' to determine the color changes from a default TBD.
The Arms Requirements Tracker beans display has been modified to include Beans Lookahead Threshold
settings that will allow an Organization to look ahead a number of days to assess the health of
individuals’ progress towards completing their activities. The new settings, located in System Manager,
allow for look ahead values to be set for Annual, Semi-Annual, and Quarterly activities based on cycle
progress. The new settings will allow for the same Organization hierarchy control as the Warning
Threshold settings. The beans display has also been updated so that progress shows as On Track at the
start of a cycle.
2.2.8. ER 16309 - LETTER OF XS - HIGHLIGHT CHANGES ON FTL COLUMN
ER Description: Aug '16 Technical Exchange - Currently, almost any change to a live LoX with a signed
LoX behind it, highlights changed cells in the grid w/ yellow (added) or red (deleted) backgrounds.
User requests this behavior be added to the cells in the FTL column. Because FTL changes are generally
changes and not an additions or deletions, user requests that the cell background turn yellow when the
cell entry changes.
In Letter of X’s Management in Ops Manager, cells in the Trn Lvl column are now highlighted in yellow if
the FTL has changed since the last signed Letter of X’s. Cells in the Trn Lvl column are now highlighted in
red if the FTL has been deleted since the last signed Letter of X’s. Highlighted cells in the Trn Lvl column
will display tooltips explaining the reason for the highlight if the user hovers over the cell with the
mouse.
2.2.9. ER 16315 - EVENT NOTIFICATION EDITOR - ADD ADDITIONAL FORM 4324 NOTIFICATION
ER Description: Aug '16 Technical Exchange - User requests additional Form 4324 Event Notification
when 4324 is complete.
An additional notification has been added to the Form 4324 that will notify individuals or groups when a
Form 4324 is completed. The new notification can be configured per organization by an Administrator
using Event Notification Editor in System Manager for a Group or Role. Optionally, an Administrator can
create a “dummy user” and direct the notifications to an Org box email address.
22
2.2.10. ER 16363 - TBT LOAD TEMPLATES – EDITING
ER Description: When in TBT in the reviews tab and you select Load Template, there is an option to
select the template. Once the template is selected, it displays in the lower pane. System needs to allow
for editing in this pane. Once you select OK, the template shows in the remarks box in the review where
you can edit it, That box need to be expanded or open to a larger window to edit the template. Current
state is unusable.
Request this be added to Service Pack.
In Task-Based Training Grading, once a single grade sheet is open for a person, under the Reviews tab,
the Remarks field in the Review Sign off and the Trainee Sign off were reorganized, next to each other,
to allow for additional vertical editing space in the Remarks text field.
2.2.11. ER 16383 - WAIVER SETUP/MANAGEMENT ENHANCEMENT REQUEST
ER Description: Problem: The 32 ARS received a new commander (Lt Col Jason R. Evans) and when the
32 ARS/CC e-mail was changed from McClasky to Evans it retroactively updated ALL the previously
approved waivers by the old 32 ARS/CC to the new CC (Evans).
Is it possible to not have approved waivers affected by Organization/OPR updates in Waiver Setup?
NOTE: Commands opt to use their own e-mail rather than their organization account due to multiple
junk e-mails received.
When the emails are changed for any Org/OPR name pair in Waiver Setup, any waivers that are ‘Waiting
to Review’ will have the Email field change to the new value. The Approved (Concurred) or Disapproved
waiver’s emails will not change. This will have the effect of preserving the email for the Org/OPR pair
that was used at the time of the Approval/Disapproval.
2.2.12. ER 16447 - 4324 - CHANGE SIGNATURE REQUIREMENT
ER Description: Problem currently is the AF form 4324 requires a signature from both the Training
Official and Stan/Eval Official. AMC requests that this be changed to "either or both signature(s) may be
used if no commander signature is required, but if the CC signature is required, then both Training and
Stan/Eval must sign" (current functionality). Instructions for which signature(s) are mandatory are on
the back of the AF Form 4324.
On a form 4324, when the ‘Require Block 25. Commander Signature’ option is checked, the
process will remain the same as it was previously, where the Training Authority, Stan/Eval
Authority and Commander all need to sign the form in order to move it into a Final state
When the ‘Require Block 25. Commander Signature’ is unchecked, the system no longer requires
both the Training Authority and the Stan/Eval Authority to sign in order to push the form to a
Final state, now a signature from either the Training Authority or the Stan/Eval Authority will
put the form in a Final state, but both authorities can still sign the form.
2.2.13. ER 16452 ARMS INTERFACE - ADD "ARMS LAST SUCCESSFULLY UPDATED" APP TO OPS
MANAGER
ER Description: AMC is requesting a new shared component that will be integrated into Ops Manager
under: ARMS Interface, ARMS Requirements Tracker, Go/No Go Status, and Crew & Duty Position
23
Manager. The new component, ARMS Interface Statistics, will permit users with the “ARMS Interface
Statistics – View Retrieval Dates” permission to view the last pull dates for Duty Codes, Quals, and
Profiles.
ARMS Interface Statistics component is accessible from ARMS Interface, ARMS Requirements
Tracker, Go/No Go Status, and Crew & Duty Manager as a fly out panel that is expanded / closed
by clicking on the appropriate button.
By default, the component is closed, and a “heads up” display will show the Last ARMS Qual
Date pull for the user’s assigned organization. If one does not exist, then it will show the most
recent ARMS Qual Date pull for all organizations that the user has the appropriate permissions
for.
When the component is expanded, ARMS data will be shown in a grid in the following columns:
Last Duty Code Retrieval, Last Qual Date Retrieval, and Last Profile Map Retrieval.
2.3. AETC FLEX CONTENT
2.3.1. ER 16266 - ADD FILTER TO MOST SUPERVISORY DISPLAYS
ER Description: JMATS is requesting to have a Resource Type and Person Resource Type filters be added
to the following Supervisory displays listed below. This filter should be similar to the filter Used in
Personnel Management that allows the user to filter on a Resource Type and or Person Resource Type.
These filters should have the ability to compound on top of each other and have the ability for the user
to save their preferences.
Qualifications Status
Readiness Status
Stan/Eval Status
Stan/Eval Signature Status
Testing Status
Training Status (Big Board)
On the Find Training Jacket Tab and the Find Grade sheet Tab in the Open Training Jacket Module add
the same filter capabilities as listed above.
Solution: The “Parameters” dialogs for the following Status Displays were updated to use the new
Organization Tree Selector for selecting Organizations, and all were enhanced with additional Person
Type and Resource Type filters where that functionality was missing:
Go/No Go Status
Go/No Go Management
Qualification Status
Resource Status
Stan/Eval Status
Stan/Eval Signature Status
Testing Status
Training Status (Big Board)
24
The new filters all allow multi-select, the Organization and Resource Type filters support “Select All” and
“Clear All” buttons, and they all save their settings as existing filters do.
In addition, the Parameters dialog for the Training Status (Big Board) was further enhanced with the
addition of a Class filter which also allows multi-select, supports “Select All” and “Clear All” buttons, and
saves its settings as existing filters do.
Finally, on the “Open Training Jacket” dialog in the Training Jacket application, Person Types and
Resource Types columns were added to the selection grids on the “Find Training Jackets” tab and on the
“Find Gradesheet” tab. These new columns support text-matching and multi-select row filtering via a
text box and drop-down selectors in the row filter for each column. As with the other column filters on
these grids, the filter selections are not retained between uses.
2.3.2. ER 16543 - USER REQUESTS A 4293 ENHANCEMENT TO ALLOW AT LEAST 6 PEOPLE TO
DIGITALLY SIGN 4293'S, CURRENTLY LIMIT IS 3 PEOPLE
ER Description: User requests a 4293 enhancement to allow at least 6 people to digitally sign 4293's, (IP,
student, flight Commander, ADO, DO, and CC).
The new optional roles, namely ADO, CC, CoUPT, DO, FC, and MTO, can be assigned to be used, per org,
in the System Manager’s Training Jacket Options in the 4293 Signatures grid. This grid allows for adding,
removing, and reordering the new roles. Also, each role’s row will indicate whether Task List or Email
will be used for notifications. The user can change either of these settings by toggling the checkbox in
the row. When submitting the 4293 Writeup for Signatures, the selected optional roles will appear
under the Counselor, Student and Supervisor in the grid listing the signers. After the initial 3 signers
have signed, the optional roles will all be available to sign; they do not follow a signing order.
2.3.3. ER 16544 - STAN EVAL SIGNATURE STATUS PAGE ENHANCEMENT REQUEST
ER Description: The DOV shop is requesting an enhancement to the Stan Eval signature status page. Capt
Maru's statement is:
On Stan/Evan Signature Status page, can we add an icon to link directly to the Digitally Signed form 8?
Current behavior
Click on name of Examinee from Signature Status Page
TIMS opens Stan/Eval Management with member's active Form 8
User clicks on View
User clicks on Digitally Signed Form 8
Desired
Click on icon or something adjacent to name of Examinee on Signature Status Page
TIMS opens Digitally Signed Form 8
I know it's not huge but it'd save three steps on every single Form 8, every time review and print these.
25
The Stan/Eval Signature Status page, accessed in Ops Manager, has been modified to include a column
next to the examinee’s name, which will allow the user to directly open an examinee’s digitally signed
Form 8 from that status screen.
2.4. ACC FLEX CONTENT
2.4.1. ER 16071 - FLIGHT RECORD NEEDS TO BE MODIFIED TO HANDLE TWO FIELDS WHICH ARE
USED BY THE RPAS
ER Description: The RPAs used blocks 30 and 33(?) on the 781 to log specific times. It appears to be a
different 781 than what is used by all other MDSs in the Air Force. They may have special authorization
from ACC to repurpose those blocks. The flight record app will need to be modified to display the
correct header. The ARMS interface may also need to be looked at to see if those block can even be
transmitted to ARMS. If they can, a separate ER should be created. The two forms are attached. The
XFDL file is the original 781 that GTIMS currently prints out.
When configured to show RPA fields, the AF781 Aircrew Data grid should hide “PRI INST” and “PRI SIM”
columns and show “LRE” and “MCE” columns. In addition, the AF781 report should record LRE and MCE
hours for each crew member in the Remarks section.
The following change was made to the System Manager | Flight Record Options | AF781 Options tab: A
new checkbox option “Display RPA fields LRE and MCE” was added. When checked, the “PRI INST” and
“PRI SIM” columns are hidden and the “LRE” and “MCE” columns become visible in the AF781 Aircrew
Data grid.
The following changes were made to the Flight Record | AF781 application:
1. When configured to show RPA fields, the “PRI INST” and “PRI SIM” columns are hidden.
2. When configured to show RPA fields, the “LRE” and “MCE” columns are displayed.
3. A non-save preventing validation warning is displayed if either “LRE” or “MCE” hours exceed
total flight time.
The following change made to the AF781 Report: LRE/MCE hours are displayed for the first four crew
members in the Remarks section.
2.4.2. ER 16458 - PUSH OF RPA SPECIFIC FLIGHT RECORD DATA LRE AND MCE TO ARMS
ER Description: The data entered for the added RPA specific fields LRE and MCE within the GTIMS Flight
Record application need to be pushed to ARMS. The fields in question (rpa_lre_qy / rpa_mce_qy) are
located in the Virtual Transaction PL/SQL Package flight_transaction.flt_act_rec_type.
The following change was made to the ARMS Interface: Code was refactored to send the new LRE and
MCE 781 crew fields to ARMS. No changes were made to the UI.
2.5. USAACE ENHANCEMENT REQUESTS
2.5.1. ER 14462 – ENHANCEMENT TO THE ARMY STANDARD GRADESHEET
ER Description: USAACE users have asked for an enhancement to the Army Standard gradesheet to
make the counter have a running total column. This would be like the current FTU gradesheet style in
26
GTIMS. Also a rule to not opt or not allow to progress to the next phase/category when the counter is at
or below a value.
Example:
Event CON-1, Item = PREPARE PPC, Count = 3, Total = 3.
Event CON-2, Item = PREPARE PPC, Count = 2, Total = 5.
The Army Standard gradesheet has been updated to provide a running total column, named “Total.”
This new column sums up tasks within the gradebook and provides a running total, per task and within
the same category, for each of the tasks within the Army Standard gradesheet.
Example:
Event CON-1, Item = PREPARE PPC, Count = 3, Total = 3.
Event CON-2, Item = PREPARE PPC, Count = 2, Total = 5.
2.5.2. ER 14463 – ENHANCEMENT TO ACADEMIC ROSTER FOR OVERALL GRADES
ER Description: USAACE Users request an enhancement to the Academic Roster Grades UI that;
1. When the user sets the Overall Grade to "N" (grading system Accomplished/Not Accomplished) to set
the duration to 0.0.
2. Add column for Reason to right of Overall Grade. Values need to be in a LU table and currently are:
Med, Admin. Make Reason be mandatory when OG set to "N" in order to leave or save the changes.
3. If OG is set to "A" (grading system Accomplished/Not Accomplished) and duration set to less than
planned duration then make Reason field be mandatory.
NOTE: Class sizes make it too difficult for these values to be set on individual gradesheets.
When an Army Gradesheets Overall Grade is set to 'N', the duration now changes to 0 and a Grade
Reason is required. If the Overall Grade is set to 'A', but the duration is less than the Estimated
Duration, a Grade Reason is now required. This behavior was implemented for both the individual
Academic Gradesheets and the Academic Roster.
3. ENHANCEMENT REQUESTS/DISCREPANCY REPORTS
3.1. GTIMS 1.7.33.1 ER LIST
(For more details, please consult the Redmine database.)
ER # ER Headline
ER16659 Remove Legacy Components From GTIMS
ER16542 KC-46 ATS Student Record Exchange
27
3.2. GTIMS 1.7.33 ER LIST
(For more details, please consult the Redmine database.)
ER # ER Headline
ER 14462 Enhancement to the Army Standard Gradesheet
ER 14463 Enhancement to Academic Roster for Overall Grades
ER 14658 Task-Based Training Grading Module Enhancements- Add Files At Template Task Level
ER 15064 Inspections And Trends - Data Widget - S/E Gradesheet Comments
ER 15168 Filter Needed for Flight Authorization Duty Code
ER 15176 Add Virtual column in GNG
ER 15392 TBT Time Logging Modification
ER 15425 Training Waiver Acknowledgement
ER 15454 Creation, Signing, Preservation, and Display of Group NMR Letter
ER 15723 User Requests the Ability to Launch ClickOnce Client from Desktop
ER 15761 Enhancement Request - Executing individual schedule lines
ER 15843 Inspections And Trends Waiver Widget Only Shows TBT Waivers
ER 15976 Unit Interfly ORG Selection
ER 15995 Change Organization Schedule View
ER 16000 Waiver Management Needs To Allow Attachments
ER 16071 Flight Record Needs to Be Modified to Handle Two Fields Which Are Used by the RPAs
ER 16203 ARMS Requirement Tracker (Custom Filter Save Layout)
ER 16211 Beans Display Currency Indicator on Summary Tab
ER 16220 Integration Missions from Schedule Module with Task Based Training
ER 16244 Add Incorrect Date warnings to StanEval Status page
ER 16253 Enhancement Request - Arms Requirement Tracker (Excel Export)
ER 16266 Enhancement Request to Add Filter to Most Supervisory Displays
ER 16277 ARMS Requirements Tracker - Change Approach to Beans Coloration
28
ER # ER Headline
ER 16309 Letter of Xs - Highlight Changes on FTL Column
ER 16315 Event Notification Editor - Add Additional Form 4324 Notification
ER 16318 Arms Interface - Ability To Push “Zero Accomplished” To Arms From Dotsheets
ER 16363 TBT Load Templates – Editing
ER 16383 Waiver Setup/Management Enhancement Request
ER 16397 Support MEIS 4 Development Work
ER 16447 4324 - Change Signature Requirement
ER 16452 Arms Interface – Add “ ARMS Last Successfully Updated” App to OPS Manager
ER 16458 Push of RPA specific Flight Record data LRE and MCE to ARMS
ER 16520 ARMS Rollover Overwriting Historical Data
ER 16543 User Requests A 4293 Enhancement To Allow At Least 6 People To Digitally Sign 4293's,
Currently Limit Is 3 People
ER 16544 Stan Eval Signature Status Page Enhancement Request
3.3. GTIMS 1.7.33.1 DR LIST
(For more details, please consult the Redmine database.)
DR # DR Headline
DR16624 Manual Flight Record Issue
DR16649 ARMS Requirements Tracker Excel Export Icon Distortion
DR16685 Task -Based Training Grading -Reviews Center Slider Between Reviewer Signoff and Trainee Signoff text boxes
DR16686 Differentiate Between Icons for Click Once Clients
DR16687 Add a ‘Not Editable’ Warning Label to the TBT Attachment Enhancement
DR16696 Organization for Person Resources Display as N/A in Personnel Management
DR16698 Change Information Icon in TBT Grading When the Original Completion Date is Different
DR16699 Alter Last ARMS Retrieval Date Text
29
DR # DR Headline
DR16708 Gradesheet Details Displays Issues
DR16729 Start Menu Launches VB Version of Timeline App
DR16730 GNG Status – Filter Combo is too Narrow Making it Impossible to See Differences in Orgs and is not Ordered
DR16740 Qual Mgr – Qual Levels Dialog Issue
DR16741 Qual Mgr – Edit Qual Activity Dialog Hides Quantity and Expiration Drop Down is Scrunched
DR16742 Qual Mgr – Add/Edit Qual Dialog Issues
DR16743 Qual Mgr – Grids Use Nonstandard Way of Forcing InitalizeRow that Caused a Smothered Exception
DR16744 Qual Mgr – Qual Def Date
DR16745 Qual Mgr – Add/Edit Qual Does Not Require an Abbreviation
DR16773 AF781 Report Back Page has Text that Overlaps
3.4. GTIMS 1.7.33 DR LIST
(For more details, please consult the Redmine database.)
DR # DR Headline
DR13556 Sortie Flow View Ordering Of Cloned Events
DR14733 ATJ Report Will Not Open In Report Browser For Specific Student.
DR15502 ARMS Interface TimeZone Issues
DR15566 Unable To Bring Up Report - Class Roster Or Student Roster(etf 16 Hrs)
DR15737 ARMS Interface Error (etf 20 hours)
DR16536 Discrepancy Report - Revision Double Entry
DR16537 MASS Not Calculating Scores Correctly
DR16554 Pilots Log One Flight Event On Dotsheet, Two Show In ARMS Interface
DR16566 Student Flow Management
DR16591 Account Citation Editor Error
DR16602 ARMS Interface - Change button order.
DR16606 Discrepancy Report-Flight Authorization Reports
30
DR # DR Headline
DR16621 Attachment Size Too Big Error
DR16643 CURRDEV TIMEZONE ISSUE
4. DATABASEGTIMS release version 1.7.33.1 uses the 12.9.0 database schema.
END GTIMS 1.7.33.1 Release Notes