Programme controls for construction and infrastructure
Programme reporting you can cite.
BIDashboard takes your Primavera P6 schedules and turns them into schedule assurance, commercial registers and issued report packs — with every figure traceable to the snapshot and the settings that produced it.
One place for the programme, from the XER to the issued pack.
Upload a P6 export and it becomes a dated snapshot. Everything below reads from those snapshots, so last month's answer is still there next month.
Gantt
A virtualised Gantt built for programmes with tens of thousands of activities, grouped by your own code structures rather than by whatever P6 happened to call them, with PDF and Excel export.
Health
DCMA 14-point and extended checks, measured against thresholds you set. Those thresholds belong to the project, not to whoever's browser is open.
Compare
What changed between two updates, the finish first — dates, durations, float, logic, added and deleted work, and what moved on P6's own driving path — with tolerances you control.
Milestone trends · Adherence
Milestone movement across every update, in working days on each milestone's own calendar, and adherence that states its own rule rather than implying one.
Risk analysis
Monte Carlo on the programme itself, seeded so that a result can be reproduced instead of merely re-run.
Milestone status · Progress vs plan · Planning reliability · Cost
Where the milestones stand, progress against plan by whichever breakdown the project uses, Percent Plan Complete measured as commitments met, and cost against budget.
Report packs
Compose a pack from the same analysis you reviewed on screen, issue it, and keep the record of what was issued, when, and what was left out.
Delay events · Change events
Delay events reconciled against the programme's own finish movement, and change events with their contractual clocks running, so a notice approaching its time bar is visible before it lapses.
Risks · Progress proposals · Documents
A scored risk register, site progress proposed against the programme and approved by someone other than its author, and a document register with its full revision chain.
Built the way a controls team would audit it.
- P6 is always rightImported values are never “corrected”. If the schedule says it, the dashboard says it — and the analysis is layered on top, not written over the source.
- Every figure has a provenanceA number names the snapshot, data date and settings behind it. Views live in the URL, so an analysis can be linked, bookmarked and reproduced.
- Your data stays yoursClient and project separation is enforced inside the database by row-level security on every table, and checked by an isolation test suite that runs against the live system.
- Readable without colourStatus always carries a shape or a word as well as a colour, on screen and in the PDF. A chart that only works in red and green does not work.
- Access by invitationThere is no public sign-up. People are invited to specific projects, at a specific level, module by module.
Want to see it on your programme?
BIDashboard is invitation-only while it is rolled out project by project. Get in touch and we will set up a workspace.