Processes
Overview
Processes define how a resource is used.
A Process represents a documented procedure, recipe, or workflow that can be selected at the time of booking and enforced during usage. Processes may:
- Require process-specific training
- Be restricted by Access Rules
- Generate Usage Records
- Apply their own Rates
- Produce Charges independent of the resource itself
- Trigger process-level interlocks
Processes allow facilities to control methods, not just machines.
How Processes Fit Into the System
A process sits between the resource and the user’s activity:
Resource → Process → Booking → Usage Session → Usage Record → ChargeKey concepts
- A resource can support many processes
- A booking includes one selected process
- Access Rules may evaluate process training
- A single usage session may generate multiple usage records
- Processes can independently control billing and interlocks
When Processes Are Used
Processes are selected:
- During booking creation
- Based on user permissions and training
- Only if permitted by applicable Access Rules
If a user does not meet the process requirements, the booking or activation will be blocked.
Process Training
Processes may require their own training, separate from resource training.
Important Distinction
- Access Rules evaluate Training Records
- They do not evaluate training sessions directly
A user is eligible if they hold a Valid Training Record for the process.
Access Rules & Processes
Processes integrate tightly with Access Rules.
Common rule patterns include blocking booking or activation if process training is missing or expired.
- Block booking if user lacks valid process training
- Block activation if training expires between booking and usage
- Combine with Provided Roles to allow exceptions
Info
Process training is enforced using booking and activation rules such as:
- Enforce Valid Process Training (Booking)
- Enforce Valid Process Training (Activation)
Usage Records & Billing
Processes are first-class billable entities.
- Each process creates its own Usage Record
- Rates may be defined at the process level
- Charges are generated when the usage session completes
- A single session may produce multiple records:
- Resource usage
- Process usage
- Configuration usage (if applicable)
Process Interlocks
Processes may have interlocks associated with them.
Unlike resource interlocks, process interlocks fire based on the selected process, regardless of which resource is used.
How Process Interlocks Work
- Interlocks fire when a usage session starts
- The session must include the specific process
- The interlock remains active until all sessions using that process have completed
Multi-Resource Process Behavior
Because a process can be associated with multiple resources, the following scenario is possible:
Resource A → Process X
Resource B → Process XIf Process X has an interlock, starting a usage session on either resource with that process will activate the interlock.
Critical Configuration Warning
If a process contains an interlock that should only fire for a specific resource, that process MUST NOT be associated with any other resources.
Use separate processes if behavior must differ by resource.
Best Practice
If an interlock should only fire for a specific resource, create a resource-specific process and do not reuse it elsewhere.
Managing Processes
When creating or maintaining processes, administrators typically define:
- Parameters (settings, values, tolerances)
- Instructions / SOPs
- Training requirements
- Rates
- Interlocks
- Applicable resources
Tips
If a process changes significantly, consider creating a new process instead of modifying the existing one to preserve historical accuracy.
Example Workflow
Scenario: CNC Milling
Resource: CNC Mill Processes:
- Aluminum Milling – Rough Cut
- Aluminum Milling – Finish Cut
- Steel Milling – Standard
User experience:
- User selects CNC Mill
- User selects a valid process
- Booking validates process rules
- Usage session starts
- Interlocks activate (if configured)
- Usage records and charges are generated