AI that decides when a technician really needs to go out, and makes sure the job is fixed the first time.
For anyone who runs remote assets: chargers, wind and solar, telecom sites, pumps and more.
Scroll to see a day in the field
The problem
Remote assets raise alarms all day.
Chargers, turbines, solar parks, pumps and telecom sites. On a screen, most alarms look the same.
The problem
Today, a fixed rule decides.
Still down after 30 minutes? Send a van. When in doubt, dispatchers send someone, because a missed fault gets someone blamed and a wasted trip doesn't.
The problem
1 in 7
visits isn't needed.
The fault cleared on its own or could have been fixed remotely. The van drives out for nothing.
The problem
1 in 4
jobs needs a second trip.
Wrong part, wrong skill or wrong diagnosis. A failed visit adds 2 trips, and the fix comes about 14 days later.
At €300–500 a visit, an operator making 50,000 visits a year spends €2.1–3.6M on visits it didn't need.
50,000 ÷ 7 ≈ 7,100 visits × €300–500. Second visits and downtime come on top.What Veld does
Veld reads every alarm with the machine's data and its history.
Telemetry, past faults and past fixes, read together the way an experienced engineer would.
What Veld does · 1 Triage
Fix remotely, wait, or send.
Each call comes with its reasons. Faults that clear on their own, or can be fixed from a distance, stay off the road. Only real faults get a van.
What Veld does · 2 Complete
The van leaves with the right part.
Veld writes or completes the work order: likely fault, evidence, skill and parts, kept current as data comes in.
What Veld does · 3 Check
Veld confirms the fix held.
Pass or fail on every job, from the machine's own data. Every result flows back into triage, so each job makes the next call better.
What you get
Fewer trips, faster fixes, and proof that every job was done right.
The same day, decided by Veld: in this example, 2 van trips instead of 6, and none wasted. Your own number comes from a replay on your own history.