bad customer data?

26
Copyright © 2007 Accenture All Rights Reserved. Accenture, its logo, and High Performance Delivered are trademarks of Accenture. What’s the price of bad customer data ? Breakfast Session 15 September 2009 Hotel Sofitel Brussels

Upload: datavaluetalk

Post on 27-Jan-2015

117 views

Category:

Business


1 download

DESCRIPTION

 

TRANSCRIPT

Page 1: Bad customer data?

Copyright © 2007 Accenture All Rights Reserved. Accenture, its logo, and High Performance Delivered are trademarks of Accenture.

What’s the price of bad customer data ?

Breakfast Session

15 September 2009

Hotel Sofitel Brussels

Page 2: Bad customer data?

Copyright © 2007 Accenture All Rights Reserved. – for internal use onlyDM&A External Overview Deck Slide 2 v5.0 April, 2007

Table of Contents

Client Challenges

How we respond

Bad customer data ?

Page 3: Bad customer data?

Copyright © 2007 Accenture All Rights Reserved. – for internal use onlyDM&A External Overview Deck Slide 3 v5.0 April, 2007

« I get two different results from two different systems and, guess what, they are both wrong. »

« Our business strategy is for us to be an information-driven company and to justify our decisions with hard data but that data is usually unclear and inconsistent when I receive it. »

« I receive numerous reports every day but they all use different terminology and data formats – what does this all mean? »

« One of the administrative people had a report on their desk with our hiring and firing numbers from last month. They said they got it from the company portal and that there is all sorts of “nasty stuff” out there. This information is supposed to be confidential – why were they allowed to get it? »

What clients tell us (1/3)

Client Challenges

Page 4: Bad customer data?

Copyright © 2007 Accenture All Rights Reserved. – for internal use onlyDM&A External Overview Deck Slide 4 v5.0 April, 2007

What clients tell us (2/3)

« I was told that we should have standards for our data models and data names so I asked for a copy. What I received was 5 years old and didn’t even include the company we merged with in 2003. »

« I am trying to determine why we have different formulas for Inventory in different systems.Doesn’t anyone own or have responsibility for this data throughout the company? »

« I just reviewed a Data Model of our business to prepare for an acquisition. It looked very nice but it used difficult terminology, a very old business model and had nothing to do with our current organization and strategy. »

« I need to do a study that looks at our sales for the last 5 years. I was told that the data is all archived but no one knows where it is or how to retrieve it. »

Client Challenges

Page 5: Bad customer data?

Copyright © 2007 Accenture All Rights Reserved. – for internal use onlyDM&A External Overview Deck Slide 5 v5.0 April, 2007

What clients tell us (3/3)

« I just got the budget request from the IT department and they want to spend $25 million dollars in 2006 to double our storage capacity because that is how much data we are generating each year. Can’t we store some of this data somewhere else? There must be a cheaper alternative. »

« We did a great Data Cleanup effort last year but the data is becoming corrupt again. Shouldn’t that effort made sure that errors don’t creep in again? »

« We are being audited by the SEC and they want to see how we calculate our asset data. There are values here that don’t quite make sense – I know who entered them originally but who made all the changes to them? »

Client Challenges

Page 6: Bad customer data?

Copyright © 2007 Accenture All Rights Reserved. – for internal use onlyDM&A External Overview Deck Slide 6 v5.0 April, 2007

The threats (1/2)

« Data Quality problems cost U.S. businesses more than $600 billion a year. » (TDWI)

« NASA lost its $125M Mars Climate Orbiter because one group of engineers used kilograms and meters, while another used pounds and feet. The error caused the spacecraft to fly too close to the Martian surface where it either burned up or broke up as it swung around the planet. »

« Rogue trader lost $691 Million due to lack of data governance. »

« Average costs per data mart are $1.5M to $2.0M and a data mart consolidation initiative can reduce costs by 50%. » (META Group)

« Master data problems leads to $250M law suit of a large investment bank. »

Client Challenges

Page 7: Bad customer data?

Copyright © 2007 Accenture All Rights Reserved. – for internal use onlyDM&A External Overview Deck Slide 7 v5.0 April, 2007

The threats (2/2)

« Overcharging customers due to master data issues lands a large utility in a $1B law suit. »

« For the U.S. grocery industry, up to 1 percent of net revenue lost, and one in 2,000 of sales lost because the item was out of stock, were attributable to bad master data. » (Gartner)

« Retailers and manufacturers can reduce their current supply chain costs by 1 to 3 percent depending upon their current state. » (GCI)

