Problem managing operators with process flow & 3D Model & parameter

Question

question

Carmen F asked Mar 09 2023 at 12:38 PM Carmen F commented Mar 16 2023 at 1:02 PM

Problem managing operators with process flow & 3D Model & parameter

Hello,

I am using the process flow to control the operators as a resource referenced to 3D object. The quantity of this resource can be variable so it is defined by the "OP" parameter (see example: Operators_PF_Parameter_OK.jpg) My problem comes when I set the value of the parameter to 0, because the process flow logic still acquires the operator created in the 3D model and I don't know how to avoid it. Any suggestion to control this particular case?

I have attached a model with an example: Dummy_Operators_PF_Parameters_v01.fsm

Thanks in advance.

Software Version:

FlexSim 23.0.0

process flow operators parameter

operators-pf-parameter-ok.jpg (169.5 KiB)

dummy-operators-pf-parameters-v01.fsm (58.5 KiB)

______

Cookie preferences

Your privacy is important to us and so is an optimal experience. To help us customize information and build applications, we collect data about your use of this site.

May we collect and use your data?

Learn more about the Third Party Services we use and our Privacy Statement.

Strictly necessary – required for our site to work and to provide services to you

These cookies allow us to record your preferences or login information, respond to your requests or fulfill items in your shopping cart.

YES

Improve your experience – allows us to show you what is relevant to you

These cookies enable us to provide enhanced functionality and personalization. They may be set by us or by third party providers whose services we use to deliver information and experiences tailored to you. If you do not allow these cookies, some or all of these services may not be available for you.

YES

NO

Customize your advertising – permits us to offer targeted advertising to you

These cookies collect data about you based on your activities and interests in order to show you relevant ads and to track effectiveness. By collecting this data, the ads you see will be more tailored to your interests. If you do not allow these cookies, you will experience less targeted advertising.

YES

NO

Are you sure you want a less customized experience?

We can access your data only if you select "yes" for the categories on the previous screen. This lets us tailor our marketing so that it's more relevant for you. You can change your settings at any time by visiting our privacy statement

Your experience. Your choice.

We care about your privacy. The data we collect helps us understand how you use our products, what information you might be interested in, and what we can improve to make your engagement with Autodesk more rewarding.

May we collect and use your data to tailor your experience?

Explore the benefits of a customized experience by managing your privacy settings for this site or visit our Privacy Statement to learn more about your options.

Answer 1 · 2023-03-09T14:52:44Z

Sebastián Cañas answered Mar 09 2023 at 2:52 PM Carmen F commented Mar 16 2023 at 1:02 PM

Hi @Carmen F ,
I suggest you to use Jason Lightfoot's answer here. With Process Flow you can reference a Dispatcher with the Create Task Sequence activity. With these activities you can also replace Acquire/Release activities.

Hope it helps!

dummy-operators-pf-parameters-v01_SC.fsm

dummy-operators-pf-parameters-v01-sc.fsm (47.2 KiB)

· 7

Carmen F commented · Mar 14 2023 at 1:36 PM

Hello @Sebastián Cañas,

Thanks for your answer but I wouldn't want to use a dispatcher because the acquisition of the resource in the real model has a certain complexity and is given by the application of some priority rules that I control through process flow. I have attached a new dummy including this aspect. Dummy_Operators_PF_Parameters_withPriorityRules_v01.fsm

In the example, depending on label "Type" of the item and the values in the global table "Operator_Priority", it is selected the operator profile to be acquired (Example: { 2,1} --> Firstly, it will be looking for OP2 and secondly for OP1). In addition, depending on the schedule, it will choose an operator from one shift or another but it is not relevant at this point.

If the first operator profile requested is not available, it will look for an operator from the second profile and so on. It will go through a loop until it finds a free one. Once the operator is acquired, the task sequence is created.

In the new attached example this logic is working, but I still don't know how to handle the case where the value of the parameter that controls the number of operators in a profile is =0. Example_malfunction_withParameter0.jpgIn this case, no operator of that profile should be acquired.

Any suggestions how to solve it using this approach or using another?

Thanks in advance.

0 ·

example-malfunction-withparameter0.jpg (224.6 KiB)

dummy-operators-pf-parameters-withpriorityrules-v0.fsm (104.1 KiB)

Jason Lightfoot ♦♦ Carmen F commented · Mar 14 2023 at 1:45 PM

Push your available operators to a list and pull them off using an ORDER BY clause that references the expression:

 puller.orderProfile.indexOf(value.operatorID)

which assumes the puller has an array label containing the operator profile , where the values match those stored on the operators as the label 'operatorID'.

0 ·

Sebastián Cañas Jason Lightfoot ♦♦ commented · Mar 14 2023 at 2:22 PM

@Carmen F ,

Besides Jason's suggestion, I made a demo model that seems to work! I'll explain the steps I did:

Add your operators to an objects group.
Reference the Group you'd created as PF Resource.
Create the Parameter with the Lower Bound as 0, reference the Group you'd created and select the operation Delete and Copy Group Members in the trigger On Set.
Create a Model Triggers OnModelReset. I reuse the code of Set Number in People Group that you find also in the operations of the trigger On Set of the parameters. I made a few changes, set the variable newValue as the parameter you set before and the variable group as the group you'd created.

ParameterOPZero_PF.fsm

0 ·

parameterzero-pf.gif (3.1 MiB)

parameteropzero-pf.fsm (39.3 KiB)

Show more comments

question