Runs
A run is the traceable record of research or production work. It connects the organisational context and source material to an ordered set of executable steps, results, files, approvals, and history.
Run contents
Every run has a number, name, type, owner, organisation group, team, project, motivation, optional sample location and conclusion, part count, and status. Depending on configuration it can also have a tray and sample type, substrates, consumables, parent or child runs, related runs, reservations, priorities, hold codes, roles, and batch-card data.
The detail page exposes:
Information: master data, status controls, organisation, parent/child context, priorities, and hold codes.
Steps: process and recipe execution, instructions, parameter values, checklists, files, remarks, and part state.
Substrates and consumables: source and stock material assigned to the run.
Relationships and experimental split: related runs and part ancestry/mapping.
Requirements and measurements: acceptance criteria and recorded results.
Files: run-level attachments.
Reporting: remarks, equipment logging, changelog, progress timeline, and exports.
Other: variables, service work, roles/access, and related-run controls.
Lifecycle
A new run starts Under construction, where source material and steps can be prepared. Starting the run changes it to Open, directly or after approval. Finish it when execution and conclusions are complete; cancel it when it will not be executed. Closed or cancelled work can be reopened by authorised users, with every transition written to the changelog.
Follow Create a run, then see Run status and Run steps.