• Orchestra Networks

Recapping Data Governance Financial Services 2016

Updated: Jun 12, 2018

Last week Orchestra Networks had the unique opportunity to deliver two presentations to the attendees of the Data Governance in Financial Servicesconference in Jersey City, NJ.


Our first session, jointly delivered with a partner, focused on how the Information Asset data governance operating model was implemented in EBX. The second, jointly delivered with Citi, was a keynote on the future scope of data governance.


We're pleased to report that the presentation went over quite well (thanks to our awesome co-presenters!). For those of you that missed it, we quickly recap the talks beneath and provide a few comments. If you'd like copies of the presentation materials please feel free to send us a note.


Data Governance in a Box with EBX


This session was co-presented by Jae Lee, Manager at Information Asset, and Conrad Chuang, Director of Solutions Strategy at Orchestra Networks. The team provided a quick, thirty minute, overview of how Information Asset's comprehensive data governance operating model ("Data Governance in a Box") was implemented in Orchestra Networks' EBX. It was the ideal follow-on from Sunil Soares' earlier "Data Governance in a Box" presentation. The talk brought to life many of the concepts Mr. Soares covered in his presentation.

Information Asset Data Governance Operating Model


Implementation in EBX5


Mr. Lee and Chuang highlighted how data governance teams and their constituents could use Orchestra Networks software, EBX, to support typical governance use cases, such as:

  • Definition of business terms and data dictionaries,

  • Identification of critical data elements,

  • Specification of acceptable use criteria for data owners (and attestation by data consumers),

  • Documentation of data quality rules and DQ rule scoring,

  • Governance of analytical models,

  • Ties to reference and master data, and of course

  • Workflows


EBX5 screenshot: Business Glossary


EBX5 screenshot: Workflow


EBX5 screenshot: Analytical Model


Among the highlights was a brief discussion of how the EBX supports the three main types of data lineage.



What's the "D" in CDO?


This session was co-presented by Garry Katz, Chief Information Architect for Global Functions at Citi and Conrad Chuang, from Orchestra Networks. Unlike our solutions session—which was focused on the implementation of a governance model—this session was a bit more forward looking. This keynote followed Jennifer Ippoliti's excellent keynote that identified lessons learned from implementing data governance at JPMC.


The speakers poked fun at their title, pointing out that today the "D" in many CDO groups represents "documentation." This is natural because governance teams have been busy documenting their current "as is" environment—cataloging and inventorying their data assets, business terms, policies, lineage, and quality rules—to comply with regulations. But as teams near the end of their major documentation effort, questions emerge. Should governance teams do more than policy documentation? And if so what? These questions and how Citi is addressing them consumed the remainder of the keynote..


To highlight the scope of the governance challenge the team used a fault-tree to illustrate the various root causes that could create poor quality reports.



The speakers then looked at the typical remedies for addressing those challenges



… and where governance teams have typically been responsible:



For the speakers, these gaps represented opportunities for the governance teams. Addressing these other areas could lead to a holistic, ‘networked' solution to their organization's data governance/management challenges. To drive this point home, Mr. Katz presented a case study on Citi global functions and how they have taken this approach with their Data Catalog.



Mr. Katz spoke at length about how the data catalog unifies and connects governance to other areas of data management. And how, as a whole, this catalog will support key initiatives to govern analytical models and end user computing (excel, et al), and comply with regulations such as DFA and BCBS 239.