KIM BARE

Thornton, Colorado 80602 720-524-3253 [email protected] www.linkedin.com/in/kimbare

CAREER SUMMARY
Provide successful and cost-effective solutions for Ontology Management, Master Data Management, Data Governance & Data Quality, Metadata Management, Enterprise Models or Architectures, Information or Metadata Repositories, and Business Systems. Manage data as an asset, and architect and manage the business glossary, canonical data model, and the systems configured to support these assets. Also have expertise in enterprise-wide and project level models and architectures; data lineage and impact analysis; well-designed standards; system life cycle methodologies; and enterprise architectures. Successfully implement all solutions in business and Information Technology (IT) environments. Professionally provide consulting, coaching, training, support, and guidance services to customers, all levels of management, business personnel, and IT personnel. Have excellent oral, written, and presentation skills. Specialize in: Data Governance (DG) with Data Quality (DQ) Master Data Management (MDM) including a Glossary and Canonical Data Model Metamodel & metadata architectures & management Rochade, Mega, & other repository & modeling tool concepts, design, implementation, & management Semantic or Ontology modeling, conceptual & logical data modeling, business rule modeling Functional data modeling - basically the same thing as Dimensional Data Modeling Data and Information Standards Structured process, workflow, and use case modeling Zachman Framework concepts, implementation, & management JAD (joint application development) workshop facilitation SLC (system life cycle) methodologies Knowledge transfer and training

EXPERIENCE
SEMANTIC ARTS, Ft. Collins, Colorado MAY 2012 TO AUGUST 2012 Senior Enterprise Ontology Architect Defined data objects and developed portions of an Ontology using semantic technologies and the OWL modeling formalism for the client Proctor and Gamble. Facilitated data gathering sessions with cross-functional teams at the client site. Created semantic models using the E6Tools (a Semantic Arts tool) and Protg. Trained in semantic technologies and semantic modeling using the OWL formalism. Trained in the model-driven, business process development tool Be Informed. G&B SOLUTIONS, Lakewood, Colorado FEBRUARY 2012 TO MAY 2012 Senior Data Modeler Defined, modeled, and managed semantic (conceptual) and logical data models including glossary, and work flow models for the BLM (Bureau of Land Management). Defined and managed a Business Glossary. Defined standards for semantic and logical data models, a business glossary, and work flow models. MAYO CLINIC, Rochester, Minnesota APRIL 2009 TO OCTOBER 2010 Senior Programmer Analyst Architected and administered Rochade servers and clients for the production, integration, development, and native environments of EMME (Enterprise Managed Metadata Environment) and a Repository Management Repository. Defined, modeled, and managed semantic (conceptual), logical, and functional data metamodels and physical RIMs (Repository Information Models) for EMME and a Repository Management System Repository. Defined and managed a Semantic Model and Business Glossary in Rochade.
January 30, 2013 Page 1

Defined and suggested standards for managing data as an asset including data governance and data quality processes and disciplines. Defined and managed users, Subject Areas, RIMS (Repository Information Models), and queries using Metability in Rochade. Installed and maintained various Rochade scanners and used them to import data into Rochade. Installed and managed WebAccess. Used WebAccess to build and manage queries and reports. Provided technical support to both IT and business metadata users. Educated users on populating and managing metadata using WebAccess. Facilitated JAD workshops and provided education to team members and project management on modeling, metamodeling and using the Zachman Framework and the Business Rules Groups models to build and manage models for Rochade and other Repository Systems. Defined and managed semantic (conceptual), logical, and functional metamodels and models in PowerDesigner. XYLO TECHNOLOGIES, Rochester, Minnesota MARCH 2008 TO APRIL 2009 Senior Programmer Analyst at Mayo Clinic (a contract to hire position) As a Xylo Technologies employee performed everything listed above under Mayo Clinic in a contract-to-hire position. MUTUAL OF ENUMCLAW, Enumclaw, Washington OCTOBER 2004 TO MARCH 2006 Senior Data Analyst Lead the enterprise practice of data architecting including the formalism for object design, and data relationship design patterns and repository design. Directed and lead the design of Enterprise Architecture and Information Repository metamodels using the Business Rules Groups metamodels and the Zachman Framework as the basis for the requirements. Defined, modeled, and managed: semantic (conceptual), functional, and logical metamodels for data models; business rule models; data lineage and impact analysis; process, work flow, and use case models; and the maps or links among metamodel components. Modeled in Enterprise Architect and then Mega. Mentored and trained three new modelers, and managed the Enterprise Modeling Team and all associated project plans. Led the evaluation, selection, and implementation of Mega as both an Information Repository and a modeling tool. This tool replaced Enterprise Architect as the modeling tool. Facilitated JAD Workshops for a cross-functional team to design and document in Mega state-of-the-art semantic (conceptual) and logical data models and business rule models of a core business system. With Mega, provided the capability to: produce and manage Enterprise Architectures, manage the core business systems, manage architecture components of the strategic plan, perform Master Data Management and Data Governance, determine data lineages, and perform impact analysis. Provided education and training to team members and management on: metamodels vs. metadata; semantic and other data modeling; data lineage and impact analysis; process, work flow, and use case modeling; Information Repositories; Master Data Management and Data Governance; the Business Rules Groups metamodels; the Zachman Framework; and all associated policies, procedures, and standards. ASG SOFTWARE SOLUTIONS, Denver, Colorado JANUARY 2002 TO JANUARY 2004 Senior Sales Engineer Presented and demonstrated Rochade to prospects as the presales technical support in the sales cycle. Helped prospects determine how to use, define, and implement Rochade to meet their goals and objectives. Provided answers to questions about Rochade in Request for Information (RFI) and Request for Proposal (RFP) documents submitted by Rochade prospects. Provided additional education on Rochade during the pre-sales portion of the sales cycle, which included suggested policies, procedures, and standards. Used Rational Rose to build semantic (conceptual) and logical metamodels to define and manage conceptual, logical, and physical data models; data lineage and impact analysis; business rule models; process, workflow, and use case models; other Enterprise Architecture artifacts in Rochade; and the relationships among metamodel components. Implemented these models in Rochade in order to build a research version of Rochade to test defining semantic (conceptual) data models and mapping repository artifacts to each other according to the Zachman Framework for Enterprise Architectures.

January 30, 2013

Page 2

PREVIOUS EMPLOYMENT INTERSECT TECHNOLOGIES, Denver, Colorado Senior Analyst at DFAS (Government Facility) SPRINT PCS, Lenexa, Kansas Enterprise Information Architect (Staff Engineer) - EA Integration Department VIASOFT, Phoenix, Arizona Staff Engineer - Core Services Development Department ENTERPRISE ARCHITECTURE SOLUTIONS, Reno, Nevada Owner and Enterprise Architect and Consultant at Washoe Medical Center BEST CONSULTING, INC., Reno, Nevada - Senior IT Consultant CNA COMPUTER SYSTEMS ENGINEERING, Bellevue, Washington - Senior Consultant DMR GROUP, INCORPORATED, Seattle, Washington - Senior Consultant, Modeler, & Methodologist

January 30, 2013

Page 3