Clear control authority · local override that always works · unattended-site ready
Control
Plants add remote operation for good reasons. Sites get consolidated into fewer control rooms, units end up in locations nobody wants to stand next to, and stations become unattended. What follows is a control hierarchy that grew rather than got designed: a local panel, a unit HMI, a plant-wide control, and a SCADA master, each capable of issuing commands, with the arbitration between them living partly in logic, partly in a selector switch, and partly in a procedure taped to the cabinet door.
Innova Technologies engineers that hierarchy explicitly. Control authority is held by exactly one station at a time, indicated identically at every station, and transferred through a defined request-and-accept sequence rather than by whoever moves a switch first. Setpoints track on the inactive stations so transfer is bumpless. Local control retains the authority it needs for maintenance and emergency action regardless of what the remote station is doing, and the machine’s protective functions answer to neither.
The Problem
Loss of communications to a remote site is a well-understood failure that most systems handle. The harder failure is ambiguity: a maintenance technician working at the local panel while an operator two hundred kilometers away still holds an active setpoint, a unit that accepts a remote start while a local lockout was assumed to be in force, or a transfer that completes on one station’s display but not the other’s. These are not exotic scenarios. They are the predictable result of a control hierarchy that was extended one project at a time.
The second problem is what happens on communication loss, which is a design decision that frequently gets omitted. Should the unit hold its last setpoint indefinitely, ramp to a defined safe state, shut down, or continue running autonomously on local control? All four are correct in some context and wrong in others, and the answer depends on the process, the site staffing, and how long a realistic outage lasts. A system that simply holds the last value because nobody specified otherwise will eventually hold it through a condition change that mattered.
The third pressure is that remote operation and remote access are not the same thing, and conflating them creates exposure. Operational remote control across a plant network is a different risk profile from vendor diagnostic access across an external boundary. Innova Technologies engineers both, with the segmentation, controlled paths, and logging that separate them properly, which is also where the balance of plant network architecture scope connects.
Capabilities
A defined hierarchy establishes which station may command the machine, with authority held by one station at a time and transfer executed through request and accept rather than unilateral capture. Setpoint tracking on inactive stations makes every transfer bumpless, and current authority is displayed identically at the local panel, the unit HMI, and the remote station so nobody has to infer it.
Fail-safe behavior on loss of communications is specified explicitly per unit and per site: hold, ramp to a defined state, shut down, or continue autonomously on local control, with timeouts and re-establishment logic to match. The behavior is documented in the control narrative and exercised at factory acceptance test rather than discovered during an outage.
The local panel retains the authority required for maintenance, commissioning, and emergency action independent of remote status, including local lockout that is positively indicated remotely and cannot be overridden from the control room. Local operation is designed as a complete capability rather than as a degraded fallback, because that is how it is used during outages.
For genuinely unattended sites, local control is engineered to start, regulate, protect, and shut down without instruction, with the remote station providing supervision, dispatch, and exception handling. Multi-station coordination over satellite or cellular links is proven in Innova's multi-plant work, where the platform scales from a single turbine to coordinated multi-station control.
Unit-level and plant-level interfaces present the same data model, the same graphics standard, and the same alarm set, so an operator moving between them is not translating. Interface redundancy is engineered so that loss of one station, one server, or one network path does not remove the ability to see and control the machine.
Diagnostic and support access is engineered separately from operational remote control, with network segmentation, defined and logged access paths, and firewall rules. Innova Technologies, formerly Petrotech, has long provided remote troubleshooting and diagnostic support alongside 24-hour telephone support, and the architecture that makes that safe is engineered as part of the scope rather than assumed.
Integration with plant-wide control system and SCADA uses standard protocols including Modbus TCP, OPC UA, DNP3, EtherNet/IP, PROFIBUS, and FOUNDATION Fieldbus, depending on the existing infrastructure. The unit control system remains an independent controller capable of full automatic operation without the supervisory system, which is what makes remote operation a convenience rather than a dependency.
Alarms are routed to where someone is actually present, with escalation paths for unattended hours, acknowledgment tracked across stations so an alarm answered remotely is visibly answered locally, and first-out capture preserved regardless of which station was in control when the event occurred.
Why Innova Technologies
Protection answers to neither station
Communication loss behavior is a decision, not a default
Open architecture, no vendor lock-in
Technical Resources
FAQ
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
