Valve & Loop Tuning
Tune
Stiction, hunting, poor turndown and oscillation rarely trip an alarm. They show up instead as instability everywhere downstream — and as faults the diagnostic engine can already see but cannot yet tell you how to fix. Tune closes that gap.
Why this is next
Control-loop instability is already a root cause in the causal map — level control hunting, valve stiction, poor turndown. Several of the fifty-four indicators are oscillation detectors. The engine can see the problem today; it simply cannot yet recommend the fix.
The intent is to work from routine operating data the plant already logs. Asking a producing unit to sit through step tests is the reason most loop-tuning programmes get scheduled and then never happen.
Oscillation propagates through coupled loops, so half a dozen controllers can look bad because of one sticking valve. The value is in ranking which one is the source.
Before-and-after variability is measured from the historian, so an improvement is demonstrated rather than asserted.
Planned scope
This is a plan, not a product. Nothing in this list is shipping today.
What it builds on
Every figure on this page is countable in the delivered system. If you want to see where a number comes from, ask us and we will show you the record it is read from.
Where it stands today
Where it applies
The platform is focused on acid gas removal — gas sweetening and post-combustion carbon capture — because that is where the model is calibrated and where the fault library is real. The method underneath is not amine-specific: a physics reference model, residuals against expected-healthy, fuzzy diagnosis over graded indicators, and costed consequences. Extending it to another unit means new datasheets and a new calibration, not a new platform.
The rest of the platform
The platform runs on a real amine train with thirteen days of one-minute history behind it. Nothing on these pages is a mock-up.
Open the platform