Scope and criteria
We agree disciplines, level of information need, deliverable list and the design criteria before any authoring starts. Ambiguity at this point is the single most expensive thing on an MEP appointment.
Mechanical, electrical, public health and fire protection engineered as one interacting set of systems rather than four models that happen to share a coordinate origin.
MEP engineering
Sizing a duct is the part of MEP engineering that a competent graduate can do. Getting that duct through a structural zone, past a cable tray, above a ceiling that has already been set by the architect, with enough clearance left for someone to reach the fire damper in ten years' time, is the part that consumes the programme. We treat the two as one activity, because a size decided without the route is a size that will change.
A model in which chilled water pipework is a collection of cylinders is not an engineering model. It is a drawing that happens to be three-dimensional. Ours are authored with system assignment, connectivity and design parameters populated during authoring, so that "check the chilled water system" is an instruction a machine can resolve rather than an instruction to open a view and look.
BIMRACE provides engineering design and BIM delivery. Statutory approvals, authority submissions and the professional stamp belong to the licensed engineer of record on the project — your practice, or the local consultant you appoint. We are explicit about this because the alternative is a delivery model that quietly leaves a liability gap.
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.
We agree disciplines, level of information need, deliverable list and the design criteria before any authoring starts. Ambiguity at this point is the single most expensive thing on an MEP appointment.
Templates, shared coordinates, naming, classification and the project parameter schema are established first. This is the unglamorous work that decides whether anything can be checked automatically later.
Spatial allocation per discipline, then primary distribution. Routes are tested against clearance and access rules as they are drawn, not after.
Calculations driven from the modelled network, with results written back to the elements so the model carries the engineering, not just the geometry.
Federation with the other disciplines, clash and clearance testing, resolution tracked to closure with the decision recorded.
Drawings and schedules derived from model state, QA rule set run before issue, and a named 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
Both, and the distinction matters commercially. Modelling means authoring to a design someone else has fixed. Design support means we make the sizing, routing and system decisions against stated criteria and you review them. Say which you want at enquiry stage and the proposal will price the correct one.
Yes, and we prefer it. Working inside your standards means the model returns to you in a state your team can maintain. Where there is no standard, we apply ours and hand over the documentation for it.
The engineer of record on the project. BIMRACE produces engineering design and BIM deliverables and a named BIMRACE engineer is accountable for the quality of what we issue, but statutory sign-off sits with the licensed professional appointed for that jurisdiction.
Re-federate, re-run the clearance and clash rule sets, and report what the change broke as a prioritised list grouped by discipline. Because the checking is rule-based rather than manual, the cost of re-checking after a change is a fraction of the cost of checking the first time — which is the practical argument for automating it.
Revit for authoring, Navisworks for federation and clash workflows, Dynamo and in-house routines for automation, IFC for exchange. Where a project mandates a different toolchain we work in it. Software names are listed to describe practice; no partnership is implied.
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.