Heavy Machinery & Fleet
Dispatching equipment to a jobsite, fueling it, and keeping it running — the three screens that manage every piece of powered machinery from mobilization to breakdown.
What this group does
An excavator, generator or crane moves through the same lifecycle on every job: it gets allocated to a site and zone, it burns fuel while it works, and eventually it needs maintenance — sometimes planned, sometimes an emergency breakdown that stops work cold. These three screens track that lifecycle end to end, and each one reads the same equipment's live allocation record to auto-fill fields (engine hours, current jobsite) rather than asking the operator to re-enter them.
All three screens share their record types and cross-screen sync logic. The Jobsite and Zone pickers on all three screens are a type-ahead search field rather than a plain dropdown, so operators can find a site or zone instead of scrolling a flat list.
1. Equipment Allocation
Purpose: Dispatch a piece of fleet equipment to a jobsite and zone for a shift, track its planned-vs-logged engine hours, and hand it off to Fuel Consumption and Field Maintenance once it's on site.
Key features
- Dispatch record — equipment code/name (picked from a searchable list of available fleet assets), jobsite, zone, operator crew code, telematics log ID, day/night shift, and a mobilization-checklist-attached toggle.
- Five-state status pipeline —
scheduled→in_transit→active_on_site→released, with a separatebreakdown_standbystate entered directly from a field breakdown report. - Utilization gauge — a per-row progress bar comparing logged engine hours against planned task hours, colored amber at 75% and red once logged hours meet or exceed the plan.
- Sync to Task — a per-row picker that links the allocation to a Site Execution group Subcontractor Task, so the equipment's usage is traceable to the work item it's actually supporting.
- Report Field Breakdown — a dedicated modal that captures a breakdown reason and flips the allocation's status to
breakdown_standbyin one action.
Integration triggers
| Action | What it does |
|---|---|
| Sync to Task | Links the allocation to a Subcontractor Task from Site Execution, tying equipment usage directly to that task's progress. |
| Report Field Breakdown | Sets status to breakdown_standby and records a breakdown ticket reference on the allocation — the same equipment code is what Field Maintenance's work-order form looks up to auto-fill the current engine-hour meter reading and jobsite. |
2. Fuel Consumption
Purpose: Log every fuel/DEF/electricity dispense against a piece of equipment, deduct it from the site's bowser inventory, and flag dispenses that look abnormal against a baseline burn rate.
Key features
- Three fuel types —
diesel,def_adblue,electricity_kwh, each with its own baseline liters/kWh-per-engine-hour constant used only to compute the efficiency-variance indicator. - Equipment auto-fill — selecting equipment via the combobox pre-fills the engine-hour meter reading and jobsite from that equipment's current allocation.
- Efficiency variance bar — compares the dispensed quantity against an assumed 8-hour-shift baseline expectation; a dispense flagged abnormal or scoring ≥150% is highlighted red with a warning icon.
- Bowser source picker — refueling source is chosen from the site's bowser inventory, scoped to the selected jobsite, and shows each tank's remaining quantity inline in the option label.
- Push Operational Expense to Daily Log — a per-row action that is disabled once a voucher has already been pushed.
Integration triggers
| Action | What it does |
|---|---|
| Save a new dispense | On the initial save (not an edit), if a refueling source was picked and quantity > 0, the site's fuel inventory is deducted automatically — reducing the dispensed quantity from that bowser's remaining inventory and recording which source tank it came from. |
| Push to Daily Log | Records the fuel expense into that day's Daily Site Log (Site Execution group) and marks the record as pushed, disabling the button so the same voucher can't be pushed twice. |
3. Field Maintenance
Purpose: Log a maintenance work order — preventive, hydraulic/mechanical repair, or emergency breakdown — against a piece of equipment, track parts consumed and downtime, and flag work orders that put a project milestone at risk.
Key features
- Three maintenance types × three severities — type is
preventative_pm/emergency_breakdown/hydraulic_mechanical_repair; severity iscritical_stop/major_routine/minor_field_fix, each with its own badge color. - Parts-replaced line list — a searchable picker (with the ability to add a new part on the fly) against the warehouse parts catalog builds a quantity-editable list of parts entries attached to the work order.
- Downtime critical-path flag — a row is marked red when the work order is
critical_stopseverity, not yetcompleted_passed, and either has ≥4 downtime hours with no milestone linked, or is linked to a milestone that isn't yetcompleted. - Auto-Request Spare Parts — a confirm modal that raises a spare-parts request from the work order's parts list, disabled once a request already exists or if no parts were logged.
- Update Milestone Impact — a picker modal that links the work order to a Site Execution Project Milestone; if the work order is already
completed_passed, a note warns that confirming will release the equipment's allocation back to available. - Safety Clearance Sign-off — a required toggle before the work order can be considered closed out, independent of its status field.
Integration triggers
| Action | What it does |
|---|---|
| Auto-Request Spare Parts | Raises a spare-parts request from the work order's parts-replaced list and records the resulting request on the work order, disabling the button afterward. |
| Update Milestone Impact | Links the work order to the selected milestone; Milestone Progress's data is refreshed to reflect the link, and if the work order was already completed, the equipment's Equipment Allocation record is released and the maintenance list is refreshed to reflect it. |
End-to-end data flow
| Source screen | Action | Target screen / record |
|---|---|---|
| Equipment Allocation | Sync to Task | Linked → a Subcontractor Task in Site Execution |
| Equipment Allocation | Report Field Breakdown | Status set to breakdown_standby → equipment code visible to Field Maintenance's work-order intake |
| Fuel Consumption | Save new dispense with a source tank | Site bowser inventory quantity reduced automatically |
| Fuel Consumption | Push Operational Expense to Daily Log | Fuel cost line appended to that day's Daily Site Log (Site Execution) |
| Field Maintenance | Auto-Request Spare Parts | A spare-parts request raised from the parts-replaced list and linked back to the work order |
| Field Maintenance | Update Milestone Impact | Linked → Milestone Progress (Site Execution); if already completed, the linked Equipment Allocation is released |
AI Assistant on every screen in this group
Equipment Allocation, Fuel Consumption, and Field Maintenance each carry an embedded AI Assistant — the same right-edge panel used across TotalApp, opened from the vertical AI Assistant tab. Every panel reads the live rows on screen (or your current selection), can summarize, flag data gaps (missing operators, unchecked mobilization checklists, missing safety clearance), and answer natural-language questions in Markdown (Turkish or English), and ships with Save as Report and Add Knowledge.
Pages in this section
Frequently Asked Questions
critical_stop, status is not yet completed_passed, and either it has no linked milestone but has logged 4 or more downtime hours, or it is linked to a milestone that is not yet completed.completed_passed when you confirm the milestone link, the associated Equipment Allocation is released back to available and the maintenance list is refreshed.