Pragmatos Flow · Act

Flow turns an approved decision into work that gets done.

Work orders, the shift board, the terminal at the machine and your ERP: the decision reaches the people who carry it out, and the confirmation comes back. People act. Pragmatos never writes to a machine control.

Illustration: a planner seen from behind at a desk covered in paper slips, above a machining hall where a lathe stands with its door open and a technician walks the other way. A card asks who carries out an approved decision, whether the ERP has an order, whether the shift knows and when it is done

Approved. And then?

  • Who carries it out
  • Is there an order in the ERP
  • Does the shift know
  • When is it done

Four phone calls and a sheet of paper

Decided is not done. A tool change approved at nine is still a slip of paper at noon. The shift has not heard, the ERP has no order, and the machine waits.
Illustration: a technician seen from behind at an injection-moulding machine with a tablet terminal beside it, and a shift lead in the distance at a wall screen of coloured bars. A card lists where Flow sends the job: the shift board, the terminal at the machine, the maintenance lead's phone and the planner's capacity view
Flowpeople carry it out

Flow sends it to

  • The shift board: next job on line 2
  • The terminal at the machine
  • The maintenance lead's (Instandhaltung) phone
  • The planner's capacity view

A person does the work

On the board and at the machine. Flow puts the approved job where the work happens: on the shift board, on the terminal and on the phone of the person who can act.
Illustration: a cutaway of a production hall with a press brake joined to an office by a loop of light, with blank document cards travelling along it and one ticked card travelling back. A card lists what Flow does with your ERP: the work order created, the ERP number back on the card, pieces and times confirmed and the decision marked done
Flowpeople carry it out

Your ERP, both ways

  • Work order created
  • ERP number back on the card
  • Pieces and times confirmed
  • Decision marked done

One order per approved decision

Shop floorthe count comes from the machine
Your ERP, both ways. The order goes into your ERP, its number comes back, and the confirmed pieces and times follow from the machine's own count.

What Flow is: the step where a decision becomes work

Flow

Decisions get lost between the approval and the machine: in an email, on a slip of paper, in an ERP order someone types in after lunch. Flow carries each approved decision to the people and the systems that carry it out. It opens the work order in your ERP, puts the job on the shift board and the terminal, sends a message to the person who can act, and brings the confirmation back.

Flow is the Act step in the Pragmatos loop. It follows Orbis, where a person approves a proposal, and it hands the finished work to Decisions, where the whole path stays on the record.

  1. Connect: LoomLoom AI reads your machines, old and new.
  2. See: Pragmatos LiveThe plant on one screen, as it runs.
  3. Analyze: PulsePulse finds what changed.
  4. Decide: OrbisOrbis proposes, a person approves.
  5. Act: FlowFlow turns it into work.
  6. Prove: DecisionsDecisions keeps the record.
5ERP packs, from SAP to a REST or CSV link
2directions: orders in, confirmations back
1work order for each approved decision that needs one
1stated source on every cost figure

The path of one approved decision

  1. Orbis proposes, a person approvesA tool change, with the readings behind it, approved by the maintenance lead (Instandhaltung) on the phone.
  2. Flow opens the order in your ERPOne work order for the approved decision. The ERP's order number comes back to the decision.
  3. The job reaches the floorIt lands on the shift board, on the terminal at the machine and on the phone of the person who does it.
  4. A person does the workThe technician changes the tool and confirms it at the terminal. Nothing touches the machine control.
  5. The confirmation goes backPieces and times return to the ERP from the machine's own count. The decision is marked done in Decisions.

People act. Flow sends work to people and to your ERP. Pragmatos never writes to a machine control, so every job on the floor is done by a person, with the machine's own controls.

Work orders: one for each approved decision that needs one

Flow

An approved decision that needs work opens one order in your ERP: a maintenance order, a tool change, a scrap note. The ERP's order number is written back to the decision, so anyone looking at either one finds the other.

Nobody retypes the decision into the ERP, and nobody has to remember to. When the work is confirmed, the decision is marked done. A rejected proposal opens no order.

What changes on Monday: the maintenance lead approves a job once, on the phone, and it is already an order with a number when the technician picks it up.

