S-165-V1-EN
This article is a collection of use examples for the Time Definition Designer (TDD). Going over these can give you a deeper understanding of the feature and how you can make the most use of it.
If you want to learn about the feature itself, check this overview article.
Examples
1. Pulling in an existing time definition
You will often use existing time definitions as the starting point for your TDD groups, so in the first example we will show how Work Time can be included into your own work time definition:
Name your TDD group and row.
In the Context drop-down, select Other time definition. This will access the list of time definitions already existing in the system, be it through the old Time Definition preferences or others created in the TDD.
In the Time definition drop-down, select Work Time.
For Property, choose Include (aggregated).
For Value, choose All.
2. Excluding breaks and splits from Paid time
To create a simple example of what many operators might consider Paid time, we can create a new TDD group containing three rows which perform the following actions:
Include spread time.
Exclude breaks.
Exclude splits.
To achieve this, follow these steps:
Name the group paid_time so that it overrides the system’s internal definition definition of paid time and can be used during duty optimization.
Create 3 rows in the group.
In the first row, pull in the Spread Time definition the same way as described in Example 1.
In the second row, exclude breaks with the following configuration:
Context: Break
Break IDs: select all.
Property: Exclude
Value: All
In the third row, exclude splits as described below:
Context: Event
Event Types: Split
Property: Exclude
Value: All
3. Making breaks unpaid up to X minutes
In this example we’re creating a rule that states that the drivers' breaks are unpaid up to a certain duration, and paid when they exceed it.
For this definition, you can use the same rows as the previous example: include spread time, exclude breaks and splits. Note: spread time must always be included for this to work.
However, to set the maximum unpaid break duration, the Exclude breaks row should be modified using Range. Only the maximum amount of time defined in the Range field will be excluded from this Paid time definition.
For example, if you want to breaks to be unpaid for up to 90 minutes, you can set the range to 00:00-01:30 (in hh:mm). If the break time amounts to less than 90 minutes, the whole break will be unpaid. If break time is over 90 minutes, the set range means that only the 90 minutes of the break will be unpaid.
If the rule is that you want to remove up to 90 minutes per break, you can use the Exclude property, but if you want to remove up to 90 minutes total across all breaks, then you’ll want to use the Exclude (aggregated) property, so that the breaks are aggregated before the maximum Range is applied.
In the example below, we exclude up to 90 minutes (1 hour 30 minutes) per break from the Paid time definition.
This row removes (excludes) up to 90 minutes (1:30) from the group for each break
Note: you can limit paid breaks in a similar way, but in this case you should use the Include or Include (aggregated) property:
The Include property will make every break paid up to the set time limit.
Include (aggregated) will combine the durations of all breaks and make the X minutes out of that amount of time paid.
4. Excluding events
A common use-case adding or removing certain events to your time definition. For this example, we will use sign-ons during breaks.
To achieve this, you can use the Events context and select the Sign-on in Event types.
Also, use a filter to set Breaks as the only sign-on purpose for this rule:
5. Guaranteed time
Your driver agreement may state that drivers must be paid a minimum number of hours. You can use the Range field to set the minimum time that should always be reached.
In the example below, we use a base definition of Spread time, but you can set up a minimum range for any time definition or event. If the spread time amounts to less than 7 hours, this setup will still count it as 7. If the spread time is above 7 hours, the guaranteed time will be the same as spread time, since the minimum is met.
6. Calculating the makeup of Guaranteed time
Building on the Guaranteed time example above, you want to know how much time was added to the time definition so that the minimum range is met. This is possible through subtracting the original time from the makeup time.
Group 1:
Add any definition you like, or use an existing one.
Group 2:
Select Group 1 using the Other Time Definition context, and use the minimum Range like in the Guaranteed time example.
Group 3:
Pull in Group 2 with the Other Time Definition context and the Include property.
Add another row using Other Time Definition for Group 1 and Exclude.
Group 3 will be equal to the difference between Groups 1 and 2:
If no time was added to meet the Guaranteed time, Group 3 will equal 00:00.
If there was added time, that amount of time will be the value of Group 3.
Example: if the original time definition was 6 hours but the Guaranteed time is 7 hours, Group 3 will equal 1 hour.