Ingesting Data into the Platform
ThingWorx as a platform can be used in variety of ways as the destination (data sink) for your data leveraging its extensibility. It is possible to use both push and/or pull mechanisms to ingest the data into ThingWorx. Only the IoT environments using the officially available software components and capabilities are considered here. In this scenario, the data will be pushed into ThingWorx. The three primary use cases are as follows:
• Device data from the Edge connected to Remote Things in ThingWorx. The data from the devices is represented as properties in the Things.
• Industrial data from factory floors connected through ThingWorx Kepware Server to Industrial Connections entity in ThingWorx. The data (tags) from industrial devices represented as properties in the Things.
• REST API exposed by ThingWorx
In any of the above use cases, the data is bound to Thing properties and stored in the ThingWorx data store depending on the property configuration as mentioned above (persisted, logged, etc.). Irrespective of the origin of the data, the visualization of the data via mashups would be identical due to the Thing model abstraction.