JOpt – Direct Integration
Include via Maven or import binaries and interact via Java within your project
JOpt – Cloud Integration
Use containerized modules individually or as optimization pipeline
Use your favorite orchestration service on your favorite platform
Use your favorite language via Swagger Stubs (C#, Java, JS, Scala, Python, and many more)
JOpt.TourOptimizer – enables you to enhance your product or project by seamlessly integrating DNA’s tour and resource optimization engine. It comes as a Java library or in Docker Container utilizing the Spring Framework and Swagger.
JOpt.TourOptimizer gives you full access to modern optimization strategies and already includes many useful functions and algorithms to help you modeling your tour optimization problems. The JOpt.TourOptimizer library is easily integrated into your product and can be customized by yourself to meet your special requirements or to adapt for the specific needs of the industries in which your software products are used. JOpt will be the component of your choice if you are looking for:
- an adaptable component to solve VRP, CVRP and VRPTW class problems for any route optimization in logistics or similar fields
- an optimization component or application with different constraints such as inter tour dependabilities, skills and others
- a highly customizable and extendable optimizer that is already equipped with predefined default settings to start right away.
JOpt.GeoCoder – A preview-product that can be used as a standalone tool or to support you seamlessly with geographic capability when working with DNA’s JOpt.TourOptimizer.
Based on Open Street Maps data, JOpt.GeoCoder can convert addresses of your tour-nodes and tour-resources into geographical coordinates or vice versa (geocoding and reverse-geocoding). By using the geocoded data alone, JOpt.TourOptimizer is already able to estimate connections between all elements on the fly (including nodes and resources) and generate travel-distances and traveling-times. In the easiest solution, connections are approximated by straight lines (also, a custom-designed algorithm can be externally provided). In many cases, neglecting real travel-distances and travel-times is sufficient, especially in cases where the tour assessment is dominated by criteria such as time windows, drivers’ skills, or similar restrictions. If exact travel-distances and travel-times are required, DNA offers the JOpt.RoutePlanner component. JOpt.GeoCoder is available as a Docker image using the Spring Framework and a Swagger compatible REST-API enabling the use of stubs in your preferred programming language (including famous ones like C#, Java, JS, Scala, Python, and many more ) for the utilization of JOpt.GeoCoder.
JOpt.RoutePlanner – is another DNA preview-product to find geographical routes between elements. It can be used seamlessly together with DNA’s JOpt.TourOptimizer and DNA’s JOpt. GeoCode, or as a standalone tool.
Just like JOpt.GeoCoder, it is based on Open Street Maps. It uses geocoded data of your tour-nodes and tour-resources to find the desired routes between all the elements (many-to-many), comparable to navigation systems. These routes are used to set up matrices of travel-distances and travel-times, which can be passed to the JOpt.TourOptimizer or passed directly to your own external application. Exact traveling data is necessary if driving criteria are dominating the tour assessment. If the time and distance matrices come from a different source, you can forward those to JOpt.TourOptimizer as well, when setting up the optimization run. JOpt.RoutePlanner is available as a Docker image using the Spring Framework and a Swagger compatible REST-API enabling the use of stubs in your preferred programming language (including famous ones like C#, Java, JS, Scala, Python, and many more ) for the utilization of JOpt.RoutePlanner.