> ## Documentation Index > Fetch the complete documentation index at: https://docs.assetinfinity.ai/llms.txt > Use this file to discover all available pages before exploring further. # Energy management > Utility consumption against what a supply point should be using — findings, targets and carbon, built on top of meter readings. Energy management asks whether a site is using more of a utility than it should be, and turns a reading into a finding rather than just a chart. This is a distinct module from [meters and readings](/assets/meters) on an asset. A meter is something you count on a machine; a **supply point** here is what a utility bills you for — a gas line, an electricity feed, a water main — and can name an asset, a location, or just a site. The reading mechanics are the same one you already know from meters; this page covers what's built on top of them. ## Findings, not just a chart The screen leads with what it can see that nothing else can: * **A supply point nobody has read.** No reading means no consumption, no consumption means nothing to compare, and a meter nobody walks past looks identical to one that used nothing — everywhere except this banner. * **A period that's mostly a utility's estimate.** An estimated bill is deliberately left out of anomaly detection, so it's invisible to the findings list rather than merely absent from it. Below that, a bar chart of consumption against expectation, and a list of **findings** — periods that came in worse than expected, either against the site's own history or against comparable supply points — each with the method its baseline was worked out from stated in words rather than left as an enum. ## Recording a reading Recording a reading lives on this screen, not in settings — it's the operational act, and it belongs where the person transcribing a bill or reading a dial actually is. Configuring what's metered (commodities, tariffs, targets) is a decision made once when a contract's signed, and lives under [Configuring energy](/config/energy). Readings can also be taken on the [field app's](/field/offline-and-sync) dedicated meter-reading round, which covers both a utility supply point and an asset's own meter in the same walk and queues offline for exactly the rooms and basements a reading round usually means. ## Targets A reduction target is a commitment — so much less of a commodity over a named period, against what an earlier period actually used — set under [Configuring energy](/config/energy). Where each target stands (ahead, on track, behind, met, missed) shows here, because that's a fact about the meters rather than about the decision to set it. ## Weather and carbon Consumption can be **degree-day normalised** against an outdoor sensor, so "the boiler used more gas in January" and "January was colder" aren't the same finding. Every reading also carries a **carbon figure** (kg CO₂e) from the emission factor in force when it was taken — dated, so a cleaner grid later never restates a year already reported. ## On an asset An asset with a supply point pointed at it shows an **energy over the last year** panel on its Costs tab: what it used, what it cost, and its carbon figure, by commodity. An asset with nothing metered shows as **not metered** rather than as zero — the two are different facts, and the panel is deliberately built to keep them apart. Commodities, supply points, tariffs, emission factors, weather sources and targets.