Data Warehouse

Profile

A data warehouse architect recognized as a true business partner with the

ability to bridge the business-technology gap by building trust, focusing

on delivering business value, and developing techniques to meet the

business needs.

Technical Skills

SAP BW, ERwin, Oracle, SQL, TOAD, IIW (financial services model), DB2,

Access, Word, Excel, Visio, Project, COGNOS BI Suite, PowerDesigner,

OS/390, Informix, UNIX, InfoRefiner (ETL tool), Sapiens (RAD OO tool),

JCL, COBOL, FORTRAN.

Professional Experience

Confidential Princeton, NJ 2004-

present

Data Warehouse Architect

Defined the framework for capturing insurance data in a new data warehouse

in preparation for end user reporting.

. Facilitated data gathering requirement sessions. This task entailed

meeting with all of the business areas and documenting their business

processes and the data elements required to satisfy them, including

the business metrics. The final outcome was a business data model

that defined all of the business elements required for their reporting

needs.

. Performed data profiling steps of structure discovery, data discovery,

and relationship discovery to document data quality issues.

Relationship issues were documented by business metric volume. This

allowed the business to prioritize and address the most critical data

issues which affected their reporting results.

. Established naming standards for both the business and technical names

of data elements.

. Designed and modeled a multi-tier data warehouse environment which

included a staging layer for loading preparation, a transaction detail

layer, a transaction summary layer, and a business process cube layer

for reporting.

. Developed source to target mapping specifications which documented

source, staging and warehouse business elements along with the

business rules that applied to them.

. Designed and modeled the master data required to support the reporting

requirements.

. Managed a group of consultants who were contracted to build out the

data warehouse environment.

. Developed a data model change log to keep track of modeling changes by

project, by layer, and by object. It was instrumental during

migration planning.

OneBeacon Insurance Philadelphia, PA 1984-

2003

Technical Specialist (January 2000-October 2003)

Worked as a data warehouse architect to define the logical enterprise

warehouse model, facilitate data requirements gathering JAD sessions,

synchronize project warehouse model with enterprise warehouse model, create

physical models for application systems and establish a data dictionary

model.

. Designed dimensional models from which data cubes were developed.

This provided data to the customer in a format that allowed them to

make sound business decisions.

. Modeling standards and guidelines were established so all models had

the same look and columns across models were consistently named.

. Developed a staging model to allow data to be cleansed and transformed

as necessary before being loaded into the enterprise data warehouse.

. Designed an operational data store for capturing the most recent and

highly accessed data.

. Functioned in role of ETL architect and established an ETL design for

the data warehouse. The ETL developers when extracting data and

loading the data warehouse used this design.

. Established an information framework for an enterprise warehouse and

data marts. This design was a blueprint showing the flow of data

through one consistent stream.

. Designed a template to capture metadata. Created a metadata

repository that documented the flow of data from the source systems to

the data cubes.

Technical Consultant (October 1997-January 2000)

Worked as a data warehouse architect to define and oversee the architecture

for the corporate data warehouse, participate in data requirements

gathering sessions, integrate new requirements and extract data from source

systems to load into the enterprise data warehouse.

. Participated on Data Stewardship Council to establish a corporate

enterprise data model and to develop consistent business definitions

for all business elements in the data warehouse.

. Designed the implementation of critical underwriting information

required to allow the customer to make product and pricing changes.

. Streamlined the extract and pre-processing functions by developing a

common extract format, one extract per source system and one

transformation program. This cleaner design was easier to follow when

enhancements were made or resources were added to the team.

. Implemented generic modeling structures that allowed new data elements

to be added more quickly and accurately to the data warehouse.

System Consultant (March 1993-October 1997)

Solved business problems as a system architect by leading requirement

sessions and designing system solutions for the organization's largest

policy administration system.

. Trained as a system architect under an IBM-certified architect.

. Created the system design for the interfacing of all legacy systems to

and from a new policy administration system.

. Designed an innovative interface that handled all business transaction

types. This eliminated double entry of data.

. Designed renewal underwriting referrals that gave flexibility to the

customer to decide how each individual referral should be handled.

Team Leader (June 1988-March 1993)

Managed 18 programmers responsible for a commercial lines insurance policy

administration system. Responsibilities included resource allocation,

monitoring adherence to strict regulatory schedules and performance

management.

. Designed solution to add surety line of business to a policy

administration system. This line of business had to be put up quickly

in a system not designed to handle open-ended bonds.

. Established a design to place surcharges within tables that the

customer could update. This allowed a new surcharge to be added very

quickly to the system by the customer.

Senior Analyst/Programmer (May 1986-June 1988)

Performed the function of a technical project leader to convert a large

policy administration system.

. Created a benchmark format for design documents for system changes.

This was the first time the company used a standard design document.

. Analyzed design documents from numerous systems and integrated the

design approaches.

Programmer (May 1984-May 1986)

Analyzed and debugged errors in an insurance policy administration system.

Education

LaSalle University Philadelphia, PA

Bachelor of Art in Computer Science

Affiliations

Data Management Association (DAMA), member

Enterprise Modeling User Group (EMUG), Vice President of Membership

Contact this candidate