FAQ

Frequently Asked Questions About Maddox AI

Find the answers to frequently asked questions about Maddox AI below. If you have any further questions or would like to know whether Maddox AI is also suitable for your quality control processes, our team of experts is happy to advise you!

FAQ

Do you have any questions? We've got answers:

General Information

What is the difference between classic and ML-based visual quality control?
Classic systems are given rules to recognise defects. A ML model, on the other hand, learns from examples whether a part is OK or NOK. In this learning process, the model derives implicit rules that do not require explicit programming (e.g. "NOK, if scratch on top left"). Machine Learning allows Maddox AI to automate even very complex use cases, such as surface recognition.
We’ve tried automation systems before – why should Maddox AI reliably automate our inspection task?
In contrast to classic quality control systems, the Maddox AI system is very robust in the face of high error variability and changing external influencing factors. Typical problems of classic systems, such as high pseudo rejection rates, can be prevented.
As a user, can I use Maddox AI without a technical or artificial intelligence background?
Yes, Maddox AI's software is designed in such a way that everybody can train AI models and put them into use after an initial thirty-minute training session.

Costs

Can I try Maddox AI without charge and risk-free?
Yes, Maddox AI bears the entire investment risk. Only when we have been able to show you that our model achieves the predefined performance KPIs (e.g. inspection accuracy and speed) you enter a paid licensing model.
How much does Maddox AI cost?
This depends on the specific use case. Before we start with a Maddox AI project, we show you transparently how much the use of Maddox AI would cost. Based on this, you can calculate your business case.
Is Maddox AI also worthwhile for companies that produce in small batches?
A small series is undoubtedly more challenging for an AI system. However, we have already successfully implemented several systems in manufactory-like productions. Let's talk about your potential use cases. There are some interesting possibilities that AI offers to create added value for you even at lower production volumes.

Features of Maddox AI

How exactly does Maddox AI find defective parts?
Maddox AI learns the textures and the characteristics of defects. Once the AI has learned what constitutes a scratch, it can recognise scratches in all variations on the entire component.
Can Maddox AI reliably inspect even at very high production speeds (e.g. several parts per second)?
In the vast majority of cases, high production speed is not a problem. Our models run on our industrial PC at your site, which means that the AI model analyses images within milliseconds. In our experience, it is the part handling rather than the AI evaluation that becomes the possible automation bottleneck.
Can Maddox AI also detect extremely small defects (e.g. 1-3mm)?
Yes, that is usually no problem. We adapt the recording hardware used (camera, lighting, mounting, etc.) completely to your use case. Since our system is manufacturer-independent, we can always provide the optimal camera setup for your individual inspection case.
Can Maddox AI reliably detect defects that occur in completely different places and/or in different variations?
Yes, this is one of the things that makes machine learning (ML) so valuable for quality control. An ML model learns, based on examples, whether a part is OK or NOK. Through this approach, the model derives implicit OK/NOK rules, that do not require explicit programming (e.g. "NOK if scratch on top left"). A cleanly trained model knows the properties of an OK part and therefore reacts very robustly to defect variance or a not quite constant image capturing conditions (e.g. different positions of the product in the image).
Can Maddox AI interact with other automation components such as robots and can the solution be integrated into the clients software infrastrucutre?
This is absolutely possible. Maddox AI can communicate with all common robots and also ERP systems via an interface. By default, we can output our data e.g. via OPCUA, MQTT, REST or TCP-IP. If you have further/different communication requirements, we would be happy to discuss these in more detail in a short call.
Is partial automation in the sense of a cooperative system with a skilled worker also possible?
Partial automation is possible at any time. In addition to a high-performance ML-based inspection system, Maddox AI always comes with an industrial PC and an industrial touchscreen monitor. This setup shows you live, directly at the inspection point, whether a part has been assessed as OK/NOK and supports the skilled worker, who only has to carry out the subsequent work steps (sorting, packing, etc.).

Implementation

How long does the implementation process of the Maddox AI system take?
This depends very much on how quickly we get enough data (pictures of OK/NOK parts). Since Maddox AI is an AI system, data is very important as a basis. We therefore always ask our customers to collect bad parts in advance. We can usually record these parts directly on the installation day and ideally already have enough data to train the model. In this case, the implementation only takes a few days. If we need to collect more data, the system can also run for a few weeks before the implementation is completed.
How much data (=annotated images) does Maddox AI need?
The important thing is not necessarily the amount of data, but its diversity. This means that different appearances of error types are relevant for a good and representative sample of defecets. We do not need many OK images, as the diversity in these images is usually smaller than for NOK images. Accordingly, our focus is on images with defects. We can give you the following rough rule of thumb: In 90% of the cases, 50 images per task (e.g. 50 NOK images of a defect class) are sufficient. In 10% of the cases, another 50 images (i.e. 100 in total) are needed to reliably adapt the Maddox AI system to your use case.
Is Maddox AI compatible with already installed cameras?
That is absolutely possible. Depending on the installed setup and cycle time requirements, the camera can be connected directly to our industrial PC or images can be shared via shared drives or file transfer protocols.
Can Maddox AI integrate with my software systems (MES, PLC, Data-Lake, etc.)?
Yes, this is not a problem. Maddox AI makes the results of the AI available via several protocols that are common in the industry, such as OPC-UA, REST API, MQTT, Modbus TCP or simple digital I/O.

Data Protection

What kind of data is stored and do I as a customer have full control over my data?
We normally store the image data and the associated metadata (AI classification result = OK/NOK, timestamp + product type if applicable). So far, our system is used by large medium-sized companies, but also listed companies. Of course, the data is not stored in a silo, but you as a customer can access it completely at any time and transfer it e.g. to your internal MES system or a data lake.
Does Maddox AI make sure that there are no people visable in the images it takes?
Yes, Maddox AI places great emphasis on this. The Maddox AI system provides the ability to recognise people in the images to blur or black them out before uploading them to the cloud. No one has access to the people's identities - not even we can recover these images.

Ongoing Support

Will I receive new software updates regularly over time?
Yes, Maddox AI is a classic SaaS (software as service) solution. Accordingly, you will receive software updates regularly and free of charge.
Do I have to pay separately for software updates, maintenance and other after-sales services?
No, the software updates, maintenance and other after-sales services are included in the licence fee.
What happens if a new error class occurs after successful implementation?
This is not a problem, we are happy to re-train the Maddox AI system for new error classes free of charge.