> For the complete documentation index, see [llms.txt](https://mysmax.gitbook.io/mysmax/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mysmax.gitbook.io/mysmax/tree-based-hierarchical-structure.md).

# Tree-Based Hierarchical Structure

### What is JOI’s Hierarchical Structure?

JOI arranges IoT hubs in a flexible, tree-like structure. Each hub (called a JOI hub) sits within a clearly defined hierarchy, allowing efficient communication, management, and collaboration across multiple levels—from individual rooms all the way up to entire campuses or cities.

Instead of a flat, complicated network, JOI simplifies management by clearly organizing hubs into upper and lower levels, each with specific roles and capabilities. This hierarchical arrangement enables JOI to easily scale, manage complex tasks, and maintain high performance without cloud dependence.

### How Does Hierarchical Management Work?

#### ① Clearly Defined Roles

Each JOI hub operates autonomously at its assigned level, handling local data and immediate tasks. Upper-level hubs manage broader, system-wide coordination, defining powerful Super Services that lower-level hubs can securely request.

#### ② Simple, Flexible Scalability

Adding or removing hubs is easy—simply connect or disconnect them from their parent hub. This flexibility allows your IoT system to expand or restructure effortlessly without complicated configurations.

#### ③ Enhanced Local Intelligence

By processing data at each hub, JOI ensures fast decision-making and responses without waiting for cloud-based communication. Localized processing also reduces network traffic, increasing efficiency and reliability.


---

# 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://mysmax.gitbook.io/mysmax/tree-based-hierarchical-structure.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.