SOT
    • Introduction
    • User manual
      • Condition monitoring and its tabs
        • Live
        • Counters
        • Measurements
        • Events
        • Rules
        • View configuration
        • Details
      • Rules management
        • Rule types and standard functions
        • Rule details
      • Function configuration
      • Condition Monitoring widgets
      • Access Management
        • Application Roles
        • Fine-Grained Access Control and Configuration
        • How to Configure Organization Roles
    • Operations manual
      • Overview
      • System architecture and interfaces
        • System components
      • System requirements
        • General notes
        • cm/condition-monitoring-core
        • cm/rule-service-app
        • cm/rule-function-executor
        • cm/rule-result-aggregator
        • cm/rule-value-aggregator
        • cm/rule-value-provider
        • cm/stateful-function-executor
      • Migration from previous versions
        • Migration to 2.1+
        • Migration from CPM 1.5.4 to CM and RM 3.0.x (Nexeed IAS 2023.02.00.xx)
          • CPM to CM relational database migration
          • CPM to RM relational database migration
          • CM Influx database migration
          • Deletion of an old CPM installation
        • Resources mapping from MES to IAS Condition Monitoring
        • Migration to 4.0.0+ (Nexeed IAS 2024.01.00.xx)
        • Migration to 4.3.x (Nexeed IAS 2024.02.01.x)
        • Migration to 4.5.x (Nexeed IAS 2025.01.00.x)
        • Migration to 4.6.x (Nexeed IAS 2025.01.01.x)
        • Migration to 4.8.x (Nexeed IAS 2025.02.00.x)
        • Migration to 4.9.x (Nexeed IAS 2025.02.01.x)
        • Migration to 4.10.x (Nexeed IAS 2025.02.02.x)
        • Migration to 4.11.x (Nexeed IAS 2026.01.x)
      • Setup and configuration
        • Manual MACMA configuration after setting up a new tenant
        • RabbitMQ
        • Influx configuration
        • Kafka topics
        • Condition Monitoring - Helm Configuration
        • Advanced configuration parameters
          • cm/condition-monitoring-core
            • Common shared variables
            • Portal shared variables
            • MDM shared variables
            • RabbitMQ shared variables
            • OTEL shared variables
            • Graceful shutdown shared variables
          • cm/rule-service-app
            • Rules Management shared variables
            • KAFKA shared variables
          • cm/rule-function-executor
          • cm/rule-result-aggregator
          • cm/rule-value-aggregator
          • cm/rule-value-provider
          • cm/stateful-function-executor
        • Fine-Grained Access Configuration
      • Start and shutdown
      • Regular operations
      • Failure handling
        • Rule Management Light Helm installation failing when Kafka is disabled or Kafka is not configured at all
        • User manual injection into Rule Management
        • Infrastructure outages: health verification Endpoints
        • OPP/PPMP are not received in CM
        • Master data (Devices, Facilities, Measuring Points, DeviceTypes) is missing in CM
        • Condition Monitoring Domain is missing in Ticket Management
        • CM is not visible in the portal
        • How to verify if the broker is out of sync
      • Backup and Restore
      • Logging and monitoring
        • General logging characteristics
        • Required monitoring
        • General logging format
        • Request-based logging format
        • Security logging format
        • Lifecycle logging format
        • Module health Endpoints and K8s probes
      • Known limitations
    • API documentation
      • Condition Monitoring HTTP API
      • Rules Management HTTP API
    • Glossary
Condition Monitoring
  • Smart Operations Toolkit
    • Deviation Processor
    • Multitenant Access Control
    • Notification Service
    • Ticket Management
    • Web Portal
  • Shopfloor Management
    • Andon Live
    • KPI Reporting
    • Operational Routines
    • Shift Book
    • Shopfloor Management Administration
  • Product & Quality
    • Process Quality
    • AI Services
  • Machine & Equipment
    • Condition Monitoring
    • Device Portal
  • Enterprise & Shopfloor Integration
    • Information Router
    • Master Data Management

