A booking connects an order to the element planned for that work. The Scheduler presents bookings over time and can include shifts and availability alongside them.
Generic requirements and specific assignments
Elements and bookings distinguish generic requirements from specific assignments. A generic requirement identifies a position or type of item. A specific assignment identifies the selected person, facility or asset.
The element-booking workflow can fill a compatible unassigned generic booking with a specific resource, facility or asset. The generic booking must be active, match the relevant type and generic identity, and have no active actual records. When no eligible generic booking is available, the workflow creates a booking for the selected element.
This distinction matters when reviewing an assignment: filling a requirement and adding another booking have different effects on the planned work.
Order views and the Scheduler use related booking data
Bookings can be retrieved by order, element, project and master project. Scheduler queries organize booking data by time and selected elements. The displayed result also depends on the view's date range, status selection and filters.
When a booking appears in one view but not another, compare:
- The booking ID and its order.
- The selected element and date range.
- The booking and order statuses included in the view.
- The user's access and the active filters.
Matching names alone do not establish that two views show the same record.
Recorded work constrains Scheduler date changes
When the Scheduler adjusts a booking that has actuals, the proposed booking range must still contain the recorded actual range. A range that excludes those actual times is not applied through that update path.
Booking dates describe planned work. Actual dates describe recorded work. A correction to actual time belongs on the actual record; changing the schedule is a separate operation.
Conflict behavior follows configuration
Order classes control conflict checking. Elements have double-booking settings, and bookings have settings that determine participation in conflicts. These controls work together when ShowMgr evaluates scheduled work.
A conflict indicator and a blocked save are different outcomes. Review the class, element and booking settings when explaining why a scheduling operation is allowed or flagged.
Time-zone context affects display and updates
ShowMgr carries the user's time-zone context through scheduling and actual-entry operations and converts values to UTC in the corresponding service paths. Local display time and integration timestamps therefore need to be interpreted in their respective contexts.
When comparing overnight work or dates around a daylight-saving transition, include the full date, time and time zone. Comparing only the displayed hour can hide a difference in the underlying time.