March 23, 2026

ON THIS PAGE

Introduction of the ThinkIQ chatbot, i3X API, bug fixes and other corrections.

New Features

ADDED:

Major New Features in this Release

i3X API

ThinkIQ introduces it's implementation of  i3X,  the industrial information interoperability standard for accessing data from type-aware systems via a standardized API. While the i3X API is still being actively improved, ThinkIQ has taken a first cut, implementing the latest spec as of this release. See the i3X documentation here and to get started explore the API with our own API key issued on a per-user basis.

ThinkIQ Chatbot

ThinkIQ introduces an AI chatbot built to natively understand the ThinkIQ Model, Material Movements, time‑series signals, and all other data integrated into the platform. Leveraging the enormous power of Large Language Models, user can now explore their model, build dashboards and create insights with the greatest tools. For more information contact your account manager.
 
 

Model Explorer

FIXED:
  • Model instances that were previously deleted and then readded could not be deleted again. This has been fixed.
  • When focused on an instance in the tree, using the 'Edit instance name' link in the right hand quick menu under the Overview tab -  which opens the Edit dialog -  was not allowing one to delete the instance and items under it. This has been fixed.
 

Connectors

FIXED:
  • Data ingestion now fails gracefully when bad data is sent to the server. 

    If a user maps a tag to an attribute with a mismatched data type, the system will

    • Either display NULL or empty data,

    • Or show the data in a default compatible format, without breaking ingestion.

      Previously, no data was shown.

  • The MQTT connector was not handling bad data or invalid payloads sent by the broker to the ingestion server. Now, the bad data is set to null and inserted into the table that is the same (data)type as the attribute. 
  • Data buffering has been improved on the Live Data connectors such as MQTT and OPCUA to buffer in larger chunks, allowing for higher overall data transmission rates. This is a configurable parameter in the Connector Configuration.
 

Integrated Development Platform

FIXED:
  • Updates have been made to manage unruly scripts that could cause runaway conditions. In particular, script executions have been capped to protect script execution time and resource usage. This is managed locally in the scripting environment and a second line of defense has been created on the web server. Additionally, a new 'reaping' process will now free up system threads for efficient usage.