Data Flux
Download as PPT, PDF2 likes1,547 views
The document discusses the journey organizations take to establish trusted data through effective data management. It outlines key barriers such as a disconnect between business and IT needs as well as a lack of data ownership and governance. The document promotes establishing repeatable data processes through a single data management solution that provides data quality, integration and master data management capabilities. This helps improve business user productivity, reduce costs and risks, and support data-driven decisions.
Data Flux
- 1. “ The Journey to Trusted Data” Saul Cunningham DataFlux ANZ General Manager 10 March 2011
- 2. Welcome Saul Cunningham Managing Director, DataFlux ANZ
- 3. Where are you on your data journey?
- 4. Planning is the Key
- 5. The Evolution of Data Awareness
- 6. The Current State of Data Management The top four potential barriers to coordinating data management initiatives
- 8. Understanding the Gap IT Drivers for Data Management Back Office Applications IT Infrastructure Operational Efficiency Proven Technologies Methodical in Approach Business Drivers for Data Management Front Office Applications Customer Oriented Revenue Generation Leading Edge Technologies Process Oriented
- 9. Closing the Gap It ’ s a question of ownership Business owns the processes IT owns the systems It ’ s a question of sponsorship Organisations can place a value on almost all assets (buildings, machinery, employees, bandwidth) Data is, at its core, viewed by the business as a by-product of IT assets It’s a question of technology adoption Traditional data management capabilities are lacking Right technology at the right time
- 10. The Data Governance Maturity Model Sales Force Automation Database Marketing IT-driven projects Duplicate, inconsistent data Inability to adapt to business changes Data Warehouse ERP CRM Line of business influences IT projects Little cross-functional collaboration High cost to maintain multiple applications IT and business groups collaborate Enterprise view of certain domains Data is a corporate asset Customer MDM Product MDM Materials MDM Employee MDM Asset MDM Business requirements drive IT projects Repeatable, automated business processes Personalized customer relationships and optimized operations MDM Business Process Automation
- 12. Your Data. Your Business. One Solution. DataFlux enables business agility and IT efficiency by providing innovative data management technology and services that transform data into a strategic asset . Our Mission
- 13. Recognised as a leading provider of data quality, data integration and MDM solutions Over 2300 customers worldwide Been in the leadership position within the Gartner DQ MQ since 2006 Single home grown platform providing DQ, DI and MDM capabilities Wholly owned subsidiary of SAS DataFlux - Proven Market Leader in Data Management
- 14. DataFlux – one solution with broad application across your business “ It’s like having a “Swiss Army knife” suite of tools to characterise, clean, integrate and monitor the quality of BP’s data.” Ken Dunn (BP Data Architecture Manager)
- 15. Scenario 1: Business Reporting The “classic” use of Data Quality Access and integrate data in batch & real-time for analytics Apply Data Quality business rules to ensure trusted data for reporting - improve User confidence in the data Business Intelligence Legacy Systems Application Systems Data Mart DW / DM Data Warehouse Batch DQ Real-time DQ DataFlux DQ Platform
- 16. Scenario 2: Business Process Improvement Improve data quality at the “Point of data entry” into your Enterprise Applications Eliminates duplicate data entering the system Data quality management over the life of an ERP/CRM system Ensuring quality information at User interface Enterprise Applications Business Users DataFlux Quality Firewall DataFlux DQ Platform
- 17. Scenario 3: Reduce Risk in Data Migrations Legacy Systems ERP/ CRM New Enterprise Application Migrate cleansed and standardised legacy application data into new or upgraded Enterprise Application Reduce risk and ensure timely delivery of application go-live Monitor DQ issues during Data Migration process to increase confidence for key stakeholders Data Migrations Legacy Systems DataFlux DQ Platform
- 18. Scenario 4: Data Governance process Meet compliance requirements with ability to trace and audit data Consolidate enterprise data to establish a single version of customer, product or employee Data Governance Legacy Systems MDM Application Systems Enterprise Apps Business Users DataFlux DQ Platform
- 19. Questions?
- 20. Improve Business User productivity with ease of use and process reuse and sharing for collaboration Helps Users make decisions with confidence using trusted information Flexibility to scale from small pilot projects to enterprise-wide deployments Reduce costs and Total Cost of Ownership with a single easy-to-use product solution Flexibility to support multiple data types and emerging technologies such as SOA and Web Services
- 21. Conceptual View of Master Data Management SFA ERP Data Warehouse Call Center Apex Equipment Pty Ltd | Newcastle Apex | Newcastle, New South Wales Apex Construction | Newcastle NSW Apex Equip & Const | Newcastle NSW Apex Equipment & Construction, Pty Ltd | Newcastle NSW 2300 Batch | Real-Time Batch | Real-Time Batch | Real-Time Batch | Real-Time Data Integration Data Quality Data Model Business Services Stewardship Console Business User Interface Data Governance Identity Management Reporting Data Profiling Metadata Discovery Business Rule Definition Entity Definition
Editor's Notes
- #3: My name is SC I run Dataflux ANZ We are a wholly owned subsiduarary of SAS We specialise in Data Management and are the leaders in Data Quality according to Gartner We provide DI and MDM solutions as well as DQ Our software sits inside many SAS products like EDI server and DI server etc Possibly you own it without realising it. Possibly you use it without knowing its full potential. Drop by our stand and get to know us. Today I only have 25 mins before I get kicked off I won’t have time to go down into the weeds What we will do is cover What Why and How of MDM.
- #11: Speaking of Data Stewards and Data Governance its important to understand that MDM is an evolutionary process You don’t just go there in a day Organisations range from being undisciplined through to governed Indeed right now in our experience over 80% of organisations would be in the undisciplined or reactive phases. In these phases they are really IT lead with departmentally funded projects adding to the siloed nature of their data They tend to be driven by external events like compliance reporting or the implementation of a new major CRM system There exists a chasm between the reactive and proactive phases that has nothing to do with technology This chasm can never be crossed until multiple business units together with IT collaborate around business process that spam the enterprise. These business processes will need data that is accurate and current Often the business process in question might be customer focussed – say order-to-cash and so this drives the adoption of domain specific customer MDM Other times the process might be procure-to-pay and so drive supplier and materials MDD As time goes by and this focus moves beyond individual business processes to a complete enterprise view multi-domain MDM and business process automation It is here that we see the biggest paybacks with lowered risk in things like customer churn and compliance Key element though is that this is all about getting buy in from the different LOB’s and IT to work towards our common goal of our MDM charter
- #22: So lets have a look at how it works at a conceptual level Here we see a customer MDM example – Apex In the various systems – Call Centre, Sales Force Automation, Enterprise Resource Planning etc various versions of Apex exist They may have different names, different addresses, ABN numbers, contact information etc The central MDM hub holds what is often called the “Golden record”. It has a strict definition. Now at this point we could talk about different models of MDM. All I am going to say is The hub can actually store this information itself Or the hub can hold references to which system holds the “golden name”, the “golden address” etc Various combinations of these approaches exist and various synchronisation schemes exist For the purpose of this presentation it is enough for us to think about this at a conceptual level and understand one key thing. The apps are still responsible for the owning and managing the transaction data i.e the Call Centre system will still be responsible for recording the customer interactions The SFA app be responsible sales The ERP for interacting with suppliers etc However they will no longer own the Master Data Why? What is the reason for this shocking truth? Well if they each do that still we will still have multiple version of the truth At its heart MDM is about decoupling the applications from the common, business wide master data and managing it as an application independent asset This can be heard to hear for some but it is the only way to fix the problem of “too many watches” As you can imagine the biggest hurdle is not technology but political. In fact the technology is straight forward The tools we need all exist and are shown on the slide Data profiling and discovery – to help us find out what exists in the source systems and what state of health its in Metadata tools – to help us define definitions Data Integration tools to interact with the source systems and merge information together Data Quality tools to cleans, deduplicate the data down to a single record The ability to render the data as a business service for consumption by the source systems and my users