BIMTester Requirements Generator Because your BIM actually sucks but you don't know it yet.

In order to ensure quality of the digital built environment
As a responsible digital citizen
We expect compliant OpenBIM deliverables



Need help meeting these requirements with a vendor? Read more

Scenario: Receiving a file

  1. The data must use the "{schema}" schema Example: The data must use the "IFC4" schema

    BIM data may be structured using a particular version of IFC, known as the "schema" version. Newer versions add lots of capabilities like extra parameters, new data relationships, and improved data classification. The version you choose will affect what data can be stored, and which programs have support for reading and writing that version. At the moment, you are likely to specify either "IFC2X3" or "IFC4".

Scenario: Exempt files

  1. The IFC file "{file}" is exempt from being provided Example: The IFC file "PROJECT.ifc" is exempt from being provided

    Sometimes, projects may create BIM data that is purely temporary, or as a workaround that is needed as part of their workflow, but not required from a contractual perspective. In this case, it is advisable for the requirements to explicitly exclude these BIM files so that the client knows what is included in the scope of requirements. Simply specify the name of the file that you know is not required as a deliverable.

  2. No further requirements are specified because "{reason}" Example: No further requirements are specified because "it will be superseded in a future project phase"

    The recipient may not necessarily wish to specify more BIM requirements to audit. Scenarios when this is the case may be when the recipient does not have processes in place to use the BIM data or does not know how to use the BIM data, or when the BIM data is temporary or irrelevant for any reason. In this scenario, it may be useful to specify the reason why no further audits will take place. This is the contractual equivalent to "this page is intentionally left blank".

Scenario: Project metadata is organised and correct

  1. The project must have an identifier of "{guid}"
  2. The project name, code, or short identifier must be "{name}"
  3. The project must have a longer form name of "{long_name}"
  4. The project must be described as "{description}"
  5. The project must be categorised under "{object_type}"
  6. The project must contain information about the "{phase}" phase

Scenario: Project geometry is stored

  1. The project must contain 3D geometry representing the shape of objects