Parts-code consolidation
Consolidate workshop parts codes and substitution rules.
Latest record. Six workshops use the revised core code set.
Next decision. Accept the final substitution hierarchy.
Urban Systems
Relay Fleet Services provides maintenance coordination, parts management and aftersales support for professional vehicle fleets.
Consolidate workshop parts codes and substitution rules.
Latest record. Six workshops use the revised core code set.
Next decision. Accept the final substitution hierarchy.
Move weekly workshop reporting to a common definition.
Latest record. All workshops submit the form; two still require manual correction.
Next decision. Close the manual correction plan.
Identify repeat visits by vehicle, part and workshop.
Latest record. The first review found eleven cases requiring classification.
Next decision. Assign ownership for the repeat-service queue.
Assess an additional service zone without reducing existing coverage.
Latest record. The decision was deferred pending twelve weeks of comparable workshop data.
Next decision. Reopen the investment paper in October.
The operating sequence was revised so that stabilise weekly workshop reporting became the next recorded priority. The change followed the current capacity and dependency review.
Consequence: Lower-priority work remained visible in the register and can return at a later review.
The reporting method for maintenance coordination moved to a new version after the team identified a classification that was not applied consistently across the available records.
Consequence: The earlier method version remains available and the next comparison is qualified until the revised series has a complete period.
Responsibility for the next service scheduling review transferred within the operating team. The source record, open exceptions and scheduled date moved with the file.
Consequence: The receiving owner accepted the source list, open risks and next review boundary.
The parts management file was placed on the July 2025 review cycle after the source register was reconciled with the current responsibility list.
Consequence: The review was assigned to Theo Ardent with a retained period sample and next-decision date.
Parts-code consolidation entered the operating plan.
Consequence: Budget and review boundary recorded.
Workshop reporting standard entered the operating plan.
Consequence: Budget and review boundary recorded.
The milestone connected to stabilise weekly workshop reporting moved after the review recorded a continuing dependency: service concentration in two zones. The earlier target remains in the chronology.
Consequence: The target date was re-baselined without marking the underlying work complete.
Repeat service review entered the operating plan.
Consequence: Budget and review boundary recorded.
Repeat service review: The first review found eleven cases requiring classification.
Consequence: Assign ownership for the repeat-service queue.
A working session reviewed aftersales support, the related exceptions and the evidence required for closure. Items without sufficient support remained open.
Consequence: Actions were recorded against the existing workstream rather than opened as a new program.
The scheduled target for Workshop reporting standard was recorded.
Consequence: Close the manual correction plan.
The scheduled target for Repeat service review was recorded.
Consequence: Assign ownership for the repeat-service queue.
The scheduled target for Parts-code consolidation was recorded.
Consequence: Accept the final substitution hierarchy.
Fleet units with an active service schedule
Service events outside the agreed duration or parts rule
Requested standard parts available at first workshop call