Welcome to ELAM Solutions Helpcenter

All topics /
Categories /
ELAM Analytics
/
Products

Products

Published:
May 30, 2024
Updated:
May 23, 2024
From:
Waldemar

Table of Content

This article describes what data can be evaluated on the Products page. Since variants in ELAM are specific manifestations of a product, the generic term products is also used in this article.

Generally speaking, ELAM saves all captured data when the operator works with the active flowchart in the ELAM Assistant and acknowledges steps. All entries, acknowledgements and measured values are always saved for the respective variant and used for the statistics. Documents opened at runtime in the ELAM Assistant document viewer are not included in the statistics.

Completed products by status

The pie chart Completed Products by Status shows what % of variants were completed with the following statuses:

Status OK - show which variants have been completed with the status OK. These are products that have been successfully completed.

Status NOK - Shows which variants have been completed with the status NOK. These are defective products that are not in order and count as scrap, for example.

Status Unknown - Indicates which variants are completed with the status Unknown. These are products that have been completed, but the last step has neither OK nor NOK status.

Note: Please note that as a setter in the flowchart you have to specify exactly with which status your product should be completed by the completion step with OK or NOK. Unless the last step in the flowchart is a completion step, your product will be completed with the status Unknown.

Process quality

The average process quality shows you the percentage of individual steps in the flowchart that are error-free on the first process run and did not require any rework from the operator. For each completed variant, a separate process quality is also calculated and displayed in the list of completed products.

Formula for the calculation of process quality per variant

Sum of steps with status OK / sum of all steps * 100 = process quality (%)

Formula for calculating the average process quality

Total process quality (%) per variant / total of all variants = average process quality (%)

First Pass

The first pass or first yield shows you the percentage of variants that have already passed through the first process run without errors and have not required any rework. As soon as a single work step has the status NOK or Manual OK, the First Pass for the variant is false.

List of completed products

The list of completed products gives you an overview of all completed variants. You can set your own filters per column and search for specific information. Hiding columns is currently not supported.

Definition of the information in the list
  1. Finished on - Indicates when the flowchart was completed in the ELAM Assistant.
  2. Started on - Indicates when the flowchart was started for the first time in the ELAM Assistant.
  3. Serial number - Indicates whether a serial number was entered in the ELAM Assistant when a variant was started.
  4. Order number - Indicates whether an order number was entered in the ELAM Assistant at the start of a variant.
  5. Variant-ID - Specifies the unique variant ID stored by the installer in the administration
  6. Status - Indicates the status (OK / NOK / Unknown) of the variant specified by the setter in the flowchart.
  7. Processing time - Indicates the calculated time when a flowchart was started and ended.
  8. Inactive time - Indicates the calculated time for a flowchart that was canceled by the operator in the ELAM Assistant.
  9. Assembly time - Specifies the calculated time for a flowchart that is displayed in the ELAM Assistant.
    •  Formula: Lead time - inactive time = assembly time
  10. Median deviation - Indicates the median deviation of the assembly time across all products in the list as a percentage.
    • Blauer Indikator - The variants were completed faster than the median.
    • Roter Indikator - The variants were completed more slowly than the median.
  11. Process quality - Indicates the percentage of steps in the flowchart that were completed with status OK.
    • Formula: Number of steps with OK status / sum of all steps *100 = process quality

Median deviation vs. arithmetic deviation

In ELAM Solutions, the assembly time is calculated for each product, which indicates how long a flowchart was actively displayed in the ELAM Assistant. This assembly time is an important indicator of the efficiency and effort required to assemble a product. To enable a meaningful analysis of these times, we calculate the median deviation of the times as a percentage across all products in the list. In this article, we explain why the median deviation is a better choice than the arithmetic deviation and what insights our customers can draw from it.

What is the median deviation?

The median deviation measures how much the assembly times deviate from the median (i.e. the middle value). The median is the value that lies in the middle of an ordered data series, i.e. 50% of the values are smaller and 50% of the values are larger than the median. The median deviation therefore indicates the average deviation of the assembly times from the median.‍

Why is the median deviation better than the arithmetic deviation?
  1. Robustness against outliers
    • Median deviation: The median is robust against extreme values or outliers. This means that individual extremely high or low assembly times hardly affect the median. The median deviation therefore provides a more realistic representation of typical deviations.
    • Arithmetic deviation: This method uses the average (arithmetic mean), which is strongly influenced by outliers. Extremely high or low assembly times can distort the average and lead to an incorrect interpretation of the data.
  2. Representativeness
    • Median deviation: As the median represents the middle position of the data series, the median deviation is more representative of the majority of the data. It shows how most assembly times deviate from the central value.
    • Arithmetic deviation: The average considers all values equally, which means that unusually high or low values can strongly influence the result, even if these values are rare.

Insights for you as a customer

By using the median deviation instead of the arithmetic deviation, our customers receive a more accurate and meaningful analysis of assembly times. Here are some concrete benefits:

  1. Better basis for decision-making
    • You can make more precise statements about the typical assembly time and make more informed decisions about process optimization and resource planning.
  2. Recognizing potential for improvement
    • By identifying typical deviations from the median, customers can identify specific areas where assembly times can be optimized without extreme outliers distorting the overall picture.
  3. More reliable benchmarking data
    • For benchmarking and comparing assembly times of different products, the median deviation offers more reliable and stable key figures that are less susceptible to distortions caused by atypical values.
  4. Improved transparency and understanding
    • An analysis based on the median deviation is more intuitive and easier to understand for many users, as it has a clear reference to the central tendency of the data and better reflects the actual distribution.

In summary, the median deviation enables a more robust and representative analysis of assembly times, which leads to a better basis for decision-making and optimization options. Our customers benefit from a more accurate and reliable assessment of their processes.

FAQ

How exactly do the filter options work and what information is most relevant?
  • The most relevant filter settings are by time period, variant and status.

What are the most common reasons for the failure of a First Pass?
  • Operators most frequently repeat tightening steps in the wizard because screws could not be tightened correctly.

How exactly is the "Unknown" status determined and what are the most common causes?
  • The status is determined if the very last step is not a completion step with the status OK or NOK. As a result, the software does not know with which status the flowchart or the product should be completed. The error is in the flowchart setup.