Run entity relationship diagram

Reading the diagram

Each box is a database table and lists its mapped columns. Columns marked FK hold a relationship to another entity. The text beside a connecting line is the Doctrine association name; 1, 0..1, and 0..* indicate required single, optional single, and zero-or-more relationships respectively. References to shared entities, such as users, equipment, files, and projects, may appear only as foreign-key columns in this focused diagram.

Main relationships

• The Process portion defines reusable process modules, parameters, units, recipes, recipe versions, checklists, and rework configuration that can supply run steps.

• run_run is the execution aggregate. It owns run steps, parts, trays, changelog entries, roles, service work, priorities, hold codes, and references to parent or related runs.

• A run_step belongs to one run and carries execution-specific parameter values, parts, checklist entries, labels, requirements, measurements, tags, and optional service-work or monitored-process links.

• Measurements have result values and labels; requirements have targets and can be attached to steps and parts. Consumable and substrate matrices, part mappings, and trays preserve material and physical traceability.

Use this view to trace an execution from its process definition through steps and captured results. Follow an FK into the full ERD when the relationship continues into Equipment, Template, Chemical, or a shared domain.