This reference outlines the fields and data attributes available within the Bundle Detail window. This interface serves as the comprehensive control center for a specific Bundle, displaying its aggregated scheduling requirements, mandatory resources, and underlying creation criteria.
The Bundle Detail window is accessed within the FSM Platform via the Bundle Monitor.
Global Bundle Detail Actions
Persistent actions are located in the detail page, providing the following global actions:
-
Unbundle: Cancels and dissolves the specific bundle back into individual operations.
-
Lock / Unlock: Secures the bundle from being canceled, or removes the lock.
-
Refresh: Updates the bundle data and the statuses of any related operations.
Bundle detail tabs
The top section of the window organizes the core attributes of the Bundle into four distinct tabs.
Bundle Summary Tab
Contains the foundational identification and scheduling window data.
|
Field |
Description |
|
Id / Name |
The system-generated ID and the user-editable Name of the bundle. |
|
Operations Center |
The specific branch or center responsible for the bundle. |
|
Creation Date & User |
Timestamp and user ID of the person or system that generated the bundle. |
|
Bundle State |
The current operational status of the bundle. |
|
Coordinates |
Geographic coordinates, automatically inherited from the first aggregated operation. |
|
Work Execution Interval |
The required date range for the work (min "From" and max "To" of all operations). |
|
Appointment Slot |
The closest appointment date and time among all the aggregated operations. |
|
Microcluster |
The scheduling area, calculated based on the associated coordinates. |
|
Locked |
Flag indicating if the bundle is protected from cancellation. |
|
Starting Point Coordinates |
The initial coordinates used specifically for topological reordering algorithms. |
Scheduling Data Tab
Details the aggregated time and dispatching requirements.
|
Field |
Description |
|
Duration |
The sum of the residual duration of every single operation. |
|
On duty only |
Indicates at least one operation requires "On duty" status. |
|
Exclude if available On Call |
Indicates at least one operation has this specific scheduling exclusion. |
|
Multi-day |
Indicates at least one operation spans multiple days. |
|
Minimum Daily Time |
The maximum value among the minimum daily times required by the single operations. |
|
Minimum Time for Suspension |
The maximum required wait time between scheduling consecutive operations. |
Resources Data Tab
Outlines the personnel and skill requirements needed to execute the bundle.
|
Field |
Description |
|
Team Cardinality |
The maximum team size required among all the aggregated operations. |
|
Mandatory / Preferred Resources |
The combined union of all specific resources requested by the operations. |
|
Required Skill Table |
Lists all required skills and the maximum cardinality needed for each. |
Bundle Criterion Data Tab
Displays the rule parameters used to generate the bundle (if applicable).
|
Field |
Description |
|
Execution Type |
Indicates if the bundle was created via Manual or Automatic execution. |
|
Technical Object Type |
Displays if aggregation used Same Technical Object, Parent, or Root. |
|
Location Bundling Type |
Displays if aggregation used Same Municipality, Street, or Street Number. |
Related Resources