CIT STANDARD OPERATING PROCEDURE |
New User Account Request
...
LAMP Service
Procedure Number:
...
SOP
...
2010-
...
LA001
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/11/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?)
Procedure identifies the processes used to complete a CIT LAMP Hosting Service request for a new customer account.
SERVICES
CIT Hosting ServicesServices 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 | Service Dependencies |
|---|---|---|---|
LAMP | Donna Taber |
|
|
|
|
|
|
|
|
|
|
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.
...
Jon Atherton | Service Support Team, DBA |
SCOPE
In Scope:
- Details the steps necessary to create a new LAMP Hosting Service account.
- Identifies the roles and responsibilities of CIT staff, regardless of reporting structure, necessary to create a new LAMP Hosting Service account.
Out of Scope:
- Does not identify methods, steps or resources used by the Service Support Team or Database Administrator (DBA).
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.)
...
. | Various |
PEOPLE
Title | Role |
|---|---|
Director | Service Delivery goals. |
Service Owner | Drive the Service Delivery goals. |
Service Owner | Negotiating SLAs; OLAs for the Service. |
Service Manager | In partnership with the Serivce Delivery Owner, drives the Service Delivery goals. |
Service Manager | Accountable for the daily operation of the Service; may directly respond to service operation needs of Customers. |
Service Support Team | Works with other Service Support Team members to achieve defined Service Delivery goals. |
All | Responsible for expected (or guaranteed) availability of the Service and responsible for the quality of Service Delivery. |
APPENDICES and ATTACHMENTS follow the approval block.
...
Name | Function | Comments | Signature | Date |
|---|---|---|---|---|
| Director |
|
|
|
| Service Owner |
|
|
|
| Service Manager |
|
|
|
Appendix A:
...
References
The CIT Hosting Service Community
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.)