Fleet Overview

Three views of the whole fleet of metering nodes in one report — a type-by-status matrix, a hierarchy tree, and an expandable table.

A single entry point to look at the whole fleet of metering nodes in three different ways. You choose the view at launch and can switch between them instantly. It is meant for operators and operations teams who need to understand the composition and condition of the fleet quickly, from a convenient angle.

What it shows

Three views of the same data:

View	What it shows
Matrix	a “corrector type x operational status” table — how many devices of each type are working, under repair, blocked, and so on. A quick overall snapshot of the fleet.
Hierarchy	a 4-level tree: utility / DSO -> subsidiary organization -> customer -> metering node. Expands on click.
Table	a large expandable table with totals at each level; within a customer, a breakdown by device type is added.

All three use the same fleet data — they differ only in how it is grouped and displayed.

How it works

The report itself computes nothing substantive — it simply builds the chosen view. You select a view and the corresponding layout (matrix, hierarchy, or table) is built.

The matrix works only with fleet metadata and is therefore fast. The hierarchy and table additionally load customer lists, so they take longer to build; loading runs in several parallel threads for speed.

The data source is the fleet-wide reference data: metering nodes, utilities, and customers.

Run parameters

Parameter	Default	What it means
View	Matrix	which angle to build: matrix / hierarchy / table
Utility company (fleet filter)	from context	filter the fleet by utility / DSO
Device types in matrix	all (0)	matrix only: how many device types to show (0 = all)
Parallel fetch workers	8	hierarchy and table only: number of parallel download threads

Parameters not relevant to the chosen view are simply ignored: the matrix needs no threads, and the hierarchy needs no type count.

How to read the result

Matrix — for a quick answer to “what do we have, and in what state”. Look at the columns with problem statuses (blocked, under repair).
Hierarchy — when you need to go top-down: from the company to a specific node, expanding the branches you need.
Table — when you need totals at every level at once, plus a breakdown by device type within a customer.

Useful to know:

The matrix builds quickly; the hierarchy and table are slower because they load customers.
To compare two views of the same fleet, run the report twice with different selections — both stay open, and switching is instant.
From here you can move on to analyzing a specific metering node in a separate report.