Significant Incident Automation
The process for significant incidents was able to be significantly improved with the adoption of Slack and BlueJeans by ITS. In order to improve the coordination and responsiveness, a portion of the manual work has been eliminated through automation.
QRCode
Group Members:
Joseph Lisi
Scan here to contact us!
(Any essential images. If you don’t have any, you can leave the space blank, or include a photo of the group working.)
More photo/picture/graphic space.
(You can change the colors of this design, but make sure the contrast between the text and background is enough that everyone can see and read easily. Use the same color for the section headers and main title. Keep the background gray and white)
Problem
The significant incident process was unreliable and in need of improvement. Zapier, a third party application that handled some of the automation, was not consistently working properly. Recent significant incidents were not as smooth as they could have been.
Methods
Results
This integration allows a portion of the process be done instantly via the click of a button.
The nature of the significant incident process is hectic and stressful. The automated process this will create more ease.
I developed a deep understanding of this process and gained a sense of the importance behind it.
The methods used to solve this problem
The automated process