AVEVA is looking to understand how customers are using the Equipment model. If you would be open to sharing your Plant SCADA application, and are using Equipment, we would welcome the opportunity to analyze your shared project internally.

Hi Nathan, thank you for reaching out.  All of our work as of past few years has been upgrades, additions, or niche manufacturing (little to no repetitive equipment) that does not warrant using or cannot use equipment.  We've used equipment on a few virgin projects, but most of my guys (7 now) don't do it enough to remember how to use it.  I find it confusing to setup, but once setup, it is powerful.  

Greg

Nathan - I have used equipment successfully on quite a few projects.  It becomes especially useful when you want two structured tag references to an item.  Mostly on I/O. A limit switch or solenoid is generally referenced by it's tag name, but a set of supergenies can give access to an entire I/O card with proper controls and tags through the equipment, and the pages are transportable between projects. 

Unfortunately, I have not had it give much advantage over giving the same PLC reference to two tags, except for the fact that you can see them together.  Much easier to edit.  The features of the equipment are documented on how to enter them into the program, but I have net been able to dig into the structure deeply enough to see what they do.  Digging into the Help is pretty much useless, and tight time tables on jobs doesn't allow much time for experimenting and "reverse engineering".

It does seem to have potential for solidly structuring similar devices.  The example project seems to use it to a limited degree.  A few diagrams showing the relationships and references of the fields would be great.  I have always wished that the relationship between tags and alarms was relational, and the equipment seems to provide a path to that if I can find it.

Nathan - I have used equipment successfully on quite a few projects.  It becomes especially useful when you want two structured tag references to an item.  Mostly on I/O. A limit switch or solenoid is generally referenced by it's tag name, but a set of supergenies can give access to an entire I/O card with proper controls and tags through the equipment, and the pages are transportable between projects. 

Unfortunately, I have not had it give much advantage over giving the same PLC reference to two tags, except for the fact that you can see them together.  Much easier to edit.  The features of the equipment are documented on how to enter them into the program, but I have net been able to dig into the structure deeply enough to see what they do.  Digging into the Help is pretty much useless, and tight time tables on jobs doesn't allow much time for experimenting and "reverse engineering".

It does seem to have potential for solidly structuring similar devices.  The example project seems to use it to a limited degree.  A few diagrams showing the relationships and references of the fields would be great.  I have always wished that the relationship between tags and alarms was relational, and the equipment seems to provide a path to that if I can find it.