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 | year | site_code | site_name | plant_code | plant_name | vector_code | prod_conso_indic | pattern_in_bom_activity_code | energy_type | Comment |
| DESCRIPTION | SAP Code of the Global Business Unit. | Calendar year for which the PCF energy mapping is reported. | CERISE Site Code identifying the Syensqo production site. | CERISE Site Name corresponding to the site code. | SAP Plant Code identifying the plant within the site. | SAP Plant Name corresponding to the plant code. | Vector Code defining the energy type and activity at the site level. Source: CERISE. Examples include PU_GAS (purchased gas), PU_EL_NREN_MPL (purchased non-renewable electricity), UT_ST_DIS (utility steam distributed). | Indicates whether the vector relates to production (P) or consumption (C) of a specific energy type. Source: CERISE. | Activity code of the energy type as it appears in the Bill of Materials (BOM). Possible values: GAS, ELEC, STEAM, TFLUID. | The broad type of energy associated with the vector code. | Free-text field for additional notes or clarifications inserted by the data owner. |
| DATA TYPE | String | String | String | String | String | String | String | String | String | String | String |
| MANDATORY | YES | YES | YES | YES | NO | YES | YES | YES | YES | YES | NO |
| VALIDATION / ALLOWED VALUES | e.g. "CS" (Novecare), "SP" (Specialty Polymers), "TS". Validated against known GBU list. | e.g. 2022, 2024, 2025 | e.g. 1307, 1386 | e.g. AUGUSTA, GA | e.g. 0241, 8160 | e.g. 7424 Baltimore | e.g. PU_GAS, PU_EL_NREN_MPL, UT_ST_DIS, PU_EL_SOL | C (Consumption) or "P" (Production) | GAS | ELEC | STEAM | TFLUID | GAS | ELECTRICITY | STEAM | FUEL | BIOMASS | STEAM_LP | STEAM_HP | Free text |
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. • vector_code is sourced from CERISE and defines the energy type and site activity. Do not invent or modify vector codes. • prod_conso_indic must be either "C" (Consumption) or "P" (Production). • pattern_in_bom_activity_code must be one of: GAS, ELEC, STEAM, TFLUID. • energy_type must be one of: GAS, ELECTRICITY, STEAM, FUEL, BIOMASS, STEAM_LP, STEAM_HP. • Do not modify, add, or remove columns. • Duplicate rows will be rejected during data upload. Ensure no duplicate entries are present in the sheet. • 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.