# Data Flow

> A dashboard item that draws where the plant's data comes from as one flow from site to area, and on to equipment model, sized by the values stored.

Source: https://proxus.io/docs/analyze/dashboard-items/data-flow

The **Data Flow**  item draws where the plant's data comes from: one flow
from each site to its areas, as wide as the values stored. With an equipment model bound, the flow goes on to the
models; an area or a model that several sites share appears once, so a model fed by every plant is one band.

- **Header.** The values stored, the assets and the signals behind them, and how many areas (or equipment models)
  there are.
- **Chart.** Point at a band or a node to see its values. Where a column has more nodes than room for their names,
  the smallest share one **more** node, and its tooltip names them.

## Data fields

**Site**, **Area** and **Values stored** are required. **Equipment model** adds a third column. **Asset** and
**Signal** add their counts to the header; with them bound, there is one row per asset and signal.

## Where to see it

The Meridian demo plant uses it on **Meridian · Data Model Command Center**, filtered by the
[Signal Model](https://proxus.io/docs/analyze/dashboard-items/signal-model) item.

## Related

- [Signal Model](https://proxus.io/docs/analyze/dashboard-items/signal-model)
- [Namespace](https://proxus.io/docs/analyze/dashboard-items/namespace)
- [Proxus dashboard items](https://proxus.io/docs/analyze/dashboard-items)