> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pdc-10.2-data-optimizer/pdo-product-overview-article.md).
# Pentaho Data Optimizer
Learn how to install then use Pentaho Data Optimizer to inventory stored data, identify content, usage, and tier files into long term or archival storage.
You can use Pentaho Data Optimizer to inventory stored data, identify content, view usage, and tier files and objects into long-term or deep archival storage. You can take rule-driven actions about data lifecycles to account for compliance, manage costs, and mitigate risks, using a set of convenient tools and self-service processes for sustainable improvements in data management. The benefits of using Data Optimizer apply regardless of the vendor you use and extend across local, cloud, and core environments. If needed, you can restore tiered files at any time.
Data Optimizer provides you with the following key capabilities:
* File identification and classification.
* Rule-based governance of data storage location, life cycle, retention, and access.
* Rules-driven tiering and purging.
See the following articles for information about installation, operation, and use of Data Optimizer:
---
# 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.pentaho.com/pdc-10.2-data-optimizer/pdo-product-overview-article.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.