The six leakages your daily report hides — and the one screen that surfaces them

The 11 pm reconciliation

You know the routine. The plant closes. The supervisor sends the shift output on WhatsApp. Accounts sends the dispatch summary. Store sends the GRN list. Somewhere around 11 pm you open all three on your phone and try to make them agree.

They never fully agree. Copper issued does not match wire produced. Cartons dispatched do not match invoices raised. A job card shows complete, but the coil is still on the floor. You note the gap, tell yourself you will chase it tomorrow, and tomorrow brings a new gap.

The problem is not your team. The problem is that a daily report is a summary. A summary tells you the total. It cannot tell you where the total went wrong. Leakages live in the gaps between numbers, and a report is built to hide gaps.

Here are the six leakages we see most often in ₹10–50 Cr factories, and why the report cannot show them.

Six leakages a summary cannot show

1. Vanishing raw material

RM goes out on issue slips. FG comes back on job cards. The difference is called "process loss" and nobody questions it until the year-end stock audit. In a wire plant, a 1% gap on copper is a serious number. In laminates, it is resin and paper. The report shows consumption. It does not show consumption against standard, batch by batch.

2. Ghost production

A job card is marked complete because the shift is ending, not because the coil passed. The output figure looks healthy. Then the coil sits at the next stage for two days waiting for rework, and no one can say where it went. Output was counted. Value was not created.

3. Off-spec slipping through

Inspection happens. Results go in a register. The register is checked at month end. Meanwhile a lot that failed a parameter was already packed because the packing team did not know. The complaint arrives from the dealer three weeks later. Now it is a warranty cost and a relationship cost.

4. Orders drifting late

Nobody decides an order will be late. It drifts. RM arrives a day late, the job card waits for a machine, QC is backed up, dispatch is Monday instead of Friday. Each delay is small. The customer only sees the sum. Your report shows "orders pending"; it does not show which ones are at risk today.

5. RM shortfalls nobody planned

Purchase raises orders from memory and from what the planner shouts across the floor. Then a big MTO order lands and three SFGs need an RM that is not in stock. The shortfall becomes visible on the day the job card is supposed to start.

6. Incidents lost in WhatsApp

A machine breakdown, a gate-pass argument, a rejected lot from a supplier. It goes in a group. Ten messages later it is buried. Nobody owns it, nobody closes it, and it comes back next month.

What the Command Centre does differently

MAFLO's Command Centre is not a dashboard of totals. It is a live exception queue from the MES. It reads every job card, barcode state, QC result and order risk score, and shows you only what is stuck, ranked by how much it is hurting you right now.

It ranks on four things.

Ranking signal	What it asks	Which leakage it exposes
Most-blocked stage	Which process step has the most job cards waiting?	Ghost production, off-spec
Longest queue age	What has been sitting the longest without moving?	Orders drifting late
Most overdue	Which orders have already crossed their promise date?	Orders drifting late, RM shortfalls
Act-now vs watch	Does this need a decision today, or just an eye?	Everything else

Behind it, the Orders screen scores every order as On Track, At Risk, Delayed or High risk, with a fulfillment bar and MTO/MTS split. Stock Status splits every item into Physical, Reserved, Available, Quality Hold and Rejected, by depot. The Planner runs exception-first MRP: late planned orders, material shortfalls, capacity violations, bottlenecks, blocked job cards. Barcodes carry a state ladder from Created to Quality Pass or Fail to Store In to Dispatched, with Rework and Scrap as explicit branches. IQC, PQC and FQC each have a register, NC and release approval. Tasks & Incidents give every issue a ticket number and an SLA.

The Command Centre sits on top of all of that and asks one question: what should the owner look at first?

A worked example: a wires factory

Take a copper winding wire plant running drawing, annealing, enamelling and spooling. Monday morning, the Command Centre shows:

Most-blocked stage: enamelling, 14 job cards waiting. Longest queue age: one job card at 41 hours. Act-now: 3 orders.

The owner opens the enamelling stage. Nine of the fourteen job cards are waiting on PQC. The PQC register shows one parameter, enamel thickness, failing on two lots from the same drawing machine. Those two lots are on Quality Hold in Stock Status, not in Available, so sales cannot promise them. A NC is already open against the machine, and the Machine Inspection Dashboard shows an open NC with zero closure this week.

The three act-now orders are all MTO for one dealer, all High risk, all pegged through the Planner to an SFG that comes out of that same enamelling queue.

That is one screen, three clicks, ten minutes. The owner now knows: one drawing machine is producing off-spec, it has blocked one stage, and that stage is holding three orders for one customer. The fix is a machine, not a lecture to the shift.

Under the old routine, this shows up at 11 pm as "enamelling output low" and a dealer call on Thursday.

What to do Monday

Do not start by configuring everything. Start with the queue.

First, get every job card into MAFLO with a barcode. No barcode, no state, no visibility. This is the one thing that cannot be skipped.

Second, put IQC, PQC and FQC results into the registers as they happen, not at month end. A Quality Hold bucket only works if the hold is entered on the day.

Third, open the Command Centre every morning before the WhatsApp groups. Look at the top three act-now items. Assign each one as a ticket with an owner and an SLA. Ignore the rest until tomorrow.

Fourth, after two weeks, look at which stage was most-blocked most often. That is your first real bottleneck. Fix it with the APS Scheduler and Work Centers, not with overtime.

The point is not more data. The point is fewer things to look at, ranked correctly.

See your plant. Catch the leakages. Sleep at night.

If you run a wires, lighting, laminates or resins plant and want to see the Command Centre on your own job cards, talk to us. We will show you the exception queue, not a slide deck.