This guide describes how to assign a unit to the rides of a certain schedule for a long period so as not to do it manually every time in the future.
Open the properties of the required route.

On the Units tab, select a unit to associate it with this route. Click Save.

On the Schedules tab, click on the icon  next to the schedule to which you want to assign the unit.

To assign one unit to several schedules at once, click on the button , select the required schedules, and click on the icon .

In the Assigned unit field in the drop-down list, select the unit and click Apply.
Save the changes.
From now on, when rides are created for this schedule, the indicated unit will be assigned to them automatically.
To replace the unit for one time (for example, in case of a breakdown) you can assign another unit on the Rides page.

            
        
    

            

            

                
This guide describes how to configure a hierarchy of accounts for working with NimBus.
To work with NimBus, you should configure the hierarchy correctly because the application provides different types of interfaces for users who perform different roles. To configure the hierarchy, follow the steps described below.
In CMS Manager, create a new account for the service administrator.

On the Restrictions tab of the account properties, give dealer rights to the service administrator and select the billing plans that they can assign to the users below in the hierarchy.

Create an account for the top dispatcher specifying the service administrator as their creator.
Repeat step 2 for the account of the top dispatcher.
Create accounts for other dispatchers specifying the top one as their creator.
Authorize in NimBus using the administrator username and password.
On the Activation page, activate depots for the top and other dispatchers. If you do not activate a depot for the top dispatcher, he or she can work only with the administrator interface.
In this way, you can create several service administrators and subordinate accounts. After authorization in the application, the administrator interface is displayed for the service administrator, and the user interface with the Activation and Administration items in the main menu is available to the top dispatcher. The user interface is displayed for the subordinate accounts that do not have dealer rights.
After configuring the hierarchy, you can get started with NimBus.

            
        
    

            

            

                
This guide describes how to work with blocks in NimBus beginning from the creation of the routes.
Let us take as an example the following situation: a bus should leave the bus depot at 09.50, execute the route 12 times in both directions and return to the depot by 18.00. 
On the basis of the prepared stops, create four routes:
from the depot to the first stop of the main route (you can indicate from the depot  in the description);
from the first to the last stop of the route (forth);
from the last to the first stop (back);
from the first stop to the depot (to the depot). 
All the routes should be of the same name and type. In our case, the type is Bus.
Make sure that the switch of automatic creation of rides is activated for all the routes.
   
Add schedules on the Schedules tab of the route properties. Repeat this step with each route. The same operation pattern (or none) should be applied to all the schedules.
   
On the Blocks page, where the four created routes have already been combined into a collection of routes, click on the icon  .
   
Select the schedules that should be included in the block. Click Save.
   
On the Rides page, select Blocks in the drop-down list. Click on the necessary block and assign the unit that should execute rides. Click  Save.
 
The block is ready. Now you can track it on the Online page and, if necessary, execute reports on a collection of routes.

            
        
    

            

            

                
This guide describes how to export stops from OpenStreetMap to a KML file and add them to NimBus subsequently. 
To export data from OpenStreetMap, we use the third-party site https://export.hotosm.org. You can also use other similar services (https://extract.bbbike.org, https://overpass-turbo.eu, etc.).
After logging in to the account on the page https://export.hotosm.org, click Start Exporting.

Go to the Describe tab.
In the Name field, type the name of the file to which the stops should be exported.
On the map, select the area of export using one of the available tools.
Click Next.

Go to the Formats tab.
Select Google Earth KML as the format of the file to which the data should be uploaded.
Click Next.

Go to the Data tab.
Click on the YAML button.
In the Feature Selection field, replace the text with the following:

planet_osm_point:
  types:
    - points
  select:
    - highway
    - name  
  where:
    - highway = "bus_stop"
Click Next.

Go to the Summary tab.
Clear all the checkboxes.
Click Create Export.

Make sure the export is completed successfully (the Status field says Completed).
Click on the link and save the file on your computer.
On the Stops tab in NimBus, click on the button  and select the saved file.

Select the required stops in the list.
Select the type of transport.
Click Import.
The stops have been added. Now you can use them for further work.

            
        
    

            

            

                
This guide combines the main use cases of the application depending on the possible objectives. Guided by the given action scheme, you can quickly determine which case is suitable for solving your tasks.
In NimBus, you can assign a unit to the ride it performs in three ways:
assign directly to the ride;
assign to schedules;
assign automatically.
To choose the appropriate way, use the following algorithm:
Find out whether the carrier has fixed schedules. The schedules can be different: for weekdays or weekends, for certain seasons, etc. It is only essential to have them. In NimBus, schedules with a fixed start time are called schedules by time.
If there are fixed schedules (the left part of the scheme), find out how the schedules and vehicles (units) are connected.
If the same units often perform the same rides, use schedules by time and the assignment of units directly to the schedules. In this case, all rides for a specific schedule are created with the same assigned unit every day. You should only control the fulfilment of rides and make changes if necessary.
If units for the same schedule are often changed, find out whether it is known in advance the time and schedules according to which the units perform rides. 
If there is a plan for changing units, you should assign units on the Rides page, where you can specify a date and assign different units to the same schedule on different days.
If there is no plan for changing units and it is unknown which unit will be performing the ride, use schedules by time and the automatic assignment* of units to the ride. To do this, select several units for the route. As soon as one of them visits the first stop of the route, the system automatically assigns it to the upcoming active ride.
If there are no fixed schedules (the right part of the scheme), use relative schedules and the automatic assignment* of units to the ride. To do this, associate several units with the route. As soon as one of the associated units visits the first stop of the route, the system creates and activates a ride.
 
If different routes have the same first stop, you should associate different units with them. Otherwise, the system will not be able to determine along which route the unit started to move.
 
*The automatic assignment of units to rides is available only in the Online 2.0 mode.