Skip to main content

Module value

Module value 

Source
Expand description

IfcCostValue and the applied-value tree beneath it.

§Slots, verified against IFC4 EXPRESS

IfcCostValue adds nothing of its own; every slot comes from IfcAppliedValue:

0 Name                1 Description        2 AppliedValue
3 UnitBasis           4 ApplicableDate     5 FixedUntilDate
6 Category            7 Condition          8 ArithmeticOperator
9 Components

§A cost value is a tree, not a number

Components holds nested IfcAppliedValues and ArithmeticOperator says how to combine them. A value with components and an ADD operator is the sum of its children; the AppliedValue slot may then be absent entirely. Reading only slot 2 and calling that “the amount” silently reports nothing for every composed rate in the file.

§What this module refuses to do

It does not evaluate the tree. ArithmeticOperator is ADD, DIVIDE, MULTIPLY or SUBTRACT over a LIST whose order the schema does not constrain to be meaningful for non-commutative operators: SUBTRACT over [a, b, c] has no defined bracketing in the standard. Folding it anyway would produce a number that looks authoritative and is not. So the shape is reported and evaluation is left to a caller who knows their own convention.

Structs§

CostValue
A borrowed view of an IfcCostValue entity.
UnitBasis
How a rate is expressed per unit of something.

Enums§

ArithmeticOperator
How an applied value combines its components.