Project controls,
simplified.
The daily report shouldn’t take your morning. One upload and progress, cost, float, milestones, off-site equipment and safety rebuild themselves — no spreadsheets, no manual status updates, no interpreting the programme/schedule to manually build the report. Teams running Virtus get 4 hours a day back.
| COMPONENT | WBS | SENT | DUE BACK | RETURN | VAR | STATUS |
|---|
| AREA | COMPONENT | REMOVED | REPLACED | ITP | REF | STATUS |
|---|
- Baseline start and finish on every activity1,192 of 1,192100%
- Actuals recorded up to the status dateno open activities behind 29 Oct100%
- Crew assignments carried on activitiesneeded for the per-crew curves94%
- Discrete inspection activities for ITP components40 components carry a demonstration ITP until the schedule holds one27 / 67
- Open-ended logicactivities with no successor3 open
Planned against earned, every day
Grey is the plan for that day, green is what was actually claimed. Earned stops dead at the status date — the curve never guesses at work nobody has signed for. Daily for the crews on the floor, weekly for the commercial report, identical totals either way.
| WBS | BAC (H) | PV | EV | SV | SPI | STATUS |
|---|
"We're behind" becomes "electrical is behind on the motors"
Drill from the whole shutdown/project down four WBS levels — boom, tub, hoist machinery, motors — or filter to one crew. The curve, the hours and the SPI all re-cut to whatever you picked. That's the version you can act on.
Roll back to any past date
Every update ever uploaded is kept. Pick a date and the whole dashboard reports as it stood that morning. Settles the argument about what was known and when — useful in a claim, and useful in a post-mortem.
Ask the project a question
Dates, hours and crew performance read straight off the programme, with the source activity UIDs against every figure. It states its own basis — which crews count as mechanical, how hours are apportioned — so the number can be argued with rather than taken on trust.
This is where to focus this morning
Baseline date passed with no actual recorded — the schedule raises it, nobody has to notice it. Worst first, with days late and the current forecast against every line.
- 0tasks missed their baseline startWorst 5 days late · Hoist Gearbox 2 bearing & gearing · Boom foot · Vacuum circuit breakersMISSED START
- 0of 70 critical tasks forecasting later than baselineRanked by total float — where the two days of slip actually liveCRITICAL PATH
- 0of 36 off-site components due back lateSent date, contractual due back, forecast return, variance in daysOFF SITE
- 0ITPs due — the inspector's list for the morning21 complete · 25 awaiting refit · a component can't show its ITP is ready until the refit isITP CENTRE
- 0milestones slipped of the 5 you chose to trackMachine walks off shutdown pad · baseline 20 Nov · forecast 22 Nov · +2MILESTONES
- 0overdue safety action, on the same screen as the schedule1,496 HSE records · 6 open actions · every one tied to the activity in that area that dayHSE
The dashboard is just the beginning
Virtus is a full project controls suite, tailored to your shutdown or project. The dashboard is the front door.
Run it on your own shutdown/project
Send us a schedule export and we'll walk you through your own dashboard in about twenty minutes. Your data, your WBS, your crews.
- Runs in a browser, on a phone, offline. Nothing to install.
- No spreadsheets to maintain, no manual status.
- Every update kept — roll back to any morning.
- We'll show you the gaps in your schedule too. Readiness names every one.