Thingworx Remote Thing tags segregation

Question

Thingworx version: 9.3 +Hello developers, i need help with a trouble:I have 12 equipments (PLC), for all of those have the same tags, and my doubt is, if is a good practice to segregate the tags between 12 things that are similar, but using tags that are bound to their respective PLCs. E.g.: Thing1 with tags T1_Temperature, T1_ContentWeight; Tthing2 with tags T2_Temperature, T2_ContentWeight and so on.Some considerations: all of those are on PTC Kepware Server using only one Industrial Connection.Questions to answer: 1: Is this a good practice? I haven't found anything about it in Docs and CS.2: Do this offers more performance than having only one Thing for all those PLC tags?3: Do we have some performance difference or network charge on some of these approaches?

Rocko · Accepted Answer

If they all have the same tags, is it safe to assume the 12 devices are of the same model?

In that case my advice would be to create one thingshape with those shared attributes (temperature, weight,...) and then create 12 things (T1,...,T12) implementing that Shape. Then bind your tags to each thing.

Performance is equal but this is much more manageable and you save the renaming.

wcui · Answer

@slucasTN

While there is no set limitation relating to the number of properties per thing, please consider the following:

The higher the number of properties that are defined for a single thing, the more difficult it may become to maintain
There is no set property threshold number that can be provided as this will be affected by several factors, such as the following:
- Server sizing
- Frequency of writes/updates
- Other use case specifics
As such, it is strongly recommended that scale testing be performed well in advance of any planned development milestones to determine if the number of properties per thing is an issue
Some key symptoms to look for while testing include the following:
- Missing property updates
- Longer/unacceptable load times when opening the thing in question via the composer
If it is determined that the number of properties per thing is too high after testing, consider splitting the properties up across multiple things in a logical way
- For example, consider breaking down a single thing with many properties into its sub-components, sub-systems, etc. that make up the thing, each with their relevant properties

Sign up

Please use your PTC eSupport account.

Welcome to the PTC Community

Please use your PTC eSupport account.

Scanning file for viruses.

This file cannot be downloaded