Where technical search loses time
The right document almost always exists. The problem is finding it. The data sheet is in the EDMS vault, the previous revision sits in a network folder and the vendor’s comment is in an email. To answer a simple question, such as a line’s design pressure, an engineer opens three systems and checks which revision applies. In a pilot, that time fell from 20 to 3 minutes per search.
What AI does on an engineering archive
- Answers technical questions in plain language, with the source document and revision.
- Finds the current version of a drawing, data sheet or procedure.
- Extracts metadata from legacy documents that entered the vault without attributes.
- Summarises what changed between two revisions of a document.
Security and governance
The agent runs in the client’s tenant and infrastructure. Whoever can access a document keeps that access, and nobody gains new permissions because of the AI. In the pilot, access is by invitation, in a dedicated test team in Teams. Client data does not train public models.
Why AI starts with the data
AI answers well when the archive is in order. Consistent metadata, standard numbering and a master document register that says which revision applies are what separate a correct answer from a plausible one. It is the work 29docs has done for years in engineering document management, which is why every AI project starts with an archive assessment.
Updated on .