Fatigue breach events are created when a staff member breaches the fatigue rules defined in the system & causes a Fatigue Violation. Breach Events capture the details surrounding the violation for later investigation & reporting.
Only users in the COP_Operations AAD group can update fatigue breach events.
A fatigue breach occurs when a driver is no longer compliant with any of the rulesets defined in the system.
Fatigue breaches record any breach of the standard hours rulesets (see below). When allocating drivers to jobs, the fatigue rules are checked before the allocation is allowed to proceed, ensuring drivers cannot be allocated into a breach. For a breach to occur, the driver must extend their job by finishing after the scheduled finish time, by not recording the required fatigue breaks in the vehicle’s tablet or by creating an adhoc job directly from the tablet, such as Emergency Rail.
Central ops follow the standard fatigue rulesets, which includes:
Fatigue breach events also include the severity of the breach. (See below)
Fatigue breach events also show the severity of the breach separated into 4 levels
❕Note: For specific details around what contributes to a breach and breach severity, view the fatigue legislation here:
Navigate to Compliance → Fatigue → Breach Events
❕Note: The default filter will show breach events with the status of Open. To change the filter to also see Invalid or Closed breach events, click the filter icon at the bottom of the page & apply the desired filter.
The Open Fatigue Breach Events tile on the Compliance page shows a count of breach events with the status of Open. Clicking on the tile will navigate to the Fatigue Breach Events page applying the default filter as above.
Details of a breach event can be viewed by clicking the Breach Event Number on the Fatigue Breach Events page.
The Manage Fatigue Breach Event page will show the details of the fatigue breach including, the staff member, breached ruleset, the date the breach occurred, which rule and ruleset was breached, the severity of the breach and job number the event is linked to. Processing options are available in the Triple Dot Menu.
Export to PDF: Exports the details of the event as a pdf document.
View Fatigue Breach Details: This takes you to the fatigue page pre-filtered for the driver and the date of the breach.
Mark as Closed: The breach event will be closed and no further changes can be made.
💡 Recommendation: Only close a breach event after all comments have been made and the details of the breach are verified and all audit information has been gathered.
Mark as Invalid: Will mark the breach as invalid.
Verify: The jobs that contributed to the breach will be re-evaluated to determine if the breach is still valid or not. See Verifying breach events for more information.
The Jobs tab lists all jobs that fall within the date range where the breach occurs, showing the scheduled clock on and off times versus the actual times with the reason for difference.
From the Manage Fatigue Breach Event page, click the edit icon ✏️.
Insert or update comments to record details such as why the event occurred, action plans for the event, or links to further information relating to the event.
Click Submit to save the changes.
If you wish to re-verify that a breach is still valid, you are able to run a recalculation to do this:
While viewing a breach event or on the Manage Fatigue Breach Event page, click the triple dot menu and click the Verify option.
If the breach is no longer valid, the system will alert you with a message.
If the breach is still valid the system will alert you with a message.
❕Note: The validation process will also verify the breach severity and if there are any changes to the severity then the breach will be updated to reflect this.
Click Invalidate to invalidate the breach event ❕Note: if the re-calculation finds new breaches, these will be added to the breach event list.
In This Topic
Related Topics