Fleet
Fleet guides explain how Array HQ maps vehicle operations into roles, workflows, and operational data.
The operational problem
Fleet operations move fast. Vehicles return, move, get cleaned, inspected, staged, and released back into inventory. When a scan is missed or a handoff is unclear, the work can disappear from the system even if it happened on the floor.
How Array HQ solves it
Array HQ helps operators connect vehicle work to the people and events behind it. The Fleet solution area gives managers a shared model for roles, vehicle readiness workflows, and the data needed to support reporting and follow-up.
How it works
Fleet documentation is organized around the operating model:
- Roles — the frontline and supervisory roles that move vehicles through readiness.
- Workflows — how a vehicle moves from identification to rentable inventory.
- Operational data — the event trail that shows what happened, when it happened, and who performed the work.
What you'll be able to do
- Understand which roles own cleaning, movement, inspection, and reconciliation.
- Trace how a vehicle moves through the readiness process.
- Explain why completed events matter for visibility and client reporting.
- Separate high-level Fleet concepts from site-specific operating details.
Key terms
| Term | Meaning |
|---|---|
| Fleet vehicle | A vehicle moving through rental-car or fleet readiness work |
| Work event | A recorded action such as a clean, inspection, move, or ready-line placement |
| Vehicle readiness | The workflow that turns a returned or staged vehicle into rentable inventory |