Task Linking

In the realm of large scale construction it is standard to maintain a full project lifecycle schedule usually spanning several years. Relatively speaking, optimal output from Fuzor requires Micro Scheduling, a more detailed and specific scheduling of tasks.

To make a realistic schedule with Fuzor, tasks must be broken down into individual operations. When this is done properly it allows for a holistic and approach to project planning. IDD Teams can perform a detailed and visual audit of the construction simulation before the project begins. This is an opportunity to avoid scheduling issues, safety hazards and modeling errors.

A holistic approach to schedule integrations allows for faster and more accurate turn around time for a ensuing construction simulation audit. After loading new schedule data, each detailed step in a procedure can be reviewed with the revision to the schedule.

Because schedule updates are so integral to Fuzor Project management it is important for a Fuzor user to know the best practices to ensure schedule updates run smoothly.

A Macrotask is a task imported into Fuzor from another software. A psuedo Macrotask can also be created in Fuzor unders specific conditions

A Microtask can only be created in Fuzor.

When a microtask is created it is created as the child of the selected task. This allows users to clearly evaluate the relationship between the microschedule and the macroschedule.

When a XML update is made macrotasks update durations and dates based on the offset that is introduced with the XML update.

When a schedule update is made to ‘Macrotask’ that changes the start date ‘Microtask 1’, ‘Microtask 2’ and ‘Microtask 3’ will all have their start dates adjusted by the same amount.

There are two ways to create multiple microtasks linked together

Creates multiple Microtasks linked together in a chain as children of the currently selected task.

Microtasks can also be created separately and manually linked together.

Sometimes tasks are deleted when a schedule update is made. This means that there are Macrotasks in Fuzor that do not exist in the updated XML. When a macrotask is deleted any microtasks that are children will become Orphaned.

Orphaned Microtasks always appear at the top of the gantt chart and have a special column to allow the user to

INSERT PIC HERE

When Using Merge By ID there is an option to delete tasks with assigned objects. Macrotasks that have no objects assigned will always be deleted if not included in the XML update. the Logic Relationship the best linking method when there are many deleted tasks in the XML as Children are always deleted with their parents.