We have 360 scheduling Jobs (Create and Change) which are executing in 8 to 15 min interval to plan the work order scheduling. Usually, these Jobs takes 20-30 sec of time to execute but sometimes, these are taking 1-2 min of time.What could be the cause of this performance issue?
If you look at the XMLs generated, are these particularly large? Do you have events triggering for specific things on a work order that might cause the delay?
anmise wrote:
If you look at the XMLs generated, are these particularly large? Do you have events triggering for specific things on a work order that might cause the delay?
How Events on Work order could impact on Such Jobs? Some events are planned on the work orders (One event to finish the work order which have already invoiced). Work orders are also being updated by the Integrations.
Hello,
We are currently using IFS Apps 8 alongside 360.
Each day starting at 00:01 we initiate the task Send Data For Schedule with input type LOAD which effectively sends everything across to 360. This task is currently taking around 6 hours to complete and has taken longer incrementally over the past 6 months without the volume of data such as work orders changing too much month on month. We need to reduce the time taken as it is impacting on those engineers who start at 6am now. However the issue appears to be with the core IFS procedure, so not sure what can be done.
During the day, we then have the task Send Data For Schedule with input type CHANGE which only sends over the changes since the full load. This takes from 1 to 3 minutes to complete.
In addition, we then have Process Plan from 360 Scheduling which is initiated every minute by IFS.
I believe this is the recommended setup by IFS for this plans to be initiated.
Is there anyone else out there using IFS and 360, and having performance issues as highlighted above on Apps 8?
Regards
Shaun
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.