Can one reusable WTNote have a different local name when associated to different parts?

We are using Windchill to manage aircraft repair parts and have a set of standard General Notes, currently numbered GN01–GN30.

Each GNxx is a reusable standard note. For example, GN05 is one standard WTNote containing the approved text.

The problem is that the same standard note may need to appear under a different G-number depending on its position within an individual repair.

For example:

• Repair A requires GN01–GN10 → displayed as G01–G10
• Repair B may not require GN03, so GN04 might need to appear as G03
• Another repair may use GN05 as G04

We can currently use Add Note to add an existing GN05 to a Part, which is what we want from a reuse perspective. However, the Name belongs to the WTNote itself. Therefore, changing GN05 to G04 would change the name of the actual shared note rather than just its designation within that particular Part.

What we would ideally like is:

            Master WTNote

                 GN05

              /       \

             /         \

       Repair A       Repair B

         G04            G05

In other words, GN05 would remain one single reusable WTNote, but its local designation/alias could be G04 when associated with Repair A and G05 when associated with Repair B.

We do not want to create a new WTNote every time it is used, because each repair currently creates approximately 20 new note objects. Over a large number of repairs this creates thousands of duplicate note objects containing identical text.

Our desired long-term structure would be approximately:

30 master WTNotes (GN01–GN30)
→ associated/reused across potentially hundreds of repair Parts
→ with a Part-specific G-number/designation for each association.

Is this possible in standard Windchill?

Specifically, is there a way to store a local designation/alias against the Note-to-Part relationship, rather than changing the Name of the WTNote itself?

Alternatively, can the BOM/structure display a relationship attribute instead of the WTNote’s Name, allowing something such as:

We are trying to achieve reuse of the same controlled Note object without creating duplicate Note objects, while still maintaining the required G01, G02, G03… numbering within each individual repair.

Any guidance on whether this is achievable through configuration, relationship attributes, aliases, or another standard Windchill mechanism would be greatly appreciated.