Overview of Oracle DRM Analytics

Oracle DRM Analytics is a product that consists of a set of dashboards and reports for the Oracle Data Relationship Management application. It was initially made available in March 2016 with PSU 11.1.2.4.330 and it has been enhanced in future PSUs.

Analytics

Oracle DRM Analytics Dashboards for DRM Master Data Change Tracking, Growth Analysis, DRG Request Monitoring, DRG Workflow Model Performance, DRM/DRG Participant and User Group Performance.

Analytics User Guide

Different from the Data Relationship Governance module, DRM Analytics can not be accessed directly from the DRM application. Users have to setup an Analytics URL for the Dev, Stage, Prod environments, then setup a Web server and finally link it to the DRM database to get the data. There is a shortcut icon available within the DRM application that will navigate to the DRM Analytics URL which can only be configured by the DRM Admin.

Most dashboard data in DRM Analytics is not refreshed automatically, that is why users have to manage Execution Plans. Check the sections in the DRM Admin Guide for more information on how to setup DRM Analytics.

The UI of DRM Analytics looks very similar to all the Oracle Cloud products that’s why it flows well with the new EDMCS cloud data management application. Even if the product looks great and it provides valuable insights on DRM data, based on discussions I’ve had with DRM customers at the ODTUG Kscope17 and Kscope18 conferences, it has the potential to be leveraged even more by DRM users if a few more enhancements were to be added in the future. (I will highlight some below. in Section 6)

1. Change Dashboard

Provides aggregated views of changes that have occurred in the Oracle Data Relationship Management system over time. Metrics in this dashboard are based on committed requests and all interactive changes. This dashboard includes change actions such as adds, updates, moves, and deletes across node and property changes to lend change perspectives by hierarchy, node type, property category, and so on. Users can understand change trends by change method, interactive, or workflow to ratify governance uptake. Users can drill into each change contextually to inspect transaction details and export these details to a flat file for further analysis offline. (Description per the Oracle DRM Admin Guide)

Request Dashboard

In the Filter section, users can choose to see data for different DRM Versions, Hierarchies and Node Types for different time spans. In the Change Method field, the user can differentiate between data that was added via DRG workflows or data added directly into DRM, since in many cases not all DRM data changes might have been automated. It would be useful for this field to have a multi select capability so that users have the choice to see all changes to DRM data despite of the way it was added in the application. Users can also see Property changes and visualize the trend of changes.

When users drill down to see the details of the changes, they’ll be able to detach the table to a larger view, reorder columns, display only relevant information, as well as export the data in Excel. In the Request ID column users will be able to see additional details of a DRG request, however once clicking on the id, they will be moved to the DRM application since this type of information is not stored in the DRM Analytics module.

Growth Dashboard 1

2. Growth Dashboard

Provides analysis of how versions and hierarchies have changed over time by displaying the number of orphan and shared nodes, the total number of nodes, and the total increase or decrease in nodes from a previous version (for lineaged versions) and the total increase or decrease in the last 30 days for non-lineaged versions. (Description per the Oracle DRM Admin Guide)

Change Dashboard

3. Request Dashboard

Displays key performance indicators as they relate to open Oracle Data Relationship Governance requests allowing you to identify bottlenecks and requests that are overdue or near due, and provides the ability drill-back into Data Relationship Governance requests to make changes to a request. (Description per the Oracle DRM Admin Guide)

Request Dashboard

Request Dashboard 1

4. Model Dashboard

Provides analysis of Data Relationship Governance workflow model design by displaying historical performance of requests that are completed (committed or rejected), including participant behavior trends, resource workload, and the ability to drill-back into Data Relationship Governance requests. Workflow model analysis reports on performance of completed requests processed by each workflow model to understand model performance based on service level agreements, level of automation achieved, cycle time, resources committed, request workload, throughput, and participant engagement. (Description per the Oracle DRM Admin Guide)

Model Dashboard

In the above image the user could see metrics on the DRG Workflow model performance specific to cycle time, average request items, and average participants because the “Sort By” was by Count. However if the “Sort By” filter selection is changed to Participant Name, the user will see metrics on the behavior of individual participants for that particular DRG workflow model.

Model Dashboard 2

Another insightful way to look at participants’ performance is across all DRG workflow modules. To do that, the user needs to select “All” in the “Model” field filter and adjust the other filter criteria for Model Status and Timeframe. Afterwards, the user will have a clear understanding of the DRG workflow participants need to be trained to adhere to data management procedures based on the number of rejected, overdue requests associated with that particular participant.

Model Dashboard 1

5. DRM Analytics Reports

Used to view user and group membership, security, and activity. Information provided includes user role assignments, access group assignment reports, and user login activity. (Descriptions per the Oracle DRM Admin Guide)

Reports analytics

  • User Role Assignment Report––Provides a list of users by role or roles by user with counts by licensed user types.
  • Access Group Membership Report––Provides a list of users by interactive and workflow user groups.

User Role Assignment Dashboard

  • User Login Activity Report––Provides trend reports for user login activity over time.
  • Metadata Object Usage Report––Provides frequency distribution and aging information for Data Relationship Management objects: queries, compares, imports, exports, blenders, and books.

User Login Dashboard

  • Object Access Group Authorization Report––Provides mapping of users and user groups to specific Data Relationship Managementobjects.
  • Hierarchy Access Group Assignment Report––Provides data grants of users and groups to nodes in a hierarchy.
  • Workflow Access Group Assignment Report––Provides data grants of users and groups to workflow model stages.

6. Suggested Enhancements

  • Draft DRG request metrics are not displayed in any of the dashboards. Even though it makes sense to see details of Committed DRG requests in a dashboard, DRM Analytics Managers are interested to see the number of Draft requests that are pending to be submitted. This is especially important during quarter close periods.
  • There is no dashboard or report that displays DRG Property Value details. Most dashboard drill through views display data at the DRG Request and DRM Item level, however the Property Details that are added/updated for a DRM node can not be readily seen unless the user logs into the DRM application. This functionality would be useful because the metadata is what gives the master data meaning.
  • Currently DRM Analytics doesn’t have any reports to display DRM specific validations and DRG validations for each workflow model. DRM data quality relies heavily on validations so the product should offer an accessible way for all kinds of users to review validations and propose changes as well.
  • It would be useful to have the ability to create customized reports either through the DRM Analytics Interface or through a behind the scenes scripting functionality that doesn’t require DRM Admins to tackle back end tables to retrieve this kind of information.

By Neviana Zhgaba, Oracle DRM Project Manager at General Electric

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s