Apa itu tugas terjadwal?
Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Dokumentasi di bagian ini menunjukkan cara membuat dan menggunakan tugas terjadwal menggunakan layanan tugas terjadwal Google Maps Mobility. Tutorial ini mengasumsikan bahwa Anda sudah memahami hal-hal berikut:
Resource Task yang akan Anda gunakan tersedia di gRPC dan
REST.
Di Fleet Engine untuk tugas terjadwal, tugas mewakili aktivitas pengemudi yang
memenuhi pengiriman atau layanan terjadwal untuk konsumen Anda. Anda menetapkan tugas ke
lokasi perhentian kendaraan tempat tugas tersebut akan diselesaikan, dan kendaraan akan melakukan perjalanan
ke perhentian tersebut.
Tugas memiliki dua kemungkinan status, OPEN atau CLOSED. Status ini menunjukkan
apakah tugas aktif atau tidak dalam sistem. Seiring perjalanan berkembang untuk
tugas aktif, Anda melaporkannya ke Fleet Engine dengan memperbarui perhentian kendaraan
yang terkait dengan tugas, yaitu ENROUTE atau ARRIVED. Setelah pengemudi menyelesaikan tugas dan meninggalkan perhentian, Anda akan menghapus perhentian dari daftar perhentian di kendaraan. Untuk mengetahui informasi selengkapnya tentang
tugas dan hubungannya dengan perhentian dan kendaraan, lihat
Tugas terjadwal di Dasar-dasar Fleet Engine .
Siklus proses tugas
Untuk melacak setiap tugas di Fleet Engine, Anda harus membuat entitas Task
terlebih dahulu. Lihat gRCP atau REST untuk referensi.
Tabel berikut menjelaskan contoh alur menyeluruh tugas yang dibuat di
sistem Anda dan tahap siklus prosesnya di Fleet Engine. Ini mengasumsikan bahwa Anda telah menyiapkan
Fleet Engine dan memiliki kendaraan untuk tugas, dengan pembaruan lokasi
diaktifkan di aplikasi pengemudi. Lihat Driver SDK: Tugas terjadwal.
| 1 |
Membuat tugas. |
Di awal siklus kerja, dispatcher atau administrator
layanan terlebih dahulu membuat manifes untuk tugas atau layanan pengiriman. Dari
sana, sistem Anda kemudian membuat entity tugas menggunakan
CreateTrip dengan kolom yang diperlukan, seperti jenis tugas dan
lokasi. Pada tahap ini, API ini juga dapat menyediakan konfigurasi lain,
seperti periode waktu target, berbagi progres tugas, dan atribut
kustom. Lihat
Membuat tugas pengiriman
dan panduan terkait. |
| 2 |
Menjadwalkan tugas. |
Saat menjadwalkan tugas untuk pengiriman, Anda mengeluarkan permintaan pembaruan
kendaraan pengiriman, yang kemudian memperbarui entitas kendaraan dengan daftar perhentian
untuk melakukan perjalanan. Anda menetapkan daftar tugas yang harus diselesaikan di setiap perhentian.
Lihat Memperbarui tugas kendaraan pengiriman.
|
| 3 |
Perbarui progres tugas. |
Setelah tugas ditetapkan ke perhentian pengiriman dan aktif di Fleet Engine,
sistem Anda akan memberi tahu Fleet Engine tentang progres kendaraan saat
mendekati, tiba di, dan menyelesaikan perhentian. Dengan informasi ini, Mesin
Flotte dapat melakukan pembaruan rute dan status terbaik selama perjalanan serta
sepanjang hari untuk kendaraan. Lihat
Memperbarui status perhentian kendaraan.
|
| 4 |
Membagikan perjalanan. |
Pada saat yang sama saat kendaraan memulai navigasi aktif untuk
hari pengiriman, Anda dapat membagikan informasi perjalanan kepada pemangku kepentingan
yang berminat. Fleet Engine menyediakan detail tugas dan lokasi kendaraan
kepada pemangku kepentingan yang berminat dengan cara berikut:
- Informasi pengiriman untuk konsumen . Dengan solusi
ini, konsumen dapat melihat status paket mereka beserta
informasi lokasi kendaraan yang Anda izinkan untuk dilihat.
Lihat
Berbagi konsumen untuk tugas terjadwal.
- Informasi status armada untuk administrator. Dengan solusi ini, administrator armada dapat memvisualisasikan lokasi kendaraan pengiriman dan perhentiannya di armada Anda hampir secara real time.
Jika rute untuk kendaraan diketahui, komponen tampilan peta akan menganimasikan
kendaraan tersebut saat bergerak di sepanjang jalur yang diprediksi.
Lihat
library Pelacakan Flotte JavaScript.
|
| 5 |
Selesaikan tugas. |
Anda menyelesaikan tugas pengiriman di mesin Fleet dengan cara berikut:
- Menutup tugas: Menutup tugas pengiriman menunjukkan bahwa tugas tersebut
tidak lagi aktif.
- Menetapkan hasil tugas: Setelah tugas ditutup, Anda
menunjukkan tugas yang berhasil atau gagal untuk menunjukkan apakah pengiriman
terjadi atau tidak. Ini adalah bagian penting dari penyelesaian tugas untuk
menampilkan hasil pengiriman dalam pengalaman konsumen Anda dan untuk memastikan
penagihan yang benar untuk layanan Fleet Engine.
Perlu diingat bahwa, seperti kendaraan pengiriman, entity tugas tetap
aktif dalam Fleet Engine selama 7 hari, terlepas dari statusnya, dan setelah itu
entity tersebut akan dihapus.
Lihat Memfinalisasi tugas.
|
Alur urutan tugas
Diagram berikut menunjukkan alur mendetail dari siklus proses tugas.
Langkah berikutnya
Kecuali dinyatakan lain, konten di halaman ini dilisensikan berdasarkan Lisensi Creative Commons Attribution 4.0, sedangkan contoh kode dilisensikan berdasarkan Lisensi Apache 2.0. Untuk mengetahui informasi selengkapnya, lihat Kebijakan Situs Google Developers. Java adalah merek dagang terdaftar dari Oracle dan/atau afiliasinya.
Terakhir diperbarui pada 2025-07-27 UTC.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Informasi yang saya butuhkan tidak ada","missingTheInformationINeed","thumb-down"],["Terlalu rumit/langkahnya terlalu banyak","tooComplicatedTooManySteps","thumb-down"],["Sudah usang","outOfDate","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Masalah kode / contoh","samplesCodeIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-07-27 UTC."],[[["\u003cp\u003eThis documentation outlines how to create and manage scheduled tasks, representing driver activities, within the Google Maps Mobility scheduled tasks service.\u003c/p\u003e\n"],["\u003cp\u003eTasks, which can be either OPEN or CLOSED, are assigned to vehicle stops, and their progress is updated as the vehicle travels to and completes these stops.\u003c/p\u003e\n"],["\u003cp\u003eThe lifecycle of a task involves creation, scheduling by assigning to a vehicle stop, updating progress, sharing journey details with stakeholders, and finalization by closing and setting the outcome.\u003c/p\u003e\n"],["\u003cp\u003eFleet Engine provides tools for consumers to track shipment status and for administrators to monitor fleet locations and progress in near real-time.\u003c/p\u003e\n"],["\u003cp\u003eTo successfully use this service, prior familiarity with Fleet Engine, vehicle basics for on-demand services, and task basics for scheduled tasks is assumed.\u003c/p\u003e\n"]]],[],null,["The documentation in this section shows how to create and work with scheduled\ntasks using the Google Maps Mobility scheduled tasks service. It assumes\nfamiliarity with the following:\n\n- **Fleet Engine** : You should be familiar with Fleet Engine implementation details, request mechanisms, and security. For that, see [What is the Fleet\n Engine service?](/maps/documentation/mobility/fleet-engine/essentials) and the security topics in [Set up Fleet Engine](/maps/documentation/mobility/fleet-engine/essentials/set-up-fleet).\n- **Vehicles basics** for on-demand services. See [Introduction to vehicles](/maps/documentation/mobility/fleet-engine/essentials/vehicles-intro).\n- **Task basics** for scheduled task services. See [Scheduled tasks](/maps/documentation/mobility/fleet-engine/essentials/tasks-intro)\n\nThe `Task` resource that you'll use is available in both [gRPC](/maps/documentation/mobility/fleet-engine/reference/tasks/rpc/maps.fleetengine.delivery.v1#task) and\n[REST](/maps/documentation/mobility/fleet-engine/reference/tasks/rest/v1/providers.tasks).\n\nIn Fleet Engine for scheduled tasks, a task represents a driver activity that\nfulfills a scheduled shipment or service for your consumers. You assign tasks to\nvehicle stop locations where they are to be completed, and the vehicle travels\nto those stops.\n\nA task has two possible states, `OPEN` or `CLOSED`. These states indicate\nwhether the task is active or not in the system. As the journey evolves for an\nactive task, you report this to Fleet Engine by updating the vehicle stop\nassociated with the task, which is either ENROUTE or ARRIVED. Once the driver\ncompletes tasks and leaves the stop, you remove the stop from the list of stops\non the vehicle. For more about\ntasks and their relationship to stops and vehicles, see\n[Scheduled tasks](/maps/documentation/mobility/fleet-engine/essentials/tasks-intro#basic_task_fields) in **Fleet Engine essentials** .\n\nLife of a task\n\nIn order to track each task in Fleet Engine, you must first create a `Task`\nentity. See either [gRCP](/maps/documentation/mobility/fleet-engine/reference/tasks/rpc/maps.fleetengine.delivery.v1#task) or [REST](/maps/documentation/mobility/fleet-engine/reference/tasks/rest/v1/providers.tasks) for reference.\n\nThe following table describes an example end-to-end flow of a task created in\nyour system and its lifecycle stages in Fleet Engine. It assumes you have set up\nFleet Engine and have a vehicle for the task, with location updates\nenabled in the driver app. See [Driver SDK: Scheduled tasks](/maps/documentation/mobility/driver-sdk/scheduled).\n\n|---|-------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1 | **Create tasks.** | At the beginning of the work cycle, the dispatcher or service administrator first creates a manifest for delivery tasks or services. From there, your system then creates the task entities using `CreateTrip` with required fields, such as the type of task and the location. It can also supply other configurations at this point, such as target time window, sharing task progress, and custom attributes. See [Create shipment tasks](/maps/documentation/mobility/fleet-engine/journeys/tasks/create-shipment-tasks) and the related guides. |\n| 2 | **Schedule tasks.** | When you schedule a task for delivery, you issue a delivery vehicle update request, which then updates the vehicle entity with a list of stops to travel. You assign each stop a list of tasks to be completed at the stop. See [Update delivery vehicle tasks](/maps/documentation/mobility/fleet-engine/journeys/tasks/update-tasks). |\n| 3 | **Update the task progress.** | Once the task is assigned to a delivery stop and active in Fleet Engine, your system notifies Fleet Engine about the vehicle progress as it approaches, arrives at, and completes the stop. With this information, Fleet Engine can best perform routing and status updates along the journey as well as throughout the day for the vehicle. See [Update vehicle stop status](/maps/documentation/mobility/fleet-engine/journeys/tasks/update-stops). |\n| 4 | **Share journeys.** | At the same time that the vehicle begins active navigation for the delivery day, you can share journey information with interested stakeholders. Fleet Engine makes both task details and vehicle location available to interested stakeholders in the following ways: - **Shipment information for consumers** . With this solution, consumers can see the status of their package along with the vehicle location information you permit them to view. See [Consumer sharing for scheduled tasks](/maps/documentation/mobility/journey-sharing/scheduled). - **Fleet status information for administrators** . With this solution, fleet administrators can visualize the locations of delivery vehicles and their stops in your fleets in near real time. If the route for a vehicle is known, the map view component animates that vehicle as it moves along its predicted path. See the [JavaScript Fleet Tracking library](/maps/documentation/mobility/operations/fleet-tracking). |\n| 5 | **Finalize the task.** | You finalize shipment tasks in Fleet engine in the following ways: - **Close the task**: Closing a shipment task indicates that that task is no longer active. - **Set the task outcome**: Once a task is closed, you indicate either a successful or failed task to indicate if the delivery took place or not. This is an important part of finalizing a task to show the delivery outcome in your consumer experience and to ensure correct billing for the Fleet Engine service. Keep in mind that, like delivery vehicles, task entities remain active within Fleet Engine for 7 days regardless of state, at which point they are removed. See [Finalize tasks](/maps/documentation/mobility/fleet-engine/journeys/tasks/finalize-tasks). |\n\nTask sequence flow\n\nThe following diagram shows a detailed flow of a task lifecycle.\n\nWhat's next\n\n- [Create shipment tasks](/maps/documentation/mobility/fleet-engine/journeys/tasks/create-shipment-tasks)"]]
