SCADA

SCADA screens

The problem The SCADA screens are stuck in the control room.

intellifix · SCADA SCADA inventory
Data it needs
The SCADA screen export
Areas of the operation
Process and utilities
Integrates with
IPM · APC · vRover
How it starts
14-day free trial
What it does

The supervisory screen, outside the control room.

The plant's SCADA screens, imported into Intellifix next to the data from every module.

The SCADA screen export
  • Each screen in two views: faithful and Intellifix
  • Live equipment status, always saying where the values came from
  • Equipment inventory and where each tag is used
Module screens

The interface, screen by screen.

Captures from the running application, with demonstration data.

intellifix · SCADA SCADA inventory
SCADA inventory
intellifix · SCADA SCADA inventory
SCADA inventory
How it works

From the data that comes in to the decision that goes out.

  1. 1

    The screens are imported

    The export from the supervisory system is checked first: equipment recognized, colors not read and which screen each file replaces. Nothing is saved until someone confirms.

  2. 2

    The plant sends the tags

    A collector inside the plant reads the tags the screens use and sends out only the latest value. The history stays in the plant, and nothing is written to the control network.

  3. 3

    The screen shows only what is real

    Faithful or Intellifix view, same instant and same positions. A reading that went stale is hidden instead of looking current, and simulated values are always labelled.

  4. 4

    The selection becomes a question

    Mark equipment on the drawing to see its readings, ask Felix what is going on, or open its history, fetched from the plant.

Requirements

What it takes to go live.

Data it needs

The SCADA screen export

This is the hard requirement. Without it, the capability has nothing to read.

What the plant needs

  • The screens exported from the supervisory system, in a format Intellifix has an importer for.
  • Read access to the plant's OPC UA server, for the collector that runs inside the plant.
  • The image files the screens use, since the export names them but does not carry them.
  • Who can import and replace screens, since an import changes what every operator reads.
Where it acts

Where it acts in the plant.

Results delivered

What becomes possible.

  • The supervisory screen leaves the control room and sits next to the rest of the operation.
  • Faithful and Intellifix views of the same instant, with every piece of equipment where the engineer put it.
  • A missing reading shows as unknown, never as zero or as a closed valve.
  • Finding where a tag is used takes one search, not opening every screen by hand.
Examples of use

On the floor, it looks like this.

A tag about to be changed

Before anyone touches it, the inventory lists every screen and every piece of equipment that reads it.

A temperature that keeps rising

The operator marks the instruments on the drawing and asks Felix, who reads the same state the screen is showing.

The link to the plant goes down

The screen says there is no plant data and hides the values, instead of quietly switching to simulated ones.

Benefits by role

What each side of the operation gains.

Operation

The shift sees the supervisory screen outside the control room, and knows whether the values came from the plant.

Automation and process

Every import comes with a report before it is saved, and the inventory shows where a tag is read before anyone changes it.

Management

What the control room sees reaches the rest of the operation, with no path opened into the control network.

Integrations

It does not work alone.

Every capability reads from and feeds the others. What this one exchanges inside the operation:

Cyber

Plant network security

The collector inside the plant that reads the screen tags also runs the network collection, and both only send data out of the plant.

Open capability
RMS

Best recipe

The screens never write to the machine. A recipe that has to reach it goes through Best recipe, as a queued request the plant itself picks up.

Open capability
Trends

Process history

The history of a selected instrument is fetched from the plant's own historian, the same local store Process history can read.

Open capability
SCADA

Want to see this on your own data?

Bring the export of one supervisory screen. In the demo we import it and show it in both views.