« Inaccurate and time consuming product information exchanges between CPG trading partners caused an estimated $25M - $50M in extra costs across the supply chain. » (AT Kearney Study)

« 30% of all operational errors are due to poor information quality. » (Reuters)

Client Challenges

Page 8: Bad customer data?

Copyright © 2007 Accenture All Rights Reserved. – for internal use onlyDM&A External Overview Deck Slide 8 v5.0 April, 2007

Direct & Indirect Impacts of poor Data Quality

Hidden in business processes, data maintenance and integration costs.

Typical Problem Areas:Missing Data Ownership and Accountability

• Data owner is not clear• Data owner maintains data quality for users in other

organizations• Data owners tend to treat data quality as low priority work

Lack of Data and Business Process Integration• Data not modeled to reflect business processes.

Inconsistent Data Definition and Standardization• Different names are used for the same data; • Same data name refers to different definitions in different

organizations.

Ineffective Data Relationship and Classification • Data relations are not appropriately defined or are out of

date.

Invalid Data Entry• Data is mistyped (or judgmental error) into the system.• The data creator often does not know how that data will be

used later.

Impacts:Extra Time to Reconcile Data

• Maintenance of extra, manual cleansing rules

Loss of credibility in systems– Proliferation of separate, off-line data sources

Extra Costs– Increased costs related to verifying data

Delays in project deployment– Over budget and delayed projects due to time-

intensive data cleansing

Compliance Issues– Inability to adhere to local compliance standards

Suboptimal Decision Making – Corporate strategy and decisions negatively

affected by data quality issues

Lost Revenue– Lost business opportunities due to inaccurate

data quality

– Customer attrition looking for better service elsewhere

Client Challenges

Page 9: Bad customer data?

Copyright © 2007 Accenture All Rights Reserved. – for internal use onlyDM&A External Overview Deck Slide 9 v5.0 April, 2007

The bottom line

Our clients face these challenges every day and they find them very difficult to solve! And they have to meet legal requirements and regulations (example: Sarbanes-Oxley/SOX)

They need to start managing their data now!

Client Challenges

Hard facts and figures are essential to making decisions in a high performance company. Managing by whims and instincts is becoming a path to extinction.  Data is quickly becoming the lifeblood of an organization and a valuable enterprise asset.  In the past, the focus has been on the use of the data but very little has been done to manage its quality and integrity.

Page 10: Bad customer data?

Copyright © 2007 Accenture All Rights Reserved. – for internal use onlyDM&A External Overview Deck Slide 10 v5.0 April, 2007

Table of Contents

Client Challenges

How we respond

Bad customer data ?

Page 11: Bad customer data?

Copyright © 2007 Accenture All Rights Reserved. – for internal use onlyDM&A External Overview Deck Slide 11 v5.0 April, 2007

What is Data Management & Architecture ?

Accenture’s Data Management and Architecture (DM&A) practice addresses how an organization manages its data.  The fundamental focus of DM&A is ensuring that the data that underlies an organization is available, accurate, complete, and secure.  DM&A is not just the technology to manage data.  Effective data management includes Processes, People and Technology.

How we respond

Accenture Information Management ServicesHolistic Framework

Business IntelligenceMeasure, Analyze, Optimize

• BI Diagnostic • Custom Data Warehousing • Large Data Warehousing • ERP Data Warehousing • Advanced Business Intelligence Delivery • Business Intelligence Sourcing

Portals & Content ManagementDocument Lifecycle

• Document Management • Imaging • Web Content Management • Records Management • Business Process Management• Collaboration • Enterprise Search

Data Management& ArchitectureStructured Approach

• Data Governance• Data Structure• Data Architecture• Master Data & Metadata• Data Quality• Data Security

Data Management & Architecture is part of Accenture Information Management Services

Page 12: Bad customer data?

Copyright © 2007 Accenture All Rights Reserved. – for internal use onlyDM&A External Overview Deck Slide 12 v5.0 April, 2007

DataGovernance

DataGovernance

DataStructure

DataStructure

Data Architecture

Data Architecture

Master Data &Metadata

Master Data &Metadata

Data Quality

Data Quality

Data Security

Data Security

DM&ACapabilities

DM&ACapabilities

DataCreation

DataStorage

DataMovement

DataUsage

DataRetirement

•Data Ownership

•Data Stewardship

•Data Policies

•Data Standards

•Data Ownership

•Data Stewardship

•Data Policies

•Data Standards

