|modifications||abstract||Changed from True to False|
|modifications||attributes ApplicableDate definition||Changed from IfcDateTimeSelect to IfcDate|
|modifications||attributes FixedUntilDate definition||Changed from IfcDateTimeSelect to IfcDate|
|modifications||inverses ValuesReferenced definition||Changed from SET OF [0:?] IfcReferencesValueDocument FOR ReferencingValues to SET OF [0:?] IfcExternalReferenceRelationship FOR RelatedResourceObjects|
|modifications||inverses ValuesReferenced name||Changed from ValuesReferenced to HasExternalReference|
This entity captures a value driven by a formula, with additional qualifications including unit basis, valid date range, and categorization.
The extent of the IfcAppliedValue is determined by the AppliedValue attribute which may be defined either as an IfcMeasureWithUnit or as an IfcMonetaryMeasure or as an IfcRatioMeasure via the IfcAppliedValueSelect type.
Optionally, an IfcAppliedValue may have an applicable date. This is intended to fix the date on which the value became relevant for use. It may be the date on which the value was set in the model or it may be a prior or future date when the value becomes operable. Similarly, an IfcAppliedValue may have a 'fixed until' date. This is intended to fix the date on which the value ceases to be relevant for use.
An instance of IfcAppliedValue may have a unit basis asserted. This is defined as an IfcMeasureWithUnit that determines the extent of the unit value for application purposes. It is assumed that when this attribute is asserted, then the value given to IfcAppliedValue is that for unit quantity. This is not enforced within the schema and thus needs to be controlled within an application.
Applied values may be referenced from a document (such as a price list). The relationship between one or more occurrences of IfcAppliedValue (or its subtypes) is achieved through the use of the IfcExternalReferenceRelationship in which the document provides the IfcExternalReferenceRelationship.RelatingExtReference and the value occurrences are the IfcExternalReferenceRelationship.RelatedResourceObjects.
HISTORY New entity in IFC2x2.
IFC4 CHANGE Entity made non-abstract to support general formula expressions of constraints, data type of date-based attributes changed into IfcDate, ValueType and Condition promoted from IfcCostValue, Components and ArithmeticOperator attributes added to replace IfcAppliedValueRelationship for more efficient encoding and reference tracking.
|1||Name||OPTIONAL IfcLabel||A name or additional clarification given to a cost value.|
|2||Description||OPTIONAL IfcText||The description that may apply additional information about a cost value.|
|3||AppliedValue||OPTIONAL IfcAppliedValueSelect||The extent or quantity or amount of an applied value.|
|4||UnitBasis||OPTIONAL IfcMeasureWithUnit||The number and unit of measure on which the unit cost is based.|
Note: As well as the normally expected units of measure such as length, area, volume etc., costs may be based on units of measure which need to be defined e.g. sack, drum, pallet, item etc. Unit costs may be based on quantities greater (or lesser) than a unitary value of the basis measure. For instance, timber may have a unit cost rate per X meters where X > 1; similarly for cable, piping and many other items. The basis number may be either an integer or a real value.
Note: This attribute should be asserted for all circumstances where the cost to be applied is per unit quantity. It may be asserted even for circumstances where an item price is used, in which case the unit cost basis should be by item (or equivalent definition).
|5||ApplicableDate||OPTIONAL IfcDate||The date on or from which an applied value is applicable.|
> IFC4 CHANGE Type changed from IfcDateTimeSelect.
|6||FixedUntilDate||OPTIONAL IfcDate||The date until which applied value is applicable.|
> IFC4 CHANGE Type changed from IfcDateTimeSelect.
|7||Category||OPTIONAL IfcLabel||Specification of the type of cost used.|
> NOTE There are many possible types of cost value that may be identified. Whilst there is a broad understanding of the meaning of names that may be assigned to different types of costs, there is no general standard for naming cost types nor are there any broadly defined classifications. To allow for any type of cost value, the IfcLabel datatype is assigned.
In the absence of any well defined standard, it is recommended that local agreements should be made to define allowable and understandable cost value types within a project or region.
|8||Condition||OPTIONAL IfcLabel||The condition under which a cost value applies. |
For example, within the context of a bid submission, this may refer to an option that may or may not be elected.
|9||ArithmeticOperator||OPTIONAL IfcArithmeticOperatorEnum||The arithmetic operator applied to component values.|
|10||Components||OPTIONAL LIST [1:?] OF IfcAppliedValue||Optional component values from which AppliedValue is calculated.|
|HasExternalReference||SET [0:?] OF IfcExternalReferenceRelationship FOR RelatedResourceObjects||Reference to an external reference, e.g. library, classification, or document information, that is associated to the IfcAppliedValue. |
> IFC4 CHANGE New inverse attribute.
ENTITY IfcAppliedValue SUPERTYPE OF (ONEOF (IfcCostValue)); Name : OPTIONAL IfcLabel; Description : OPTIONAL IfcText; AppliedValue : OPTIONAL IfcAppliedValueSelect; UnitBasis : OPTIONAL IfcMeasureWithUnit; ApplicableDate : OPTIONAL IfcDate; FixedUntilDate : OPTIONAL IfcDate; Category : OPTIONAL IfcLabel; Condition : OPTIONAL IfcLabel; ArithmeticOperator : OPTIONAL IfcArithmeticOperatorEnum; Components : OPTIONAL LIST [1:?] OF IfcAppliedValue; INVERSE HasExternalReference : SET [0:?] OF IfcExternalReferenceRelationship FOR RelatedResourceObjects; END_ENTITY;