Pragmatos Live

Pragmatos Live shows the plant on one screen, as it runs.

Each connected machine, line and plant in its state right now, the stops and their reasons, the alarms and who has them, and the energy where meters exist. Each person gets the screen for their job.

A shift lead walks the long central aisle of a machining hall in the early morning, past lathes, a milling machine, a press and a grinder, with stack lights glowing far away at the end of the hall
Which machines are running right now?
Why did line 2 stop overnight?
Who knows about the red lamp?
Walking the hall to find out what runs. Every morning starts with a walk, a phone call and a guess about the night shift.
A person stands in front of a large wall screen showing a floor plan of the hall below, each machine with one coloured dot for its state; a card lists what the plant overview shows

On the plant overview

  • Running, idle, fault, stopped or offline, per machine
  • Open faults, per line
  • The age of the last reading, on every figure

Each machine where it stands on the floor plan.

The whole hall on one screen. Pragmatos Live shows each connected machine where it stands, in its state, with the age of every reading.
Four people at four screens: an operator at a terminal beside a lathe, a technician with a phone beside a compressor, a shift lead under a wall screen and a manager at a laptop; a card lists the start screen for each role

Start screen by role

  • OperatorAndon board
  • Shift leadLine
  • Plant managerPlant overview
  • MaintenanceMaintenance
  • QualityQuality

Set by your admin, per role.

The right screen for each person. The operator sees the andon board, the shift lead the line, the plant manager the plant overview.

The morning question, answered before the walk

What ran overnight, what stopped and why, and who knows about it. Pragmatos Live answers on one screen, for the plant manager (Werkleiter), the shift lead (Schichtleiter), the operator (Maschinenbediener) and maintenance (Instandhaltung) alike.

18screens to run the plant and keep it running
15 sabout, to log a stop reason at the machine
28languages, each operator picks one
5shift patterns, plus your own dates

What Pragmatos Live is: the live plant, and the record every module reads

Live

Pragmatos Live is the live picture of your plant. Each connected machine, line and plant sits in one structure, from the company down to plant, area, line, station and machine, with meters at any level. Every figure says what it is: its value, its time window, its shift calendar and its basis, in the terms of ISO 22400-2. Pulse, Orbis, Flow and Decisions all read from it, and each person opens on the screen for their job.

  1. ConnectLoomThe machines you have, read where they stand.
  2. SeeLiveThe live plant on one screen.
  3. AnalyzePulseCondition and trends, machine by machine.
  4. DecideOrbisProposes; a person decides.
  5. ActFlowApproved decisions become work.
  6. ProveDecisionsEvery decision on the record.

On Monday: the question "what ran overnight" is answered on a screen, before anyone walks the hall.

Plant and machine: each connected machine where it stands, in its state

Live

The plant overview and the floor plan

The plant overview (Werksübersicht) counts machines by state and lists the open faults. The floor plan puts each machine where it stands on the floor, in the colour of its state: running, idle, fault, stopped or offline. The line screen adds the takt strip, the open faults and how the line runs this shift.

On Monday: the shift lead knows which machines stand before the first coffee, and where they stand on the floor.

Pragmatos floor plan of a hall: turning, milling, the main aisle, the store and saw shop, the measuring room, compressed air and power distribution
What it shows: the floor plan (Aufstellungsplan), each area of the hall where it stands.

One machine, over time

The machine screen shows state, speed, load, part count and alarms, with the age of the last reading on every figure. Open it from the floor plan and the figures for that one machine sit on one screen. A figure that has not updated says so, with its age.

On Monday: maintenance opens the machine screen before walking to the fault, and knows how old each figure is.

Pragmatos machine screen: the machine state over time, spindle load and power
What it shows: one machine over time, its state, spindle load and power.

Every screen in 28 languages; each person picks their own.

Andon, shift board and terminal: stops with their reasons, in the same hour

Live

