This chapter provides project management workflows that enable Microtasks to automatically update when new schedule is loaded.
Micro vs Macro
Learn why schedules updates are so important to Fuzor workflow.
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. |
Creating the Microschedule
Learn how to start creating the detailed Microschedule 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 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. | |||||||
Addtionally |
Orphaned Tasks
Learn how to handle microtasks that are associated with macrotask that is deleted in a schedule update.
Deleted Macrotasks : 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. Depending on whether these tasks are linked to microtasks or have objects assigned, there are a few different things that we may be expecting to happen. Below are some potential expectations and the best workflow associated with that result. 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. |
Handling Specific Update Cases
Learn how to use different Linking Methods and Schedule Update Methods to Properly manage a project in different schedule update situations.
Base Update Case : To understand the other cases of schedule updates. We first need to understand what the most simple update case is:
If the schedule update meets the above parameters any Update workflow and Linking method is appropriate and Microtasks will update as expected with their associated relationship. | |||||||
Changes to Calendars the Data Date and Resources: Both Calendars and the Data Date can effect dates and durations of tasks in the project. If these are not imported or updated during a schedule update it is possible that the dates in your Fuzor Project are inconsistent with that of your authoring software. Resources may affect cost calculations. If these are not imported or updated during a schedule update it is possible that the costs in your Fuzor project are inconsistent with that of your authoring software. An XML update is needed to update or import new Calendars and Resources, Update the Data Date, or change resource and calendar task assignments and allocation. However, Column Mapping can be used to update incorrect costs directly and handle them as edited total costs. | |||||||
Changes to Activity Codes : blash balsh XMLS are needed for the activty codes | |||||||
Manually Schedule Tasks : If manually schedule tasks is enabled Fuzor does not respect any logic in the schedule. This means that neither Task Linking Method will update Microtasks that are linked to updated Macrotasks. If substantial lag is introduced early in critical path the result would be an project where Microtasks are occuring far before Macrotasks that they are linked too. There are a few common reasons why a user might enable Manually Schedule Tasks
Fuzor does not support schedule updates for Microtasks when Manually Schedule Tasks is checked. The above issues need to be resolved in order for a Task Linking Method to be effective. |