Incident, problem and root cause
Service disruption, cause investigation, impact, response and recovery. Incident, problem, security event, defect and task play different roles.
Research draft, second pass
A second pass drafted this model: the structure a model of this thing needs, and what is known about it in the world. The line under this one says how the second half was obtained - researched against sources, or recalled without web access, in which case nothing here was read anywhere and every claim is a lead to verify. Unreviewed either way.
Bundle → Layer → Finding → Questions Missing, in the backlog
Not described yet. This gap is in the card backlog.
Note: Research contour: bundles not designed yet; questions are listed as open questions.
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 Derived, awaiting review
- A cause has evidence and confidence
- Recovery does not close the problem automatically
- Severity and priority are separate
What robots and AI may and may not do Derived, awaiting review
Must not
- Negative case: Closing an incident deletes an unfinished root cause fix.
Note: Negative case of the research brief, not yet a rule for agents.
Moral aspects Missing, in the backlog
Not described yet. This gap is in the card backlog.
Owners Filled
Steward
CTO / CIO / владелец сервиса
Master systems
- Каталог ПО
- Git
- CI/CD
- CMDB
- observability
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 Incomplete
Identity and identifiers required Derived, awaiting review
- Incident
- Problem
- ImpactAssessment
- ResponseAction
- RootCauseClaim
Direct properties not applicable Not applicable
Not applicable
Enterprise record contour: physical properties belong to referenced world models.
Recognition required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Capabilities and actions required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Hazards and failure modes required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Standards and interfaces required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Context of use required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Sources Filled
- AISMM/WM-SFT and ArchiMate: product, system and architecture
- CSDM: business application, service and runtime instance
- SPDX/OpenTelemetry/Google SRE: delivery, observation and reliability; choose by boundary
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
Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.