Sequence of events to the millisecond · first-out capture · compliance-grade records
Control
Most plant historians are configured for process trending: one-second or slower scan rates, compression enabled, and a timestamp applied when the value arrived at the historian rather than when it occurred at the device. That is an entirely reasonable configuration for watching a temperature drift over a shift. It is useless for reconstructing a trip, because everything interesting happened inside a single scan and arrived carrying the same timestamp.
Innova Technologies engineers the record layer for both duties. Process data is historized for trending and reporting with sensible compression. Digital events are captured separately as a sequence of events with time stamping at the source, resolved finely enough to establish order rather than coincidence, and synchronized across controllers to a common time reference. First-out logic captures which protective input actually initiated the trip, before the cascade of consequences arrives and obscures it.
The Problem
The typical post-trip investigation starts by pulling trends and discovering three problems at once. The scan rate was too slow to establish sequence. Compression discarded the transient. And the timestamps came from different clocks, so the vibration data and the process data disagree about what happened first by more than the event itself lasted. The investigation then proceeds on the operator’s recollection and the first-out annunciator window, if one was fitted and if anyone photographed it before it was reset.
The regulatory version of the same problem is worse, because it arrives on a schedule. Emissions records, runtime and fuel accounting, and, for facilities inside the bulk electric system, evidence of configuration and access control are all requests for historical data at a defined quality. A record layer designed only for operator trending will not produce them without manual reconstruction, and manual reconstruction is exactly what auditors are trained to distrust.
The third problem is durability. Historians deployed with the control system frequently outlive the vendor’s support for that version, and plants discover at migration time that ten years of history is locked in a proprietary format nobody can read without a license. Innova Technologies builds on open architecture with standard interfaces and documented data models, so the record survives the platform it was written on.
Capabilities
Digital events are time stamped where they occur rather than where they arrive, at a resolution sufficient to establish order within a trip cascade, with controllers synchronized to a common time reference. The result is a sequence you can defend, rather than a list of things that all appear to have happened in the same second.
Automated reports covering emissions data, runtime and starts, fuel accounting, and exception logging are generated on schedule and archived with the data that produced them.
First-out logic latches the initiating protective input on every trip, separately from the consequential alarms that follow it. The trip record captures the initiator, the full cascade in order, and the process state at the moment of initiation, so the investigation starts from evidence rather than from reconstruction.
Data is exposed to plant historians, asset management, reliability, and business systems through standard interfaces including OPC UA and equivalent protocols, rather than through a proprietary connector. Where a corporate historian already exists, the control system feeds it rather than competing with it, with the local record retained for the resolution the corporate system will not carry. Over the years, Innova has integrated with most historians in the market.
Continuous process data is historized with per-point scan rate and compression configured to the duty, so slow-moving temperatures do not consume the storage that fast loops require, and fast loops are not compressed into uselessness. Operators get live and historical trending through the same interface they use to run the plant, with comparison against previous starts, previous runs, and commissioning baselines.
Remote access for diagnostics and support is engineered with segmentation, controlled access paths, and logging, so support capability does not become an exposure. Innova has long provided remote troubleshooting and diagnostic support alongside 24-hour telephone support, and the network architecture, segmentation, and firewall rules that make that safe are part of Innova's balance of plant scope.
High-resolution circular buffers hold recent data on selected fast points continuously and freeze on trigger, capturing the transient at a resolution that would be impractical to historize permanently. This is what lets an engineer replay a governor response, a valve stroke, or a surge event afterward at the resolution the event actually required.
Retention policies are set per data class rather than globally, so sequence-of-events and trip records are kept to the period your regulator or your insurer requires while high-rate process data ages out. Archives are written in documented formats with the data model delivered as part of project documentation, which is what makes the next platform migration a project rather than a loss.
Why Innova Technologies
Innova Technologies, formerly Petrotech, brings 50+ years of turbomachinery control experience and has provided data logging, real-time trending, and remote diagnostic support as part of its control scope throughout. The reason this matters is accountability. When we write the protection logic and the record layer, we are the ones who have to reconstruct the event afterward, which is a strong incentive to specify the record properly the first time.
Full-function factory acceptance testing
Open architecture, no vendor lock-in
Security engineered with the access, not after it
Technical Resources
FAQ
You probably do not need a second historian, and we will not sell you one. What plant historians typically do not carry is high-resolution sequence-of-events data with source time stamping, because storing every point at that rate across the whole plant is impractical. The usual answer is a local record at the resolution trips require, feeding your corporate historian with the process data at the rate it is designed for. Two data classes, one architecture.
Independent control for every turbine class.
Anti-surge, loadshare, performance, and capacity control.
Featured
Don’t see your industry?
If your equipment runs and your downtime costs more than the controls do, let’s talk
Single-source
A MESSAGE FROM JOHN KAZOUR, CEO
To our customers and partners,
For more than 50 years, our team has helped customers keep critical operations running. We built our reputation as Petrotech by taking responsibility for control systems on important rotating machinery.
As more industries came to us with similar challenges across power generation, compression, and hydro applications, our engineering team kept finding ways to solve them. Eventually, the business outgrew the Petrotech name.
We are entering our next chapter as Innova Technologies. The new name reflects the full scope of our work as a rotating machinery control systems specialist. We engineer controls around the machine, deliver complete projects from design through commissioning, and provide support that stays with the problem until it is solved.
Our name is changing, but the people, engineering experience, and commitment behind the work continue. Our responsibility to active projects and installed systems carries forward under the Innova Technologies name. Your current contacts remain the right place to start, and we will communicate directly if an administrative record requires an update.
We appreciate the trust you have placed in us over the decades, and we look forward to continuing that work as Innova Technologies.
CEO, Innova Technologies
