Today, with more than 1.8 million industrial robots in different factories, the quantity of cutting-edge technology in factories around the world has reached a new record. This fast development in the industrial world is representative of the increasing automation and digitalization in factories. In fact, international studies assume that companies will invest an estimated 250 billion dollars in IoT alone by 2020, which is just one of many different technologies in this environment.
Within this context, the German Ministry of Economics and Energy announced different Centers of Competences where the research of the Industry 4.0 paradigm was to be investigated. SmartFactoryKL is a network of more than 50 member organizations from industry and research. These partners perform research and development projects related to Industry 4.0 and the factory of the future. The work ranges from developing their vision and preparing descriptions all the way to industrial implementation.
The production line of this type of solution represents a reconfigurable and flexible system where different technologies from different manufacturers come together. From the connection perspective, it is highly interoperable through universal plug-in connections for electricity, compressed air, and industrial ethernet.
Figure 1. SmartFactoryKL manufacturing station
IBM® participates as a partner in SmartFactoryKL and is responsible for the integration as well as analytics. To develop the solutions, a digital twin of the SmartFactoryKL has been implemented and combined with data from all production modules. The main goal is to achieve the highest possible quality. In this use case, a predictive quality mechanism is going to be implemented to detect anomalies.
Figure 2. Digital twin implementation
Use case environment
A specific advantage of machine learning for manufacturing is the capability to process and interpret both structured and unstructured data from production processes. AI-based systems can identify patterns and anomalies to detect problems automatically. These systems can warn you in time to make suggestions to eliminate the problem or in a best case scenario, eliminate the problems themselves. Raw data is the main asset that is needed to implement this type of solution. Data for this use case is taken directly from one of the production modules, more precisely from the weight measurement module where some random vibrations have been made with the intention of simulating a real case in which one of the modules starts to fail. The extracted data consists of eight different fields that define the use case.
Time: The timestamp of the process
AmplitudeMean: Statistical parameters that measure system vibrations
NumberUnderloads: Parameters that indicate whether the measures have been taken with different numbers of product loads
StabilizationTime: The time it took for the measure to stabilize
StableWeight: Flag that indicates whether the WeightValue is real or calculated
WeightValue: Value of the weight of the product
In this case, the mission of the implemented solution is going to be to detect whether the weight value of the module is reliable, based on the other inputs. If the goal is reached, it indicates that the model is able to predict whether the production line is going to behave as expected based on the vibrations of the machines, which means that the high quality is reached. To define whether the quality of the weight sample is good, a new variable must be created. In this use case, we know that the weight module is working as expected because the
WeightValue parameter has a value of 38 or a value of 0. If it’s 38, it means that you are measuring the normal weight of a unit of product. If it’s 0, it
means that you are measuring an empty space. In this context, this new variable is going to be the target that the model is going to predict. It will have a value of 1 for reliable measurements (38 or 0) and -1 for not reliable measurements.
The solution is implemented in IBM Watson SPSS® Modeler, which enables predictive analytics with various statistical and mathematical techniques for AI modeling or data mining.
Creating an IBM Watson account and SSPS model
IBM Watson SPSS Modeler flows in Watson Studio provide an interactive environment for quickly building machine learning pipelines that flow data from ingestion to transformation to model building and evaluation, without needing any code. To complete this tutorial, you need an IBM Cloud account. You can obtain a free trial account, which gives you access to IBM Watson Studio.
- Create a free IBM Cloud account.
- Sign in to Watson Studio using the account that you created for your IBM Cloud account. If you do not have the Watson Studio service available, you can create an instance, then click Get started.
- Click Create a project, then Create an empty project.
- In the New project window, name the project, then click Create.
- Click Add to project, then Data to import the data that you want to use.
- Click Add to the project, and select Modeler Flow.
Implementing the model
To implement the model:
- Create a Data node. From the node menu on the left, click Import, then Data Asset, and drag it to the flow.
- Open the node, and attach the data from the data assets of your project by clicking Change data asset > Data assets, where your data should be available.
- Click Outputs, and drag the Data Audit node to the flow to get an overview about the data.
- Connect the Data Audit node with the Data node. The Data Audit node displays the fields used for the system and presents different parameters to understand the data. You can configure the node if you want to compute some statistical variables. This is an ideal way to get quick understanding of the input data.
- Click Field Operations, and drag the Derive node to the flow.
- Enter writeWeight_accuracy in the Derived Field Name.
- Select the conditional mode with nominal measurement in the Derive as field.
Define the condition that you want to apply in the model.
- In the
ifstatement, enter (WeightValue >= 37.6) and (WeightValue <= 38.4) or (WeightValue >= -0.4) and (WeightValue <= 0.4).
- In the
then value equalsstatement, write 1.
else value equalsstatement, write -1.
Here, you are selecting the values that you considerate valid, in this case, 0 and 38. This is the quality measure of the model. As you can deduce from the
ifstatement, the value 1 is assigned to valid values and -1 is assigned to values that are not valid.
- In the
- Click Field Operations, and drag, connect, and open a Type node. Configure the role for
Weight_accuracyas target because you want to predict this field.
NumberOverloadsmust be configured as None because
WeightValueis a variable related with the target, and
NumberOverloadshas just one value. Configure the measure for
StabilizationTimeas flag and
- Click Modeling, and drag and connect the Auto Classifier node. Then, run the model. The SPSS software selects and builds the model for you. Then, another green node appears.
Drag and connect to the auto-created node, one Analysis node and one Table node from the output menu to analyze the results. Make sure that you save the model. If you followed these steps exactly, your model should look like the model in the following image.
Figure 3. Model
Conclusions about the data
The most important part of any AI process is the decision-making step based on the knowledge that you are able to extract from the raw data by using the machine learning model. This section gives examples of some conclusions that could be reached due to the implemented solution. To analyze the results, the auto-created green node has an option called “View Model” where all of the model’s features reside. For this specific modeling option, the SSPS software runs different algorithms for you as you can see when you click View Model. For this example, the conclusions have been drawn from the C5.0 algorithm, an algorithm that is based on a decision tree that can be seen by clicking the C5.0 option. The two best tools that you can use to analyze a model is searching features in the decision tree or in the top decision rules. If Auto Classifier results don’t show the C5.0 result, open the node, then click Expert > Select Models.
Global results of the analysis. The first output that is possible is the accuracy with which the model is able to predict the value of
Weight_accuracybased on the other variables. This result means that the model is able to categorize the different samples with a certain value and make the model more reliable. In this example, the accuracy of the prediction is fairly high so the model improves the confidence of the results. This measure doesn’t show whether the accuracy variable is 1 or -1. It shows the likelihood that the model will correctly categorize the specific sample. So, this is a direct parameter that defines the quality of the model itself.
Figure 4. Global results
Another feature that the model brings is that you can observe that the calculated values always give you values that are wrong. This is a good performance indicator in the calculated process. You can see this feature at the beginning of the tree model, where if
StableWeightis False, the measure of the weight is not reliable.
Figure 5. Beginning of the decision tree
Another important feature of the use case that would be interesting to know is the range of values of the different fields that allow the machine to produce a good measurement. For example, this is important because you can limit the vibrations values to this range for the production procedures to ensure a good measurement of the final product. In this case, the
AmplitudeMeanshould be a minor value of 3319.0 to ensure a good behavior with a
StabilizationTimebetween 383 – 1225. This process could be followed to analyze the -1 (or incorrect) measurement.
Figure 6. Top decision rule for +1 prediction
The last thing that is going to be analyzed in this section is the different paths that you can observe in the decision tree. There are many different conclusions that can be extracted from this decision tree, and the one shown in the following image is just a quick example. If you follow the bottom path, you should notice that for samples with an
AmplitudeMeangreater than 7700 you must have an
AmplitudeBandWidthless than 2106 and greater than 745 or less than 166 to be considered as a reliable measure.
Figure 7. Bandwidth analysis
In conclusion, it can be said that the model achieved the original goal, predict the quality of the measurement with a likelihood of 93.38%. The first real implementation of this solution is obviously to predict, based on the vibrations in the production line, if the quality of the measure is as high as expected, extracting the -1 predictions and comparing them with the reliable samples. Another important point is that, as shown previously in these conclusions, we can extract the boundary conditions in which unreliable measurements appear. Being aware of these conditions is possible to force the production line to work under limit parameters that ensure the highest possible productivity while providing us with measures that we know can be trusted.