Hello everyone,
We have a customer using PSO Standalone (Version 6.16.) who requires that short-term absences are immediately visible in the system. When a resource reports sick and this is entered in PSO under unavailabilities, the absence does not appear in the Gantt chart until after an import (load file). This is problematic for short-notice absences.
Is there any way to make absences visible immediately?
Thank you!
Best answer by Sachitra_W
Hi
I’m guessing the following is happening here,
It is likely that the CHANGE files do not include the source update entities, which means the synchronization from the Planning workspace to the Scheduling workspace is not taking place. In contrast, the daily LOAD file does include these source update entities, which is why the absences become visible only after a LOAD.
To explain further: since you are using PSO Standalone, absence records are created in the Planning workspace under Planning → Resource Data → Unavailabilities for the relevant resource. When data is added or updated in the Planning workspace and needs to be reflected in the Scheduling workspace (Gantt chart), a scheduling input file must be sent to PSO . This could be even a simple time update CHANGE file that includes the source_data and source_data_parameter entities.
You can verify this by comparing the payloads of the LOAD and CHANGE files. The LOAD file will most probably contain elements similar to the following to pull planning data into the Scheduling workspace, whereas the CHANGE files most likely do not.
<Source_Data>
<source_data_type_id>RAM</source_data_type_id>
<sequence>1</sequence>
<source_dataset_id>Demo/source_dataset_id>
</Source_Data>
<Source_Data_Parameter>
<source_data_type_id>RAM</source_data_type_id>
<sequence>1</sequence>
<parameter_name>rota_id</parameter_name>
<parameter_value>Demo-Rota</parameter_value>
</Source_Data_Parameter>
To overcome this you can include the same source_data and source_data_parameter records found in the LOAD file to the CHANGE files.
+3Can you not create a private activity that would show against the Technician for when they are planned to be absent? This would show on the Gantt chart immediately and ‘block’ the technicians time from attracting any other planned work.
+5Hi
I’m guessing the following is happening here,
It is likely that the CHANGE files do not include the source update entities, which means the synchronization from the Planning workspace to the Scheduling workspace is not taking place. In contrast, the daily LOAD file does include these source update entities, which is why the absences become visible only after a LOAD.
To explain further: since you are using PSO Standalone, absence records are created in the Planning workspace under Planning → Resource Data → Unavailabilities for the relevant resource. When data is added or updated in the Planning workspace and needs to be reflected in the Scheduling workspace (Gantt chart), a scheduling input file must be sent to PSO . This could be even a simple time update CHANGE file that includes the source_data and source_data_parameter entities.
You can verify this by comparing the payloads of the LOAD and CHANGE files. The LOAD file will most probably contain elements similar to the following to pull planning data into the Scheduling workspace, whereas the CHANGE files most likely do not.
<Source_Data>
<source_data_type_id>RAM</source_data_type_id>
<sequence>1</sequence>
<source_dataset_id>Demo/source_dataset_id>
</Source_Data>
<Source_Data_Parameter>
<source_data_type_id>RAM</source_data_type_id>
<sequence>1</sequence>
<parameter_name>rota_id</parameter_name>
<parameter_value>Demo-Rota</parameter_value>
</Source_Data_Parameter>
To overcome this you can include the same source_data and source_data_parameter records found in the LOAD file to the CHANGE files.
What’s proposed by
However, Source_Data and Source_Data_Parameter entities should be added to the time updates and/or to the changes that are not time critical. They shouldn’t be used in time critical change inputs such as appointment requests. When those 2 entities are in the Change XML, Input Manager should check Planning database for changes and it can have an overhead on appointment response times.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
