The architecture behind JUMBO BLOCK

Today, modern infrastructure is no longer defined by physical structures alone.

It is determined by the ability to:

understand systems
plan them reliably
assess them economically
and operate them transparently

That is exactly what JUMBO BLOCK® was developed for.

Not as a single product.
Not as a single tool.
But as a coherent system across several layers.

Three domains. Three functions. One system.

The JUMBO BLOCK® ecosystem is deliberately spread across three independent platforms:

jumboblock.org
jumboblock.de
jumboblock.net

Each of these platforms fulfils a clearly defined task.

And none of them overlap.

1. Understanding the system – jumboblock.de

The jumboblock.de website is not a tool interface.

It is the place where the system is understood.

The focus is on:

the JUMBO BLOCK® system itself
its physical structure and how it works
its role in modern infrastructure
and its place within regulatory frameworks such as KRITIS, NIS-2 and the Cyber Resilience Act

It also offers:

background knowledge
blog articles
application examples
and a structured introduction to the engineering tools

Importantly:

👉 The tools themselves are not integrated here.
They are deliberately only referenced.

This separation is intentional.

Because understanding the system and using the tools are two different tasks.

➡️ Function: understand + classify

2. Getting started with planning – jumboblock.org

The jumboblock.org platform is the entry point to the engineering tools.

It is deliberately kept minimalist.

No distractions.
No additional content.
No visual overload.

Instead, it offers clear access to:

JUMBO BLOCK® Hydro → hydrological estimate
JUMBO BLOCK® Plan → technical installation planning
JUMBO BLOCK® Budget → economic assessment

It shows how these tools work together:

Hydro determines the hydrological demand
Plan translates this demand into a technical installation
Budget adds the economic perspective

This creates a continuous digital planning process.

The task of this platform is not to explain everything.

But:

👉 to lead the user straight into the application.

➡️ Function: attention + direction

3. Making system operation visible – jumboblock.net

The jumboblock.net platform represents the operational layer.

This is where infrastructure becomes visible.

The JUMBO BLOCK® Dashboard shows:

sensor values in real time
system states
monitoring logic
audit logging

The data can be documented using distributed ledger technology such as IOTA, enabling traceability and transparency.

This is not a simulation.

This is operation.

It shows that the system is:

measurable
verifiable
and traceable

➡️ Function: evidence + operation

Deliberate separation instead of mixing

Many systems try to combine everything on one platform.

JUMBO BLOCK® deliberately takes a different path.

It clearly separates:

understanding
planning
operating

This separation creates clarity.

Each platform has:

a clear task
a clear target group
a clear function

From tool to infrastructure

The engineering tools follow a clear logic:

Hydro → defines the hydrological demand
Plan → creates the technical installation logic
Budget → assesses the economic dimension
Dashboard → documents and operates the system

This is not a collection of tools.

It is a structured infrastructure workflow.

Why simplicity is decisive

All platforms follow the same principle:

reduced design
clear structure
no unnecessary elements

This is not a design decision.

It is a deliberate decision in favour of:

comprehensibility
performance
trust

Especially in infrastructure, clarity matters more than visual complexity.

Conclusion

JUMBO BLOCK® is not just a physical system for stormwater retention.

It is a connected infrastructure approach that combines:

physical resilience
digital planning
economic assessment
and operational transparency

Across three platforms.
With one continuous logic.

From the first idea
to measurable operation.