Company master training_final_l

© 2010 VMware Inc. All rights reserved

Confidential

Company Master Training

Company Master Implementation Team

June 6th, 2013

2 Confidential

Agenda

Project Overview

Governance Process

File Upload Functionality

VMware Hierarchy Updates

EA# in company master

MDM BI Datamart (Reports)

3 Confidential

Project Overview

4 Confidential

Company Master Project Highlights

Existing

New / Impacted Integration Process

New / Impacted System

EMS

UCM HUB

File Upload

POC 2.0

FMW

ETL

EDW

Trillium

Managed

Mastered

- Party- EA#- EA_ID

- Party- Account- Site

- DUNS #- Segment

- Partner ID- Account

Batch Process

D&BRefresh

MDM Data-Mart

APJ 150

ETM

- Account- Parent - DUNS

- Account- Parent- DUNS #

5 Confidential

Company Master landscape

My VMware

(EMS)

COMPANY MASTER (UCM)

Master Attributes

(Best version, xref and legal H)

Managed Attributes

(VMware H, Enrichment)

EBS

(Oracle)

VMStar

(SFDC)

ETM

(DRM+iLog)

EA#

Party ID

EA#

Account

Site ID

Account

Site ID

EDW

APJ file,

POC 2.0

Parent DUNS#

BI / Reporting

UUID

Master and Managed

Attributes

Existing Source

New Source

DRM

Node ID

MDM BI

6 Confidential

Project Scope

Bring company data from disparate systems into the Company Hub and centralize all company

information associated to it.

• APJ Top 150 accounts

• ETM accounts

• POC 2.0 attributes

Bring additional D&B linkages associated to the accounts (White Space)

Maintain Legal Hierarchy for each company (DUNS based hierarchy provided by D&B)

Create and maintain VMware custom hierarchy; and allow user overrides to it. This is a UUID

based hierarchy (Global Parent -> Subsidiary -> Country HQ -> Site)

Maintain Managed attributes that are owned and maintained by business. Eg: Market

Segment, Revenue, Employee total, Hardware spend, No of desktops, SIC etc.

Integrate Entitlement accounts from EMS with the master – EA# to Company ID association.

Build Company Master BI dashboards to provide users the ability to view and access company

data – Hierarchy and managed attributes

Load Managed attributes and UUID based hierarchy into EDW and connected data marts – For

analysis and comparison purposes in Phase1 only.

7 Confidential

What’s coming in Phase 2?

Real Time integration with spokes (EBS, SFDC) to sync back Master and Managed

data

Impact analysis of shifting EDW hierarchy from DUNS based to UUID based

hierarchy and the impact to BI reporting.

Moving Market Segment derivation logic to UCM

Plugging in the new D&B IM workflow to the master for more accurate DUNsing

Introduce a Reference Master to track/audit DUNs changes on company records

during D&B refreshes.

Data Profiling and analysis for Atlas sites – Add as a new spoke

8 Confidential

Master Attributes

Master attributes are key to the operation of business and are the primary focus of the

company master data management program. These attributes describe the “who” in a

business transaction.

Master attributes are “locked in” and are not allowed to be directly updated by business users

manually in company master.

They are also attributes that provide a cross reference between company data that is mastered and

the corresponding record in the transactional system.

These attributes form the heart of the master data management system.

Once mastered these attributes will be owned and governed by the EIM team. All mastered attributes

need to be harmonized with the business systems (spokes) that source and/or consume the data.

Example : Company Name, Address, xref info (source system ID, Source system name) etc.

9 Confidential

Managed Attributes

An information set of company enrichment attributes that helps business function

make informed business decisions. These attributes are generally of interest to more

than one business unit so they are centralized and maintained within the company

master.

If an attribute is used solely by one business function, it does not reside in the company master

and can be maintained within the local business system.

Some of the data attributes maintained by the business unit can be nominated for inclusion in the

managed data set.

Each of these data elements are owned by the respective functions that (1) sources it and (2) keeps

