AnsweredAssumed Answered

OWB Performance and Best Practice For Schedules

Question asked by Owen_R on Nov 16, 2011
Latest reply on Nov 28, 2011 by Robert Ensinger

We recently had an issue where a PM was unable to save their project back to Clarity from OWB - changes would simply not show when the plan was reopened and there were no errors either in OWB or the logs.

On investigation we found it had 17 baselines :rolleyes:- we export all baselines to the scheduler and not just the most recent one - and after removing a couple of the redundant ones the issue resolved itself. However this got us thinking about best practice for schedules and how to improve performance.

I was wondering if anyone had any hints, tips or experience to share in terms of keeping OWB performance as quick as possible - either from a Clarity global perspective or the schedule level?

So far, things I've gleaned from here include:

[*]Only add the resources you really need to the project team
[*]Only assign those resources to the tasks they really need to work on
[*]Keep WBS levels to no more than 5 or 6 deep
[*]Keep sub-project numbers reasonable
[*]Keep baselines to a reasonable number (is there a documented limit?)
[*]Consider only exporting the most recent baseline to OWB

I appreciate that network speed and the spec of the user's machine also comes into play too. Is there anything else we should be aware of such as implicit limits on the number of tasks/resources? Or any other useful advice?

Thanks in advance