Home / What we build on / PLCs & SCADA

Your SCADA sees everything.
You still get surprised.

PLCs, SCADA, historians — the data is already there. The analysis isn’t.

SCADA was built to operate the process, not to analyze equipment health. A fixed alarm fires when the limit is crossed — which means the problem has already arrived. Meanwhile the historian quietly logs years of data nobody reads, and the equipment that actually takes the plant down — the compressor, the genset, the pumps — often never made it onto the HMI at all. Veritas Data designs and builds the analysis layer your control system doesn’t have: we tap it read-only, learn each tag’s normal, and warn you days before your alarm would — with the likely cause and the next step attached.

OPC-UA subscriptions, strictly read-onlyModbus & historian fallback pathsControl logic never touched — not a setpoint, not a tag
If you run a control system, you already know the pattern: the alarm was technically correct — and completely useless, because it arrived with the failure instead of ahead of it.
  • Alarms that fire too late. A fixed threshold says nothing until it’s crossed. By then the bearing is gone, the exchanger is fouled, the tank is hot — the alarm announces the problem, it doesn’t prevent it.
  • Alarm floods. Hundreds of nuisance alarms a shift, and operators tune them out — there’s an entire standard (ISA-18.2) because of it. The one alarm that matters is buried in the noise.
  • The historian nobody reads. Years of process data, logged at real expense, analyzed never. The early-warning signal is usually sitting in there right now.
  • Orphan equipment. The production line is on SCADA. The air compressor, the standby genset, the cooling pumps — the things that quietly stop the plant — usually aren’t.
Why it matters

Data rich. Insight poor.

You’ve already paid for the instrumentation, the wiring, the tags, the historian licenses. The gap between what that system records and what anyone learns from it is where the surprise outage lives. The drift that ends in a 2 a.m. callout is almost always visible in the data for days or weeks first — visible, logged, and unwatched. Closing that gap doesn’t take new instruments. It takes an analyst that never stops reading them.

Descriptive → Predictive → Prescriptive

What we build on top of your control system.

The same analytics spine behind every Veritas system — reading the data your PLCs and SCADA already produce.

01 · Descriptive

What’s happening

A read-only window on the tags you already trust — plus the orphan equipment your HMI never covered.

  • OPC-UA subscriptions, read-only
  • Historian import
  • Modbus fallback paths
  • One view, every system & site
02 · Predictive

What’s coming

Learned normal per tag, drift flagged while your alarm limits are still quiet — ranked, not flooded.

  • Learned baseline per tag
  • Drift caught before alarm limits
  • Ranked early warnings
  • No nuisance floods
03 · Prescriptive

What to do

The likely cause and the next step, routed to the right person — with the trend history to justify the work order.

  • Likely-cause analysis
  • Ranked next step
  • Routed to the right role
  • Evidence for the fix
Interactive example

Your alarm limit, our head start.

One heat-exchanger loop, with sample data — not a live system. The dashed line is your existing SCADA alarm limit. Drive the scenarios and watch when our early warning fires versus when your alarm would. That gap — measured in days — is what we build.

Scenario:
HX-3 loop · Process cooling SAMPLE DATA
--:--:--
Heat-exchanger outlet temp · 30-day trend + projection
142.3°F
SCADA alarm limit · 160°F today → projected your alarm fires here
No alarm-limit crossing projected at the current trend.
OKWATCHACT
Recommended action

97health score
Example dashboard · sample data for illustration · your build reads your tags and your alarm limits
How it connects

Onto the control system you already trust.

  • OPC-UA, strictly read-only

    We subscribe to the tags your PLCs and SCADA already publish. Never a write, never a setpoint change, never a touch on the logic or the interlocks.

  • Meets your network where it is

    Where OPC-UA isn’t exposed, we read Modbus TCP or import from the historian instead — and we deploy to respect your segmentation and change-management, not around it.

  • One dashboard, everything

    Process tags and orphan equipment — compressors, gensets, pumps — side by side in a single learned-baseline view, across every site.

It never touches your control logic.

Read-only subscriptions, parallel analysis, recommendations only. Your PLC programs, interlocks, and safety systems stay exactly as your integrator left them — that’s the answer that gets IT, OT, and the plant manager to the same yes.

// read-only · no writes · logic & interlocks untouched
Who it's built for

Anywhere the data outruns the attention.

Manufacturing & process

Plants where SCADA runs the line but nobody has time to read the historian — and the surprise failure is always in equipment the HMI barely shows.

Utilities & water

Lift stations, treatment plants, distributed assets — alarm floods at 3 a.m. and a truck roll to find out it was nothing. Or wasn’t.

Controls & integration teams

Integrators who want to offer their customers the analysis layer — without taking on another control system, or another liability.

You’ve already paid for the data. Start using it.

Tell us what runs your process — we’ll design the analysis layer around it, read-only.

Book a consultation →

Horacio De La Cruz · 305.295.2729 · hdelacruz@veritas-data.io