Services

BIM Quality Services for verifiable IFC model deliveries.

We translate BIM requirements into machine-checkable rules, validate IFC models and establish repeatable quality gates. Five services that build on one another.

Service ladder

How the services build on one another.

Software alone is not enough. Before a permanent IFCLint deployment, there is usually a concrete trigger: a problematic model, a data field catalogue without machine-readable rules, or a model delivery that has to be checked repeatedly. These services are built for exactly that. They can be booked individually — or one building on the next.

1
Diagnosis
Entry check

Is the IFC delivery fit for coordination and validation?

2
Sharpening requirements
Auditable Rule Set

Are our BIM requirements machine-checkable?

3
Establishing a process
Acceptance Gate

Can this become a repeatable validation process?

Headline service · Requirements engineering

Auditable Rule Set.

Written BIM requirements become machine-checkable.

Your BIM requirements already exist — in an AIA, BAP, data field catalogue or Excel. But they are written as "All shafts must be uniquely identifiable", not as "Property ObjectID must be present and not empty". We analyse your requirements, classify them by checkability, reformulate them with technical precision and translate them into machine-checkable IDS rules.

(AIA/BAP are the German equivalents of EIR/BEP and are the standard BIM requirement documents in the German-speaking market. In Switzerland the underlying catalogues are often referred to as Fachdatenkatalog or Informationslieferungsspezifikation — IDS is the international standard behind them.) The result: a reusable validation catalogue that runs directly in IFCLint.

Deliverables (Starter package)
  • Analysis of one AIA / BAP / data field catalogue
  • Extraction of the checkable requirements
  • Assessment: checkable / unclear / not checkable
  • Reformulation of approx. 20–30 requirements
  • Implementation as IDS and/or Bimtester rules
  • Test run with a sample IFC
  • Short results report
  • 60-minute handover workshop
PackageScope / When it fits
Starter20–30 requirements, 1 sample IFC
Project50–100 requirements, complete validation catalogue, pilot check with 1–2 models
Owner standardreusable validation library across multiple phases, optional maintenance
Example — what we deliver
Before (clause in BAP):
"All shafts must be uniquely identifiable."
After (IDS rule, simplified):
Object type: classified infrastructure element "shaft"
Property set: project / client Pset
Property: ObjectID
Check: present and not empty
Status: required

Price on request. Each engagement is scoped individually — we send a concrete quote, usually within one business day.

Discuss a rule set project
Entry check · Expert review

Compliance Baseline.

The quick, low-cost entry point: an external second opinion on an IFC delivery.

You have received an IFC model and want a quick read on where it stands — without setting up a full validation project. The entry check runs your model against our standard model-hygiene catalogue: classification, property sets, georeferencing, quantities, structure. You get a technical assessment — not a black-box verdict.

Deliverables
  • Automated validation run with IFCLint
  • Manual expert assessment
  • Complete findings list, grouped by critical / moderate / cosmetic — nothing left out
  • Prioritised focus recommendation: what to tackle first
  • Short report (PDF)
PackageScope / When it fits
Entry check1 IFC model, standard catalogue, short report
Extended checkmultiple models or deeper analysis
Scope note
The check evaluates data quality — structure, properties, classification. Geometric clash detection is not part of the offering.
What you are not buying
The entry check does not replace a full validation project — it shows you quickly and cheaply where your model stands. If recurring validation needs emerge from it, we turn those into a machine-checkable rule catalogue in the next step.

Price on request.

Request an entry check
Defined consulting package

Acceptance Gate.

A defined consulting package for a real model delivery.

The Acceptance Gate is a defined consulting package: together we set up a repeatable validation process for a real model delivery — defining validation rules, two validation runs, reports, BCF issues, a closing recommendation.

Deliverables
  • 1 project
  • 1–2 IFC model revisions
  • 20–30 validation rules
  • 2 validation runs
  • PDF and HTML reports
  • Optional: BCF export
  • 2 review calls
  • Closing recommendation for permanent operation
PackageScope / When it fits
Pilot project1 project, 1–2 model revisions, 20–30 rules, 2 validation runs, 2 reviews
Add-onsfurther model revisions / rule packages as needed

Price on request.

Request an Acceptance Gate
Ongoing service

Compliance Operations.

The one-off pilot becomes a permanent quality process.

