Configure Bundling rules

A Bundling Rule defines the specific criteria and constraints used to aggregate individual Work Order (WO) operations into a single, combined Bundle. By creating these rules, you control exactly how work is grouped—whether by location, technical object, or schedule—optimizing field routing and dispatching.

By completing the following steps, you have successfully created and activated a Bundling Rule in the Job Bundler. The platform will use this criteria to evaluate incoming WOs, automatically generating logical bundles that reduce travel time and improve field efficiency.

Prerequisites

• You must have configuration access to the Job Bundler settings.

Create a Bundling rule

1. Navigate to Configuration > Job Bundler > Bundling Rules. and click the New button to open the configuration window.

2. In the Rule section, define the foundational settings and size limits for the generated bundles:

• Priority: Sets the processing order during the aggregation cycle. This value must be unique among active rules.

• Default: Checking this box automatically pre-populates this rule when a user manually creates a bundle from the Daily Plan. Only one rule can be the default at a time.

• Execution Options: Enable Automatic Execution for the system to process the rule automatically, or Manual Execution to allow users to trigger it. (Note: If Manual Execution is enabled, you are not strictly forced to define a Primary Bundling Criterion).

• Partial Operations: Check Automatically bundle partial operations to permit the system to generate new bundles from parent bundles that have interventions with partial outcomes.

• Bundle Size Limits: Define the required volume by setting the Min Operations Number (default is 2), Max Operations Number (default is 100), and Max Bundle Duration (in minutes).

3. Define Primary Bundling Criteria

Determine the primary matching conditions that WO operations must share to be aggregated. Select applicable options from these categories:

Technical Object: Same Technical Object, Same Parent, or Same Root.

Location: Same Municipality, Same Street, or Same Street Number.

Work Types: Same Request Type, Same Service Type, Same Facility Type, or Same Operation Type.

4. Define Secondary Bundling Criteria

Apply additional, optional constraints for tighter grouping:

Team Cardinality: Group operations that require the same team size.

Appointment: Group operations scheduled for the Same Day or the Same Slot (time interval).

5. Apply Work Order Filters (Optional)

In the Work Order Filter table, click New to attach specific WO filters previously configured (e.g., filtering by specific Codes).

Note: If you apply multiple filters, the system processes them as a union. The total pool of operations considered for bundling will include any operation that meets at least one of the selected filters.

6. Set Bundle Operation Ordering

In the Bundle Operation Ordering table, click Edit to dictate the internal sequence of operations within the final bundle.

You can sort by: Creation time, Expected work start/end date, Appointment slot start/end, or Street number logic (e.g., ascending odds / descending evens).

If multiple sorting attributes are chosen, the system uses them sequentially. For example, if two operations tie on the first attribute, the system uses the second attribute to break the tie.

7. Save and Handle Validation Errors

Save your configuration. If the system encounters conflicting logic, it will return one of the following errors to resolve:

Next Step:

• Automatically create a bundle