Skip to main content

Crew Preference Designer

Set custom crew preferences to suit your operational needs, all in one place.

Updated over 2 weeks ago

S-140-V3-EN


The Crew Preference Designer is a tool that lets you easily create custom crew rules. It enables you to set more complex and tailor-made preferences to suit your operational needs. It also lets you set all those preferences in one place instead of multiple separate categories.

Configuring the Crew Preference Designer

  1. In the Scheduling module, open Preferences .

  2. Select Crew Preference Designer from the Drivers section or by using the search bar.

  3. Hover over +Preference and click +New Preference .

Set up your preference

Like other preferences, the Crew Preference Designer lets you create multiple instances, each built from the components described below.

Note: Each component affects the one that follows it, so be sure to configure them in order from top to bottom.

Context

Context is an aspect of the schedule your preference will affect. For example, to set a desired maximum number of duties, choose Duty as your context.

Contexts can be filtered. This ensures the preference only affects schedule elements that meet certain criteria. For example, you can apply the preference only to duties carried out by a certain vehicle type.

Property

Each context comes with a specific set of properties. For example, if your context is Duty, you can manage properties such as duration, count, start/end time, etc.

Value

Each context property supports only certain types of values. For example, when setting a maximum or minimum duty duration, the value must be defined as a time range.

Penalty

Finally, you can set a penalty to apply when your preference is violated. The types of penalty you set depend on previous components. For example, in a max duty count preference, you can set a fixed penalty amount per violation. In a max split duration preference, you can also set linear or exponential penalties.

To make your preference restrictive instead, you can choose the Restrict (None) option. This option is available regardless of the other components you've configured.

Setup example

In this example, we will be creating a preference that sets an allowed maximum of 25 duties carried out by double-decker buses. The penalty will be $30 per violation.

  1. In the Crew Preference Designer, click + Preference to start.

  2. Enter a name for your preference. You can also add a description to clarify its purpose for others.

  3. Since we are limiting the number of duties, we are selecting Duty in the Context drop-down.

  4. Next, limit the preference to only apply to duties operated by double-decker buses.

    • Click the filter icon that appears next to the Context drop-down.


      In the Add filters window, set the following:

      • Filter - Vehicle Type;

      • Vehicle type - is (logic operator, as opposed to is not);

      • IDs - Double Decker.

    • Click Apply.

  5. For Property, select Duty Count to define the number of duties.

  6. Set Value to Global Sum and enter 25 at the end of the range.

  7. According to our preference, every double-decker trip past the limit of 25 will cost $30. Thus, we set the Penalty to be calculated Per Violation and give it a value of $30.

The end result looks like this:

Note: You can use multiple filters at once.

More examples

The Crew Preference Designer allows for numerous combinations of components, filters, and values. This allows you to create preferences tailored to your operational needs. Here are some more examples of the preferences you can set up with this tool.

  1. Create a 5-minute sign-off event when the driver takes a meal break after a specific route:

    • Context: Sign-off (use Filter to select the route)

    • Property: Break

    • Break IDs: (select relevant IDs)

    • Value: Integer | Value: 5

    • Penalty: Restrict (None)

  2. Restrict the number of duties for a specific preference group:

    • Pref. groups: (select relevant groups)

    • Context: Duty

    • Property: Duty Count

    • Value: Global Sum

    • Range: (set range)

    • Penalty: (set if needed)

  3. Duties with Time definition Between, maximum of X duties above X platform time:

    • Context: Duty

    • Filter: Time Definition is Platform Time (set time range)

    • Property: Duty Count

    • Value: Global Sum

    • Range: 0-X

    • Penalty: Restrict

  4. Set Average Paid Time per preference group:

    • Pref. groups: (select relevant groups)

    • Context: Duty Piece

    • Property: Paid Time

    • Value: Average

    • Range: (set range)

    • Penalty: Restrict

  5. Limit the number of duties with X pieces of work:

    • Context: Duty Piece

      • Potential Break Ids: Meal Breaks

      • Split by changeover: On

    • Filter: Piece Count is Minimum of X and Maximum of X

    • Property: Duty Count

    • Value: Global Sum

    • Range: (set range)

    • Penalty: Restrict

Did this answer your question?