Outcome
Reduce RFIs and variations
Around half of every variation register starts as a design miss.
The rest is pricing. The half that is documentation arrives as a stream of small items - a bollard, a lock change, acoustic panelling around an FCU - each one modest on its own and each one an RFI, a response, a price and an instruction. They get paid because arguing them costs more time than they are worth, which means the only real saving is in the ones that are never raised.
CIM reads the set the way the builder's team will and returns the ambiguities before issue: a detail that stops short, a specification covering two conditions, a schedule that disagrees with the drawing. A frequent one is cabling - a network rack that needs dual UPS-backed feeds scheduled against the allocation for a production rack.
The gap gets closed while it is a drafting task, so the question is never asked and the change order is never priced.
Before CIM
- Design misses arrive as a constant stream of small RFIs.
- Change orders get paid because arguing them costs time.
- Nobody is counting how many started in the documents.
With CIM
- Ambiguities found before issue, cited to the sheet.
- The gap closed as a drafting task.
- Fewer questions raised, fewer change orders priced.