it up to date leveraging the Enterprise data management process.

The EIM ops team will govern these attributes and work with these business functions to define the

attributes, their data standards and governance policies to create/read/update/delete the data.

Example : System Generated :- PRM ID, EA#, Company Type, Company Category

Managed by Business users :- Industry vertical, # of employees, Software spend, Hardware spend etc.

10 Confidential

Legal Hierarchy

DUNS based hierarchy queried from D&B

GLOBAL ULITMATE

Head Quarter Parent

1:n

Domestic Ulimate

1:n

SITE

1:n

The Global Ultimate is the top most entity within the company hierarchy and may have subsidiaries reporting

to it

Has financial decision making authority for all the branches under it.

Top most parent identified for a country

A site is the lowest node in the hierarchy and is the

account site associated to a transaction in VMware.

11 Confidential

Example

HEADQUARTER PARENT

DOMESTIC

ULTIMATE

12 Confidential

Company Hierarchy

A fixed 4 level customized hierarchy that can be used by multiple business functions and geos

Uses the D&B legal hierarchy as baseline.

GLOBAL ULITMATE

SUBSIDIARY

1:n

COUNTRY HQ

1:n

SITE

1:n

The Global Ultimate is the top most entity within the company hierarchy and may have subsidiaries reporting

to it

A company within the corporate family having a unique name. May not legally directly report to the GU

The Country Headquarters is an entity identified within the company hierarchy to which all sites for that company and a given country roll up to

A site is the lowest node in the hierarchy and is the

account site associated to a transaction in VMware.

13 Confidential

Example

14 Confidential

Governance Process

15 Confidential

Governance Team Structure

Trustees - Executives who have the ultimate

decision making authority and are accountable

for the quality, accuracy and usage of data in the

enterprise company master system. These

trustees form the Data Management Steering

Committee.

Data Steward – Managers within the business

function who are nominated by their unit‟s trustee

to lead the data efforts within their respective

function. This individual has in-depth knowledge

of the organization and is responsible for the

quality of data in his/her business unit

Data Advisor - Individual with in-depth

knowledge of function/business unit data who

advises the data steward on impacts of mastered

and managed data to the business function.

Data Analyst – Individual or team who has

working knowledge of the processes and data in

the company master and has a strong

understanding of the data requirements of the

business unit and how they relate to master data.

Trustees

Data Stewards

Data Advisors

Data Analysts

Enterprise Information Management

16 Confidential

Governance Team

OrganizationTrustee

(Steering Committee)

Data Steward

(Stewards)

Trusted

Data Advisor(s)

FAST Mia Leondakis Partha Baral Paul V, Jay Franklin, Raj Srinivasan

FAST – EDG Mia Leondakis Emilie Ly Shreeram Neelavar

FAST – BI Mia Leondakis Jay Franklin TBD

Marketing Susan Nishimoto Andrew StevensonSwaroop Malangi, Jaydeep Patel,

Michelle Walters, Rob Dunse

Finance Sirisha Dasu Wendy CollinsUsha Lal, Mike Gabrys, Paresh

Mackrani

Renewals Bryan Cox Andrew Condon Kathleen Gormanshaw

Customer Advocacy Eric Wansong Gregory Daly Shreeram Neelavar

GSS Mark Ritacco Torsten Hentschel Robert Quaglia

Product Marketing Michael Huang Yiting Jin Ankur Jain

Americas Michael Ogden Peter McDonaldBill Reposa, Georgia Close, Aubrey

Santos

EMEA Clive Pocock Roberto Meani David Adamson, Paul Raja

APJ Paul Bailey Karthik Palanievel Kiran Kumar

Legal Rebecca Matthias Rebecca Mathias Aine Lyons, Mary Futch

SPAN Sindy Braun Barry Davis Arnab Guha

HR Jonathan Schoonmaker Amy Gannaway Kelly Pankratz, Jennifer Nickel

Channels Ko Mistry Jeanine Bierlein Sam Pritchett

17 Confidential

