question

shanice.c avatar image
0 Likes"
shanice.c asked Felix Möhlmann commented

What's the difference using Resource and list in Process flow?

I'm using Resource to administrate all standbypoints of AGV, I read manual before, it says that Resource and Lists both can be used for shared assets.

But I have problem if using Resource, I want to understand how to fill in the parameter when using Resource.

Below is my process, lefthand side is using list; righthand side is using Resource. Using List seems working fine.

p1.png

Below is my setting of Acquiring Resource.

p2.png


0901resource and list.fsm

FlexSim 21.2.0
listresourceflexsim 21.2.0shared assets
p1.png (38.1 KiB)
p2.png (184.2 KiB)
· 1
5 |100000

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

1 Answer

Felix Möhlmann avatar image
2 Likes"
Felix Möhlmann answered Felix Möhlmann commented

The "Assign to Label" option only lets you assign the label to a token. Assuming that "token.agv" references an AGV in the model, this is likely the reason why you are having problems. Assign the pulled resource to a label on the token first. Then, if you want to have the value available on the AGV, use an "Assign Label" activity to copy it from the token onto the AGV. The "Release" activity also expects a label on the token.

The advantage of the "Resource" is that it lets you define a numeric ("virtual", so to speak) resource with only a few clicks, whereas doing this with a list would require you so create some dummie objects/tokens.

If you are referencing to a group of objects in the resource, it internally switches to using a list as well. At this point, the only difference is that, again, the setup of a resource of group objects requires a couple fewer clicks than a list. On the other hand, the "Pull From List" activity has some options that are missing from the "Acquire Resource" activity, such as distinguishing between requested and required number of pulled entries.

A list also supports partitions and can be made global to pass information/objects between multiple parts of the model.

· 4
5 |100000

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