Patok Gemba — Shop floor digitisation: production control, downtime and non-conformities

What happens today

01 The shift ends and nobody knows what happened: how much was produced, how long each machine was down, and why.
02 You spend your day putting out fires and depend on somebody telling you — and on them telling you all of it.
03 It is not fair that a plant that produces well cannot prove what it did.

The floor runs on paper and WhatsApp groups. The information exists: it is in the supervisor’s notebook, in the operator’s memory, and in a chat nobody is ever going to read again.

The capture

24 one-tap actions, stuck on the machine.

These are not twenty-four loose buttons: it is a catalogue organised by the moment of the shift. The operator scans the sticker that applies and the action runs — no menus, no keyboard, nothing to look for.

Start

Create WIP
Create and load
Start production
Set-up
Set-up → production
Load material

During

Downtime with a reason
Resume
Consume material
Ask for a refill
Scan skid
Call somebody

Finish

Finish
Finish and print
Finish to lot
Finish and queue
Tear down to queue
End of production

Problem

Andon · ask for help
Start maintenance
End maintenance

Utility

Reprint label
Unload material
End of shift

· 24 actions ·

Floor Kit

Patok prints each machine’s QR sheet in A4, A3 or A1. You stick it on, and that machine is instrumented. That is the whole installation.

One distinction that matters

The problem QR is an Andon —a call for help that escalates—, not a defect record. A quality inspection is a different thing and lives in its own flow.

It runs on the phone the operator already has in his pocket. That is enough to start — and when the plant asks for more, the hardware is further down this page.

The station

The screen the operator watches the whole shift.

Big buttons, for working with gloves on. At the top, the machine state with its clock and the shift band. In the middle, what is running. At the bottom, the queue in its real order — the one the order priorities dictate, not the one that shouts loudest.

Patok Gemba machine screen in Producing state, with order 0555-2026-LPR-W01 for a pharmaceutical customer, the shift band showing 11 h 15 min of production, 12 in the output bay, and the job queue with each final customer — Exactly as the operator sees it: PRODUCING in green, the running order with its customer, 11 h 15 min of production in the Shift 1 band, 12 units in the output bay, and the queue below, each row with its final customer.

64 px buttons, made for gloves and for a tablet bolted to the machine.
The shift band: how much it produced, how long it was down and how long in set-up.
The output bay: what finished and nobody has closed yet.
One QR per row, so scanning is the short path to everything else.

Who is operating?

You know what each person produced without giving them an account, an e-mail or a licence. The screen is shared and split across three shifts: you type the name and, if it does not exist, it is created right then. It is remembered per machine, and everything released is attributed to that person. That is what makes a bonus calculable.

Downtime with its reason

When a machine goes down, two clocks are running.

One is the alarm: it escalates on its own, level by level, at the minutes you define, to the people or groups you choose, through the app, push, WhatsApp or e-mail. The other is the task: somebody takes it, resolves it and closes it with a note.

Patok Gemba downtime reason dialog with seven causes configured by the plant —mechanical failure, out of material, tool change, electrical failure, quality adjustment, staff unavailable and other— and the Record Downtime button — Seven reasons, configured by the plant and per machine: mechanical failure, out of material, tool change, electrical failure, quality adjustment, staff unavailable, other. They come out ranked in a Pareto so you know which one to attack.

Escalation · minutes Downtime · 09:42

0 Operator and line supervisor AppPush
15 Production manager PushWhatsApp
45 Plant manager WhatsAppE-mail

And critical alerts ignore notification preferences on purpose. An escalated downtime is operations, not marketing.

The detail nobody else has

The system does not lie to you about whether the alert arrived.

Push · 3 sent · 1 with no device

WhatsApp · 2 sent · 1 outside the window

Instead of a “sent” that means nothing.

Patok Gemba Floor › Machines view: 7 machines, 3 operating and 1 down; the slitter stopped by an electrical failure with 34 h 49 min on the clock, and three machines idle — 7 machines, 3 operating, 1 down and 3 idle. The slitter has been stopped for 34 h 49 min and the reason is written right there: electrical failure. Each machine carries its queue (Q) and its priority (P).

Orders

What you owe to whom, and which machine it is on.

The planner’s notebook is not a report: it is a living sheet. You type on it, it saves itself, rows get re-prioritised, and every version of the plan is signed. And the same floor can be read as a board when what you want is to push columns.

