Page History

...

There are four primary components used in a system using Sparkplug SiteWise IoT Bridge. These are:

• Edge Gateways publishing Sparkplug based MQTT data
  • Our examples will use Ignition+MQTT Transmission for the Edge Gateway.
• An MQTT Server
  • This could be AWS IoT Core or any other v3.1.1 compliant MQTT Server
• Sparkplug SiteWise IoT Bridge (SSBIB)
• AWS IoT SiteWise

Image RemovedImage Added

There are some translations that need to take place between the components and these platforms have different capabilities that result in some limitations in how an Edge Gateway can be configured. For example, UDTs in Ignition support more data types that AWS IoT SiteWise does. As a result, use of data types in Ignition must be limited to those supported by AWS IoT SiteWise in order for data to properly show up and be updated in AWS SiteWise.

...

Ignition and AWS IoT SiteWise use different terminology for similar contructsconstructs. Those definitions are below.

• An Ignition 'UDT Definition' is mapped to a SiteWise 'Asset Model'.
• An Ignition 'UDT Instance' is mapped to a SiteWise 'Asset'.
• Ignition 'UDT parameters' are mapped to 'SiteWise Attributes'.
• Ignition 'UDT member tags' are mapped to 'SiteWise Measurements'.
• Transform, Metric, and Hierarchy definitions in AWS SiteWise are not used by SSBIB.

Constraints and Limitations

...

These are not supported currently in Sparkplug SiteWise IoT Bridge. AWS SiteWise allows Asset Models to have one or more child Asset Models. Ignition supports UDTs having children UDTs as well as UDTs referencing a parent UDT. However, these hierarchical relationships will not be maintained by SSBIB. Support for simple hierarchies as supported by AWS IoT SiteWise will be added in a future version of Sparkplug SiteWise IoT Bridge.

AWS IoT SiteWise Limits and Quotas

...