Continuous service

Enhanced PI Monitoring

We watch the health of your whole PI System, so problems are found early, and not by the people who need the data.

Schematic of PI System health signals with an alert

Most PI problems are found by the people who need the data.

An interface stops, a buffer fills, a disk runs low. Nobody notices until a report is wrong or a trend goes flat.

Do-it-yourself monitoring templates help, but someone still has to maintain them and watch them.

  • Health of every component

    PI Data Archive (archives, backups, event queue, licence), AF, Asset Analytics, Notifications, buffering, every interface and adapter, PI to CONNECT, PI Vision, PI Web API, and the Windows servers and disks.

  • Incidents and alerts

    Alerts by text message and email to our team and to the contacts you choose. Incidents are tracked in Jira.

  • A status page for your site

    One page in TTech OneStop: current status and open problems, in plain words.

  • Early warnings

    Disks, archive space and certificates running out are flagged before they cause an outage.

  • Expert review

    Our PI specialists review the findings and recommend improvements: reliability, security, capacity, compression and storage.

  1. 01

    Install the collector

    A small TTech tool on your PI server gathers health data. It adds its own health points and never changes your existing points.

  2. 02

    Send it through AVEVA CONNECT

    Health data leaves through your PI to CONNECT agent, outbound only. No inbound firewall port, no VPN.

  3. 03

    Watch and alert

    Rules open incidents, send alerts, and close them when the system recovers.

  4. 04

    Review and recommend

    Regular reviews turn findings into concrete improvements.

  • Fewer surprises

    Problems are seen when they start, not when a report is wrong.

  • Less effort for your team

    No monitoring templates to build or maintain.

  • A healthier system over time

    Recommendations improve reliability, security and storage, step by step.

  • Your PI System feeds production reports, control-room displays or other systems.
  • Your team has no time to watch interfaces, buffers and backups.
  • You have just gone live and want close attention while things settle.
Does it change our PI System?

It adds its own health points and a small collector service. It never changes or deletes your existing points. The health points use your point licence; the count is shown before anything is created.

What do we need on our side?

AVEVA CONNECT with the PI to CONNECT agent, and a read-only CONNECT access for our team. Nothing reaches your network from outside.

How does it fit with Hypercare and the helpdesk?

After a go-live, Hypercare can start with monitoring in place. Add the PI Helpdesk so the same team fixes what monitoring finds.

Start a conversation.

Tell us about your PI System and what you need. We will suggest a practical next step.