Core concepts
Physical structure
The normal location hierarchy is site → building → room → zone group → zone or location. Rooms are the main access boundary. Zones can be reserved, while locations identify a storage or placement point. Equipment can be placed in a room and optionally narrowed to a zone group, zone, location, or—when that classification mode is enabled—a facility area.
Equipment and modules
An equipment record represents the whole tool, accessory, or storage unit. A module represents a functional part of that equipment. The main module carries operational status and can connect the equipment to process definitions, parameters, issues, engineering change notices, assets, and external activity. Small tools often need only the main module; complex tools can have several.
Processes, recipes, and templates
A process describes a type of operation. Its equipment-module association determines where it can execute and which parameters are available. A recipe is a versioned, reusable set of process settings. A template arranges processes, recipes, requirements, and measurements into a reusable sequence.
Runs and parts
A run records actual research or production work. It belongs to an organisation group, team, and project, and it can contain one or more parts. Steps record execution, parameter values, files, checklists, measurements, and requirements. Runs may start from a template, another run, selected parent parts, or substrates. The experimental-split feature keeps the ancestry and mapping of split parts.
Access and approval
Global permissions decide which routes and actions are available. Entity roles then designate responsible users for a specific room, equipment item, project, team, or run. Room and equipment training requests create approval flows from the responsible roles configured to participate. Some installations also require approval before a run starts or an equipment reservation is confirmed.