SYSTEMA CONSTRUCTUM

Accepted ontology entry

root-cause-analysis

Root-cause-analysis is the human-made systematic method for identifying the fundamental cause of a problem or failure by tracing observable effects backward through chains of contributing factors. It is defined by four parameters: (1) effe…

ACCEPTED THINGcms82vo3z00odh6s86r3hkpih

Definition

Root-cause-analysis is the human-made systematic method for identifying the fundamental cause of a problem or failure by tracing observable effects backward through chains of contributing factors. It is defined by four parameters: (1) effect — the observable failure or problem to be explained; (2) causal-chain — ordered sequence of contributing factors linking effect to root cause; (3) technique — the structured method used (five-whys, fishbone/Ishikawa diagram, or fault-tree analysis); (4) termination — the point at which further tracing yields no actionable contributing factor. Persistence mechanism: documented procedure codified in standard operating protocols and quality-management systems. [formal: analysis-causae-fundamentalis | substrate: behavior | horizon: a moment | explicit: yes | epoch: 0.01]

Why it is in scope

The human-made systematic method for identifying the fundamental cause of a problem or failure by tracing observable effects back through chains of contributing factors, using structured techniques such as the five-whys, fishbone diagrams, or fault trees.

Names and aliases

Relations from this entry

  • cms8624hw0106h6s8t8c71gedSERVES →

    Root-cause-analysis is a method for identifying the fundamental causes of problems. Its designed purpose is to produce actionable insights that feed into corrective-action. Law 8d SERVES: the servant points at the master. Without corrective-action as the target, root-cause analysis is academic exercise. Purpose is by design in safety and quality management practice.

  • cms8fls9600pv73fklpt543o4INSTANCE_OF →

    RCA IS a specific kind of cause-analysis — it narrows the general task of identifying causes down to finding the fundamental (root) cause rather than proximate ones. A competent speaker would call RCA 'a cause-analysis technique.' Specific→general, Law 9. Nearest kind is cause-analysis (no intermediate category).

  • cms8hv4kr00xq73fkv0rpdis4DERIVED_FROM →

    which-came-first test: the concept of a root cause (fundamental reason behind failure) existed long before the formalized method of root-cause-analysis was systematized in the 1960s (Ishikawa). The older concept fed into the newer method.

  • cms8i0dos00yc73fk56hh20mdDEPENDS_ON →

    Root-cause-analysis depends on cause-and-effect reasoning as its operational mechanism: without the ability to trace causal chains (cause-and-effect), the method cannot identify root causes. Law 8 removal test: remove causal reasoning and RCA stops operating — it becomes pattern-matching without explanatory power. This is a present-tense dependency, not historical association.

  • cms8a929t007573fkafm8ap7iSERVES →

    root-cause-analysis is a systematic method for identifying fundamental causes of failures, built and maintained for the sake of risk-management. Law 8d: for-whose-sake — its designed purpose is to feed root-level findings into risk assessment and control decisions.

  • cms8vp46t02bw73fk0i3zar8rINSTANCE_OF →

    Root-cause-analysis is a specific form of hazard assessment: it systematically investigates incidents to identify underlying causal factors, making it a concrete method within the broader hazard-assessment practice.

  • cms9ugt75025w7skq30mpohwiSERVES →

    Law 8d: root-cause-analysis is built and maintained for the sake of safety-investigation. RCA is a method whose designed purpose is to further the operation of safety-investigation by identifying underlying causes. Servant (RCA) → master (safety-investigation).

  • cmsa1z0mp02l87skqqqhj21wqSERVES →

    root-cause-analysis is a method built and maintained for the sake of investigating safety-failures. Its designed purpose is to identify underlying causes of failures. Law 8d: servant (RCA) points at master (safety-failure investigation/understanding).

Relations to this entry

  • cms8exw0t00n973fkx6kg59sj← SERVES

    For whose sake? The fishbone diagram (Ishikawa diagram) is designed specifically to serve root-cause analysis — its branching structure maps causes to effects to help teams identify contributing factors. It is built and maintained for that purpose. Direction: fishbone-diagram → root-cause-analysis (servant → master).

  • cms8n4nox01g173fkaf4ugmim← SERVES

    forensics is built for the sake of root-cause-analysis. Forensic methods — systematic evidence collection, measurement, and reconstruction — serve the purpose of identifying underlying causes of failures and incidents. Its designed purpose in safety, engineering, and accident investigation contexts is to provide the evidential basis for root-cause-analysis. For whose sake is forensics maintained? For root-cause-analysis. The servant points at the master.

Record identity

Created
Jul 30, 2026, 10:21 PM UTC
Content hash
f9dd69af964f598aec404f252a0bf6feaf92d424eb4a2b41ac45ff407e1cde16

Open a related act record