IfcProjectOrder

Natural language names
deProjektanweisung
enProject Order
Change log
ItemSPFXMLChangeDescription
IFC2x3 to IFC4
    IfcProjectOrder
      OwnerHistoryMODIFIEDInstantiation changed to OPTIONAL.
      IdentificationXMODIFIEDName changed from ID to Identification.
Instantiation changed to OPTIONAL.
      PredefinedTypeMODIFIEDInstantiation changed to OPTIONAL.
      LongDescriptionADDED
Semantic definitions at the entity
Entity 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.

HISTORY  New entity in IFC2.0
IFC4 CHANGE  Attribute ID renamed to Identification and promoted to supertype IfcControl. Attribute 'LongDescription' added.
Attribute definitions
#AttributeTypeCardinalityDescription B
7PredefinedTypeIfcProjectOrderTypeEnum[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
8Status- This attribute is out of scope for this model view definition and shall not be set.
9LongDescription- This attribute is out of scope for this model view definition and shall not be set.
Inherited definitions from supertypes
Entity inheritance IfcControl IfcObject IfcObjectDefinition IfcRoot
Attribute inheritance
#AttributeTypeCardinalityDescriptionB
IfcRoot
1GlobalIdIfcGloballyUniqueId[1:1] Assignment of a globally unique identifier within the entire software world. X
2OwnerHistoryIfcOwnerHistory[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
3NameIfcLabel[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
4DescriptionIfcText[0:1] Optional description, provided for exchanging informative comments.X
IfcObjectDefinition
HasAssignmentsIfcRelAssigns
@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
NestsIfcRelNests
@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).
IsNestedByIfcRelNests
@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
HasContextIfcRelDeclares
@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.
IsDecomposedByIfcRelAggregates
@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
DecomposesIfcRelAggregates
@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
HasAssociationsIfcRelAssociates
@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
5ObjectType- This attribute is out of scope for this model view definition and shall not be set.
IsTypedByIfcRelDefinesByType
@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
IsDefinedByIfcRelDefinesByProperties
@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
6Identification- This attribute is out of scope for this model view definition and shall not be set.
ControlsIfcRelAssignsToControl
@RelatingControl		S[0:?]Reference to the relationship that associates the control to the object(s) being controlled. X
IfcProjectOrder
7PredefinedTypeIfcProjectOrderTypeEnum[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
8Status- This attribute is out of scope for this model view definition and shall not be set.
9LongDescription- This attribute is out of scope for this model view definition and shall not be set.
Definitions applying to Bridge View

 Instance diagram

Concept usage

Control Assignment

The Control Assignment concept applies to this entity.



Aggregation

The Aggregation concept applies to this entity as shown in Table 67.

PredefinedTypeRelatedObjectsDescription
 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.
WORKORDERIfcWorkScheduleA 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 67 — IfcProjectOrder Aggregation

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

Composition Use Definition

Figure 203 — Project order composition

Exchange
Import R
Export R


Concept inheritance

#ConceptModel View
IfcRoot
Software IdentityBridge View
User IdentityBridge View
Object OwnershipBridge View
IfcObject
Property Sets for ObjectsBridge View
IfcProjectOrder
Control AssignmentBridge View
AggregationBridge View
Formal representations
XSD Specification
 <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:extension>
  </xs:complexContent>
 </xs:complexType>
EXPRESS Specification
ENTITY IfcProjectOrder
 SUBTYPE OF (IfcControl);
  PredefinedType : OPTIONAL IfcProjectOrderTypeEnum;
  Status : OPTIONAL IfcStrippedOptional;
  LongDescription : OPTIONAL IfcStrippedOptional;
END_ENTITY;

Link to EXPRESS-G diagram EXPRESS-G diagram

Link to this page  Link to this page