SUMMARY:

• I have excellent communications and interpersonal skills with proven effectiveness in project leadership, coordination, and teamwork. I have been successful in articulating a vision, creating implementation strategies, and then assembling and empowering a team to transform that vision into concrete business results has proven to be an asset as a goal oriented leader.
• I have extensive experience in designing and developing Data Marts, and Data warehouses. I have extensive experience in creating data models with over 200 entities using Erwin and ModelMart.
• I have hands on experience in using ETL tools, DSS tools, and data repository tools.

TECHNICAL EXPERIENCE:

Operating Systems: UNIX, DOS, Windows, MVS, VMS, Windows NT.

DBMS: DB2, Oracle, and SQL Server, Siebel 7

Case Tools: ERwin (Model Mart); Visio, Bachman Data AnalysisERP/BI Tools Cognos; Impromptu, Power Play (OLAP) Cubes.

Hardware: Confidential PC and compatible, Confidential Mainframe, Confidential 4300, AIX - RS-6000, AS400, HP9000 Hardware platform

ETL Tools: Informatica; Ascential (Datastage)..

PROFESSIONAL EXPERIENCE:

Confidential

Data Architect

Responsibilities:

• Responsible for Enterprise wide Data Management services, Metadata, data standards, ODS, data mart, and data warehouse design. Worked with other modeling teams to ensure quality of support equaled expectations of business unites. Also interfaced with lines of business (LOB) to design, support, and analyze various data marts, warehouses and ODS’s.
• Developed conceptual and logical data model for data warehouse and marts.
• Identified data management view of data that is used Enterprise wide
• Identified data and process inconsistencies
• Participated in end user requirements sessions
• Gathered requirements for logical data model from user groups.
• Validated requirements with user community as each subject area modeled
• Provided support consistent with data modeling standards leveraging corporate and industry standards
• Maintain data standards, naming conventions, policies and metadata across the Enterprise on various
• Developed logical and physical data model using Erwin, Oracle databases.
• Develop transactional databases supporting several application LOB’s at Confidential .
• Identified metadata, data sources across enterprise and developed strategy for data access.
• Designed and developed Data models to access and query each database
• Work closely with the user community to analyze existing database schemas for effectiveness
• Worked to integrate existing models into one view of LOB’s data
• Developed ODS to capture data supporting internal and external clients supporting payments and other types applications
• All logical and physical data model were designed using Erwin, on Oracle or DB2 databases.

Confidential

Data Architect

Responsibilities:

• Maintain data standards and policies across the Enterprise on various projects
• Gathered requirements for logical data model from user groups and technical resources
• Provided data analysis, data model analysis of existing databases
• Designed new data model ODS for Package delivery data used to support Enterprise
• Data Warehouse and other data store houses
• Designed transportation data mart to provide tracking of On Time Service Measurements and Time and Transportation metrics for package deliveries
• Developed data model using Power Designer on a Teradata DB, Informatica.

Data Architect

Confidential, Middletown, CT

Responsibilities:

• Gathered requirements in JAD sessions for database design to capture data external from vendor Ingenix.
• Developed new subject area for Claims data mart and to enhance reports Claims reporting application.
• Created new data model subject area in existing Enterprise Data warehouse to allow tracking and analysis of patient lab results from external vendors.
• All data modeling was completed using Erwin modeling on a DB2 database.

Data Architect

Confidential, Michigan

Responsibilities:

• Providing data analysis and design support for the existing data warehouse
• Provided data analysis and design for Disease Management database
• Gathered requirements for logical data model from user groups
• All modeling was completed using Enterprise Analyst modeling tool set for a DB2 database.

Data Architect

Confidential

Responsibilities:

• Identified data management view of data that is used Enterprise wide
• Identified and tracked master data entities development Life - cycle
• Maintain data standards and policies across the Enterprise on various projects
• Identified data and process inconsistencies
• Worked with data owners/stewards to actively analyze and correct data inconsistencies
• Created document that identifies master data Entities and there relationships to each Line of Business
• Created data mapping document for data transfer by ETL developer
• Participated in end user requirements/Data Quality/Validation sessions
• Perform analysis on data required for Rochade metadata integration strategy project
• Gathered data to load in Rochade metadata repository for proofs-of-concept project
• Developed logical and physical data model using Erwin, Oracle 10.0.
• Develop conceptual data model of to be architectural direction for data warehouse.
• Gathered requirements for logical data model.
• Documented and validated requirements with user community as each subject area are modeled.
• Model is developed in Erwin.

Confidential

Data Architect

Responsibilities:

• Worked as Data Architect to develop a transactional database for member access to Pharmacy benefits information.
• Identified data sources across enterprise and developed strategy for data access.
• Designed and developed Data model to access Pharmacy benefit plan information.
• Data model requirements were developed in Use Cases.
• The database was designed to allow member to identify their Eligibility for Pharmacy benefits, identify member benefits and coverage, and identify Disease Interaction/drug dictionary look up, member ability to locate a pharmacy in geo area and review prescription history.
• DB2 V8 AIX, Power Designer Data Modeling Tool set.

