Utilization For Location Chair
One possible way to achieve this would be to set the state of the location to some value that is not normally within the range of the HC states. For the chair this could be state "3" for example. The time spend in such a state will not appear in the person tables and as such also not count towards any statistics derived from them.
The issue however is that you would have to account for the possibility of the location state changing after the shift has ended (a patient only leaving some time after the shift ends). This would cause the state to be updated to a "normal" state again.
The, in my opinion, better solution is to customize the state chart instead. As a first step, select "Compare hours of the day" in the options. This will make the following changes easier. Next "install" the charts components. This will create a statistics collector and a calculated table in the toolbox.
Open the calculated table and navigate to the "Calculations" tab. Because we changed the chart to "Compare hours of the day", a lot of the needed syntax is already in place in the query. Click on the "Enable direct editing" button. This allows you to directly edit the SQL query the table is performing, though it will also disable the interface to automatically generate the query based on menu options.
Then make the following changes:
- Replace the "toString()" part in the first row with "hour".
Instead of taking the current datetime of the model and converting it to text that displays the full hour, this will convert the time into a numerical hour value.
- Add the clause "WHERE Hour >= 8 AND Hour < 14"
Because "Hour" is now a numerical value, we can apply a condition that it has to be equal or larger than 8 but smaller than 14. In other words, only data from the active shift will be used.
- Remove the last line ("GROUP BY")
The calculated table should only have a single row, not be split by the hour value.
Instead of writing the shift start and end time directly into the query, you can also read them from somewhere else in the model by enclosing the necessary flexscript code in curly braces. In the picture below I read them from the parameter table for example.
The calculated table (and with it the connected chart) will now only take into account the active hours.
Your method should normally work. Once reset the model once the schedule rows should re-order themselves in ascending order based on the arrival time and create the specified quantity of tokens for each row.
It's difficult to say what might be going wrong in your case without seeing your model. Could you maybe share it or at least a screenshot that shows the settings of your source activity?
To subtract the times from each other you have to convert them back into number values.
Are you using a calculated table because you want to use the data in a dashboard chart? Because if not, adding the process time in a fourth column to the TrackTime table, together with the OutTime, might be easier.
Note: In future, please create a new post for questions that don't directly belong to the original topic of the current one. Otherwise it's difficult for other users to find answers to these questions if they are buried in comment chains.
