IFC 4.3.2.20250327 (IFC4X3_ADD2) under development

6.5.3.5 IfcProjectOrder

RV ⓘ
AbV ⓘ

6.5.3.5.1 Semantic definition

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.

6.5.3.5.2 Entity inheritance

6.5.3.5.3 Attributes

# Attribute Type Description
IfcRoot (4)
IfcObjectDefinition (7)
IfcObject (5)
IfcControl (2)
Click to show 18 hidden inherited attributes
IfcProjectOrder (3)
7 PredefinedType OPTIONAL IfcProjectOrderTypeEnum

Predefined generic type for a project order that is specified in an enumeration. There may be a property set given specifically for the predefined types.

8 Status OPTIONAL IfcLabel

The current status of a project order.Examples of status values that might be used for a project order status include: * PLANNED * REQUESTED * APPROVED * ISSUED * STARTED * DELAYED * DONE

9 LongDescription OPTIONAL IfcText

A detailed description of the project order describing the work to be completed.

Table 6.5.3.5.C

6.5.3.5.4 Property sets

6.5.3.5.5 Concept usage

Concept Usage Description
IfcRoot (2)
IfcObjectDefinition (9)
IfcObject (5)
IfcControl (1)
Click to show 17 hidden inherited concepts
IfcProjectOrder (5)
Aggregation General

As shown in Figure 160, an IfcProjectOrder may be aggregated into components.

Composition Use Definition
Figure 6.5.3.5.A — Project order composition
Approval Association General

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.

Control Assignment General

Figure 6.5.3.5.B 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.
Assignment Use Definition
Figure 6.5.3.5.B — Project order assignment

This concept can be applied to the following resources:

Object Nesting General

This concept can be applied to the following resources:

  • IfcProjectOrder - May contain subordinate orders, particularly change orders indicating contract amendment in order of issue.
Property Sets for Objects General

This concept can be applied to the following resources:

Table 6.5.3.5.D

6.5.3.5.6 Formal representation

ENTITY IfcProjectOrder
SUBTYPE OF (IfcControl);
PredefinedType : OPTIONAL IfcProjectOrderTypeEnum;
Status : OPTIONAL IfcLabel;
LongDescription : OPTIONAL IfcText;
END_ENTITY;

6.5.3.5.7 References

Edit on Github


Is this page difficult to understand? Let us know!

6.5.3.5.8 Changelog

6.5.3.5.8.1 IFC4

  • attribute, LongDescription
  • attribute, PredefinedType
  • unique rule, UR2
  • attribute ID name, Changed from "ID" to "PredefinedType"
  • attribute ID optional, Changed from "False" to "True"
  • attribute ID type, Changed from "IfcIdentifier" to "IfcProjectOrderTypeEnum"