Now you can Instantly Chat with Dileep!
About Me
17+ years of experience in Mainframes Technologies. Around 7 years of working experience in UNITED STATES OF AMERICA & UNITED KINGDOM. Good experience in all phases of System Development Life Cycle (SDLC). Worked extensively in analysis, design, deve...
Show MoreSkills
Portfolio Projects
Description
The place of working is at Clients office in Malaysia.Document Trade Port (IMEX) is an Internal Trade Mainframe application used by the Wholesale banking services of Standard Chartered Bank. This product aims at achieving Inter-trade among the customers located in different countries. This product provides services like issuing Letter of credit, indemnity, Guarantees etc. through which the Inter Trade is established among the customers from different countries. This product is being used by 44 countries to perform Trade related operations.
Show More Show LessDescription
Standard Chartered Bank was formed in 1969 through the merger of two separate banks, the Standard Bank of British South Africa and the Chartered Bank of India, Australia and China. These banks had capitalized on the expansion of trade between Europe, Asia and Africa since 1853 (the Chartered Bank) and 1862 (The Standard Bank).Standard Chartered Bank, headquartered in London, UK, provides Banking and Financial Services thru its 1700 (approx.) branches and outlets in more than 70 countries across the globe. It is a constituent of FTSE 100 Index and has a market capitalization of approx 33 Billion Pounds. It is a universal bank with operations in consumer, corporate and institutional banking, and treasury services and around 90% of its profits come from Africa, Asia and the Middle East.IMEX Trade is a mainframe trade finance application that caters for processing various trade products like Import & Export Letters of Credit, Import & Export Bills, Bank Guarantees, Bank to Bank Reimbursement and Loan Processing. The Product is successfully running across 38 Countries.Responsibilities:Analyze the functional requirements and come up with Technical specification required for the Build.Review the build work during the build phase.Supporting during SIT, UAT and UVT phase.Participate in release management activities.
Show More Show LessDescription
Experian is the leading credit bureau in UK which does the credit rating for individuals as well as for Business institutions. As a part of process improvement, the client has decided to move all the applications from traditional M204 database to DB2 under a project by name MORT. Database Matching and pinning is one among the many streams which are being moved.The project involves in migrating the Insurance data from Adabas database in to DB2 and pinning them to the existing database. Took care of the migration strategy and is currently involved in the data migration.Responsibilities:Analyzed the functional requirements and came up with Technical specification required for the Build.Reviewed the build work during the build phase.Developed test harness in CICS to assist in the testing phase.Developed Seeding mechanism using DB2 and Sort mechanisms to lay the initial bed of data.Designed the whole migration plan to migrate the data from legacy into MORT. The plan is being used for the whole migration.Monitoring of the whole process. Single point of contact for the whole process.Tuning some parts of the application designed by others to be in synch with NFR.Managing the deliveries and milestones during the course of project.Performing DB2 DBA tasks in live region after load process and weakly maintenance.Participating in release management activities.Mentoring of resources working under me.
Show More Show LessDescription
Experian is the leading credit bureau in UK which does the credit rating for individuals as well as for Business institutions. As a part of process improvement, the client has decided to move all the applications from traditional M204 database to DB2 under a project by name MORT. Database Matching and pinning is one among the many streams which were moved.
The project involves in matching the given input search name or place against the database and scoring the similarity for all the matches. Pinning would ping the record based on the results from Matching. Client purchased another company by name pH for doing the Scoring mechanism. Took care of Pinning, Matching and scoring part of the project. The project also involved in migrating the Insurance data from Adabas database in to DB2 and pinning them to the existing database. Took care of the migration strategy and is currently involved in the data migration.
Responsibilities:
- Design the work flow between Matching, Pinning and Orchestration streams to attain the functionality.
- Analyze complex pH scoring code in C++ to come up with the corresponding algorithms in COBOL to have the same functionality.
- Design the interfaces between various streams involved in this project.
- Design DB2 stored procedures required at various places of the flow.
- Work at client’s place to have the design agreed upon by the clients’ Tech leads.
- Got selected to participate in performance tuning workshop held at client’s place which involved architects and DBAs from USA and UK.
- Tune some parts of the application designed by others to be in synch with NFR.
- Design the whole migration plan to migrate the data from legacy into MORT.
- Lead the build team consisting of nearly twenty people to build the same design.
- Support during QAT, UAT and Proving phase.
- Mentor the people who worked under me during the whole build.
- Manage the deliveries and milestones during project.
- Performing minor DBA tasks in development region.
Description
Experian is the leading credit bureau in UK which does the credit rating for individuals as well as for Business institutions. As a part of process improvement, the client has decided to move all the applications from traditional M204 database to DB2 under a project by name MORT. Database Matching and pinning is one among the many streams which are being moved.The project involves in matching the given input search name or place against the database and scoring the similarity for all the matches. Pinning would ping the record based on the results from Matching. Client purchased another company by name pH for doing the Scoring mechanism. Took care of Pinning, Matching and scoring part of the project.Responsibilities:Designing the work flow between Matching, Pinning and Orchestration streams to attain the functionality.Analyzing complex pH scoring code in C++ to come up with the corresponding algorithms in COBOL to have the same functionality.Designing the interfaces between various streams involved in this project.Designing DB2 stored procedures required at various places of the flow.Working at clients place to have the design agreed upon by the clients Tech leads.Got selected to participate in performance tuning workshop held at clients place which involved architects and DBAs from USA and UK.Tuning some parts of the application designed by others to be in synch with NFR.Leading the build team consisting of nearly twenty people to build the same design.Supporting during QAT, UAT and Proving phase.Mentoring the people who worked under me during the whole build.Managing the deliveries and milestones during the course of project.Performing minor DBA tasks in development region.Release management activities.
Show More Show LessDescription
The work location was at Client's place at Jersey city, New Jersey.Key bank project involved insourcing the Banktrade product which RBS uses for Transaction banking. This required a Fileset setup and location rollout in insourcing region in Banktrade. Key Bank wanted the accounting and event files which have the transaction details to be sent daily from mainframes to another interface called Mercator which in turn sends to GXS (the receiving side of Key bank). This involves setting up of a new location and file set.
Responsibilities:
- Coordinate with client regarding queries from offshore in developing the programs required for delivering the event and accounting files
- Create Bind cards to bind the existing Banktrade programs to bind to the new database created for Key Bank.
- Create the batch jobs required to be run at the end of every day, week and month.
- Create a new schedule diagram to have all the new jobs.
- Create jobs to load data into certain tables in the new database.
- Code new batch program to handle the 4 MB queue message which was the new requirement for Key Bank.
- Create input file to load input file for loading business provided account details into Account master table.
- Monitor new batch jobs in Integration test environment, Pre- production environment and Production environment.
- Code new online screen specific to Key Bank.
- Load the Banktrade rules (Banktrade functionality is controlled by database entries called rules) in Development environment, Integration test environment, Pre- production environment, Production environment and Production Support environment.
- Support the testing in Integration test environment, Pre- production environment and Production environment.
- Coordinated the whole project from development till it is moved to production by IBM Change control process
Description
Key bank project involved insourcing the Banktrade product which RBS uses for Transaction banking. This required a Fileset setup and location rollout in insourcing region in Banktrade. Key Bank wanted the accounting and event files which have the transaction details to be sent daily from mainframes to another interface called Mercator which in turn sends to GXS (the receiving side of Key bank). This involves setting up of a new location and file set.Responsibilities:Coordinate with client regarding queries from offshore in developing the programs required for delivering the event and accounting filesCreate Bind cards to bind the existing Banktrade programs to bind to the new database created for Key Bank.Create the batch jobs required to be run at the end of every day, week and month.Create a new schedule diagram to have all the new jobs.Create jobs to load data into certain tables in the new database.Code new batch program to handle the 4 MB queue message which was the new requirement for Key Bank.Create input file to load input file for loading business provided account details into Account master table.Monitor new batch jobs in Integration test environment, Pre production environment and Production environment.Code new online screen specific to Key Bank.Load the Banktrade rules (Banktrade functionality is controlled by database entries called rules) in Development environment, Integration test environment, Pre production environment, Production environment and Production Support environment.Support the testing in Integration test environment, Pre production environment and Production environment.Coordinated the whole project from development till it is moved to production by IBM Change control process
Show More Show LessDescription
Place of work was at Jersey City, New Jersey.The Client ABNAMRO was sold to RBS consortium. The objective of the project is to separate 'To-Be' NL Trade portfolio retaining the same back-office infrastructure to achieve data segregation and to enable ring-fencing of Operational users (Netherlands and ACES) and Client Servicing Personnel. The NL Separation Phase 1 project thus aims at only portfolio separation with all other infrastructure like back-office systems, SWIFT etc remaining common.
The project was initially named as Fortis but later changed to NLTS (Netherlands Trade Separation)
Responsibilities:
- Coordinate with client regarding queries from offshore in developing the programs required for delivering the event and accounting files.
- Create Bind cards to bind the existing Bank trade programs to bind to the new database.
- Create the batch jobs required to be run at the end of every day, week and month.
- Create a new schedule diagram to have all the new jobs.
- Create jobs to load data into certain tables in the new database.
- Monitor new batch jobs in Integration test environment, Pre production environment and Production environment.
- Develop jobs to migrate data from base location to the new location.
- Load the Bank trade rules (Bank trade functionality is controlled by database entries called rules) in Development environment, Integration test environment, Pre production environment, Production environment and Production Support environment.
- Coordinated the whole project from development till it is moved to production by IBM Change control process
Description
The Client ABNAMRO was sold to RBS consortium. The objective of the project is to separate To-Be NL Trade portfolio retaining the same back-office infrastructure to achieve data segregation and to enable ring-fencing of Operational users (Netherlands and ACES) and Client Servicing Personnel. The NL Separation Phase 1 project thus aims at only portfolio separation with all other infrastructure like back-office systems, SWIFT etc remaining common.The project was initially named as Fortis but later changed to NLTS (Netherlands Trade Separation)Responsibilities:Coordinate with client regarding queries from offshore in developing the programs required for delivering the event and accounting files.Create Bind cards to bind the existing Bank trade programs to bind to the new database.Create the batch jobs required to be run at the end of every day, week and month.Create a new schedule diagram to have all the new jobs.Create jobs to load data into certain tables in the new database.Monitor new batch jobs in Integration test environment, Pre production environment and Production environment.Develop jobs to migrate data from base location to the new location.Load the Bank trade rules (Bank trade functionality is controlled by database entries called rules) in Development environment, Integration test environment, Pre production environment, Production environment and Production Support environment.Coordinated the whole project from development till it is moved to production by IBM Change control process
Show More Show LessDescription
The palce of work was Jersey city, New Jersey.
The Client had a batch job stream and online submitted jobs which generated reports using Focus reporting tool. There were around 300 reports which used to be generated weekly, quarterly and yearly basis. Client came to know that the license for using Focus was going to expire by Dec 31, 08. It was suggested to convert all the reports from Focus to another reporting tool Easytrieve. The project was completed in three months and by Dec 31, 2008 all the reports were put into production. Client has saved more than million dollars in the form of fines for using Focus.
Responsibilities:
- Identify all the reports required to be converted.
- Develop macros in Easytrieve which were used across the offshore team in developing their respective reports.
- Resolve the queries raised by offshore team in their reports
- Change all the procedures using Focus to use Easytrieve.
- Change all the JCLs using Focus to use Easytrieve.
- Coordinated the whole project from development till it was moved to production.
- Supported the initial runs of the batch job to see smooth running of jobs.
Description
The Client had a batch job stream and online submitted jobs which generated reports using Focus reporting tool. There were around 300 reports which used to be generated weekly, quarterly and yearly basis. Client came to know that the license for using Focus was going to expire by Dec 31, 08. It was suggested to convert all the reports from Focus to another reporting tool Easytrieve. The project was completed in three months and by Dec 31, 2008 all the reports were put into production. Client has saved more than million dollars in the form of fines for using Focus.Responsibilities:Identify all the reports required to be converted.Develop macros in Easytrieve which were used across the offshore team in developing their respective reports.Resolve the queries raised by offshore team in their reportsChange all the procedures using Focus to use Easytrieve.Change all the JCLs using Focus to use Easytrieve.Coordinated the whole project from development till it was moved to production.Supported the initial runs of the batch job to see smooth running of jobs.
Show More Show LessDescription
The place of work was Jersey city, New Jersey.Bank Trade is a product used by ABN Amro Bank. Modules involved are Letter of Credits, Reimbursements and Collections. NJ Gt Development is a test environment support team which is responsible for Development, Test and Pre- production environments. It is also responsible for coordination of Bank Trade releases.
Responsibilities:
- Monitor batch jobs daily in Test and Pre- production environment to resolve any batch failures immediately so that the job runs without any problem in production.
- Resolve any DB2 bind problems that occur during COBOL code promotion through Change Man tool.
- Setup new Filesets or locations in Development, Test, Pre- Production and Production regions as a part of new projects. This includes Bank trade rule setup, new batch jobs setup and printer setup.
- Create RFC (Request for Change) required for Bank Trade quarterly releases.
- Coordinate complete release activities right from Pre- prod implementation to production implementation with all other interfaces. This includes RFC maintenance, conducting Business and Technical Risk assessment meeting, resolve any issues raised during Pre- production testing of a release.
- Create tools to minimize manual errors during releases.
- Interact with Client regarding new enhancement requests and communicate to offshore as onsite coordinator.
Description
Bank Trade is a product used by ABN Amro Bank. Modules involved are Letter of Credits, Reimbursements and Collections. NJ Gt Development is a test environment support team which is responsible for Development, Test and Pre production environments. It is also responsible for coordination of Bank Trade releases.Responsibilities:Monitor batch jobs daily in Test and Pre production environment to resolve any batch failures immediately so that the job runs without any problem in production.Resolve any DB2 bind problems that occur during COBOL code promotion through Change Man tool.Setup new Filesets or locations in Development, Test, Pre Production and Production regions as a part of new projects. This includes Bank trade rule setup, new batch jobs setup and printer setup.Create RFC (Request for Change) required for Bank Trade quarterly releases.Coordinate complete release activities right from Pre prod implementation to production implementation with all other interfaces. This includes RFC maintenance, conducting Business and Technical Risk assessment meeting, resolve any issues raised during Pre production testing of a release.Create tools to minimize manual errors during releases.Interact with Client regarding new enhancement requests and communicate to offshore as onsite coordinator.
Show More Show LessDescription
This project involves maintenance of Purchase Order Management (POM) System. Maintenance of the project involves Production support, Bug fixing, handling minor request, handling Major requests and research on production problems/optimization. JCPenney is using POM system for creating/sending orders to suppliers, allocating the created orders to different stores and tracking the goods delivered by the suppliers to the stores.
POM system was installed in phased manner and maintenance tasks involves in taking over the new releases from the time of warranty period. Complexity increased with the number of technologies that needs to be handled as a part of production support.
Responsibilities:
- Do the Impact Analysis for the minor and major enhancement requests.
- Create High level design documents for major enhancement requests.
- Review developed code and unit test results performed by team members.
- Performance tuning of NSSQL stored procedures.
- Configuration controlling for the project, Knowledge transfer about the application to the new team members.
- Allocate work to team members.
Description
This project involves maintenance of Purchase Order Management (POM) System. Maintenance of the project involves Production support, Bug fixing, handling minor request, handling Major requests and research on production problems/optimization. JCPenney is using POM system for creating/sending orders to suppliers, allocating the created orders to different stores and tracking the goods delivered by the suppliers to the stores.POM system was installed in phased manner and maintenance tasks involves in taking over the new releases from the time of warranty period. Complexity increased with the number of technologies that needs to be handled as a part of production support.Responsibilities:Do the Impact Analysis for the minor and major enhancement requests.Create High level design documents for major enhancement requests.Review developed code and unit test results performed by team members.Performance tuning of NSSQL stored procedures.Configuration controlling for the project, Knowledge transfer about the application to the new team members.Allocate work to team members.
Show More Show Less