Illustration: a technician seen from behind changes a cutting tool on a turning centre with its guard door open, a tool trolley beside him and a small tablet on the machine showing a list with ticks
What it shows: the approved tool change carried out at the machine by a person, with the job on the tablet beside it.
What each kind of approved decision becomes in your ERP
The approved decisionWhat Flow opens in your ERP
Maintenance: a worn tool, a bearing running warmA maintenance order, or a tool change
Availability: the same stop, again and againA maintenance order for the cause
Quality: parts drifting out of toleranceA quality notification, or a scrap note
Energy: a machine drawing power while idleA corrective-action order
A rejected proposalNo order
Pragmatos screen: proposals waiting for approval, each with the evidence it is based on
What it shows: proposals waiting for a person to approve, each with what it is based on.

On the floor: the shift board, the terminal and the capacity view

Flow

Your ERP orders arrive per line and machine, with part number, quantity and target cycle (Vorgabezeit). The shift lead dispatches them on the shift board, the planner balances them on the capacity view, and the operator works them at the tablet terminal next to the machine.

Shift boardWhat runs on each machine, what is next, and every stop with its reason.
Capacity viewLoad per line and machine, so orders move before a line falls behind.
Terminal at the machineStart set-up, start, confirm pieces, book scrap or a stop with its reason.
Travelling card and labelThe travelling card (Laufkarte) and the label print from the order.
Material and lotsMaterial is booked as pieces are confirmed, with lots and genealogy.
Shift calendarFrom your ERP, or kept in Flow: shifts, holidays and scheduled stops.
Pragmatos Flow screen: the shift board, machines with their current order and state, and the reasons for stops
What it shows: the shift board, machine by machine, with the current job and the stops.
Pragmatos Flow screen: work orders dispatched to a machine, each with its order number and state
What it shows: orders dispatched to one machine, each with its number and state.
Pragmatos Flow screen: availability, performance and quality for a shift, and the stops listed by reason
What it shows: stops listed by reason, with the minutes each one cost the shift.

What changes on Monday: the shift starts from a board that already shows what runs where, the operator confirms a count the machine has made, and the next shift reads the stops with their reasons instead of a note.

Messages: one, to the person who can act

Flow

When something needs a person, Flow finds the right one. Flow finds the person responsible for that machine, and if nobody is set, an administrator gets it, so every message reaches someone.

It goes out by email, chat or webhook, and as a push message on Pragmatos Mobile. An alarm that stays on repeats at its set interval: every minute for critical, every 15 minutes for major and every hour for the rest. Quiet hours hold routine messages for the morning, and critical ones always get through.

What changes on Monday: the technician on call gets the message for the stop that needs them, and the night stays quiet for everything that can wait.

Illustration: a person walks down a factory aisle holding a glowing phone, past a surface grinder and a press with an amber stack light, while a second person further down turns towards the press
What it shows: one message from the press with the amber lamp, on the phone of the person who can act.
Repeats by severityAn alarm that stays on repeats every minute for critical, every 15 minutes for major and every hour for the rest.
Quiet hoursRoutine messages wait for the morning. Critical ones always get through.
To the person who can actLooked up from the machine to the line, the plant and the company, with an administrator as the last stop.

Your ERP, both ways: five packs, checked field by field

Flow

Flow is the bridge between your ERP and the plant. Orders, routings, cycle times, maintenance plans and confirmations move in both directions. Your ERP keeps its plans and its costs, and the plant data stays authoritative for what happened on the shop floor.

SAPIDoc and OData, including SAP Business One
proALPHAOrders, operations, confirmations and maintenance plans
Dynamics 365 Business CentralDynamics 365 Finance and Operations on request
OdooOrders, operations, confirmations and maintenance orders
REST or CSVFor any other system, mapped the same way

From your ERP

  • Orders and operations per line and machine, with part number, quantity and target cycle.
  • Maintenance plans from SAP PM or proALPHA, shown beside the machines in Pragmatos Live.
  • The target cycle per part number from the routing, which Pulse compares with the measured cycle.
  • The shift calendar, or Flow keeps its own.
  • Cost rates such as the machine-hour rate.

Back to your ERP

  • Pieces and times per operation, from the machine's own count.
  • Done maintenance work, as a confirmation.
  • One work order for each approved decision that needs one.
  • Nothing at all, if you choose the read-only option.