RACI Chart

Role Overall Data

Quality

Data Update &

Remediation

DQ Monitoring &

Communication

Business

Adoption

Trustees A A A A

Data Stewards R C C R

Data Advisors C I I I

Data Analysts C I I I

EIM Team C R R C

For overall data quality management, the following chart designates that the data stewards are responsible

and trustees accountable. Stewards, Advisors, Analysts and EIM are consulted and informed.

18 Confidential

Detailed Process FlowGovernance Process – Company Data Updates

EIM

Tea

mSt

eerin

g Co

mm

ittee

Data

Adv

isors

Data

Ste

war

dsDa

ta A

naly

sts

Chan

ge

Requ

esto

r

1Request a change1. Hierarchy Override2. Master Attribute Update3. Managed Attribute Update

2Validate the request

per the Checklist

SFDC Case assignment

Request Valid?

3aInvestigate the

change and consult the relevant data

advisor

Yes

4Review request and

validate the data change

Change is valid?

Start

No

5Respond to Data Analyst and send information to

Data Steward for approval

Yes

3bNotify the requestor and close the case

No

Any conflicts identified?

Needs conflict resolution from

Steering Committee?

Yes No

6Facilitate meeting

with Steering Committee

Yes

7Determine the course

of action to resolve conflict. Determine

survivorship

9Perform the change in Company Master and update ticket

Approve Change?

Yes

8Communicate the decision back to

data steward

No

No

End

Ensure all required information is present

in the document -

1. Company Name and address for new

company creation

2. UUID and attributes for managed

attribute update

3. Parent and Child company UUID for

hierarchy override

Determine the Geo that

will be impacted by this

change.

Authenticate the change.

1. Does the parent child

relationship indeed exist?

2. Is the managed attribute

value correct?

1. Any cross Geo conflicts (if GULT or

subsidiary is being overridden)?

2. Any issues with changing name or

address of the company?

What geo or business function gets

precedence ?

1. Surviving GULT may be determined

based on the GEO where the

company is Headquartered

2. If company name or address change

would impact transactional systems

then a new record may need to be

created

19 Confidential

Use Case – Company Hierarchy change

Governance Process – Company Hierarchy Update

EIM

Tea

mSt

eerin

g Co

mm

ittee

Data

Adv

isors

Data

Ste

war

dsDa

ta A

naly

sts

Chan

ge

Requ

esto

r

Request a hierarchy update/override

Validate the request per the Checklist

Case assignment

Request Valid? Yes

Review request and validate the data

changeChange is valid?

Start

No

Respond to Data Analyst and send

information to Data Steward for

approval

Yes

Notify the requestor and close the case

No

GULT and or Subsidiary level

change?


Steering Committee?

No

Facilitate meeting with Steering Committee

Yes

Determine the course of action to

resolve conflict. Determine

survivorship

Perform the change in Company Master and update ticket

Approve Change?

Yes

Communicate the decision back to

data steward

No

No

End

Determine type of request and GEO

and contact appropriate Data

Steward

Involve Data stewards from other GEO’s and functions

for approval

Yes

Would be Country HQ

change

20 Confidential

Use Case – Master attribute update

Governance Process – Mastered Attribute update

Da

ta

Go

ve

rna

nce

G

rou

p

Co

mp

an

y M

ast

er

(UC

M)

So

urc

e S

yst

em

1Initiate the update to the record.End user updates – EBS/SFDCPartner Updates - SFDC

Start

2Minor update – Update existing record.Major update – Create new record

3Minor update – Existing record gets updatedMajor update – Record gets xref’d to an existing BV or ends up creating a new BV

4Ping D&B to get the updated DUNS number

5Update legal hierarchy if required and flag D&B+1 hierarchy for business review.

6

Validate and update the D&B+1 hierarchy if required

(facilitated by EIM Ops team)

7Run quarterly data quality report and check the health of the system by validating major and minor updates

End

21 Confidential

Use Case – Managed attribute updateGovernance Process – Managed attribute Update

