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.
- Data Center Management
- Data model and import order
The tables behind Data Center Management
Data Center Management 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
- 7, plus shared settings
- Change it
- Add fields and tables in Proto
How the model is organised
Service and asset context:
Services, People, Assets. The service owner and equipment record anchor operating work.
Rack and cable evidence:
Rack positions link to Assets; cable connections link to Incidents.
Response:
Incidents link to Services, Assets and People; incident updates link to Incidents and their authors.
Planned and requested work:
Changes and service requests each link to Services; requests also link to a requester.
Follow-up and events:
Problems link to Services and owners; integration receipts keep event identity and processing outcome.
Every table, by feature
- Service and asset context5
- Rack space and power3
- Cable connections4
- Incident response6
- Changes and windows3
- Requests and fulfillment3
- Problems and receipts5
- Shared and settings1
- Services
Services for data center operations.
Linked to People - Assets
Assets for data center operations.
Linked to Services - People
People for data center operations.
Linked to Users - Incidents
Incidents for data center operations.
Linked to Services, Assets, People - Rack positions
Rack Positions for data center operations.
Linked to Assets
- Rack positions
Rack Positions for data center operations.
Linked to Assets - Assets
Assets for data center operations.
Linked to Services - Services
Services for data center operations.
Linked to People
- Cable connections
Cable Connections for data center operations.
Linked to Incidents - Incidents
Incidents for data center operations.
Linked to Services, Assets, People - Assets
Assets for data center operations.
Linked to Services - Services
Services for data center operations.
Linked to People
- Incidents
Incidents for data center operations.
Linked to Services, Assets, People - Incident updates
Incident Updates for data center operations.
Linked to Incidents, People - Services
Services for data center operations.
Linked to People - Assets
Assets for data center operations.
Linked to Services - People
People for data center operations.
Linked to Users - Cable connections
Cable Connections for data center operations.
Linked to Incidents
- Changes
Changes for data center operations.
Linked to Services - Services
Services for data center operations.
Linked to People - Assets
Assets for data center operations.
Linked to Services
- Service requests
Service Requests for data center operations.
Linked to People, Services - Services
Services for data center operations.
Linked to People - People
People for data center operations.
Linked to Users
- Problems
Problems for data center operations.
Linked to Services, People - Services
Services for data center operations.
Linked to People - People
People for data center operations.
Linked to Users - Integration receipts
Integration Receipts for data center operations.
- Incidents
Incidents for data center operations.
Linked to Services, Assets, People
Keys and references
Preserve the asset tag and cable identity from physical labels. Link an incident to the affected service and asset, then link its updates and cable work to that incident. A rack position uses its asset reference. Keep the external event identity with its provider when importing receipts, and reconcile repeat deliveries before applying them.
A person’s app identity is represented through People and Users. Confirm those links before assigning incidents or requests. Avoid matching a service or asset by display text alone when a stable reference is available.
Migration order
- Load Users and People, then confirm active people and service ownership.
- Load Services and Assets with stable tags, serial numbers and locations.
- Load rack positions against assets and verify rack codes and measured values.
- Load Incidents and linked incident updates; then load cable connections against incidents.
- Load Changes, service requests, Problems and integration receipts; compare source identities and status values.
- Rehearse access, review decisions and rejected physical observations before opening routine work.
Set up Data Center Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.