|
MetricID
|
Description
|
SSI Inspection Method
|
Metric Threshold
|
Project Archive required
|
DECM Test Spec
|
SSI Test Method
|
|
06A204b
|
Are there open starts or finishes (“dangling logic”) in the schedule?
|
Inspect the Predecessors & Successors for each incomplete task and milestone for missing dependency to their start or from their finish. The Schedule will pass this test if 0% of incomplete task or milestone are missing a start dependency. Excludes tasks or milestones that Start or Finish the project.
|
X = 0
|
No
|
|
|
|
06A205a
|
Are lags used in the schedule?
|
Inspect the Predecessors for each incomplete task and milestone for dependencies with lag. The Schedule will pass this test if <= 10% of inspected items have at least one lag.
|
X/Y <= 10%
|
No
|
|
|
|
06A208a
|
Do summary tasks in the schedule have logic applied?
|
Inspect the Predecessors and Successors for Summary tasks. The Schedule will pass this test if 0% of summary tasks have predecessor or successor.
|
X = 0
|
No
|
|
|
|
06A209a
|
Are schedule network constraints limited?
|
Inspect each incomplete task and milestone for hard constraints (Must Start/Finish on, Start/Finish no later than). The Schedule will pass this test 0% inspected item have a hard constraint.
|
X = 0
|
No
|
|
|
|
06A210a
|
Do LOE tasks/activities have discrete successors?
|
Inspect each incomplete LOE for successors to discrete tasks (not LOE or SVT). The Schedule will pass this test if 0% inspected items have a discrete successor.
|
X = 0
|
No
|
|
|
|
06A211a
|
Is high float rationale/justification acceptable?
|
Lists all incomplete, non-LOE tasks and milestones with high float according to the user's high float value on the Saved Settings tab of the SSI DECM form. SSI scores this according to the threshold but does not make a determination regarding acceptable rationale/justification since this can be subjective.
|
X/Y <= 20%
|
No
|
|
|
|
06A212a
|
Are there out of sequence tasks/activities & milestones?
|
Inspects the successors of Incomplete Tasks and milestones. If dependency is Finish-to-start, determines if start of successor is before finish of the predecessor. If Start-to-start, determines if start of successor is before the start of the predecessor. If Finish-to-finish, determines if finish of successor is before the finish of the predecessor. If Start-to-finish, determines if the finish of the successor is before the start of the predecessor. If out of sequence is caused by leads (negative lag) justification/rationale must be provided.
|
X/Y <= 1%
|
No
|
|
|
|
06A301a
|
Are lower level baseline and forecast dates traceable to, and not outside, the corresponding higher level dates in the IMS?
|
Inspects the Baseline Start and Finish of the parent task and determines if the task's baseline period of performance is within the parent task's baseline period of performance.
|
X = 0
|
No
|
|
|
|
06A401a
|
Does the schedule tool produce a critical path that represents the longest total duration with the least amount of total float?
|
Step 1, Inspect the tasks marked as critical per Microsoft Project's critical flag or your own flag field. Step 2, Add a constraint date, which is prior to the end point's current date or baseline date (whichever produces negative float). Tasks with negtive float should be the same as the tasks marked as critical from step 1.
|
X = 0
|
No
|
|
|
|
06A501a
|
Do all tasks/activities/milestones in the IMS have baseline start and finish dates?
|
Tasks & milestones without baseline dates
|
X/Y <= 5%
|
No
|
|
|
|
06A504a
|
Are actual start dates changed after first reported?
|
Identify tasks in the prior reporting period with an Actual Finsih date for comparison to the same tasks in the current schedule according to their UniqueID. Differences between Actual Start dates in prior vs current period are reported as findings for the numerator of this test.
|
X/Y ≤ 10%
|
Requires Current Project plus 1 prior reporting period
|
|
|
|
06A504b
|
Are actual finish dates changed after first reported?
|
Identify tasks in the prior reporting period with an Actual Start date for comparison to the same tasks in the current schedule according to their UniqueID. Differences between Actual Finish dates in prior vs current period are reported as findings for the numerator of this test.
|
X/Y ≤ 10%
|
Requires Current Project plus 1 prior reporting period
|
|
|
|
06A505a
|
Do all in progress activities have actual start dates?
|
Percent Complete or Physical % Completeis >0 w/o Actual Start dates
|
X/Y <= 5%
|
No
|
|
|
|
06A505b
|
Do all complete tasks/activities have actual finish dates?
|
Identifies tasks having a EV Percent Complete (using Physical % Complete) = 100 w/o Actual finish dates
|
X/Y <= 5%
|
No
|
|
|
|
06A506a
|
Are actual start and actual finish dates valid for all tasks/activities & milestones in the IMS?
|
Actual dates after the status date
|
X/Y <= 5%
|
No
|
|
|
|
06A506b
|
Are forecast start and finish dates valid for all tasks/activities & milestones in the IMS?
|
Forecast start or finish dates before the status date
|
X = 0
|
No
|
|
|
|
06A506c
|
Are forecast start/finish dates riding the status date of the IMS for two consecutive months?
|
Report of tasks riding the status date (within 3 working days or 5 calendar days) for two consecutive periods.
|
X/Y <= 1%
|
Requires Current Project plus 1 prior reporting period
|
|
|
|
06I101b
|
Do schedule margin tasks represent risk impact to subsequent major milestones?
|
Report Schedule Margin tasks with resource assignments (may imply scope) or task successors (instead of milestones)
|
X = 0
|
No
|
|
|
|
06I201a
|
Are Schedule Visibility Tasks (SVTs) identified and controlled in the IMS?
|
Report of tasks identified as SVT with resources assignments - may imply scope and part of the PMB
|
X = 0
|
No
|
|
|
