Skip to content
Blog

Introducing an AI agent: effort, process and prerequisites.

How much effort goes into introducing an AI agent in machine and plant engineering? What should be settled beforehand, how a 60-day pilot runs, what IT has to do and how you can tell at the end whether it is worth it.

Yanik YeganehfarCo-Founder & COO4 min read
Quick answer

Introducing an AI agent such as KoAssist starts with a 60-day pilot on a real project. Uploading the customer specification and documents is enough to begin. Connecting SharePoint, network drives or PDM follows in a second step and typically takes under two weeks. Settle the data processing agreement, subprocessors and file storage beforehand.

Contents
  1. What should be settled before the start?
  2. How does a pilot run?
  3. What does IT have to do?
  4. What does the team have to do?
  5. How can you tell after 60 days whether it is worth it?
  6. How do you get started?

If you run fourteen projects in parallel, you do not have three months to introduce a new tool, and you have no interest in an IT project. So the first question about AI in projects is a fair one. How much effort does it take?

This article describes how introducing an AI agent works, using KoAssist as the example, what should be settled beforehand and what your team needs to do.

What should be settled before the start?

Three things, and they should be settled before the first document, not after it.

The data processing agreement is signed. At KoAssist it is part of the standard terms, under Article 28 GDPR.

The subprocessors have been assessed. Your data protection officer should know who is involved in the processing and where.

It is decided which file storage will be connected. For the pilot, the project folder of one project and a set of completed projects are usually enough.

If you postpone these points until after the test, you risk having to repeat the test or not getting approval at all. What to check is covered under GDPR-compliant AI. How KoAssist handles these points is described under security and EU hosting.

How does a pilot run?

Choose a real project. A current or upcoming project, not one that is tidied up specially for the occasion. The usual mess is part of it.

Upload documents. To start, the customer specification with its accompanying documents is enough. This is not an IT project. KoAssist fills a project profile from them, every detail with evidence.

Connect file storage. In a second step SharePoint, OneDrive, Google Drive, network drives or PDM are added, together with completed projects as a source of experience. This is typically set up in under two weeks.

60 days in the project. KoAssist works with the released documents, maintains the project status and puts forward proposals. Your team carries on working as before.

Measure. On day one and after 60 days, onboarding time, effort for status requests and status meetings, and search time are recorded. Management then receives a results report. There is no commitment.

What does IT have to do?

Less than is often feared.

  • Decide where the knowledge is. SharePoint, network drive, PDM, project folders. This is the real preparation, and only your company knows which storage counts.
  • Set up access. The sources are connected through open interfaces, a whole folder at a time.
  • Do not rebuild permissions. They come from the directory service. Anyone who may not open a document in the source system will not see it in KoAssist either.

After that it runs alongside. KoAssist picks up new and changed documents by itself, and deleted ones disappear from it too. Whether the file storage has to be tidied up first is answered in the article on connecting AI to SharePoint and network drives. It does not.

What does the team have to do?

Mainly keep working. KoAssist changes nothing in the project status and sends nothing unless someone on the team confirms it. Proposals arrive marked as Change, New or Done and are accepted or rejected.

It helps to have one person in the pilot project who reviews proposals regularly and gives feedback on what is missing or was recognised wrongly.

How can you tell after 60 days whether it is worth it?

From the figures from the measurement, and from one simple question to the team. In the last few weeks, did you look in Project Memory before asking someone? If so, it is being used. Knowing your own coordination effort beforehand helps with the assessment. A method for this is described in the article How much time does coordination cost in design engineering?

How do you get started?

With a demo on one of your projects. After that you receive a proposal for a 60-day pilot, with no commitment. The key facts about KoAssist are on one page under facts. Which other tasks an AI agent can take on is described in the guide AI in engineering design.

Written by

Yanik Yeganehfar

Co-Founder & COO

On LinkedIn ↗

Frequently asked questions

Yanik Yeganehfar, co-founder of KoAssist

Find out with Yanik whether KoAssist fits your projects.

Request a demo