Knowledge transfer and communication with data owners are the be-all and end-all

In this part of our ESG diary, we once again report on the implementation of the IBM Envizi ESG Suite at the delta pronatura group of companies. This time you can read about the current challenges, questions and problems we are facing in determining and documenting technical aspects. 

In the last article in our ESG diary, I briefly talked about the IBM Envizi project method.  With this method, we and the sustainability experts at delta pronatura focus 100% on their technical analysis and reporting requirements instead of discussing functions and features with IT experts.

As the team is already ready to start implementation as quickly as possible, we involve them in the project's methodological approach. Specifically, the method provides for several workshops with the team to involve all colleagues, including management, and familiarize them with the method. There is a danger that we will realize at a later stage that we have invested unnecessarily in the wrong preparations, which will either not lead to the goal or will lead to it much later. We are particularly concerned with the gap between the desire for detailed information and available data. Remember: only what is recorded can be analyzed! An example: The breakdown of the energy consumption of a production line by individual products is desired, but only the total consumption is recorded. The breakdown by product, e.g. as a percentage, is possible retrospectively, but will depend on the accuracy of a possibly artificially estimated factor.

We are currently defining the basis for the “Master Data Matrix” (MDM), i.e. the master data for the evaluation, the digital copy of the relevant business processes. In this context, I would like to point out the importance of the term “dimensions”. This view into the future has proven to be helpful in designing analytical solutions that fit precisely. 

A standard part of the matrix, and included in the scope of Envizi, are also the structures required to complete the respective frameworks (in this case ESRS), including questions from the specifications and the appropriate fields for the answers. 

Here are some example lines that are necessary for filling in the ESRS framework:

So it remains exciting: as soon as the basis for the Master Data Matrix has been created, this task can be completed and the plan for the configuration can be drawn up. Stay tuned for the next blog, where I will report on the final coordination and the configuration activities, as well as the first data transfer. We will then report on the smooth handover to the customer, training measures and the transfer of tasks to the data entry users.