Skip to main content
E
EF_127870644-Participant
4-Participant
March 28, 2025
Solved

kepserver connectivity

  • March 28, 2025
  • 1 reply
  • 595 views

Hello all

I am working on a project that involves integration of thingworx for real time performance monitoring. This involves investing in new machines with PLCs that ease connectivity with kepware. However, another case involves legacy machines with no PLCs. Data is collected and logged in manually into SQL-based excel platform.

We aim to eliminate the use of excel for visualisation and use just thingworx as a single analytics monitoring platform. How can we move data from legacy  SQL server to kepware by using data lake functionalities or power BI? Please if an architecture is possible, it will be more helpful.

Best answer by pshashipreetham

Could you clarify a few things to help shape the most suitable architecture?

  1. What type of SQL Server is used (e.g., Microsoft SQL Server, MySQL, PostgreSQL)?

  2. Is the SQL server accessible over the network from your ThingWorx environment?

  3. Are you open to using intermediate services like MQTT brokers, Azure/AWS/GCP Data Lakes, or ETL tools like Apache NiFi or Azure Data Factory?

  4. Do you need real-time sync between SQL and ThingWorx, or is scheduled batch sync acceptable?

  5. Are you already using Power BI as part of your reporting stack, or just exploring its use for this pipeline?

Thanks,

1 reply

P
18-Opal
pshashipreetham18-OpalAnswer
18-Opal
March 31, 2025

Could you clarify a few things to help shape the most suitable architecture?

  1. What type of SQL Server is used (e.g., Microsoft SQL Server, MySQL, PostgreSQL)?

  2. Is the SQL server accessible over the network from your ThingWorx environment?

  3. Are you open to using intermediate services like MQTT brokers, Azure/AWS/GCP Data Lakes, or ETL tools like Apache NiFi or Azure Data Factory?

  4. Do you need real-time sync between SQL and ThingWorx, or is scheduled batch sync acceptable?

  5. Are you already using Power BI as part of your reporting stack, or just exploring its use for this pipeline?

Thanks,

Terms & ConditionsCookie settingsAccessibility statement