Questions people actually ask.

What is a fault finding tree?

A structured diagnostic route. It starts at a symptom, such as a motor that will not start, and asks a sequence of questions and checks that narrow things down until you reach the component that has actually failed. Think of it as an experienced engineer's reasoning, written out so somebody else can follow it.

Is any of this available to buy yet?

No. BuntelliBuild, BuntelliTrace and BuntelliData are all in development. Nothing is on sale, there are no pre orders, and there is no beta programme to sign up to yet.

When will it be ready?

There is no date, and any date given now would be invented. This is built in evenings and weekends alongside a full time engineering job, and it will be released when it works properly rather than on a schedule. Leave your email on the home page and you will hear when there is something real.

What will it cost?

Not decided. The likely shape is that authoring trees is free and the paid element sits elsewhere, but that is a working assumption rather than a commitment. Anyone who tells you exact pricing for software that does not exist yet is guessing.

Where does my data live?

On your own machines. Trees, run records and feedback are stored as plain files locally. There is no cloud application database, which means your fault history never passes through my systems and cannot be seen by me or by anyone else using the software.

The one exception is if you choose to send feedback directly to me, which is an ordinary message you decide to send. Details are in the privacy notice.

Which platforms will it run on?

Windows, Mac and Linux. It is a desktop application rather than a website, because it needs to read and write files on your machine directly and because a plant room is not always a place with reliable signal.

Will it work offline?

Following a tree will, yes. Once a tree is on the machine you can work through it with no connection. A licence check will need network access occasionally, so the honest description is offline capable rather than offline forever.

Do I have to write my own trees?

You will be able to, and for anything specific to your plant you probably will want to. There is also an intention to ship generic trees for common equipment so there is something useful in the box on day one.

Can you write a tree for our equipment?

Possibly, later. Bespoke trees written to order is one of the directions being considered, but the tools come first. If you have a specific need, say so anyway. Real examples shape what gets built.

Is this aimed at apprentices or at experienced engineers?

Both, at different ends. An experienced engineer writes the tree. An apprentice, a new starter, or anyone covering an unfamiliar area follows it. The value is in moving knowledge between those two people without either of them having to be in the same room.

How is this different from a manual or a flowchart?

A manual tells you how the equipment works. A flowchart tool lets you draw boxes. Neither is built around the specific job of walking somebody through a live diagnosis, recording what actually happened, and improving the route afterwards based on what was learnt. That is the whole scope here.

I have a problem with the website or my signup.

Send a message through the contact page and it reaches me directly. If you want your email taken off the notification list, ask and it will be deleted.