Release 3.5
Kelvin SDK
- New Emulation System & Emulation configuration based on the app.yaml. The
systemconfiguration now applies to emulated applications. - Support for the new simplified app configuration as well as the new MQTT implementation.
Kelvin Connect
One of the most significant features of this release is the launch of Kelvin Connect v1.0 for OPC-UA protocol. Kelvin Connect is a part of our broader edge computing product strategy (Kelvin Edge) and is designed to make connection to machines and data sources like historians, PLCs, etc. in a manufacturing facility a breeze with a wizard based UI.
With Kelvin Connect, users can now easily create a bridge between OT data sources and the KICS software, map the OPC tags and metrics, and easily decide to bring the most relevant data into the KICS platform to do machine learning and / or to run applications.
In the current release, Kelvin Connect offers OPC-UA connectivity. Our intent is to extend the capabilities of Kelvin Connect in subsequent releases to offer additional OT + IT data integration capabilities as well.
Asset Model
An equally significant and long awaited development that we are introducing in this release is the introduction of 'Assets' and 'Asset Model' in our platform. Until now customer's machines / assets were identified in KICS software in correlation with the Node (gateways) which is not the right representation of assets, especially as our customers are scaling and there are scenarios where more than one asset could be connected to a Node.
In this release, we are introducing the 'Asset' representation and modeling capabilities. We are decoupling 'Assets' from 'ACPs' and renaming ACP to a more market and customer friendly term 'Node'.
The asset model definition in the platform will now allow us to bring new use cases in the following releases like asset representation in a hierarchy (July release), Asset health monitoring (August release), etc. The 'Nodes' on the other hand will represent the IT workloads and information (bridges, connections, other workloads running on the gateway and their health). Together this Asset + Node view will offer our customers complete operational intelligence about their facility and infrastructure -- something which is going to be a key differentiator of our software.
Move to MQTT in Kelvin Core
One of the bedrocks of the KICS platform has been it's modularity and flexibility to run and manage multiple workloads across various 'Nodes'. As 3rd party workloads and services are becoming more and more modular, we want to create a framework that will allow our customers, partners and acceleration teams to easily extend and plug'n'play additional software and services on the platform without the need for code change or engineering intervention.
With that in mind, we are making a significant move away from OPC-UA as the 'transport' mechanism between workloads in Kelvin Core at the edge to a more user and ecosystem friendly pub-sub mechanism based on MQTT.
With this change, it's now easy for customers and partners to bring their own workloads and 'subscribe' to the MQTT queue in Kelvin Core. These workloads could be packaged applications, data science models, other services (ex: Object DB, custom system integration, etc.).\