The planner’s notebook in Patok Gemba: plan v9 with 2 orders at risk, 15 out of alignment and 1,176 accumulated hours; the three perspectives by order, machine and customer; and the running orders with their line items — Plan v9: 2 at risk, 15 out of alignment, 1,176 h accumulated. Below, 59 orders holding 122 WIPs. Each order opens its line items with machine, customer, quantity and notes — “burr on the edge: check…” was written by somebody on the floor.

Three perspectives, one plan

By order, by machine or by customer. It is the same information rotated, not three reports that contradict each other.

Six states, counted

Plan, queue, process, downtime, output and done. The number above each one is the real count, not an estimate.

At risk and out of alignment

The notebook tells you which ones are not going to make it and which ones no longer match the plan. It flags them; it does not hide them.

Signed versions

Every time the plan changes a version is kept with its timestamp. Arguing about Tuesday’s plan stops being an argument from memory.

Patok Gemba job kanban with 145 WIPs across five columns: Plan 5, Queued 40, In process 6, Output 92 and Done 2, each card with its order, its machine and its customer — 145 WIPs, 94 advanced (65 %). Plan 5 · Queued 40 · In process 6 · Output 92 · Done 2, with the oldest one in process (6 h 29 min) and the average wait in queue (5 h 22 min). Labels build a sprint; dragging is the floor’s verb.

How your orders come in

Any ERP knows how to send an e-mail. You forward the purchase order —a PDF, a spreadsheet or plain text— and Patok drafts it with customer, product, quantity and date. You confirm it. No API, no connector, no IT project.

Release control

Before releasing more work, the floor tells you whether you can.

You select what you were about to release and, before you confirm, Patok projects the effect: how much work-in-process you would be left with against your ceiling, how much the bottleneck queue grows, and whether the material is enough.

The Patok Gemba notebook with an order selected for release and the projection on top: CONWIP at 49 against a ceiling of 30, the bottleneck queue at 25 flagged as congestion, and a direct release with no routings — Here the floor is already at 49 against a ceiling of 30 — and it says so, in red, before letting you confirm. The bottleneck queue stays at 25 and that is flagged as congestion too.

L = λW

Little's law

Lead time comes out of the WIP and the throughput you actually measured. And the screen tells you where the number came from: real data, simulation, or a routing estimate.

CONWIP

Release gate

A ceiling on work in process. When you hit it the gate closes: no other order goes in until one comes out.

OEE

Availability × Performance × Quality

Computed from the downtime and the inspections that were actually recorded. If a factor is missing it comes out blank instead of inventing itself.

What nobody else does: Patok tells you when it does not know.

If nobody inspected, the quality factor of OEE comes out blank — not at 100 %. If there is no reference cycle time, it does not invent a performance figure. And the morning report greys out what is not instrumented yet instead of filling it in.

The floor on one page

Get the floor on one page

The six views, the 24 actions and what gets measured in each. As a PDF, in your inbox.

Quality

Two lanes that never mix: what gets inspected and what somebody complained about.

One board per plant, not per machine: what is left to inspect, how compliance is going, and what is still open. The inspection happens at the machine, in under a minute, and comes out with its printed label on the part.

0

uninspected

33

checks in 24 h

85 %

compliance

8

open NCR / CAPA

Patok Gemba quality board: 0 uninspected, 33 checks in 24 hours, 85 % compliance and 8 open NCR or CAPA; compliance broken out per machine and the latest inspections with their lot — 0 uninspected · 33 checks in 24 h · 85 % compliance · 8 open NCR/CAPA. On the right, compliance machine by machine: the sheet polisher at 50 % (1 ok · 1 fail) against a cross-cut line at 100 % (3 ok · 0 fail).

Lane 1 · the inspection

Measure, rule and decide what happens to the part —release, rework, scrap or hold— right there. The plant creates the check type itself: classification when you judge, measurement when you measure, with its unit and its limits.

Lane 2 · the non-conformity

Internal, customer or supplier: all three follow the same path. A customer e-mail to the quality inbox becomes a case with the counterparty matched, the line item, the catalogue defect and the attachments as evidence.

And when somebody has to be claimed against

The floor signal becomes a claim, is captured in the language of the plant’s own catalogue, and on issue becomes an official numbered document nobody can change any more.

The proof: from the skid you ship to the lot it came from

Skid WIPs Source lots Inspections Machine Cost

Every WIP on that skid, the materials each one consumed, the inspections it passed, which machine it was made on and what it cost — in one PDF. The chain assembles itself because the operator scanned the material as he consumed it. This is the moment a floor system is won or lost: an audit, a claim, a certification.

Maintenance

