Abstract base for reusable cost record fields shared by atomic and aggregated cost records.
Integer revision counter for change tracking.
Classification entries from IFC and other schemes.
Aggregated unit prices associated with this entity.
Last modification timestamp for this entity record.
Geometry references associated with the entity. A single element may link to multiple geometry representations to serve different intents (authoring, coordination, analysis, visualization) without duplicating the element itself.
Quantity type used as basis for this cost calculation.
Linked documents associated with this entity.
Quantity magnitude used as basis for this cost calculation.
Optional semantic URI for linking the entity instance to an external ontology concept.
Normalized, strongly typed domain properties (fire/acoustic/thermal/structural/ security/material) extracted from raw IFC PropertySet values.
Cost category label kept intentionally open pending classification-backed modeling.
Material definitions associated with this entity.
Creation timestamp for this entity record.
Generic metadata container for IFC attributes/properties and project-specific extensions.
ISO 4217 currency code (for example EUR, USD).
Decision records associated with this entity.
Value type discriminator for normalized storage (for example string, number, boolean).
Canonical key inside the domain; constrained via subclass slot_usage to a domain-specific enum.
Original IFC PropertySet name (for example Pset_WallCommon).
String value when property_value_type is string.
Numeric value when property_value_type is number.
Mapping specification version used to derive the normalized property.
Normalized unit where applicable (for example min, dB, W/m2K).
Original property name inside the source PropertySet (for example FireRating).
Boolean value when property_value_type is boolean.
Physical element acting as a boundary treatment (for example covering).
Classification of boundary element (e.g., covering).
Spatial context node constrained to building semantics.
Zone members; may include spaces, separations, systems, etc.
Optional zone classification; intended for SpatialContext nodes where context_type is zone.
Classification of context entity (project, perimeter, legal_site, building, civil_structure, level, zone).
Spatial context node constrained to civil structure semantics.
Physical connector providing functional connection between spaces (for example door, window, duct, pipe, cable).
Classification of physical connector type (for example door, window, duct, pipe, cable).
Primary transport medium carried or enabled by the connector (for example human_access, air, liquid, electricity).
Performance requirement drivers for this physical connection element. Multiple values are allowed because one connection may need to satisfy several requirements.
Logical or topological connection between spaces and/or physical elements.
Classification of virtual connection semantics (for example structural_joint, adjacency, access).
Spaces connected by this virtual connection.
Physical elements connected by this virtual connection (for example wall-wall, wall-slab).
Main requirement drivers for this virtual connection.
Endpoint or device element (for example terminal, unit, control device, sensor) located in a space and assigned to a system.
Classification of equipment (for example HVAC, electrical, plumbing).
Parent systems that the equipment belongs to.
Parent space where the equipment is located.
Optional assessment record linking requirement intent, normalized property evidence, and compliance result for an entity.
Target criterion or threshold used by the requirement rule.
Human-readable evidence or machine rule reference supporting the assessment.
Requirement driver key used in assessment context (for example fire, acoustic, structural, security).
Canonical normalized property key used as evidence for requirement evaluation.
Assessment result status (for example pass, fail, unknown).
Abstract base class for elements that separate spaces or zones.
Performance requirement drivers for this separator. Multiple values are allowed because one separator may need to satisfy several requirements.
Slab-based separating element (for example floor/roof/base slab separators).
Level context nodes separated by this slab separator.
Classification of slab-based separator element (for example floor/roof/base slab).
Spaces separated by this separator element.
Classification of wall-based separator element.
Context node used to represent project, perimeter, legal site, built asset, level, or zone.
Abstract base class for non-physical, conceptual, or informational entities.
Building service system grouping that serves spaces or zones.
Classification of system discipline (electrical, sanitary, ventilation, heating).
Generic containment for associated entities.
Classification of system role (unit, network, terminal).
Zone context nodes served by this system.
Base class for physical elements that can be placed in built asset/level context.
Spatial container used for occupancy, circulation, service, or analysis.
Classification of space (void, circulation, usable, service).
Spatial context node constrained to perimeter semantics.
Spatial context node constrained to project semantics.
Spatial context node constrained to zone semantics.
Common base class for all schema entities.
Aggregated unit price assembled from multiple cost items.
Atomic cost items that are aggregated into this cost assembly.
Material definition that can be associated with one or more entities.
Material category label kept intentionally open pending classification-backed modeling.
Material grade, specification, or product description.
Abstract spatial context for built assets such as buildings and civil structures.
Cost record used for estimation and calculation, optionally linked to quantities.
Spatial context node constrained to legal site semantics.
Spatial context node constrained to level/storey semantics.
Reference to an external document stored in a file system, DMS, object storage, or URL.
URI/URL/path to the stored document location.
Minimal geometry reference for an entity, separating representation from encoding format.
Representation kind/dimension (for example body_3d, footprint_2d, point), independent of file format.
Optional serialization/encoding format (for example ifc, gltf, wkt, geojson), independent of representation kind.
URI/path/hash/pointer to geometry payload.
Generic metadata entry for storing IFC attributes, PropertySet fields, or project-specific key-value data.
Metadata key, for example IfcWall.FireRating or Pset_WallCommon.Reference.
Normalized performance/property record derived from raw IFC PropertySet values with source traceability and strong typing through domain-specific subclasses.
Minimal quantity record for costing and analysis.
Action/task record linked to an entity for implementation and follow-up workflows.
Task type expressed as a URI/CURIE from a controlled vocabulary.
Task status URI/CURIE aligned with action status vocabularies.
Additional notes or implementation details for the task.
Optional reference to a decision that informs or drives this task.
Generic classification entry from any scheme (for example IFC, Uniclass, OmniClass, custom).
Optional URI/CURIE that identifies the classification concept in an external registry.
Source authority or dataset for this classification.
Optional human-readable classification label.
Name of the classification scheme (for example ifc, uniclass, omniclass, custom).
Decision record linked to an entity for workflow traceability and governance.
Human-readable rationale that explains why the decision was made.
Decision status expressed as a URI/CURIE (for example proposed, accepted, rejected, superseded).
URI/CURIE for the agent responsible for the decision.
Decision type expressed as a URI/CURIE from a controlled vocabulary.
Localized text value for a specific language tag.
IETF BCP 47 language tag (for example en, de, pt-BR).