Performance
The ThingWorx Native Interface gives users the most efficient, flexible, and integrated smart manufacturing interface available, including:
- Codeless Mapping to a Wide Range of Devices: Users can configure connectivity to an industrial device, seamlessly map KEPServerEX tags to the ThingModel, maintain and view mapping directly from the ThingWorx platform, and more.
- Accessible Data for Real-Time Analysis: Users can model, analyze, and visualize their KEPServerEX real-time industrial data, and quickly and easily find and utilize the specific data they need from any device supported by KEPServerEX.
- Remote Project Loading with ThingWorx: Users can easily deploy KEPServerEX projects remotely—while editing network settings and configuring and managing all of their KEPServerEX instances from a single ThingWorx platform interface.
- Store and Forward:
- Users can seamlessly transfer data between KEPServerEX and ThingWorx—even in the event of a communication loss or unstable connection.
- Users can easily monitor and determine operational health.
- Multiple modes enable users to determine when stored data is forwarded.
- Enhanced Augmented Reality and Machine Learning Integration: Users can quickly and easily find and utilize industrial data in augmented reality (AR) experiences, machine learning models, mashups, and other ThingWorx tools. Users get access to all of their real-time KEPServerEX data within ThingWorx Composer, including the ability to quickly associate that data with new or existing things in the ThingModel, and the ability to view mapping and critical diagnostic information from the ThingWorx platform.
- Enhanced Data Contextualization: With KEPServerEX data and the ThingModel, users can access ThingWorx’s advanced analytics and simulation tools, orchestrate workflows, create mashups, and engage in AR experiences.
Release Notes
6.5.829.0
6/19/2018
- Fixed an issue where a configuration transfer (push or pull) between the server and the ThingWorx platform failed due to the reliance on a blank password for the server's Administrator user account.
- Added a new user group in the User Manager called “ThingWorx Interface User” that is dedicated to the ThingWorx platform connection and allows for configuring the platform's permissions to access the server's object properties.
- Added a new user in User Manager called “ThingWorx Interface” that is dedicated to the ThingWorx platform connection.
- Enhanced the error reporting associated with configuration transfers to provide more information to help with troubleshooting.
- Added a new Store and Forward mode called “On Hold” to forward only the latest property updates to the ThingWorx platform after recovering from a disconnect. This new mode allows ThingWorx applications that are actively monitoring production to get the freshest data available on reconnect.
- Forwarding stored property updates that were collected while in "On Hold" mode can be triggered by changing the mode from “On Hold” to “Active”.
- Added “_ForwardMode” system tag to control changing the Forward Mode (On Hold, Active). This allows configuring (and scheduling via user defined script) the mode from the ThingWorx platform.
- Updates for Diagnostic Properties are no longer stored when the server is disconnected from the ThingWorx platform. This change is to ensure that the latest diagnostics updates can always be provided to the platform upon reconnect while Store and Forward is enabled. If these properties need to be stored, then it is recommended that the platform reference the server's matching system tags to the Diagnostic Properties (Note: Diagnostic Properties are available on the ThingWorx platform via the Industrial Gateway Thing).
- Added support for the following Store and Forward system tags:
- _StoreAndForwardEnabled
- _StoreAndForwardEnabledStatus
- _DatastoreCurrentSizeMB
- _DatastoreRemainingSpaceMB
- _DatastoreUseableDiskSpaceMB
- _DatastoreAttachError
- _DroppedUpdates
- _ForwardMode
- _ForwardModeStatus
Manufacturing Use Case
A global automotive parts manufacturer needed to reduce machine downtime, improve product quality, and create dynamic visualizations of production systems so they could proactively prevent issues.
Using the KEPServerEX ThingWorx Native Interface to connect KEPServerEX data with ThingWorx, the manufacturer enabled company-wide device-to-Cloud connectivity through one single-pane-of-glass IoT solution.
In this example, KEPServerEX collects data from CNC machines and streams it in real-time to ThingWorx, which in turn provides clearly visualized data and gives users the ability to rapidly analyze their plant floor performance—from individual components to holistic overviews. Using data from KEPServerEX, ThingWorx analyzes uptime data to find trends and prevent downtime. With greater insight into asset and resource allocation, the manufacturer makes more informed decisions about productivity and efficiency across the entire enterprise.
Read the full use case: HIROTEC AMERICA case study