Hi Bruno
Thanks for all the hard work you've put into MxLoader over the years that has made my work and the work of many other Maximo user much more comfortable.
I have a few issues which might not necessarily be anything to do with MxLoader but which have been observed during it's use.
1. When using the template to upload vehicle mileages (about 149 trains), I've observed that each mileage is loaded very quickly initially around about 10 secs per vehicle (on average), which slows down to over 30 seconds by about a quarter of the way in (after processing about 25-30 vehicles), then finally to well over 3 minutes by mid-way point. Have you seen, been notified, or experienced this before? To see if it might be a memory issue, I even broke them up into 3 batches and run them separately. The performance was exactly the same - despite shutting down the loader template and re-opening it.
2. I've observed that a few of the vehicles takes between 5-11 minutes to run (which affects the average figure above) and usually I get an error messages in the log for them. Usually, these will not have had their mileages updated in the system - except yesterday when they all got uploaded despite the error messages. The attached shows the two common error messages.
3. related to issue #2 above is that the offending vehicles have a different time loaded into maximo to the time on the MxLoader template used for upload - usually plus 1 hour. We usually use '07:30:00' time for all vehicle mileage uploads. When the data is downloaded all vehicles have exactly the same time except for these few vehicles which have '08:30:00' instead.
I'd be grateful if you or any of the forum members here can help me understand what's going on because the net effect is that the upload processes for the 149 vehicles takes at least 2 hours to complete instead of 25 minutes (at an average of 10s per vehicle).
Thanks for you help.
Yinka
------------------------------
Yinka Oludipe
KeolisAmey Docklands Ltd
------------------------------