It is not a good idea to include that much historical data in schedule.

What is the requirement here? Do you need it for some reporting purpose? Is it mandatory for user to see them in schedule or you just need to take out some data for reporting?

Hi Sajith,

Its not for Past ones, we are looking for Future Gantt to visible for 28days.

Currently its restricted to 14days & Planners unable to get the view to assign future jobs in PSO.

We are having more that 20+ Dataset, 1 customer is asign for future visiblity of gantt for 28 days.

Regards,

Shiyaz

Having a 28 day Optimization window is not recommended. 

Earlier you were using a 4 day optimization window + 10 day appointment window to see 14 days shift period. We had to change it due to some performance issues in plan generation. You can go back to this configuration only for the required dataset and add the additional number of days to appointment window. 

But you need to pay attention to total activity count for 28 days. It should not exceed the counts specified in Architecture and Sizing guide for workbench performance. 

Having a 28 day Optimization window is not recommended. 

Is it possible to Keep 4 + 28 , 4 days as optimization & 28 days as Appointment, Will that impact the performance.

And is it possible to set 1 dataset

Hi Sajith,

Can you please comment.

Regards,

Shiyaz

If the total requirement is 28 days, you can use 4 day optimization window+24 day appointment window.

Since this is only for 1 dataset, I don’t think it will affect DSE performance much, but you need to pay attention to total activity count for 28 days because it will impact workbench performance. It should not exceed the counts specified in Architecture and Sizing guide for workbench performance.

You can do it only for a single dataset using FSM Scheduling App Params.  

@Sajith Anushan  can you please share the details of app parms to be updated for same ?