Float fields
For each field listed below, the following information is given:
- Description - the information displayed by the field when added to the spreadsheet or to a text annotation.
- Parameters - any additional, optional parameters that you can use to modify the information that the field displays or the way in which the information is displayed.
- Editable? - whether the field is editable when displayed in a spreadsheet column. If a field is editable in the spreadsheet, you can change the data displayed in the column to edit the properties of the corresponding bar, task or allocation.
Breaks critical path integrity
Description |
You can configure Asta Powerproject to check the integrity of the critical path when rescheduling. If you do, this field identifies any incomplete critical tasks that are linked incorrectly in such a way that the integrity of the critical path is broken. If a task breaks the integrity of the critical path, you should examine its links for logical errors.
If you do not configure Asta Powerproject to check the integrity of the critical path when rescheduling, this field's check box is cleared for all tasks.
For more information, refer to Checking the integrity of the critical path when rescheduling. |
Parameters |
|
Editable? | No |
Buffer consumption
Description |
A numerical value showing either:
Careful monitoring of this field, for example by displaying it in the spreadsheet and sorting on it, enables you to keep track of buffer tasks that are shrinking or growing to undesirable durations.
You can also use this field to monitor the consumption of interruptible tasks if required.
For more information, refer to Working with buffer tasks. |
Parameters |
|
Editable? | No |
Critical
Description |
Whether or not a task is on the critical path.
For more information, refer to Understanding the results of rescheduling. |
Parameters |
|
Editable? | No |
Critical path drag
Description |
Critical path drag (Devaux's Removed Activity Gauge) can be thought of as:
You can calculate the drag of critical tasks when rescheduling.
For more information, refer to Calculating the drag of critical tasks when rescheduling. |
Parameters |
|
Editable? | No |
Early finish
Description |
The earliest date that a task can finish, within the logical constraints of the plan.
For more information, refer to Bar and Task Properties dialog - Task tab. |
Parameters |
|
Editable? | No |
Early start
Description |
The earliest date that a task can start, within the logical constraints of the plan.
For more information, refer to Bar and Task Properties dialog - Task tab. |
Parameters |
|
Editable? | No |
Free finish
Description |
A task's finish date, using up any period of free float.
For more information, refer to Bar and Task Properties dialog - Task tab. |
Parameters |
|
Editable? | No |
Free float
Description |
The period that a task can be delayed before any successor task is affected.
For more information, refer to Bar and Task Properties dialog - Task tab. |
Parameters |
|
Editable? | No |
Free start
Description |
A task's start date, using up any period of free float.
For more information, refer to Bar and Task Properties dialog - Task tab. |
Parameters |
|
Editable? | No |
Late finish
Description |
The latest date that a task can finish, within the logical constraints of the plan.
For more information, refer to Bar and Task Properties dialog - Task tab. |
Parameters |
|
Editable? | No |
Late start
Description |
The latest date that a task can start, within the logical constraints of the plan.
For more information, refer to Bar and Task Properties dialog - Task tab. |
Parameters |
|
Editable? | No |
Longest path
Description |
Whether or not a task is on the longest path through the project network.
A task is computed to be on the longest path if one or more of the following is true:
If a summary task contains tasks that are on the longest path and the summary task has an incoming driving link, the summary itself is also on the longest path. |
Parameters |
|
Editable? | No |
Nearly critical
Description |
Whether or not a task has an amount of total float at or below the critical gap that has been defined on the Schedule tab of the Format Bar Chart dialog. You can use the critical gap to display tasks that have a specified amount of total float (or less) as if they are critical. This alerts you to tasks that are almost critical as well as ones that are actually critical, so that you can take action to ensure that they are completed on time. Note that when you choose to display nearly critical tasks as critical, they appear without float in the bar chart.
Note that the status of this field is unaffected by whether you choose to display nearly critical tasks as if they were critical, using the Show nearly critical tasks as critical check box on the Schedule tab of the Format Bar Chart dialog. Note also that as the critical gap is defined on a per-view basis, this field may display different values for the same task in different views. |
Parameters |
|
Editable? | No |
Original buffer task duration
Description |
For buffer tasks and interruptible tasks, the duration that a task had at the point at which it was defined as a buffer task or an interruptible task. You can change the value of this field by editing it in the spreadsheet, or by removing the buffer task or interruptible task designation from a task, then redefining it as a buffer task or interruptible task - at which point the field takes the current duration of the task.
For more information, refer to Working with buffer tasks and Working with interruptible tasks. |
Parameters |
|
Editable? | Yes |
Total float
Description |
The period that a task can be delayed before the project finish date is affected.
For more information, refer to Bar and Task Properties dialog - Task tab. |
Parameters |
|
Editable? | No |
Total float variance
Description |
The difference between the total float of a task in the live data and its total float in the specified baseline. You can display the total float variance in a time unit of your choice.
You may find this field useful if you use logical paths to monitor the erosion of total float: once you have identified those tasks that are most likely to affect the project finish date if they are delayed, you can monitor the total float variance of these tasks to ascertain whether it is increasing or decreasing as a project progresses.
For more information, refer to Using logical paths to monitor the erosion of total float. |
Parameters |
|
Editable? | No |