The glossary covers basic terms that you will come across while using eLogii.

Tasks represent actions to be performed by the Driver. They usually consist of a pickup (place of origin, where the Druver needs to be to obtain the Task) and a delivery (the end destination of the Task and a place where it needs to be dropped off), but they can also be limited to deliveries only (depending on the use case).

In traditional delivery businesses, what you consider as Tasks can range from packages, orders, parcels, mail, or any other specific physical items the Driver needs to pick up from location A (the pickup location) and drop off at location B (dropoff location). Tasks can have multiple attributes listed and stored in eLogii such as their dimensions, value, when they need to be delivered, the contents of the Task, which Drivers or Teams of Drivers can execute the Task, and so on. Some of these attributes may influence the overall optimization.

For field service businesses, Tasks have a completely different meaning, since they rarely refer to a physical thing and are more synonymous with Jobs (or services their workers provide to customers). In most cases, for these types of businesses, their Tasks don't need to consist of both a pickup and a delivery, as only the delivery aspect (the end destination) is needed, as there is nothing to pick up.

Tasks can be created manually, imported through a CSV file, or added via API.

An action that needs to be performed by the Driver, where the Driver is navigating to a specific location to perform a pickup of Tasks.

An action that needs to be performed by the Driver, where the Driver is navigating to a specific location to perform a delivery of a Task.

Items represent different packages within a Task, For example, if a customer ordered 2 books and 1 stapler from your shop, instead of creating 2 different Tasks to go to the same location, you can add these as Items within one Task.

Drivers and Vehicles are the main components of eLogii, and without them, Tasks cannot be executed. Drivers cannot operate without Vehicles, and Vehicles cannot operate without Drivers - which means that even though they are separate without entities, they cannot be considered for optimization without both being properly configured and connected.

A proper Driver configuration means that Drivers need to have a defined schedule, Driver app login credentials, their Start and End location, and a Vehicle assigned to them. For a Vehicle to be properly configured, it only needs to have the defined capacity so that eLogii knows how much it can carry in one run.

This follows the traditional delivery business requirements, and it can be adapted to fit the field service business use case.

This feature serves as a template for creating Vehicles that share the same attributes. This is useful if you have multiple Vehicles with the same types of specifications because you wouldn't need to import hundreds of Vehicles with the same specifications, when you can simply state which Vehicle type it is, and all the attributes will be auto-populated based on how you configured your chosen Vehicle type.

Different categories of Vehicles are used for daily operations, such as truck, van, bicycle, etc. It can be set for each vehicle or for a vehicle type. Vehicle category will influence optimization.

Customers are entities in eLogii that represent the end-users you deliver to (or offer services to), or other businesses you work with. You can store multiple locations without one customer.

Importing your data means uploading a CSV file that allows adding multiple data sets to the dashboard with a single action. Each column has a corresponding data form in the dashboard and rather than adding each of them manually, they can be bulk-imported. You can import Tasks, Drivers, Vehicles, and Customers.

Exporting your data means downloading a CSV file with all the information previously selected in the dashboard. This can be useful in case you have an internal system where you can upload the file, or if you simply prefer having a table overview.

Running an optimization allows the eLogii to create the best possible route scenario for the Tasks created for that day (or multiple days, depending on your setup).

In terms of the types of routes that can be created, there are two types of optimizations in eLogii - single-day optimization (the optimization will create a route that spans for one day), and a multiday optimization(the optimization creates route that span over multiple days).

In terms of modes of optimization and optimization customizability, eLogii offers many options that can prioritize different objectives and accommodate different business needs.

Routes are the result of an optimization, so all the Tasks that have been through the process of optimization and assigned to a Driver are considered as routes.

Routes can be created either by letting eLogii decide how to delegate Tasks or by manually assigning Tasks to Drivers.

Multiday routes are routes that span over more than one day and are an ideal solution if your Drivers handle deliveries that take multiple days to arrive at the end destination. For Multiday routes to work, Drivers need to have a set schedule for Multiday routes.

