DEVICE AND METHOD FOR HANDLING A DATA ASSOCIATED WITH ENERGY CONSUMPTION OF A VEHICLE

Abstract

A method performed by a device for handling data associated with energy consumption of a vehicle in operation. The device obtains modelling data associated with energy consumption of a model vehicle. The modelling data are generated by a digital model of the vehicle in operation. The device obtains operating data associated with energy consumption of the vehicle in operation. The device compares the operating data to the modelling data. Based on a result of the comparing, the device detects a discrepancy between the operating data and the modelling data and associated with the energy consumption. The device evaluates the detected discrepancy associated with the energy consumption. The device triggers an operation when the discrepancy has been detected.

Claims

1. A method performed by a device for handling data associated with energy consumption of a vehicle in operation, the method comprising: obtaining modelling data associated with energy consumption of a model vehicle, wherein the modelling data are generated by a digital model of the vehicle in operation; obtaining operating data associated with energy consumption of the vehicle in operation; comparing the operating data to the modelling data; based on a result of the comparing, detecting a discrepancy between the operating data and the modelling data and associated with the energy consumption; evaluating the detected discrepancy associated with the energy consumption; and triggering an operation when the discrepancy has been detected.

2. The method according to claim 1, wherein the evaluating the detected discrepancy associated with the energy consumption comprises one or more of: evaluating energy consumption of the vehicle in operation; detecting malfunction of the vehicle in operation; determining a reason for the discrepancy; determining a vehicle configuration change; and determining a vehicle operation change.

3. The method according to claim 1, wherein the operation comprises one or more of: providing information associated with the discrepancy; triggering an alert; initiating scheduling of a service operation; and requesting input from a user of the vehicle in operation.

4. The method according to claim 1, wherein the modelling data and the operating data are both based on static data and/or dynamic data.

5. The method according to claim 1, comprising: obtaining a statistical distribution of the modelling data; and wherein the comparing the operating data to the modelling data comprises: comparing operating data to the statistical distribution of the modelling data to determine if the operating data is according to the statistical distribution or not.

6. The method according to claim 1, wherein the evaluating the detected discrepancy associated with the energy consumption comprises: determining a user anticipation score for a user of the vehicle in operation, wherein the user anticipation score is: user anticipation score ˜ $f\left(\frac{\mathrm{w\_overall}}{\text{?},\text{?},\text{?}}\right),\text{?}\text{indicates text missing or illegible when filed}$ where W: weight impact ˜α*w.sub.light+β*w.sub.medium+γ*w.sub.full B: brake impact ˜ $\max \left(\frac{\mathrm{brakes}-\mathrm{stops}}{\mathrm{stops}},\mathrm{brake\_max}\right)$ S: speed impact ˜ $\frac{v-v_{\min }}{v_{\max }-v_{\min }}$ α, β, γ, δ, ε, ζ, w.sub.overall, brake_max: real value scalar parameters w_overall: overall weight brake_max: max limit for a brake impact f: a normalized sigmoid function that maps any real value to a value between 0 and 1 w.sub.light, w.sub.medium, w.sub.full: a ratio of km driven with light, medium and full weight load respectively v: an average speed and speeds outside v.sub.min or v.sub.max will be clipped to those values.

7. The method according to claim 1, wherein the evaluating the detected discrepancy associated with the energy consumption comprises: determining a user eco score for a user of the vehicle in operation, wherein the user eco score is: eco score ˜ $f\left(\frac{w_{\mathrm{overall}}*\text{?}}{O^{\theta }*N^k*S^{\mu }}\right),\text{?}\text{indicates text missing or illegible when filed}$ where W: weight impact ˜α*w.sub.light+β*w.sub.medium+γ*w.sub.full O: overload impact ˜ $\frac{1}{\phi }*\frac{\mathrm{t\_overload}}{\mathrm{t\_total}}$ N: not in green zone impact ˜ $\frac{1}{\xi }*\left(\max \left(\min \left(\frac{l_{\mathrm{notgreen}}-l_{\mathrm{avg}}}{l_{\mathrm{avg}}},0\right),1\right)\right)$ S: speed impact ˜ $\frac{v-v_{\min }}{v_{\max }-v_{\min }}$ η, θ, κ, μ, φ: real value scalar parameters w.sub.overall: an overall weight φ, ξ: normalization factors f: a normalized sigmoid function that maps any real value to a value between 0 and 1 w.sub.light, w.sub.medium, w.sub.full: a ratio of km driven with light, medium and full weight load respectively $\frac{\mathrm{t\_overload}}{\mathrm{t\_total}}:$ a ratio of time spent in overload l_notgreen: liters per 100 km spent above the green zone l.sub.avg: liters per 100 km v: an average speed and speeds outside v.sub.min or v.sub.max will be clipped to those values.