The andon board (Andon-Tafel) shows every machine in large format: running, idle, fault, stopped or offline. At the machine, the operator's terminal logs what the machine cannot know: the order, the part count, the scrap and the reason for a stop.

The stops screen (Stillstände) sorts stops by reason and values them at the machine-hour rate (Maschinenstundensatz), taken from your ERP or entered by a person and stated on every cost figure. A stop counts where it hits the result: at the bottleneck, or where an order is lost.

A large screen hangs above a production line with rows of coloured bars, one per machine; workers in safety glasses stand below and look up at it
What it shows: the andon board above the line, one bar per machine in its state, read by the whole shift.
OrdersStart and stop an order, log the part count and the scrap.
Stop reasonsSix to eight buttons per machine class, set by the shift lead, about 15 seconds per stop.
Release and acknowledgeAsk for first-article release and acknowledge an alarm, each recorded with machine, shift and time.
CorrectionsA correction keeps the original entry beside it.
Pragmatos andon wall: a grid of machine tiles, most green, a few amber and grey
What it shows: the andon wall, every machine as a tile in its state.
Pragmatos shift board: machines in rows with their state for the shift
What it shows: the shift board, machine by machine.

Large type and large touch targets. Every state carries colour, a symbol and text together, and no alarm is sound only.

On Monday: the andon meeting starts from stops already logged with their reasons and valued, not from memory.

Alarms: to the right person, again and again

Live

You set the rules: who gets which alarm, by type, severity and event, to a named person, everyone or a role, and the threshold per machine. The alarm repeats every minute for critical, every 15 minutes for major and every hour for the rest, and the acknowledgement is recorded with the time.

In the appA bell on every screen, with the alarms meant for you.
On the phoneA push message for major and critical alarms, to named people, everyone or a role.
On TelegramAlarms to a Telegram chat, switched on per installation.
Again and againRepeats every minute for critical, every 15 minutes for major and every hour for the rest.
Into your systemsE-mail and REST, so an alarm reaches the tools you already use.

A figure older than 15 minutes says so, and a machine with no data for three times its usual interval is flagged. Silence is shown as silence, not as a machine that runs.

Not a safety function. A Pragmatos Live alarm reports. It is not a safety function in the sense of ISO 13849 or IEC 61508; the machine's own safety circuit protects people and equipment.

On Monday: the compressor alarm at 06:15 reaches the maintenance role on their phones, and repeats every 15 minutes.

Energy where meters exist: kWh first, cost where you set a tariff

Live

The meter screen lists every meter, the level it sits on and its last reading. Consumption adds up by plant, hall and line, in kWh first, with cost only where a tariff is entered.

The words are the ones your energy team already uses: energy performance indicators (EnPI) against the energy baseline (EnB). Pragmatos Live supports your ISO 50001 energy management.

A cutaway drawing of a factory: the power supply branches through two electrical cabinets to each machine, with a small green disc where a line is measured
What it shows: meters where they sit, on the supply, on a cabinet or on one machine. Pragmatos Live reads each at its level.
The 15-minute blockThe running block against the limit you set below the year's peak, with the history of what was decided.
Base loadWhat the plant draws when no shift is running, line by line.
kWh per partEnergy per part where a meter and a part count exist for the same machine.
Reactive energyReactive energy and the live load curve beside the active load.

On Monday: the energy manager (Energiebeauftragter) reads last night's base load line by line, in kWh, and has a question for the right shift lead.

Several plants, one structure, a screen for each job

Live

Each plant (Werk) keeps its own areas, lines and shift calendar. The plants screen sets them side by side, on the same basis. Several companies run in one system and stay apart, each with its own plants and settings.

Pragmatos energy screen: load per plant for three plants
What it shows: load per plant (Last je Werk) for three plants.

On Monday: the plant manager compares Werk 1 and Werk 2 on the same shift calendar, without asking for two spreadsheets.

