Test loads

Load was placed on the system from two sources: System Platform application objects and MES Web API tests.

System Platform application objects

In System Platform, load was generated using 50 entities, each with one OCO and one UCO, for a total of 50 OCOs and 50 UCOs. An additional five SROs were used for quality data. The entities were deployed to four Application Engines on a single platform. The following load was generated:

• Each entity generated one utilization event per minute except for a four‑minute period of inactivity each hour. Thus, there were 56 utilization events produced per entity per hour.

• Each entity generated two item production events (one good production and one scrap production) per minute except for a four-minute period of inactivity each hour. Thus, there were 112 item production events (56 x 2) produced per entity per hour. The system was set to collect distinct production, so each item production event generated a new record in the database.

• Each entity generated one item consumption event per minute except for a four‑minute period of inactivity each hour. Thus, there were 56 item consumption events produced per entity per hour. The system was not set to collect distinct consumption, so the item consumption data was accumulated in existing records rather than having a new record for each consumption event.

• Each entity with an SRO recorded a quality result every minute except for a four‑minute period of inactivity each hour. Thus, there were 56 result records produced per entity per hour. New samples were generated by the system every five minutes with five characteristics in each sample.

• Each hour, the following processing took place for each entity, in the order shown:

  • The current job was stopped

  • The machine state was changed to down (generating a utilization event)

  • A new job was created

  • The item lot was changed

  • Inventory was received

  • The new job was started

  • The machine state was changed to running (generating a utilization event)

MES Web Portal

From an MES client system, load was generated from 50 virtual users, half performing MES Web Portal functions and the other half performing quality functions. The MES Web Portal tests simulated this activity by making the same Web API calls that the MES Web Portal makes from the page being tested. The following load was generated:

• Nine users simulated loading the following MES Web Portal pages. Each user loaded one of these pages at random every 30 seconds:

  • Home page

  • Line Collection page

  • Line Work Order page

  • Line Entity page

  • Entity Work Queue page

  • Utilization Event History page

  • Production History page

  • Entity Monitor page

  • Line Monitor page

• 16 users simulated activities that might be performed by a line operator. Some of these activities were page loads, while others involved data generation. Each user performed one of these activity at random every 60 seconds:

  • Line Collection page load

  • Line Entity page load

  • Line Work Order page load

  • Add utilization event

  • Add item production

  • Create work order

  • Line Monitor page load

MES quality testing

25 users simulated activities that might be performed by a line operator. Some of these activities were requesting data, while others involved recording results or modifying sample context data. Each user performed one of these activities at random every 60 seconds:

• Update sample context data

• Pull or finalize sample

• Read sample and result data

• Record results

Other test information

The settings in the FactMES.Server.Host.exe.config file were all left at their default values. No other MES applications were run during the tests. The Operations Control Management Console Log Viewer was checked for error or warning messages; no messages occurred during the test.