1 / 32

EXPRESS SCRIPTS

Express Scripts Enterprise Data Warehouse Joe Federer, Senior Director. EXPRESS SCRIPTS. A bit about the Journey. Introduction Business Story Implementation – SuperBowl Sunday Enterprise Logical Data Model Summary.

eugenia-parsons
Download Presentation

EXPRESS SCRIPTS

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Express Scripts Enterprise Data Warehouse Joe Federer, Senior Director EXPRESS SCRIPTS

  2. A bit about the Journey • Introduction • Business Story • Implementation – SuperBowl Sunday • Enterprise Logical Data Model • Summary

  3. “Our health is far behind the progress of medical science…Proper medical care is so expensive that it is out of reach of the great majority of our citizens.” Who Said It??? • George W. Bush • William J. Clinton • Lyndon B. Johnson • John F. Kennedy • Harry S. Truman State of the Union address - 1949

  4. Demographics Are Crucial • growing • aging • getting heavier The Population is…

  5. Who Is Express Scripts? Contact Centers • Arizona • Colorado • Georgia • Michigan • Minnesota • Missouri • New Mexico • New York • Pennsylvania Home Delivery • Arizona • Missouri • New Mexico • Pennsylvania Corporate Headquarters: St. Louis, Missouri Coming soon to a campus near you

  6. Revenue Growth with Acquisitions Specialty Platform Labor/ NE/ SG&A Managed Care / Rebates / SG&A Large Employer/ Mail Middle Market Millions

  7. Data Marts New Enterprise Logical Data Model Teradata Teradata Implementation - Progression Pharmacy Reference s t a g e DB-2 Adjudication Decision Support RS-6000 SP-2 8 nodes AIX 4.3 DB-2 4 TB / 1.8 TB Data Marts RS-6000 SP-2 2 nodes AIX 5.1 DB-2 800 GB / 200 GB April 2006 Q1 2007 Operational DW DB-2 2 TB Feb 2006 Client Ad-Hoc RS-6000 SP-2 1 nodes AIX 5.1 DB-2 200 GB / 50 GB April 2006 Client Portal P690 AIX 5.1 UDB 2 TB /800 GB July 2006 On-going

  8. “Tall and Skinny” to EDW

  9. “Tall and Skinny” to EDW t5 t1 t2 t3 t4 Specialty GL/Finance Claims Contact Member Benefit Home Delivery Prescriber Drug Sales

  10. Goal State Architecture – EDW Operational Data Repository • New Integration Technologies to provide a consistent mechanism for application integration and data inquiry services (ESB/SOA). • High availability in the Data Warehouse Teradata, Informatica, Business Objects, and Web environments. • Active feeds from operational systems into the warehouse via consistent integration technologies. • Inquiry services reference a single data source in many cases. • Operational Business Intelligence is enabled by loading transactions into the EDW in near real-time. Enterprise Service Bus

  11. Enterprise Logical Data Model

  12. And Now… • A shameless sales pitch for a career at Express Scripts…

  13. Our Work Matters • We serve patients and clients • We align our interest with clients • We add value to help us grow • We make this a positive place to work

  14. Information Technology We develop great people We deliver world-class system performance & reliability We build solid platforms and architecture We deliver innovative business solutions We develop solid strategic plans We are developing top talent for tomorrow’s leaders.

  15. How to Apply: • Visit www.express-scripts.com • Click on Careers under “Our Company” • Click on Opportunities at Express Scripts • Select a location or “All” in the Location drop-down list • Select “Intern Opportunities” in the Job Category drop down list • Fill out the application online Watch for Internship job descriptions online after Oct. 16th

  16. Conclusions • Good Roadmap • Fostered Executive Buy-in • Continue to Deliver on Strategy • And… consider Express Scripts…

  17. BACKUP

  18. Desired Situation • Data Warehouse as an enterprise information asset. • Business driven implementation. • Re-use and leverage of intellectual property. • Phased delivery for managing risk and maximizing ROI. • Efficiency in deployment. • Extensibility for new applications and data content. • Consistent enforcement of privacy and security policies.

  19. An Analogy Imagine that you are building a city... How would you go about doing it?

  20. An Analogy First Method: Construct neighborhoods of the city as required on an as-needed (ROI justified) basis. • Each neighborhood is constructed based on the needs of its constituency and pre-existing neighborhood infrastructure. • Each constituency pays only for its neighborhood construction costs. • As the city evolves and expands, invest in appropriate re-engineering to meet new requirements.

  21. An Analogy Example Result: Boston. • Numerous one-way streets and dead ends. • Difficult to navigate. • Non-extensible without major costs. • e.g., “The Big Dig” • New neighborhoods not well integrated.

  22. An Analogy Second Method: Invest in an up-front city plan as a “blueprint” for city design. • Requires infrastructure investment prior to constructing first neighborhood. • Funded by “city tax” across all constituents. • City plan provides high level framework, not the detailed design. • Each neighborhood construction project adheres to the city plan (blueprint). • Each constituency pays for its detailed design and construction costs. • Extensibility built into the city plan.

  23. An Analogy Example Result: Toronto. • Investment and vision applied prior to actual construction. • Extremely “user friendly” city. • Extensibility of infrastructure anticipated in city design and overall cost is minimized. • e.g., Toronto subway. • New neighborhoods easily added without straining infrastructure.

  24. An Analogy The Enterprise Data Model for your Data Warehouse is like the City Plan for designing a Metropolis. Efficient and extensible deployment of a Data Warehouse requires an Enterprise Data Model. Note that disciplined adherence to blueprint is a pre-requisite to success.

  25. Implementation and Deployment There is a spectrum of implementation approaches for a data warehouse – each with a different set of investment tradeoffs. • Independent PDM (Physical Data Model) for each domain of analytic applications (e.g., marketing, pricing, medical management, etc.). • Incremental deployment of enterprise PDM with re-engineering appropriate to each phase of delivery. • Phased deployment of PDM within an enterprise LDM framework.

  26. Implementation and Deployment The Enterprise Logical Data Model provides a framework for building the 80% once rather than once for each domain of analytic applications. • Estimated cost for independent multi-mart approach is 70% higher than for phased implementation using an Enterprise LDM framework. • Estimated cost for incremental deployment of enterprise PDM without Enterprise LDM is 20-30% higher due to re-engineering requirements in each phase.

  27. Implementation and Deployment The blueprint provided by an Enterprise Logical Data Model allows extension of data content in the warehouse via enhancement to data domains and data relationships... ...without re-engineering the data model for each new application or data source.

  28. Implementation and Deployment Avoid “big bang” approach to data modeling: • Goal is to create a conceptual data model to act as blueprint for the enterprise. • Do not get caught up in detailed sub-typing, attribution, or data typing for entities. • Complete conceptual model and opportunity analysis within four months of start date.

  29. Funding Model • High-level design of conceptual ELDM performed across business units and funded as infrastructure investment as pre-requisite to data warehouse construction. • Detailed design and population of ELDM is justified by specific ROI opportunities. • Conceptual ELDM deliverable is focused on what is necessary for extensible delivery of the data warehouse solution. • Detailed design of ELDM is delivered incrementally with each ROI opportunity.

  30. “TheBusinessUser” “TheBusinessUser” Business Value Business Value IT Development IT Development “TheITProvider” “TheITProvider” Member Reporting Churn Growth Customer Churn Growth Customer Churn Growth Customer Member Billing Billing Billing Think Big, Start Small Member Reporting EnterpriseParadigm Member (150) DepartmentParadigm (150)

  31. “TheBusinessUser” “TheBusinessUser” Business Value Business Value IT Development IT Development “TheITProvider” “TheITProvider” Member Reporting Medical Management Churn Growth Customer Churn Growth Customer Churn Growth Customer Member Member + Claims Billing Billing Billing Think Big, Start Small MemberReporting + Medical Management EnterpriseParadigm Claims Member (150) (120) DepartmentParadigm (150) (260)

  32. Optimized cost structure Store once, use many Single view of enterprise “TheBusinessUser” “TheBusinessUser” Business Value Business Value IT Development IT Development “TheITProvider” “TheITProvider” Inforce Reporting Medical Management Churn Growth Customer Churn Growth Customer Churn Growth Customer Member Member + Claims Billing Billing Billing Think Big, Start Small Member Reporting + Medical Management + Financial Analysis EnterpriseParadigm Claims Revenue Member (150) (120) (110) Financial Analysis DepartmentParadigm Member + Claims + Revenue (150) (380) (260)

More Related