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.
- Status Page System
- Data model
The tables behind Status Page System
Status Page 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
Service foundation
Services name ownership and criticality; public components carry visible status and order; Assets provide an affected item and location.
Incident communication
Incidents hold assignment and recovery dates. Incident updates hold attributed working notes. Public updates hold audience, approver and publication time.
Planned and requested work
Changes carry risk, dates and rollback plan. Service requests carry requester, due date and completion. Problems carry owner and root cause.
Connector evidence
Integration receipts retain provider event identifiers and outcomes. People link operational responsibilities to Users.
Every table, by feature
- Services and components4
- Incidents5
- Public communication5
- Changes and maintenance4
- Requests and problems5
- Assets and receipts4
- Shared and settings1
- Services
Services for service operations and status communications.
Linked to People - Public components
Public Components for service operations and status communications.
Linked to Services - Incidents
Incidents for service operations and status communications.
Linked to Services, Assets, People - Changes
Changes for service operations and status communications.
Linked to Services
- Incidents
Incidents for service operations and status communications.
Linked to Services, Assets, People - Incident updates
Incident Updates for service operations and status communications.
Linked to Incidents, People - Services
Services for service operations and status communications.
Linked to People - Assets
Assets for service operations and status communications.
Linked to Services - People
People for service operations and status communications.
Linked to Users
- Public updates
Public Updates for service operations and status communications.
Linked to Incidents, People - Incident updates
Incident Updates for service operations and status communications.
Linked to Incidents, People - Incidents
Incidents for service operations and status communications.
Linked to Services, Assets, People - Public components
Public Components for service operations and status communications.
Linked to Services - People
People for service operations and status communications.
Linked to Users
- Changes
Changes for service operations and status communications.
Linked to Services - Services
Services for service operations and status communications.
Linked to People - Public components
Public Components for service operations and status communications.
Linked to Services - Incidents
Incidents for service operations and status communications.
Linked to Services, Assets, People
- Service requests
Service Requests for service operations and status communications.
Linked to People, Services - Problems
Problems for service operations and status communications.
Linked to Services, People - Services
Services for service operations and status communications.
Linked to People - People
People for service operations and status communications.
Linked to Users - Incidents
Incidents for service operations and status communications.
Linked to Services, Assets, People
- Assets
Assets for service operations and status communications.
Linked to Services - Integration receipts
Integration Receipts for service operations and status communications.
- Incidents
Incidents for service operations and status communications.
Linked to Services, Assets, People - Services
Services for service operations and status communications.
Linked to People
Keys and references
A service is the common reference for assets, changes, incidents, problems, components and requests. An incident can reference an asset and an assigned person. Incident updates and public updates reference incidents; their author or approver references People. Keep those links intact when importing history. The Users self-reference is part of the published schema; review it before importing identities.
Migration order
- Import Users and People, then assign service owners.
- Create Services and their public components; load Assets against the correct service.
- Import Incidents and related incident updates and public updates.
- Add Changes, service requests and Problems after their service references exist.
- Load integration receipts with provider identifiers and original received times.
Set up Status Page System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.