How a Shared Plan Shortens the Daily Production Meeting

A daily production meeting runs long because it is not really a meeting, it is a data reconciliation session: most of the time is spent agreeing on what the schedule says before anyone can decide anything. EDGEBIC by User Solutions removes that half by putting one computed plan and one set of logged actuals on a screen the whole room reads. What is left is the part that needed a room: the four jobs in trouble and who owns them.

This post is about the meeting-time outcome. It sits under the EDGEBIC results guide. For the mechanics of the board itself, see how to use the standup dashboard.

What the Meeting Is Actually Doing

Sit in one and time the segments. A typical 45-minute production meeting breaks down roughly like this:

Only the last block needed eight people in a room. The first 35 minutes exist because sales is reading a promise-date spreadsheet, the supervisor is holding a list printed yesterday afternoon, maintenance knows about a spindle nobody else has heard about, and no two of those sources agree. Before the group can act, it has to merge them out loud.

That merging is not a communication problem you can fix with a better facilitator. It is a data problem, and it disappears when everyone reads the same plan.

One Board, Read Top to Bottom

The standup tab is built for exactly this ten minutes. It switches to a dark floor-TV theme for a wall screen and lays out four things in the order a meeting needs them:

• The SQDC band. Safety, Quality, Delivery, Cost across the top. Delivery shows on-time performance, Cost shows a variance figure. Safety and Quality show a dash with an Offline chip until an incident or defect log exists to compute them from, which is the board declaring what it cannot yet know instead of inventing a number.
• The Andon strip. One colored tile per active work center. Green is running on plan, yellow means elapsed time has passed 125 percent of the planned duration, red means the station is past its planned start with nothing logged, blue is a material wait, and white is planned downtime.
• The late jobs list. Jobs ranked behind their due date. Click a row and you land on that job's Gantt.
• The bottleneck panel. The constraint station's load today next to its seven-day average.

Read top to bottom and you have the shop in about 40 seconds. Nobody reports status, because the status is already on the wall. The room starts at the first red tile.

The Arithmetic

Take a plant running the 45-minute version with eight attendees.

That is roughly 83 hours a month back, and the hours come from the people you least want stuck in a conference room at shift start. A supervisor released 30 minutes earlier is on the floor while the first setups are happening, which is when a bad setup is cheapest to catch.

The saving is real but it is not free. It requires that the actuals feeding the board are current, which means operators logging starts and finishes at the kiosk rather than at the end of the week. That is the trade: a few seconds of logging per operation buys the plant a meeting it does not have to hold.

The Questions That Leave the Meeting Entirely

Half of a long meeting is people asking where one specific job stands. Those questions leave the room when a faster answer exists, and the report catalog carries three:

Once people learn that a 20-second lookup exists, the meeting stops being the way to get status, because it is the slow way. See the EDGEBIC report catalog for the full set.

The Second Meeting You Also Stop Holding

There is usually a follow-up meeting after the meeting: two or three people in a hallway deciding what the group could not, because the group never got to a decision. That one goes away too, and it is often the more expensive of the pair because it pulls the exact people who were about to do something useful.

A shared plan also changes the tone. When the schedule is a computed result rather than one person's opinion, disagreements move from "your number is wrong" to "the plan assumes 14 hours here and we both think that is high." The second conversation is short and produces a routing fix. The first one has no end.

What This Does Not Do

It does not remove the need for the meeting. Exceptions still need a decision and a name attached to it. The board tells you which four jobs to talk about; it does not decide which one gets the overtime.

The Andon colors are inferred, not sensed. Tile state comes from schedule actuals, not from machine signals. A station running with an unlogged start paints red. That is worth knowing before you distrust a surprising tile: check the kiosk before doubting the board.

There is no auto-refresh. Click Refresh at the start of the meeting or you are reading the last time somebody looked.

Safety and Quality stay honest rather than full. They read Offline until the underlying logs exist. A dash is better than a fabricated green, but it does mean two of the four SQDC letters are placeholders on day one.

It will not fix a meeting that is really about something else. Some daily meetings are long because two departments are in conflict. A shared plan removes the excuse, not the conflict. What it does do is stop the argument being about whose spreadsheet is right, which is the version nobody can win. See how one plan aligns sales and production promises for that side of it, and what production scheduling is for the underlying idea.

Want to see your own morning on one screen? Bring an export to a demo and we will put your jobs on the standup board and time the read.