SKILLS HIGHLIGHTS:

Project Management Tools: MS Project 2010

C.A.S.E. Tools: ERWIN 9.6, Oracle Designer 6i, Knowledgeware ADW, IEF/Composer

DBMS: Confidential 15, Oracle 9.0.1, SQL Server 2000

Data Warehouse Tools: Informatica Power Mart 5.0, Oracle Express, SQL Server OLAP

Programming Lang: SQL, TSQL, PL/SQL

Specialty Skills: Data Warehouse Design, Data Architect, Data Modeling, Data Quality, Data Warehouse Project Management, JAD, Process Modeling

PROJECT EXPERIENCE:

Confidential

Responsibilities:

• Performed the role of lead data modeler/ data warehouse architect for an Confidential project with Confidential .
• This was meant to be a short assignment to explain Confidential ’s Oil & Gas Logical Data model.
• After the two weeks Confidential asked that I replace their data modeler employee for the remainder of the Phase Data Modeling.
• Performed the role of lead data modeler/ architect for the initial implementation of the Enterprise Data Warehouse.
• The data modeling involved the integration of data captured directly from SAP ECC into a 3rd Normal form for the Confidential platform.
• The migration was handled by the Confidential ’s Confidential product. In addition, I was mentoring and assisting various client employees in data modeling, data architecture, and enterprise data architecture aside from the data warehouse project.
• The EDW database was Confidential 15.0 and the data modeling tools were Erwin and Power Designer.
• Consulted on the EDW architecture which combined one company’s SAP ERP implementation with a JD Edwards implementation into a Confidential SAP product which was modeled from Confidential ’s Manufacturing Data Model.
• The modeling enhancements and mapping activities from the JD Edwards source were integrated into the target physical data model.
• The EDW database was Confidential 14.0 and the data modeling tool was Erwin.

Confidential

Responsibilities:

• This assignment was a weeklong engagement with a Confidential client to review their Enterprise Data Warehouse architecture, framework, and processes.
• The engagement was paid entirely by Confidential with the specific condition that no other Confidential employee would be part of the process including sales representatives.
• Developed Confidential ’s Oil & Gas Logical Data Model. This product modeled Oil and Gas business areas from Upstream (survey, drilling, and extraction), as well as, Midstream (distribution). The model’s sales documentation and educational artifacts were developed in conjunction with corporate policies.
• The EDW database was Confidential 14.0 and the data modeling tool was Erwin.

Confidential

Responsibilities:

• Developed Confidential ’s Health & Human Services Logical Data Model. This product’s initial business area was focused on all Medicaid data for analytic discovery by Confidential .
• Due to some significant modeling objects, the model was expanded into the Health and Human Service business area of which the Medicaid data was a subset.
• The model’s sales documentation and educational artifacts were developed in conjunction with corporate policies.
• The EDW database was Confidential 14.0 and the data modeling tool was Erwin.
• This assignment’s role was the Tester of data inserted into the EDW.
• Developed a Testing Strategy which was coordinated with the Enterprise Test Strategy.
• There was no data modeling or database design involved in this engagement.
• In the later phase responsibilities expanded to be the primary data warehouse consultant on the ETL and Semantic layers.
• Evaluated the main Enterprise Data Warehouse Structure against three new systems.
• The result of this engagement was an initial analysis identifying the positive aspects and obstacles of the new system integration capability.
• This assignment involved customizing Confidential ’s Retail Logical Data Model to include major Pharmacy data areas. The data to be modeled also was interconnected to the POS system within the other business areas. There was a second engagement which was a critique and remodeling effort of the Time Assessment and Capture in the key functional areas. The EDW database was Confidential 12.0 and the data modeling tool was Erwin.

Confidential, MN

Responsibilities:

• Create Logical/Physical Data Model for a Membership subject area in several OLTP applications.
• Assisted Data Architecture team in redefining major components of the business to accept emerging Service Orientated Architecture (SOA).
• In addition, created a strategy for the major component migration.

Confidential

Responsibilities:

