--- title: "WattEY" headline: "WattEY — Ali Ahmed, Head of Product & Platforms, BijliBachao.pk" description: "Ali Ahmed built WattEY: IoT electricity monitoring for Pakistani industry — three-phase readings turned into time-of-use, net-metering and generator accounting." canonical_url: https://alioahmed.com/work/wattey type: case-study role: "Head of Product & Platforms, BijliBachao.pk" date_label: "January 2026 – present" status: live date_modified: 2026-08-26 author: name: "Ali Ahmed" url: https://alioahmed.com/ orcid: https://orcid.org/0009-0007-4265-3295 key_figures: - "1.92 GWh energy measured, live" - "43 meters 19 organisations" - "~156,000 measurements a day" - "635.76 kW peak load recorded" entities: - name: "WattEY" type: SoftwareApplication url: https://wattey.bijlibachao.pk/ - name: "BijliBachao.pk" type: Organization url: https://www.bijlibachao.pk/ same_as: - https://bijlibachao.pk/#organization - name: "WattEY meter classes" type: DefinedTermSet - name: "Net metering" type: DefinedTerm same_as: - https://en.wikipedia.org/wiki/Net_metering - name: "Time-of-use tariff" type: DefinedTerm same_as: - https://en.wikipedia.org/wiki/Electricity_pricing - name: "National Electric Power Regulatory Authority (NEPRA)" type: GovernmentOrganization url: https://nepra.org.pk/ same_as: - https://www.wikidata.org/wiki/Q6972401 - https://en.wikipedia.org/wiki/National_Electric_Power_Regulatory_Authority - name: "UN Sustainable Development Goal 7 — Affordable and Clean Energy" type: DefinedTerm url: https://sdgs.un.org/goals/goal7 same_as: - http://metadata.un.org/sdg/7 - name: "UN Sustainable Development Goal 9 — Industry, Innovation and Infrastructure" type: DefinedTerm url: https://sdgs.un.org/goals/goal9 same_as: - http://metadata.un.org/sdg/9 - name: "UN Sustainable Development Goal 12 — Responsible Consumption and Production" type: DefinedTerm url: https://sdgs.un.org/goals/goal12 same_as: - http://metadata.un.org/sdg/12 - name: "Water and Power Development Authority" type: GovernmentOrganization url: http://www.wapda.gov.pk/ same_as: - https://www.wikidata.org/wiki/Q7973437 person_same_as: - https://www.linkedin.com/in/alioahmed/ - https://github.com/alioahmed - https://orcid.org/0009-0007-4265-3295 - https://x.com/Alioahmed_ - https://about.me/alioahmed - https://dev.to/alioahmed - https://medium.com/@alioahmed - https://hashnode.com/@alioahmed - https://substack.com/@alioahmed - https://huggingface.co/alioahmed - https://bsky.app/profile/alioahmed.bsky.social - https://mastodon.social/@alioahmed - https://www.kaggle.com/alioahmed - https://www.producthunt.com/@alioahmed - https://www.patreon.com/cw/alioahmed - https://www.goodreads.com/user/show/202106301-ali-ahmed - https://fueler.io/alioahmed - https://gitlab.com/alioahmed - https://linktr.ee/alioahmed - https://topmate.io/alioahmed related: - https://alioahmed.com/work/tenantbill - https://alioahmed.com/work/sts - https://alioahmed.com/work/solar-performance-cloud - https://alioahmed.com/work/bijli-bachao full_corpus: https://alioahmed.com/llms-full.txt site_index: https://alioahmed.com/llms.txt --- # WattEY > WattEY is an industrial IoT electricity-monitoring and billing-intelligence platform built by Ali Ahmed. It reads a site running grid power, rooftop solar and a generator at once — sixteen values every three minutes from a three-phase meter — and turns the raw telemetry into what the business is billed on: the time-of-use split, grid import net of solar export, and generator energy kept separate from grid. It is live in Pakistan: 43 meters across 19 organisations, 1.92 GWh measured since November 2025. **Canonical URL:** https://alioahmed.com/work/wattey **Role:** Head of Product & Platforms, BijliBachao.pk — January 2026 – present **Summary:** Ali Ahmed built WattEY: IoT electricity monitoring for Pakistani industry — three-phase readings turned into time-of-use, net-metering and generator accounting. ## Key figures - **1.92 GWh** — energy measured, live - **43 meters** — 19 organisations - **~156,000** — measurements a day - **635.76 kW** — peak load recorded ### What Ali builds, and what WattEY is. Ali Ahmed builds systems that turn messy, multi-source real-world data into numbers a business can bet money on. WattEY is one of them: an industrial IoT electricity-monitoring and billing-intelligence platform for sites that run the grid, rooftop solar and a diesel generator at once, under time-of-use tariffs no ordinary dashboard reads correctly. A three-phase meter reports sixteen values every three minutes, and the platform turns that raw telemetry into the quantities a business is actually billed on — the time-of-use split, grid import net of solar export, and generator energy kept separate from grid. It is live in Pakistan, one of the hardest energy markets on earth: 43 meters across 19 organisations, 1.92 GWh measured since November 2025. As an energy-transition platform it is built in line with UN Sustainable Development Goals 7 (affordable and clean energy), 9 (industry, innovation and infrastructure) and 12 (responsible consumption and production). ### What changed because Ali was there. WattEY was built at BijliBachao.pk — an engineering design house that builds its own software rather than an installer — and has run continuously for nine months in one of the world’s hardest energy markets, across mills, hotels, malls, farms and cold storage in Lahore, Sheikhupura, Kasur, Sargodha, Kamoke. The arc is Started → Built → Delivered → Scaled → Outcome. It started with one opaque figure a month. Ali built a three-phase meter reporting sixteen values every three minutes that classifies each meter from its own telemetry; delivered billing-grade accounting that separates the three sources automatically; scaled it to 43 meters across 19 organisations; and the outcome is 1.92 GWh in which every unit is attributable to its source and its shift — a figure a CFO can take to the board. ### The bill that never explains itself. Every industrial site now runs on more than one source — the grid, a rooftop array, a generator — and gets a single number a month for each. Can the operator say which shift drove last month’s peak? Whether the generator is the most expensive kWh on site? Whether the solar is delivering what the contractor promised? Most cannot, and have quietly accepted that they cannot. On a Pakistani bill the variable components — fuel price adjustment, quarterly tariff adjustment, general sales tax and a stack of surcharges — swing the total by fifteen to thirty per cent, and the page arrives with the answer already priced in. The line items are specific to Pakistan; the blind spots are universal. ### Six things the bill charges for and never names. - The evening window: peak hours cost more than off-peak, and nothing says how many units landed inside them. - The demand penalty: maximum demand was crossed — but not which shift, or which fifteen minutes. - Power factor sitting below 0.90, quietly adding to the total until it has already been charged. - The generator: diesel burned on a meter-less schedule, so a unit of backup power has no known cost. - Solar you cannot verify: whether the array is actually delivering the promised saving. - No early warning: every overcharge is learned about on the day the bill arrives, never the day it starts. ### I built the system behind the number. WattEY was not a dashboard project. Ali designed and built the end-to-end system that turns unreliable, multi-source meter data into a number a business can trust — the whole path from the physical world to the business decision. Grid, rooftop solar and a diesel generator feed in as three separate sources; the platform carries it from raw three-phase data, through ingest and validation, into the WattEY engine that classifies and reconciles each meter, out to the product layer, and finally to a business decision. One system, many decisions. The build is proven by what it sustains in production: industrial-grade three-phase monitoring; sixteen values per reading every three minutes; roughly ~156,000 measurements processed a day; 1.92 GWh measured since November 2025. Two principles are deliberate — it is honest by design, showing gaps rather than guessing across them, and it is delivered phone-first, because the managers who depend on it are rarely at a desk. ### It tells you when it doesn’t know. This is the one thing no competitor copies. When a meter loses signal, most platforms draw a smooth line across the gap so the chart looks complete, and the customer never finds out. WattEY refuses: it shows exactly how much of a period was genuinely measured, and will not say when energy was used if nobody was watching. One site went silent for 56.9 hours — more than two days — and reported all of it at once when the meter reconnected. The meter kept counting internally the whole time; the link stopped, the metering did not. Filed by arrival time, 15,860 kWh would have landed on a single day; WattEY keeps that energy in the total but excludes the time-of-use, peak and hourly breakdown for a window nobody observed, and says why on the screen. Across the fleet a meter goes quiet 1,170 times in ninety days — 497 of those gaps run over an hour — and every one of them is shown, not filled in. A total can be correct while the story is wrong. This is the engineering decision the section is about: a trustworthy system knows the boundary between what is known and what is not, and WattEY is designed to know the difference. A total you can trust is worth more than a chart that looks finished. ### A meter reading is not a bill. Reading three phases every three minutes is the easy half of this problem. Hardware that does it is available off the shelf, and a chart of kilowatt-hours is a weekend of work. The hard half is that a Pakistani industrial electricity bill is not computed from total consumption. It is computed from when the consumption happened, from consumption net of anything the site exported back, and from which source was carrying the load at the time. A monitor that reports units and stops has told a factory director nothing he can act on. WattEY is the layer that closes that gap, and it is the layer Ali built. ### Three meter classes, assigned from telemetry rather than configuration. A Pakistani site can run on the grid, on its own roof and on a diesel generator, switching between them through the day. Most monitoring treats that as a configuration problem: an installer ticks a box, and the box is wrong within a year — because panels get added, because a generator gets commissioned, because the person who ticked it has left. WattEY infers the class from the meter’s own telemetry instead. 1T is a site that only draws from the grid. SM adds a roof that exports. 2T adds a generator. Each class reads everything the class below it reads and more, which means the product has three shapes rather than three products — and a site that commissions an array is reclassified without a window in which it is silently mis-billed. ### Where a reading becomes a bill. Two pieces of arithmetic separate a meter reading from the number on the bill, and both are specific to Pakistan. The first is the clock. Peak-hour electricity is billed at a higher rate than off-peak, and the peak window is not fixed — it moves with the season, roughly 5 PM to 9 PM in winter, 6 PM to 10 PM in spring and autumn, and 7 PM to 11 PM in summer. WattEY applies the current window automatically, so the split it reports is the split the tariff will actually be computed on rather than an approximation somebody has to remember to update. The second is a minus sign. Under net metering the billable quantity is signed: import minus export, not import. When a roof sends more to the grid than the building draws, consumption for that hour is negative, and a platform that reports absolute throughput will overstate a solar site’s consumption on every sunny afternoon of the year. WattEY tracks the two as separate quantities and reports the difference — the same subtraction the net-metering bill performs. Export is measured per phase, which is how a wiring fault on one leg becomes visible before it costs a season of generation. ### What it runs on. As of August 2026, WattEY had 43 meters in production, 34 assigned to customer organisations and 28 reporting in the last week, across 19 organisations — 16 with a meter live in the last week — in Pakistani cities including Lahore, Sheikhupura, Kasur, Sargodha, Kamoke. It had measured 1.92 GWh of energy since November 2025, roughly ~156,000 individual measurements a day, and the highest instantaneous load recorded at a single site was 635.76 kW. Generator runtime is detected automatically, without a fuel sensor. No two of those sites have the same load profile. A paper mill draws steadily around the clock. A shopping mall peaks in the evening and runs a generator through load-shedding. A dairy farm’s refrigeration never stops but its roof exports all afternoon. A cold store never switches off; a bakery swings with the shift pattern. The meter class the platform assigns each one is that difference made explicit. The sites are described by sector rather than named. They are BijliBachao’s clients, and naming them on a personal portfolio is a clearance question that has not been answered. ### We built it to measure. It started revealing. Running a fleet for nine months surfaces patterns no site can see about itself until it measures. These are production observations, not projections. Peak-hour exposure varies roughly fourfold between sites — from 8.9% of consumption to 32.5% inside the expensive evening window, against an 18.7% fleet average (20.1% weighted by import). Some sites draw more power at 3 AM than during their own average hour, one reaching 182.3% of its average overnight and pulling 229 kWh every hour at that time. Rooftop solar offsets grid import by as little as 2.7% at the weakest site, while the best is a genuine net exporter — sending back 232% of what it draws — a difference visible only at the meter, never the inverter’s own app. And one site whose typical draw was 61.82 kW briefly reached 96.53 kW, 1.56× its own baseline, the ratio the platform’s demand alert fires on. The interesting part was not collecting two million readings — it was discovering what they meant. Every one of these has an answer for a given site, and the only way to find it is to measure it. These are fleet-level patterns as of August 2026; no individual client is identified. ### What a reading actually is. A reading count on its own is a vanity number. What makes the volume mean anything is what a single raw reading holds: current, voltage, power and power factor on each of three phases — twelve values — plus frequency, the active tariff register, and total power. Fifteen values in all. Separately, the meter’s own kilowatt-hour register carries cumulative grid import and export, which is what net metering is computed from. That is enough to reconstruct the state of a three-phase supply at one instant, which is the precondition for every other claim on this page. Fifteen values, per meter, every three minutes. ### What actually transfers — the electricity is only the domain. Strip away the meters and the tariffs, and WattEY is a machine for making untrustworthy, multi-source data — from devices you do not control — safe to compute money from. Almost none of that hard part is about electricity, which is why it is the thing Ali builds for other people. The transferable engineering: classify an asset from its own behaviour rather than a configuration record that goes stale; keep a signed quantity signed all the way through, so a credit never reads as a charge; apply a rule set that changes on a calendar without asking an operator to remember; attribute every unit to its source; and isolate every tenant’s data by default. That is the same problem in sensor and IoT telemetry, in logistics and fleet data, in water and utility metering, and in payments and reconciliation — any platform whose output an accountant will eventually have to defend. ### Nobody owns the multi-source number. Utilities meter the grid. Solar vendors monitor the panels. Generator vendors monitor the genset. Nobody unifies them into the one figure a business is actually billed on — the dollar view across every source. WattEY is the layer that closes that gap: the platform that decides the number. The category it sits in — energy management — is a roughly $41–69 billion market in 2025 growing 13–15% a year, with industrial energy management (WattEY’s exact home) at about $20.7 billion rising to $33.2 billion by 2034. The opportunity is mapped, not claimed: WattEY is live in Pakistan only, and the markets where the same problem is most acute are its export horizon, not its reach. The emerging-market twins of Pakistan carry the same conditions and thin competition — South Africa, the Philippines, India and Nigeria. The developed analogs are larger and more contested — Australia, the United Kingdom and the United States. Pakistan runs every one of those pressures at once, which is why a platform proven there is proven for the hard version of every market above: the fleet is the credential, not the ceiling. ### Why this one is on the page, and what it does not do. The instrument was the easy part; the accounting was the product. Knowing which number the director argues about, and building backwards from it, is a product judgement before it is an engineering one. Ali took WattEY end to end — the data model, the tariff logic, the meter classification and the dashboard a client sees — from nothing to production, alone, in one of the hardest energy markets on earth, and it has been running since November 2025. What it does not do, stated plainly: it does not decode the rupee bill (it accounts for units and windows; no rupee figure is published for any client); it is not a control system beyond administrator relay control; and it is a private system nobody can buy from this page — an operator who wants it goes to BijliBachao, which deploys it. Every figure here is a production snapshot dated August 2026, not a live read of the production database. ## FAQ ### What did Ali Ahmed actually build in WattEY? The platform layer: the data model that a three-phase meter reports into, the tariff accounting that turns those readings into billable quantities, the meter-class system that decides what each site is capable of reporting, and the multi-tenant dashboard the client sees. He leads it as Head of Product & Platforms at BijliBachao.pk, where it has been running since November 2025 across 19 organisations (19 with meters installed). ### What was the hardest decision on this platform? Making the meter class an inference rather than a setting. The straightforward build is a configuration screen where an installer declares whether a site has solar or a generator. That is faster to ship and it is wrong within a year, because sites change and nobody goes back to update the record. Deriving the class from telemetry meant accepting a harder detection problem in exchange for a system that stays correct without maintenance. ### Why does a monitoring platform need to know about Pakistani tariffs at all? Because otherwise it reports a number nobody is billed on. A generic energy monitor tells a site how many units it used. A Pakistani bill is computed from when those units were used, from consumption net of anything exported back to the grid, and from which source was carrying the load. The tariff logic is not a feature bolted on top of the measurement — it is the thing that makes the measurement worth taking. ### What on this page is still unverified? The figures are a production snapshot dated August 2026 rather than a live read, though the whole site — this chapter, the Bijli Bachao hub, and the project index — was reconciled to that same pull, so they now agree. The meter model and the full set of supported network links are recorded as unconfirmed in the source data and are therefore not stated, and no generator-hours total is published because the pull surfaced none. No client is named, because that clearance has not been given. ### How does WattEY relate to Solar Performance Cloud? They measure opposite halves of the same site and neither replaces the other. WattEY measures what a business pulls from the grid and what that consumption costs under the tariff. Solar Performance Cloud inspects what the site’s own solar generates, string by string. Ali built and leads both, which is the point: the two chapters are one argument about being able to take a measurement problem end to end. ### What transfers from this to a problem that is not about electricity? Most of it. The electricity is domain detail; the engineering is about making third-party device data safe to compute money from — classifying assets from their own behaviour rather than from a stale configuration record, keeping a signed quantity signed all the way through, applying a rule set that changes on a calendar without asking an operator to remember, and isolating tenants from each other by default. That is the same problem in logistics telemetry, in metering water, and in any platform whose output an accountant will eventually have to defend. ### Why is my industrial electricity bill so unpredictable? Because one monthly number hides three things it cannot separate: how much of your consumption landed inside the expensive peak window, how much your rooftop solar actually offset at the grid connection, and how many units your generator burned versus the grid. WattEY measures all three directly — a three-phase reading every three minutes — so the bill stops being a surprise and becomes a set of quantities you can watch move through the month. ### How do I tell whether my generator or the grid is cheaper per unit? You need the generator’s energy measured separately from grid energy, which almost no site does. WattEY detects generator runs automatically and keeps backup energy on its own ledger, so the units it produced can be set against the diesel you bought — and against grid units over the same period. Without that separation the comparison is a guess; with it, it is arithmetic. ### Can an energy manager or operator get WattEY for their own sites? WattEY is built and deployed by BijliBachao.pk, the engineering firm where Ali built it, and it runs live across industrial and commercial sites in Pakistan today. An operator who wants it on their own fleet goes through BijliBachao; this page is a case study of the system and the engineering behind it, not a product store. --- Rendered from the structured content at https://alioahmed.com/work/wattey. Facts trace to the canonical bio; render, don't reword.