Darwin - Identifying causes of performance losses

Uncover bottlenecks in your production lines and machines and create transparency about the causes of performance losses - down to the signal level.

Advantages

Identify the causes of performance losses

Our analysis algorithms get to the root cause of performance losses of your complex, automated production lines and machines

Optimize production lines in the right place

Only if you know the real bottleneck of a linked production line, you can increase the output in a targeted way.

Darwin continuously determines the real bottleneck based on various factors and thus helps you to perform focused optimizations:

  • Breakdown of the real cycle and process times of the individual production stations
  • Combination with states of production stations incl. waiting and blocking situations

= Increase of the output of production lines

Identify the cause of performance losses

When looking for the cause of performance losses, the devil is often in the details. A multitude of influencing factors makes it difficult to identify the real cause of cycle time deviations.

Darwin analyzes manufacturing operations at the process step level and allows you to drill down to get to the root cause of timing deviations:

  • Process step analysis as drill-down of process time deviations
  • Benchmark of similar production lines and machines to identify potential for optimization

= Reduction of performance losses (short stops, process fluctuations)

Detect changes in your production lines and machines at an early stage

A manufacturing process is subject to a variety of influencing factors. If these change and negatively influence the manufacturing process, it is important to react quickly.

With our trend analysis, you can reliably detect changes in process times and in malfunction behavior and react to them quickly:

  • Identification of trends in disturbance behavior and process times
  • Notification about new trends

= Optimization through targeted, rapid rectification of deviations

Impact

Darwin's Added Value

6-18%

Reduction of cycle time per machine

Up to 38%

Reduction of the average productivity variation

10 - 30%

Shortening the start-up and relocation phase

Darwin solves these production problems

  • No transparency about actual & ideal cycle time behavior
  • Causes of output fluctuations that are difficult to identify due to complex, fully automated manufacturing processes
  • Output increase only possible with multiple resources
  • Differences in Productivity Among Similar Machines
  • High fixed and unit costs for fully automated machines
Features

All features of Darwin

Identification of trends

Detection of malfunction and process time deviations
Learn more

Identification of trends

A manufacturing process is subject to a variety of influencing factors. If these change and negatively influence the manufacturing process, it is important to react quickly.

With our trend analysis, you can reliably detect changes in process times and in malfunction behavior and react to them quickly:

  • Identification of trends in disturbance behavior and process times
  • Notification about new trends

Benchmark of similar machines

Detailed process step comparison of similar machines
Learn more

Benchmark of similar machines

Similar manufacturing machines often have different levels of productivity. Due to the complexity of the manufacturing process, it can be difficult to identify the cause of different KPI values.

With the machine benchmark, you can compare the performance of similar machines in detail at process step level to identify optimization potential.

Downtime statistics

Statistics on downtimes and their causes
Learn more

Downtime statistics

In order to optimize a production line in a targeted manner, you need good information at hand that clearly identifies problem areas.

To do this, use the statistics on faults to understand which faults caused how much downtime over time. Get detailed statistics to understand the disturbance behavior in detail.

Process time statistics

Statistics on cycle and process times
Learn more

Process time statistics

Only if you know the real bottleneck of a linked production line, you can increase the output in a targeted way.

Darwin breaks down the real cycle and process times of the individual manufacturing stations, enabling analysis of the performance of the individual components of a manufacturing plant.

Process Step Analysis

Detailed analysis of manufacturing processes
Learn more

Process Step Analysis

When looking for the cause of performance losses, the devil is often in the details. A multitude of influencing factors makes it difficult to identify the real cause of cycle time deviations.

Darwin analyzes manufacturing operations at the process step level and allows you to drill down to get to the root cause of timing deviations.

State statistics

Statistics on machine states
Learn more

State statistics

Only if you know the real bottleneck of a linked production line, you can increase the output in a targeted way.

Darwin determines the states of production components and thus enables, for example, the waiting and blocking behavior of production stations to be analyzed.

KPIs

