CAREER SUMMARY:

• Twenty - seven (27) years experience in business/requirements analysis
• User interviews
• Process, data flow, object schema diagrams, and use cases.
• Defining and writing Requirements Analysis, Database Specifications, Data Dictionaries, User Manuals, Computer Operation Manuals, Maintenance Manuals, SQL Training Manuals, and Testing Procedures (conforming to IV&V standards)
• Twenty-eight (28) years experience in database modeling (logical and physical; relational and object-oriented)
• Relational and Object-oriented database methodology and structure
• Defining Naming Conventions/Rules/Standards
• Entity-Relation Diagrams
• Seventeen (17) years experience in Oracle
• Twenty-three (23) years experience as a consultant
• Four (4) years experience in Data Warehouse
• Certified in Inmon's latest methodology, DW 2.0
• Authored three (3) books on Oracle SQL (v5.1a, v6.0, & v7.0)

COMPUTER EXPERIENCE:

Software: Databases Oracle v10g, Teradata v14.1, SQL Server 2005, SQL Server 2007

Case Tools: Designer 2000 v2.1, S-Designer v6.0, ERWin v9.5, Embarcadero ER/Studio v8.0, SilverRun

Microsoft: Windows 8, Windows 7, MS Access, Excel, Word, PowerPoint, SharePoint

Miscellaneous: Crystal Reports, Visio, Photostudio, Brio/Hyperion 8.3, Toad

Design Methodologies/Processes: Yourdan, Chen, Martin, Booch-Rumbaugh, IDEF, Inman, Kimball, UML 2.0, RUP, SOA, Agile, SCRUM

Classes: Compiere ERP software

PROFESSIONAL EXPERIENCE:

Confidential, Phoenix, Arizona

Consultant/Database Architect

Responsibilities:

• Responsible for designing the central core, Party module, of a proposed new Enterprise Data Warehouse.
• Currently, there are several third party databases for which users must query separately and store the results from these sources in their own MS Access database or an Excel spreadsheet in order to produce their reports.
• Many of these queries take several hours to run. A Universal Key defining a Person, Business, and Service does not exist. The Party Module will solve this initial issue.
• Responsible for writing the Cigna EDW Naming Standards, Rules, and Conventions document, Cigna EDW Business Rules Specification, Cigna Data Analysis, Metrics, and Cleansing document, Cigna EDW Data Mapping Spreadsheet, and the Cigna Enterprise Data Warehouse Specification.
• The project was short term. The objective was to prove the value of having an Enterprise Data Warehouse, data marts, and data stores for running reports for future funding.

Confidential, Phoenix, Arizona

Consultant/Database Architect

Responsibilities:

• Responsible for designing new logical databases as well as updating current logical databases owned by the Enterprise Data Management Services using ER/Studio.
• Work is performed in collaboration with the Business Analysts, Technical Architects, and Developers.
• Projects assigned utilize either Waterfall, Reiterative Waterfall, or Agile methodology.

Confidential, Hillsboro, Oregon

Consultant/Database Architect

Responsibilities:

• Responsible for assisting with the redesign of a product exceptions database.
• Responsibilities included assimilating old documentation against the current database to define the business requirements into one source document, define the new requirements and incorporating them into the new logical database model, creating data flow diagrams, writing user stories, as well as performing data analysis against the existing database.

Confidential, Beaverton, Oregon

Consultant/Database Modeler

Responsibilities:

