Achieving connected data governance using Informatica’s Axon and EDC

Achieving connected data governance is vital if you want to be able to use your organisation’s data to effectively compete and comply. A common barrier to achieving connected data governance is that business and IT people speak different languages and use different systems (there’s more information about this in our Connected Governance White Paper). To achieve connected governance you need to unite the disparate worlds of business and IT within your organisation to create a more effective ways of working. This short series of videos shows how this can be achieved by combining Entity’s data expertise with Informatica’s data software tools.

Each video shows a commonly experienced data governance related challenge for both business and IT users in a typical business setting, and demonstrates how these challenges can be overcome through the employment of Entity’s connected data governance strategy together with the data governance software (EDC and Axon) supplied by Informatica.

We used Axon because it provides a higher-level view of the data and associated systems within an organisation, and EDC because it provides a much more technical and detailed view of specific information about the data that is being held. Axon would be typically used by a business user, and EDC by a technical IT user. Working together, these two systems facilitate connected governance by ensuring that both IT and business users have everything they need to work together towards their shared objectives.

Making a change request in Axon

A sales manager has been tasked with making a change to system by adding a new attribute to a sales table so he can record secondary email addresses. As a business user the sales manager doesn’t know much about the change process or who to speak to so, using Axon, he can find the system in question and then review further details about that system such as system interfaces, stakeholders or data, which is where he finds the sales table that he wishes to add the attribute to.

Now, he can use the stakeholder overlay on the data map to see the stakeholders of the data involved and any other linked datasets. Using these details he knows who he can contact with any queries.

He wants to find out what the change request process is on the system so he clicks through to review the workflow and now he can understand the exact process of initiating the change request to the system. With all the relevant information at hand he can now complete the change request  that will go straight through to the IT user who will be able to action his request.

Locating an attribute definition in Axon using a business glossary

 

A business user in an insurance company receives a daily motor claims report, detailing claims figures from the previous working day. He’s unclear as to what an attribute labeled DOL means. In the past he has noted that different people in different departments have given this term different meanings. However, he can use Axon to avoid any ambiguity by locating the agreed business definition of the term within the business glossary.

He can find the report in Axon using the Unison search feature. He can then locate the attributes of that associated report and then click on the attribute glossary tab. This takes him through to a summary screen with the full definition made available to him where he finds that this particular attribute refers to ‘date of insured loss’.

If the user is still at all unclear about the definition he could contact the person responsible for the glossary definition. Axon connects the glossary term’s objects such as attributes across linked datasets. The business user can further analyse the distribution of the glossary term and discover any associated linked attributes throughout the business by activating the dataset lineage mapping tool with the linking attribute overlay.

Investigating a data quality issue using Axon

A business intelligence analyst has received a notification indicating that the data quality of a data attribute in a GDPR report has been flagged as being below acceptable limits. She’s been tasked with investigating the data quality issue.

First, the user can find the report in question using the Unison search feature on Axon. Then she can look at the data quality tab and look at the data quality dashboard for a quick overview of the data quality of the report.

She wants to see if this is a new issue or if it has been going on for some time so she looks for the affected attribute and its associated DQ rule in Axon. She clicks on the report tab and she can see that the issue has been going on for many weeks. She therefore suspects that the issue may coincide with a recent business acquisition.

She needs to confirm that this is the issue so wants to discuss this with the person responsible for the DQ rule. She goes to the stakeholder tab where she can then locate the contact details for the responsible person and approach them to discuss the matter further.

Understanding the policies that govern your data using Axon

A compliance user is conducting a policy and regulatory audit of the company’s core systems. She wants to understand what policies regulate a particular system, how these policies operate and what their impact is on the business as a whole. However, being a business user she isn’t quite sure how to source this information.

She begins by using Axon’s search feature. She is presented with a wealth of information about that system, however she wants to know exactly what business policies and regulatory policies are affecting this system. She clicks on the impact tab and the policies subtab.

She notes a policies with which she is not familiar so she clicks onto it. Here she is provided with a plethora of information about that policy including a summary, and a link to any associated documentation or web links. Having reviewed the information, she would like to discuss the policy further with someone in the business so she clicks onto the stakeholder tab where she can find the responsible person and click through to contact them for further information.

Identifying data stakeholders using Axon’s stakeholder community feature

An IT user has received a change request for an attribute in an existing dataset. However, before implementing this change he needs to speak to the owner of the attribute or the dataset to check that there will not be any adverse impact of implementing the change.

First of all he goes to the search feature to find the attribute in question. He can see from the search results that this date attribute from the claims history dataset is the one in question. He can read through the list and check that the attribute is in the list and consult the attribute glossary term if required. Once he has confirmed this information he can proceed to find out who the stakeholder is.

He then realises that the claims history dataset doesn’t have any dataset stakeholders or any data attribute stakeholders however Axon’s stakeholder community feature enables him to locate stakeholders of linked objects that he could contact to see if they are able to help with any of his queries.

In the stakeholder community there is a list of other people within the organisation who, whilst they do not have direct responsibility for the claims history dataset, may be able to help out with any queries he has. Once he has assessed the best person to contact he can click through onto their contact page to obtain their contact details.

Using Informatica’s Enterprise Data Catalog to understand an organisation’s systems

A new IT manager has been recruited and wants to understand the systems that she is responsible for. She uses the search feature in EDC to find such systems. She can look deeper into each of them to find what other system are upstream and downstream to ascertain what potential inputs she may be responsible for. Technical assets may have names that are cryptic or difficult to understand. She can display the business terms defined for each asset. She can view the description for a specific technical asset from the Axon glossary imported already in EDC.

How Informatica’s EDC and Axon enable IT and business users to speak the same language

A business user has to fix a priority issue in a system. The problem has been located with a single attribute with the wrong format.

With a connected governance solution he can trace all associated technical assets, helping the IT team in quickly and efficiently searching out other affected systems or tables. He can search for the specific attribute in the Axon glossary.

In the Enterprise Catalog tab there is a list of linked assets. He can view the impact on associated assets in the EDC. He can find the tables that the problematic object was sourced from and of course he can go back to Axon using the associations of technical assets with business terms. That way he can get a better understanding of both the business and IT worlds for fast and accurate action.

Axon and ECD – understanding linked fields and determining value frequency

A management information analyst at a motor insurer is working with the marketing department to help develop a new marketing strategy. He is aware of a mailing report that contains some valuable sales data that will enable the business to target multiple vehicle households. Using the connected systems of Axon and EDC he is able to review and analyse the mailing system and any associated databases from both a business and IT perspective.

He uses Axon Unison search to locate the attribute ‘num_cars’. He clicks on the attribute from the search list. This opens the mailing table page showing all the attributes in the table. He can click on the glossary tab for an explanation of the business term or he can click on the linked field ‘number of cars’ attribute which opens the attribute in EDC.

Within EDC he can see a wealth of information about that attribute including the frequency of given values within the data to help him analyse the number of cars in each potential customer’s household, enabling the business to target its marketing accordingly.

  • Need to find out more:

    Contact Entity

  • This field is for validation purposes and should be left unchanged.