Flexsim job shop problem

Question

question

mark zhen asked Apr 22, '24 Jeanette F commented May 16, '24

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

5 |100000

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

Joerg Vogel commented · Apr 22 at 08:34 PM

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

0 ·

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

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

0 ·

mark zhen mark zhen commented · Apr 24 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 at 06: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 ·

Answer 1 · 2024-04-24T15:18:50Z

Felix Möhlmann answered Apr 24, '24 mark zhen commented May 9, '24

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

5 |100000

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

mark zhen commented · Apr 25 at 06: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 at 06: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 at 08: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