Three different questions: what is stopped, what is about to stop, and what hurts most.

The same floor, read by the team that repairs it. It is not a service calendar: it is the list of what has the plant waiting today, with the reason written by whoever saw it.

01
What is stopped

The machine that is down, with its clock running and the recorded reason. Nobody has to be asked: it is on the same screen where the operator declared it.
02
What is about to stop

The out-of-range readings, each one with its button to raise the work order. At Monteluna: 92.4 °C on the polisher bearing against a maximum of 85.
03
What hurts most

The reliability ranking. The slitter comes first, with 14.8 h MTTR and 29.5 h of accumulated downtime. The machine that hurts most is not the one that fails most: it is the one that takes longest to come back.
04
And the open work

Six open maintenance work orders, one overdue, and the preventive plan per machine with its cadence. Every intervention closes with evidence.

The board declares by itself that this repair time includes the waiting. It is not a flattered average: it is how long the plant actually took to produce again.

Walks and audits

An audit that is not repeated is a photo, not a trend.

A walk is a guided round of the floor: a script with its checkpoints, someone who walks it and answers point by point at the machine itself, and a round that gets closed. The sheet full of ticks nobody ever reads again is what this replaces.

01The script

The list. It is written once —5S, safety, quality, TPM, LPA— or derived from a round already walked. And if you would rather not write it first, you walk free and the script comes out of that walk.

02The round

When somebody walks it. Every point is answered at the machine, and whatever fails is written in the words of whoever saw it, not as a line number.

03The series

The same round repeated. It is the only one that shows a trend: in the capture, two rounds against a target of 85 % and an average of 92 %.

92 %

Compliance · 30 days

3

Rounds · 30 days

3

Findings · 30 days

0

Running right now

Patok Gemba Walks view: 92 % compliance, 3 rounds and 3 findings over 30 days, zero walks running, the latest rounds with their score and the two series by script — 92 % compliance, 3 rounds and 3 findings over thirty days — and zero running right now, which at seven in the morning is the number you look at. Below, the latest rounds with their score: 95 % and 89 %, both “passed” because the script asks for 85. The condition round carries no score because it does not score: it collects, and leaves 4 records.

The whole path is short

It is walked
It is answered
The round is closed
The finding is born

The step that matters is the third. Until the round is closed, the failures are nobody’s findings and the board counts nothing. Once closed, the finding stops living on the auditor’s sheet and moves into somebody’s list, with its machine and its time.

A Patok Gemba walk from the inside: REC-A000012 at 95 % with 19 points passing, one failing and one finding; the list of points with their machine and the note from whoever walked, and on the right the replay with its four stops — The round from the inside: 95 %, 19 points passing, one failing and one finding. The one that failed carries its machine —Línea de Corte Transversal 1— and the sentence written by whoever walked: “Two skids of finished goods blocking the cross-cut aisle”. On the right, the replay: the four stops in the order they were walked.

Every point is filed with its machine and the time it was answered. A failure is not one tick less: it is a sentence written by whoever was standing there.
A script does not have to score. A collection round takes the shift’s readings instead of ticking boxes — and that is where the data comes from, not a note.
The replay is assembled from what is already there: the QR, the mesh and what was captured. The screen says it plainly —“Map (no GPS)”—: the stops come from the order they were walked in, not from a location.
Every round keeps its number (REC-A000012), who walked it and at what time. A month later it opens again exactly as it was closed.

WhatsApp · Plant

The plant from the phone. There is nothing to teach.

WhatsApp is not an alert channel: it is where the floor already works. An operator sends a voice note and it is recorded with his name, his photo and the transcription — without opening an app, without filling in a form.

Note that there is a noise on the unwinder of number 3
Voice note · transcribed · kept in the log
Done. Recorded on Press 3 at 07:12, under your name.
How is number 3 doing?
Down since 09:42 · tool change · 1 h 18 m. It has 4 orders queued; OP-4471 is for Cliente Norte and is committed for Friday.

Dictates what he sees: A voice note is transcribed and kept with his name, his time and his photo.
Sends video: The system pulls the audio, transcribes it and extracts the findings the operator actually said.
Receives the andon: The escalated downtime reaches him right there, not on a board nobody opens.
Asks for the form: An Ishikawa, an A3, a 5-whys or a non-conformity — the PDF comes back.

It is the same engine and the same thread that serves the handheld console and the web chat. A question asked by voice shows up in the conversation the team sees, marked with where it came from.

