AI is usable in operations when the same question gives the same answer every time, and every answer can be traced to its source.
That comes from the data, not from the AI.
From source data to AI-ready asset knowledge. IEC 81346 provides the common language. Beside it, the same three layers in a setting everyone knows.
The material already held in documents and databases: diagrams, manuals, maintenance records, spare parts lists, requirements. Complete in each system, connected in none.
IEC 81346 gives every technical object one identity, wherever it appears. Not a new naming scheme, but an address system that the existing names can be resolved to.
Documents, properties, requirements and maintenance data connected into one structure the AI can use directly. It is the same reason GPS navigation works.
Indexing the documents gives the first layer and only the first.
The same pump can appear under four different names, and nothing in the text says they are the same object.
An AI reading that is working from photographs of buildings. It can describe each one, but it cannot give directions between them, because no photograph contains a street.
And when it fails to connect them, nothing shows. The answer is less complete, but it still reads well.
Four names. No line between them.
With the three layers in place, an AI can work directly on the asset. Staff ask in a chat window, and get answers that hold.
Every answer points back to a component, a document and a revision, and all of it runs on the organisation’s own systems.
The map knows what belongs in the area it covers, so it can list what is installed but never described.
Files that refer to nothing that exists any more, or that never existed under that name.
Demands that were set, and against which no test, inspection or document was ever filed.
A system built on documents alone cannot do that. It has no way of knowing whether something is missing or simply was not found.
The whole asset does not have to be described before the first questions can be answered.
The foundation is built from the documents and databases already in place, one area of the asset at a time. Nothing has to be re-documented first.
The principle can be shown, not only described. A preliminary model of one area is enough for a short demonstration of how this works in practice.
An AI can be added at any time, and whichever one is added will be replaced by a better one. The map of the asset is the part that keeps its value.
An AI can only be trusted if the data beneath it is structured and traceable.
The asset map is not new data. It is the structure already implied by the documents, tags and records you have, made explicit and connected. OntoTeq reveals that structure, and Know-Y is where it becomes navigable and, from there, AI-ready.
Start with one area and the data you already have. We’ll show you what the map already knows, and what it says is missing.