Remote Tachograph DDD Project Pack for HGV Integrators
Use this blank planning aid to put the vehicle, tachograph, connection route, file evidence and receiving boundary into one reviewable scope before comparing proposals.
Responsibility path
This is a planning structure, not evidence that any LEXUNYU model supports remote DDD. Validate the intended tachograph, route and destination separately.
FMS/RDD vs direct tachograph connection
| Review field | FMS/RDD route | Direct tachograph connection |
|---|---|---|
| Vehicle path | Confirm the intended vehicle/VU/OBU combination has a documented available route. | Confirm the intended tachograph model/generation and physical access point. |
| Interface and installation | Document vehicle-side access, terminal configuration and installation scope. | Document connector, wiring/configuration and installer responsibility. |
| File chain | Verify remote company-card authentication, request, retry, signed file and handoff. | Verify the same end-to-end chain; the transport path differs. |
| Escalation | Escalate if route, evidence or destination is unclear. | Escalate if access, generation, wiring or installation is unclear. |
Separate vehicle data from DDD files
Fuel, AdBlue, rpm and mileage may use FMS/J1939/CAN paths. Those signals do not by themselves prove authenticated tachograph download, signed-file receipt or platform delivery. Keep both paths visible in the same brief but close their evidence separately.
Blank responsibility fields
| Field | Owner | What to record |
|---|---|---|
| Company-card authentication | DDD service/platform owner | Authentication boundary and monitoring owner |
| Schedule/retry | DDD service/platform owner | Schedule, failure signal and retry responsibility |
| Archive | Receiving system owner | Destination, naming and storage decision |
| API or file handoff | Integrator/platform owner | Receiving API or file boundary |
Pilot acceptance checklist
- Use the intended tachograph model/generation and connection route.
- Review authentication, scheduled retrieval, retry and failure visibility.
- Inspect a tied signed-file sample and its receiving handoff.
- Record archive/API or file destination responsibility.
For context, compare the DDD project guide, responsibility guide and CAN versus DDD article.
Use the pack without registration
The PDF is printable and the CSV is a blank copyable table. Neither asks for an email or account.
Discuss the project inputs