◆ OPENSPAD Documentation 2.0
Chapter 08 · Information assurance

IDS, Constraint Engine
& Model Validation

From versioned project information requirements to IFC checks, explainable graph evidence, 3D feedback and coordinated BCF issues.

IDS import ↔ exportConstraint compilationIFC model checksValidation evidence3D viewer + BCF

Design/specification draft 0.1 · Baseline OpenSPAD 7.8.53 · 17 October 2026

Maturity disclaimer: This chapter defines the approved architectural direction. A fully integrated IDS-to-IFC-to-viewer validation pipeline has not been verified as deployed in OpenSPAD 7.8.53. Individual module descriptions, examples and acceptance tests below are proposed unless separately evidenced.

One traceable requirement, from intent to evidence

Project Use CasePinned Concept versionRequirementsApplicability + facetsConstraint EngineIDS / extended backendsIDS ExportSupported subsetIFC ModelProject model revisionValidation RunVersioned result evidence3D ViewerBCF IssuesTraceability: Requirement ID · Concept revision · IFC GlobalId · ValidationRun ID · BCF topic
Project knowledgeSemantics & viewerRules & evidenceInterchange & issues

Explore the specification

01Scope and evidence02Requirements and graph representation03IDS import04Constraint compilation05IDS export and traceability06IFC model validation07Validation result graph083D viewer integration09BCF issue lifecycle10Revision and change management11Roles and governance12Acceptance scenarios
01 / CHAPTER SECTION

Scope and evidence

IDS defines machine-readable information requirements, while the broader Constraint Engine is a proposed orchestration layer. This chapter describes the intended end-to-end workflow, not a claim of current production functionality.

02 / CHAPTER SECTION

Requirements and graph representation

Each Project Use Case references pinned Concept versions. Requirement nodes capture target entities, applicability conditions, expected properties, operators, units, tolerances, source references and revision provenance.

03 / CHAPTER SECTION

IDS import

Parse IDS XML into a staging representation; validate syntax and supported facets; resolve entity classes and property requirements; preview Concept and IFC schema alignment; flag ambiguous or unsupported facets for administrator review. Store source identity and revision.

04 / CHAPTER SECTION

Constraint compilation

Translate supported requirements to executable validation rules. Each rule carries a stable ID, scope, version, severity, evidence path and backend. Distinguish IDS-expressible constraints from extended graph, geometric and cross-object rules.

05 / CHAPTER SECTION

IDS export and traceability

Export only constraints expressible in the selected IDS specification. Provide a coverage report listing exported, partially represented and excluded rules. Keep a traceability link from each exported IDS requirement to its source Use Case and Concept revision.

06 / CHAPTER SECTION

IFC model validation

Associate a project IFC model and model revision with a Validation Run. Evaluate applicability before requirements; record pass, fail, not applicable and not evaluated separately. Unsupported rules must never be silently counted as passing.

07 / CHAPTER SECTION

Validation result graph

Persist planned ValidationRun, ValidationResult and Evidence relationships to IFC element GlobalIds, requirement revisions, models, issue references and timestamps. Store measured values, expected values and diagnostic context for reproducibility.

08 / CHAPTER SECTION

3D viewer integration

Load the relevant project model, select the failing IFC object by GlobalId, colorize status and reveal the exact failing property or relationship. Provide filters by Use Case, discipline, severity and validation run. Geometric overlays require suitable model geometry.

09 / CHAPTER SECTION

BCF issue lifecycle

A failed validation may propose a BCF topic with title, description, assignee, status, comments and viewpoint. Topic creation is controlled and deduplicated; a BCF issue is not identical to a validation result or a BPMN task.

10 / CHAPTER SECTION

Revision and change management

Published Concept revisions remain immutable. Existing Project Use Cases keep pinned references. Upgrades trigger explicit impact analysis, regeneration of affected requirements and new validation runs; prior evidence remains available.

11 / CHAPTER SECTION

Roles and governance

Administrator governs global Concepts and rule definitions; BIM Manager configures project requirements, executes review and approves project checks; Standard User consumes authorized deliverables and issue information according to project permissions.

12 / CHAPTER SECTION

Acceptance scenarios

Validate a missing required door property; compare an unexpected property value; handle a non-applicable rule; report an unsupported geometry rule; create a BCF topic with IFC viewpoint; revalidate after a deliberate Concept-version upgrade.

Worked example · Door fire-rating requirement

Intent: Every applicable IfcDoor on a protected escape route must carry a specified fire-resistance classification. A project requirement identifies its applicability and accepted values; an IDS-expressible property facet is exported when the selected schema and mapping support it. A model validation run reports matching doors separately from missing/invalid properties. Any failure can be highlighted by IFC GlobalId and linked to a reviewed BCF topic.

Boundary: Deciding whether a door is on a protected escape route can require relationships or geometry beyond an IDS property check; that prerequisite must be implemented in a separate validation backend rather than presumed from IDS alone.

Release maturity

Verified baselineChapter site and prior 7.8.53 Concept Graph pilot evidence; not a validation suite
PilotConcept relationship evaluation in 7.8.53; limited scope
PlannedIDS round-trip coverage, validation runs and viewer feedback
FutureFederated execution and access-controlled cross-server validation