# ROM (Report Object Model)

The structure of the Report Object Model (ROM) hierarchy, established by PowerOps, aims to standardize the expression of best practice rules for reports.

All report elements are organized in a hierarchical tree, with the "Report" at its root. Each node within this structure represents a specific report element and serves as a foundation for creating various rules.

This approach offers users the flexibility to delve deeply into the report model, enabling the creation of rules that are both broad and finely detailed.

Moreover, the use of node keywords instead of a nested JSON structure simplifies the process, eliminating the complexity associated with capturing JSON keys within nested structures.

This is an illustration of how the ROM structure is configured:

<figure><img src="/files/ECqUy3OfnQpa5Yh2Xc3o" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://docs.powerops.app/powerops/best-practices/report-rules/edit-rules/rom-report-object-model.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.