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.

Please note: [Disclaimer]

Architecture Diagram

Download the architecture diagram PDF 
  • Overview
  • This architecture diagram is a broad overview showing the minimal deployment of Siemens Opcenter Execution applications on AWS.

  • High availability
  • This architecture diagram shows how core, critical Siemens Opcenter Execution applications are deployed across multiple Availability Zones within an AWS Region to achieve high availability.

  • AWS Managed Services
  • This architecture diagram shows how AWS Managed Services deploy Siemens Opcenter Execution applications across multiple Availability Zones within an AWS Region for high availability and fault tolerance.

  • AWS Outposts
  • This architecture diagram shows how the AWS Outposts service deploys Siemens Opcenter Execution applications on-premises at a designated location, establishing a secure and low-latency connection to the designated AWS Region.

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.

  • 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 

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.

[Content Type]


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


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?