“Practical Examples” chapter

The six examples from the book, one per entry channel

The following cases correspond to real deployments, and they follow the order of a working day in a plant. Six cases, six different entry channels: an email, a label, a WhatsApp message, a photograph, a panel, a voice. At the end of each case, the address where you can request the exact return on investment it produced.

Editorial illustration: at 5:00 a.m. order emails in Excel, PDF and plain text become a unified order book and three plan proposals the head of planning compares on screen.

5:00 a.m.

Orders come in on their own

The complete order book, always up to date with nobody typing: IRIS Connect reads every email on arrival — Excel, PDF, or plain text — and every night the planner generates three plan proposals. The head of planning compares, adjusts, and validates at 7:15 a.m.

 Editorial illustration: at 7:31 a.m. the production manager photographs the first unit's label, the system flags the expiration-date discrepancy, holds the printer and distributes the alert to quality and the line technician.

7:31 a.m.

The plant's paperwork

One photo of the first unit's label, and the system checks product, lot, and expiration date against the order in progress. This morning the date didn't match: line alerted, printer held, and the procedure distributed within the same minute.

 Editorial illustration: at 8:40 a.m. a WhatsApp message reports a broken down truck; on screen, the affected purchase order and the proposed replanning with reshuffled orders and alerts to sales, warehouse and line.

8:40 a.m.

The trucker's WhatsApp

The truck breaks down and won't arrive until Thursday. IRIS Connect reads the message, identifies the affected order, and the planner redoes the plan validated an hour earlier: moves work up, reshuffles, recalculates dates, and notifies everyone affected. The manager validates — and Thursday stops being a fire.

 Editorial illustration: at 12:10 p.m. the quality manager photographs an automotive part in the inspection area and the screen shows a scratch, a burr and pores classified by severity, with the proposed hold.

12:10 p.m.

The part in the inspection area

One photo in the inspection area and the defects appear marked and classified by severity. Production is running: line alerted and a hold proposed on the spot. The same network works as short-cycle AI inside the line: two speeds, one shared memory.

 Editorial illustration: at 3:12 a.m. a fixed low-cost camera points at the kiln's analog panel and its firing curve appears posted into central memory and the ERP.

3:12 a.m.

The kiln panel

The oldest machine in the plant, without a single data port, gets connected with a low-cost camera facing its panel: readings every few seconds and the firing curve posted into central memory and the ERP, 24/7. A camera, a bracket, and one afternoon of installation.

 Editorial illustration: Sunday at 6:40 p.m., the on-call technician checks the incident and its history on his phone while the earpiece guides him step by step, hands-free.

Sunday, 6:40 p.m.

The voice in the earpiece

A line goes down on a weekend and the on-call technician has been with the company for three weeks. The system presents the full context and the earpiece guides him step by step, hands-free. By 7:30 p.m. the line is running — without a single phone call.
IRIS hardcover, English edition, by Sebastian J. Brau with a foreword by Jay Lee

This case is one of the six in the “Practical Examples” chapter

“Practical Examples” walks through a working day in a plant with six different entry channels: an email, a label, a WhatsApp message, a photograph, a panel, and the voice. It is part of IRIS, by Sebastian J. Brau (foreword by Jay Lee, University of Maryland).

Join the book waitlist