--- title: "P6 Optimisation: diagnosis first | Skyhigh PMO" description: "A diagnostic of your Primavera P6: performance, data, configuration and administration. Quick fixes done, a prioritised roadmap, findings you own." image: https://skyhighpmo.com.au/hubfs/website/share-primavera-optimisation.png --- [![Skyhigh PMO, Project Controls Solutions](https://skyhighpmo.com.au/hubfs/raw_assets/public/skyhigh-theme/images/skyhigh-logo-reverse.svg)](https://skyhighpmo.com.au/?hsLang=en-au) - Problems we solve Getting started with P6 - [**Transformation**New installs, upgrades and consolidation](https://skyhighpmo.com.au/transformation?hsLang=en-au) - [**Cloud**Cloud options, costs and the move](https://skyhighpmo.com.au/cloud?hsLang=en-au) Looking after P6 - [**Primavera Optimisation**Diagnostics, future state design and configuration reviews](https://skyhighpmo.com.au/primavera-optimisation?hsLang=en-au) - [**Primavera Support**From roadside help to a race-day pit crew. Choose your crew.](https://skyhighpmo.com.au/primavera-support?hsLang=en-au) - [**Project people**Planners and schedulers, for weeks rather than years](https://skyhighpmo.com.au/project-people?hsLang=en-au) Phase 2 Tools and licences - [**Licensing & Procurement**Licence advice, renewals and new licences](https://skyhighpmo.com.au/licensing-procurement?hsLang=en-au) - [**Oracle products**Learn more about each product](https://skyhighpmo.com.au/licensing-procurement#other-products) - [**Primavera P6**](https://skyhighpmo.com.au/licensing-procurement/primavera-p6?hsLang=en-au) - [**Oracle Primavera Cloud**](https://skyhighpmo.com.au/licensing-procurement/primavera-cloud?hsLang=en-au) - [**Primavera Unifier**](https://skyhighpmo.com.au/licensing-procurement/primavera-unifier?hsLang=en-au) Hidden at launch - [**Oracle Aconex**](https://skyhighpmo.com.au/licensing-procurement/oracle-aconex?hsLang=en-au) Hidden at launch - **Australian innovators' tools**Tools from Australian problem solvers Hidden: no agreement yet Reporting and P6 data - [**Reporting & Integration**Portfolio reporting, and P6 in your data warehouse](https://skyhighpmo.com.au/reporting-integration?hsLang=en-au) - [Insights Hidden at launch](https://skyhighpmo.com.au/insights?hsLang=en-au) - [About](https://skyhighpmo.com.au/about?hsLang=en-au) - [Contact](https://skyhighpmo.com.au/about#contact) [Test us on your issueTest us](https://skyhighpmo.com.au/test-us?hsLang=en-au) Menu Problems we solve Getting started with P6 - [**Transformation**New installs, upgrades and consolidation](https://skyhighpmo.com.au/transformation?hsLang=en-au) - [**Cloud**Cloud options, costs and the move](https://skyhighpmo.com.au/cloud?hsLang=en-au) Looking after P6 - [**Primavera Optimisation**Diagnostics, future state design and configuration reviews](https://skyhighpmo.com.au/primavera-optimisation?hsLang=en-au) - [**Primavera Support**From roadside help to a race-day pit crew. Choose your crew.](https://skyhighpmo.com.au/primavera-support?hsLang=en-au) - [**Project people**Planners and schedulers, for weeks rather than years](https://skyhighpmo.com.au/project-people?hsLang=en-au) Phase 2 Tools and licences - [**Licensing & Procurement**Licence advice, renewals and new licences](https://skyhighpmo.com.au/licensing-procurement?hsLang=en-au) - [**Oracle products**Learn more about each product](https://skyhighpmo.com.au/licensing-procurement#other-products) - [**Primavera P6**](https://skyhighpmo.com.au/licensing-procurement/primavera-p6?hsLang=en-au) - [**Oracle Primavera Cloud**](https://skyhighpmo.com.au/licensing-procurement/primavera-cloud?hsLang=en-au) - [**Primavera Unifier**](https://skyhighpmo.com.au/licensing-procurement/primavera-unifier?hsLang=en-au) Hidden at launch - [**Oracle Aconex**](https://skyhighpmo.com.au/licensing-procurement/oracle-aconex?hsLang=en-au) Hidden at launch - **Australian innovators' tools**Tools from Australian problem solvers Hidden: no agreement yet Reporting and P6 data - [**Reporting & Integration**Portfolio reporting, and P6 in your data warehouse](https://skyhighpmo.com.au/reporting-integration?hsLang=en-au) [Insights Hidden at launch](https://skyhighpmo.com.au/insights?hsLang=en-au) [About](https://skyhighpmo.com.au/about?hsLang=en-au) [Contact](https://skyhighpmo.com.au/about#contact) [Test us on your issue](https://skyhighpmo.com.au/test-us?hsLang=en-au) Optimise your P6 # Find out what is really wrong with your P6. Then fix what matters most. We diagnose your Primavera P6 environment, covering performance, data, configuration and administration, with the scope sized to your environment and agreed before we start. You get a prioritised report, with the quick fixes already made through your change process and without disrupting your users, and you decide what happens next. [Find out how to optimise your P6](https://skyhighpmo.com.au/primavera-optimisation#enquire) ## Pick the question that's on your mind. ← All questions Replay Each question opens its own hub. You'll see the problems behind it turn into outcomes, and the work that solves each one. - Is P6 running slow? - Everyone's complaining P6 is slow, becomes: Root cause identified. Solved by Optimisation diagnostic. - Reports time out, becomes: Reports that finish. Solved by Optimisation diagnostic. - One planner's P6 flies, another's crawls, becomes: Every planner on the same footing. Solved by Optimisation diagnostic. - Database maintenance never scheduled, becomes: Maintenance scheduled and done. Solved by Optimisation diagnostic. - About to buy a bigger server, becomes: The real cause found before you spend. Solved by Optimisation diagnostic. - Can we trust the data? - Reports take days to pull together, becomes: Data maps created for each report. Solved by Optimisation diagnostic. - The monthly report starts an argument, becomes: A schedule that is evidence again. Solved by Optimisation diagnostic. - Codes applied three different ways, becomes: One way of coding, written down. Solved by Optimisation diagnostic. - Calendars that disagree, becomes: Calendars reconciled. Solved by Optimisation diagnostic. - Baselines nobody can date, becomes: Baselines you can date and trust. Solved by Optimisation diagnostic. - Has the configuration drifted? - Too many codes, and nobody knows why, becomes: A clean and documented configuration. Solved by Optimisation diagnostic. - The person who understood it has left, becomes: The setup written down, not in one head. Solved by Optimisation diagnostic. - Nobody feels safe changing it, becomes: A change process that makes it safe. Solved by Optimisation diagnostic. - Is the upgrade blocked? - Nobody can say what will break, becomes: An inventory of what the upgrade will hit. Solved by Optimisation diagnostic. - The version falls further behind support, becomes: A plan to a supported release. Solved by Optimisation diagnostic. - Customisations nobody has listed, becomes: Every customisation and integration listed. Solved by Optimisation diagnostic. How we help ## Diagnosis before any fix Most P6 problems get blamed on the wrong thing. Slow responses are blamed on the server, incorrect reports on the reporting tool, and the fix that gets funded is the one somebody guessed. We start by finding out what is actually going on. ![A stethoscope with its chest piece resting on a server, with a database beside it](https://skyhighpmo.com.au/hubfs/website/illus-optimisation-stethoscope-env.png) ### What we check - We check data integrity, to see whether the schedule data is sound and where it is broken. - We compare the server's specification and capacity with what the environment is being asked to do. - We read the application and database logs, which usually show the trouble before the users do. - We review planning practice, meaning how schedules are built, updated and reported. - We check data quality across codes, calendars, resources, baselines and layouts. - We review administration, meaning who owns what and how changes are made. ### What that gives you - A slow screen, a report that times out and a login error often share one cause. The diagnostic looks at the whole environment, so you see every issue at once instead of meeting them one at a time. - Fixing problems one by one turns a well-connected system into a patchwork. Seeing every issue together often justifies one bigger fix that clears several at once. - That saves time and money: fewer interruptions for your planners, an IT team confident the system won't fail the same way again, and the hours you'd otherwise lose the next time something breaks. Where it usually hurts ## Four problems we see most Pick the one that sounds like yours, or keep scrolling. 1. Everyone's complaining P6 is slow Screens and schedules that take minutes to open or copy. 2. Data nobody trusts Reports argued over instead of acted on. 3. Too many codes, and nobody knows why Years of codes and settings, and no one knows why they're there. 4. Upgrade or patch blocked No one knows how to upgrade or patch it safely. 1 of 4 ### Everyone's complaining P6 is slow Projects take minutes to open, copies take even longer, and errors log people out. That is rarely one big problem. Usually it is several small ones stacked up, such as database maintenance that was never scheduled, middleware nobody checks, hardware and network bottlenecks, and years of redundant data that every query pays for. The diagnostic checks all four before anyone buys a bigger server. [See what the diagnostic checks](https://skyhighpmo.com.au/primavera-optimisation#diagnostic) ![Speedometer with the needle in the low range](https://skyhighpmo.com.au/hubfs/website/illus-optimisation-p6-slow.png) ### Data nobody trusts When the monthly report starts an argument instead of a decision, the schedule has stopped being evidence. The causes are not mysterious. Activity codes are applied three ways, calendars disagree, resources are duplicated, nobody can date the baselines, and each project team updates progress differently. We check data integrity and planning practice side by side, and you get a list of what is broken, what it affects and what to fix first. [See how we check your data](https://skyhighpmo.com.au/primavera-optimisation#diagnostic) ![Two reports showing different numbers for the same month](https://skyhighpmo.com.au/hubfs/website/illus-optimisation-data-trust.png) ### Too many codes, and nobody knows why P6 configuration drifts. Codes, layouts, calendars and structures get added for one project and never retired, and the person who understood why has left. Every new project inherits the mess, and nobody feels safe changing it. Want to start with a clean slate but don't know how? Our configuration review documents what you have, separates the standard core from the one-off additions, and shows you how to realign your configuration with your future goals. [See how we review your configuration](https://skyhighpmo.com.au/primavera-optimisation#configuration-review) ![A tangled tree of codes with duplicate and dead branches, beside the same tree trimmed and labelled](https://skyhighpmo.com.au/hubfs/website/illus-optimisation-configuration-tree.png) ### Upgrade or patch blocked IT cannot upgrade or patch P6 because nobody can say what will break, so the version falls further behind support every year. Sometimes a move to the cloud makes more sense than an upgrade, and it raises the same question. Add upgrade planning to the diagnostic. We design the future state, from the version and whether P6 runs on your own servers or in the cloud to the integrations and what to clean up first, and our [Transformation page](https://skyhighpmo.com.au/transformation?hsLang=en-au) carries it out with you. [See how we plan your upgrade](https://skyhighpmo.com.au/primavera-optimisation#future-state) ![A race car marked P6 pulling into its pit box, the crew ready with a fresh tyre, wheel guns and a board reading Upgrade](https://skyhighpmo.com.au/hubfs/website/illus-transformation-pitstop.png) What we do ## Future state design The health check tells you where P6 stands today. Future state design sets out where it should be, and the steps to get there. - **Technical.** We set out the version to move to, whether it runs on your own servers or in the cloud, the server sizing, the integrations, and the data to clean up before anything moves. - **Functional.** We design how planning, progress and reporting should work in P6, including the structures, the codes, the reports people actually use, and who does what. - **The roadmap.** We put both in an order you can fund and act on, with what each step will ask of your team's time. You can carry it out yourselves, or we can deliver the roadmap with you through [Transformation](https://skyhighpmo.com.au/transformation?hsLang=en-au). [Design your future state](https://skyhighpmo.com.au/primavera-optimisation#enquire) ![Today in grey on the left and the future in white on the right, in three layers: the architecture of server and database, the coding, and the process library](https://skyhighpmo.com.au/hubfs/website/illus-optimisation-future-state-layers.png) What we do ## P6 configuration review A P6 that has been running for years carries every project's additions, such as codes, calendars, layouts and structures that were added once and never retired. A configuration review takes stock before anything changes. - **What you have.** We document your EPS and OBS, activity codes, calendars, resources, layouts, reports and user security as they stand. - **What should stay.** We separate the standard core from the one-off additions, and record what each one feeds and who still uses it. - **What it should become.** We design a target configuration and the rules that keep it right, covering who owns what, what may vary and how changes are approved. Small changes go through your change process during the review. A full rebuild is done through [Transformation](https://skyhighpmo.com.au/transformation#p6-configuration), which builds the new configuration with you. [Get your configuration reviewed](https://skyhighpmo.com.au/primavera-optimisation#enquire) ![A magnifying glass over a project structure tree, one branch ticked to keep and another crossed out to retire](https://skyhighpmo.com.au/hubfs/website/illus-optimisation-config-review.png) What you get ## Three things leave with you These are yours at the end of the diagnostic, whatever you decide to do next. ### A prioritised report Every finding comes with what it affects and what to do about it, in the order that matters. It is written so an IT manager and a planning manager can both act on it. ### Quick fixes, done The problems that can be resolved without impacting the end users are fixed during the diagnostic, not left on a list. ### A roadmap you own The findings are yours. Implement them in-house, or ask us to help through Transformation or Primavera Support. There is no lock-in and no second report to buy. How it works ## From your enquiry to a roadmap you own There are five steps, with the checks in the middle. 1. 1 ### Tell us what is going on Fill in the form at the bottom of this page. We read every enquiry and aim to be in touch within one business day. 2. 2 ### A short scoping call We agree what is in and out, how long it will take, and the access we need from your IT. We work hands-on rather than over a screen-share, and read-only access covers most of the checks. We give your IT the access list at the scoping call, because waiting for access is where a diagnostic most often loses time. 3. 3 ### The checks We run the checks on your environment, and make the quick fixes as your change process approves them. 4. 4 ### The report, walked through with you We explain the findings, the priorities and the roadmap in person, rather than just emailing them. 5. 5 ### Do it yourselves, or with us Carry out the roadmap in-house, bring us in for a one-off project such as an upgrade, or hand us the day-to-day administration and support of P6. After an upgrade, an optional session familiarises your team with the new features. Common questions ## Questions people ask How long does it take? It depends on your environment. Some take less time and some take longer, so we agree the length at the scoping call, before anything starts, and it doesn't change without your say-so. Do you need access to our servers? Yes. We work hands-on in your environment rather than over a screen-share, which keeps the diagnostic moving. Read-only access covers most of the checks, so we ask only for the access each check needs, arranged with your IT at the scoping call. Nothing is changed without your say-so, and the quick fixes go through your change process. Will you fix things, or just write a report? Both. During the diagnostic we make the quick fixes, which are small, low-risk changes your change process allows without a CAB approval and your users won't notice. Bigger changes, such as upgrades, patches or global configuration changes, need planning, testing and your approval, so they go on the roadmap with a priority. The roadmap is yours to act on. Is this the free Test us offer? No. Test us looks at one specific issue under our published terms. The diagnostic service is a paid engagement that covers the whole environment. If you are not sure which you need, start with [Test us](https://skyhighpmo.com.au/test-us?hsLang=en-au), where we look at one issue for free. What happens after the diagnostic? That is your choice. Many organisations implement the roadmap themselves. If you want help, [Transformation](https://skyhighpmo.com.au/transformation?hsLang=en-au) carries out upgrades, migrations and configuration rebuilds, and [Primavera Support](https://skyhighpmo.com.au/primavera-support?hsLang=en-au) can take on the day-to-day administration and support of P6. Which versions and deployments are covered? We cover Primavera P6 EPPM and P6 Professional, on your own servers or in the cloud. Patches and Oracle service requests need an active Oracle support subscription for your P6 licences. If yours has lapsed, we'll tell you at the scoping call what that limits. Does our data leave our environment? No. We work inside your environment, and the report holds findings, not your project data. [Ask a question we have not answered](https://skyhighpmo.com.au/primavera-optimisation#enquire) ## Not sure it is an optimisation problem? Test us on your current issue first. We look at one specific issue under our published terms, with one free test per organisation. [Test us with your current issue](https://skyhighpmo.com.au/test-us?hsLang=en-au) [Read the Test us terms](https://skyhighpmo.com.au/legal/test-us?hsLang=en-au) Enquiry ## Find out how to optimise your P6 Tell us what is going on with your P6. We read every enquiry and aim to be in touch within one business day. ### What happens next - We read every enquiry and aim to be in touch within one business day. - If a call would help, we offer times. [![Skyhigh PMO](https://skyhighpmo.com.au/hubfs/raw_assets/public/skyhigh-theme/images/skyhigh-logo-reverse.svg)](https://skyhighpmo.com.au/?hsLang=en-au) Experienced Primavera P6 and Project Controls specialists, working with organisations that deliver Major Projects in Australia © 2026 Skyhigh PMO Pty Ltd · ABN 80 653 189 881 · ACN 653 189 881 [Contact](https://skyhighpmo.com.au/about#contact) · [Privacy policy](https://skyhighpmo.com.au/legal/privacy-policy?hsLang=en-au) · [Terms](https://skyhighpmo.com.au/legal?hsLang=en-au) · [Partner with us](https://skyhighpmo.com.au/partner-with-us?hsLang=en-au)Hidden until the page is built · Cookie settings Oracle and Primavera are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.