History of older versions

MDM 6.5.0 / IAS 2022.02.02

MDM supports deployment via Helm

The MDM Helm chart is now available and supports the latest MDM version.

New features in equipment management

Import & export of device information details
Measurement points are now ensured to be unique per name + category
Errors are now ensurede to be unique per code + category

MDM 6.4.1 / IAS 2022.02.01

Memory leak fixed in equipment management service

A memory leak has been identified in the Equipment Management service. A small amount of memory is leaked on every request to the Equipment Api and becomes noticeable after a large number of requests (> 20000). This is fixed with version 6.4.1.

MDM 6.4.0 / IAS 2022.02.01

MDM is resilient against dependent services failures

MDM will automatically reconnect to its dependencies in case of failures.

MDM health endpoints reflect liveness and readiness

The complete health endpoints are now implemented: /health /ready /live /startup

Added facility Identifiers

Master Data Management 6.4 brings a mapping possibility between MDM Facilities and external systems identifiers. From this version, external identifiers management on facility level is available.

Along with this, the System Id of an MES instance can be available in MDM on facility level as a read-only identifier. The System Id will be stored in MDM when data is migrating from MES to IAS MDM.

Detection of parallel changes in process UI

A message pops up when attempting to save a process that was modified by another user in another session.

MDM 6.3.0 / IAS 2022.02

MDM supports subdomains

For the subdomain support a special release has to be built. An image of MDM works only in one scenario at a time: subdomain or relative paths but not both. It only supports the scenario it was built for - by default the releases are created and support the relative paths scenario.

MDM is resilient against RabbitMQ failures

MDM will automatically reconnect to RabbitMQ in case of failures.

Strict validation of the OpconLocationString

In order to fulfill MES requirements, starting with MDM 6.3 a more strict validation of the LocationId (OpconLocationString property) was introduced:

Facility property "OpconLocationString" is now unique per tenant. The user can no longer create multiple facilities with the same MES Location Id.
MDM ensures unique OpconLocation for all elements that are linked to a complete topology tree starting from Plant. *If IAS module need strictly unique OpConLocation then the ignore of the non-unique facilities when synchronizing data from MDM is necessary. The rule is: "Ignore all facilities where OpConLocation starts with #" in the database.

MDM will ensure uniqueness of the existing data during the automatic migration to the new release. This might require manual user intervention in the UI in order to fix the data.

Automatic migration rules
- The first character of duplicated OpConLocation strings is replaced with a #
- There is a warning message and the user is notified about the conflicts
- User / App engineer will have to manually fix conflicting elements in MDM Topology UI

New configuration option to allow deletion of facilities

Configuration attribute EQUIPMENT__TOPOLOGY__ALLOWFACILITYDELETION was introduced to restrict or permit the deletion of the Facilities. It can be set at deployment time and the default value is to allow the deletion of the Facilities (TRUE).

New process features

Starting with Version 6.3.0, Process Module supports bulk operation on Processes.
Additionally we are constraining Process Number to be unique per tenant.

To keep integrity of data, an algorithm was created to avoid deleting non-unique records in database.

Data Migration Algorithm

This algorithm is run on the start of the application. First, it validates that there are no duplicate Process Numbers per tenant. If the validation fails, then all Process Numbers are calculated accordingly:

rootProcessBase + (HierarchyLevel * hierarchyBase) + ProcessNumber

maxNumberFloored = Math.Pow(10, lengthOfMaxNumber + 1)
for (var i = 0; i < rootProcesses.Count; i++)
{
  rootProcessBase = (long)(maxNumberFloored * (i + 1))
  hierarchyBase = (long)maxNumberFloored / 10
  newProcessNumber = rootProcessBase + (HierarchyLevel * hierarchyBase) + ProcessNumber;
}

Level 0 - 1 → 10000

Level 1 - 100 → 11100

Level 2 - 500 → 12500

Level 2 - 700 → 12700

Level 2 - 800 → 12800

Level 2 - 900 → 12900

Level 1 - 200 → 11200

Level 0 - 1 → 20000

Level 0 - 2 → 30000

MDM 6.2.1 / IAS 2022.01.03

MDM bugfixes

Equipment service returns Forbidden on any tenant except BCI

MDM 6.2.0 / IAS 2022.01.02

MDM bugfixes

High CPU usage on Equipment Management service when receiveing lots of unknown measuring points through the message bus
Disconnecting from the message bus when receiving a message starting with "

Added process features

Starting with Version 6.2.0, Process Module supports deletion of SubProcesses and constraint of Process Number in Process hierarchy.

MDM 6.1.0 / IAS 2022.01.01

Equipment service restructuring

Starting with MDM 6.1, the entity services for Facilities, Devices, Measurement Points and Error Definitions are merged into Equipment Management Service.

The containers for the above services are removed. Equipment Management, Masterdata Management UI and Process remain as the active services.

The public APIs remain the same as before - all the adaptions are only MDM internal.

First release of process

Version 6.1.0 is the first release of Process Module.