Management, finance and ESGBI, AI and ML for the business
Emissions and the sustainability report
Meter readings come from the utilities, emission factors sit in a spreadsheet and production in the ERP. In Muvia they become Scope 1 and Scope 2 emissions site by site, with every step checked from the raw reading to the figure ready for the report.
Illustrative scenario: it describes a typical case, not a customer project.
A number in the report should be able to say where it came from.
The sustainability report is put together once a year: bills and meter readings are copied into a spreadsheet, multiplied by emission factors and summed site by site. When someone asks why January is higher, you trace it back to the reading by hand.
Emissions are data like any other: if they arrive on a schedule, pass written checks and are calculated once, every figure can be traced back to the meter and the report does not start from zero each year.
- Who it's for
- ESG and sustainability leads, energy managers, the CFO and finance who sign the report; site managers for their own consumption.
In Muvia, step by step
Real product screens, recorded on a project with sample data.
The video · Meter readings come from the utilities, emission factors sit in a spreadsheet and production in the ERP. In Muvia they become Scope 1 and Scope 2 emissions site by site, with every step checked from the raw reading to the figure ready for the report.
What you get
- Every figure traces back to the meter
- From Gold to Silver to Bronze, each step is a query you can read: an emission can be followed back to the reading.
- Anomalies show up
- A fault or a wrong reading appears in the site's trend and in the Data Checks, not at year end.
- Changes can be measured
- Intensity per tonne shows the effect of a solar installation or a change at the site, month after month.
- The report does not start from zero
- The calculation is written once: next year the chapter regenerates on new data.
For the technical team
How it is built in Muvia
- 1
Connect readings, factors and production
Readings arrive from an SFTP folder: each new file is added to the rows already loaded. Emission factors come in as an Excel file, tonnes produced through an incremental copy from the ERP.
- 2
Clean and check, layer by layer
The raw readings are Bronze. A query turns them into clean daily consumption, the Silver; a Live Query works out daily emissions per site, the Gold, with Data Checks that keep impossible readings out.
- 3
Build the emissions dashboard
Tonnes of CO₂ for Scope 1 and Scope 2, a Sankey diagram from carrier to scope to site, the trend per site and the rolling intensity per tonne produced.
- 4
Write the environmental chapter
A notebook of text, KPIs and charts becomes the PDF of the environmental chapter, regenerated on fresh data whenever it is needed.
- The data it needs
- Gas and electricity readings for each site's meters, in the files the utilities make available
- Emission factors by energy carrier and year, from an Excel file
- Tonnes produced per site from the ERP on SQL Server
- Solar output at the sites that have panels
More cases in this line
All use cases- Margins and management accountingInvoices and costs sit in the ERP, customers and sales reps in the CRM, the budget in a spreadsheet. In Muvia they become one margin by customer and by product, with the Monday report and an alarm when the numbers drift from budget.
- Sales and pipelineThe CRM knows what is being negotiated; the ERP knows what was ordered and invoiced. Muvia joins them: pipeline and conversion with one definition, the customers who are ordering less, and Athena answering the sales team's questions.
- Month-end close and budget variancesThe ledger sits in the ERP, the budget in a spreadsheet, payroll costs with another provider. In Muvia they become one monthly income statement per business unit, with an EBITDA bridge against budget and the close commentary arriving as a PDF on day three.
Bring us a question you can't answer today.
We start from a real question your business has and walk the path from source to dashboard with your systems, not a demo dataset.