> For the complete documentation index, see [llms.txt](https://help.tillit.cloud/tillit/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tillit.cloud/tillit/knowledge-base/scheduler.md).

# Scheduler

TilliT Scheduler helps manufacturers create, manage, and publish production schedules. It models complex operational constraints — equipment capacity, personnel availability, material requirements, and changeover times — so that what you schedule is what actually happens on the shop floor.

## Navigation

***Scheduler*** is accessible from the main TilliT navigation menu. The Scheduler menu contains:

| Menu Item          | Description                                                    |
| ------------------ | -------------------------------------------------------------- |
| **Scenario**       | Opens the Scenario Kanban board for managing schedule versions |
| **Live**           | Opens the currently active Live Scenario                       |
| **Planned Orders** | Opens the order list for creating and managing orders          |
| **Data Templates** | Opens configuration data shared across scenarios               |

<figure><img src="/files/dkz87jtLTK3G82FcbI7b" alt=""><figcaption></figcaption></figure>

## Key Concepts

| Concept           | Description                                                                                                                                                                   |
| ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Scenario**      | A self-contained scheduling environment where you create, model, and refine a production schedule. Scenarios move through a workflow: Draft → Proposed → Published → Complete |
| **Live Scenario** | The single active scenario whose orders are synchronised with TilliT Digital Operations for execution                                                                         |
| **Data Template** | A reusable set of master data (equipment, personnel, materials, operations, availability, changeovers, optimisation) shared across scenarios                                  |
| **Order**         | A production request with a quantity, operation, due date, and priority that needs to be scheduled                                                                            |
| **Optimisation**  | Automated scheduling using AI algorithms that balance competing objectives like changeover time, makespan, and on-time delivery                                               |
| **Allocation**    | The assignment of specific resources (equipment, personnel) to each step of a scheduled order                                                                                 |

## User Roles

| Role              | Permissions                                                    |
| ----------------- | -------------------------------------------------------------- |
| **Administrator** | Full access — create, edit, delete scenarios and configuration |
| **Scheduler**     | Create and manage scenarios, schedule orders, run optimisation |
| **View-only**     | View scenarios and schedules without editing                   |

{% hint style="info" %}
Scheduler requires a location to be selected before use. Click your profile icon and choose **Select Location** to set your site.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.tillit.cloud/tillit/knowledge-base/scheduler.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.