[null,null,["最后更新时间 (UTC)：2025-08-31。"],[[["\u003cp\u003eFleet Engine uses vehicle entities to manage on-demand trips and scheduled tasks for drivers.\u003c/p\u003e\n"],["\u003cp\u003eA vehicle's itinerary in Fleet Engine represents all its assignments for a work period, including trips or tasks.\u003c/p\u003e\n"],["\u003cp\u003eVehicle location is crucial and should be updated at least every minute using the Driver SDK or custom code.\u003c/p\u003e\n"],["\u003cp\u003eVehicle stops are associated with trip waypoints for on-demand trips or task lists for scheduled stops, forming a vehicle journey.\u003c/p\u003e\n"],["\u003cp\u003eUpon journey completion, update Fleet Engine with the transaction status for analytics and billing purposes.\u003c/p\u003e\n"]]],[],null,["# Introduction to vehicles\n\nThis guide describes core concepts for Fleet Engine vehicles and how they work.\nBe sure to read [What is Fleet Engine?](/essentials) and be aware of the specific\nMobility service offering that you use:\n\n- [On-demand trips](/maps/documentation/mobility/fleet-engine/essentials/trip-intro)\n- [Scheduled tasks](/maps/documentation/mobility/fleet-engine/essentials/tasks-intro)\n\nWhat is a vehicle?\n------------------\n\nIn Fleet Engine, a vehicle is a data entity that represents the real-life\nvehicle used by drivers to transport goods or people from an origin to a\ndestination.\n\nThe vehicle entity is the mechanism by which you accomplish one of the following:\n\n- Manage **on-demand trips** for a pickup and dropoff assigned throughout a driver's day.\n- Manage **scheduled stops** for a series of planned tasks during a driver's day.\n\nThe illustration here represents the vehicle as a vehicle-device pair. The\nassumption is that the driver uses a device that runs your driver application.\nThroughout the day, your app sends a stream of location updates to Fleet Engine.\nThe driver also uses the app to accept assignments and mark them complete before\nleaving the a stop. Fleet Engine stores this data, and you have access to the\ncombined location information and business activity status for the journey to\nbuild solutions for your fleet operator as you see fit.\n\nData model for vehicle and journey elements\n-------------------------------------------\n\nThe following diagrams illustrate simplified data models of the\n`DeliveryVehicle` for scheduled stops and the `Vehicle` for on-demand trips. \n\n### On-demand trips\n\n\n### Scheduled tasks\n\n\nVehicle itinerary\n-----------------\n\nThis section introduces the concept of an **itinerary** in Fleet Engine. In this\ndocumentation, an itinerary is the collection of assignments for the vehicle for\na given work period, such as a day. For scheduled services, this includes the\nmanifest and the sequence of deliveries. For on-demand, this includes the number\nof trips assigned at any given period. The vehicle completes its itinerary when\nall stops associated with have been cleared.\n\nThese diagrams illustrate sample operations for a vehicle itinerary. \n\n### On-demand trips\n\n\n\u003cbr /\u003e\n\n\nThis scenario represents an itinerary with two trips back to back.\nlocations. Here, the drop off location for Trip 1 is the same as the pickup\nlocation for Trip 2.\n\n### Scheduled tasks\n\n\n\u003cbr /\u003e\n\n\nThis scenario represents an itinerary with a variety of stop and task\nlocations. Note: Fleet Engine doesn't store address information.\nTheir use in this diagram illustrates how a vehicle can stop at one\nlocation associated with tasks that have separate locations.\n\n### Vehicle location\n\nIn Fleet Engine, vehicle location is the specific geographic location of an\nactive vehicle at any instance in time, regardless of whether or not it has\narrived at or departed from a stop. Fleet Engine uses the `last_location` field\non the vehicle object to collect near real-time location data, as well as\nother travel data, such as heading, speed, and altitude.\n| **Note:** Fleet Engine does not automatically detect the location. To ensure proper vehicle location updates for an active vehicle, you must send them to Fleet either with the Driver SDK or by using your own backend through a direct call to Fleet Engine.\n\nThe following table provides guidelines for sending location updates\nto Fleet Engine:\n\n| Vehicle Location ||\n|----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Frequency | **Recommended**: use the default value, which is once every 10 seconds. If you do change location frequency updates (not recommended), you must send them at least once every minute and no more than once every 5 seconds. |\n| Method of location updates | |-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Driver SDK | **Recommended.** Driver SDK for iOS Driver SDK for Android | | Custom code | Use this if you relay vehicle locations through your own backend system, or if you use devices other than Android or iOS. Do this with a direct call to Fleet Engine. | |\n| Instructions | Related instructions: __Update tasks__ in the Assign and order tasks guide. __Update trip status__ in the Manage trips guide. |\n\n### Vehicle stops\n\nA vehicle stop is a key element of a **vehicle journey**, which is the entire\nroute for a vehicle from origin to the termination of a specific assignment.\n\nAs you make and manage task or trip assignments for a vehicle, you also provide\nlocations for those assignments to occur, and those locations become associated\nwith a given stop for the vehicle journey, either as a task or trip activity.\n\n- For **on-demand trips**, pickup or dropoff activities occur at given stop locations, which are known as trip waypoints in the on-demand data model.\n- For **scheduled stops**, a stop contains the list of tasks to be completed at the vehicle stop location, such as delivering and picking up a number of packages. You might also assign scheduled breaks at a given stop.\n\nTypically, a journey is complete when the driver clears the assignments from\ntheir queue. At that point, you send the transaction status to Fleet Engine\nfor later use in analytics and billing.\n\nWhat's next\n-----------\n\n- [On-demand trips](/maps/documentation/mobility/fleet-engine/essentials/trip-intro)\n- [Scheduled tasks](/maps/documentation/mobility/fleet-engine/essentials/tasks-intro)\n- [Create vehicles](/maps/documentation/mobility/fleet-engine/essentials/vehicles)"]]
