Work

Selected work, in detail

Where each company started, what I did, and what they ended up with.

Villa del Rosario municipality

The town weather station

Apps published on the App Store and Google Play, open to the whole town.

tiempo.vdr.ar

The problem

Deciding whether to harvest today or call off an event means knowing what's happening here, and how the week has been going. Data from the nearest city is not enough.

What I did

A station measuring in town: temperature, wind and rainfall by the minute, with the history to compare against previous days. A public site and apps for Android and iPhone. Official weather-service warnings arrive as a phone notification the moment they are issued.

Municipalities of Córdoba

Traffic lights configured from a browser

Four intersections running in Villa del Rosario and Luque, with no daily intervention.

viacontrol.ar

The problem

Changing the timing of an intersection meant calling the vendor and waiting. A small municipality can't depend on that.

What I did

I designed the whole unit, from the board to the control panel. It creates its own WiFi network: municipal staff connect from a phone, adjust the ways and the timing, and leave. From then on it works unattended and without internet, switching mode by time of day — flashing amber overnight, back to the normal cycle in the morning, on its own.

International consultancy

A website that was infecting its own visitors

The site went back to serving clean content, with the way in closed for good.

The problem

The company site had been taken over and was showing visitors a fake screen that talked them into running a command on their own computer. Nobody knew since when, or how the attackers had got in.

What I did

A full cleanup of the site and of the files the attackers had scattered around to let themselves back in: close to fifty turned up. I closed the door they came through, rotated every credential, and left a check that flags any file that shouldn't be there.

Several companies under my care

Seeing something is about to fail before it does

Thirty-three machines across eight companies, reviewed from one place every day.

The problem

Looking after several companies, you find out about problems when somebody calls. And by the time they call, the disk is already full, an update has gone months without being applied, or a machine went down days ago and slipped by unnoticed.

What I did

Every client's machines report to a single panel I run. It shows the disk about to fill up, the pending update or the protection left out of date, and any of those gets fixed remotely without interrupting anyone.

Sofa factory

The plant, tracked stage by stage

From order to delivery, the whole route is recorded with no paperwork.

The problem

Nobody knew for sure which stage each sofa was at, or how much fabric was left. Orders were tracked by memory and phone calls.

What I did

A tablet at every station: the operator scans the order and marks the stage complete. The office sees progress as it happens, stock is deducted automatically, and the time clock feeds the same system.

Construction company, 100+ employees

Payslips signed from a phone

Over a hundred payslips a month that stopped circulating on paper.

The problem

Handing out, collecting and filing signed payslips for over a hundred people, every month, on paper.

What I did

Each employee logs in, sees their payslip and signs it with a finger on screen. Time off is requested and approved in the same place, with statutory days calculated automatically. Those without an email address log in with their employee number.

Companies with data they can't afford to lose

Backups that get tested, not assumed

It surfaced the reason some backups had been failing silently for months.

The problem

Backups ran every night and not one had ever been restored. When one fails, the alert gets lost among the automated emails nobody opens any more, and the problem surfaces on the one day it matters.

What I did

I reorganized the setup so the data lives in more than one place and outside the building. Failures now actually raise an alert, and every so often a copy gets restored into a separate environment to confirm the files open.

Production and distribution companies

The invoice comes from the same system that took the order

One entry: the sale closes and the invoice is already issued.

The problem

Entering the sale in the system and then entering it again at the tax authority. The same work twice, and two chances to get it wrong.

What I did

The invoice is authorized against the tax authority without leaving the system, and the document prints on the spot. A batch can be reviewed before issuing, so a data-entry mistake doesn't burn authorizations.

Want to look at this in your company?

Get in touch Back to home