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.
Technology & standards
Information management structured to ISO 19650, the artefacts that govern an appointment, and the checks applied before anything is issued.
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.
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.
Working artefacts
The documents that govern an appointment
These are the instruments that make information delivery auditable. They are agreed before authoring begins.
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.
Quality assurance
What gets checked before anything is issued
01
Model health
File size and performance, warnings, unplaced and duplicated elements, worksets, links and shared coordinate integrity.
02
Standards compliance
Naming, classification, view and sheet organisation, parameter completeness against the agreed level of information need.
03
Geometric accuracy
Origin and orientation, level and grid alignment, discipline model alignment, tolerance against the coordination datum.
04
Data completeness
Required parameters populated, schedules reconciling, exported data validating against the exchange requirement.
05
Coordination status
Open clashes reviewed, resolutions re-tested, decisions recorded against a tracked issue list with an owner.
06
Issue readiness
Correct status code and revision, correct formats, deliverable list reconciled against the delivery plan before upload.
In development
The intelligence layer we are building
Alongside delivery work, BIMRACE is developing an internal platform that reads model information and assists with review, checking and reporting.
It is described here as work in progress because that is what it is. It is not a released product, it is not available for licence, and nothing on this site should be read as a commitment to a feature or a date.
The reason it exists is the same reason we model information-first: once a model's data is structured and reliable, a large share of routine checking stops needing a person to do it by hand.
Being built toExtract model information
Read elements, parameters, systems and relationships from the model as structured data.
Being built toRun rule-based checks
Validate a model against project rules, standards and internal practice automatically.
Being built toReport engineering analytics
Turn model data into quantities, distributions and system behaviour.
Future capabilityNatural-language model queries
Ask questions of BIM and engineering data in plain English.
Platform architecture