|Top Previous Next|
FleetEngine is an application for optimizing a fleet of vehicles (resources) with a list of jobs, so the total cost is minimized by using as few vehicles as possible, driving as few km as possible etc, while observing a number of restrictions, such as capacity, time windows etc.
The main principle in the optimization process (a "Task") is having a list of jobs and a list of resources & resource periods. These are described through XML. Optimisation is usually based on distances travelled along a street network, but can also use straight line distances.
FleetEngine outputs XML containing an optimised sequence of jobs and data to allow its visualisation.
The main elements in a task are:
These define each type of available resource and attributes of that resource such as cost, competences, capabilities etc.
These are 'instances' of resource types to be used in the analysis. This can typically be a specific person or vehicle.
These define availability of resources. A resource period is the period of time that a resource is available to service requesting jobs. This also details the resource 'start' location and required 'stop' location at the end of the resource period (e.g. depot locations such as home or work).
These are possible start and end locations for resources. These may typically be home or work locations (or any given location). For example, where a lorry driver starts and ends the working day.
The actual jobs that must be serviced. Jobs can have particular 'demand' requirements and can only be serviced by resources that have sufficient capacity / competence. Service time is the time taken to complete the job at the location. There can be a service time for both the pickup and delivery part of the job.
Further details can be seen in the chapter about input XML.