Validation Service Updates

[Evandro]

v.0.7.4

17 Apr, 2025

• 1 new Normative IFC Rule:

  • BBX001 – Consistent Geometry Bounding Box

• 4 new activation rules:

  • AXG000 – Axis Geometry
  • GDP000 – Grid Placement
  • ALS000 – Alignment Geometry
  • PJS000 – Project Existance

Activation rules are used to verify the presence of specific IFC entities. These rules never return an error, and are used mainly to extract metrics from files.

• Platform update:
  • Improved performance by inserting multiple validation results in a single database query, reducing load on the database.
  • Added detailed documentation to help developers write Gherkin rules more easily.
  • Various backend platform improvements.

[Evandro]

v.0.7.5

28 Apr, 2025

• 1 new Normative IFC Rules:

  • ALB002 – Alignment Layout Relationship (enabling a previously disabled rule)

• 1 new activation rule:

  • ALB000 – Alignment Layout

• 5 rule fixes:

  • Display correct entity from gherkin check (affects ALS015, 016, 017, GRF001, GEM003)

• Platform update:

  • Various backend platform improvements.

[Evandro]

v.0.7.6

28 May, 2025

• 2 new Normative IFC Rules:

  • QTY001 – Base Quantities
  • SPS005 – Simultaneous spatial relationships

• 3 rule fixes:

  • GEM002 – Add tessellation as acceptable representation type (version 2)
  • ALB012 – Relax precision for value matching (version 2)
  • SPS001 – Update to valid MVD; Coordination_View2.0 (version 2)
  • All test files are now compliant with the header policy check.

Rule versions are incremented when there is a change to processing logic. Edits to clarify descriptions, address typos, or similar edits that do not affect the rule validation outcomes are not considered a new version of the rule.

• Platform update:
  • Implement check for Digital Application Authentication.
  • Various bugfixes related to the header policy check.
  • Various backend platform performance improvements.

[Evandro]

v.0.7.7

June 30, 2025

• 5 New Normative IFC Rules:

  • GEM011 – Proper entity types for curve segments
  • GRF000 – Support of Georeferencing
  • GRF004 – Valid EPSG prefix
  • GRF006 – Proper use of WKT in absence of EPSG code
  • GRF007 – Valid Coordinate Reference System for vertical datum

• 3 new Industry Best Practice checks:

  • GRF002 – Valid EPSG code as Coordinate Reference System name
  • GRF003 – Presence of Coordinate Reference System
  • SPS008 – Representations for spatial containers

• 4 rule fixes:

  • ALS011 – only activate when used with IfcAlignment (version 2)
  • ALS016 – incorporate clarification of Transition attribute (version 3)
  • ALS017 – incorporate clarification of Transition attribute (version 4)
  • SPS005 – add ‘VoidsElement’ relationship (version 2)

Rule versions are incremented when there is a change to processing logic. Edits to clarify descriptions, address typos, or similar edits that do not affect the rule validation outcomes are not considered a new version of the rule.

• Platform update:
  • Syntax check split into two parts: header and data. This allows the Validation Service to capture and report information about the vendor and originating system that generated a model with invalid syntax.

[civilx64]

v.0.7.7.1

July 17, 2025

Hot-fix:

• 1 rule fix:

  • ALS017 – Correctly format observed text in the UI

• Platform update:

  • Show statistics in Django Admin

  • Display syntax result of models uploaded before v0.7.7

[civilx64]

v.0.7.8

July 28, 2025

There are no new rules or rule fixes in this update. This release focuses on improving the functionality of the API.

• Platform update:

  • Add API Quickstart to documentation

  • Incorporate rate limiting to the API

  • Capture the channel (WebUI or API) of an incoming ValidationRequest

• bug fixes:

  • Address errors with rendering reports created prior to Digital Signatures feature (v0.7.6)
  • Fix issue with postback of client-side errors

[civilx64]

v.0.7.8.1

July 31, 2025

Hot-fix:

This release addresses an issue affecting new users attempting to self-report their vendor affiliation. Due to a cookie handling bug, the self-reporting process was previously blocked. This hotfix resolves the issue, restoring full functionality for vendor affiliation reporting.

[Evandro]

v.0.7.9

August 25, 2025

• No new Normative IFC Rules

• No new Industry Best Practice checks

• 3 rule fixes:

  • ALS005 – properly handle IfcOffsetCurveByDistances and similar entities
    (Version 3)
  • GEM001 – fix indentation in code (Version 3)
  • SPS007 – correct relationship supertype (Version 6)

Rule versions are incremented when there is a change to processing logic. Edits to clarify descriptions, address typos, or similar edits that do not affect the rule validation outcomes are not considered a new version of the rule.

• Platform update:
  • Add end-to-end test suite for website & API
  • API:
    • Enforce file size limit
    • Reject non-valid API calls
    • Various minor improvements

[civilx64]

v.0.8.0

September 15, 2025

• No new Normative IFC Rules

• No new Industry Best Practice checks

