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.
- Patch Management System
- Process
- Change review
Change review
Make a service change decision from risk, timing and rollback context.
Step by step
-
Draft the change Change Manager
Change Manager records a summary and affected service. Risk, scheduled start and end, and rollback plan make the intended work reviewable.
- Planned work scoped
- Updates Changes, Services
-
Submit for review Change Manager
The change moves from Draft to Review when the planned work and recovery approach are ready for the Service Owner.
- Review state recorded
- Updates Changes
-
Decide Change Manager
Change Manager reviews the service impact with Service Owner and records Approved or Rejected. The decision should reflect the stated window and rollback plan.
- Approval or rejection recorded
- Updates Changes, Services
ApprovalA person approves before the work moves on. -
Implement Patch Operator
Patch Operator carries out asset-specific attempts during the approved work. Change Manager marks the change Implementing as execution begins.
- Execution recorded per asset
- Updates Patch attempts, Assets, Changes
-
Review the result Change Manager
Compare attempt results and any incident with the intended change. Mark the change Verified when the result supports it, or rolled back when recovery was used.
- Service change outcome reviewed
- Updates Patch attempts, Changes, Incidents
Who does what
Roles and permissions- Change Manager
- , Service Owner, Patch Operator, Incident Responder.
Set up Patch Management System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.