The observation is caught before it becomes a breakdown

An excavator's checklist is not a truck's: general safety, engine and fluids are shared, then each type adds its own sections — hydraulics and tracks for tracked equipment, tires and brakes for vehicles. Templates are managed at company level in numbered versions that only the administrator edits, and every inspection stores a snapshot of its template and version at the moment it was filled — so a later template change never rewrites the meaning of an old inspection.

Every item and every section title is written in Arabic, English, Urdu and Hindi inside the product itself, not through external translation — so the driver reads each item in his own language and answers from understanding, not guesswork. Each item takes one of three answers — sound, remark, or not applicable — and the whole inspection carries a result of pass or needs action, with a day or night shift and photos backing what was recorded.

A submitted inspection does not enter the asset record directly; it waits in a review queue where the supervisor approves or rejects it, and only the approved one is written as a permanent entry in the machine's history. On approval, the cumulative meter reading is captured into the meter ledger under a monotonic guard — so the preventive-maintenance engine feeds off the most frequent reading source in daily operations without a single extra entry.

An inspection that ends as needing action does not stop at documentation: the system automatically creates a fault report gathering the failing items grouped under their sections in one clear description, carrying the inspection's photos, its reporter's name and its location, then follows the usual incident cycle from diagnosis to documented closure. That closes the gap where remarks used to vanish between the inspection sheet and the workshop — early detection becomes a procedure, not an intention.