SOT Learning Portal

  • Condition Monitoring
  • User manual
  • Condition monitoring and its tabs
  • Events
preview 4.11.2 4.11.1 4.11.0

Events

When a device is selected in the Performance Analysis > Condition Monitoring menu, the Events tab is available. This tab shows all events created by rules or machines, helping users quickly find and understand potential problems. The AI feature "Event Sequence Detection" looks at connections between events to help spot issues early.

cm_event_list_view_2023_02

The following display options are available:

  • The List tab displays events in a list and trigger event sequence detections

  • The Grouped List tab Display events in a grouped list and count the number of occurrences of each event.

  • The Chart tab view the events in a chart, based on the timeline. It is possible to zoom in and out of the chart and navigate through time.

  • The Event sequences tab displays calculated event sequences of the AI Service.

List tab

Machine messages, technical information and rule events of the device are displayed in a table in the detailed view under the Events tab in the List sub-tab. By default, the results of the last 24 hours are displayed. Here its also possible to trigger event sequence detection.

cm_event_list_view_2023_02
Element Description

XX entries

Number of events

filter Filter

Filter the overview by selecting Time Range , Event Code , Severity and Title in the dialog window.

fullscreen

Open full-screen mode.

The full-screen mode can be closed with [ESC].

Code

Code defined in the triggered rule or code of the machine message

Title

Description of the triggered rule or of the machine message

Time

Time at which the event occurred

bar-chart-search-detail

If the Backend-Service AI Services module is installed, event sequence detection is available.

Trigger Event Sequence Detection

forward-right down

Expand or collapse all details of the event.

Grouped list tab

Machine messages, technical information and rule events of the device are displayed in a table grouped by priority, code, title and number of events in the detailed view under the Events tab in the Grouped List sub-tab.

cm_event_group_list_view_2023_2
Element Description

XX entries

Number of events

filter Filter

Filter the overview by selecting Time Range , Event Code , Severity and Title in the dialog window.

fullscreen

Open full-screen mode.

The full-screen mode can be closed with [ESC].

Code

Code defined in the triggered rule or code of the machine message

Title

Description of the triggered rule or of the machine message

Count

Number of times the event occurred

Time

Time when the event last occurred

forward-right down

Expand and collapse all details of the event.

Chart tab

Device events (machine messages, rule results, technical information) are displayed in a graphical view in the Chart tab under the Events tab in the detailed view.

cm_event_chart_view_2023_02
Element Description

XX entries

Number of events

filter Filter

Filter the overview by selecting Time Range , Event Code , Severity and Title in the dialog window.

fullscreen

Open full-screen mode.

The full-screen mode can be closed with [ESC].

back-left forward-right

Navigate forward or back by half an hour.

zoom_out zoom-in

Zoom in and out.

To select an area, draw a rectangle with the mouse.

Event sequences tab

If the Backend-Service AI Services module is installed, event sequence detection is available.

Calculated event sequences of the AI Service are displayed in the Event Sequences tab under the Events tab in the detailed view.

cm_event_event_view_2023_02
Element Description

X item/XX items

Number of event sequences

filter Filter

Filter the overview by selecting Time Range , Event Code , Severity and Title in the dialog window.

fullscreen

Open full-screen mode.

The full-screen mode can be closed with [ESC].

Target event

Error code defined in the triggered rule

ppm_icon_exclamation_mark

The icon is displayed if there is no event sequence. This could be for the following reasons:

  • There are no events in the specified time period.

  • There are fewer than three target events in the data.

Created by

Time at which the event sequence was created

Time period in consideration

Period of time monitored by the event sequence

Number of target events (in consideration)

Specifies how many times an event sequence was triggered.

Status

Status of the event sequence:

DONE

The event sequence is complete.

STARTED

