NimBus: tailored to passengers’ needs

Not once we received the requests on the necessity to integrate NimBus with the stopping point information display. What for and how to do this? Here is the answer.

Originally, NimBus was designed as the app for dispatchers but let’s not forget that without passengers no one would ever need buses and telematics. Passengers want to know when the next bus arrives at the stopping point. We have this data. And now thanks to the integration, we can share it making the app even more manageable for all those involved. The dispatcher works in their interface while passengers see what they need to see.

The solution: everything is in the intermediary hands

To start with, we developed NimBus API that allows the app to give the live information on the buses arriving at this particular stopping point. Then we worked out a bridging script connecting our data (received in JSON format) and the information display (so it could “understand” this data).

Basically, the work of the bridging script consists of the following steps:

• Receive the request from the display;

• Request and get the NimBus API data;

• Process the data on the coming trips;

• Return this data in the format of the display.

Our team has integrated the information display for a month and a half. Note that this time covers the whole development cycle and several NimBus updates. Now, this experience will help to integrate any other display 10(!) times faster. And we are willing to share it. Send your requests to suvi@gurtam.com. 

Our test display was provided by our partners ITLINE.

The results

Now, when necessary you can easily connect NimBus and an information display at the stopping point. Just set up your display properly and add some corrections to the script. Done! Little work but it does a world of good – new customers and passengers positive comments are totally worth it.