question

Nicolas M6 avatar image
0 Likes"
Nicolas M6 asked Nicolas M6 commented

how to manage Maintenance on release ?

Hi, I would like to set up room maintenance when the patient has finished in the room (on realese).

Approach 1: I tried to create a token that solicits staff and performs a time. In this case, I have problems:
1) the patient still occupies a room and there is an error message when the patient token is destroyed.
2) the created token disappears with the patient token

Approach 2: I found that it is possible to use condition maintenance in people objects. Perfect! However, the trigger of the On Release subflow is also called when the room changes state due to the time table. At 7 am the room becomes available and maintenance is called. What is not desired.

Can you refer me to the best method and how to
- Correct the error of approach 1 (error message when destroying the token)
- Correct the unintended effect of approach 2 (maintenance not desired when changing state due to time table)

the two approaches in the attached models. Thanks in advance

MaintenanceIndependanteDuPatient_Approach_1_Create_token_for_maintenance.fsm

MaintenanceIndependanteDuPatient_Approach_2_MaintenanceCondition.fsm

FlexSim 20.1.1
resourcemaintenancepeople
· 3
5 |100000

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

tannerp avatar image tannerp commented ·

Hi @Nicolas M6,

I'm not sure that this is an answer, but it's an idea. Since you are assigning the "RoomToMaintain" label in the "Release Location Resource QUERY" activity, you could create a token with that label that will acquire the necessary resources to perform the maintenance. Would something like that work? I've created an example that creates a token in a Start activity, but it could create a token at the beginning of the maintenance routine flow.

approach 3 suggestion.fsm

0 Likes 0 ·
Nicolas M6 avatar image Nicolas M6 tannerp commented ·

Hi @tanner.p, thanks for your answer.

what you suggest is what I suggest in approach 1. Let's run the model attached (approach-3-suggestion-completed) and you will see the problems:
1) The token created will disapear at the same time that the patient is destroyed (and the maintenance routine is interrupted)
2) An error message appears

Certainly, I make something wrong, but I'm curious to know how to make it right

approach-3-suggestion-completed.fsm

0 Likes 0 ·
Matthew Gillespie avatar image Matthew Gillespie ♦♦ commented ·

Maintenance should not be happening when a time table releases the location. This is an oversight and a bug. Thanks for pointing it out.

0 Likes 0 ·

1 Answer

·
Nicolas M6 avatar image
1 Like"
Nicolas M6 answered Nicolas M6 commented

in approach 2, I corrected as follows: I
- moved the maintenance routine into a general flow process (not error message anymore)
- make a request in the "Rooms" resource (value = puller.Room) to find the same room as before
- set a high priority (200) so that the request has priority over other patients who also wish to use this room



approach-3-suggestion-completed-solution.fsm



· 2
5 |100000

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

Leah R avatar image Leah R commented ·

Hey @Nicolas M6 ! Thanks for sharing with us :) Were you working on an OR modeling by chance ? Or an inpatient service ?

0 Likes 0 ·
Nicolas M6 avatar image Nicolas M6 Leah R commented ·

Hi @Leah R. I work for Procsim, Switzerland. I work to conceptualize and tests healthcare systems. Around patients flows and logistics flows.

0 Likes 0 ·

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

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