You have some good points/questions that I’m going to address individually
We then have the choice of modeling this system as physical ie what is connected to each facility or logical the aspects of each facility that are directly related to each other.
Yes, you do have the choice. The defining feature of Systems is Data Propagation.. Looking at an example:
The aggregation in this example is a sum. Each parent system is taking a sum of an attribute across all of its children. All of the children just represent the presence of a person ( 0 or 1 ). Before systems, yes you can have all of these as tags but answering the question of: “How many devices of this tag are of value 1?” or relating to the problem (each device is a seat in a row of seats) “How many seats are filled for a row?”. Then, the problem gets harder when you want to say “How many people are in all of the rows combined?”. Systems are the answer to these questions.
Systems are a device type. The grouping of systems is really focused on data relationships. In your instance, deciding if it should be a system or not should be about data relationship. Depending on the use case, it could be logical or physical, but I think it’s best to think about Sytems from a physical relationship.
At the moment devices/systems can only have a single parent so we have to choose one or the other and then try and work with tags to define the other relationship.
So, yes. You will still use both. Since systems are devices and only define data relationships, you still need a mechanism to logically group devices.
You can’t really say “give me all the devices in this system” (as you would using tags) Correction:You can using a Parent ID Query in the Device: Get Node, but you still can’t query systems devices in all the same ways you would tags.
Systems answer different questions (see above).
Following the example from above:
If you notice, there is a system for “Losant Row 2” but there is also a tag
2. The system allows me to capture the data relationship, and the tag allows me to query and group devices logically.
So a feature request would be - could a system (or possibly a device) have multiple parents?
This was discussed internally. Since systems really focus on the data relationships, and systems can be parents of systems, which are parents of devices and so on. It would be really difficult to calculate (and understand) the system attribute value the more complex that tree is.
Following that it would also be nice for system tags/descriptions to be accessible for use in dashboards this would allow the expression of these organizational structures when visualizing. It would be nice to allow some dashboard widgets (especially titles) to be derived from devices
You should check out: https://docs.losant.com/dashboards/context-variables/
Currently, you can use device name, description, and some other things all throughout your dashboard. But, it looks like attribute tags/descriptions don’t flow through. I’ll make a ticket for that.
As always, we appreciate your discussions. Let me know if this helps!