Lean Master Data Management


Published on

Using Lean Six Sigma for Data Quality Management

  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Possible to use with RACI
  • Take the opportunity to discuss D&B
  • Highlight that CD2 is a customer and an enabler
  • What is important about each element Accessible:HON diversity of source system types, even after we are all on SAP will have Siebel as systems of reference Available: quick reaction to the business climate Quality: Perfection is the enemy of good Consistent: Communication Auditable: keep whole Secure: protect this valuable resource, role based security
  • Receive what is needed when it is needed
  • 1. Specify value in the eyes of the customer - VoC survey for CD2 Engage cross functional team for Governance Manage expectations and understand gaps 2. Drive standards within the SAP environment Identify and define Core CMD Drive standardization of data stewardship processes Populate DUNS# in Credit Info. No. in FI Credit Master 3. Make the processes flow – Material Flow Analysis Perform a 5 S effort for CMD Reconciliation to DUNS# Drive standards within the SAP environment Automate CD2 processes for CMD management 4. Make only what is pulled by the customer CD2 Self-Service & standard reports Special Request Reports 5. Strive for perfection by continually removing waste Seek root cause and drive to a standard process Facilitate Data Quality tool rollout and Governance plan End to end performance management STAR: Empower the employees Ensure data ownership and management at the source Drive decisions to the lowest possible level Load balance work groups
  • Key point: burn out, not have institutionalization, quality degradation Success: Engaged Finance to assist in encouraging SBGs to take data ownership Equated clean data to dollars (without alignment we do not understand our customer family structures) Only the business itself can make the “calls” due to different definitions of quality. Oracle (bill to & ship to). People who know the data, understand the date, and can make the call or clean up. Hurdle: Disbelief, you will hear, this can’t be done. It is never technical always cultural.
  • Introduction to 5-S Use as presentation guide organizing around CMD Governance Council, RTY, Standards for CMD & Tools, and Audit trails
  • Result: percentage increase of Honeywell customer business entities having D&B Confidence code (cc) of 8 or greater enabling family alignment and associated revenue recognition Match rate calculation excludes classified customers and U.S. Government entities Utilize 2004 customer master data sold-to records, aligned dollar values, and revenue Target: increase the current rate of XX% to XX% match rate based upon 2004 revenue coverage Match criteria D&B match CC of 8, 9,or 10 is accepted as a match D&B CC of 1-7 are Low Confidence (LC) match records requiring manual review CC of zero is a Non-Match (NM) record requiring manual review
  • 3 Determine required quantities Identify CMD Sold-to records by dollar amount within source system required to achieve 85% of total revenue aligned to customer families Sort the source systems by dollar: Top 7 source systems required to meet objectives Sort the customers within Top 7 source systems by dollar resulting in the Top 100 customers per source systems to meet dollar goal Add additional source systems (Group2) to ensure success Add additional source systems ensuring success (2007 addition) Review top 100 customers in remaining source systems to ensure that no high dollar customer is neglected (2007 addition) Maintain transaction traceability Matching customer record to sales dollar record Traceability to customer within source system within SBU
  • 3 How do we prevent LC records Yield is the good vs. bad for each process box Prasanna will run SM as an example to see how it goes. When the process is set he will run one ACS file (HPS), TS, Atlas. A control chart will be done to show the range and a final sigma score can be taken from the range average (R-bar chart).
  • Measure 1 Business impact: LC & NM customer records, return from D&B, measured by dollar value as % of revenue need to be matched to DUNS# Ensures family alignment, identification of strategic customers, proper revenue recording Attaining targeted % match rate resolving 2006 LC & NM Manage 2007 incoming data resolving matching issues for Top Customers independent of source on a quarterly basis 2. Measure 2 – Re-work Cost of re-work per record = employee cost at 20 min per record * no. of records. Cost of training, set up and post resolution analysis included Not included: Cost of LC re-send at 65 cents per record Calculation: Estimated re-work and loaded employee salary 3. Measure 3 – Scrap and OTTR Timing: Monthly, Correction can be sent next month & even 1 scrap may indicate process error OTTR to CD2 – file arrives per monthly agreement Timing – Begins 1QTR07 Discuss in regular Monday meeting which sources should use. Do an example for Monday 29 th . Determine reporting timeframes, suggestion is quarterly to be re-visited each ½ year. We used to send approx 5K per month, now send 1K per month records. Identify top source systems at year beginning to use as the base for the comparison Identify sources worked in 2006, show pre-effort NM and LC dollars and post resolution to have for Monday meeting. Data is 2004 / 2005 data. 4. Scrap is an email to Nancy / John Nancy to obtain access to CD2 mailbox thru Cathy K:CD2MetricsOTRR 20070123.xls OTTR – prize for best in show, most improved, booby prize
  • ACS: Alignment and mitigation of multiple legacy backend financial applications AERO: Rationalize / retrofit standards (changes have occurred along the way) Delivery of clean / current / de-duped records in SAP SM: Data integrity & standards including rules across all SAP systems. Facilitate M&A. TS: Documented process for Master maintenance, controlled, managed Corporate: Common structures with consistent definition & use across all data domains HCS: Minimize billing errors and bad debts
  • Factor this into your planning Be sure to address these things in your planning process If you’re going to tackle this, keep these things in mind Whole pain of standardization and simplification are needed
  • Lean Master Data Management

    1. 1. Honeywell Customer Master Data Governance Visibility Changes the Game Nancy Northrup, PMP Customer Master Data Governance Leader Six Sigma Black Belt, + Lean
    2. 2. Contents <ul><li>Introduction </li></ul><ul><ul><li>Honeywell International </li></ul></ul><ul><ul><li>The current state </li></ul></ul><ul><ul><li>Governance Begins </li></ul></ul><ul><li>Measure and Model – Six Sigma Lean as a core focus </li></ul><ul><ul><li>What is Lean </li></ul></ul><ul><ul><li>Lean concepts applied </li></ul></ul><ul><li>Current and Future Focus </li></ul><ul><li>Wrap up </li></ul><ul><li>Appendix </li></ul>
    3. 3. Honeywell’s Strategic Business Groups (SBGs) 2006 Sales Total = $31.36B Diverse Businesses, Technologies, Products, Channels 35% 15% 35% 15% Aerospace Specialty Materials Automation and Control Solutions Transportation Systems
    4. 4. Summary of CD2 Usage Reflects the Need Multiple uses for cross Honeywell view
    5. 5. It’s All About Growth Is this customer also a vendor? How is the Customer’s business growing and changing? Do other Honeywell business share this Customer? Source: Adapted from BI presentation D.Clark Dir. BI SM Dave needs it by Monday
    6. 6. Pre-Customer Data Integration <ul><li>Standard financial code names </li></ul><ul><li>But definitions are not standardized </li></ul><ul><ul><li>Data maintenance at the individual line of business level </li></ul></ul><ul><ul><li>But no central repository </li></ul></ul><ul><li>No Customer Relationship Management controls </li></ul><ul><li>Limited customer interaction awareness </li></ul><ul><li>Mergers and Acquisitions create additional complexity </li></ul><ul><li>Acquired competitors continue competing </li></ul>Customer Knowledge Sharing Done by “Talking” High Labor Costs / Low Return Constrained Growth
    7. 7. Finding Barriers and Enablers in Honeywell <ul><li>Historic autonomy in a diverse company </li></ul><ul><li>Accountability for strategic initiatives at the operational level </li></ul><ul><li>Integration of multiple versions of SAP </li></ul><ul><li>Enormity of legacy data quality issues </li></ul><ul><li>Complex distributed customer creation authority in a global corporation </li></ul><ul><li>Continued growth through mergers and acquisitions </li></ul>Barriers <ul><li>Buy-in of top management </li></ul><ul><li>Engaged middle management </li></ul><ul><li>Business Case for CMD quality </li></ul><ul><li>Well-executed communication plan </li></ul><ul><li>Inclusive council membership </li></ul><ul><li>Goal-driven program </li></ul><ul><li>Regular progress measurement & reporting </li></ul><ul><li>Distributed decision-making </li></ul><ul><li>Data standards and best-practice processes </li></ul><ul><li>Tool support for data cleansing, maintenance and system integration </li></ul><ul><li>Data stewardship and quality activities integrated with the day-to-day processes </li></ul><ul><li>Real benefits for front-line workers </li></ul>Enablers
    8. 8. Define Phase Begins <ul><li>Structured approach using Six Sigma DAMIC </li></ul><ul><ul><li>Define, Measure, Analyze, Improve, and Control </li></ul></ul><ul><li>Engage expertise </li></ul><ul><ul><li>Dun & Bradstreet </li></ul></ul><ul><ul><ul><li>Experts in commercial information and insight on businesses </li></ul></ul></ul><ul><ul><ul><ul><li>DUNS# : site and division specific code provided by D&B </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Data cleansing and family alignment </li></ul></ul></ul></ul><ul><li>Incorporate Lean toolsets </li></ul><ul><ul><li>Value Stream </li></ul></ul><ul><ul><li>5 S </li></ul></ul><ul><ul><li>Supply chain management </li></ul></ul><ul><ul><ul><li>Cycle time management and cost control </li></ul></ul></ul><ul><ul><ul><li>Load Balancing </li></ul></ul></ul>
    9. 9. Customer Family Analysis is a Starting Point <ul><li>Deep dive on select group of Customers </li></ul><ul><ul><li>Researched the data for match candidates </li></ul></ul><ul><ul><li>Categorized why the candidate did not match to high confidence ( ≥ 8) </li></ul></ul><ul><ul><li>Framework to understand Dun & Bradstreet (D&B) processing </li></ul></ul><ul><ul><li>Results are the basis of CMD Governance Council kick-off </li></ul></ul>Unknown address Not Matched By D&B Not sent to D&B Confidence <8 Not matched Under Global Ultimate <ul><li>Quality Actions Generate More Improvements </li></ul><ul><ul><li>Sharing match results with D&B </li></ul></ul><ul><ul><li>Drive CMD Governance Business Case </li></ul></ul><ul><ul><ul><li>Quantifying impact to users </li></ul></ul></ul><ul><ul><ul><li>Support CMD guidelines </li></ul></ul></ul><ul><ul><li>Projects and tools for: </li></ul></ul><ul><ul><ul><li>Data transformation </li></ul></ul></ul><ul><ul><ul><li>Standardization—codes, naming conventions… </li></ul></ul></ul>
    10. 10. CD2 Value Proposition <ul><li>Enable growth through expansive customer views </li></ul><ul><ul><li>Establish Honeywell view of strategic customer account sales and purchases </li></ul></ul><ul><ul><li>Support informed Customer and Supplier visits and negotiations </li></ul></ul><ul><ul><li>Enables quick response legal and business development inquiries </li></ul></ul><ul><ul><li>Serve as clearing house for D&B requests to reduce duplicate requests and costs </li></ul></ul>Source: IBM CD2 Study <ul><li>Enable Improved Customer Master Data Governance </li></ul><ul><ul><li>Facilitate transaction productivity & success </li></ul></ul><ul><ul><li>Complete customer “sold to” information </li></ul></ul><ul><ul><ul><li>360  customer relationship management </li></ul></ul></ul><ul><ul><ul><li>Provides standardized postal addressing </li></ul></ul></ul><ul><ul><ul><li>Enables business intelligence reporting </li></ul></ul></ul><ul><ul><li>Strategic Business Groups (SBG) and Corporate entities aligned on data standards for self-governance and ownership </li></ul></ul>Aerospace Specialty Materials Automation & Control Solutions Transportation Systems Honeywell Customer Creating “ One-Honeywell” Aligned to the Customer
    11. 11. Problem Statement <ul><li>Honeywell is unable to consistently and clearly identify the complete relationship with our business partners which impacts: </li></ul><ul><ul><li>Assessing credit risk management </li></ul></ul><ul><ul><li>Analyzing the full relationship for cross sell & up-sell </li></ul></ul><ul><ul><li>Maximizing value exchange in the relationship </li></ul></ul><ul><ul><li>Understanding the full relationship with a partner and impact on working capital </li></ul></ul><ul><ul><li>Providing consistency in product offerings and services, where appropriate </li></ul></ul>Exxon, Exxon/Mobil Buy/Sell position **Dollars are for demonstration purposes only and bear no resemblance to actual data Calendar Year Year 1   Year 2 Honeywell Organization Purchase Sales Sales $$$ $$$ $$$ CORPORATE $$$     $1,000,000 $$$   AUTOMATION & CONTROL $$$ $3,000,000 $$$ SPECIALTY MATERIALS $5,000,000 $$$ $$$ TRANSPORTATION SYSTEMS $$$     HONEYWELL AEROSPACE SOLUTIONS
    12. 12. Honeywell CMD Governance Approach Define the Problem Identity Data & Sources Define priorities Define Core Data Measure Current State Completeness Conformity Consistency Accuracy Duplicate Integrity Control Quality Standardize Monitor compliance Utilize common tools, services, processes Identify & share best practices & lessons learned Improve Data Integrity Ensure validity Establish baseline Re-design processes Promote reuse / best practices
    13. 13. Customer Data on Demand (CD2) Overview <ul><li>Improve service & growth: </li></ul><ul><li>Establish Honeywell view of strategic customer account </li></ul><ul><li>Provide information expediently to support business development </li></ul><ul><li>Provide information to support informed Customer visits and negotiations </li></ul><ul><li>Improve Customer Master Data Governance: </li></ul><ul><li>Facilitate transaction productivity and success </li></ul><ul><li>Complete 360  view of customer relationship management </li></ul><ul><li>SBG’s and Corporate data standards for self-governance and ownership </li></ul>ERP DW CRM D&B Customer Master & Summary Info Staging User Interface Administration User Interface 360 ° View Transaction Processing Customer Data on Demand Hub Business Unit Applications & Technologies Cleanse, match & append: DUNS, Parent Global Ultimate & SIC Code User Interface SAP BW Datamart Reporting Business Unit SAP Environment Data & Service Vendors
    14. 14. CMD Governance Council <ul><li>Vision </li></ul><ul><ul><li>Improve </li></ul></ul><ul><ul><ul><li>Establish business case for CMD quality </li></ul></ul></ul><ul><ul><ul><li>Share lessons learned, techniques and tools across organization </li></ul></ul></ul><ul><ul><ul><li>Establish and implement CMD guidelines and standards </li></ul></ul></ul><ul><ul><li>Guide, Monitor, Control </li></ul></ul><ul><ul><ul><li>Implement audit and metrics to ensure compliance </li></ul></ul></ul><ul><li>Composition </li></ul><ul><ul><li>Business process owners </li></ul></ul><ul><ul><ul><li>Order Management </li></ul></ul></ul><ul><ul><ul><li>Accounts Receivable </li></ul></ul></ul><ul><ul><li>Stakeholders </li></ul></ul><ul><ul><ul><li>Information Technology </li></ul></ul></ul><ul><ul><li>Users and creators of CMD </li></ul></ul><ul><ul><ul><li>Customer Service </li></ul></ul></ul><ul><ul><ul><li>Sales and Marketing </li></ul></ul></ul>HCS
    15. 15. Governance Council Principles and Responsibilities <ul><li>Strive for a core set of customer master data (CMD) standards and guidelines, globally common across Honeywell </li></ul><ul><li>Implement and oversee effective and efficient processes for managing and ensuring the quality of the core set of CMD </li></ul><ul><li>Build Data Quality into the stewardship processes, creating and managing data at the source </li></ul><ul><li>Set objective metrics and reasonable targets for managing data quality </li></ul><ul><li>Share lessons learned across SBGs </li></ul>Guiding Principles ground all design and recommendations
    16. 16. Customer Master Data Management Program Charter Mission: Provide common master data standardized, agreed-to, consistent format across Honeywell for Customer Master Data (CMD) records independent of source system but with an SAP focus. <ul><li>Value Proposition: </li></ul><ul><li>Data Integrity: Correct customer alignment </li></ul><ul><li>Improved productivity through common process </li></ul><ul><li>Improved reliability and validity of reporting & analytics </li></ul>
    17. 17. Customer Master Data Management Program Charter <ul><li>Scope: </li></ul><ul><li>Global Honeywell Organization </li></ul><ul><li>Information domains—core customer master data </li></ul><ul><li>Processes—customer master data creation & update supporting common processes </li></ul><ul><li>Technology—ERP (SAP, Seibel, Oracle), data cleansing tools, MDM solutions (i2, WCC, SAP…) </li></ul>Boundary Statement: This project will not attempt to “fix” legacy systems despite their continued operation through 2012, but highlight areas impacting the move to SAP for pre-load data remediation. Implementation: Due to the independent schedules of SBG SAP implementation efforts, timelines will be negotiate with each SBG.
    18. 18. Customer Master Data Management Program Charter <ul><li>Mission Enablers: </li></ul><ul><li>Enterprise Customer Master Data Governance Council </li></ul><ul><li>Clear data ownership and supportive staffing </li></ul><ul><li>Common data management and cleansing processes </li></ul><ul><li>Data harmonization & consolidation process </li></ul><ul><li>Unified ERP platform with appropriate tools </li></ul><ul><li>Goals: </li></ul><ul><li>Develop business case & priority focus </li></ul><ul><li>Establish Enterprise Customer MDM program </li></ul><ul><li>Customer MDM education & communication </li></ul><ul><li>Solution & services aligned with SAP Enterprise Architecture direction and roadmap </li></ul>
    19. 19. Enterprise Data – Requirements Customer Data is a Valued & Respected Resource Accessible Data access is independent of source or structure Available Data is available when, where & how needed Quality Completeness and accuracy are defined Consistent Consistent data definitions are used across the enterprise Auditable Managed audit trails cross the enterprise Secure Data is secure
    20. 20. Measure and Model Incorporate 6 ơ Lean Principles (The Toyota Operating System)
    21. 21. The History of Lean Thinking <ul><li>Waste triggers root cause analysis </li></ul><ul><ul><li>Determines opportunities for improvement </li></ul></ul><ul><ul><ul><li>Process redesign for improved flow </li></ul></ul></ul><ul><ul><ul><li>Load balanced work groups </li></ul></ul></ul><ul><ul><ul><li>End to end performance management </li></ul></ul></ul>Standard Work VOC/VOP Quality Cost Alignment Taguchi & Deming Lean Manufacturing <ul><li>Global Supply chain </li></ul><ul><li>Control/Ownership </li></ul><ul><li>Henry Ford - River Rouge Plant 1915 </li></ul><ul><li>Cars for income levels - </li></ul><ul><li>Paying by installments </li></ul><ul><li>Collect Requirements </li></ul><ul><li>Collect historical defect data </li></ul><ul><li>Alfred Sloan - GM Variation 1926 </li></ul><ul><li>Resource constraints WWII </li></ul><ul><li>Focus on productivity </li></ul><ul><li>Noise isolation </li></ul><ul><li>Process Robustness 1950 </li></ul><ul><li>Toyota Operating System </li></ul><ul><li>USA buy-in to teachings of Deming </li></ul><ul><li>Customer Metrics </li></ul><ul><li>Process Control Metrics </li></ul><ul><li>Functional Metrics </li></ul><ul><li>Predictive ability (SPC) </li></ul><ul><li>Scorecards </li></ul>Lean transformation requires changes to tools methodologies, standards, & procedures 1915 1980+
    22. 22. Value Stream Common Repository Driving Common Metadata Incoming SBG CMD <ul><li>Diverse Quality </li></ul><ul><li>definitions </li></ul><ul><li>Scrap: incomplete data </li></ul><ul><li>Files not </li></ul><ul><li>on time to </li></ul><ul><li>request (OTTR) </li></ul>Outgoing Reporting Process D&B file <ul><li>CMD Hierarchies </li></ul><ul><li>Industry Reports </li></ul><ul><li>Customer Visit Preparation </li></ul><ul><li>Revenue Reports </li></ul><ul><li>Send errors to SBGs </li></ul><ul><li>Load validated CMD into CD2 for reporting </li></ul>DUN & Bradstreet Separation & Cleanse <ul><li>Validate, correct, standardize , enrich with hierarchy </li></ul><ul><li>Apply confidence codes </li></ul><ul><li>ID new CMD for D&B send </li></ul><ul><li>Add established customer and revenue to CD2 for reporting </li></ul>NVA NVA VA VA NVA Supply Chain Management is Cost Management <ul><li>Speed through Standard Work </li></ul><ul><li>Re-work decreases </li></ul><ul><li>Cycle time decreases </li></ul><ul><li>Voice of the Customer </li></ul><ul><li>Predictable Quality </li></ul><ul><li>Continuous Improvement </li></ul>
    23. 23. Measure the Baseline <ul><li>Customer Master Data (CMD) Revenue Alignment </li></ul><ul><ul><li>Honeywell Revenue </li></ul></ul><ul><ul><ul><li>64% Revenue ready for CASH recovery and Growth alignment </li></ul></ul></ul><ul><ul><li>The hidden customer - one customer, many definitions </li></ul></ul><ul><ul><ul><li>No cross Honeywell standard CMD definitions, or attributes </li></ul></ul></ul><ul><ul><ul><li>No system independent identifier to enable leveraging strategic customer management </li></ul></ul></ul><ul><li>Empower the Employees </li></ul><ul><ul><li>Many source systems, little or no data ownership </li></ul></ul><ul><ul><ul><li>Data resolution owned & largely executed by CD2 team </li></ul></ul></ul><ul><ul><ul><li>Little understanding of DUNS#, D&B coverage, or the need to align revenue for recovery </li></ul></ul></ul><ul><ul><li>Information sharing void </li></ul></ul><ul><ul><ul><li>No centralized forum for data management </li></ul></ul></ul><ul><ul><ul><li>No Best Practice sharing through a stewardship network </li></ul></ul></ul>Rejects / Repair Excessive Motion Over Processing Transportation Waiting <ul><ul><li>Over production </li></ul></ul><ul><ul><li>Excessive Inventory </li></ul></ul><ul><ul><li>Defective Information </li></ul></ul><ul><ul><li>Process Failure </li></ul></ul><ul><ul><li>Wrong or Sub-optimized Decisions </li></ul></ul>
    24. 24. The 5 Lean Principles – Managing Change <ul><li>Specify value in the eyes of the customer - VoC survey for CD2 </li></ul><ul><ul><li>Engage cross functional team for Governance </li></ul></ul><ul><li>Make the processes flow – Material Flow Analysis </li></ul><ul><ul><li>Perform 5S </li></ul></ul><ul><li>Identify all the steps along the process chain </li></ul><ul><ul><li>Enable process re-design </li></ul></ul><ul><li>Make only what is pulled by the customer </li></ul><ul><ul><li>Reporting </li></ul></ul><ul><li>Strive for perfection by continually removing waste </li></ul><ul><ul><li>End to end performance management </li></ul></ul><ul><li>Empower the employees - The business owns the data </li></ul>Ownership & Responsibility Activates Problem Solving Predictable Trainable Measurable
    25. 25. Load Balancing: Leverage Business Knowledge <ul><li>Year 2 </li></ul><ul><li>SBG Data Stewards own data integrity. </li></ul><ul><li>Project Manager trains, tracks, & reviews progress </li></ul>Driving Business Data Ownership Institutionalizes Stewardship Year 1 Project Manager / Data Steward SBG N/A N/A SBG N/A N/A I’m tired
    26. 26. Lean Maturity Pyramid – Data Quality & Completeness Assess the maturity level Sort, Store, Shine, Standardize, and Sustain 5S Workplace Organization Share Information Share Standards Build Standards into the Workplace Prevent Abnormalities (Error-Proof) Stop Abnormalities (Prevent defects from moving on) Warn About Abnormalities (Build in alarms) Visual Display Visual Control SBU CMD Sold-to Transactions Feed CD2 Governance Council Kickoff Metrics Management Managed State Lean Begins with Information Sharing Data Cleansing Effort Define CORE CMD Standards Standardize DUNS# Storage Define Metrics Tracking & Trending Mechanize CORE CMD Standards, stage II Mechanize CORE CMD Standards, stage III Enterprise MDM alignment, stage I Enterprise MDM alignment, stage II Enterprise MDM alignment, stage III Mechanize CORE CMD Standards, stage I Year over Year Effort 6 5 4 3 2 1
    27. 27. 5 S Process SUSTAIN Monitor / Measure Utilize documented standards STANDARDIZE SHINE Take corrective action STORE Create a place for everything SORT Keep only the necessary to perform the task
    28. 28. Sort Establish goal and standard definitions <ul><li>Goal: Deliver continued improvement in CD2 quality </li></ul><ul><li>Establish Scope and Criteria </li></ul><ul><ul><li>High confidence D&B DUNS# match to Sold-to customer records aligned with sales dollars </li></ul></ul><ul><li>Define ownership - SBU owned and managed, CD2 team assisting </li></ul>Store Shine Standardize Sustain Sort
    29. 29. STORE <ul><li>Determine required quantities </li></ul><ul><li>Label needed items </li></ul><ul><ul><li>Maintain transaction traceability </li></ul></ul><ul><ul><li>Define D&B DUNS# as key code – system independent & family linkage </li></ul></ul><ul><li>Create a place for everything </li></ul><ul><li>Define scrap and remove from the process </li></ul><ul><li>Enrich CMD records through the D&B process </li></ul><ul><li>Develop shadow boards aligning CMD by family </li></ul>Sort Shine Standardize Sustain Store
    30. 30. Shine <ul><li>Corrective Action - Resolve CMD returned from D&B with a low confidence (LC) or non-match (NM) </li></ul><ul><ul><li>SBG created and owned </li></ul></ul><ul><ul><ul><li>Maintain audit trail – source system & customer number </li></ul></ul></ul><ul><ul><ul><li>Utilize Standard Work process </li></ul></ul></ul><ul><ul><li>Enlist resources </li></ul></ul><ul><ul><ul><li>Identify SBG Data Stewards </li></ul></ul></ul><ul><ul><li>Track & drive results in weekly status meetings </li></ul></ul><ul><li>Create standard work </li></ul><ul><ul><li>Provide consistent format </li></ul></ul><ul><ul><li>Conduct Training on documented process </li></ul></ul><ul><ul><ul><li>Provide D&B suggested low confidence match </li></ul></ul></ul><ul><ul><ul><li>Enable mechanized correction </li></ul></ul></ul>Sort Store Standardize Sustain Shine
    31. 31. Standardize Sort Store Shine Sustain Standardize <ul><li>Create CORE Customer Master Data </li></ul><ul><ul><li>Define elements and attributes </li></ul></ul><ul><ul><li>Obtain consensus across organizational lines </li></ul></ul><ul><li>Define unique identifier </li></ul><ul><ul><li>System independent </li></ul></ul><ul><ul><li>D&B DUNS# </li></ul></ul><ul><li>Install in SBG systems </li></ul><ul><ul><li>SAP FI Credit Master </li></ul></ul><ul><ul><ul><li>Credit Info.No. (KNKK table) </li></ul></ul></ul>
    32. 32. Sustain <ul><li>Measure Quality & predictability </li></ul><ul><ul><li>Definition: Percentage Honeywell yearly revenue aligned with D&B DUNS# </li></ul></ul><ul><li>Measure Re-work </li></ul><ul><ul><li>Drives Cost Containment & need for mechanized standards </li></ul></ul><ul><ul><li>Definition: Cost of employee time + opportunity cost </li></ul></ul><ul><li>Measure Scrap & On Time to Request (OTTR) </li></ul><ul><ul><li>Drives Data Completeness </li></ul></ul><ul><ul><li>Definition: Scrap (unusable record) for first pass yield per file </li></ul></ul><ul><ul><ul><li>Example: CMD record with no associated dollars, blank customer name, blank country, unusable record </li></ul></ul></ul>Sort Store Shine Standardize Sustain
    33. 33. Current and Future Focus
    34. 34. One Honeywell Focus <ul><li>Build in Quality: </li></ul><ul><li>Populate SAP FI Credit Master with DUNS# </li></ul><ul><li>Create SBG specific Roadmaps for Change </li></ul><ul><li>Roll out Informatica Data Quality Tool </li></ul><ul><li>Process Improvements: </li></ul><ul><li>Standardize data stewardship processes </li></ul><ul><li>Leverage CMD Governance Council for cross Honeywell best practices sharing, stewardship support, and decision making body </li></ul><ul><li>Leverage CD2 as D&B central </li></ul>
    35. 35. Quality and Completeness <ul><li>Key Data Requirements: </li></ul><ul><li>Customer master data from all SBGs and source systems providing a comprehensive understanding of customer entities and relationships </li></ul><ul><li>Defined data quality </li></ul><ul><li>Properly identifying business organizations enabling building corporate families & associations </li></ul><ul><li>Providing complete & consistent name, address & codification </li></ul><ul><ul><li>Name </li></ul></ul><ul><ul><li>Source identifiers (source system name and customer number) </li></ul></ul><ul><ul><li>Address lines, city, state and country </li></ul></ul><ul><ul><li>Telephone number </li></ul></ul><ul><ul><li>Honeywell organization identification </li></ul></ul>
    36. 36. Source System Data Quality <ul><li>Common Errors: Blank, special characters </li></ul><ul><ul><li>Name – “ Do Not Use, Unknown ” </li></ul></ul><ul><ul><li>Address (lines 1 and 2) - “ Accounts Payable, Directives ” </li></ul></ul><ul><ul><li>City - “ unknown, numbers, concatenated ” </li></ul></ul><ul><ul><li>State - “ unknown, numbers, concatenated ” </li></ul></ul><ul><ul><li>Country - “ unknown, numbers, concatenated ” </li></ul></ul><ul><ul><li>Postal code - “ all zeros, punctuation ” </li></ul></ul><ul><ul><li>Phone numbers - “ all zeros, punctuation ” </li></ul></ul><ul><li>Lack of naming / codification standards </li></ul><ul><ul><li>Trigger and compound errors </li></ul></ul><ul><ul><li>Store location numbers, country spelling, territories identified as states, etc. </li></ul></ul><ul><li>Captured on Monthly Scorecard </li></ul>
    37. 37. 2006 - Corporate Drives Enterprise Data Management <ul><li>Forming </li></ul><ul><li>Governance Council formed </li></ul><ul><ul><li>Storming </li></ul></ul><ul><ul><li>Corporate leads in data cleanup </li></ul></ul><ul><li>Norming </li></ul><ul><li>Data Quality tools assessment </li></ul><ul><li>Conforming </li></ul><ul><li>Agreement to seek CMD alignment </li></ul>Kickoff - Charter / SIPOC Sub-teams 86.7% achieved Informatica Data Quality Tool Baseline data gathering CMD Core field straw-man
    38. 38. Business Drives Enterprise Data Management Goal Alignment across One Honeywell Automated Control Solutions Common Standards Aerospace Data Quality Integrity Specialty Materials Strategic Management Transportation Systems Business Reporting Corporate One Honeywell Honeywell Credit Services Improve Working Capital
    39. 39. Customer Data Integration <ul><li>Standard financial code names </li></ul><ul><li>But definitions are not standardized </li></ul><ul><ul><li>Data maintenance at the individual line of business level </li></ul></ul><ul><ul><li>But no central repository </li></ul></ul><ul><li>No Customer Relationship Management controls </li></ul><ul><li>Limited customer interaction awareness </li></ul><ul><li>Mergers and Acquisitions create additional complexity </li></ul><ul><li>Acquired competitors continue competing </li></ul>Customer Knowledge Sharing Done by “Talking” High Labor Costs / Low Return Constrained Growth <ul><li>CD2 is a central repository for Customer Data Integration </li></ul><ul><ul><li>Consistent code definitions </li></ul></ul><ul><ul><li>Report requests OTTR 1 or 2 days </li></ul></ul><ul><li>CD2 enables view into customers across Honeywell </li></ul><ul><ul><li>Insight into the customers of other Honeywell businesses </li></ul></ul><ul><ul><li>M anaged CRM </li></ul></ul><ul><li>CD2 enables view into industry codes aligned to Honeywell customers </li></ul><ul><ul><li>Alignment of customer by business through SIC codes (industry type) </li></ul></ul><ul><ul><li>Enabled competition </li></ul></ul>Managed and Enabled Customer Knowledge Sharing
    40. 40. Positive Feedback but What have you Done for me Lately? It helps to see in total what Honeywell means to the customer The tool is really valuable! CD2 information is critical because each business unit is on a separate system. CD2 helps identify our potential leverage and risks, particularly for big contracts It helps to understand our risk exposure The visibility that CD2 provides really changes the game! The people that use it frequently should think about the 5 things it has caused them to do differently and start tracking it It used to take me 1-2 weeks to pull the information together that I can now get from CD2 in 24 hours! CD2 saves a massive amount of time and improves the quality of the data We’ve had One Honeywell chats forever, until you use these reports you don’t start thinking outside of your business unit. CD2 is fostering collaboration across Honeywell. Source: IBM CD2 Study
    41. 41. Data Governance Reality Check <ul><li>Don’t think that a tool will solve all your problems </li></ul><ul><li>Don’t forget that Data Governance is required & on-going </li></ul><ul><li>Do remember that life is made up of baby steps </li></ul><ul><li>Do pick your battles – be flexible </li></ul><ul><li>Don’t ignore the significance of data stewardship </li></ul><ul><li>Don’t over do it or do it at the wrong time </li></ul><ul><li>Don’t think it will be easy </li></ul>
    42. 42. Questions?