Schedule reviews still depend on meetings, reports and manual comparisons between versions. This deck shows how the AWP Labs dashboards review P6 schedules in the browser instead, starting from the exports a planning team already produces.
Use the arrow keys or click to move through the deck. Open it in a full page ↗
Two routes, one suite
- .db route: open a P6 SQLite database directly in the browser and compare the versions it contains.
- .xer route: connect a folder of XER exports, assign each schedule to a project and a category (baselines, updates, sandbox), and keep the workspace file beside the XER files, which are never changed.
Both routes feed the same ten dashboards, carry the same built-in guide in English, Spanish and Portuguese, and can connect an optional AI Analyst.
A review path, from the portfolio to the owner
- Portfolio: score every schedule of the EPS (LFH, DCMA-14) and see forecast labor accumulate across projects.
- Project: pick it on the EPS tree, rebuilt as P6 stores it.
- Schedule versions: compare A and B, with one delta (B − A) on every dashboard.
- Phase or WBS: read phases, the critical stretch and milestones on the Roadmap and the Advanced Gantt.
- Activity: reach the row with its dates, float and links.
A finding should lead to supporting evidence and an accountable owner; cross-plan checks stay with the review team.
How the file is handled
The schedule file is read in your browser, read-only, and is not uploaded to AWP Labs. The built-in guide needs no AI account or key. The AI Analyst is optional and runs on your own AI account and key; it queries the open file read-only.
What the dashboards do not do
They do not update P6, do not integrate automatically with Capex, AWP, execution or permit plans, and do not diagnose the cause of a change. No measured benefit, saving or price is claimed in the deck; those are agreed and measured in a pilot.
Every dashboard view in the deck uses synthetic demonstration data; none of it is customer data.