Calibration runs on data and ships as software. We integrate with the SCADA, control systems and historians your plant already runs — capture combustion data at rates that actually resolve the physics — and deploy every change with the discipline of a firmware release.
We don't replace your control system — we work inside it. A calibration engagement starts read-only: we connect to the plant's existing SCADA, DCS or unit controller, map the tags that matter (exhaust and firing temperatures, fuel flow, stack O₂, load, ambient conditions, vibration and combustion dynamics where instrumented), and establish a trustworthy baseline before anything is touched. When changes ship, they go in through the platform's own configuration and parameter mechanisms — under the site's management-of-change process, with the protective functions untouched. Trips, overspeed, flame-out and surge protection are never in scope for modification; we calibrate inside the safety envelope, not around it.
Most plant historians store one-minute averages — fine for production reporting, useless for combustion work. Knock margin lives in individual cycles; combustor dynamics live in hundreds of hertz; a Wobbe excursion does its damage in seconds. Our first technical deliverable is usually a data-quality upgrade: identifying which signals need high-rate capture, deploying supplementary logging where the native system can't provide it, and time-aligning fuel, air, ambient and emissions data onto one clock so cause and effect can actually be separated. We work from your historian exports where they're sufficient, and we bring our own acquisition where they're not.
A calibration is a versioned artifact: parameter sets, curve tables, control-logic patches. We treat it exactly like production firmware:
Integration experience spans the control, SCADA and data ecosystems below. The list is representative, not exhaustive — if your system can log data and accept a parameter file, we can almost certainly work with it.
| Layer | Platforms |
|---|---|
| Turbine & plant control | GE Mark VIe / Mark VI, Woodward MicroNet & 505 series, Siemens SPPA-T3000, Emerson Ovation, ABB 800xA, Honeywell Experion, Allen-Bradley / Rockwell ControlLogix |
| Engine controls & ECUs | Woodward easYgen & E6, ComAp InteliGen / InteliSys, HEINZMANN, MOTORTECH, Altronic, Cat ADEM, Cummins PowerCommand, GE Jenbacher DIA.NE, Waukesha ESM |
| SCADA / HMI | Ignition (Inductive Automation), AVEVA System Platform / InTouch (Wonderware), GE iFIX & CIMPLICITY, Siemens WinCC, AVEVA/Schneider GeoSCADA (ClearSCADA), VTScada |
| Historians & data stores | AVEVA PI System (OSIsoft), Canary Labs, InfluxDB, TimescaleDB, SQL-based plant historians, structured CSV / export pipelines |
| Protocols | OPC UA / OPC DA, Modbus TCP & RTU, DNP3, MQTT (Sparkplug B), CAN / J1939, HART, serial ASCII |
| Instrumentation | Zirconia O₂ probes, CEMS (NOx/CO), gas chromatographs (Emerson, ABB), Wobbe analyzers, Coriolis & ultrasonic fuel metering, thermocouple / RTD arrays, combustion dynamics monitoring |
Read-only first, least privilege always. We work within your OT network policies — site-escorted, VPN'd or fully offline via data export. NDAs are standard, no plant data leaves your control without written agreement, and nothing we deploy phones home.
Platform, historian, instrumentation — send the list and we'll tell you exactly how we'd connect, capture and deploy at your site.
Schedule an Introductory Call