CARIMOTechnologies

CAPMAC / CARI-Loops

CARI-Loops · Control loop and valve health

Know which loops and valves need you first.

CARI-Loops reads the trend history your control system already keeps and gives your team one list, ranked for review: frozen measurements, suspected valve sticking, valve play, outputs at their limits, swinging loops and loops left in manual. Assessed findings come with a likely cause, a next check and how sure.

  • Ranked for review, with the next check
  • How sure, for assessed findings
  • No DCS connection, no internet
  • Read-only
Worked example: one unit of our own test plant. Three hours of routine records; four of the loops with findings
LIC-301Instrument frozenLIC-301 trend: instrument frozen
FIC-102Sticking valve suspectedFIC-102 trend: sticking valve suspected
FIC-104Output saturatedFIC-104 trend: output saturated
FIC-105Left in manualFIC-105 trend: left in manual
MeasurementSet pointController outputLogged in manual
The film

Watch the film

3 min, with captions. Sound on for the narration.

CARI-Loops film
A control valve, motor and pressure gauge on a process pipe rack
One unit, one report

The right work first.

A plant has hundreds of control loops. CARI-Loops turns the trend records you already keep into a practical review list, with the next check beside each finding. Add your own cost rates for a second view of the recorded error, and use plant criticality to set the work order.

Works from CSV or Excel trend exports of your DCS, PLC, SCADA or historian. No DCS connection, no OT network or firewall change, no new sensors, no shutdown: trend review is read-only.

Tested on our own test plants built to industry practice.

CARI-Loops · result
CARI-Loops result: loops counted by result, then what to look at first, with what to do and how sure
One ranked listthe whole unit, ranked for review
Next checka plain next step on every finding
How surehigh, medium or low for assessed findings
31 sto check the twelve-loop example unit on one PC
A hand on a control panel of lit buttons
Step by step

Every file graded. Your tags confirmed.

Exports are graded the moment they are read, with the export setting that fixes a poor one. Loops are found from your own tag names, and your engineer confirms them before anything is judged.

CARI-Loops · is the data good enough?
Data check: two files good to use, one stored only on change, with the export setting that fixes it
CARI-Loops · check the tags for each loop
Tag table: each loop with its type and its measurement, set point and output columns
Three control valves in a row on a process line
What it finds

Every finding, and its next check.

Finding names are the app's own. A second finding on the same loop is printed under “Also seen”. The checks help your team confirm the cause and choose the work.

Finding on the reportWhat it meansWhat your team checks
Instrument frozenA measurement that stayed unchanged for a long stretchThe transmitter and its wiring, against a local gauge.
Sticking valve suspectedA swing in the pattern a sticking valve makesA small-step test agreed with operations, then the valve inspection.
Valve dead bandValve position that waits before it follows small changes of output (where position is logged)Linkage, positioner and actuator for friction or play; positioner calibration.
Output saturatedA controller output held at its limit, with no further output movement available in that directionOperating limits, valve or pump response and duty, before any retune.
Swings with othersLoops that swing at the same rhythm as othersReviewed as one job: a common cause looked for first.
Loop swingingA loop that swings up and down in a regular rhythmThe loop in manual, then valve response, before a retune; upstream if the swing continues.
Left in manualA loop logged in manual for much of the recordWhy it was in manual, and whether to return it to automatic.
Export againA loop whose export cannot show enoughHow to export it again: rate, compression, missing signal or a fresh record.
No problem foundThe checks this export supports found no problem in the recordNo action; keep it in next month's check.

For a loop whose own settings are the cause, CARI-Tune gives new settings to try.

Worked example

One unit, three hours, twelve loops.

The example that comes with the app: one unit of our own test plant, exported as two ordinary trend files with vendor-style tags, one row every 2 seconds.

LIC-301  Instrument frozen

level, %

LIC-301, level, %

FIC-102  Sticking valve suspected

flow, m³/h

FIC-102, flow, m³/h

FIC-104  Output saturated

controller output, %

FIC-104, controller output, %

FIC-105  Left in manual

controller output, %

FIC-105, controller output, %

FIC-103  Valve dead band

controller output and valve position, %

FIC-103, controller output and valve position, %

TIC-201  Loop swinging

temperature, °C

TIC-201, temperature, °C

TIC-203  Loop swinging

temperature, °C

TIC-203, temperature, °C

PIC-401  Export again

pressure, bar

PIC-401, pressure, bar
MeasurementSet pointController outputValve position

The unit, ranked for review.

