Configuration Document CITI CEEMEA CRM PROJECT

Table of Contents

1 CEEMEA CRM Directory Configuration on Batch server.............................................2

1.1 Overview...................................................................................................... .......2
1.2 Directory Structure in CRM Batch server..................................................... ........3
1.2.1 Archive Folder Structure................................................ ...............................4
1.3 File Share on Novell File server (GCB01)................................... ..........................5
1.4 FTP Server on CRM Batch server............................................................. ............5
2 Flows................................................................................................................ .........6
2.1 Direct Mailer Campaign for print shop............................................................... ..6
2.2 Import of files from CBAW / ISS / CPO................................................................ ..6
2.3 Export of files to CPO system................................................................. .............7
2.4 SMS Campaign ...................................................................................... .............7
3 Estimation of Data volumes on Novell File Server................................ .....................8
3.1 Print shop feed......................................................................................... ...........8
3.2 SMS files................................................................................ .............................8
3.3 Download files from Local Systems (CPO, CBAW, ISS).................................. .......8
3.3.1 Initial Download Sizes............................................................... ....................8
3.3.2 Incremental Sizes....................................................................................... ...8
3.4 Lists......................................................................................... ...........................9
3.5 SIT Environment............................................................................................ ......9
3.5.1 NDM Node Details........................................................................... ..............9

MphasiS Confidential-Internal Use Only Page 1 of 9

Configuration Document CITI CEEMEA CRM PROJECT

1 CEEMEA CRM Directory Configuration on Batch server

1.1 Overview
The following diagram provides an overview of information exchange between CRM
batch server and other local systems.

CitiGSM CitiGSM
Provider Application MailRoom / Data Centre

HTTPS
Xerox
Cell phone
Printer

$CRMFileShare
Novell Server
Channels
SMS
DM
Response Local System (CPO/ISS/CBAW)
place files in specific in tray folders.
PLSystems It is transferred to batch server
folder for processing. Responsibility
ISS of local systems to delete files in
InTray these folders. GCB01 Systems in
CPO Poland
(CPO,
File Sharing CBAW, ISS)

$CRMFileRoot CRM Batch Server

Systems Each host will have its separate intray
InTray folder. For some hosts, CRM systems
GRB generates data that will be placed in NDM
out tray folders.
OutTray
GRB
Channels
DirectMailer/SMS file are first
DM generated in Batch server and then Systems in
Response transferred to share on novell server. APPC
SMS After the file has been processed, it is
moved to archive folders
Archives

The CRM batch server and the Novell file server will be on the same LAN.

MphasiS Confidential-Internal Use Only Page 2 of 9

Configuration Document CITI CEEMEA CRM PROJECT

1.2 Directory Structure in CRM Batch server

The following table lists the directory structure for files that are to be imported and
exported from the people soft CRM batch server.

$CRMFileRoot
|
|----Systems
| |----InTray
| | |---- GRB
| | |---- ECS
| | |---- IMPACS
| | |---- CITIPLUS
| | |---- ALS
| | |---- WORKAREA
| | |---- OW
| | |---- CWP
| | |---- IPT
| | |---- ISS
| | |---- CPO
| | |---- CBAW
| |
| |---- OutTray
| | |---- GRB
| | |---- CWP
| | |---- CPO
| | |---- WORKAREA
| | |---- IPT
|
|---- Channels
| |------- DM
| | |----Response
| |
| |---- SMS
|

MphasiS Confidential-Internal Use Only Page 3 of 9

Configuration Document CITI CEEMEA CRM PROJECT

1.2.1 Archive Folder Structure

$CRMFileRoot
|
|----Archives
| |---- YYYYMMDD // date specific archives will be created.
| |
| |----Systems
| | |----InTray
| | | |---- GRB
| | | |---- ECS
| | | |---- IMPACS
| | | |---- CITIPLUS
| | | |---- ALS
| | | |---- WORKAREA
| | | |---- OW
| | | |---- CWP
| | | |---- IPT
| | | |---- ISS
| | | |---- CPO
| | | |---- CBAW
| | |
| | |----OutTray
| | | |---- GRB
| | | |---- CWP
| | | |---- CPO
| | | |---- WORKAREA
| | | |---- IPT
| |
| |----Channels
| | |----DM
| | | |----Response
| | |
| | |----SMS
|
|---- YYYYMMDD // date specific archives will be created.

