question

Aidan W avatar image
0 Likes"
Aidan W asked Jason Lightfoot action

Processors not pulling by label on item?

Hello,

I'm trying to simulate a shop floor in which a bunch of different products are produced and as a result, each have to go to a different tester that is specialized to its needs. What I had tried to accomplish with my design is that after the assembly step is complete, the product is moved to a queue that is linked to every tester. From there, each tester is using a Pull Strategy that is only pulling for products that have the label that concerns that tester. For example, when the model starts, there is a unit that goes to PWCASSY3 that has the label PWCRIG22. At Rig 22, the Pull Strategy is pulling any label that contains that 'RIG22' based on data I have. However, when it gets to the queue, it stays there and is never pulled. Am I misunderstanding the Pull Strategy I'm trying to apply or is there something else wrong with my process?

Couple of side notes: I know the connections mesh is a mess so any alternative recommendations would also be greatly appreciated. The error that comes up due to a product having itemNum 1000 is something I'm working on fixing but it doesn't affect the model currently. Lastly, I know some labels are not being called to any tester so they will be stuck at queues forever; I'm figuring out which Rig those labels go to.

Attached is the model, and thanks! Shop Floor.fsm

FlexSim 20.2.0
FlexSim 20.0.10
labelsprocessorsflexsim 20.0.10job shopjobshop
shop-floor.fsm (2.1 MiB)
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

Jason Lightfoot avatar image
1 Like"
Jason Lightfoot answered

An alternative approach for you to consider.

Define your process steps for a product as operations in a table:

Define your capability in another table:

Put that information as labels on machine and push those onto lists which then look like this:

And then have a process flow for each item pull a machine that can do its next operation:

This avoids the need to a nest of connections. Example/concept model attached.


1617291445326.png (3.5 KiB)
1617291497935.png (4.1 KiB)
1617291510603.png (5.6 KiB)
1617291835035.png (6.4 KiB)
1617291884884.png (9.6 KiB)
1617291932091.png (21.1 KiB)
1617291962402.png (90.3 KiB)
jobshoprouting.fsm (48.1 KiB)
5 |100000

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