• Responsible for creating the Sales Order Data Mart. This data mart is comprised of Customer, Product, Sales Order, Sales Representatives, Credit Representatives, Location, Accounts Receivable Documents, and Dispute Management. The data populating these tables is from SAP extractors.
• Responsible for obtaining the business rules, data analysis of the landing tables from SAP, creating the Data Dictionary for the Sales Order Data Mart, and data mapping from SAP, SAP Landing tables, JD Edwards (SAP is replacing JD Edwards), and the Enterprise Data Warehouse (currently being modeled).
• Agile/SCRUM environment. New tasks and continued tasks defined during each two week sprint.
• Responsible for the cleanup, modification, and documentation of the Confidential Plus database (MSP) for which is becoming the center model for the Confidential Digital Sports Enterprise Data Model. This database stores data from global Users of the Confidential Plus website.
• Data is synced in via different sports devices, apps, or manually.
• Responsibilities included data modeling, data cleansing, working with the development team and the MSP DBA, as well as writing and maintaining all technical documentation.
• Though considered as an Agile/SCRUM environment, the actual design and development utilizes an iterative waterfall methodology. The database is under constant modifications as new requirements are added/changed during each two week sprint.
• Projects included preparing a data migration from an earlier version of the Confidential Plus database to the current MSP database, migrating the database model from SQL Modeler to Erwin 7.3, and participating with other teams in Confidential Digital Sports concerning the design of an Enterprise Data Model and with the business intelligence teams.

Confidential, Folsom, California

Consultant/Data Analyst/Database Modeler

Responsibilities:

• Worked with a team to create a next - gen Enterprise Identity and Access Management (EIAM) project for creating and maintaining international identities requiring access to over twenty-five Confidential portals. The primary database is Oracle's OIM and OIA products.
• Responsibilities include as-is and to-be requirements gathering, analysis, and creation of data flow diagrams (UML) from several internal departments, wrote use cases, performed data analysis of current databases both internal and external to the EIAM team for which I am affiliated, data mapping of several data sources to OIM and from OIM to data targets, creating and designing relational conceptual, logical, and physical database models in SilverRun and Visio, as well as writing all corresponding technical/support documentation.
• Other responsibilities included working with other team members for defining data cleansing rules and defining data quality monitors. I was also responsible for restructuring the team's Sharepoint site and became the owner of several documents for different team groups/members (incorporating version control).
• As a side project, I wrote two white papers. One paper discussed best practices in database modeling and the other discussed a database architecture for which I proposed over the current architecture plan.
• I also served as a mentor to new team members.
• Conforming to business or SDLC methodologies.
• Performed business/requirements analysis, created data/process flow diagrams, wrote use cases, as well as worked closely with the client.
• Held weekly internal and external status meetings and performed internal and external walk-thrus to ensure that the data processes captured were correct and to address questions and concerns.
• Defined standardized naming conventions, business rules, and conventions.
• Created the logical and physical design of a relational or objected-oriented database utilizing Oracle's case tool, Designer, Erwin, and Embarcadero.
• Created the indices, constraints, data types, tables, and tablespace sizing.
• Wrote all related documentation including data dictionaries and the detailed database specifications.
• Created test databases as well as wrote testing procedures.
• Data validation and data cleansing.
• Performed quality and user assurance testing when needed.
• Established/adhered to Change Management/Version Control Standards.
• Trained/mentored new team members.

Confidential, Washington, DC

Data Sourcing Manager

Responsibilities:

• Managed a seven person team to upgrade of the Informatica PowerMart tool from version 3.5 to 4.0.
• Redesigned the mappings and transformations for an enterprise data warehouse and data stores.
• Updated automation of all processes from loading data from Oracle as well as outside load files, completing the transformations, and loading the data into Red Brick via Unix flat files.
• Better opportunity which allowed relocation to Colorado.

Consultant/Defense Contractor/Database Architect/Business Analyst & Team Lead

Confidential, Washington, DC

Responsibilities:

• Performed business/requirements analysis (IDEF, process and data flow diagrams, team and one-on-one interviews, etc.) and worked closely with the client.
• Held weekly internal and external status meetings and performed internal and external walk-thrus to ensure that the data processes captured were correct and to address questions and concerns.
• Defined standardized naming conventions, business rules, and conventions.
• Created the logical and physical design of a relational or objected-oriented database utilizing Oracle's case tool, Designer, ERWin, or MS Access.
• Created the indices, constraints, data types, tables, and tablespace sizing.
• Wrote all related documentation including data dictionaries and the detailed database specifications.
• Reformatting of existing data
• Data cleansing/scrubbing
• Data loads using SQL*Loader
• Established/adhered to Change Management/Version Control Guidelines per DoD.