The same P0–P5 structure from the Approach page, broken down into what’s actually built at each stage.
P0 — Mobilise
Advisory. Programme charter, sponsor alignment, pilot value-stream selection, and a baseline metric pack — agreed before any data work begins.
P1 — Data Substrate
Power Query. Connectors built to your source systems, data cleansing, a Data Quality Score engine, and a single unified, refreshable PFEP query — the governed dataset everything downstream reads from.
P2 — Variability & Segmentation
Power BI. Demand and lead-time variability instrumented (ADU, coefficient of variation), parts segmented ABC/XYZ, first DAX measures and a segmentation dashboard.
P3 — Position & Size Buffers
VBA. Decoupling-point logic, safety-stock sizing, EOQ/Min-Max calculations, container and kanban sizing, and a what-if scenario engine for testing buffer decisions before committing to them.
P4 — Pilot Execution
Power BI + VBA. Live executive and operational dashboards, a weekly cadence run, exception automation, and user training on the pilot value stream.
P5 — Stabilise, Govern & Scale
Governance. Roll-out to the full part population, a leading/lagging KPI framework, refresh scheduling, documentation, and handover — including, where useful, a configured AI agent that runs daily buffer-zone and exception analysis against the PFEP dataset conversationally, so the system runs without ongoing dependency on the advisor.
Scoped and costed before you commit
Every engagement is priced against the specific scope agreed in the P0 charter — not a fixed package. Day rate sits under the €900/day cap the Enterprise Ireland Lean rails support (see Funding), so most of a diagnostic-stage engagement is grant-eligible before you pay anything out of pocket.
Get a scoped, costed proposal.
A scoping call establishes which phases apply to your operation and what they’ll cost — grant-eligible costs included.