workcenter_dashboard_graph

Capacity planning on a shop floor comes down to one question per work center: is the coming week overloaded. A list of hours answers it slowly; a chart answers it at a glance, provided the chart distinguishes load from overload.

This widget does exactly that. It draws the work center's capacity as a line and its load as bars beneath, and puts any hours beyond capacity into a separate bar series with its own color. The overloaded days are then obvious without reading a single figure.

Everything charted comes from a JSON payload the server computes into a text field, the same arrangement the accounting dashboard chart uses. The widget adds the three-series configuration and the tooltip wording.

Overload that nobody sees becomes a late order. The value of separating excess into its own series is that it turns a quantitative question, how many hours, into a visual one, is there a second bar, which is the kind of question a planner can answer while scrolling.

It also makes the conversation about capacity concrete. Adding a shift or moving an order is easier to argue for against a picture of three overloaded days than against a spreadsheet of hours.

The usual usage

<field name="workcenter_load"
       widget="workcenter_dashboard_graph"
       graph_type="bar"/>

The attribute names the chart type, as on the base widget.

The three series

capacity      # drawn as a line
total load    # drawn as bars
excess load   # separate bars, own color

All three come from the same payload and share one category axis.

The base chart

<field name="kanban_dashboard_graph"
       widget="dashboard_graph" graph_type="line"/>

One series, no tooltips, and a much simpler payload.

The configuration is a scatter chart carrying three datasets, which is how a line and two bar series share one axis. The line is the capacity, and the two bar series are total load and excess load, each with its own color drawn from the interface palette.

Separating excess into its own dataset rather than coloring individual bars is the design decision worth noting. It means the legend concept exists even though the legend is not shown, and it lets the excess sit visually on top of the load rather than replacing it.

Tooltips are the other difference from the base chart. They are enabled, and the label callback appends the word hours to each value, with a distinct branch for the total load series so that the number shown is the total rather than the segment. That branch is the sort of thing that only makes sense once you know the series are stacked conceptually.

The x axis is a plain category axis fed by the payload's labels, so the granularity, days or weeks, is entirely the server's choice.

Odoo 20 is expected at Odoo Experience in Brussels, 24 to 26 September 2026. The development branch is unstable and this may still change; we re-verify this page after the release.

Byte-identical. The file on the development branch matches Odoo 19 exactly, including the three series and the tooltip wording.