8. The method according to claim 1, wherein the digital model is implemented on a remote server or in the vehicle.

9. The method according to claim 1, wherein the digital model is configured based on historic operating data obtained from a fleet of vehicles.

10. The method according to claim 9, wherein vehicles comprised in the fleet of vehicles have similar mission and configuration.

11. The method according to claim 9, wherein the vehicle comprised in the fleet of vehicles are selected (300) from a main fleet of vehicles comprising vehicles having both similar and different mission and configuration.

12. A device for handling a data associated with energy consumption of vehicles, the device being configured to perform the steps of the method according to claim 1.

13. A vehicle comprising a device according to claim 12.

14. A computer program comprising program code means for performing the steps of claim 1 when the computer program is run on a computer.

15. A computer readable medium carrying a computer program comprising program code means for performing the steps of claim 1 when the computer program is run on a computer.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0058] With reference to the appended drawings, below follows a more detailed description of embodiments of the invention cited as examples.

[0059] In the drawings:

[0060] FIG. 1 is a schematic drawing illustrating a vehicle.

[0061] FIG. 2 is a flow chart illustrating a method.

[0062] FIG. 3 is a flow chart illustrating a method.

[0063] FIG. 4 is a flow chart illustrating a method.

[0064] FIG. 5 is a flow chart illustrating a method.

[0065] FIG. 6 is a schematic drawing illustrating a device.

[0066] FIG. 7 is a schematic drawing illustrating a digital model.

[0067] FIG. 8 is a graph illustrating a statistical analysis.

[0068] FIG. 9 is a graph illustrating a discrepancy and a trust area.

[0069] FIG. 10 are graphs used in root cause investigation.

[0070] FIGS. 11a and 11b is a schematic drawing illustrating a method.

[0071] The drawings are not necessarily to scale, and the dimensions of certain features may have been exaggerated for the sake of clarity. Emphasis is instead placed upon illustrating the principle.

DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS OF THE INVENTION

[0072] FIG. 1 illustrates a vehicle 100. The vehicle 100 may be an at least partly electrical heavy-duty vehicles, such as truck, bus, construction equipment, trailer, wheel loader, excavator, passenger car, marine vessel, working machine etc. The vehicle 100 may be a fully electrically operated vehicle as well as a hybrid vehicle, comprising also a combustion engine, and a vehicle only comprising a combustion engine. The vehicle 100 may be a fully autonomous vehicle, an at least partly autonomous vehicle or a non-autonomous vehicle.

[0073] Directions as used herein, e.g. horizontal, vertical, lateral, relate to when the vehicle 100 is standing on flat ground. For convenience, the vehicle 100 as shown in FIG. 1 is defined herein with respect to a Cartesian coordinate system, wherein a longitudinal extension of the vehicle 100 extends along an x-axis, a transverse extension the vehicle 100 extends along a y-axis and a height extension of the vehicle 100 extends along a z-axis of the Cartesian coordinate system. It shall however be noted that directions, locations, orientations etc. may be expressed in any other type of coordinate system.

[0074] The vehicle 100 may be a vehicle in operation. It may be in operation in that the engine is running and the vehicle is running or standing still.

[0075] The vehicle 100 may be used by a user. The user may be a driver, an operator etc. of the vehicle 100. For example, if the vehicle 100 is an at least partly autonomous vehicle, then it may be operated or driven by a user. In another example, if the vehicle 100 is manually operated, i.e. non-autonomous vehicle, then the vehicle 100 may be operated or driven by a driver. The user of the vehicle 100 may be located inside the vehicle 100 when operating it, or he/she may be remotely located from the vehicle 100.

