IFC 4.3.2.20250327 (IFC4X3_ADD2) under development

5.3.3.6 IfcTask

RV ⓘ
AbV ⓘ

5.3.3.6.1 Semantic definition

An IfcTask is an identifiable unit of work to be carried out in a construction project.

A task is typically used to describe an activity for the construction or installation of products, but is not limited to these types. For example it might be used to describe design processes, move operations and other design, construction and operation related activities as well.

Quantities of resources consumed by the task are dealt with by defining the IfcElementQuantity for the resource and not at the instance of IfcTask.

5.3.3.6.1.1 Attribute use definition

Each occurrence of IfcTask is given a name that is indicative of its content (IfcRoot.Name). A textual description of the task may be provided and this may be further elaborated by a narrative long description (IfcProcess.LongDescription). A work method may be declared for the method of work used in carrying out a task. A task is identified as being either a milestone task or not. A milestone task is defined by the marker IsMilestone. and has no duration. A status and priority for each task may also be set.

5.3.3.6.1.2 Time and duration use definition

Compared to previous IFC releases, basic task time information (scheduled start time, scheduled finish time, duration) is now directly attached to IfcTask through the TaskTime attribute. Regular tasks are defined through IfcTaskTime. Recurring tasks are defined through IfcTaskTimeRecurring. In case a regular task is derived from a recurring task both tasks should be linked together through a IfcRelNests relationship, where IfcRelNests.IsNestedBy points to the recurring task and IfcRelNests.Nests points to all regular tasks that have been derived from the recurring task.

5.3.3.6.1.3 Representation of other activities

The use definitions for IfcTask have been generalised to represent other activities as well, including activities that had been defined by own entities in previous IFC releases. This includes

  • Order actions
  • Move operations

IfcTask represents an order that might be carried out by a Helpdesk acting the role of interface for the organization between the facility user and the functional requirement of fulfilling their needs. The actual task represented by the IfcTask entity is turning a request into an order and initiating the action that will enable the order to be completed. The IfcProjectOrder or one of its subtypes including maintenance work order, is related to the IfcTask using IfcRelAssignsToControl.

IfcTask can also be used to describe an activity that moves people, groups within an organization or complete organizations together with their associated furniture and equipment from one place to another. It thus replaces the previous IFC entity IfcMove. The functionality is represented in IfcTask as follows:

  • Move from: The place from which actors and their associated equipment are moving. Use IfcRelAssignsToProcess where RelatingProcess points to the task and RelatedObjects holds the location(s) from which to move.
  • Move to: The place to which actors and their associated equipment are moving. Use IfcRelAssignsToProduct where RelatedObjects points to the task(s) and RelatingProduct points to the location to which to move.
  • Punch list: A list of points concerning a move that require attention. Use LongDescription or else identify sub-tasks to track punch list items individually via IfcRelNests.

5.3.3.6.2 Entity inheritance

5.3.3.6.3 Attributes

# Attribute Type Description
IfcRoot (4)
IfcObjectDefinition (7)
IfcObject (5)
IfcProcess (5)
Click to show 21 hidden inherited attributes
IfcTask (6)
8 Status OPTIONAL IfcLabel

Current status of the task.

9 WorkMethod OPTIONAL IfcLabel

The method of work used in carrying out a task.

10 IsMilestone IfcBoolean

Identifies whether a task is a milestone task (= TRUE) or not (= FALSE).

11 Priority OPTIONAL IfcInteger

A value that indicates the relative priority of the task (in comparison to the priorities of other tasks).

12 TaskTime OPTIONAL IfcTaskTime

Time related information for the task.

13 PredefinedType OPTIONAL IfcTaskTypeEnum

Identifies the predefined types of a task from which the type required may be set.

Table 5.3.3.6.1.3.G

5.3.3.6.4 Formal propositions

Name Description
CorrectPredefinedType

The attribute ObjectType must be asserted when the value of PredefinedType is set to USERDEFINED.

NOT(EXISTS(PredefinedType)) OR (PredefinedType <> IfcTaskTypeEnum.USERDEFINED) OR ((PredefinedType = IfcTaskTypeEnum.USERDEFINED) AND EXISTS(SELF\IfcObject.ObjectType))
HasName

The Name attribute should be inserted to describe the task name.

EXISTS(SELF\IfcRoot.Name)
Table 5.3.3.6.1.3.H

