This multi–bottling line solution collects data from a MES system and displays it in dashboards, including OEE and other KPIs. 

How-to → Examples → Industry → ProveIt

UNS

The Proveit solution organizes its data model following a Unified Namespace (UNS) structure. The UNS defines a standardized hierarchical tag structure that serves as the single source of truth for all operational data across the plant. It is organized by site, production area, and individual machines, ensuring consistent data access and interoperability throughout the system.

Sites +-- Site1 +-- FillerProduction | +-- FillingLine01 | +-- CapLoader | +-- Filler | +-- Filler_Sim | +-- Washer +-- Packaging | +-- LabelerLine01 | +-- Labeler | +-- Packager +-- Palletizing +-- Palletizer01 | +-- Pallet01 | +-- Pallet02 +-- RobotPalletizer01

Each machine object listed above contains the following set of properties:

Displays

The Proveit solution includes a set of pre-built displays designed to provide comprehensive visibility into plant operations. The layout system supports three responsive modes — Desktop, Pad, and Mobile — allowing users to switch between them depending on their device.

The Home display serves as the initial landing page. From there, users can navigate to the Site display, which provides an overview of status, current downtime, production, and rejects for each machine in the site. The Area display drills deeper, showing OEE information, top downtime reasons, and rejects for each machine within a specific production area. The Line display presents production information along with a layout view of the line.

For OEE analysis, the solution offers multiple perspectives: OEE By Day shows OEE values with bar and line charts, OEE Bars provides a focused bar chart view, OEE by Time tracks OEE by smaller time buckets such as hours or intervals, and OEE Calcs explains the OEE calculation methodology.

Downtime analysis is covered by three displays: Downtime Timeline visualizes downtime events on a timeline filtered by time range, Downtime Summary presents a Pareto view of top causes and durations, and Downtime Edit allows operators to correct downtime events including reasons, categories, and timestamps. The Grid View display enables users to view production, events, and downtime data in a filterable table format.

The AI display provides access to the machine learning algorithms described in the ML.NET Forecasting section. Additionally, the Logon display manages user authentication and sessions, and the Theme display allows users to customize the UI appearance between light, dark, and contrast modes.

MQTT

The solution communicates with the plant floor through MQTT, connecting to a virtual factory broker at virtualfactory.proveit.services on port 1883. Two channels are configured: a read-only Tag Provider that subscribes to real-time data with a 500ms read cycle, and a write-enabled Device channel used to publish new values back to the broker.

read-only Tag Provider:

write-enabled Device:

Dataset

The solution uses a SQL Server dataset named CoreM, connected through the System.Data.SqlClient provider. The database is hosted on the frameworx server and stores the core operational data used across the solution, including production records, downtime events, and OEE calculations.

ML.NET

The Proveit solution includes a Machine Learning algorithm built with ML.NET and C#, designed to forecast hourly production output for a filler machine. All Machine Learning algorithms were implemented entirely through Script Tasks and Script Classes within FrameworX, requiring only the import of ML.NET library references. The model is trained using a production data table called Input Training Data that contains hour-by-hour records including production volume, timestamps, product type, downtime, OEE, and other operational metrics from the filler machine.

Every day at midnight, the algorithm retrains using the full historical dataset and generates a 24-hour production forecast for the upcoming day. These predicted values are stored in a vector called Predicted Production, containing one entry for each hour of the day (00:00 through 23:00).

As the day progresses, the system collects the actual production values each hour and stores them in a separate vector called Real Production. This enables a real-time comparison between what the model predicted and what was actually produced, which can be visualized through a trend chart.

Additionally, the model is consumed once per hour to refine its predictions based on the most recent real production data from the current and previous days. The system also calculates an end-of-day production estimate by summing the real production accumulated so far with the predicted production for the remaining hours of the day.

MCP

Server setting

The MCP server is configured through a JSON file that defines the API key, certificate settings, listening port, and runtime connection parameters. The server listens on port 3000 and connects to the FrameworX runtime at localhost:3101.

{ "appSettings": { "X_API_KEY": "", "CertFileName": "", "CertPass": "", "CertHash": "", "ListenPort": "3000", "Runtime": { "Host": "localhost", "Port": "3101", "Username": "guest", "Password": "" } } }

Run “C:\Program Files (x86)\Tatsoft\FrameworX_1058\fx-10\net8.0\MCP\RuntimeMCPHttp.exe”

Claude setting

The Claude Desktop configuration includes two MCP servers: ProveIt-2026 connects to the remote runtime MCP hosted on the cloud via SSE, and MCP-Designer connects to the local FrameworX designer MCP. Node.js must be installed for the remote connection to work, as it uses npx mcp-remote to bridge the SSE transport.

{ "mcpServers": { "ProveIt-2026": { "command": "C:\\WINDOWS\\System32\\cmd.exe", "args": [ "/C", "C:\\Program Files\\nodejs\\npx.cmd", "-y", "mcp-remote", "http://40.76.104.252:3000/sse", "--allow-http" ] }, "MCP-Designer": { "command": "C:\\Program Files (x86)\\Tatsoft\\00 - v10\\FrameworX_v1058\\fx-10\\MCP\\DesignerMCP.exe" } }, "preferences": { "coworkScheduledTasksEnabled": false, "sidebarMode": "chat", "chromeExtensionEnabled": false } }

Install Node.JS for remote connection.

This setting include connection to local MCP Designer and remote MCP Runtime.

MCP Runtime Chat

This chat connects to a remote FrameworX solution via MCP runtime tools, querying ML.NET production forecasts and downtime events for real-time diagnostics.

MCP-Runtime-ProveIt

MCP Designer querie

“Create a new solution for a bottling line, with the equipment filler, washer and caploader. UNS ISA-95, value simulator protocol for the tags using SINE and BOOL, historian archiving, select two tags for alarms example. Create a dashboard 3 x 2 with gauges on the first row, trend, Alarm and DataGrid on the second row. In your final report, give recommendations for next steps for the solution, including good tag candidates to apply ML. We are live at ProveIT trade show, so as you do, explain briefly to the audience what you are doing.“

Solution created:ProveIT BottlingLine.dbsln on Egnyte

Claude chat used to create the solution:MCP-Designer-ProveIt

MCP Skill

Skill file: Skill-ProveIT.md on Egnyte

Solution created from the Skill:Skill.dbsln on Egnyte

Claude chat used to create the solution: Skill-ProveIt

In this section...