Order Template
Overview
Order templates in our system allow for sophisticated management and configuration of orders, including the ability to split orders into multiple segments.
Order template is used when we want to influence the creation of an order. It is common that production orders are scheduled and maintained in a more aggregated level compared to how they need to be executed.
A common case is that we schedule production on a “Line level” but we need to execute the production at an equipment level.
As an example, in case of a bottling line, it's common to schedule at the line level but we want to track production at the Depalitiser, Filler, Labeller and Palletizer level. We use order template to perform the conversion between the line level to the equipment level.
This document will guide you through the process of understanding, creating and configuring order templates.
The video below guides you through the process of creating and using Order Templates.
Accessing Order Templates
Go to Settings > Asset Hierarchy > Order Templates.

Creating an Order Template
When creating an order template, you need to think about a parent-child relationship between levels of productions. Which level A of production (the parent) that you want to map onto another level B of production (the child).
The available levels are: - Asset Class > Asset > Material Group > Material > Attribute
Step-by-Step
Go to the page and click the Create button to open the modal.

Fill in the required fields.
In this example, we map orders created on the LINES Asset Class level to new orders on the Fillers Asset Class level:
Name: Fillers
Operation: FILLER
From Asset Class: LINES
To Asset Class: Fillers
Since we are working at the Asset Class level, assets falling under these classes will inherit this mapping rule

Click Save and open to expand and configure the full settings of the Order Template.
Understanding Basic Information Fields
Upon opening the entity you will be presented will multiple configuration options like the image attached below and this table will help you go through what they all mean.

ID
This field is automatically populated for the entity by TilliT.
Name *
The name of this Order Template.
From Asset Class / Asset / Material Group/ Material / Attribute
The parent level of entities that you want to map from. For this example, we want to map every order created on the Lines level to all Fillers under the Fillers Asset Class
To Asset Class / Asset / Material Group / Material
The child level of entities that you want to map to. For this example, we have put Fillers under To Asset Class. If we want a specific filler to be mapped on, we can edit the To Asset field instead.
Segment Code From
Code used to filter or specify the source segment for the mapping. Leave empty if no specific segment restriction is applied.
Operation *
The text attached to the end of the mapped's order's names to differentiate all the different levels you have mapped to. For example if the parent order name is "PO0001", the filler child order will be named "PO0001 - FILLER".
Variable Quantity *
The amount of order quantity the child level entities will receive in multiplication. For example if the quantity you put in the parent is 100 units to produce, and the variable quantity is 1.2 then the child order will need to fulfill 100 * 1.2 = 120 units.
Fixed Quantity *
The amount of order quantity the child level entities will receive in addition. For example if you put 100, and the parent order has production quantity 100, your child production is 100 + 100 = 200. Note: Variable and fixed quantity values can be combined in configuration.
Constant Delay in Minutes
Same philosophy as Fixed Quantity, can be used to model delay in the orders being mapped. If you put 20 minutes, the order will only go to the child entities 20 minutes after order creation on the parent level.
Delay In Minutes
Same philosophy as Variable Quantity, can be used to model variable delay in the orders being mapped based on the parent order.
Fixed Changeover Minutes
Sets a constant changeover time in minutes applied directly to child entities.
Variable Changeover Minutes
Applies a proportional multiplier to the parent's changeover time (e.g., setting 0 removes changeover for child entities).
Fixed Default Run Rate
Sets constant base run rate added directly to the default target speed of child entities.
Variable Default Run Rate
Multiplier applied to the parent's default run rate to adjust the child entity's target speed.
Fixed Scheduling Run Rate
Fixed run rate value used by the scheduling engine to plan order duration for child entities.
Variable Scheduling Run Rate
Multiplier applied to the parent's scheduling run rate to scale planned order duration for child entities.
Downtime Type
The status that will be defaulted to when the asset is not running but the order is. In this example, the status "UNPLANNED" is set for the Downtime Type, which will alert actions or notifications based on how you configure it.
Changeover Downtime Type
The status that will be defaulted to when the asset is in changeover but the order is running. In this example, the status "PLANNED" is set of Changeover Type in the case an order is to run on an asset in changeover.
The Changeover downtime type has been removed. Any assets previously configured with the Changeover downtime type have been automatically migrated to use Planned. The default changeover downtime type when changeover is on schedule is now Planned.
Configuring Components (BoM)
The final step in configuring an Order Template is setting up the Bill of Materials (BoM), also known as Components in TilliT.
This allows you to set up specifically which child entities you want to use materials of the BOM that were part of the parent order.
Scroll down past the Basic Information section to find the Components panel, then click Create.

A modal will appear, prompting you to select the Material Group and Material. In this example, to map all Glass materials to the Fillers, select the Material Group. If you need to specify a particular Glass material, select it from the dropdown.

Once configured correctly, the component will appear in the table as shown below.

How it works in TilliT
In the example below, a new order is created on asset Line 1, which belongs to the LINES Asset Class configured previously. (Check out Create an Orderif you are not sure how to create an Order in detail.)
Two additional Order Templates were also created to map orders from the Line level down to Depalletisers and Palletisers.

After completing the order details, navigate to Line 1. You will see three distinct child orders created with their respective operations: DEPAL, FILLER, and PAL.

Last updated