Your 1995 machine still runs great — now it can report to your 2026 software

The toolkit is broad because old machines are diverse: RS-232 and RS-485 capture with protocol analysis when documentation is gone, Modbus RTU polling of drives and meters, serial-to-Ethernet converters with correct handshaking and timing, and communication modules for legacy PLC families that never left service. Where no data interface exists at all, we instrument from the outside — current transformers on the main feed, retrofit sensors, optical or contact-based cycle counting — inferring machine state without modifying a certified control system. Signal quality matters at this layer: isolation, grounding, and termination decide whether the data can be trusted.

The output lands wherever your modern stack expects it: an MQTT namespace, a historian, a SQL database, a dashboard. Success looks like a 30-year-old machine appearing in the same OEE report as the new cell, with data your scheduler trusts — and the retrofit typically costing a small fraction of replacement, on downtime measured in hours.

The survey comes first and covers every candidate machine: what ports and interfaces exist, what they emit, what documentation survives, and who on your maintenance staff knows the machine best. From that we produce an integration map with a per-machine approach — passive serial capture here, a comms module there, external sensing where nothing else works — and a named owner for each connection. Where an original vendor still exists and is protective, we work only at the interfaces they document and stay out of control logic, so any support relationship is preserved and responsibility for the machine's behavior stays where it was.

Each retrofit is tested against the machine itself. Captured serial output is decoded and checked against what the operator saw on the panel; external sensors are validated by counting cycles by hand for a while and comparing; polled registers are confirmed against known states. Machines come online in phases, usually starting with the one whose data matters most and whose downtime hurts least, and the collected data runs beside existing manual logs until both agree. Every retrofit can be removed by unplugging it, which is the rollback plan. Documentation records each connection, its wiring, its decoding rules, and who owns the machine.