Controls & systems

The platforms we work across.
And how they connect.

Plants run on what was installed when the line was built, and then on whatever came next. We work in all of it, current and legacy, with no partner agreements and no catalog to sell from.

How to read this page

Fluency, not a brand preference.

Nobody standardizes a thirty-year-old plant before calling for help. A typical site has three generations of controllers, two HMI products, a SCADA layer somebody inherited, and a historian nobody trusts. The families below are the ones we meet most and program, migrate, secure, and integrate directly, with licensed vendor tools.

If yours isn’t listed, ask. The engineering is the same; the software is just the dialect.

What this list is for

  • Knowing we can read your existing programs before we quote
  • Planning a migration between any two families below
  • Connecting controllers to SCADA, historians, and business systems
  • Securing and hardening the layers you already own

Layer 1

Controllers

Ladder, structured text, function block, and sequential function chart across the major PLC and PAC families, including the discontinued ones still running production.

  • Rockwell Automation / Allen-BradleyControlLogix, CompactLogix, GuardLogix and the Logix 5000 family in Studio 5000; legacy PLC-5, SLC 500, MicroLogix, and Micro800 in RSLogix 5, 500, and Connected Components Workbench.
  • SiemensSIMATIC S7-1500 and S7-1200 in TIA Portal; S7-300 and S7-400 in STEP 7 Classic; S5 where it is still in service.
  • Schneider Electric / ModiconM580 and M340 in EcoStruxure Control Expert (Unity Pro); Quantum and Premium legacy systems.
  • Emerson / GEPACSystems RX3i and RSTi-EP in PAC Machine Edition; Series 90-30 and 90-70 legacy.
  • Machine and motion controlBeckhoff TwinCAT 3 on CX and C-series industrial PCs with EtherCAT; B&R Automation Studio, X20, and mapp on Automation Runtime; Bosch Rexroth ctrlX and IndraLogic; CODESYS-based controllers from WAGO, Phoenix Contact (PLCnext), Festo, and Eaton.
  • Compact and machine PLCsOmron Sysmac NJ/NX and CJ/CS; Mitsubishi MELSEC iQ-R, Q, and FX; Keyence KV; AutomationDirect Productivity, Do-more, and DirectLOGIC; Unitronics and IDEC where OEM equipment brings them in.
  • Process control and DCSRockwell PlantPAx; Emerson DeltaV; Siemens PCS 7 and PCS neo; Honeywell Experion; ABB 800xA, for the batch and utilities side of food and process plants.

Around the controller

Drives, motion, safety, and robots

The devices a controller has to talk to, and the ones that have to be integrated when a machine builder leaves.

  • Drives and motionPowerFlex and Kinetix; SINAMICS and SIMOTION; Altivar and Lexium; Yaskawa, SEW-Eurodrive, Danfoss, ABB, and Beckhoff AX; EtherCAT, CIP Motion, and PROFIdrive.
  • SafetyGuardLogix and CIP Safety; Siemens F-CPUs and PROFIsafe; Pilz PNOZmulti; SICK and Banner safety devices; Beckhoff TwinSAFE and B&R safety.
  • Robotics and visionFANUC, ABB, KUKA, Yaskawa Motoman, and Universal Robots integrated with the cell controller; Cognex and Keyence vision.

Layer 2

Operator interfaces

Terminals and HMI applications built for the person running the line, including the discontinued products that still have to be migrated rather than replaced from scratch.

  • Rockwell / FactoryTalkFactoryTalk View ME on PanelView Plus and PanelView 5000; FactoryTalk View SE; legacy PanelView Standard, PanelBuilder32, and RSView32.
  • SiemensWinCC Unified and WinCC Comfort/Advanced on Comfort and Unified panels; WinCC flexible legacy.
  • Schneider ElectricHarmony and Magelis panels in Vijeo Designer and EcoStruxure Operator Terminal Expert.
  • Machine-builder panelsBeckhoff CP panels and TwinCAT HMI; B&R Power Panel and mapp View; Omron NA/NB; Mitsubishi GOT; Keyence VT.
  • Other panelsRed Lion Crimson, Pro-face GP-Pro EX, AutomationDirect C-more, Weintek EasyBuilder, Exor, Maple Systems.

