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.
- IT Service + Asset + Knowledge
- Data model
The tables behind IT Service + Asset + Knowledge
IT Service + Asset + Knowledge 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
Service context
Services and People identify the owner and the operation affected.
Response and requests
Incidents, incident updates and service requests record intake, decisions and work.
Planned and recurring work
Changes and Problems hold the planned window or underlying cause.
Equipment and guidance
Assets, asset service links and knowledge articles connect equipment and reviewed knowledge to services.
External evidence
Integration receipts retain provider events and their processing status.
Every table, by feature
- Incidents
Incidents operational records
Linked to Services, Assets, People - Incident updates
Incident Updates operational records
Linked to Incidents, People - Services
Services operational records
Linked to People - Assets
Assets operational records
Linked to Services - People
People operational records
Linked to Users
- Service requests
Service Requests operational records
Linked to People, Services - People
People operational records
Linked to Users - Services
Services operational records
Linked to People
- Changes
Changes operational records
Linked to Services - Services
Services operational records
Linked to People
- Assets
Assets operational records
Linked to Services - Asset service links
Asset Service Links operational records
Linked to Assets, Services - Services
Services operational records
Linked to People - Incidents
Incidents operational records
Linked to Services, Assets, People
- Problems
Problems operational records
Linked to Services, People - Services
Services operational records
Linked to People - People
People operational records
Linked to Users - Incidents
Incidents operational records
Linked to Services, Assets, People - Knowledge articles
Knowledge Articles operational records
Linked to Services
- Knowledge articles
Knowledge Articles operational records
Linked to Services - Services
Services operational records
Linked to People - Problems
Problems operational records
Linked to Services, People - Incidents
Incidents operational records
Linked to Services, Assets, People - Incident updates
Incident Updates operational records
Linked to Incidents, People
Keys and references
Most operational records carry an auto-generated ID. A service has an owner in People; an asset has a service; an incident points to a service, asset and assignee. An incident update points to its incident and author. A request points to a requester and service. A change, problem and article each reference a service. Asset service links connects an asset with a service and records its dependency type and verification date. People links to Users for sign-in context.
Migration order
- Users and People. Establish identities and the people who will own work.
- Services. Add service names, criticality, status and owners.
- Assets and asset service links. Import equipment and verify service dependencies.
- Operational work. Bring in Incidents, incident updates, service requests, Changes and Problems with their references.
- Guidance and receipts. Add knowledge articles and integration receipts after their source context is clear.
Set up IT Service + Asset + Knowledge your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.