Skip to content

Conversation

@DimitriosThe
Copy link
Contributor

This is a simplified approach.

In preliminary cost evaluations in most cases the model is quite abstract to derive detailed costs, how ever by leveraging the use of spaces and working with indices cost /m2 cost/m3 and quantities from IfcSpace, one could easily generate rough budgets, aligning with conceptualization/ preliminary phase scope.

I am not aware/ do not know if there are specific restrictions for which these entities should/ must not be included in a Cost Schedule.

In the context of IfcSpatialElement, the entity IfcSpace would have the funtion continue to the next iteration and not include IfcSpace entities for assigning cost item quantities. 
How ever there are use cases where especially in preliminary cost budgeting spaces are used to derive costs for the general quantities (floor, ceiling, walls etc)
Related to costing which uses the function, IfcSpace.is_a("IfcTypeProduct") returns False whereas IfcSpace.is_a("IfcProduct") returns True, and as such the IfCSpace is assigned to CostItem
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant