This Guidance helps automate the integration of computer vision-based inspection into existing quality management workflows or business processes in SAP. It uses Amazon Lookout for Vision to send defect notifications to SAP quality management, improving first pass yield (FPY) and rolled throughput yield (RTY). This Guidance overcomes the limitations and inaccuracies associated with manual inspection of products, improving overall customer satisfaction.
Please note: [Disclaimer]
Smart cameras at the end of every assembly line capture images of products and push these images to an Amazon Simple Storage Service (Amazon S3) bucket.
Amazon S3 holds the images for model inference. You can schedule or invoke an AWS Lambda function to start the inference.
The Lambda function calls the Amazon Lookout for Vision anomaly model to detect any visual inspection issues with the product.
If an anomaly is detected, the Lambda function accesses Amazon DynamoDB to find look-up information and prepare the payload for SAP Business Technology Platform (BTP).
The Lambda function calls the SAP BTP API management endpoint and records defects in the SAP S/4 HANA system. Optionally, SAP S/4 HANA can be hosted in a separate virtual private cloud (VPC) or even on-premises.
The AWS Well-Architected Framework helps you understand the pros and cons of the decisions you make when building systems in the cloud. The six pillars of the Framework allow you to learn architectural best practices for designing and operating reliable, secure, efficient, cost-effective, and sustainable systems. Using the AWS Well-Architected Tool, available at no charge in the AWS Management Console, you can review your workloads against these best practices by answering a set of questions for each pillar.
The architecture diagram above is an example of a Solution created with Well-Architected best practices in mind. To be fully Well-Architected, you should follow as many Well-Architected best practices as possible.
Serverless services, such as Amazon S3, DynamoDB, and Lambda use AWS CloudTrail and Amazon CloudWatch to log and analyze application metrics. You can also send Amazon Virtual Private Cloud (Amazon VPC) flow logs to CloudWatch to analyze packet flow from network interfaces.
Use Secrets Manager with key rotation policies to store authentication information related to SAP. You can encrypt data at rest using customer-managed AWS server-side keys.
You can independently monitor each architecture layer and components with CloudWatch key performance indicators (KPIs). CloudWatch also helps you enable automated resolution for issues that arise using managed services.
Considering this is an asynchronous workload, the cold start latency of an individual Lambda function is less significant than the overall performance in aggregate. You can filter Amazon S3 events on prefix and suffix patterns, enabling you to filter on only certain object keys. The SAP BTP API follows the best practices from SAP for a performance optimized CRUD operation into the SAP backend.
With serverless technologies, you pay only for the resources you use. Using Lookout for Vision, you can increase or decrease your defect detection capacity by requesting or removing additional inference units, depending on the demands of your manufacturing line.
Serverless services help you you maximize overall resource utilization, because compute is only used as needed. The efficient use of serverless resources reduces the overall energy required to operate the workload. You can also use the AWS Billing Conductor carbon footprint tool to calculate and track the environmental impact of the workload over time at an account-, Region-, and service-level.
A detailed guide is provided to experiment and use within your AWS account. Each stage of building the Guidance, including deployment, usage, and cleanup, is examined to prepare it for deployment.
The sample code is a starting point. It is industry validated, prescriptive but not definitive, and a peek under the hood to help you begin.
The sample code; software libraries; command line tools; proofs of concept; templates; or other related technology (including any of the foregoing that are provided by our personnel) is provided to you as AWS Content under the AWS Customer Agreement, or the relevant written agreement between you and AWS (whichever applies). You should not use this AWS Content in your production accounts, or on production or other critical data. You are responsible for testing, securing, and optimizing the AWS Content, such as sample code, as appropriate for production grade use based on your specific quality control practices and standards. Deploying AWS Content may incur AWS charges for creating or using AWS chargeable resources, such as running Amazon EC2 instances or using Amazon S3 storage.
References to third-party services or organizations in this Guidance do not imply an endorsement, sponsorship, or affiliation between Amazon or AWS and the third party. Guidance from AWS is a technical starting point, and you can customize your integration with third-party services when you deploy the architecture.