Editing IFC - Industry Foundation Classes/IFC concepts/IFC sequence concepts
From Wiki.OSArch
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
− | |||
Processes are individual events or tasks. Processes may have different meanings when used in different scenarios. When processes are used in construction, they represent construction tasks which have associated sequence relationships, may transform inputs into outputs, and have relationships to costs, products, and resources. When processes are used in facility management, they represent maintenance tasks, including to-do lists and recurring patterns. | Processes are individual events or tasks. Processes may have different meanings when used in different scenarios. When processes are used in construction, they represent construction tasks which have associated sequence relationships, may transform inputs into outputs, and have relationships to costs, products, and resources. When processes are used in facility management, they represent maintenance tasks, including to-do lists and recurring patterns. | ||
Line 13: | Line 12: | ||
* IfcLagTime | * IfcLagTime | ||
* IfcTaskType | * IfcTaskType | ||
+ | * IfcEvent | ||
+ | * IfcProcedure | ||
Bits that are currently skipped for further analysis: | Bits that are currently skipped for further analysis: | ||
* IfcTask: Quantities of resources consumed by the task are dealt with by defining the IfcElementQuantity for the resource and not at the instance of IfcTask. | * IfcTask: Quantities of resources consumed by the task are dealt with by defining the IfcElementQuantity for the resource and not at the instance of IfcTask. | ||
+ | * IfcTask: Object Typing. Looks complicated. | ||
+ | * IfcTask: An IfcTask may in turn nest other IfcTask, IfcProcedure or IfcEvent entities. | ||
+ | * IfcTask: IfcTask's can be triggered or can trigger IfcEvent's, which is also defined through the relationship IfcRelSequence. | ||
* IfcTask: Constraints may be applied to a task to indicate fixed task duration, fixed start or fixed finish, where IfcMetric.ReferencePath is set to the corresponding attribute on the IfcTaskTime entity. | * IfcTask: Constraints may be applied to a task to indicate fixed task duration, fixed start or fixed finish, where IfcMetric.ReferencePath is set to the corresponding attribute on the IfcTaskTime entity. | ||
Line 223: | Line 227: | ||
Source: IfcWorkCalendar | Source: IfcWorkCalendar | ||
− | == A work calendar can be inherited through child tasks | + | == A work calendar can be inherited through child tasks == |
<!-- | <!-- | ||
Line 242: | Line 246: | ||
If a task does not have a calendar assigned to it, it inherits the calendar from its parent task. This inheritance makes it easy to assign default calendars to a top level task in a work schedule and only override as necessary in more specific child tasks. | If a task does not have a calendar assigned to it, it inherits the calendar from its parent task. This inheritance makes it easy to assign default calendars to a top level task in a work schedule and only override as necessary in more specific child tasks. | ||
− | |||
− | |||
Note: it is assumed, but no evidence found, that hierarchical resources have this same inheritance behaviour. In other words, it is assumed that if a resource does not have a calendar assigned to it, it inherits the calendar from its parent resource. | Note: it is assumed, but no evidence found, that hierarchical resources have this same inheritance behaviour. In other words, it is assumed that if a resource does not have a calendar assigned to it, it inherits the calendar from its parent resource. | ||
Line 639: | Line 641: | ||
Source: IfcTask | Source: IfcTask | ||
− | == A task | + | == A task may contain properties == |
<!-- | <!-- | ||
Line 660: | Line 662: | ||
[[File:Ifc-concept-sequence-task-pset.png]] | [[File:Ifc-concept-sequence-task-pset.png]] | ||
− | A task | + | A task may contain properties. Typically this is used for risk assessment. For logistic tasks, it may also contain properties for packing instructions. |
Source: IfcTask | Source: IfcTask | ||
Line 734: | Line 736: | ||
--> | --> | ||
− | [[File:Ifc-concept-sequence-task-type-nest-task.png]] | + | [[File:Ifc-concept-sequence-task-type-nest-task.png|thumb]] |
Note: It is currently ambiguous as to what this means. | Note: It is currently ambiguous as to what this means. | ||
Line 805: | Line 807: | ||
Source: IfcTaskType, IfcRelDefinesByObject | Source: IfcTaskType, IfcRelDefinesByObject | ||
− | |||
− |