Please Note:
 Archive folders will be created by date. The processed files will be moved to
respective archive folders.

 The “$CRMFileRoot” is a variable that points to a folder on the batch server.

For e.g “$CRMFileRoot” can map to d:\CRM\Poland\Files

MphasiS Confidential-Internal Use Only Page 4 of 9

Configuration Document CITI CEEMEA CRM PROJECT

1.3 File Share on Novell File server (GCB01)

The CRM Batch server will map a volume of the Novell based File server. Access
control to this share will be provided to a select group of users.

$CRMFileShare
|
|----Channels
| |-------DM // Print shop files will be placed here.
| | | ----- Response // Print shop responses will come
here.
| |
| |----SMS
|
|----PLSystems // local systems in Poland
| |----ISS // only files coming from ISS
| | |---- InTray
| |
| |----CBAW // only files coming from CBAW
| | |---- InTray
| |
| |----CPO // both inbound and outbound files
| | |----InTray
| | |---OutTray
|
|----Lists
| |----XSell // Xsell lists will be placed here
| |----Prospect // 3rd party Prospect lists will be placed
here

Please note
 The folder “$CRMFileShare” is folder on the Novell File server (GCB01) that is
shared.

 The files on the share have to be deleted after they are processed so that they
do not occupy space on the novel file server. The rule of thumb is that the
system that processes the file on file share will delete the file.

 The novell share will not support file names in excess of 8.3. This will create a
problem for file naming conventions proposed for feed from ISS / CBAW and
CPO systems.

1.4 FTP Server on CRM Batch server

The CRM batch server also acts as a FTP server to store attachments that are
uploaded into CRM system.

As FTP server is only going to be used between App server and Batch server, IIS Ftp
server is considered for this purpose.

MphasiS Confidential-Internal Use Only Page 5 of 9

Configuration Document CITI CEEMEA CRM PROJECT

2 Flows

2.1 Direct Mailer Campaign for print shop

Steps
1. CRM system executes wave for direct mailer campaigns on a specific date.

2. CRM system generates file with naming convention “CampaignID_WaveID.txt”

on folder “$CRMFileRoot\Channels\DM”. The variables campaign ID and wave
ID are the identifier of the campaign and wave in CRM system.

3. CRM system copies the file from this folder to share

“$CRMFileShare\Channels\DM”. It also archives the file in folder
“$CRMFileRoot\Archives\YYYYMMDD\Channels\DM” as
“CampaignID_WaveID.txt”

4. Mailroom picks up the files from this folder and forwards this to data centre.
Data centre forwards this to print shop.

5. Mailroom also deletes the file from “$CRMFileShare\Channels\DM” folder.

6. Responses from print shop are placed in

“$CRMFileShare\Channels\DM\Response”. The response file will have the same
filename as the request. CRM system will schedule a daily job that checks this
directory and transfers the file to “$CRMFileRoot\Channels\DM\Response”
folder and deletes the file from file share.

7. CRM system process the print shop response file in

“$CRMFileRoot\Channels\DM\Response” folder and moves the file to archive
folder
“$CRMFileRoot\Archives\YYYYMMDD\Channels\DM\Response\CampaignID_Wav
eID.txt”

2.2 Import of files from CBAW / ISS / CPO

The following steps detail the flow of data import from local systems in Poland

Steps
1. Files from Poland local systems are placed on the novell server in respective
system folder “$CRMFileShare\PLSystems”

2. CRM System checks for files in these folders and transfers the file to
respective system folder in tray.

For e.g in the case of ISS, it would be “$CRMFileRoot\Systems\InTray\ISS”.

3. CRM system also deletes the file from novell server after it is picked up.

4. CRM system ETL processes the files in “Intray” like any other host file and
imports the data in CRM system.

5. After processing the file, it is moved to respective system folder in

