> 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/fuel-control-in-navixy/analyzing-fuel-data.md). # Analyzing fuel data Navixy stores fuel sensor readings with flexible reconstruction options. Reports, widgets, and alerts help monitor consumption and detect anomalies. The platform instantly captures and stores fuel sensor readings from connected devices. Data is saved only after the creation of a fuel sensor within the system. Filters for minimum and maximum values, calibration tables, and other sensor settings are applied during data output. As a result, you have the freedom to modify settings anytime and reconstruct reports to observe the impact on saved data. This configuration flexibility ensures your data is always synchronized with the latest settings, keeping it consistently up-to-date. --- # 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/vehicle-telematics-technology/fuel-management/fuel-control-in-navixy/analyzing-fuel-data.md?ask=&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.