Time Calc Engineering
Engineering Work to The Time Calc Code
The core processing engine for new time and critical path derivation has been completely re-engineered. This not only brings about significant performance improvements, it enhances scalability and positions the product for enhanced flexibility in future dependency management.
Changes to Previous Functionality
Pre Deployment Tasks
Pre Deployment Tasks no longer get planned times. They will only ever get planned and baseline times. If Pre Deployment Tasks are not completed ahead of the Implementation start time then they will begin to impact the start of the Deployment and you will see that the start time of the Deployment will push out to the left over the Runbook gauge.
Suspending Activity in the Runbook
When suspending a Runbook where there are available tasks, on suspension these tasks will transition to a state of pending rather than suspended.
On completion of any active tasks in a Suspended Runbook successor tasks will remain in a pending state, rather than transitioning to suspended which previously occured.
When a Runbook is suspended which contains one remaining stage and one active task, on completion of the active tasks, any skipped tasks and auto complete checkpoints will remain pending until the Runbook has been reactivated. On Re-Activation of the Runbook the skipped tasks and auto complete checkpoints will transition to complete.
Activating the Backout
On activating the backout, any Active Implementation Tasks will transition to a state of complete. Any Available tasks will transition to state of Not Available.
TIMESTAMPS and the Runbook Lifecycle
Pre Deployment Tasks will never show a planned times
Approve Task - this will timestamp the baseline duration given to a task.
Approve Runbook - this will timestamp the baseline start and end of tasks. If you update a task after this point, planned times will then update.
Commit Runbook - this will timestamp the planned start end and duration of tasks. If you updated a task after this point forecast times update.
Working Examples:
You have a Committed Runbook, from the Runbook, you add a new stage either via add, move or copy. The newly placed stage will only have forecast times populated.
You have an Runbook which is in a Review state - so the Tasks have been approved, you update one of the tasks duration, the baseline duration will remain the same, however the planned duration of the tasks would be updated to reflect the new duration of the task.