v1.41
There is a button at the bottom of the fault-edit page that allows the user to view any fault trees related to the fault currently being edited. These are fault trees in which the current fault is used as an associated item.
The button is disabled when there are no related fault trees for the fault being edited.
After pressing the button, a slider will appear displaying the highlighted affected faults based on the current fault-tree edits. These items are clickable and will take the user directly to the corresponding location in the fault tree.
The two [–] and [+] buttons at the top of the tree collapse and expand the entire tree in sequence, while the triangle on each node performs the same action but only for that specific node.
A generic fault tree (equipment type) is a static fault tree that can be reused by other equipment types with the same service mode. An equipment type can be marked as generic by selecting the Generic option when creating it. However, on the edit page, you can uncheck this option to convert it back to a non-generic fault tree.
When editing a generic fault tree with the Generic option checked, you can view the target equipment types, these are equipment types that are in the same available service mode as the generic equipment type currently being edited. After selecting the desired equipment types, or by selecting All, you can see the faults defined for the generic equipment type under the corresponding categories of the selected target equipment types.
In the Fault & Failures Trees, after selecting a generic fault, the user can create a fault that will also be usable in the target equipment types highlighted on this page.
Note that to make a generic fault available in other fault trees with different service modes, the fault must be defined in the same category and have the same service mode.
Once a fault tree is defined as generic, it can be reused in other fault trees.
Users can authenticate using either their Microsoft account (Azure Entra ID) or their normal account, but only one authentication mode can be active at a time. If access to the dashboard has been granted via Azure, the user can log in with a default profile. An administrator can then complete the user’s details and assign the appropriate roles, or alternatively create the user in the dashboard beforehand.
After clicking the Microsoft Login button, users are redirected to the Azure login page, where they enter their username and password, and then return to the dashboard.
When creating a new user, there is an option to choose between SSO or normal login. Once one option is selected, the other authentication method will be disabled for that user.
It is also editable when updating a user’s information, as long as the user has not logged in using a Microsoft account. Once the user logs in via Microsoft SSO, the authentication method becomes locked to SSO only.
The ability to change a password will be disabled for SSO users.
Driver Call Notification
The Driver Call Notification feature allows to send email notifications to specified distribution lists when they communicate with train drivers during an incident. This ensures that relevant operational teams are kept informed of driver communications in real-time.
Enabling Driver Call Notifications
Step 1: Navigate to Settigns > Incident Settings and make sure the Enable Driver Call i checked.
Step 2: Navigate to Administration > Routes and Location > Routes. Here you can add or edit email addresses for each operational route.
How it works
When you have an active incident and need to notify operational teams about a driver call, you will see a Driver Call Notification button in the FoF. The minimum you need to specify is the UnitNumber and the HeadCode to enable the notification
Once you've filled in these minimum fields, click the Driver Call Notification button to select which route to notify.
The system will only show routes that have email recipients configured. Select the appropriate route and the notification will be sent.
After you send a notification to a route, the button for that route will show a checkmark and be disabled.
Retry After Failure
If a notification fails to send (for example, due to email server issues), you'll see an error indicator and can retry the notification.
Searching by Notifications
You can search and filter incidents based on driver call notifications by navigating to Reporting > Incidents, then check the Notification Sent filter to find all incidents where notification was sent to a specific route
When your operational teams receive the notification, they'll see an email with the incident details including Unit Number, Head Code and any other relevant incident information.
ActionCheck Feature
The ActionCheck feature allows administrators to embed mandatory or optional verification checkboxes into fault resolution procedures. This ensures technicians complete critical safety and verification steps during incident resolution, creating a full audit trail.
Enabling ActionChecks
Step 1: Enable the Feature in Settings
Navigate to Settings > Incident Settings and make sure Enable Action Checks is checked.
Note: ActionChecks only work with Resolution and Standard fault types. They will not appear for Supporting Documents or other fault types.
Creating ActionChecks
Using the Associated Items Dialog
Navigate to Administration > Fault Tree > [Your Train] > [Your Fault]
Click Edit on the step where you want to add an ActionCheck
Scroll to Associated Items at the bottom
Click Add Associated Item
Select Action Check from the dropdown
Fill in the ActionCheck details:
Checkbox Title: Descriptive name (e.g., "Verify pressure gauge reading")
Mandatory: Check this if the action MUST be completed before resolving the incident
Click Save
Inserting ActionChecks into Body Text
After creating an ActionCheck via the Associated Items dialog, you need to insert it into your step instructions:
In the Associated Items list, find your ActionCheck
Click the Insert Checkbox button
The tag will be inserted at your cursor position in the body text
Example body text:
1. Reset the compressor switch
2. [AC ID=85]
3. Wait 30 seconds and verify pressureThe tag
[AC ID=85]will render as an interactive checkbox with the title you specified during incident resolution.
How ActionChecks Work During Incidents
Viewing ActionChecks
When going thru an incident and navigates through fault resolution steps, ActionChecks appear as interactive checkboxes with their titles:
Optional ActionChecks appear in gray with normal font weight
Mandatory ActionChecks appear in red/orange with bold text and a "(Required)" label
Completing ActionChecks
Technicians simply check the box when they complete each action:
The checkbox state is saved immediately via AJAX
Each checkbox click creates an IncidentAction record for audit purposes
Technicians can uncheck boxes if needed (the state updates immediately)
Mandatory Validation
If a step contains mandatory ActionChecks, the technician cannot proceed until all are completed:
The Resolve button is disabled (grayed out)
The Next Step button is disabled (grayed out)
Internal link buttons are disabled (grayed out)
The Abort and Unresolved buttons remain enabled (always accessible)
Once all mandatory ActionChecks are completed:
ActionChecks in Incident Exports
Export Summary Section
When you export an incident to text/PDF, a dedicated ACTION CHECKS section appears showing:
Which ActionChecks were present
Whether they were mandatory or optional
Completion status (COMPLETED or PENDING)
Completion timestamp for checked items
Example export:
=== ACTION CHECKS ===
Step 1 of 3: Reset Main Compressor
[✓] Verify pressure gauge reading (REQUIRED) - COMPLETED at 14:23:45
[✓] Check for air leaks (OPTIONAL) - COMPLETED at 14:24:12
Step 2 of 3: Test Secondary Compressor
[ ] Verify backup system (OPTIONAL) - PENDING
Note: Only ActionChecks from Resolution and Standard fault types appear in exports.
Editing ActionChecks
Changing Title or Mandatory Status
Navigate to the step containing the ActionCheck
Find the ActionCheck in the Associated Items list
Click Edit
Update the Title or Mandatory checkbox
Click Save
Important: Changing an ActionCheck's mandatory status will affect ALL future incidents. Existing incidents retain their original completion state.
Deleting ActionChecks
Navigate to the step containing the ActionCheck
Find the ActionCheck in the Associated Items list
Click Delete
Confirm the deletion
Warning: Deleting an ActionCheck will remove it from:
The Associated Items list
All step body text where it was inserted
Future incident resolution screens
However, past incident records remain intact for audit purposes.
If you have the "Request Save Reason for Fault Editing" setting enabled, buttons will appear on fault edit pages allowing you to see what was changed and why.
We've reworked the way you attach documents to faults.
Word documents and PDFs
You can click the "Upload Document" button above the Associated Items.
"Display Document" will show the document in the sidebar underneath images
Once it's added as an Associated Item, you can click "Embed Document" to add it to the main text body
SharePoint Sites (Excel/Powerpoint/etc.)
From your sharepoint site, go to File -> Share -> Embed this workbook
Here you can update the embed settings (ignore the height and width for now, excel used for example)
Copy the Embed code and add it to the URL of a Weblink Associated Object
You can then click Embed Document to add it to the fault body text
It will appear as text looking like : [EMBED ID=X WIDTH=500 HEIGHT=500]Test Sheet[/EMBED]
Edit the height and width values to change the size of the embedded document.
You can now upload documents to show under the support button for all faults for a train class.
To create the document, go to Administration -> Resources -> Global Documents -> Add Document. These are formatted the same as resolution faults where you can attach images, text and documents.
You can then attach these to trains by going to Administration -> Trains -> Edit one -> Add Document
Last updated
Was this helpful?