Standard MES topology with scaling factors applied

Every production environment is different. A solution architect would need to fully evaluate the customer requirements and respective load to estimate a server sizing.

The basis for scaling the system is based on the collection of performance data on the system. This data includes CPU and memory usage, as well as server-specific data such as scan overruns for the Application Server (see the Key Measures for each server type in General Server Requirements). The ideal source of this data is the actual production system. Alternatively, you can use the test system.

You will have to determine the best way to scale the system. Whether the scaling is based on lines, equipment, or number of users depends on your application.

The performance data provided in Performance Test Results, along with the scaling information provided for each server type in MES solution component requirements, should provide enough information to determine how to scale the system.

The following diagram shows an example of the scaling up of standard MES architecture with System Platform.

In this example, the system was scaled by:

• Adding multiple Application Servers to handle more transactions and System Platform objects (see the Middleware guidelines in MES middleware recommendations. In this example, the Application Server was scaled by process area.

• Separating the Historian and Archive databases to run on separate servers.

• Adding a second Work Tasks Server to accommodate increased number of workflows that are executing concurrently.

• Adding multiple Terminal Servers (Load-Balanced Server Farm), each with their own MES middleware host, to handle increased number of OMI and InTouch app users.

• Increasing in the number of Engineering stations. Engineer user access can also be provided through permissions and MES clients installed on non-Engineering stations.

• Increasing in the number of Supervisor stations. A suggested guideline is that 1 Supervisor station is required for every 10 to 20 lines.

• Adding additional CPUs and memory to the Database, Archive, and Report Servers.