[text]
This Guidance provides real-time visibility into field-critical workflows that help field personnel complete job tasks accurately, safely, and efficiently. In the energy manufacturing industry, the management of both daily field activities and planned maintenance outages are critical for maintaining reliable operations. Every manufacturing site needs access to timely information to help ensure field safety, business profitability, and operational excellence. This Guidance provides a way for field workers to visualize, consume, collect, and collaborate on operational data, as part of daily rounds, maintenance, construction, inspection, and turnaround workloads.
Please note: [Disclaimer]
Architecture Diagram
[text]
Step 1
The industrial data lake extends data availability and capture outside of the control room and into the facility or field. It turns this data into usable, contextualized datasets using Amazon Simple Storage Service (Amazon S3) and AWS Glue for field use.
Step 2
System of record data from equipment, work order, asset specification, and other customer databases are synchronized with AWS and AWS ISV Partner software-as-a-service (SaaS) platforms.
Step 3
The AWS Partner operational technology (OT) gateway device extracts sensor data from historians with telemetry from programmable logic controllers (PLCs) and distributed control systems (DCS). AWS IoT Core ingests the data into the AWS Cloud along with Internet of Things (IoT) sensor data.
Step 4
No/low code applications from AWS ISV Partners simplify mobile device app development, configuration, distribution, and administration for field access.
Step 5
Amazon API Gateway and AWS Lambda send or receive data updates between work processes and equipment to synchronize data between the AWS industrial data lake and AWS ISV Partner platforms.
Step 6
Amazon QuickSight or AWS Partner business intelligence (BI) applications visualize and generate reports on data based on customer preference. QuickSight focuses on business key performance indicators (KPIs) that you can consolidate across multiple AWS Partner and external data sources.
Step 7
Notifications from Amazon Simple Notification Service (Amazon SNS) keep dispatchers and field technicians aware of status and changes.
Step 1
The industrial data lake extends data availability and capture outside of the control room and into the facility or field. It turns this data into usable, contextualized datasets using Amazon Simple Storage Service (Amazon S3) and AWS Glue for field use.
Step 2
System of record data from equipment, work order, asset specification, and other customer databases are synchronized with AWS and AWS ISV Partner software-as-a-service (SaaS) platforms.
Step 3
The AWS Partner operational technology (OT) gateway device extracts sensor data from historians with telemetry from programmable logic controllers (PLCs) and distributed control systems (DCS). AWS IoT Core ingests the data into the AWS Cloud along with Internet of Things (IoT) sensor data.
Step 4
No/low code applications from AWS ISV Partners simplify mobile device app development, configuration, distribution, and administration for field access.
Step 5
Amazon API Gateway and AWS Lambda send or receive data updates between work processes and equipment to synchronize data between the AWS industrial data lake and AWS ISV Partner platforms.
Step 6
Amazon QuickSight or AWS Partner business intelligence (BI) applications visualize and generate reports on data based on customer preference. QuickSight focuses on business key performance indicators (KPIs) that you can consolidate across multiple AWS Partner and external data sources.
Step 7
Notifications from Amazon Simple Notification Service (Amazon SNS) keep dispatchers and field technicians aware of status and changes.
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.
-
Operational ExcellenceRead the Operational Excellence whitepaper
Amazon CloudWatch automatically captures activity, logs, and metrics for AWS services, including Amazon Athena, AWS Glue, Lambda, and Amazon API Gateway. You can use this logged data to understand near real-time health of data integration and validate data quality. Having a centralized repository for logs provides a simple way to create operational dashboards that monitor the Guidance from end-to-end.
Additionally, as revised patterns and best practices using AWS IoT Core evolve for the energy industry, we will incorporate these updates into the Guidance.
-
SecurityRead the Security whitepaper
This Guidance employs AWS IAM Identity Center to provide authentication through a centralized directory with AWS Identity and Access Management (IAM) roles and policies controlling authorization for the directory.
-
ReliabilityRead the Reliability whitepaper
You can combine built-in CloudWatch logs with Amazon SNS notifications to monitor key performance and reliability system indicators. Administrators are notified through email or SMS text message when metrics fall outside defined operating ranges.
-
Performance EfficiencyRead the Performance Efficiency whitepaper
To support performance efficiency, you should launch end-user facing resources, such as QuickSight, in an AWS Region that will allow for low latency to end users. You can implement any of the services in this Guidance in a multi-Region architecture where appropriate.
-
Cost OptimizationRead the Cost Optimization whitepaper
Core services in this Guidance, including Amazon S3, AWS Glue, Lambda, and Athena, are serverless and can scale on demand while providing consumption-based pricing.
-
SustainabilityRead the Sustainability whitepaper
By using serverless, consumption-based services, such as Amazon S3, AWS Glue, Athena, API Gateway, Amazon SNS, and QuickSight, you can promote utilization of shared resources in the AWS Cloud. This reduces the need to maintain your own on-premises servers, helping you optimize energy consumption.
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.
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.