P6 EPPM Implementation & Configuration
A Primavera P6 EPPM implementation rarely fails at installation; it fails at adoption. The software goes in, the licences are paid — and a year later planners are still exchanging XER files by email because the structures never matched how the business actually runs projects.
I have implemented and reconfigured P6 EPPM for contractors, owners and defence programmes for over fifteen years, and I hold Oracle's Certified Implementation Specialist credential for it. The method below is what that experience has distilled into.
What a good implementation looks like
It starts with requirements, not software. Before anything is installed we agree on what the organisation needs to see: which decisions the schedule data must support, who plans, who updates, who approves, who only reads. That becomes the design — EPS and OBS structures, project and activity codes, calendars, security profiles, user roles and naming standards — written down before it is clicked into existence.
Then configuration, against that design. Then documentation: a standards document that survives me leaving, so the environment does not quietly drift back into chaos with the first staff turnover. Then a pilot on a real project, corrections, and rollout with role-based training.
How we work
A typical implementation runs in five phases: requirements workshops → design document (reviewed and signed off by you) → environment build and configuration → pilot and adjustment → rollout, training and handover. Timeline depends on scale: a focused single-company setup and a multi-entity enterprise programme are different animals, and I will give you an honest estimate after the first call rather than a template answer.
I work with your IT on infrastructure (on-premise or Oracle cloud), but the centre of gravity is always the project controls team — they are the ones who have to live in it.
Already have P6 installed but not working for you? That is not an implementation project, it is a reconfiguration — usually cheaper, and it starts with a system audit.
Beyond P6 itself
Implementations rarely stop at the P6 boundary. Where the scope calls for it, I design and deliver the surrounding pieces: Primavera Unifier for cost and contract workflows, Primavera Gateway for data flows between systems, and the reporting layer on top. One person owning the whole chain keeps the design coherent.
Frequently asked questions
On-premise or cloud?
Both. I have delivered on-premise EPPM installations and Oracle-cloud deployments; the configuration and governance work is largely the same, and I will recommend honestly based on your IT reality rather than a preference.
How long does an implementation take?
A focused single-organisation setup is typically measured in weeks; enterprise, multi-entity programmes in months. I scope it properly after the requirements conversation — beware of anyone who quotes a duration before that.
Our P6 is installed but a mess. Do we start over?
Almost never. Most "failed" implementations are salvageable through reconfiguration, data cleanup and restated standards. An audit first tells us which parts to keep.
Do you work alongside our internal IT and PMO?
Yes — that is the normal mode. IT owns the infrastructure, the PMO owns the process, I bring the P6-specific design and configuration experience, and everything is documented so your team owns it after handover.