Create or Configure a Rule

Create or Configure Frequently Countable Events Rule

Precondition

Rules Management Expert or Rules Management Administrator role

Procedure

  1. Call up the Efficiency analysis > Rules management menu.

    rm_overview

  2. Create a new rule with add_border.

    Or :

    Edit rule with mdm_edit_icon.

    The Add Rule or Edit rule dialog window is displayed with the Set context step:

    rm_add_new_rule

  3. Select the device or device type from the Set context drop-down list.

    Depending on the selected context, the Device or Device type field appears.

  4. Select the Device or Device type from the drop-down list.

  5. Optionally enter a part type.

  6. Confirm entries with Continue.

    Multiple conditions are automatically AND-linked.

  7. Create a condition with add_black.

    Or :

  8. Press mdm_edit_icon to change the settings of a condition.

    rm_add_new_rule_hit_events_2022.02

    In the field, select the Frequently Countable Events Function.

    If Rules Extended is installed, the Number-based option is also available in the Optional settings area for the Time range and a value range above 200 can be defined in the Number field.

  9. In the Further settings area, configure the Time range.

    Values in the following numeric fields can also be changed by scrolling with the mouse wheel.

    • Time-based (in seconds) : Specify the time period in which measured values or codes for the rule are to be recorded.

      Or:

      Number-based : Specify the number of measured values or codes to be recorded for the rule.

    • Number/seconds: Specify the number of measurements/time span in seconds that will be used to execute the rule.

    • Frequency: Define the number of occurrences before the rule creates a new event.

  10. Enter Function Parameters or select from the respective drop-down list:

    • Select Operator (<, >, =).

    • Code : Enter the code of the machine message to be checked.

  11. Create a condition with Add.

    Or:

    Change a changed condition with Save.

    The settings of the new or changed condition are displayed in the overview.

  12. Edit conditions:

    • To add another condition, create a condition with add_black Add condition.

    • To change the settings of a condition, edit the condition with mdm_edit_icon.

    • Delete the condition with delete.

  13. Confirm entries with Continue.

  14. Configure the event that is to trigger the rule.

    • Title

      Enter the rule name.

    • Code

      Specify the message code that the rule should create.

      A unique code must be specified so that there is no conflict with a code generated by another rule or a machine message.

    • Severity type

      Specify the severity of the event ( Low , Medium , High ).

    • Description

      Enter text to describe the function of the rule.

    • Note __ (optional)

      Enter the message text.

  15. Apply the rule with Save.

The new or changed rule is displayed in the Rule overview.

  • To assign a ticket to the rule, continue with Create ticket assignment.

Create or Configure Upper Limit/Lower Limit Rule

Precondition

Rules Management Expert or Rules Management Administrator role

Procedure

  1. Call up the Efficiency analysis > Rules management menu.

    rm_overview

  2. Create a new rule with add_border.

    Or :

    Edit rule with mdm_edit_icon.

    The Add Rule or Edit rule dialog window is displayed with the Set context step:

    rm_add_new_rule

  3. Select the device or device type from the Set context drop-down list.

    Depending on the selected context, the Device or Device type field appears.

  4. Select the Device or Device type from the drop-down list.

  5. Optionally enter a part type.

  6. Confirm entries with Continue.

    Multiple conditions are automatically AND-linked.

  7. Create a condition with add_black.

    Or :

  8. Press mdm_edit_icon to change the settings of a condition.

  9. Select Upper Limit or Lower Limit in the Function field.

    If counters have been created for the Device or the Device Type , they can be selected in the Measuring Point field. If a counter is selected, the current status of the counter is monitored.

    If Rules Extended is installed, the Aggregation Type and the Source can be changed.

  10. In the Context area, select the Measuring Point , Aggregation Type and Source from the respective drop-down lists.

    If Rules Extended is installed, the Number-Based option is also available in the Optional settings area for the Time range and a value range above 200 can be defined in the Number field.

  11. In the Further settings area, configure the Time range.

    Values in the following numeric fields can also be changed by scrolling with the mouse wheel.

    • Time-based (in seconds) : Specify the time period in which measured values or codes for the rule are to be recorded.

      Or:

      Number-based : Specify the number of measured values or codes to be recorded for the rule.

    • Number/seconds: Specify the number of measurements/time span in seconds that will be used to execute the rule.

    • Frequency: Define the number of occurrences before the rule creates a new event.

      rm_add_new_rule_Upper_lowbound_2022.02

  12. In the Function Parameters area, in the Limit Value field, enter the value with which the measured value is to be compared.

  13. Create a condition with Add.

    Or:

    Change a changed condition with Save.

    The settings of the new or changed condition are displayed in the overview.

  14. Edit conditions:

    • To add another condition, create a condition with add_black Add condition.

    • To change the settings of a condition, edit the condition with mdm_edit_icon.

    • Delete the condition with delete.

  15. Confirm entries with Continue.

  16. Configure the event that is to trigger the rule.

    • Title

      Enter the rule name.

    • Code

      Specify the message code that the rule should create.

      A unique code must be specified so that there is no conflict with a code generated by another rule or a machine message.

    • Severity type

      Specify the severity of the event ( Low , Medium , High ).

    • Description

      Enter text to describe the function of the rule.

    • Note __ (optional)

      Enter the message text.

  17. Apply the rule with Save.

