*** This version of Confluence is for testing only and contains a copy of content from June 29th 2026. No changes will be preserved. ***
-
Created by
user-ef11d, last updated on May 06, 2011
2 minute read
CIT STANDARD OPERATING PROCEDURE
Monthly review of Hosting rebill activity
Procedure Number: |
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 |
4/27/10 |
jca8 |
0.0 |
New Document |
5/6/11 |
jca8 |
0.9 |
Final Draft |
|
|
1.0 |
Approved Document |
|
|
|
|
BACKGROUND AND PURPOSE
The purpose of this document is to describe the procedure for monthly review of re-bill activity for the hosting environments. This review is important in order to insure customers are billed appropriately.
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. (This is a required section for this document.)
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?)Monthly review and validation of Hosting re-bill activity as part of the monthly billing process.
CARD (Contingencies, Assumptions, Requirements, Dependencies)
(Indicate contingencies, assumptions, requirements and dependencies not indicated elsewhere which are required for execution of this procedure.)
- Assumptions: Working knowledge of Remedy
- Requirements: Remedy
- Dependencies: Monthly billing process
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. |
Generate report from Remedy ISIS queue |
yc115 |
1.1 |
Assign billable hours |
yc115 |
1.2 |
Export to spreadsheet |
yc115 |
1.3. |
Send spreadsheet to jca8 |
yc115 |
2 |
Look up incident in Remedy and assign customer number to each billable entry |
jca8 |
2.1 |
Confirm Customer id by name look-up |
jca8 |
2.2 |
Save report and send to Sandi |
jca8 |
|
|
|
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.)
ISIS Team Lead (yc115)
Hosting service manager (jca8)
APPENDICES and ATTACHMENTS follow the approval block.
Approvals
Name |
Function |
Comments |
Signature |
Date |
|---|---|---|---|---|
|
Director |
|
|
|
|
Service Owner |
|
|
|
Jon Atherton |
Service Manager |
|
Jon Atherton |
5/6/11 |
(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.)