Historian & Trending
What are the historian & trending functions?
Audience: This page is intended for readers without a technical background. It explains how Mantsu stores historical process data and how you can build trends and reports on top of it.
The historian in Mantsu records time series process data from the Unified Namespace, and the trending functionality lets you visualise and analyse that history. Both are performed in the reporting application. This is a separate application not created in the Mendix low-code platform.
What does the reporting application do?
The reporting application is a custom high-code application that serves as the primary operational interface for data consumers. It is designed to:
- Connect to multiple data sources: MQTT topics from OT edge nodes and Kafka topics from the Redpanda broker.
- Contextualize data streams: users can map raw topics to meaningful process variables, add metadata, and define a Unified Namespace (UNS) structure.
- Configure dashboards and reports: operators and engineers can build and manage their own views without developer intervention.
The application is developed using a high-code approach (as opposed to the low-code Mendix services), allowing full flexibility in data handling and visualization logic.
Summary: Historical process data and trending live in the customer owned reporting application, which connects to MQTT and Kafka topics, contextualizes them into the UNS, and lets users build their own dashboards without developer intervention.