← Back to catalogue
Published

Incident, problem and root cause

EM-TEC-05 · em-tec-05

Service disruption, cause investigation, impact, response and recovery. Incident, problem, security event, defect and task play different roles.

Enterprise profiles Enterprise subject EnterpriseTEC

Bundle → Layer → Finding → Questions Filled

2 bundles · 3 layers · 4 findings · 9 questions

Disruption and response A service disruption, its impact and the response to it.

Incident

An incident separated from the observation events that revealed it.

Incident versus event

When an observation becomes an incident with an owner.

  1. Which observations or alerts led to declaring this incident?
  2. Which services and users were affected, and for how long?

Severity and priority

Severity of impact and priority of response as separate fields.

  1. What is the assessed severity, and on which impact basis?
  2. What priority was set for the response, and by whom?
Cause and follow-up Investigation of causes and the actions that remove them.

Problem and cause

Recurring incidents grouped under a problem with cause claims.

Root cause claim

A cause stated with its evidence and confidence, possibly disputed.

  1. Which evidence supports the stated cause, and how confident is it?
  2. Is the cause disputed, and by whom?
  3. Which incidents are linked to the same problem?

Recovery and fix

Temporary recovery kept apart from removal of the cause.

Follow-up actions

Response and fix actions with their own status after the incident closes.

  1. Was service restored by a workaround or by removing the cause?
  2. Which follow-up actions remain open after the incident was closed?

Classifiers Filled

Family
Enterprise profiles
Category
Enterprise subject
Entry kind
subject
Domain
EnterpriseTEC
Industry
Cross-industry
Tags
EM-TEC-05W1subjectIncidentProblemImpactAssessmentResponseActionRootCauseClaim

What it is Filled

Service disruption, cause investigation, impact, response and recovery. Incident, problem, security event, defect and task play different roles.

Why it exists Filled

Service disruption, cause investigation, impact, response and recovery. Incident, problem, security event, defect and task play different roles.

Distinguishing features Filled

  • Recovering a service does not close the problem behind it.
  • A cause is a claim with evidence and confidence, and may stay disputed.
  • Severity measures impact while priority sets response order; they are recorded separately.
  • Distinct from security events, defects and tasks, which play different roles in the same story.

What robots and AI may and may not do Filled

Must not

  • Delete or close an unfinished root cause fix when the incident is closed.
  • State a root cause as settled without evidence and confidence.
  • Merge severity and priority into one value.
  • Assign blame to a named person in an incident record.
  • Execute remediation changes in production on its own initiative.

Only with a human decision

  • Declaring a major incident or notifying customers and regulators.
  • Accepting a root cause as final when it is disputed.

May

  • Group recurring incidents under a candidate problem for review.
  • Draft a timeline from recorded observations and actions.
  • Flag closed incidents with open follow-up actions.
  • Summarise the evidence behind each cause claim.

Moral aspects Filled

  • Blameful records discourage honest reporting and harm staff.
  • Users affected by outages need timely and truthful information.
  • Unresolved causes expose people to repeated harm.

Who is affected

  • Users and customers of affected services
  • On-call and operations staff
  • Regulators for notifiable incidents

Owners Filled

Steward

The CTO, the CIO or the service owner accountable for the system.

Master systems

  • Software catalogue
  • Source control
  • CI/CD pipeline
  • CMDB
  • Observability platform

Links to other meta-models Filled

neighbor

  • EM-OPS-01
  • EM-PRD-02
  • EM-TEC-04
  • EM-WRK-01

references

  • WM-ACT-019 - conceptual-candidate
  • WM-ACT-020 - conceptual-candidate

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • An incident has its own identifier and links to separately identified problems, cause claims and actions.

Direct properties not applicable Not applicable

Not applicable

Enterprise record contour: physical properties belong to referenced world models.

Recognition required Filled

  • An incident record names an affected service, a start and end time, a severity and a status.
  • An incident can be confused with an alert, a security event, a defect or a work ticket.

Capabilities and actions required Filled

  • Problem records connect repeated incidents to a shared cause.
  • Follow-up actions remain traceable after the incident is closed.

Hazards and failure modes required Filled

  • Incidents can recur when fixes are dropped after service is restored.
  • Accepting the first plausible cause without evidence creates confirmation bias.
  • A culture of blame suppresses incident reporting.

Standards and interfaces optional Filled

  • ISO/IEC 20000-1, issued jointly by the International Organization for Standardization and the International Electrotechnical Commission, addresses incident and problem management.
  • The ISO/IEC 27035 series, issued jointly by the International Organization for Standardization and the International Electrotechnical Commission, addresses information security incident management.
  • NIST SP 800-61 Revision 3, Incident Response Recommendations and Considerations for Cybersecurity Risk Management, is issued by the National Institute of Standards and Technology.

Context of use required Filled

  • Operations, site reliability engineering, service desk and security teams use incident and problem records.
  • Some sectors require notification of significant incidents to regulators within specified deadlines.

Sources Filled

  1. AISMM/WM-SFT and ArchiMate: product, system and architecture
  2. CSDM: business application, service and runtime instance
  3. SPDX/OpenTelemetry/Google SRE: delivery, observation and reliability; choose by boundary
  4. OpenTelemetry Specification - Checked live (HTTP 200) on 2026-10-07.
  5. NIST SP 800-61 Rev. 3: Incident Response Recommendations and Considerations for Cybersecurity Risk Management - Checked live (HTTP 200) on 2026-10-07.

Open questions

  • How to separate an observation event from an incident?
  • How to link recurring incidents to a single problem?
  • When does service recovery not eliminate the cause?
  • Установить границу и решение reuse/extend/new по действующим спецификациям.
  • Подтвердить semantic crosswalk, права и source mastership.
  • Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.

Machine files

Provenance

enterprise research programme · published-partial

Built from: enterprise/models/em-tec-05/brief.json, ver-cy/world-models/card-supplements/em-tec-05.json

Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.