'ASAP force critical' quality metric

Use this metric to check the proportion of tasks that are not configured to be ASAP Force Critical. It is not good practice to configure tasks to be ASAP Force Critical, as this can introduce unwanted float into a schedule.

You can change the impact that this metric has on the weighted total result of a quality check by entering a factor by which the quality metric should be multiplied in the Weighting field. For the weighting to have any effect, a quality check must have more than one quality metric.

Pass and fail criteria

Pass or fail?	Criteria
Pass	A project passes this metric if the percentage of tasks that are not configured to be ASAP Force Critical is greater than or equal to the pass boundary percentage. For example, if the pass boundary was set to 100.00%, a project would pass this metric if 100.00% of tasks were not configured to be ASAP Force Critical.
Fail	A project fails this metric if the percentage of tasks that are not configured to be ASAP Force Critical is less than the fail boundary percentage. For example, if the fail boundary was set to 100.00%, a project would fail this metric if less than 100.00% of tasks were not configured to be ASAP Force Critical.
Neither pass nor fail	If the percentage of tasks that are not configured to be ASAP Force Critical falls between the pass and fail boundary, the result is neither a pass nor a fail, but somewhere in between.

Pass or fail?

Criteria

Pass

A project passes this metric if the percentage of tasks that are not configured to be ASAP Force Critical is greater than or equal to the pass boundary percentage.

For example, if the pass boundary was set to 100.00%, a project would pass this metric if 100.00% of tasks were not configured to be ASAP Force Critical.

Fail

A project fails this metric if the percentage of tasks that are not configured to be ASAP Force Critical is less than the fail boundary percentage.

For example, if the fail boundary was set to 100.00%, a project would fail this metric if less than 100.00% of tasks were not configured to be ASAP Force Critical.

Neither pass nor fail

If the percentage of tasks that are not configured to be ASAP Force Critical falls between the pass and fail boundary, the result is neither a pass nor a fail, but somewhere in between.

Suggested settings

Pass boundary: 100.00%. A project will pass this metric if no tasks are configured to be ASAP Force Critical.
Fail boundary: 100.00%. A project will fail this metric if any tasks are configured to be ASAP Force Critical.

The following table shows whether some example projects would pass or fail this metric using these settings:

Percentage of tasks that are not configured to be ASAP Force Critical	Pass or fail?
0.00%	Fail
50.00%	Fail
99.99%	Fail
100.00%	Pass

Does the metric force a project to be rescheduled?

No.

Suggested actions if a project fails this metric

If a project fails this metric, select the metric in the Quality Check Results dialog and click Show Failing Tasks to view the tasks that have failed the metric.

You could take the following actions to remedy the failing tasks:

Remove the ASAP Force Critical placement setting from the failing tasks.
Use constraint flags or links to determine the dates on which tasks must start and finish.