Flexsim job shop problem

Question

question

mark zhen asked Apr 22 2024 at 6:21 PM Jeanette F commented May 16 2024 at 6:14 AM

Flexsim job shop problem

I'm currently building a model for gig production and I'm not sure why my model is having issues. But what I can provide is some preliminary information on modeling.

1. I have 20 orders but my production order is randomly generated.

2. My processing time wants to be set to evenly distribute 1,100, but I am wondering if I can give him a processing time label at the beginning, and then the machine will process according to the processing time label on the item.

But now it seems that my model is not processed as I thought.

random.fsm

Software Version:

FlexSim 22.0.16

job shop

random.fsm (200.2 KiB)

· 4

Joerg Vogel commented · Apr 22 2024 at 8:34 PM

@mark zhen, what do understand under „evenly distributed“?

0 ·

mark zhen Joerg Vogel commented · Apr 23 2024 at 2:41 AM

The frequency of occurrence on a scale of 1-100 is the average occurrence

0 ·

mark zhen mark zhen commented · Apr 24 2024 at 10:58 AM

@Felix Möhlmann @Jason Lightfoot @Kavika F

Hello, I have updated my content, but there is still a problem with the processing order. I don’t know what the problem is.random.fsm

0 ·

random.fsm (194.7 KiB)

Jeanette F ♦♦ commented · May 16 2024 at 6:14 AM

Hi @mark zhen , was Felix Möhlmann'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 comment back to reopen your question.

0 ·

______

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 · 2024-04-24T15:18:50Z

Felix Möhlmann answered Apr 24 2024 at 3:18 PM mark zhen commented May 09 2024 at 4:23 PM

In both your models you use a label ("processtime" and "pt" respectively) to refer to the column from which the process time should be read. In both cases, the values of the labels point to wrong columns or aren't even in the range of the table.

In your first model you have "duniform()" expressions in the "StationAssignments" table. You replaced these with number data without switching the cell nodes out of 'flexscript-mode'. As as result, only 0s are returned when reading from the table. It's probably easiest to just create a new table alltogether.

· 28

mark zhen commented · Apr 25 2024 at 6:29 AM

But I fixed the random seeds and the order of StationAssignments in the new model, and I still can't run the model smoothly. There will be a lot of products that are not labeled smoothly. I want to solve this problem. As for the processing time, my approach is to read a new table and the table content will have the corresponding TYPE and PROCESSTIME. I think this approach should not be done. There will be problems.

0 ·

mark zhen mark zhen commented · Apr 25 2024 at 6:34 AM

In both models, you use labels ("processtime" and "pt" respectively) to reference the fields from which the processing time should be read. In both cases, the label's value points to the wrong column, or isn't even within the scope of the table. (I don't understand where I made this mistake, the settings in the second model)

0 ·

Felix Möhlmann mark zhen commented · Apr 25 2024 at 8:13 AM

When an item is created, a value of 1 is assigned to the "pt" label in Process Flow.

Processor1 uses this label to refer to the table column from which the process time should be read. Column 1 in that table is called "Arrival Time" and only contains 0s though.

I fixed this and the table issue in the attached model and reworked the processor connections.

random_2.fsm

One issue that remains is that the "date" label is missing on the items which the sink tries to read.

0 ·

capture1.png (3.0 KiB)

capture2.png (5.6 KiB)

capture3.png (15.4 KiB)

random-2.fsm (193.2 KiB)

Show more comments

question