Site installation in Muthari OS is recorded daily, per zone, by the people doing it — built for contractors who fabricate what they install. Each entry adds a quantity to the zone; the running total can never exceed the zone’s BOQ-derived quantity, and a correction is a new entry, never an edit. Photos taken with the entry are stamped with the person’s name and the time before they are uploaded. Material and work inspection requests are raised against the zone with A/B/C/D verdicts, and the zone cannot be handed over until both are approved. Asked ‘what did we install on the east elevation, and can we prove it?’, the answer is a list of dated entries with names and photos, not a foreman’s estimate.
Install quantities accumulate; the system refuses any entry that would take the zone past its quantity. Reaching 100% prompts the person to mark completion — it never stamps it for them.
Per-entry photos keyed to the entry’s own time, canvas-stamped with name and timestamp before upload, with server-enforced caps. Every download is logged.
Installation cannot be logged on a zone that site has not received. Starting before the material inspection is approved is possible only as a recorded ‘urgent start’ — a fact on the record with a name on it, not a hidden bypass.
A work inspection request needs an approved material inspection and a completed installation. Verdicts A to D drive the zone’s state — C resubmits, D rejects — and repeat visits are stamped as repeats with the rounds counted. Comments and photos attach to each.
Handover requires approved MIR and WIR; then the zone record locks. A site rejection back to the factory is a typed rework round with photos and a rolled-back stage, not a message in a group chat.
The zones site receives arrive through Logistics; installed quantities and approved inspections are what Commercial claims against. Muthari OS is built by contractors in the trade.