Julien Beaumont SR TECHNICAL SPECIALIST

As a purchasing departement, I want to be able to do a factor mapping based on quantity and emission factors provided by suppliers if their is some.

I want to be able to fall back to a generic emission factor (typically Finance based EF using spend type) when there is no match on a more precise EF Mapping.

Would end up being

• Try
• Report (precise emission factor)
• Fallback
• Report (more generic emission factor)

On the calculation profile filtering, I'd like to be able to exclude from activities evaluated the activities that have been evaluated through another profile.

Example:

• If I run a specific algorythm "Boat" for boat transportation, I want to run a generic "transportation profile" that would exclude the boats thats matched the "boat" profile

Currently, numeric values are displayed with lots of unsignificant numbers, which decrease lisibility.

I would like in setting to adjust accuracy displayed on the interface.

I would like a power query connector for Google Sheets in MSM like Power Query Google Sheets connector - Power Query | Microsoft Learn.

It would be interesting to enable emission factor mapping for "an organization and all its child", not only the organization itself.

As of today, we need to list all child organization for emission mapping and remap when organization changes

Hello,

We are seeing asks from users to integrate a "range of accuracy" in calculation. Either because emission factor integrate their own accuracy, or because activity are estimated.

Would it be possible to apply a % of uncertainty to Activity cost, activity quantity and on Emission factor ?

Regarding calculation, would add in emission table a "uncertainty" that would depending on calculation model, apply uncertainty of emission factor to uncertainty of base data.

Example:

• Energy Consumption - Estimated - 12 MWh +/-7%
• Emission factor of energy : 200g/kwh +/-10%
• Emissions calculation : 2.4t +/-17,7%

It would be helpfull to be able to edit calculation model by enabling insert of a step in an existing calculation model. Example, adding a condition to an existing scenario require today to delete all steps post-condition.

Benefits:

• Avoid losing configuration when adding a step (and potential errors)
• Avoid the workaround : create another calculation model and switch the calculation profile. This workaround induce emissions to be linked to the old calculation model/the new one

Feature request : Add a reference data related to the Location of the end user/customer to apply related carbon intensity

Problem: When you sell product/services, the category 11 – use of sold products needs to calculate emissions based on the grid intensity of the product and services. The Grid intensity of the end user could vary

-         Country/location of usage is often possible for B2C product & services. Eg: mobile phone, laptop, electric car, setTop box

-         For B2B, customer account may be relevant. Eg: train, cables, servers…

Ask:

-         Create a new reference data : Location of Usage

-         Add a reference column to "Location of Usage" in the Activity data “use of sold product”

-         Enable emission factor mapping “reference data” with "Location of Usage"

Usage:

Calculation model for Use of sold product with this design would be:

-         Ingest activity data with Location of Usage

-         If Quantity is from Energy Unit Group

o  If yes : Apply an emission factor based on Location of Usage (and exist, Factor contingency feature)

o  If no : Apply an estimation factor to convert Quantity of product to Energy Consumption, then, apply an emission factor to calculate emission based on Location of Usage

It would be interesting to be able to build custom dashboard on the standard MSM product without having to deploy a datalake.

Typical example:

• dedicated Scope 3 - Purchased goods and services dashboard (rank suppliers, rank categories...)
• Row level security for "Organization unit centric" dashboards

Going through a customer dedicated datalake and customized powerbi necessitate a huge investment in time.

In the importation phase, setting up a fixed value for every column needs an addition in the "import" part, which complexify the flow.

Would be usefull to be able to map a destination field, either to a source column (like today) or a fixed, provided value.

Typical example is for Unit: EUR, KWH, km... or for specific columns like "data quality type", "ORganization unit type"...