A project order is a directive to purchase products and/or perform work, such as for construction or facilities management.
Project orders are typically formal contracts between two organizations, where cost and time information may be rigid or flexible according to contained schedule types and constraints.
HISTORY New entity in IFC2.0
IFC4 CHANGE Attribute ID renamed to Identification and promoted to supertype IfcControl. Attribute 'LongDescription' added.
Common Use Definitions
The following concepts are inherited at supertypes:
The Object Approval concept applies to this entity.
Approvals may be associated to indicate the status of acceptance or rejection using the IfcRelAssociatesApproval relationship where RelatingApproval refers to an IfcApproval and RelatedObjects contains the IfcProjectOrder. Approvals may be split into sub-approvals using IfcApprovalRelationship to track approval status separately for each party where RelatingApproval refers to the higher-level approval and RelatedApprovals contains one or more lower-level approvals. The hierarchy of approvals implies sequencing such that a higher-level approval is not executed until all of its lower-level approvals have been accepted.
Property Sets for Objects
The Property Sets for Objects concept applies to this entity as shown in Table 252.
Table 252 — IfcProjectOrder Property Sets for Objects
The Object Aggregation concept applies to this entity as shown in Table 253.
| ||IfcCostSchedule|| A cost schedule may indicate costs and quantities where the cost schedule type may designate whether rates and/or quantities are estimated or final. Such cost schedule may have assigned cost items indicating detail, where each cost item may have assigned products, processes, or resources.|
|WORKORDER||IfcWorkSchedule||A work schedule may indicate tasks and scheduled times where the work schedule type may designate whether tasks and/or times are planned or actual. Such work schedule may have assigned tasks indicating detail, where tasks may be assigned to products and may have assigned resources.|
Table 253 — IfcProjectOrder Object Aggregation
As shown in Figure 160, an IfcProjectOrder may be aggregated into components.
Figure 247 — Project order composition
The Object Nesting concept applies to this entity as shown in Table 254.
|IfcProjectOrder||May contain subordinate orders, particularly change orders indicating contract amendment in order of issue.|
Table 254 — IfcProjectOrder Object Nesting
The Control Assignment concept applies to this entity.
Figure 248 illustrates IfcProjectOrder assignment relationships as indicated:
The IfcProjectOrder may have assignments of its own using the IfcRelAssignsToControl relationship where RelatingControl refers to the IfcProjectOrder and RelatedObjects contains one or more objects of the following types:
- IfcActor: Organization(s) contracted to fulfill the order, typically a single contractor, subcontractor, or supplier.
Figure 248 — Project order assignment
XSD Specification: <xs:element name="IfcProjectOrder" type="ifc:IfcProjectOrder" substitutionGroup="ifc:IfcControl" nillable="true"/>
<xs:attribute name="PredefinedType" type="ifc:IfcProjectOrderTypeEnum" use="optional"/>
<xs:attribute name="Status" type="ifc:IfcLabel" use="optional"/>
<xs:attribute name="LongDescription" type="ifc:IfcText" use="optional"/>
|PredefinedType|| : ||
Predefined generic type for a project order that is specified in an enumeration. There may be a property set given specificly for the predefined types.
IFC4 CHANGE The attribute has been made optional.
|Status|| : ||The current status of a project order.Examples of status values that might be used for a project order status include:
|LongDescription|| : ||
A detailed description of the project order describing the work to be completed.
Link to this page