Foundational proof
A single duration change, cascaded correctly
On a live P6 EPPM instance, Sage looked up a real project, changed an activity's duration from 160 to 240 hours, and ran a full F9 recalculation. The three downstream activities each shifted forward by exactly 14 calendar days — the correct cascade for a 10-working-day increase on a 5-day work week — with every activity retaining its correct duration afterward. No spreadsheet export, no manual re-entry, no P6 client UI.
160→240hours changed
+14days × 3 activities
1F9 recalculation
Full-scale proof
A complete project, built live from scratch
Sage built a complete project live — roughly 30 activities across 8 WBS nodes, ~34 relationships, up to 16 labor, non-labor, and material resources, ~29 resource assignments with computed costs, and multiple activity code categories — with schedule dates and costs matching a hand-verified training manual's own answer key. It then enabled multiple float paths, ran F9, and produced a correct float-path report — six distinct paths, Gantt-format, with Total Float — directly from the live schedule.
~30activities / 8 WBS nodes
~29resource assignments
6float paths reported