Wedge — Energy
Joules per tonne,
as a query.
Energy intensity is how every heavy-industry P&L is actually read. On PlantOS it’s the unit of the API, not a downstream spreadsheet. Live, receipted, queryable.
Why this is the unit
Cost, contract, and control all read the same number.
Energy is the line
In a smelter, electricity is a third of operating cost. In a refinery, steam and fired-heater fuel set the margin. A 1% intensity move is a real number on a real P&L.
Customers ask for it
Green-bond reporting, low-carbon-product premiums, customer scope-3 packets all demand per-tonne intensity figures with provenance. The premium is paid only against verifiable numbers.
Operators tune to it
Joules-per-tonne is the single number an operator can move shift-to-shift. Surfacing it live, with provenance, is what turns the metric into a control input.
Per unit of product
Same accounting, every domain.
Crude unit
MJ of fired-heater fuel + steam per barrel of throughput, rolled up by unit and by campaign.
Aluminium potline
kWh per tonne of metal, normalized to current efficiency and bath temperature.
EAF charge
MJ per tonne of liquid steel, separating power, oxygen, and burner inputs.
Kiln line
MJ per tonne of clinker, with alternative-fuel substitution rate as a sibling figure.
Reformer + synth
GJ per tonne of NH₃, with natural-gas feed split from fuel.
Data centre
Joules per inference, joules per token, joules per query — the same accounting, different unit of product.
Joules is the universal unit of the Transaction Science platform. PlantOS reads it where it’s already the customer’s unit.
API
Energy intensity, with the chain attached.
# Joules per tonne of product, over the last 24 hours
GET /api/v1/plant/energy/intensity/{asset}?window=24h&unit=mj_per_t
# Response carries the aggregate receipt
{
"asset": "potline-3",
"intensity_mj_per_t": 49680.0,
"window": "24h",
"samples": 86400,
"receipt": "rcpt:ag-019e..."
}
# Drill into the chain
GET /api/v1/plant/receipt/{receipt_id}