Skip to content
Proxus 2.0.0 Proxus 2.0: the largest release in Proxus history Release notes
Try free Book a demo

Platform · Dashboards

Views the plant uses, reports the business trusts.

Operational dashboards and scheduled reports built on the governed namespace, so what the line sees and what management receives come from the same numbers.

Book a demo Try the live demo

In the product

A live plant view: OEE per line and the state of every machine.

Built with the dashboard designer on the same governed data as everything else: availability, performance and quality per line, and each machine's state and throughput. The plant is simulated.

Live plant dashboard with OEE gauges per line and machine states with throughput.
Live plant dashboard built on the same governed dataSimulated plant data
Built on
The modelled namespace and the telemetry historian
For
Line operators, plant management and group reporting
Delivery
On screen, scheduled, or exported
Access
Role-based, down to the namespace path

The line and the boardroom read the same numbers.

Dashboards, alarms and scheduled reports are built on the same modelled signals and the same history.

The same signals, from history to insight Equipment sends data through an edge gateway to Historian, then to Dashboards & reports. Controllers S7 / CIP / MELSEC Machines & robots FOCAS / MTConnect Meters & SCADA Modbus / OPC UA Modelled signals 02 / EDGE Proxus Edge Collect / evaluate / buffer 03 / PLATFORM Historian Telemetry / logs / retention Dashboards &reports Inside Proxus Databases & cloud Optional destinations Business systems MES / ERP / QMS 01 / PLANT FLOOR04 / CONSUMERS The same signals, from history to insight Read from bottom to top. Field equipment is at the bottom and data travels upward. Equipment sends data through an edge gateway to Historian, then to Dashboards & reports. 01 Plant floor PLCs / CNCs / robots 02 Proxus Edge Collect / evaluate /buffer 03 Historian Telemetry / logs /retention 04 Dashboards &reports Built into the platform

What it solves

What teams run into without it.

  • The screen and the report disagree

    Two tools, two calculations, and a meeting spent reconciling instead of deciding.

  • Reporting by manual export

    Someone spends the first morning of every month pulling numbers into a spreadsheet.

  • Dashboards nobody can change

    A view built by a contractor two years ago that no one in the plant can adjust.

What you get

Built in, not bolted on.

  • Operational dashboards

    Line status, cycle performance, energy and quality views built from modelled signals.

  • Scheduled reports

    Recurring reports produced from the same data and delivered on a schedule you control, or an AI Assistant shift summary or weekly health report by e-mail.

  • Alarms with context

    What triggered, on which asset, with the values that caused it, not just a colour change.

  • Role-based views

    People see the sites, areas and signals their role covers, and nothing else.

  • Export and share

    Send a view or a result set to the people who need it without handing out database access.

  • Audit trail

    Changes to dashboards and reports are recorded, so a view that shifted can be explained.

What this enables

What the capabilities add up to, in practice.

  • Give the floor and the boardroom the same numbers
  • Replace the monthly manual export with a scheduled report
  • Let plant staff adjust a view without a contractor
  • Scope what each role sees down to the namespace path

Proven in production

On screens the floor and the boardroom both use.

All deployments

Questions

What teams ask before the first call.

Ask something else
Do we need a separate BI tool?
Not for operational views. Dashboards, alarms and scheduled reports are part of the platform. If you already run Power BI or similar for business reporting, Proxus writes to the database it reads from.
Can plant staff build their own views?
Yes. Dashboards are built in the product against modelled signals, so a supervisor can adjust a view without a contractor and without touching the collection layer.
How are reports delivered?
On screen, on a schedule, or exported. Scheduled delivery is off by default and enabled deliberately per schedule, so a configuration change cannot start sending mail unexpectedly.
Can different sites see different data?
Yes, through role and namespace-path permissions. A site sees its own lines; a group role sees across sites.
Do dashboards and reports use the same numbers?
Yes, both read the modelled namespace and the same historian, which removes the usual argument about whose figure is correct.

Continue

Two numbers set your price: the gateways you run and the data rate they carry. See pricing

Next step

Point it at one of your lines.

The fastest way to judge a data layer is to watch it read your own equipment. Bring one machine and one destination system, and we will build the path in front of you.

Book a demo Talk to an engineer
  1. 01

    Scoping call

    Equipment, protocols, sites and the systems the data has to reach.

  2. 02

    Technical walkthrough

    A working demo against a scenario that resembles your plant, not a generic tour.

  3. 03

    Pilot plan

    A defined first line or site, with the deployment and security questions answered up front.

  4. 04

    Roll-out

    The same templates bring the next lines and sites online.