|modifications||attributes RelatingProcess definition||Changed from IfcProcess to IfcProcessSelect|
The objectified relationship IfcRelAssignsToProcess handles the assignment of one or many objects to a process or activity. An object can be a product that is the item the process operates on. Processes and activities can operate on things other than products, and can operate in ways other than input and output.
EXAMPLE It may be common to define processes during estimating or scheduling that describe design tasks (resulting in documents), procurement tasks (resulting in construction materials), planning tasks (resulting in processes), etc. Furthermore, the ways in which process can operate on something might include "installs", "finishes", "transports", "removes", etc. The ways are described as operation types.
The inherited attribute RelatedObjects gives the references to the objects, or object type, which the process operates on. The RelatingProcess is the process or process type, that operates on the object. The operation types are captured in the inherited attribute Name.
NOTE The agreement on valid and recognizable values for the Name attribute is part of view definitions and implementer agreements.
HISTORY New entity in IFC1.5. Has been renamed from IfcRelProcessOperatesOn in IFC2x.
IFC4 CHANGE The data type RelatingProcess has been extended to cover also IfcTypeProcess
|1||GlobalId||IfcGloballyUniqueId||Assignment of a globally unique identifier within the entire software world.|
|2||OwnerHistory||OPTIONAL IfcOwnerHistory||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.
> IFC4 CHANGE The attribute has been changed to be OPTIONAL.
|3||Name||OPTIONAL IfcLabel||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.|
|4||Description||OPTIONAL IfcText||Optional description, provided for exchanging informative comments.|
|5||RelatedObjects||SET [1:?] OF IfcObjectDefinition||Related objects, which are assigned to a single object. The type of the single (or relating) object is defined in the subtypes of IfcRelAssigns.|
|6||RelatedObjectsType||OPTIONAL IfcObjectTypeEnum||Particular type of the assignment relationship. It can constrain the applicable object types, used within the role of RelatedObjects.|
> IFC4 CHANGE The attribute is deprecated and shall no longer be used. A NIL value should always be assigned.
|7||RelatingProcess||IfcProcessSelect||Reference to the process to which the objects are assigned to.|
> IFC4 CHANGE Datatype expanded to include IfcProcess and IfcTypeProcess.
|8||QuantityInProcess||OPTIONAL IfcMeasureWithUnit||Quantity of the object specific for the operation by this process.|
IfcRoot assigns the globally unique ID. In addition it may provide for a name and a description about the concept.
Ownership, history, and merge state is captured using IfcOwnerHistory.
ENTITY IfcRelAssignsToProcess SUBTYPE OF (IfcRelAssigns); RelatingProcess : IfcProcessSelect; QuantityInProcess : OPTIONAL IfcMeasureWithUnit; WHERE NoSelfReference : SIZEOF(QUERY(Temp <* SELF\IfcRelAssigns.RelatedObjects | RelatingProcess :=: Temp)) = 0; END_ENTITY;