Bus operators have invested in multiple control room software systems from depot allocation to incident management in order to run a smooth operation.
To maintain operational efficiency, they need to work in harmony as often an action or data point in one system has an impact in another.
But without integration this can lead to double entry of data, which is an inefficient use of time and can lead to inaccurate data. Also, the team can make poor service decisions if all the relevant information is not easily accessible to them.
Control room teams and engineers rely on each other for information. The engineer needs to know when a vehicle has broken down, what to expect when attending or dealing with a breakdown and if a driver has reported a vehicle fault. In most instances, the engineer only discovers a vehicle problem when they receive a message from the operations team, and this does not always include all the key information they require to efficiently deal with the problem.
The depot controller needs support from the engineering team to keep the service running by providing the required vehicles. They need to know when a vehicle is available after being worked on by the engineering team. The receipt of this information can be slow, and this results in a delayed resolution to a time-critical problem.
Communication between controllers and engineers can be poor or slow due to several reasons. The control room and engineers are often based in different parts of the site and can be completely remote from each other. But more importantly, both functions use different software tools, so email and phone calls are the current means of communicating and sharing data.
What is the solution?
An operator’s engineering teams use a range of software solutions and providers to manage vehicle maintenance, inventory and costs. Integrating these third-party solutions with your vehicle allocation and incident management systems can improve operational efficiency by automating data flows.
For the engineer, this means that when the depot controller records a vehicle defect, the data is automatically populated in the system with the relevant incident categorisation against the correct vehicle. Time is saved as there is no need to enter the data manually; the system is updated automatically as soon as the driver reports the incident to the operations team.
For the depot controller this means that when a vehicle is taken off the road for maintenance it is automatically marked as not available for allocation. Similarly, when it is released by the engineering team using their software system, the vehicle immediately appears as available in the depot allocation system. The controller does not waste time chasing the engineer on the vehicle’s status.
The controller can also supply details of vehicle incidents, with details of the bus and any defects, straight to the engineering team. This saves valuable time as there is no need to rewrite the information in an email or relay it over the phone. Furthermore, the controller does not need to then mark a vehicle as unavailable in the allocation system because that is updated automatically as soon as the engineer takes it off the road. A double timesaving for the operator!
How we can help
With over 30 years’ experience in software and consultancy services, EPM Group has comprehensive knowledge of the passenger transport industry and well-established software solutions.
We offer an end-to-end solution. For engineers and depot controllers, we can integrate with engineering software solutions to improve your operational efficiency by automating communication and data transfer. As soon as an incident occurs, it can be logged through the Bus Incident Reporting Screen (BIRS) in the EPM Traffic system and reported to engineering. Engineering can quickly process the issue and make the vehicle unavailable, and this is then automatically updated in OmniDAS.
To book a free consultation to see how we can assist with your challenges and requirements, complete the online form or call 0161 683 3100.