Representing Operator Vacations

Question

question

Noah Z asked Jun 14, '16 Jeanette F commented Jan 29, '24

Representing Operator Vacations

I can use MTBF/MTTR and Time Tables as two ways of taking operators off of availability to represent vacations taken. However, I don't know of a way to to use either of those while satisfying the following operator logic needs:

Avoid taking vacation concurrently with other operators connected to the same dispatcher (Example: If I have two operators trained on a piece of equipment they would coordinate in real life to prohibit concurrent unavailability)
Only take a single two week vacation once per given year but have it be randomly timed (except for respecting the caveat of #1.)

Does anyone have a clever way they have tackled representing operator vacations? Even if a technique you've used doesn't meet my two specifications I'd be interested to hear how vacations have modeled by other users/developers.

Software Version:

FlexSim 16.0.1

operator time break down vacation

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.

Answer 1 · 2016-06-14T17:41:14Z

Adrian Haws answered Jun 14, '16 Jeanette F commented Jan 29, '24

Noah,

This is a method to use in order to prohibit more than one operator to be scheduled down at the same time, although it may not be ideal for your situation.

In the attached sample model, I used two Operators connected with a Dispatcher. The first operator transported items to the Processor from the Source, and the second was utilized to process items. I made a Group with the two operators, and used this group as the members of the MTBF/MTTR.

The next step is to add a Sub Flow where I acquired a Resource (the group of operators), entered a Zone with a max content of 1 (to restrict the number of operators on break), then had a Delay Task Sequence activity set to the desired amount of downtime, and to the state of “scheduled down.”

I then referenced the sub flow from the Down Time picklist in the MTBF/MTTR window.

With the parameters in this model (which include fairly frequent breakdowns) one operator can be off right after the other, but never two at the same time.

Hope this helps.

model-screenshot.png (69.9 KiB)

delay-screenshot.png (12.3 KiB)

down-time-screenshot.png (22.3 KiB)

mtbfmttr-sample-model-4.fsm (23.5 KiB)

· 2

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.

Flexinator commented · Jan 27 at 06:30 PM

Hi @Adrian Haws , i am using your solution approach at the moment. In your model i get the error: exception: FlexScript exception: Array index out of bounds at MODEL:/Tools/MTBFMTTR/vacation>variables/downfunction

what is that mean?

0 ·

Jeanette F ♦♦ Flexinator commented · Jan 29 at 04:46 PM

Hello @Flexinator,

Great work on using the forum to find solutions for your models. If you have a question about a post that is old and has already had an accepted answer, I recommend starting a new post and referencing this post in your new one.

0 ·

Answer 2 · 2016-06-14T19:57:50Z

Adrian Haws answered Jun 14, '16 Adrian Haws edited Jun 14, '16

Here is a way I went about the random two-week vacations (albeit with different time units).

Similar to the first answer, I created a separate process flow with a Schedule Source activity (with whichever statistical distribution is best for the arrivals), acquiring a Resource (the group of operators), entering a Zone with a Max Content of 1 and a Delay task sequence set to the "scheduled down" State and the entered value for Delay Time as preferred.

(See updated sample model attached).

two-week-vacation-screenshot.png (151.5 KiB)

mtbfmttr-sample-model-5.fsm (29.0 KiB)

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.

question