Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi,
I have a dashboard on Issues that shows different graphs on the Issues raised within the organization. Each Issues has a Primary Owner and impacted DMST attribute value. The primary owner identifies which department 'owns' the issue and is responsible for its closure while the DSMT attribute is used to identify other departments that this particular Issue might have an impact on from a risk standpoint.
This Issues table is linked with 3 hierarchy tables that identifies where in the organization the ownership of the Issues lies. One is segment table (link to department), second is geography table that identifies the region where the issue originated and the last is GOC (think of it as cost center). The whole dash is driven by bookmarks for different execs that get views for their respective organizations.
We recently added a PY (previous year) view. This shows metric values for previews year for selected executive. The problem is issue primary owners keep moving across organization. So, when a issue is registered (let's say in Oct 2017), the owner was in department A. In March 2018, the owner is in department B. So, PY metric would show the issue in department A (under executive of department A bookmark) and CY (current year) metric would show it under B (under executive of department B) as primary owner is now in department B. Ideally, the ownership should lie with department and not individual. So, department B should not get a report on this issue as they were not responsible for it. Basically, ownership should remain with A.
To get over the above issue, the PY metrics use hierarchy tables (segment, geography and GOC) frozen as of 12/31 of the previous year while CY uses current hierarchy files. How can bookmark for department A exec show the issue in both CY and PY metric despite both metrics using different hierarchy tables.
Sorry for the long question and possibly confusing question/title. Thanks for your time!
