Skip to content

Data science consultancy in Eindhoven

We build predictive models using machine and maintenance data, and turn engineers’ knowledge into features, as we did for Fokker Services’ maintenance planning.

We worked closely with Fokker Services’ maintenance engineers to turn their knowledge into features for the model

We developed a planning tool that combines historical maintenance data, sensor data and operational data in a predictive model. On a Databricks platform in Azure, we brought together the scattered data sources and trained the predictive models.

Read the case study

Can a model predict when our machine or component needs attention?

The control system logs temperatures and vibrations, the ERP system tracks orders, and faults are recorded in the maintenance system. An experienced engineer can spot small signs that something is about to go wrong. A model makes those signs measurable across all your machines at once.

Book a conversation

A predictive model for manufacturing depends on the right features and a fair evaluation

Discuss your prediction

Engineers’ knowledge as features

For Fokker Services, we turned maintenance engineers’ knowledge into features: the characteristics drawn from sensor and maintenance data that the model uses.

Taking rare failures seriously

Failures are rare. We measure precision and recall, because the percentage of correct predictions is almost always high when failures are rare.

Tested on a later period

We train on completed years and test on the period that follows, by machine type, so a new series or revision is taken into account.

An explanation for every prediction

For each prediction, we show which signals carried the most weight, so an engineer can assess whether the model is right.

We define the failure or anomaly first, then look at the sensor data

  1. Define the outcome

    Which failure, rejection or replacement do you want to anticipate, and how much time does the planner need to act?

  2. Features with engineers

    Together with engineers, we select signals from sensor, ERP and maintenance data and test the model against a later period.

  3. Bring the prediction into planning

    The result goes into the planning or maintenance system, with a designated owner and monitoring for anomalous inputs.

Have enough faults and sensor data been recorded to build your own model?

Talk it through

Suitable if

Machines already log sensor readings, faults and replacements are recorded with dates and machine numbers in the maintenance system or ERP, and planners or engineers want to know sooner where problems might arise.

Not suitable if

Faults are mostly documented in emails or held in people’s heads, or they rarely occur. In that case, a model has nothing to learn from. Start by recording faults or building a dashboard; we’ll tell you that too.

What the scope depends on

The number of machines and machine types, how sensor data is stored, whether faults can be linked to a machine, where the prediction needs to appear, and who will manage the model afterwards.

Who owns the machine data?

If the machines are at your client’s site or the data comes from the OEM, contracts determine what you can do with it. Document this in advance; your legal counsel or procurement officer should review the agreements.

Fixed maintenance intervals, a condition-based model, or bring the data together first?

Fixed intervals

Choose this if failures are rare and cause little damage, or if the manufacturer specifies the interval. It’s easy to schedule and explain.

A predictive model

Choose this if downtime is costly and sensor and failure data are already available. Our advice: start with one type of machine and compare the model with the fixed interval.

Bring the data together first

Choose this if sensor, ERP and maintenance data are kept separately. A data platform brings them together, as it did for Fokker on Databricks in Azure.

We help manufacturers with both the model and the platform behind it

Data Science Lab has worked with data and AI since 2016. Based in Amsterdam, we’re a Databricks and Microsoft partner. For Fokker Services, we brought data sources together on Databricks in Azure. In Brainport, we work on site or online.

Book an introductory meeting

With your breakdown history on the table, the first conversation gets straight to specifics

Stef Stoelwinder

Stef Stoelwinder

Business Development

Stef is your point of contact. In our first conversation, we’ll discuss which breakdown you want to predict and what machine data is available.

Which fault or anomaly do we want to spot earlier?

Describe the machine or process, what you want to predict and what data you have. We’ll reply by email or arrange an initial conversation.

Enter a valid email address.

Let us know how we can help you.

Frequently asked questions

It builds models using your own machine, sensor and maintenance data to predict outcomes such as a breakdown, a rejected part or the need to replace a component. These models are part of the AI applications we build and put into use.

If you’re first looking for advice on where to start with AI in your factory, see AI consultant Eindhoven. That’s about deciding what to do; here, we’re talking about the model itself.

No. Fokker Services is an aviation MRO company, providing maintenance, repair and overhaul services. We mention this case study as an example of what we do with maintenance and sensor data. We haven’t published a case study involving an organisation in Brainport.

Our office is on Westerdoksdijk in Amsterdam. In Eindhoven and the rest of Brainport, we work on site or online.

At Fokker, maintenance was largely scheduled at fixed intervals and based on engineers’ experience. This sometimes meant maintenance happened too early or too late. Working closely with the maintenance engineers, we translated their knowledge into features that make the model reliable.

A feature is an attribute the model uses in its calculations, such as the number of operating hours since the last overhaul. The engineer knows which attributes matter; the model weighs them. Read the case study.

Usually, it’s sensor readings from machine controls, downtime and faults recorded in an MES or maintenance system, orders and routings from the ERP system, and measurement reports from quality control. The challenge is linking them: which machine number and timestamp correspond to which fault?

Brainport Development describes the region as strong in high mix, low volume, high complexity manufacturing. That means there’s little repetition for each product. So we often make predictions per machine or component, rather than per product. Read more about the sector in data and AI for manufacturing.

There are then few examples to learn from, and a model that never predicts a breakdown will already be right almost all the time. That’s why we measure precision (how often an alert is justified) and recall (what proportion of breakdowns the model detects), then work with the planner to set the threshold.

If there are too few breakdowns, a model can instead learn what normal behaviour looks like and flag deviations. This is called anomaly detection.

For each prediction, we show which features carried the most weight, for example using SHAP values: a method that calculates each feature’s contribution to an individual prediction. The engineer can then see whether the model is responding to a rising temperature or to something irrelevant.

This also tests whether the features make sense. If a model performs well because of a feature that engineers consider illogical, it’s relying on a chance pattern in the data.

Where planners and technicians already work: in the planning system, maintenance system or a dashboard. At Fokker Services, the tool helps planners schedule work orders, parts and capacity ahead of time. To learn how we improve planning itself, see optimising planning with AI.

Machines, suppliers and products change. So agree in advance who will monitor the model and when it will be retrained.

When breakdowns are rare and inexpensive, when the manufacturer prescribes the maintenance schedule, or when a dashboard using ERP and MES data already answers the question. To learn how we build models for images, text and predictions, see machine learning.

For predictions about individual patients or customers, with an emphasis on the decision point and validation, read data science consultancy Utrecht.