Resource Connectors

A resource connection attaches a resource to an activity, so the activity seizes that resource to do its work. You draw it from a resource to an activity, and the type decides when the resource is taken and given back.

• Get / Free: seize the resource for the activity, release it automatically when the activity finishes (the default)
• Get / Keep: seize the resource and hold it across later activities until you free it
• Free: release a resource that a Get / Keep connection is holding
• Alternate: a backup resource used when the primary is busy

Resource connections share a few settings on their General tab:

• Quantity: how many units of the resource to seize (a number or an expression).
• Priority: when several activities compete for the same resource, this sets the order in which they acquire it.
• Setup / Travel Time: the time the resource needs to reach the entity before work begins (0 means instant). This applies to Get / Free and Get / Keep. On a connection to a resource that moves along paths the row reads Setup instead, because the travel then comes from the paths (see below).

A resource connection carries a label on the canvas, such as Keep or Free. Right-click the connection and choose Edit Label to type your own text in its place, and Delete Label to put the automatic text back, exactly as on a route (see A route’s label).

A resource with Moves along paths ticked (see Resource) uses the same connections. What you draw says what the unit does:

What you mean	How to draw it
The unit works here	A Get / Free on the activity, as for any resource. The unit drives to the step, then the work runs.
The unit brings the part here	A Get / Keep at the source with Collect at set to Output queue, and a Free at the destination with Let go at set to Input queue.
The unit brings the part here and then works on it	The same Get / Keep at the source, and the destination’s Free left on After activity.
The unit carries the part through several steps	A Get / Keep at the first step and a Free at the last. The unit stays with the part at each step between (see Through every step to the Free).

On these connections:

• Setup is charged when the unit arrives, on top of its own pickup time. A Free to a moving resource has a Setup row too, charged at the drop-off on top of the unit’s drop-off time.
• Collect at appears on a Get / Keep and Let go at on a Free, only when the resource moves. See Get and Keep Connector and Free Connector.
• A queue can hold a connection from a moving resource, for delivery only, since a queue does no work: the unit collects from it or puts parts into it. A connection from a resource that does not move to a queue does nothing, and the checker says so: “[Resource] does not move, so its connection to [queue] does nothing. Mark it as moving, or remove the connection.”
• Every step a moving resource serves needs a Path node, set on the step’s General tab (see Drawing Paths). Without one the checker reports “[Step]: [resource] delivers here, but [step] has no path node. Link it to a path.” A step a unit carries a part through on its way to the Free needs one too: “[Step]: [resource] carries parts through here, but [step] has no path node. Link it to a path.” So does a step where a carry ends with a FREE or FREE ALL in its logic, or where a unit that collected from a queue with a Get / Free puts the part down: “[Step]: [resource] carries parts to here, but [step] has no path node. Link it to a path.”
• A resource that picks orders takes no calls from the flow, so it cannot be connected to a step at all (see Order Picking and Station Schedules).

A Get / Free or Get / Keep connection also has Assignment on its General tab, below Setup / Travel Time. It says which unit of the resource serves the case:

• Pool (any free unit): “Any free unit serves the case.” This is the default.
• Dedicated (same worker every visit): “First claim assigns the case to a worker; later claims wait for that worker.”
• Assign only (assign a worker now, use them later): “Admission requires this worker’s caseload headroom and assigns the case. The worker is not held here.”

Dedicated and Assign only stay gray, with the note “Enable Caseload on Resource 1 first” (the name is the resource’s own), until the resource’s Caseload is turned on. Once it is on, and the resource is in a resource group, the two choices carry a second line: “Binds across the group’s on-shift members.” The pictures are in Get and Free Connector and Get and Keep Connector.

On a connection left on Pool, from a resource that is in a resource group, a checkbox reads Someone other than the person it is assigned to: “Anyone on the team is eligible except the worker already carrying this case.” It is gray, with a note to turn a caseload on for the resource first, until the resource’s Caseload is on. It is not offered on Dedicated or Assign only.

LegacyHow this worked in the previous version

A resource connection assigns a resource to perform an activity or conduct a move. Resource assignments use connectors as shown below or use action logic. Connectors are fast, easy, and automatically handle the proper collection of statistics, while action logic provides greater control of resource assignments, but requires more effort. To learn more about assigning resources in the action logic see What is a Get statement?

A resource assigned to the Check-in process.

The resource assignment starts when an entity enters the activity or when the entity is released to move on a route. The Get and Free use the resource for one task (activity or move), then automatically releases the resource for other assignments.

The resource is assigned to escort people from Waiting to Exam.

Assign multiple tasks in succession

Section titled “Assign multiple tasks in succession”

To assign multiple tasks in succession, use a Get connection on the first and a Free on the last activity. In the example below, the worker is required before an entity can proceed to start process of the three activities. After finishing all three activities and the associated moves, the entity releases the resource and continues in the flow.

Multiple activities and moves are performed in succession.

Capture multiple resources for a single entity

Section titled “Capture multiple resources for a single entity”

No individual of a multi-resource request accepts the Get until all units become available. At Cessna Aircraft, airplanes move from station to station during production. Workers push the plane, advancing it to the next position. Union rules require eight people before a push occurs. The information below shows the assignment of eight workers. After finding eight people, the capture occurs, and the move time starts. The assignment of multiple resources must not be confused with the number of resources. The number of resources stays the same.

Assigning multiple resources to the same entity.

Assign resources to multiple activities

Section titled “Assign resources to multiple activities”

When captured, a resource becomes unavailable for use by other activities. For example, if Agent1 is performing the activity “Process a Return,” they won’t be able to “Checkout” a customer at the same time.

Prioritize the work

Section titled “Prioritize the work”

When two or more activities request the same resource, a priority decides the first selected. The greater the number the higher the priority. For example, a call center does both inbound and out bound calls. Queued inbound calls always receive priority over making outbound calls.

Priority entries range from 0 to 99. Selecting the Respond Immediately checkbox make the priority preemptive. A preemptive priority means this request overrides the current work and pulls the resource. To find greater detail about priorities and preemption see What is a Resource Priority?

Entities waiting for resources always select the connection with the highest priority.

Alternate resources, resources on different shifts

Section titled “Alternate resources, resources on different shifts”

Multiple or alternative resources may be used for an activity or move. An alternate resource might be coworker that steps in an overwhelming surge, during breaks or lunch, or resources on second and third shift. If the first resource is unavailable then the second resource connection is attempted.

If Shift1 is not available then the Shift2 connection is tried.