Dynamic Scheduling (Optimise) - Release 9.42

Release Date: August 2026

We have been enhancing Dynamic Scheduling since the last release, adding new features and addressing known issues to improve quality.

Some features may require additional setup by Totalmobile. If needed, reach out to your Account Manager for access details.

What's New

  • Create an SLA Based on Contract and/or Worktype

    You can now define Service Level Agreement (SLA) details by Contract Reference and Work Type Reference combination. These settings control how far in advance customers must be notified of a scheduled visit, taking into account non-working days and ad-hoc exclusion dates (such as bank holidays).

    This helps scheduling coordinators and operations managers ensure customers receive contractually-required advance notice of scheduled visits even when weekends or holidays fall within the notification window, particularly useful where SLAs specify minimum notification windows and non-working days must be respected.

    The new Optimise Admin > SLA Details page lists existing SLAs and enables you to create, edit, and delete SLA configurations. Access to this page is controlled by the new SLA Details permission, configurable on the Web Admin > Permissions page.

    Each SLA record includes the following:

    • Reference - a unique identifier for the SLA of up to 50 characters.

    • Contract Reference - the contract this SLA applies to (optional - leave blank to apply across all contracts).

    • Work Type Reference - the work type this SLA applies to (optional - leave blank to apply across all work types).

    • Notification Period (hours) - how far ahead of the scheduled time the customer should be informed. This can be between 0 and 999 hours, and decimals are supported, for example 0.25 for 15 minutes.

    Only one SLA is permitted per Contract Reference/Work Type Reference combination.

    Each SLA can define days and dates to skip when calculating the notification deadline:

    • Recurring exclusions - exclude any day(s) of the week (such as Saturday and Sunday) so they are not counted when working back from the job schedule date.

    • Ad-hoc exclusions - exclude specific dates that fall within the notification window.

    Once configured, SLA details are used in the following areas:

    Area

    Behaviour
    Auto Commit SLA Jobs Jobs with SLAs are automatically locked in place ahead of the notification period, ensuring stability before the customer is informed. For more details refer to SLA Automatic Commit Background Job below.
    Manual Job Scheduling Planners are warned when manually scheduling a job inside or outside the notification period.

    For more details refer to SLA Details and Manually Scheduling Jobs.

  • SLA Automatic Commit Background Job

    Enhancements have been made to the Optimise Admin > Select World > Background Job Settings page to introduce a new SLA Automatic Commit background job that automatically locks jobs in place ahead of SLA notification deadlines. This removes the need for manual intervention and ensures client notifications are sent on time.

    The job runs on a configurable schedule, using the same settings pattern as existing background jobs. On each run, it evaluates scheduled jobs that have an SLA defined, based on their Contract and Work Type reference combination. For each job, it calculates the point at which the client must be notified, and if that Notification Date falls within the configured Hours In Advance window, the job is automatically committed and locked in place.

    A CommitJobNotification message is produced for each affected job, enabling downstream integrations and alerting. The standard audit log is updated for every auto-committed job, maintaining full traceability.

    For more details refer to Background Job Settings.

    This feature is available for Enterprise and Cloud Worlds only.

  • Automatically Commit Scheduled Jobs

    Enhancements have been made to the Optimise Admin > Select World > Background Job Settings page to enable scheduled jobs to be automatically committed on a rolling basis. The Automatic Commit background job removes the need for manual intervention to commit non-SLA jobs ahead of their start time, helping ensure schedules are finalised without relying solely on SLA notification periods.

    The job runs on a configurable schedule, using the same settings pattern as existing background jobs. On each run, it evaluates scheduled jobs that are not already committed. For each job, it checks whether the scheduled start time falls within the configured Hours In Advance window, and if the job is within that window, it is automatically committed and locked in place. Once committed, the job cannot be moved or reassigned without decommitting it first.

    A CommitJobNotification message is produced for each job that is automatically committed, enabling downstream integrations and alerting. The standard audit log is updated for every auto-committed job, maintaining full traceability.

    For more details refer to Background Job Settings.

    This feature is available for Enterprise and Cloud Worlds only.