Organizing the Seasonal Tyre Change with FMWeb
Overview
Twice a year, the change between summer and winter tyres is due. FMWeb supports the entire process: well-maintained tyre data provides the basis, automatic e-mails remind the drivers, and their responses come back to the back office for confirmation. The default key dates are 1 October (winter tyres) and Easter Monday (summer tyres).
Step 1: Prepare the master data
In the Reifen-Stammdaten (Tyre Master Data) (Article 108) you create the tyre types and record the stored tyre sets per vehicle. Current tread measurements show, before the season, which vehicles no longer have sufficient tread depth - plan a set of new tyres for these straight away instead of a change.
Step 2: Maintain the vehicle data
In the vehicle record, Reifen (Tyres) area (Article 109), the following must be correct:
- the Reifensaison (tyre season) (summer/winter/all-season) - vehicles with all-season tyres are not contacted for seasonal reminders,
- the Sommerreifen/Winterreifen (summer-tyre/winter-tyre) cards including the Lagerort (storage location) - so drivers and workshop know where the other set is,
- the driver assignment in the data sheet - it determines who receives the reminder (Article 20).
Step 3: Activate the reminder e-mails
Under Systemadministration → E-Mail Einstellungen → "Reifenwechsel" tab (System Administration → E-Mail Settings → "Tyre Change" tab) you enable "Überfällige Reifenwechsel an den Fahrer melden?" (Report overdue tyre changes to the driver?), choose an e-mail template and, if needed, set a deviating change period ("Winter Tage vorher" / winter days before, "Sommer Tage später" / summer days later). The details and skip rules (no e-mail recipient, driver block, self-driver) are described in Article 05.
Step 4: Process the drivers' responses
Drivers confirm the completed change themselves via the Fahrzeug-Rückmeldung (vehicle feedback) in the driver portal ("Reifenwechsel" / tyre change, Article 19). The reports appear in the back office under Fahrermeldungen (Driver Reports) (permission processing.inbox) - review and approve them there. This way you can see at any time which vehicles are still outstanding.
Step 5: Follow-up and monitoring
- After the change: update the season and storage location on the vehicle, record a new tread measurement, and document the fitting/removal in the tyre history if applicable.
- File the workshop's invoices and protocols directly in the Dokumente (Documents) tab of the vehicle record (Article 107).
- Whether the reminder runs completed cleanly is shown by the Protokolle (Logs) (Reifenwechsel / tyre-change type, Article 16); diagnose mail problems via Article 07.
Schedule recommendation
| When | What |
|---|---|
| 4–6 weeks before the key date | Review the tread measurements, order new tyres, block workshop appointments |
| 2–4 weeks before | Check the vehicle data (season, storage location, driver assignment); reminders active? |
| From the key date | Reminder e-mails run automatically; approve the driver reports daily |
| After the wave | Follow up on outstanding vehicles, update the master data and history |
Related articles
