Meter estate & smart-rollout PM · vacancy
Here's what AI can do for this role — and what still needs a human. Built straight from ENSEK's own job advert, running live on my_db.ensek_demo.accounts. Not a slide about AI. The job, getting done.
Every line on the left is lifted from ENSEK's actual job ad. If a card lacks a harvested JD line, it is omitted. On the right is the AI doing it — with eligible cards running live against the warehouse and offline inspection clearly labelled in the workspace.
“Own the strategy and roadmap for Asset Management, informed by users, retailers and commercial partners”
What's the current meter fleet breakdown — tech type by fuel, share of fleet and mean consumption?
bar chart“Define and track key performance metrics (e.g. asset issue rates, MTD processing accuracy, onboarding times)”
Which regions have the largest traditional-meter tail — the smart-rollout gap by geography?
bar chart“Conduct user research and bring actionable insights into product decisions and stakeholder conversations”
How stale are meter reads across the fleet — mean and worst-case days since last read, by tech and fuel?
bar chart“Run experiments, analyse data, and iterate based on evidence to improve product outcomes”
How does the active book split by settlement class — HH vs NHH by fuel and meter tech?
table“Build strong relationships with stakeholders while maintaining a product-led approach and protecting team focus”
Which meter-tech band carries the most book value — revenue concentration by asset type?
kpiThe honest other half. AI does the analysis; a person owns the decision — especially where regulation, fairness and accountability bite.
A plain-English question — the same one the job ad describes — is translated to SQL by the agentic backend.
Curated cards run server-side against MotherDuck when eligible. The workspace separately labels any local inspection path.
Runs against my_db.ensek_demo.accounts. No synthetic numbers.
Each figure carries a falsifier — recomputed from the result set, not a stored number, so it can't quietly drift.
It's the role getting done: curated questions run live server-side against the warehouse; local inspection is labelled inside the workspace.
Open the live workspace →Provenance. Representative ENSEK-style operational dataset (480 accounts · 728 meters · 5,676 monthly consumption records). Schema mirrors my_db.ensek_demo.accounts and my_db.ensek_demo.meters. Seed 20260609 — reproducible. No real ENSEK or customer data.
It's Sorted — I took ENSEK's job ads and didn't write a report on what AI could do. I built it. Get the rest sorted →
I'm trained on this proof and the real ENSEK: the Ignition meter-to-cash platform (seven modules), the move under Centrica in 2024, 7M+ energy accounts migrated for suppliers like British Gas and Utility Warehouse, and the Ofgem framing. Ask me how the Data Analyst function changes shape, or which open roles map to which Ignition module.