These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Data Center Management
- Features
- Changes and windows
Changes and windows
Review service changes with risk, scheduled start and end, and a rollback plan.
OverviewChange review×
Data Center Management · Changes and windows
New
Change review
Approval waits for the change manager
| Summary | Risk | Scheduled start | Scheduled end | Rollback plan | Service | |
|---|---|---|---|---|---|---|
| SMM-143 | Low | 16 Oct | 18 Oct | RP-232 | SRV-2902 | |
| SMM-552 | Medium | 04 Oct | 08 Oct | RP-175 | SRV-3255 | |
| SMM-170 | High | 15 Oct | 20 Oct | RP-865 | SRV-9263 | |
| SMM-869 | Low | 27 Oct | 03 Nov | RP-725 | SRV-5422 | |
| SMM-646 | Medium | 14 Oct | 17 Oct | RP-906 | SRV-4598 |
6 of 6 records
SMM-143Changes · CHN-50236
LowScheduled start16 Oct
Scheduled end18 Oct
Rollback planRP-232
ServiceSRV-2902
What you can do
Make planned work reviewable
A change names the affected service and describes the proposed work. Its risk, scheduled start and end, rollback plan and state let the Change Manager decide whether the work is ready to proceed. A draft can be prepared before the team has chosen a window. Review is the point where those controls must be present. When risk, both ends of the window and rollback instructions are recorded, eligible work can move to approved. An incomplete entry stays in review.
The window should describe when technicians expect to perform the work. It is not a substitute for their actual incident or rack and cable observations. Keep the change summary plain enough for the service owner to understand what will happen and the rollback text specific enough for the technician to use if the change must be reversed.
How the work is organized
The Change Manager reviews the plan; the Service Manager checks the effect on the service; the Service Technician carries out approved work.
- Risk and service. The risk choice belongs to a named service change.
- Scheduled window. A start and end date make planned work visible in the schedule.
- Rollback instruction. The plan states how the team will respond if implementation fails.
What to agree during setup
Agree who prepares the change and who checks its risk before it enters review. Decide the minimum useful rollback detail for routine and high-risk work. Set a convention for scheduled dates and what happens if the window moves. Rehearse one complete review and one with a missing control. Decide who marks implementation, verification, rejection or rollback after work is observed.
Check the handoff on an actual case
A technician proposes moving a service asset during a maintenance window. The Change Manager reads the service, summary and risk, checks the scheduled start and end, and reads the rollback plan. With those controls recorded, the change can become approved. The technician then starts implementation in the agreed window. If the work fails, the team follows the recorded rollback plan and marks the change rolled back; if it succeeds, verification captures the outcome.
Now remove the rollback plan from a second review. It must stay in review. The manager can then ask for a workable plan before the physical work is scheduled. This check prevents a status change from standing in for a real plan.
What your team sees
- Change review — Entries awaiting a complete risk, window and rollback review.
- Change schedule — Approved and implementing work with start and end dates.
- Change board — The status of planned work across the service portfolio.
Follow the work through
What it keeps track of
Data model- Changes
- Changes for data center operations.
- Services
- Services for data center operations.
- Assets
- Assets for data center operations.
Who uses it
Permissions- Change Manager
- , Service Manager, Service Technician.
- The manager checks the plan; the technician follows the approved window.
Set up Data Center Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.