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.

AVEVA is looking to understand how customers are using the Equipment model within your project specific use case.  For awareness, Equipment definitions create logical groupings that allow you to organize your project using a hierarchical design. Each definition brings together the base SCADA properties into a single entity that can be easily replicated within your project. 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 only, and how you are leveraging this feature to it's fullest capability. Please Private Message or email me if interested. Thanks!

Parents
  • I have used the equipment model on several projects (<5k tags) and have found it a great time saver.  The first instance was before the equipment editor and had to be developed directly in XML which i found slow and clumsy, but when you have 250 motors or essentally 3 types (DOL, VSD, SoftStart), once the equipment template is setup and is aligned with a DFB/AOI and a supergenie, it becomes very fast to create the tag, alatms, trends & graphics.  It is also great when the customer decides to change a motor from DOL to VSD, just change the equipment type, update equipment  and swap the genie.

    The only real issue I've had was when using address based tags (ie modbus/TCP not OFS/Rockwell) where some manipulation of the Custom Properties is needed to push PLC addresses into the various equipment items.

    Being able to filter the alarm SOE by the equipment tree hierarchy is also a great advantage over a "Flat" system model.

Reply
  • I have used the equipment model on several projects (<5k tags) and have found it a great time saver.  The first instance was before the equipment editor and had to be developed directly in XML which i found slow and clumsy, but when you have 250 motors or essentally 3 types (DOL, VSD, SoftStart), once the equipment template is setup and is aligned with a DFB/AOI and a supergenie, it becomes very fast to create the tag, alatms, trends & graphics.  It is also great when the customer decides to change a motor from DOL to VSD, just change the equipment type, update equipment  and swap the genie.

    The only real issue I've had was when using address based tags (ie modbus/TCP not OFS/Rockwell) where some manipulation of the Custom Properties is needed to push PLC addresses into the various equipment items.

    Being able to filter the alarm SOE by the equipment tree hierarchy is also a great advantage over a "Flat" system model.

Children
No Data