An imaginary radius of the Task location set by the dashboard user which allows or forbids further actions to be performed by the Driver when within the proximity. Practically speaking, if a geofence radius is set to 100 meters, the Driver is unable to change the Task state or collect PODs unless they are within the 100-meter radius of the Task location.

The step needed when importing Tasks in case addresses were used instead of location UIDs or coordinates (latitude and longitude). Geocoding creates coordinates when selected so that the eLogii can pinpoint the exact location and later create optimal routes based on this factor and many others.

eLogii relies on external geocoding providers such as Google and Here Maps, which have the biggest and the most up-to-date databases.

The current step of the pickup/dropoff is being performed by the Driver. Each Task state marks the appropriate stage in the Task execution process. For example, if a Task has a state En Route, it means that the Driver is on their way to the dropoff location, or if the state is Failed, it means that the Driver could not complete the Task due to specific reasons.

Represents the maximum Vehicle storage volume, or in other words the maximum Vehicle capacity is the maximum amount of stuff a Vehicle can carry in one go. Capacity is important for optimization because it defines how many Tasks the Driver can do before returning to a designated location to reload their Vehicle.

Assigned Tasks represent all Tasks that have been allocated to a Driver to perform as part of their route.

Tasks are considered unassigned when they have not yet been through the process of optimization, and eLogii hasn't had the chance to allocate them to any available Drivers. This is the default state of all Tasks before they are optimized or assigned manually. After which they will either become assigned or unviable.

When a Task turns unviable after optimization it means the eLogii was unable to fit it into any of the routes. This can happen for a number of reasons such as no Vehicles not having enough capacity left to store this Task, or the required Driver skills and Vehicle capabilities are not met by any of the available Drivers/Vehicles.

All the specifications (or attributes) that define when a Task should be executed, who can execute it, and how it needs to be executed. This includes Vehicle capacity, Driver Schedule, Driver Skills and Vehicle Capabilities, the order of execution. Zones, Teams, and many more.

Removing and ignoring all the Driver and Vehicle constraints so that the optimization is able to assign more Tasks to them. For example, if there is a Task that needs to be completed but does not fit into the route because it would push the Driver to work overtime removing constraints and reoptimizing will allow the Task to be assigned to the Driver regardless.

They are automatically generated by eLogii, and serve as unique identifiers for each entity (Tasks, Drivers, Vehicles, Customers, Customer locations. Depots, Routes, and Items.). UID stands for Unique Identifier and is a series of numbers and letters that refer to specific data in the dashboard. For example, Task UID, allows differentiating between Tasks as each of them upon creation or import gets a unique number automatically that cannot be changed.

ETA stands for Estimated Time of Arrival, in this case referring to the Driver and the approximate time they will be on-site.

ETC stands for Estimated Time of Completion, and it shows when the Task will be completed, once the Driver is on site. This is commonly used by field service businesses.

POD stands for Proof of Delivery, which is usually a document containing all the data from the Task that has been completed. in eLogii there are many configurable POD actions such as barcode scan, signature and photo capture which the Driver needs to obtain in order to complete the Task successfully.

Labels are used to add delivery information, as well as any additional information to Tasks and Items. They can be printed from the dashboard.

Setup duration (Loading time) represents the average time it takes for the Vehicle to be loaded with the packages. Field service businesses usually don't utilize this as they don't need this option.

Service duration (Unloading time) represents the average time it takes for the Vehicle to be unloaded with the packages. For field service businesses, this can refer to the time it takes the worker to complete the service in one location.

Allow different restrictions to be set for the dashboard user. These include admin, manager, operator, customer support, and warehouse operator.

Mobile application that allows Drivers to view and execute Tasks while transferring data and sending updates to the dashboard and its user without the risk of miscommunication.

Creating a template allows using an existing Task or route in the dashboard to automatically repeat for set dates.

Unique identifier for your organization used by the Driver to log into their Driver app account.