Page Comparison

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 Schedulingmicro 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 an 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 project management it is important for a Fuzor user to know the best practices to ensure schedule updates run smoothly.

Fuzor enables users to control this by clearly defining the difference between tasks that are imported from other software and should be updated directly by a schedule update and tasks created in Fuzor.

A Macrotask Macro Task is a task imported into Fuzor from another software. A Macrotask macro task can also be created in Fuzor but is not recommended if expecting the task to update sensibly when changes are made to the Macroschedulemacro schedule.

A Microtask Micro Task can only be created in Fuzor. macro tasks have special scheduling logic that allow you to

When an XML is imported into Fuzor, Microtasks By default, micro tasks are created instead of macrotasksmacro tasks when using the create construction task button. A Macrotask macro task needs to be selected in order to add a microtask micro task to the schedule.

Adds a construction Microtask micro task to the currently selected Macrotaskmacro task. Other Task Types also Create 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.