The Corporate Sustainability Reporting Directive (CSRD) is an EU regulation requiring companies to disclose detailed information about their environmental, social, and governance (ESG) impacts. It expands reporting obligations to include all large companies and listed SMEs, as well as non-EU companies with significant EU revenues.

The purpose is to provide stakeholders (investors, customers, regulators) with clear, reliable, and comparable sustainability data and to integrate sustainability into business decision-making.

Under the CSRD, companies must report in line with the European Sustainability Reporting Standards (ESRS). These standards aim to improve transparency and consistency in sustainability reporting, supporting the EU's climate and social goals.

Describe the key User profiles that exist for the application.

General role/Viewer role:

Approver role:

Target Users:

As examples: Controllers / Accountants

VERSION	DATE	MODIFIED BY	DESCRIPTION
0.01	dd.mm.yyyy	Fagr Nasser	Initial draft

Data Product Type	Dashboard Report Advanced analytics AI Others <specify which one>
Technologies	BW Power BI Qliksense Talend Dataiku Others <specify which one>
Data Sources	SAP PF1 (Production environment) SAP WP1 SAP PI1 BW (versions) iCare CRM CORE CRM Data Ingestion Template (Google Sheets)

2.0 Business Process

Capture the business process that the application supports . This can be describe through a process diagram or a business capability model.

2.1 KPIs References

Refer to the file: DTT Gap Assessment ESRS analysis Reporting Standard design
For further details, access the Commission Delegated Regulation (EU) supplementing Directive 2013/34/EU of the European Parliament and of the Council regarding sustainability reporting standards. (link?)

3.0 ESRS Reports Overview

Data Collection Templates (Manual)

ESRS Code	Description	Link
E1	Climate Change	CSRD \| E1 Climate Change
E2	Pollution	CSRD \| E2 Pollution
E3	Water and Marine Resources	CSRD \| E3 Water and Marine Resources
E4	Biodiversity and Ecosystems	CSRD \| E4 Biodiversity and Ecosystems
E5	Resource Use and Circular Economy	CSRD \| E5 Resource Use and Circular Economy
G1	Business Conduct	CSRD \| G1 Business Conduct
S1	Own Workforce	CSRD \| S1 Own Workforce

4.0 Business Objects

This section should contain a table with the business objects used in the reports with links to the business object definition in LeanIX. The purpose is to ensure that all DA&AI Products adhere to a centrally maintained list of business objects and definitions to allow us to achieve our digital ambitions. For any questions about business objects and LeanIX, contact Data Governance or the Enterprise Information Architect.

Data Domain	Business Object (in LeanIX)	Business Object Definition (only use when the object is not yet in LeanIX)
ex: Marketing & Sales	ex: Customer

5.0 Data Architecture

5.1 Data Capturing

Talend for Batch Processing:

Data collection is initiated through Talend batch processes, which extract raw data from both automated and manual sources.
- Automated Sources: Systems such as SAP BW, SAP ERP, SAP SuccessFactors EC, SAP BFC, WAVE, NAVEX, and PURE;
- Manual Sources: Includes Google Sheets and other manual templates.

5.2 Data Ocean

The Data Ocean serves as the central hub for storing, processing, and normalizing data to support CSRD metric and KPI calculations. It is structured as follows:

Storage:

Raw data is collected and stored securely.
Normalized data is prepared for downstream processes.
Google Cloud Platform (GCP):
The Data Ocean utilizes GCP services such as Cloud Storage and BigQuery to process and store data efficiently across environments:
- Dev - link
- Test - link
- Prod - link

Curation:

Data Quality (DQ) Measures: Implemented to standardize data quality processes.
Data Validation: Ensures accuracy and reliability of input data.
Data Consolidation: Combines various data sources into a cohesive format.

Provisioning:

CSRD Metric, KPI, and Target Data Models are generated to support reporting and analysis.

5.3 Validation Process

KPIs are reviewed and validated through Jira workflows, allowing for user collaboration and audit logging.

Workflow phases include:

KPI review and input;
Analysis and comments;
Final sign-off by KPI owners;
Data Approver will sign-off the KPI.

5.4 Data Consumption

The validated data from the Data Ocean is used for multiple reporting and analytical purposes:

CSRD Report Pack:
Official CSRD reports are generated and shared with auditors.
Performance Tracker:
Tracks KPI performance against planned targets.
Audit Analysis:
Provides insights into data lineage and compliance requirements.