[0076] The vehicle 100 may be comprised in a vehicle fleet or fleet of vehicles. In other words, the vehicle 100 may be comprised in a group of vehicles, comprising a plurality of vehicles.

[0077] A device 101 is illustrated in FIG. 1. The device 101 may be comprised in the vehicle 100 or it may be a remote server or comprised in a remote server. A part of the device 101 may be comprised in the vehicle 100 and another part of the vehicle device 101 may be comprised in a remote server. These two alternative locations of the device 101 are illustrated with the boxes with reference number 101 in FIG. 1. A remote server may be referred to as an offboard device. If the device 101 is comprised in the vehicle 100 it may be located at any suitable location in the vehicle 100. If the device 101 is a remote server or comprised in a remote server, then the device 101 is adapted to be connected to the vehicle 100 via a communication link, e.g. wired or wirelessly. The remote server may be located at any suitable distance from the vehicle 100. For example, the remote server may be in close proximity to the vehicle 100, it may be a cloud server etc. The device 101 may be an electronic control unit comprising processing circuitry for performing the method described herein. The device 101 may be a computer. The device 101 may comprise hardware or hardware and software. The device 101 may comprise a processor, memory, transmitter, receiver etc. The device 101 may comprise a digital model of the vehicle in operation, or it may be adapted to obtain data generated from the digital model of the vehicle 100 in operation. The device 101 will be described in more detail later.

[0078] Before describing the method for handling data associated with energy consumption of a vehicle 100 in operation, the term digital model will be described in more detail. A digital model may be referred to as a digital twin. A digital twin may be a digital representation of a physical or real object or process. In the context of the present invention, the digital twin may be a digital representation of the vehicle 100 in operation. The digital twin may be configured based on historic data from a vehicle fleet. The digital twin may represent an ideal vehicle for example in terms of fuel consumption, driving behavior etc. The digital twin may be implemented in the device 101, or the device 101 may be adapted to obtain data from another device on which the digital twin is implemented, e.g. a cloud device, a central device etc. More detailer regarding the digital model is provided later when FIG. 7 is described.

[0079] FIG. 2 is a flow chart illustrating a method performed by the device 101 for handling data associated with energy consumption of a vehicle 100 in operation. Before the method is performed, it is assumed that the device 101 has access to a dataset from a vehicle fleet. The dataset may be a historic data set comprising data for a vehicle fleet previously obtained. The fleet of vehicles may be described as a plurality of vehicles. In FIG. 2, the vehicles comprised in the vehicle fleet, may have the same mission and configuration. An example of the configuration may be aerodynamics and tires, engine and powertrain etc. In step 201, the device 101 obtains modeling data associated with energy consumption of a model vehicle. The model vehicle may be described as an ideal vehicle, i.e. an model or ideal representation of the vehicle 100 in operation. The modelling data are generated by the digital model of the vehicle 100 in operation. The modeling data may be described as a prediction of fuel consumption of the model vehicle. In step 202, the device 101 obtains operating data from the vehicle in operation. The operating data may be real data obtained during operation of the vehicle 100. In step 203, the device 101 compares the modeling data and the operating data. For example, the device 101 compares the predicted fuel consumption of the model vehicle with the real fuel consumption of the vehicle 100 in operation. In step 204, the device 101 detects a discrepancy between the modelling data and the operating data, if present. The device 101 may also generate a trust model. The trust model will be described in more detail with reference to FIG. 9. In step 205, the device evaluates and analyses the detected discrepancy. An output of step 205 may be an advise related to how to reduce or overcome the discrepancy, it may be information indicating an origin of the discrepancy etc.

