incident
Let an agent interpret incident as a distinct event, support incident recording, response and investigation in general terms, describe incident management practices, and separate the sense of a notable public affair.
Bundle → Layer → Finding → Questions Filled
4 bundles · 8 layers · 8 findings · 16 questions
Interpret Which sense.
Sense
Which incident.
Sense
Sense.
- Is incident used for a distinct event, a managed occurrence, or a notable public affair? boundary
- Which entry fits? action
Classify
Classifying incidents.
Classify
Classification.
- How are incidents classified by severity and type in different domains? definition
- How do incidents differ from accidents and near misses? definition
Respond Responding to incidents.
Response
Response.
Response
Response.
- How should an incident be responded to, contained and escalated in this domain? action
- Is an emergency in progress, requiring emergency services now? boundary
Record
Recording and reporting.
Record
Recording.
- How are incidents recorded and reported, and which reporting duties apply? provenance
- Which entry fits a specific reporting scheme? action
Learn Investigation and improvement.
Investigate
Investigation.
Investigate
Investigation.
- How are incidents investigated for root causes, and how are lessons applied? action
- Which entry fits root cause analysis? action
Systems
Incident management systems.
Systems
Systems.
- What are incident management frameworks in IT, emergency services and workplaces? provenance
- Which references are standard? provenance
Public Public incidents.
Affairs
Causes celebres.
Affairs
Public affairs.
- What makes an incident a cause celebre, and how should contested public incidents be described with attribution? provenance
- Is the presentation neutral? boundary
Teach
Teaching.
Teach
Teaching.
- How can incident management be taught with case studies? action
- Which misconceptions arise? provenance
Classifiers Filled
- Family
- Thing Registry
- Category
- Activities and processes
- Entry kind
- noun.event
- Plane
- ACT
- Domain
- ACT.EVT
- Facets: substance
- activity
- Facets: origin
- conceptual
- Facets: agency
- inert
- Facets: mobility
- not-applicable
- Facets: scale
- not-applicable
- Facets: affordances
- observable
- Other names and narrower kinds
- cause celebre, infection, contagion, transmission, sideshow
What it is Filled
A single distinct event, especially one that is notable, disruptive or requires a response, from minor occurrences to safety, security and public health incidents such as an infection transmission or a contagion event, and to widely discussed affairs known as causes celebres; incidents are recorded, investigated and managed in incident management systems across workplaces, IT, transport and emergency services.
Why it exists Filled
Let an agent interpret incident as a distinct event, support incident recording, response and investigation in general terms, describe incident management practices, and separate the sense of a notable public affair.
Distinguishing features Filled
- Discrete
- Notable or disruptive
- Recorded and managed
- Cross-domain
What robots and AI may and may not do Filled
Must not
- Suppress, downgrade or delay reporting an incident to avoid blame.
- Speculate publicly about causes or culprits before the facts are established.
- Disclose the identities of people involved beyond those who need to know.
- Alter logs or evidence relating to an incident.
Only with a human decision
- Declaring a major incident or calling emergency services when the situation is unclear.
- Notifying regulators, the public or people affected.
May
- Log incidents with time, place, source and what is known, keeping facts separate from guesses.
- Notify the people on the agreed response list when an incident meets the threshold.
- Help compile a timeline from records it is authorized to read.
Moral aspects Filled
- Fast and honest reporting saves lives and prevents repeats.
- People caught up in an incident deserve privacy and fair treatment before blame is assigned.
Who is affected
- People hurt or affected
- Responders
- Staff involved
Owners Filled
Steward
The organization or authority in whose area the incident happens.
Links to other meta-models Filled
parent
- oewn-07298313-n - registry parent class
related
- event - category
- origin - events that begin sequences
- pathogen - infection incidents
- conflict - dramatic incidents in narrative
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- Vercy registry: vr.tr.incident
- Open English WordNet: oewn-07322095-n
Direct properties not applicable Not applicable
Not applicable
Plane ACT: no invented physical properties.
Recognition optional Filled
- Single distinct event
- Often requiring a response
- An accident is unintended harm; a process is ongoing
- Not physical; an event in time.
Capabilities and actions required Filled
- interpret the sense
- support recording and response
- describe incident management
- separate senses
Hazards and failure modes required Filled
- Unreported incidents
- Poor response coordination
- Confusing senses
Standards and interfaces required Filled
- Incident reporting regulations in workplaces and transport
- IT incident management frameworks
- Public health notification rules
Context of use required Filled
- A distinct event requiring attention.
- safety and workplace incidents
- IT and security incidents
- transport incidents
- public health incidents such as transmission events
- public affairs and causes celebres
Sources Filled
- Open English WordNet 2024, synset oewn-07322095-n - sense and gloss of the concept
- Wiktionary: incident - word senses and usage
Open questions
- Should incident management be a separate entry?
- How should reporting rules be linked?
- How should the public affair sense be split?
Machine files
Provenance
thing registry research (pass 2) · unreviewed
Built from: models/things/publications/thing-incident/spec.json