question

Kari Payton avatar image
0 Likes"
Kari Payton asked Mischa Spelt edited

Limiting one crane in operation at a time.

Hello,

The token pulls either Crane 1, 2, or 3 from a list. I want to create a simpler way to do the following:

1. Check which crane was pulled.

2. Whatever cranes were not pulled, check if they are in operation. The cranes are used on different custom FR process flows.

3. If another crane is operating I need to wait until that crane is done operating before using the crane that was pulled.

Basically only one crane can be operating at one time. This is what I have, but hoping there is a clearer way to model because the number of cranes will increase to 8 in some cases.

Choose One
process flowcranes
idea.png (100.6 KiB)
idea.png (99.6 KiB)
· 4
5 |100000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

Steven Hamoen avatar image Steven Hamoen commented ·

@Kari Payton. Why don't you pull the new crane after the previous one is finished?

0 Likes 0 ·
Kari Payton avatar image Kari Payton Steven Hamoen commented ·

@steven.hamoen the crane may be used in another process flow so I don't know when the previous one is finished. I am using multiple custom fixed resources.

0 Likes 0 ·
Steven Hamoen avatar image Steven Hamoen commented ·

@Kari Payton Couldn't you use a global process flow to determine which crane has to perform and then have the crane action in their respective FR Flows?

0 Likes 0 ·
Kari Payton avatar image Kari Payton Steven Hamoen commented ·

Sorry @steven.hamoen I'm not quite sure what you mean or how to do that.

0 Likes 0 ·

1 Answer

Mischa Spelt avatar image
1 Like"
Mischa Spelt answered Mischa Spelt edited

How about creating a numeric resource with a capacity of one? Any time any process wants to do something with a crane, it also acquires this resource. This way, the numeric resource acts like a sentinel or access token for crane movement, that activities will pass around and only the one holding the token is allowed to use the crane. Something like the following, where I have drawn two processes (they may be in different Process Flow instances) that both want to do something with a crane.

If you need to wait until the crane has actually stopped moving, rather than having the task sequence assigned, it is straightforward to use "Wait for task to finish" or a "Wait for event" activity to keep control of the access token until any other activity is allowed to touch a crane; conversely you may release the control early (while the crane is still moving) if other activities can start crane movements on other cranes before the current movement has finished.


cranecontrol.png (700.1 KiB)
5 |100000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.