Use machine learning to detect anomalies and predict downtime with Amazon Timestream and Amazon Lookout for Equipment

The last decade of the Industry 4.0 revolution has shown the value and importance of machine learning (ML) across verticals and environments, with more impact on manufacturing than possibly any other application. Organizations implementing a more automated, reliable, and cost-effective Operational Technology (OT) strategy have led the way, recognizing the benefits of ML in predicting assembly line failures to avoid costly and unplanned downtime. Still, challenges remain for teams of all sizes to quickly, and with little effort, demonstrate the value of ML-based anomaly detection in order to persuade management and finance owners to allocate the budget required to implement these new technologies. Without access to data scientists for model training, or ML specialists to deploy solutions at the local level, adoption has seemed out of reach for teams on the factory floor.

Now, teams that collect sensor data signals from machines in the factory can unlock the power of services like Amazon Timestream, Amazon Lookout for Equipment, and AWS IoT Core to easily spin up and test a fully production-ready system at the local edge to help avoid catastrophic downtime events. Lookout for Equipment uses your unique ML model to analyze incoming sensor data in real time and accurately identify early warning signs that could lead to machine failures. This means you can detect equipment abnormalities with speed and precision, quickly diagnose issues, take action to reduce expensive downtime, and reduce false alerts. Response teams can be alerted with specific pinpoints to which sensors are indicating the issue, and the magnitude of impact on the detected event.

In this post, we show you how you can set up a system to simulate events on your factory floor with a trained model and detect abnormal behavior using Timestream, Lookout for Equipment, and AWS Lambda functions. The steps in this post emphasize the AWS Management Console UI, showing how technical people without a developer background or strong coding skills can build a prototype. Using simulated sensor signals will allow you to test your system and gain confidence before cutting over to production. Lastly, in this example, we use Amazon Simple Notification Service (Amazon SNS) to show how teams can receive notifications of predicted events and respond to avoid catastrophic effects of assembly line failures. Additionally, teams can use Amazon QuickSight for further analysis and dashboards for reporting.

Solution overview

To get started, we first collect a historical dataset from your factory sensor readings, ingest the data, and train the model. With the trained model, we then set up IoT Device Simulator to publish MQTT signals to a topic that will allow testing of the system to identify desired production settings before production data is used, keeping costs low.

The following diagram illustrates our solution architecture.

The workflow contains the following steps:

1. Use sample data to train the Lookout for Equipment model, and the provided labeled data to improve model accuracy. With a sample rate of 5 minutes, we can train the model in 20–30 minutes.
2. Run an AWS CloudFormation template to enable IoT Simulator, and create a simulation to publish an MQTT topic in the format of the sensor data signals.
3. Create an IoT rule action to read the MQTT topic an send the topic payload to Timestream for storage. These are the real-time datasets that will be used for inferencing with the ML model.
4. Set up a Lambda function triggered by Amazon EventBridge to convert data into CSV format for Lookout for Equipment.
5. Create a Lambda function to parse Lookout for Equipment model inferencing output file in Amazon Simple Storage Service (Amazon S3) and, if failure is predicted, send an email to the configured address. Additionally, use AWS Glue, Amazon Athena, and QuickSight to visualize the sensor data contributions to the predicted failure event.

Prerequisites

You need access to an AWS account to set up the environment for anomaly detection.

Simulate data and ingest it into the AWS Cloud

To set up your data and ingestion configuration, complete the following steps:

1. Download the training file subsystem-08_multisensor_training.csv and the labels file labels_data.csv. Save the files locally.
2. On the Amazon S3 console in your preferred Region, create a bucket with a unique name (for example, l4e-training-data), using the default configuration options.
3. Open the bucket and choose Upload, then Add files.
   
4. Upload the training data to a folder called /training-data and the label data to a folder called /labels.

Next, you create the ML model to be trained with the data from the S3 bucket. To do this, you first need to create a project.

5. On the Lookout for Equipment console, choose Create project.
   
6. Name the project and choose Create project.
7. On the Add dataset page, specify your S3 bucket location.
8. Use the defaults for Create a new role and Enable CloudWatch Logs.
9. Choose By filename for Schema detection method.
10. Choose Start ingestion.

Ingestion takes a few minutes to complete.

