Vijay A Ramachandra Resume

  • June 2020
  • PDF

This document was uploaded by user and they confirmed that they have the permission to share it. If you are author or own the copyright of this book, please report to us by using this DMCA report form. Report DMCA


Overview

Download & View Vijay A Ramachandra Resume as PDF for free.

More details

  • Words: 2,783
  • Pages: 8
Vijay A Ramachandra +91 99000 95707 LinkedIn Profile URL: http://www.linkedin.com/pub/vijayramachandra/14/675/a31

-

-

Siebel 7 Certified Consultant 13+ years of total Industry Experience 12+ years of experience in IT Consulting. 9 + years of experience in Siebel CRM Applications 3 years of experience as Release Manager handling various major releases, parallel releases, involving several integrated applications. Energetic and decisive Manager Excellent organizational, Leadership, team building, project management and customer servicing skills Good communication, analytical and interpersonal skills

Role: Release Manager / Project Manager Organization: Wipro Technologies Summary of Experience: 12 years of IT Experience. 1 year of Industrial Experience.



• •



• Technical Expertise: -

Siebel 7.5/7.7/7.8 Verticals: Finance, Insurance, Manufacturing, Telecom

• • • • • • • •

• • • •

Rsmt.Ford0856Nov01.doc



A Siebel Certified Consultant executed Siebel projects including Project Management, Release Management, Business Analysis, System Study, Requirement Gathering, GAP Analysis, Configuration, Mapping, testing and deployment. Experience in working as Release Manager & successfully managed multiple integrated releases across platforms Siebel Implementation experience on Agile process Model  Providing an ability for the business to refine requirements  Quick Application Demos to business  Conduct Daily Scrum meetings involving business users, SME’s & Technical team Multi Siebel Release strategy planning and execution. Proficient in managing / coordinating with customer, Interacting with end users, vendors, business analysts and IT team Effort, Schedule Estimation and Impact analysis and preparation of SOW. Timely highlighting of Risks and Issues to Senior Management as well as to the Customer Manage Customer Interaction throughout project lifecycle Planning and scheduling activities to ensure completion of the project within time and budgetary parameters Release Management and change control process Management Effective participation in introduction of tools in project lifecycle to enhance operational efficiencies Experience in Data Loads using Siebel EIM. Proficient in Experience in Onsite/Offshore Software Development Life Cycle. Good Communication, Project Management and Team Management Skills. Expertise in handling teams and client interfacing skills Strong interpersonal skills both in leadership and teamwork Expertise in proposals, estimations and presentations Project Management Institute (PMI) registered member

Page 1 of 8

Selected Few Project Details: 1. Siebel Releases {Projects / Enhancements / Change Requests / Production Fixes} Client: Pitney Bowes (PB), USA Duration: November 2008 to till date Role: CRM Release Manager Execution Location: Onsite Team size: 24 Description: Pitney Bowes (PB) provides the world's most comprehensive suite of mail stream solutions to help companies manage their flow of mail, documents and packages. As a CRM Release Manager was responsible for

 Requirements scope management & Sign off from all business stakeholders for every planned Siebel Release Planning & Scheduling Siebel Releases (major, minor & patch) for current calendar year based on business groups needs  Identification, preparation & maintenance of all Development & Testing environments  Responsible for periodic & adhoc environment refresh requests from PROD / other environments  Co ordinate all cross tower QA environments refresh for major releases, in order to be in sync  Chair & conduct Repository meetings twice a week in order to evaluate all the changes that need to be moved into Siebel Master Repository  Entire Planning and scheduling of release activities from initiation to closure of the release to ensure successful release  Responsible for monitoring & control of all deliverables after each major phase in release  Co ordinate Code / Design review of all the projects identified for a release with Siebel Expert Services  Prepare & maintain release project plan capturing all activities  Schedule System Integration Test (SIT), Regression Testing (RT) & User Acceptance Testing (UAT) defect review meetings with the team & business groups  Responsible for planning & execution of Performance Testing cycles for every release with performance testing team  Evaluate & compare performance test results with baseline with the team and plan appropriate corrective actions in order to improve the system performance  Schedule SRF builds during SIT / RT / UAT phases  Prepare build specific Release notes during UAT phase and communicate to all business groups  Plan & Schedule Mock Run deployment in QA environment with all migration activities in similar lines as will be carried out in actual deployment  Conduct deployment walk through of migration items from all involved project teams with DBA & Siebel Admin before deployment  Preparation of monthly / quarterly CRM release activities calendar  Preparation of Deployment Support plan during deployment week end  Preparation of Rollback plan for all the release items that needs to be deployed as part of the release  Conduct Technical smoke testing meetings with technical teams after deployment  Conduct Functional smoke testing meetings with business teams after deployment  Conduct Go – No Go meeting with business teams after deployment to announce successful Go-Live or determine Rollback  Monitor & control of all release deliverables in IBM Rational Clear Case after completion of each phase of release  Creation of Parent Appdev record, Queries in IBM Rational Clear Quest for each Siebel Release  Monitor & control timely updation of all the records in IBM Rational Clear Quest for each Siebel Release by all team members

