RWC (Andry)

Target: end of December
PTC first closed: ERP done development, landed. will deploy to production
After PTC done, RWC first closed will be developed in ECI
Visa (ERP) and Eats (v3): will be added later to data lake. Need to check bookingId availability in TripBookingData.
For v3 user, need assessment for the development whether can be generic or not.

Not assessed yet. (PIC: Merlin)
Ale will share required fields for RWC to Merlin today

Data is on datalake but only prod env

Ticket is already in ECI team's backlog, but not prioritized yet
Leli to create ticket to push Visa Sales report in ERP to ECI
Andry & Kurni to join sprint planning to discuss the priority of these tickets (tomorrow 3 Dec 2019)

Tax (Faisal)

B2B first, B2C later
Timeline: https://docs.google.com/presentation/d/1Ksmzn9Iuzo9MERshgCBU0CdDeDlBCdP3nvTjRjMaEKg/edit#slide=id.p

Tax Invoice Report for ID & VN: W3 Jan 2020
Commission Invoice & Invoice Breakdown (all countries): Q2 2020

Will post open bidding in this channel, to open contribution for all interested engineers.
Until new tax system for B2B is ready, Flight Tax Invoice will stay in VPS

Need Airport tax and Agent Fee field in Flight report.

ECI Integration (updates)

Xperience in progress assessment: https://docs.google.com/document/d/1c4hUAToHDmAPem6Hq79LT_ZybFjpYt1boTgRqHmhtfU/edit#

Q1 double write to bpng
Q2 full production
For Experience, product prefer to use Option 1 (data aggregated by POT), need to discuss the details
For Cinema, will discuss this week for the integration.

Putri & Faisal prepare Central Flow's slide to product : https://docs.google.com/presentation/d/1m4IBBOa623qBiPtpA-nDvQp_VRzXV74lee_sb0gSQvo/edit#slide=id.g634e516c5e_0_0

Has been shared to product
BPNG's downstream orchestration will be in our side.

Payment

Still on going assessment,
Payment in integration to EAS -> Jan 2020
Points -> Dec 2019 - March 2020

Flight

Assessment by engineers (separate service in Product domain)
Ongoing assessment retry mechanism framework
Documentation: https://drive.google.com/drive/folders/1On5ZE4M5l6wX3AdVjcJIFMCzQ2OCHbVt

Accom Demand

Ongoing BA assessment

Speciar offer

Maybe assessment in Q1

Experience

Data patch is done
Comparison in progress (September & October OK)

Refund

Library still ongoing. (still ongoing, target: next 2 weeks)

Eats special offer will integrate to data lake

Postponed
To consider: whether directly to BPNG or still use data pipeline.

Requirements for BPNG:

IM, transaction, business partner management, payment data

There might be requirements for finance/accounting to be able to generate self-service report (Putri will setup separate meeting if the requirements is fixed - Not yet)

Will be put in Q1 planning
The needs from Accounting: data should come from report, can't use raw data

Payment-in AWS Multiaccount

Dec 2019 Closing

From Khresna, for closing December 2019, finance need have a plan to have final data in 6 Jan 2020. So finance team expect Corptech to send the data before that.
Will confirm this in Nov 2019, related work in holiday (calendar days vs working days).

Technical timeline

1-10 Dec: 13 Dec, Finance will recon in 16 Dec
11-20 Dec: 23/24 Dec, Finance will recon in 26 Dec
21-31 Dec: 3 Jan, Finance will recon after 3 Jan

Khresna to formalize the reconcilliation process decision with Accounting --> has been formalized, Khresna to share the MoM
Khresna will re-confirm with finance team about their commitments to do checking every 10 days.

QA engineer / SDET

Done, BPNG will start to adopt in Q4 2019
Not suitable for Product stream using older TBI/BP
Backend infra and payment also have this SDET things

Payment not have SDET yet.
BEI don't know yet

After implementation of sample cases, will calculate the reduction of effort to do the tests

FBI Eng + Outsource

Eng: Togi will move the reports from VPS to central flow. He will come up with timeline & prioritization. VPS on call owned by Togi.
Outsource contract has been extended.
Agus & Rydhan will get new assignment to develop ECI Aggregator, waiting for Nazmy approval.
VPS accounting

Manual Addon: decom from VPS --> improvement will be done on Flight Product side
Assigned Payment Reclass & Translation VN --> no major support in BAU, new system: undecided

Treasury Dashboard

Current: Changes from BIA --> will be discussed with Christopher whether it will be catered or not. If yes, will be changed on VPS, development by each product stream
New system --> can't be catered on Kyriba. Christofer has discussed with Khresna, ongoing prioritization

Any changes triggered by product, BIA will coordinate with FPNA & PEA-Anaplan to gather requirement & assess the impact, changes in DOMO data flow will be done by BIA
During transition period, PEA-Anaplan will assist BIA to implement the changes
Any changes triggered by FPNA, will be done by PEA-Anaplan (to be confirmed case by case)
MDR in the meantime will be handled by PEA-Anaplan, before we have centralized MDR
If there is an issue PEA-Anaplan will investigate first, if the root cause is in product data flow, BIA will help to fix the issue

Owned by Data Team Reports

Still waiting for terraform changes on tvlk-eci account
Payment to Deploy Scheduler to TVLK-Prod --> cannot push data from product, data size is too big. There will be a discussion between back end infra vs site infra. After that, require approx. 1 week for development
Currently creating short term solution

Closing Oct, connect Domo to product's DB (only for Oct closing). Continued with short term, replicator in Payment Domain -> Firehose will meeting with Sudhi at 22 Oct. And for long term, asked to be ready in mid Jan 2020.
Short term solution will start to be used starting December 2019

Replacing DOMO

DOMO replacement plan as is although DOMO contact is extended , it just mean we have more buffer --> domo replacement assessment is on hold, will continue in december
Still assessment from analyst (End of Dec 2019)
No query join in this platform, only grouping.
Assessment result:

EAS

E2E corporate technology architecture current and future

Recon Tools

Who will responsible for the recon tools config? Discussion in this meeting
Faisal Ansyari said there's decision in the previous meeting, corptech (PEA) will be responsible to change the config.
When the config need to be changes? Faisal Ansyari will share the criteria/trigger

CT PM TLEAD SYNC 20191202

ECI Integration (updates)

Payment-in AWS Multiaccount

Dec 2019 Closing

QA engineer / SDET

FBI Eng + Outsource

Owned by Data Team Reports

Replacing DOMO

EAS

E2E corporate technology architecture current and future

Recon Tools