11. When ingestion is complete, you can review the details of the dataset by choosing View Dataset.
12. Scroll down the page and review the Details by sensor section.
13. Scroll to the bottom of the page to see that the sensor grade for data from three of the sensors is labeled Low.
14. Select all the sensor records except the three with Low grade.
15. Choose Create model.
    
16. On the Specify model details page, give the model a name and choose Next.
17. On the Configure input data page, enter values for the training and evaluation settings and a sample rate (for this post, 1 minute).
18. Skip the Off-time detection settings and choose Next.
    
19. On the Provide data labels page, specify the S3 folder location where the label data is.
20. Select Create a new role.
21. Choose Next.
    
22. On the Review and train page, choose Start training.

With a sample rate of 5 minutes, the model should take 20–30 minutes to build.

While the model is building, we can set up the rest of the architecture.

Simulate sensor data

1. Choose Launch Stack to launch a CloudFormation template to set up the simulated sensor signals using IoT Simulator.
2. After the template has launched, navigate to the CloudFormation console.
3. On the Stacks page, choose IoTDeviceSimulator to see the stack details.
4. On the Outputs tab, find the ConsoleURL key and the corresponding URL value.
   
5. Choose the URL to open the IoT Device Simulator login page.
6. Create a user name and password and choose SIGN IN.
7. Save your credentials in case you need to sign in again later.
   
8. From the IoT Device Simulator menu bar, choose Device Types.
9. Enter a device type name, such as My_testing_device.
10. Enter an MQTT topic, such as factory/line/station/simulated_testing.
11. Choose Add attribute.
    
12. Enter the values for the attribute signal5, as shown in the following screenshot.
13. Choose Save.
    
14. Choose Add attribute again and add the remaining attributes to match the sample signal data, as shown in the following table.

15. On the Simulations tab, choose Add Simulation.
16. Give the simulation a name.
17. Specify Simulation type as User created, Device type as the recently created device, Data transmission interval as 60, and Data transmission duration as 3600.
18. Finally, start the simulation you just created and see the payloads generated on the Simulation Details page by choosing View.

Now that signals are being generated, we can set up IoT Core to read the MQTT topics and direct the payloads to the Timestream database.

19. On the IoT Core console, under Message Routing in the navigation pane, choose Rules.
20. Choose Create rule.
21. Enter a rule name and choose Next.
22. Enter the following SQL statement to pull all the values from the published MQTT topic:

SELECT signal5, signal6, signal7, signal8, signal48, signal49, signal78, signal109, signal120, signal121 FROM 'factory/line/station/simulated_testing'

23. Choose Next.
24. For Rule actions, search for the Timestream table.
25. Choose Create Timestream database.

A new tab opens with the Timestream console.

26. Select Standard database.
27. Name the database sampleDB and choose Create database.

You’re redirected to the Timestream console, where you can view the database you created.

28. Return to the IoT Core tab and choose sampleDB for Database name.
29. Choose Create Timestream table to add a table to the database where the sensor data signals will be stored.
30. On the Timestream console Create table tab, choose sampleDB for Database name, enter signalTable for Table name, and choose Create table.
31. Return to the IoT Core console tab to complete the IoT message routing rule.
32. Enter Simulated_signal for Dimensions name and 1 for Dimensions value, then choose Create new role.

33. Name the role TimestreamRole and choose Next.
34. On the Review and create page, choose Create.

You have now added a rule action in IoT Core that directs the data published to the MQTT topic to a Timestream database.

Query Timestream for analysis

To query Timestream for analysis, complete the following steps:

1. Validate the data is being stored in the database by navigating to the Timestream console and choosing Query Editor.
2. Choose Select table, then choose the options menu and Preview data.
3. Choose Run to query the table.

Now that data is being stored in the stream, you can use Lambda and EventBridge to pull data every 5 minutes from the table, format it, and send it to Lookout for Equipment for inference and prediction results.

4. On the Lambda console, choose Create function.
5. For Runtime, choose Python 3.9.
6. For Layer source, select Specify an ARN.
7. Enter the correct ARN for your Region from the aws pandas resource.
8. Choose Add.

9. Enter the following code into the function and edit it to match the S3 path to a bucket with the folder /input (create a bucket folder for these data stream files if not already present).

This code uses the awswrangler library to easily format the data in the required CSV form needed for Lookout for Equipment. The Lambda function also dynamically names the data files as required.

