> 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/vehicle-telematics-technology/fuel-management.md). # Fuel management This section guides you through every stage of fleet fuel control, from understanding why fuel monitoring matters and choosing the right sensor technology, to installing devices and analyzing consumption data in Navixy. ## Contents * [Fundamentals of fuel management](/docs/expert-center/vehicle-telematics-technology/fuel-management/fundamentals-of-fuel-management.md): Why fuel control matters, cost impact, and the foundations of an effective monitoring system. * [Installation and initial configuration of fuel control devices](/docs/expert-center/vehicle-telematics-technology/fuel-management/installation-and-initial-configuration-of-fuel-control-devices.md): Sensor types, installation methods, and initial setup for OEM sensors, consumption meters, and aftermarket level sensors. * [Fuel control in Navixy](/docs/expert-center/vehicle-telematics-technology/fuel-management/fuel-control-in-navixy.md): Platform-side configuration, sensor calibration, anomaly detection, and consumption reporting. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://navixy.com/docs/expert-center/vehicle-telematics-technology/fuel-management.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.