The new or changed rule is displayed in the Rule overview.

  • To assign a ticket to the rule, continue with Create ticket assignment.

Create or Configure Upper Limit/Lower Limit (Calculated Limit) Rule

Precondition

Rules Management Expert or Rules Management Administrator role

Procedure

  1. Call up the Efficiency analysis > Rules management menu.

    rm_overview

  2. Create a new rule with add_border.

    Or :

    Edit rule with mdm_edit_icon.

    The Add Rule or Edit rule dialog window is displayed with the Set context step:

    rm_add_new_rule

  3. Select the device or device type from the Set context drop-down list.

    Depending on the selected context, the Device or Device type field appears.

  4. Select the Device or Device type from the drop-down list.

  5. Optionally enter a part type.

  6. Confirm entries with Continue.

    Multiple conditions are automatically AND-linked.

  7. Create a condition with add_black.

    Or :

  8. Press mdm_edit_icon to change the settings of a condition.

  9. Select Upper Limit (Calculated Limit) or Lower Limit (Calculated Limit) in the Function field.

    If counters have been created for the Device or the Device Type , they can be selected in the Measuring Point field. If a counter is selected, the current status of the counter is monitored.

    If Rules Extended is installed, the Aggregation Type and the Source can be changed.

  10. In the Context area, select the Measuring Point , Aggregation Type and Source from the respective drop-down lists.

    If Rules Extended is installed, the Number-Based option is available in the Optional settings area for the Time range and a value range above 200 can be defined in the Number field.

  11. In the Further settings area, configure the Time range.

    Values in the following numeric fields can also be changed by scrolling with the mouse wheel.

    • Time-based (in seconds) : Specify the time period in which measured values or codes for the rule are to be recorded.

      Or:

      Number-based : Specify the number of measured values or codes to be recorded for the rule.

    • Number/seconds: Specify the number of measurements/time span in seconds that will be used to execute the rule.

    • Frequency : Define the number of occurrences before the rule creates a new event.

      rm_add_new_rule_upperbound_calculated_2022.02

  12. Enter data in the Function Parameters area or select from the respective drop-down list:

    • Relative: Checkbox for selecting whether the deviation is used as a percentage or as an absolute value when calculating the limit

    • Variation: Deviation used to calculate limit values

    • Tolerance range: Checkbox for defining which calculation is to be used. Can only be activated if Relative is selected.

  13. Create a condition with Add.

    Or:

    Change a changed condition with Save.

    The settings of the new or changed condition are displayed in the overview.

  14. Edit conditions:

    • To add another condition, create a condition with add_black Add condition.

    • To change the settings of a condition, edit the condition with mdm_edit_icon.

    • Delete the condition with delete.

  15. Confirm entries with Continue.

  16. Configure the event that is to trigger the rule.

    • Title

      Enter the rule name.

    • Code

      Specify the message code that the rule should create.

      A unique code must be specified so that there is no conflict with a code generated by another rule or a machine message.

    • Severity type

      Specify the severity of the event ( Low , Medium , High ).

    • Description

      Enter text to describe the function of the rule.

    • Note __ (optional)

      Enter the message text.

  17. Apply the rule with Save.

The new or changed rule is displayed in the Rule overview.

  • To assign a ticket to the rule, continue with Create ticket assignment.