5.3.3.6.5 Property sets

  • Pset_PackingInstructions MOVE
    • PackingCareType
    • WrappingMaterial
    • ContainerMaterial
    • SpecialInstructions
  • Pset_Risk
    • RiskName
    • RiskType
    • NatureOfRisk
    • RiskAssessmentMethodology
    • UnmitigatedRiskLikelihood
    • UnmitigatedRiskConsequence
    • UnmitigatedRiskSignificance
    • MitigationPlanned
    • MitigatedRiskLikelihood
    • MitigatedRiskConsequence
    • MitigatedRiskSignificance
    • MitigationProposed
    • AssociatedProduct
    • AssociatedActivity
    • AssociatedLocation

5.3.3.6.6 Concept usage

Concept Usage Description
IfcRoot (2)
IfcObjectDefinition (9)
IfcObject (5)
IfcProcess (4)
Click to show 20 hidden inherited concepts
IfcTask (7)
Classification Association General

An IfcTask may be assigned a Work Breakdown Structure (WBS) code from of a published external structure or company standard. As well as being used to designate the code, the classification structure also enables the source of the work breakdown structure classification to be identified.

Constraint Association General

Constraints may be applied to a task's scheduled duration, start, or finish, by setting the IfcMetric.ReferencePath to the corresponding attribute on the IfcTaskTime entity.

Figure 5.3.3.6.1.3.A indicates fixed duration of task with ConstraintGrade=HARD and Benchmark=EQUALTO such that changes to an assigned IfcConstructionResource.Usage.ScheduleWork should impact IfcConstructionResource.Usage.ScheduleUsage, and vice-versa.

dot_neato IfcTask IfcTask IfcTaskTime IfcTaskTime IfcTask->IfcTaskTime TaskTime IfcRelAssociatesConstraint IfcRelAssociates Constraint IfcRelAssociatesConstraint->IfcTask RelatedObjects[1] IfcObjective IfcObjective ObjectiveQualifier: PARAMETER IfcRelAssociatesConstraint->IfcObjective RelatingConstraint IfcMetric IfcMetric ConstraintGrade: HARD Benchmark: EQUALTO IfcObjective->IfcMetric BenchmarkValues[1] IfcReference IfcReference AttributeIdentifier: TaskTime IfcMetric->IfcReference ReferencePath IfcReference2 IfcReference AttributeIdentifier: ScheduleDuration IfcReference->IfcReference2 InnerReference
Figure 5.3.3.6.1.3.A — Constraining the task duration

Figure 5.3.3.6.1.3.B indicates how to constrain the scheduled start date of the task. Depending on the ConstraintGrade and Benchmark the constraint may indicate different meanings as shown in Table 5.3.3.6.1.3.J.

ConstraintGrade Benchmark Indicates
HARD EQUALTO Must start on
HARD GREATERTHANOREQUALTO Start no earlier than
HARD LESSTHANOREQUALTO Start no later than
SOFT LESSTHAN Start as soon as possible
Table 5.3.3.6.1.3.J — Different constraints that can be applied to a start date
dot_neato IfcTask IfcTask IfcTaskTime IfcTaskTime IfcTask->IfcTaskTime TaskTime IfcRelAssociatesConstraint IfcRelAssociates Constraint IfcRelAssociatesConstraint->IfcTask RelatedObjects[1] IfcObjective IfcObjective ObjectiveQualifier: PARAMETER IfcRelAssociatesConstraint->IfcObjective RelatingConstraint IfcMetric IfcMetric ConstraintGrade: SOFT Benchmark: LESSTHAN IfcObjective->IfcMetric BenchmarkValues[1] IfcReference IfcReference AttributeIdentifier: TaskTime IfcMetric->IfcReference ReferencePath IfcReference2 IfcReference AttributeIdentifier: ScheduleStart IfcReference->IfcReference2 InnerReference
Figure 5.3.3.6.1.3.B — Constraining the task start date to start as soon as possible

Figure 5.3.3.6.1.3.C indicates how to constrain the scheduled finish date of the task. Depending on the ConstraintGrade and Benchmark the constraint may indicate different meanings as shown in Table 5.3.3.6.1.3.K.

ConstraintGrade Benchmark Indicates
HARD EQUALTO Must finish on
HARD GREATERTHANOREQUALTO Finish no earlier than
HARD LESSTHANOREQUALTO Finish no later than
SOFT GREATERTHAN Finish as late as possible
Table 5.3.3.6.1.3.K — Different constraints that can be applied to a start date
dot_neato IfcTask IfcTask IfcTaskTime IfcTaskTime IfcTask->IfcTaskTime TaskTime IfcRelAssociatesConstraint IfcRelAssociates Constraint IfcRelAssociatesConstraint->IfcTask RelatedObjects[1] IfcObjective IfcObjective ObjectiveQualifier: PARAMETER IfcRelAssociatesConstraint->IfcObjective RelatingConstraint IfcMetric IfcMetric ConstraintGrade: SOFT Benchmark: GREATERTHAN IfcObjective->IfcMetric BenchmarkValues[1] IfcReference IfcReference AttributeIdentifier: TaskTime IfcMetric->IfcReference ReferencePath IfcReference2 IfcReference AttributeIdentifier: ScheduleFinish IfcReference->IfcReference2 InnerReference
Figure 5.3.3.6.1.3.C — Constraining the task finish date to finish as late as possible
Object Nesting General