Confidential

Data Modeler /Analyst

Responsibilities:

• Migrated data from current Data Systems of Record to the new databases created as part of the Siebel Desktop work stream. (Customer Integrated Data Store, Trouble Integrated Data StoreProduct Integrated Data Store and Siebel Desktop Application Data Store).
• Migrated/transformed data from existing legacy systems into new systems deployed as part of Siebel Desktop.
• Utilized the delta process to create test data for each of the environments to ensure synchronization between systems. Data Cleansing
• All types of customers were migrated to the new databases; synchronized between databases to allow for maintenance to occur in either the Siebel Desktop.
• Utilize data synchronization for application of deltas to Siebel desktop.

Confidential, Chicago

Consultant

Responsibilities:

• Managed both clients companies and candidates for perspective projects.
• Provided technical sales and account management support - assessed client needs, defined client requirements and identified solution.

Confidential, Chicago

Team Lead /Data Modeler

Responsibilities:

• Responsible for Enterprise wide Data Management strategy, data integrity, data integration, data standards, data mart, and the corporate data warehouse design. Interfaced with local and divisional corporate Information Technology teams to define processes and develop enterprise wide data management infrastructure. These efforts were done to create an Enterprise view of all corporate data including Metadata, intranet, extranet and data repositories.
• Work closely with the user community to analyze their data warehousing needs.
• Developed and established data management infrastructure, identify data relationship, identified internal and external data sources. Performed ERP tool selection for DSS, (Cognos OLAP, Business Object), ETL and Data Mining needs. Interfaced with other departments, Finance, Customer Care, Retail and Procurement. To identify their needs and develop plans going forward to meet any reporting or data analysis and reporting requirements.

Data Architect/Business Analyst/Data Modeler

Confidential, Houston

Responsibilities:

• Worked as Data Architect to develop a ODS and Data Mart for Energy services Company.
• Designed Operational Data Store (ODS) to capture data from internal (Siebel ) and external data sources, for reporting and analysis purposes.
• Designed database to allow for maturing of data over a period of time for each client while still in the sales cycle. The database was designed using Oracle and Erwin as the data-modeling tool.
• At the conclusion of each project facilitated knowledge management transfer from client project to Confidential KM database (Lotus Notes) for BI practice.
• Was brought on as a Business Analysis by the (M&A) Assessment team and assigned to take a detailed look at physical databases, data management strategy for the three companies.
• Interface with local and corporate Information Technology teams. Interviewed key personnel responsible for performing operations in Database support, Data Warehouse development-support, Decision Support and Data Administration. Reviewed each companies existing plans, documentation and supporting log reports that would give me an idea of the quality of services provided.
• Also gathered operations information directly from Perot Systems and EDS personnel concerning their Database support of Value Rx and DPS.
• Presented the Data Warehouse portion of the IS Assessment to Confidential IS management.
• Recommended a strategy on implementing an Enterprise-wide Data Warehouse, an Operational Data Store (ODS). A central Data Administration area and Decision support group with tools, training and staff that will enhance their ability to fulfill end users need for reports and access to analytical data.
• Designed and developed Data Architecture for an enterprise Data Warehouse of a large global chemical corporation. The warehouse, which was populated from SAP as well as from the company’s legacy environment, was designed based on design principles to ensure consistency and extensibility and was architected to facilitate the future development of data marts.
• Erwin Model Mart, data modeling tool was used.

Confidential

Team Lead/Data Architect/Data Modeler

Responsibilities:

• Data Architect for the development of a strategic enterprise data model, at a major pharmaceutical corporation. A working project plan was created and presented to management, using Summit as the corporate methodology.
• Created Data administration procedures, data naming standards and quality assurance guidelines were established, to be utilized across multiple divisions and internationally.
• This effort was undertaken to redesign of business support systems, capture critical information for needed for decision making, simplification of systems, eliminating systems and redundancy and integrate information to provide business value.
• Data modeling was done using ERwin/Open, for Oracle databases.

Confidential, Chicago

Data Warehouse Manager

Responsibilities:

• Developed a project plan to migrate data from legacy system to relational database.
• Directed an information delivery project designed to cleanup incompatible catalog numbering and asset tracking system. This effort is designed to integrate data capturing client sites and update current master files with the new data.
• Evaluated staff technical skill levels, define roles, project plan to retrain technical staff in relational database design, GUI programming techniques, case tools and client/server training. Managed and developed a data warehouse for sales/marketing division of a software development company. Gathered requirements and implemented Cognos (OLAP) technology based on solutions for end user community. Designed and develop reporting solutions, including cube creation, and performed development services for customers, including prototype programs.
• Directed frontline support and consultation for Cognos power users in the user community.
• Provided training for end user.
• The RDBM was Sybase 5.1 running on an NT server for the backend database.
• The data model was developed using Erwin, with its Repository Tool set.