v1.40
Last updated
Was this helpful?
Last updated
Was this helpful?
Providing that you have following settings checked within the General Settings of the system users will be prompted and required to supply a reason for the changes they are making to Faults, Steps and DOTE entries.
When a reason for changed is prompted the user will see the following dialog.
If they are required to enter a reason they will not be able to save without a reason.
When editing a DOTE entry, you now have a new button for each section that enables you to display the audit trail for each section.
Clicking the audit button will display a new "Fault Audit Log" dialog showing each time the section was edited, by who and why.
Clicking the highlighted button will expand the row to show you what the user changed.
There is also a new "Audit" button at the bottom of the main DOTE edit page for viewing an audit history of the properties of the main page.
There are now new settings that enable the TEAM to raise work orders within EAM's Hexagon system The new settings are found in administration settings under the API Settings tab.
Once these settings have been filled you then need to enable the "Enable Export Options" in the Incidents Settings Tab
Then during the incident the user can export the current incident as a work order to EAM by using the "Export" button in the "Fix or Fail Template".
Once an incident has been exported to an EAM work order it can not be exported to EAM again
To be able to use the new cut and run policy by location you need to have the dynamic timeline enabled in the settings.
You then need to administer your locations and then network routes. A network route in this instance is a section of your network (a list of locations) that you deem critical. It doesn't relate to operational routes that you may have.
Once you have setup your locations and network routes, you can decide how you want your users to select the location. This can be "None" (Freetext) or a Drop down. These settings can be found in the Incident Settings.
Below are how the users will see these options in the FoF slider.
You then need to either edit an existing dynamic milestone or create a new new one and assign the network route to the milestone.
Once complete, should a train be at a location that is in a network route that is associated to a cut and run policy you will see the associated milestone on your dynamic timeline. If you have set the dynamic milestone to be a cut and run policy with alarm and dialog options these will display as appropriate.
To use this filter, hover "Administration" and then click "Change Requests".
The new checkbox allows you to only search for Change Requests flagged in the RulesAndRegs.
The checkbox label will match your "RulesAndRegs Global Title" defined in your RulesAndRegs Settings
To record if the RulesAndRegs were used in an incident, you'll need to enable it in your Incident Settings.
The name will match the "RulesAndRegs Global Title" defined in your RulesAndRegs Settings.
You will then see a checkbox in the FoF template, also using the "RulesAndRegs Global Title".
To enable this feature you need to have the "Ask for Change Request Descriptions" setting checked
The next time you flag a fault/step for review, this popup will appear, allowing you to enter a description
We've added an icon next to the button to show how many open change requests you have for the fault.
If your system is , the value will be stored under "RulesAndRegsUsed".
