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
- Who it's for
- Distributed service teams
Distributed service teams
A service may depend on assets in different locations. Asset tags, serial numbers and locations help a distributed team identify the intended equipment before a patch attempt starts. The service link lets the Service Owner review those assets together. A change window gives the team an agreed time for work, while each attempt records the actual start, completion and outcome for its asset.
How Patch Management System is set up for you
Location check
Confirm the asset tag and location before scheduling work for an operator.
Shared service context
Review service criticality and ownership when timing work at different sites.
Local outcome
Keep failed and rolled back attempts distinct from verified results elsewhere.
A service may depend on assets in different locations. Asset tags, serial numbers and locations help a distributed team identify the intended equipment before a patch attempt starts. The service link lets the Service Owner review those assets together. A change window gives the team an agreed time for work, while each attempt records the actual start, completion and outcome for its asset.
Select one service with assets at two locations. Confirm that each asset has a unique recognizable tag and the correct service reference. Add the intended patch release and have the Change Manager review its risk, planned timing and rollback plan. The Patch Operator records a separate attempt for each asset. Compare the actual start and completion dates with the scheduled window and review any difference at the handoff.
Make one attempt Verified and another Failed during the rehearsal. The Service Owner should see the mixed result and decide what follow-up is needed. If the failed installation disrupted the service, open an incident for the specific asset and record the response. A later problem investigation can document the root cause without changing the original attempt outcome. Expand to more locations once asset selection and service ownership are reliable.
[Review asset records](/patch-management-system/modules/assets-and-services) and [prepare a rehearsal](/patch-management-system/processes/patch-planning-to-verification).
Features to start with
Roles on the team
- Patch Operator
- Records asset-specific patch attempts and their outcomes.
- Change Manager
- Reviews service change risk, timing and rollback plans.
- Service Owner
- Reviews service impact and responds to service interruptions.
- Incident Responder
- Investigates active incidents and adds dated updates.
Set up Patch Management System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.