Inside the service
Heavy-equipment data usually lives scattered across site spreadsheets, workshop notebooks, and supervisors' memory — nobody can reliably say how many machines are available today or retell the history of a specific unit. This service gives every machine one record under a fixed internal number that appears on every screen and report, and posts everything that happens afterward against it: movements, maintenance, fuel, inspections, incidents. A machine's full story reads from one place, from registration day to the replacement decision.
01
One identity, never duplicated
Every machine is registered under an internal number that is unique within the heavy-equipment class, independent of vehicle numbering, and that number — never a system identifier — is what appears in lists, reports, and page links. The equipment type is picked from one unified list of familiar Saudi-market names, from backhoes and wheel loaders to cranes, man lifts, and crushers, while attachments are registered as units linked to their parent machine so they never mix with standalone equipment.
02
Meters that match the work
Each unit declares its measurement system at registration: operating hours, kilometers, both together with a designated primary meter, or no meter at all — in which case its schedules run on dates. Every reading is stored in a dedicated readings log along with its source, whether it came from a field entry or an import file, so maintenance scheduling is built on documented numbers rather than supervisor estimates.
03
Bulk onboarding without chaos
Importing starts from a ready template whose Arabic columns match the form's fields exactly, and every field that is a fixed choice in the system arrives as a dropdown in the template itself, so no free-typed value lands where the system expects a defined option. Before executing, a preview shows what will be added, updated, or skipped with the reason; a row matching an existing internal number updates that record, and an empty cell keeps the stored value untouched.
04
A code that opens the field, no account
Every machine gets a printed code stuck onto it. Scanning it from any worker's phone opens a public page — no login — showing the machine's identity and offering the field actions: daily inspection, fault report, movement recording, diesel filling, accident documentation, and a photo-backed maintenance report, plus access to the machine's log. The page is multilingual and speaks the operator's language, so site workers need neither an account nor training.
05
Retirement is a documented decision
Dropping a machine from the fleet is an explicit action recorded with its reason, its author, and its date — not a mere status flip. The dropped unit automatically disappears from all operational lists, the system refuses new movements or fault reports against it, the import file skips its rows, and even approving one of its old movements never touches its preserved state. Its entire history stays readable for reference and accountability: retirement freezes the record, it never erases it.