• Assisted the Data Quality Team comprised of senior level managers in developing the framework and requirements for a Data Quality organization across the enterprise.
• Once the framework was developed, I mentored the data quality team in identifying processes that would support the next phase of the Enterprise Data Warehouse.
• Worked with the Data Acquisition Team and individual Data Mart Teams in techniques to collaborate the overall data quality efforts.

Confidential

Responsibilities:

• Build an Enterprise Logical Data Model for the large retail firm.
• Working with Business Units that are re - engineering the Business, I was responsible for designing and validating the Enterprise Logical Data Model.
• In addition, assisted the Application, OLTP, and Data Warehousing teams in the customization of Confidential ’s RLDM for the new Data Warehouse design, as well as, working with an Confidential team to customize a Master Data Management tool for the Product Category area.

Confidential

Responsibilities:

• Worked as the Data and Technical Architect for the final phase (Reports and Letters) of a HIPAA implementation for the Confidential of Michigan.

Confidential

Responsibilities:

• Design all data models for OLTP and Data Warehouse environments.
• In addition, design, development, and implement a billing ETL application.
• This required the design of the SQL Server Database and coding of all stored procedures and triggers.

Confidential

Responsibilities:

• Assisted the company’s staff in creating an Enterprise Data Repository.
• Worked with multiple internal divisions including Finance, Marketing, and Compliance to reverse engineer their existing database designs and create a new architectural structure that will accommodate enterprise-wide reporting requirements.

Confidential

Responsibilities:

• Developed an ODS and Dimensional data structures for a manufacturing group within HP Corvallis site.
• The data structures were designed to integrate with other Corporate designs and databases such Supply Chain, Human Resources, and Finance.
• I worked with the Oracle DBA in the reconfiguration of the OLTP, as well as, Data Marts.
• Performed as the project Lead for the ETL work, which was performed in Informatica Power Mart. In addition, led JAD sessions that resulted in the design of a Logical Data Model and a first cut Physical Database Design for another group concerned with tracking status across operations at the plant.

Confidential

Responsibilities:

• Provided technical advice on the development and implementation of the OSPI Education Information Enterprise Data Repository which integrated data across all school districts in Washington State.
• This advice includes the selection of tools for the data warehouse construction, establish a set of procedures and processes for manipulating data within a data warehouse environment, and tools used in querying data.
• Led a team that conducted several JAD sessions resulting in the design of a Logical Data Model and first cut Physical Database design for the ODS, which encompassed data from more than 200 school districts.
• Assisted the OSPI staff in the development and implementation of an agency data dictionary. In addition, provided OSPI with a long-range plan for the collection, storage, utilization and disposition of data.

Confidential

Responsibilities:

• Supervised all activities involved in the design, construction, population, and use of the Data Warehouse across all sub projects.
• Coordinating requirements with Product managers, Tech leads, individual developers, data modelers, and DBA's.
• Forecasted needs and set expectations for all phases and requirements. Developed overall architecture design of warehouse components, as well as, integrating third party applications, their associated data, and requirements into a Web based environment that was reaching rural America.
• Led or supervised JAD sessions that involved both Customers and Product Managers.
• Implemented the data architecture as an enterprise wide Logical Data Model across all OLTP application data to support the future ODS structure and represent the Enterprise Wide business rule set.
• In addition, lead a small team in the deployment of a data mart utilizing an Oracle 8 database, which was migrated to a SQL Server OLAP platform. Star schemas and OLAP cutes were designed and implemented which allowed data to be distributed as an XML/Chart F/X application over the Web.

Confidential

Responsibilities:

• Designed Data Mart/ Data Warehouse for multiple projects within Confidential using concepts such as Star Schemas and Snowflake database arrangement, as well as, fourth and fifth normalized form.
• Coordinated the data modeling design to integrate with other projects database design and validate the existing Data Model for the Corporate Data Warehouse.
• Designed and coded a Multi-dimensional cube for OLAP processing using Oracle Express toolset and PL/SQL.
• Developed the framework for using Pinecone Products within the various data warehouses and data marts.
• Collaborated with the DBA team in developing strategy for partitioning tables and insuring referential integrity.