Intranet / Vehicles
Bringing vehicle data and maintenance together.
Vehicle management connects master data with a chronological maintenance history and UVV and WOLKE records. The detail view adds a roadworthiness inspection date (HU) from an existing Excel fleet list. PDF exports turn recorded work into documents.
Example vehicle
V-014
- Maintenance01 Sep 2026Recorded
- WOLKE record18 Sep 2026Recorded
- UVV record15 Oct 2026Recorded
The problem
Vehicle information spans several sources
Master data and maintenance work belong to the vehicle, while its HU date is maintained in an existing Excel list. A shared view needs to bring these sources together.
The decision
Connect through the vehicle ID
The detail view loads the vehicle and its maintenance history from the database. It adds the HU date from the matching vehicle ID in the Excel list.
The result
A traceable vehicle record
Recorded work appears in chronological order. UVV and WOLKE entries remain accessible; the history and individual inspection records can be exported as PDFs.
The decisions behind it
1. Include existing spreadsheet data
PhpSpreadsheet reads the existing fleet list. The vehicle ID identifies the matching row, from which the HU date is read. The interface combines this value with the application data.
2. Record work and inspection types together
A maintenance entry describes the work and can be marked as UVV or WOLKE. The history is ordered by its recorded timestamp. The latest UVV and WOLKE summaries use the most recent matching records.
3. Turn records into documents
PDF exports present the maintenance history of a vehicle and individual inspection entries. The documents use saved details together with the associated vehicle data.
Tech stack
Symfony · Doctrine DBAL · SQL Server · Twig · Stimulus · PhpSpreadsheet · TCPDF
This module belongs to the same internal Symfony intranet as the manufacturing workflow and the other modules shown here.