RajaRajeswari Gunda

Project : MIRO

Technology : Data Stage, Oracle, LINIX, Java

Tools &Utilities : Autosys, Splunk, AppDynamics,AppWatch, Sitescope, SQL data studio, ITSM Remedy, JIRA,ServiceNow and Grafana

• The MIRO application is the provisioning tool for BNPP doubtful client.
• The Main objective of MIRO is to provide a standard and automated it system for impairment calculation. This IT system provides the following features
• Collection of outstanding from the accounting systems.
• Monitor and review all doubtful commitments and other outstanding requiring an impairment calculation (management of the complex workflow between Business lines/Risks/Finance
• Have a calculation process regarding the provision movements with all required IFRS components.
• Each components of the provision Un discounting time Effect (UTE)
• Record implements decisions from local and central committees.
• Produce all necessary reporting statements for stakeholders.
• Monitor the history of decision masking of a file.

Responsibilities:

• Experience in leading L2 and L3 production support team.
• Incident management, Problem Management, Release Management and Change Management
• Conducting Knowledge transition sessions for new joiners and bring them up to speed
• Resolving all issues encountered in Production environment
• Involved in the AppDynamics deployment across multiple applications in production
• Creating support tickets for critical application issues and provide the logs for resolving the issues
• Using Grafana to create operations dashboard for business people to monitor overall applications health and provide reports for daily/weekly basis
• Sending Application Downtime and Release notifications
• Coordinating with teams and resolving complex application and system issues.
• Well-Versed with Software Development Life Cycle / Process / Methodologies / support Frameworks.
• Willingness to learn and master the latest technologies.
• An excellent team player with very good communication skills.
• Coordinated monthly application releases with the business team and other stakeholders and ensured that agreed timelines are met.

Project : UCRS

Technology : Data Stage, SQL Server, LINIX, Java

Tools &Utilities : Autosys, Splunk, AppDynamics,AppWatch, Introscope, SQL data studio, ITSM Remedy, JIRA, ServiceNow

• UCRS is a Unified Collection Recovery System for payments and continuing to build a positive relationship with customers. This Execute adequate and timely collection and instigate recovery activities in order to minimize risk costs and optimize returns
• Record arrears history in order to ensure a complete file as a sound basis for decision making during collection / recovery
• Communicate with customers by telephone and in writing to manage debtors and arrears process
• It is a process which generates reports related to regular credit card payments.
• It receives source data from TSYS(Third Party Tool). It is raw data which contains daily credit card payment details and process into UCRS application with the help of autosys and DataStage and Java.
• In autosys jobs execute by hitting Sql server and through Data stage jobs. Once data is processed from source to staging, it sends the data from UCRS to Blaze. Blaze is a rule engine which applies rules on current data for all business units and retransmits data into UCRS. Now UCRS starts preparing queues which will be available for agents for dialer process.
• 8AM is SLA for this application. By this time agents start dialing to customer using this data.
• Worked on Change management, release management and capacity management.
• Resolving all issues encountered in Production environment
• Monitoring the daily batch process and resolving any issues in the process
• Periodic Application Health Check and Follow-up
• Alert Monitoring and necessary Support/Follow-up
• Creating the change tickets for Production environment and work along with the teams for the implementation of changes along with the respective teams Represent and raise issues/pain points with the relevant stakeholders
• Bring in production stability by way of process improvements (time saving etc.).

Project : Reportnet

Technology : Autosys, SQL Server, LINIX, Java

Tools &Utilities : SQL Server Management Studio, Splunk, AppDynamics, AppWatch, ITSM Remedy

• Monitoring Autosys batch jobs and analyse the logs if job fails.
• Worked on Autosys scheduling tool and created JIL scripts to scheduling job.
• Addressing business user’s queries and responding to their ad-hoc request
• Resolving all issues encountered in Production environments
• Monitoring the daily batch process and resolving any issues in the process
• Periodic Application Health Check and Follow-up
• Alert Monitoring and necessary Support/Follow-up
• Reviewing and Executing the DB requests
• Handling and coordinating Production Releases
• Reviewing Release Notes and Sanity Test Documents
• Performing Application Checkouts after the releases
• Periodic Support Status and Reporting
• Excellent experience on incident management and change management.

Project : Think Money

Technology : Data Stage 8.1, SQL Server, Linux

• Think Money is a debt management solution organization that helps its customers to solve their financial problems through their innovative products. Used lookup, transformer, join while designing jobs.
• The company having different products like FreemanJones, Mortgage, Insurance, Credit Cards Gregpenn and Think banking.
• Each product having different features. The Database has lots of historical data. So data warehouse plays a major role in enabling various stores to view the data at a lowest level and help them to make decisions to bring more revenue to company with new policies Cleanse and transform the data as per business logic.

Responsibilities :

• Created Data stage Sequencers to run jobs in a particular sequence.
• Used the transformations like Lookup, Filter, Aggregator, transformer in the development of data stage jobs.
• Good hands on experience in writing and debugging database complex queries.
• Performed import and export of Data Stage jobs from one environment to other environment.
• Used Data Stage Director for running, monitoring & scheduling the jobs.
• Worked on Control M to schedule and monitor the jobs.
• Used Data Stage Director & Control M for running, monitoring & scheduling the jobs.