We provide IT Staff Augmentation Services!

Lead Data / Sr. Warehouse Data Architect Resume

GA

SUMMARY:

  • Over 25 Years in the banking and financial industry.
  • Over 18 Years as a Data Architect working and leading technical groups including DBA, ETL, UI and Reporting development. Over years as a Sr Data Architect.
  • Over 20 Years in advanced data modeling skills including Conceptual, Logical and Physical for OLTPs and Data Warehouses. Data modeling technique included Relational (Inmon) and Dimensional (Kimball). Application of correct normal form and understanding correct de - normalization opportunities. Creation of Conceptual Data Model (CDM), Logical Data Model (LDM) and Physical Data Models (PDM)
  • Over 20 years using Erwin as data modeling tool. Creation of DDL and seed metadata.
  • Over 18 years providing quality assurance support from defining test cases (including negative testing) to the creating and execution of repeatable test scripts.
  • Over 10 Years supporting and setting up data governances and master data management for various projects. Ensuring all systems, reporting and regulatory items use conformed codes. Work with various business units to define the enterprise standards for master data.
  • Over 13 years providing metadata management including data dictionary and reference data.
  • Target and Source RDBMS experiences includes DB2 (UDB and Mainframe), SQL Server (2000, 2005, 2008 and 2012 ), Oracle 10i and below and Teradata... Advanced skills in client side MS Access 2007 and below
  • Development of logical and sometimes physical code to migrate data from environments (downstream from source to target).
  • Over 18 years working with multiple source types including VSAM, flat files, CSV, RDBMS and spreadsheets.
  • Over 18 years’ experience in creating views and stored procedures to help reduce model complexity
  • Worked with ETL in creating advanced CDC (Change Data Capture) logic as applicable
  • Over 18 years of experience facilitating JAD sessions and gathering and documenting business requirements. Often requirements are vague and not clearly known. Ability to pull needed information from stakeholders.
  • Over 17 years of transforming business requirements to technical requirements / specifications.
  • Over 12 years working with ETL developers using AbInitio, Informatica and Data Stage.
  • Over 17 years in Report development using Ms Access and Crystal Reports. Limited experience in Cognos
  • Over 17 years creating technical design and architecture documentation including data flows, data mapping, physical data models, UI Maps and transformation rules.
  • Over 17 years providing or leading QA testing of accurate data movement including creation of simulated data to test all rules in the process. Also provided repeatable processes to assist in continual data validation.
  • Over 17 years creating and documenting standards including technical names and classwords.
  • Provide advanced data modeling training for client employees
  • Over 16 Years’ experience in Banking Data Warehouse Model (BDW) and Financial Service Logical Data Model (FLSDM). This includes leading teams on the implementation of the model; scoping the model to fit client's needs; providing in-house training on the BDW and advance modeling techniques; delivering scoped BDW logical data model and a implementable physical data model; mapping source to BDW; guiding ETL on how to load the BDW; and reporting on how to get information out of the BDW
  • Over 12 years of Customer Relationship Management, Analytics and Know the Customer from both a marketing and regulatory view
  • Over 8 years creating master data management (MDM) / reference data solutions. Mostly from a data perspective but work with MDM developers/admins to ensure master data is achieved to support the enterprise.
  • Over 8 Years in facilitating training sessions including: Data Modeling (101), Advanced Data Modeling Techniques, Banking Data Warehouse Model (BDW), FSLDM "9" Data Concepts, Classifications, etc.
  • Over 3 Years using Toad and other query tools.
  • 4 Year using Netezza and Aginity
  • 2 Year Quality Director

PROFESSIONAL EXPERIENCE:

Confidential, GA

Lead Data / Sr. Warehouse Data Architect