The mapping screenEach pack is mapped field by field, with a test run and a diff before go-live.
Read-only optionOrders, plans and calendars come in. Nothing goes back until you switch it on.
The Fabric linkFlow reaches your ERP through Fabric, using API users on the ERP side.

What changes on Monday: production confirmations stop being typed in from paper at the end of the shift, and the ERP's figures match what the machines made.

No ERP on the shop floor? Flow runs standalone.

Where the ERP stops at the office door, or where there is none, Flow carries the shop-floor work: production, stock, orders, maintenance and quality, booked by your people in one system that knows the machines.

Orders and dispatchProduction orders, the shift board, the capacity view and the terminal.
StockA stock ledger with lots, FEFO or FIFO picking and two-way batch genealogy.
Maintenance and qualityMaintenance plans and checklists, inspection plans, nonconformance and 8D.
Sales and invoicesSales orders, deliveries, invoices with gapless numbering, payments and dunning.

What changes on Monday: a plant without an ERP on the floor books orders, stock and quality in one place, at the machine.

Finance: every cost figure says where its rate came from

Flow

Cost rates, such as the machine-hour rate (Maschinenstundensatz), come from your ERP or are entered by a person, and every cost figure states which. A stop is valued at that rate and counted where it hits the result: at the bottleneck, or as a lost order.

The journal is designed for GoBD: entries are never overwritten, and every correction is a new, logged entry. Invoices go out as XRechnung or ZUGFeRD, and the DATEV export goes to your tax adviser.

What changes on Monday: the controller reads a stop in money with the source of its rate beside it, and can answer the question "where does that figure come from" without a spreadsheet.

Illustration: a controller seen from behind at a desk by a tall window over a factory roof, sliding a paper into a folder beside a laptop and a desk lamp
What it shows: the controller's (Controlling) side of the same stop: a cost figure with its source, ready for the month-end export.
Journal designed for GoBDEntries are never overwritten. Every correction is a new, logged entry.
XRechnung and ZUGFeRDElectronic invoices go out in the formats your customers ask for.
DATEV exportThe month goes to your tax adviser as a DATEV export.

A morning on line 2: one stop, from alarm to the ERP

Flow

A machining plant with three lines, the early shift, your ERP on the other end. This is what Flow does with one spindle stop.

  1. 06:40The turning centre on line 2 stops on a spindle-load alarm. It is the third stop on that spindle this week. Pulse shows the tool wearing faster over the last shifts.
  2. 06:48Orbis proposes a tool change. The proposal carries the readings behind it and how Orbis arrived there.
  3. 06:52The maintenance lead approves it on the phone. Flow opens 1 maintenance order in your ERP. The ERP's order number comes back to the decision.
  4. 06:53The job reaches the floor. It is on the shift board and on the terminal at the machine, and the technician on shift gets 1 message.
  5. 07:20The technician changes the tool and confirms it at the terminal. Line 2 runs again after 40 minutes. The stop is booked with its reason.
  6. 07:30The planner (Arbeitsvorbereitung) opens the capacity view. Line 2 is 40 minutes behind, so the planner moves 2 orders to line 3. The shift board updates for both lines.
  7. 14:00The shift ends. 120 pieces go back to the ERP against their operations, from the machine's own count. The 40 minutes are valued at line 2's machine-hour rate, with the source of that rate shown. Decisions keeps the record of the whole path.
1maintenance order, opened in the ERP by Flow
1message, to the technician on shift
2orders moved to line 3 by the planner
120pieces confirmed back to the ERP

Who it's for: what changes for each role

Flow

Flow is where the office and the shop floor meet, so it means something different on each side of the door.

