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
❓ How to choose the most suited module format?
Only an advanced module (Manual processing) is available for this module so you have no choice but to use it.
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
Your client is encountering errors when uploading data on the end-to-end module, and asks you to check what is wrong with their file
👉 You should proceed to a series of checks to make sure that the data can be correctly processed:You have to save the data collection as a Google Sheet (make sure to copy it in the client folder)
Make sure columns are in the right order for each sheet
Make sure the data fits the template (drop down menus)
Make sure the data collection sheets name (template / archetype) fits the data processing import columns
3. Data processing
Ⓜ️ Manual processing
Link to the analysis template:
Notes
Verify there is no comma in the collect template
Verify that the amount of Impact per day (kgCO2e/day) is approximatively the same on the platform.
Verify the names of countries are accepted by the template (if the file of the client indicated some specific countries, then the calculation tab should also have these countries and not only “World” as country)
🧨 Debugging the analysis file
#N/A everywhere: On the analysis file, if you calculate BEGES, then you need to rename the sheet "Archetype" in the client's file to "Archétype." (this is necessary because the analysis file expects a French collection template for BEGES calculations, which isn't always the case.)
#DIV/0: If some entries or more display a #DIV/0, it is because some entries in the client file’s “Template” sheet have 0 worked days. You therefore need to delete these entries (because 0 worked days don’t produce any emissions)
Countries are not recognized in the calculation sheet (world when it should be something else): check the client file and ensure that all countries are spelled correctly
Data collection
Data collection template: GHG Protocol / BEGES
The clients will need to give information in two tabs: Archetype and Template.
Archetype is the tab where the client will select different options to build the archetypes that will be attributed to the consultants. 5 parameters are available:
Country
Which company is providing the IT equipment (your client or the other company)
The percentage of teleworking
The type of business travel (none, rail, air, car)
If the contractor is internal to the company, or working on an external mission. If it is an external missions (consultant of the company sent somewhere else for a mission), you’ll need to use different purchase categories - ask as it is a corner case and doesn’t represent the regular use of this module.
Template is the tab where your client will fill the name, company and number of days worked of the contractors, and connect them to an archetype previously built.
Data analysis
First, copy the template in your client’s folder and go to the tab “Calculation”.
There, you can copy/paste the URL of your data collection file (make sure to save it as a Google Sheet and save it in the client’s folder) in the cell “C10”, and give access to the import range formula by clicking on the yellow cell.
Select the right version of the data collection template:
If you used the French data collection template, the version should be “BEGES”, and “GHG” otherwise. Your data is automatically imported in the “raw data tab”.
If the template has been well followed, the calculation is totally automated. For each type of energy and unit available, the right EF is mapped.
Make sure the name of the tabs in the data collection file hasn’t changed (you can check if they are correct by clicking in the tab ‘Archetypes’ → “A1” (check the formula) and ‘raw data’ →”A1”. If it did, make changes directly onto the Data collection sheet.
Make sure you saved the data collection files as a Gsheet and not as a.xslx (otherwise you’ll not be able to connect your sheets) and that you saved it in the client’s folder.
The formulas can take a while to update; a trick to make them refresh is switching the “data collection template version”. You can also refresh your page directly.
Data export
Now is time to import data on the platform.
Go to the tab “To platform”.
You’ll find a table generated that you can download as a csv, and upload on admeenly in the advanced module “Consultants & Contractors”. All the emission factors are using an override under the “FREELANCE” purchase category.
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 numer 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
