Release Notes for IAH SaaS Application

Release Notes 2025.06

Bugfixes

June 11, 2025

• Fixing issue with not applying access group configuration correctly. Consequently, users will lose access to an asset, if not being assigned to the asset's access group. To restore access, administrator needs to configure access groups as needed.

June 3, 2025

• New version (1.3.1) of Industrial Edge App "Asset Link SNMP" fixing issue of missing <Article number> and <Vendor> when discovering assets via SNMP.

Release Notes 2025.05

May 2025

Enhancements

• Asset Gateways are managed in a view separate from the general Asset List.
• ID Link information is displayed in Asset details view.
• MAC- and IP-address relations are displayed in Asset details view.
• The responsible of an asset is displayed using assigned e-mail address.
• A dedicated asset gateway management page has been added in this version. All asset gateway related functionality has been removed from the asset list page and transferred to the new page. The impact of the separation affects only the graphical user interface and is independent of the backend APIs.
• Access groups are no longer case sensitive. If an access group with the same name (ignoring case) already exists, a conflict error will be returned when attempting to create a new group with the same name.

Inventory-Service API

v1-earlyaccess

• The API now enables asset filtering with full-text search.
• The API now supports asset grouping with pagination and sorting on properties.
• The API now enables adding a responsible to an asset:
• The user onboarding an asset automatically becomes asset responsible.
• The responsible user for an asset can be changed.
• The API now provides metrics for discovery results, i.e., number of assets found, updated, rejected, failed and duplicate assets.
• The API now provides a metric indicating whether the assets of a device discovery follow the asset schema.

v2-earlyaccess

• The API now validates an asset against the provided schema.

Discovery-Service API

v1-earlyaccess

• The API now provides comprehensive information about the results of a discovery job:
• Total number of assets detected.
• Newly detected assets: The number of assets identified for the first time.
• Updated assets: The number of assets already present and updated by a scan.
• Duplicate assets: The number of assets identified as duplicates with a different asset link.
• Rejected assets: The number of assets rejected by the inventory and not captured at all.
• Failed assets: The number of assets that failed due to an internal error.

v2-earlyaccess

• The API now provides an endpoint to get details of a discovery job.
• The API now supports canceling a discovery job.
• The API now enables deleting a discovery job.

Remote-Access-Service API

v2-earlyaccess

• The API now provides an endpoint to get details of a remote access job.
• The API now supports canceling a remote access job.
• The API now enables deleting a remote access job.

Onboarding-Service API

Notice: The following deprecated APIs and depending endpoints of the authorization service will be removed with the release after IAH 1.3

• /authorization/v1-earlyaccess
• /authorization/v1

WFX-Service API

Notice: The following deprecated APIs and depending endpoints of the WFX service will be removed with the release after IAH 1.3

• /cdm/v1/jobs

Inclusion of Default IP scanner

Boundary conditions

• The Default IP scanner is included in the Asset Gateway. It will come as a pre-installed Asset link bundled with the Asset Gateway.
• It will scan all the reachable assets in the network.
• Currently, the Default IP scanner returns the IP address, MAC address, hostname and vendor of the assets scanned, with other attributes planned for future scope.
• One subnet per scan supported for current release, for multiple subnet scans multiple scans need to be triggered.

Compatibility

• Asset Gateway v1.3.1 or higher is required to use Default IP scanner as an edge app only.
• Layer-2 needs to be enabled in the Industrial Edge Device.
• If the Asset Gateway is installed locally via docker compose, the default ip scanner feature will not be available, as it is only supported in the siemens edge app.

Release Notes 2024.10

October 2024

Enhancements

• The total number of assets found is displayed in the job management.
• Special characters are allowed for vendors when adding assets manually.
• The Access management page is extended with the possibility to manage Access groups.
• The inventory API enables asset filtering for arrays.
• Remote connection is closed automatically if the Asset/Asset Gateway is deleted.

API Deprecation in Authorization Service

• The API endpoint /check is deprecated. Please use /access-groups/check instead.
• The API endpoint /users/me/zones is deprecated. Please use /users/me/access-groups instead.
• The API endpoint /zones/check is deprecated. Please use /access-groups/check instead.

Release Notes 2024.09

September 2024

API Deprecation in Authorization-Service

Api endpoint /check becomes deprecated

• The API endpoint /check of the authorization-service has been deprecated. Use /zones/check instead.

Release Notes 2024.07

July 2024

Remote Access out of feature flag

Preview features behind feature flag in 2024.07

Authorization-Service

