When using the 23R2 Dispatch Console for manual resource assignment for a customer who does not use PSO and has 4000 resources, is it advisable to use multiple datasets? What advantage would the use of multiple datasets bring without PSO? Is there is a concern that so many resources under one dataset would cause performance issues in the Dispatch Console even without using PSO? Couldn’t filters on Resource Group and Region sufficiently limit the number or resources hitting the Dispatch Console even with all 4000 resources in one dataset?
Question
Dispatch Console Dataset Limitations
+25Even without PSO I would definitely use multiple datasets to avoid performance issues. How are these 4,000 resources split - countries/regions/business units, etc.? How many Service Organizations or sites are you using or planning to use? How many resources would a dispatcher typically be responsible for?
Thanks Alexander,
Those 4,000 resources are for Crown, all in the USA, split across 73 “branches” each of which is a site, and those branches are grouped into 10 regions. Each branch/site handles its own dispatch of around 50 technicians. Reframing my questions I would ask, what is a recommended maximum number of resources per dataset when not using PSO? And to understand the potential performance impact, why would a dispatch console that is filtered to show only a few dozen resources suffer a performance problem even with an underlying dataset of thousands of resources?
+17
+4Hi
Do you have an update on the benchmark numbers for Dispatch Console?
There is a situation where the customer is experiencing a visibility issue in the Gantt when “Hide non-working time” is enabled. However, this happens only in their Production environment but not in any of the other lower environments which are in the same version, 24.1.5. Client framework versions are also the same (24.1.12). The assumed cause for this issue is the high amount of data available in their Prod compared to that of other environments. So, they would like to know the number of activities and resources that can be loaded to a single dataset.
+17Hi @Thanuja,
Benchmark exercise is still ongoing. What you are describing however needs to be handled through a support case. Is there such a support case if so we should investigate the issue and see whether it is related to performance or not. I dont think it sounds like a performance issue if the gantt is not struggeling to load data , but that rather you are experiencing some kind of problem with the Hide working time.
+4Hi
Thank you for the response. There is indeed a support case raised by a customer. I have already initiated discussions with Scheduling and Framework Product Development teams. Their recommendation was to upgrade to the latest version as some improvements have been done to hide non-working time algorithm since 24R1 SU5 and it could solve this issue.
+9Hi
Do you have any benchmark values for a recommended maximum number of resources and activities or a combination for a dataset for manual scheduling with PSO.
If we have more datasets to streamline resources and dispatchers to work with less number of activities per dataset, will that make PSO slower? Is it better to use less datasets with filters such as Region, Delivery Units?
+25Hi
Do you have any benchmark values for a recommended maximum number of resources and activities or a combination for a dataset for manual scheduling with PSO.
If we have more datasets to streamline resources and dispatchers to work with less number of activities per dataset, will that make PSO slower? Is it better to use less datasets with filters such as Region, Delivery Units?
What order of magnitude would you need? With PSO’s “APPOINTMENT” process type the recommendation already goes to a max of 35,000 activities, that would work for MANUAL as well.
+9Hi
Do you have any benchmark values for a recommended maximum number of resources and activities or a combination for a dataset for manual scheduling with PSO.
If we have more datasets to streamline resources and dispatchers to work with less number of activities per dataset, will that make PSO slower? Is it better to use less datasets with filters such as Region, Delivery Units?
What order of magnitude would you need? With PSO’s “APPOINTMENT” process type the recommendation already goes to a max of 35,000 activities, that would work for MANUAL as well.
I assume, It would be around 40000/50000 activities. Working on exact figure. If we have more datasets in Region based (then will be around 20/30 datasets), then will it make some performance issue due to the many datasets?
+25Hi
Do you have any benchmark values for a recommended maximum number of resources and activities or a combination for a dataset for manual scheduling with PSO.
If we have more datasets to streamline resources and dispatchers to work with less number of activities per dataset, will that make PSO slower? Is it better to use less datasets with filters such as Region, Delivery Units?
What order of magnitude would you need? With PSO’s “APPOINTMENT” process type the recommendation already goes to a max of 35,000 activities, that would work for MANUAL as well.
I assume, It would be around 40000/50000 activities. Working on exact figure. If we have more datasets in Region based (then will be around 20/30 datasets), then will it make some performance issue due to the many datasets?
In that case I would reach out to your IFS account executive to create a proper sizing based on the amount of data. You also need to consider workbench users for this.
+9Hi
What does an activity means? is it only an assignment of a request task? Or, if there travel to and from components associated with an assignment to technicians, does that mean three activities?
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.