1. Steven Adler IBM Information Governance Solutions IBM Information Governance
2.
3. Outcomes That's why you need Data Governance... Five years ago, The IBM Data Governance Council Created the Data Governance Maturity Model To benchmark organizational maturity...
4.
5. My company is like every organization... ...We are product-driven...
7. The IBM Info Supply Chain for System X Announcement process CBS CCE MASSLOADER BH MASSLOADER CCE Staging Core Data BH BUILD CCE BUILD BH Catalog CCE Web Catalogs EDI CoC Launch CIR POST PROCESSING & ENTITLEMENT Public Entitled Prices EPR ePricer CMT NetBill BIDOPS BIDS BIDS01 Parts Price File Special Bids Catalog SMB Catalog Price Letters / Announcements PartnerWorld US Catalog Data Store USPrice (Greenock) PPSG AM Price Files Partner Commerce Catalog DATA ENTRY CUSTOMER Price Action Worksheet Price Announcement Creation (Notes) eAnnounce HWPIMS ECCM OIM (HVEC simplified)
8.
9. We all share the same challenge... ...To become Data Driven Organizations
10.
11. To become a Data Driven Organization ...You need Data Governance
12. To overcome challenges and achieve common goals Revenue Generation Strategy & Business Agility Cost Reduction / Avoidance Compliance & Risk Goals Inhibitors Can’t easily customize product offerings and bundles No single view of customer Undermines Causes Can’t easily Identify cross-sell, up-sell opportunities Can’t easily identify high value customers Causes Causes Can’t easily Reduce data errors Ad-hoc data quality methods Lack of data retention policies High infrastructure cost Causes Causes Inhibits Weak data security monitoring Exposure of Personally Identifiable Information in non-production Higher than necessary probability of data misuse Difficult to meet demands of new business channels Non-compliant with state & federal regulations High potential remediation costs Undermines Tarnished brand reputation Can’t easily identify key relationships and hierarchies Can’t easily consolidate data from silos, integrate new systems quickly (M&A) Undermines drawn by | marc salzman
13. Governance is the Activity of Coordinating Communication To Achieve Collective Goals Through Collaboration
14. To achieve better business outcomes... ... you need more information, people, and systems
15. Lets talk about People: Architects define the world as it should be: - Standards - Policies - Guidelines Stewards measure the world as it is: - Assessments - Compliance - Monitoring
16. You need a 3-step process to monitor change... ...So you know what to fix before it fixes you Assessment Investigation Gleaning
17. In 2009, I hosted a Data Governance Council Meeting ...in Kuala Lumpur, Malaysia for 30 customers
18. At the meeting we had one customer with a problem ...and he wanted help from the Council to solve.
31. Data Quality Management Information Life-Cycle Management Information Security and Privacy Core Disciplines Data Architecture Classification & Metadata Audit Information Logging & Reporting Supporting Disciplines Organizational Structures & Awareness Enablers Stewardship Policy Requires Supports Enhance Data Risk Management Business Outcomes Goals 1. You can use The Maturity Model to ... Assess potential risks to Data Integrity from SDLC
33. Join the global community and work with your peers www.infogovcommunity.com
34.
Editor's Notes
Why is it so difficult to get the data right? This is a simplified view of the e2e landscape for System X product announcements IBM delivers Product & Price data to Partners via many different mechanisms There are multiple begin and end points, aka catalogs The Partners imbed the data from some of these feeds into their systems The way that we deliver product & price data to our customers & partners is highly complex and data driven. It relies on the synchronization of multiple data points in the flow in order for the correct data to be provided. When something goes wrong there is usually a customer impact that has a negative impact on IBM’s credibility and revenue. To get it right, for an announcement for example, requires the coordination of multiple activities performed by multiple organizations, according to a very tight schedule. When something goes wrong, tracing back through the flow to determine when and where a failure occurred can be complex and time consuming. Each of the nodes and manual intervention points can be a potential cause for data quality issues The goal is to identify data problems as early as possible to minimize customer impacts
The Information chain is not just about “data” Data is the blood stream enabling and connecting business activity through IT systems and applications All 3 dimensions need to be understood, which can be a continuous learning experience Efforts on Business glossary and Meta Data solutions will help, but often gaps remain Initial challenge often is to find the right place or right SME to obtain information – Build a “who is who” along the way Detail knowledge is often in “people’s head” or disbursed across many places on the Intranet, Documents, archives etc. For long term sustainability decide on how to capture the information consistently, ensure it is easy to access and navigate and determine on how to maintain the information current Level of granularity can easily become burdensome and overwhelming to avoid turning this into a documentation exercise Stay practical, develop the knowledge as needed, ie what area and pain point is being worked and expand over time Working the information chain typically brings different teams together, IT operations, application defect mgmt, Business operations, Business transformation architects and analysts and process experts Often a blend of different disciplines will be applied depending on issues being worked and in which of the 3 spheres the improvements targeted The information chain mgmt can easily lead into Lean sigma projects and business performance mgmt methods being applied This can be seen as another dimension of e2e – bringing IT, Business and Data together, and while the blurring of the lines can cause confusion of accountabilities, it should be seen as key element of information chain management
![Agenda ,[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)