EIM

Tea

mSt

eerin

g Co

mm

ittee

Data

Adv

isors

Data

Ste

war

dsDa

ta A

naly

sts

Chan

ge

Requ

esto

r

Request a managed attribute update

Check the attribute being asked to

update

Case assignment

Is it a source system record key such as

PRM ID or EA#?No

Review request and validate the data

changeChange is valid?

Start

Yes

Respond to Data Analyst and send

information to Data Steward for

approval

Yes

Notify the requestor and close the case

No

Conflict resolution needed?


Steering Committee?

No

Facilitate meeting with Steering Committee

Yes

Determine the course of action to

resolve conflict. Determine

survivorship

Perform the change in Company Master and update ticket

Approve Change?

Yes

Communicate the decision back to

data steward

No

No

End

Determine type of request and GEO

and contact appropriate Data

Steward

Involve Data stewards from other GEO’s and functions

for approval

Yes

22 Confidential

Escalation Path

This escalation path will be followed in the below scenarios–

• Data update validity and survivorship rule determination due to cross geo or

cross business unit conflicts.

• Data update requests are not turned around within defined SLA.

• New/existing source system or process in any of the VMware systems is not

following the Company master data model or data standards and processes.

Data Stewards EIM Steering Committee

23 Confidential

EA# in Company Master

24 Confidential

Party ID and EA# are maintained in company master at cross-reference level (External ID)

EA# between EMS and company master is in-sync for the below scenarios of EA# –

Create

Inactivate

Merge

EA# for Incomplete and Middle Match scenario records will only be displayed in company

master after the record gets remediated by EIM team

EA# and Party ID job is scheduled to be executed every 3 hours

EA# in MDM BI datamart (Demo provided later as part of MDM datamart training) -

Available on the hierarchy against the company ID/UUID against the sites

Capability to search by EA#

EA# and Party ID in Company Master

25 Confidential

Overriding managed attributes/VMware

hierarchy - File Upload Functionality

26 Confidential

This feature facilitates overrides for VMware hierarchy and managed attributes in Company

Master

The below actions can be performed via this process – Inserting a new company with or without managed attributes populated

Updating master attributes for an existing company. Managed attributes (if needed) can also

be updated as part of this action

Overriding only managed attributes for an existing company

Overriding VMware hierarchy

All the Business Units will prepare the data per the file format. After the upload file is

ready, as per the governance process reviewed earlier, open a SFDC case.

Post governance process and necessary approvals, EIM team will upload the file to

company master

Upload file format:

Upload File Format

File upload process for managing data

https://vmshare.vmware.com/it/pmo/Tier 1 Project/MDM/Shared Documents/SDLC Documents/2. Design/Upload_file_format.xlsx

27 Confidential

File should be saved as pipe-delimited text file prior to uploading

File name should be: For updating VMware hierarchy: CMP_HIERARCHY_UPD.txt

For all other actions: CM_UPLOAD_DG.txt

File upload process – File naming convention (EIM team)

28 Confidential

File upload process (EIM team)

First email received:

Acknowleding that file

has been

accepted for upload

Second email received

(~5 minutes after the 1st

first email): Confirming file is being processed.

Each file is provided with a unique batch ID.

This email has details about the file name and Batch ID.

Based on this, the file status can be tracked in the file

upload UI.

After file has been processed, post processing

Summary is received.

This email has information about

total # of records, # upload, # rejected. Error file can be

downloaded from File status UI

File uploaded by

EIM in File upload UI

29 Confidential

Format all the cells in the excel spreadsheet as “Text” before entering or copying/pasting

data. This is to avoid auto-correction performed by excel which may lead to incorrect data

in fields like Number_of_desktops, Number_of_servers which accept data in a range and

excel auto-corrects to a date. Ex: “10-20” becomes “20-Oct”

EIM team -

To avoid junk characters that get appended while converting the excel into a text file, change the

default delimiter to “pipe” in windows- control panel- region and language-additional settings under

