Pratik Chandran Nair

TICS is a Muti Branch and Multi entity structured Settlement System. It handles Confirmations, netting, bookings, and Payments. TICS handles products such as FX, FX Options and Call Notices. It is a combination of Java for xml Injection (Parsing), Trade display GUI and underlying Mainframe for Data processing and Batch execution.

• Functioned as a Mainframe and Lead Java technical resource for the team
• Worked extensively on Java xml Parsing and creation of MT/MX Messages using the schema definitions with hands on experience in both Mainframe and Java development
• Collaborated with different architectural teams for migrating from WebSphere to liberty which included changing the entire Web application structure from Build to war Package deployment and rebuilding of approx
• (80+ modules) including Java and Mainframe
• Involved in developing new CI/CD pipelines for Application scans such as Fortify and Nexus to determine and remediate code vulnerabilities
• Actively lead the team towards ensuring optimal utilization of server storage and efficient trade data display on the WebTICS GUI for end user implementations

The warehouse is a repository of data from various data-capturing and processing applications. Data is captured by various applications, like Infolink, CSW, etc. And is passed on to the different processing systems. Depending on the type of data, whether global or domestic, the various data processing applications, like WINS (accounting data), Titan ¾ (for domestic US), COSMIC (global transactions), CAPP, and COACS, etc. Send their data across to the warehouse.

• Functioned as a technical resource for the team.
• Designed and developed new programs, JCLs, and procedures as per business requirements.
• Expertise in IBM MQ Series coding for the conversion of other message processing mechanisms to MQ's.
• Involved in analyzing, testing both unit and integration testing, and handling errors in case of issues.
• Prepared implementation documents, test case documents for all the mentioned projects, as per implementation.

Projects

A. TDQ to MQ Conversion – GDW.

The current architecture uses a TDQ structure to transmit the incoming data from source systems to the data pop process, and then finally to the outbound processing. As an overhaul to the existing system, it was decided to migrate all the existing TDQs to Native MQs for added processing advantages and reliability.

Roles and Responsibilities:

1. Was solely responsible for communication with the GTI infrastructure for the setup of the different MQs.

2. The complete system was implemented in three phases and worked without a single incident.

B. Legacy to Strategic Onboarding – GDW.

All account supporting attributes and legal entity data were sourced from other secondary systems by means of a daily batch input file. These secondary systems were about to be decommissioned, and there was a lot of data stitching done before the data was sent to GDW. I undertook this project to remove the applications dependency on the other secondary systems. We developed an architecture of Alias and Remote Queues, which would transmit the delta data on a real-time basis, and the same would get processed into our system. Adequate measures were taken for the logging, monitoring, and clearing of messages from the Archival Queue.

Roles and Responsibilities:

1. Was solely responsible for communication and deliberation with the secondary systems as to the viability of information that can be procured from them.

2. The entire project was completed within a span of four months, from inception to release.

Undertook one month of rigorous production parallel testing, where all data received was compared between the current batch and the proposed online system of data collection.

C. Other responsibilities and accomplishments – GDW.

1. Manage all the start-of-the-year holiday scheduling and database restore/upgrade activities to handle the current year’s data.

2. Manage all communications regarding the new CICS Configuration Manager for creating new CICS resource definitions.

3. Work on the resolution of 200+ client-raised alacrities so that the root cause can be found, and any fixes should be made and communicated to the client at the earliest.

4. Create documentation of all newly created processes so that it will be useful for everyone on the team to undertake an analysis or debug anything later when required.

Projects

MLIDT - PCA/SAV.

The Personal Chequing/Savings Application is one of the crucial constituents of the CIBC Banking System in general, and Global Deposits and Payment Transactions (GDPT) in specific. It supports the retail transaction products for CIBC. PCA/Savings has over 40 interfaces to and from other applications; it covers functions including financial transaction postings, management information, financial reporting, updates to operating terms, and managing balances, as well as opening, closing, and maintaining customer accounts.

Roles and Responsibilities:

1. Functioned as a technical resource with lead responsibility in a team of two.

2. Designed and developed modifications to programs, Jcls, and procedures to implement new account offers as per business requirements.

3. Awarded recognition for work done in the RIPTIDE Phase 2 release.

4. Was recognized by Onsite with the Applaud Award for maintaining CGI quality values.