Drillthrough target — reached from a mark, not from the page tabs. ← back to the source page

Project financial detail

Everything the report holds on Ostend line, on one page.

No slicer strip on a drillthrough page — filter context is inherited from the visual you came from. Carried through: Period all · Region UK · iHub Sheffield · Project type Feasibility study · Status Closure · Currency GBP.

Ostend line

UK-1111 · PRJ-0112ITAR restricted — row-level security applies
Customer CRMMarlow Automotive
iHub Sheffield · UK
Project type Feasibility study
Stage Closure
Project lead Quinn Mayer
Original currency (GBP) Budget 28,131
Reporting currency (GBP) Budget £28,131
CRM link CRMNSP-50111

Predicted against actual

CRM
Variance £3,193 (6%) against the offer-gate prediction

Cost against budget, and where the cost sits

EPMS
Waterfall shows every category · dashed steps sit outside the declared cost base

Hours by person

EPMS
Hours only · no rate, no cost · 14 people booked

Scope-change events and the hours they caused

EPMS
Chronological · 0 events · No hours booked additional in total

Savings committed against delivered

EPMS
Per project only · the customer-level roll-up lives in D365 Customer Value Planning

Stage-payment status

EPMS
Status only · invoicing is M3's · no amounts, balances or ageing here
As at 2026-08-12 · EPMS refreshed 2026-08-12 05:40 UTC · CRM refreshed 2026-08-12 04:05 UTC · GBP, period-average rates
Cost basis: project engineering time only. Excludes senior management time, business development time, travel. Not yet agreed.
  1. Tab order:
  2. 1. Header — project identity and currency basis
  3. 2. Predicted against actual, against the portfolio parity line
  4. 3. Cost against budget and the category waterfall
  5. 4. Hours by person
  6. 5. Scope-change events
  7. 6. Savings committed against delivered
  8. 7. Stage-payment status