Module M-04 · Dashboards

Your dashboard, built for your machines - not a template with your logo on it.

Mavex builds the portal your customers open every morning: your name, your plant-line-machine hierarchy, your 3D models with the live values pinned on the components, the tiles and views your operators need - and custom code where the standard components don't fit. Then every machine of that model you ship opens with that page.

DashboardLab-LineCell-01 · NR-620 demo data

Mavex portal screenshot: the machine page of a tending robot - a saved 3D view with the live value pinned on each component (motor currents, gripper vacuum, axis speed, base temperature), its metric tiles and the alarms on this machine. Demo data.

White-label means built for you

We write the code. You ship the portal.

Every competitor's white-label is a configuration screen: upload a logo, pick a color, point a domain. Mavex's white-label is an installation built for one machine builder: their machines, their hierarchy, their views - built once, then shipped with every machine of that model.

Standard components where they fit - the metric tiles, Explore, the alarm engine - and custom code where they don't: a view, a calculation, a page your process needs and nobody else's. You describe the machine; we build the dashboard; your customer sees your name.

What your customer sees

Their machines, your brand

  • The portal

    Your name in the header, your domain, your look. Light or dark, 12- or 24-hour, set per user.

  • Their plant, top down

    Machines running, stopped, in maintenance; one card per line; one slot per machine with its render and its state.

  • The machine as they see it on the floor

    Saved views of the 3D model - tending side, gripper side - with the live value pinned on each component: motor current on the motor, vacuum on the gripper, temperature on the base.

  • Every metric, one tile

    Below the views, a tile per metric: value, unit, freshness, a sparkline; on/off signals as a state timeline; the machine state. Click any tile for its chart.

  • The alarms that matter to that machine

    At the bottom of the page, with their live status - firing, cleared, never fired - and their full history one click away.

Mavex portal screenshot: the saved tending-side view of the robot, with motor currents, gripper vacuum, position drift, axis speed and base temperature pinned on the components. Demo data.
Mavex portal screenshot: the saved gripper-side view of the same robot, with TCP speed, gripper vacuum, motor currents, axis speed and controller cabinet temperature pinned on the components. Demo data.

The line page

One slot per machine, whatever the brand

A line is several machines working together, often from different manufacturers. The line page gives each one a slot with its own render and its own state.

The renders are captured from the same 3D models the machine pages use, so the line view and the machine view are never out of step.

Mavex portal screenshot: the machines on a line, one card each - two robot cells and a parts elevator - with the render of the machine, its running state and this shift's availability, parts and cycle time. Demo data.

Build once

Built per machine model, shipped with every serial number

  • The 3D model One or more files per model

    The 3D model of each machine model goes in - one or more files per model.

  • The views Saved cameras

    The views your operator needs get saved - tending side, gripper side, a detail of the gripper.

  • The metrics Pinned overlays

    Each metric gets pinned on the component that produces it, so the value is read where it happens.

  • The pages Slot bindings

    The pages get assembled: which view fills the machine page, which view fills each slot on the line page.

Every machine of that model - at every customer, on every line - now opens with that page. The tenth customer costs you nothing extra, and the portal is ready in days, not months. After hand-over your own team can keep going: new views, new alarms, new machines, from the admin screens.

Mavex portal screenshot: the machine page of a second model, a parts elevator, built the same way - its own 3D model with live values, its metric tiles and its alarms. Demo data.

Two views, three roles

The OEM view and the customer view

  • For you - Admin and Manufacturer

    Every customer, every plant, every line, every machine, and every configuration screen. Add a customer, add a plant, add a machine, upload a model, write an alarm.

  • For them - Customer

    Their own plant and their own machines, separated at the data layer rather than hidden in the interface.

Portal as a sales tool

Show the portal before you ship the machine

Mark a machine as Simulate and it produces demo data - so the portal is a demo in the sales meeting: "this is what you will see every morning once the line runs", on your own 3D model, with your name on it.

It turns connectivity from an aftermarket add-on into part of the machine offer - and into a subscription you can bill at the point of machine sale.

What the field tells your engineers

The dashboard is also your R&D input

Real-world data shows you how your products perform once they leave the factory - which limits are hit, which components run hot, what your customers actually need, often before they have realised it themselves. The next generation of your machines gets shaped around genuine demand.

Measured results

What the branded portal changed in the field

Outcomes measured across Mavex deployments with a plastic extrusion machine manufacturer.

  • 2.3× Faster line startups Shared startup recipes on the dashboard: operators follow the same proven settings on every line, so lines reach their optimal production rate sooner, with far less scrap.
  • +1 New revenue stream for builders The connected service became a subscription billed at the point of machine sale.
  • −58% On-site service visits Live machine metrics answered most first-response calls remotely.

Results based on early customer deployments. Individual outcomes vary by industry, machine type, and operational context.

The full customer story and every figure

Common questions

Questions we hear about the dashboard

Here are the questions we hear most - answered directly, without the sales pitch.

All questions, general and technical

Can we fully white-label the platform?
Yes - completely. Your customers see your logo, your colors and your domain; the Mavex name doesn't appear unless you choose to show it. And because each installation is built for you, white-label goes past branding: pages, views and calculations specific to your machines, in custom code where needed.
What if our dashboard needs something the platform doesn't have?
We build it. The standard components - tiles, Explore, alarms, 3D views - cover most of a machine dashboard; what is specific to your process is written for you and becomes part of your installation.
Do we need a 3D model?
No. A machine without a 3D view shows its metrics as tiles. The 3D view is the layer on top.
Does the portal work on a phone?
Yes. The web app adapts to a PC browser or to a phone screen.
How is it priced?
A monthly fee per connected machine, depending on how many data points you capture. No per-user fees. For OEMs, a reseller model - you set your own price to your customers and keep the margin.

Get in touch

Ready to connect the machines you build?

Tell us about your machines and your customers - we'll show you exactly what Mavex can do for your business.