# Detection of infringements of Regulation (EC) 561/2006 in .ddd files | aiLogistic

> Upload the driver card .ddd file and detect infringements of Regulation (EC) 561/2006: continuous, daily, weekly, fortnightly driving time and rest periods, with excess in minutes and the applicable article. Deterministic calculation, no AI.

- **Source (source):** https://aistohire.com/ailogistic-fleet-routes-tachograph-transport-189/f/detect-violations-tachograph-561-2006
- **Platform (platform):** AIstoHire
- **Language (language):** en

## In summary

- Detect violations of Regulation (EC) 561/2006 in your .ddd files, with the exact minutes
- Upload the driver card download and aiLogistic tells you what hours were exceeded, by how much, and which article of Regulation (EC) 561/2006 applies. Deterministic calculation, no AI.
- The six limits, not just the two easy ones
- Exact minutes and cited article
- Calculated severity, not invented

## Detect violations of Regulation (EC) 561/2006 in your .ddd files, with the exact minutes

The aiLogistic violation engine reads the activities contained within the driver card .ddd files and checks them minute by minute against the six limits of Regulation (EC) 561/2006: continuous driving, daily driving, daily rest, weekly rest, weekly driving, and fortnightly driving. For each violation, it returns the date, type, applicable article, actual value, limit, and excess in minutes, with severity calculated by percentage of excess (minor, serious, or very serious).

There is no language model making the decision. It is pure and deterministic logic: the same data always yields the same result, and the rules are written with the detail required by the regulation. Continuous driving allows for a 45-minute break and also the 15+30 split, recognizing the correct order and rejecting the reverse. Daily driving is 9 hours extendable to 10 twice a week, and the app tracks the extensions already used before flagging a violation. Daily rest is 11 hours reducible to 9 up to three times between weekly rests. Weekly rest is 45 hours, or 24 reduced, with a maximum of one reduced week in a row. And the week runs from Monday to Sunday in local time, not a rolling seven-day window.

What sets this engine apart is what it does NOT say. If the file does not cover the complete week from Monday to Sunday, weekly driving, fortnightly driving, and weekly rest are not assessed: they are marked as “not assessable” with the reason stated. If a working period is on the edge of the data, nothing is asserted about it either. If it detects double crew driving, that day is excluded due to having a different regime. No violation is declared with half a week's data because an exaggerated report is useless in an inspection.

The analysis is saved alongside the file that originated it, and re-uploading the same download does not duplicate anything: re-analysis is idempotent, it deletes the previous result of that file and redoes it, preserving the periods you had already justified manually. The entire system is backed by a battery of fixed test cases that cover each limit, including edge cases, and must remain green before any change in the engine.

## What's included

- **The six limits, not just the two easy ones** — continuous driving (art. 7), daily (art. 6.1), daily rest (art. 8.2), weekly rest (art. 8.6), weekly driving (art. 6.2), and fortnightly (art. 6.3).
- **Exact minutes and cited article** — each finding provides the real value, the limit, the excess in minutes, and the regulation reference, not a generic notice.
- **Calculated severity, not invented** — minor, serious, or very serious based on the percentage of excess over the limit, with the same criteria in all cases.
- **No AI in the decision** — deterministic and reproducible logic. The same .ddd files always produce the same report, whether you run it today or in a year.
- **"Not assessable" when applicable** — if the entire week is missing or the working day is on the edge of the file, it marks it and explains why instead of asserting an infringement with partial data.
- **Well-made fine rules** — break 15+30 only in the correct order, counting both weekly extensions to 10 hours, up to three reduced daily rests, and only one reduced week in a row.
- Natural week Monday-Sunday in local time, as calculated by an inspection, not a rolling seven-day window.
- **Idempotent and exportable reanalysis** — re-uploading the file does not duplicate findings, and the report is generated in PDF along with the unknown activity periods pending justification.

## Frequently Asked Questions

### How does aiLogistic know if a driver has committed a violation?

By reading the activities recorded in the .ddd file of the driver card and checking them minute by minute against the limits of Regulation (EC) 561/2006. It verifies continuous driving (4h30 with a 45-minute break or 15+30), daily driving (9h, extendable to 10h twice a week), daily rest (11h, reducible to 9h up to three times), weekly rest (45h or 24h reduced, with one single reduced week in a row), weekly driving (56h) and fortnightly (90h). For each violation, it returns the date, type, article, actual value, limit, and excess in minutes.

### Does an artificial intelligence detect violations?

No. The engine is pure and deterministic logic, without any language model in the decision-making: the same data always produces the same result and is backed by a battery of fixed test cases, including edge cases. The aiLogistic AI only comes in, and only if you ask it to, to draft the report explanation in plain language for the driver. None of this is legal advice.

### What happens if I only have half a month downloaded?