Three factory buildings in three towns, linked by thin lines to one laptop where a person compares them
What it shows: three plants on one screen, each in its own state.
A start screen per roleThe operator opens on the andon board, the shift lead on the line, the plant manager on the plant overview, maintenance and quality on their own screens.
Ask your plantAsk your plant a question in words and get the figure back, with its source. Nothing leaves the plant unless you switch a channel on.
Your screens, your rulesYour admin ticks which screens each group sees, with save, undo and a change log. A screen outside a role is refused.

A morning with Pragmatos Live: 05:52 to 06:45

Live
A morning meeting at the edge of a machining hall: five people in front of a standing touch screen with a timeline of coloured bars, one person pointing at a red piece
What it shows: the andon meeting, run from the timeline and the stops already logged.

A machining plant with two lines and a utilities room, on a Monday after the night shift.

  1. Press 3 shows grey on the line screen.Shift lead

    The tile reads "No new reading, last one 23 min ago". The figure says it is old, so nobody counts press 3 as running.

  2. Two stops on line 2 overnight, both with a reason.Andon meeting

    47 minutes of "material missing" and 12 minutes of "tool change", each logged at the terminal when it happened. The 47 minutes hit the bottleneck, so the stops screen counts them against the result, valued at the machine-hour rate from your ERP. The rate is shown beside the figure.

  3. A stop reason in about 15 seconds.Operator

    The lathe on cell 4 stops for a measurement. The operator taps one of the eight buttons the shift lead set for turning machines, and the stop appears on the stops screen in the same hour.

  4. Compressor 2 raises a major alarm.Maintenance

    The maintenance role gets a push message on their phones. It repeats every 15 minutes, and when someone acknowledges it, the acknowledgement is recorded with the time.

  5. Werk 1 and Werk 2 side by side.Werkleiter

    The plant overview shows both plants on the same shift calendar and the same basis, so the night shift in one plant compares with the night shift in the other.

  6. Overnight base load, line by line.Energy manager

    310 kWh between 22:00 and 06:00 with no shift running, most of it on line 1. The question for the shift lead is written before the first coffee is finished.

Who it's for: what changes for each role

Live

Pick a role to see what Pragmatos Live gives that person. The plant manager's is open to start.

  • Opens on the plant overview: every line in its state, with the open faults, before the first meeting.
  • Compares plants and shifts on the same calendar and the same basis, because every figure states its window and calendar.
  • Sees what a stop costs where it hits the result, at a machine-hour rate whose source is shown.

  • Opens on the line screen: the takt strip, the open faults and how the line is running this shift.
  • Runs the andon meeting from stops that are already logged with their reasons.
  • Sets the six to eight stop-reason buttons for each machine class, and the same list feeds the stops screen.

  • Starts and stops orders, logs part count and scrap, and gives a stop reason in about 15 seconds.
  • Asks for first-article release and acknowledges alarms at the terminal.
  • Reads large type and large touch targets, with colour, symbol and text together, in one of 28 languages.

  • Gets the alarms meant for maintenance, in the app and as a push message for major and critical ones.
  • Opens the machine screen before walking to the fault: state, speed, load, part count and alarms, with the age of the last reading.
  • Knows when a figure is old, because every figure shows the age of its last reading.

  • Opens on the quality screen and sees first-article release requests as they come in.
  • Reads scrap where it is logged, by machine and shift, with corrections that keep the original entry.

  • Watches the current 15-minute block against the limit you set below the year's peak.
  • Reads off-shift base load, consumption by plant, hall and line, reactive energy and kWh per part where meters exist.
  • Works in ISO 50001 terms: energy performance indicators against the energy baseline. Pragmatos Live supports your ISO 50001 energy management.

  • Sees the stops by machine and reason, logged at the terminal against the order.
  • Plans against the shift calendar the figures use: five patterns from off to continuous, plus your own dates.

  • Runs Pragmatos Live where you choose: on premise in your plant, in your own cloud, or both, with single sign-on and invitation links valid for three days.
  • Keeps the plant network as it is: Pragmatos Live reads, and nothing is written to a machine control.
  • Gets notifications by e-mail and over REST into the systems you already run.

  • Sees stops valued at the machine-hour rate, with the rate and its source on every cost figure.
  • Keeps several companies apart in one system, each with its own plants and its own settings.

  • Has a read-only view of what is recorded and shown, in Pragmatos.
  • Shift and crew figures appear only for groups of five or more by default; smaller groups are not shown, and named people are never ranked.
  • Linking a figure to a person stays off until a works agreement (Betriebsvereinbarung) reference is entered.

