Caroline Kolmodin Palm

Factor libraries: When deactivating a factor library, that library should become "hidden". I'm looking for a similar functionality as for unit groups where you can filter on active / inactive unit groups. In addition, it would make sense to not being able to create new calculation models with inactive factor libraries. Not sure how to technically solve it, as for old calculations the old emission factors must still be shown. However I imagine that clients will get a lot of factor libraries as the years proceed and it will be a bit annoying to see all of them in the long list (as you should not use the ones that are inactive).

Emission factors: Currently, when deactivating an emission factor, that has no effect. The factor does not show as inactive in the overall library view, and you can still choose it for calculation models. Same resoning as above (factor libraries). It shouldnt be possible to set up new calculation models with inactive factors. If needed, then the user should activate the factor and then set up the calculation model.

Calculation models: It exists a filtering functionality for "active calculation models" but there's no functionality for actually inactivating a calculation model (where do you press "deactivate"?). I think that it is a great idea to be able to deactivate calculation models, for the same reason as above (there could in the end be a lot of old / current calc models in the list).

Facility should not be a mandatory field in purchased electricity. This is non applicable for electric company vehicles, these emissions are not connected to a certain facility but are to be reported in scope 2. I'm also sceptic to why Energy provider name needs to be mandatory. I understand that some activity type is needed to be able to use factor mappings and connect emission factors to reference data. For the vehicles, perhaps "region" or something similar would be more suitable than facility?

Currently, accounting method market / location based is asked for in all scope 2 categories. It should only be used / mandatory for purchased electricity.

• In the Carbon emissions data template, "Is market based?" should only be asked for in purchased electricity.
• In Emissions insight, when switching between location and market based method, scope 2 should only be impacted for purchased electricity. Other scope 2 categories should be unaffected (just like scope 1 is unaffected).

Furthermore, the box for "market based" in the calculation models should only appear in Scope 2: Purchased electricity. The same goes for All emissions, I dont understand why all other scope categories get "market based: no". This table should be left blank and only be used for purchased electricity.

When Microsoft push updates automatically, some configurations get undone and/or overwritten. This has happened several times and we have identified the following issues:

• Calculation profiles get back in the system, even if we had removed the standard profiles. The client's own profiles are still there.
• Calculation models get back in the system, even if we had removed the standard models. The client's own models are still there.
• Factor libraries get back in the system, even if we had removed the standard libraries. The client's own libraries are still there.
• Unit groups get back in the system and overwrite configurations made. The client had removed standard units and replaced them with custom ones, including changing the base unit. With the updates, Microsoft standard units are back in the system, together with the custom ones. The system also overwrites changes made to the base unit. E.g., if we had changed base unit to kWh, the base unit is now back to Joule. The conversion factors get messed up by this, which leads to faulty calculations.