Skip to content

Dashboards

Dashboards are in beta — the core works and your data is safe, but expect rough edges. Tell us what breaks.

A dashboard is a saved question, rendered continuously: order backlog per month, stock value, purchasing per supplier. Every number is fetched live from your ERP when the page is shown — nothing is a stale export, and every widget shows when its numbers were fetched.

Create one from the chat

Describe what you want to see, in your own words:

gör en dashboard med orderstock per leveransmånad, lagervärde och de största leverantörerna

The colleague builds the page, validates every widget against your ERP, and answers with the address. The dashboard appears under Dashboards in the left menu, and its definition is saved in your company repository — a plain file you own, like everything else.

Edit it the same way

Ask for changes in the chat: "lägg till leveransprecision per kund", "ta bort inköpsgrafen". The colleague rewrites the definition and checks every widget again before saving.

On a wall screen

Open a dashboard and press Kioskläge: a window of its own, full screen, larger type, meant for a TV in the workshop. It refreshes itself. The page otherwise refreshes on its own schedule too; Uppdatera nu fetches everything again at once.

Honest numbers

  • Every widget shows hämtat kl … — when its numbers were fetched.
  • A widget that fails shows its error alone; the rest of the page lives.
  • Amounts in different currencies are never added into one figure.

One page, many values

A dashboard can declare a chooser — one "Supplier" page serving every supplier through a dropdown, instead of a page per supplier. Ask the chat: "gör en leverantörsdashboard med en väljare för leverantör".

Daily steering (daglig styrning)

If you run a daily-steering board in the workshop — Monitor's own board or a whiteboard — the same questions can live here. Ask the chat for a dashboard with:

  • Shop load — open operations per work center, remaining and overdue hours, and days of load against the center's capacity basis.
  • Run plan — one work center's operations in planned-finish order with an overdue flag. A work-center chooser on the page makes one dashboard serve every group.
  • Open manufacturing orders — totals, what is overdue, and the load per planned finish week.
  • Rejections — scrapped quantity per day, article and work center, with the scrap rate. Monitor's API exposes no cause codes, so the cards show what and where, not why.
  • Internal delivery reliability — the share of operations finished on time, per week, with the same tolerance idea as Monitor's board.
  • Order proposals and production efficiency — what should be ordered, and planned versus reported time.
  • Customer OTD (delivery precision) — the share of customer order lines delivered on time, against the requested or confirmed date and with your delivery windows. Partial deliveries count as complete at the last shipment, and orders that cannot be judged are reported as such instead of guessed.

What we deliberately do not show: the absence board and staffing adjustments. Monitor's API does not expose them, and a guess has no place on a steering board. Hours and capacity come from the preparation's time fields and the work centers' capacity basis — check the first numbers against Monitor's own körplan screen, then trust the wall.