Skip to content
C. Celaya
// Industrial

Software that can hurt someone gets built differently.

The floor is where I learned this. A drawing is a promise. The system never signed it, so somebody has to check.

Industrial work has a property most software doesn't: the output touches something physical. A setpoint moves a damper. A schedule energizes a bus. Get it wrong on a website and a page looks bad. Get it wrong on a floor and somebody's day ends in an ambulance.

That gap is the whole reason I build the way I do. An industrial system has to be legible to the person holding the responsibility. If a maintenance tech can't tell why the machine said what it said, the machine has moved the risk onto them without asking.

What that means in practice: the model runs where you can reach it, not in a vendor's account. Answers come back with the record they came from. Confidence is stated, not implied. And the system is built to hand control back, because the person on the floor is the one who signs for the outcome.

The useful work here is rarely exotic. Twenty years of maintenance tickets nobody can search. Controls data being logged and never read. A procedure that lives in one person's head and retires with them. Those are ordinary problems, and they're worth more solved than any demo.

Questions that come up

What counts as industrial Applied Intelligence?
Applied Intelligence over the data a plant already produces: controls and SCADA histories, maintenance and work-order records, sensor telemetry, procedures and manuals. The goal is usually to make an existing record answerable, or to see a pattern in telemetry a person would need a week to find.
Does operational data have to leave our network?
No. Local-first is the default. Models can run on hardware you own, on your network, with nothing crossing to a third party. That is a design choice made at the start, not a setting toggled later.
What industrial background do you bring to this?
Twelve years in industrial and critical facility work: medium-voltage switchgear, building controls, commissioning and maintenance at Microsoft, T5 Data Centers and Schneider Electric. NFPA 70E and OSHA 10. The Applied Intelligence work came after, and it's aimed back at the problems that job left unsolved.
Do you work with manufacturers in the border region?
Yes. El Paso, Ciudad Juarez and Santa Teresa are a single manufacturing corridor and I'm inside it. Work spans both sides of the border, in English and Spanish.