Improve OnePlan Performance as an End User

Use pre-filters. Ideally, your administrator has made pre-filters required for the portfolio area, so users must select a pre-filter in order for data to load. These pre-filters are server-side filters that significantly reduce the amount of data loaded in the Portfolio, thus increasing performance.

Archive old plans. The archive function moves your plans and associated data into a separate database partition. Archiving old plans removes them from your portfolio, reducing the number of plans that OnePlan needs to load when you open your portfolio.

Use filters when setting up your models so you only pull in the plans you need. Limiting the amount of data that the model needs to load will reduce load times and improve performance.

Use pre-filters. Ideally, your administrator has made pre-filters required for the resource planner, so users must select a pre-filter in order for data to load. These pre-filters are server-side filters that significantly reduce the amount of data loaded in the resource planner, thus increasing performance.

Limit the number of periods of data in your resource planner.

Stick to monthly planning unless you absolutely must plan weekly. In order to enable users to plan on a weekly basis, OnePlan actually stores data daily, which significantly increases the amount of data handled by the system, and, in turn, slows performance. Higher-level financial planning reduces the amount of data stored per cost category and helps improve performance.

If your environment allows you to create custom cost categories or detail rows, refrain from adding too many additional cost categories or detail rows to the financial planner. The more custom cost categories and detail rows you add to the financial planner, the slower your OnePlan performance will be.

Limit the number of periods of data in your financial planner.

Limit the number of tasks in your timesheets. Be sure to delete tasks that you are not recording time to. The fewer tasks in your timesheet, the faster it will load.

Limit the number of tasks in your work plans. The fewer tasks in your work plan, the faster it will load.

Limit the levels of hierarchy in your work plan. 4-5 levels max is best practice, but the fewer layers, the better.

If you find that your project is very large, with a lot of tasks and levels of hierarchy, consider breaking that large project into several sub-projects.

You may also want to consider using Activities to break down tasks into smaller work items rather than creating several tasks and additional layers of hierarchy. Using Activities reduces the number of tasks and layers of hierarchy in your work plan, which helps improve performance.

Do not assign too many resources to tasks. The more resources assigned to a task, the slower the load time.