Limit monthly processor availability to value in global table

Question

question

Pieter Cecat asked Mar 12 2017 at 1:29 PM Pieter Cecat commented Mar 16 2017 at 1:54 PM

Limit monthly processor availability to value in global table

Hi fellow FlexSimmers!

I am working on a model (time unit: hours) to simulate a production plan. I have 1 processor and would like to limit its capacity each month (1 month=720 hours) to the sum of 2 values (regular + overtime) defined in a global table (see below):

CAPACITY	1	2	3	4	5	6
Regular	480	480	480	480	480	480
Overtime	0	45	0	120	0	0

For instance:

During the first month (0-720 hours), the processor is available for 480 + 0 = 480 hours. Then it becomes unavailable for processing until the start of the second month (720-1440 hours).

During the second month, the processor is available for 480 + 45 = 525 hours, thus from 720 (end of first month) till 1245 hours, after which it becomes unavailable again until the start of the third month.

Et cetera.

I was thinking of using process flow here but assume there is an easier way for doing this.

Any hints? All help would be appreciated.

Have a good afternoon everyone!

Kindest regards

Pieter

Software Version:

FlexSim 16.0.7

process flow global table processor capacity

· 2

______

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 · 2017-03-13T14:56:55Z

Kari Payton answered Mar 13 2017 at 2:56 PM

@Pieter Cecat

One way you can do this without using process flow is to use a custom time table that is linked to an excel file. Use excel to calculate the start time of the breakdown and the duration of the breakdown. Then link it to a timetable that is referenced by the processor.

1. In the excel file, I made a column to calculate the scheduled down time for the processor. So from that chart above "720 - working hours" for each month. Then for the information needed by the time table, I took the cumulative monthly time - scheduled down to get the start time of the scheduled down. The duration or the breakdown is the same as the scheduled down time.

2. Link the excel file to a time table. Add a new time table toolbox -> add -> Time Table. On the time table, click the button in the top right corner that says "add table to MTEI". Now in your toolbox you should see a reference to Import/Export Excel. There you add the file path for your excel table.

Hope this helps!customscheduleprocessor.fsm

stateprofile.png (32.0 KiB)

customscheduleprocessor.fsm (19.6 KiB)

Answer 2 · 2017-03-13T16:38:55Z

Pieter Cecat answered Mar 13 2017 at 4:38 PM Pieter Cecat commented Mar 16 2017 at 1:54 PM

@Kari Payton

Thanks for your quick and clear reply! I am following your logic and tried to do as you said. However, I cannot seem to add an excel file to my FlexSim. Everytime I push the 'add table to MTEI' button, it returns the following error in the system console:

exception: Exception caught in flexscript execution of VIEW:/active/TimeTable Parameters2843403040/tabcontrol/Table/Add Table to MTEI>OnPress line 9 instruction 34. Discontinuing execution. exception: Exception caught in TreeNode::callMemberFunction() flexscript execution VIEW:/active/TimeTable Parameters2843403040/tabcontrol/Table/Add Table to MTEI>OnPress c: VIEW:/active/TimeTable Parameters2843403040/tabcontrol/Table/Add Table to MTEI

Any idea what I am doing wrong?

Thanks again for your assistance, appreciate it.

Regards

Pieter

· 6

Kaspar Chabot commented · Mar 14 2017 at 12:32 PM

Pieter,

If you don't need to change the table very often you don't really need an Excel import/export. You can simply use the calculations the way @Kari Payton made them in Excel and copy paste those values into a TimeTable for the Processor. In my experience, most of the time those FlexScript errors occur when you make a small mistake in setting some parameters or you refer to something that doesn't exist.

1 ·

Pieter Cecat Kaspar Chabot commented · Mar 14 2017 at 12:49 PM

Hi @Kaspar Chabot

That is what I did for now but unfortunately I need to import large tables from Excel to several Global Tables so then it might come in handy to use the Excel Interface...

Regards

0 ·

Kari Payton commented · Mar 13 2017 at 4:44 PM

@Pieter Cecat post your model and a FlexSim developer can look at it @Sam Stubbs. You can also try deleting the object and the treenode, creating the object again, and restarting the program. Sometimes this works for me but I don't know how to solve flexscript errors.

0 ·

Pieter Cecat Kari Payton commented · Mar 13 2017 at 4:53 PM

The Excel Import/Export Interface in general does not seem to work as it also returns an error when I try to add an excel file to a global table, eventhough I was able to do this some months ago (on the same computer and FlexSim version). It would be nice if someone can tell me what is wrong. I have a legal version of Excel installed on my computer so that should not be the issue.

Thanks for your help!

Regards

uncertain-quality-cores.fsm

0 ·

uncertain-quality-cores.fsm (53.6 KiB)

Logan Gold ♦♦ Pieter Cecat commented · Mar 15 2017 at 7:00 PM

@Pieter Cecat,

I'm not sure what happened, but it looks like the ExcelAuto node in your model's tree was changed to be a different node type. So when you try to add a table to the Excel Import through a Time Table or even try to use the Excel interface, FlexSim can't make the necessary changes in the tree that are needed to get the importer/exporter working correctly.

To fix the issue, I deleted the ExcelAuto node in the tree and opened the Excel interface again so that node would be recreated. This seems to have fixed the issue and I am including a fixed model file in this comment (uncertain-quality-cores.fsm).

Let me know if it still doesn't work for you or if it does work and then stops working at a future date. If the latter occurs, let me know what you were doing before the issue reoccurs if you can.

1 ·

uncertain-quality-cores.fsm (54.0 KiB)

Show more comments

question