As a pilot, you have access to the emission factor creation feature.
To create an EF, you need to go to the administration section, then click on "Emission Factor" in the top banner.
Once you are on the list of emission factors, you can click on Add
To create your EF, you will need to fill in the following information:
The name of your EF: text field to enter the label of the EF in the desired language: French (required), German, English, Spanish, Italian, Flemish, Dutch, Portuguese (optional).
The keywords: these are important as they will allow you to find your EFs when you type keywords in the search bar during data creation.
A comment: this field is mandatory as it allows you to justify the assumptions made for your EF. For example, if you only took the combustion part of an EF for this creation, this is where you should indicate it. Feel free to add any information to this section that you believe is important for a good understanding of the EF.
The geographic location: the EFs are linked to a location and can greatly vary depending on it. It is therefore important to be meticulous with this field.
The categorization: in the Carbon Balance method, EFs are classified into different categories. Here, it is about finding one that corresponds to yours. If you do not know precisely where your EF goes, place it in the macro category that seems most appropriate.
The value: this is the numerical value of your EF. Use the point to mark the decimal. You can enter up to 5 decimals.
The unit: this is to complete the unit of your EF. Note, we are indeed talking about kgCO2e, and not tCO2e. If necessary, you may need to make a small conversion.
The uncertainty: every EF must have an associated uncertainty. As a reminder, monetary ratios have a high uncertainty (around 90%) while EFs that approach physical flow have a low uncertainty (around 10%).
The structure: some EFs are broken down by post, by gas, or both. For that, refer to this article.
The source version: it corresponds to the source of your EF. A certain number of databases are listed. If your source is not on the list, for example if it is an internal EF, you can contact your project manager, or otherwise Toovalu support.
The identifier: This field allows you to identify your EF. If you later have a new version of this EF (a version 2.0 for example), you will be able to re-enter the EF with the previously provided identifier and it will allow proposing the updates on the data using this EF in your collection templates.
You now know how to create an EF independently!