Administration in Primavera P6 and P6 Web Access Rel. 7.0

P6 produces confident output from poor data without complaint. A programme with the wrong calendar, constraints used in place of logic, activities nobody owns and a baseline that has been quietly reset will still render a critical path and a progress curve, and both will be wrong. Most of that is an administration problem rather than a planning one. This week covers the configuration and control a trustworthy programme depends on, from the enterprise structure and coding through to baselines, progress and user access.

It runs 7 times over the published calendar, in 6 cities and live online. Every date is the same programme with the same content and the same certificate.

• Set up an enterprise project structure and coding that reporting can actually use.
• Configure calendars so durations and dates mean what they appear to mean.
• Maintain baselines so progress is measured against something fixed.
• Control constraints, and recognise where they are substituting for logic.
• Set user access so the programme cannot be changed without a record.

Planners and schedulers using P6, project controls staff, P6 administrators, and project managers who rely on the output.

Short input, then work. Across 5 days of roughly 6 teaching hours each, the balance sits deliberately with the second: a programme where the trainer talks for six hours produces notes rather than capability.

• Your own material

  Exercises run on situations delegates bring, not on a case study written for a different organisation in a different decade.

• A capped cohort

  Small enough that everybody is asked something. Executive programmes are capped tighter still.

• Practice under scrutiny

  The difficult conversation, the challenged assumption, the decision defended out loud. Judgement is not built by watching.

• Something to take back

  Each day ends with a thing you can use on Monday rather than a slide deck you will not reopen.

• A configured project structure and code set for the delegate's own portfolio.
• A baseline and progress procedure, written.
• A user and access matrix defining who may change what.

A GATI certificate recording what you attended, issued after the programme has run and attendance has been taken. Attending at least 80 per cent of the days earns a certificate of completion; attending less earns a certificate of attendance stating exactly what was attended.

Every certificate carries a code that anybody can check against GATI's own record, which is what makes it worth holding. It records participation. This site will not imply one it does not have.