Applied AI & systems integration · since 1989

AI that reaches into the systems it was never meant to touch.

Your ERP has no usable API. The portal was built for a human with a mouse. The terminal screen is older than the internet. Getting data out of systems like those — and keying it back in — is what we have done for more than three decades. The AI goes on the other end of that pipe.

The approach

Everyone else builds AI for a blank page. We build it for the system you cannot turn off.

The hype is all greenfield — chatbots, copilots, new apps on clean data. But the systems a business actually runs on are ten, twenty, forty years old, mission-critical, and have no API. That is where the real work is, and where we have lived since 1989. The AI just goes on the far end of a pipe we already know how to build. Four rules make it safe to put on the systems that cannot fail.

  • 01 — Through the glass

    We read the system the way your best employee does

    Through the same screen, with every business rule, validation and calculation the system has accrued over decades left intact. The data comes out literal and correct — already assembled by the system that owns it.

  • 02 — Hands off the data

    We never touch the files underneath

    On a mission-critical system, writing to the data below the application is how disasters are born. We go through the front door, the way a person would — just faster, and around the clock.

  • 03 — It compounds

    Every correction becomes a permanent rule

    We never fix one case by hand and move on. Each piece of feedback hardens the whole system, so it gets more correct and less needy every week.

  • 04 — It shows its work

    The AI explains itself; a human signs off

    It reads, classifies and assembles — and audits its own work, with a stated reason for every decision — before anything irreversible goes out. You keep control of the moves that cannot be undone.

Thirty-odd years

Prying open systems that fight back — since before “RPA” had a name.

The tool on the far end of the pipe keeps changing — a mainframe transaction then, a web page, a Notes agent, a large language model now. The craft never has: get the data out of the system that will not give it up, and put it where the business needs it. Plugs Technology was incorporated in 2007; the work goes back to 1989.

  • 1989

    IBM mainframe · CICS

    First production screen integration — reading 3270 transaction screens under CICS on IBM VM, before the web existed.

  • 1997

    A prominent customs house broker

    Put a System/36 on the web for shipment tracking — the start of a relationship now approaching three decades, today running on AI.

  • 1999

    Hampton Jitney

    Extended a System/36 reservation system to the web — bidirectional, booking seats straight back into the midrange, when online booking itself was brand new.

  • ~2000

    Riverhead Building Supply

    Contractor online ordering against an AS/400 custom ERP — live pricing, availability and order entry, years before B2B e-commerce was ordinary.

  • Today

    Nassau University Medical Center

    A Master Patient Index in production fifteen years, and the next re-platforming underway — the same discipline, now with AI on the far end.

Start here

Tell us what you have been told is impossible.

A couple of sentences about the system and what you need out of it is enough to get a straight answer about whether we can do it.

bobg@plugsinc.com (631) 830-2555 WhatsApp 455 Sunrise Highway, West Islip, NY 11795 Plaza León, Cozumel, QROO, MX