Layer 3

SCADA and supervisory

The supervisory layer is where plants accumulate the most complexity and the least documentation. We design, migrate, and consolidate it, and we are fluent in the platforms most plants end up standardizing on.

  • Inductive Automation IgnitionPerspective and Vision; Ignition Edge; Tag Historian, SQL Bridge, and Reporting modules; MQTT Engine and Transmission.
  • AVEVA (Wonderware)InTouch HMI and InTouch for System Platform; System Platform / Application Server; AVEVA Edge (Indusoft); legacy InTouch and ArchestrA applications.
  • RockwellFactoryTalk View SE distributed and network station; FactoryTalk Optix.
  • Emerson / GEiFIX and CIMPLICITY, including Proficy-era installations.
  • Siemens, Trihedral, othersWinCC SCADA (V7) and WinCC Unified; VTScada; COPA-DATA zenon; ICONICS GENESIS64; AVEVA Plant SCADA (Citect).

Layer 4

Connectivity and integration

Where the controller data becomes something the rest of the business can use. This layer is also where most security and resiliency problems live, so we treat the servers, drivers, and schemas as engineered components, not installers to click through.

  • OPC servers and driversKepware KEPServerEX and ThingWorx Kepware; FactoryTalk Linx and RSLinx Classic; AVEVA Communication Drivers and the OI/DAServer family (including DASABCIP); Matrikon OPC; Ignition’s native OPC UA server; Softing and Takebishi where installed.
  • Protocols and standardsOPC UA and OPC DA; MQTT with Sparkplug B; EtherNet/IP and CIP; PROFINET and PROFIBUS; Modbus TCP and RTU; DNP3 and IEC 61850 for utilities; legacy DH+, DH-485, DF1, DeviceNet, and ControlNet.
  • Data and application integrationSQL Server and PostgreSQL via Ignition SQL Bridge and FactoryTalk Transaction Manager; ISA-95 and ISA-88 models for MES and ERP interfaces; REST and JSON interfaces; Unified Namespace designs on MQTT brokers (HiveMQ, EMQX, Mosquitto).
  • Historians and reportingAVEVA PI System (OSIsoft PI) and FactoryTalk Historian SE; AVEVA Historian (Wonderware Historian); Ignition Tag Historian; Canary; reporting through SQL, Power BI, and Grafana.

Where it usually goes

Migration paths we plan most often.

Each of these is a project we have scoped, rehearsed, and cut over around production. The hardware changes; the operating behavior, alarm philosophy, and operator knowledge have to survive the move.

  • PLC-5, SLC 500, MicroLogix→ ControlLogix or CompactLogix, with the I/O and program conversion done deliberately rather than by the automatic tool alone.
  • PanelView Standard, RSView32→ FactoryTalk View ME or SE, or Ignition where the plant is consolidating its supervisory layer.
  • S7-300/400, S5→ S7-1500 in TIA Portal, including the SCL and STL rework that the migration tool leaves behind.
  • Quantum, Premium, 90-30→ M580 or PACSystems, or a cross-vendor move when the site is standardizing.
  • InTouch, iFIX, RSView32 SCADA→ Ignition, AVEVA System Platform, or FactoryTalk View SE, with historian and alarm data carried forward.
  • Orphaned OEM machines→ Documented, supportable control on the plant standard when the machine builder is gone, the controller is discontinued, or the program was never handed over.
  • DH+, DH-485, DF1, serial Modbus→ EtherNet/IP, PROFINET, or Modbus TCP over a segmented plant network, with OPC UA at the boundary.

Your installed base

Tell us what’s running.
We’ll tell you what it will take.

Discuss a project