Nexeed
    • 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)
      • 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
          • 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
      • 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
        • 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
  • Industrial Application System
  • Core Services
    • Block Management
    • Deviation Processor
    • ID Builder
    • Multitenant Access Control
    • Notification Service
    • Ticket Management
    • Web Portal
  • Shopfloor Management
    • Andon Live
    • Global Production Overview
    • KPI Reporting
    • Operational Routines
    • Shift Book
    • Shopfloor Management Administration
  • Product & Quality
    • Product Setup Management
    • Part Traceability
    • Process Quality
    • Setup Specs
  • Execution
    • Line Control
    • Material Management
    • Order Management
    • Packaging Control
    • Rework Control
  • Intralogistics
    • AGV Control Center
    • Stock Management
    • Transport Management
  • Machine & Equipment
    • Condition Monitoring
    • Device Portal
    • Maintenance Management
    • Tool Management
  • Enterprise & Shopfloor Integration
    • Archiving Bridge
    • Data Publisher
    • Direct Data Link
    • Engineering UI
    • ERP Connectivity
    • Gateway
    • Information Router
    • Master Data Management
    • Orchestrator

Nexeed Learning Portal

  • Condition Monitoring
  • Operations manual
  • System architecture and interfaces
  • System components
preview 4.10.0

System components

Generic components

Component Rule Service App

Technology:

  • Java, Spring Boot i.e.

    • Web MVC

    • Actuator

    • Spring-Cloud-Stream

    • Spring-Data-JPA

  • Frontend:

    • JavaScript

    • TypeScript

    • Angular

Purpose:

  • Manage life cycle of rules and rule functions

  • Routing incoming OPP/PPMP data from RabbitMQ to appropriate rule functions in Apache Kafka (stateful or stateless) when rule context matches (device, device type or part type)

Interfaces:

  • HTTPS (REST)

  • Relational DB (JDBC over tcp)

  • RabbitMQ (AMQP 0.9.1 over tcp)

    • incoming OPP/PPMP measurements and machine messages

    • outgoing rule results

  • Kafka (Binary protocol over tcp) (not needed when Rules Management light is active)

    • outgoing PPMP measurements and machine messages

    • incoming rule results

  • Portal for UI-registration

  • MACMA for authentication/authorization

  • MDM for master data

Component Rule Value Provider (RVP)

Technology:

  • Java, Spring Boot i.e.

    • Web MVC

    • Actuator

    • Spring Boot Kafka Streams

Purpose:

  • Provides requested raw previous measurements or/and aggregated values (aggregation function) for given device and measuring points

Interfaces:

  • HTTP/HTTPS (REST endpoints for health and monitoring)

  • Kafka (Binary protocol over tcp)

    • incoming → PPMP data with request for previous raw values or aggregated values

    • outgoing → PPMP data enriched with previous raw values or aggregated values

Component Rule Value Aggregator (RVA)

Technology:

  • Java, Spring Boot i.e.

    • Web MVC

    • Actuator

    • Spring Boot Kafka Streams

Purpose:

  • Aggregates values (aggregation function) for given device and rules

Interfaces:

  • HTTP/HTTPS (REST endpoints for health and monitoring)

  • Kafka (Binary protocol over tcp)

    • incoming → PPMP data which should be aggregated by time (e.g. 1 minute)

    • outgoing → aggregated PPMP data

Component Rule Function Executor (RFE)

Technology:

  • Java, Spring Boot i.e.

    • Web MVC

    • Actuator

    • Spring Boot Kafka Streams

Purpose:

  • Executes functions for incoming messages and publishes their results

Interfaces:

  • HTTP/HTTPS (REST endpoints for health and monitoring)

  • Kafka (Binary protocol over tcp)

    • incoming → PPMP data enriched with previous values and functions to be executed

    • outgoing → PPMP data enriched with rule results (negative and positive)

Component Rule Result Aggregator (RRA)

Technology:

  • Java, Spring Boot i.e.

    • Web MVC

    • Actuator

    • Spring Boot Kafka Streams

Purpose:

  • Manages rule results and provides insights of rule behavior

  • Publishes rule results

