You are viewing PowerRosterâ„¢ v8.1. See what's new in Release Note v8.1

Compliance Overview

Prev Next

PowerRoster Compliance is used to configure rules and constraints to create custom fatigue management plans, manage overtime or apply the rules to specific contractual rules, industry-specific requirements and regulations, or local labour laws.

Constraints can be managed and tailored to different groups or individual workers through the use of contracts. Then, when creating or updating rosters, ensuring the right rules are enforced for the right people.

Compliance Checks can be run against a Roster or a Bookable Resource to detect if there are any notifications or issues identified.

The flow chart below describes the compliance process as managed within PowerRoster Compliance.

Flowchart illustrating compliance processes including rules, constraints, and breach management steps.

PowerRoster Compliance Process

Compliance Process

  1. Create a Compliance Rule - Compliance Rules can be configured to define the rules to be considered when rostering resources on various rosters. Further information about Compliance Rules can be found here.

  2. Create a Compliance Constraint - Compliance Constraints are created from rules to define specific policies against which the compliance is tested. These records consist of rules and parameter values that define the specificities of the constraint. Further information about Compliance Constraints can be found here.

  3. Create a Contract - Constraints can be managed and tailored to different groups or individual workers through the use of Contracts by bundling Constraints and assigning them to a Contract to ensure that the right rules are enforced for the right people. Further information about Contracts can be found here.

  4. Create a Constraint Allocation - Constraint Allocation allows the user to allocate constraints to specific resources or to multiple resources by allocating them to a roster, territory, or persona. Further information about Constraint Allocation can be found here.

  5. Create a Contract Constraint Allocation - Contract Constraint Allocation allows the user to allocate multiple constraints to specific resources or to multiple resources by allocating them to a roster, territory, or persona. Further information about Contract Constraint Allocation can be found here.

  6. Execute Real-time Compliance - Users can execute the real-time compliance engine to check upcoming compliance breaches.

  7. Execute Batch Compliance Engine - Alternative to the real-time compliance check, the compliance engine can be set up to run batch runs or nightly runs to periodically check for and flag compliance breaches.

    1. On-Demand Compliance Runs - Compliance can be run on-demand when required for a particular resource or roster by clicking the Run Compliance button.

    2. Nightly Compliance Runs - The compliance engine can be configured to run every 24 hours to identify changes to shifts that may have had knock on affects.

  8. Review Breach - Breaches can be reviewed once the compliance is run and all breaches have been identified and reported.

  9. Dismiss/Accept a Breach - Users are able to dismiss or accept a breach once identified. This results in future breaches for the same constraint and shift being ignored.

  10. Fix a Breach - Fixing a breach involves modifying the breached shift to satisfy the breached rule.

To understand how to create a Compliance Rule, Constraint, Contract and Constraint Allocation, please refer to the Compliance Settings section under Administration.

Important

Compliance Email notifications are generally created by developers. Customers using email notifications are encouraged to collaborate with Microsoft Partner Velrada for their setup.