Environmental & Energy Management System Suite
Carbon Management System
Carbon figures are usually built when a report is due. Activity data is gathered from electricity invoices, gas meters, fuel cards, travel claims, purchasing records and supplier questionnaires, assembled into a spreadsheet, turned into a number, and handed over. The next disclosure starts the same work again.
Carbon Management System turns that into a ledger. Activity data comes in from the energy, production, purchasing and finance systems already running, is organised by scope one, two and three, is paired with the factors and boundaries you have chosen, and every figure keeps a record of how it was produced. It shares the same activity data as Energy Consumption Management — collected once, used in both places.
A carbon figure is worth what its evidence is worth. Auditors, customers and regulators rarely ask only what the number is; they ask where it came from, which factor was used, whether the boundary is the same as last year, and what has changed since. A ledger exists so those questions can be answered.
You cannot report what you cannot reproduce.
What it is
One structure for all three scopes. Direct emissions, purchased energy and value chain emissions are organised under the same boundary and the same rules, rather than being worked out in three separate spreadsheets.
A ledger, not an annual snapshot. Every figure carries its activity data, the factor applied, the factor version, the boundary it was calculated under, and its revision history. How last year was calculated is still available.
Activity data from systems already running. Energy, output, purchasing, fuel, transport, travel and waste data come from the systems that already hold it, with as little re-keying as possible — and shared with energy management rather than collected twice.
Factors are yours to manage. Factor libraries are imported and maintained with source, version and effective date. When a factor changes, whether history is recalculated or kept on the original basis is a decision that is configured, not an accident that is discovered.
Footprint down to the unit. From the ledger to the product: carbon footprint per unit, per batch or per order, using the same output data that sits behind energy per unit.
Reductions accounted separately. Reduction projects carry their own baseline, boundary and accounting period, and are kept apart from the inventory they are measured against, so the two are not mixed together.
What gets in the way today
The numbers are everywhere, the evidence is nowhere. Data is collected; how it was produced is not.
Activity data is spread across invoices, meters, fuel cards, expense claims, purchase records and supplier questionnaires. Each with its own format and its own timing.
Every disclosure collects it again. And the collecting itself is where the boundary drifts.
Where a particular figure came from is known only to whoever built that sheet. Which is often nobody currently in the role.
What gets handed over is a result, not a process. So when it is questioned, there are no steps to show.
Scope three is the hard part. The difficulty is data, not arithmetic.
Supplier data is unavailable. Or available only as a statement that it is not measured.
Where it is unavailable, it is estimated from spend. An estimate and a measurement are not the same quality, but they end up in the same total.
Different customers send the same supplier different questionnaires. So the answers that come back cannot be reconciled with each other.
Data quality is not graded. Which leaves a measured value and a rough estimate looking identical in the table.
Every report is a rebuild. Nothing carries over except the work.
Factors change, and two years stop being comparable. Without anyone being able to say exactly where the difference sits.
Last year's calculation cannot be reproduced. Because the sheet was assembled by hand and the formula was written on the day.
Boundary changes, reorganisations, acquisitions and disposals break the series. And rebuilding the history is not feasible.
When audit asks how a figure was produced, the answer is a search through old messages. Which is not an answer.
Reduction claims that do not survive scrutiny. The saving is stated; the basis is not.
The baseline year, boundary and accounting period behind a reduction are not written down. So the reduction cannot be checked.
An efficiency project finishes, energy falls, and the carbon equivalent is not derived on any stated basis. So it cannot be reported.
Reduction and operational improvement are reported separately. And the two sets of figures do not agree.
The result never reaches the disclosure. Because there is nothing to give an auditor to re-perform.
What it accounts for
Three scopes, and underneath them the question of where each figure came from.
Scope | What it covers | Where the activity data usually comes from |
Scope 1 — direct | Fuel burned on site, own vehicle fleet, process emissions, fugitive releases | Energy and metering systems, fuel purchasing, equipment records |
Scope 2 — purchased energy | Purchased electricity, steam, heat and cooling | Energy management systems, invoices, supplier settlement |
Scope 3 — value chain | Purchased goods and services, upstream transport, waste from operations, commuting and business travel | Purchasing and ERP, logistics, waste contractors, travel and expenses |
Figures are graded by how they were produced, so an estimate is never presented as a measurement.
Grade | What it means | How it is used |
Measured | Taken from a meter or a system record | Enters the inventory directly |
Calculated | Derived from activity data and a factor | Records the factor and version applied |
Supplier-provided | Reported or issued by a supplier | Records the source and when it was obtained |
Estimated | Derived from a proxy or from spend | Marked and reported separately, so improvement can be prioritised |
The system organises, calculates and reports on the methodology and boundary you choose: where the boundary sits, which categories are included, which factor set is applied, and how history is treated are all configuration, decided by the user. The system does not decide whether a result meets any particular disclosure requirement or standard — that judgement belongs to the external auditor, the customer or the regulator. Factor libraries are imported and maintained by the user; this product supplies no emission factor values and endorses none.
What you get
Where it is used
What changes between these settings is which scopes dominate, which activity data is hardest to obtain, and who is asking for the result.
Setting | What the carbon work usually focuses on |
Export manufacturing and brand supply chains | Footprint questionnaires from customers, product-level data, and evidence that can be re-performed |
Groups with multiple plants | Consolidation on one basis, comparison between plants, and a series that stays continuous |
Energy-intensive process industries | Process and fuel emissions in scope one, purchased energy in scope two, reduction projects accounted separately |
Automotive parts and machinery | Supplier data collected up the tiers, graded by quality rather than treated as equivalent |
Electronics and semiconductor | Purchased electricity dominating the profile, and the structure of that consumption |
Food, beverage and central kitchens | Cold chain and processing energy, packaging and waste, transport |
Capabilities
Grouped by what they do. Energy measurement, allocation and cost sit with Energy Consumption Management; this application turns that activity data into carbon data.
Capability | What it means |
Organisational boundary | Configure which entities, sites and facilities are included, and how they roll up. |
Reporting period and baseline year | Set the periods reported and the year reductions are measured against. |
Category inclusion rules | Decide which categories are in and which are out, and record the reasoning against the boundary. |
Scope 1 | Activity data and calculation for fuel burned on site, own fleet, process emissions and fugitive releases. |
Scope 2 | Purchased electricity, steam, heat and cooling, sharing the collection already done for energy management. |
Scope 3 | Purchased goods and services, transport, waste, commuting and travel, with supplier collection and submissions managed. |
Data quality grading | Mark figures as measured, calculated, supplier-provided or estimated, and report the mix rather than hiding it. |
Estimation recorded | Where estimation is used, record the proxy or basis, so it can be revisited and improved. |
Factor library management | Import and maintain factors with source, version and effective date. |
Factor versioning | Decide whether a factor change recalculates history or leaves prior periods on the basis they were reported under. |
Ledger and traceability | Each figure keeps activity data, factor, version, boundary and revision history, with changes logged. |
Approval and locking | Review, approve and lock a period; later changes go through approval and remain visible. |
Product footprint | Carbon per unit, per batch and per order, against output from production systems. |
Reduction accounting | Register reduction projects with their own baseline, boundary and period, kept separate from the inventory. |
Restatement and comparison | Recalculate after a basis change and show what moved between one version and the next. |
Reporting output | Produce inventory, disclosure, footprint and reduction results in a structure you configure. |
Integration | Energy management, production systems, purchasing and ERP, finance, travel and expenses, waste contractors. |
Deployment choice | Run in the cloud or on your own servers, usually decided by where the underlying data may be processed and stored. |
Access and retention | Role-based access, retention set by policy, with access and changes logged. |
How it works
Set the boundary. Organisational scope, reporting period, baseline year and which categories are included.
Bring in activity data. From energy, production, purchasing, finance and travel systems — sharing the collection already done for energy management rather than collecting it twice.
Choose factors. Import and maintain the factor library with source, version and effective date, and set how history is treated when they change.
Calculate and grade. Organise by scope one, two and three, and mark every figure as measured, calculated, supplier-provided or estimated.
Review and lock. Check, approve and lock the period; changes after locking go through approval and stay visible.
Report and carry forward. Produce inventory, disclosure, footprint and reduction results, and continue from the existing ledger next period instead of rebuilding it.
Method, boundaries and what it does not decide
Methodology is chosen by you. Boundary, categories, factors and basis are configuration. The system calculates on the basis you select; it does not select it for you.
It does not judge compliance. Whether a result meets a disclosure requirement, a standard or a customer's specification is judged by the external auditor, the customer or the regulator. This product provides no such conclusion.
It supplies no factor values. Factor libraries are imported and maintained by the user. No emission factor values are built in and none are endorsed.
History stays explainable. When a factor or boundary changes, recalculation or retention of the original basis is configurable, and either way the change and its effect are recorded.
How it divides the work with energy management. Energy Consumption Management measures, allocates and costs energy. This application turns that activity data into carbon figures. The former does not perform carbon accounting; the latter does not repeat the collection.