Part 1
Concepts and principles
Defines the core terms, roles and the information delivery cycle, including expectations for a common data environment, status codes and approval.
Standards, information management and QA
ISO 19650 information management, the artefacts that govern an appointment, and the checks applied before anything is issued. This is the discipline the intelligence layer is built on top of.
Information standards
Structured to ISO 19650
ISO 19650 is the international standard series for managing information using BIM across the life cycle of built assets. BIMRACE structures delivery around its principles by default, on every appointment.
Part 2
Delivery phase
The part most referenced in day-to-day practice. Covers information management during design and construction, and the artefacts that govern it.
Part 3
Operational phase
Information management during operation and maintenance, and the transition from a project information model to an asset information model.
Part 4
Information exchange
Process and decision criteria for individual information exchanges, including quality criteria for what is handed over.
Part 5
Security-minded management
Applies where the sensitivity of the information requires protection — relevant to government, defence and critical infrastructure assets.
Part 6
Health and safety information
The most recent addition to the series, covering the structuring of health and safety information.
On certification. BIMRACE structures its delivery to align with ISO 19650 principles. This is a statement of working method, not a claim of third-party certification to the standard. Where a project requires certified parties, we will say so at enquiry stage rather than after appointment.
Working artefacts
The documents that govern an appointment
These are the instruments that make information delivery auditable. They are agreed before authoring begins — and they are also what an automated check is checking against.
EIRExchange Information Requirements
What the appointing party needs, when, in what format and to what level
of information need. Everything downstream is measured against this.
BEPBIM Execution Plan
How the delivery team will meet those requirements — model structure,
federation strategy, naming, coordinates, software and responsibilities.
MIDP / TIDPInformation delivery plans
The master and task-level schedules that say who issues which
container, at which milestone, in which state.
CDECommon Data Environment
The single source for project information, with status codes controlling
whether a container is work in progress, shared, published or archived.
LOINLevel of Information Need
Defines what "complete" means for an object at a given milestone —
geometry, alphanumeric data and documentation. It is the successor to inconsistent LOD usage
and removes most of the ambiguity that caused. It is also what turns a completeness check
into a factual test rather than an opinion.
Quality assurance
What gets checked before anything is issued
Six categories, run as rule sets rather than as a person opening views one at a time. The routines are live, and AI-assisted reasoning clusters failures by root cause for an engineer to review.
01
Model health Live
File size and performance, warnings, unplaced and duplicated elements, worksets, links and shared coordinate integrity.
02
Standards compliance Live
Naming, classification, view and sheet organisation, parameter completeness against the agreed level of information need.
03
Geometric accuracy Live
Origin and orientation, level and grid alignment, discipline model alignment, tolerance against the coordination datum.
04
Data completeness Live
Required parameters populated, schedules reconciling, exported data validating against the exchange requirement.
05
Coordination status Live
Open clashes reviewed, resolutions re-tested, decisions recorded against a tracked issue list with an owner.
06
Issue readiness Live
Correct status code and revision, correct formats, deliverable list reconciled against the delivery plan before upload.
Delivery methodology
A defined route from requirement to deliverable
Requirements are agreed before modelling starts, and every deliverable is checked against them before it is issued.
STAGE 01
Define
Confirm information requirements, scope, disciplines and level of information need.
STAGE 02
Plan
Execution plan, model structure, naming, shared coordinates and delivery programme.
STAGE 03
Model
Discipline authoring to the agreed standard, with data populated as the model is built.
STAGE 04
Coordinate
Federate, resolve clashes and record decisions against a tracked issue list.
STAGE 05
Validate
Automated rule sets plus engineering review, against the plan, before anything is issued.
STAGE 06
Deliver
Issue through the common data environment with the agreed formats and status codes.