1.Purpose of the file
This file is used to collect and centralise the mapping between Syensqo production sites and their energy vectors for Product Carbon Footprint (PCF) calculations.
For each combination of GBU, year, site, plant, and energy vector, it records the vector code (sourced from CERISE), the production/consumption indicator, the BOM activity code, the energy type, and any relevant comments.
The data supports the correct assignment of energy-related emission factors across all Syensqo sites and reporting years.
2. File Structure
2.1. List of tabs
| Sheet Name | Description | Mandatory | Comment |
| Sheet1 | Main data entry sheet. Maps each site / plant / energy vector combination to its energy type and BOM activity code. | YES | Don't delete this sheet |
2.2. Main columns description
SHEET: Sheet1
| FIELD | GBU | intermediate_product_plant | intermediate_product_plant_name | prod_year | energy_type | Correction_factor | Comment_reason_for_correction | DQR | PDS |
| DESCRIPTION | SAP code of the Global Business Unit. | Unique SAP code assigned to the plant where the material is produced. | Unique SAP name assigned to the plant where the material is produced. | Calendar year for which the energy correction is applied. | Energy type for which the correction factor is computed. | Multiplication factor applied to CERISE energy quantities to correct them to actual consumption. A value of 1 means no correction is applied. | Free-text explanation of the reason for the correction, including source data references (e.g. IMEP vs CERISE quantities). | Data Quality Rating. Non-qualitative by design, as this file alternates CERISE data with manually sourced data. | Primary Data Share. Non-primary by design, as this file alternates CERISE data with manually sourced data. |
| DATA TYPE | String | String | String | String | String | Float | String | Float | Float |
| MANDATORY | YES | YES | NO | YES | YES | YES | NO | NO | NO |
| VALIDATION / ALLOWED VALUES | e.g. CS (Novecare), SP (Specialty Polymers), TS (Technology Solutions). Validated against known GBU list. | e.g. 0246, 8192, 8160 | e.g. 7424 Blue Island, 6526 Zhangjiagang | e.g. 2022, 2023, 2024, 2025 | GAS | ELECTRICITY | STEAM | FUEL | BIOMASS | STEAM_LP | STEAM_HP | Must be > 0 and ≤ 10. Values outside this range are invalid. | Free text; e.g. "In IMEP 6850 MWh, In Cerise 7942 MWh" | Typically 1 | Typically 1 |
3. Filling instructions
| Sheet Name | Instructions |
| Sheet1 | • Complete all mandatory fields for every row. Rows with missing mandatory values will be rejected during upload. • GBU must match a valid GBU code (e.g. CS, SP, TS). Values not in the validated list will be rejected. • energy_type must be one of the accepted values: GAS, ELECTRICITY, STEAM, FUEL, BIOMASS, STEAM_LP, STEAM_HP. • Correction_factor must be a positive float greater than 0 and no greater than 10. Use 1 when no correction is needed (default – no correction). • Comment_reason_for_correction should clearly reference the data sources used to justify the correction (e.g. IMEP vs CERISE quantities with units). • DQR and PDS are not mandatory. They are set to 1 by convention for this file, as the data alternates between CERISE and manually sourced values. • Do not modify, add, or remove columns. • Duplicate rows (same GBU + intermediate_product_plant + prod_year + energy_type) will be rejected during data upload. Ensure no duplicate entries are present. • Do not leave mandatory fields blank. |
4. Maintenance best practices
Please comply with the following instructions to maintain the file:
• Always keep the original structure (do not add/remove columns without approval).
• Update only the necessary fields.
• Save a backup copy before any major changes.
• Respect data confidentiality.
5. Contact Points
| File owner | Hubert Sizaret |
| Technical Support | Camille Faure Laëtitia Arantes |
For any questions or issues, please contact the responsible person listed above.
Please strictly follow these guidelines to ensure data quality and reliability.