“$CRMFileRoot\Archives\YYYMMDD\Systems\InTray”.

MphasiS Confidential-Internal Use Only Page 6 of 9

Configuration Document CITI CEEMEA CRM PROJECT

2.3 Export of files to CPO system

Steps
1. CRM system generates file for CPO system in folder
“$CRMFileRoot\System\OutTray\CPO”.

2. CRM system transfers the files from this folder to novell file server share in
folder “$CRMFileShare\PLSystems\CPO\OutTray”.

3. CRM system deletes the file from “$CRMFileRoot\System\OutTray\CPO” and

moves the file to archive folder
“$CRMFileRoot\Archives\YYYYMMDD\System\OutTray\CPO”.

4. CPO system picks up file from “$CRMFileShare\PLSystems\CPO\OutTray” and

processes it. It also deletes the file from novell file share.

2.4 SMS Campaign

Steps
1. CRM system generates file for SMS provider in folder
“$CRMFileRoot\Channels\SMS”.

2. CRM system transfers the files from this folder to novell file server share in
folder “$CRMFileShare\Channels\SMS”.

3. CRM System deletes the file from “$CRMFileRoot\Channels\SMS” folder and

moves the file to archive folder
“$CRMFileRoot\Archives\YYYYMMDD\Channels\SMS”.

4. The SMS file is manually uploaded to CITI-GSM application that sends the SMS
messages to mobile phones.

Please Note
In this case, CRM system does not check for delivery of SMS by provider.

MphasiS Confidential-Internal Use Only Page 7 of 9

Configuration Document CITI CEEMEA CRM PROJECT

3 Estimation of Data volumes on Novell File Server

3.1 Print shop feed

Average Record Size for a customer 600 bytes

Average number of customers in one campaign 10000 – 15000
Campaigns frequency – 200 per month, 40 direct mailer 1 Direct Mailer
campaigns campaign per day

Data Volumes: 9 MB per day.

3.2 SMS files

Average Message Size for a customer (160 bytes message 300 bytes
+ 140 bytes of XML tag overhead)
Average number of customers in one campaign 50000
Campaigns frequency – 200 per month, 40 direct mailer 1 SMS campaign per
campaigns day

Data Volumes: 15 MB per day

3.3 Download files from Local Systems (CPO, CBAW, ISS)

3.3.1 Initial Download Sizes

Sr File System Number of Size of File
No records Record Size in
MB
1 Company CBAW 8200 186 1.5
2 Company Address CBAW 8200 126 1
3 Company Contacts CBAW 12000 316 3.6
4 Endowment Products ISS 1000 267 0.25
5 Customer Mobile CPO 30000 15 0.42
Numbers
6 Customer Activations CPO 30000 12 0.34

Total : 7.1 MB

3.3.2 Incremental Sizes

Sr File Syste Freque Number Size of File
No m ncy of Record Size in
records KB
1 Company CBAW Daily 60 186 10.9
2 Company Address CBAW Daily 40 126 4.92
3 Company Contacts CBAW Daily 60 316 18.5
4 Endowment Products ISS Daily 4 268 1.07
5 Customer Mobile CPO Weekly 800 23 18.4
Numbers
6 Customer Activations CPO Weekly 800 12 9.6

Total : Approx 63.39 KB

MphasiS Confidential-Internal Use Only Page 8 of 9

Configuration Document CITI CEEMEA CRM PROJECT

3.4 Lists
Lists (Customers are prospects) are generated on the Poland work area and
downloaded via NDM to CRM batch server. The directory for these files is
“$CRMFileRoot\Lists\XSell” or “$CRMFileRoot\Lists\Prospect”.

These files are subsequently transferred to the novell file share folder
“$CRMFileShare\Lists” folder. These lists have to be imported in CRM system on
demand. The MIS CRM user will have the capability to browse for this file in this
folder.

3.5 SIT Environment

3.5.1 NDM Node Details

Node Name OAS (Batch server name in SIT)
Operating System Windows NT
TCP-IP Address 169.162.150.152 (SIT)
NDM Port 1364 (SIT)

MphasiS Confidential-Internal Use Only Page 9 of 9