...
- Each Status added to the Milestone Report grid view receives an associated filter, titled "<Status> : Completion". This allows Users to filter according to the Schedule Compliance for that status.
- Under each status, the Milestone Report displays icons that communicate whether a System Element reached a status by the Planned Date, after the Planned Date, or with no Planned Date set.
Icon | Schedule Compliance | Description |
---|---|---|
Not Planned | No Planned Date has been set for the System Element Status. | |
Late | The System Element transitioned into the status after the Planned Date, or the System Element has not transitioned into the target status and the Planned Date has already passed. | |
On Time | The System Element transitioned into the status before the Planned Date. | |
On Time - Pending | The System Element has not transitioned into the status and the Planned Date is still in the future. | |
n/a | On Time - At Risk | The System Element has not transitioned into the status, the Planned Date is still in the future, but a dependency status is late. ** Currently Users are able to Filter according to this condition, but the grid view does not display an icon for "On Time - At Risk" Schedule Compliance. |
Expand | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
|
Milestone Report Summary
...
The Milestone Report Summary allows Users to display milestone progress for System Elements according to Location. Selecting a Location under the Location column will open the relevant Milestone Report grid view displaying all of the devices at that Location and any relevant milestone progress for the System Element and associated components (e.g., links, connections, terminations).
...
Expand | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
|
Device Task Completion Progress
...
InfraLink Device Tasks are currently measured, in terms of reporting purposes, as 100% complete or 0% complete. While adequate for Tasks associated with low labor estimates, this limitation is amplified when a single task has a very large labor component, sometimes hundreds of hours. It can result in misleading progress reporting, an inability to forecast the remaining work, and/or an inaccurate roll-up of all work on a project. For example, pulling a feeder cable with many sets is often tracked as a single Task. However, the completion percentage for that Task should be updated when each set is pulled.
...