How-tos Concepts Training paths

How to run the daily meeting from the board

Wiki: Floor concepts

When to use this

You run a short daily or per-shift standup, ten minutes or less, and want one screen that already has yesterday’s numbers, the biggest losses, what is still open, and what changed, instead of pulling several screens together yourself.

Steps

  1. Click Home, then Daily Board (/daily).
  2. If your account covers more than one line, pick Line or Plant near the top. Line shows one line’s own numbers, Plant rolls every line up together, the manager view. If your plant only has one line, the board opens straight to it.
  3. Walk the board top to bottom:
    • Yesterday vs target, OEE, good parts, and first pass yield for the day, next to the target and what the numbers were graded against.
    • Top losses, the three biggest dollar losses from yesterday, each with its likely reason.
    • Open actions, work items still open, with an owner and how long each has been open.
    • What changed since yesterday, alerts opened and closed, plus how many jobs are late and how many preventive maintenance tasks are overdue right now.
    • Stops coded, the share of yesterday’s stops a person or the auto-classifier assigned a reason to, and the share coded within 15 minutes of the stop ending. Coded within 15 minutes is the habit worth building: a reason picked while the stop is still fresh is a reason worth trusting. Stops still blank carry no reason at all, and are listed by machine, start time, and length, each one tap from that machine’s coding queue on the Downtime page.
    • A line naming how many losses from the last 7 days still have no action against them, with a link to the Opportunities board already filtered to just those.
  4. See a loss with no action against it yet, click Raise action on that row. It creates a work item already linked to that machine and reason, so someone owns it before the meeting ends.
  5. See a stop still blank on the Stops coded card, click it to jump straight to that machine on the Downtime page and pick a reason.
  6. Click Email to send the board to the team, or Print for a paper copy on the way to the floor.

On your phone

Open /daily on your phone and the board reorders itself for a quick walk down the screen: top losses first, then open actions, then stops coded, then losses with no action against them, then yesterday’s numbers, then what changed. Each loss row carries two full width buttons, View loss and Raise action. Each andon call or incident in Open actions carries an Acknowledge button right on the row, so you can mark it seen without opening the work item.

Pick a line once and the board remembers it: next time you open /daily on the same phone, it opens straight to that line. Switching phones or tablets, or opening the board on the web, remembers the same line too, once you have picked it at least once on any device while signed in.

Turn on push notifications (see How to enable push notifications on your phone or tablet) and Spall sends one notification each morning naming yesterday’s biggest loss, how many actions are still open, and how many stops still need a reason. Tap it to open the board already scoped to your line.

Notes

  • Every number on this board comes from the same live data every other screen uses, it is an assembly, not a separate data source, so it always agrees with Performance, Opportunities, Alerts, and Work Items.
  • Jobs late and preventive maintenance overdue are counted right now, not since yesterday. There is no record of who was late yesterday, only who is late this minute.
  • Coded within 15 minutes only counts stops coded by a person, not a stop the system automatically coded as a short minor stop. A window that starts before your plant began tracking coding speed shows “timing tracked from” a date instead of a share, so an old stop never looks slower than it really was.
  • The board defaults to yesterday’s full day so the whole prior shift is captured, beyond just the last few hours. “Yesterday” is your plant’s own calendar day, not one fixed clock for every plant, so a shift that ends at midnight local time always lands on the right day. The subtitle under the header names the day and the plant’s timezone. A multi-site account viewing Plant scope uses the timezone of the first site set up on the account.