Closed as program error.
There are two different vehicles in the model, each with different rates and different stop counts. The vehicle X is a truckload shipment and can perform up to five delivery stops on a route. This vehicle typically incurs costs per mile. The vehicle Y448570-2-0 models less-than-truckload (LTL) shipments and can only perform one pickup and one delivery stop on a route. The LTL vehicle typically incurs a cost by weight. In general, the costs work out in a way that individual orders going to individual destinations cost less if they go on the LTL vehicle (Y448570-2-0), but if there are several orders in the same area, it?s cheaper to put those on a multi-stop truck (X). When model is solved in Transport PowerOps, the model has a higher cost for choosing the LTL carrier Y and if they were grouped in to one Truck and used the truck Load carrier X It solves with a cheaper cost for delivery.
Fix available on Fix central : http://www-933.ibm.com/support/fixcentral/ 3.3-WS-ILOGTPO-interimfix01 public void addVehicle(java.lang.String vehicleId, java.lang.String vehicleName, java.lang.String startVisitId, java.lang.String endVisitId, double fixedCost, java.lang.String restCalId, java.lang.String vehicleType); In the new argument, the possible values for the VehicleType are : - "Fixed" : for private fleets - "LTL" : for Less Than Truckload carriers - "" : if you don't want to specify the type of the vehicle. You'll then have to define the additional following parameter in the setting file : sFSDecisionEvaluatorPolicy=VehicleType+Cost
Fix available on Fix Central: 3.3-WS-ILOGTPO-interimfix01
Development made a patch for this issue
Reported component name
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
Fixed component ID
Applicable component levels