Skip to main content

For customers of large groups where you have multiple configurations across different BUs I am wondering if you have any best practices to share around creating new attributes vs sharing attributes between BUs.

We have a few BUs that we know we want to do reporting on across the BUs so we are requiring some standard shared data elements.  But there are other BUs that are very much stand alone. We are wondering with new configurations being created, do we just have all the new attributes be specific to that BU’s implementation?

Interested in any other customer is struggling with this issue.

We’ve helped many of our customers with establishing architectural principles and change control and governance processes to ensure that different business units can all use a single Portfolios instance and reconcile an element of BU specific autonomy alongside the value of being able to consolidate data, report and collaborate across business units. Fundamental is an approach like this to designing the solution:

 

Reply


Terms of UseCookie settings
All Data Subject Access Requests (DSARs), and requests of “Do Not Sell My Personal Information” according to the CCPA, must be submitted through the Planview DSAR portal located here

Planview has appointed a Data Privacy Officer (DPO) to be responsible for overseeing our Privacy Management Program and related privacy compliance measures. DPO can be contacted at privacy@planview.com