Point Counts for Insight when using MES?

Dear AVEVA,

We are working with a Partner SI developing an AVEVA insight Solution. They are feeding some tags that is used for MES.

We discovered each asset consumes 10+ Tags for OEE, Utilization, MTBF, etc...

How do we estimate how many tags that is needed for each asset when we are using MES?

We need to estimate how many Credits to estimate for FLEX Credits.

I will need to use the "Rate Plan- Insight Pricing Estimator- 24_02.xlsx" to estimate the number of tags needed for the final solution.

Any assistance to help estimate the tags needed would be appreciated.

Thanks.

Kien

Parents
  • When an equipment is imported into Insight Performance, it will create a set of 11 tags for that equipment.  The list can be found at https://docs.aveva.com/bundle/insight/page/605175.html.

    In most cases, customers will also want to use tags to set the current utilization state of the equipment, to record production counts (good and scrap), to start / stop a production run, and to set values for additional context properties.  The list of configuration options can be found at https://docs.aveva.com/bundle/insight/page/594400.html.

    Assuming a customer has a tag for utilization state, two tags for reporting production (one for good counts and one for scrap), two tags to meet the minimum requirement for starting / stopping production runs, and no additional context tags; then there will be an additional 5 tags per equipment.  However, if the customer has many OEE context properties defined and set through tags, this number can increase quickly.

    If you have further questions, you may contact me through email at jeff.barkehanai@aveva.com

    Regards,

    Jeff Barkehanai

Reply
  • When an equipment is imported into Insight Performance, it will create a set of 11 tags for that equipment.  The list can be found at https://docs.aveva.com/bundle/insight/page/605175.html.

    In most cases, customers will also want to use tags to set the current utilization state of the equipment, to record production counts (good and scrap), to start / stop a production run, and to set values for additional context properties.  The list of configuration options can be found at https://docs.aveva.com/bundle/insight/page/594400.html.

    Assuming a customer has a tag for utilization state, two tags for reporting production (one for good counts and one for scrap), two tags to meet the minimum requirement for starting / stopping production runs, and no additional context tags; then there will be an additional 5 tags per equipment.  However, if the customer has many OEE context properties defined and set through tags, this number can increase quickly.

    If you have further questions, you may contact me through email at jeff.barkehanai@aveva.com

    Regards,

    Jeff Barkehanai

Children