UDT Inheritance Across Providers
K
Kevin Garman
I would like to create a master UDT over all providers. The UDT may be instantiated in any provider and all instances are updated when the master changes.
Log In
l
lionel MAZEYRAT
A smart way to address this need could be a kind of UDT reference to another UDT inside another provider. The tag reference is ever available. The UDT reference across providers (of the local gateway) would be really usefull
L
Lee Meyer
Yes this managed on an EAM to cover all tag servers would be fantastic and the natural extension of v8 project inheritance
S
Shane Robin
Lee Meyer: We are doing this currently by having a global UDT at each location. The tag provider UDT inherits from the local instance of the global UDT. We have a master global UDT where we make changes and then an EAM task moves the changes from the master UDT to the different locations since they don't have direct network connectivity to the master. The only connection from the local sites to the Enterprise are through the gateway network. It is not the best, but this keeps all instances of the global UDT the same.
P
Philip Follansbee
I would also like to see this as it promotes standardization of incoming data and tag provision to templates. It keys nicely with inheritance in vision clients. This could be implemented via a tag provider inheritance type setup wherein a master tag provider could provide data types as well as global tag data (like gateway data) to all tag providers.
L
Luc Martin
That feature will be very appreciated, we want to centralized all UDTs, it will be very helpful when UDT is updated