Level of information need uplift
Agree what has to be modelled to installation standard and what does not. This is the scope conversation and it has to be explicit.
Output produced for the people installing the work, at the detail and tolerance installation actually requires — not at the level a design model happens to hold.
Construction support
The level of information need for installation is different in kind, not just in degree: real fittings rather than generic ones, real connection detail, real support positions, and tolerances that reflect what can actually be manufactured and carried through a door. Uprating a design model to fabrication is a scoped piece of work. It is not a setting.
Penetrations, cast-in items and structural openings are the deliverable with the hardest deadline on the project and the one most often produced last. We take the coordinated model, extract every penetration, and issue it as a drawing and a schedule that the structural engineer can actually review — before the pour, not as an RFI afterwards.
A record model that is the design model with a new title block is a liability dressed as a handover deliverable. We update against site information and state clearly what has been verified and what has not, because an operator who trusts an unverified record model will find out the hard way.
Deliverables
Any of these can be appointed on their own or combined. Nothing here depends on buying the intelligence layer, which is not for sale in any case.
How it runs
Sequence is not a formality on this kind of work. Most of the expensive rework we are asked to fix was produced by doing step four before step two.
Agree what has to be modelled to installation standard and what does not. This is the scope conversation and it has to be explicit.
Generic content replaced with the selected products, because fabrication detail is a property of the actual item.
Re-run the clash and clearance rule sets against the uprated model. Real fittings clash where generic ones did not.
Bracket layouts and penetration extraction, scheduled and issued for review.
Shop, spool and BWIC drawings derived from model state.
As-built updated against verified site information with status stated.
What we need to start
Missing any of these is survivable. Not knowing which of them are missing is not, so we establish it at enquiry stage rather than at forty per cent.
Automation
Every line carries its real status. Three of the four states on this site mean "not yet", and we use them.
Scope boundary
Published because a scope boundary discovered at month three is a dispute, and the same boundary stated at enquiry stage is just information.
FAQ
Usually yes, and the honest answer depends on how the design model was authored. A model with a clean parameter schema and correct system assignment uprates economically. One without often costs more to uprate than to re-author, and we will tell you which case you are in before you commit.
Yes. Penetration extraction from the coordinated model is automated, and the output is a dimensioned drawing plus a schedule the structural engineer can review — issued before the pour rather than raised as an RFI after it.
Yes. Construction support is most often appointed by the installing party rather than the design team, and the deliverable list above reflects that.
Stated verification status, element by element. A record model that does not distinguish between what was verified on site and what was carried over from design is worse than no record model, because it invites trust it has not earned.
Related
Engineering enquiry
Send a scope, a drawing set or the workflow you want this applied to. You will get a technical response on approach, disciplines, deliverables and what is realistically automatable — from an engineer, not a sales desk.