*** 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
...
2010-GE001
Related Processes and Procedures:
DRP 20yy-000 Disaster Recovery Procedure Template
(
...
None at this time, didn't know if we'd need to link this to a DR procedure later on).
All text in "blue" should be removed from this document prior to release as final draft.
Revision History
Date | Author | Version | Description | ||
3/9/2010 | ajl44 |
|
| 0.0 | New Document |
|
|
|
| ||
|
| 0.9 | Final Draft | ||
|
| 1.0 | Approved Document | ||
|
|
|
|
BACKGROUND AND PURPOSE
(Provide any applicable background information and purpose of this document. For example, what are we trying to accomplish?)
Provide background material and purpose in this section. What is actually being recovered?
(If this section is not required, indicate "Not Applicable" rather than removing this section from the document).
SERVICES
(Specifically what services are covered within this procedure? What other services do these services depend on?)
CIT Hosting Service customers need timely information regarding unplanned outages. In addition, responsible CIT departments must be notified. Status updates must be provided until outages are resolved.
SERVICES
CIT Hosting Services
Use cit-hosting@cornell.edu as the sender when sending to the customer e-Lists.Services included within the scope of this document are indicated below: The Service Owner, Service Manager and services the included services depend on are also listed. (This is a required section for this document.)
Included Service | Service Owner | Service Manager | Customer e-List | Service Dependencies | |||
|---|---|---|---|---|---|---|---|
CommonSpot | Donna Taber | Nathan Reimer | cit-cms-hosting-l@cornell.edu |
| |||
ColdFusion | Donna Taber | Nathan Reimer | coldfusion-hosting-l@cornell.edu |
| |||
LAMP |
|
| |||||
|
|
|
| ||||
Donna Taber | Jon Atherton | cit-lamp-hosting-l@cornell.edu |
| ||||
Static | Donna Taber | Jon Atherton | staticwebhosting-l@cornell.edu |
| |||
uPortal/myCornell | Donna Taber | Jon Atherton | portal-hosting-l@cornell.edu |
|
| |
|
SCOPE
(What is in scope and what is not in scope for this procedure?)
Describe the situation or problem or specific deliverables applicable to this standard operating procedure.
In Scope:
- Details the steps necessary to communicate outages to CIT Hosting customers.
- Identifies the roles and responsibilities of CIT staff, regardless of reporting structure, necessary to communicate outages to CIT Hosting customers.
Out of Scope:
- Does not identify methods, steps or resources needed to resolve the outage issue.
...
CARD (Contingencies, Assumptions, Requirements, Dependencies)
(Indicate contingencies, assumptions, requirements and dependencies not indicated elsewhere which are required for execution of this procedure.)
Any relevant Contingencies, Assumptions, Requirements or Dependencies should be included.
- Contingencies describe "what if" scenarios and how to accommodate them.
- Assumptions are things which are presumed to be valid or true. Many assumptions will have a risk related to them.
- Requirements are items which are necessary in order to successfully execute this procedure.
- Dependencies are related items which depend on this procedure. Alternatively, the converse may also be relevant.
(If this section is not required, indicate "Not Applicable" rather than removing this section from the document).
TASK DESCRIPTION
Provide a description of the individual tasks which constitute the SOP. Flow chart diagrams may be included for clarity.)
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. |
|
|
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.)
...
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 |
3 | | Various |
PEOPLE
Title | Role |
|---|---|
Service Owner | Point of escalation for major incidents. |
Service Owner | Developing and executing the Service's outage communications plan. Executing the outage communications plan may be delegated. |
Service Manager | Responsible for internal planned outage communications. May be responsible for external planned outage communications. |
Service Support Team | Provide timely outage status updates |
NOC | Provide internal communications support. |
APPENDICES and ATTACHMENTS follow the approval block.
...
Name | Function | Comments | Signature | Date |
|---|---|---|---|---|
| Director |
|
|
|
| Service Owner |
|
|
|
| Service Manager |
|
|
|
Appendix A:
...
References
Communicating Unplanned Outages and Service Interruptions
Include any material for Appendix A as referenced in the main document.
(If this Appendix is not required, remove this appendix from the document).
Appendix B: Second Appendix
Include any material for Appendix B as referenced in the main document.
Add additional appendices, as required.
(If this Appendix is not required, remove this appendix from the document).
(Add any attachments that may have been too large to include in the main text portion of this document. Label as Attachment 1, Attachment 2, etc.)