CO2 calculation, fuel consumption type

[CAPcargo]

Hi guys

You provide these 4 input parameters for CO2 calculation regarding fuel consumption, I call them for now fuel consumption TYPES

• 1. Actual consumption
• 2. Route consumption
• 3. Vehicle consumption
• 4. Fleet consumption
• 5. HBEFA

Additionally the CO2 calculation requests a field with litre/kg of fuel consumption or kw for electric consumption.
We can input 1 numeric value of the fuel consumption, but theoretically all of the fuel consumption types.
Question: What do these fuel consumption types impact in the calculation at all?
If I input 35 litres with actual consumption, or 35 litres with fleet consumption, the result is the same.

Or do we misunderstand and is this fuel consumption (litres) input parameter (under vehicle profile) only meant for fleet consumption type and there are more fuel consumption fields for the other fuel consumption types?

Thanks, best regards
Oliver

[Joost]

I'm guessing you are using xServer 2, let me know if I'm wrong.

The RouteRequest.requestProfile.vehicleProfile.engine.fuelConsumption and RouteRequest.requestProfile.vehicleProfile.engine.electricityConsumption are only intended for the "Vehicle consumption" calculation. The fuel consumption for "Actual consumption", "Route consumption" and "Fleet consumption" need to be set in the RouteRequest.routeOptions.effectiveFuelConsumption . Note that HBEFA does not fuel consumption at all, it use formula to determine the fuel consumption based on the route properties and other vehicle properties.

And yes the fuel to CO2e conversion factor is the same for all use cases AFAIK.

[Bernd Welter]

Hello Oliver,

as a user you are supposed (by law) to use the "best approach" you can provide the required input data:

• Best case: You know the actual consumption on a specific trip (e.g. based on "started the trip full, had to fill up afterwards").
• If not: check the vehicle's average consumption (e.g. based on "I know via my tank card history the average consumption of the vehicle in charge")
• if not: check the fleets average consumption
• ...

Maybe the following articles can help, too:

• Usage Scenarios CEN 2012 (EN16258_2012)
• Emission calculation (v2.20 and later)

[CAPcargo]

Thanks Joost, yes we're using xS 2.

ok, much clearer, do I get correctly, we have 2 options to hand-over fuel consumption:

1. RouteRequest.requestProfile.vehicleProfile.engine.fuelConsumption
→ for type "Vehicle consumption"
2. RouteRequest.routeOptions.effectiveFuelConsumption
→ for type "Actual consumption"
→ for type "Route consumption"
→ for type "Fleet consumption"

If so:
- strange naming, isn't it? "...vehicleProfile" is only for vehicle consumption, not for other vehicle related (fleet and actual); and "...RouteOption" is not only for Route consumption... - however, not important
- My main question about the purpose remains open for me:
What do these fuel consumption types impact in the calculation at all?

If I input 35 litres with RouteRequest.requestProfile.vehicleProfile.engine.fuelConsumption for "Vehicle consumption" and 30 litres with RouteRequest.routeOptions.effectiveFuelConsumption for "fleet consumption" → Yes then I get 2 different results. OK.

But if I input 30 litres with RouteRequest.routeOptions.effectiveFuelConsumption for "fleet consumption" and also "route consumption" → Then I get 2 responses, both with same results. So what is the purpose of those parameters "Actual consumption", "Route consumption", "Fleet consumption"? Just for "documentation" where my consumption originates from?

Thanks a lot, Joost
Oliver

[CAPcargo]

Thanks Bernd, I understood the idea and difference of the different consumption types. But not the purpose of the real parameters, as they don't impact the result in any way, IMHO. The fuel consumption itself impacts the calculation. Therefore my question: I assume the consumption type is just for "documentation" where my handed-over fuel consumption comes from.