LogiKal-class tools are excellent at what they do — calculation, cutting lists, machine data. And they stop at the factory door. The project around them — who ordered what, which batch arrived, what got issued to which zone, what shipped, what was installed and what can be claimed — usually lives in WhatsApp and an Excel nobody fully trusts. Muthari OS is that missing layer, and it runs beside your fabrication tools, never instead of them.
Every receipt is a batch on a project lane with a QC status and, when you record it, the supplier’s own batch or heat number. Issues draw approved stock first from the right project. A borrow from another project needs an approval and stays in the ledger forever.
Take-offs raise requisitions against catalogue items, POs route through a real approval ladder, goods receipts write the stock and queue QC by themselves — and a shortfall auto-raises a gap requisition.
Every zone of every job on one matrix with the age of every stall. The morning view sorts your projects worst-first, computed from the records — nobody types a status.
An aluminium fabricator's project control lives and dies on two things the office rarely sees: the finish batch and the offcut.
Shop drawings drive the cutting list, and the cutting list is produced in the fabrication software that optimises bar usage — that is where it belongs and it should stay there. What the project needs from that stage is different: which zones are released to cut, against which drawing revision, and what material that consumes.
Profiles are ordered by system, die and length, and then powder-coated or anodised. Finish is applied in batches, and two batches of the same nominal colour can differ enough to be visible when installed side by side on one elevation. Managing that is a material-identity problem: the receipt has to carry the supplier's batch reference, the batch has to keep that identity in stock, and issuing to a zone has to record which batch went where. Otherwise the mismatch is discovered on the facade.
Deliveries arrive partially against long orders. Each receipt reduces the outstanding balance on the order, raises stock as a batch, and goes to quality — profiles are checked for coating defects, twist and transit damage at receipt, not at assembly. Material issued to a zone leaves a movement record, so the question "what did we actually use on level 8?" has an answer that is not an estimate.
Cutting, machining, assembly, hardware and gasket fitting, with a quality decision before dispatch. Stages are stamped per zone with the drawing revision they were built to, which is the only reliable defence when a revision arrives mid-run.
Zones are dispatched under a delivery note and received on site against what arrived. Installation is recorded per zone against its quantity, inspections follow, and the claim is built from those records. Because progress is derived from stage stamps and installed quantity rather than reported, a package running thirty jobs at once can be sorted by urgency instead of by whoever called last.
The same operational chain runs every specialist trade — a factory and a site against one contract. Why specialist contractors need a different model, and what construction operations software is. For the broader category, see construction project management software.