Interfaces:

  • HTTP/HTTPS (REST endpoints for health and monitoring)

  • Kafka (Binary protocol over tcp)

    • incoming → PPMP data enriched with rule results (negative and positive)

    • outgoing → PPMP events for positive rule results

Component Stateful Function Executor

Technology:

  • Java, Spring Boot i.e.

    • Web MVC

    • Actuator

    • Spring-Cloud-Stream

Purpose:

  • Enriches incoming PPMP data with historic data

  • Collects historic data of measurement and/or machine messages executes stateful rules when Rules Light is enabled

Interfaces:

  • HTTP/HTTPS (REST endpoints for health and monitoring)

  • Influx DB (HTTPS over tcp)

  • RabbitMQ (AMQP 0.9.1 over tcp)

    • incoming PPMP measurements and machine messages

    • outgoing rule results

Component Condition Monitoring Core

Interface

  • HTTP/HTTPS (REST)

  • Influx DB (HTTPS over tcp)

  • Relational DB (JDBC over tcp)

  • RabbitMQ (AMQP 0.9.1 over tcp)

  • incoming OPP/PPMP measurements and machine messages

  • Portal for UI-registration

  • MACMA for authentication/authorization

  • MDM for master data

  • Deviation Processor

    • outgoing deviations from rule result

Technology:

  • Java, Spring Boot i.e.

    • Web MVC

    • Actuator

    • Spring-Cloud-Stream

    • Spring-Data-JPA

  • Frontend:

    • JavaScript

    • TypeScript

    • Angular

Purpose:

  • receive device information (measurements, events)

  • plot live-, historic-measurements and list events

  • see Condition Monitoring Core Database Schema

  • see Condition Monitoring Core Rest APIs

  • responsible for aggregating deferred OPP/PPMP measurements for displaying in the historic view

  • aggregating deferred OPP/PPMP measurements for displaying in the historic view

  • Integrates data analytics building blocks into the system (ESDS)

Description:

The CM Core component provides the basic features to receive device measurements and events and present them to the user, related to devices.

IAS/BMLP components

Component AI Services

Purpose:

  • Finds a causing event sequences, based on a list of events and a target event

  • see SDM - Concepts

Interfaces:

  • RabbitMQ (AMQP 0.9.1 over tcp) for internal communication - SDM Messaging & API

Description:

Finds a causing event sequences, based on a list of events and a target event.

Component Information Router

Purpose:

  • Authenticate Devices

  • PPMP/OPP schema validation

  • see Machine Connectivity

Interfaces:

  • HTTPS (PPMPv3 or OPPv0.9) → via ppmpOverRest or oppOverRest configuration in information router

  • RabbitMQ (AMQP 0.9.1 over tcp) → OPPv0.9 via oppOverAmqp configuration in information router

CM Information Router Communication

Description:

Connectivity provides the data from the machines on the shop floor to the upper-level systems and services and vice versa.

Component MACMA (Multitenant Access Control Management Application)

Purpose:

  • Authenticate user

  • Manage authorization (roles, permissions)

  • Administer system usage policy (authentication & authorization)

  • Manage tenants and their relations to each other

  • Provide Java clients / SSO libs

  • See MACMA

Interfaces:

  • HTTPS

  • DB (JDBC over tcp)

Description:

MACMA (Multitenant Access Control Management Application) is the central application within BCI to manage tenants, relations between tenants, users, clients and their respective roles.

Component MDM (Master Data Management)

Purpose:

  • Manage device types, measuring points, devices and facilities

  • See MDM

Interfaces:

  • HTTPS

  • DB (JDBC over tcp)

  • RabbitMQ (AMQP 0.9.1 over tcp)

Description:

MDM (Master Data Management) is the central application within BCI to manage device types, measuring points, devices and facilities.

Component Portal

Purpose:

  • Manage views and dashboards

  • see Portal

Interfaces:

  • HTTPS

  • DB (JDBC over tcp)

Description:

Manages all views and dashboards.

Component Deviation Processor

Purpose:

  • Manage all arising deviations within the IAS

  • See SM Deviation Processor Home

Interfaces:

  • HTTPS

  • DB (JDBC over tcp)

Description:

Manage all arising deviations within the IAS.

Contents

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

Changelog Corporate information Legal notice Data protection notice Third party licenses