date and time format- List separator (Type |)

The junk character causes upload failures, batch count shows up as 0 even though there are

records in the file

The junk character cannot be viewed in notepad or textpad. Is visible only when opened on server

(unix box)

In the error file, the first column has the error message. After reviewing and correcting and

record, the error column can be removed and the file can be re-uploaded as the rest of the file is

same as the standard upload file format

Multiple files can be uploaded at the same time. This feature is available while updating both

Managed attributes and VMware hierarchy. The files are queued in this case

File upload process – Tips

30 Confidential

Link to File Upload screen. This screen should only be accessed by EIM team

http://ucmprod.vmware.com:7780/cgi-bin/file/compmaster.pl

Credentials will be shared separately

File upload screen and File Status screen (EIM team)

To view the file

upload

status

Error file is

an excel file








31 Confidential

File upload Format – Different attribute groups within the file

Master attributes

Managed attributes

32 Confidential

File upload Format – Different attribute groups within the file

Updating VMware Hierarchy

33 Confidential

File upload process – Inserting a new company

Master attributes

are mandatory

Validation rules -

Action and Source fields are mandatory per LOV/domain values

UUID should not be provided. Record will be rejected if this field has been populated

Name and Address line 1 are mandatory. Either city, state or zipcode has to be provided

Country is mandatory as per LOV/domain values

For these records, Trillium cleanse/standardization/matching will be performed using

existing Trillium rules. Records will be set to incomplete per existing completeness rules

DUNS IM process will be performed for this activity to populate legal hierarchy attributes.

If managed attributes are not provided, managed attributes will be the same as legal

attributes

34 Confidential

File upload process – Updating an existing company

Validation rules -


UUID is mandatory and should be valid

Name and Address line 1 are mandatory. Either city, state or zipcode has to be provided

Country is mandatory as per LOV/domain values

For this action, update will happen based on UUID

DUNS IM process will be performed for this activity to populate legal hierarchy attributes

Master attributes

are updated

35 Confidential

File upload process – Updating managed attributes

Validation rules -


UUID is mandatory and should be valid

Master attributes (including country) should not be provided

For this action, update will happen based on UUID

All managed attributes should be as per respective LOV‟s (mentioned in Upload File

Format)

All managed attributes should follow the format requirement (mentioned in Upload File

Format) Example: All revenue/dollar value fields need a “$” as part of the value. Number of servers, Number

of desktops need to be a range and hence need “-” as part of the value

All DUNS #‟s should be 9 digits long. If not, zeroes will be appended to the left to make it 9 digits

Only managed

attributes

should be provided

36 Confidential

File upload process – Updating VMware hierarchy

Validation rules -

Both UUID and Parent UUID are mandatory and should be valid

No other attributes should be provided

Swap Scenario(e.g elevating Site to CountryHQ and bringing CountryHQ down to Site

Level) can be achieved in 3 steps.

1. Elevate Site1 S1 to CountryHQ level-2 say CHQ2

Site1 UUID points to new Parent say SUB1 UUID(which is a Subsidiary –

Level3)

2. Repoint all the other sites from current CountryHQ CHQ1 to this new CountryHQ

CHQ2

Site2 S2,Site3 S3 parent UUID points to CHQ2

3. Bring down the current Country HQ CHQ1 to site level-4.

Point Parent UUID of CHQ1 to CHQ2.

Master+Managed attributes should

not be provided

37 Confidential

Updating VMware hierarchy - Details

Parent UUID is the immediate Parent‟s UUID in the new tree

Example: If the use-case is to move a site under a subsidiary node, parent UUID will

be the new Subsidiary‟s UUID

When a parent node is moved to a new tree, all the child nodes under the parent move

with it. No separate action is needed to point the child nodes to the parent.

When UUID and Parent UUID are same in the upload file, that particular company will be

detached from the existing tree and made a single location i.e. it‟s own GULT

GULT

SUB1 SUB2 SUB3

In the File, SUB3 UUID and Parent UUID

