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
  • Migration from previous versions
  • Migration to 4.8.x (Nexeed IAS 2025.02.00.x)
preview 4.10.0

Migration to 4.8.x (Nexeed IAS 2025.02.00.x)

Migration of deviation notifications (limitation: version 4.5.0 was not deployed on the system before)

To create Hit of Event rules from Deviation Notifications, set the rs_create_rule_from_deviations_tenant_ids variable with the relevant tenant IDs before migration. This step is only necessary if version 4.5.x, 4.6.x or 4.7.x was not previously deployed on the system. If version 4.5.x, 4.6.x or 4.7.x was already deployed, the Hit of Event rules have already been created.

Enable forwarding of machine messages as deviation

To enable forwarding machine messages as deviation set the cm_core_deviation_forward_machine_messages_tenant_ids variable with the relevant tenant IDs. Attention: If version 4.5.x, 4.6.x or 4.7.x was previously deployed on the system Hit of event rules are already existing for some machine messages. Activating the forwarding could lead to multiple deviations created by one machine message.

Migration of RabbitMQ classic queues to quorum queues to be compatible with RabbitMQ 4

Condition Monitoring services automatically migrate RabbitMQ classic queues to quorum queues during startup. After starting the services, verify the migration status by filtering q.cm in the queues tab of the RabbitMQ Management UI. If some queues are not migrated, review the service logs and try restarting a pod. Note: Due to a bug in the Spring RabbitMQ client, some auto-delete classic queues without consumers may still appear in the RabbitMQ Management UI after migration. These queues are no longer used by Condition Monitoring services and can be deleted manually.

The migration tool requires the RabbitMQ management URL (managementUrl) and port (adminPort). In a Radium environment, you can provide these settings as shown below:

global:
  serverInstances:
    externalRabbit:
      host: xref:operations:06_setup_and_configuration/_shared_variables/common-rabbitmq-shared-variables.adoc#rabbitmq_host[rabbitmq_host]
      port: xref:operations:06_setup_and_configuration/_shared_variables/common-rabbitmq-shared-variables.adoc#rabbitmq_port[rabbitmq_port]
      tls: xref:operations:06_setup_and_configuration/_shared_variables/common-rabbitmq-shared-variables.adoc#rabbitmq_tls_enabled[rabbitmq_tls_enabled]
      type: RABBITMQ
      default: true
      adminPort: <<management_port>>
      managementUrl: <<management_url>>

Contents

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

Changelog Corporate information Legal notice Data protection notice Third party licenses