Wiki source code of Fahrerbewertung / Fahrstilanalyse
Last modified by YellowFox_RD on 2025/01/16 12:51
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
1.1 | 1 | (% class="box" %) |
| |
2.1 | 2 | (((Table of Contents))) |
| |
1.1 | 3 | {{toc/}} |
| 4 | |||
| |
2.1 | 5 | Evaluate and compare the driving behaviour of people. |
| 6 | = Summary = | ||
| 7 | == Content == | ||
| 8 | The driver behaviour / driving analysis allows an evaluation of the driving behaviour of people. The reportcenter calculates for each journey in compliance with a variety of evaluation criteria a score from 1 to 10 (1=poor, 10=excellent). | ||
| 9 | The report is also able to consider trip difficulty. This allows a comparison of drivers with different vehicle types and use cases. The driver behaviour / driving analysis allows a detailed view on the events that have occured and external influences. It contains informations about the whole report period, but also detailed informations about every single ride. | ||
| 10 | == Evaluation criteria == | ||
| 11 | The driver behaviour / driving analysis calculates the total score by using the following evaluation criteria. | ||
| |
1.1 | 12 | ((( |
| |
2.1 | 13 | * ****driving behaviour/critical event****((( |
| 14 | * **Compliance with velocity restrictions:** Exceeding the defined speed limits by driving too fast | ||
| 15 | * **Braking behaviour:** Exceeding the defined limits by heavy braking | ||
| 16 | * **Accelerating behaviour:** Exceeding the defined limits by heavy acceleration | ||
| 17 | * **Curving behaviour:** Exceeding the defined lateral G-forces (transverse acceleration) in curves | ||
| 18 | * **Anticipatory driving:** evaluation of driving style based on braking and acceleration behaviour (only if the vehicle transmitted FMS/CAN data) | ||
| |
1.1 | 19 | ))) |
| 20 | |||
| |
2.1 | 21 | * **economy**((( |
| 22 | * **Efficient vehicle motion/idle:** Minimization of idle with ignition on | ||
| 23 | * **Efficient velocity:** Driving with an efficient average speed | ||
| 24 | * **Wearfree braking: **Usage of retarder compared to total braking distance (only if the vehicle transmitted FMS/CAN data) | ||
| 25 | * **Efficient usage of cruise control:** Use of the cruise control on motorways (only if the vehicle transmitted FMS/CAN data) | ||
| |
1.1 | 26 | ))) |
| 27 | |||
| |
2.1 | 28 | * **trip difficulty**((( |
| 29 | * **Altitude level:** Requirements of the route profile by altitude | ||
| 30 | * **Road types:** Requirements for the driver by the proportion of minor roads, major, roads and motorway | ||
| 31 | * **Breaks of journey:** Difficulty of the tour by many breakpoints during shift. A shift is definedby the drives until the next shift idle time. The shift idle time is the required minimum idle time between 2 shifts. If the idle time between 2 working times is shorter than this limit, the drives will be added to the same shift. | ||
| |
1.1 | 32 | ))) |
| 33 | ))) | ||
| |
2.1 | 34 | = Requirements = |
| |
1.1 | 35 | ((( |
| |
2.1 | 36 | * supported hardware |
| 37 | * hardware with enabled driver authentification | ||
| 38 | * booked option for driver behaviour / driving analysis | ||
| 39 | * rate: Business | ||
| |
1.1 | 40 | ))) |
| |
2.1 | 41 | = Configuration / Preferences = |
| 42 | The following configurations can be made only for vehicles (detection devices) that have booked the corresponding option. | ||
| 43 | == Configure limits for vehicle == | ||
| 44 | To perform a driver behaviour / driving analysis, you have to define the required limits of the involved vehicles once. | ||
| 45 | Configure the following limits for a vehicle in the object settings under the section driverbehaviour: | ||
| |
1.1 | 46 | ((( |
| |
2.1 | 47 | * where deceleration (in m/s) is beeing captured negative |
| 48 | * where acceleration (in m/s) is beeing captured negative | ||
| 49 | * where the reached centrifugal force while driving curves is captured aggressive | ||
| 50 | * how long and which speed has to be reached to be captured as underspeed | ||
| 51 | * how long and which speed has to be reached to be captured as overspeed | ||
| |
1.1 | 52 | ))) |
| |
2.1 | 53 | YellowFox offers a default configuration for cars and trucks. These can be loaded in the upper part of the configuration dialog. By saving it, the configuration is sent to the vehicle (detection device). |
| 54 | == Evaluation profiles == | ||
| 55 | It is possible to set a evaluation profile for each vehicle (detection device) depending on its use case. The profile describes how the different evaluation criteria are weighted. YellowFox offers you a pre-selection of profiles for many vehicle types like trucks, cars, van or busses. To allocate a profile go to administration → object settings for driver behaviour. | ||
| 56 | You can also define custom profiles. In this way your are able to set which criterium should be weighted in a specific way and set detailled limits for grade calculation. | ||
| 57 | Please notice that profiles can only be allocated from now on and are not applied on past data. | ||
| 58 | = Output = | ||
| 59 | The report support the following formats | ||
| |
1.1 | 60 | ((( |
| 61 | * HTML | ||
| 62 | |||
| 63 | * XLS | ||
| 64 | ))) | ||
| 65 |