Pick your role to see what changes for you. Production planning is open to start.

  • Your ERP orders sit per line and machine, with part number, quantity and target cycle (Vorgabezeit).
  • When a line loses time, the capacity view shows it, and you move orders to another line before the shift runs out.
  • Pulse compares the target cycle from your routing with the measured one, so a routing that is out of date shows up.

  • You start the shift from the shift board: what runs where, what is next, what is stopped and why.
  • An approved maintenance job appears on the board with its order number, so you plan around it instead of hearing about it.
  • Stops carry a reason booked at the machine, so the handover to the next shift is the board, not a note.

  • The tablet terminal shows your next job. You start set-up, start the run, confirm pieces, and book scrap or a stop with its reason.
  • The piece count comes from the machine, so you confirm it instead of counting it.
  • The travelling card (Laufkarte) and the label print from the order, and material is booked as pieces are confirmed.

  • An approved decision arrives as a maintenance order in your ERP, with the readings behind it attached to the decision.
  • Your maintenance plans from SAP PM or proALPHA appear beside the machines, and done work goes back as a confirmation.
  • An alarm reaches the person on call and repeats at its set interval while it stays on; routine messages wait for the morning, critical ones get through.

  • You pick the pack for your ERP and map each field on the mapping screen, with a test run and a diff before go-live.
  • You can start read-only: orders, plans and calendars come in, nothing goes back until you switch it on.
  • The Fabric link uses API users on your ERP side, and everything runs where you choose: on premise in your plant, in your own cloud, or both. Data leaves only through a channel you switch on, such as mobile push.

  • Every cost figure states where its rate came from: your ERP or the person who entered it.
  • Downtime is valued at the machine-hour rate (Maschinenstundensatz) and counted where it hits the result: at the bottleneck, or as a lost order.
  • The journal is designed for GoBD, invoices go out as XRechnung or ZUGFeRD, and the DATEV export goes to your tax adviser.

  • You see which approved decisions are open, which are in progress and which are done, each with its ERP order.
  • A decision made at nine is a job on the floor a minute later, not a slip of paper at noon.
  • Nothing in Flow writes to a machine control. People carry out the work, and the record shows which role did what.

  • Notifications are about machines and processes, never about people.
  • No view ranks named individuals.
  • The record stores the role that approved a decision. Linking it to a named person is switched on only under your Betriebsvereinbarung, and you are told before it takes effect.

  • A part drifting out of tolerance becomes a decision, and once approved, a quality notification in your ERP.
  • Nonconformance and 8D sit on the same order the parts were made on, next to the machine data from that run.
  • A quality hold reaches the shift board, so the next pieces wait for a check instead of shipping.

People decide, people act, the data stays yours

Flow
People actPragmatos never writes to a machine control. A person carries out every job.
People decideOrbis proposes, a person with the right role approves. Designed for the EU AI Act's human-oversight and logging requirements. Whether your use meets the Act is for you and your advisers to assess.
Your data, your installationFlow runs where you choose: on premise in your plant, in your own cloud, or both. Data leaves only through a channel you switch on, such as mobile push. The read-only option keeps your ERP untouched.
Co-determinationMessages are about machines and processes. No view ranks named individuals.

Before and after Flow in the loop

  • Decide: OrbisOrbis proposes with the evidence behind it, and a person with the right role approves.
  • Prove: DecisionsEvery decision on the record: which role proposed it, which role approved it, what was done.

Bring one decision that got stuck between the office and the machine. We walk you through where Flow carries it.

We set it up with you, starting with your ERP's mapping.

Book a walkthrough

The whole loop

Get new articles by email

One shop-floor problem at a time.

Questions planning, IT and finance ask

An alarm from a machine, shown on a phone
No. Flow sends work to people and to your ERP. Pragmatos never writes to a machine control. A person carries out every job, at the machine, with the machine's own controls.
SAP (IDoc and OData, including SAP Business One), proALPHA, Dynamics 365 Business Central; Dynamics 365 Finance and Operations on request, Odoo, and any other system over a generic REST or CSV link. Each pack is a mapped set of orders, operations, confirmations and maintenance orders.
Your ERP keeps its orders, routings, plans and, where it holds them, cost rates. The plant data stays authoritative for what happened on the shop floor: the pieces and the times Flow confirms come from the machine's own count.
API users in your ERP for the Fabric link. Any licence fees on the ERP side are set by your ERP vendor. Before go-live you map each field on the mapping screen, test it and see the difference.
Yes. The read-only option takes orders, plans and calendars from your ERP into Pragmatos and writes nothing back. You switch on write-back when you are ready.
No. Orbis proposes, a person with the right role approves, and Flow carries out what was approved. A rejected proposal creates no order.
No. Flow sends messages about machines and processes, never about people, and no view ranks named individuals. That is a line the works council can check.