are the same. SUB3 will be detached

from this tree

38 Confidential

Use case: SUB1 has to be moved to a new tree. Tree flag should be provided as

„N‟.

Updating VMware hierarchy – Tree Flag Usage

GULT

SUB1 SUB2 SUB3

CHQ1 CHQ2

Site1

Only SUB1‟s UUID

should be provided

as “UUID” in the file. Only SUB1 along

with child nodes will move under the new

Parent.

No impact to SUB2 and SUB3

39 Confidential

Use case: All companies need to be moved to a new GULT. Tree Flag should be

provided as „Y‟.

Updating VMware hierarchy – Tree Flag example

GULT

SUB1 SUB2 SUB3

CHQ1 CHQ2

Site1

Any of the Subsidairy‟s UUID

can be provided as “UUID” in the file.

All the companies will be

moved under the new GULT

40 Confidential

Use case: All companies at CHQ level need to be moved. Tree Flag should be

provided as „Y‟.


GULT

SUB1 SUB2 SUB3

CHQ1 CHQ2

Site1

Any of the CHQ‟s UUID



moved under the new parent

CHQ3 CHQ4

Site2 Site3 Site4

41 Confidential

Use case: All sites (level 4) need to be moved. Tree flag should be provided as

„Y‟.


GULT

SUB1 SUB2 SUB3

CHQ1 CHQ2

Site1

Any of the Site‟s UUID



moved under the new parent

CHQ3 CHQ4

Site2 Site3 Site4

42 Confidential

“One off” update in UCM UI (EIM team)

Validation rules -

Press Crtl+N or select Menu-”New Record” to perform the required action

Validations are same as bulk upload process

All actions except updating VMware hierarchy can be performed

New screen under

Universal

Customer Master

43 Confidential

BI Reporting – Company Master

44 Confidential

Reporting - Platform

45 Confidential

Reporting Tool – OBIEE

Production : http://bi-prd-mdm-a1:9704/analytics/

http://bi-prd-mdm-a1:9704/analytics/saw.dll?bieehome








46 Confidential

Company Master – Dashboard

Click to open dashboard

47 Confidential

Legal Hierarchy

48 Confidential

Dashboard Page – Legal

49 Confidential

Click on the dropdown

and start the search by

Company.

Later click on

More/Search option.

Search – Company Name

50 Confidential

Specific company search

is performed in the pop-

up window.


51 Confidential

Click SEARCH.

Uncheck the Match case option,

Search for a particular company Example: Berkshire Hathaway


52 Confidential

Remove the EMC Corp from right-hand side by selecting

remove option.


53 Confidential

Select the Company Berkshire Hathaway Inc. from search.

Click move.


54 Confidential

Click OK


55 Confidential

Click on Apply Button to see the result.

Click on the DUNS Number Column to view the Legal Hierarchy.

Viewing Hierarchy – Click on DUNS Number

56 Confidential

Click on the Return button to go the Legal Search Page

Viewing Hierarchy & Return To Search Page

57 Confidential

Search by DUNS Number by selecting the drop down.

Search – DUNS Number

Click on More/Search option.

58 Confidential

Uncheck the match case option and search for a particular DUNS Number


59 Confidential

Type the DUNS Number

Click Search


60 Confidential

Click on the DUNS Number on the left.

Select Move option


61 Confidential

Click OK


62 Confidential

Click on Apply Button


63 Confidential

Other Search Parameters

Search by UUID / Company Id

64 Confidential

VMware Hierarchy

65 Confidential

Dashboard Page – VMware

66 Confidential

Search By Company

Search – Company Name (Ex: Berkshire Hathaway)

67 Confidential

Click on the Company Name dropdown

Select More/Search option.


68 Confidential

Uncheck the Match Case option,


69 Confidential

Search for a particular company in the pop-up window text box Example: Berkshire Hathaway


Click Search

70 Confidential

Select the default EMC Corp on the right-hand side

Click on Remove


71 Confidential