Responsibilities:

  • Provided internal training on the BDW methodology and concepts which was the initial intention.
  • After the bank realized what they had purchased, they extended contract to support in full capacity as a Sr Data Architect and lead scoping, mapping, logical and physical modeling efforts, metadata and master data and supported ETL as needed.
  • ETL had limited exposure to the BDW so detail training and flow documents were created to support them including the off shore team.
  • These deliverables became my responsibly:
  • Database Planning - Schemas and Database as well as supporting the migration plans
  • Modeling Effort
  • Scoping the BDW is an effort to limit the BDW to only what is in scope for the bank. This bank desired to keep the logical as is and only de-scope the physical.
  • Preform Data Analysis and/or support off shore data analysis work
  • Extend Logical Data Model and update metadata to include bank information
  • Part of scoping is to document gap analysis. What is needed vs. what is required?
  • Created physical data model from logical data model on first pass someone as is.
  • Utilized a technical naming glossary and extended as needed.
  • Created all FK contains and indexes including PK, AK and IDX.
  • Created full and alter ddl as needed and provided to DBA to build. DB platform was SQL Server 2012.
  • Validate all objects created correctly including all indexes and constraints
  • Created detailed mapping and transformation rules document to clearly show movement of data from source to target. Applied order in which unit of works must be worked. Mapping was logged and versioned to match the model.
  • Data Governance
  • Worked closely with Data Governance department to define understand how each source system links / relates to enterprise standards and define gaps.
  • Created first cut of enterprise values as well as standardized ETL transformational logic for target databases.
  • Created audit reports to show 1) where data has been loaded incorrectly and 2) where data is not in compliance with enterprise standards.
  • Created LDM/PDM to house master data (Banks, Branches, Codes, and Employees. Etc) which becomes confirmed dimensions.
  • Supported all teams including testing, ETL and reporting as needed
  • ETL support was a challenge. There was a combination of on shore and off shore. For each mapping, a high level data flow was needed so ETL could more easily understand the mapping. Sample pseudo code was also provided. ETL team was Jr and had challenges in both the architecture and learning BDW.
  • Created test scripts
  • Validated source information was loaded as expected
  • Validated all constraints and FK were correctly built and utilized.
  • Posted testing results to a dashboard in SQL Server. Items no resolved was escalated to quality center.
  • Worked other defects from Quality Center.
  • Created test scripts to validate the model was being used as desired. Scripts were automated to run at the end of the ETL process.
  • Worked on Data Warehouse Manager, Project Planner and Data Warehouse Director to ensure the overall company goals were being met, the level of work in each release and any issues that need to be moved to next release due to time constraint.
  • Worked closely with reporting team to support customer relationship management (CRM) including customer analytics. Regulatory reporting was also key in know the customer.
  • Worked remote proximally 30% of the time using VPN and live chat to work with team as if I was in office.
  • Worked on Mart developing time by providing the following:
  • Created and updated ERDs as needed
  • Show how to extract the data from the BDW based EDW

Confidential, OH

Lead Data Warehouse Data Architect

Responsibilities:

  • Lead the efforts to enhance an existing data warehouse and reporting Confidential for retail store level reporting.
  • Provided a roadmap and guidance for future enhancement including templates for modeling and mapping, technical name standards, physical object naming standards.
  • Created DDL for DBA to create new structures in Netezza
  • Facilitated knowledge transfer to offshore staff to load and support database objects.

Confidential, VA

Senior Data Warehouse Data Architect

Responsibilities:

  • Responsible to architect an end to end solution for a distribution client who desires to build and end solution of a Confidential . Mart was a relativity traditional star schema with snowflakes as needed
  • Facilitated and requirements gathering and created work flows for both ETL and Reporting
  • Neteeza DB, DataStage ETL and Cognos reporting.
  • Responsible to deliver Conceptual, Logical and Physical Model using Erwin as well as all metadata, domain of values, mapping and ETL Packages / Unit Of Work
  • Worked with Project Manager to provide all dates and tasks for myself and sub teams.
  • Provided knowledge transfer to key employees as I rolled off the project. Project was always intended to be short term to get internal employees up to speed.
  • Technical mentorship to various teams including business analysis, testing, ETL development, DBA support and business analysts.

Confidential, OH

Senior BDW Data Warehouse Data Architect

