1

<Insert Picture Here>

Oracle Enterprise Data Quality for Siebel

March 2013

2

Architecture

3

Architecture

• Uses Siebel’s Universal DQ Connector interface

• EDQ Web Services are used for standardization and matching, and EDQ Jobs are used for batch/incremental batch duplicate identification

• A shared database is used for batch duplicate identification jobs (only)

Siebel Server

EDQ Server

Shared Staging

Database

Universal DQ Connector interfaceEDQ Siebel Connector

Web Services Jobs

Customer Data Services Pack

4

Deployment example 1 – Single EDQ server

Siebel Server

EDQ Server

Shared Staging Database (Oracle /

PostgreSQL)

Universal DQ Connector interface

EDQ Siebel Connector Web Services

Jobs

EDQ-CDS Project

EDQ-CDS Initialize Project

Real-time requests

Batch jobs

Initialization

Shipped CDS reference data Prepared CDS

Reference Data

5

Deployment example 2 – Multiple EDQ servers

Siebel Server

EDQ Server 1

Universal DQ Connector interface

EDQ Siebel Connector Web Services

Jobs

EDQ-CDS Project

EDQ-CDS Initialize Project

Real-time requests (load balanced)

Batch jobs

Initialization

Shipped CDS reference data Prepared CDS

Reference Data

EDQ Server 2

Web Services

Jobs

EDQ-CDS Project

Shared Staging Database (Oracle /

PostgreSQL)

6

Matching

7

Matching

• EDQ uses Siebel’s Universal DQ Interface to prevent duplicate contacts or accounts being entered into a Siebel CRM

• The same interface is used to match records in real-time in Siebel UCM

• In both cases, the EDQ server does not hold a copy of the working data

• Instead, records are passed between the application and the DQ service. This is a three step process:

– Cluster Generation (Siebel)

– Candidate Selection (Siebel)

– Matching (EDQ web service)

8

Matching Process (1) - Offline

• First, the Siebel Key Generation job is run in Batch on all records to populate the keys• This uses the Query Expression configured in Siebel to generate the keys for each

entity

All records

Id Key

1-7K4E MATTCB23

1-9J4G FRAN4564

1-8K3F CLUB5471

1-7JEZ GWALFL4

1-2NXE MMATTCA7

• The same Siebel job is used to refresh keys for all records, or a subset of records, e.g. on Query Expression change, or if records exist with missing keys

Update table

Siebel Server

Siebel Key Generation Job

9

Matching Process (2) - Online

1

2

New/updated record

Id ClusterKey

1-LJZJ MATTCB23

Driving Record Key Generation

Candidate Selection

Siebel then looks up all records that share a key with the driving record…

…and submits driving and candidate records to the matching service as a single message

Id Key

1-7K4E MATTCB23

1-9J4G FRAN4564

1-8K3F CLUB5471

1-7JEZ MATTCB23

1-2NXE MMATTCA7

Siebel Server

Siebel Key Generation

Siebel uses the Query Expression to generate a key for a new or updated record…

10

Matching Process (3) - Online

3

Matching

• Driving record and candidates passed to matching service

• Matching candidates passed back, ranked by Match Score

• Siebel then handles transaction commit (including commit to Cluster Key table), or not (if user picks an existing record)

CRM/UCM displays possible matches

11

OEDQ Advantages

• Stateless real-time DQ services easier to scale and make Highly Available

• Fully configurable matching processes with all the power of OEDQ transformation and matching available

• Transactional commit integrity controlled by Siebel – no complex replication/synchronization issues

12

Functionality• Records can be checked, cleaned and checked for matches as they are entered

• Supports real time, batch and incremental batch modes

• No integration code is required – the service interface and functionality are all defined in configuration

• Templates and complete configuration instructions for both Siebel and EDQ are provided to ease initial deployment

• Function-rich templates are provided in the Customer Data Services Pack for:– Real-time contact matching

– Batch contact matching

– Real-time account matching

– Batch account matching

– Real-time/Batch address verification/cleaning

• ‘Insert logic here’ templates are provided for:– Real-time/Batch account standardization/cleaning

– Real-time/Batch contact standardization/cleaning

13

Standardization

14

Example Account Standardization

Example Account

standardization service

(running)

Account details instantly

standardized by the service as data is

entered

15

Address Verification & Standardization

Address details instantly verified and cleaned. Partial or incorrect addresses corrected

automatically.

• Address Cleaning service works in real-time and batch

• Uses EDQ Address Verification

• Country-specific ‘thresholds’ are used to control whether or not to change the input address based on the confidence of the address verification result – default settings are provided

• Siebel can easily be customized to display return verification codes/messages and geocodes from the service

16

Account Matching

• OEDQ provides a multi-locale enabled matching process for entities (companies)

• Match scoring allows Siebel UCM to apply standard decision on survivorship

17

Example Contact Standardization

Example Contact standardization

service

Contact details

standardized and

common errors

corrected

18

Example Contact Matching

Possible matching contacts

immediately identified and

scored

19

Editing the Interface

• Where required, changing the interface is a simple two-step process (no change to Connector):– Edit the Field Mappings in Siebel (GUI)

– Edit the Web Service in EDQ Director (GUI)

Siebel Field Mappings EDQ Web Service Definition

20

Editing the Services

• Standardization and Matching services can easily be customized using EDQ

21

Integrated Service/Job Control

• EDQ Real Time services can be started automatically on Siebel startup

• Batch Jobs can be initiated from Siebel Administration or the command line

22

Siebel Data Quality Reporting

• Use EDQ’s built-in Dashboard capability to provide up to the minute reporting on the quality of data in the Siebel system as reported by the running services and jobs

• Additional jobs can be set up to profile data

23

Example Dashboard

24

Example Dashboard

25

Example Dashboard

26

Example Dashboard

27