LubiMES Station terminal · ST04-PC · Line A

Sign in

Every action on the floor is recorded against the person who performed it, so the terminal is never left signed in to a shared account.

Five failed attempts lock the account and raise an entry in the audit trail. Passwords are stored hashed and are never visible to an administrator.

Identity photo

Captured at sign-in and attached to every unit built during the shift.

Camera ready Capture happens automatically when you sign in
On a station PC this needs HTTPS with a certificate the machine trusts, or the browser refuses camera access without warning.

Demonstration accounts

Pick a role to fill the form. Each one sees a different system — that is the point of this screen.

LubiMES Reference build
Shop floor
Supervision
Records
Administration

Station 04 · IPC Assembly

LINE A · TERMINAL ST04-PC

ShiftA · 06:00 - 14:00
Done / Plan18 / 26
10:42:06

Station Queue

Orders released to this station. The colour tells the operator whether the job can be started before they walk to the bench.

Green — ready to start

Every material issued and verified, incoming QC clear, previous stage signed off.

Orange — ready, carries a remark

Startable, but a material or QC condition was bypassed under an approved deviation. The remark follows the order for life.

Red — not ready

A hard stop. The station cannot open the job until the listed condition is cleared.

Line Dashboard

Live view for the supervisor. Every figure here is computed from station transactions — nothing is keyed in twice.

Hourly output

Good units, with rework shown separately

Good Rework

Stations

Same colour language as the queue

Why jobs are held

Blocked and deviation reasons, this shift

Open deviations

Every orange order on the floor right now

Where these numbers come from. Output, yield and cycle time are derived from the same stage transactions that build the traceability record. There is no separate production entry screen, so the dashboard cannot drift from what actually happened at the bench.

Traceability

One serial in, the full history out — and the reverse: one component lot in, every finished unit it went into.

Try LBE-2026-004417 (clean unit) or LBE-2026-004431 (carries a deviation).

Audit Trail

Append-only. Every insert, change and approval is written with the user, the terminal and the before and after value.

The audit table cannot be edited, by anyone.
Update, delete and truncate are blocked inside the database itself, not merely hidden in the application. A user with full database rights still cannot rewrite a line of this table.
Retention. Audit rows are retained for the full life of the product record and are included in the nightly backup. Exports are produced as signed CSV for sharing with an auditor or customer.

Roles & Access

Permissions are granted to a role, and people are put into roles. Nobody is given a permission directly, so there is never a user whose access nobody can account for.

Read the empty cells, not the ticks.
A System Administrator can create users and edit masters but cannot approve a quality gate or run a job. A QC Inspector can pass in-process work but cannot sign off final QC. Those gaps are deliberate: they are what stops one person from taking a unit from start to dispatch on their own.

Permission matrix

Every screen and every action in the system

People

Who holds which role right now

Changing a role is itself an event. Every grant and revoke is written to the audit trail with the administrator who made it and the value before and after, so a permission that appears on a Friday evening can be traced on Monday morning.