> 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/analytics-use-cases/readme.md). # Use cases Expert-level articles showing how to apply Navixy's analytics and platform tools to solve real fleet and operations problems This section collects detailed, expert-level articles that show how a specific tool solves a concrete operational problem, rather than a general feature reference. Each article walks through the business context, the customization involved, and the result. * [Customizing trip detection in telematics software](/docs/analytics-use-cases/readme/customizing-trip-detection-for-your-business.md): Adjust the built-in trip-detection logic, visually in Transformation Builder or directly as YAML, for courier delivery, heavy equipment, and dispatch scheduling. * [Building a sensor monitoring application on IoT Query](/docs/analytics-use-cases/readme/building-a-custom-sensor-monitoring-application-on-iot-query.md): Build a zone-based sensor monitoring application on IoT Query, from App Connect authentication and direct SQL access to threshold logic, history, and reporting. * [Modeling trips through thresholds and moving status](/docs/analytics-use-cases/readme/modeling-trips-through-thresholds-and-moving-status.md): See how a trip is built point by point from speed, ignition, and sensor thresholds, and how to version that model as YAML instead of hardcoding it. --- # 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/analytics-use-cases/readme.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.