6.5.3.5 IfcProjectOrder
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 Click to hide 18 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. |
6.5.3.5.4 Property sets
-
Pset_ProjectOrderChangeOrder
CHANGEORDER
- ReasonForChange
- BudgetSource
-
Pset_ProjectOrderMaintenanceWorkOrder
MAINTENANCEWORKORDER
- ProductDescription
- WorkTypeRequested
- ContractualType
- IfNotAccomplished
- MaintenanceType
- FaultPriorityType
- LocationPriorityType
- ScheduledFrequency
-
Pset_ProjectOrderMoveOrder
MOVEORDER
- SpecialInstructions
-
Pset_ProjectOrderPurchaseOrder
PURCHASEORDER
- IsFOB
- ShipMethod
-
Pset_ProjectOrderWorkOrder
WORKORDER
- ProductDescription
- WorkTypeRequested
- ContractualType
- IfNotAccomplished
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 Click to hide 17 inherited concepts | |||
IfcProjectOrder (5) | |||
Aggregation | General |
As shown in Figure 160, an IfcProjectOrder may be aggregated into components. ![]() |
|
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:
![]() This concept can be applied to the following resources: |
|
Object Nesting | General |
This concept can be applied to the following resources:
|
|
Property Sets for Objects | General |
This concept can be applied to the following resources:
|
6.5.3.5.6 Formal representation
ENTITY IfcProjectOrder SUBTYPE OF (IfcControl); PredefinedType : OPTIONAL IfcProjectOrderTypeEnum; Status : OPTIONAL IfcLabel; LongDescription : OPTIONAL IfcText; END_ENTITY;