Service Operations Baseline - Transition Checklist
Service Operations Baseline is introduced in SA2 operations tasks in the beginning of GN4-2. The aim of Service Operations Baseline is to ensure that service operations are performed with satisfying quality. This page contains Service Operations Baseline checklist that accompanies the transition process, and must be completed by the end of it.
| Content provided by | Signed off by | |||||
Responsible team | Development (JRA3) | Operations (SA2/T2|T3) | Visibility (NA) | Development (JRA3) | Test and validation (SA2/T1)1 | Operations (SA2/T2|T3)2 | Support |
Person responsible to edit checklist | |||||||
Service Definition | |||||||
BSD1 Service Description | ON HOLD |
|
|
| ON HOLD |
|
|
BSD2 Service Policy | ON HOLD |
|
|
| ON HOLD |
|
|
BSD3 Branding and Visibility | ON HOLD |
| ON HOLD | ON HOLD |
|
| |
Service Operations | |||||||
BSO1 Operational Requirements | ON HOLD |
|
|
| ON HOLD | ON HOLD |
|
BSO2 OLA |
| ON HOLD |
| ON HOLD |
| ON HOLD |
|
BSO3 Operational Documentation | ON HOLD |
|
|
| ON HOLD | ON HOLD |
|
BSO4 Operational Processes | ON HOLD |
|
|
|
| ON HOLD |
|
Service Support | |||||||
BSS1 User Documentation | ON HOLD |
|
|
| ON HOLD |
|
|
BSS2 User Support | ON HOLD |
|
|
| ON HOLD | ON HOLD | ON HOLD |
1 Sign off after test and validation.
2 Sign off after implementation in production.
Appropriate status can be pasted from here:
ON HOLD INITIATED N/A PREPARED
APPROVED REJECTED
Typical change of states for "Content provided by"
Typical change of states for "Signed off by"