Data visualization is achieved through Power BI report, which offer comprehensive insights into the reporting process and KPI granularity, that can be accessed via the following link: LIINNKKK

5.5 Data Management and Operation

Data Management Features:

Data cataloging for better accessibility.
Workflow orchestration to manage data processes efficiently.
Continuous data audits for compliance and traceability.

Operational Features:

Monitoring and workload management ensure system reliability.
Data security protocols are implemented to safeguard sensitive information.
Backup and CI/CD processes support system robustness and scalability.

These processes are not isolated to a single stage but are integrated across all steps, from data capturing to data consumption. They ensure that data quality, consistency, and compliance are maintained at every stage of the CSRD flow.

6.0 Data Visualization

The purpose of this part is to describe the physical components that supports the functionalities of the product. From that point of view, this part should capture and visualizes the physical components of the data products such as backend, front end, data providers, libraries for ML models, etc.

Deep dive into power bi

7.0 Non-functional Descriptions

Please populate the relevant section and delete those that are not applicable.

7.1 Usability

Usability is about the ease with which a User can learn to start using the solution and the ease with which they can use the system. In addition to ease of learning and ease of use, usability also includes areas such as ease of recall, error avoidance and handling, accessibility among others e.g., 99% of metadata entry Users who have use the Maintenance Dashboard should be able to change filters, extract etc., when required. Maintenance data will be centrally stored in the Google Cloud platform, which will be available to other applications e.g., and Dashboards if needed.

7.2 Regulatory Compliance

Software systems must comply with legal and regulatory e.g., GDPR requirements, this can change depending on country, organisation industry and / or region. The software systems must be secure from unauthorized access. The Maintenance Dashboard will comply with Solvay’s regulations and compliance e.g., access only granted to authorized Users.

7.3 Security

Security refers to essential aspects that assure a solution and its components will be protected against unauthorized access or malware attacks. Important considerations related to security aspects of a system are User authentication, User authorization or User access privileges, data theft, malware attacks, data encryption, and maintaining audit trails, e.g., only Users with administrator access shall be able to create new accounts and assign data access privileges to the new accounts e.g.,

All data will be encrypted in the dashboard
Only authorised Users / Administrative Users will be able to access data.
Maintenance data will be split between either SCO or ECO, and Users will only have authority to one Entity data.

7.4 Performance

Performance defines how fast a software system or a particular section of it responds to certain User actions under a certain workload. In most cases, this metric explains how long a User must wait before the target operation happens e.g., the page renders, a transaction is processed, etc., given the overall number of Users now. Performance requirements may describe background processes invisible to Users, e.g., backup and speed of data transfers.

7.5 Reliability

Reliability is the ability of a solution or its component to perform its required functions without failure under predefined conditions for a specified time / period. Reliability can possibly be specified in terms of average time system runs before failure occurs, percentage of operations completed successfully within a time / period, maximum acceptable failure probability, or number of failures within a period. Reliability aspects are in reference to (but not limited to) evaluation of the system to be considered as reliable, classification of reliability defining failures vs. regular failures, and the impact of failure on business operations. The Maintenance Dashboard will display data from the previous refresh of data.

7.6 Scalability

Scalability refers to the degree to which a solution can evolve to handle increased amounts of work. The increased amount of work could be in terms of the user base, transactions, data, network traffic, or other factors e.g., the system should be able to handle an additional load of a maximum of 5,000 Users every month for the next 6 months without any noticeable performance impacts.

7.7 Compatibility

Interoperability is the degree to which the solution is compatible with other components. It is a measure of how effectively the system interoperates with other software systems and how easily it integrates with external hardware devices.

Interoperability aspects to be discussed during elicitation are in reference to (but not limited to) software systems to be interfaced with along with data / messages to be exchanged and any standard data formats, hardware components to be integrated with, and any standard communication protocols to be followed e.g., Order Management system will push the order file into a secured file transfer protocol server from where it will be loaded into the system through a daily job. To guarantee between Google Cloud platform and SAP BW Queries e.g., BW_QRY_MVPMOR01_0002, Solvay has introduced a new tool called Xtract (Xtract).

7.8 Availability

Availability is the degree to which the solution is operable and accessible when required. It is a measure of time during which the system is fully operational e.g., available for use and sometimes included as a Service Level Agreement (SLA) considering its criticality to the business, e.g., the system shall be at least 99% available on weekdays between 09:00 to 18:30 Central European Time (CET).

7.9 Refresh of the Data

Frequency, data, and time of the data refresh in the data product.

1.0 Overview