The event sequence is running and monitoring the set target event.

NOT STARTED

The event sequence has not yet started.

ppm_icon_event_sequence_detection

Display event sequence detection details.

Event Sequence Details

Event Sequence details

If the Backend-Service AI Services module is installed, event sequence detection is available.

If ppm_icon_event_sequence_detection is selected for a row in the Event Sequences tab, the details of the event sequence will open. In the details, event sequences can be identified based on their relevance.

cm_event_sequence_detection_2023_01
Element Description

Target event

Code of the rule or machine being examined.

Number of target events (in consideration)

Number of times the target event occurred

Date of execution

Time at which the event sequence detection was created

Time period in consideration

Period of time monitored by the event sequence detection

Status

Event sequence detection status:

DONE

Event sequence detection is complete.

STARTED

The event sequence is running and monitoring the set target event.

NOT STARTED

Event sequence detection has not yet been started.

Sequence time period (hours)

Time period in hours monitored by the event sequence detection

Time period selected

Period of time selected for the event sequence detection

Comments

Additional information on the event sequence detection

Sequence

Name of the rule triggered by the event sequence detection

Relevance

The relevance indicates how well event sequence detection leads to the target event.

Event Sequence Detection Details

Trigger Event Sequence Detection

If the Backend-Service AI Services module is installed, event sequence detection is available.

Prerequisites

  • Condition Monitoring User or Condition Monitoring Administrator role

  • An event is triggered.

Procedure

  1. Call up the Efficiency analysis > Condition monitoring menu.

  2. Select device.

  3. In the detailed view, call up the Results tab.

  4. Open the List tab.

  5. Open the event sequence in the event row with bar-chart-search-detail.

    cm_Event_Sequence_2023_01
  6. Select date/time period :

    • Select a time frame.

    • Select the time range from the drop-down list.

      Or:

    • Select the time range.

    • Select the date or date range using the calendar.

    • Select the time using the Start time and End time fields.

  7. Enter a Comment.

  8. Trigger the event sequence with Save.

Event sequence detection is triggered and displayed in the Events Tab — Event sequences.

Event Sequence Detection details

If the Backend-Service AI Services module is installed, event sequence detection is available.

When using event sequence detection to find a specific event target, the event sequence detection analyzes event data, such as rule results and machine messages. Event sequence detection can be used to detect anomalies before an event target is reached.

A rule can be created for event sequence detection. A rule is triggered as soon as the specified sequence occurs. In this way, certain behaviors can be identified so that they can be responded to as quickly as possible.

The event sequence detection calculates the following variables:

  • Confidence

    Confidence indicates how often the event target occurs after the sequence.

  • support

    Support indicates how often the sequence occurs before the event target.

  • Relevance

    Relevance is the geometric mean value of Confidence and Support.

Prerequisites

  • Production planner or Administrator role

  • The Backend-Service AI Services module has been installed.

  • At least two event targets have occurred during the specified time period.

Example calculations

ppm_sequencedetection_example
Performance size Description Calculation

Confidence

In 6 (= dark red A or C) out of 9 (= dark red A or C) cases, the event target (= T) occurs after the sequence.

Values in the event sequence details:

Event Sequence Details

Target event and sequence/number of (viewed) target events = confidence value

ppm_cal_confidence

support

In 6 (= dark red A or C) out of 8 (= T) cases, the sequence occurs before the event target (= T).

Values in the event sequence details:

Event Sequence Details

Target event and sequence/(target event and sequence + sequence without target event) = support value

ppm_cal_support

Relevance

The relevance indicates how well event sequence detection leads to the target event.

Values in the event sequence details:

Event Sequence Details

√ (confidence value + support value) = relevance value

ppm_cal_relevancy

Contents

© Robert Bosch Manufacturing Solutions GmbH 2023-2026, all rights reserved

Changelog Corporate information Legal notice Data protection notice Third party licenses