#LoopFindingLikely causeNext checkHow sure
1LIC-301
level
Instrument frozenMost likely a stuck or failed transmitter, or a broken signal wire. The controller was acting on a frozen number.Check the transmitter and its wiring. Compare with a local gauge.High
2FIC-102
flow
Sticking valve suspectedValve friction or linkage play may explain the pattern. A small-step test checks the valve response.Agree a small-step test with operations. Check valve position, or the flow or pressure response, for delayed movement and jumps; use the result to plan the valve inspection.Medium
3FIC-103
flow
Valve dead bandThe position record shows delayed valve response. Friction, mechanical play or positioner behaviour may explain it.Check the linkage, positioner and actuator for friction or play; check positioner calibration and correct it as needed.High
4FIC-104
flow
Output saturatedDemand, operating limits, or a valve or pump not delivering the required response, may be holding the output at its limit.Check operating limits, valve or pump response and duty before deciding whether to retune.High
5TIC-201
temperature
Loop swingingController settings, valve sticking or an upstream disturbance; a manual observation and a valve check help separate them.With operations, observe the loop in manual. If the swing stops, check valve response before retuning (CARI-Tune gives the settings); if it continues, investigate upstream.Low
6TIC-203
temperature
Loop swingingController settings, valve sticking or an upstream disturbance; a manual observation and a valve check help separate them.With operations, observe the loop in manual. If the swing stops, check valve response before retuning (CARI-Tune gives the settings); if it continues, investigate upstream.Low
7FIC-105
flow
Left in manualThe loop ran in manual for much of the record. Ask the operators whether this was intended and what prompted it.Confirm why it was in manual. Resolve any fault, then agree with operations whether to return it to automatic.High
8PIC-401
pressure
Export againThe historian stored too few or too coarse values (compression, rounding, gaps), or a needed signal is missing.Follow the named export correction: use a suitable recording rate and uncompressed history, add a missing signal, or record a fresh stretch where detail has been lost.—
9–12FIC-106, TIC-202, FIC-107, FIC-101No problem foundThe checks this export supports found no problem.No action. Keep it in next month's check.Medium

The frozen measurement comes first, then the suspected sticking valve, valve dead band, the output at its limit, swinging loops and the loop in manual; loops with no problem found close the list. On a swinging loop the record shows the swing; its cause is settled by the on-site checks. Your team sets the work order with plant criticality in mind.

Trend charts on an operator screen
The report

Every finding shows its own record.

Each loop with a finding gets its own section: likely cause, what to do, and its trends over the record. Print it or save it as PDF; take the findings as CSV.

CARI-Loops · report, one loop
Report section for one loop: finding, likely cause, what to do, measurement and output trends

Next month, loop by loop

LoopEarlierLaterChange
FIC-102Sticking valve suspectedSticking valve suspectedstill there
PIC-401Export againLoop swingingjudged now: problem found
FIC-101No problem foundNo problem foundstill fine

Ranked by error at your cost rates

#LoopFindingError over the record
1TIC-201Loop swingingRs 2,706
2TIC-203Loop swingingRs 714
3FIC-102Sticking valve suspectedRs 468

Values assigned to the error over the three-hour record, using example rates per loop: Rs 200 per m³/h away from set point per hour for flow, and Rs 1,500 per °C away from set point per hour for temperature.

A technician checking a control valve with a handheld meter
Valve health

Check the valve. Then plan its repair.

The app plans a small-step test for your engineer to check a suspect valve, about half an hour in the example. Your own team runs it under your plant procedures; the app reads the exported response and sizes dead band as a share of the output signal.

Sticking valve

dead band 2.5 % of output

Manual test on a sticking valve: the valve position waits at each change of direction

Sound valve

followed small moves

Manual test on a sound valve: the valve position follows every small move
Controller output, stepped by handValve position

Another valve, followed to your limit

stroke tests every two months, dead band as % of travel

Dead band from stroke tests rising towards a limit of 1 % of travel, with the range of months to reach it

About 22 months to the limit, with a range of 15 to 40 months, from the example stroke-test history: a basis for planning the repair into a shutdown, updated as each new test arrives.

A pressure vessel with its relief valve in a process plant
Working with your team

On your own PC. With your own team.

Where it runs

On your own PC, opened in a web browser. It listens on that PC alone and needs no internet. It only reads exported files: it writes nothing to your control system and sends no data elsewhere.

Your system, your tags

Works from CSV or Excel exports of your DCS, PLC, SCADA or historian, one file or several, so it needs no direct connection. The app lists the loops it sees from your tag names, and you confirm.

Set up with you

CARIMO sets up the app with your team, maps the first unit's tags, goes through the first report with your engineers and agrees the monthly routine.

CARI-Loops finds the trouble. CARI-Tune is CARI-Loops plus tuning.

Send one export. Get one ranked list.

Start with a guided first unit, on a call on your own PC or from an export you send. Then CARI-Loops runs on your own PC.

Request a demo