This article describes methods you, as an end user, can use to help improve OnePlan performance.
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.
This article details the actions you can take as an administrator to help improve OnePlan performance.
As a OnePlan administrator, you need to understand that almost every setting has a consequence. You must configure your OnePlan environment carefully to ensure that you do not hinder system performance. Following are recommendations from the OnePlan team to help improve and maintain OnePlan performance that you can implement as an administrator.
There are also actions that your end users can take to help OnePlan performance as well. See Improve OnePlan Performance as an End User for more information.
Set up Resource Managers. This will reduce the number of resources loaded into the resource planner for those users with the RM role. This will increase loading speeds for the resource planner.
Follow the lowest-level permissions model. This means that you should assign your users the lowest permissions possible. Most users should be Team Members and Contributors. This approach cuts down on clutter and risk.
Review the schedules and automations that you have configured for your environment. Remove what you do not need.
Avoid scheduling an automated function to begin at midnight Pacific time. This is a very common time slot for automations to be configured, so there may be some traffic that will slow down performance.
Limit the total number of fields you configure in your OnePlan environment. Only configure the fields that you need. Having a lot of fields in your environment can slow down OnePlan performance due to the large amount of data that it needs to load when there are a lot of fields.
Limit the number of choices you have configured for a given choice field. Having a lot of choices in a choice field can negatively impact OnePlan performance as there is a lot of data that needs to load when interacting with the choice field.
Limit the number of calculated fields in your environment. Having a lot of calculated fields can slow down OnePlan performance as the system needs to run each calculation configured.
Review your calculations to ensure they function as intended. Having bad calculations for your calculated fields can negatively impact OnePlan performance as it will run into errors when the system tries to run bad calculations.
Only run status reports as needed, and no more. Review the Schedule settings for your status reports. Running status reports on a less frequent schedule can help improve performance as there is one less automated function that is running in the background.
Limit the number of snapshot fields in the Snapshot Settings for your status reports. Reducing the number of fields that are snapshotted when a status report is pulled can help improve performance as there is less data being captured.
Minimize cost categories and types in the financial planner.
Limit or do not turn on custom cost categories and detail rows.
Reduce the number of capacity months for your resource plans. The fewer the better. Limiting the number of capacity months in your resource plans reduces the amount of data in your resource plans and helps speed up performance.
Negotiations on all types.
Keep your plan details forms simple. Limit the number of fields that you have in your plan details forms and refrain from creating complicated plan details forms where possible.
Limit the number of format rules configured in your environment. Review the pre-configured format rules and remove the ones that you do not need. Having a lot of format rules can negatively impact performance.
Comments
0 comments
Article is closed for comments.