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
- Incident to problem
Incident to problem
Respond to service impact and record a longer root cause investigation.
Step by step
-
Open the incident Incident Responder
Incident Responder records the summary, service, asset, priority and opened date. The assignee makes immediate responsibility clear.
- Affected equipment and service named
- Updates Incidents, Assets, Services
-
Acknowledge and investigate Incident Responder
The responder records acknowledgment and investigation progress. Dated updates carry the author and the action taken.
- Response history recorded
- Updates Incidents, Incident updates
-
Resolve the disruption Incident Responder
Incident Responder records the resolution date and moves the incident to Resolved when service has been restored. Service Owner reviews the outcome before Closed.
- Immediate outcome dated
- Updates Incidents
-
Open a problem Problem Analyst
Problem Analyst records a problem statement and names an owner when the cause needs longer investigation.
- Longer investigation assigned
- Updates Problems, Services
-
Document the cause Problem Analyst
Problem Analyst moves the problem through investigation, records a known error where appropriate and writes the root cause before resolution.
- Cause recorded for review
- Updates Problems
Who does what
Roles and permissions- Incident Responder
- , Service Owner, Problem Analyst, Patch Operator.
Set up Patch Management System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.