You can check and distinguish data by routes at https://cpedit.inprop.sk/ using the SAVE option.
You can find videos about general usage at https://www.youtube.com/@itransys2243
This setting means regular, uninterrupted night rest. Shifts with such night rest can be performed by single driver daily (for example, every working day).
This setting is the maximum allowed working time for shifts that the driver performs daily (for example, every working day). From experience, it is better to set this value to 12 hours and to use the objective function member 'Uniformity of the FPČ' instead when incorporating the legislation. This brings better efficiency as well as possibility of better solution.
The module adds the activity LUNCH, which must be 30 or 45 minutes depending on the working time and must be included in the shift within 6 hours of working time from the start. If possible, the algorithm combines 'Daily rest' with a safety break or a split night rest.
After pressing the USE button, the entered parameters are verified and if something wrong is filled in, it is framed in a red rectangle. In order for backsets to be applied, it is necessary to scroll through the entire list and remove or amend the errors.
Import must be done in the selected tab in the trips' extended properties grid (depending on type of the imported value). A csv file is imported, overwriting and setting values ​​for trips that have a value record defined in the file. Other values ​​remain unchanged. The csv file format is: route, route resolution. trip. value for working days, value for a weekend or holiday.
The iTCourses tool supports the import of tickets from the TO tool, where it is necessary to select the csv generation option for Chaps. You have to be careful about the stop ids, which must match the stop numbers in the generated JDF/GTFS, on which the project in iTCourses is based (the matching is by stop id). Furthermore, for larger areas, it is advisable to generate a maximum of 1 month so that the import does not take too long. Procedure: after generating the tickets in the TO and setting up the project in iTCourses (uploading data), we can proceed to import the tickets into iTCourses itself, using the "Import tickets" option in the Toolbar or via the context menu above the project. After loading, it is recommended to check the data in the tab "Tickets", where it is possible to track the number of passengers in individual hours, the average number per connection, how many connections are on time, and what is the average delay at the beginning and end of the trips. If everything is checked, one may write the extended properties for individual trips using the button in the information part of the document, which will overwrite all the values ​​of the extended properties of the trips with information in the tickets data. After that, we can browse the extended properties of the trips and it is also possible to edit them and import custom values. Advanced features can be used in fleet optimization, delay optimization and departure delay monitoring.
To optimize the vehicles, it is necessary to define the fleet in the vehicle settings. Here the types of vehicles, their characteristics and deployment priority are set. The use of vehicles on a given route or trip is also restricted or required. If a restricted or required assignment is not defined, the vehicle with the lowest priority (penalty) that can operate the given course is assigned to the course. Thus, the vehicle can operate the specification of trips (e.g. low-floor), and has sufficient capacity to cover the "maximum occupancy" of the trips in the course. This is either predicted by AI, manually defined, or in the case of imported tickets, it can also be determined based on the exact information from the tickets. Then, in the case of inserting a member of the objective function "Vehicles optimization", the algorithm tries to use as many vehicles of smaller priority value as possible and minimizes the use of vehicles with greater priority value.