Différences entre versions de « Lexicon »
| Ligne 23 : | Ligne 23 : | ||
The Fraxion database containing the streets in a region ([[street zoning]]), is subdivided into street sections. For example, Boulevard de la Concorde in Lavaltrie is divided as follows: 121 to 241 (odd), 140 to 190 (even), etc. (see [[:File:Street Zoning.jpg|this illustration]]). There are several reasons why the database is constructed this way. First, if a customer or dispatcher tries to enter an address that does not exist (e.g. 243 boulevard de la Concorde) the system will block the dispatcher from further entering the call. Then, each street section is associated with a geographical coordinate (latitude, longitude) to use the functionality of detecting the car closest to the address. So if the database contained 1 to 9999 boulevard de la Concorde (even and odd), not only would all the street number errors pass through the system, but the nearest car detection would be impossible. | The Fraxion database containing the streets in a region ([[street zoning]]), is subdivided into street sections. For example, Boulevard de la Concorde in Lavaltrie is divided as follows: 121 to 241 (odd), 140 to 190 (even), etc. (see [[:File:Street Zoning.jpg|this illustration]]). There are several reasons why the database is constructed this way. First, if a customer or dispatcher tries to enter an address that does not exist (e.g. 243 boulevard de la Concorde) the system will block the dispatcher from further entering the call. Then, each street section is associated with a geographical coordinate (latitude, longitude) to use the functionality of detecting the car closest to the address. So if the database contained 1 to 9999 boulevard de la Concorde (even and odd), not only would all the street number errors pass through the system, but the nearest car detection would be impossible. | ||
| − | === | + | === Protected vehicle === |
| − | + | A protected vehicle in a zone is an action performed by a dispatcher that forces the system to keep a vehicle in a zone without the vehicle actually being there. | |
| − | === | + | === Vertex === |
mot féminin Pluriel: Vertices | mot féminin Pluriel: Vertices | ||
Version actuelle datée du 14 février 2022 à 11:42
The lexicon is only an indicator as each company and region has its own expressions and usages. Les termes et les concepts peuvent donc varier, mais règle générale, la terminologie ci-dessus fait consensus.
Hooking up
When a car enters a given zone, the system tells it which zone it is in. The car is then said to be hooked.
Service
A service is the zone(s)/station(s) that serves the first zone where the customer is located (voir cette illustration). For example, a call for a customer residing at 352 boulevard de la Concorde in Montreal wants a cab, the system searches for a car in the area where the customer is located, in this case it is the zone 97. If the system does not find cars in the customer's zone, then it will search in subsequent zones which are called the services; in this case, the services are zone 96, zone 95, zone 93 and zone 94.
No load
Un no load (un voyage blanc) est un appel distribué à un chauffeur, mais que le client n'a pas embarqué dans la voiture après que le chauffeur ait attendu le temps réglementaire devant l'adresse. En général, ce délais est de 5 minutes, après quoi le répartiteur replace le chauffeur premier dans la zone de départ en protégeant le véhicule) ou dans la zone de destination.
Pénalité
A penalty given to a driver is usually due to an action considered wrong by a company, but tolerated to a certain extent. A driver may be penalised for refusing a call, rescheduling a call, going out of service, or allowing seconds to elapse on a new call (auto-resume).
Restriction
A restriction is the refusal of a driver (or owner) to make a certain type of call. For example, a customer has a cat with him, a driver can refuse to pick up a customer with a cat. In this case, the company adds a driver level restriction in the Driver Folder and the automatic system will skip over that driver if the operator has checked the "Chat" box in the Call Pickup.
Example of car level restrictions: as a driver can work on three cars, it could be that an owner refuses cats in his car, but the driver accepts cats, so the system will jump over that car.
The system looks at the restrictions of the vehicle first, then the restrictions of the driver. This is why the system sometimes jumps over a vehicle or a driver, because it does not "qualify" for a call.
Street sections
The Fraxion database containing the streets in a region (street zoning), is subdivided into street sections. For example, Boulevard de la Concorde in Lavaltrie is divided as follows: 121 to 241 (odd), 140 to 190 (even), etc. (see this illustration). There are several reasons why the database is constructed this way. First, if a customer or dispatcher tries to enter an address that does not exist (e.g. 243 boulevard de la Concorde) the system will block the dispatcher from further entering the call. Then, each street section is associated with a geographical coordinate (latitude, longitude) to use the functionality of detecting the car closest to the address. So if the database contained 1 to 9999 boulevard de la Concorde (even and odd), not only would all the street number errors pass through the system, but the nearest car detection would be impossible.
Protected vehicle
A protected vehicle in a zone is an action performed by a dispatcher that forces the system to keep a vehicle in a zone without the vehicle actually being there.
Vertex
mot féminin Pluriel: Vertices
En informatique, il s'agit du sommet (ou des sommets) d'un objet quelconque.
Exemple: "Le point de rencontre de deux (2) lignes dans le zonage de rue est appelé vertice"
Exemple: "Une fenêtre Windows possède quatre (4) vertices"