slug: xmatters
provider: xMatters
generated_by: planning/capability-mapping/scripts/classify_capabilities.py
model: claude-opus-5
frame:
- Software & Technology
min_confidence: 0.7
capability_model:
  source: https://github.com/vincentmakes/turbo-ea-capabilities
  license: CC-BY-4.0
  attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities,
    CC BY 4.0
  notice: NOTICE
edge_count: 3
edges:
- tag: Events
  spec_file: xmatters-events-api-openapi.yml
  capability_id: BC-4220.30
  capability_id_l1: BC-4220
  capability_name: Incident Response Management
  confidence: 0.85
  evidence: POST /events createEvent Trigger a new event; PUT /events/{eventId} Change the status of an
    event; POST /events/{eventId}/annotations Add a comment to an event
  reason: xMatters events are the incident notification/alert objects routed to on-call responders, with
    status changes and annotations — i.e. incident detection, coordination and communication during production
    incidents. Maps to Incident Response Management. Could also be read as ITSM incident, but the vendor
    context is service reliability/on-call response.
- tag: On Call
  spec_file: xmatters-on-call-api-openapi.yml
  capability_id: BC-4220.30
  capability_id_l1: BC-4220
  capability_name: Incident Response Management
  confidence: 0.8
  evidence: GET /on-call getOnCall Determine who is currently on-call
  reason: Resolving who is currently on-call is the core of on-call response rostering for production
    incidents, which the frame places under Incident Response Management ('On-call response, incident
    detection, coordination').
- tag: Shifts
  spec_file: xmatters-shifts-api-openapi.yml
  capability_id: BC-4220.30
  capability_id_l1: BC-4220
  capability_name: Incident Response Management
  confidence: 0.7
  evidence: GET /shifts listShifts; POST /shifts createShift; API description cites 'on-call schedules'
  reason: Shifts define group on-call rotation schedules, part of the on-call response capability. Lower
    confidence because the operations are generic CRUD and shift scheduling could superficially read as
    workforce scheduling; the vendor context ('on-call schedules') grounds the reliability reading.