This Guidance demonstrates how to integrate building systems, assets, and sensors to enable real-time and historical insights for sustainable building management. Operations data from sources such as HVAC, water, electricity, and solar power are consolidated and processed with artificial intelligence and machine learning (AI/ML) capabilities. The data is stored, analyzed, and visualized to reveal where and how buildings are generating emissions across their infrastructure and operations. Customers can also deploy their own sensors, on their own networks, and quickly show which buildings are driving the greatest emissions across their global environment.
Architecture Diagram
Step 1
Ingest utility bills with Amazon API Gateway and convert into machine data using Amazon Textract to normalize electric, gas, water, and waste usage (see the Guidance for Utility Bill Processing on AWS for more details). This data can be sent to the data lake for further analysis.
Step 2
Send device telemetry from Building Management System (BMS) platforms to AWS IoT Core for ingestion into the Cloud. Deliver real-time telemetry data to AWS IoT SiteWise and to the data lake using Amazon Kinesis Data Firehose.
Step 3
Harvest and process device sensor data with AWS IoT SiteWise Edge deployed on AWS IoT Greengrass and send directly to AWS IoT SiteWise.
Step 4
Use Amazon AppFlow or AWS DataSync to connect to your BMS and Enterprise Resource Planning (ERP) systems. This allows you to ingest equipment attributes and your Building Information Modeling (BIM) platform for spatial building models and other attributes. Use AWS Lambda to modify equipment data to adhere to a chosen building metadata standard.
Step 5
Build a data lake using Amazon Simple Storage Service (Amazon S3) to store your data, save technical metadata in your AWS Glue Data Catalog, use AWS Step Functions to orchestrate AWS Glue jobs for extract, transform, and load (ETL), and administer fine-grained access control with AWS Lake Formation.
Step 6
Collect device measurement data in Amazon Timestream or AWS IoT SiteWise to calculate metrics and generate alarms.
Step 7
Manage your asset attributes and relationships in Amazon Neptune or create a digital twin of your sites and assets using AWS IoT TwinMaker. Compose an interactive 3D view of your environment and overlay real-time measurements directly from AWS IoT SiteWise.
Step 8
Provide structured query language (SQL) access to your data through Amazon Athena, or build embeddable, machine learning (ML) dashboards in Amazon QuickSight or Amazon Managed Grafana.
Step 9
Connect Amazon SageMaker to your data lake to train ML models for deployment back on-site in AWS IoT Greengrass for real-time inferencing. Model outputs can be used to control on-site equipment or to derive new metrics for ingestion through the standard architecture.
Step 10
Monitor overall system health and performance using Amazon CloudWatch.
Step 1
Ingest utility bills with Amazon API Gateway and convert into machine data using Amazon Textract to normalize electric, gas, water, and waste usage (see the Guidance for Utility Bill Processing on AWS for more details). This data can be sent to the data lake for further analysis.
Step 2
Send device telemetry from Building Management System (BMS) platforms to AWS IoT Core for ingestion into the Cloud. Deliver real-time telemetry data to AWS IoT SiteWise and to the data lake using Amazon Kinesis Data Firehose.
Step 3
Harvest and process device sensor data with AWS IoT SiteWise Edge deployed on AWS IoT Greengrass and send directly to AWS IoT SiteWise.
Step 4
Use Amazon AppFlow or AWS DataSync to connect to your BMS and Enterprise Resource Planning (ERP) systems. This allows you to ingest equipment attributes and your Building Information Modeling (BIM) platform for spatial building models and other attributes. Use AWS Lambda to modify equipment data to adhere to a chosen building metadata standard.
Step 5
Build a data lake using Amazon Simple Storage Service (Amazon S3) to store your data, save technical metadata in your AWS Glue Data Catalog, use AWS Step Functions to orchestrate AWS Glue jobs for extract, transform, and load (ETL), and administer fine-grained access control with AWS Lake Formation.
Step 6
Collect device measurement data in Amazon Timestream or AWS IoT SiteWise to calculate metrics and generate alarms.
Step 7
Manage your asset attributes and relationships in Amazon Neptune or create a digital twin of your sites and assets using AWS IoT TwinMaker. Compose an interactive 3D view of your environment and overlay real-time measurements directly from AWS IoT SiteWise.
Step 8
Provide structured query language (SQL) access to your data through Amazon Athena, or build embeddable, machine learning (ML) dashboards in Amazon QuickSight or Amazon Managed Grafana.
Step 9
Connect Amazon SageMaker to your data lake to train ML models for deployment back on-site in AWS IoT Greengrass for real-time inferencing. Model outputs can be used to control on-site equipment or to derive new metrics for ingestion through the standard architecture.
Step 10
Monitor overall system health and performance using Amazon CloudWatch.
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
CloudWatch provides centralized logging with metrics and alarms across all deployed services to raise alerts for operational anomalies. For example, you can create an alert to prompt for a service limit increase if you surpass a threshold of concurrent Lambda executions or active Kinesis Data Firehose partitions.
-
SecurityRead the Security whitepaper
Resources are protected using AWS Identity and Access Management (IAM) policies and principles. Use least-privilege access and role-based access to grant operators permissions to modify resources, such as deploying an updated stack through AWS CloudFormation.
AWS Key Management Service (AWS KMS) encrypts your data at-rest in Amazon S3 and AWS IoT SiteWise. AWS KMS encrypts your data in-transit with Lambda and Kinesis Data Firehose. The keys should be rotated on a regular schedule.
-
ReliabilityRead the Reliability whitepaper
This Guidance uses AWS services that are serverless, enabling auto-scaling to respond to fluctuating demands. For example, AWS IoT Core, AWS IoT SiteWise, and Kinesis Data Firehose scale to match the throughput of your data with no management required. For in-flight processing, Lambda will automatically scale the number of execution environments required to handle demand.
AWS services are used to provide various options for data backup and recovery. For example, Amazon S3 has object versioning, replication, and backup features to ensure Recovery Point Objectives (RPOs) can be met. If needed, AWS IoT SiteWise APIs can provide definitions of assets and models for easy backup and restoration.
-
Performance EfficiencyRead the Performance Efficiency whitepaper
Services in this Guidance were purposefully selected to handle the needs of a modernized building management system. Amazon S3 was selected for its reliable long-term storage and flexibility of consuming tools and services. AWS IoT SiteWise provides managed, scalable ingestion, and real-time calculation of streaming asset data, minimizing the need to build custom components. It integrates seamlessly with AWS IoT TwinMaker, which was chosen for digital twin creation.
-
Cost OptimizationRead the Cost Optimization whitepaper
This Guidance relies on serverless AWS services such as AWS IoT TwinMaker, AWS Glue, Lambda, Athena, and Kinesis Data Firehose. These services are fully managed and autoscale according to workload demand. As a result, you only pay for what you use.
-
SustainabilityRead the Sustainability whitepaper
Data in Amazon S3 can be stored in more efficient file formats (such as Parquet) to prevent unnecessary processing and reduce the overall storage required.
Amazon S3 lifecycle policies can automatically move data to more energy-efficient storage classes, enforce deletion timelines, and minimize overall storage requirements.
This Guidance uses managed, serverless technologies such as AWS Glue, Lambda, Athena, and Step Functions to ensure hardware is minimally provisioned to meet demand.
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.
Related Content
Creating Sustainable, Data-Driven Buildings
Guidance for Monitoring and Optimizing Energy Usage on AWS
Guidance for Utility Bill Processing on AWS
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.