Trends

Process history

The problem The process data is recorded, but finding the right tag and comparing it takes someone who knows the historian.

intellifix · Trends Filling history
Data it needs
Plant historian (ADX or local)
Areas of the operation
Process, packaging and utilities
Integrates with
IPM · APC · QCP
How it starts
14-day free trial
What it does

Every process tag, one click away.

Pick the area or line and its tags come out of the plant historian, ready to compare in the same chart.

Plant historian (ADX or local)
  • Tags found by area, line and machine
  • Several series in one chart, with the right summary for each
  • Collection health: which tags are late or stopped
Module screens

The interface, screen by screen.

Captures from the running application, with demonstration data.

intellifix · Trends Filling history
Filling history
intellifix · Trends Process history
Process history
How it works

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

  1. 1

    The naming is read

    The plant's tag naming convention says which code means which line, machine and measurement. The system suggests it from the real tags; you correct what is wrong.

  2. 2

    You choose what to look at

    Area, line or machine, the time window and the tags. The query is built by the system, never typed by hand.

  3. 3

    The chart compares

    Each series with its unit and range, summarized as average, minimum, maximum or produced per interval, depending on what the signal measures.

  4. 4

    The analysis stays

    Save the view for the site or just for you, mark on the chart what happened, and check whether the data is still arriving.

Requirements

What it takes to go live.

Data it needs

Plant historian (ADX or local)

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

What the plant needs

  • A historian with the process tags: Azure Data Explorer or the local one.
  • Tag names that carry the line or machine code.
  • Optional: the instrument map from the PLC exports, for unit, description and range.
  • Lines, areas and machines registered in Intellifix.
Where it acts

Where it acts in the plant.

Results delivered

What becomes possible.

  • Anyone on the team finds the tag by the line, not by the historian's code.
  • Process and packaging side by side, in the same time window.
  • A flat curve stops being ambiguous: collection health says whether the process is stable or the collector stopped.
  • The analyses that matter are saved and reopened by the whole site.
Examples of use

On the floor, it looks like this.

A pressure peak hidden by the average

Switching the summary to maximum shows the peak that the average smoothed out, in the same window.

The filler start-up, compared

The start-up of the filler is saved as an analysis and reopened at the next one, with the same tags.

A curve that went flat

Before blaming the process, collection health shows the tag stopped publishing.

Benefits by role

What each side of the operation gains.

Operation

The shift checks how the line behaved without asking engineering for an export.

Quality and process

The deviation is investigated on the real series, with unit and range, next to what was happening around it.

Management

The history the plant already pays to keep becomes something people actually use.

Integrations

It does not work alone.

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

IPM

Monitor the process

Process models are trained on the same historian, and the model's tags come from it.

Open capability
APC

Stabilize the process

The control loop reads the history of its tags from the same source.

Open capability
QCP

Quality and deviations

Control charts read the measurements stored in the historian.

Open capability
Trends

Want to see this on your own data?

Bring the name of one line and its historian. In the demo we find its tags and put process and packaging in the same chart.