02 · TYPED ENGINEERING DATA

A reported number needs a type and a unit.

An IFC precheck that keeps the path from a model property to a finding visible, then separates safe enrichment from work that still needs a designer.

Open the report workflowRead the evidence
  1. Readvalue / type / unit
  2. Checknormalized evidence
  3. Enrichtyped write / defer
  4. Reopenindependent readback
250 mm → 0.25 mNormalized evidence; original 250 mm property retained
9 writesTraceable fills in the authored fixture
1 deferredUnknown unit kept for review

The problem

The same numeric value can mean millimetres, metres or a dimensionless ratio. Treating every property name as a measurement produces plausible-looking but incorrect checks. A useful report must show what was read and why a conversion or derivation was allowed.

Implementation decisions

01

Read the IFC semantics

Keep the original value, IFC measure type and explicit or project unit. A generic IfcReal with no explicit physical unit does not acquire a length dimension because of its property name. Unknown units remain unresolved.

02

Fill only with justified evidence

Geometry-derived values are written as typed measures with units. Existing nonempty values are preserved, and shared property sets are separated before changing one element.

03

Make review navigable

Filter findings by agency, severity, element identity, property and status. Inspect all findings, export the filtered view, and retain the complete report and derivation evidence.

Inspect it yourself

Open the authored three-slab example, compare the before/after reports, inspect a conversion and a deferred field, then download the findings. Rebuild it locally with:

python scripts/report_demo.py --output-dir demos/report-review
  1. Start with the original report and locate a specific GlobalId or property.
  2. Compare the enriched report, including typed writes and unresolved items.
  3. Open the independent reopen evidence; export the selected findings without changing the original totals.

Open the report workflow →

Scope and limits

This static report replay uses a small self-authored IFC and illustrative rules; it processes no visitor files. It is not an official regulatory rulebook or an approval decision. Geometry assumptions, absent values and unknown units remain visible for human review.

Sources and verification

Source and CI links let you inspect the implementation and reproducibility. Passing checks do not establish deployment success or business gains.