No
Yes
View More
View Less
Working...
Close
OK
Cancel
Confirm
System Message
Delete
Schedule
An unknown error has occurred and your request could not be completed. Please contact support.
Scheduled
Wait Listed
Personal Calendar
Speaking
Conference Event
Meeting
Interest
Times for this session to be announced soon
Conflict Found
This session is already scheduled at another time. Would you like to...
Loading...
Please enter a maximum of {0} characters.
{0} remaining of {1} character maximum.
Please enter a maximum of {0} words.
{0} remaining of {1} word maximum.
must be 50 characters or less.
must be 40 characters or less.
Session Summary
We were unable to load the map image.
This has not yet been assigned to a map.
Search Catalog
Reply
Replies ()
Search
New Post
Microblog
Microblog Thread
Post Reply
Post
Your session timed out.
This web page is not optimized for viewing on a mobile device. Visit this site in a desktop browser to access the full set of features.
LiveWorx 2017

Mashing-up Multiple Data Streams - Lessons Learned Using ThingWorx and Kepware

Session Description

We will review the lessons learned and best practices discovered when developing a mashup that streams live data from several PLC controllers via a Kepware KepServerEX. The mashup uses a repeater to display data for several PLC controllers that are all instances of a Thing Template so that a single mashup can be used, with the mashup displaying unique information from each controller. We'll show how the company mapped controller tags to ThingWorx properties, how they bound those properties to individual controller thing properties, and how they use a scheduler to calculate formulas on the data input to display information like rates, times, hit ratio, etc


Session Presenter
Additional Information
Industrial Internet of Things
Manufacturing
How keeping services logic separated from the server and the client improves performance.
Why the refactor code should be checked early and often, and why to use an IDE and GIT to edit/track code (since you can't do it in the composer).
Why use a Thing Shape instead of a data shape to reduce the dependency of service info table results.
Case Study
45 minutes
Session Schedule