Numpty
Newbie
Karma: 0
Posts: 4
|
 |
« on: December 15, 2010, 08:44:37 am » |
|
Hi All, forgive me if this has been asked before (I have searched): Using V7.1 and SQL Server 2008 we are having performance issues in generating work orders from PM and changing status on parent work orders. We've set up routes at child work orders and have Job Plans with multiple tasks so a parent WO could have 100+ child WOs and potentially many task WOs for each. In one example we have 62 child work orders each with 6 tasks = 61 + (61 x 6) + 1 = 428 individual work orders. Completing the WO takes nearly 4 minutes! Generating the WOs also takes a very long time although running in background definately improves performance for this. So I suppose my question should come down to initial setting up.... did we do the right thing by splitting our PMs down to individual assets and then having job plans split into many tasks? We are generating 1000s of work orders each month and we anticipate this growing over the next few months. If this remains a problem we could combine the job tasks into one but this is not our preferred solution. Any help or advice gratefully received.
|
|
|
|
|
Logged
|
|
|
|
|
Ethen
|
 |
« Reply #1 on: December 16, 2010, 02:05:47 pm » |
|
do you try to create WO's from PM's automatically using cron task or manually create WO's from PM.
|
|
|
|
|
Logged
|
regards,
Ethen...
|
|
|
Numpty
Newbie
Karma: 0
Posts: 4
|
 |
« Reply #2 on: December 28, 2010, 10:16:16 am » |
|
Currently we are doing this manually. Whilst I understand a cron task can be done when things are quiet, it will not solve the problem - particularly the slow updates on WO status i.e. completing PM work orders that cover multiple assets and tasks.
|
|
|
|
|
Logged
|
|
|
|
|
Ethen
|
 |
« Reply #3 on: December 28, 2010, 01:17:50 pm » |
|
changing status of a WO changes the status of the all the child WO and task WO. Having so many WO might be an issue. Does changing status of simple WO takes this much of time.
|
|
|
|
|
Logged
|
regards,
Ethen...
|
|
|
Numpty
Newbie
Karma: 0
Posts: 4
|
 |
« Reply #4 on: January 01, 2011, 04:09:28 pm » |
|
Without setting up logging to record the events and times (which would itself take database time and resources) it is difficult to say. I suspect it is a simple percentage i.e. 240(seconds) / 460 (WOs) = approx 0.5 seconds per record. I know Maximo is doing much more than updating the record but it still seems to be a long time. I would expect 10s / 100s of record updates to be done per second assuming the hardware is OK.... and ours certainly is!
|
|
|
|
|
Logged
|
|
|
|
|
Ethen
|
 |
« Reply #5 on: January 04, 2011, 12:57:12 pm » |
|
Never did in so much of bulk so dont know how much time it takes... but yeah.. Maximo does a lot of other things like freeing up any resource, update the PM records, labor records and also children records..
|
|
|
|
|
Logged
|
regards,
Ethen...
|
|
|
MaximoEngineer
Newbie
Karma: -1
Posts: 3
|
 |
« Reply #6 on: January 12, 2011, 11:19:22 pm » |
|
With that high of a number of workorder records getting touched in that manner, you might look at using the Maximo Database Config. App to create an index for the WORKORDER table ISTASK column. Also might look at running SQL Server index Reorganize routine on the workorder indexes on a regular basis with that volume.
Note: I am not a 7.1 or SQL Server Expert (Im currently spending most of my time on 6.2 and Oracle)
|
|
|
|
« Last Edit: January 12, 2011, 11:22:39 pm by MaximoEngineer »
|
Logged
|
|
|
|
Numpty
Newbie
Karma: 0
Posts: 4
|
 |
« Reply #7 on: February 10, 2011, 06:41:37 am » |
|
Thank you for the advice. We'll certainly look at the additional index though I note there are many indexes already set up. We are currently reviewing the need to have Parent / Child / Task work orders. The concept is a good one which allows us to trace every task undertaken on every asset but the downside is the sheer volume of information - the database is growing at an alarming rate.
|
|
|
|
|
Logged
|
|
|
|
|
WorldTraveller
|
 |
« Reply #8 on: March 10, 2011, 05:44:25 pm » |
|
You might consider using tasks instead of children work orders. Since tasks are really work orders (they live in the workorder table), I am not sure if this strategy will help or not. As someone else suggested, appropriate indexes may help.
|
|
|
|
|
Logged
|
|
|
|
|
BrandonMark
|
 |
« Reply #9 on: January 12, 2012, 07:28:30 am » |
|
Within a Change, the system offers a "Add Work Order" feature which enables any number of sub-tasks (Work Orders) related to a selected Change to be entered.
|
|
|
|
|
Logged
|
|
|
|
|