IfcTask may be contained within an IfcTask using the IfcRelNests relationship. An IfcTask may in turn nest other IfcTask, IfcProcedure or IfcEvent entities. Such nesting indicates decomposed level of detail. From IFC4 onwards it is required to have a summary task (root of all tasks), which is used to define a link to the work plan or work schedule. All subtasks of the summary tasks are then implicitly linked to this work plan or work schedule. Please note that the summary task is used for data organization and not meant to store typical task information as defined by the user. It is therefore recommended that the summary task is hidden from the user to avoid confusion. Please also note that IfcRelNests is used to show the dependency between regular tasks and recurring task definitions (please see the section about time and duration use definitions).

As shown in Figure 5.3.3.6.1.3.D, the installation of a number of items of equipment within a particular space may be the subject of a single task which is identified as 'fix equipment in space 123'. IfcTask represents the occurrence of a work performance of a type of process in a construction plan.

task example
Figure 5.3.3.6.1.3.D — Task visualization

A task may nest other tasks as sub-items; the nesting relationship is modeled by IfcRelNests as shown in Figure 5.3.3.6.1.3.E. For example, the construction of a stud wall may be designated as a nesting task named 'install wall #1' including other tasks such as 'install dry wall', 'install studs', 'wall taping', and 'erect wall' as sub-processes. A value that indicates the relative tree view position of the task (in comparison to the tree view position of other tasks and the task hierarchy defined by IfcRelNests).

The task order information that is used for viewing purposes is derived from the order defined by the IfcRelNests relationship and thus is independent of the logical task order defined through IfcRelSequence. The hierarchy and order defined through IfcRelNests enables to order the tasks in a tree view or list view structure.

task instantiation diagram
Figure 5.3.3.6.1.3.E — Task nesting relationships

A top-level task is declared within the IfcProject using the IfcRelDeclares relationship.

This concept can be applied to the following resources:

Object Typing General

The IfcTask defines the anticipated or actual occurrence of any task; common information about task types is handled by IfcTaskType.

This concept can be applied to the following resources:

Process Assignment General

It is suggested to use the 'summary task' (root element of the task hierarchy that is required for task management purposes) to assign all subtask to a work plan or work schedule. Resources used by tasks are assigned by IfcRelAssignsToProcess.

Property Sets for Objects General

This concept can be applied to the following resources:

Sequential Connectivity General

The relationship IfcRelSequence is used to indicate control flow. An IfcTask as a successor to an IfcTask indicates logical sequence how these tasks should be performed. IfcTask entities can be triggered or can trigger IfcEvent entities, which is also defined through the relationship IfcRelSequence.

Table 5.3.3.6.1.3.I

5.3.3.6.7 Examples

5.3.3.6.8 Formal representation

ENTITY IfcTask
SUBTYPE OF (IfcProcess);
Status : OPTIONAL IfcLabel;
WorkMethod : OPTIONAL IfcLabel;
IsMilestone : IfcBoolean;
Priority : OPTIONAL IfcInteger;
TaskTime : OPTIONAL IfcTaskTime;
PredefinedType : OPTIONAL IfcTaskTypeEnum;
WHERE
CorrectPredefinedType : NOT(EXISTS(PredefinedType)) OR (PredefinedType <> IfcTaskTypeEnum.USERDEFINED) OR ((PredefinedType = IfcTaskTypeEnum.USERDEFINED) AND EXISTS(SELF\IfcObject.ObjectType));
HasName : EXISTS(SELF\IfcRoot.Name);
END_ENTITY;

5.3.3.6.9 References

Edit on Github


Is this page difficult to understand? Let us know!

5.3.3.6.10 Changelog

5.3.3.6.10.1 IFC4

  • attribute, IsMilestone
  • attribute, PredefinedType
  • where rule, CorrectPredefinedType
  • where rule, HasName
  • attribute, TaskId
  • where rule, WR1
  • where rule, WR2
  • where rule, WR3
  • attribute IsMilestone name, Changed from "IsMilestone" to "Priority"
  • attribute IsMilestone optional, Changed from "False" to "True"
  • attribute IsMilestone type, Changed from "boolean" to "IfcInteger"
  • attribute Priority name, Changed from "Priority" to "TaskTime"
  • attribute Priority type, Changed from "integer" to "IfcTaskTime"