1. MoBile: +91 88615 33469
+91 9573 890999
eMail: sriraaji.sana@gmail.com
Experience Summary:
10.5 years of experience as Architect, Consultant, Solution Designer, Pre-sales(Up-selling & Cross selling competencies),
Architect, Designer in Master Data Management, Data Quality, Data Migrations, Data Analysis, Data Modeling, Data
Profiling, Data Mining and of Requirement gathering & analysis, Development, Implementation, Support & Maintenance
and Post-Upgrade tasks.
MDM Architecture experience: Initial Data & Data Quality assessment, Assess landscape & technology, capturing current
data practices, Identify business opportunities, Map solutions capabilities, Identify Project & business sponsorships,
Defining conceptual data models, building road maps, defining conceptual solutions, evaluating tool options , Defining
data governance model, defining migration strategies, Proof of concept, technical architecture, defining data
stewardship model, Incremental rollout, balancing global/local requirements, Data governance rollouts and change
request & enhancements
Sl# Organization Designation From To
1 IGATE Architect 21-Aug-2014 11-Dec-2014
1 Wipro Technologies Architect 02-Nov-2011 30-Apr-2014
2 Sierra Atlantic Package solution consultant 17-Nov-2009 07-Sep-2011
3 IBM India Pvt ltd Package solution consultant 06-Aug-2008 13-Nov-2009
4 Oracle India Pvt Ltd Staff Consultant 04-Jan-2007 01-Jul-2008
5 Cognizant Technology Solutions Technical Analyst – CRM 06-Jan-2006 28-Jul-2006
6 GENPACT(Phenomena) Associate Consultant 16-Feb-2004 30-Dec-2005
Skills Summary:
MDM Tools Data Quality ETL Programmi
ng
Languages
Integration DataBas
es
Business
Appliacatio
ns
Page 1 of 20
2. Informatica MDM IDQ Informatica Java XML/Webservices IBM DB2 Siebel CRM
IBM MDM IIR IBM –
DataStage
J2EE WSDL/SOAP Oracle
Oracle MDM IBM Quality
Stage
BOA - Cransoft e-script Integration
Workflows
Sybase
Siebel UCM ISS Oracle
PL/SQL
Domains & Industries
Banking & Financial Telecom
Marketing e- Sales
Pharma Dealer
Automotive Communications
Manufacturing Aerospace
Healthcare
Education
M.B.A Kakatiya University Year 2003
B.Sc Computers Kakatiya University Year 2000
Professional Experience:
Project 1: Business Evaluation & Solutions
Duration: 50 days
Responsibilities:
• Mobilization and initial assessments, Assess Current state & Future state models, Gap analysis and develop
future state road maps.
Page 2 of 20
3. • Understand Data Integration maturity, strategy& program management, Life Cycle of Businesses involved.
• Identify impact of MDM, Data warehousing appliances, In-memory computing systems, Document
Management, Data Lake, Data Virtualization, Data Quality and Complex event processing. strategy on existing
systems; finding gaps.
• List out Quick wins and risks and develop high-level plans. Presentation.
Project 2: Millicom - South America Region
Duration: Jan 2014 to April 2014
Job Profile : Solution Designer – Data Migration
Role – Consultant
Responsibilities:
• Expand on the Data Migration strategy provided during Blueprinting phase
• To provide sequence of Activities required to complete data Migration in agreement with all three countries
• Identify stakeholders for data corresponding to each functional area
• Define the deliverables for the implementation team
• To provide a resource plan for all stages of the implementation including roles, responsibilities and when
Performing Extraction and Cleansing strategy, Cut Over proposal , Acceptance Criteria for Migration, Resource
• Plan identifying required roles and time all resources are required, Migration activities execution plan, CBS data
structure / requirement understanding
• Migration Requirements Include AS-IS applications understanding, Application mapping preparation, Application
level mapping between AS-IS and TO-BE, Acceptance criteria finalization, Historical requirement finalization,
Reconciliation requirement understanding
• Migration Strategy activities including Extraction, Cleansing, Transformation and loading approach, Exception
Handling and Reconciliation framework, Cut-over strategy, Rollback strategy, Staging environment
recommendations, Cut-over strategy, Rollback strategy, Staging environment recommendations
Project 3: Lloyds Banking Group IBM M.D.M WCC v10.1 Wipro
Duration: Aug’ 2013 to Jan'2014
Environments: Microsoft Active Directory, IBM FileNet P8,BPF & Custom UI, IBM Web sphere, Message Queue, IBM
Web sphere Message Broker, IBM Web sphere Customer Center, Oracle 10g
Page 3 of 20
4. Role – Technical Manager
Team: 45
The COM CMD is a strategic application portfolio for the bank, which is serving for corporate & commercial
customers, has experienced a significant increase in delivery demand. The Core Business Functionalities includes
1.Creating Non Personal Legal Entity (NPLE) and Personal Legal Entity (PLE), 2. On-boarding process includes approval
and verification of a new customer to Bank, 3. Maintenance process includes updating of information in ongoing
KYC/KYB Compliance, 4. Business processes associated with closing, 5. Closing Prospect when an opening Case is still in
progress or before an opening Case is initiated, 6. Closing Customer when after confirming that the Customer has no
active Product Holdings and that the Customer has no existing relationships with another LTSB Organisational Unit (OU)
& the customer is closed,7. Maintaining, adding, updating and removing legal entity relationships
It was experienced that the project deliveries have encountered number of barriers and missing to stay up to
commitments. One of them being-lack of programme attention and investment into the portfolio infrastructure. The
severely strained development infrastructure, limited SME base and delayed ADM engagements for key regulatory
programs has brought a need for a rapid ramp up of skill base, environment provisioning and delivery of prioritized
programs
The key objective of this pack is to appraise the stakeholders on the approach being taken by ADM customer
team so far for the current 2013 project delivery roadmap and seek assistance /support/ contributions as appropriate
from stakeholder in order meet the commitments in the bank.
Responsibilities:
• Leading the entire development team, responsible for the Code Reviews & development
• Examining software requirements, preparing project documents.
• Coordinating interdependent changes, revision of scope.
• Channeling team effort into activities.
• Preparing PDMR(Project Data & Metrics Report), RLS(Resource Loading Sheets), Detailed project plans, high
level plans and effort, resource and Delivery trackings.
• Involved in requirement gathering process along with SME and reviewed requirement documents.
• Reviewed IA,MLPD,LLD,Functional & Technical Design documents
• Defining each project’s scope; developing business requirements; determining priorities; implementing
project plans; assessing risks; vendor evaluation; and monitoring schedules, resources and costs on a Per-
Page 4 of 20
5. project basis through product launch
Project 4: Ansell Healthcare LLC
Duration: Feb’2013 to April’2014
Environment: MDM, Informatica’s multi-domain hub
Role – Information Architect
Ansell Customer is a global leader in protection solutions, with operations in North America, Latin America, Europe
Middle East and Africa, and in the Asia Pacific. Business Segments include Industrial GBU, Medical GBU, Specialty
Markets GBU, Sexual Wellness GBU of major Product Categories: surgical, examination, industrial and household gloves
and protective clothing,
The business and operations data managed across Enterprise Oracle Applications: Oracle Siebel CRM, Oracle Siebel Sales,
Oracle Demantra, Oracle E-Business Suite, Oracle Business Intelligence Enterprise Edition (OBIEE), Oracle VM Virtual Box,
VMware vCenter etc.,
The aim of this project was to implement a corporate wide Master data governance and MDM
solution across Customer, and Product domains. The expectations were to provide an easy to maintain, flexible and well
integrated solution with different current and future ERP, CRM and DW
solutions
Responsibilities:
• Requirement analysis , design , development , system integration testing , implementation , training and hyper-
care for product and customer master data domains
• Provide enterprise wide data governance strategy and roadmap for customer and product master data domains
• Understand as-is Ansell Business and IT processes , identify data issues & provide implementation approach for
a comprehensive data governance and MDM solution
• Build MDM Consolidation hub for customer and product master data domains
• Implementing Master Data Management and Information Exchange (MIX) architecture and is technology
agnostic.
• Developing framework in partnership with Informatica to address MDM challenges, Data Migration Factory and
Page 5 of 20
6. Wipro’s Accelerators for MDM Assessment
• Ensure better business insights across the organizational value chain. The need for accurate and consistent
product and customer master data through data governance, data quality and data integrity is intensified to
support multiple enterprise systems (ERP / CRM).
• Integration of Duns and Bradstreet with the MDM hub and Address Doctor for Address cleansing, Data
cleansing of customer and product data, Data Profiling for customer and product data
• Installation of the MDM tools in the DEV, UAT and PROD environment, Global roll out of MDM hub
implementation for customer and product, Unit and Integration testing with SW installation on DEV, UAT and
PROD
• Building architecture which takes into account the business model of Ansell and clearly demarcates the related
attributes to provide a proper global definition of product and customer, The Governance model encompassing
both the master data and enterprise related data, global hierarchy definition and data enrichment.
• Getting all stakeholders on the same page and signing off on the global strategy for Ansell - handled via global
workshops
• Getting a well defined business glossary in place – handled via separate focused meetings with customer teams,
focused discussions with QA team to trickle down the message for Getting a well defined hierarchy that was
applicable in the dynamic environment of M&A’s
Project 6: SASOL South Africa
Duration: 2 months
Environment: SAP MDM
Role – Advisory Consultant
Responsibilities:
• Current state assessment and profiling and Data Modeling for SCM application- Supply Chain Management.
• Establishing Data Governance mechanism, deployment of MDM as part of broader data governance program
involving combination of technology, people, policy makers and process management, following steps to
comprise the interactive process of implementing MDM solution.
• Determining the data domain and policy makers, establish and develop policy definitions, strategies, objectives,
metrics and revision processess.
• Engage with process executers to define data usage, management processes and protocols - for people,
applications and services- including how to store, archive and protect data(data security, application security).
Page 6 of 20
7. • Establishing in creating controls to process managers to enforce and monitor policy compliance, country
compliance and to identify policy exceptions.
• Establishing contact for Managing auditors review, access and report historical performance of the systems
involved, establishing governance and policy revision feed auditors reports in as enhanced part of MDG.
• Suggest implementing Master data management solutions to enhance data reliability and data maintanance
procedures.
• Establishing tight controls over the data imply a clear understanding of the myriad data entities that exist across
the organization, data maintenance processes and secure access to the usage of data.
Project 7: CITI-CMR IBM M.D.M WCC v10.1 Wipro
Duration: June 2012 to Jan'2013
Environments: Tibco Abinitio IBM MDM(WCC) Oracle DB Unix Environment
Role – Information Architect – Lead
Responsibilities:
• Responsible for the Design and the Mapping of the existing entities with that of the WSDL objects
• Identify functional and non functional requirement to do design reviews and suggest design
• Use a flexible multi domain data model that fits unique business requirements
• Perform requirement gathering, design review and architect solution. Increase agility and accommodate current
and future business needs by expanding beyond a single data domain, use case, and region
• MDM solutions implementation plans and solution run books to the client
• Suggesting best practice and alternate solutions for the applications
• Design and deliver project documents for maintenance and monitoring processes and procedures
• Leading the entire development team (TIBCO, ETL & MDM), Responsible for the Code Reviews.
Page 7 of 20
8. • Preparation of the Test Plans and Review of the Test Scripts for both Unit and Integration Testing.
• Accelerate and streamline MDM, data integration, and data quality projects by reusing business rules
Fine tune the application for better performance and scalability
Manage and Lead Infrastructure Support Project team
Manage solutions implementation, routine deployments, and enhancements, suggest patches and hot fixes.
Project 8: CHC HELICOPTERS , Canada
Duration: Mar' 2012 to June' 2012
Environment: AMOS 10.0 , LINUX 5.4, SYBASE 15.0.3, INFORMATICA 9.8
Role: Architect
CHC Helicopters is the parent and holding organization of Heli1 and other merged entities across the globe and
comprises disparate MRO processes and systems. To achieve optimal costs in terms of inventory, man power, facilities,
process standardization and improved customer experience, CHC is implementing AMOS MRO (Maintenance, Repair,
Overhaul) system. As part of Data migration, source/legacy systems data is extracted from AS00/DB2 application into
staging tables and flat files are generated to feed into AMOS using Informatica. Data Cleansing, Profiling and
Transformation logic implemented in Informatica Database.
As the AMOS application dealing with large set of data (200 G.B) and multiple parts of Aviation business entities
included (Majorly Address, Aircraft Parts, Aircraft Setup, Rotables, Aircraft Tree Definitions, Aircraft Data, Order
Management, Work orders, Maintenance Schedules, Maintenance Schedule, Receiving’s etc..) Fetching data for 190
tables across sources and feeding in for 130 tables of AMOS. Performance is affected at every layer starting from
Extraction from DB2 and different layers of processing data in Informatica layer and Feeding the Data into AMOS and
AMOS application layer w.r.to Integrations taking huge amount of business time and cost w.r.to changes reflecting to
the Business Users and the Accessing the data.
Page 8 of 20
9. Responsibilities:
My role as an Architect to understand functional & Technical aspects included and analyzes the different systems
including applications, middleware, at the Database layers and system configurations. Come up with the optimization
solutions for Insertion, extraction, accessing, updating and manipulating data at staging, transforming and storing
levels.
Optimization of transactional SQL’s at the informatica – ETL level (Source code definitions, DB Check Errors, Look-ups,
Filter and Transformation conditioning scripts) to retrieve the data fast and to minimize the timelines while retrieving
data from source systems into ETL, as-is-ready for the next levels.
Preparation of reconciliation scripts to analyze the common errors, statistical and report generations, insights from the
team and stakeholders in-order not to lose important concurrent information & data and incorporate client decisions.
Project 9: SAP –BOA Data Assessment and Data Mapping,GE Lighting - SAP M.D.M Assessment
Duration: Nov'2011 to Mar'2012
Environment: BOA-Cransoft, MS SQL
Role: Project Lead
GE Lighting is embarking on an initiative to migrate its business processes across globe from diverse legacy applications
into SAP. This also involves migration of the master and transaction data from the legacy systems and loading into the
target SAP systems. The company has identified BackOffice tools as the technology platform for the data migration
activities. The primary objective of these data quality initiatives undertaken by the company is to establish an effective
data assessment, management and governance strategy. This project will endeavor to leverage the BackOffice (BOA)
toolset across the company ERP implementations and effectively manage the data migrations/conversions as well as
standardize and improve the data quality.
Responsibilities:
Page 9 of 20
10. Understand source systems for various objects, Understand business rules / migration specifications for objects In Scope
and Understand and analyze business objects (e.g., attributes, tables, relationships) between new system and legacy data.
Define conversion specifications.
Build assessment rules and execute data quality assessment, Generate data quality reports and support GE Subject
Matter Experts (SME) / Black Belts to conduct workshops
Identification and finalization of the data objects to be migrated, Identification of the legacy data to be migrated and
understand the target data object template structure.
Data migration approach, Detailed design document.
Data assessment reports using BOA tool(s) (e.g., DSW). Data assessment reports for objects with GE SMEs and assist in
workshop.
Load object source data files in predefined format into staging area (Data Garage). Creation of data migration template
(Source to target Mapping Specification).
Transform data migration completed templates into eZMap, Integration of value mapping and field mapping with DSW.
Data object dependency model, Build conversion, loading and validation routines and Prepare unit test plans, test cases.
Project 10: Siebel UCM & MDM Implementation F5 Networkds, Seattle, WA
Duration: Feb 2010 to Nov'2011
Environment: Siebel UCM 8.1.1.1, SAP Business Objects DQ XI 3.2, Oracle 11g, Oracle Fusion MDM PIPs.
Role: Solution Architect – MDM Implementation
Team Size: 12
F5 Networks operating business in Application Delivery Networking and having multiple applications in supporting
business using Oracle EBS, SFDC, Clarify CRM, Siebel CRM and Neolene. This Project intended to integrate all these
applications via Oracle Fusion – MDM PIPs into Siebel UCM, to have as single source of truth, and deploy as centralized
and unified customer & Business unit data to the source applications.
Page 10 of 20
11. Responsibilities: My role as Solution Architect
• Assessing customer needs and prioritize utilizing a structured requirements gathering process (gathering,
analyzing, documenting, and managing changes), Involved in the Initial thought process for Porting the
systems and Participating in Technical and Non-Technical discussion with Client Teams
• Aspects of customer servicing at different phases of the life cycle, Elicit and document High-Level Business
Requirements
• Involving in Design and Implementation strategies and Analyze & Preparing Project Plans, solution designs, Elicit
and document Detailed System Requirements, Designing the development strategies.
• Create Project specific documentation as needed (i.e. Use Cases, Gap Analysis, Report Specifications, Test
Plans/Test Cases)
• Analyzing the data with given requirements and articulating the business logic, Analyzing data through
relational and non-relational source systems, Convey data models with requirements by giving dimensions and
facts for the model and Articulate the business logic in data base query language
• Conduct walkthroughs with stakeholders and obtain sign-offs
• Create and document the Requirements Traceability Matrix, Work with technical resources and share business
knowledge to assist in solution generation
• Review Technical Design documents and Test Plans, Participates in Technical Design Review to ensure that
requirements are met
• Resolve or escalate requirement related issues that arise during construction and Act as a liaison between the
business customer and the IT technical team
• Designing the Conceptual data model for Siebel UCM, Involved in Design and Implementation of the
Interfaces, Interpreting Real-time integration strategies with the source systems
•
Preparing Estimations & Tracking, Work breakdown and deciding on timelines.
•
Conducting sessions for the team to understand the requirements and performance requirements for the systems
and Involved in Performing various proof of concepts.
Project 11: Siebel UCM (Universal Customer Master) -8.1.1 EMAAR – DUBAI
Duration: Nov' 2009 to Feb'2011
Page 11 of 20
12. Environment: Siebel UCM 8.1, IRR DQ, Siebel ISS Informatica 8.6.2, Informatica DQ 8.6.2, Oracle 11g(for repositories)
& 10g(for Informatica Staging Environments), Linux/Unix O/S
Role: Technical Lead Siebel UCM (Implementing Siebel UCM).
Team Size: 7
This project is aimed to Implement & automate the integration of Customer data across various Emaar International &
Dubai’s business systems (Hospitality, Properties, Malls, Education and Healthcare) into centralized and unified data
repository to integrate and to provide accurate customer data/deploy non-disruptively and transactions without the
need to reengineer existing applications and databases.
Responsibilities:
My role as a Sr.Technical Business analyst involved in gathering & analyzing business requirement in initial phase to
implement external systems data into Siebel UCM application by having day to day meetings with the various business
people from EMAAR and analyzing the source systems data.
• Preparing Requirement analysis document, Functional Design Documentation, Technical Design Document
preparation and Proof of Concept documentations to better go with the EMAAR business requirement into
Siebel UCM Implementation.
• Driving the Workshops and derive the Usercase/Functional Specs.
• Functional Specification and Configuration and design experience in Siebel product.
• Prepare, Present the User training manuals during the deployment phase.
• Coordinating Onsite-Offshore assignments implementing Siebel UCM and Informatica ETL Team in Phase 1
design.
• Working on implementing the Siebel UCM Data base Extensions, BC Extensions, Creation of IO/IC’s, creating the
Integration Workflows, BDM workflows for routing the data from Source systems into Siebel UCM(Inbound Data
Flow) and from UCM data to externals systems (Outbound Data flow).
Page 12 of 20
13. • Creating IFB files, invoking ISS(Siebel DQ) components in Integration workflows to generate matching, cleansing
rules and appending survivorship rules for incoming records.
Project 12: Siebel UCM (Universal Customer Master) - AVAYA – USA
Duration: 1 year
Environment: Siebel UCM 8.0, Oracle 10g, Linux/Unix O/S
Role: Lead Developer – Siebel UCM (Implementing Siebel UCM & Production Support for UCM)
Sr. Business Analyst (Data Analysis Support Team)
This project is aimed in Implementation and Production Support for Siebel 8.0.0.1 Universal Customer Master
Application for AVAYA – USA.
The Project aimed in implementing the Integrating Siebel UCM with seven external applications
Namely SAP’s, Partner Application, Sales Force Dot Com(SFDC), Siebel Ticketing application, Siebel Call Center
Applications, PLD, CXP and MDM.
Oracle's Siebel Universal Customer Master (UCM) is a comprehensive customer data hub that unifies customer data
across multiple business units and functionally disparate systems.
Responsibilities:
As Part Implementing Siebel UCM for AVAYA, I am involved in Developing Interfaces (Batch & Real Time) which support
importing external databases & Data into Siebel UCM Applications and publishing Unique records from UCM to
registered external applications via JMS Transport to ALSB.
• Involved in Data Modeling, Creating Integration Objects, and Integration Components for Outbound, Data
Conversion, Integration Workflows, Data Mapping, along with Web Services (Inbound-Outbound).
• Driving the Workshops and derive the Usercase/Functional Specs.
• Functional Specification and Configuration and design experience in Siebel product.
Page 13 of 20
14. • Prepare, Present the User training manuals during the deployment phase.
• Data mining activities include understanding and implementing external applications databases and combing
them in compatible for maintaining data into UCM, Developing Siebel Workflows in order to implement the
logic to maintain single unique record into UCM applications.
• Scheduling & Monitoring Continuous Daily Batch Loads from External Systems into Production UCM Application,
which include rigorous implants of components and Tools which are used to Schedule and to monitor using
Informatica ETL Tool. Siebel Workflows, Siebel components and Oracle PL/SQL Scripts.
Project 13: Data Migration – Vodafone - Spain
Duration: 5 months
Environment: Siebel 8.0, Data Stage 8.0, Oracle 9.2 and Windows 2000
Role: Sr. Application Consultant
Vodafone Group Plc is the world's leading mobile telecommunications company, with a significant presence in Europe,
the Middle East, Africa, Asia Pacific and the United States. One of their IT solution implementation is Siebel
implementation for their Spain division. Currently the project is in Design phase of 1B where in number of new
functionalities are being identified and implemented.
Responsibilities:
• Involved in analyzing the functional requirements.
• Preparing the test specification and Program specification documents for the respective interfaces.
• Designing and creating the Data stage parallel jobs to load the flat file data in EIM tables.
• Designing and creating the Data stage sequence jobs.
• Designing and creating the Data sets.
• Preparing and testing the .ifb files.
• Running the EIM server component on Windows, Unix Siebel Servers to load the data into base tables.
Page 14 of 20
15. • Managing the error handling techniques in the Data stage Area, EIM Tables loading Stage and EIM process as
well.
• Logging the errors into errors table.
Project 14: Siebel UCM VMWare UCM Implementation – Palo Alto, CA, USA.
Duration: 1.5 years
Environment: Siebel UCM 8.0, Oracle 10g, Linux/Unix O/S.
Role: Offshore Team Lead – Siebel UCM Implementations
Team Size: 5
Siebel Universal Customer Master (UCM) is, briefly the ability to create and maintain unique, complete, and accurate
customer information capturing a comprehensive set of customer attributes (including demographic information), as
well as information on previous interactions, purchases, and privacy preferences.
The Objective of the Customer Master project is to provide a complete and accurate view of the customer by taking the
best customer related attribute values from the participating applications (CRM, EBS, PRM, and MYLEARN) and perform
cleansing, matching and applying survivorship rules to create the best version record in UCM from Bulk load and real-
time messaging.
Responsibilities:
I have involved in developing EAI Integration Workflows, Integration Objects, Integration Components, Custom Business
Services, Data Conversion, Data Mapping and Application Services Interfaces.
Also I involved in developing EIM Interfaces Tables, Creating Control Files to load external system data into Siebel
Interface Tables, Created IFB files for data load part into SDH Tables, Created Batch Data Management Workflows in-
order to invoke Data Quality Components make a record Cleanse, Matching and Created UCM Survivorship rules to
Inserting/Updating Accounts, Contacts and respective Address records into UCM, and dispatching them to registered
external applications.
Page 15 of 20
16. I actively involved in Application performance tuning by building/dropping custom Indexes so as to make application
performance speeder.
Project 15: Siebel e-Pharma Implementation - Shire Nuclious - UK
Environment: Siebel 8.0, Oracle 10g.
Role: Siebel Consultant.
Data Migration & Interfaces for Siebel e-Pharma solution for European Pharma Company.
This project is aimed to Implement Siebel 8.0 e-pharma Siebel Application for UK, Ireland regions, where the existing
non-Siebel Application data converted into Siebel Application data using Oracle 10g PL/SQL and Siebel EIM.
Description: C&C is the name for SHIRE NUCLIOUS sales force automation (SFA) and Sales Analysis tool that is being
designed to support common selling activities, and processes that the sales force engages in, while interacting with
customers.
The Existing Data for all these countries need to be migrated into the Siebel Database used by C&C. Data Migration will
only be done as a One Time Activity during initial load. Data Entities for the various countries will be migrated into the
Target Siebel Database:
Responsibilities:
The entities which I’ve worked on Siebel 8.0 E-Pharma Applications are: Contacts, Accounts, Activities, Regions, Bricks,
LOV’s, My Daily Armin’s, Territory Structure, Addresses, Targets and Specialties
The Customer Data Provider will upload the files in the file server (I-PROJECTS) through FTP. The scheduling mechanism
will continuously poll the pre-defined path in the file server. On receiving the files, the scheduler process will start the
Data Load sequence into Temporary Data base tables (Staging Area) loaded through SQL Loader than to EIM Tables
through SQL Pl/SQL procedures Scripts. After data has been populated into the target tables (EIM tables), the EIM
process will be fired and the corresponding Siebel destination base tables will be loaded. All error handling will be
managed in the Temporary Tables Staging Area, EIM Tables loading Stage and EIM process as well.
Project 16: Siebel Upgrade project from Siebel 7.5x to Siebel 7.8x - GPM Funding, Inc.
Page 16 of 20
17. Role: Siebel Consultant
This project is aimed to upgrade the existing Siebel 7.5.3 application to Siebel 7.8.3. This implementation mainly focused
on implementing Web-based, clients for Ease of application deployment, Simplicity of maintenance. Also this improvises
the existing functionality to meet the growing needs of client.
Responsibilities:
• Identified the Data required and Interface tables required for loading the Data into the Siebel Database.
• Populated the interface tables and performed data mapping, Used Sql*Loader to stage the data.
• Finding the differences between 7.5x Data model with 7.8x data model.
• Configuration of EIM process, data loading in EIM tables and import of data to Siebel using EIM process.
• Performed Import and Update Operations.
• Configure and optimized the .ifb files, Created EIM Server task, set the Configuration parameters.
• Preparing Technical Design Document on EIM.
Project 17: Siebel 7.7 Siebel e-Dealer 7.7 & Siebel e-Automotive 7.7 Oracle PL/SQL - GM-InTouch –Canada.
Environment: Siebel 7.7, Oracle9i
Role: Siebel Consultant
The project deals with Data Migration and Interfaces support for CRM solution using Siebel Automotive Applications to
cater to the Canada operation of the Client. Client’s system will import and export data from and to a single source- the
Client’s Enterprise Data Warehouse (CEDW).
Interfaces load vehicle sale data, such as new Smart Lease or Purchase / finances as well as consumers information. This
data facilitates the customer retention program in inTouch. Leads from gmcanada.com and from customer surveys /
auto –shows are also downloaded, to drive new sales.
InTouch also exports data to the CEDW on a regular basis. Customer data captured from dealerships and lead / retention
touch points completed by dealership staff related to a lead or retention, are sent back to the CEDW nightly.
Adhoc interfaces exist for different purposes. Bringing on a new dealer into InTouch, loading purchase / finance data for
Page 17 of 20
18. a dealer, or requesting data from another dealership (also known as dealerization) are some examples.
Each interface, generally extracts data from CEDW, performs transformations, and loads this data into the EIM tables.
Siebel EIM is the program used to load data from the EIM tables to the Siebel base tables.
Interfaces use the staging environment to conduct the extracting, transforming and loading of data. This staging
environment is a custom build environment that also manages logging and control data.
Responsibilities:
• Significant reduction in the time taken to resolve a Service Request
• Enhancing Customer Experience by in time resolution of their queries and due escalation in case of deviations.
• Assistance to business users in User acceptance testing and Regression testing
• Data change management like Data Loads, Data Deletes, Data Updates
• Design and delivery of Maintenance releases.
• Change Request Analysis for feasibility, impact and effort.
• Preparation of functional and technical design documents based on the client requirements.
• Preparation of SMTD (System Maintenance Technical Documentation)
• Implementation of the change requests and defect fixes using Siebel Tools.
• Effective offshore co-ordination
Project 18: Siebel e-Pharma implementation for European Pharma Company: PFIZER, UK
Environment: Siebel 7.7, Accential DataStage 7.5.1.A Oracle 9i.
Role: Technical Analyst – CRM
Siebel Implementation project, where the existing non-Siebel Application data converted into Siebel Application data
using Accential Datastage and Siebel EIM.
Description: ECMS stands for Electronic Customer Management System and is the name for Pfizer’s PGP sales force
Page 18 of 20
19. automation (SFA) and Sales Analysis tool that is being designed to support common EuCon selling activities, and
processes that the sales force engages in, while interacting with customers. The Pfizer ECMS system is based on the
Siebel software.
All the countries that will be using the ECMS Application. The Existing Data for all these countries need to be migrated
into the Siebel Database used by ECMS Application. Data Migration will only be done as a One Time Activity during initial
load. Data Entities for the various countries will be migrated into the Target Siebel Database:
1. Master Data 2. Customer Data 3. Activity Data
The Customer Data Provider will upload the files in the file server through FTP. The scheduling mechanism will
continuously poll the pre-defined path in the file server. On receiving the files, the scheduler process will start the
Datastage job sequence. The data will flow from the Provider Data Area to the Target Data Area via the Staging Area. All
transformation logic will be handled within Datastage. After data has been populated into the target tables (EIM tables),
the EIM process will be fired automatically and the corresponding Siebel destination base tables will be loaded. All error
handling will be managed in the Datastage as well as EIM process.
Project 19: Siebel e-Sales Maintenance and support
Environment: Siebel 7.5, VB and Oracle.
Role: Technical Consultant
The project is aimed to support the Siebel e-sales application. The data needs to be synchronized with Siebel. Portfolio
data is extracted and stored in a network location. The delimited text data is then loaded into Siebel interface tables by
running oracle utility SQL Loader and/or VB Script. SQL Loader and/or VB Script control files process the data in each of
the file and loads it into respective interface table’s process is executed on the interface tables to load data into base
tables.
Responsibilities:
• Data change management activities like Data load, Data cleanup, Data extraction, Data reassignment, Data
Updates etc.
• Loading Bulk Amount of Data Inserts, Deletes and Updates using EIM.
Page 19 of 20
20. • Preparing IFB files based on the requirement.
• Trouble shooting of EIM Problems.
• Performance Tuning of EIM.
• Scheduled execution of batch programs for data clean up and business purposes.
Project 20: Siebel 7.5 Application Enhancements and Support Project
Environment: Siebel 7.5, Siebel Tools, and Oracle.
Role: Technical Consultant
This project involved providing Enhancement support to Siebel eBusiness solution developed and implemented to
increase sales productivity through utilization Sales Process
Responsibilities:
• Configuring Views, Screens, Business Objects, Business Components, MVLs &MVGs, Shuttle Applets.
• Drill Down, Toggles and Configuring Applets.
• Creating New Users
• Creating New Positions for Users
• Creating Responsibilities
• Assigning Positions and Responsibilities to Users
Page 20 of 20