One engineer, two evenings a week, and a problem worth solving.

I am Ben, a practising electrical engineer and designer. BuntelliSystems is mine. There is no team behind it, no investor, and no sales department. It is one person building something in the evenings because the problem has bothered him for years.

Why fault finding

Spend enough time around machinery and you notice the same pattern. A line stops. Somebody who knows the plant well walks over, asks two or three questions, checks one thing, and finds it. Somebody who does not know the plant spends four hours on the same fault and might still be wrong.

The difference is not intelligence or effort. It is a route. The experienced engineer is following a sequence in their head that they have never written down, mostly because writing it down is tedious and no tool makes it easy.

That is the gap. Not another flowchart app, and not a training course. Something that captures the route properly, then hands it to whoever is standing in front of the machine at two in the morning.

How this is being built

Build first, sell later. I would rather show a working tool to an engineer and watch them use it than sell a promise and then discover the promise was wrong. That means no launch date, and no pre orders.

Evenings and weekends only. This is not my day job and it is not going to become a second one. It moves at the pace one person can sustain, which is slower than a funded startup and considerably more honest about it.

Lightweight by choice. No heavy platform, no monthly cloud bill passed on to you, and no application database sitting between you and your own data. Trees and records live as plain files on your own hardware. That is partly cost and partly principle: your fault history is your business, not mine.

What this is not

None of the content here comes from my employer. The fault finding trees BuntelliSystems produces are generic and equipment agnostic, written from scratch outside of work. Anything specific to a particular company's machinery belongs to that company, and it stays there.

Where it is up to

Early. The brand exists, the architecture is settled, and the tools are being built. The journal is where the progress gets written up, including the parts that go badly.

If any of this sounds like a problem you have, I would like to hear about it. Real faults from real plants are more useful to me right now than almost anything else. Send me a message.