Create or Configure the Upper Limit/Lower Limit (Priority of Current Value) Rule

Precondition

Rules Management Expert or Rules Management Administrator role

Procedure

  1. Call up the Efficiency analysis > Rules management menu.

    rm_overview

  2. Create a new rule with add_border.

    Or :

    Edit rule with mdm_edit_icon.

    The Add Rule or Edit rule dialog window is displayed with the Set context step:

    rm_add_new_rule

  3. Select the device or device type from the Set context drop-down list.

    Depending on the selected context, the Device or Device type field appears.

  4. Select the Device or Device type from the drop-down list.

  5. Optionally enter a part type.

  6. Confirm entries with Continue.

    Multiple conditions are automatically AND-linked.

  7. Create a condition with add_black.

    Or :

  8. Press mdm_edit_icon to change the settings of a condition.

  9. Select the Upper Limit (Priority of Current Value) or Lower Limit (Priority of Current Value) in the Function field.

    If counters have been created for the Device or the Device Type , they can be selected in the Measuring Point field. If a counter is selected, the current status of the counter is monitored.

    If Rules Extended is installed, the Aggregation Type and the Source can be changed.

  10. In the Context area, select the Measuring Point , Aggregation Type and Source from the respective drop-down lists.

    If Rules Extended is installed, the Number-Based option is also available in the Optional settings area for the Time range and a value range above 200 can be defined in the Number field.

  11. In the Further settings area, configure the Time range.

    Values in the following numeric fields can also be changed by scrolling with the mouse wheel.

    • Time-based (in seconds) : Specify the time period in which measured values or codes for the rule are to be recorded.

      Or:

      Number-based : Specify the number of measured values or codes to be recorded for the rule.

    • Number/seconds: Specify the number of measurements/time span in seconds that will be used to execute the rule.

    • Frequency: Define the number of occurrences before the rule creates a new event.

      rm_add_new_rule_upperbound_prio_2022.02

  12. In the Function Parameters area, in the Limit Value field, enter the value with which the measured value is to be compared.

  13. Create a condition with Add.

    Or:

    Change a changed condition with Save.

    The settings of the new or changed condition are displayed in the overview.

  14. Edit conditions:

    • To add another condition, create a condition with add_black Add condition.

    • To change the settings of a condition, edit the condition with mdm_edit_icon.

    • Delete the condition with delete.

  15. Confirm entries with Continue.

  16. Configure the event that is to trigger the rule.

    • Title

      Enter the rule name.

    • Code

      Specify the message code that the rule should create.

      A unique code must be specified so that there is no conflict with a code generated by another rule or a machine message.

    • Severity type

      Specify the severity of the event ( Low , Medium , High ).

    • Description

      Enter text to describe the function of the rule.

    • Note __ (optional)

      Enter the message text.

  17. Apply the rule with Save.

The new or changed rule is displayed in the Rule overview.

  • To assign a ticket to the rule, continue with Create ticket assignment.

Create or Configure the PPMP Limit Rule

Precondition

Rules Management Expert or Rules Management Administrator role

