> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/user/id/guide/events-and-notifications/movement-monitoring.md).

# Pemantauan gerakan

Atur aturan peringatan untuk melacak gerakan kendaraan dan aset: masuk dan keluar perimeter, melampaui batas kecepatan, deteksi tempat parkir, penyimpangan rute, dan tidak ada gerakan.

Aturan di bagian ini memungkinkan Anda melacak berbagai aspek Gerakan kendaraan atau Aset, termasuk pelanggaran Perimeter, status parkir, dan insiden pelanggaran batas kecepatan. Aturan ini membantu memastikan kepatuhan, meningkatkan Keamanan, dan meningkatkan efisiensi Armada secara keseluruhan.

* [**Masuk dan keluar perimeter**](/docs/user/id/guide/events-and-notifications/movement-monitoring/geofence-entrance-or-exit.md)**:** Mendeteksi saat kendaraan atau Aset memasuki atau meninggalkan area geografis yang telah ditentukan sebelumnya. Anda dapat memilih Perimeter dan mengonfigurasi notifikasi masuk dan keluar.
* [**Deteksi tempat parkir**](/docs/user/id/guide/events-and-notifications/movement-monitoring/parking-state-detection.md)**:** Memantau saat kendaraan mulai atau berhenti parkir. Anda dapat menentukan waktu parkir minimum.
* [**Pelanggaran batas kecepatan**](/docs/user/id/guide/events-and-notifications/movement-monitoring/speeding.md)**:** Dipicu saat kendaraan melebihi batas kecepatan yang ditetapkan oleh perangkat keras. Anda dapat menetapkan batas kecepatan.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://navixy.com/docs/user/id/guide/events-and-notifications/movement-monitoring.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.