This Guidance demonstrates how industrial operations and water utilities can collect and monitor water usage data. It displays how you can improve your water use efficiency through the use of advanced analytics, such as forecasting. By adopting sustainable water management practices and investing in water-efficient technologies, you may reduce your business’s water usage and mitigate some of the operational risks of water scarcity.

Please note: [Disclaimer]

Architecture Diagram

Download the architecture diagram PDF 
  • Overview

  • This architecture diagram provides an overview of the data workflow for collecting, monitoring, and optimizing telemetry data for water use efficiency. For more details about the different stages of the data workflow, open the other tabs.

  • Part 1

  • This architecture diagram provides a more detailed description about data sources and ingestion. Follow the steps in this architecture diagram to deploy Part 1 of the Guidance. 

  • Part 2

  • This architecture diagram provides a more detailed description about storing and processing data in hot and cold storage. Follow the steps in this architecture diagram to deploy Part 2 of the Guidance.

  • Part 3

  • This architecture diagram provides a more detailed description about processing and storing data for visualization and analytics. Follow the steps in this architecture diagram to deploy Part 3 of the Guidance.

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.

  • This Guidance uses AWS IoT Events to continuously monitor Internet of Things (IoT) sensor data for equipment failures. Amazon SNS alerts you when it detects an event.

    Read the Operational Excellence whitepaper 

  • IAM policies and roles protect resources, following the least-privilege principle. It encrypts IoT data in transit using Transport Layer Security (TLS), and it encrypts and protects data at rest using AWS KMS.

    Read the Security whitepaper 

  • This Guidance follows an event-driven architecture with loosely coupled dependencies, making it easy for you to isolate behaviors and increase resilience and agility. You can also use CloudWatch metrics and alarms to monitor the application and send notifications when thresholds breach. Specify an automation runbook in Systems Manager Incident Manager to enable automated responses to critical issues.

    Read the Reliability whitepaper 

  • The services in this Guidance are purpose-built to perform required functions. For example, AWS IoT SiteWise is built to collect, organize, and analyze data from industrial equipment at scale. It reads data from on-site equipment using industrial protocols, such as OPC UA. Timestream is built to store and manage time-series data from telemetry. Forecast is made for time-series forecasting based on machine learning.

    Read the Performance Efficiency whitepaper 

  • This Guidance uses services that scale automatically according to demand, so you only pay for what you use. Timestream manages the life cycle of timeseries data, keeping recent data in memory and moving historical data to a cost-optimized storage tier based on user-defined policies.

    Read the Cost Optimization whitepaper 

  • This Guidance follows an event-driven architecture and uses fully managed services such as Timestream, AWS Glue, and Amazon S3. These services scale automatically according to workload, helping you avoid overprovisioning resources. Additionally, you can use the Amazon S3 Intelligent-Tiering storage class to automatically move data to the most sustainable access tier in Amazon S3.

    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.

Open implementation guide
Open sample code on GitHub

Related Content

[Subject]
[Content Type]

[Title]

[Subtitle]
This [blog post/e-book/Guidance/sample code] demonstrates how [insert short description].

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.

Was this page helpful?

 Feedback