2005 Ratemaking Seminar ACTUARIAL DATA MANAGEMENT (ADM) IN A HIGH-VOLUME TRANSACTIONAL PROCESSING ENVIRONMENT Joe Strube and Bryant Russell GMAC Insurance,

Slides:



Advertisements
Similar presentations
Chapter 13 The Data Warehouse
Advertisements

Data Warehouse Architecture Sakthi Angappamudali Data Architect, The Oregon State University, Corvallis 16 th May, 2005.
Database – Part 3 Dr. V.T. Raja Oregon State University External References/Sources: Data Warehousing – Mr. Sakthi Angappamudali.
Multidimensional Database Structure
Chapter 3 Database Management
IS Consulting Process (IS 6005) Masters in Business Information Systems 2009 / 2010 Fergal Carton Business Information Systems.
Database – Part 2b Dr. V.T. Raja Oregon State University External References/Sources: Data Warehousing – Sakthi Angappamudali at Standard Insurance; BI.
Components and Architecture CS 543 – Data Warehousing.
Organizing Data & Information
Business Intelligence System September 2013 BI.
Data Warehouse Components
Data Warehouse Concepts & Architecture.
Data Warehouse Toolkit Introduction. Data Warehouse Bill Inmon's paradigm: Data warehouse is one part of the overall business intelligence system. An.
Data Warehousing: Defined and Its Applications Pete Johnson April 2002.
Lecture-8/ T. Nouf Almujally
E-Data Jill Dyché Turning Data into Information with Data Warehousing.
Basic Concepts of Datawarehousing An Overview Prasanth Gurram.
Chapter 1 Database Systems. Good decisions require good information derived from raw facts Data is managed most efficiently when stored in a database.
CIS 321—IS Analysis & Design Chapter 1: The World of the Modern Systems Analyst.
Understanding Data Warehousing
DBS201: DBA/DBMS Lecture 13.
CompuBase Data for CRM / PRM Integration How compuBase fits to an existing CRM / PRM system? Last review 25/03/2007.
The McGraw-Hill Companies, Inc Information Technology & Management Thompson Cats-Baril Chapter 3 Content Management.
Business Intelligence Solutions for the Insurance Industry DAT – 13 Data Warehousing Rasool Ahmed.
Data Warehouse Concepts Transparencies
Data Warehouse Overview September 28, 2012 presented by Terry Bilskie.
Data warehousing and online analytical processing- Ref Chap 4) By Asst Prof. Muhammad Amir Alam.
2 Copyright © Oracle Corporation, All rights reserved. Defining Data Warehouse Concepts and Terminology.
OLAP & DSS SUPPORT IN DATA WAREHOUSE By - Pooja Sinha Kaushalya Bakde.
1 Reviewing Data Warehouse Basics. Lessons 1.Reviewing Data Warehouse Basics 2.Defining the Business and Logical Models 3.Creating the Dimensional Model.
1 Categories of data Operational and very short-term decision making data Current, short-term decision making, related to financial transactions, detailed.
5 - 1 Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
Building Data and Document-Driven Decision Support Systems How do managers access and use large databases of historical and external facts?
Decision Support and Date Warehouse Jingyi Lu. Outline Decision Support System OLAP vs. OLTP What is Date Warehouse? Dimensional Modeling Extract, Transform,
Datawarehouse A sneak preview. 2 Data Warehouse Approach An old idea with a new interest: Cheap Computing Power Special Purpose Hardware New Data Structures.
6.1 © 2010 by Prentice Hall 6 Chapter Foundations of Business Intelligence: Databases and Information Management.
MANAGING DATA RESOURCES ~ pertemuan 7 ~ Oleh: Ir. Abdul Hayat, MTI.
1 Categories of data Operational and very short-term decision making data Current, short-term decision making, related to financial transactions, detailed.
Data Warehouse. Group 5 Kacie Johnson Summer Bird Washington Farver Jonathan Wright Mike Muchane.
© 2007 IBM Corporation IBM Information Management Accelerate information on demand with dynamic warehousing April 2007.
By N.Gopinath AP/CSE. There are 5 categories of Decision support tools, They are; 1. Reporting 2. Managed Query 3. Executive Information Systems 4. OLAP.
AL-MAAREFA COLLEGE FOR SCIENCE AND TECHNOLOGY INFO 232: DATABASE SYSTEMS CHAPTER 1 DATABASE SYSTEMS Instructor Ms. Arwa Binsaleh.
Chapter 5 DATA WAREHOUSING Study Sections 5.2, 5.3, 5.5, Pages: & Snowflake schema.
The Data Warehouse “A data warehouse is a subject-oriented, integrated, time-variant, and nonvolatile collection of “all” an organisation’s data in support.
DATA RESOURCE MANAGEMENT
© 2003 Prentice Hall, Inc.3-1 Chapter 3 Database Management Information Systems Today Leonard Jessup and Joseph Valacich.
Why BI….? Most companies collect a large amount of data from their business operations. To keep track of that information, a business and would need to.
Advanced Database Concepts
1 Categories of data Operational and very short-term decision making data Current, short-term decision making, related to financial transactions, detailed.
Data Resource Management Agenda What types of data are stored by organizations? How are different types of data stored? What are the potential problems.
1 Copyright © Oracle Corporation, All rights reserved. Business Intelligence and Data Warehousing.
MBA/1092/10 MBA/1093/10 MBA/1095/10 MBA/1114/10 MBA/1115/10.
1 Management Information Systems M Agung Ali Fikri, SE. MM.
Data Warehouse – Your Key to Success. Data Warehouse A data warehouse is a  subject-oriented  Integrated  Time-variant  Non-volatile  Restructure.
The Concepts of Business Intelligence Microsoft® Business Intelligence Solutions.
2 Copyright © 2006, Oracle. All rights reserved. Defining Data Warehouse Concepts and Terminology.
Data Mining and Data Warehousing: Concepts and Techniques What is a Data Warehouse? Data Warehouse vs. other systems, OLTP vs. OLAP Conceptual Modeling.
Business Intelligence Overview
Advanced Applied IT for Business 2
Defining Data Warehouse Concepts and Terminology
Chapter 13 The Data Warehouse
Defining Data Warehouse Concepts and Terminology
Chapter 1 Database Systems
انباره داده Data Warehouse
Data Warehouse Overview September 28, 2012 presented by Terry Bilskie
Data Warehouse.
Chapter 1 Database Systems
Chapter 3 Database Management
Analytics, BI & Data Integration
Database Systems: Design, Implementation, and Management Tenth Edition
Presentation transcript:

