1. Align with the client’s specific requests and choose the most suited module
👉 Clients might have specific requests for data processing → they will have an impact on which module format you should opt for
🎯 Examples of common requests
Client that wants some very specific EFs
Client has already their emissions calculated by their waste management company.
❓ How to choose the most suited module format?
🅰️ 100% automatic processing → Lightweight
This option must be favored as much as possible, as the client will be fully autonomous from data collection to data processing on platform.
Ⓜ️ Manual processing → Advanced module
When the options in the lightweight module aren’t enough, you can use the advanced one to get access to more specific EFs. Use the right database depending on the profile’s methodo and country >
2. When receiving the raw data
👉 This section is relevant for the following situations:
You are using the advanced module, hence manually processing your client’s data
👉 You should proceed to a series of checks to make sure that the data can be correctly processed:Make sure that the client followed the dropdown menus, and didn’t add something else
Make sure the correct unit is used (only “waste water and sludges” can be in m3, some clients put m3 for some hazardous/non hazardous waste)
3. Data processing
👉 Choose the most suited option below.
🅰️ Automatic processing
The lightweight module compute emissions automatically.
Ⓜ️ Manual processing
The manual processing is now highly automated!
Use this tool, make a copy of it.
Copy-paste your client’s data in the data collection sheet.
Find client data from your MC/activity data page
Tip: if there are multiple file, use the one with “data collection” tag as the raw data
Go to the Intermediate Import and change the country accordingly
France → BEGES
UK → UK
US → GHG P
If any line is highlighted in red, you need to go back in the data collection sheet and correct the data that is wrong (no ID could be found meaning the waste type is wrong)
If not, continue
Check the C1 cell and its percentage: This indicates what portion of waste weight doesn't match exactly with Waste Type + Treatment Type combinations in our database (e.g., client data shows Waste type: Cardboard and paper; Treatment type: landfilled, but our database only has Recycling for this waste type → this is considered as a proxy)
You can add manual EF id in column O and it will override the other id when you import (this could be used if you want to use specific EF, or if the matching algorithm of the sheet doesn’t find the right type/treatment)
♻️ Rebaseline
There are no rebaselining in the waste module as far as I know.
4. Data integration on SaaS
👉 With the E2E module, data integration on the client’s account will be automatic → No need to read further.
👉 In order to integrate data on the platform, you must go through the OneSchema process on the module from Admeely.
💡 For any information on Admeenly’s “Activity data” page or OneSchema, don’t hesitate to check the below page: “Add modules and begin your physical analysis: Activity Data ”
💡 Important specifics for data format in your export tab
Negative quantities will generate errors from OneSchema, make sure you don’t have any in your file
The algorithm does not accept number format with thousands separators (ex: 1, 563, 732.45, or 1 563 732, 45) → To make sure that the format is correct:
Remove any space as thousands separators (otherwise the format will be considered as text)
If you see any “,” as a decimal separator, convert them as points
Select your whole column > “123” in the control panel > Select “Automatic” (you should get 1563732.45 for the same example)
⚠️ Once you have followed OneSchema’s integration process and the algorithm is calculating emissions, check the status of your file at the bottom of the module:“Processing”: calculations from the algorithm are still ongoing
“Completed”: calculations are finalized → Emissions and visuals on the module are final, and you can set the module as “Done” on the Mission Control
“Processing error”: click on “See import logs” to check the source of the issue
It’s often due to an emission factor id that is no longer existing (database updates can happen) → You can check by yourself or with the R& M team what the correct id is
For any source that you can’t manage yourself (other than data format), check with the product team by creating a ticket
Once you have corrected the errors, you can go through the import process again until you the “Completed” status
