ThingWorx concepts

Figure 1. Connect Edge to ThingWorx

The FairCom Edge ThingWorx connector connects FairCom Edge to the ThingWorx IoT platform, which allows developers to model complex applications and dashboards. FairCom Edge provides full SQL and navigational access to your data persisted on the edge with very little change to your ThingWorx project.

As opposed to other ThingWorx persistence solutions (such as JDBC, ADO, SQL), which connect to databases in the cloud, FairCom Edge persists data on the edge/locally as well as in the cloud.

With FairCom Edge integration, it is easy to update a model in the ThingWorx platform with new data as it arrives in FairCom Edge. No matter how your data is persisted on the edge (such as through FairCom Navigational APIs, SQL APIs, MQTT, or OPC UA), this data is automatically updated in the platform with the desired frequency, from near real-time to a predefined frequency such as once per hour.

The ThingWorx connector is easy and intuitive. You can quickly add FairCom Edge to existing ThingWorx applications to locally persist data in the factory and automatically send it to ThingWorx.

This feature is designed for developers of ThingWorx applications. It requires minimum experience with ThingWorx Foundation and databases. The connector provides an easy way to map edge-persisted data to the properties of a thing.

FairCom Edge maps time series tables into ThingWorx. A time series table is one in which new data values are stored by inserting new records/rows into the table, rather than by editing existing rows in the table.

For example, imagine a device with several sensors. Every minute, those sensors are sampled and their values are stored in a FairCom Edge table as one new row, often with a timestamp. This allows the table to track the sensors' values over time. When a table column is mapped into ThingWorx, ThingWorx receives the data from the last row inserted into the table.

FairCom Edge collects data from MQTT and OPC UA at high speed from local devices. FairCom Edge's ThingWorx connector uploads these newly-inserted records directly into ThingWorx. Integrations with FairCom Edge can also update and delete records from Edge tables, but the ThingWorx connector only sends the latest inserts to ThingWorx.

The ThingWorx connector can map a FairCom Edge table column to multiple things on the ThingWorx platform. This provides more flexibility in how FairCom Edge data is viewed and grouped in ThingWorx.

You can create multiple digital twins that represent, differently, whatever physical objects are producing sensor data. Typically you will have several different types of edge devices, whose data is being concentrated in edge gateways. However, these devices are not necessarily going to be uniquely represented in a single, logical, digital twin, but rather in several twins. The mapping between the digital representation of your physical world can be more complex than simple, single objects.

"thingworxThings": [
  {
    "thingName": "myThing1",
    "thingCreator": "FairComThing"
  },
  {
    "thingName": "myThing2",
    "thingCreator": "FairComThing"
  }
]

For additional details about the config/ctthingworx.json file, see the FairCom Edge setup section.

When the FairCom Edge server loses its connection to the ThingWorx platform, due to network issues, server-side issues, or for any other reason, FairCom Edge automatically attempts to reconnect.