---
# System prepended metadata

title: Ankur provided.

---

# Ankur provided.

----
<font color="#f00">
出差計劃
We are planning for the travel, we would start our Visa processing as well.
Dishank and myself are discussing on the travell dates and will get back to you shortly ...

Howerver, I still have the following worries:
- The material we provided in the other email, has it been discussed with CTBC; I am worried CTBC may be thinking that we are not telling them what and how - and that material answers those questions hence it important to socialize that (I saw your other mail on queries, will reply shortly)
- Have you and Jeremy incorporated that in the plan? We would need to align our travels in line with some of those sessions as well ...
- We also need to arrange folks for Interfaces and Batch sessions, the methodoligy sessions we can cover but the detailed discussions we have to arrange th right team - Jeremy - did Nitin or Kamal come back with any names yet? (Gyan most likely in ONLY for NFR)
</font>

----
Please find enclosed
1. NFR Study Approach WBS – This elaborates the Approach & WBS for NFR Study
2. NFR_Streams_View_v0.6 – This provides details of what all items we can have under NFR and how they are categorized under 6 streams
3. Interfaces Study Approach WBS v2 – This elaborates the Approach & WBS for Integration Study
4. Batch Study Approach WBS – This elaborate the Approach and WBS for Batch Study

You can use these details either to update the program plan excel (which is like L4) or you can create more detailed version for NFR/Interfaces/Batch Streams (which is like L5/L6)…

<font color="#f00">
**Ankur Reply @20220905**
As discussed the other day, instead of editing the plan, Dishank and myself have worked on the WBS details for each stream.</font>


----
## NFR Study Approach WBS

1. NFR Strategy (Sessions by TCS)
    1.1 NFR Study Approach
    1.2 Brief overview of the coverage of line items and their categories 
2. NFR Study (Discussions by TCS covering the following categories) 
    2.1 Development Arch.
    2.2 Integration Arch
    2.3 Security Arch
    2.4 Deployment Arch
    2.5 Operations Arch
    2.6 Reliability & Performance Model 
3. Documentation, Walkthrough and Sign-off
    3.1 NFR Specification Documentation Preparation (TCS)
    3.2 Prepare Roles and Responsibilities for various parts on NFRs (i.e. across CTBC, TCS & IBM)
    3.3 Review with CTBC for documentation scope coverage
    3.4 Scope finalization & sign-off

----
## Batch Study Approach WBS

1. Batch Strategy (Sessions by TCS)
    1. Batch Study Approach
    2. Approach to Classification (Functional, Integration, Extract & Reports, etc.)
    3. Approach to Solutioning for each Category
2. Overview of BaNCS Batch Processing (Sessions by TCS)
    1. GxP Batch Processing Cycle (Intra-day, End of Day, etc.)
    2. Sharing & Explaination of GBP Batch Catalog
    3. Sharing & Explaination of GSP Batch Catalog
    4. Sharing & Explaination of GIP Batch Catalog

3. Batch Study (CTBC & IBM - TCS can help review)
    1. Batch Catalog - create AsIs Batch Inventory (AsIs catalog of CTBC)
    2. Classification of Batch Jobs
    3. Validation of Inclusion in Target ToBe State across the following streams
        1. CTBC Extracts & Reports
        2. BaNCS GxP Functional Scope
        3. Interfaces
        4. Deprecated
    4. Identification of Batch Jobs Missed and triage on resolution for each job (e.g. Not Required, add to TCS Functional Scope, Add to CTBC list, etc.)
    5. Update BaNCS GxP FS/Interface Specification / Extracts & Reports Specification basis above agreed Resolution
    6. Finalize ToBe Batch Inventory

<font color="#f00">
**Ankur reply @20220905**
I belive the below questions are on Batch WBS, please also look at Interface WBS which also covers some of these parts.
Answer to your questions inline below. Hope this helps.. please call me in case of further questions and I can explain...

In Case you want to discuss the WBS in detail we can do it over a call as well, BUT is is very important that you understand this in detail and clearly... Based on your experience/inputs we can refine as well.

Probably CH would need some context from our previous - you can explain to him.
</font>

----
## Interface Study Approach WBS

1. Integration Strategy (Sessions by TCS)
    1. Sharing & Explaination of GIP Batch Catalog
    2. Integration Experience
    3. Integration Approach & Key Success Factors
    4. TCS BaNCS Integration Enablers