Responsibilities:

  • Responsible to architect an end to end solution for a banking client who was building a new enterprise data warehouse from the ground up. Limited standards and processes existed. Database platform used was Teradata and ETL tool, Ab Inito.
  • Architected a new Data Warehouse based on the industry model, IBM Banking Data Warehouse (BDW). Client desired to follow BDW strictly and only deviate where it was best for the bank. The new data warehouse would be very normalized and marts more de-normalized. 3NF (Inmon approach) used for the data hub / warehouse and dimensional / star schemas (Kimball approach) used for the marts.
  • Delivery of CDM, LDM and PDM.
  • Created first delivery of DDL and provided to DBA. Joint sessions with DBA to determine the best implantation approach while not compromise model integrity. Worked with DBA in understanding the Teradata architecture (Unique Primary Index, Non Unique Primary Index and alternate key constraints) as well as knowing when data integrity should be at the RDBMS level vs. ETL level.
  • Created work packets for repeatable processes in the delivery of the end to end data warehouse solutions.
  • Marts work both conformed and functional. Conformed dimensions and fact tables were created.
  • Designed, based on client’s desire, a target based architecture that allowed as much reuse as possible for future projects. Information is transformed as quickly as possible to the target as the data is migrated from source to target. Enterprise rules are placed close to the data warehouse and source rules placed close to the extraction.
  • Defined both data quality / movement and load quality testing scripts, including negative testing. Developed over 800 test scripts that are run after each load process (post load scripts)
  • Created / Delivered - Project Release Schedule including objects (tables, views, model, etc.) release schedule, technical naming standards (including classwords), end to end solutions architecture (worked closely with ETL Architect), logical and physical data model, supported the mapping where needed, seed data, history management rules and documentation, enterprise views and post load processing and testing scripts.
  • Facilitated trailing for the BDW as needed and created multiple BDW explanation documents for client to conduct their own training in the future as needed.
  • Created logical data flow using reusable logic for ETL to provide to offshore teams.
  • The primary goal of the client in using my services was to get a process, architecture, documentation and overall BDW information and transfer this knowledge to the bank’s resources so they could be as self sufficient as much and as soon as possible.
  • Created a metadata repository and loaded all metadata from the data models, mapping documents and Teradata. Metadata db will be used as a self service for different members of future projects to pull their packages as the build goes through the process.
  • Worked with client in the design of a credit risk mart to support Basel and regulatory requirements. Information for the mart would be fed from the new enterprise data warehouse
  • Worked with Data Governance and Master Data Management team to both model the data as well as create quality checks to ensure the accuracy of the data

Confidential, IL

Senior Data Architect / Team Lead

