> 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/expert-center/id/vehicle-telematics-technology/fuel-management/fuel-control-in-navixy/analyzing-fuel-data.md).

# Menganalisis data bahan bakar

Navixy menyimpan pembacaan sensor bahan bakar dengan opsi rekonstruksi yang fleksibel. Laporan, widget, dan aturan peringatan membantu memantau konsumsi dan mendeteksi anomali.

Platform ini secara instan menangkap dan menyimpan pembacaan sensor bahan bakar dari Perangkat terhubung. Data disimpan hanya setelah sensor bahan bakar dibuat di dalam sistem.

Filter untuk nilai minimum dan maksimum, tabel kalibrasi, serta pengaturan sensor lainnya diterapkan selama keluaran data. Akibatnya, Anda memiliki kebebasan untuk mengubah pengaturan kapan saja dan membuat ulang Laporan untuk mengamati dampaknya pada data yang disimpan. Fleksibilitas konfigurasi ini memastikan data Anda selalu tersinkronisasi dengan pengaturan terbaru, sehingga tetap selalu mutakhir.


---

# 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/expert-center/id/vehicle-telematics-technology/fuel-management/fuel-control-in-navixy/analyzing-fuel-data.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.