Analyzer and monitoring data analytics is an on-premises application that runs beside a plant’s existing data acquisition system or historian and continuously checks the quality of analyzer and monitoring data. Akan Industrial and Automation installs and configures it, as part of its Industrial AI and Software practice, for process analyzers, emission and effluent monitoring stations and metering data. It reads data over a read-only connection, flags invalid values and drift, and gives engineers the evidence to decide what to do next.
What problem does it solve?
An analyzer can keep reporting a number long after the number has stopped being reliable. A frozen signal, a blocked sample line or a slow calibration drift may only be noticed at the next validation, or when a laboratory result disagrees. Until then, operators work with the value and reports are built on it.
The application checks each configured measurement as new data is read and shows which values failed a check and which analyzers are degrading.
What does the application do?
| Function | What it checks or shows |
|---|---|
| Validity checks | Flat-line signals, out-of-range values, spikes and gaps in each measurement |
| Drift detection | Control charts (CUSUM and Shewhart) that reveal slow shifts in validation results and in the measurement itself |
| Analyzer performance dashboard | Availability, validation results over time and time since last calibration, per analyzer |
| Early warning | A notice to engineers when a measurement trends towards a limit the operator has set |
| Periodic reports | Data validity and analyzer performance for the plant’s own quality and environmental teams; internal documents, not submissions to an authority |
Every finding shows the data, the rule or the chart that produced it, so an engineer can verify it before acting.
Optional later step: inferential cross-checks
At a later stage, and as a separately scoped step, inferential estimates can be added where enough related process measurements exist. They cross-check an analyzer against measurements such as flow, temperature and pressure. A persistent difference between the estimate and the analyzer is a reason to inspect the analyzer. The estimate is advisory and does not replace the analyzer reading.
Which measurements does it cover?
- Process analyzers – gas chromatographs and liquid analyzers such as TOC and ammonium.
- Emission and effluent monitoring stations – in Türkiye, the stations operators run within continuous emission monitoring (SEÖS) and continuous wastewater monitoring (SAİS).
- Metering data – flow and the associated pressure, temperature and quality measurements of metering skids and custody metering systems.
The application works with analyzers and systems of any make, including equipment Akan did not supply.
How is it installed and connected?
The application runs on a server on your premises, and the data stays on site. It reads from the data acquisition system or historian over a read-only connection. Nothing writes to the PLC or DCS, and no setpoint is changed. Engineers review the findings and decide. The approach is described in Method, Data and Security.
How is the work delivered?
Scope, typical duration and deliverables are stated before work starts.
| Step | Scope | What you receive |
|---|---|---|
| Assess | A paid, fixed-scope Measurement Data Health Check of the site, on exports produced by plant staff | A written report with ranked findings, a data-access map and, if the findings justify one, a pilot proposal |
| Pilot | One unit, stack or discharge point; typically six to twelve weeks; acceptance criteria agreed beforehand | The application running on the pilot scope and an acceptance report against the criteria |
| Deploy | Rollout to further units and measurement points | Configured checks, dashboards and reports for the agreed scope |
| Support | Updates, tuning of rules and limits, new analyzers added | Support within an agreed scope |
The pilot starts after the health check at that site, because the checks and limits are set from the plant’s own data. To discuss a site, contact Akan.
What it does not do
- It does not filter, alter or delay data that is reported to an authority.
- It is not a substitute for accredited laboratory tests, or for the plant’s own calibration and validation procedures.
- Early warning concerns data validity and trends towards limits set by the operator. It is not an alarm, trip or protection function.
- It does not write to the control system or change setpoints.
- It does not promise a regulatory outcome.
Who is it for?
Analyzer and instrument maintenance engineers, quality and laboratory teams, environmental teams and metering engineers. Typical sites: water and wastewater treatment, oil, gas and petrochemical, energy and chemical and mining, cement and metals plants.
