Professional Documents
Culture Documents
Page 1 of 8
Selected Few Project Details:
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.
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
Rsmt.Ford0856Nov01.doc
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.
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
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
Rsmt.Ford0856Nov01.doc
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.
• 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.
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.
• 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.
Rsmt.Ford0856Nov01.doc
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.
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:
• 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
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.
Rsmt.Ford0856Nov01.doc
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
• 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
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:
the problem.
Page 6 of 8
• IPAT task creation / Monthly PDMR Generation for the team.
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.
Industry Experience
Wipro Technologies, India
Role: Programmer
Duration: August 1997 - September 1998
Page 7 of 8
Academic
Page 8 of 8