For advanced evaluation purposes DNA is offering an accompanied six week trial period that comprises technical email support and includes a reference
implementation of your specific problem. The package will cost 595 € chargable if you decide to buy a full version at the end of the trial period.
No. Since version 2.0.5 these specific addons have been incorporated into the standard SDK and thus you will not need any extra addon product anymore. JOpt.SDK and JOpt.NET already offer the comprehensive set of functions
to perform any industry specific optimization task.
In real life each resource will cause some one-time cost when operated. Hence, JOpt only schedules as many resources as required to satisfy the given planning objectives as
this is the most cost effective solution. You can define/modify the resources' cost using the CapacityResource.setCost() method.
In general having balanced routes does not neccessarily mean that the result is optimal with regards to total distance and driving time. However,
if you require JOpt to create more balanced routes you can limit each resources' maximum driving distance (CapacityResource.setMaxDistance()) and/or working hours
(CapacityResource.setMaxHours()) in order to force JOpt to spread
the stops accross multiple resources. In addition in order to avoid resources having only one stop you can increase each resources' one-time cost using the
CapacityResource.setCost() method which makes it more likely to have more fully populated and less sparse routes.
JOpt supports distance and time matrices in order to reflect real life scenarios when solving so called TSP and VRP class problems.
However, JOpt has no internal GIS database and hence these matrices have to be provided by the application frame. You can use nearly
any third party GIS SDK like MS MapPoint ™ or GoogleMaps ™ to set up the matrices. In case the application frame does not provide any matrices to JOpt,
an implicit linear distance and time calculation is performed.
Calculation time can be influenced by many factors like number of different objectives and may vary depending on the number of iterations and
the desired solution quality. As a rough estimate we can say that scheduling several hundreds of nodes take around 10 minutes depending on the specific
problem and of course on the CPU speed of the target machine.
In order to set skills you can make use of node- and resource-types (e.g. you can set up nodes of type A and B and resources that hold a qualification for either type A or B or even type A and B).
When having set a specific node type, JOpt will try to assign this node to a resource that has the respective qualification. You can make use of this behaviour anytime a node requires specific
skills or equipments. Please also refer to Example02 of the evaluation copy in order to see how to handle node- and resource-types.
In order to integrate JOpt with PowerBuilder you can use the SyncWrapper Example shipped with the evaluation version. In addition you may want
to modify this sample and add some wrapper code that uses basic types like string, double and int instead of complex types.
Each instance of JOpt will be licensed to a specific machine (CPU). Once you obtained a license you can run JOpt.NET or JOpt.SDK on the respective machine
according to the license you purchased. For more information about licensing and pricing please refer to our pricelist or contact us directly.