•Data Modeling

•Data Taxonomy

•Data Modeling

•Data Taxonomy

•Data Migration

•Data Storage

•Data Access

•Data Archiving

•Data Retirement

•Data Migration

•Data Storage

•Data Access

•Data Archiving

•Data Retirement

•Master Data Management

•Reference Data Management

•Metadata Management

•Master Data Management

•Reference Data Management

•Metadata Management

•Data Profiling

•Data Cleansing

•Data Monitoring

•Data Compliance

•Data Traceability

•Data Profiling

•Data Cleansing

•Data Monitoring

•Data Compliance

•Data Traceability

•Data Privacy

•Data Retention

•Data Privacy

•Data Retention

DM&A Capabilities Overview

How we respond

Page 13: Bad customer data?

Copyright © 2007 Accenture All Rights Reserved. – for internal use onlyDM&A External Overview Deck Slide 13 v5.0 April, 2007

DM&A Capability Definitions

Data Governance

Data Governance is how an enterprise oversees its data assets. Governance includes the rules, policies, procedures, roles and responsibilities that guide overall management of an enterprise’s data. Governance provides the guidance to ensure that data is accurate & consistent, complete, available, and secure.

Data Structure

Data Structure is how data is organized in a specific enterprise. The Data Structure includes multiple levels of an enterprise ranging from overall corporate data models down to the level of an individual system.

Data Architecture

Data Architecture is the processes, systems and human organizations required to store, access, move and organize data.

Master Data & Metadata

Master Data is the fundamental business data in an enterprise. Master Data is typically long-lived and used across multiple applications. Master data can also be considered the language of doing business – the business objects and classifications that describe overall business information. Well-managed Master Data typically consists of hundreds of categories including customers, products, suppliers, key performance indicators, etc. Metadata is structured information about data or, simply, “data about data”.

Data Quality Data Quality is the ability of data to satisfy the stated business, system, and technical requirements of an organization. Data Quality is typically measure in terms of completeness, timeliness, accuracy, consistency, relevance, and integrity.

Data Security

Data Security is the processes and technology to protect data from unauthorized access, viewing, modification or deletion whether the intent is accidental, intentional, or malicious. Data Security initiatives should be in concert with enterprise-wide Security efforts including physical security, network security and technology security.

How we respond

Page 14: Bad customer data?

Copyright © 2007 Accenture All Rights Reserved. – for internal use onlyDM&A External Overview Deck Slide 14 v5.0 April, 2007

DM&A CapabilitiesDM&A Capabilities

The DM&A Capabilities have a Process, People and Technology component

Data Governance

Data Governance

DataStructure

DataStructure

DataArchitecture

DataArchitecture

Master Data& Metadata

Master Data& Metadata

DataQuality

DataQuality

DataSecurity

DataSecurity

Pro

cess

Peo

ple

Tec

hn

olo

gy

• Data Policies• Data Standards• Business Data

Ownership• Data Workflow

• Data Taxonomy• Logical Data

Models• Business Process

Flows

• Data Sizing, Storage & Movement Architecture

• Data Retention & Deletion Policies

• Phys Data Models

• Data Definitions• Master Data• Metadata• Reference Data

• Data Quality Rules & Policies

• Data Cleansing Standards

• Compliance Rules

• Compliance & Security Policies

• Local, National & International Laws

• Pre-test Anonymization

• Data Stewards• Business Data

Owners• Data Czar or Mgt.

Committee

• Enterprise Data Architects

• Data Modelers

• Solution Architects• Storage/

Technical Architects

• DBAs

• Business Data Administration

• Data Stewards• Data Owners

• Data Administration

• Data Quality Services Team

• Data Governance• DBAs

• Corporate Security• Auditors• Compliance Dept.

• Data Rules Library• Automated

Notifications (Workflow)

• Data Modeling Tools

• Design/CASE Tools

• Archiving Tools• Storage

Management & Hardware

• Technical Architecture

• Master Data Mgt. Tools

• Reference Data Architecture

• Metadata Repository

• Data Profiling, Quality & Monitoring Tools

• ETL Tools• Audit Reports

• Security Software• Access Rights

Management• Data Audit Trails• Data

Anonymization

How we respond

Page 15: Bad customer data?

Copyright © 2007 Accenture All Rights Reserved. – for internal use onlyDM&A External Overview Deck Slide 15 v5.0 April, 2007

Our Value Proposition

15

