Skip to content

IT / Security — Service Catalog & Ownership Registry

A service catalog with owners and criticality helps incident response and AI ops without requiring a full CMDB program.

Why this is needed

  • Outages stall while people hunt Confluence for owners.
  • Criticality is debated every incident.
  • Links cleanly to Organizational Capability Registry.

Proposed entities in EntiHub

Governance settings

Setting Recommended value Why
approvalRequired true Ownership/criticality changes are controlled.
historyEnabled true History of ownership transfers.
allowSameAuthorApproval false Maker/checker separation for sensitive changes.
deletedRetentionDays 90 (or higher) Soft-delete retention for auditability.

Entity definition (YAML sketch)

name: it_service
displayName: IT service
domain: IT
description: IT service
version: "1.0.0"
approvalRequired: true
historyEnabled: true
deletedRetentionDays: 90
displayRefColumn: service_code
uniqueConstraints:
  - name: uq_it_service_service_code
    columns: [service_code]
columns:
  - name: service_code
    dataType: string
    nullable: false
    maxLength: 64
  - name: name
    dataType: string
    nullable: false
    maxLength: 128
  - name: owner_team
    dataType: string
    nullable: false
    maxLength: 128
  - name: criticality
    dataType: string
    nullable: false
    maxLength: 16
  - name: systems
    dataType: string
    nullable: true
    maxLength: 512
  - name: status
    dataType: string
    nullable: false
    maxLength: 16

YAML sketches

Sketches highlight the important fields and governance flags. Trim or extend columns to match your domain. See Setup Entity for the full YAML reference.

Sample data

service_code name owner_team criticality systems status
SVC-ERP ERP core IT Ops critical SAP active
SVC-CRM CRM Sales Ops IT high Dynamics active

Benefits for the company

  • Fast owner lookup during incidents.
  • Explicit criticality.
  • Webhook-friendly into ITSM.