import json
import boto3
import awswrangler as wr
from datetime import datetime
import pytz def lambda_handler(event, context): # TODO implement UTC = pytz.utc my_date = datetime.now(UTC).strftime('%Y-%m-%d-%H-%M-%S') print(my_date) df = wr.timestream.query('SELECT time as Timestamp, max(case when measure_name = \'signal5\' then measure_value::double/1000 end) as "signal-005", max(case when measure_name = \'signal6\' then measure_value::double/1000 end) as "signal-006", max(case when measure_name = \'signal7\' then measure_value::double/1000 end) as "signal-007", max(case when measure_name = \'signal8\' then measure_value::double/1000 end) as "signal-008", max(case when measure_name = \'signal48\' then measure_value::double/1000 end) as "signal-048", max(case when measure_name = \'signal49\' then measure_value::double/1000 end) as "signal-049", max(case when measure_name = \'signal78\' then measure_value::double/1000 end) as "signal-078", max(case when measure_name = \'signal109\' then measure_value::double/1000 end) as "signal-109", max(case when measure_name = \'signal120\' then measure_value::double/1000 end) as "signal-120", max(case when measure_name = \'signal121\' then measure_value::double/1000 end) as "signal-121" FROM "<YOUR DB NAME>"."<YOUR TABLE NAME>" WHERE time > ago(5m) group by time order by time desc') print(df) s3path ="s3://<EDIT-PATH-HERE>/input/<YOUR FILE NAME>_%s.csv" % my_date wr.s3.to_csv(df, s3path, index=False) return { 'statusCode': 200, 'body': json.dumps('Hello from Lambda!') }

10. Choose Deploy.
11. On the Configuration tab, choose General configuration.
12. For Timeout, choose 5 minutes.
13. In the Function overview section, choose Add trigger with EventBridge as the source.
14. Select Create a new rule.
15. Name the rule eventbridge-cron-job-lambda-read-timestream and add rate(5 minutes) for Schedule expression.
16. Choose Add.
    
