Real-Time Stamping Press Monitoring

Every connected press reports its state, stroke count, rate and stop events as it runs. One board shows the whole floor: which presses are running, which are in setup, which are stopped and which are under maintenance. Each machine carries its work order, product, target, progress, actual rate against scheduled rate and the tool in use. Maintenance activity appears on the same board as production, because a press held for a die change is unavailable in exactly the way a breakdown is.

Book a walkthrough
Update
As the press runs
Per machine
State, strokes, rate, target, tool, work order
Floor view
Running, alarm, downtime, scheduled, setup, maintenance, idle
Access
Browser, no install, tablet and phone
Scoping
Users see only the assets they are mapped to

In the product

Three presses in three different states. Maintenance sits on the same board as production.

  • MC004Running
    SNX-45 Ton
    WO-SFG0151-08
    Contact plate
    16,394 / 28,00059%
    Rate84.2 / 90.0 SPM
    ToolTL0051
  • MC001Setup pending
    SNX-63 Ton
    WO-SFG0117-09
    Valve guide
    0 / 5,0000%
    Rate0.0 / 70.0 SPM
    ToolTL0130
  • MC010NP activity
    BSTA-25 Ton
    MNT-MC010-09-02
    Machine maintenance
    TypeCorrective
    Raised bySupervisor
    StatusIn progress

What it does

Whole floor at a glance
State counters across every connected press, refreshed continuously.
Per machine detail
Work order, product, target, progress, strokes, rate against target, tool.
Maintenance on the same board
Non production activity is shown beside production, not in a separate system.
Operator terminal
A machine side screen with counters, run chart, state timeline and guided actions.
Asset scoped access
Each user sees the presses they are mapped to and nothing else.

How it works

  1. Connect the press

    Run status and production count arrive as wired I/O through the PLC and gateway.

  2. Attach the order

    A run order binds press, tool, product and operator, so counts have context.

  3. Watch it build

    The board and the operator terminal update as strokes accumulate.

Who this is for

  • A supervisor who currently walks the floor to learn machine status.
  • A plant head who wants the same picture from the office as from the shop.
  • A shop where stop reasons are reconstructed from memory the next morning.

Questions

How current is the data?
It updates as the press runs. Counts are read at the crank rather than entered by hand.
Does it work on a tablet?
Yes. The console and the operator terminal are browser based with no installation.
Can operators see other people's machines?
Only if they are mapped to them. Access is per asset as well as per module.
What counts as a stop?
Any state configured to record downtime. The operator names the reason at the machine.

Related

See it on your own presses.

We instrument one press, run it for a month, and show you the shift record against what you thought was happening.

Book a walkthrough