← muthari.com

Rev 04 arrived. The factory was cutting Rev 03.

Muthari guides · for contractors who fabricate what they install

When a shop drawing is revised after fabrication has started, three things must happen, and usually none of them do. The floor must stop working to the old revision. Every stamp already made must say which revision it was made to. And someone must work out what is stranded — cut profiles, ordered glass, panels already dispatched or installed. In most companies the revision arrives as a PDF in an email, the register is updated if there is one, and the factory finds out when a fitter notices the dimension is wrong. A good record holds the built-to revision on every production stamp, treats a superseded drawing as a stop instruction rather than a filing event, and keeps every revision as an appended row, never an overwrite. This guide is about what that record must contain.

What actually happens

Rev 03 is released and the zone enters fabrication. The consultant returns comments; engineering issues Rev 04, and the register — correctly — now shows Rev 04 as the current drawing. Nobody tells the saw operator, because the register does not talk to the floor. The zone moves into coating, then to inspection, then onto a truck, all against Rev 03. Weeks later the dispute begins: which revision was this built to? The only evidence is a stack of timestamps on three different lists and the memory of whoever was on shift. Reconstructing it takes a day and convinces no one.

The loss is rarely the drawing. It is the profiles already cut to Rev 03, the glass ordered to Rev 03 dimensions with a long lead time, and the zones sharing the same drawing number that nobody thought to check.

What a good record must hold

The revision on every stamp

Each production stage stamp records the drawing number and revision it was performed to, at the moment it is made. Then "what was this built to?" is a lookup, not an investigation.

Superseded means stop

Issuing a new revision must change the state of every zone on that drawing so that the next floor move is refused until the new revision is approved and released. A superseded drawing that only changes a register row has changed nothing on the floor.

An append-only history

The old revision row is flagged superseded and kept, with the file, the actor and the time. The drawing number is minted once and kept across revisions; the revised file is mandatory. Nothing is overwritten, so the dispute above is answered from the record.

Who was told, and when

The release of a revision notifies production, and the notification is itself a record. "We sent it to the WhatsApp group" is not a record.

What is affected

The list nobody makes: material already issued to the zone, orders placed to the old dimensions, sibling zones on the same drawing, zones already dispatched or installed. A good record identifies these; a good process at least walks the list by hand.

The practice

How Muthari OS handles this. The production drawing register is append-only: revising a drawing requires the new file, keeps the server-minted drawing number, flags the prior revision as superseded, and records actor, role and time. Every production stage stamp records the drawing revision it was performed to, so the built-to revision of any zone is read from the stamp. A superseded drawing stops further floor moves on its zones until the new revision is released, and the revision notifies the production role holders. Fabrication cannot start on an unapproved drawing in the first place. The honest limit: Muthari does not yet list the affected material, open orders, deliveries or installed work for a revision automatically. The record tells you what was built to which revision and stops the floor; the walk through what is stranded is still done by a person.

Book a free demo  See the whole system →