Alternate hierarchy to manage work through different lens

We look at the same Initiatives through two lenses: (1) the product lens, which Aha! solves really well; and (2) the program lens, which Aha! does not solve for. 

The idea is to have an Alternate Hierarchy in Aha!, such that the same initiative can contribute to multiple parents. We currently manage these through Tags, but we do not get the same hierarchy the products get (i.e., rollup to product line level initiatives, attribution to goals, Overview, etc.).

This concept exists in other systems, such as Oracle. Please see example below.

https://docs.oracle.com/cloud/latest/financial-consol-cloud/AGFCC/alternate_hierarchies.htm#AGFCC-GUID-D6E209E9-68FD-4B59-BC2E-298C6DE0579A

A single entity can have multiple parents and contribute differently to each parent. The following example shows a leaf-level entity that has more than one parent.

In this example:

• Entity E111 is a child of both P11 and P12.

• Input data that is entered for E111 at either P11 or P12 is replicated to the other entity after Save. You can enter the data at any of P11.E111 and P12.E111 members.