2. Interfaces Study Approach (Sessions by TCS)
    1. Integration Landscape - AsIs/Current & ToBe/Target
	2. Integration Principles for Evolution to Target State
	3. Interface Inventory & Scoping
	4. Classification & Grouping into Patterns & Sub-Patterns (Upstream/Downstream, Channels/Core Engines/Satellite Apps, Online/Batch, Command/Query/Extracts)
	5. Creating System Interaction Catalog/Touch Point Tracker
	6. Interface Specification Documentation 
3. Discovery & Finalizing Scope (CTBC & IBM - TCS can help review)
    1. Interface Inventory (AsIs)
	2. Integration Principles
	3. Target State Landscape
	4. Templates - for Interface Inventory, System Interaction Catalog, Interfaces Specification Doc
	5. Interfaces Inventory (ToBe) - In-Scope Systems, Integration Patterns
	6. System Interaction Catalog/Touch Point Tracker Details
4. Online Interfaces (Sessions by TCS)
	1. Overview of API based Integration
	2. Approach of Design, Mapping & Build for API based Integration
	3. API Ecosystem (ESB, API Management, Developer Portal, IAM, Co-Ex / Orchestration, TCS BaNCS APIs, etc). & Responsibilities of each participant
	4. UUID & API Usage Standardization
	5. API Versioning & Roll Out
	6. API Security
	7. Exception Management 
	8. Sharing & Explaination of GBP API Catalog
	9. Sharing & Explaination of GSP API Catalog
	10. Sharing & Explaination of GIP API Catalog
5. Message based & Batch based Interfaces (Sessions by TCS)
    1. Overview of Inbound Message based & Batch based Integration
	2. Overview of Outbound Message based & Batch based Integration
	3. Approach of Design, Mapping & Build for Message based & Batch based Integration
	4. Message based & Batch based Integration Ecosystem (File Gateway, SI, TCS BaNCS, DataWay, EDL, etc). & Responsibilities of each participant
	5. Scheduling & Triggering Approach
	6. Exception Management 
	7. Sharing & Explaination of Standard GBP Message and Batch Interface details
	8. Sharing & Explaination of Standard GSP Message and Batch Interface details
	9. Sharing & Explaination of Standard GIP Message and Batch Interface details
6. Interfaces Study (CTBC & IBM - TCS can help review)
    1. Interface Specification Documentation x for each In-Scope System as per the Interfaces Inventory
        1. API Mapping x for each API based touch point as per the System Interaction Catalog
	    2. Message/File Mapping x for each message/file based touch point as per the System Interaction Catalog

<font color="#f00">
**Ankur reply @20220905**
This is a bigger and worrying topic -- we would also need to work with the functionals steams for this....
Probably best to have a call with everyone ...
</font>

----
Dear All,
Happy to share that Gyan from GSP team would be joining us for CTBC Taiwan NFR Tracks.
He will actively participate in GSP’s NFR side, and for GSP’s Migration/Interface/Batch, he will act as SPOC (liaising with GSP team internally).

We have had an overview call with him to explain the context of the program, please include him in the relevant threads as well…
Also, do add him to the NFR Teams Channel and Meeting Invites …

Dear Gyan,
In the first call we have, we will introduce you to the team and their areas – for now sorry for throwing so many new names 😊 

----
2022/9/12

Hi CH,

Please find enclosed an updated WBS – the changes broadly are:

NFR
Have modified a few line items
Have changed the timeline and ordering for NFR tasks – instead of going sequentially with streams, have tried to group them logically together across streams…
@Jeremy Lau – Like we were discussing the other day, NFR stream would NOT have signoff BUT would still have User Stories, NFR Specs, Design, Build, Test etc. Shouldn’t these activities be part of this plan like Functional Stream? Or you feel this is already factored in the functional build tasks? [@Chung Hsiang Shen please setup a call on Mon/Tue to discuss this point]
Interfaces & Batch
Have included additional line items
Have changed the timeline for some tasks
@Jeremy Lau, @M Sivasankar – there are some tasks highlighted in yellow – basically for making the release plan and incremental details available to CTBC – From the functional streams perspective do you feel we would be in a position to deliver these? [@Chung Hsiang Shen please setup a call on Mon/Tue to discuss this point]
 

@Jeremy Lau & @M Sivasankar – In addition to the above specific points, we want to run this plan as a whole by you and seek your feedback – please provide a slot for Monday/Tuesday to review this

----