Responsibilities:

  • Responsible for the design and delivery of a new Customer Confidential for the new rewards program for the Retail and Healthcare Industry
  • Worked closely to gather and implement requirements to support a new customer relationship management initiative and worked with reporting team to support all levels of analytical reporting including regulatory, customer, inventory, locations, etc.
  • Gathered requirements from business, facilitation of priority of release, created conceptual, logical and physical data models using Erwin 8x using a standard dimensional modeling approach but allowing for dynamic and reusable dimensions to aid the client for future requirements (this was critical since the rewards program was new and requirements were still vague)
  • Created and delivered DDL for Neteeza (new DB for client) and helped and provided sourcing logic from a Teratdata Platform (client's Enterprise Data Warehouse) as well as drill down / traceability matrix for reports to traverse from mart summary to warehouse details.
  • Created delivery tasks, times and dependencies and provided to project manager.
  • Facilitated business requirements sessions and design sessions with reporting, DBA and ETL teams. Created user and technical documentations.
  • Created dynamic audit architecture to allow client to create new data audits / exceptions as needed with no changes to db or ETL code.
  • Participated in Enterprise Architecture sessions to understand Walgreen's standards to ensure we were in compliance or provide alternate ways the solution could be done to get enterprise architecture's support.
  • Created stress test cases to overload fact and dimensions tables to simulate 10 years of data to prove out the proposed architecture.
  • Created 70~ views to provide the end users with a presentation layer to remove some of the complexity needed in the model needed to support a flexible solution.
  • Physical environments included Netezza and Aginity.

Confidential, TN

Senior BDW Data Warehouse Data Architect

Responsibilities:

  • Responsible to help client correct issues with the way the BDW had been implemented by previous client. Reversed engineered current BDW database to determine current situation.
  • Scoped out issues and prepared step by step approach to correct. Worked with ETL (Client used DataStage) on impact analysis during corrections.
  • Participated in planning and scoping exercises to help set reasonable expectations.
  • Created delivery tasks and plans for project management.
  • Responsible for the overall scoping of the BDW for the bank to multiple sources to determine model usability
  • Worked with DBA and provided DDL on BDW Oracle 10i Implementation
  • Back created detail logical model as it had not been created by previous client.
  • Facilitated work sessions in BDW Mapping and Scoping with other business areas

Confidential, Warren, NJ

Senior BDW Data Warehouse Data Architect

Responsibilities:

  • Responsible for the overall scoping of the BDW for the bank to multiple sources to determine model usability.
  • Created and provided presentations of the logical flow of data into and out of the BDW
  • Created delivery tasks and plans for project management.
  • Participated in planning and scoping exercises to help set reasonable expectations.
  • Recommended areas of extended and customized the BDW to better fit the Bank's specialized needs around Wholesale and Securities Banking.
  • Facilitated work sessions in BDW Mapping and Scoping with other business areas.
  • Documented LDM, PDM and other standards that were needed for the client.
  • Created detail logical mapping from source to target.
  • Created scoped Logical Data Model and Physical, Data Model (for Oracle 9i) of the BDW based on bank's needs.
  • Created training, overview and story board document for both technical and business teams.
  • Designed automated testing system to allow for on-going audits of the health of the data warehouse.

Confidential, New Orleans, LA

Senior BDW Data Warehouse Data Architect / Technical Lead

Responsibilities:

  • Responsible for setting the directions of the overall data warehouse architecture from acquisition of the data to presentation of the data to the reporting tool.
  • Define tasks and resource hours needed for each steps and work measuring with Bank employees in accomplishing various tasks. Includes setting the technique for % complete.
  • Work with various key team members to understand the overall objective of the BDW model and the advantages and disadvantages of the model. 
  • Worked with business and data analysts in creating and/or obtaining source metadata including source definitions, domain of values (DOV), standardized codes (which become classifications), data anomalies, and data profile.
  • Create data architecture documents including Data Architecture Standards, Naming Standards, Data Flow Diagrams, metadata and database environments
  • Facilitated training sessions on the BDW and advanced modeling techniques used by the BDW. Including the basic "9" data concepts of the BDW, Traversing the BDW, etc.
  • Provide scope and mapping from the BDW IDA tool. Worked with users to determine what part of the BDW should be implemented for the bank.
  • Provided source to stage, stage to target (DW), DW to BDW to DW and DW to Presentation layer mappings and detail transformation rules.
  • Worked closely with DBAs on how the physical db2 database should be set up including environments (instances and schemas) and partitioning. This also included delivering physical DDL for builds and alters.
  • Worked closely with ETL team members on creating the ETL architecture and defining the load strategy needed for this Target Based Architecture (TBA).
  • Facilitated regular architect and team lead meetings and led the various other architects in resolving issues and meeting project objects.
  • Worked with project management in setting milestones and deliverables.
  • Client abandoned a project for a promised of a shrink wrapped solution.

Confidential, Houston, TX

Enterprise Data Architect / Technical Lead

Responsibilities:

  • Data Architect for re-engineering project using Erwin as the modeling tool and DB2/UDB as the target RDBMS. Sources included VSAM, DB2, Oracle 9i, and SQL Server 2005
  • Continuation of project to complete an enterprise data model solution. The current target RDBMS plan was to develop an ODS to move reporting away from production systems. In addition, details plans were being captured to move into a enterprise data warehouse solution for a later phase. A overall logical enterprise data model will be used to create other targets as needed.
  • Deliver of Logical and Physical Data model, as well as detailed mapping of logical to physical and source to target. Provided transformation rules and load logic to ETL team.
  • Mentoring of the full time staff on modeling approach and concepts who will take over future support and extension of the model.
  • Provided detailed metadata / data dictionary documents after numerous JAD and Business Analysis session.
  • Worked with ETL developers on load strategy and review loaded data to ensure data was being loaded as intended. Facilitated sessions of ETL and DBA team, making sure everyone was on the same page as to the spirit and intention of the modeling approach. (Client used DataStage)
  • Supported reporting team in traversing the model and built and/or recommended views as needed based on the complexity of the reports.
  • Evaluated reports and extract to ensure on version of the truth was being provided
  • Provided risk assessment, issues and concerns, and enhancements suggestions to management for current and future needs.
  • Created test plans and scripts and validated test results.
  • Developed training documents and facilitated training classes in "Data Modeling 101"

Confidential, Atlanta, GA

Enterprise Data Architect / Technical Lead

Responsibilities:

  • Lead the efforts in Logical and Physical Data Modeling design for the DOE’s enterprise solution. Target RDBMS was SQL Server 2000.
  • Facilitated sessions with business owners and technical leads to determine the best solution to meet their needs.
  • Architect the flow of data from source system to analytical / downstream marts.
  • Data Architect consisted of source system, staging, relational (3nf) data warehouse (data hub), analytical dimensional marts and reporting (Cognos) cubes.
  • Developed views used to access the 3rd relational data warehouse. Views for both for power uses and ETL extractions.
  • Worked with ETL to create target based loads and supported the efforts to identify the needs of load ready files.
  • Collected and documented metadata as well as source to target mappings and transformation rules.
  • Created documentation naming standards (Object Names, Classwords, etc.)
  • Developed training documents and facilitated training classes in "Data Modeling 101"

Confidential, Atlanta, GA

Lead Data Modeler / Data Architect

Responsibilities:

  • Lead the efforts in Logical and Physical Data Modeling for a multi-terabytes warehouse and 15+ sources systems for a major financial banking company. Data modeling tools included Erwin.
  • Provided solutions architecture guidance for warehouse implementation
  • Project goal was to create an EDW and Confidential to support current reporting requirements for Basel II while at the same time creating a reusable enterprise data warehouse. Risk Management / Basel II requirements were built in downstream data marts and cubes.
  • Worked with Risk Management team and external / outside vendor to identify risk management / Basel requirements and map requirements to existing data source and identify gaps.
  • Regular Basel meeting to review various reports needed (Exposure, Collateralization, cross Collateralization, exposure, etc.)
  • Facilitate JAD session to identify business and data requirements to successfully build a data model, ensuring that the bank’s data modeling standards are met: (Normalization, Referential Integrity, Metadata, Classwords, etc.)
  • Attended Team Lead Meetings and determined project plan, dates and deliverables for the data modeling team.
  • Support included supporting the build out of both regulatory reporting a customer relationship management and know the customer.
  • Physical Data Model Design for DB2 / UDB.
  • Facilitated cross-functional team review / work sessions with Reporting, Mapping, DBA and ETL to determine the best physical model that will both maintain business rules and provide manageable database creation and maintenance, minimizing de-normalization as much as possible.
  • Provided guidance and templates to other sub-teams in the creation of mapping and transformation rules from source to target.
  • Worked closely with ETL to show how the EDW should be loaded. Provided Pseudo code as needed.
  • Created seed and transformation data for the EDW.
  • Participated in Data Architecture Design sessions for the overall architecture of source to EDW to Confidential .
  • Used baseline data model from IBM, Banking Data Warehouse Model (BDWM), and customize to fit the specific needs of client.
  • Facilitated training sessions for knowledge transfer of the BDWM concepts.
  • Provided supporting documents to other sub teams (Logical Metadata, Physical Data Dictionary, Business Data Element to Mapping Document, Model History Retention Strategy, Model Implied Foreign Keys, etc.)
  • Provided Testing support as needed.
  • Used MS Access for AdHoc reports and data analysis as needed. Creating Forms for inputs; VBA as needed and various reports. Some data was local to Access while other data was access via Linked Tables and merged or downloaded.

Confidential, Alpharetta, GA

Data Architect / Lead Data Modeler

Responsibilities:

  • Provided solutions architecture guidance for OLTP Implementation
  • Facilitated JAD Sessions in order to gather the data requirements to create a Conceptual, Logical and Physical Data Model for an OLTP
  • Target Database of SQL Server 2000. Project was the reengineering of 5 existing systems to a single system.
  • Provided Stress testing results by prototyping parts of the PDM in SQL Server 2000 and loading data to emulate a 5 year plan
  • Created and Maintained Standard Metadata documents (Data Dictionaries, Source To Target and Gap Analysis)
  • Developed training documents and facilitated training classes in "Data Modeling 101"

Confidential, Houston, TX

Data Architect / Lead Data Modeler

Responsibilities:

  • Provided Data Modeling support to Gulf State Toyota in the reengineering of their existing Vehicle Distribution, Parts Allocation and Warranty Claim systems from VSAM / DB2 files to an RDBMS (Oracle 9i). Data Modeling tools included Erwin and Visio.
  • Responsible for the Conceptual, Logical and Physical Data Modeling design in a high volume transaction and operation data store environment using the “9 Data Concepts” modeling approach in order to provide a data model that is reusable, extendable and adaptable over time for future business changes.
  • Worked with Subject Matter Experts to identify, document, define and capture all applicable domain of values for source data elements.
  • Facilitated JAD session to identify business and data requirements and model validation.
  • Created metadata documents (Source and Target Data Dictionaries, Classword Names and Data Type Standards, Source To Logical Target Mapping, Source to Physical Target Mapping (with transformation rules), and domains of values documentation)
  • Facilitated Usage Sessions determine the best physical model that will both maintain business rules and provide manageable database creation and maintenance, minimizing de-normalization as much as possible.

Confidential, Jacksonville, FL

Vice President / Data Modeler

Responsibilities:

  • Responsible for the Conceptual, Logical and Physical Data Modeling in operational / warehouse systems as part of a development team. Data Modeling tools included Erwin and Visio.
  • Facilitate JAD session to identify business and data requirements to successfully build a data model, ensuring that the bank’s data modeling standards are met: (Normalization, Referential Integrity, Metadata, Classwords, etc.)
  • Warehouse and Operation Data Store Data Modeling as needed
  • Worked on several merger and acquisitions projects where both OLTP and DW were merged. Some projects required dual and centralize repositories.
  • Work with DBA’s to determine the best physical model that will both maintain business rules and provide manageable database creation and maintenance, minimizing de-normalization as much as possible.
  • Physical Data Model Design for DB2, Oracle and Teradata platforms

Hire Now