Resource Node
TLDR: Resource nodes are shared pools of workers or machines. Assign them to Processors so that work can only start when a resource is available. Use for cross-trained staff, shared equipment, or any capacity that's dynamically allocated.
The Workers
The top section of the Resource properties panel shows:
- Avatar & color: Click the colored circle to pick a color for this resource pool on the canvas.
- Pool Size: [number stepper] STAFF — how many workers or units are in this pool. For example, "3 STAFF" means 3 nurses, 3 forklifts, or 3 machines.
A Processor's capacity is how many agents it can serve simultaneously. Resource requirements are an additional constraint — the Processor also needs an available resource from the pool before it can start work. Both must be satisfied.
Works At
This section shows all Processor nodes on your canvas as clickable chips.
- Click a chip to toggle whether this resource pool serves that Processor
- Blue chip with checkmark = assigned
- Gray chip = not assigned
If no Processors exist yet, a message reads: "No processors on canvas yet".
If no assignments are made, a warning banner appears: "Select one or more processors to assign this resource".
Availability
Collapsed by default.
A Gantt-style timeline for scheduling when this resource pool is available. Add shift blocks to define working hours. Outside of scheduled shifts, the resources are unavailable.
Use this to model:
- Day/night shifts with different staffing levels
- Lunch breaks when some staff are unavailable
- Part-time workers with limited hours
How Resources Work at Runtime
- An agent arrives at a Processor that requires this resource
- If a resource is available in the pool, it's allocated for the duration of service
- When service completes, the resource returns to the pool for reuse
- If no resource is available, the agent waits in the Processor's queue
Create separate Resource nodes for different types. A surgery might require both a "Surgeon" resource AND an "OR Room" resource. Configure this with staffing groups on the Processor node.
Use Cases
- Cross-trained staff: 5 nurses serving Triage, Treatment, and Discharge
- Shared equipment: 2 CT scanners serving ER and Radiology
- Floating workers: Employees who help wherever the queue is longest
- Material handling: Forklifts serving multiple workstations