Issues/Actions Lifecycle

The Issue and Action lifecycle is a linear workflow progression that begins in the Draft state and ends either in the Closed or Effective state. Outlined below is an overview of each of state, purpose, and next steps.

  • Draft
    • You must have the correct permissions to log a new Issue
    • Overview: the issue is fully editable, no workflows have been launched
    • Purpose: this state allows users to complete the core information required to login the issue; users can create and assign Actions
    • Next steps: Either the issue investigators or any user with the appropriate permissions chooses users for the required workflow steps and clicks  on the Workflow tab
  • Awaiting Approval
    • Overview: the issue is locked, users will only be able to edit some fields on the details tab, add attachments, update custom fields, log comments, or close Actions
    • Purpose: this state gives item owners the opportunity to review the details of each of their items (Issue or Action) then enforces the Site Workflow Approval
    • Next steps: first the investigators and Action assignees will need to review and sign-off of the details their items; all alerts are sent simultaneously. After the investigator and assignee reviews, the site workflow steps will need to be signed
  • Implementation
    • Overview: the issue is locked, users will only be able to edit some fields on the details tab, add attachments, update custom fields, log comments, or close Actions
    • Purpose: Action assignees can complete their Actions and issue investigators can log additional information
    • Next steps: All of the Actions will need to be completed before the issue will transition to the next state
  • Final Review
    • Overview: the issue is locked, users will only be able to edit some fields on the details tab, add attachments, update custom fields, or log comments
    • Purpose: Final reviewers can confirm that all of the issue details were logged correctly and that all of the Actions were completed as specified
    • Next steps: The final review users will need to sign

Following the Final Review stage, depending on the defined workflows, there are two potential states. If no Effectiveness Check has been assigned, the issue will either move to the Closed state.

If an Effectiveness Check has been assigned, the Issue will transition through the states below:

  1. Awaiting Effectiveness Check
    • Overview: the issue is locked, users will only be able to edit some fields on the details tab, add attachments, update custom fields, or log comments
    • Purpose: Effectiveness Check assignees can confirm that the issue's root cause analysis was correct and that the Actions will effectively prevent future issues
    • Next steps: The effectiveness check users will need to sign
  2. Effective
    • Overview: the issue is locked, users will only be able to log comments
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.