Definition
The registry of "things being measured" in the system: what subjects exist on-site, what events occur on them, how they are connected, what can be done to them, and who has the right to do it. Contrasted with tool cards and rule packages (the rulers). Not DBS textbook content; this is the system's own design.
In detail
Tool cards and rule packages answer "how to calculate, how to judge"; the ontology answers "who is being calculated, who is connected to whom, and what can be done to it." It is divided into three layers—entities (factory, production line, workstation, equipment, parts, Standard Work, people, external organizations, projects, value streams), events (abnormalities, problems, Kaizen activities, audits, rectifications), records (daily grid, five tables, countermeasure table)—with only one criterion: whether there is a person or Agent that needs to do something to it. Types are registered in the repository's registry and cannot be added at will in the interface; only the six registered relationships are recognized. See Part 8 of the practical guide for the tutorial.
Example in practice
An Andon ticket reads "L3"; the system finds the object "Line 3" by line_id and attaches the ticket to it; the escalation chain finds the team leader accordingly; if the category is in the stop list, a proposal is opened for the team leader to approve; the problem raised from this ticket carries the "derives" edge, and when the countermeasure is standardized, it connects to the revised standard work.