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 Macrotask can also be created in Fuzor but is not recommended if expecting the task to update sensibly when changes are made to the Macroschedule.

A Microtask can only be created in Fuzor.

When an XML is imported into Fuzor, Microtasks are created instead of macrotasks. A Macrotask needs to be selected in order to add a microtask to the schedule

Adds a construction Microtask to the currently selected Macrotask. Other Task Types also Create Macrotasks, by default.

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.

By default, the user cannot edit the Macroschedule and Task names and dates of macrotasks appear grey instead of black. This enables the user to easily distinguish between the two.

When a XML update is made microtasks update durations and dates based on the offset that is introduced to an associated macrotask 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.

In some situations the user may need to edit task data in the macroshedule. The user also may be creating a schedule entirely in Fuzor and does not need to use the Macro-Micro relationship.

The Micro and Macro radio button toggle between macro and micro scheduling modes. When in Micro schedule mode the user can only create and edit microtasks. When in Macroscheduling mode The user can edit any task, but can only create Macrotasks.

When an XML is imported, the mode is always switched to macro mode.

A Construction task is the only task type than can be created as a macrotask. However the task type be changed after it is created to any Fuzor task type.

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 the user is prompted to decide whether they would like Microtasks with deleted macrotask to automatically relink to another Macrotask with the closest date or if they would like to manually relink microtasks back to the macroschedule.

If manually relinking is desired any microtasks that are children of deleted macrotasks will become Orphaned.

Orphaned Microtasks always appear at the top of the gantt chart. In order to continue working the microtasks need to be remapped to new macrotasks. The relinking column is used for to remap the microtask to a new macrotask

Selected to relink a microtask. All microtasks contain the icon in the relinking column allowing you to relink them at any time.

After the relinking column in the microtask is selected a macrotask is needed to relink the microtask too. The same column is used to select the macrotask. A different Icon is used to denote a macrotask.

Selected to denote the macrotask that the microtask is being relinked too.

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.