On May 27, 2026, Germany’s TÜV Rheinland officially released the ‘AIoT Sensor Interoperability Certification’ (ASI-Mark), targeting smart sensors that support the MQTT/OPC UA protocols and feature edge data preprocessing capabilities. The first batch of certification covers three categories of sensors: pressure, temperature and humidity, and flow. Starting from Q3 2026, it will become a mandatory entry requirement in industrial IoT project tenders for German industrial clients such as Siemens and Bosch. This will have a substantial impact on related niche sectors such as industrial automation, smart manufacturing, sensor manufacturing, and system integration.

Event Overview

On May 27, 2026, Germany’s TÜV Rheinland announced the launch of the ‘AIoT Sensor Interoperability Mark’ (ASI-Mark). This certification applies to smart sensors that comply with the MQTT and OPC UA communication protocols and possess localized edge data preprocessing capabilities; the first batch of certification is limited to three product categories: pressure sensors, temperature and humidity sensors, and flow sensors; the certification is implemented through TÜV Rheinland’s global testing network, and a localized testing center has already been established in China; starting from Q3 2026, this certification will serve as a mandatory technical entry requirement for industrial IoT project tenders by companies such as Siemens and Bosch.

Which Niche Industries Will Be Affected

Sensor manufacturers

Reason for impact: The certification applies directly to sensor products themselves, and the first batch of covered categories are all high-frequency application types in industrial field environments. Products that do not obtain ASI-Mark certification will not be able to enter the approved supplier lists of relevant German companies.

Impact: Sensors exported to European industrial customers will need to simultaneously meet three technical thresholds: protocol compatibility, edge computing functionality, and data structure standardization; the certification cycle and testing costs will need to be incorporated into new product development processes; existing product lines that previously only met basic EMC or safety certifications (such as CE) will face upgrade pressure.

Industrial automation system integrators

Reason for impact: If a system integration solution uses sensors that have not obtained ASI-Mark certification, the entire solution will lose bidding eligibility in tenders issued by German companies.

Impact: During the solution design stage, the certification status of selected sensors must be reviewed in advance; project delivery cycles may be extended due to certification validation procedures; the technical responsiveness and certification progress of existing partner sensor manufacturers will need to be reassessed.

Domestic industrial IoT platform service providers

Reason for impact: If a platform relies on uncertified sensors as connected data sources, its joint solutions with German corporate clients will be constrained by the compliance status of terminal devices.

Impact: Platform compatibility statements must be updated in sync to the ASI-Mark support level; POC (proof of concept) projects for German-invested customers will require advance coordination of certified sensor samples; the platform’s edge-side data preprocessing logic must be adapted to the data formats and interaction timing defined by ASI-Mark.

What Key Points Should Relevant Companies or Practitioners Pay Attention To, and How Should They Respond at Present

Pay attention to updates on the ASI-Mark implementation rules and test cases officially released by TÜV Rheinland

What is currently most worth paying attention to is that TÜV Rheinland has not yet disclosed the complete test outline and evaluation thresholds (such as MQTT QoS level requirements, OPC UA information model versions, and upper limits for edge preprocessing latency). These details will directly affect the difficulty of product modification. Companies should subscribe to technical notices on its official website and track the supporting white papers that will be released successively starting in June 2026.

Prioritize sorting out the main sensor models for German-system customers and the corresponding certification schedules

From the analysis: Although pressure, temperature and humidity, and flow are the three product categories covered in the first batch, different models vary in the depth of protocol implementation (such as whether OPC UA PubSub is supported) and edge computing configuration (such as whether FFT or filtering algorithms are built in), so certification pass rates may not be equal. Companies should rank priorities according to customer order weight and concentrate resources on advancing certification for high-priority models.

Confirm the service capabilities and scheduling cycle of the localized testing center

From observation: The localized testing center established by TÜV Rheinland in China can shorten sample submission cycles, but not all test items (such as verification of specific OPC UA security configurations) can be fully completed locally, and some scenarios still require review by laboratories in Germany. Companies should contact the center as soon as possible to obtain the current average acceptance cycle and parallel testing capacity, so as to avoid delays caused by concentrated applications before Q3.

Differentiate between the execution milestones of ‘certification requirements’ and ‘certification status’ in tender documents

From an industry perspective: The mandatory certification requirement in tenders starting from Q3 2026 does not mean that all ongoing projects must immediately provide certificates; for projects where framework agreements have already been signed but equipment procurement has not yet started, there may be a transition window. Companies need to review one by one the effective date definitions in the latest version of customer tender clauses (such as whether they are defined by the RFP release date, bid submission deadline, or contract signing date), so as to avoid misjudging the compliance timing.

Editor’s Viewpoint / Industry Observation

Observably, this ASI-Mark is not simply the addition of another voluntary certification, but rather uses the procurement rules of leading German companies as a fulcrum to turn interoperability from a technical倡议 into a supply chain access reality. At present, it is more like a clear compliance signal rather than a fully implemented result——the certification system has just been launched, the testing rules are still being refined, and the first batch only covers three product categories, without yet extending to other industrial sensor dimensions such as vibration, gas, and vision. What the industry needs to continue watching is: whether the certification scope will subsequently extend to edge devices such as actuators and gateways; whether ASI-Mark will be bundled with IEC 62443 cybersecurity certification requirements; and whether, besides Siemens and Bosch, other German manufacturers (such as Festo and Heller) will follow up by adopting the same standard.

Conclusion: The ASI-Mark launched by Germany’s TÜV marks that the industrial AIoT field is accelerating from “able to connect” to “able to use well”, and interoperability is becoming a hard technical infrastructure requirement. At present, it is more appropriate to understand this as: a supply chain compliance upgrade with clear time nodes, clear applicability boundaries, and already tied to real procurement behavior, rather than a long-term technical vision. Relevant companies should use Q3 as a countdown anchor, focus on product-level protocol adaptation and certification pathway management, and avoid misreading the policy signal as a broad technology trend.

Description of information sources:
Main source: Announcement on the official website of Germany’s TÜV Rheinland on May 27, 2026 (‘AIoT Sensor Interoperability Mark Launch’)
Parts requiring continued observation: full text of the ASI-Mark testing rules, certification pass rate statistics for each product category, and the expansion timetable for sensor categories not covered in the first batch