Request a demo

We connect the machines, the MES and the ERP, and build what is missing.

From PLC signals to the ERP, VZIAM designs, builds and integrates the systems production depends on. Most of that work runs on VZIAM MES, the manufacturing execution system we develop and maintain ourselves.

Request a demoBook a call
Shop floorMachines and PLCs

Read directly, over a protocol VZIAM MES speaks.

OPC UAMQTTHTTP
On the lineGateway

Node-RED or a DAS box, for Modbus, S7 and proprietary controllers.

ExecutionVZIAM MES

On your network, as Docker.

  • Terminals and andon
  • Stops, OEE and quality
  • Lots and order records
PlanningERP

Orders down, results back at close.

RESTJSONCSV
Built for the plantCustom software

What no product does, on the same foundations.

Each gap is between two systems, and closing it is integration work.

Not another licence. The machine, the order and the ERP each hold part of the answer, and the work is joining them where the facts are made.

A loss with no cause attached

A stop, a slow cycle, a reject. Without the machine, the order and the reason attached to each, the end-of-shift figure says something was lost, not where.

A genealogy rebuilt from paper

When a material lot is in question, the links from it to every finished lot should already exist, not be reconstructed from batch sheets while the customer waits.

Three files, one story

Production, quality and maintenance each hold part of it in their own file. Decisions wait while somebody reconciles them.

What we build, layer by layer.

Four layers from the controller to the report, each with its own page, and software for what no product covers. Where a plant already runs something that works, we integrate with it rather than replace it.

  • Machine data acquisition

    Connections to PLCs over OPC UA and MQTT, with a gateway for Modbus and S7. No manual entry in the path.

  • Execution & MES

    Operator terminals and execution logic for what a machine cannot report: downtime reasons, quality declarations, checks, forms and consumption.

  • ERP integration

    Work orders, articles and bills of materials pulled from SAP, Sage or Microsoft Dynamics; good quantities, rejects and cycle times posted back when each order closes.

  • Analytics & reporting

    OEE to AFNOR NF E60-182, loss Pareto and shift reports, calculated from PLC signals and published where your teams already look.

  • Custom software

    Plant-specific screens, rules and exchanges, built on the acquisition, terminals, displays and admin portal VZIAM MES already has.

Three engagements, described by what changed.

Each is described by what changed in kind rather than by how much, with its sector linked. Client names withheld under NDA.

  • Automotive

    Tier-1 automotive supplier

    Before
    Downtime logged by hand, with reasons rebuilt from shift notes.
    After
    Direct PLC capture, site by site; downtime reasons categorised at source.
  • Food Processing

    Food processing plant

    Before
    Audit preparation meant a document hunt across the plant.
    After
    Batch traceability and quality declarations digitised end to end; an audit is a query against the record.
  • Plastics

    Plastics manufacturer

    Before
    OEE reconciled from spreadsheets once a month.
    After
    Injection presses connected over OPC UA and Modbus; OEE published to the ERP daily.

Assess, pilot, build, run: one line before the rest.

Every project runs in these four steps, and the pilot comes before any commitment to a rollout.

  1. 01

    Assess

    We walk the floor, map the machines and the data that already exists, and agree what “done” means before anything is built.

  2. 02

    Pilot

    One line, one machine, real signals, in weeks. You check your own data before you commit to a rollout.

  3. 03

    Build

    Delivered in increments against the agreed scope, on your network, with your team in the loop.

  4. 04

    Run

    Support, monitoring and changes after go-live. What we built stays ours to answer for.

Frequently asked questions.

Describe what is on your floor, and ask the engineers where a project would start.

Book a call

Usually from VZIAM MES, extended to fit the plant. Where a plant already runs something that works, we integrate with it rather than replace it.

Plan the change before it reaches the line.

Request a demo and an engineer looks at how your production runs today, shows how the software would fit around it, and where a pilot on one line would start.

Request a demoBook a call
How the demo works

  1. 01Pick a time

    Choose a slot in the calendar, and note what you make and what reads your machines today.

  2. 02Screen shared with an engineer

    A video call with someone who builds the software, in English or French.

  3. 03What would connect

    For each machine, its path: native (OPC UA, MQTT or HTTP push), through a gateway, or nothing to build.