Skip to main content

AWS Solutions Library

Guidance for Deploying Siemens Opcenter Execution Foundation on AWS

Overview

This Guidance illustrates four architecture design options for deploying Siemens Opcenter Execution, a manufacturing execution system (MES) used to orchestrate and monitor production processes. First, the minimal architecture deploys the primary Opcenter Execution application and supporting components. Second, for high availability, the core applications can be deployed across multiple Availability Zones (AZs), while non-critical applications remain in a single Zone. Third, AWS Managed Services can be used to automate the deployment and management of these applications across AZs. Finally, an AWS Outposts option is available, where Outposts is deployed on-premises, establishing a secure connection to the AWS Region. These diverse options enable manufacturers to choose the deployment model that best suits their requirements for proximity, availability, scalability, and integration with AWS Cloud services.

How it works

Overview

This architecture diagram is a broad overview showing the minimal deployment of Siemens Opcenter Execution Foundation on AWS, a manufacturing execution system (MES) designed for orchestration of visibility, control, and optimization of production and processes.

Download the architecture diagram
Architecture diagram showing the integration of Siemens Opcenter Execution Foundation with AWS Cloud services, including components such as Amazon EC2, Route 53, CloudTrail, CloudWatch, S3, Backup, Site-to-Site VPN, Direct Connect, Application Load Balancer, and on-premises enterprise and plant systems.

High Availability

This architecture diagram shows core, critical OEE applications deployed in multiple availability zones for high availability.

Download the architecture diagram
Architecture diagram showing the high availability deployment of Siemens Opcenter Execution Foundation on AWS. The diagram details integration between on-premises ERP systems, plant shop floor, user clients, and AWS Cloud infrastructure across multiple availability zones. Key AWS services include Amazon EC2, Amazon SQL Server, NAT gateways, AWS S3, AWS Backup, Amazon CloudWatch, Amazon CloudTrail, and site-to-site VPN and Direct Connect for secure connectivity.

AWS Managed Services

This architecture diagram shows how AWS Managed Services can be configured to deploy OEE applications in multiple availability zones for high availability.

Download the architecture diagram
Architecture diagram illustrating Siemens Opcenter Execution Foundation deployed with AWS Managed Services. The diagram shows integration between on-premises systems and AWS Cloud, with components such as VPN gateways, Amazon EC2 Opcenter servers, Amazon RDS for SQL Server, Application Load Balancer, and supporting AWS services like AWS Backup, Amazon S3, Amazon CloudWatch, and AWS Systems Manager across multiple availability zones.

AWS Outposts

This architecture diagram shows how AWS Outposts is deployed on-premises, and connectivity to the AWS Region is established through an edge router connecting the Outposts service.

Download the architecture diagram
Architecture diagram showing the integration of Siemens Opcenter Execution Foundation with AWS Outposts. The diagram illustrates connections between AWS Cloud services (including Amazon S3, AWS Backup, Amazon EC2, CloudWatch, CloudTrail) and an on-premises environment featuring AWS Outposts, with details on networking, subnets, backup vaults, application and database servers, and user/local gateway connections.

Well-Architected Pillars

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.

CloudWatch collects logs, metrics, and events, providing you with a centralized view of your environment. Configure CloudWatch alarms to proactively notify you of any deviations from normal operations, so you can respond and maintain optimal performance.


Read the Operational Excellence whitepaper

The ALB allows your Amazon EC2 instances to reside in private subnets, shielding them from direct internet exposure. And the Amazon EC2 security groups help ensure that only legitimate network traffic can reach your application and database instances.


Read the Security whitepaper

AWS Backup enables centralized and automated data protection, allowing you to restore your environment in the event of a disaster. Also, the ALB distributes client requests across healthy Amazon EC2 instances for high availability and fault tolerance.


Read the Reliability whitepaper

The ALB distributes the workload across multiple Amazon EC2 instances, enabling horizontal scalability. CloudWatch provides long-term usage metrics, so you can make informed decisions and fine-tune your environment for optimal performance.


Read the Performance Efficiency whitepaper

CloudWatch offers long-term usage metrics, allowing you to right-size your Amazon EC2 and RDS for SQL Server database instances for cost efficiency. Systems Manager allows you to manage and access your Amazon EC2 instances without the need for additional bastion hosts, reducing your overall infrastructure costs.


Read the Cost Optimization whitepaper

CloudWatch provides long-term usage data for you to make informed decisions about instance sizing, resource utilization, and the adoption of AWS managed services, ensuring the sustainable operation of your environment.


Read the Sustainability whitepaper

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.