Rsmt.Ford0856Nov01.doc



Page 2 of 8

 Evaluate,Analyze & approve / reject all Change Requests  

Prepare metrics after each release and compare to previous release metrics, and determine the performance of the release Document & share lessons learned for each release

2. Order Entry Data Conversion Phase 2 {Asset Data} Client: Level (3) Communications, USA Duration: August 2007 to October 2008 Role: Release Manager Execution Location: Onsite Team size: 18 Description: Level 3 Communications is an international communications company and operates one of the largest communications and Internet backbones in the world and is one of only six Tier 1 Internet providers in the world. During Phase 2, Assets (Service Images) of various products of the Level3 acquired companies were migrated from various legacy sources into one common Siebel 7.8 platform. As a Siebel Release Manager was responsible for A. Run Management: Client’s single point of contact for run planning and execution, which includes:       

Planning of Siebel Environment & database refreshes for data conversion runs Siebel refresh and all-clear (readiness for run) to offshore Regular Run status Updates during weekly unity conversion run Handoff between Onsite and Offshore Connection Settings changes for Informatica Updation of Run checklist, Run tracker sheet and preparation of Postmortem reports for the run and closure of issues detected Fallouts’ projection for the next run

B. Data Fallout Management:   

     

Dashboard generation for every Run Source, Load & UDT Reports Fallout Review Meeting i. Internal – Development Team ii. Business – With Level 3 Biz & Project stake holders Run - Defect creation & allocation Defect Tracking & Management Supporting Data for Defect Fixes Weekly Dashboard & Analysis to Level 3 Top Management Defect fixes for next run. Level3 Weekly Status dashboard

Rsmt.Ford0856Nov01.doc

C. Release Management:        

Detailed Release Plan Present the plan to Level 3 Release Management Co ordination of activities across team for Integrated Release Production Resource Planning GCR Creation TCOE Releases Test Plan Doc Approval from Biz for Test Plan Doc Requirements approval from BIZ

Page 3 of 8

   

Fill Up SOX checklist & GCR approval meetings All production access related 3 help tickets Conduct safe user session & get necessary approval for production Go Live Prepare production audit documents

3. Order Entry Data Conversion Phase 1 {Non Asset Data} Client: Level (3) Communications, USA Duration: February 2007 to July 2007 Role: Business Analyst Execution Location: Onsite Team size: 7 Description: During Phase 1, billing accounts contacts of the Level3 acquired companies were migrated from various legacy sources into one common Siebel 7.8 platform. As a Business Analyst was responsible for • • • • •



Involved in requirements sessions to capture the business needs and come up with the Requirements specification document. Preparation of high level design & mapping Document and getting sign off. Single point of contact between customer & offshore team for all project related ongoing activities. Responsible for all the deliverables & Quality from the offshore development center. Responsible for resolving all defects / fallouts during the conversion process. Responsible for successful conversion of the billing accounts & contacts into Siebel 7.8.Tracking & monitoring all project deliverables, calculating burn rate, Schedule/Cost & Effort Variance.

