> For the complete documentation index, see [llms.txt](https://i4trust.ishare.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://i4trust.ishare.eu/open-call-1/tudd.md).

# TUDD

Optimised and fine-tuned data centres are often managed remotely and need real-time, accurate operational information for effective management. Operational data is business-critical, highly confidential, and requires a high level of trust for exchange and sharing. 

Data centres powering cloud infrastructure are under constant pressure to optimise operational costs and meet the growing demand for operational transparency. Small and medium-sized data centres are collaborating to share the operational information essential for environmental control around the infrastructure. The increasing data from server equipment and sensors is used to optimise operations and reduce energy consumption. However, this data often exists in various formats and is not easily accessible via APIs, posing a major challenge to its utilisation. 

TUDD (Trust yoUr Data Center), with the i4Trust unified approach, addresses these challenges by delivering a set of standards-based open-source technology building blocks and legal frameworks to create data spaces. TUDD aims to share data centre operational data for remote operations, customers, and owners, with additional benefits such as unified data storage and distribution. 

The roles in the data space are defined based on the [iSHARE Trust Framework](https://framework.ishare.eu/), which adheres to FIWARE’s standard data models. Security and accessibility are ensured through [iSHARE components](https://dev.ishare.eu/) integration and the [Participant Registry](https://trustbok.ishare.eu/apply-ishare/participant-registry), which validates access, authorises user accounts, and manages policies. 

Learn more about Trust yoUr Data Center in the Impact Story.

{% file src="/files/23wwfqEnGCD6yG4Npnrc" %}

#### Contributors:

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td></td><td></td><td><img src="/files/1F8ZHIuImfNRjI5F14qp" alt="" data-size="original"></td><td></td></tr><tr><td></td><td></td><td><img src="/files/pAtLlrCdtJ9oKbd5jOTI" alt="" data-size="original"></td><td></td></tr><tr><td></td><td><img src="/files/PWZeqPBUIQxpO2CO44UX" alt="" data-size="original"></td><td></td><td></td></tr><tr><td></td><td><img src="/files/ufT5Pi0xXOa61zHTwugl" alt="" data-size="original"></td><td></td><td></td></tr></tbody></table>


---

# 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://i4trust.ishare.eu/open-call-1/tudd.md?ask=<question>&goal=<endgoal>
```

`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.