• No results found

Collaborative Enterprise Understanding

N/A
N/A
Protected

Academic year: 2021

Share "Collaborative Enterprise Understanding"

Copied!
10
0
0

Loading.... (view fulltext now)

Full text

(1)

Collaborative Enterprise Understanding

A New Approach to Data Understanding & Governance

(2)

Case Study Index

1.

Initiating Cultural Change

2.

Promoting Alignment & Reuse

3.

Establish Lasting Governance

4.

Wholesale Division Resolvability

5.

Research Data Stewardship

(3)

The value dilemma

1.

Small contributions in tune with local expertise

2.

Linking data to business facets brings relevance to business users

3.

Local understanding is connected up to the wider context and visa versa

4.

Each connection strengthens or extends the knowledge network

5.

Each connection validates and enriches the whole

Nobody argues that managing our information better can provide

significant benefits to the business.

It’s human nature to ask “What’s in it for me / my department?”

If there is no local value fairly quickly, support will only last until a

more urgent task comes along

(4)

Outcome

Case Study 1 : Initiating Cultural Change

• The wholesale division of a large UK bank had identified

significant data challenges & wanted to set-up a division wide data management programme

• Multiple programmes had tried

and failed to make an impact in the past

• Stakeholders pushed back on

the idea due to scale, complexity, and previous failures

• The CEO of the division was a

strong initial sponsor to force initial momentum

• Axon was used to quickly

collate data understanding and engage communities across functional boundaries

• An integrated and contextual

view brought business relevance and turned forced participation to voluntary and growing

participation

• The initiative extended outside of the division, with groups requesting to join

• Over a period of 6 months, over

250 people from Change

Management, Operations, Risk, IT and FO collaborated on

building, validating and

managing a real-world view of data usage

• 100+ systems, 9000+

attributes, 800 unique data concepts etc.

Axon provided a view of data that was relatable, and shared the workload to simplify

collaboration

“Where is the value?”

“This is practical, and can help

me solve real issues”

“We have a go-to-point and

a process to get clarity”

(5)

Outcome

Case Study 2 : Promoting Alignment & Re-use

• A Finance department was

responsible for consolidated reporting performance

• Many performance unit code

lists existed and materiality of differences, origination, usage and ownership was unclear

• Previous alignment efforts had

failed

• Significant reporting challenges were arising every month as the codes could not be reconciled across platforms

• Axon was used to maintain,

change control and publish the central unit code list

• New parties were gradually

brought on board by initially recording mappings into central list

• Over time almost all differences got reconciled as materiality, context and impact of

differences end-to-end was clearly understood

• 3 years later the team are still controlling a widely used reference data list, efficiently and effectively supporting the business

• The success has inspired them

to bring additional lists under governance in the same manner

• Stakeholders of the service are also improving their data

governance practices in their areas

Axon helped to break down complex issues, promoted collaboration through common

understanding, and expansion through demonstrable results in a credible application

“Lists are too complex and

diverse to align”

“Aha, I understand why you

want to do it that way”

“Transparency & control

breaking years of deadlock”

(6)

Case Study 3 : Establish Lasting Governance

• Wholesale banking division had

made several attempts at data governance had failed before

• Data Governance was perceived

to be overhead, detached from reality and providing little benefit to the day-to-day

• No tangible output other than

policy document and meeting minutes

• Axon was used to engage local

business communities and invite them to capture their local data reality in terms of system

dictionaries, lineage,

stakeholders, change processes etc.

• Local responsibilities as well as local subject matter experts were recognised

• Local submissions were

connected up in terms of data lineage and business glossary

• Unprecedented level of input

and support for data governance

• Data governance work was

grounded into the business reality of today

• Discussions of ownership had

precision and context

• Data was made tangible and

given a documented state that could be discussed

strategically rather than just going from hot issue to hot issue

Axon provided a platform for local business communities and central functions to

collaborate and establish a transparent and responsible way of working

Outcome

“They are stuck in their own

silo, in committee rooms”

“Data has been made

tangible and relevant to me”

“Getting DG into the reality of

today”

(7)

Case Study 4 : Wholesale Division Resolvability

• Wholesale banking division was

