For machine builders who export

Your machine, live in the browser.
Tested, followed and explained in 3D.

Rovik builds web tools to check off I/O tests on the 3D model, follow the machine on any tablet, and put the manual inside the controls. Wherever the machine is.

Mixing skid M-07Commissioning · I/O test Live
Watch, or drag to rotate and tap a sensor yourself.

I/O test

18 of 24

Pick a sensor on the model or in the list.

FAT report

Appears as soon as the last test is recorded.

  1. 01Once

    Model and I/O list go in

    Your CAD model and I/O list go in once, during the pilot. Every sensor gets its place on the model and its range.

  2. 02Manual

    Technician taps the sensor

    On the tablet, on the model. No drawing, no searching the list: you tap what's in front of you.

  3. 03Manual

    Pass or deviation, one tap

    The value comes live from the PLC and is already checked against its range. The technician confirms. A deviation stays on the model as a punch item.

  4. 04Automatic

    FAT report is ready

    As soon as the last test is recorded: what passed, what's open, who did it and when. Nothing to retype afterwards.

This is a staged impression with a made-up machine. In reality this is your own CAD model, with the real I/O list and values from the PLC.

Who it's for

Machine builders with their own controls, a service department and customers far away

You design your own controls, your machines cross borders, and your service team travels after them. Commissioning takes days and gets documented afterwards. That's what this tool is for.

The FAT report is a day of Excel afterwards.

During the test the values live on scraps of paper, in an I/O list and in someone's head. The report comes later, and is never quite right.

Service flies out for something a screen could have shown.

The customer calls with a fault. What's actually wrong only becomes clear on site — after a day of travel.

The manual sits in a binder. The alarm is on the screen.

The operator sees a code, hunts for the right chapter and the right part. Or just calls.

What it does

01

Commission on the model

Tap a sensor, see the live value and record the test. No searching drawings and I/O lists. The FAT report is ready the moment the last test is checked off.

02

The same machine for everyone

Operator, technician and office see the same current status. No installation, on any tablet. Service can look in without travelling.

03

The manual inside the controls

An alarm opens the right instruction and points to the part in 3D. That fits the digital documentation the EU Machinery Regulation allows from 20 January 2027.

20 January 2027

That's when the EU Machinery Regulation applies, and it allows digital documentation. If the manual lives inside the controls by then, it's where it gets read: at the alarm, at the part.

How it integrates

Three interfaces, and nothing else

No platform to move into, no cloud your data goes to. The tool runs on your server and talks to what's already there.

1

CAD

Your own model, usually as STEP. It's converted into something a browser can handle; detail you don't need on a tablet is stripped so it stays fast.

2

Controls

Live values from the PLC over OPC UA, the standard nearly every modern controller supports. Other connections by arrangement.

3

Your systems

Report and punch items as PDF and as data (CSV, JSON). A connection to SAP, Ultimo, Maximo or your own ERP is a separate step, inside your network.

The offer

Fixed-price pilot.

One machine, your own CAD model, working in the browser. At the end you have something to show internally, and only then do you decide what's next.

What you get

  • ·Your machine in 3D, working in the browser on your server
  • ·I/O test with ranges, punch items and FAT report
  • ·Report as PDF and as data
  • ·Source code and documentation

What we need from you

  • ·The CAD model of the machine
  • ·The I/O list, with a range per sensor
  • ·Access to the PLC, or a test setup

Why this is low risk

  • ✓Open web technology, no game engine or plug-ins.
  • ✓Runs on your own server.
  • ✓Source code and documentation become yours.
  • ✓What you see in the demo above is the same technology as in the pilot.

Where it goes from there

The pilot is step one. After that there are three roads, and you choose only after the pilot.

  1. 01Pilot

    One machine

    Fixed price, your model, working in the browser. The proof to show internally.

  2. 02Per machine type

    Every machine that leaves the factory

    Model and I/O mapping are reused for every machine of that type. Commissioning becomes a repeatable routine instead of a project.

  3. 03At the end customer

    Service and manual on board

    The tool keeps running at the customer. Service looks in from the office, the alarm opens the instruction, punch items stay tracked. With a maintenance agreement.

What you probably want to know

Does this work with our PLC? +

Over OPC UA, the standard nearly every modern controller supports. Which PLC and which connection you have is the first thing we look at in the call.

Which CAD format do you need? +

The model you already have, usually STEP. It's converted into something the browser can handle, and detail you don't need on a tablet is stripped so it stays fast.

What happens with a test that fails? +

The technician records it as a deviation. It stays on the model as a punch item until it's retested, and appears in the FAT report with reason, time and who saw it.

Can this connect to SAP or our maintenance system? +

Report and punch items come out as PDF and as data, so any system can read them. A real connection to SAP, Ultimo, Maximo or your own ERP is a separate step after the pilot, inside your network.

Does this run in the cloud? +

No. On your own server, inside your own network. Nothing leaves unless you want it to — for instance to let service look in.

Does anything need installing on the tablets? +

No. A browser on a tablet, laptop or panel PC is enough.

What if Rovik isn't around tomorrow? +

Source code and documentation are yours, in open web technology. Any web developer can carry on with it.

What does the pilot cost? +

That depends on the job: the machine, the model and what needs connecting. After the first call you get a fixed price, and it stays fixed.

What else Rovik builds

Operator interfaces for industrial machines, in the browser

The pilot above is one application. The craft behind it is the human-machine interface: what the operator sees and touches. Rovik builds those for all kinds of machines, with whatever the machine has on board.

Controls on tablet or panel

An interface that runs in the browser, so no installation on any screen at the machine or in the office.

The machine in 3D

Your own CAD model as the interface: see what moves, what's stopped and where the alarm is.

Lidar and sensor data live

Readings from lidar and other sensors straight in the interface, not in a separate tool.

Connected to the PLC

Read and write live values from the controller that's already there.

Different machine, different question? Book a 20-minute video call and we'll see if it fits.

About Rovik

Rovik builds human-machine interfaces for industrial machines and commissioning software, in the browser. Based in the Netherlands, working for machine builders who deliver worldwide. Behind Rovik is Elmer Bakker, a web developer for over 18 years, with work on commissioning software for industrial installations and on HMIs with 3D animation for machine builders.

We don't name clients on the site. In the call we're happy to tell you what we built for whom.