Improves the enterprise core data quality (i.e. quality of customers, products, suppliers, etc. data). Improves the decision quality by securing reliable, high quality master data “just in time”. Improves the availability of key data – speed of access, data timeliness, common (user) support. Improves all management activities through enhanced abilities to access consolidated data across

the enterprise and more quickly integrate new data (new customers, new products, etc.). Eliminates/prevents redundant & non-coordinated data quality activities within the company. Enables development projects to deliver consistent high quality results faster and cheaper.

Reduces cost of manual data reconciliation & alignment efforts, error fixing, etc. Reduces the data redundancy cost by consolidating & eliminating duplicate masters. Reduces reporting costs as a result of continuously consistent and updated data. Reduces application development & maintenance costs, by having clear data quality standards. Reduces redundant SW/HW purchase & license costs associated with disparate systems

Enables 360º view of the enterprise and corporate performance management improvement. Provides competitive advantage by enabling customer behavior insight & predictive modeling. Enables process automation and faster data exchange also with business partners. Improves the forecast management through more effective logistics and inventory control. Increases the accuracy and the return of marketing campaigns. Enables effective customer retention/churn management by providing integrated master data. Improves the customer service quality by enabling higher responsiveness to customer needs. Offers a robust solution able to support business change & growth in the right pace & price. Improve “profitability” by optimizing cost to serve for both low cost margin customer & high-value

customer segments Provides optimized margins by category and product consistently Improves “time-to-market” efficiency by providing more accurate master data in a timely manner.

Revenue

Quality

Cost

ValueProposition

Many factors support a strong business case for effective Data Quality Management

How we respond

Page 16: Bad customer data?

Copyright © 2007 Accenture All Rights Reserved. – for internal use onlyDM&A External Overview Deck Slide 16 v5.0 April, 2007

« I get two different results from two different systems and, guess what, they are both wrong. »

« Our business strategy is for us to be an information-driven company and to justify our decisions with hard data but that data is usually unclear and inconsistent when I receive it. »

« I receive numerous reports every day but they all use different terminology and data formats – what does this all mean? »

« I call them Products, other people call them Parts, one system calls them SKUs – and our customers call them by their catalog names and numbers – are they all the same thing? »

« One of the administrative people had a report on their desk with our hiring and firing numbers from last month. They said they got it from the company portal and that there is all sorts of “nasty stuff” out there. This information is supposed to be confidential – why were they allowed to get it? »

What clients tell us (1/3)

Data Governance Data Quality

Data Governance Data Quality

Master Data & Metadata

Data Security

Data Structure

Data Structure

Master Data & Metadata

How we respond

Page 17: Bad customer data?

Copyright © 2007 Accenture All Rights Reserved. – for internal use onlyDM&A External Overview Deck Slide 17 v5.0 April, 2007

What clients tell us (2/3)

« I was told that we should have standards for our data models and data names so I asked for a copy. What I received was 5 years old and didn’t even include the company we merged with in 2003. »

« I am trying to determine why we have different formulas for Inventory in different systems.Doesn’t anyone own or have responsibility for this data throughout the company? »

« I just reviewed a Data Model of our business to prepare for an acquisition. It looked very nice but it used indecipherable terminology, a very old business model and had nothing to do with our current organization and strategy. »

« I need to do a study that looks at our sales for the last 5 years. I was told that the data is all archived but no one knows where it is or how to retrieve it. »

Data Structure

Data Governance Master Data & Metadata

Data Governance Data Structure

Data Architecture Data Governance

How we respond

Page 18: Bad customer data?

Copyright © 2007 Accenture All Rights Reserved. – for internal use onlyDM&A External Overview Deck Slide 18 v5.0 April, 2007

What clients tell us (3/3)

« I just got the budget request from the IT department and they want to spend $25 million dollars in 2006 to double our storage capacity because that is how much data we are generating each year. Can’t we store some of this data somewhere else? There must be a cheaper alternative. »

« We did a great Data Cleanup effort last year but the data is becoming corrupt again. Shouldn’t that effort made sure that errors don’t creep in again? »

« We are being audited by the SEC and they want to see how we calculate our asset data. There are values here that don’t quite make sense – I know who entered them originally but who made all the changes to them? »

Data Architecture

Data Quality

Data Quality

Data Governance

How we respond

Page 19: Bad customer data?

Copyright © 2007 Accenture All Rights Reserved. – for internal use onlyDM&A External Overview Deck Slide 19 v5.0 April, 2007

The threats (1/2)

« Data Quality problems cost U.S. businesses more than $600 billion a year. » (TDWI)

