One vendor · one platform · one point of accountability

One Plant. One Control Platform. One Point of Accountability.

Innova Technologies brings the balance-of-plant systems across your facility under a single, consistent control platform, common parts, controllers that talk to each other and to one plant HMI/DCS/SCADA and historian, consistent programming and documentation, and integrated cybersecurity.
Aerial view of a power generation facility

Control

Innova Technologies brings the balance-of-plant systems across your facility under a single, consistent control platform

A facility’s balance of plant spans many auxiliary and process systems, and the value isn’t in any one of them: it’s in having them engineered, integrated, and maintained as one consistent whole. Innova Technologies engineers the balance-of-plant control for your facility so that every system uses common parts, every controller communicates cleanly with the others and with the plant’s HMI/DCS/SCADA and historian, and operators see the same interface and the same data wherever they are in the plant.

 

One vendor delivers it all, consistently, and stands behind it. Common parts, consistent programming, consistent graphics, and consistent documentation, backed by a single point of accountability across the plant’s control systems.

View White Papers

Aerial view of power plant with water treatment systems

The Problem

A plant stitched together from many vendors is hard to integrate, operate, and maintain

When a facility’s systems come from many vendors on different platforms, they speak different communication languages, often need translation hardware to talk to each other, and rarely present a single, full view of the plant in one HMI. The result is difficult integration, inconsistent documentation, operator confusion as interfaces change from one system to the next, few common parts, and difficult, costly maintenance.

 

The fix is to bring it under one umbrella: common parts across systems; controllers that talk to each other and to the plant HMI/DCS/SCADA and historian; a single vendor delivering everything consistently; and the same format across all documentation, I/O lists, control narratives, cause-and-effect matrices, consistent programming, and consistent graphics. An operator on either side of the plant then sees the same interface whether they are looking at a fuel-conditioning skid, a gas turbine, or any of several compressor trains.

Capabilities

Balance of plant, engineered as one system

The exact balance-of-plant scope depends on the facility, rather than a fixed list of functions, Innova delivers whatever your plant needs, engineered consistently and integrated with the main machine control.

Whole-Plant Integration

Bring auxiliary skids, process systems, and machine controls onto one consistent platform with common parts, integrated with the plant HMI/DCS/SCADA and historian. Every controller communicates cleanly with the others and with the plant, so the balance of plant behaves as a single engineered whole rather than a set of isolated islands.

HMI and Graphics Standardization

One graphics standard across every system in the plant, with consistent navigation, consistent alarm presentation, and consistent symbol and color conventions, so an operator moving from a fuel conditioning skid to a compressor train is reading the same language. Alarm rationalization and priority assignment are applied across the whole balance of plant rather than left at each vendor's defaults, which is usually where nuisance alarm load actually originates.

Consistent Engineering and Documentation

One programming standard, one graphics standard, and one documentation format across the plant, I/O lists, control narratives, and cause-and-effect matrices, so everything is easy to operate, maintain, and extend. Operators see the same interface and the same data wherever they are in the plant.

Historian and Business System Integration

Every controller in the balance of plant feeds one data model with one timestamp, exposed to the plant historian, asset management, and reliability systems over standard interfaces rather than through per-vendor connectors. That is what makes cross-system analysis possible at all: correlating a skid event against a machine event requires that both were recorded in the same place, on the same clock.

Cybersecurity

The balance of plant is where the networking, external connections, and firewalls live. Innova implements the network architecture, segmentation, firewalls, and the configuration and rules that secure the plant's control systems, concentrated here where it belongs.

Network Architecture and Segmentation

The balance of plant is where the plant network physically lives, so it is where the architecture gets decided. Zone and conduit segmentation aligned with IEC 62443, defined boundaries between IT and OT, controlled and logged remote access paths, and firewall configuration are engineered as part of the scope rather than added after commissioning. Concentrating this here is deliberate: security applied consistently at the network layer is stronger than security applied unevenly system by system.

Auxiliary and Process Systems (as applicable to your plant)

Lube/seal oil systems, water-injection skids, fuel-conditioning skids, pumps and utilities, and other plant-specific systems, engineered into the integrated control rather than left as isolated, single-function islands. The scope follows your plant; the consistency and integration stay the same.

