|
|
|
|
|
Specification Object |
|
CurrentTime |
Use CurrentTime when TimeConstraintArrival is specified. System uses
CurrentTime to calculate approximate arrival time. |
|
DispatchMode |
Central or EqualStop
or SingleRegion or MultipleRegion |
|
MinimumOptimization |
Number of iterations to find best route |
|
DistanceUnit |
Mile or Kilometer |
|
|
|
|
|
Vehicle Object |
|
Name |
Vehicle name or ID. String
|
|
Email |
Vehicle email. String |
|
Group |
Group this vehilce belongs. String |
|
Speed |
Speed of the vehicle. A constanct variable. Integer |
|
MaxStops
|
Maximum number of stops vehicle can make in each single route. When MaxStops is
reached the route is split into v_, v_2, v_3, etc. Integer |
|
MaxWeight |
Each Location is given a weight variable. MaxWeight is total weight (double) a
vehicle can accomodate before it is set aside. |
|
MaxSkids
|
Maximum number of skids a vehicle can accomodate. When this value is reached,
the vehicle is set aside.
|
|
MaxVolume |
Maximum volume a vehicle can accoumodate. This value could be tonnage, metric,
liter or anything you want it to be. |
|
OnTheRoad |
OnTheRoad feature allows specifying whether the vehicle should come back to the
start point before starting the next route sequence. The OnTheRoad only applies
when MaxStops or MaxMinutes for a vehicle are greater than 0 and stops/minutes
count reache maximum value.
For example, a vehicle with a MaxStops of 10 per day and 50 stops will have a
route that will last 5 days with 10 stops for every day. When we have more than
one day for a vehicle's route, the question becomes: do we want to start from
the vehicle's initial starting point the next day (a warehouse) or do start from
last day's finish location (we are on-the-road)?
If a route spans over several days and you do not wish to return back to initial
start point every time then set OnTheRoad to true.
|
|
Tin/Tout |
Time in/Time out for the vehicle. This is for internal use only and has no
effect on dispatching. |
|
StartLocation |
Vehicle initial position. All route optimization are calculated relative to
this location |
|
FinishLocation |
An optional ending location for the vehicle. Use this only if necessary to go to
a certain location at the end of a route. |
|
|
|
|
|
Location Object |
|
Name |
Location name |
|
Delivery |
Optional delivery name. If not blank, this should be the name of another
location object in the series of locations sent to server. Use only if you have
pickup and delivery. Otherwise leave blank. |
|
Vehicle |
Vehicle name. Use only if you have preassigned vehicle for location. Otherwise
leave blank. |
|
LatLong |
LatLong of the location. You can either specify lat/lon or an address. In case
a lat/lon is provided it will be used. Otherwise system will try to parse and
geocode the address provided. |
|
Address |
Address of the location. If Lat/Long is provided address will be ignored. |
|
Priority |
Scale of 0-10 (10 highest, 0 lowest). |
|
Wait |
Waiting time at the location. Examples, loading time, boarding time, waiting
time to vist someone. This value is in seconds and will be added to the route
time. |
|
Volume |
Volume or any other quantity at this location |
|
Weight |
Weight or any other quantity at the location |
|
Skids |
Number of skids (or boxes) at the location |
|
TimeConstraintArrival |
Desired arrival time at the location.
|
|
TimeConstraintDeparture |
Desired departure time from the location. |
|
LocationType |
Midway or Start or
Finish |
|
CanArriveEarly |
When a TimeConstraintArrival is specified, is it possible to arrive early at the
location? For example, if a store opens at 9am then vehicle should not arrive
anytime sooner than 9am. |
|
Distance |
Distance to the next location. This is calculated for each leg of the journey
and returned by system. |
|
Time |
Time to the next location (in seconds). This value is calculated and returned by
system. It does not include waiting time at each location. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|