« NASA lost its $125M Mars Climate Orbiter because one group of engineers used kilograms and meters, while another used pounds and feet. The error caused the spacecraft to fly too close to the Martian surface where it either burned up or broke up as it swung around the planet. »

« Rogue trader lost $691 Million due to lack of data governance. »

« Average costs per data mart are $1.5M to $2.0M and a data mart consolidation initiative can reduce costs by 50%. » (META Group)

« Master data problems leads to $250M law suit of a large investment bank. »

Data Quality

Data Governance

Data Governance

Data Architecture

Master Data & Metadata

How we respond

Page 20: Bad customer data?

Copyright © 2007 Accenture All Rights Reserved. – for internal use onlyDM&A External Overview Deck Slide 20 v5.0 April, 2007

The threats (2/2)

« Overcharging customers due to master data issues lands a large utility in a $1B law suit. »

« For the U.S. grocery industry, up to 1 percent of net revenue lost, and one in 2,000 of sales lost because the item was out of stock, were attributable to bad master data. » (Gartner)

« Retailers and manufacturers can reduce their current supply chain costs by 1 to 3 percent depending upon their current state. » (GCI)

« Inaccurate and time consuming product information exchanges between CPG trading partners caused an estimated $25M - $50M in extra costs across the supply chain. » (AT Kearney Study)

« 30% of all operational errors are due to poor information quality. » (Reuters)

Master Data & Metadata

Master Data & Metadata

Master Data & Metadata

Master Data & Metadata

Data Quality

How we respond

Page 21: Bad customer data?

Copyright © 2007 Accenture All Rights Reserved. – for internal use onlyDM&A External Overview Deck Slide 21 v5.0 April, 2007

Data Governance Definitions

Data Governance Data Governance is how an enterprise manages its data assets. Governance includes the rules, policies, procedures, roles and responsibilities that guide overall management of an enterprise’s data. Governance provides the guidance to ensure that data is accurate & consistent, complete, available, and secure.

Data Stewardship

Data Stewardship is the accountability for the management of data assets. Data Stewards do not own the data; instead they are the caretakers of the enterprise data assets. The Data Stewards ensure the quality, accuracy and security of the data.

Data Ownership Data Ownership is the responsibility for the creation of the data, and the enforcement of enterprise business rules. Data Owners usually refers to the business owners of Master/Business Data.

Data Policies Data Policies are the high-level and/or detailed rules and procedures that an enterprise utilizes to manage its data assets. Data Policies might include adherence of data to business rules, enforcing authentication and access rights to data, compliance with laws and regulations, and protection of data assets.

Data Standards Data Standards are the precise criteria, specifications, and rules for the definition, creation, storage and usage of data within an organization. Data Standards include basic items like naming conventions, number of characters, and value ranges. Data Standards may also dictate specific quality measures, retention rules, and backup frequency.

DM&A Definitions

Page 22: Bad customer data?

Copyright © 2007 Accenture All Rights Reserved. – for internal use onlyDM&A External Overview Deck Slide 22 v5.0 April, 2007

Data Structure Definitions

Data Structure Data Structure is how data is organized in a specific enterprise. The Data Structure includes multiple levels of an enterprise ranging from overall corporate data models down to the level of an individual system.

Data Modeling Data Modeling is the creation of Data Models that capture business requirements and present them in a structured way. Data Modeling enables an enterprise to communicate its data entities, attributes, and relationships, support system development and maintenance projects, and underlay most enterprise data initiatives. Data Modeling is generally done at both the Enterprise and Business Unit levels.

Data Taxonomy Data Taxonomy is the classification of data within an enterprise. An alternate definition is that Data Taxonomy is the terminology used within an enterprise when looking at its data. Data Taxonomy applies to both structured and unstructured data. The Data Taxonomy could be the product catalog including components and part numbers (structured data) and it could be the classification or grouping of documents (unstructured data).

DM&A Definitions

Page 23: Bad customer data?

Copyright © 2007 Accenture All Rights Reserved. – for internal use onlyDM&A External Overview Deck Slide 23 v5.0 April, 2007

Data Architecture Definitions

Data Architecture Data Architecture is the processes, systems and human organizations required to store, access, move and organize data.

Data Migration Data Migration is the automated movement or migration of enterprise data such as from a transactional data base to a specific data store. Data Migration is sometimes defined to also include the migration of data from transactional systems to data archives.

Data Storage Data Storage is the physical storage of data on an enterprise’s (or outsourcer’s) hardware.

