Process step | Description | Time frame |
---|---|---|
New | Change initiator has entered a request. | |
Added to backlog | Change request has been added to the backlog of Technology Services and will be evaluated based on priority. | |
|
| |
| Release/version has been established, but work still needs to be started and a resource assigned. | |
Blocked | Change request is currently blocked and work has stopped. | |
Implementing | Development, testing, and documentation is being completed. | |
Awaiting deployment approval | Work has been completed and tested, but waiting for deployment to production system. | |
Scheduled | ||
Released | ||
Closed | Performance targets have been met and change initiator has accepted the change. | |
Waiting for customer | Request is waiting on the response from a customer. | |
Waiting for support | Request is waiting for support through the Service Desk. | |
No response | The customer does not respond with 60 hours of the issue (following the same calendar as the SSD Technology Department) then an issue will move into a No response status. | 60 hrs. |
Pending closure | The customer does not respond with 30 hours of the issue (following the same calendar as the SSD Technology Department) then an issue will move into a Pending Closure status. | 30 hrs. |
...