buildingSMART / buildingSMART/IFC4.x-development

Proposal to describe how CostQuantities cannot be used for SCHEDULEOFRATES

Open
#81 0 comments 0 reactions 0 assignees View on GitHub
allocated-cost ifc-update-out proposal
Dominant language
Python
Stars
234
Forks
123
Avg merge
15h 4m
Merged PRs (30d)
5

Description

The current description for CostQuantities of an IfcCostItem is:

> Component quantities of the same type for which the total quantity for the cost item is calculated as the sum.

However, I believe that if the IfcCostSchedule is a SCHEDULEOFRATES, then CostQuantities do not have meaning. Instead, "unitised quantities" are provided using `UnitBasis` of `CostValue`, it seems.

Proposed new description:

> Component quantities of the same type for which the total quantity for the cost item is calculated as the sum. **If the cost item is part of a schedule of rates, the quantity must be omitted.**

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.