Worlds

A World is an individual instance of Optimise Schedule.

You can create separate Worlds in Dynamic Scheduling to simultaneously operate and solve multiple scheduling problems. You might want to create multiple Worlds because of:

  • Volume - separate a large amount of jobs and resources into manageable Worlds.

  • Organisational Structure - model separate worlds on team structures in your organisation.

  • Geographic Region - this might be within the same country or, if configured, across multiple countries or time zones.

  • Scheduling and Dispatch Rules - configure different schedule and dispatch rules for different Worlds.

There are three types of Worlds in Dynamic Scheduling, each offering different levels of scheduling capability.

Essentials World

This is the basic World type where job allocation and scheduling is done manually or via the Optimise API or Optimise Integration.

  • Jobs are scheduled to resources - you can drag and drop jobs onto resources and also deallocate them by dragging back to the Job List.

  • Pre-loaded job allocations can be received via the Optimise API or Optimise Integration. For more details of these options, contact Totalmobile.

  • There is no automatic plan generation - scheduling is purely a manual process.

Enterprise World

This option offers scheduling with Mendel, Totalmobile's automated scheduling and optimisation engine.

  • Mendel automatically allocates jobs to resources based on predefined criteria and constraints (for example, attribute matching, travel time, skills).

  • Jobs are committed to resources, and you cannot deallocate jobs by dragging them back to the Job List.

  • Plans are automatically generated and published by Mendel, then applied to the schedule in your World.

  • There are additional settings in Optimise Admin that do not apply to Essentials Worlds, for example Mendel Settings, Distance Settings, and Constraint Override Reasons.

  • There are more World import and export options than with an Essentials World.

  • When creating an Enterprise World, you require a Mendel Access Key, Mendel Secret, and Mendel URL. For more details refer to Configuring Worlds in the Mendel Database and Installing the Mendel Service.

Cloud World

A variant of Enterprise that connects to cloud-hosted Mendel rather than the on-premises version. This option is functionally similar to Enterprise with the following exceptions:

  • When creating a Cloud World, you require your unique customer ID to access the cloud version of Mendel.

  • This World type uses cloud-hosted agents for plan generation.