We are relatively new to LeanIX and have just completed an initial phase with a small selection of applications. User Groups have proven to be a real challenge and we are considering if the new Organisation and sub types help us address this.
We have grown via acquisition so have a very diverse IT landscape with multiple sites in the same country using different applications for the same business capability. This is the detail we want to capture. Therefore User Group has been set as physical locations (addresses) which represent sites. We have then put in a 4 tier hierarchy to help aggregate that data into meaningful summaries. The challenges we still face are:
- Who is using the application versus where it is supporting? Where we have finance shared services, they are the user of an application for say accounts receivable but the data belongs to a site. Finance Shared Services being the User Group is a given, but do people also map the site, or just accept that the Accounts Receivable capability is provided by Finance Shared Services and as a result the site is in itself not a User Group for that application?
- If we switch to the new meta model and replace User Groups with Organisation, what sub types would people recommend, given our desire to map site locations. A simple Business Unit hierarchy or a combination of Region and Business Unit with relationships?
- Physical site locations are logical Organisations/User Groups for manufacturing and production plants, but are less logical when looking at corporate functions, where the functional user type is more meaningful. How have others handled this?
- As an option to address the challenge above for Head Offices, but also to get a richer view, we would also like to map Functions as a User Group or Organisation Type e.g. Finance, Procurement, IT, HR, Customer Services etc but without a hugely complex organisation model. Would people recommend using the new “Team” subtype. And have people used 2 different User Groups/Organisation independent of each other. So assigning say Finance and Site A, rather than it being hierarchical with Finance as a child of each and every site
Any other input on how others have addressed similar problems around where and who etc, would be much appreciated. We are looking at applications and capabilities at the moment not the underling IT components….that is another challenge for another day