*** This version of Confluence is for testing only and contains a copy of content from June 29th 2026. No changes will be preserved. ***
CIT STANDARD OPERATING PROCEDURE |
Communication Unplanned Outages *
| Procedure Number:
SOP 20yy-000
"yy" is the year | Related Processes and Procedures:
DRP 20yy-000 Disaster Recovery Procedure Template
(Remove the above reference and include any Disaster Recovery, Standard Operating or other procedures related to the procedure documented herein). |
All text in "blue" should be removed from this document prior to release as final draft.
...
Task Number | Task Description | Responsible Party |
|---|---|---|
1. | Provide a description of each task and the individual or functional unit responsible for executing this task. |
|
1.1. | Flow charts or other diagrams may be included. |
|
2. |
|
| 3. |
|
Report all incidents to the NOC every time (call 255-9900). Don't assume someone else will be doing this! | Service Owner/Service Support Team | |
1.1 | Update the NOC regularly to keep them in the loop. Tier one services require hourly updates. | Service Owner/Service Support Team |
1.2 | Once resolved, provide outcome information to the NOC; include what happened and how you fixed it. | Service Owner/Service Support Team |
2. | Engage the service owner/service support team (if not already confirmed to be involved). | NOC |
2.1 | Provide internal communications support. | NOC |
2.2 | Update the CIT status page.| NOC |
2.3 | Involve Communication & Outreach when necessary.| NOC |
PEOPLE
(Indicate functional units, titles of individuals who are both responsible and accountable for this SOP. If applicable, indicate skill sets required to execute the SOP in the event that the assigned individuals are not in a capacity to do so.)
...