Configuring the event log rules
Prerequisites
- Access to the Configuration > General parameters (SP019) menu.
- Access to the Management > Collection tracking (SP004) menu.
- Planned collection
Introduction
In the SPC context, the event log is a mechanism for tracking and traceability. It allows data to be analyzed in relation to standards or set limits. Any event that do not meet the expected standard generates an occurrence in the log.
To configure an event log, it is necessary to define its rules first: a set of conditions and parameters that determine how the events and occurrences will be recorded and monitored throughout the production process.
Event log rules
The event log rules are applied to the characteristics of the variable and attribute types, divided into three major groups:
- Occurrences: they are triggered when an unexpected event occurs. For example: when a point out of the executed control limit is out of the deadline (only occurs when a frequency is set for the collection).
- Sequences: they are triggered when a point sequence begins a pattern. For example: a sequence of "X" consecutive points, alternating above and below the central line.
- Values: they are triggered upon crossing a certain value. For example: "CPK lower than" and "PPK lower than".
- Rules of the sequence and value types will have suggested values, but it is possible to configure them according to your needs.
- The values suggested in the rules are based on SPC literature and on market standards.
A rule can be applied to all data collections or to specific ones.
Below, see an example for each situation:
Configuring event log rules for all collections

Configuring event log rules for a specific collection
8. To finish, click on the button.

As of version 2.1.09, SoftExpert SPC considers the user's browser, no longer the server's time, to record the time of both the data collection sample and the event log.
Conclusion
The rules for activating the event log are essential to ensuring that critical process performance information, such as deviations or failures, is captured precisely and in a timely manner.
The next step is to determine the situations that will be monitored and recorded by the system. To move forward, refer to the Configuring occurrences article.