Frequently Asked Questions

SixMap aims to transform greenhouse gas (GHG) emissions management and reporting from a compliance burden into a strategic advantage by:

• Automating data collection, aggregation, real-time emissions calculations, and automation of mandatory reporting data
• Reducing compliance costs
• Driving energy efficiency and cost savings
• Simplifying regulatory compliance (NGER & GHG Protocol)

We currently support Scopes 1 and 2, with support for Scope 3 planned for later in 2025.

Our position is that Scope 3 is much easer to  report accurately if every node in the value chain is calculating Scope 1 and 2 accurately.

Since many businesses start Scope 3 reporting from the 2026 reporting year, we're looking forward to working with feedback from SixMap users automating their Scope 1 and 2 Calculations to optimise the user experience and our calculation engine so Scope 3 is less burdensome and more accurate.  

In the meantime time, SixMap's open standards based approach means that providing sanitised Scope 1 and 2 data, or even Product Carbon Footprint data (PCF) to others in your value chain to enable their Scope 3 calculations is possible.

• Automated calculations replace manual processes  
• Built-in regulatory framework understanding
• Direct integration with CER's next-gen EERS
• Lower expertise requirements for system maintenance.

Data integration challenges are part of what SixMap was designed to handle. Reading text files, Excel spreadsheets, connecting to ERP,  Industrial systems like SCADA and even IoT are part of the new world of digital transformation.  Our roadmap includes support for emerging European data exchange formats and policies like Catena-X, Manufacturing-X, Aerospace-X etc, as well as support for Asset Administration Shells and Digital product passports.

SixMap's architecture also supports native connectivity to Industrial Automation and Process Control platforms enabling the accuracy afforded by Automated CEM and PEM techniques that can apply to Method 4 calculations.    

Yes! Data is stored in SQL, a standard compliant open source database format. We don't encrypt it or do anything unusual with the formatting. It's your data after all!

Yes! SixMap was designed to be incredibly scalable, and cater for large and complex corporate structures.

Yes! Even if you don't fall into the mandatory reporting net yet, you may have to provide emissions data to Group 1 companies as part of their Scope 3 compliance. SixMap can help by automating your emissions calculations right down to a process line, or even a single machine. You'll get the added benefit of better understanding the energy consumption and utilisation of that process as well!

It can be, yes!

Industry 4.0 is an initiative created in Germany and announced in 2011, designed to harness digital technologies to better optimise manufacturing operations by promoting connected systems and automating data flow between them. The original vision for Germany mentioned sustainability and resilience that could result from these systems being connected  not only within a business (vertical integration), but also between enterprises and related logistics (horizontal integration). 

SixMap sets out to deliver a core part of that vertical integration, connecting and automating the flow of data sources across the enterprise (Facilities and entities within a controlling corporation) to meet mandatory emissions reporting compliance.

But that's just the start. The way we've designed SixMap allows it to be built upon to integrate with full scale enterprise MES, ERP Integrations, Energy monitoring, Water monitoring, and environmental monitoring platforms. Many of our integration partners are delivering these types of projects now with the same platform.

If you haven't started an Industry 4.0 or digital transformation initiative, SixMap is a great place to start. If you're already on that Journey and have Ignition already installed at your site, chances are you can add the SixMap module and any of the dependencies, and be up and running quickly!