Elizabeth Lilly product manager

When importing data, MSM tallies successful ingestions as well as failures/ignored duplicates. The failures and duplicates are then able to be downloaded in spreadsheet form, which is quite helpful in diagnostics.

When running a calculation profile, successes/failures are also tallied, but there isn't a report to help determine which line(s) of data failed or why, which makes troubleshooting and rectification much more difficult. Having a downloadable report like is available in data imports would be a great addition.

It would be very helpful if employees' addresses (or just zip codes) could be added to the import for employee commuting. Then in either the transformation or in the calc model, MSM could calculate the distance they commute. Currently we are using an external application to calculate road distance between zip codes, but this is cumbersome, and we may not have this available to us in the future.

The standard view of Emissions Insights includes a chart of emissions over time. On our instance, this chart starts at 2018 even though we only have emissions data starting 2020. And the majority of our data is not shown because you have to scroll to the right to get to last year or current year. And after any filtering, it immediately scrolls back to 2018.

We (and probably most customers) are most frequently interested in this year and last year, so it would make sense to show people the newest data first. That could be through either only showing years with data and compressing the chart, defaulting to the right side of the chart, not having the chart return to the default position if anything is clicked, allowing the range to be set by users, reversing the time direction of the chart, etc.

Typical summations of data have drill down ability that can get all the way down to the raw data entries that went into a number. Emissions insights doesn't have that.

The Emissions Overview in Emissions Insights is a good way to quickly filter data to relevant sets. Once sufficiently filtered, sometimes I think the values aren't what I think they would be. It would be good to be able to drill into emissions numbers to bring this all the way down to the All emissions data that went into it.

As an example, if I've filtered data to a year and a division and I see a spike in a particular month in the emissions chart, I can click on it to see the breakdown by scope and sub-scope. If I see that Scope 3, 2 Capital Goods seems high, it would be good to then be able to click that and get a list of the All emissions that went into it so I can figure out if those values are wrong or in the wrong time.

As is, I have to go into All Emissions and try to filter the data the same way, which isn't nearly as convenient. To even find if I have the same filter, I have to export to Excel and sum the emissions to see if I get the same result.

Create a view where a facility/division could see why emissions changed from month to month or year to year and biggest influencers (changes in activity data and changes in emissions factors)

It would also be useful when applied to categories or the corporation for a corporate/auditing/policy view of why emissions changed from year to year and/or why baseline changed.

For people who have exhausted Emissions Insights and are trying to create summations and charts of their own, have a raw Power BI layer available for them to interact with All Emissions and Carbon Activities data.

Within scope subcategories, we often want to differentiate further. We've relied on Connection or factor library for that. However, that's not available in Emissions Insights.

Import jobs are accessible (for editing or even examination) only to the creator of that import. That job can be transferred by that user to someone else. The documentation says that it's possible for an admin to transfer import jobs.

However, users with an admin security role in MSM are not able to do this. It may be a global admin who can do this outside MSM. But we don't know. This gives us risk because our imports are complex, and if someone were to leave the company without transferring, we'd have to rebuild these jobs. And they aren't easy to document, so we wouldn't have much to go on.

I'd suggest that either the system is modified so that those in the admin security role are able to transfer import jobs or eliminate this ownership restriction. No other parts of the tool (like calculations or All Emissions) are restricted to the creator. Imports (from our perspective) aren't in more need of this "protection" than other functions.