Patok Gemba Link My WhatsApp dialog: generate a secure link, scan the QR code, send the message, and the account is linked automatically — Linked once: a secure link, a QR, a message sent — and that number is tied to that person. From then on the talking is short.

The log

The shift’s memory, written by itself.

The plant’s day told by the plant, with its time, its machine and the door each thing came through: what arrived by WhatsApp says “Agent” and what was done in the application says “System”.

Plant log Punch Press 3 · today

Shop floor · operational memory

Today · Monday the 6th

Live

07:12 OBS WhatsApp Transcript “There’s a noise coming from the decoiler” Juan Pérez · Punch Press 3
08:05 PRD System 47 production movements · 07:12 – 09:38 Punch Press 3
09:42 MAQ App Downtime · Tool change · 1 h 18 min Punch Press 3
10:26 CAL Email Visual Quality: FAIL 2/10 · burr (CRITICAL) · scrap Lot L-A0912
11:03 EVI Copilot Evidence anchored by QR · WIP-A000206 Glasses · with GPS
11:40 OBS Agent OA-238 · Resequence the Punch Press 3 queue Assigned to Miguel Ruiz

Plant pulse · 48 h PRDMAQCALOBSEVI

01 · The shift starts

Things happen. Nobody writes them down.

The odd noise, the hour of downtime, the part that came out wrong, the photo someone sent over WhatsApp. It all exists — scattered across chats, emails, and the memory of whoever was there.
02 · Someone speaks

The operator dictates and it gets written down

They send a voice note over WhatsApp: “make a note that there’s a noise coming from the decoiler”. It is filed with their name, their photo, and the transcript. No app to open, no form to fill in.
03 · Everything converges

Wherever it comes from, it lands in the same place

The quality email, the evidence from the glasses, the downtime the machine recorded, the action the agent assigned. Every entry carries the color of the channel it came in through.
04 · The plant has memory

And suddenly you can see the whole day

The 48-hour pulse stacks what happened by hour. Production fades back; the exception stands out. You no longer have to reconstruct the shift by asking around — it is written down.

What it looks like

Patok Gemba plant log: the plant pulse over the last 48 hours, filters for observations, quality, machine, evidence and production, and today’s events with their time, their machine and who recorded them — Plant pulse over the last 48 h and 60 events today out of 414 in the history. “19:52 · Machine CTL-1 DOWN — Out of Material · Agent” came in through WhatsApp; “19:53 · Move requested · System” was done by the application.

Production, machine, quality, observations, evidence and physical flow: six types, each with its own filter.
Every entry says who and through which door. None of them was typed by hand.
The operator’s photo and voice note stay attached to the event, not in somebody’s chat.
Searchable by text, by date and by machine. A claim from three weeks ago is reconstructed in a minute.

And what moves gets written down too: physical flow is one of the log’s six types, so every material trip lands on the same timeline, with its time and with whoever did it.

It brings the result

It does not say QUALITY_CHECK_PERFORMED. It says “FAIL 2/10 · burr (critical) · scrap”. The fact, not the name of the event.

The real time

The time you see is the time it happened, not when the system found out. A video analyzed three hours later lands on the minute the camera saw it.

No forms

Reporting is free: a voice note is enough. Making a note does not force you to open a task — that is another layer, and it is a human’s call.

NoteThe log is also one of the datasets Patok exposes over MCP — so you can ask it from Claude or ChatGPT without exporting anything.

Forklifts

“Picked up.” “Delivered.”

Moving material gets coordinated by shouting, over the radio, or on WhatsApp — and none of it leaves a record. Patok turns it into a task with an owner, a time, and evidence, on a screen made for a tablet and for gloved fingers.

Someone requests
Take the task
I arrived
Picked up
Delivered

It gets verified

The QR of the origin, the unit, and the destination are scanned. Verification can be skipped, but the system requires writing down why — and it is recorded.

It leaves a trail

A printed trip ticket that sticks to the material, and that applies the delivery when scanned. Inventory changes on confirmation, not on acceptance.

It gets measured

Delivered, in progress, exceptions, and average delivery time — broken down by operator.

The movements module is switched on during implementation, once the plant has the rest running.

Command Center

What gets asked out loud gets lost out loud.

The list of what somebody asked for, who it fell to, and what happened with it. Every action says why it was asked before it says what is asked, and it belongs to a team —Quality, Maintenance, Logistics—, not to a loose individual.

