Action Items, Root Cause Analysis, Jumpers
- Edward Barrier (Unlicensed)
In this example.
maddison’s role: Process Engineer
ebarrier’s role: Supervisor
Dan Stoller: Maintenance
Create a new jumper ticket.
2. Save it and change the status to open. This will now send an email to a supervisor (In this case ebarrier) that a new ticket has been created and they will look over it and accept or deny it.
3. The supervisor (ebarrier) can view the ticket and choose to approve or deny the request.
4. Once approved, the ticket is now active.
5. Action items can be added to the ticket that shows the work that needs to be done and assign it to whoever needs to do it. Manager groups will recieve emails when new action items are added. Maintenance (Dan) has been assigned to go look at what’s wrong with the switch.
6. Maintenance (Dan) can now go into the ticket and request to complete this action item and create a new action item for the next step. Maintenance (Dan) added an action item to order a new switch.
7. This process can continue until the job is complete.
8. The switch is now fixed and installed. A picture has been uploaded to the ticket, and all action items can be completed.
9. If the ticket is fully completed. Select Save and change status to closed. Manager groups will receive emails whenever this ticket is almost to its due date, when it’s overdue, and when it’s seven days past overdue date.
10. The ticket is now in “Completed” but can be re-opened in the future if needed.