• 1 rule fix:

  • ALS021 – Fix false negatives (Version 2)

Rule versions are incremented when there is a change to processing logic. Edits to clarify descriptions, address typos, or similar edits that do not affect the rule validation outcomes are not considered a new version of the rule.

• Platform update:

  • Improve model caching, reduce python memory usage and boost overall performance

  • Redirect to default landing page for API

  • Improve observability in Django Admin Statistics

  • Various bugfixes and minor improvements

[geerthesselink]

v.0.8.1

October 16, 2025

• No new Normative IFC Rules

• No new Industry Best Practice checks

• 1 rule fix:

  • BRP001 (v2), SWE001 (v4) & TAS001 (v2) – Fix false positives

Rule versions are incremented when there is a change to processing logic. Edits to clarify descriptions, address typos, or similar edits that do not affect the rule validation outcomes are not considered a new version of the rule.

• Platform update:

  • API: Implement pagination & improved security

  • Storage: Compressed (gzip) older IFC files

  • Testing: Implement Playwright end-toend testing across the entire platform

  • General: Various bug fixes and minor improvements

[civilx64]

v.0.8.2

November 10, 2025

• 1 New Normative IFC Rule:

  • MPD001 – Correct use of Representation Type and Identifier for mapped items

• No new Industry Best Practice checks

• 3 rule fixes:

  • GRF006 – fix missing implementation string (version 2)

  • OJP001 – refactor for improved performance (version 3)

  • SWE002 – fix missing implementation string (version 2)

Rule versions are incremented when there is a change to processing logic. Edits to clarify descriptions, address typos, or similar edits that do not affect the rule validation outcomes are not considered a new version of the rule.

• Platform update:

  • rename “Digital Signature” to “Digital Application Authentication”

  • various bugfixes, database improvements, and performance enhancements

[geerthesselink]

v.0.8.3

December 9, 2025

• New Normative IFC Rules:

  • ALB031 – Alignment Layouts (default case)

  • ALB032 – Alignment Layouts with re-use of Horizontal

  • GRP000 – support of groups

  • PJS001 – proper use of conversion-based units

• Rule fixes:

  • ALS011 – Small bug fixes (version 3)

  • OJT001 – Exclude checks for IFC2X3 models (version 3)

  • GEM011 – Fix execution error (version3)

  • QTY001 – Revised report text for clarity (no version change)

Rule versions are incremented when there is a change to processing logic. Edits to clarify descriptions, address typos, or similar edits that do not affect the rule validation outcomes are not considered a new version of the rule.

• Platform update:

  • Added extensive documentation for Gherkin rules: IFC Gherkin Rules Documentation — buildingSMART Validation Service 0.7.8 documentation

  • Improve performance by reducing RAM usage for large models

  • Optimized rendering when handling a large number of outcomes

  • Various bugfixes and minor improvements

[geerthesselink]

v.0.8.4

December 30, 2025

• 1 new Normative IFC Rule:

  • GRF008 – Correct rigid operation units

• 1 new Industry Best Practice checks:

  • GRF005 – Scale is provided for units of Coordinate Reference Systems

• 4 rule fixes:

  • PJS001 - Eliminate strict schema-specific checking (version 2)

  • ALS017 – Fix UI report rendering bug (version 4;no version change)

  • ALB032 – Point to correct Concept Template (version 1; no version change)

  • IFC105 - Synchronise entity instances in UI report (version 3; no version change)

[geerthesselink]

v.1.0.0

March 20, 2026

• Exit beta phase:

  • Stability – Critical bugs and major issues from beta testing are resolved.

  • Feature Completeness – Planned features are implemented, functional and tested.

  • Rules maturity – Over 100 rules developed.

  • Extensive documentation available via the dashboard

  • Deployment readiness – Infrastructure and support systems are prepared for production use.

• 1 new activation rule:

  • DOC000 – Document Reference & Information

• 6 rule fixes:

  • GRF002 – Disabled; superseded by GRF006

  • GEM001 – Restrict to faceted brep only (version 4)

  • GRF005 – Fix rounding and precision, consider IfcResourceLevelRelationship

  • IFC105 – Correct handling of IfcWellKnownText, consider shape aspect (version 4)

  • SWE001 – Apply only to IFC4 onwards (version 3)

  • PJS001 – Improve UI for reporting incorrect factor

Rule versions are incremented when there is a change to processing logic. Edits to clarify descriptions, address typos, or similar edits that do not affect the rule validation outcomes are not considered a new version of the rule.

• Platform update:

  • Removed download button for uploaded file. Added a warning when deleting files from platform

  • Added ability to toggle digitally signed models.

  • Added allowlisting – ability to suppress specific validation outcomes without disabling entire rule.

  • Added queue mechanism with Redis lock.

  • Added Docker Swarm for scalable deployment across multiple virtual machines

  • Implemented robust file retention policy.

  • Enhanced login experience using a landing page.

  • Changed logo – use official BuildingSmart logo.

  • Various bugfixes and platform improvements