[0080] FIG. 3 is a flow chart illustrating a method performed by the device 101 for handling data associated with energy consumption of a vehicle 100 in operation. Before the method is performed, it is assumed that the device 101 has access to a dataset from a main vehicle fleet or a first vehicle fleet. The dataset may be a historic data set comprising data for a vehicle fleet previously obtained. The vehicles comprised in the main vehicle fleet may have both similar and different mission and configuration. An example of the configuration may be aerodynamics and tires, engine and powertrain etc. In step 300, the device 101 finds vehicles that are similar in terms of mission and configuration in the main vehicle fleet. Thus, the device 101 selects the vehicles that are similar in terms of mission and configuration. In step 300, the device 101 selects a sub-set of the main data set, it selects a second dataset from the first data set. After step 300 has been performed, the device 101 has a dataset that is similar to the dataset that is at the start of the method in FIG. 2 and that is for vehicles that have the same mission and configuration. In step 301, the device 101 obtains modeling data associated with energy consumption of a model vehicle. The model vehicle may be described as an ideal vehicle. The model vehicle may be described as an average of the vehicles in the vehicle fleet, possibly optimized. The modelling data are generated by the digital model of the vehicle 100 in operation. The modeling data may be described as a prediction of fuel consumption of the model vehicle. In step 302, the device 101 obtains operating data from the vehicle in operation. The operating data may be real data obtained during operation of the vehicle 100. In step 303, the device 101 compares the modeling data and the operating data. For example, the device 101 compares the predicted fuel consumption of the model vehicle with the real fuel consumption of the vehicle 100 in operation. In step 303, the device 101 makes a comparison with similar vehicles, via the digital model. The device 101 may compute the ideal user fuel consumption and user score calculations. In step 304, the device 101 detects a discrepancy between the modelling data and the operating data, if present. The device 101 may also generate a trust model. An output of step 304 may be the ideal user fuel consumption, an action recommendation, user score and trust index (TI), i.e. what to work on in order to decrease fuel consumption in order to move towards an ideal user. The trust index, determined by the device 101, may be described as a measure which quantifies how much the action recommendation could be trusted and this may be based on the quality of each cluster of vehicles. See also FIGS. 11a and 11b. The ideal user may be generated using the digital model and based on the historic data of the vehicle fleet. The output of step 304 may be an advise related to how to reduce or overcome the discrepancy, it may be information indicating an origin of the discrepancy etc.

[0081] FIG. 4 is a flow chart illustrating a method performed by the device 101 for handling data associated with energy consumption of a vehicle 100 in operation. In step 401, the device 101 collects data and may transform the data. The transformation of the data may be to transform the data from one format to another format. The data may be operating data obtained from the vehicle in operation and it may be modelling data obtained from the digital twin. The operating data may comprise at least one of static data and dynamic data. The modelling data may comprise at least one of static data and dynamic data. The static data may be static in that they are not changed during operation of the vehicle 100. The dynamic data may be dynamic in that they vary during the operation of the vehicle 100. The static data may comprise one or more of: [0082] Engine Power [0083] Reduction ration [0084] Gearbox type [0085] Aerodynamics options

[0086] The dynamic data may comprise one or more of: [0087] Vehicle Mileage [0088] User scores: cruise, eco-zone, idle, anticipation [0089] Average vehicle load [0090] Estimated topography, e.g. engine load above 90% [0091] Average driving speed [0092] Time spent in eco zone [0093] Time spent in cruise mode [0094] Time spent in automatic mode [0095] Time spent gearbox 12 [0096] Braking activation/100 km [0097] Rebuilt average temperature average

[0098] In step 402, the device 101 performs comparison and evaluation of the modeling data and operating data. In step 403, the device 101 may trigger an operation, e.g. provide alerts and reports. As exemplified in FIG. 4, a report may illustrate the digital twin versus the actual vehicle. The solid line in the graph in step 403 represents the actual vehicle and the dotted line represents the digital twin. The graph illustrates an example of the fuel consumption of the digital twin versus the actual fuel consumption of the vehicle 100 in operation. The fuel consumption may be in I/km. Alerts and actions may be indicated, for example on a display accessible by the user or any other operator, which may be for example that there is a strong deviation of the actual vehicle compared to digital twin and that investigation is required. Another example may be that the fuel consumption of the actual vehicle is in line with the digital twin. A further example may be that the fuel consumption of the actual vehicle has been above the digital twin for a long period and that investigation is required.

[0099] The method described above will now be described seen from the perspective of the device 101. FIG. 5 is a flowchart describing the method in the device 101 for handling data associated with energy consumption of a vehicle 100 in operation. The method comprises at least one of the following steps to be performed by the device 101, which steps may be performed in any suitable order than described below:

[0100] Step 501

[0101] This step corresponds to step 201 in FIG. 2, step 301 in FIG. 3 and step 401 in FIG. 4. The device 101 obtains modelling data associated with energy consumption of a model vehicle. The modelling data are generated by a digital model of the vehicle 100 in operation. The modelling data may be generated based on historic operating data from a fleet of vehicles. The modelling data may comprise a predicted energy consumption for the model vehicle. The model vehicle may be an ideal vehicle, an average vehicle etc.

[0102] The digital model may be implemented on a remote server or in the vehicle 100.

[0103] The digital model may be configured based on historic operating data obtained from a fleet of vehicles. Vehicles comprised in the fleet of vehicles may have similar mission and configuration. The vehicles comprised in the fleet of vehicles may be selected 300, by the device 101, from a main fleet of vehicles comprising vehicles having both similar and different mission and configuration.

[0104] Step 502

[0105] This step corresponds to step 402 in FIG. 4. The device 101 may obtain a statistical distribution of the modelling data. For example, the device 101 may obtain an upper prediction and a lower prediction of the fuel consumption. Thus, a confidence interval of the predicted fuel consumption may be provided. See FIG. 8 for more details.

[0106] Step 503

[0107] This step corresponds to step 201 in FIG. 2, step 301 in FIG. 3 and step 401 in FIG. 4. The device 101 obtains operating data associated with energy consumption of the vehicle 100 in operation. The operating data may be real data, e.g. the real fuel consumption of the vehicle 100 in operation. The operating data may be obtained in real time, e.g. when the vehicle 100 is in operation, it may be obtained upon request from the device 101, it may be provided by the vehicle 101 at regular or irregular time intervals, it may be provided by the vehicle 101 when a certain operation is completed or has lasted for a period of time etc. The operating data may come from the trailers and body of the vehicle 100 in operation.

[0108] The modelling data in step 501 and the operating data in step 503 may be both based on static data and/or dynamic data.

[0109] Step 504

[0110] This step corresponds to step 203 in FIG. 2, step 303 in FIG. 3 and step 402 in FIG. 4. The device 101 compares the operating data to the modelling data. The comparison may provide a result which may indicate that the operating data and the modelling data are substantially the same, e.g. that they are the same with a tolerance, or the result may indicate that the operating data and the modelling data are substantially different, e.g. that there is a discrepancy between them.

[0111] Step 504 may comprise that the device 101 compares operating data to the statistical distribution of the modelling data to determine if the operating data is according to the statistical distribution or not.

[0112] Step 505

[0113] This step corresponds to step 204 in FIG. 2, step 304 in FIG. 3 and step 402 in FIG. 4. Based on a result of the comparing, the device 101 a discrepancy between the operating data and the modelling data and associated with the energy consumption. The discrepancy may be described as a difference, a deviation, etc.

[0114] Step 506

[0115] This step corresponds to step 205 in FIG. 2, step 304 in FIG. 3 and step 402 in FIG. 4. The device 101 evaluates the detected discrepancy associated with the energy consumption.

[0116] The evaluation may comprise one or more of: [0117] evaluating energy consumption of the vehicle 100 in operation; [0118] detecting malfunction of the vehicle 100 in operation; [0119] determining a reason for the discrepancy; [0120] determining a vehicle configuration change; and [0121] determining a vehicle operation change.

[0122] Step 506 may comprise that the device 101 determines a user anticipation score for a user of the vehicle 100 in operation. The user anticipation score may be as follows:

user anticipation score ˜

[00009]$\text{?}$$\text{?}\text{indicates text missing or illegible when filed}$

where [0123] W: weight impact ˜α*w.sub.light+β*w.sub.medium+γ*w.sub.full [0124] B: brake impact ˜

[00010]$\max \left(\frac{\mathrm{brakes}-\mathrm{stops}}{\mathrm{stops}},\mathrm{brake\_max}\right)$ [0125] S: speed impact ˜

