1. The document describes an EDW data architecture using GreenPlum for data storage. 2. It involves mapping data from source systems into the EDW according to source context, storing source reference codes in a master lookup table, and forcing through records with minimal rejection except for critical errors. 3. The architecture also includes cleansing and deduplicating data using Trilium, and storing cleansed and deduplicated information in a business vault.

1. EDW Data Architecture
GreenPlum
4 Key concepts
5 2.Map data from *SOE as per
3 1 source system context
2 4.Store source ref. code in
system of record area
(A master lookup table wil
used to get *ECC)
8.Force-through->min rejection
of records(except critical e
10.Cleansing and De-dupe is
performed by Trilium
12.Cleansed/De-dupe information
is store in Business Vault a
Survivorship
/Dedupe
3NF
* ECC - Enterprise common code/reference code
* SOE – System of entry

2. Cleansing and De-dupe(Survivorship)
Business Vault
Survivorship
Involved party
IP x IP relationship
Lineage
will store which
Trilium-TS Quality TS<match-id> different source
Cleanse System customer
link to the ‘golden
Conditional Golden Record’
SOR Record
Range
IP Golden record
De-dupe Will be created
as new record;
+ cleansed party
info
FINIQ – Mohd. Ali; Female; cif12345; Jln Alor Akar, Melaka,012-233xxxx
Alltel –Ali Mohd; Male; cif12345; Jln Ampang, KL,019-2304302 Mohammad Ali; Male; cif12345; Jln Alor Akar, Kuantan