Breaking Change - API Version Update

• The API version of the authorization-service has been changed from v1 to v2. The new version introduces the zone concept, which must be enabled via feature flag. Although the v1 version remains unchanged, once the zone concept feature gets effective, those assets which are assigned to a zone, will only be visible to assigned users.

• Grace Period: To provide a smooth transition, the old API path will be maintained. During this time, both the old and new API paths will be supported.

• Action Required: If you are currently using the authorization-service API, please update your integrations to use the new API path (v2). It is recommended to migrate as soon as possible to avoid any disruptions after the grace period.

Release Notes 2024.04

April 2024

Preview features behind feature flag in 2024.04

Authorization-Service

Breaking Change - API Version Update:

• The API version of the authorization-service has been changed from v1-earlyaccess to v1. This is a breaking change that may require updates to your integrations.

• Grace Period: To provide a smooth transition, the old API path will be maintained. During this time, both the old and new API paths will be supported.

• Action Required: If you are currently using the authorization-service API, please update your integrations to use the new API path (v1). It is recommended to migrate as soon as possible to avoid any disruptions after the grace period.

Release Notes 2024.03

March 2024

Preview features behind feature flag in 2024.03

Remote Access

Boundary conditions

• Currently, only one remote connection per tenant is supported. Disconnect the existing remote connection before establishing a new remote connection.
• An established remote connect session is valid for a maximum of 12 hours after which it is automatically terminated.
• Remote connection to an Asset Gateway is currently not supported.
• An asset to which remote connection is being established should be exposing a web server, have a discoverable IP address and is to be attached with an Asset Gateway.
• Cross check if the port that is specified while establishing the remote connection is the correct port on which the web server is exposed. If the port specified is incorrect, the remote session will be established successfully but not usable.
• The system cannot detect if a remote connection is active while an asset or gateway is being "Deleted"/"Ignored" or "Offboarded". The active remote connection must be disconnected for that asset before doing such operations.
• If the gateway via which a remote connection is established is abruptly disrupted (powered off, network loss, etc.). while a remote connection is active, the "Delete API" must be manually executed to close the connection gracefully.

Compatibility

Minimum component versions to support the Industrial Automation Hub.

These components support the asset model schema version 0.7.0.

Release Notes 2023.10 (V1.0)

October 2023

Usage

This release is targeted to find as many assets as possible via network scans or by manually adding them to the inventory. With this release a preview on the Industrial Asset Hub (IAH) is provided for incubation customers. Via the scan functionality discovers connected automation (OT) devices with the information of product type, serial number and installed firmware version so that they can understand possible issues in production and schedule mitigation accordingly.

Content

The release of v1.0 Identify Otto's Assets is the first productive release of the Industrial Asset Hub:

• Implement multi-tenancy on application layer
• Industrial Asset Hub integrates with the Xcelerator foundation gateway (XF-Gateway) to separate tenants
• Device builders are enabled with a software development kit for Asset links
• Enhancement for a better overview and navigation in the UI:
• Grouping of devices
• Search bar with free text search
• Advanced device details
• Improved handling of custom tags
• User interaction via keyboard
• Support Asset Modelling:
• Support a device agnostic platform for easy support of new asset types
• Well documented and tool supported modelling language
• Extensions for consumption outside Industrial Asset Hub are possible
• Industrial Asset Hub provides a fluent user experience for a quantity structure of 2000 device per tenant
• Industrial Asset Hub introduces the artifact update service:
• Users can create, upload, check and manage updates
• Available update files are associated with the devices based on the meta data and can be installed by the user remotely through the Industrial Asset Hub infrastructure

Boundary conditions

• Per scan only one Asset Link can be chosen from the drop down menu. In order to perform multiple scans in one Asset Gateway, multiple jobs need to be triggered sequentially.
• After triggering a discovery job, a hexagon appears. When changing the tab and switching back, the hexagon doesn't reappear to signal that the discovery job is still running.
• Upgrade the Asset Gateway app greater or equal to the 0.3.10 version, in order to be able to perform device discoveries.
• Cross Asset link update is not supported.
• Unknown device classes are not supported.
• The new gateway onboarding feature will require to re-onboard all connected field agents according to the description in the user manual.
• Grouping for multi-value columns isn't possible within the Asset list (i.e. MAC, IP and Custom tags).
• Filtering and grouping cannot be used in combination.

Compatibility

Minimum component versions to support the Industrial Automation Hub.

These components support the asset model schema version 0.7.0.

Any questions left?

Ask the community