You are on page 1of 1

I can provide following comments on the overall tasks

1- ESP installation and setup task (1.4 & 1.5) for Dev & Prod is newly added which
was not in the previous plans. We assume that inbound campaigns in this project
will be impenetaed using ESP. In this case, the E2E solution from Kafka to RTDM via
ESP should be discussed and drafted in SDD.

2- 1.2.2 (Reactivate Implementation team stc accounts) & 1.2.3 (CMS EBU
environment Access) - please share the existing account details.\\\

3- 1.2.8 - All STPs and ETLs were shared with SAS and Solutions teams. What
additional is needed?

4- 1.2.9 - It was mentioned last time, that the E2E solution has to be discussed
for all the 5 inbound events with Kafka. Since ESP is considered part of the
updated plan, this item can be closed once discussed with KAFKA team in detail.

5- 1.2.10 - I believe this item was already done as per previous communication. It
was created in Teradata for EBU already. Please check again and confirm.

6- 1.2.11 - This is not clear what RTDM web service is needed? Should be discussed
in conjnction with point 4 & point 1.

7- 1.3.1 - CR Approval - which CR approval is pending?

8- 1.3.2.8 - All existing ETLs were shared with SAS team for their assessment and
review. SAS should be assigned for any further analysis and input needed on the
shared ETL jobs. THe ETLs were built on SAS tool and any migration must be based on
the same tool.

9- 1.3.2.9 - "New ODS" word should be replaced with "CMS Intgration DB". Also, as
of now no new ETL jobs are identified to be built. Existing should be covered under
1.3.2.8

10 - 1.3.2.9.1 - Which ETL environment you are referring here?

You might also like