Procedure

  1. Call up the Efficiency analysis > Rules management menu.

    rm_overview

  2. Create a new rule with add_border.

    Or :

    Edit rule with mdm_edit_icon.

    The Add Rule or Edit rule dialog window is displayed with the Set context step:

    rm_add_new_rule

  3. Select the device or device type from the Set context drop-down list.

    Depending on the selected context, the Device or Device type field appears.

  4. Select the Device or Device type from the drop-down list.

  5. Optionally enter a part type.

  6. Confirm entries with Continue.

    Multiple conditions are automatically AND-linked.

  7. Create a condition with add_black.

    Or :

  8. Press mdm_edit_icon to change the settings of a condition.

  9. Select PPMP Limit in the Function field.

    If counters have been created for the Device or the Device Type , they can be selected in the Measuring Point field. If a counter is selected, the current status of the counter is monitored.

    If Rules Extended is installed, the Aggregation Type and the Source can be changed.

    In the Context area, select the Measuring Point , Aggregation Type and Source from the respective drop-down lists.

    If Rules Extended is installed, the Number-Based option is also available in the Optional settings area for the Time range and a value range above 200 can be defined in the Number field.

  10. In the Further settings area, configure the Time range.

    Values in the following numeric fields can also be changed by scrolling with the mouse wheel.

    • Time-based (in seconds) : Specify the time period in which measured values or codes for the rule are to be recorded.

      Or:

      Number-based : Specify the number of measured values or codes to be recorded for the rule.

    • Number/seconds: Specify the number of measurements/time span in seconds that will be used to execute the rule.

    • Frequency: Define the number of occurrences before the rule creates a new event.

      rm_add_new_rule_PPMP_limits_2022.02

  11. Enter data in the Function Parameters area or select from the respective drop-down list:

    • Operator: Select an operator to compare the values.

    • Limit: Enter a numeric value as the slope limit.

    • Variation: Enter the value added to the actual value.

    • Relative: Activate the checkbox to set a relative limit value.

  12. Create a condition with Add.

    Or:

    Change a changed condition with Save.

    The settings of the new or changed condition are displayed in the overview.

  13. Edit conditions:

    • To add another condition, create a condition with add_black Add condition.

    • To change the settings of a condition, edit the condition with mdm_edit_icon.

    • Delete the condition with delete.

  14. Confirm entries with Continue.

  15. Configure the event that is to trigger the rule.

    • Title

      Enter the rule name.

    • Code

      Specify the message code that the rule should create.

      A unique code must be specified so that there is no conflict with a code generated by another rule or a machine message.

    • Severity type

      Specify the severity of the event ( Low , Medium , High ).

    • Description

      Enter text to describe the function of the rule.

    • Note __ (optional)

      Enter the message text.

  16. Apply the rule with Save.

The new or changed rule is displayed in the Rule overview.

  • To assign a ticket to the rule, continue with Create ticket assignment.

Create or Configure the Process Capability Index Rule

Precondition

Rules Management Expert or Rules Management Administrator role

Procedure

  1. Call up the Efficiency analysis > Rules management menu.

    rm_overview

  2. Create a new rule with add_border.

    Or :

    Edit rule with mdm_edit_icon.

    The Add Rule or Edit rule dialog window is displayed with the Set context step:

    rm_add_new_rule

  3. Select the device or device type from the Set context drop-down list.

    Depending on the selected context, the Device or Device type field appears.

  4. Select the Device or Device type from the drop-down list.

  5. Optionally enter a part type.

  6. Confirm entries with Continue.

    Multiple conditions are automatically AND-linked.

  7. Create a condition with add_black.

    Or :

  8. Press mdm_edit_icon to change the settings of a condition.

    The Process Capability Index function is available only when Rules Extended is installed.

  9. Select the Process Capability Index in the Function field.

    If counters have been created for the Device or the Device Type , they can be selected in the Measuring Point field. If a counter is selected, the current status of the counter is monitored.

  10. In the Context area, select the Measuring Point , Aggregation Type and Source from the respective drop-down lists.

  11. In the Further settings area, configure the Time range.

    Values in the following numeric fields can also be changed by scrolling with the mouse wheel.

    • Time-based (in seconds) : Specify the time period in which measured values or codes for the rule are to be recorded.

      Or:

      Number-based : Specify the number of measured values or codes to be recorded for the rule.

    • Number/seconds: Specify the number of measurements/time span in seconds that will be used to execute the rule.

      rm_add_new_rule_processindex_2022.02

  12. Enter data in the Function Parameters area or select from the respective drop-down list:

    • USL: Enter the upper limit from which the measured value triggers the rule.

    • Limit value: Enter the threshold that is compared to the calculated C pk value.

    • LSL: Enter the lower limit from which the measured value triggers the rule.

    • Operator: Comparison operator for threshold and C pk value.

  13. Create a condition with Add.

    Or:

    Change a changed condition with Save.

    The settings of the new or changed condition are displayed in the overview.

  14. Edit conditions:

    • To add another condition, create a condition with add_black Add condition.

    • To change the settings of a condition, edit the condition with mdm_edit_icon.

    • Delete the condition with delete.

  15. Confirm entries with Continue.

  16. Configure the event that is to trigger the rule.

    • Title

      Enter the rule name.

    • Code

      Specify the message code that the rule should create.

      A unique code must be specified so that there is no conflict with a code generated by another rule or a machine message.

    • Severity type

      Specify the severity of the event ( Low , Medium , High ).

    • Description

      Enter text to describe the function of the rule.

    • Note __ (optional)

      Enter the message text.

  17. Apply the rule with Save.

