A pallet running out at the point of use
The operator replenishes it with one tap and a confirmation, and follows the AGV and the forecast in Active calls.
The problem Information does not reach the people on the line.
The floor tablet and the line panel: material calls, the operator's plan and tickets.
Lines, points of use and operator codesCaptures from the running application, with demonstration data.
A 4-digit operator code opens the session, and the operator picks the packing line. Every request is logged with its author, and the session ends after 5 minutes without a touch.
Each point of use has its own buttons: replenish a pallet at a position, take away empty pallets and cases, or a full waste bin. Nothing is sent before the operator confirms.
No stock in the warehouse, no AGV free, a request already active for that position: each case has its own message and says what to do, and a duplicate is blocked before it becomes a double delivery.
Active calls shows the AGV, the forecast and the elapsed time, and paints red what is past the forecast. Everything that happened stays in the operations log.
Lines, points of use and operator codes
This is the hard requirement. Without it, the capability has nothing to read.
The operator replenishes it with one tap and a confirmation, and follows the AGV and the forecast in Active calls.
The second request is blocked before it goes out, and the tablet points to the request that is already in progress.
No request is created, so there is no risk of a double call, and the tablet says what to do: ask the logistics lead by radio and record it on the contingency form.
The operator calls material, follows each request and opens a ticket when something needs adjusting, without leaving the post.
Each request arrives with line, point of use, position and operator, and the destination of each button is changed in the field, with no new version of the app.
The operations log keeps who asked for what, when and with what result, so supply on the line is discussed with data.
Every capability reads from and feeds the others. What this one exchanges inside the operation:
The material call is the materials module on the line: each request carries line, point of use, position and operator, and a request with no stock in the warehouse is refused before any AGV is sent.
The site's batches and quality forms open on the tablet, and a device set up for it keeps answers and signatures without network until the next sync.
On the tablet the plan is read only, by machine, day and shift, and a comment on any card is how the operator sends information back to whoever plans.
Bring the lines and points of use of one area. In the demo we call a material and follow the request on the tablet.