Skip to content

Projects

The portfolio register — an EPS tree, full project CRUD, and one place to open, duplicate, or promote a what-if scenario into a real project.

Who it is for. Small teams and PMOs. Once you have more than about five schedules, "which projects exist, what did we budget and what have we spent" becomes a spreadsheet somebody maintains by hand.

What it is for

An EPS gives the portfolio a shape. Without one, projects are a flat list and roll-up reporting is manual — and the enterprise structure P6 buyers already think in is a separately licensed tier.

Against the incumbents

The scenario-to-project path: a what-if compression saved off the Gantt can be promoted into a real project in one click. EPS itself is table stakes against P6 — the honest claim is that it is included rather than a separately licensed tier.

What it does

Every line below is in the product today.

  • A real EPS tree

    Multi-level, collapsible, per-node colour, with project counts rolled up across each subtree.

  • Promote a what-if into a real project

    A saved crash scenario can become an independently schedulable project in one click, with the original untouched.

  • Duplicate a whole project

    Header, WBS parents before children, activities and dependencies cloned in one transaction.

  • KPIs scoped to the branch you selected

    Project count, active, on hold, planned budget and actual cost with utilisation — for the EPS subtree, not the whole database.

  • Open, or open alongside

    Load a project, or add it to the workspace as a read-only anchor next to what is already open.

  • Re-parenting with a cycle guard

    Moving an EPS node removes itself and its descendants from the parent options, so the tree cannot be knotted.

See it on your own schedule.

Send an XER before the call and we will import it and show you Projects running against your data.