Task Model Approval & Planned Task Updating

Task Model Approval and Planned Task Updating

FAQs  |  Feedback

 Step

  Action

 1

Task Model Approval and Revocation:  It is recommended that a Task Model is submitted for approval so that before tasks are scheduled and performed, the task model has been reviewed for its completeness and accuracy, and approved.  This will lock the version of the task model.  This is important as changing resource allocations to a task model will automatically re-calculate resource requirements for the project, just as one example.

When the workflow buttons are pressed, it will prompt the user if they want to email users who have verification and/or approval rights.  If they select YES to the email notification, CE will automatically load a list of possible verifiers, or approvers, depending on the state it is transitioning from.

The email will be attached with who, what, why and when, and also attach a datasheet of the Task Model for quick review, and a hyperlink to the record.

To revoke a current approved version of the task model, any user who has edit rights to the Task Model module will have the ability to revoke a Task Model, at which point CE will prompt the user for revocation comments.  The revocation process will remove approval status, and clear out the revision number.  In order to re-approve the record a new revision number is required, and cannot be any revision from prior approvals.

Update Planned Tasks.

 2

Update Planned Tasks:  This function is used when planned tasks have already been created, but the task model has been updated. It allows users the ability to update all non-started planned tasks to be updated with their task model information (parent object).   A user can update thousands of tasks in seconds and is a very efficient method to recalculate resource loading, equipment requirements etc.

Update Instantiated Tasks:  This function is used to update all preservation tasks.  Instantiation is termed because when a task has a recurrence; there can be multiple instances of the same preservation task. For example, if a task is meant to be performed weekly, a field technical may have performed the last 5 weeks, but the task model was updated to include a new inspection step due to feedback.  This efficient function only allows one-click of a button to update all scheduled / not-started preservation tasks that were created from that preservation task model.

Next Training:  Task Model Reports

For internal use only