2005 Ratemaking Seminar ACTUARIAL DATA MANAGEMENT (ADM) IN A HIGH-VOLUME TRANSACTIONAL PROCESSING ENVIRONMENT Joe Strube and Bryant Russell GMAC Insurance, Southfield, Michigan

2005 Ratemaking Seminar  Goal of the ADM Function Equip the Actuarial Staff with the data resources necessary to excel in the performance of their functions Not simply “get the actuaries data” Add value to their analytical processes C.A.T. Criteria –Complete (Collect, Consolidate, Derive) –Accurate (Clean dirty/distorted data) –Timely (Prioritize data resource deliveries) Possibly assume responsibility for next stage

2005 Ratemaking Seminar  What Is A High-Volume Transactional Processing Environment (HVTPE)? Frankly, It’s Arbitrary! Online Transaction Processing System (OLTP) Mainframe/Midrange Server Extract Files Operational Data Store (ODS) Data Warehouse (DW) Data Mart (DM) Desktop DB Consider your most granular actuarial data resource Are 1 million or more transactions added per month? If YES, you’re operating in an HVTPE

2005 Ratemaking Seminar  ADM, An Outgrowth of End User Computing Rockart & Flannery Research Study (1983) Sloan School of Management at MIT Interviewed 250 People 3 Fortune 50 Manufacturers 2 Major Insurance Companies 3 Sizable Canadian Companies Identified Six Types of End Users Non-Programming End Users Command Level Users End User Programmers Functional Support Personnel End User Computing Support Personnel DP Programmers

2005 Ratemaking Seminar The Square Root of 12,345,678,987,654,321 is 111,111,111

2005 Ratemaking Seminar  As Technology Evolves, So Do Deliverables Mainframe to Minicomputer to Microcomputer (PC) Complex mainframe programs Originally produced reports Historical data files Data downloads Data Management Technology Branches Out Data Warehousing Data Marts Online Analytical Processing (OLAP) Extraction-Transformation-Loading Software (ETL) Meta Data Repositories Decision Support Systems Data Profiling/Cleaning/Integration Software Data Mining

