This chapter provides project management workflows that enable Microtasks to automatically update when new schedule is loaded.
...
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. | ||||||
Addtionally Microtasks can also be created separately and manually linked together. | |||||||
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 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. | |||||||
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:
Microtasks and Macrotasks exist in the Fuzor Project.
Tasks In both the original and the Update XML have the same ID, Unique ID if using Microsoft Project.
Manually schedule tasks is unchecked in the Fuzor Construction Settings.
Autofill duration is checked in the Fuzor Construction Settings.
Changes to durations Macrotasks are not expected to reflected in Linked Microtasks.
New Calendars, Baselines, and Activity Codes are not needed or unchanged in the update.
The data date is not changed.
We are expecting dates and durations of the Microtasks to be offset by the change in dates and durations of macrotask it is linked too.
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
Manually schedule tasks was enabled for a specific task in the authoring software and the setting is needed in the Fuzor Project to ensure that the date matches for the task. This can be resolved by ensuring that the authoring software has proper logic. with respect to DCMA guidelines? CHECK THAT ONE
Schedule data was exported from the authoring software before conducting a proper schedule update and there is invalid data in the schedule. This can be resolved by running a schedule update before exporting the XML.
. |