Difference between revisions of "IFC - Industry Foundation Classes/IFC concepts/IFC cost concepts"

From Wiki.OSArch
Line 41: Line 41:
  
 
Source: IfcCostSchedule, IfcProjectOrder
 
Source: IfcCostSchedule, IfcProjectOrder
 +
 +
== A cost schedule may have approval requests ==
 +
 +
<!--
 +
digraph {
 +
  node [ shape=rect, color="lightblue" ];
 +
  edge [ fontsize=10 ];
 +
  IfcRelAssociatesApproval -> IfcApproval [ label="RelatingApproval" ];
 +
  IfcRelAssociatesApproval -> IfcCostSchedule [ label="RelatedObjects" ];
 +
  IfcRelAssociatesApproval [color="pink"]
 +
}
 +
-->
 +
 +
[[File:Ifc-concept-cost-costschedule-approval.png]]
 +
 +
A cost schedule may have an approval associated with it, to determine whether it is approved or not.
 +
 +
Source: IfcCostSchedule
 +
 +
== A cost schedule may have a series of approvals ==
 +
 +
<!--
 +
digraph {
 +
  node [ shape=rect, color="lightblue" ];
 +
  edge [ fontsize=10 ];
 +
  IfcRelAssociatesApproval -> IfcCostSchedule [ label="RelatedObjects" ];
 +
  IfcRelAssociatesApproval -> IfcApproval [ label="RelatingApproval" ];
 +
  IfcRelAssociatesApproval [color="pink"]
 +
  IfcApprovalRelationship [color="pink"]
 +
  IfcApprovalRelationship -> IfcApproval [label="RelatingApproval"]
 +
  IfcApprovalRelationship -> approval2 [label="RelatedApprovals"]
 +
  approval2 [label="IfcApproval"]
 +
}
 +
-->
 +
 +
[[File:Ifc-concept-cost-costschedule-approval-rel.png]]
 +
 +
An approval that relates to a cost schedule may itself be broken down into sub approvals. This implies that the sub approvals (RelatedApprovals) must first be approved before the parent approval (RelatingApproval) may be approved.
 +
 +
Source: IfcCostSchedule

Revision as of 04:34, 5 August 2021

The primary classes related to this concept are:

  • IfcCostSchedule
  • IfcCostItem

A cost schedule can exist

Ifc-concept-cost-costschedule.png

A cost schedule is a collection of cost items, used for a specified purpose. Typical purposes are cost plans and tenders.

Note: there is no explicit documentation which explains how a cost schedule is related back to the project or context. Therefore, in the absence of documentation, we are assuming that we declare it to the project as shown. However, this is only an assumption. There are explicit arguments against this assumption, such as that a cost schedule must be tied back to a project order. However, this evidence is not considered strong enough as it is never mentioned in the cost schedule documentation page itself.

Source: IfcProjectOrder

A cost schedule can be part of a project order

Ifc-concept-cost-projectorder.png

Project orders, such as work orders, change orders, or in particular purchase orders, may include a cost schedule. For example, a cost schedule may be used to provide an estimate of costs for a work order.

Source: IfcCostSchedule, IfcProjectOrder

A cost schedule may have approval requests

Ifc-concept-cost-costschedule-approval.png

A cost schedule may have an approval associated with it, to determine whether it is approved or not.

Source: IfcCostSchedule

A cost schedule may have a series of approvals

Ifc-concept-cost-costschedule-approval-rel.png

An approval that relates to a cost schedule may itself be broken down into sub approvals. This implies that the sub approvals (RelatedApprovals) must first be approved before the parent approval (RelatingApproval) may be approved.

Source: IfcCostSchedule