Load basis
Establish connected and maximum demand, diversity and the distribution strategy before routing.
The discipline with the most flexible routes and the least respected space allocation — which is exactly why its coordination failures surface last and cost most.
Electrical
Cable tray can go almost anywhere, so on most projects it goes wherever is left. That works until the cumulative result is a tray route with eleven changes of level, no maintained separation from the chilled water above it, and no clear access for cable pulling. Flexibility is a property of the early design and a liability in the late one. We allocate the containment zone at the same time as the mechanical zone, and test the separation requirement as a rule rather than as an instruction in a specification.
A cable tray drawn as a generic object is a rectangle. A cable tray carrying its fill percentage, its circuits and its segregation class is a thing the model can be asked about — including whether the route it was given still satisfies the segregation requirement after three rounds of coordination moved it. The difference is entirely in how it was authored.
A board schedule that fits on a page can still fail when the board, its working space, its escape route clearance and the containment arriving at it are put in a riser cupboard dimensioned from an earlier revision. We model the working space as a clearance zone, because that is the only form in which a checking routine can test it.
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.
Establish connected and maximum demand, diversity and the distribution strategy before routing.
Containment zone in the void and riser allocation, agreed alongside mechanical rather than after it.
Main tray and busbar routes set against structure and mechanical, with separation designed in.
Lighting, small power and specialist systems placed against the architectural layouts.
Board clearance, escape route and pulling access tested as clearance rules.
Panel and load schedules derived from model state, QA rule set run, engineer signs.
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
Yes. Deriving them from model state rather than maintaining a parallel spreadsheet is the point — it removes the most common source of drift between the electrical drawings and the electrical schedule.
We can start, but the sequence matters. Containment routed before the primary mechanical distribution is fixed will be re-routed, because ductwork has far less freedom. We will say so rather than produce work that has to be redone.
As a geometric rule across the federated model, at the separation distance the project standard requires, rather than by visual inspection of sections. It re-runs on every federation, which is what makes it useful after a change rather than only at first issue.
Bracket and support layouts and builders work drawings are construction support deliverables and can be appointed. State the level of information need at enquiry stage.
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.