Scenarios

TilliT scheduler has a flexible concept called Scenarios. These are user-defined modelling environments where you can create, manage, update and coordinate a Schedule for internal and external communication purposes.

Scenarios can be created by clicking on the plus button.

Once a Scenario is created, it sits in the draft status swimlane of the Kanban Board.

Scenario Status

This Kanban-style workflow represents the lifecycle of a Scenario from initial creation through to eventual completion:

Here's the information formatted as a table:

Type	Description
Draft	This is the place where your Scenario initially resides after creation. Draft Scenarios can be used to create multiple "what-ifs" and store them for your own use. They are not shared with the broader organisation or other users and therefore can reside independently
Proposed	Scenarios that users wish to propose to the broader organisation should be moved to Proposed. Proposed Scenarios can be viewed, reviewed, and analysed by various users prior to Publishing. Where multiple proposed Scenarios exist, the organisation should decide on the preferred Scenario to be published
Published	This is the active "live" Scenario that is due to be executed. Once a Scenario is moved to the Published area, the system distributes a notification to other users via email that a new Scenario has been published
Complete	This is the location for placing completed Scenarios once they have been executed. From here they can be deleted if required

We recommend creating a Template Scenario that serves as the foundation for all other Scenarios. This template should contain a clean, validated, and up-to-date configuration based on accurate master data imported from your source systems.

The template should include key foundation data that remains relatively stable over time, such as:

• Equipment resources

• Personnel

• Operations

• Availability (Shifts)

• Materials

Since this foundational data typically does not change on a daily basis, starting each new Scenario from the template ensures you begin with accurate, consistent information. This approach eliminates the need to reconfigure stable data elements each time you create a new Scenario, saving time and reducing the risk of errors.

Propose, Publish or Complete?

Only move a Scenario from Draft status once you are ready for other users to view and interact with it. The Proposed and Published statuses are essential for managing a consistent workflow as Schedules progress through approval and execution stages. This controlled progression ensures that only reviewed and approved Schedules become active in your operations.

Understanding Cloning

Cloning allows you to duplicate an existing Scenario along with all its configuration and data. When you clone a Scenario, everything is copied, including:

• Orders

• Previously scheduled Orders

• Tasks

• All configuration settings

Cloned Scenarios function identically to any other Scenario in the system and can move through all standard workflow stages (Draft, Proposed, Published, Complete).

Naming Best Practices

A well-structured naming convention helps organize and identify the purpose, timing, and scope of each Scenario. We recommend including:

• A name that reflects the Scenario's objective

• The date range or time horizon the Scenario addresses

Examples:

• "Weekly Schedule 12th April - Reduced Shifts" – This indicates a standard weekly Schedule for the week of April 12th, with a what-if analysis exploring reduced staffing levels.

• "Standard 24/5 Template" – This represents a template Scenario for regular daily business operations running 24 hours a day, 5 days a week.

Please also see the section for more information on configuration and data model management.