ROADMAP TO AN ENTERPRISE

LOGICAL DATA MODEL

Case Study

WHO AM I?

� Enterprise Data Strategist at American Family

Insurance Company

� More than 20 years of experience in data

modeling

� Current President of Wisconsin DAMA Chapter

� Vice-President of Chapter Services DAMA

International

� Forever a data modeler!

THE JOURNEY TO AN ENTERPRISE LDM

Welcome to my experience.

DATA MANAGEMENT CHALLENGES

� Lack of Enterprise Data Model

� Logical Models (what do mean logical model?)

� Incomplete Metadata

� Different Terminology Used in various areas of

the Organization or same with different meaning

� Lack of Understanding of the importance of

Enterprise and Logical Data Models

� ……

WE HAVE A PLAN…

HOW DO WE GO ABOUT IT?

� Dig through mainframe DDM’s (Data Definition

Modules)

� Review applications

� Look at system entry screens

� Talk with business partners

� Cross our fingers!

SOOOOOO…..

WHAT DO YOU THINK HAPPENED?

� Minimal support and buy in from areas outside of the Data Modeling group �

� Lack of time for the business to assist with validation �

� Many didn’t see the value of a logical model �

� Resources were focused on project work and didn’t have the bandwidth for the enterprise view �

� Model was not kept up to date due to the lack of support �

JUMP FORWARD

� Enterprise Logical Data Model still exists but is

not current and not complete

� Artifact

� Data Governance Program has kicked off

� Artifacts

� An Architecture group has been formed

� Artifacts

� Enterprise Data Management Department was

formed

PROGRESS!!!

�Data has been realized as a major

Corporate asset

�More demand for reports

�Started to replace our legacy systems

�Business partners want accessibility

to what data exists

� Uh Oh!!!!

WHAT ABOUT ALL THOSE ARTIFACTS?

WHAT ARE OUR OPTIONS?

�Do nothing and coast along

independently and continue to

add to the disconnect

�Come up with a plan

COME UP WITH A PLAN!

WHAT ARE OUR OPPORTUNITIES?

� Identify what artifacts exist and the information

that each provides

� Identify where we are aligned

� Identify what we are doing well

� Where can we make improvements

� Learn from previous efforts

� Commitments to make a change

� COMMUNICATION!!!!

EVALUATION TIME

LET THE WORK BEGIN

� Get a champion

� Accessibility of data models

� Active Data Stewards/Owners

� Develop a plan for introduction

� Identify the history within the organization and

determine how to improve on perceptions

� Let’s get busy!

WHO NEEDS TO BE INVOLVED?

� Management

� Business Partners

� Architects

� Data Modelers

� Data Governance

� Data Analysts

� EVERYONE!

LOTS OF EDUCATION!

� What are all of the various levels of data models

and what do each of them represent?

� How do you read a data model?

� What information is used to create a data model?

� What dependencies exist between the various

models?

� Data modeling classes for the business ☺

SOCIALIZATION

BABY STEPS

� Identification of responsibility and accountability

� Determine who needs to be involved

� Ensure that the various deliverables are added to

the SDLC process

� Let’s get started!

CHANGE

MORE CHANGE

STARTING OVER?

• New Director

• New Department (again)

• New Focus

PRESENTATION

� Let me help you understand ☺

� Presenting the Conceptual differently to the

business

� Know your audience

� What makes sense

SAMPLE 1

Party

A person or organization that can enter

into a contract or other legal proceeding,

or which plays a role in the insurance industry.

A Party purchases 1 or More Insurance

Policies

An Insurance Policy is purchased by 1

or More Parties

Insurance Policy

A combination of documents that makes up the insurance

contract, consisting of: declarations, named insured,

coverage descriptions, effective and expiration dates, limits

of insurance, coverage form(s), conditions, exclusions and

endorsements. Commercial and farm/ranch policies may be

made up of two or more coverage sections, each with its own

declarations, forms and endorsements. These sections are

then combined into a single policy with common

declarations and common conditions.

Policy NumberName

Date of Birth

Social Security Number

Party

A person or organization that can enter

into a contract or other legal proceeding,

or which plays a role in the insurance

industry.

Named Insured

The person(S) organization designated by

name in the policy as protected under the

insurance contract/policy.

A Party can have one or more roles of being the Named

Insured

Named Insured is a Role assigned to a

Party

Name

Date of Birth

Social Security Number

Party Identifier

Worker

Insurance

Policy

Quote

Work

Activity

Organizational

UnitUser Identifier

Hours Worked

Number

Work Start Timestamp

Work End Timestamp

Activity Status

Description

Policy Number

Quote Identifier

SAMPLE 2

�Data Modelers are all in one

department

�Continuing to educate individuals

�More involvement with projects

�People are asking for the models

�More understanding on the

importance of having the enterprise

view as well as project level models

�Resources are still constrained

OCTOBER 10, 2016

�This message is to announce the

start of logical data modeling as

a regular activity on all new

projects that are starting now

and going forward.

SUCCESS!!!

CONTACT INFORMATION

Missy WittmannMissy WittmannMissy WittmannMissy Wittmannmwittman@amfam.com

Join me on LinkedIn

@momof366