This Presentation covers Getting Started, Business Drivers, Business Intelligence and the Role of an Enterprise Data Model.

1. Data Standardisation in the Public Sector
BI in the Public Sector - Ark Conference
Barry Williams
Principal Consultant
Database Answers
July 10th. 2012
1

2. Data Standardisation in the Public Sector
Overview
• Business Drivers
• Getting Started
• Framework for BI and Performance Mgt
• Enterprise Data Model
• Data Standardisation Layer
2

3. Data Standardisation in the Public Sector
Business Drivers
• Typical Organisation has over 200 Legacy Systems
• 300,000+ customers
– Ethnic Origin Breakdown ?
– Customers receiving multiple Services ?
• Need Single View of the Customer
• Standards are ESSENTIAL for BI
3

4. Data Standardisation in the Public Sector
Getting Started
• Identify Business Champions
• Decide the Approach
• Determine the Standards
• Data Quality Audit
4

5. Data Standardisation in the Public Sector
Getting Started (a)
• Identify Business Champions
• With Vision
• High-Profile Service
• Successful Track-Record
5

6. Data Standardisation in the Public Sector
Getting Started (b)
• Decide the Approach
•Top-Down and/or Bottom-Up
• POC or ‘Feasibility Study’
• Management Involvement
• Success Criteria
6

7. Data Standardisation in the Public Sector
Getting Started (c)
• Determine the Standards
•Easy where defined
• LGSL /IPSV, BVPIs
• Look for obvious Data Leaders
• eg Social Services for Ethnic Origins
• Create Glossary for Mapping
•Aim for Buy-In
7

8. Data Standardisation in the Public Sector
Getting Started (d)
• Data Quality Audit
• Sell the Importance
• Prepare a Business Case
• Carry out Enterprise-wide
• Data Profiles suggest Standards
• Obtain Buy-In from ‘Data Stewards’
8

9. Data Standardisation in the Public Sector
Framework for Performance Management
Participants
• Directors, Managers, Business Partners,etc.
Policies and Procedures Performance Reporting
• Best Practice • Traffic Lights
• Contract Terms and Conditions • Key Performance Indicators
• Job Specifications • BVPIs (Cognos Metrics)
• Rules and Regulations • Drill-Down
• Etc. • Reports, etc.
Data Standardisation Layer
• Enterprise Data Model
• Single View of the Customer
• LGSL (Cognos Decision Stream), etc.
9

10. Data Standardisation in the Public Sector
Single View of the Customer
• Requires Standards to Consolidate Data
• Needs Customer Data Integration Software
• eg DataFlux -www.dataflux.com/Implementations/CDI.asp
Customer
- Date
- Standard Debt Type
- Amount
Business Council Tax Housing Parking Rent
Rates Benefits Fines Arrears
Overpayments
10

11. Data Standardisation in the Public Sector
Building the Data Foundation
• Each Stage builds on the previous one
5) BI Data Mart
4) Customer
Services
3) Customer
Master Index
2) Services
- Directorate
- Service Name
1) Properties
- Gazetteer
11

12. Data Standardisation in the Public Sector
Enterprise Data Model (EDM)
• Comprehensive, Generic and Unique
• A Standard way to integrate Customer Data
• Property with Gazetteer, Services with LGSL
• Over 200 Entities in 14 Functional Areas
• Defines Data Standardisation Layer in SOA
• Provides Foundation for Data Marts
12

13. Data Standardisation in the Public Sector
EDM Diagram Extract
Customer Area
Property Area Service Delivery Area
Customer
Geographic_Address - Organisation Service Catalogue
(Std = Gazetteer LLPG) - Person (Std=LGSL/IPSV)
Customer_Address_Occupancy Service_Request
13

14. Data Standardisation in the Public Sector
Data Standardisation Layer
CRM Self-Service Portal BI Data Marts
- Customer Profiles - Enquiries - Social Services
- Good/Bad Customers (SOA Tibco Portal Builder) - Street Environment
- BVPIs, IEG Returns
DATA STANDARDISATION LAYER
- Mapping from Vendor-specific to Ealing Standards,(LGSL, e-GIF, Ethnic Origins, etc.)
- Customer Master Index, Enterprise Data Model
(SOA Tibco Smart Mapper and Master Data Management)
Services Customers Customer Histories
- ERDMS File Plan - Matches - Links to LOBs
- LGSL / IPSV (Govt Standard)
Reference Data Data Quality Audit
- Ethnic Origins - Data Profiling Lines of Business
- Vehicle Makes and Models - Gazetteer Validation (LOBs)
14

15. Data Standardisation in the Public Sector
Mapping from Vendor to BI Data
• Example from Street Environment Services
BI Data Mart
Vendor Code LGSL Code Service BVPI
STC 580 Litter BV199a
GRA 584 Graffiti BV199b
FP 588 Fly-Posting BV199c
FLY 587 Fly-Tipping BV199d
15

16. Data Standardisation in the Public Sector
Debtors Warehouse Star Schema
DW_Time_Periods
Data Warehouse for Debtors Period Number
The Total Amount of Debt can be Period Name
analysed by Service, Date or Customer. Period End Date
eg 10, Jan 2005, 31/01/05
DW_Debt_Amounts
Record ID
Date Account Created
DW_Services
Debt raised YTD
Service Name Revenue received YTD
Service Description Debt written-off YTD DW_Customer_Accounts
Directorate Debt outstanding per BU
Account Number
Status - eg School Percentage Target
Business Unit Percentage Actual Customer Group Name
Section Name Red Amber Green Status Customer Address
eg Council Tax Amount 90 days and Under Customer Type
eg Housing Benefits Overpayment Amount 91-120 Days eg Person or Organisation
eg Housing Rent Amount 121-150 Days
eg Mortgage Payment Amount 151-180 Days
eg Parking Fine Amount 181-210 Days
Amount Over 211 Days
Comments - What is the Over 211 day debt ?
Comments - What is status/action on Over 211 day debt ?
16

17. Data Standardisation in the Public Sector
Top-Level KPI Control Panel (1)
• Clickable Control Panel showing Traffic Lights
17

18. Data Standardisation in the Public Sector
Top-Level KPI Control Panel (2)
• Clickable Control Panel is in left-hand corner
18

19. Data Standardisation in the Public Sector
Area-Level Display
LB Ealing Licence no. LA100019807 2006
19

20. Data Standardisation in the Public Sector
Local Area-Level Display
LB Ealing Licence no. LA100019807 2006
20

21. Data Standardisation in the Public Sector
Street-Level Display
LB Ealing Licence no. LA100019807 2006
21

22. Data Standardisation in the Public Sector
Next Steps
• Add to Customer Master Index & CRM
• Define Templates for Proof of Concepts
• Create KM Communities of Practice
• Formalise Standardisation of Best Practice
22