The new or changed rule is displayed in the Rule overview.

  • To assign a ticket to the rule, continue with Create ticket assignment.

Create or Configure Jump Detection Rule

Precondition

Rules Management Expert or Rules Management Administrator role

Procedure

  1. Call up the Efficiency analysis > Rules management menu.

    rm_overview

  2. Create a new rule with add_border.

    Or :

    Edit rule with mdm_edit_icon.

    The Add Rule or Edit rule dialog window is displayed with the Set context step:

    rm_add_new_rule

  3. Select the device or device type from the Set context drop-down list.

    Depending on the selected context, the Device or Device type field appears.

  4. Select the Device or Device type from the drop-down list.

  5. Optionally enter a part type.

  6. Confirm entries with Continue.

    Multiple conditions are automatically AND-linked.

  7. Create a condition with add_black.

    Or :

  8. Press mdm_edit_icon to change the settings of a condition.

    The Jump Detection function is only available if Rules Extended is installed.

  9. Select Jump detection in the Function field.

    If counters have been created for the Device or the Device Type , they can be selected in the Measuring Point field. If a counter is selected, the current status of the counter is monitored.

  10. In the Context area, select the Measuring Point , Aggregation Type and Source from the respective drop-down lists.

  11. In the Further settings area, configure the Time range.

    Values in the following numeric fields can also be changed by scrolling with the mouse wheel.

    • Time-based (in seconds) : Specify the time period in which measured values or codes for the rule are to be recorded.

      Or:

      Number-based : Specify the number of measured values or codes to be recorded for the rule.

    • Number/seconds: Specify the number of measurements/time span in seconds that will be used to execute the rule.

      rm_add_new_rule_jump_detection_2022.02

  12. In the Function Parameters area, enter the limit value for checking a jump in the Jump field.

  13. Create a condition with Add.

    Or:

    Change a changed condition with Save.

    The settings of the new or changed condition are displayed in the overview.

  14. Edit conditions:

    • To add another condition, create a condition with add_black Add condition.

    • To change the settings of a condition, edit the condition with mdm_edit_icon.

    • Delete the condition with delete.

  15. Confirm entries with Continue.

  16. Configure the event that is to trigger the rule.

    • Title

      Enter the rule name.

    • Code

      Specify the message code that the rule should create.

      A unique code must be specified so that there is no conflict with a code generated by another rule or a machine message.

    • Severity type

      Specify the severity of the event ( Low , Medium , High ).

    • Description

      Enter text to describe the function of the rule.

    • Note __ (optional)

      Enter the message text.

  17. Apply the rule with Save.

The new or changed rule is displayed in the Rule overview.

  • To assign a ticket to the rule, continue with Create ticket assignment.

Create or Configure Trend (Method of Least Squares, Time-Based or Normalized) Rule

Precondition

Rules Management Expert or Rules Management Administrator role