being sold off and the interconnectedness of the division with the other parts of the bank needed to be

understood

• Most time critical was to

understand the division’s client data flows and reliance on group systems and resources

• Diaku Axon was deployed as

part of a 6 week effort to capture the lineage for those data items critical in the client onboarding process across 57 systems

• Data and system usage and

ownership was mapped out at the at a legal entity level

• Local accountable parties and

subject matter experts recorded against each of the items

• The knowledge captured in

Diaku Axon formed a key part of the submission to the

regulator confirming data

lineage, usage and controls are understood and compliant with set policies and regulations

• The effort was subsequently

leveraged to introduce a data governance service and have data knowledge as a corporate asset

Axon provided a platform to very quickly chart the organisational interconnectedness and

assess resolvability issues

Outcome

“Wholesale division being sold

and needs to be carved out”

“Chart data, process and

system lineage in and out”

“Understand

interconnectedness”

(8)

Case Study 5 : Research Data Stewardship

• Research division at global pharmaceutical wants to drastically increase reuse of research data

• Research is typically executed

within the silo of a research unit with very little sharing of results be those positive or negative • Lack of sharing of research

efforts and results has lead to sizable duplication and

unnecessary spend

• Diaku Axon was deployed as

part of a 4 month effort to chart core research systems across 5 business areas

• Research data was classified

across 100+ systems

• Data lineage captured across

main data hubs

• Business glossary of 3k

research terms captured

• The research data landscape

has been outlined

• Understanding about data

origination established

• Business glossary leveraged to identify which research data resides in which systems

• Diaku Axon being rolled out

across the division to drive business engagement and stewardship effort

Axon platform rolled out to drive Data Stewardship effort and ensure reuse of research data

Outcome

“Increase reuse of research

data”

“Chart research data

landscape ”

“Data stewardship driving

reuse of research data”

(9)

Case Study 6 : Business Transformation

• Diaku Axon was deployed to

provide insight into project dependencies and overlaps in terms of systems, data,

regulation, use of subject matter experts etc

• Data lineage captured in Axon

further informed the project scheduling

• Enterprise wide programme at tier 1 bank to consolidate client onboarding activities and

systems, provide single master source of client data

• Regulatory requirements, application rollout, competing reconciliations and 600+

downstream systems create an extremely complex environment • Interdependencies not properly

understood nor managed

• Interdependencies of large

number of projects and the affected systems and data within can be tracked

• Impact of scope changes can

be assessed with precision

• Any member in any of the 100+

projects can now see the data lineage relevant to any of the projects and overlay the map with dependent projects

• Shared view shows the new landscape, enabling smooth transition into operational BAU

Axon platform giving unprecedented insight in project and data dependencies

Outcome

“Enterprise wide consolidation

of client onboarding”

“Connected view of project

and data landscape”

“Ability to manage project

and data dependencies”

(10)

Data is used by the business, but data is not their business

When data is presented within its business context, participating becomes a

way to solve business challenges

Doing better around data requires collaboration across many functions and

stakeholder groups

Why it works

References

Related documents

Patients hospitalized for AMI and heart failure in regions with lower density of cardiologists experienced modestly higher 30-day and 1-year mortality risk,

 The Statewide Data Analytics Contractor (SDAC), the focus of this case study, is responsible for providing the state, the RCCOs, and PCMPs with actionable data – at the

may in fact have played Julius Caesar in Shakespeare’s recent play about his assassination, stabbed to death on the steps of the Senate House in ancient Rome (although

Based on the conceptual framework of social determinants of health inequality, this research aimed to determine the effect of macroeconomic policies on the social-health inequality

Qrz wkdw odujh vdpsoh uxohv ri lqihuhqfh iru iudfwlrqdo U E_ä surfhvvhv duh dydlodeoh/ dqdo|}lqj iudfwlrqdo lqwhjudwlrq dqg frlqwhjudwlrq lv d uhdolvwlf srvvlelolw|1 Iru

* List the organization's five current highest compensated employees (other than an officer, director, trustee or key employee) who received reportable compensation (Box 5 of Form

(3) if you contribute to the cost of the Personal Critical Illness Insurance, the first day of the Insurance month following the date you make written application for