SensorDataFabrics
All solutions

Enterprise operators · mixed budgets · many plants

One condition-monitoring platform, right-sized for every site in your fleet

Scale hardware and analytics per site budget, keep data portable across SCADA and MES systems, and add cloud visibility only where it earns its keep.

1platform, right-sized from CX9240 to C6030

Built for the reliability programme owner across sites

Model your fleet rolloutDownload the spec sheet →
ChallengeHow it worksWhy it winsDeploymentProof

The challenge

Built for the reliability programme owner across sites.

  • Enterprise operators end up with inconsistent monitoring across sites — some over-instrumented, some under-instrumented — because one fixed hardware and software tier does not fit every site's budget.
  • Per-site vendor lock-in makes fleet-wide reporting and tooling fragmented.
  • Mandatory cloud subscriptions turn basic visibility into a recurring cost centre, whether or not the customer needs fleet-level dashboards.

How the system solves it

Only the capabilities that apply to this use case.

One software — right-sized hardware for every site
  1. 01

    Small site

    CX9240 · metrics & alarms

  2. 02

    Mid site

    C6015 / C6025 · + DSP

  3. 03

    Critical plant

    C6030 · + DSP & AI headroom

  4. 04

    Unified export

    OPC UA · MQTT · Modbus · HTTPS

Same HMI · RBAC · updates→Azure fleet view — opt-in
Hardware tiering
CX9240 through C6030 lets each site match compute cost to its actual criticality and budget, while running the same core software.
Mixed intelligence levels
Metrics-only sites and full DSP/AI sites coexist in the same fleet without running different platforms.
Northbound export
OPC UA, Modbus, MQTT and HTTP into the SCADA and MES already in place, rather than forcing a new central system.
Opt-in cloud
The Azure fleet dashboard is optional — sites that do not need multi-site visibility are not paying for or routing data through it.

Why it wins here

Architectural differences, not slogans.

01

Same operating experience at every tier

RBAC, HMI and the update/rollback workflow are consistent across the CX9240–C6030 range, which cuts training and support overhead. Tier-by-tier parity is confirmed during sizing.

02

Data is not hostage to one dashboard

Open export protocols keep the enterprise layer replaceable. We compare protocol support competitor by competitor rather than claiming it as unique.

03

Predictable TCO

One-off hardware cost with no per-asset software subscription; the only recurring item is the optional cloud dashboard.

Deployment path

Variant

Mixed — each site chooses wired or wireless

Hardware tier

CX9240 for small sites, C6015/C6025 mid-tier, C6030 for critical plants

Why

This is a programme-level decision, not a single deployment type: sites pick their variant, while the software, data model and export contract stay identical.

Proof & validation

Reference fleet, costed per site

A reference fleet records the number of sites and assets running on one platform and the cost-per-site across hardware tiers. TCO modelling is available before that, so you can size the rollout without waiting for reference data.

Next step

Model your fleet rolloutDownload the spec sheet

Explore the other use cases

Rotating equipment PdM

Catch bearing failures weeks before they cause downtime

Read use case

Remote & hard-to-wire assets

Monitor equipment kilometers from the control room — without a wiring project

Read use case

Machine protection & interlocks

Trip the machine before damage happens — deterministically, locally

Read use case

Brownfield retrofit

Add condition monitoring without ripping out what's already there

Read use case