EDMC Logo



The EDM Council freely provides access to all published resources from this website for member firms and firms interested in future membership. Please register to get a web access ID and password.
About
Sponsors
Resources & Documents
Success Stories
Contact
Join EDM Council
EDM Council BLOG
Member Directory
Member Login
Register for Website Access
Job Portal
Global Regulatory Activity
Semantics Repository
Data Management Maturiy Model
Data Quality
Standards
Presentation, Reports and Others
Links
Links - Standards Related
Links - Trade Groups
Links - Regulatory
Links - Industry Utilities






  EDM Council BLOG

The Ontological Winds of Change

My view of standards is no secret. I’ve been listening to and involved in standards for the better part of four years. And it’s not because I’m a standards geek. It’s based on an aggregation of the stated wants and needs of the financial institutions.

And I organize all those wants and needs into a core hypothesis. And that is that precise and unique identification of the three critical attributes – namely financial instruments, legal entities and data elements are the foundation of effective data management. Get the foundation right because that’s what everything else can and should be built from.

The case is compelling as it relates to data element identification. There are hundreds of data elements, delivered by an equal number of sources - making it hard to compare data, hard to automate business processes, hard to exchange data, hard to feed models, hard to create consistent benchmarks and resulting in a never ending process of mapping and cross referencing.

I’m suggesting it is time to fix this challenge. I believe it’s possible to fix this challenge. And I believe that we’re pretty close – so that the task isn’t really that hard.

However, there are some requirements. The financial institutions as a coordinated body needs to lay down the collective gauntlet that you want it to happen – and happen in the short run. Financial institutions need to make sure the requirements are stated with some degree of precision. If you don’t make it completely clear what you want, the chance of you getting it (in your lifetime) is close to zero. And you need to leverage your combined clout and insist on accountability and project delivery (i.e. the same process you use to manage every other project within your own shops).

Now I realize that no one likes to talk about standards in polite company. And I understand why. The process is shrouded in mystery … usually spoken by people with strange accents … with an ungodly amount of unnecessary bureaucracy … using lots of code words and numeric tags … with little accountability … in a process that seems never ending … with little practical output … and nothing in terms of project plans, delivery milestones or process transparency.

That being said, I don’t understand why you financial institutions tolerate it when in fact you own the governance, it’s your problem to fix and the benefits of doing it right are significant.

Now it could be that I’ve misread the importance and I’m certainly open to hearing that’s the case. But we’ve certainly got enough validation that we’re pursuing these activities with alacrity. And will continue to do so until you tell us to stop wasting your time.

With all that as backdrop – I am bursting with optimism and have mostly good news to report. And I’d like to start by uttering some bad words – namely ontology, taxonomy, symbology and metadata management. These are not words I suggest we use when trying to sell this concept – but among us data geeks it might be OK.

Let me continue by confessing my sins. Back in 1997 a bunch of financial institutions got together to try to standardize the terms and definitions of reference data. And I was one of those hired to defeat the initiative – which we did. The problem was the financial institutions also wanted to standardize values and the vendors (that hired us) didn’t like that.

In 1999 the same financial institutions came back to the industry and wanted to try again – this time leaving out the standardization of values. The problem was that the discussion was being facilitated by a bunch of technologists who were all enamored with a new processing technology know as XML. So instead of listening to the requirements of the firms and creating standard data ontology, we produced an XML schema. Lots of effort, wrong objective.

In 2004 we all tried again. This time I was helping to lead the charge and we went to ISO and got absorbed into the


 
ARCHIVES

- 2010
- 2009
- 2008
- 2007
- 2006
- All

SYNDICATION
RSS    ATOM
COMMENTS

By: Jon, 01 Oct 2007
Hi Michael,

It is sad to see that no comments have been posted yet, but also kind of interesting to be the first to do so :-)

I like the way you describe the problem (strike one, two...) but I like even more that we have the possibility to do something together on this.

Let me share with you and other readers... what we have been doing in the standards space within UBS.

Back in 1999, after the merger between old UBS and SBC, we decided to go for a standard. We called it the Partner Data Standard and it was supposed to standardize the core attributes (total of 25) we should store about a Partner.

Defintion: a Partner is any person (natural or juristical) with a relationship to UBS. It can be a customer, vendor, service provider, issuer or...

The expression "Partner" was regarded to be an umbrella expression based on the belief that the data model is the same for every person which has a relationship with UBS. A person - the relationship - a UBS enitity. The relationship is typed e.g. a credit relationhip, a vendor relationship and so on.

Creating the standard was quite a bit of work but the implementation has been terrible. The reason, as I see it, is that we did not set up a governance structure to follow up with the projects dealing with the "Partner", and this is pretty much every project in the bank. I think this might be the issue at other financial institutions as well.

Personally I see great benefit in this type of standardization effort but not without a thorough follow up with regards to the implementation. The communication effort even within a large FI as UBS is huge and not to be taken lightly.

Have you really not received any other comments on this topic? Would you consider putting together a team to work out some ground rules which could be shared between the FI's? If you did you can count me in!

Let me know what you think.

Best regards,
Arnt-Erik Hansen
Head Group Partner Data
UBS AG, Zürich
arnt-erik.hansen@usb.com




By: Marc, 09 Oct 2007
Arnt-Erik, I have a hard time reconciling the messages I get (in person) in talking with firms about unique identification with the lack of response (online) as well. Maybe our friend Mr. Luditte is still lurking in the corner. Maybe people are just too "heads down." Maybe people are afraid of embarassing themselves. Who knows.I think there are two real issues at work. The first is how long it takes and how difficult it is for these core concepts to really work their way up the organizational chain. The good news is that while we have been preaching the importance of unique entitiy identification for a number of years - it has finally emerged as a significant issue on the minds of many firms. Perhaps it was just a concept ahead of its time (back in 1999) - but it is now front and present thanks to the unmovable forces of regulation, customer compliance and the CFO's office (for client netting, profitability projections, cost analysis, etc.).

The second (and you hit upon the most critical point) is about implementation. I have been talking to a lot of people of late about the challenges of migrating to a unique identifier and integrating it into legacy environments. I think this is the most important component - and one that is not simple to address. Most firms tell me it will be a two step process. The first is to get their internal house in order in terms of creating and implementing an internal identification standard (that's the hardest part). The second is when we get the industry standard identifier (and I'm optimistic here) - how firms will link their internal activities to the standard. The first is about enterprise-wide and application-wide integration. The second (I suspect) is just another cross-referencing problem.How are the rest of you dealing with these challenges?


© 2010 EDM Council, All Rights Reserved