Scenarios
Last updated
Last updated
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.
This Kanban-style workflow represents the lifecycle of a Scenario from initial creation through to eventual completion:
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 you 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 you create a Template Scenario upon which other Scenarios can be constructed. This template should represent a clean, validated and up-to-date record of the configuration based on accurate master data that may come from source systems. Resources such as Equipment, Personnel, Operations, Availability (Shifts) and Materials are key foundation data inputs that generally do not change from day to day. Therefore constructing a new Scenario from a template is always a safe way to ensure you have a good starting point for your Scenario:
Only once you are satisfied that you wish other users to view and interact with a Scenario should it be moved from Draft status. Proposed and Published status' are the key to managing a consistent workflow of Schedules as they are approved and executed.
Cloning provides the ability to take a pre-existing Scenario including its configuration and data and clone a new version. When Cloning, all data including the Orders and previously scheduled Orders and Tasks are duplicated. Clones can migrate through all the standard stages of Scenario workflow as they are identical and essentially the same as every other Scenario in the system.
What’s in a name?
The way you name your Scenarios can help to organise the purpose, timing and scope of each version. It is helpful to include a Name that reflects the objective of the Scenario, and also the date range or time horizon the Scenario is addressing.
For example you could name a Scenario: "Weekly Schedule 12th April - Reduced Shifts".
This would indicate it is the standard Weekly Schedule for the 12th of April with a what-if model around reducing staff numbers.
Or you could name the Scenario: "Standard 24/5 Template" for a Scenario Template representing regular daily business operations.
Please also see the Data Templates section for more information on configuration and data model management.
