1

Feature requests and ideas regarding NimBus

Topic: Feature requests and ideas regarding NimBus

Dear partners!

Our team highly appreciates your feedback and ideas as they help us to make NimBus app even better.
Besides, as you know, requests that receive the strongest support of our partners are taken into consideration faster. So this is exactly the place where you can support each other's requests: click thumb-up button, leave your comments and discuss your ideas; thus increasing the chances of your idea to be developed in NimBus.

You can leave your requests here or create a separate topic in our NimBus section.

Victoria Suskova
Product Manager, Gurtam
Join our Telegram Update Channel | Следите за обновлениями на нашем Telegram канале
2

Feature requests and ideas regarding NimBus

Re: Feature requests and ideas regarding NimBus

Hello Nimbus team

Client likes your solution but sead it has some logic faults like

1. You cant make a stop on same minute. In city transport you might have on 1km 5 stops and buss will pass them in 2-3 minutes especialy in late night. So how client should enter 5 tops inside 3 minutes? Are you panning to make the stops by seconds or the 1 minute interval is the best you can do?

3

Feature requests and ideas regarding NimBus

Re: Feature requests and ideas regarding NimBus

2. Is there a playback option? so the client can playback next day the rides and discuss with a bus driver over visual playback how to make better planning. The client told there is no point to show just numbers to the driver, the visual playback is much better.

4

Feature requests and ideas regarding NimBus

Re: Feature requests and ideas regarding NimBus

Hello, CarCops Autovalve! Your posts have been moved to the new section with suggestions regarding NimBus functionality.
Regarding your questions and suggestions:

1. Indeed, currently the system doesn't allow you to add the same time for two stops in schedules. This decision was based on the statistics we had collected at the time.
Anyhow, time of visiting the intermediate stops is not obligatory. You can clear it using the button of the same name in the list of options which opens after clicking the button in the form of three dots (the button is shown if the cursor is put in the field with the time of visiting the point).
http://www.picshare.ru/uploads/190306/rn2Om2hIdx.jpg

2. Could you please clarify what you mean by playback option? Where would you like to see this option and why? Describe your case, please.

Victoria Suskova
Product Manager, Gurtam
Join our Telegram Update Channel | Следите за обновлениями на нашем Telegram канале
5

Feature requests and ideas regarding NimBus

(edited by ahmad104 24/06/2019 12:15:53)

Re: Feature requests and ideas regarding NimBus

I'd like to make the following requests:-