4. SMS MVS Integration Phase 1 Client: Pitney Bowes (PB), USA Duration: October 2006 to January 2007 Role: Project Manager Execution Location: Onsite Team size: 9 Description: Pitney Bowes (PB) provides the world's most comprehensive suite of mail stream solutions to help companies manage their flow of mail, documents and packages. The purpose of the SMS MVS Integration Phase-1 project was to provide an automated means by which service transaction data can be passed back and forth between Pitney Bowes SMS system and MVS Customer CRM system. Providing this capability will enable Pitney Bowes to offer their MVS customers a technologically current mechanism for sharing service transaction data, and providing PB with the potential to grow their MVS revenue as required. As a Siebel Project Manager was responsible for • • •

Rsmt.Ford0856Nov01.doc

• • •

Involved in internal requirements sessions to capture the business needs and come up with the Requirements specification document. Involved in conducting requirements workshop with Pitney Bowes MVS customer. Responsible for preparation of Cost Estimate, Project Plan, Test Plan, SOW & resource loading plan for the project. Preparation of Functional Specification Document and getting sign off. Single point of contact between PB, MVS customer & offshore team for all project related ongoing activities. Responsible for all the deliverables & Quality from the offshore development center.

Page 4 of 8

• • • •

Conducting regular project meetings with the team & the MVS customer, and updating the project status weekly to the client. Tracking & monitoring all project deliverables, calculating burn rate, Schedule/Cost & Effort Variance. Responsible for preparation of documentation and evidences with the help of tools like Rational Reqpro, Clear case, Clear Quest for project CMMi audit. Deliver projects (including staffing, ramping up, resolving technical conflicts, planning) as per as per committed timelines and budget.

5. MRM Data Conversion Client: Anheuser-Busch (AB), USA Duration: April 2006 to August 2006 Role: Data Analyst Execution Location: Onsite Peak Team Size: 10 Description: Anheuser-Busch (AB) is a world leading Brewing company. MRM is an integrated application which manages AB’s Accounts, Cost Centers & Budget Requests. The Project involved Data Mapping, Technical Design, Design Document preparation, Client Presentation, EIM Data Loads, Testing Contribution: As a Siebel Data Analyst was responsible for • • • • • • •

Primarily involved in working with SME’s and Business users to understand the Legacy system (MBA) and map data to existing Siebel MRM Module. Preparation of Data Matrix sheet & Technical Design Document. Presentation of Design to Client’s Internal & External Review Team. Responsible for preparing various Data transformation criteria’s while bringing data from Legacy system (MBA). Loading of Accounts (Cost Center, Cost Element & Internal Orders) & Budget Request Data into Development, Testing & Production environments. Scheduling of daily delta loads of Budget Request Adjustments Legacy Data Validation

6. UK FS & CC Implementation

Rsmt.Ford0856Nov01.doc

Client: Pitney Bowes (PB), UK Duration: June 2005 to March 2006 Role: Siebel Analyst Execution Location: Offshore Peak Team size: 17 Description: The project deals with building a CRM solution using Siebel Employee Applications to cater UK and Europe operations of the client. This includes Business process analysis, configuring the Siebel application to enhance the CRM functionality for Call center and Field Service Agents, providing Siebel application maintenance support and comprehensive extensions & customizations. This will enable the client to handle their customer touch points in a better fashion. The Field Service rollout is aimed at improving Field Technicians productivity by delivering them the assigned tasks and getting updates from them over the handheld. The subsequent implementation of Call Center is to capture, classify and resolve Customer queries, intimating the customers regarding their outstanding payments and launching campaigns so as to retain the Customers. The main benefits for the Client are:  Significant reduction in the time taken to resolve a Service Request.  Annual Maintenance visits automatically taken care off.  Inventory ordered over the handheld by the Technician.  Integration of Siebel with other systems such as SAP, Tandem etc through batch and real time interfaces. Enhancing Customer Experience by in time resolution of their queries and due escalation in case of deviations.

Page 5 of 8

Contribution: As a Siebel Analyst was responsible for • •

Involved in creation of LLD and updation of Technical Design Documents. Responsible for developmental work that involved creation of IFB and SQL Loader scripts for batch as well as initial loads.



