Service Hub

Service Hub is where servicing and maintenance across plant, vehicles, and equipment get actioned — assets sorted by what needs attention first, defects raised from prestarts, and the tools to log a service, ground a machine, or clear a backlog in bulk.

Who can use it — You need "Manage Asset Services" permission to open the page at all — there's no separate view-only access here, unlike most other Fleet & Assets pages. If you can see Service Hub, you can also log services, force a status, and run the bulk actions. See Roles & Permissions for how access is set.

Where to find it — Fleet & Assets → Service Hub in the sidebar. The sidebar item itself carries a red badge showing your open defect count, so you'll see at a glance if anything needs eyes before you open the page.

Before you start — Service Hub surfaces what your setup tells it to. If an asset has no Service Profile (or category default) with thresholds, service unit, and interval set, it won't show up as due or overdue no matter how many hours it's racked up — that setup lives in Asset Configuration.

How to use it

The page opens with five stat cards — Overdue, Due in 7 days, Grounded, Open defects, and Avg days overdue (average across the overdue cohort) — each a shortcut into the matching tab. Below that sits a row of tabs, each with a badge showing its current count: All, Defects, Due Soon, Overdue, Grounded, Greasing Due, and Compliance Due.

Every tab (except Defects) lists the same base set of assets — machines, vehicles, and equipment (attachments aren't included, since they don't carry their own service schedule) — filtered and sorted for that queue. You can filter by Type (Plant/Vehicle/Equipment), Category, and Service Profile on any tab. Clicking a row opens that asset's profile at its Health & Service tab (or Compliance tab, if you're on the Compliance Due queue).

All

Every machine, vehicle, and piece of equipment, ordered by urgency (worst first). Columns show the Asset, its Profile, Current Hours (flagged "(stale)" if the reading hasn't updated in over 7 days), Next Due (a date, or a reading + unit if there's no date target), and Service Status — one or two small badges showing hours remaining and/or days remaining, e.g. "31 hrs" or "Overdue by 12 days".

Defects

Open defects logged against your assets, pulled from failed prestart checklist items and reported damage. Three buttons above the table — Open, Resolved, All — switch which set you're looking at (Open is the default, with its own badge count). Columns: Asset, Defect, Area, Checklist Item / Source, Reported By, Assigned To, Reports (how many times the same fault has been reported — a badge lights up amber past 1), Photo, Priority, Status, Last Reported, and Days Open.

Row actions:

Assign — set who's handling it.
Triage — set Priority (Low/Medium/Critical) and Status (Open/In Progress/Resolved) together, with an optional maintenance note appended to the record.
Resolve — closes it out with an optional resolution note. Once resolved, this action disappears from the row.

Bulk actions across selected rows: Mark In Progress, Set Priority, and Resolve Selected.

Due Soon / Overdue

Due Soon shows assets inside their configured due-soon threshold (by hours remaining, days remaining, or both — whichever profile the asset has). Overdue shows assets that have passed zero on either measure. Both are ordered worst-first and use the same Service Status badges as the All tab.

Grounded

Assets currently overridden as Grounded via the Force Status action (below) — this is a manual flag, not something the calculator sets on its own.

Greasing Due

Plant assets whose category or service profile has Track Greasing switched on, and that haven't had a "greased" record logged in the last 7 days. Columns swap Next Due/Service Status for Last Greased and Elapsed, showing who logged the last grease and how long ago.

Compliance Due

Registrations, insurance, finance and lease expiries, general compliance documents, and risk assessment expiries falling due in the next 60 days — whichever is soonest for that asset. A Type filter narrows to one kind (Registration, Insurance, Finance Repayment, Lease, Compliance Document, Risk Assessment). This tab has its own View Asset row action (since Log Service and Force Status don't apply to compliance items) and clicking a row goes straight to the asset's Compliance tab.

Logging a service

From the Actions menu on any row outside Defects and Compliance Due, Log Service opens a slide-over with:

Service Performed — Serviced On (date), Reading at Service, Service Type (Minor/Major/Inspection/Repair/Other), and Service Schedule (if the asset's profile has any defined).
Billing & Parts — Service Provider, Service Cost, Invoice #, and a tags field for Parts Used.
Next Service Triggers — Next Service Reading and Next Service Date. Leave these blank and Subgrade works them out for you: from the reading plus the asset's service interval, and from the service date plus the profile's interval-in-months (or the chosen Service Schedule's own interval).
Notes — free text.

A couple of things worth knowing: logging a service clears any manual Force Status override on that asset and recalculates its status fresh. And only Minor/Major services (or anything without a type) count toward resetting the due countdown — logging a Repair, Inspection, or Other doesn't push the next-due date out.

Forcing status — grounding and clearing

The Actions menu also has a status action that toggles based on the asset's current state: Ground Asset (if operational) or Mark Operational (if grounded). Both open a small form asking for the new status and a required Reason — every change is recorded as a history row against the asset (from-status, to-status, reason, who did it, when), even though there isn't yet a dedicated place on the asset profile to browse that history back.

A manual Grounded override sticks until someone clears it — but it isn't a hard lock: if the machine goes out and gets a prestart submitted against it, the meter-reading recalculation runs and clears the override automatically, replacing it with whatever status the numbers now say. If you've grounded something for a mechanical reason (not a due-service reason), make sure it actually stays off the job — Service Hub won't stop a prestart being logged against a grounded asset.

Bulk actions

Select rows with the table checkboxes to use:

Log greased today (Greasing Due tab only) — creates a dated greasing record for every selected machine in one go, the same as ticking "Machine greased today" on a prestart, without needing to run a full prestart for each one.
Ground for inspection (All, Due Soon, Overdue tabs) — grounds every selected asset with one shared reason, recording a separate history row per asset. Assets already grounded are silently skipped rather than double-recorded.

Both show a confirmation with a summary of what will happen, and refresh the tab counts and stat cards once done.

Tips & common mistakes

An asset never shows as due or overdue. It almost certainly has no Service Profile (or category default) assigned, or the profile has no thresholds/interval set — check Asset Configuration.
"Current Hours" shows "(stale)". The reading hasn't been updated by a prestart in over 7 days — chase up a prestart on that machine rather than trusting the countdown.
Grounded an asset but it's still showing as due/overdue on the next shift. A prestart submitted after grounding clears the override and recalculates status from the current reading — grounding isn't a permanent lock, and Service Hub doesn't block the prestart itself.
Logged a service but the due date didn't move. Check the Service Type — Repair, Inspection, and Other don't reset the next-due countdown, only Minor/Major (or a blank type) do.
Same fault keeps reappearing on the Defects tab. Check the Reports count — if it's climbing, the underlying issue likely wasn't actually fixed when it was marked resolved or when the prestart said "Marked fixed".
Compliance Due tab feels empty when you know something's expiring soon. It only looks 60 days ahead — anything further out won't show until it's inside that window.

Connected pages

Asset Manager — full asset profiles, including Service History and Compliance tabs that Service Hub links into.
Asset Configuration — where Service Profiles, thresholds, and greasing tracking are set up.
Start a Prestart — meter readings from prestarts drive the service-status recalculation, and failed checklist items/reported damage are what create defects here.
Incidents — for damage or faults serious enough to warrant an incident report rather than just a defect.