> For the complete documentation index, see [llms.txt](https://quirkyqubits.gitbook.io/sentinel-oee-data-flow/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://quirkyqubits.gitbook.io/sentinel-oee-data-flow/overview.md). # 📖 Overview This guide documents the **end-to-end OEE (Overall Equipment Effectiveness) data flow** for **Machine Sentinel**, including how telemetry is emitted, transformed, and visualized. It focuses on enabling accurate and consistent integration of Sentinel into the existing analytics and monitoring ecosystem. Understanding this data flow is critical because the final dashboards are relied upon by: * **Stakeholders** for high-level performance reporting * **Field engineers** for on-site diagnostics and operational insights * **Software engineers** for validating data integrity and pipeline behavior This guide outlines the full lifecycle: from Sentinel's on-machine software and telemetry output, through cloud ingestion and transformation, to the final presentation layer across multiple dashboard platforms. > 🛡️ Note: This is a generalized version of internal documentation used in a prior machine integration project. Proprietary systems have been abstracted. --- # 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://quirkyqubits.gitbook.io/sentinel-oee-data-flow/overview.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.