| h3. *CIT STANDARD OPERATING PROCEDURE* |
h4. {color:#000000}{*}New User Account Request LAMP Service{*}{color}
{color:#000000}Procedure Number: SOP 2010-LA001{color}
Related Processes and Procedures:
\\
DRP 20yy-000 Disaster Recovery Procedure Template
\\ {color:#0066ff}(None at this time, didn't know if we'd need to link this to a DR procedure later on).{color}
*Revision History*
| Date | Author | Version | Description |
| 3/11/2010 | ajl44 | 0.0 | New Document |
| | | | |
| | | 0.9 | Final Draft |
| | | 1.0 | Approved Document |
| | | | |
h3. BACKGROUND AND PURPOSE
{color:#777777}Procedure identifies the processes used to complete a CIT LAMP Hosting Service request for a new customer account.{color}
h3. SERVICES
{color:#777777}CIT Hosting Services{color}
|| *Included Service* || *Service Owner* || *Service Manager* || *Service Dependencies* ||
| LAMP | Donna Taber | Jon Atherton | Service Support Team, DBA |
h3. 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).
h3. CARD (Contingencies, Assumptions, Requirements, Dependencies)
{color:#777777}(Indicate contingencies, assumptions, requirements and dependencies not indicated elsewhere which are required for execution of this procedure.){color}
{color:#0066ff}Any relevant Contingencies, Assumptions, Requirements or Dependencies should be included.{color}
* {color:#0066ff}Contingencies describe "what if" scenarios and how to accommodate them.{color}
* {color:#0066ff}Assumptions are things which are presumed to be valid or true. Many assumptions will have a risk related to them.{color}
* {color:#0066ff}Requirements are items which are necessary in order to successfully execute this procedure.{color}
* {color:#0066ff}Dependencies are related items which depend on this procedure. Alternatively, the converse may also be relevant.{color}
{color:#0066ff}(If this section is not required, indicate "Not Applicable" rather than removing this section from the document).{color}
h3. TASK DESCRIPTION
{color:#777777}Provide a description of the individual tasks which constitute the SOP.{color}
|| *Task Number* || *Task Description* || *Responsible Party* ||
| 1. |
{visio:file=LAMP.vsd}
. | Various |
h3. 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._*
h3. Approvals
|| *Name* || *Function* || *Comments* || *Signature* || *Date* ||
| | Director | | | |
| | Service Owner | | | |
| | Service Manager | | | |
h3. Appendix A: References
{color:#0066ff}[LAMP:The CIT Hosting Service Community]{color} |