Patok Gemba Command Center with 11 actions: 9 open, 2 confirmed and 2 resolved; a request to a customer, an inspection of a skid and a maintenance intervention, each one with its reason and its team — 11 actions: 9 open, 2 confirmed, 2 resolved. “Slitter stopped by electrical failure: check the panel and the starter” goes to Maintenance, and its reason says it all: the machine has been down for over forty hours.

01
Open

Somebody asked for it and wrote why. It has no owner yet.
02
Confirmed

The team took it. This is the state almost everybody skips: an action with no owner is not an action, it is a wish.
03
Resolved

Closed with a note, a photo or the paper that goes with it.

The floor agent

It answers with your floor, not with a manual.

The plant pulse hands you the question and the agent answers with your machines and their queues. It reconstructs an order’s day hour by hour, hands you the shift report as a PDF inside the conversation, and says no when it has no permission.

Patok Gemba agent chat next to the plant pulse: 49 WIPs against a ceiling of 30 at 163 % capacity, high variability, the bottleneck at Cross-cut line 1 with 25 queued, and the agent’s recommendation for relieving congestion — Question: “what do you recommend to relieve congestion?”. Answer with the floor in hand: 49 active jobs, 43 queued, 6 in process; CTL-1 with 25 queued and 4 in process; SLT-1 with 6 queued and down; Inspection empty. Then the order in which to attack it.

The shift report arrives two ways: in your inbox, signed by your plant’s agent, and in the chat as a PDF.
An Ishikawa with the 6Ms ranked by impact and five guided whys, without leaving the conversation.
You e-mail it the dirty file your system spits out and it returns the report, a dashboard, the detail in Excel and the cleaned file, so you can check what was cleaned instead of trusting it.
When it has no permission, it says so. It does not invent the permission or the number.

What it runs on

It runs on what your people already have in hand.

The operator's phone is enough to start. And when the plant asks for it, there is a native console that runs on a watch, a PDA, and a tablet — the same app, adapting itself to the screen size.

Patok Console Android

The same app on the watch, the PDA, and the phone.

It adapts itself

It detects whether it is running on a two-inch wrist or on a tablet and sizes the buttons for a gloved finger.

It works with no network

Every action is saved on the device first. When the signal comes back, everything goes in in the real order it happened, with its original time.

It prints labels

The PDA's built-in printer or a 58 mm thermal over Bluetooth. An entity label with its QR and its lineage.

It scans with a gun

If the device has a laser reader, it works just like the camera. Nothing to configure.

It installs from a QR and updates itself: you cut the version and every device gets the notice immediately, verifying the fingerprint before installing. It does not go through app stores.

AI glasses Optional peripheral

A button at the temple, a photo of what you are looking at, and the answer comes back spoken in your ear. If the photo contains a machine's QR, the conversation is anchored to that machine.

Built and tested with the hardware in hand. They need a paired Android phone nearby, and they have no screen: the answer is voice only.

Beacons · Patok Mesh Enabled per plant

Bluetooth tags to find a lot with a hot-and-cold radar, take a census of an area, or know what was nearby when something happened.

They are configured from Patok, without the manufacturer's app. It is switched on during implementation; it does not come active out of the box.

Industrial kiosk with tablet, QR scanner, and thermal printer at a workstation — Industrial kiosk

A tablet mounted on the machine, with a reader and a label printer. The complete station for a high-volume line.

TabletUSB readerLabel printerFixed mount

Supervisor using a ruggedized PDA on a walk through an industrial plant — Gemba Walker

A ruggedized PDA for whoever walks the floor. Scan, review, and print without going back to the office.

PDA AndroidLaser readerBuilt-in printerOffline

Operator scanning a QR code with their phone on the shop floor — The operator's phone

What they already have in their pocket. Scan the QR with the camera and log it instantly, with nothing to install.

iOS / AndroidNothing to installCameraStart today

The three images above illustrate each setup; they are not product captures. The application screens you see on this page are real.

Who is telling you this

Horacio Canales Patok

I have stood on the floor at seven in the morning asking what happened overnight, and I have seen the face of the supervisor who does know but has not written it down. It is not that people do not want to: recording costs effort, and in the middle of a shift the machine takes all of it.

With Patok I take production control software to plants all over Mexico. Before that I did a doctorate in manufacturing engineering in Europe, with research for Airbus and for Rolls-Royce.

Who it is for

Plants where the shift ends and the data leaves with it.

The plant manager

Wants to know at seven what happened overnight without being told. Today he depends on a notebook and a WhatsApp group nobody is going to read again.

The production manager

Chases progress order by order and finds out about delays when they are already delays. He needs the queue to have an order, and that order to be respected.

