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
- Data model
The tables behind Patch Management System
Patch Management System ships with 12 tables, grouped here by the feature that uses them. Every record your team works with lives in one of them, and you can add fields and tables in Proto.
- Tables
- 12
- Features
- 6, plus shared settings
- Change it
- Add fields and tables in Proto
How the model is organised
Patch identity and execution
Patch catalog identifies the release; patch attempts connects it to Assets and records the outcome.
Service planning
Services holds the service context; Changes records risk, window, rollback plan and decision.
Service response
Incidents points to the affected Service and Asset; incident updates adds dated response; Problems carries longer cause investigation.
Intake and people
Service requests links requesters to Services, integration receipts records event intake, and People links staff to Users.
Every table, by feature
- Patch catalog3
- Patch attempts5
- Changes5
- Assets and services5
- Incidents and problems6
- Requests and receipts6
- Shared and settings1
- Patch catalog
Patch Catalog for patch planning and service operations.
- Patch attempts
Patch Attempts for patch planning and service operations.
Linked to Assets, Patch catalog - Assets
Assets for patch planning and service operations.
Linked to Services
- Patch attempts
Patch Attempts for patch planning and service operations.
Linked to Assets, Patch catalog - Patch catalog
Patch Catalog for patch planning and service operations.
- Assets
Assets for patch planning and service operations.
Linked to Services - Changes
Changes for patch planning and service operations.
Linked to Services - Incidents
Incidents for patch planning and service operations.
Linked to Services, Assets, People
- Changes
Changes for patch planning and service operations.
Linked to Services - Services
Services for patch planning and service operations.
Linked to People - Assets
Assets for patch planning and service operations.
Linked to Services - Patch attempts
Patch Attempts for patch planning and service operations.
Linked to Assets, Patch catalog - Incidents
Incidents for patch planning and service operations.
Linked to Services, Assets, People
- Assets
Assets for patch planning and service operations.
Linked to Services - Services
Services for patch planning and service operations.
Linked to People - Patch attempts
Patch Attempts for patch planning and service operations.
Linked to Assets, Patch catalog - Changes
Changes for patch planning and service operations.
Linked to Services - Incidents
Incidents for patch planning and service operations.
Linked to Services, Assets, People
- Incidents
Incidents for patch planning and service operations.
Linked to Services, Assets, People - Incident updates
Incident Updates for patch planning and service operations.
Linked to Incidents, People - Problems
Problems for patch planning and service operations.
Linked to Services, People - Services
Services for patch planning and service operations.
Linked to People - Assets
Assets for patch planning and service operations.
Linked to Services - Patch attempts
Patch Attempts for patch planning and service operations.
Linked to Assets, Patch catalog
- Service requests
Service Requests for patch planning and service operations.
Linked to People, Services - Integration receipts
Integration Receipts for patch planning and service operations.
- People
People for patch planning and service operations.
Linked to Users - Services
Services for patch planning and service operations.
Linked to People - Changes
Changes for patch planning and service operations.
Linked to Services - Patch attempts
Patch Attempts for patch planning and service operations.
Linked to Assets, Patch catalog
Keys and references
Keep asset tag and patch ID stable when importing active records. Each attempt must reference one Asset and one patch catalog entry. Each Asset references a Service. A Change references a Service, while an Incident references both Service and Asset. Compare change plans and requests with attempt outcomes by service and asset. Review event receipts by provider and external event ID as a separate intake record.
Migration order
- Bring in Users and People so ownership and authorship can be assigned.
- Add Services and their owners, then Assets with the correct service links.
- Add patch catalog releases and check their product, version and severity.
- Bring in open Changes and service requests, then asset-specific patch attempts.
- Bring in Incidents, incident updates, Problems and integration receipts with their source identifiers.
Set up Patch Management System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.