Continuous generation of key production figures
Learn more

KPIs

Key performance indicators are an important component of manufacturing optimization to identify problem areas.

Darwin continuously generates key figures for the considered production lines and machines. You can display and group these flexibly to generate the statements that are appropriate for your use case.

Action Tracker

Plan, document, and verify optimization measures
Learn more

Action Tracker

Plan, document, and verify optimization measures.

Most factories have a continuous improvement process in place to increase the efficiency of their production lines and machines. Darwin gives this process a permanent place—right next to the data on which it is based.

Darwin directly links actions to analysis: With a single click, last week’s error statistics are used to generate an optimization measure, including a description of the planned change and a comment feature for team review. After implementation, Darwin provides a before-and-after comparison and shows whether the change actually had an effect.

The board view groups tasks by label, production unit, or area of responsibility, making it clear at a glance who is responsible for what.

‍

‍

Interface

API
Browser

Security

Encrypted TLS Communication
All communication is encrypted with TLS
Role-based access control (RBAC)
User management with dedicated roles and permissions management
Single sign-on
Single sign-on with Microsoft 365

Add-ons

System integrations (ETL)
Integration into system landscape through ETL processes
On-Premise Deployment
Optional on-premise deployment
Success Stories

What our customers & partners say

Shannon® & Darwin at M10 Solar Equipment

  • Virtual commissioning of a fully automated solar module production plant with plus10 tools (hardware-in-the-loop simulation) with seven newly developed processes
  • Full transparency regarding system behavior and optimization potential in terms of availability and performance
  • Faster start-up and smooth handover to operating personnel thanks to virtually trained plus10 tools

Impact: Rapid ramp-up and full transparency into system performance

Darwin at Schwarzkopf

  • Fully automated and interlinked filling and packaging line for consumer goods (0.17 sec. cycle time)
  • Detailed transparency of downtime per shift at station level for effective shift handover and basis for conceptual optimization
  • Faster root cause identification in the optimization process and in the event of downtimes thanks to visualization of the signal behavior
Learn more

Impact = up to 17% potential for throughput increase identified

Darwin at Haselmeier

  • Fully automated assembly line for the production of self-injection pens (cycle time under 5 seconds)
  • Identification and quantification of the causes for availability and performance degradation
  • Trend analysis on fault occurrence and problem resolution times for each individual cause of loss
Learn more
Products used:

Impact = Uncovering of OEE potential greater than 10%.

Contact now

  • Personal Product Presentation with Live Demo
  • Initial Assessment of Your Use Case
  • Help with Calculating Your ROI
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
FAQ

Do you have questions? We have answers.

And if you have any further questions, please feel free to contact us.

Do we need Darwin or Hopper for predictive maintenance?

These are often confused because the terms are used in different contexts. Predictive Maintenance refers to the technical availability of the machine— Darwin and Shannon® are the right tools for this. Hopper is quality-oriented, i.e., Predictive Quality. We make this decision based on your OEE breakdown: Where are your biggest losses today? For automated assembly and manufacturing lines, starting with Shannon® usually offers the greatest leverage; however, the decisive factor is what most significantly impacts your production during multi-shift operations.

Can trends be used as an alternative to traditional predictive maintenance? 

Yes. Trends can be identified and analyzed from the collected asset data, and these have proven effective in practice as a pragmatic approach to predictive maintenance—without the effort required by traditional condition monitoring projects.

What are the IT requirements for Darwin? 

The same as for Shannon®: a local virtual machine for the DataCollector, outbound data traffic via port 443 to the plus10 backend, targeted firewall rules allowing access to the control addresses, user management via LDAP, and the option to operate as Software-as-a-Service within the EU or entirely on-premises.

How long are the raw signals recorded by Darwin stored?

The high-frequency raw signals (e.g., step chain signals) are stored for three months. This allows users to go back to any point in time within the last three months in the plus10 SignalViewer—for example, to analyze in detail a malfunction that occurred during the last night shift the following day.