Procedure

  1. Call up the Efficiency analysis > Rules management menu.

    rm_overview

  2. Create a new rule with add_border.

    Or :

    Edit rule with mdm_edit_icon.

    The Add Rule or Edit rule dialog window is displayed with the Set context step:

    rm_add_new_rule

  3. Select the device or device type from the Set context drop-down list.

    Depending on the selected context, the Device or Device type field appears.

  4. Select the Device or Device type from the drop-down list.

  5. Optionally enter a part type.

  6. Confirm entries with Continue.

    Multiple conditions are automatically AND-linked.

  7. Create a condition with add_black.

    Or :

  8. Press mdm_edit_icon to change the settings of a condition.

    The Trend Detection function is only available if Rules Extended is installed.

  9. Select Trend Detection in the Function field.

    If counters have been created for the Device or the Device Type , they can be selected in the Measuring Point field. If a counter is selected, the current status of the counter is monitored.

  10. In the Context area, select the Measuring Point , Aggregation Type and Source from the respective drop-down lists.

  11. In the Further settings area, configure the Time range.

    Values in the following numeric fields can also be changed by scrolling with the mouse wheel.

    • Time-based (in seconds) : Specify the time period in which measured values or codes for the rule are to be recorded.

      Or:

      Number-based : Specify the number of measured values or codes to be recorded for the rule.

    • Number/seconds: Specify the number of measurements/time span in seconds that will be used to execute the rule.

      rm_add_new_rule_trend_method_squares_2022.02

  12. Enter data in the Function Parameters area or select from the respective drop-down list:

    • Operator: Select an operator to compare the values.

    • Limit value: Enter a numeric value as the slope limit.

    • Normalized:

      To calculate the straight line based on the number of measured values, activate the checkbox.

      Or:

      To calculate the straight line in relation to the distances in milliseconds, deactivate the checkbox.

  13. Create a condition with Add.

    Or:

    Change a changed condition with Save.

    The settings of the new or changed condition are displayed in the overview.

  14. Edit conditions:

    • To add another condition, create a condition with add_black Add condition.

    • To change the settings of a condition, edit the condition with mdm_edit_icon.

    • Delete the condition with delete.

  15. Confirm entries with Continue.

  16. Configure the event that is to trigger the rule.

    • Title

      Enter the rule name.

    • Code

      Specify the message code that the rule should create.

      A unique code must be specified so that there is no conflict with a code generated by another rule or a machine message.

    • Severity type

      Specify the severity of the event ( Low , Medium , High ).

    • Description

      Enter text to describe the function of the rule.

    • Note __ (optional)

      Enter the message text.

  17. Apply the rule with Save.

The new or changed rule is displayed in the Rule overview.

  • To assign a ticket to the rule, continue with Create ticket assignment.

Create or Configure Trend Rule

Precondition

Rules Management Expert or Rules Management Administrator role

Procedure

  1. Call up the Efficiency analysis > Rules management menu.

    rm_overview

  2. Create a new rule with add_border.

    Or :

    Edit rule with mdm_edit_icon.

    The Add Rule or Edit rule dialog window is displayed with the Set context step:

    rm_add_new_rule

  3. Select the device or device type from the Set context drop-down list.

    Depending on the selected context, the Device or Device type field appears.

  4. Select the Device or Device type from the drop-down list.

  5. Optionally enter a part type.

  6. Confirm entries with Continue.

    Multiple conditions are automatically AND-linked.

  7. Create a condition with add_black.

    Or :

  8. Press mdm_edit_icon to change the settings of a condition.

    The Trend Detection function is only available if Rules Extended is installed.

  9. Select Trend Detection in the Function field.

    If counters have been created for the Device or the Device Type , they can be selected in the Measuring Point field. If a counter is selected, the current status of the counter is monitored.

  10. In the Context area, select the Measuring Point , Aggregation Type and Source from the respective drop-down lists.

  11. In the Further settings area, configure the Time range.

    Values in the following numeric fields can also be changed by scrolling with the mouse wheel.

    • Time-based (in seconds) : Specify the time period in which measured values or codes for the rule are to be recorded.

      Or:

      Number-based : Specify the number of measured values or codes to be recorded for the rule.

    • Number/seconds: Specify the number of measurements/time span in seconds that will be used to execute the rule.

      rm_add_new_rule_trend_2022.02

  12. Enter data in the Function Parameters area or select from the respective drop-down list:

    • Target: Enter the value that is added to the oldest measured value and used to calculate the target line for the best fit.

    • Target type

      Select the best fit line as the lower limit: The target fit line acts as the lower limit.

      Select the best-fit line as the upper limit: The target fit line acts as the upper limit.

  13. Create a condition with Add.

    Or:

    Change a changed condition with Save.

    The settings of the new or changed condition are displayed in the overview.

  14. Edit conditions:

    • To add another condition, create a condition with add_black Add condition.

    • To change the settings of a condition, edit the condition with mdm_edit_icon.

    • Delete the condition with delete.

  15. Confirm entries with Continue.

  16. Configure the event that is to trigger the rule.

    • Title

      Enter the rule name.

    • Code

      Specify the message code that the rule should create.

      A unique code must be specified so that there is no conflict with a code generated by another rule or a machine message.

    • Severity type

      Specify the severity of the event ( Low , Medium , High ).

    • Description

      Enter text to describe the function of the rule.

    • Note __ (optional)

      Enter the message text.

  17. Apply the rule with Save.

The new or changed rule is displayed in the Rule overview.

  • To assign a ticket to the rule, continue with Create ticket assignment.