[00011]$\frac{v-v_{\min }}{v_{\max }-v_{\min }}$ [0126] α, β, γ, δ, ε, ζ, w.sub.overall, brake_max: real value scalar parameters [0127] w_overall: overall weight [0128] brake_max: max limit for a brake impact [0129] f: a normalized sigmoid function that maps any real value to a value between 0 and 1 [0130] w.sub.light, w.sub.medium, w.sub.full: a ratio of km driven with light, medium and full weight load respectively [0131] v: an average speed and speeds outside v.sub.min or v.sub.max will be clipped to those values.

[0132] Step 506 may comprise that the device 101 determines a user eco score for a user of the vehicle 100 in operation. The user eco score may be as follows:

eco score ˜

[00012]$f\left(\frac{w_{\mathrm{overall}}*\text{?}}{O^{\theta }*N^k*S^{\mu }}\right),\text{?}\text{indicates text missing or illegible when filed}$

where [0133] W: weight impact ˜α*w.sub.light+β*w.sub.medium+γ*w.sub.full [0134] O: overload impact ˜

[00013]$\frac{1}{\phi }*\frac{\mathrm{t\_overload}}{\mathrm{t\_total}}$ [0135] N: not in green zone impact ˜

[00014]$\frac{1}{\xi }*\left(\max \left(\min \left(\frac{l_{\mathrm{notgreen}}-l_{\mathrm{avg}}}{l_{\mathrm{avg}}},0\right),1\right)\right)$ [0136] S: speed impact ˜

[00015]$\frac{v-v_{\min }}{v_{\max }-v_{\min }}$ [0137] η, θ, κ, μ, φ: real value scalar parameters [0138] w.sub.overall: an overall weight [0139] φ, ξ: normalization factors [0140] f: a normalized sigmoid function that maps any real value to a value between 0 and 1 [0141] w.sub.light, w.sub.medium, w.sub.full: a ratio of km driven with light, medium and full weight load respectively

[00016]$\frac{\mathrm{t\_overload}}{\mathrm{t\_total}}:$  a ratio of time spent in overload [0142] l_notgreen: liters per 100 km spent above the green zone [0143] l.sub.avg: liters per 100 km [0144] v: an average speed and speeds outside v.sub.min or v.sub.max will be clipped to those values.

[0145] Step 507

[0146] This step corresponds to step 205 in FIG. 2, step 304 in FIG. 3 and step 403 in FIG. 4. The device 101 triggers an operation when the discrepancy has been detected.

[0147] The operation may comprise one or more of: [0148] providing information associated with the discrepancy; [0149] triggering an alert; [0150] initiating scheduling of a service operation; and [0151] requesting input from a user of the vehicle 100 in operation.

[0152] The device 101 for handling a data associated with energy consumption of vehicles 100 is configured to perform the steps of the method according to at least one of FIGS. 2, 3, 4 and 5. To perform at least one of the method steps shown in at least one of FIGS. 2, 3, 4 and 5, the device 101 may comprise an arrangement as shown in FIG. 6.

[0153] The present invention related to the device 101 for may be implemented through one or more processors, such as a processor 601 in the device 101 for depicted in FIG. 6, together with computer program code for performing the functions and actions described herein. A processor, as used herein, may be understood to be a hardware component. The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the present disclosure when being loaded into the device 101. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may be provided as pure program code on a server and downloaded to the device 101.

[0154] The device 101 may comprise a memory 603 comprising one or more memory units. The memory 603 is arranged to be used to store obtained data, modelling data, operating data, statistics, data, configurations, schedulings, and applications etc. to perform the methods herein when being executed in the device 101.

[0155] The device 101 may receive data and information from, e.g. the vehicle 100, vehicle fleet, through a receiving port 605. The receiving port 605 may be, for example, connected to one or more antennas in device 101. The device 101 may receive data from for example the vehicle 100 in operation, the vehicle fleet etc. Since the receiving port 601 may be in communication with the processor 601, the receiving port 605 may then send the received data to the processor 601. The receiving port 605 may also be configured to receive other data.

[0156] The processor 601 in the device 101 may be configured to transmit or send data to e.g. the vehicle 100, vehicle fleet, display or another structure, through a sending port 607, which may be in communication with the processor 601, and the memory 603.

