Events

The machine shop application was based on a set of System Platform object templates with pre-configured scripts that trigger events at regular intervals. This made the events, and thereby the data logged in the MES database, predictable. Any values related to events (e.g., good production) are set to a constant value.

The following events were triggered by the machine shop application.

Hourly Events

• Change state of machine to a running state

• Create job

• Receive inventory

• Stop job

• Reset event commands if in error

• Reset stop job commands if in error

• Start job

• Change state of machine to a running state

Minutely Events

• Add good production

• Add bad production

• Add consumption

• Reset various event commands if in error

This configuration guarantees that at any given second one of each minutely event will be triggered if there is a corresponding MES object for that second. This ensures that when migration (Live Migration/failover) is triggered, the configured events are being exercised.

Also, the MES database was pre-populated with one year’s worth of data prior to running through the various scenarios to ensure that the test scenarios were run on a typically loaded system.