Strata: element, system, product, and the as-supplied line

Construction professionals often struggle with the alignment of data standards such as Uniclass and IFC when classifying building elements. This lesson addresses how different strata, element, system, product, map to one another and how IFC’s approach can obscure these distinctions. The confusion becomes critical when AI tools attempt to automate classification, as misalignment leads to incorrect data outputs.

Stratification in Uniclass and IFC

Uniclass uses a stratified approach to categorise building information. For instance, a wall is classified in EF_25_10 as a functional element, under Ss_25 as a wall system, and in Pr codes as a set of purchasable products. Each classification addresses a different question: what is the functional role? What is the assembly? What was purchased? This approach allows for precise data use but requires careful handling when mapping to a single standard like IFC.

IFC compresses this stratification. A single IfcWall occurrence can represent both the element and the system. A crosswalk study found that the element row received a close match score of 0.85, while the system row was only related at 0.6. The study explicitly warns that mapping IfcWall to a single Uniclass table without considering the stratum introduces an undeclared modelling decision.

Consistency of Strata Across Multiple Elements

This stratification pattern is consistent across multiple building elements. For example, doors and windows are classified in EF_25_30_25 and EF_25_30_97 respectively for elements, but in Ss_25_30 for their systems. Similarly, piling is classified in EF_20_05_30 for the element and Ss_20_05_65 for the system. Ceilings follow the same pattern with EF_30_25_12 for the element and Ss_30_25 for the system. These consistent mappings highlight how each stratum addresses a distinct functional need.

As-Supplied vs As-Installed: A Critical Distinction

The boundary between as-supplied and as-installed information is one of the most important distinctions in construction data. Uniclass explicitly states that the Products table (Pr) does not map to IfcElement. A product refers to an item in a manufacturer’s catalogue, while an IfcElement refers to the physical element within a building. Mapping the two collapses the distinction and leads to data inaccuracies. For example, if a wall is modelled as an IfcElement, it should not also be treated as a product from a supplier’s perspective.

This issue mirrors a parallel distinction found in other industrial standards: the as-designed versus as-built line. Standards committees maintain these distinctions because they reflect real-world construction workflows. Mappings that erase these differences are not simplifications, they are data errors that distort project understanding.

Practical Implications for AI Classification Pipelines

When building AI tagging pipelines, it is essential to specify the stratum for each destination field. For example, classifying a wall to EF_25_10 and Ss_25_30 are two distinct tasks. A pipeline that fails to distinguish between these will fill both fields with the same value, leading to data inconsistency. This misalignment undermines the utility of the data for reporting, cost estimation, or facility management.

What to take away

Understanding the distinction between element, system, and product strata is essential for accurate data use. IFC’s compression of these strata can obscure important data boundaries. When classifying with AI, always specify the stratum to avoid conflating data that serves different functional purposes. This clarity is essential for maintaining data integrity in automated workflows.

Reference

Apply it to your work