Microsoft Copilot in engineering design: where it fits and where it stops

How the two are built.

The difference is not a feature list, it is a question of construction. Microsoft 365 Copilot is built on the Microsoft Graph, that is, on what the tenant already knows about your work: files in SharePoint and OneDrive, mail, calendars, meetings, Teams. That is an excellent foundation for asking what was discussed last week or where a project stands. For asking which clause of a standard applies to this assembly it is the wrong starting point, because standards rarely live in Teams.

KoAssist starts at the other end. The starting point is the engineering document base: the standards library, specifications, design guidelines, drawings, old project folders, archives in Autodesk Vault and SOLIDWORKS PDM. From those a dedicated index is built, one in which a page number means something. That is why the answer can point at page 34 and not only at the file.

The rest follows almost by itself. Copilot is broad and flat: it can do something in every Office document but covers no professional domain in depth. KoAssist is narrow and deep: outside engineering and technical documentation it can do nothing, and inside it knows the difference between a tolerance and a material specification. These are not competing product philosophies but two different jobs.

When is Microsoft Copilot the better choice?

If your company runs entirely on Microsoft 365 and the knowledge you are looking for sits in SharePoint, Teams and Outlook, Copilot is the shorter path. The licence is negotiable, the rollout needs no new vendor, and IT does not have to assess an additional processor.

If the benefit should reach beyond engineering, Copilot wins as well. It summarises meetings, drafts mail and builds presentations. That is not what KoAssist is built for.

And if generative AI is to be tried across the whole office first, rather than specifically in engineering, Copilot is the obvious starting point.

When is KoAssist the better choice?

When the answer needs a source. File, page, a jump to the passage in the original. For a query from an assessor, an approval or a deviation report, being told it is somewhere in this document is simply not enough.

When the knowledge sits outside Microsoft 365. In mechanical engineering that is the normal case: thirty years of project folders on a network drive, drawings in Autodesk Vault or SOLIDWORKS PDM, the standards library as PDFs next to them. Copilot reaches those archives only through a connector project of its own; KoAssist connects to them directly.

When the drawing itself should be checked. A comparison against your own design guidelines in which every finding names its rule and its place on the sheet is not part of an office assistant's scope, and here it is a module of its own.

One special machine, one query, two routes

An engineer is designing a special machine for a customer in France. The assessor asks which requirement applies to the emergency stop and where the company decided this before. In the company there are: the standards library as PDFs on a network drive, a design handbook in SharePoint, an email from 2022 with the interpretation at the time, and three drawings in the Vault.

With Copilot she finds the email and the handbook, because both sit in the Graph. The answer names the documents. The standards library on the network drive is not there unless a Graph connector has been set up for it, and neither are the drawings in the Vault. So she has two of four sources and has to find the rest herself.

With KoAssist she gets one answer that brings all four together, and behind it sit file and page: handbook page 34, standard section 5.3.2, the email with its date, the drawing with its sheet number. She clicks the passage, reads the paragraph in the original and attaches it to her reply. That way the assessor can trace where every statement comes from.

To be fair: if everything sat in SharePoint the advantage would be small. It comes from the network drive and the PDM, that is, from exactly the archives that are typical in mechanical engineering and not foreseen in an office tool.