Best Practices: Enable and Configure Agile PLM Dashboard
By abhijit.kakhandiki on Jan 07, 2009
I just thought I would write this small blog post for the benefit of the broader Agile audience. This came up recently as a query from a customer. How does one enable the Agile PLM Dashboard? What are the recommended best practices for configuring the PLM Dashboard?
In 9.2.2, the dashboard really expanded from just being PPM Dashboard to being a PLM Dashboard. You can now configure any advanced search and PX within a dashboard widget. This provides customers with tremendous flexibility in displaying search results in tabular or graphical format as well as displaying PLM relevant data from other systems via Process Extensions.
It is really simple to enable the PLM Dashboard. If you are on version 9.2.2 or later, your license should include the PLM Dashboard functionality, however you need to 'enable' it for the users. Starting with 9.2.2, there is a special privilege type 'Dashboard Tab View', that controls visibility of Dashboard tabs. You can create one or more privileges of this type to view a set of dashboard tabs. These privileges can in turn be part of one or more roles depending on the need.To enable the dashboard, do the following:
• Under User Settings -> Privileges -> Dashboard Tab View in Java Client, open up ‘Read Dashboard Tabs’ privilege
• In the ‘Applied To’ section, add the appropriate tabs that you want to view to the ‘Selected’ section
• In the ‘Where Used’ section, add the appropriate roles that you want this privilege to be part of
• Login as a user with this role to view the set of dashboard tabs you just created access to
There are some best practices to keep in mind here:
• Dashboard privileges should be created for a related set of tabs. When setting up the privileges, think about which group of users would benefit from viewing this data and how data in different tabs relates to one another e.g. Project Management v/s Sourcing v/s Quality Management. You may also have separate tabs for the benefit of executives that summarize data across some of these functions.
• It is generally easier to create separate dashboard related roles and configure privileges and roles in a one-to-one correspondence. e.g. you could create a new role 'Quality Dashboard' role and apply the Quality Management dashboard privilege that allows access to a set of quality related dashboard tabs such as compliant failure modes by product and field problems with missing info. This way it is very clear which roles provide the access to which set of tabs. Managing user access simply becomes a function of providing or revoking a user's role.
• It works even better if these roles are assigned at a user group level (unless you want to differentiate access within a group). This way, when a user leaves a particular team, you can remove the user from the appropriate group and take away that specific user's access to the set of tabs related to their former function. In the above example, if the 'Quality Analyst' user group had the 'Quality Dashboard' role, you could provide or revoke access to quality related dashboard tabs by simply moving users in or out of this group.
In a future blog, I will focus on dashboard layout, and some cool things you can do with process extensions.
As usual your comments are welcome.