Equipment Scheduler
Equipment Scheduler is the workspace-level engine that finds conflicts in shared-equipment demand across projects. It reads every project's reservations on shared cranes, lifts and hoists, detects overlaps, computes utilization per asset and proposes re-sequencing options that resolve each conflict with the lowest schedule impact.
What is the Equipment Scheduler?
Equipment Scheduler is the workspace-level engine that prevents two active jobs from needing the same crane on the same Tuesday. It reads every project's equipment reservations across the workspace, identifies overlap on shared assets, computes per-asset utilization, and proposes re-sequencing alternatives that resolve the conflict with the lowest schedule impact.
This is the engine mid-size GCs reach for when their crane log is in three spreadsheets and the dispatcher just realized two jobs both need the 240-ton tomorrow. Aggregating reservations under one workspace exposes the conflict before it becomes an emergency rental call.
When should I use the Equipment Scheduler?
Use Equipment Scheduler in the weekly equipment planning meeting, when a slipped schedule means a reservation has to move, when you are weighing whether to buy or rent another boom lift, or at a new project kickoff to check that the pool can cover your equipment needs.
- Weekly equipment planning meeting — surface conflicts before the dispatcher does.
- Project schedule slipped and the equipment reservation needs to move — check who else is affected.
- Considering whether to buy or rent a fourth boom lift — utilization data is the input.
- New project kickoff — verify equipment requirements fit the existing pool before committing the date.
When the engine detects an unresolvable overlap, chain into Schedule Risk with the conflict pre-loaded — the schedule simulator models the delay impact and proposes pull-forward actions for the affected projects.
What do I upload to the Equipment Scheduler?
Nothing — this is a workspace-scoped aggregation engine. It reads the equipment assets table (workspace-scoped) and the equipment_reservations on every active project. The output is computed from those rows; there's no document upload step.
What the engine needs is well-maintained equipment data: assets identified by name + class, reservations with start/end dates per project, and accurate active-project status flags. Garbage in, garbage out.
How do I run the Equipment Scheduler?
To run Equipment Scheduler, open it, set the date window, run the analysis, read the conflict list, check utilization per asset, apply or reject the re-sequencing proposals and escalate any conflict that will not resolve.
Open the engine
Sidebar → Engines → Equipment Scheduler. The engine is workspace-scoped, not project-scoped — the toolbar shows the workspace name.
Set the date window
Default is rolling 90 days. Stretch to 180 days for long-lead planning. Tighten to 30 days for tactical work.
Run analysis
10–20 seconds. The engine scans every reservation across every active project.
Read the conflict list
Each detected overlap is one card: the asset, the two projects, the overlap dates, the proposed resolution.
Check per-asset utilization
For each shared asset, the engine reports utilization percentage over the window. Low utilization = underused; high = at risk of conflicts.
Apply or reject re-sequencing proposals
Each conflict card has a proposed move. Apply pushes the new reservation into the project schedule. Reject keeps the conflict open for manual handling.
Escalate stubborn conflicts
Conflicts you can't resolve internally chain into Schedule Risk (for impact modeling) or Procurement Tracker (for external rental).
How do I read the Equipment Scheduler results?
The result is a conflict list with per-asset utilization, re-sequencing proposals, a workspace heatmap and external rental candidates.
One card per detected overlap. Shows asset, projects, dates, proposed resolution. Severity badge if the conflict touches a critical-path activity on either project.
Utilization percentage and reservation density chart for each shared asset over the date window. Identifies under-used assets you could divest.
For each conflict, the engine proposes a move (shift Project A's reservation by N days). Shows the float impact on each affected project.
Calendar view across the date window showing every asset's reservation status. Hot spots are immediate eyeballs on the next conflict.
For unresolvable conflicts, suggested external rentals with rough day-rates. Hands off to procurement.
Every control, explained
Run analysisConsumes one run. 10–20 seconds.
Date windowRolling window for the analysis. 30 / 60 / 90 / 180 day presets.
Filter by asset classNarrow the conflict list to cranes / lifts / hoists / generators / pumps / other.
Apply proposalPushes the proposed re-sequence into the affected project's schedule. Logs an audit trail entry.
Reject proposalKeeps the conflict open. Useful when you know a contextual reason the proposal won't work.
Chain to Schedule RiskOpens Schedule Risk with the conflict's affected projects pre-loaded for impact simulation.
Chain to Procurement TrackerOpens Procurement Tracker pre-filled to track an external rental as the conflict resolution.