Data Access Data Access is the various mechanism used to view, add, change, or delete data. Data Access includes transactional, analytical, and archival systems.

Data Archiving Data Archiving is the storage of an enterprise’s data on a secondary storage medium. Data is archived to minimize the cost of online data storage. Depending on the archiving process and technology, archived data can be accessed in near real-time or only after an extended period.

Data Retirement Data Retirement is the removal of data from Data Storage. Data Retirement is not simply the deletion of data. Data Retirement is a process that may include long-term retention of key information and historical data for future analysis or reuse. Data Retirement must adhere to Local and National laws especially as it relates to Data Privacy. In some circumstances, data may be unretired such as a transaction with a former customer.

DM&A Definitions

Page 24: Bad customer data?

Copyright © 2007 Accenture All Rights Reserved. – for internal use onlyDM&A External Overview Deck Slide 24 v5.0 April, 2007

Master & Meta Data Definitions

Master Data Master Data is the fundamental business data in an enterprise. Master Data is typically long-lived and used across multiple applications. Master data can also be considered the language of doing business – the business objects and classifications that describe overall business information. Well-managed Master Data typically consists of hundreds of categories including customers, products, suppliers, key performance indicators, etc.

Reference Data

DM&A considers Reference Data to be a form of Master Data. Reference Data can sometimes be defined as code/decode data or external coded information.

Metadata Metadata is structured information about data or, simply, “data about data”.

Master Data Management

Master Data Management (MDM) is the collection of processes and technology that ensures that Master Data is coordinated across the enterprise. MDM provides a unified Master Data service that provides accurate, consistent and complete Master Data across the enterprise and to business partners.

Reference Data Management

DM&A Considers Reference Data Management to be synonymous with Master Data Management.

Metadata Management

Metadata Management is the tools and processes used to manage Metadata. Typically there are three types of Metadata that is managed: 1) Business metadata; 2) Technical metadata; 3) Operational metadata. Metadata Management is used to define, create, update, migrate, and disseminate metadata throughout an enterprise.

DM&A Definitions

Page 25: Bad customer data?

Copyright © 2007 Accenture All Rights Reserved. – for internal use onlyDM&A External Overview Deck Slide 25 v5.0 April, 2007

Data Quality Definitions

Data Quality Data Quality is the ability of data to satisfy the stated business, system, and technical requirements of an organization. Data Quality is typically measured in terms of completeness, timeliness, accuracy, consistency, relevance, and integrity.

Data Profiling Data Profiling is the systematic analysis of data to gather actionable and measurable information about its quality. Information gathered from Data Profiling activities is used to assess the overall health of the data and determine the direction of Data Quality initiatives.

Data Cleansing Data Cleansing is the process of detecting and correcting erroneous data and data anomalies both within and across systems. Data Cleansing can take place in both real-time as data is entered or afterwards as part of a Data Cleansing initiative.

Data Monitoring Data Monitoring is the automated and/or manual processes used to continuously evaluate the condition of an enterprise’s data. Information obtained from Data Monitoring activities is used to plan and focus data improvement initiatives.

Data Compliance Data Compliance is the ongoing processes to ensure adherence of data to both enterprise business rules, and, especially, to legal and regulatory requirements. Data Compliance includes 4 items: Controls, Audit, Regulatory Compliance & Legal Compliance.

Data Traceability Data Traceability is the tracking of the lifecycle of data to determine and demonstrate all changes and access to the data. Data Traceability helps an enterprise demonstrate transparency, compliance and adherence to regulation. Data Traceability along with Data Compliance can be considered part of a Data Audit process.

DM&A Definitions

Page 26: Bad customer data?

Copyright © 2007 Accenture All Rights Reserved. – for internal use onlyDM&A External Overview Deck Slide 26 v5.0 April, 2007

Data Security Definitions

Data Security Data Security is the processes and technology to protect data from unauthorized access, viewing, modification or deletion whether the intent is accidental, intentional, or malicious. Data Security initiatives should be in concert with enterprise-wide Security efforts including physical security, network security and technology security.

Data Privacy Data Privacy is the legal right and expectation of confidentiality in the collection and sharing of data. Data Privacy is an evolving area with numerous local and national laws. Data Privacy is also known as Data Protection.

Data Retention Data Retention defines the policies and rules that an enterprise utilizes to keep data online, in archives, and in backups. Data is generally retained for regulatory and legal reasons as well as for historical analysis or Business Intelligence.

DM&A Definitions