The ‘total’ value represents the sum of the four specific emission categories.

Although not specifically demanded by the ISO 14067 reporting requirements, Mattermaps requests the user to enter the total value to ensure compatibility with other PCF reporting standards.

In the current Mattermaps version, the user needs to enter the total value manually into the respective field. No automatic fill out option or mathematical check-up with regard to the specific GHG emissions is provided.

According to ISO14067 a partial PCF may be gate-to-gate, thus some life cycle stages may be omitted if transparently stated.

In order to enhance transparency over the emissions along the life cycle stages the user has to make the following decisions/statements:

Whether a life cycle stage is:

included in the PCF — means that this life cycle stage is covered completely in the PCF. This statement does not mean that the emissions for this stage need to be provided as a separate figure, but that it is part of the total.

excluded from the PCF — a cut out or systematic cut off. Although the life cycle stage is part of the product, it is an active decision to not include it in the PCF, for example upstream transport. Some initiatives might define in their PCRs generally not to account for packaging, if it is usually very small.

partially included — meaning that a sub-life cycle stage is excluded, and therefore the respective higher-level life cycle stage is not complete.

not applicable — this statement helps the user to report that this life cycle stage is not part of the product system and that it is not possible to report a value at all, for example the installation phase of products would not be an applicable life cycle stage for fuels. This is different from the active decision of cutting it out.

not specified — this statement represents the least information and should be selected if it is not known whether the life cycle stage is included or if the user does not want to provide such information.

For which life cycle stages the emission values will be provided.

For each sub-life-cycle stage, the user has the option to enter emission values.

At a minimum, Mattermaps requires values for the so-called “production stage”, and for this stage the four emission categories fossil, biogenic, direct land use change, and aviation, if ISO 14067 is selected.

As a general rule, the sum of emissions from sub-level life cycle stages shall not be greater than the emissions of the respective higher-level life cycle stage. For example, for distribution stage as the higher level, the emissions shall be equal to or higher than the emissions reported for Transport A as the sub-level.

In the current Mattermaps version, all values have to be entered manually. Mattermaps does not provide an automatic sum-up of all emissions at sub-level or check-up yet if numbers match. The user is responsible.

Although is not mandatory to upload your BOM (Bill of Material) data to Mattermaps it is useful and will help you with your PCF accounting.

As BOM contains the components and the amount of the components, we use this information to aggregate the upstream emissions of your product.

Following our promise of data sovereignty, the BOM data and description of materials it is not used by Siemens. The data is encrypted and stored safely, only your company users can see this data, and even then users have different rights to see this data.

We refer to a third party certification to those verifications that are being officially provided by a certifying company. A self-certification is the one that does not count with a third-party review but in which the company creating the PCF backs the data with their name, and following a chosen standard.

You can think of it and sharing information with a signature, it has its own validity but has not been reviewed. We understand that certification will not make sense to all Mattermaps users, and because it has a cost that specially small suppliers may not be able to bear; third-party certification is not needed.

Mattermaps is designed in such a way that you can complete your tasks intuitively and quickly. One of the most important functions is the exchange of emission data between you and your partners.

So that you can see at first glance to what extent the quality and reliability of the data is guaranteed, each PCF in Mattermaps is assigned a color-distinguishable Trust Level depending on the certification status.

Mattermaps distinguishes between the following trust level options:

Self-published: self-exhibited PCF, without external certification.

Certified: certified by an independent accredited body, name of the certifier in brackets.

Certification pending: certification applied for, certificate pending.

Expired: certificate has exceeded its validity.

Revoked: certification revoked due to incorrect information or company does not wish customers to use that information anymore.

Withdrawn: withdrawn PCF.

The status of the PCF is displayed wherever necessary in Mattermaps. For example, in the dashboard overview, in the PCF records of the product overview, in the overview of PCFs when sending data and in the overview of the received PCFs in the "Bill of Material" tab.

A PEFCR is a Product Environmental Footprint Category Rule. This is an industry specific guidance of the PEF-System.

The PEF System requires you to calculate several impact categories, such as CO2e, abiotic resource depletion, and others. If a PEF has been calculated, the CO2e values from that PEF can be used in Mattermaps as a PCF, or Product Carbon Footprint.

But from a PCF in Mattermaps, you can’t create a full PEF, since the other impact categories are missing.

Yes, that's right a PCF can be valid yet expired. So let's untangle this mystery.

A PCF can have multiple statuses:

Self-published: The company sharing the proof calculated the component PCF.

Certified: The company sharing the proof had a third-party verifier reviewing the information for this component PCF.

Expired: The company sharing the proof set an expiration date. While the proof may still be valid, it would be a good idea to request an updated proof for this component.

Revoked: The company who shared this proof with you has revoked your access and you are not able to use it any longer.