Nexeed
    • Introduction
    • Concepts
      • Domain model
    • User manual
      • Device types
        • Manage or create a new Measuring Point for a device type
        • Manage or create a new error definition for a device type
        • Manage devices for a device type
      • Devices
        • Manage or create a new Measuring Point for a device
        • Manage or create a new error definition for a device
      • Topology
        • Navigate the topology
      • Error definitions
      • Measuring points
      • Processes
      • Process groups
      • Material definitions
    • Operations manual
      • Overview
      • System architecture and interfaces
      • System requirements
        • Equipment management service
        • Material service
        • Messaging service
        • Nginx gateway
        • Process service
      • Migration from previous versions
        • History of current versions
        • History of older versions
      • Setup and configuration
        • Helm configuration
        • Horizontal scalability for services in HELM deployments
        • Module health verification Endpoints and K8s probes
        • Data migration & synchronization
        • mmpd/equipment-service
        • mmpd/messaging-service
        • mmpd/process-service
        • mmpd/material-service
      • Start and shutdown
      • Regular operations
        • Deletion policy
        • Entities & fields
        • Resources and roles
      • Failure handling
        • Health verification Endpoints
        • Resiliency against failures in RabbitMQ
      • Backup and Restore
      • Logging and monitoring
      • Known limitations
    • API documentations
      • Equipment HTTP API
      • Process HTTP API
      • Material HTTP API
    • Glossary
Master Data Management
  • 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

  • Master Data Management
  • Operations manual
  • Migration from previous versions
  • History of current versions
preview v9.0.0

History of current versions

MDM 8.8.0

RabbitMQ upgrade preparation

As preparation for an upgrade to RabbitMQ 4, removed all deprecated RabbitMQ 3 features.

Migration of RabbitMQ queues

Classic queues are automatically transitioned to quorum queues during the services update processes. Messages are seamlessly migrated from the old queues to the new ones to ensure no data loss occurs.

Use of Kubernetes jobs for RabbitMQ queues migration

The Equipment and Material services now rely on initialization jobs to perform the RabbitMQ Queues migration:

  • Each service has a job set as dependency: the service will run only after the job is completed successfully

  • Each job runs only once. If it fails it will be restarted by kubernetes. If it completes it will never be run again.

MDM 8.0.0 / IAS 2024.01.01

Material Management

Material Management is added to MDM. It consists of a new service, a new UI added in the IAS Portal and a new set of public APIs.

In order for it to be accessible a user must be assigned one of the two new roles: Material Manager or Material Reader.

Use of Kubernetes jobs for DB migration

The Equipment, Process and Material services now rely on initialization jobs to perform the DB migration:

  • Each service has a job set as dependency: the service will run only after the job is completed successfully

  • Each job runs only once. If it fails it will be restarted by kubernetes. If it completes it will never be run again.

This scenario optimizes the DB migration when using horizontal scaling: All the instances of the same service will wait for one single DB migration job, and the job can run the DB migration scripts without multiple overlapping instances. Also, this job will not be affected by the k8s liveness / readiness probes.

MDM 7.1.0 / IAS 2023.02.02

Topology configuration

User can switch between 3 predefined topology configurations:

  • IAS Standard Template

  • Legacy Template

  • Custom Template (IAS + Legacy)

There is an automatic migration on service startup:

  • The former facility type IAS Area is renamed to Production Area

  • The facilities of type IAS Station are migrated to facility type Work Unit

  • Facility type IAS Station is removed

MDM 7.0.0 / IAS 2023.02.02

CMR Restrictions

MDM 7.0 brings breaking changes for customized installations in BMLP context. From now on, when CMR (Corporate Machine Registry) is available, more restrictions to MDM Topology are applied:

  • A facility of type MES Station can be installed (related/linked) on a MES Line only if a Device with a valid GIAI identifier is assigned to it.

Also, support in identifying potential interruptions of connected devices was introduced in MDM with the Predefined Properties on Device Type master data.

The Predefined Property can be directly applied on Device types and will enable registering on Devices the timespan elapsed before a deviation is triggered.

MDM 6.9.1 / IAS 2023.02.01.01

Update services base image to resolve CVE 2023 38545

Fix DB migration issue

Fix the migration issue related to already existing MDM_EventMessages table.

MDM 6.9.0 / IAS 2023.02.01

MDM supports the search and storage of GIAI machine identifier from Corporate Machine Registry(CMR)

The user is able to assign/generate a valid and unique GIAI identifier to a MDM Device, by searching in CMR.

As CMR is available only in the internal market context, this functionality cand be enabled / disabled based on the deployment configuration.

MDM 6.8.3 / IAS 2023.02.00.03

Update nginx base image

Fix DB migration issue

Fix the migration issue related to already existing MDM_EventMessages table.

MDM 6.8.2 / IAS 2023.02.00.01

Updated docker base image

Fixed missing event messages

Relation created messages are now sent when approving unknown devices or measuring points.

Facility delete messages are now sent also for children when deleting facilities with children.

MDM 6.8.0 / IAS 2023.02

Messaging service is added

This service will handle the RabbitMQ messages for all MDM services. It handles the communication with the message broker and also all errors that can appear in the process.

If an error appears, it will retry to send a message until it succeeds.

if the service is stopped it will resume from where it left when it is restarted.

Filter by technical Id is available in devices

The device screen now allows to filter by one or more Technical Ids.

MDM 6.7.0 / IAS 2023.01.02

Bugfixes and improvements

Added indexes on MDM_Relations table to improve performance. Various bugs are now fixed.

MDM 6.6.1 / IAS 2023.01.01

.NET Core is included in the MES packages for Sync & Mapping

These packages now have .NET built-in (self-contained deployment) and do not require the framework to be availble on the server.

MDM 6.6.0 / IAS 2023.01

MDM supports life-cycle logging

The life-cycle logging is now implemented according to the IAS requirements

New category added to measuring points

The "Measurement Counter" category is added in the measauring point categories and is available in both UI and Equipment Api

Added caching to APIs

The API responses are cached as long as there are no data changes. This brings a massive usability and performance improvement to Master Data Management.

Contents

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

Changelog Corporate information Legal notice Data protection notice Third party licenses