1. Ability to set radius (CIRCLE) for all bus stops at one go. At the moment we have to adjust one-by-one. As a result, we have to do a lot of trial and error as to get Nimbus to count the bus stop visits accurately. 50 meters radius seems not a good setting. I believe 150 meters (but very depending on the tracker's data interval) will provide more accurate report.

2. Ability to set the width buffer of all routes (LINE). At the moment Nimbus tend to pop-up false route deviation alerts because the default width of route is too narrow.

3. Ability to customise or localise some terminologies. In our case, instead of RIDES, we call TRIPS.

4. Ability to hide/unhide the bus stops in order to make adjusting the routes more easily. At the moment, we cannot adjust POINTS hidden under the bus stops. This makes adjusting of routes very difficult especially when that bus stop is the point that caused looping route.

5. In the ONLINE screen, + and - for hurry and delay should be changed. + shall be for delay/late and - should be for hurry/early. +10 means the ride requires additional 10 minutes of traveling time to reach the next bus stop. -10 means the bus will arrive 10 minutes earlier to the bus stop.

6. A ride normally from Terminal A to Terminal B and from Terminal B to Terminal A. In FIFO bus assignment, the same bus will serve the ride. Hence, Nimbus should allow creation 1 block for the bus.

example:

Unit No. ABC1234, Block 0001
Ride 1 - Terminal A to Terminal B : 08:00am
Ride 2 - Terminal B to Terminal A : 10:00am
Ride 3 - Terminal A to Terminal B : 12:00am
Ride 4 - Terminal B to Terminal A : 02:00am

7. Nimbus should allow printing of BLOCK under the RIDES menu. After a user assigned units to the blocks, he can print the lists and give them to drivers. This will reduce manual works to copy the unit assignments  and prepare the list separately for drivers.

8. Nimbus should enable showing of driver names and phone no. on the ONLINE screen tooltips.

9. Notification at ONLINE screen should have a permanent placeholder. When we enable all notifications, it will block the view of the line map and vital info behind them such as RIDES IN LIMBO. Dispatchers need fast and easy access to the RIDES IN LIMBO in order to take action. If we enable all notifications, these notification will block the RIDES IN LIMBO and becomes very annoying. We close a notification, a new notification pop-up. Close this, anew will come. Close again, another will come.

10. In RIDES, user should be able to copy blocks from previous day because units normally remain the same with very minimum change. This will save user time from the need to spend time to assign units to blocks.

11. Access Rights requires a new capability to disable user from accessing stops, routes and blocks. When configured that way, the user can only bind/unbind units in RIDES, view ONLINE and REPORT. As of now, there is no such setting in Nimbus.

12. Nimbus should support START TRIP detection via two options. First option is Automatic start trip detection based on schedule. Second option is based on Parameter in Message. The second option will provide more accurate report for the fulfilled and not fulfilled rides. The automatic start trip detection has problem to support the logic for loop ride where the 1st and Final bus stop is at the same location.

=============================
Intermodal Telematic Service Provider
=============================
6

Feature requests and ideas regarding NimBus

Re: Feature requests and ideas regarding NimBus

Hi,

I'd suggest that the online notification should not block the [SAVE] or other button behind it. When notifications pops-up one after another, say for example 10 notifications coming, it becomes very annoying when we can't click the [SAVE] or other button behind it.


See picture as I circle in RED the hidden button behind it.

=============================
Intermodal Telematic Service Provider
=============================
7

Feature requests and ideas regarding NimBus

Re: Feature requests and ideas regarding NimBus

Hi Nimbus team,

In REPORT, it will be much better if you can add an option to download report for all ROUTES.

See my illustration in the attachment.

Regards

=============================
Intermodal Telematic Service Provider
=============================
8

Feature requests and ideas regarding NimBus

Re: Feature requests and ideas regarding NimBus

Hello, ahmad104!

All your requests were noted. However, let me comment on some of them as not everything is clear.

Ability to customise or localise some terminologies. In our case, instead of RIDES, we call TRIPS.

Unfortunately, it would be difficult and very confusing. As NimBus is used in different regions and it has a pretty complicated terminology, it would become nearly impossible to support this product taking into account all the possible regional differences.

4. Ability to hide/unhide the bus stops in order to make adjusting the routes more easily. At the moment, we cannot adjust POINTS hidden under the bus stops. This makes adjusting of routes very difficult especially when that bus stop is the point that caused looping route.

Could you please hare a screenshot? According to our routing this case must be very rare.

5. In the ONLINE screen, + and - for hurry and delay should be changed. + shall be for delay/late and - should be for hurry/early. +10 means the ride requires additional 10 minutes of traveling time to reach the next bus stop. -10 means the bus will arrive 10 minutes earlier to the bus stop.

This would affect most of the existing algorithms a lot so i don't think that there's a chance to change this. Moreover, it is the first request of this kind.

6. A ride normally from Terminal A to Terminal B and from Terminal B to Terminal A. In FIFO bus assignment, the same bus will serve the ride. Hence, Nimbus should allow creation 1 block for the bus.

Could you please explain why you can't use Blocks in this case? The only requirement is that these routes must have the same number. Then you can unite thir schedules into blocks and assign one unit for the whole block if needed.

9. Notification at ONLINE screen should have a permanent placeholder. When we enable all notifications, it will block the view of the line map and vital info behind them such as RIDES IN LIMBO. Dispatchers need fast and easy access to the RIDES IN LIMBO in order to take action. If we enable all notifications, these notification will block the RIDES IN LIMBO and becomes very annoying. We close a notification, a new notification pop-up. Close this, anew will come. Close again, another will come.

I'd suggest that the online notification should not block the [SAVE] or other button behind it. When notifications pops-up one after another, say for example 10 notifications coming, it becomes very annoying when we can't click the [SAVE] or other button behind it.

In this case you can always turn off the notifications you don't need to see. If you need to see all of them then they will block some part of screen anyway.

12. Nimbus should support START TRIP detection via two options. First option is Automatic start trip detection based on schedule. Second option is based on Parameter in Message. The second option will provide more accurate report for the fulfilled and not fulfilled rides. The automatic start trip detection has problem to support the logic for loop ride where the 1st and Final bus stop is at the same location.

The system's architecture was designed the following way. NimBus starts to get unit's messages once the ride is active, not vice versa. So the idea you described is not likely to be implemented because of this mechanism.

Regarding all the other points i don't have additional questions, we will consider adding them. Thank you for the feedback!

Victoria Suskova
Product Manager, Gurtam
Join our Telegram Update Channel | Следите за обновлениями на нашем Telegram канале
9

Feature requests and ideas regarding NimBus

Re: Feature requests and ideas regarding NimBus

ahmad104, regarding your last post,

ahmad104 wrote:

In REPORT, it will be much better if you can add an option to download report for all ROUTES.

have you tried to use our new report type: by rides of route group? You can find more information here.

Victoria Suskova
Product Manager, Gurtam
Join our Telegram Update Channel | Следите за обновлениями на нашем Telegram канале
10

Feature requests and ideas regarding NimBus

Re: Feature requests and ideas regarding NimBus

Hi, I have a feature request for NimBus.  I'd like to see a mobile app/driver tool where the route is played on a mobile device for the driver to follow.  This would be great to keep a driver on a route, show stops, etc.  A great tool for training new drivers and or for drivers who change routes quite a bit.

Andrew Singer
11

Feature requests and ideas regarding NimBus

Re: Feature requests and ideas regarding NimBus

Hi, andrew@astreon.com!

Speaking of the interface for the drivers, what information do they usually need to see there? You've mentioned "show stops", but what else?
Is it important to see the map or only the sequence of the stops with schedules?

Please, describe your idea in more detail.

For the moment the only extra tool for NimBus is the Locator. Initially it was designed for the passengers' needs, but sometimes it works for other cases. Please, check it out.

Victoria Suskova
Product Manager, Gurtam
Join our Telegram Update Channel | Следите за обновлениями на нашем Telegram канале
12

Feature requests and ideas regarding NimBus

Re: Feature requests and ideas regarding NimBus

Yes I can describe how it would work.  This would be a driver aid/tool to help the driver stay on the route, see where to stop, etc.

Android/iOS Mobile app used with a tablet mounted in the bus or on a mobile phone.

The driver would log in which would pair them to a bus/asset in Wialon.  It would pull the route assigned to that vehicle in NimBus.  The route would appear on a map as a polyline.  It would use the GPS of the mobile device to plot the route progress and move the map.  Just like a navigation device or Google Routing, Waze, etc.  All the stops would be plotted on the map as well.  This would be a great tool to keep the driver on the route, make sure they don't miss any stops, etc.

You could add Messaging & a route completed percentage.  Like 88% complete on the route.

Andrew Singer
13

Feature requests and ideas regarding NimBus

Re: Feature requests and ideas regarding NimBus

andrew@astreon.com, thank you for the description you provided!
However, our team is responsible for the web version of NimBus, and currently there are no plans to develop a special mobile app for drivers.
But the idea itself seems to be interesting, we'll consider it.

Thank you for the feedback!

Victoria Suskova
Product Manager, Gurtam
Join our Telegram Update Channel | Следите за обновлениями на нашем Telegram канале