Hanumant Janjire

Description: ODS is a data lake/mart where data is gathered from various sources in the ODS mart. Once it comes, ODS has three different data processes in place to fulfill the customer/client request based on the application.
1. Service Now 2. ODS 3. AIMS (Forecast)

Responsibilities: • Analyze the request and its scope, and work on it within 24 hours. After the request was raised.
Review customer requests and provide the solution.
• Create change requests for providing ODS DB objects access to customers.
Modification of existing DB objects and enhancement based on customer requests.
Performance tuning in SQL queries and object levels.

Description: Risk Console (RC) to Risk Console Advance (RCA) upgrades. Ventiv Technology has its own product, i.e., ETL, and the domain is finance.
And insurance. So, the RC is used to generate the reports as per the client.
Requirements are based on what they have decided with fields; it’s the flexibility.
They have in place. Now, Ventiv has new features to add to its own.
ETL tool with flexibility according to the client's request, and the new server is configured to have all these features and flexibility in RCA.

Responsibilities: • Ownership of a module, and guiding the team on all fronts. • Writing good quality SQL queries with procedures, triggers, views, etc. With optimal performance and performance tuning for already written or new queries for transformation logic, understanding and collecting requirements from the business user side or business analyst, and converting the business requirements to the actual application using complex SQL queries.
Use different strategies for database development to meet the client's functional requirements.
In RC-RCA upgrades, we have migrated RC loads in RCA using the ETL tool. For that, we must take care of the extraction of data, the transformation of logic as per the client or business request, and create a load in ETL on the RCA side. Once the load gets created with all these inputs, we have to test end-to-end testing and compare it with the RC load for matching the reports.

Description: BPSA - (Broadridge Processing Service Advantage), Broadridge is an external entity that facilitates the settlement of the trades originating from UBS and populates the BPSA database.
BPSA – The database provided by Broadridge is a copy of the mainframe.
Information pertaining to a Broadridge ADP client; this allows UBS.
It runs out of queries relating to operational requirements.

Responsibilities: • Ownership of a module and guiding the team on all fronts; • Writing good quality SQL queries, with procedures, triggers, views, etc. With optimal performance and performance tuning for already written or new queries.
• Understanding and collecting requirements from the business user side or business analyst. • Converting the business requirements to the actual application.
using complex SQL queries.
Use different strategies of database development to meet the client's functional requirements.
In BPSA, there are thousands of jobs that are executed on a daily, weekly, and monthly basis; they are developed in Perl, Sybase, and Unix.
BPSA is a migration project. As required, we need to set up the required development and UAT environments, and create the same jobs that are present in AutoSys.

Description: DQCD (Data Quality Control Database). The DQCD is a data mart (database) that has different databases, such as Source, Meta, and Views. There are different upstream and downstream systems, and each upstream and downstream system has separate databases, such as DQCD_ERDS, DQCD_SERV, and DQCD_IBOR. In the DQCD source schema, we have created database objects and provided the roles and permissions to each object of the DQCD_SOURCE schema.

Responsibilities: • Ownership of a module, and guiding the team on all fronts. • Writing good quality SQL queries with procedures, triggers, views, etc. With optimal performance and performance tuning for already written or new queries, I performed various development and design activities of PL/SQL functions, procedures, packages, and triggers as per business requirements.
• Provided development support for database jobs in the production environment.
• Understanding and collecting requirements from the business user side or business analyst. • Converting the business requirements to the actual application using complex SQL queries.
Use different strategies for database development to meet the client's functional requirements.

Description: The CMART application is a system used for end-to-end transaction processes for corporate loans. This application is used in ICICI Bank for managing corporate loans (credits). They need to finance their setup and ask for a loan from a bank.
This application has three main modules: Pre-sanction, Disbursement, Post-sanction, and Reports. So, the Pre-sanction module contains all the verification of documents and various checklists before approving loans. Once verification is completed, disbursement keeps track of the actual disbursement of the loans process. The post-sanction module is the monitoring of repayment from the account holder or corporate companies.
And finally, in report modules, various reports are required by the end user of the bank, such as the Consolidated Monitoring Report, Security Report, Event Report, Branch-wise DP Report, Document Report, Summary Report, and so on.

Responsibilities: • Ownership of a module and guiding the team on all fronts. • Writing good quality PL/SQL with optimal performance.
Performance tuning for already written or new queries.
• Understanding and collecting requirements from the business user side or business analyst. • Converting the business requirements into actual applications using complex SQL queries.
Unit testing of the application after issue fixing.

• Developed scalable and maintainable code, ensuring long-term stability of the software.
• Integrated new technologies into existing systems, increasing capabilities and improving overall performance.
• Developed reusable components that significantly reduced development effort on multiple projects.
• Implemented effective debugging strategies, resulting in fewer software defects and increased reliability.

• Developed scalable and maintainable code, ensuring long-term stability of the software.
• Improved software performance by identifying and resolving bottlenecks in the code.
• Coordinated with other engineers to evaluate and improve software and hardware interfaces.
• Delivered unit-tested systems within customer-prescribed timeframes.