Responsible for designing EIM solutions for Accounts, Contacts, Employees, Products, Assets, Agreements, Entitlements Responsible for creation of unit test cases and executing the same Ensured that peer review and testing is done for all the modules developed & on- time delivery of modules Responsible for delivering modules as per the quality standards Worked on Workflows, Policies in order to automate requirements Worked on configuring Assignment Manager

• • • • •

7. CRN (Customer Restoration Network) Client: Farmers Insurance Group- CA - USA Duration : September 2002 to January 2005 Role: Project Manager Peak Team Size : 9 Execution Location: Offshore CSAT (Customer Satisfaction) Score: 4.8 Description: Siebel is part of Customer restoration Network. Siebel Application has been extensively customized to map the client’s requirement. Siebel is implemented in multi server architecture within an Enterprise with twenty five Siebel servers installed, with each server installed in dedicated machine. Server Components like Workflow and assignment manager are enabled only in particular servers to increase the availability and processing. CRN supports nearly fourteen thousand clients out of which four thousand are mobile clients and the rest are dedicated clients. Siebel has been integrated with legacy systems and external applications/systems, all the transaction with the Legacy systems are synchronize transaction, which was achieved through the middle ware MQ Series. CRN has been implemented with functionality like Loss Reporting, agent initiated loss reporting, claims entered through farmers website, claims initiated through Fax/Mail, Claims Investigation, Coverage Verification, Reserves, Payments, salvage, Diary Management, Claim Closure & Reopen, Subrogation and Management Reporting. Contribution: As a Project Manager was responsible for

Rsmt.Ford0856Nov01.doc

• • • • • • • • • • •

Responsible for daily CRN Siebel Production Activities. Responsible for Remote Database Extracts. Study the ‘As-Is’ Processes & understand the Business & User Requirements. Daily Monitoring of Subrosource Activities. One point of contact for all the Siebel Offshore Deliverables. Daily Work Allocation to team members. Responsible for Quality of work delivered by offshore. Weekly update of performance & Issues to onsite Client Managers on Status call. Maintaining minimum Backlog of Siebel Production Tickets. Resolve the daily production problems in Configuration, Remote Client Synch, and Application Admin & Workflow Administration. Done root cause analysis for the problems and notify the development team to fix or give work around to the problem.

Page 6 of 8



IPAT task creation / Monthly PDMR Generation for the team.

8. Interim Branch Platform Client: Bank of Hawaii, Hawaii, USA. Duration: September 2001 to December 2001 Role: Siebel Consultant Execution Location: Onsite Team Size: 5 Description: This project facilitates in opening various Customer & Corporate Accounts. This was implemented using Siebel Financial Services Module, which automates the account creation process, opportunity creation for the respective CSR and Account details were generated in a predefined format using Actuate Reports. As a Project Lead was responsible for • Identification of Customization requirements. • Preparation of Customization specification document & Implementation Document. • Configuration & Environment setup of Siebel Financial Service application using Siebel Tools. • Creation of Object definitions such as BO’s, BC, Applets, Find Object, Views, Screens in the application. • Creating New Table, Extend the Existing Siebel Schema as per the Requirement. • Preparing test plans for Unit testing • Process mapping. • Prepare Technical & User Manuals. • Provide User Training • Bug Fixing

Industry Experience Wipro Technologies, India Role: Project Manager Duration: October 2000 till date Advanced Technologies Labs, Chennai - India Role: Component Developer Duration: October 1998 - September 2000 Excella Software Technologies, Bangalore - India Role: Programmer Duration: August 1997 - September 1998 Leela Scottish Lace, Bangalore - India

Rsmt.Ford0856Nov01.doc

Role: Production Executive Duration: August 1996 - August 1997

Page 7 of 8

Academic

Rsmt.Ford0856Nov01.doc



Bachelor of Engineering (B.E) - M.S.Ramaiah Institute of Technology, Bangalore University. (1996)

Page 8 of 8

Related Documents

Resume Vijay
November 2019 13
Resume Vijay
November 2019 12
Vijay Resume[1]
June 2020 6
Vijay Resume[1]
April 2020 9
Vijay Kumar Resume)
June 2020 4