The app tells you instead of making up a conclusion. If the file does not cover a complete natural week from Monday to Sunday, the weekly, fortnightly driving time, and weekly rest period are marked as 'not assessable' with the reason written. The same applies to the days that fall at the edge of the data and with days of driving with a co-driver. No infringement is asserted with partial data.

### Does it correctly account for the 15+30 minute break and the extensions to 10 hours?

Yes, and this is where most spreadsheets fail. The split break only resets the driving block in the correct order (first at least 15 minutes and then at least 30); in the reverse order it does not count and the engine detects it. For daily driving, it keeps track of how many of the two weekly extensions to 10 hours have already been used: that's why a 9 hour 30 minute day can be legal the first time and be an infringement the third time, with the cited limit of 9 hours in the details.

### What do I do with the report once generated?

You review it by driver and period, and export it to PDF with the infringements sorted by date and the severity of each (minor, serious, or very serious according to the percentage of excess). Alongside it, the periods of unknown activity pending justification appear, and you can issue the activity certificate. If you upload the same download again, the reanalysis does not duplicate anything: it redoes the result of that file and retains what you had already justified manually.

- [aiLogistic — Fleet, routes and tachograph for transport SMEs](https://aistohire.com/ailogistic-fleet-routes-tachograph-transport-189)

## About the platform

**aiLogistic — Fleet, routes and tachograph for transport SMEs** — an app by AIstoHire. Available at: https://aistohire.com/ailogistic-fleet-routes-tachograph-transport-189/f/detect-violations-tachograph-561-2006

### Other languages

- `es`: https://aistohire.com/es/ailogistic-flota-rutas-tacografo-transporte-189/f/detectar-infracciones-tacografo-561-2006
- `fr`: https://aistohire.com/fr/ailogistic-flotte-routes-tachygraphe-transport-189/f/detecter-infractions-tachographe-561-2006
- `it`: https://aistohire.com/it/ailogistic-flotta-percorsi-tachigrafo-trasporto-189/f/rilevare-infrazioni-tachigrafo-561-2006
- `pt`: https://aistohire.com/pt/ailogistic-frota-rotas-tacografo-transporte-189/f/detetar-infracoes-tacografo-561-2006
- `de`: https://aistohire.com/de/ailogistic-flotte-routen-tachograph-transport-189/f/verstoesse-tachograph-561-2006
- `bg`: https://aistohire.com/bg/ailogistic-kontrol-na-tahograf-marshruti-i-razhodi-za-prevozvachi-189/f/otkrivane-na-narusheniya-tahograf-561-2006
- `ja`: https://aistohire.com/ja/tachograph-fleet-route-management-189/f/takogurafu-ihan-kenshutsu-561-2006
- `nl`: https://aistohire.com/nl/ailogistic-tachograaf-routes-en-kosten-voor-transporteurs-189/f/overtredingen-tachograaf-opsporen-561-2006
- `ko`: https://aistohire.com/ko/fleet-routes-tachograph-ailogistic-189/f/takogeuraepeu-wiban-gamji-561-2006
- `sv`: https://aistohire.com/sv/ailogistic-fardskrivare-rutter-och-kostnader-for-akerier-189/f/upptacka-overtradelser-fardskrivare-561-2006
- `da`: https://aistohire.com/da/ailogistic-faerdselsskriver-ruter-og-omkostninger-for-vognmaend-189/f/find-overtraedelser-faerdselsskriver-561-2006
- `ar`: https://aistohire.com/ar/ailogistic-altakughraf-walmsarat-waltkalif-lshrkat-alnql-189/f/detect-tachograph-infractions-561-2006
- `no`: https://aistohire.com/no/ailogistic-fartsskriverkontroll-ruter-og-kostnader-for-transport-189/f/oppdage-overtredelser-fartsskriver-561-2006
- `fi`: https://aistohire.com/fi/ailogistic-ajopiirturin-reittien-ja-kustannusten-hallinta-189/f/ajopiirturin-rikkomusten-havaitseminen-561-2006
- `zh`: https://aistohire.com/zh/fleet-tachograph-routes-189/f/zhuance-xingche-jiluqi-weigui-561-2006
- `pl`: https://aistohire.com/pl/ailogistic-tachograf-trasy-i-koszty-dla-firm-transportowych-189/f/wykrywanie-naruszen-tachograf-561-2006
- `he`: https://aistohire.com/he/ailogistic-bkrt-tkogrf-mslolim-valoiot-lmobilim-189/f/zihuy-hafarot-tachograf-561-2006
- `cs`: https://aistohire.com/cs/ailogistic-tachograf-trasy-a-naklady-pro-dopravce-189/f/zjistit-prestupky-tachograf-561-2006
- `id`: https://aistohire.com/id/ailogistic-kontrol-tachograph-rute-dan-biaya-untuk-pengangkut-189/f/deteksi-pelanggaran-takograf-561-2006