Select the Company Berkshire Hathaway.Select MOVE


72 Confidential

Click OK.


Click Apply

73 Confidential

Click on the UUID/Company ID column to view the VMware hierarchy

Viewing Hierarchy – Click on UUID

74 Confidential

Viewing Hierarchy & Link to Managed Attributes

Click on the UUID/Company ID Link.

This enables the managed attributes to pop-up for that UUID.

EA number can be viewed in the hierarchy & Managed Attributes page

75 Confidential

Viewing Managed Attributes & Return to Hierarchy Page

Click on the Return link to go back to the „VMware Hierarchy’ page.

76 Confidential

Click on the Return link to go back to the „VMware Search’ page.

Return To – VMware Search Page

77 Confidential

Search – Company Name (Ex: Kaiser Permanente)

78 Confidential

Click on UUID/Company Id to view the VMware hierarchy

Search – Company Name (Ex: Kaiser Permanente)

79 Confidential

Click on Return to navigate to the VMware hierarchy search page,

EA numbers can also be viewed on this hierarchy page.

Viewing Hierarchy (Kaiser Permanente) & Return to Hierarchy Page

80 Confidential


Search by Company Name and Country

Search by EA Number

81 Confidential


Search by Source System Name & ID

Search by UUID

82 Confidential

Click on the Export Click to Export the report to Excel OR PDF

Export - Data

DATA EXPORTED IN EXCEL & PDF IS IN WYSIWYG MODE

83 Confidential

Move the cursor towards the column to see the arrow mark for Ascending or Descending sort order.

Sorting

The Column will be sorted in Ascending order

84 Confidential

Sample Searches - many sites

Cisco Systems

Ebay South SJ

Berkshire Hathaway

Royal Philips Electronics N.V

Sony

85 Confidential

Appendix

86 Confidential

Process SLA’s by Role (will be revised post go live)

Data Activity Role SLA

Middle Match remediation EIM Ops team 2 days (existing SLA)

Incomplete data remediation EIM Ops team 3 days (existing SLA)

Duplicate resolution EIM Ops team 5 days (existing SLA)

Company Hierarchy override

Data Analysts 24 hours

Data Advisors 2 days

Data Stewards 2 days

EIM Ops team 1-1000 records – 90 mins

1000-10000 – 5 hrs

10000-50000 – 24 hrs

>50000 – subject to team bandwidth

Managed Attribute update

Data Analysts 24 hours

Data Advisors 2 days



1000-10000 – 5 hrs

10000-50000 – 24 hrs


D&B Legal Hierarchy refresh MDM IT 3 days

Company Hierarchy refresh

Data Analysts 2 weeks

Data Advisors 1 week



1000-10000 – 5 hrs

10000-50000 – 24 hrs


87 Confidential

EA# and Party ID in company master

EA# stamped for existing customers at x-ref level

88 Confidential

Steps to request a change via CMT (1 of 4)

A request for change has to be initiated via an SFDC case and assigned to the EIM ops team ([email protected]).

The below sections show the screen shots on how to log an SFDC case and assign to EIM Ops.

Log into Sales Force and navigate to Cases and create New: Select Data Governance as Case Record Type:

mailto:[email protected]

89 Confidential


Populate the required fields under Case Information as shown below:

Fill in the required fields under Issue Description -

Example, Subject: Update for entity X, Y, Z || Description: Updating segment value for X, Overriding Y with Z etc

90 Confidential


If there are any supporting documents that can be used for faster investigation and validation, please attach that using

the below functionality.

The data that needs to be updated in bulk mode should be attached based on the set template format.

Follow instructions on the Attach File(s) screen:

91 Confidential


Hit Save & Close at the bottom of the page:

A confirmation email will be sent automatically to you.

For any questions or to check the status of a ticket, you can check back in SFDC or email [email protected] with

your case number as a reference.

mailto:[email protected]

Company master training_final_l

Technology

master ea

reference master

company master bi dashboards

company duns

access company data

company hub

mastered attributes

company records