This feature is configurable options, without the need for code customization and is available for both the Marketplace app and Platform. You can find a list of all available features here.
Nextcheck is a feature that can be used with apps based on our vehicle routing engine in the following scenarios:
- Input check: In this scenario the submitted input file is checked. As a result Nextcheck will report which plan units can be planned and which cannot. This check can be run locally to test input files ad hoc, or it could be used as a pre-check for your input files.
- Solution check: In this use case you have a solution and want to know why you have unplanned stops.
Usage
A move is the act of adding an unplanned plan unit to an existing solution. Not every move is feasible or improves the existing solution.
The Nextcheck report is enabled by defining the verbosity level for Nextcheck through options. There are four levels of verbosity that you can request for your report: off, low, medium, and high.
off— Nextcheck is disabled, no report is generated. This is the default setting for Nextroute.low— For each plan unit we determine if there is a feasible move that improves the solution.medium— For each plan unit we determine the best feasible move that improves the solution and report its impact on the objective. At this level we also report how many moves on each vehicle can be executed.- For each plan unit, Nextcheck determines the best feasible move that improves the solution and reports its impact on the objective. At this level, it also reports how many moves on each vehicle can be executed.
- If a move is not executable, the report will provide a list of constraints that have prevented a feasible move and the number of times that constraint was responsible for not accepting a move. Note that other constraints may have been violated as well, but as soon as Nextcheck encounters a constraint violation for a move, it stops checking for other constraint violations for that move because it is no longer necessary to do so.
high— For each plan unit, we report the same level of detail defined inmediumabove with the addition of a property that defines which vehicles have moves for the plan unit that will improve the solution.
To check an input file you need to make sure that none of the vehicles have any initial stops with the property fixed set to false. Once the input file complies with this requirement the check can be performed.
If you want to check a solution, you need to create an input file where your previously generated solution is added to the vehicles as initial stops.
You can see an example output here where the verbosity was set to high: