Skip to content

AI consultant in Eindhoven

For manufacturers and suppliers in Brainport: we put fragmented data and engineers’ knowledge to work, as we have in aviation with Fokker Services Group.

A single data platform gives Fokker Services Group control over planning, maintenance and delivery

“For us, the data platform is the central place where data comes together. It lets us provide data for business insights across the company while ensuring that only 1 version of the truth is available” Daan Mastenbroek, Lead Data Engineer and Architect

Read the case study

How do you schedule small production runs when revisions, breakdowns and specifications collide?

In Brainport, much of the work is high mix, low volume, high complexity: small batches of complex components in open supply chains with OEMs. A client changes a revision, a milling machine breaks down, and the tolerance is in an old PDF. We identify what data can resolve first.

Schedule a conversation
Close-up van precisiegefreesde messing onderdelen

Maintenance, planning, ERP and documents each call for a different approach

Discuss your challenge

Maintenance guided by data

A predictive model based on maintenance history, sensor data and operational data. At Fokker Services Group, we incorporated maintenance engineers’ knowledge into the model.

Planning that takes capacity into account

For Fokker, we developed a planning tool that brings together fragmented data sources, so planners can plan work, parts and capacity ahead of time.

Management information from a single source

Dashboards for management, planning and finance based on the same data, such as the Power BI dashboards and Power BI app we built for Ammega.

Answers from your documents

An assistant that answers questions using specifications, manuals and contracts. At Fokker, Anthony Chat does this with retrieval-augmented generation (RAG).

Your engineers’ knowledge goes into the model

  1. Review the sources

    Together with planners and engineers, we review the ERP, MES, fault logs and document folders: what gets recorded, and who owns it?

  2. Test one bottleneck

    We choose maintenance, planning or knowledge held in documents, then use historical data to check whether the result matches what engineers see.

  3. Keep building on one platform

    What works goes onto a Databricks or Fabric platform. The next bottleneck can then reuse the same machine and order data.

Is this useful for a supplier producing small batches?

Explore whether it’s a fit in a conversation

A good fit if

You produce small batches for demanding OEMs, your planners and engineers lose time rescheduling and searching for information, and the data is already in ERP, MES or machine logs, even if it’s fragmented.

Not a good fit if

Breakdowns, setup times and rejected parts aren’t recorded anywhere yet. In that case, a model has nothing to learn from, and you need to start by recording them in ERP or MES. We can help you think that through too.

What determines the scope

How many sources are involved, how clean the order history and machine data are, whether a data platform is already in place, and whether you or we will manage it afterwards.

Confidential client documents

OEM drawings and specifications may be subject to confidentiality agreements. From the Fokker project, we know that documents need metadata, for example about the client or component, so an assistant doesn’t use passages from another client’s documents.

Does AI in your factory start with maintenance, planning or engineers' knowledge?

With maintenance

Choose this if downtime determines your delivery times and your machines already record faults or sensor readings. In that case, predictive maintenance is the logical first step.

With planning

Choose this if planners juggle orders and machines around the ERP system every day. Our advice for small production runs: the order data is already there, so start by optimising planning with AI.

With engineers' knowledge

Choose this if production planners and engineers spend time searching through specifications, work instructions and customer documents. An assistant using generative AI helps them search and cites the source.

Consultants who also build the planning tool and data platform

Since 2016, Data Science Lab has worked with data and AI from Amsterdam. We’re a Databricks Partner and Microsoft Partner, and we build those platforms ourselves. Colleagues share knowledge at Techdays, and we try out new techniques in our internal lab.

Book an introductory meeting

A fault list or planning board gives the first conversation a concrete focus

Stef Stoelwinder

Stef Stoelwinder

Business Development

Stef will arrange the first conversation with you. Together, we’ll choose a bottleneck in maintenance, planning or engineering. We can meet at your office, at ours in Amsterdam or online.

Where are our planners and engineers losing the most time right now?

Describe the bottleneck in maintenance, planning or engineering. We’ll reply by email or arrange an initial conversation, on site or online.

Enter a valid email address.

Let us know how we can help you.

Frequently asked questions

The ERP system holds orders, actual costs per production batch and routings: the sequence of operations for each product. A MES, the system that records what happens at each machine, logs downtime and faults. There are also machine logs, quality-control measurement reports and non-conformance reports.

These sources often exist but are not connected. The first task is to find the link: which order number belongs to which machine run?

It uses retrieval-augmented generation (RAG). The system splits documents into sections, finds the passages relevant to each question and has a language model base its answer on them. If you make the system cite the document and paragraph for every answer, you can check each one.

Anthony Chat works this way for Fokker Services Group. You can read about distinguishing between similar contracts in our blog on internal LLMs and RAG.

At Fokker Services Group, maintenance was mainly scheduled at fixed intervals and based on engineers’ experience. This sometimes meant maintenance happened too early or too late. A planning tool now combines maintenance history, sensor data and operational data to produce a prediction.

The lesson for manufacturing: engineers’ experience does not disappear; it becomes an input. Their knowledge became features, the characteristics the model uses in its calculations. Read the maintenance planning case study.

Yes, and the data is often already available. For Fokker Services Group, a model predicts what an invoice amount should be based on the work delivered, then compares that prediction with the actual amount. Large discrepancies appear in a dashboard, so staff only need to check the exceptions.

The same approach could work for subcontractors’ invoices or actual costs per production batch. Read the invoice-checking case study.

AI-hub Brainport has a workstream dedicated to the digital transformation of SMEs using AI. TU/e’s EAISI institute researches AI in machines, such as robots and medical equipment. OEMs, suppliers and knowledge institutions come together at Brainport Industries Campus in Eindhoven.

Their focus is on research, knowledge sharing and regional collaboration. We build an application for your own process and manage it if you want us to. The two approaches work well together.

Because experienced people are in short supply. In 2024, the Dutch government reported that the microchip sector in Brainport Eindhoven faced a shortage of staff, among other challenges. Through Project Beethoven, the national and regional governments are therefore investing, among other things, in training more technicians. Meanwhile, much of the knowledge about machines, customers and exceptions resides with experienced engineers.

An assistant built around work instructions, or a model that draws on their maintenance experience, helps keep that knowledge usable when someone leaves or changes roles.

If you produce few variants and your schedule rarely changes, your ERP planning module is often enough. A fixed maintenance interval is fine if faults are rare and cause little damage. And if the answers are in a handful of documents, a good folder structure will help more than an assistant.

A dashboard using ERP and MES data often provides enough visibility into downtime and backlogs. See our Power BI dashboards.