Shop-floor visibility and operator terminals: interpreting the production picture

Shop-floor visibility helps a supervisor connect a production problem with the work centre, order and people affected. A station waiting for material needs a different response from a station marked down. The purpose of the view is to support that decision with traceable production information.

DNA provides a 3D plant layout and an Andon board. Areas, zones, work centres and linked resources give the plant its structure. Current jobs, queued work, instructions and operator confirmations connect that structure with execution. The supplied implementation also distinguishes live records from a representative plant used when work-centre data is unavailable.

What the station status means

In DNA's current implementation, a work centre marked Down takes precedence; an inactive work centre appears Offline. Otherwise, an active order can produce Setup, Starved or Running according to the operation status and component shortage information. A work centre without an assigned active order appears Idle. The station's primary job is selected from active orders assigned to the current operation's work centre; additional jobs form its queue.

These labels summarise ERP records. They do not establish that a physical machine sensor has reported the condition. An Idle label could reflect a lack of recorded work, and a Down label comes from the work-centre status in this implementation. A supervisor should compare the displayed condition with the order, component situation and actual shop-floor evidence before deciding on a response.

Performance indicators need a known basis

Overall equipment effectiveness, or OEE, combines availability, performance and quality. DNA derives these components from confirmation data and routing standards where available. Its availability calculation uses recorded run and setup time against that time plus recorded downtime. Quality relates good quantity to good, scrap and rework quantities. Performance compares standard time earned with actual run time, capped at 100%.

When the necessary inputs are absent, the implementation uses nominal fallback factors. Work-centre utilisation can also use a fallback when no value is provided. A displayed percentage therefore does not, by itself, prove measured productivity. Before using it to evaluate a shift or compare stations, establish which confirmations, standards and recorded time support it. Missing data must not become an unexplained performance conclusion.

Live, representative and partial views

The representative plant illustrates the interface; it is not the company's actual production. In this mode, recording at the terminal produces a representative acknowledgement without creating a real operation confirmation. The implementation also avoids a real confirmation when there is no linked production-order identity.

Live views depend on the records returned for work centres, orders, confirmations, resources and routings. A partial-plant notice identifies datasets that reach the loading limits. Some failed supporting loads can leave information absent. Neither a detailed 3D scene nor the absence of a visible job proves that the complete operational dataset has been loaded.

The operator terminal creates execution evidence

For a live linked order, the terminal submits good, scrap and rework quantities, time and the relevant resource and operation. Scrap, rework and downtime require reasons when entered. Required custom fields also form part of validation. The timer supplies recorded run and labour time in the submitted confirmation; it is not an independent machine measurement.

Backflush, automatic goods receipt and final confirmation are consequential choices. They request effects beyond displaying progress. The live workflow creates a confirmation and requests posting when an identifier is returned. The resulting confirmation status and linked material or receipt records establish what was completed; an acknowledgement alone is not sufficient evidence of every downstream effect.

A layout is a model of the plant

The Plant Designer arranges work centres and linked resources. Saving a real layout updates supported positions, footprints, rotations and appearance in the corresponding masters. Area and zone structure is also part of the save workflow. Individual writes can fail, so a partial result needs review.

New palette elements are session-only drafts until the corresponding work centre exists as a master record. Representative stations are not persisted as live work centres. Moving an icon changes the model; it does not move physical equipment, create production capacity or record output.

A practical response

Suppose Northstar Manufacturing sees an assembly station marked Starved. The useful response is to identify the affected order, verify which component is short and coordinate supply. If a different station is Down, its equipment condition needs investigation. A high displayed OEE does not cancel either issue, particularly when its calculation lacks measured inputs.

The value of the shop-floor view is a shared, understandable production picture. Its decisions are strongest when the visual model, source records and physical evidence agree.