Prigo X Technologies · working demonstration on public data
One 30-minute average sets a whole month's capacity and network charges. This page takes a month of half-hour interval readings from a mid-size Peninsular Malaysia factory, prices them under the RP4 tariff structure in force since 1 July 2025, and shows what a single avoidable afternoon cost — and how much warning there was.
What one event cost
—
—
Billed maximum demand
—
Set by half-hour readings
Month consumption
—
Act 861 status
—
01 — The decision
Under RP4 the Time-of-Use demand rate is higher per kilowatt than General — but ToU bills demand only on the weekday 14:00–22:00 window, and discounts off-peak energy. Which way a site lands is a question about its own interval data, not a rule of thumb. On this profile the answer is worth more per year than the peak-shaving below, and it needs no hardware, no site visit and no permission — only a month of readings the client already has.
At the current cap. Bars share one axis.
—
| Charge | Basis | Amount |
|---|
The rule that decides it, and what it is worth here.
02 — The money
Move the cap and every figure on this page moves with it. The savings below come only from capacity and network charges — no energy saving is claimed, because shifting a load does not reduce the kilowatt-hours it uses.
—
Saved this month
—
Half-hours to act in
—
Worst single event
—
Annualised
If a month like this recurs. One month is not a year — see §8.
03 — The month
1,488 readings. The bill's capacity and network charges are set entirely by the highest point on this line — not by the area under it.
Shaded bands are weekends and Merdeka Day. Drag the cap in §2 to move the dashed line.
04 — The day
—
The tinted band is the weekday 14:00–22:00 peak window, which matters for the tariff comparison in §1.
05 — The half-hour
Maximum demand is an average, so for the first minutes of a window the outcome is not yet decided. A running average lags and only confirms the peak once it is too late to matter. Projecting where the average will land is what buys the time to act.
None of which is new. Maximum-demand controllers have shed load on a within-window projection for years, and several Malaysian platforms do it in software. This section is here to show the arithmetic is right, not to claim the mechanism — the scarce part is the decision layer above it: which tariff, what cap is worth holding, how much storage that implies, and what to tell a client who asks what last month actually saved them.
Projection holds the current instantaneous load for the balance of the window.
06 — What survives the rate uncertainty
The medium-voltage energy charges could not be sourced. That matters for some figures on this page and not at all for others, so here is the split rather than a blanket disclaimer.
These use only the capacity and network charges, which agree across independent sources.
These move with the energy charges. The rates are corroborated now, but a real bill is still the only proof.
07 — The rates
Every rate below now agrees across independent published sources, bar the retail charge, which is RM200 on a bill of hundreds of thousands and moves nothing. Each is still an editable input, carries its confidence, and is checked for plausibility as you type — a decimal point in the wrong place is caught before it reaches a client.
confirmed agrees across independent published sources · corroborated the same figure across independent published sources · assumed placeholder, not sourced
Reset monthly, which is the point: it cannot be budgeted a year ahead. Published figure for August, then the outlook.
—
08 — Method