This solution demonstrates how to integrate multiple technologies, to create a Smart Monitoring Solution for Real-Time Production Sites.
On this page:
| Table of Contents | ||||
|---|---|---|---|---|
|
Summary
This solution demonstrates how to integrate multiple technologies, to create a Smart Monitoring Solution for Real-Time Production Sites.
To see the overview information on the ProveIt! Demo Features and Goals to the page: https://tatsoft.com/proveit
To run a HTML5 client view of the solution, open https://frameworx.eastus.cloudapp.azure.com:3118/html5/
Or Download the Solution File (requires v10 Update 1b): ProveIt.dbsln
System Architecture
The project includes an instance of FrameworkX that publishes data to both an embedded MQTT broker—used as a testing environment—and the ProveIt MQTT broker. The application reads data from both MQTT brokers, retrieves published OPC UA data, and accesses the MySQL database for additional data integration.
Highlights
assets efficiently. Its hierarchical structure ensures that information is organized and accessible, providing a clear framework for asset management.
The key method responsible for determining which page to open is VerifyNavigation(), located in the code-behind of the MenuTree page. This method evaluates the current application context and decides which screen to display based on the asset name (AssetName) and the hierarchical structure of nodes.
The VerifyNavigation() method directly relies on this asset tree to determine node depth and relationships accurately. By leveraging this structure, the system can ensure seamless navigation, directing users to the appropriate screens based on asset categories such as sites, production areas, or specific system components.
Pages
The header is a navigation component that enables allows users to seamlessly switch between different application pages. The application primarily offers two ways to navigate: the header provides access to the main pages, while the asset tree determines which data is displayed on the page. Navigation can also be performed using the asset tree. Additionally, the header includes options to select the layout type, log in, and change the theme.
Layouts
The application supports adaptive layouts to ensure proper screen scaling based on the selected device type:
Desktop Layout
Pad Layout
Mobile Layout
Sites
A demonstration of geolocation-based functionalities within the application.
More information about this component can be found here.
Area
This section page showcases the use of dashboards and symbols, offering dynamic visual representations of system data.
Line and OEE
This component dynamically maps data from the MQTT broker. Users can select relevant data through the Asset Tree, making real-time monitoring more accessible.
An example of a dynamic field configuration in the OEE page is shown below. The value inside the curly brackets represents a dynamic expression where:
Client.Context.LineId: Retrieves the selected asset from the Asset Tree.
"Line/OEE/Total Count": Specifies the data path within the system.
"pcs": A static unit label.
Example: {Asset(Client.Context.LineId + "Line/OEE/Total Count")} pcs
This approach ensures real-time updates based on the selected asset, providing accurate production data at all times.
Grid View
The Grid View page demonstrates how raw data from MQTT is displayed, using @Client.Context.AssetName as the data source for the grid.
In this section:
| Page Tree | ||
|---|---|---|
|