The planner

Builds the plan in a spreadsheet and loses it the moment the floor contradicts it. She needs a living sheet that says which orders are at risk and which are already out of alignment.

Quality and maintenance

Have to prove what they did: the inspection, the claim, the intervention. And today the evidence is on somebody’s phone.

Process and transformation plants: steel cutting and service centres, coil processing, packaging, plastics, food, contract manufacturing. From one line to twenty machines. No IT department required.

How you start

Start with one machine.

01

We pick the machine that hurts most

Half an hour with you: what runs there, what stops it, and what you do not know today. Its QR sheet comes out of that.

02

The sheet goes up and that machine is instrumented

That is the whole installation. No PLC, no wiring, nothing touched on the equipment. The operator scans with the phone he already carries.

03

It runs a week on the real shift

After a week you have downtime with reasons, a Pareto and a shift report with your own data. If that worked, the next machine follows.

No new sensors · No ERP changes · Start with one machine

What is at stake

Two ways to close the shift.

If nothing changes

The shift ends and the data leaves with it.
Downtime is argued from memory and the Pareto never exists.
The audit asks for evidence and the evidence is in a chat.
The morning plan no longer looks like the afternoon floor.

When the floor records

At seven you know what happened overnight, without asking.
Downtime has a reason, and the reasons have an order of importance.
Traceability from the skid to the lot comes out as a PDF.
The plan is corrected with what the floor said, not with what somebody remembers.

Questions

What everybody asks.

Do I need PLCs, sensors or wiring on the machines?

No. Patok Gemba captures the data with a QR sticker and one tap: your operators are the sensors. The machine’s QR sheet is printed in A4, A3 or A1, you stick it on, and that machine is instrumented. That is the whole installation. If later you want to connect a machine signal, you can — but it is not the starting point and it is not needed to start measuring.

Do I have to change my ERP?

No. Your ERP is not touched. Any ERP knows how to send an e-mail: you forward the purchase order —a PDF, a spreadsheet or plain text— and Patok drafts it with customer, product, quantity and date; you confirm it. No API, no connector, no systems project.

Will my operators actually use it? They are not computer people.

They scan a QR and tap a button — and for everything else there is WhatsApp, which they already use every day. A voice note is recorded with their name, their time and its transcription, without opening an app or filling in a form. The machine screen is shared and nobody needs an account, an e-mail or a licence: you type the name and, if it does not exist, it is created right then.

Does it really run on WhatsApp?

Yes. The number is linked once —a secure link and a QR— and from then on the operator stands at a machine and speaks short: a six-word downtime lands with its reason, the forklift call goes out with a number, and the escalated downtime reaches him right there. It is the same engine that serves the handheld console and the web chat.

How long until it is running?

You start with one machine. Half an hour to pick it and build its QR sheet; it goes up and runs a week on the real shift. After that week you already have downtime with reasons, a Pareto and a shift report with your own data. If it worked, the next machine follows. There is no months-long rollout because there is nothing to install.

And if nobody records something? Does the system make it up?

No, and that is on purpose. If nobody inspected, the quality factor of OEE comes out blank, not at 100 %. If there is no reference cycle time, it does not invent a performance figure. The morning report greys out what is not instrumented yet instead of filling it in, and the agent says no when it has no permission or no data. One invented number destroys trust in all the others.

Does it help with audits and customer claims?

That is exactly the moment a floor system is won or lost. From the skid you ship to the raw-material lot it came from, in one PDF: every WIP on that skid, the materials each one consumed, the inspections it passed, which machine it was made on and what it cost. The chain assembles itself because the operator scanned the material as he consumed it.

Is this the same as Patok Office?

No. Gemba is the floor: orders, WIP, lots, machines, downtime, quality, maintenance and material moves. Office is the paperwork around production: customer orders, purchases, receiving, shipments and invoices. It is the same doctrine —count the WIP, see where it gets stuck— applied to two different terrains, and they can be used separately.

The floor on one page

Start recording what your plant already knows.

We send you the floor on one page, as a PDF: the six views, the 24 one-tap actions and what gets measured in each. And the Gemba tutorials as they are published.

The floor on one page, as a PDF, within the minute.
One e-mail per new tutorial. There are 22 published today.
No spam. You get out in one click.

See the tutorials →

Send me the floor on one page

We send you the floor on one page, as a PDF: the six views, the 24 one-tap actions and what gets measured in each. And the Gemba tutorials as they are published.

Your plant already generates the data. Nobody is recording it.