Projektanweisung | |
Project Order |
Item | SPF | XML | Change | Description | IFC2x3 to IFC4 |
---|---|---|---|---|
IfcProjectOrder | ||||
OwnerHistory | MODIFIED | Instantiation changed to OPTIONAL. | ||
Identification | X | MODIFIED | Name changed from ID to Identification. Instantiation changed to OPTIONAL. | |
PredefinedType | MODIFIED | Instantiation changed to OPTIONAL. | ||
LongDescription | ADDED |
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.
# | Attribute | Type | Cardinality | Description | C |
---|---|---|---|---|---|
7 | PredefinedType | IfcProjectOrderTypeEnum | [0:1] | 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. | X |
8 | Status | IfcLabel | [0:1] |
The current status of a project order.Examples of status values that might be used for a project order status include:
| X |
9 | LongDescription | IfcText | [0:1] | A detailed description of the project order describing the work to be completed. | X |
# | Attribute | Type | Cardinality | Description | C |
---|---|---|---|---|---|
IfcRoot | |||||
1 | GlobalId | IfcGloballyUniqueId | [1:1] | Assignment of a globally unique identifier within the entire software world. | X |
2 | OwnerHistory | IfcOwnerHistory | [0:1] |
Assignment of the information about the current ownership of that object, including owning actor, application, local identification and information captured about the recent changes of the object,
NOTE only the last modification in stored - either as addition, deletion or modification. | X |
3 | Name | IfcLabel | [0:1] | Optional name for use by the participating software systems or users. For some subtypes of IfcRoot the insertion of the Name attribute may be required. This would be enforced by a where rule. | X |
4 | Description | IfcText | [0:1] | Optional description, provided for exchanging informative comments. | X |
IfcObjectDefinition | |||||
HasAssignments | IfcRelAssigns @RelatedObjects | S[0:?] | Reference to the relationship objects, that assign (by an association relationship) other subtypes of IfcObject to this object instance. Examples are the association to products, processes, controls, resources or groups. | X | |
Nests | IfcRelNests @RelatedObjects | S[0:1] | References to the decomposition relationship being a nesting. It determines that this object definition is a part within an ordered whole/part decomposition relationship. An object occurrence or type can only be part of a single decomposition (to allow hierarchical strutures only). | X | |
IsNestedBy | IfcRelNests @RelatingObject | S[0:?] | References to the decomposition relationship being a nesting. It determines that this object definition is the whole within an ordered whole/part decomposition relationship. An object or object type can be nested by several other objects (occurrences or types). | X | |
HasContext | IfcRelDeclares @RelatedDefinitions | S[0:1] | References to the context providing context information such as project unit or representation context. It should only be asserted for the uppermost non-spatial object. | X | |
IsDecomposedBy | IfcRelAggregates @RelatingObject | S[0:?] | References to the decomposition relationship being an aggregation. It determines that this object definition is whole within an unordered whole/part decomposition relationship. An object definitions can be aggregated by several other objects (occurrences or parts). | X | |
Decomposes | IfcRelAggregates @RelatedObjects | S[0:1] | References to the decomposition relationship being an aggregation. It determines that this object definition is a part within an unordered whole/part decomposition relationship. An object definitions can only be part of a single decomposition (to allow hierarchical strutures only). | X | |
HasAssociations | IfcRelAssociates @RelatedObjects | S[0:?] | Reference to the relationship objects, that associates external references or other resource definitions to the object.. Examples are the association to library, documentation or classification. | X | |
IfcObject | |||||
5 | ObjectType | IfcLabel | [0:1] |
The type denotes a particular type that indicates the object further. The use has to be established at the level of instantiable subtypes. In particular it holds the user defined type, if the enumeration of the attribute PredefinedType is set to USERDEFINED.
| X |
IsDeclaredBy | IfcRelDefinesByObject @RelatedObjects | S[0:1] | Link to the relationship object pointing to the declaring object that provides the object definitions for this object occurrence. The declaring object has to be part of an object type decomposition. The associated IfcObject, or its subtypes, contains the specific information (as part of a type, or style, definition), that is common to all reflected instances of the declaring IfcObject, or its subtypes. | X | |
Declares | IfcRelDefinesByObject @RelatingObject | S[0:?] | Link to the relationship object pointing to the reflected object(s) that receives the object definitions. The reflected object has to be part of an object occurrence decomposition. The associated IfcObject, or its subtypes, provides the specific information (as part of a type, or style, definition), that is common to all reflected instances of the declaring IfcObject, or its subtypes. | X | |
IsTypedBy | IfcRelDefinesByType @RelatedObjects | S[0:1] | Set of relationships to the object type that provides the type definitions for this object occurrence. The then associated IfcTypeObject, or its subtypes, contains the specific information (or type, or style), that is common to all instances of IfcObject, or its subtypes, referring to the same type. | X | |
IsDefinedBy | IfcRelDefinesByProperties @RelatedObjects | S[0:?] | Set of relationships to property set definitions attached to this object. Those statically or dynamically defined properties contain alphanumeric information content that further defines the object. | X | |
IfcControl | |||||
6 | Identification | IfcIdentifier | [0:1] | An identifying designation given to a control It is the identifier at the occurrence level. | X |
Controls | IfcRelAssignsToControl @RelatingControl | S[0:?] | Reference to the relationship that associates the control to the object(s) being controlled. | X | |
IfcProjectOrder | |||||
7 | PredefinedType | IfcProjectOrderTypeEnum | [0:1] | 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. | X |
8 | Status | IfcLabel | [0:1] |
The current status of a project order.Examples of status values that might be used for a project order status include:
| X |
9 | LongDescription | IfcText | [0:1] | A detailed description of the project order describing the work to be completed. | X |
Approval Association
The Approval Association 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 251.
| ||||||||||||||||||
Table 251 — IfcProjectOrder Property Sets for Objects |
Aggregation
The Aggregation concept applies to this entity as shown in Table 252.
| |||||||||
Table 252 — IfcProjectOrder Aggregation |
As shown in Figure 160, an IfcProjectOrder may be aggregated into components.
Figure 272 — Project order composition |
Object Nesting
The Object Nesting concept applies to this entity as shown in Table 253.
| ||||
Table 253 — IfcProjectOrder Object Nesting |
Control Assignment
The Control Assignment concept applies to this entity.
Figure 273 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:
Figure 273 — Project order assignment |
# | Concept | Model View |
---|---|---|
IfcRoot | ||
Software Identity | Common Use Definitions | |
Revision Control | Common Use Definitions | |
IfcObject | ||
Object Occurrence Predefined Type | Common Use Definitions | |
IfcControl | ||
IfcProjectOrder | ||
Approval Association | Common Use Definitions | |
Property Sets for Objects | Common Use Definitions | |
Aggregation | Common Use Definitions | |
Object Nesting | Common Use Definitions | |
Control Assignment | Common Use Definitions |
<xs:element name="IfcProjectOrder" type="ifc:IfcProjectOrder" substitutionGroup="ifc:IfcControl" nillable="true"/>
<xs:complexType name="IfcProjectOrder">
<xs:complexContent>
<xs:extension base="ifc:IfcControl">
<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"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
ENTITY IfcProjectOrder
SUBTYPE OF (IfcControl);
PredefinedType : OPTIONAL IfcProjectOrderTypeEnum;
Status : OPTIONAL IfcLabel;
LongDescription : OPTIONAL IfcText;
END_ENTITY;