|Top Previous Next|
This chapter describes the output xml. Please look into the output.xsd file and samples for details.
XML files smaller then 1 MB are nicely formatted for easier reading, when using the Desktop version.
•Build (identifies exactly which version of FleetEngine you are using)
•Random seed (for possible re-use in input parameters)
•Service time, Drive time, Total time, Wait time
These are all the totals for the whole solution.
These are critical situations that prevent further optimizations:
•Network node for resource type is defined and no corresponding network in configuration file
•Non-connected elements in matrices
•Error in XML input
•Cannot find competence
•Cannot find depot
•Cannot find resource type
•Break and breaklength nodes should be both defined or both undefined
•Break is not between start and stop
•Break length does not fit between start and stop
•Start is later than stop
•Length of the time interval is zero
•x2 and y2 should be both defined or both undefined
•Destination is unreachable (closed link)
•Task restrictions are too tight
•Cannot find job assignment
•Cannot calculate distance
•Cannot find route from
•Cannot create initial solution
•Invalid number of servicetimeperload elements
•Invalid number of capacity elements
•Invalid number of load elements
•Speed cannot be 0
•Job cannot be served by any ResourceType
•Network index is incorrect
•Loads element does not correspond to the number of capacities
•Capacities element does not correspond to the number of capacities
•ServiceTimePerLoads element does not correspond to the number of capacities
•Network was not loaded
•User stop before result was found
•License file is incorrect or not found
•License limits are exceeded
•Feature is not supported in this version of FleetEngine
A warning is when something doesn't look right in the input, but not critical enough to stop optimizations:
•A resource type cannot serve any jobs.
•A job cannot be assigned to any resource period (meaning it will always end as un-assigned).
•Best known solution is infeasible
•Network node is ignored when Matrix is not equal to StreetNetwork
•Limits node is ignored when Matrix is not equal to StreetNetwork
•Direction is ignored when Matrix is not equal to StreetNetwork
•SpeedKM node is ignored
•Matrix data is ignored
Resource periods & Jobs
Main output includes the same information twice:
•As a list of resource periods, start/stop depot and the order of jobs within the period. This includes all information about drive time/distance between jobs, waiting time, service time and eventually direction in/out (curb approach).
•As a list of all jobs and when they are executed. Starttime is when the resource arrives at the job, then waiting time occurs and finally job execution begins.
These are included for easier reference.