Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

CIT STANDARD OPERATING PROCEDURE


Annual Hosting Renewals

Procedure Number:
SOP 2011-000

Related Processes and Procedures:

All text in "blue" should be removed from this document prior to release as final draft.




Revision History

Date

Author

Version

Description  

5/6/11

Jon Atherton

0.0

New Document

 

 

 

 

5/6/11

Jon Atherton

 

 

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?)

All hosting customers must renew annually in order to update their billing account number and update contact information.

SERVICES

(Specifically what services are covered within this procedure? What other services do these services depend on?)

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.

Included Service

Service Owner

Service Manager

Service Dependencies

LAMP Hosting

Donna Taber

Jon Atherton

 

Static Web Hosting

Donna Taber

Jon Atherton

 

ColdFusion Hosting

Donna Taber

Nate Reimer

 

CommonSpot Hosting

Donna Taber

Nate Reimer

 

Portal Hosting

Donna Taber

Jon Atherton

 


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.

(This is a required section for this document.)

Each hosting customer must update contact information and account number at the fiscal year boundary.

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)Assumption: We will continue to bill for custom support and CommonSpot, otherwise an account number would not be necessary.

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.

Send "Renewal coming soon" email to lists

Hosting service manager  

1.1.   

Flow charts or other diagrams may be included.

Send Renewal Notice to each customer beginning late June

Hosting Service Manager  

2.           

Generate report and follow up with those who haven't renewed

Hosting Service Managers

   

 

 

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.)Roles and responsibilities should be included in this section. Accountable individual or functional group for this standard operating procedure should be indicated. In the event that individuals or functional units specified cannot perform their function as described in this procedure, what skill sets would be required to perform the standard operating procedure?

Hosting Service Managers


APPENDICES and ATTACHMENTS follow the approval block.

...

Name

Function

Comments

Signature

Date

 

Director

 

 

 

 

Service Owner

 

 

  

Jon Atherton

Service Manager

 

 

 

Appendix A: First Appendix

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).

 

...

Jon Atherton

5/6/11