A project operating system is the single system in which a contractor’s project work is actually performed — the goods receipt, the stage stamp, the delivery note, the installation entry, the inspection verdict — so that the project’s status is computed from those records rather than typed into a report. It differs from three neighbours. An ERP is a set of money ledgers: it knows invoices and payables, not which zone is stuck in coating behind a drawing revision. A scheduler holds the plan — what should happen and when — not what did. Project management tools hold tasks and conversations about the work, while the work itself happens somewhere else. In a project operating system the record is the work, and the status is a consequence of it.
Muthari OS is a project operating system for contractors who fabricate what they install — façade, aluminium, glass, steel, joinery and fit-out — built by contractors in the trade for companies that run a factory and a site.
Progress comes from installation entries and stage stamps; stock allocations from an append-only movement ledger; a claim’s previous quantities from the last invoice. A manually typed progress field exists and is deliberately never written. Where nothing has been recorded the screen shows a dash, never a reassuring zero.
No take-off without an approved material submittal. No factory entry without an approved drawing and issued material. No dispatch without a QC pass. No WIR until installation is complete. No handover without MIR and WIR approved. No claim without an approved budget. Each refusal says why.
The batch received against a PO, the QC decision on it, the zone it was issued to, the stage it reached, the delivery note and QR it left on, the daily installation entries, the inspection verdict, the claim line it appears in. One chain, one system, with actor and time on every link.
Every project, sorted worst-first, with the age of every stall and a health band that reads “none” as “not recorded” rather than “fine”. The manager gets the answer in three seconds; the operator gets a dense worklist underneath it.