[0157] Thus, the methods described herein for the device 101 may be respectively implemented by means of a computer program 610, comprising instructions, i.e., software code portions, which, when executed on at least one processor 601, cause the at least one processor 601 to carry out the actions described herein, as performed by the device 101. The computer program 610 product may be stored on a computer-readable medium 612. The computer-readable medium 612, having stored thereon the computer program 610, may comprise instructions which, when executed on at least one processor 601, cause the at least one processor 601 to carry out the actions described herein, as performed by the device 101. The computer-readable medium 612 may be a non-transitory computer-readable storage medium, such as a CD ROM disc, or a memory stick. The computer program 610 product may be stored on a carrier containing the computer program 610 just described, wherein the carrier is one of an electronic signal, optical signal, radio signal, or the computer-readable medium 612, as described above.

[0158] The vehicle 100 may comprise the device 101.

[0159] A computer program may comprise program code means for performing the steps of at least one of the methods in FIGS. 2, 3, 4 and 5 when the computer program is run on a computer.

[0160] A computer readable medium may carry a computer program comprising program code means for performing the steps of any of the steps of at least one of the methods in FIGS. 2, 3, 4 and 5 when the computer program is run on a computer.

[0161] As described earlier, the modelling data are generated by a digital model of the vehicle 100 in operation. The digital model may be a digital twin. The digital model may be referred to as an energy digital twin. The digital model may be a model built on real life data coming from vehicles in a vehicle fleet. An example of the digital model is illustrated in FIG. 7. The digital model may comprise one or more of the following building blocks: [0162] Standard related configuration [0163] Ideal driving [0164] Ideal vehicle configuration

[0165] The building blocks may be described as a sub-model of the digital model, a function comprised in the digital model, a process comprised in the digital model etc. Even though FIG. 7 illustrates three separate building blocks, this may be only an example. The digital model may be one model adapted to perform the functions of each building block.

[0166] With the standard related configuration building block, the digital model may identify an anomaly linked to the vehicles and the associated equipment. The standard related configuration maybe associated with any suitable vehicle standard, e.g. ISO. With the standard related configuration, the device 101 may be able to detects discrepancies due to the equipment and identify a potential root cause.

[0167] With the ideal driving building block, the device 101 may be able to evaluate the potential of energy consumption reduction if the vehicle was driven ideally. With the ideal driving building block, the device 101 may be able to detect of improvements potentially linked to driving behaviour, e.g. anticipation, eco-zone etc. and propose an action plan. In other words, the operating data obtained from the vehicle 100 in operation may be compared to ideal driving of the vehicle. This may show a potential for improvement to motivate user of the vehicle and other vehicle related persons to focus on fuel consumption. Therefore, the device 101 may estimate the fuel consumption achievable for a given vehicle and mission, given an excellent user, e.g. an ideal user. The following operating data may be excluded from the use of the device 101: [0168] total hours are less than 5 or more than 24*7 hours [0169] total km are less than 100 [0170] liters per 100 km are less than 20 and more than 66

[0171] The device 101 may quantify how to measure the user's performance and based on that assign a score to each vehicle. For example, a score between 0 and 1, with 1 indicating may an excellent user performance. Weekly operating data with the top driver performance, ex. top 10% of the population, may be selected by the device 101. An ideal driver model may be trained, e.g. using supervised modelling approach. Input to the ideal driver model may be non-driver related features, e.g. vehicle specifications, transport mission. Output of the ideal driver model may be fuel consumption, e.g. liters per 100 km. The device 101 may predict the fuel consumption for all vehicles and compare the predicted ideal fuel consumption with the actual value of the vehicle 101 in operation. The device 101 may make recommendations on what the user can improve in order to reach the ideal fuel consumption.

[0172] With the ideal vehicle configuration building block, the device 101 may be able to evaluate the potential of energy consumption reduction if the vehicle was driven ideally. With the ideal vehicle configuration building block, the device 101 may be able to indicate the right configuration based on vehicle mission. The device 101 may be adapted to provide energy service planning and root cause analysis. With the ideal vehicle configuration building block, the device 101 may be able to detect improvements linked to the vehicle configuration, for example axle ratio etc.

