Separator Node
TLDR: Separator nodes take one agent and create multiple copies of it. Use for splitting an order into fulfillment + billing, unbatching a pallet, or any case where one thing becomes many.
How to Split
The first section shows:
Number: [number stepper] PCS
Set how many copies to create from each incoming agent. The minimum is 2. For example, setting 3 means each agent that enters produces 3 copies downstream.
Attributes
This section lets you assign different attribute values to each copy, so they can be distinguished downstream.
Toggle "Assign attributes to copies?" to enable. For each attribute defined in your simulation, you'll see:
- The attribute name
- Each possible value with increment/decrement buttons and a count
- A progress bar showing how many copies have been assigned (green when complete, yellow when partial)
- A status like "3 / 3" (all assigned) or "2 / 3 (1 remaining)"
For example, if you split into 2 copies with a "department" attribute, you might assign copy 1 as "fulfillment" and copy 2 as "billing".
A Separator duplicates agents — one becomes many. For routing (sending one agent to one of several paths), use Path Control on any node with multiple outgoing connections instead.
Path Control
Only visible when 2 or more outgoing connections exist.
After splitting, Path Control determines where each copy goes. The same routing options are available: Random, Custom Split, Shortest Queue, Priority, or Conditional.
Use Cases
- Order splitting: Send to fulfillment AND billing simultaneously
- Unbatching: Split a batch of 5 into 5 individual agents (set number = batch size)
- Parallel processing: Create copies that travel different paths, then recombine later with a Combiner
- Document copies: Generate backup or audit copies of documents
Don't use a Separator for triage routing. Instead, use an Assign node to set a severity attribute, then use Conditional Path Control on the next node to route severe cases to the ER and minor cases to Fast Track.