After the Acceptance Gate, we take over the ongoing validation of your model deliveries as a continuous service — monthly, with a fixed validation scope and a fixed reporting rhythm. When standards or project requirements change, the rule sets are maintained along with them.

Scope
  • Monthly validation run per agreed model delivery
  • Validation report on a fixed rhythm
  • Upkeep of the rule sets as standards and requirements change
  • Expert interpretation of the findings, not just tool output

Price on request.

Request Compliance Operations
Data engineering

Evidence-backed enrichment.

Existing project documents become model data — with a source for every value.

Enriching an IFC model rarely means inventing data: the values missing from the model usually already exist in the project — in the bill of quantities, in variations, on drawings, in product datasheets and delivery notes. Just not where they are needed. We work the relevant values out of those documents, assign them to the elements and, after expert approval, write them into the IFC — then validate the result with IDS.

For every added value we record what it rests on: which document, which version, which position, and who approved the transfer.

In technical terms, the level-of-information-need framework (SN EN ISO 7817-1) describes three components of an information delivery: geometry, alphanumerical data and documentation. Evidence-backed enrichment serves the third — the values that come out of project documents.

Status levels
Status levelBasisEvidence for
specifiedBill of quantities, tenderwhat was planned
approved_designApproved design, variationswhat currently applies
deliveredDelivery note, product recordwhat was delivered
installed_verifiedHandover, photo documentationwhat is installed

This never claims that a tender position proves what was actually installed. Whoever reuses the value knows what it rests on.

Scope
  • Review of the model and the available project documents
  • Extraction of data candidates, each with source and position
  • Assignment to elements, types and material groups
  • Expert approval — only what is unambiguous or confirmed is transferred
  • Enriched IFC model
  • Validation report (checked with IDS)
  • Source log for every added value
Scope limits
Not an automated process. Analysing the documents is tool-assisted, but the transfer into the model is a professional judgement. What cannot be evidenced is named rather than guessed.
Typical triggers
  • Material and lifecycle evidence for a project or a portfolio
  • Quantities and cost estimation on a reliable basis
  • Model handover to acceptance, operations or a buyer

Price on request.

Request evidence-backed enrichment
Overview

Which service fits your situation?

Auditable Rule SetEntry checkAcceptance GateEvidence-backed enrichment
Typical trigger"We have requirements, but checking is manual.""We received this model and don't know whether it is usable.""We receive models every few weeks and want an objective process."“The model is here, but the details we need are not in it.”
OutputValidation catalogue (IDS / Bimtester)Diagnostic report with a complete findings listEstablished validation process + recommendationEnriched IFC + validation report + source log
Duration2–6 weeksapprox. 5 working daysproject-dependentfrom approx. 1 week per model
Follow-on engagementAcceptance GateAuditable Rule SetCompliance OperationsAuditable Rule Set or Acceptance Gate
Common questions

Common questions about our services.

What does a service cost?

Every engagement is scoped individually — based on model size, number of requirements and project scope. Send us a short description of your situation and we will send a concrete quote, usually within one business day.

Why should we pay if we can use IFCLint ourselves later on?

You are not paying for the validation run, but for the technical judgement: which errors are critical, which are cosmetic, what the designer should concretely change. That assessment comes from BIM practice, not from running a tool.

What happens after a rule set project?

You receive a reusable validation catalogue as an IDS or Bimtester file. You can use it yourself in IFCLint, or you book an Acceptance Gate in which we test the catalogue against a real model delivery.

Can we do the Acceptance Gate without a previously booked rule set project?

Yes. If you do not yet have a validation catalogue, we define the first 10–30 rules as part of the pilot. If you already have a data field catalogue, we integrate it.

Can the entry check also be used for infrastructure models (IFC 4.3, civil engineering)?

Yes. IFCLint supports IFC 2x3, IFC 4 and IFC 4.3. For infrastructure projects, classification is often the hardest part — and that is exactly our focus.

What if our model is confidential?

IFCLint runs in compliance with the EU GDPR, with data held in Europe. For particularly sensitive projects we discuss data-flow questions in advance and can offer on-prem options where needed (Enterprise licence).

Which service fits your next step?

Tell us briefly which situation you are in. We will get back to you with a concrete quote — or with an honest recommendation if none of the services fit.