17. Add the following policy to your Lambda execution role:

    { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": "s3:PutObject", "Resource": "arn:aws:s3:::<YOUR BUCKET HERE>/*" }, { "Effect": "Allow", "Action": [ "timestream:DescribeEndpoints", "timestream:ListTables", "timestream:Select" ], "Resource": "*" } ]
    }

Predict anomalies and notify users

To set up anomaly prediction and notification, complete the following steps:

1. Return to the Lookout for Equipment project page and choose Schedule inference.
2. Name the schedule and specify the model created previously.
3. For Input data, specify the S3 /input location where files are written using the Lambda function and EventBridge trigger.
4. Set Data upload frequency to 5 minutes and leave Offset delay time at 0 minutes.
5. Set an S3 path with /output as the folder and leave other default values.
6. Choose Schedule inference.

After 5 minutes, check the S3 /output path to verify prediction files are created. For more information about the results, refer to Reviewing inference results.

Finally, you create a second Lambda function that triggers a notification using Amazon SNS when an anomaly is predicted.

7. On the Amazon SNS console, choose Create topic.
8. For Name, enter emailnoti.
9. Choose Create.
10. In the Details section, for Type, select Standard.
11. Choose Create topic.
    
12. On the Subscriptions tab, create a subscription with Email type as Protocol and an endpoint email address you can access.
13. Choose Create subscription and confirm the subscription when the email arrives.
14. On the Topic tab, copy the ARN.
    
15. Create another Lambda function with the following code and enter the ARN topic in MY_SYS_ARN:

    import boto3
    import sys
    import logging
    import os
    import datetime
    import csv
    import json MY_SNS_TOPIC_ARN = 'MY_SNS_ARN'
    client = boto3.client('s3')
    logger = logging.getLogger()
    logger.setLevel(logging.DEBUG)
    sns_client = boto3.client('sns')
    lambda_tmp_dir = '/tmp' def lambda_handler(event, context): for r in event['Records']: s3 = r['s3'] bucket = s3['bucket']['name'] key = s3['object']['key'] source = download_json(bucket, key) with open(source, 'r') as content_file: content = json.load(content_file) if content['prediction'] == 1 : Messages = 'Time: ' + str(content['timestamp']) + '\n' + 'Equipment is predicted failure.' + '\n' + 'Diagnostics: ' # Send message to SNS for diag in content['diagnostics']: Messages = Messages + str(diag) + '\n' sns_client.publish( TopicArn = MY_SNS_TOPIC_ARN, Subject = 'Equipment failure prediction', Message = Messages ) def download_json(bucket, key): local_source_json = lambda_tmp_dir + "/" + key.split('/')[-1] directory = os.path.dirname(local_source_json) if not os.path.exists(directory): os.makedirs(directory) client.download_file(bucket, key.replace("%3A", ":"), local_source_json) return local_source_json

16. Choose Deploy to deploy the function.

When Lookout for Equipment detects an anomaly, the prediction value is 1 in the results. The Lambda code uses the JSONL file and sends an email notification to the address configured.

17. Under Configuration, choose Permissions and Role name.
18. Choose Attach policies and add AmazonS3FullAccess and AmazonSNSFullAccess to the role.
19. Finally, add an S3 trigger to the function and specify the /output bucket.

After a few minutes, you will start to see emails arrive every 5 minutes.

Visualize inference results

After Amazon S3 stores the prediction results, we can use the AWS Glue Data Catalog with Athena and QuickSight to create reporting dashboards.

1. On the AWS Glue console, choose Crawlers in the navigation pane.
2. Choose Create crawler.
3. Give the crawler a name, such as inference_crawler.
4. Choose Add a data source and select the S3 bucket path with the results.jsonl files.
5. Select Crawl all sub-folders.
6. Choose Add an S3 data source.
7. Choose Create new IAM role.
8. Create a database and provide a name (for example, anycompanyinferenceresult).
9. For Crawler schedule, choose On demand.
10. Choose Next, then choose Create crawler.
11. When the crawler is complete, choose Run crawler.

12. On the Athena console, open the query editor.
13. Choose Edit settings to set up a query result location in Amazon S3.
14. If you don’t have a bucket created, create one now via the Amazon S3 console.
15. Return to the Athena console, choose the bucket, and choose Save.
16. Return to the Editor tab in the query editor and run a query to select * from the /output S3 folder.
17. Review the results showing anomaly detection as expected.

18. To visualize the prediction results, navigate to the QuickSight console.
19. Choose New analysis and New dataset.
20. For Dataset source, choose Athena.
21. For Data source name, enter MyDataset.
22. Choose Create data source.
23. Choose the table you created, then choose Use custom SQL.
    
24. Enter the following query:

    with dataset AS (SELECT timestamp,prediction, names FROM "anycompanyinferenceresult"."output" CROSS JOIN UNNEST(diagnostics) AS t(names))
    SELECT SPLIT_PART(timestamp,'.',1) AS timestamp, prediction, SPLIT_PART(names.name,'\',1) AS subsystem, SPLIT_PART(names.name,'\',2) AS sensor, names.value AS ScoreValue
    FROM dataset

25. Confirm the query and choose Visualize.
26. Choose Pivot table.
27. Specify timestamp and sensor for Rows.
28. Specify prediction and ScoreValue for Values.
    
29. Choose Add Visual to add a visual object.
30. Choose Vertical bar chart.
31. Specify Timestamp for X axis, ScoreValue for Value, and Sensor for Group/Color.
32. Change ScoreValue to Aggregate:Average.
    

Clean up

Failure to delete resources can result in additional charges. To clean up your resources, complete the following steps:

1. On the QuickSight console, choose Recent in the navigation pane.
2. Delete all the resources you created as part of this post.
3. Navigate to the Datasets page and delete the datasets you created.
4. On the Lookout for Equipment console, delete the projects, datasets, models, and inference schedules used in this post.
5. On the Timestream console, delete the database and associated tables.
6. On the Lambda console, delete the EventBridge and Amazon S3 triggers.
7. Delete the S3 buckets, IoT Core rule, and IoT simulations and devices.

Conclusion

In this post, you learned how to implement machine learning for predictive maintenance using real-time streaming data with a low-code approach. You learned different tools that can help you in this process, using managed AWS services like Timestream, Lookout for Equipment, and Lambda, so operational teams see the value without adding additional workloads for overhead. Because the architecture uses serverless technology, it can scale up and down to meet your needs.

For more data-based learning resources, visit the AWS Blog home page.

About the author

Matt Reed is a Senior Solutions Architect in Automotive and Manufacturing at AWS. He is passionate about helping customers solve problems with cool technology to make everyone’s life better. Matt loves to mountain bike, ski, and hang out with friends, family, and dogs and cats.

Read more about this on: AWS