Skip to content

Build a dashboard view from tiles

The Dashboard editor decides what everyone sees on the analytics overview: which tiles, in which order, at which width. An organisation can keep several saved views (say, an executive summary and a maintenance focus), and each view can be company-wide or belong to one site.

  • Permission: analytics:manage — without it the page says: “You have no right to edit the dashboard — your administrator can grant it (Master data → Roles).” The dashboard is the organisation’s view, not a personal setting: whatever you save, everyone sees.
  • Starting point: until a view is saved, the built-in default applies — the page says: “You have no saved views yet — you are looking at the built-in default. Use the “From a template” button to start a new one.”
  1. Open the editor from the analytics tab bar: “Dashboard editor”. At the top you pick which saved view to edit; “New view” starts empty, and “From a template” offers six ready-made templates (e.g. “Operations overview”, “One metric at a glance”, “Shift comparison”, “Daily rhythm”). A template is only the starting point: “it loads into the editor, and nothing is stored until you press Save.”
  2. Set the name and the scope. “Scope” is one of two values: “Company default (all sites)” or “This site only”. The “Make this the default view” checkbox decides what everyone sees first — one default per scope.
  3. Assemble the tiles. The “Add tile” palette offers eight kinds: KPI tile (number + context) · Trend · Breakdown (bars) · Metric table · Data coverage · Breakdown (chart) · Calendar (heat map) · Scatter. Drag a tile into place, or select it and move it with the arrow keys; Shift+arrow resizes (4/6/8/12 widths on the 12-column grid), Delete removes it. On a phone the buttons in the settings sheet do the same.
  4. Configure the tile. With a tile selected, the panel on the right picks the metric, the breakdown (operating mode / shift / plant) and — if needed — a plant filter: the tile then shows one plant’s data only, and its caption says so.
  5. Save it: “Save view”. Success is confirmed with “View saved.”

Switching back to the “Overview” tab shows the new layout; if you marked it default, everyone gets it first. The view also appears in the header’s view picker.

What you see Why What to do
“You have no right to edit the dashboard — your administrator can grant it (Master data → Roles).” You lack the analytics:manage right. Ask your administrator — viewing (analytics:view) is independent of it.
“Someone else changed this view in the meantime. Reload it so you do not overwrite their work.” Two editors worked on the same view. Reload the page, review the current state, then save your change.
“You reached the 24-tile limit — a longer dashboard is neither readable nor fast.” The view is full. Split it into two views (say, executive ⟂ detailed) and switch between them with the view picker.
“No tiles — add some below. While empty, the built-in view stays in effect.” You are about to save an empty view. Add at least one tile — an empty save does not replace the built-in default.
  • Customize the PDF report. At the bottom of the editor, the “Customize the PDF report” box: “By default the PDF mirrors the dashboard 1:1. Here you can reorder tiles, insert headings/text, break pages, or leave tiles out.” This also shapes the scheduled-delivery document; on an unsaved view the box asks: “Save the view first.”
  • Edit as JSON. The “JSON” button gives and takes the full content of the view (and the PDF report): “Pasting only loads the draft — saving works with the usual button.” A view can thus travel to another site or organisation without re-clicking everything.
  • Deleting: “Delete view” is final — but schedules pointing at it are not deleted with it: on their next run they stop with a speaking error, and they need a new target view.

Last updated: