Embedded Files
In the Object Manager, a task is (as it sounds) work to be executed to complete a project. Tasks can be broken down into a hierarchy, which is known as a Work Breakdown Structure (WBS,) to help keep track of all the tasks. Each task is given a name and a place in the task hierarchy.
Tasks are work that someone or something (e.g., a machine) needs to do. A task can be a work order, a road design task, etc. One task can be a component of another, creating a dependency. Each task is of a certain type. For each task type, there is a tool used to perform that type of task. The task type ‘Alignment’, for example, is performed using the Alignment Design tool.
Tasks provide the features needed to do the task, and a way to add results data to the model.
Each task stores information about which objects in the model were used as input into the task, as well as which objects were created in the model as a result of the task being executed. There are some exceptions to this; tasks that do not necessarily have input data from the model (import tasks, for example) and tasks that do not produce results in the form of objects, such as presentation tasks. A task can therefore produce anything from 0 to 1 or several thousand objects.
Note: A task can be repeated until you are satisfied with the results.
Summary tasks are used to divide and break down the activities into achievable tasks.
The example under shows a task hierarchy structure with summary tasks being used as containers leading down to an Import task called "Import L_20000.XML". This task creates creates objects of the "CantSpecification" and "LinearElement" type.
Tip: To see the features created as the result of a task, click the cogwheel in the top right corner of the Explorer pane and enable Show Result Feature for Tasks
Page updated
Report abuse