Who Is This For?

Bridging the physical divide between factory floor execution and executive decision-making requires addressing the operational stakes of every department head:

What Actually Happens on a Typical Factory Floor?

When management audits production data, they often assume paper logs represent real-time shop-floor realities. In practice, a typical manufacturing shift tells a very different story:

Machine operators operate under physical constraints that office software architects routinely ignore:

Normal ERP Screen vs. Shop-Floor Kiosk

Why do operators resist traditional software? Compare what an operator experiences when recording completed work:

Operators Should See the Job, Not the ERP

When an operator approaches a kiosk, they do not need access to accounting ledgers, purchase requisitions, or inventory valuation menus. The kiosk displays only the parameters strictly relevant to the active machine cycle:

The 8-Step Operator Journey

A frictionless shop-floor workflow is structured so that each step flows logically into the next, requiring minimal cognitive effort:

Scrap Should Be Recorded When It Happens

Scrap logging is the single most vulnerable transaction on the factory floor. When rejections are recorded hours later, accuracy collapses into rough estimation:

Configurable Industry Scrap Reasons

The Same Interface Should Capture Downtime

Unrecorded micro-stoppages (5 to 15 minutes) represent the largest hidden drain on plant capacity. When machines stop, operators should not have to hunt for a supervisor to report the stoppage:

"Downtime must be recorded while the event is fresh, not reconstructed from memory at the end of the shift."

Machine Status at a Glance

Plant leadership and shop-floor supervisors must be able to understand the operational state of the bay without opening individual work orders or refreshing spreadsheet reports:

What Does This Data Actually Tell a Plant Manager?

Overall Equipment Effectiveness (OEE) is frequently treated as an academic formula. In reality, it answers three fundamental operational questions:

End-to-End System Architecture

The touchscreen kiosk acts as an edge gateway between machine operations, local edge runners, and the central Odoo ERP server:

The Odoo ERP Connection

The kiosk is not a separate reporting silo. Every operator interaction immediately translates into native Odoo manufacturing and inventory ledger updates:

When an operator logs 5 scrap parts, Odoo creates a verified stock.scrap transaction, deducts raw material from the work center inventory location, tags the exact financial cost center, and re-computes order completion metrics.

Technical Implementation: Odoo Work Order Integration

Below is an illustrative Odoo 18 / 19 Python ORM integration pattern showing how kiosk-originated production events, scrap entries, and operator identity tokens are processed securely in the ERP:

# -*- coding: utf-8 -*-
from odoo import models, fields, api, _
from odoo.exceptions import UserError

class MrpWorkorderKiosk(models.Model):
    _inherit = 'mrp.workorder'

    kiosk_operator_id = fields.Many2one(
        'hr.employee', 
        string='Logged Machine Operator',
        help='Operator identified via RFID badge scan at kiosk terminal'
    )
    kiosk_device_uuid = fields.Char(
        string='Kiosk Terminal UUID',
        help='Hardware identifier of the shop-floor terminal'
    )
    last_downtime_reason = fields.Selection([
        ('material_shortage', 'Raw Material Shortage'),
        ('tool_wear', 'Tool Wear / Broken Die'),
        ('machine_jam', 'Mechanical Jam-up'),
        ('setup_calibration', 'Job Setup & Calibration'),
        ('quality_hold', 'Quality Inspection Hold'),
        ('power_loss', 'Pneumatic / Power Fluctuation'),
        ('operator_away', 'Operator Shift Break'),
    ], string='Active Downtime Cause')

    def action_kiosk_record_scrap(self, scrap_qty, reason_code, notes=False):
        """
        Processes point-of-defect scrap logging directly from the kiosk interface.
        Enforces work-order relationship and deducts from active work-center location.
        """
        self.ensure_one()
        if scrap_qty <= 0:
            raise UserError(_("Scrap quantity must be greater than zero."))

        scrap_vals = {
            'product_id': self.product_id.id,
            'scrap_qty': scrap_qty,
            'product_uom_id': self.product_uom_id.id,
            'workorder_id': self.id,
            'production_id': self.production_id.id,
            'location_id': self.workcenter_id.property_stock_cost_id.id or self.production_id.location_src_id.id,
            'scrap_location_id': self.env.ref('stock.stock_location_scrapped').id,
            'origin': f"Kiosk {self.kiosk_device_uuid or 'Station'}: {self.name}",
        }
        scrap_record = self.env['stock.scrap'].create(scrap_vals)
        scrap_record.action_validate()

        # Audit message on work order chatter
        self.message_post(
            body=f"Shop Floor Scrap Logged: {scrap_qty} {self.product_uom_id.name} | Reason: {reason_code.upper()} | Operator: {self.kiosk_operator_id.name or 'Unassigned'}"
        )
        return {
            'status': 'success',
            'scrap_id': scrap_record.id,
            'remaining_qty': self.qty_remaining
        }

What If the Shop Floor Goes Offline?

Factory floors are harsh RF environments surrounded by heavy steel beams, high-voltage variable frequency drives, and concrete shielding. Network dropouts are routine events:

"Offline capability must be deliberately engineered for shop-floor workflows—preventing network blips from halting production."

The Factory Shouldn't Depend on One Screen

In manufacturing, equipment uptime is paramount. A shop-floor digitization strategy must define clear operational fallbacks for physical hardware failures:

Industrial Ergonomics: Designed for Physical Work

Designing for machine bays requires discarding standard web UX rules in favor of industrial ergonomics:

The Interface Should Tell the Operator What Just Happened

Operators should never be left wondering whether the ERP received their action. Immediate visual confirmations eliminate second-guessing:

Role-Based Interfaces & Industrial Badge Authentication

A touchscreen terminal should present different operational depths depending on who is standing in front of the machine:

Digitization Is About Event Timing, Not Just Screens

Replacing paper with a tablet achieves nothing if workers merely type shift-end guesses into a browser. True shop-floor digitization is about capturing operational events at the instant they happen:

What Management Sees: The Live Executive View

Because operators record clean, simple events at the machine, plant leadership receives structured, actionable telemetry on their executive dashboards:

"Operators enter simple events. Management receives structured operational intelligence."

From Operator Action to Management Decision

Here is how a single tap on a touchscreen kiosk ripples through the entire manufacturing enterprise:

6 Industry-Specific Kiosk Scenarios

Shop-floor touchpoints must reflect the exact materials, metrics, and quality gates of each manufacturing discipline:

What This Is Not: A Kiosk Is Not a Complete MES by Itself

Architectural honesty is essential when planning shop-floor modernization. A touchscreen terminal is a high-efficiency human-machine interface layer—not an entire Manufacturing Execution System:

Before Deploying a Shop-Floor Kiosk

Before installing touchscreen terminals on active production lines, verify that your hardware, network, and operational rules satisfy these 25 baseline checkpoints:

Failure-Scenario Test Matrix

True factory readiness is measured by how gracefully the system responds when conditions fail:

Measurable Business Outcomes: Before vs. After

Simplified operator interfaces significantly reduce operator training requirements because the workflow is restricted to the exact actions needed for the machine cycle: