Critical infrastructure · Latin America

Ulmo Grid · by Tirion Systems

The base layer to monitor and operate the region's critical infrastructure.

We start with the electric grid. Ulmo Grid turns the data a utility already has into inspection priorities, organized complaints and coordinated field work.

No servers or sensors needed to start. When you're ready, add measurements on the assets where they matter most.

Book a demoSee how it works
Ulmo Grid home screen: city map with transformers by priority, key indicators and today's to-do list
Home screen · demo data · estimated load

The data is there.
It just isn't connected to decisions.

Cooperatives and utilities know their networks. But complaints, consumption, assets and field work live in separate systems, spreadsheets and chat threads. So problems surface only when they're already urgent.

01

Complaints

They come in by phone or at the counter, and aren't always tied to the asset that serves that customer.

02

Assets

The asset inventory and billing data exist, but nobody cross-references them to see which transformer is under the most stress.

03

Field work

Site visits and work orders are coordinated over chat, and results are barely recorded.

What we build

A base layer for critical infrastructure

Latin America's cooperatives, utilities and public service providers keep power and water flowing for millions of people. Ulmo Grid is the shared system where those networks are seen, prioritized and operated: one model for their assets, customers, complaints and field work.

We start with electricity distribution. The same foundation later extends to water and waste.

~600
Electric cooperatives in Argentina
~2,400
Rural water systems in Chile
1
Model for assets, customers and work
0
Servers to install

How it fits together

01
Data that already exists

Customer registry, billed consumption, transformer inventory and complaints, exactly as they come out of your systems.

02
Network model

Every service point linked to its transformer on one map. You always see where each link comes from, and you can correct it.

03
Decisions and work

Priority assets with their reasons, grouped complaints, work orders, routes and reports.

04
Measurements

Sensors on the assets where they matter most. Measurements replace estimates without instrumenting the whole network.

How it works

Start with your data. Add measurements where they matter most.

Estimated load

With the data you have today

We estimate each transformer's load from billing data and typical hourly profiles, and build the inspection priorities.

Measured load

With connected sensors

On instrumented assets, measurements replace estimates. There's no need to instrument the whole network.

Transformer indicators: priority, peak load labeled ESTIMATED, service points and service life
Every screen labels estimated values as estimated.

From complaint to inspection · illustrative case

Several complaints. One transformer. A prioritized inspection.

01

Complaints are logged

By service point number or address. Each one lands on the map.

Outage complaint linked to a transformer that already has four other complaints
02

Ulmo Grid links them to their transformer

From the billing code, a manual assignment or proximity, with a confidence level.

Transformer assigned to a service point, inferred by proximity with 67% confidence
03

The operator reviews the reasons

Each factor adds points, so you see why that asset comes first. The work order starts there.

Reasons behind a transformer's priority: estimated peak load, age, thermal life, failures and complaints
04

The crew visits and logs the result

The work order gets a crew and a date. Findings go into the asset's history.

Work order for a service outage, with crew and scheduled date

Screenshots with demo data.

For every team

One source of truth to decide and act

Management

Which problems need attention, and the evidence to back up priorities.

Engineering lead

Which assets to inspect first, and why.

Operators and crews

How to organize complaints, site visits and pending work.

Board

Clear information to support maintenance and investment decisions.

Get started

A pilot with clear success criteria from day one

Browser-based, no servers to install. Files come in Excel or CSV, straight from your billing system.

You provide

  • Customer registry: service point number, address, rate class and, if available, transformer code
  • Billed consumption for the last 12 months
  • Transformer inventory: code, rating, location and year
  • Optional: complaints and failure history

We take care of

  • Reviewing and preparing the files
  • Importing, geolocating and linking every service point to its transformer
  • Setting up users and training your team
  • Supporting you throughout the pilot

How we know it works

  • Service point–transformer links checked in the field on a sample
  • Load estimates compared with any measurements you already have
  • Inspection of the top-priority assets
  • At least one work order completed, from complaint to logged visit

Let's scope a pilot.

We'll review a sample of your data together to confirm what can be loaded.