v1.39
Last updated
Was this helpful?
Last updated
Was this helpful?
New type of FoF template added called the defect report. This can be accessed from the FoF template slider.
This is accompanied by a new drop down at the top of the FoF once an incident has started, which enables the user to switch between templates.
(AGA Only) New incident settings to enable fields in the FoF template
A new setting in the Personal Dashboard allows you to set the default preference of the Export button to show or hide the fault steps.
The Export button has been updated to now offer options to export with or without fault steps, allowing you to temporarily override the default preference.
Added new columns called CCIL, Maximo & Incident Type in the My Incidents & All Incident within last 24hrs
Added a confirmation popup box for unticking the CCIL & Maximo checkboxes
Change requests can now be exported to excel in either the "Change Requests" section
Or in the Administration > Change Requests. Once you have performed a search then the "Export" button will become visible.
New dynamic milestones can be defined that can sit on your dynamic timeline. Please go to Administration > Dynamic Milestones to add or edit a milestone.
If no dynamic milestones are defined the system will default to the milestone settings in the Incident Settings.
To create a new milestone click the create and enter the basic information about the milestone.
The image below shows creating a new milestone called "Test Milestone" with an icon an a number of mins to trigger which represents where it is displayed on the dynamic timeline in relation to the start of the incident.
You can also define that a dynamic milestone is only relevant during a specific time. To do this simply select the "Timeboxed" check box and enter the start and end time for the timeboxing.
You can either enter the time by typing or click the clock icon. Once a milestone is timeboxed it will only be relevant on the timeline between those times.
You can mark a milestone as a cut and run policy, there will only be 1 active cut and run policy for the dynamic timeline. The most relevant cut and run policy will be displayed based on the criteria with precedence being given to timeboxed policies and then the policy that best matches the criteria.
You can mark a milestone a cut and run policy by selecting the Cut n Run Policy checkbox. This will open up further options for sounding an alarm and displaying a dialog when the policy time is breached.
If you want an alarm to sound when the policy is triggered select the sounds alarm checkbox and enter an interval in seconds between sounding the alarm
If you want a dialog to show once the policy has been passed then select the Shows Dialog checkbox. You can then enter the interval between times the dialog is shown, once the policy is passed, the number of mins that you can exceed the policy before a reason to continue is required by the system and a time in mins exceeding the policy time before the system will prompt the user for "next steps".
The warning text is what is initially shown to the user when the policy time is exceeded.
You can only have 1 cut and run policy active on the timeline at once. The system will pick the most relevant milestone marked as a cut and run milestone based on the criteria. The order in which the milestones are listed in this view demonstrates the priority in which the system will select the cut and run policy.
Now that we have created our new milestone you can see that it is displayed at the top of the list, this means that it is the most relevant policy should its criteria be met, in this example, were we to start an incident on a train class 313, then "Test Milestone" would be the cut and run policy. If not, then the "Cut & Run Threshold" policy would be used.
In either instance the "Loss of Power" would be present on the timeline as it has no criteria.
You can have as many non cut and run milestones as you like.
Once you have saved a milestone there are a few extra things that you can do with it. For example you can associate your milestone to either a train class, category or fault. This means that this milestone will only be relevant on the dynamic timeline if these associations match the current incident.
Simply select the train or category you want to associate this milestone with and click the . This will add it to the list of associations below.
You can remove an association by clicking the .
