Combine Tag & FlexTag into a single tagging solution

We have two tagging features: legacy, and Flex Tag

What are the differences? Do we need to keep both?

I've heard from a few people that they are recommending to customers to not use FlexTag, and to go back to legacy tagging due to the various descrepancies and missing functionality in FlexTag.

Differences and descrepancies:

• Override control-inhibit tag creates event

  • Legacy: no

    • IMS# 2050041 - [TCEnergy] [2022 SP1] - No event message generated for warning tag override when using legacy tags. Closed in PI-41.2 for Enterprise SCADA 2022 SP1 Patch 2

  • Flex: no

• Prompt to override contains tag name/description

  • Legacy: yes

  • Flex: no

  • http://tcjira.aveva.com/browse/OGPM-3178

• Tag Expiry

  • Legacy: yes

  • Flex: no

  • http://tcjira.aveva.com/browse/OGPM-3017

  • https://aveva.aha.io/features/OASYS-481

  • But make the event be against the point, not the tag
    http://tcjira.aveva.com/browse/OGPM-2980

Known Issues:

• Limit to ~50 tags that can be bulk updates

  • https://aveva.aha.io/features/OASYS-357

  • https://dev.azure.com/AVEVA-VSTS/Issue%20Management%20System/_workitems/edit/1198664

Other requested enhancements:

• Add additional enumerations (tag types?) that are triggered on control FNPUTs
  http://tcjira.aveva.com/browse/SERPM-564

• Support more tables

  • All telemetered tables http://tcjira.aveva.com/browse/OGPM-82

  • Remote, connection http://tcjira.aveva.com/browse/SERPM-420

  • LMS tables http://tcjira.aveva.com/browse/OGPM-137

From R&D:
I recommend the project uses Flexible Tagging instead of the default Tagging.
Flexible tagging allows for greater customization of tags. It supplements, not replaces, regular tagging and can only be used with Analog, Status and Multistate tables (and in some versions, the Rate table in a limited capacity).
Flexible tagging is a feature that allows for greater customization of tags. With flexible tagging (FlexTag), you can configure the exclusivity of tags, group tags together for mass modifications, set priorities for FlexTag types, customize tag icons, and more. With flexible tagging, you can also attach multiple tags to a single record.
Flexible tagging is not enabled by default. Although the FlexTag Summary can still be accessed from the ezXOS navigation menu, the system will not acknowledge any FlexTag configuration changes unless the registry variable is turned on.
Flexible tagging also offers the ability to define a wider range of tag types:
- Inhibitive (cannot override)
- Warning (can override)
- Maintenance
- Informational

There seems to be a big disconnect here. The above text was found in Jira, but appears to have been lifted directly from the HMI controller guide. Which explains why they think these two things are complimentary, but in the backend they appear to be separate things.

To figure out:

• Are we capturing sufficient audit trail information?

• Any usability or scalability enhancements?

• should we even have the option to turn this on/off? Why do we continue to ship two different tag control panels?

• 
  

To be rationalised (from OneNote Tags vs. FlexTags (Web view))

• SDI-16748 - Tag description must be presented when a tag prevents a multistate command from executing

  • TCE D/M

  • Addressed in Realtime Add-on 7.7.1.42 released 2016/02/09

  • But did @Todd Cherry bring this up again recently?

• IMS# 1573658 - [PMC] [DOC] Tag Expiry documentation does not match observed functionality

  • Was considered a doc defect, to explain that tag expiry doesn't work if flextags are enabled. Which seems to indicate that FlexTags dont have auto-expiry capability

  • 
    

• OGPM-1135 What is the difference between Tag Expiry and Flexible Tagging?

  • seems to indicate that there was an attempt to reconcile these two things, and that there was a fix put into OGX to address warning messages for multistate

• OGPM-3017 FlexTag is missing Tag Expiry functionality

  • It sure is....

• OGPM-367 7.6 inconsistency with RVE, Interlock, On/Off Peak, Tagging restrictions etc.

  • has no detail other than there is a strangeness with interlock, RVE and tagging

  • no resolution

• OGPM-175 Tag reason information not saved historically

  • During P66 meeting one of their admins (Robbie) mentioned that when they tag a point they'd like to be able to see after the fact in the events on the tag additional/removal information about why the point was tagged.

  • Currently this information is lost, since the tag reason and work order etc. are only in Realtime and when the tag goes away the information is lost.

  • No resolution

• OGPM-82 add Tagging functionality to all telemetered tables

  • Clearly, the need is for a single tagging feature that applies to all tables, with all the added functionality of flex tag

• OGPM-2980 TCPL DM - Have tag expiry event against point table not tag table

  • When we fix tag expiration for flex tags, we need to decide where we raise the alarm against

• Override control-inhibit tag creates event

• • Legacy: no

  • Flex: no

• Prompt to override contains tag name/description

  • Legacy: yes

  • Flex: no

  • http://tcjira.aveva.com/browse/OGPM-3178

• Tag Expiry

  • Legacy: yes

  • Flex: no

  • http://tcjira.aveva.com/browse/OGPM-3017

  • https://aveva.aha.io/features/OASYS-481

  • But make the event be against the point, not the tag
    http://tcjira.aveva.com/browse/OGPM-2980

• Known Issues:

• • Limit to ~50 tags that can be bulk updates

    • https://aveva.aha.io/features/OASYS-357

    • https://dev.azure.com/AVEVA-VSTS/Issue%20Management%20System/_workitems/edit/1198664

• Other requested enhancements:

• • Add additional enumerations (tag types?) that are triggered on control FNPUTs
    http://tcjira.aveva.com/browse/SERPM-564

  • Support more tables

    • All telemetered tables http://tcjira.aveva.com/browse/OGPM-82

    • Remote, connection http://tcjira.aveva.com/browse/SERPM-420

    • LMS tables http://tcjira.aveva.com/browse/OGPM-137