question

Håkon L avatar image
0 Likes"
Håkon L asked Andrew O commented

Setting up non-unique activities

Hi, so I want to add an activity called "addToStorage" in my simulation, this activity is not unique and is carried out at several places in my production line, there are in total 6 instances.

What I am wondering is - What is the best way to set this up without having to make several addToStorage instances like addToStorage1, addToStorage2 and so on?

I could set this activity up as a processor, but they should have unique names - right?
One lastquestion - Is this something that is better done in a processFlow?

In advance, thanks for the help!


Sincerely
Flexsim-nooblet



FlexSim 22.2.2
non-unique activitiestheoretical
· 2
5 |100000

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

Joerg Vogel avatar image Joerg Vogel commented ·
Because you have used keywords like instances and activity, I had assumed you are doing this in Process Flow already. And the Answer is "YES!", do this in Process Flow as a sub flow or an instanced process.
0 Likes 0 ·
Andrew O avatar image Andrew O commented ·

Hi @Håkon L, was Jason Lightfoot's answer helpful? If so, please click the "Accept" button at the bottom of the one that best answers your question. 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 Likes 0 ·

1 Answer

Jason Lightfoot avatar image
0 Likes"
Jason Lightfoot answered Jason Lightfoot edited

The fact that you seem concerned about the names is worrisome, since it sounds like you are using them in expressions. In my opinion best practice is to avoid using the names and use pointer values instead since they are preserved regardless of name changes and other more powerful occasions (see below). Also you can have the same name object in the model as long as the path is different - so in a different container. More on that later too.

You have the option of using Templates to manage the object and have code local to it (triggers etc.) or you can have it instantiate process flows (dynamically via Subflows or via Object Process Flows) which then have a common codebase. Or you can use both of these at the same time. A template instance will receive changes you make to the Template master automatically. You can also override individual properties on the instances.

Think about the references to other objects that your 'addToStorage' object will use. Does it make sense to cluster them together in a container to make a cell? If so, you can put them all in a plane object used as a container. A key feature of FlexSim is that when you copy/paste objects as a set, any references (object pointer labels) they have you each other are preserved for the copied objects - meaning you don't have to change them. So copying the container object should be the only action needed to create a new working cell. In version 23.0 this key feature will also be true for instantiated instances of Templates that are a collection of objects contained in a plane.

5 |100000

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