FLow-logic on article/components instead of machines

Question

question

Håkon L asked Oct 10, '22 Andrew O commented Oct 13, '22

FLow-logic on article/components instead of machines

Hi!
I have already tried searching for similar posts and topics, which I suspect there are, however I do not know if I am searching by the right terms, so here I go:

I am trying to simulate a production-flow which is more complicated than anything I have simulated so far. The challenge is that the simulation model is supposed to represent a production facility which is based on make-to-order where many items are "project-specific".

What this means is that some components are not project-specific - I just need an 'axle of type B', while other components are project-specific which means that the three components which mounts together to make a propeller has specific IDs, I can't just mount together any component C, D and E, it needs to be component C, D and E with matching IDs. So far I have figured out that to be able to do this I first need to have a SEPARATOR to separate a "product" to these 3 components, to be able to mount them together later on in the simulation.

BUT how do I make sure that every component runs through the correct machines and ends up on the correct project? Is it possible to put some logic on the component to tell it where to go? Or should it be done through assigning labels and making the machines in the simulation send it by the right output-port based on labels? I suspect there are some issues I don't see with the last suggestion, yet.

So I am looking for general thoughts and comments about how to accomplish this, but concrete tips would also be greatly appreciated. And if more information is needed to make a good answer, please tell me, and I will elaborate more.

In advance, thanks!

Software Version:

FlexSim 22.0.8

Software Version:

FlexSim 22.2.2

flowitem routing pathfinding make-to-order

· 1

Andrew O commented · Oct 13, 2022 at 06:37 PM

Hi @Håkon L, was Jason Lightfoot's answer helpful? If so, please click the "Accept" button at the bottom of their answer. Or if you still have questions, add a comment and we'll continue the conversation.

If we haven't heard back from you within 3 business days we'll auto-accept an answer, but you can always unaccept and comment back to reopen your question.

0 ·

Answer 1 · 2022-10-10T13:01:32Z

Jason Lightfoot answered Oct 10, '22 Jason Lightfoot edited Oct 10, '22

Define your parts, processes and equipment capability in tables as you would in a process planning database and use the tables to determine where next to go. I wouldn't use ports if it was even moderately complex.

Also consider decoupling your process definition from the equipment by the use of operation numbers/IDs and a capability lookup of the equipment. That way your next destination can be the a choice between multiple machines that are capable of a given operation on a part, and you can choose the one that is expected to start the earliest or some other criterion.

· 4

Håkon L commented · Oct 10, 2022 at 01:27 PM

Thank you so much, Jason! Your suggestion sounds promising with regards to what I am trying to make, and it seems like it is much simpler to work with than how I thought of doing this. So I will have to read up on the use of tables, and perhaps look for someone who has done something similar. If, you or anyone else knows of some earlier posts/videos/etc where this kind of use of tables is done, it would also be appreciated greatly.

0 ·

Jason Lightfoot ♦ Håkon L commented · Oct 10, 2022 at 01:43 PM

https://answers.flexsim.com/questions/126770/how-to-make-agvs-accumulate.html?childToView=127760#comment-127081

https://answers.flexsim.com/questions/127784/wait-for-agv-before-processing.html?childToView=127835#comment-127834

0 ·

Håkon L Jason Lightfoot ♦ commented · Oct 10, 2022 at 01:58 PM

Not all heroes wear capes, or maybe you do - Jason! Thank you, again! :D

0 ·

Jason Lightfoot ♦ Håkon L commented · Oct 10, 2022 at 02:06 PM

You could start with tables like these:

I would access these tables in three scenarios:

1) To initialize the capability map of each machine

2) To define the components required to initiate an operation

3) When initiating an items production to get the list of steps/operations it has.

By having the capability map on each machine you can duplicate the machine and don't need to update the tables. Just put the machines on a list and pull by capability to do the next operation (a list expression field that refers to the machines capability map).

0 ·

1665410767707.png (33.6 KiB)

question