2005 Ratemaking Seminar  Modern Roles in End User Computing Non-Programming End Users (Business Manager, Process Modeler, Trainer) Command Level Users (HR Rep, Accountant, Claim Analyst, Market Analyst) End User Programmers (Actuary, Financial Analyst, Strategic Planner) Functional Support Personnel (Data Manager/Administrator, Actuarial Technician) End User Computing Support Personnel (Help Desk, User Hotline, DSS Analyst, DW Support Team) DP Programmers (a.k.a. Systems Analyst) (Internal/Outside Contractor, Technical Consultant)

2005 Ratemaking Seminar  Key Roles for ADM in a HVTPE The Actuary The Actuarial Technician Information Technology Dept. (IT)

2005 Ratemaking Seminar  HVTPE and The Role of the Actuary HVTPE offers the opportunity to work with detailed, granular data Classification Analyses GLM Analyses Loss Distributions Data Mining Comparison of data sources across functional areas becomes possible Policy Year vs. Accident Year vs. Calendar/Accident Year “slices” can be reconciled more easily Common data source overcomes the “my data-your data” syndrome

2005 Ratemaking Seminar  The Role of the Actuary HVTPE is inherently multidimensional Transactional data is very granular, detailed Multiple views can be aggregated from common source (transactional data) Very useful for examining interactions between factors As a “source”, HVTPE allows actuarial data repositories to be created, stored, and maintained over time Actuary can select data based on actuarial value Less reliance on non-actuarial reports

2005 Ratemaking Seminar  Q: Why not let the actuary do it all? Many actuaries well-versed with database and analytical software But data from HVTPE is just the first step Data extraction is input to analyses Actuarial work typically requires more than just a summary report of historical experience Data extraction process can overwhelm traditional desktop tools Over 1 million transactions per month Even data storage, can overwhelm desktop resources available to actuary

2005 Ratemaking Seminar  Q: Why not let others (ADM) do it all? Data specialization enables more robust process of gathering, storing, reporting data Data skills are specialized Software and hardware can be “industrial strength” Monitoring, balancing, aggregating are important, but non-actuarial tasks HVTPE is not a static environment Changes to data definitions Addition of new data elements Addition of new data sources

2005 Ratemaking Seminar  Q: Why not let others (ADM) do it all? Value of actuarial data elements may be seen as secondary to other functional areas Required level of detail for actuarial analysis is different Historical retention periods are different Specific data elements may be uniquely valuable to the actuary – other areas would not gather/maintain these. Actuarial data needs are dynamic Summary level varies by type of actuarial analysis Variables included can range from few to many Not realistic to try & build all possible aggregations ahead of time (OLAP tools notwithstanding)

2005 Ratemaking Seminar  The Role of the Actuary Identify the value of actuarial data Critical Data Elements Actuarially Valuable Data Elements Nonessential Data Elements (for actuarial analysis) Determine required level of detail Granularity of data (e.g. at transactional level) Historical time periods and retention periods Definitions of derived data (e.g. books of business, classes, etc.) Support the Value Proposition of Data Dictionary What does the data mean? What are meaningful values? Have definitions, coding, accuracy, completeness changed over time?

2005 Ratemaking Seminar  The Role of the Actuarial Technician Data Facilitator Building Inspector Lawyer Guinea Pig Data Supplier Fulcrum Sculptor Magician

2005 Ratemaking Seminar  The Role of IT Management Manage Infrastructure Manage Corporate Projects

2005 Ratemaking Seminar  Data Management Processes Data Modeling, Metadata, Data Dictionary Data Extraction, Profiling, Quality Data Integration, Transformation Data Loading Not Data Retrieval, Reporting

2005 Ratemaking Seminar There are 336 cavities on a golf ball.

2005 Ratemaking Seminar  GMAC Insurance Case Study Vehicle Service Contracts Multiple period contracts – under 12 months to over 84 months Multiple countries and business partners Multiple data sources Over 1 million transactions per month

2005 Ratemaking Seminar  GMAC Insurance Case Study Vehicle Service Contracts Multiple period contracts – under 12 months to over 84 months Multiple countries and business partners Multiple data sources Over 1 million transactions per month

2005 Ratemaking Seminar Q & A

2005 Ratemaking Seminar In Nawlins... It’s mandatory to jazz things up!