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)
        • 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
      • 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
  • 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
    • 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.11.x (Nexeed IAS 2026.01.x)
preview 4.11.0 4.10.1 4.10.0

Migration to 4.11.x (Nexeed IAS 2026.01.x)

Assign Service Account Role "Ticket Context Registrar" to Condition Monitoring (CM) Module

Overview

A new service account role "Ticket Context Registrar" is required for the Condition Monitoring (CM) module. This role enables CM to register domain context information for each tenant when the Ticket Management module is installed.

Prerequisites

  • Ticket Management module must be installed

  • Service account roles configuration must be accessible

Role Assignment Methods

Automatic Assignment (tenant-0)

For the BCI tenant (tenant-0), the "Ticket Context Registrar" role is automatically assigned by the macma-operator during upgrade.

Customer Tenants

For existing customer tenants, the role assignment can be done through two methods:

Method 1: Automated Assignment (Recommended)
  • An adhoc job can be created by ansible-operator to assign the role

  • Automatic role assignment process is described in Nexeed IAS Ops Manual 2026.01 (Chapter 8.4 - Automatic module role assignments in customer tenants)

Method 2: Manual Assignment
  1. Navigate to Nexeed Portal

  2. Go to Access Management → Modules → Condition Monitoring

  3. Select Assign Role (Ticket Context Registrar)

Post-Assignment Behavior

Automatic Registration

When the role is successfully assigned, the Condition Monitoring module will automatically register its domain context attributes in Ticket Management during startup for each tenant that includes both:

  • Condition Monitoring module

  • Ticket Management module

Manual Registration (Fallback)

If automatic registration fails or the role is not assigned, manual domain context registration is required.

  • Reference: CM Domain Context Registration in Ticket Management

Additional Information

  • Service Account Roles Documentation: Service Account Roles needed by Condition Monitoring (CM)

  • Role Details: Ticket Context Registrar

Authorized Module Health Endpoint Added

Overview

A new authorized module health endpoint has been added to the Condition Monitoring module. This endpoint complements the existing service health endpoints and provides comprehensive health status information for the module and its dependent services.

Key Features

  • Protected Access: Health endpoints are secured and require proper authorization

  • Role-Based Access: Only users with the "Operator" or "Condition Monitoring Administrator" role can access these endpoints

    • MDM Sync API: Users with "Operator" role can trigger data synchronization from MDM to Condition Monitoring

Role Assignment

Automatic Assignment (tenant-0)

For the BCI tenant (tenant-0), the "Operator" role will be automatically assigned by the macma-operator during the upgrade process.

Manual Assignment (Customer Tenants)

For existing customer tenants, the "Operator" role assignment must be done manually by creating new contracts in MACMA.

  • Process: Create contracts in MACMA as described in the documentation

Additional Information

For detailed information about the module health endpoints, refer to Module Health Endpoints.

Contents

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

Changelog Corporate information Legal notice Data protection notice Third party licenses