Spares, Standardization, and Lifecycle

Common hardware across systems means a smaller spares inventory covering more of the plant, sourced from regional suppliers rather than from a single vendor per system. Standardized platforms also mean one set of engineering tools, one training requirement, and a lifecycle plan that can be executed in phases as hardware ages, instead of a series of unrelated forced upgrades on somebody else's schedule.

Why Innova Technologies

One engineering team. One platform. One point of accountability.

Innova Technologies, formerly Petrotech, brings 50+ years of control experience across turbomachinery and the auxiliary systems that surround it, from lube and seal oil to fuel conditioning, water injection, pumps, and utilities. The reason a single supplier matters more on balance of plant than anywhere else is that balance of plant is defined by its interfaces. Every system in it exists to serve something else, so the value is not in any individual system controller but in whether they were engineered to work as one plant.
Common Parts, Common Practice
One hardware family, one programming standard to IEC 61131-3, one graphics standard, and one documentation format across the plant, delivered on commercially available platforms in simplex through triple modular redundant configurations as each system’s duty requires.
Accountability That Does Not End at a Skid Boundary
When the balance of plant comes from one supplier, integration problems have an owner. There is no interval spent establishing whether the fault sits with the skid control vendor, the integrator, or the auxiliary system supplier, because those are the same party.
Proven at Factory Acceptance Test as One System
Balance of plant systems are tested together against simulation before shipment, including the interactions between them, rather than each system being proven alone and integrated for the first time in the field.

Technical Resources

Engineering documentation for balance-of-plant control

Peer-reviewed white papers and application briefs from real facility integrations.

What Happens During Control System Commissioning?

Control Panel Design for Harsh Industrial Environments

The Future of Turbomachinery Control Systems

FAQ

Frequently asked questions

Can you integrate equipment you did not supply?
Yes, and on a live plant that is the normal starting point. Existing skids and controllers are brought into the integrated scheme where they can expose the data and accept the commands required, and replaced where they cannot or where they are obsolete. Part of the assessment is telling you which is which, and the answer is usually a mix rather than all of one.
It works at the control layer rather than at the equipment layer. You may keep your relationships for the mechanical packages while control engineering, programming, graphics, documentation, and integration come from one source. The single point of accountability is for how the plant behaves as a control system, which is where the ambiguity usually sits.
Defined per plant during engineering, and defined explicitly rather than by convention. The common arrangement is that machinery controllers hold the real-time control and protection for their systems and operate independently, while the balance of plant control provides supervision, setpoints, and the plant-wide operator view. What matters is that the boundary is documented in the control narrative and the cause-and-effect matrix, so nobody has to infer it during an event.
A common platform is not the same as a common controller. Systems retain their own controllers and their own protective functions, with redundancy specified per system according to its duty. What is shared is the hardware family, the programming standard, the graphics, and the documentation. Sharing those reduces failure by removing translation hardware and inconsistent practice, rather than concentrating risk.
Phasing is normal and usually preferable. A common approach standardizes the engineering practice, graphics, and documentation first, then migrates systems onto the common platform as each reaches an upgrade point or an outage allows. That spreads cost, avoids a single large outage, and lets the standard prove itself on one system before it is applied to twelve.

Bring your plant under one control umbrella

Common parts, one HMI experience, consistent documentation and programming, integrated cybersecurity, and a single point of accountability, engineered as one system for your facility.

Featured

Open, documented, maintainable control.

IEC 61131 standardized logic your team can support without OEM lock-in.

Don’t see your industry?

Your machinery application is likely in our scope.

If your equipment runs and your downtime costs more than the controls do, let’s talk

Single-source

One team, drawing to startup.

Engineering, fabrication, installation, and commissioning under one contract.
FORMERLY PETROTECH

A New Name for the Company We've Become.

SAME PEOPLE.
SAME ENGINEERING EXPERTISE.
BROADENED HORIZONS.

A MESSAGE FROM JOHN KAZOUR, CEO

Welcome to Innova Technologies

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.

John Kazour

CEO, Innova Technologies