4D Analysis
Learn various tools and methods to perform analysis on your construction schedule in Fuzor
Planned vs Actual
This section contains detailed information on planned vs actual durations, and highlight colors
|
|
|
|
|
|
|
|
---|---|---|---|---|---|---|---|
Utilizing planned vs actual scheduling allows you to visualize differences between various schedules. Each simulation schedule can be mapped to a Simulate column in the Task Table. By default the 3D view displays objects based on the durations in the primary simulation column. | |||||||
To enable Planned vs Actual views select the Planned/Actual button in the 4D Simulation Toolbox. This opens a new window that displays the 3D view based on the durations currently mapped to the alternate simulate column. Below is an example of both the planned and actual window opened. | |||||||
Predecessors and Successors
This section demonstrates how to create, manage and use task relationships.
|
|
|
|
|
|
|
|
---|---|---|---|---|---|---|---|
Task relationships are an important function of Fuzor’s scheduling system. Similarly to Standardized scheduling software tasks in Fuzor can be linked together forcing chronological ordering. If Auto Calculate Schedule in the 4D settings is checked when durations are changed or a schedule lag is introduced task schedules are recalculated to not break the relationship. | |||||||
In some situations, a dialog menu appears if a change to a task’s schedule violates a task relationship. If Yes is selected the task relationship is removed. If working with a complex schedule where links are important you might want to uncheck Auto Calculate Schedule. For more information see 4D Settings. | |||||||
To link tasks together in the Gantt chart hover over the space directly after the task finishes, click and drag it to the beginning of or the end of the task you wish to link it to. | |||||||
This assigns the task you dragged from as a predecessor of the task you are assigning it too. The above example shows two linked tasks. | |||||||
Links all selected tasks together | |||||||
Removes all links on selected tasks | |||||||
Divides a task into multiple linked child tasks | |||||||
The Create Predecessor Chain button prompts you to select a how you want the chain to be linked. | |||||||
Finish-Start ensures that the predecessor completes before the successor begins. Finish-Finish ensures that the predecessor completes before the successor completes. Start-Finish ensures that the predecessor begins before the successor completes. Start-Start ensures that the predecessor begins before the successor begins Using the Predecessor or Successor columns in the task table you can see all of the relationships of a task, as well as add or remove relationships. Each relationship is denoted by its task ID and separated by commas when referencing multiple links. To assign a lag to a link you can insert algorithmic notation such as 2FS+1d, "start one day after task 2 finishes". Lags can either be negative or positive. a negative finish to start lag link would ensure that a preceding task completes within a given time frame after the successive task begins. | |||||||
Use the Task Details Tab to review and or remove task relationships. To open this tab, click the Task Details button is located in the 4D Simulation Toolbox. With the Task Details Tab, you can view all of the predecessor and successor links for the currently selected task. The first number in each link row is the ID of the linked task. | |||||||
To Add a predecessor or successor enter the ID of the task into the associated textbox and select the associated addition symbol. | |||||||
Adds the task with the entered ID as a predecessor or successor. | |||||||
Remove the associated task link. |
Critical Path
Learn how to display the Critical Path of a schedule.
|
|
|
|
|
|
|
|
---|---|---|---|---|---|---|---|
Critical path analysis is an important aspect of a schedule health check. Your critical path is the chain of tasks with the longest duration. Introducing a schedule slip to a critical path with a total float of 0 should push back your completion date. | |||||||
To see the critical path of the schedule, first make sure that the Task State is enabled in the 4D Settings menu. When this is enabled the Toggle Critical Path check box appears above the Task Table. Tasks highlighted Red are part of the critical path. Tasks highlighted Blue are complete with respect to date and time in the schedule Tasks highlighted Green are incomplete with respect to date and time in the schedule. |
Schedule Quality Assessment
Learn how to use the 14 Point Schedule Assessment tool
|
|
|
|
|
|
|
|
---|---|---|---|---|---|---|---|
Guidelines are organized into 14 metrics that can be used to assess risk in a schedule. This manual section provides detailed processes to perform a 14 point analysis in Fuzor. Points on this assessment are suggestive and metrics may be exceeded as long as proper reasoning is provided in excuse. Many of the metrics are used to simply the schedule such that you can accurately conduct more complex analysis. In order to make an accurate assessment it is important to know which tasks are complete with respect to the current date in the schedule. The following recommended settings can be accessed from the 4D settings menu for more information see 4D Settings. Many of the metrics in the Schedule Quality Assessment app depend on scheduling logic. | |||||||
The Auto Fill Duration checkbox should be checked. This ensures that the durations of your tasks match their start and end dates. The Manually Schedule Tasks checkbox should be unchecked. This ensures that your predecessor relationships and constraints are not violated. | |||||||
The Schedule Quality Assessment tool is located in the bottom right corner of the Construction Toolbar | |||||||
When Opened the Schedule Quality Assessment tool Displays each of the 14 point metrics. A schedule must be populated for the test to be run. | |||||||
The Missing Logic metric is meant to ensure that a schedule is properly linked together. In theory the number of incomplete tasks that do not have predecessors and successors should not exceed 5% of all incomplete tasks. Below is the formula to calculate the Logic Metric. If is greater than 5% this is a flag. | |||||||
The Leads metric suggests that you have no leads (Negative Lags) in your schedule. This is because leads can skew the results of your critical path analysis. It is advisable to break tasks up into smaller tasks in order to preserve a more direct relationship. Below is the formula to calculate the Leads Metric. If is greater than zero this is a flag. | |||||||
| |||||||
The Lags metric ensures that the number of lags in your schedule is minimal enough to not skew more complex assessments. Lags can be replaced with tasks that describe the process that is being waited on. For example: A task that elapses the amount of time concrete must set before forms can be removed. Below is the formula to calculate the Lags Metric. If is greater than 5% this is a flag. | |||||||
| |||||||
The Relationship Types metric ensures that the logic links in your schedule are stable enough to ensure accurate results in more complex assessments. The Finish to Start Logic Link provides a logical path through the schedule. Below is the formula to calculate the Relationship Types Metric. If is less than 90% this is a flag. | |||||||
| |||||||
The Hard Constraints metric provides a framework for keeping your schedule logic driven. Hard constraints may prevent tasks from being moved by their dependencies. Hard Constraints are any of the following: Must-Finish-On (MFO), Must-Start-On (MSO), Start-No-Later-Than (SNLT) & Finish-No-Later-Than (FNLT). Below is the formula to calculate the Hard Constraints Metric. If exceeds 5% this is a flag. | |||||||
| |||||||
The High Float Metric ensures that the network of logic is stable. A task with a float over 44 working days is considered high and may be the result of missing predecessors. Below is the formula to calculate the High Float Metric. If is greater than 5% this is a flag. | |||||||
| |||||||
The Negative Float Metric suggests that you have no negative floats. Tasks with negative floats may delay the completion of other tasks. Below is the formula for the Negative Float Metric. If is greater than zero this is a flag. | |||||||
| |||||||
The High Duration Metric identifies tasks that may be able to be broken down into smaller and more concise tasks. A task with a duration over 44 working days is considered high and may be the easily split into smaller more concise tasks. Below is the formula for the Negative Float Metric. If is greater than 5% this is a flag. | |||||||
| |||||||
The Invalid Dates Metric ensures that task start and finish dates are accurately recorded. Incomplete tasks must have a planned finish date after the current date in the schedule. Additionally, any actual finish or start dates must occur before the data date in the schedule. If any of the actual dates fall after the data date this is a flag. If any of the planned dates fall before the data date this is also a flag. | |||||||
The Resources Metric ensures that all tasks with durations greater than zero have a cost associated with them. Below is the formula for the Resources Metric. If is greater than 0 this is a flag. Actual/forecast. | |||||||
| |||||||
The Missed Tasks Metric measures the accuracy of the baseline plan. This Metric is purely retrospective. It only includes tasks that are supposed to be complete with respect to the baseline plan. Below is the formula of the Missed Tasks Metric If is above 5% this is a flag. | |||||||
| |||||||
The Critical Path Test Metric intends to evaluate the integrity of the network logic in the schedule. | |||||||
This is not done automatically and must be enabled in the DCMA App Such an action should cause the projected finish date to change by the same margin. | |||||||
The Critical Path Length Index Metric intends to measure the efficiency of your ability to complete a milestone on time. To assess this metric, you need to find the length of your Critical Path. | |||||||
| |||||||
The Baseline Execution Index Metric measures the congruency of tasks completion status with the baseline plan. This metric only includes tasks that are complete as of the data date. It does not concern itself whether the task was completed on time. Below is the formula fo the Baseline Execution Index Metric. If is Less than 0.95 this is a flag. | |||||||
| |||||||
Each of the metrics can be expanded to view information relating to the tasks that are violating the laws of the Metric. | |||||||
Additional Options in the Schedule Assessment App Change whether some of these metrics ignore specific types of tasks. | |||||||
These settings effect all metrics excluding the Critical Task Test. | |||||||
The Include WBS Tasks checkbox removes parent tasks from being included with their children The Include Milestone Tasks checkbox removes tasks that are set as milestones. The Include Level of Effort Tasks checkbox removes tasks whose duration are dependent only on logic links. The Include Finished Tasks checkbox removes tasks that have been completed. | |||||||
A report of your Schedule Assessment can be exported as a CSV or a PDF. | |||||||
PDF Reports include additional Schedule Assessment Information. |
Task Report
Learn how to export specific schedule information to CSV
|
|
|
|
|
|
|
|
---|---|---|---|---|---|---|---|
The task report is accessed from the 4D Toolbox. Using the task report you can create CSV with filtered data. Exported data is compatible with PowerBi. The entries in the Task Report list are in reference to columns in your table. Data in all checked columns is exported for tasks that exist within the Start and End date of the report. The Only Show Selected checkbox hides unchecked columns. The Start Date selects the start date of the report The End Date selects the end date of the report The Export CSV button exports the CSV with the associated settings |