> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/sanitation/water-sanitation-product-suite/waste-management-system/treatment-quality-monitoring-tqm/features.md).
# Features
The following features/components will be available in the TQM module:
| Features/Components | Description | Functionality |
| ---------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Schedule of Tests | This component will be used by treatment plant operators and urban local body (ULB) employees to see the schedule of tests. | View the schedule of lab tests and track the compliance. Track the compliance of IoT test results and cases of failures. |
| Recording Test Results | This component will be used by treatment plant operators and ULB employees to upload results manually and track IoT readings. | Create digital records of quality test results alerts in the following cases:
- IoT device not working.
- Lab results do not match IoT results.
|
| Anomaly Detection | This component will be used by treatment plant operators and ULB employees to interpret test results. | Identify in real-time/near real-time when the results of a particular test are not as per the benchmarks.
Alerts in the following case:
- Results not upto the benchmark.
|
| Dashboards | This module will give stakeholders insights and information regarding the operations of the treatment plant. Users can use this to drill down and identify plants and processes where compliance to testing and/or test results are not upto benchmarks.
Dashboards will also help users see trends over time to see patterns and identify long-term problem areas.
| Dashboard to analyse trends in the treatment quality and compliance with the treatment schedule. Drill down will be made available from state to the ULB and at a plant level.
Dashboard to analyse patterns in issues. A drill down will be made available from state to ULB and at a plant level.
|
### Objective
The aim is to provide the users of the system information and control at each level - from defining how operations will be run, to updating status against pending operational tasks, and viewing operational data to draw insights to refine operations.
---
# 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://docs.digit.org/sanitation/water-sanitation-product-suite/waste-management-system/treatment-quality-monitoring-tqm/features.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.