What Pragmatos Live does not do

Reads onlyPragmatos reads, people act. Nothing is written to a machine control.
Not a safety functionAlarms report. The machine's own safety circuit protects.
Where you decideOn premise in your plant, in your own cloud, or both: you choose. In a hybrid set-up, the edge computer in each plant reads the machines, buffers through a network drop and sends on only the data you choose. Ask your plant answers from inside your installation.
Works-council settingShift and crew figures for groups of five or more by default, no ranking of named people, person linkage off by default.

On Monday: IT and the works council (Betriebsrat) read one page on what Pragmatos Live touches: it reads from the machines and writes nothing back.

Platform and trust: where it runs and who sees what

Show us your floor. We show you the morning screen for it.

The one-page sheet

Pragmatos on one page, to pass to your colleagues.

Download the sheet (PDF)

Readiness self-assessment

Where your plant stands before the first machine is connected.

Start the self-assessment

OEE reality check: the calculator

See how far a reported OEE can sit from one that counts micro-stops and speed loss.

Open the calculator

We set it up with you.

Book a walkthrough

Before and after Pragmatos Live

  • LoomConnect: the machines you have, old and new.
  • PulseAnalyze: condition and trends, machine by machine.
  • OrbisDecide: Orbis proposes, a person decides.
  • FlowAct: approved decisions become work.
  • DecisionsProve: every decision on the record.
  • NexusThe machine and the cell in 3D.
  • PragmatosThe whole platform, from connect to prove.

Get new articles by email

One shop-floor problem at a time.

How we think about it

The arguments behind Pragmatos Live, one problem at a time.

Questions plant managers and works councils ask

A shift lead walks the central aisle of a machining hall in the early morning
No. Pragmatos reads, and people act. Pragmatos Live shows what the machines report and what people log at the terminal. Nothing is written back to a machine control, so a setpoint, a program or a cycle stays as it is.
No. A Pragmatos Live alarm reports a state and routes it to the right people. It is not a safety function in the sense of ISO 13849 or IEC 61508. The machine's own safety circuit protects people and equipment.
Every figure shows the age of its last reading. A figure older than 15 minutes says so, for example "No new reading, last one 23 min ago", and a machine with no data for three times its usual interval is flagged. An old value is never shown as a live one.
From the machine-hour rate (Maschinenstundensatz), taken from your ERP or entered by a person. The rate and where it came from are stated on every cost figure. A stop is counted where it hits the result: at the bottleneck, or where an order is lost.
No. The energy screens show what your meters measure, at whatever level they sit: plant, hall, line or machine. Energy per part appears where a meter and a part count exist for the same machine. Figures are in kWh first, with cost only where you have entered a tariff.
28. Every screen comes in 28 languages, and each person picks their own, so two people on the same line can read the same screen in their own language.
On premise in your plant, in your own cloud, or both: you choose. In a hybrid set-up, the edge computer in each plant reads the machines, buffers through a network drop and sends on only the data you choose.
Each company has a works-council setting. Shift and crew figures appear only for groups of five or more by default; smaller groups are not shown, named people are never ranked, and linking a figure to a person stays off until a works agreement (Betriebsvereinbarung) reference is entered. The works council gets a read-only view.