Project and Contract Management
Project Planning and Control
Administration in Primavera P6 and P6 Web Access Rel. 7.0
Administering P6 so a programme is trustworthy: codes, calendars, baselines and who is allowed to change what.
- Duration
- 5 days
- Contact hours
- 30
- Level
- Intermediate
- Fee from
- On enquiry
Overview
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.
Who should attend
Planners and schedulers using P6, project controls staff, P6 administrators, and project managers who rely on the output.
What you will be able to do
- 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.
How it is taught
Short input, then work, across 5 days of roughly 6 teaching hours each. Exercises run on situations delegates bring rather than on a case study written for a different organisation. Cohorts are capped so that everybody is asked something.
Available as classroom, live online, in house.
Programme outline
Day 1
Structure and configuration
- Enterprise project structure, and why it is decided first
- Activity and project codes that reporting depends on
- Calendars, exceptions and the duration they imply
- Admin preferences and the settings that bite later
Day 2
Building a schedule that holds
- Logic against constraints, and the cost of the latter
- Activity types, durations and the meaning of float
- Resources and roles, assigned without overloading
- Scheduling options, and what each one changes
Day 3
Baselines and progress
- Setting a baseline, and controlling who may reset it
- Updating progress consistently across a team
- Earned value in P6, and the data it needs
- Reporting variance against the right baseline
Day 4
Multi user and access
- Users, security profiles and global change rights
- Web access, and what it exposes
- Checking a programme in and out
- Audit of changes, and recovering from a bad one
Day 5
Keeping it usable
- Layouts, filters and reports that people actually open
- Database housekeeping and performance
- Importing and exporting without corrupting the logic
- Handover of administration
What you leave with
- 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.
Dates and fees
| Dates | Location | Format | Fee |
|---|---|---|---|
| 23 to 27 November 2026 | Dubai, United Arab Emirates | Classroom | US$1,500 |
| 30 November 2026 to 4 December 2026 | Port Louis, Mauritius | Classroom | US$1,500 |
| 7 to 11 December 2026 | Nairobi, Kenya | Classroom | US$1,500 |
| 14 to 18 December 2026 | Windhoek, Namibia | Classroom | R15,000 |
Fees are per delegate and cover tuition, all programme materials and the certificate. Travel, accommodation and visas are arranged by the delegate. Registration closes two weeks before a programme starts.
Certificate
A GATI certificate recording what was 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.
It records participation. and GATI does not claim one it does not hold.