This Guidance helps industrial energy customers derive near real-time visibility into early indications of equipment failure and equipment performance. This yields additional lead time to drive field action, such as equipment optimization and proactive maintenance planning. Customers can reduce unplanned downtime while optimizing equipment lifecycles, helping them improve maintenance planning and the associated costs. 

Please note: [Disclaimer]

Architecture Diagram

Download the architecture diagram PDF 

Well-Architected Pillars

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.

  • Amazon Managed Service for Apache Flink is capable of detecting schema changes within the sensor data ingested from sources such as Internet of Things (IoT) sensors and SCADA systems. Upon detecting such changes, Amazon SNS is used to send alerts. Promptly addressing these data source schema changes helps to mitigate unexpected behavior in downstream data pipelines.

    Read the Operational Excellence whitepaper 
  • AWS IoT Core facilitates secure communication and access control for IoT devices transmitting sensor data. Additionally, AWS Identity and Access Management (IAM) enables the management of permissions and access controls for the AWS resources utilized within this Guidance. These AWS services collectively protect both the data and resources from unauthorized access.

    Read the Security whitepaper 
  • Kinesis Data Streams provides a durable and highly available data streaming service. Complementing this, Amazon Managed Service for Apache Flink offers a fault-tolerant stream processing system. These AWS services collectively contribute to the overall reliability of this Guidance through continuous data ingestion and processing, even in the face of potential failures.

    Read the Reliability whitepaper 
  • Amazon EMR Serverless furnishes a serverless environment suitable for executing big data analytics workloads, including the training of machine learning models. This AWS service enhances performance efficiency by automatically scaling resources to match the prevailing workload demand, thereby optimizing both resource utilization and overall performance.

    Read the Performance Efficiency whitepaper 
  • Amazon S3 provides cost-effective and scalable object storage to support the data lake of this Guidance. Using Amazon S3 for data storage contributes to cost optimization by eliminating the need to provision and manage storage infrastructure, allowing users to pay only for the storage capacity they consume.

    Read the Cost Optimization whitepaper 
  • Amazon Managed Service for Apache Flink furnishes a managed stream processing service capable of automatically scaling resources in response to fluctuating demand. This AWS service contributes to sustainability by minimizing resource utilization during periods of low demand, thereby reducing the overall environmental impact of this Guidance.

    Read the Sustainability whitepaper 

Implementation Resources

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.

AWS Architecture
Blog

Title

Subtitle
Text.
 
This post demonstrates how...

Disclaimer

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.

Was this page helpful?