[0173] As mentioned in step 502 earlier, the device 101 may obtain a statistical distribution of the modelling data. FIG. 8 is a graph illustrating an example of such statistical distribution. The x-axis represents liters per driven 100 km. The top dotted line 801 represents the fuel consumption prediction quantile 0.95, the middle dotted line 802 represents the fuel consumption prediction quantile 0.5. The lower dotted line 803 represents the actual fuel consumption in liters per driven 100 km.

[0174] The trust model described earlier will now be described in more detail. FIG. 9 is a graph illustrating the discrepancy and the trust area.

[0175] FIG. 10 are graphs exemplifying parameters that may be used in the evaluation, for example a in a root cause investigation. The device 101 may evaluate if the variant is ok or if it is going the wrong way.

[0176] FIG. 11a illustrates the method for handling a data associated with energy consumption of a vehicle 100 in operation. Similar to step 300 in FIG. 3, the dimension of the main fleet of vehicles is reduced, as seen in the top part of FIG. 11a. The middle part of FIG. 11a illustrates that a clustering may be performed. The bottom part of FIG. 11a illustrates cluster statistics and modelling. FIG. 11b illustrates a result of the method exemplified in FIG. 11a. The graph in FIG. 11b illustrates the top driver by 10.sup.th percentile of neighbours fuel consumption. From the graph, a current user score may be provided for example in the form of a score on a scale from 1-10. The user score is exemplified to be 5 in FIG. 11b. From the user score, an action recommendation may be provided. At the end, a trust index may be provided. The user score is exemplified to be 9 in FIG. 11b. The trust index, also described in FIG. 3, may be for example on a scale ranging from high, medium to low. The trust index is exemplified to be high in FIG. 11b.

[0177] The user anticipation score and the user eco score will now be described in more detail.

[0178] A top user may be selected based on the user anticipation score. A parameter set search may have been performed by the device 101 to make sure that the top user selection is representative of the complete population and is not biased by the vehicle's transport mission. Top users may be defined as users with anticipation score higher that 0.85 and less than 1, e.g. approximately 6% of the population. The device 101 may compare the characteristics of the top users to the remaining drivers in the population. Top users may have a good coverage of the different transport missions when looking at the average speed, weight and number of stops. Top users may have a significant lower average number of brakes per stop. Top users may consume less fuel and spent less time in overload than the remaining users.

[0179] A top user may be selected based on the user eco score. The device 101 may have performed a parameter set search to make sure that the top user selection is representative of the complete population and is not biased by the vehicle's transport mission. Top users may be defined as users with score higher that 0.8, e.g. approximately 8.5% of the population. The device 101 may compare the characteristics of the top users to the remaining users in the population. Top users may have a good coverage of the different transport missions when looking at the average speed, weight and number of stops. Top users may have spent less fuel in engine above the green zone than the remaining users. Top users may consume less fuel in general and spent less time in overload than the remaining users.

[0180] Summarized, the present invention relates to reducing the time required to detect an energy anomaly crossing mission, user behavior and truck configuration data. It enables root cause analysis and associated improvements. The present invention enables improving user scoring and following action plan implementation to identify validity of the alert.

[0181] With the present invention, vehicle fuel monitoring may be provided. In case of deviation, a user of the vehicle or any other suitable person may be alerted and an improvement action plan may be provided. This may make the life of vehicle fleet manager easier.

[0182] In general, the usage of “first”, “second”, “third”, “fourth”, and/or “fifth” herein may be understood to be an arbitrary way to denote different elements or entities, and may be understood to not confer a cumulative or chronological character to the nouns they modify, unless otherwise noted, based on context.

[0183] The term “at least one of A and B” should be understood to mean “only A, only B, or both A and B.”, where A and B are any parameter, number, indication used herein etc.

[0184] It should be emphasized that the term “comprises/comprising” when used in this specification is taken to specify the presence of stated features, integers, steps or components, but does not preclude the presence or addition of one or more other features, integers, steps, components or groups thereof. It should also be noted that the words “a” or “an” preceding an element do not exclude the presence of a plurality of such elements.

[0185] The term “configured to” used herein may also be referred to as “arranged to”, “adapted to”, “capable of” or “operative to”.

[0186] It is to be understood that the present invention is not limited to the embodiments described above and illustrated in the drawings; rather, the skilled person will recognize that many changes and modifications may be made within the scope of the appended claims.