Statewide Data Architecture and Exchange. Problem Data not standardized, consistent, or aligned...
-
Upload
moses-douglas -
Category
Documents
-
view
215 -
download
1
Transcript of Statewide Data Architecture and Exchange. Problem Data not standardized, consistent, or aligned...
StatewideData Architecture
andExchange
Problem
Data not standardized, consistent, or aligned with business needs
Citizens/Customers of state services are impacted and inconvenienced
We have: an IT project centric model We lack: understanding of the
magnitude of the problem or the quality of the data
2
Goals
Identify principles, strategies & models to:Standardize state data architectureReduce data management costsMake state services convenient to useDevelop a state data governance
3
Research
Personal interviewsMelissa Cook – MA Cook CorporationRoss Hunter –Representative, 48th DistrictTony Tortorice – State Chief Information OfficerDavid Zager – State Enterprise Architect
4
Research (cont.)
Federal data standards Other state’s data architecture models
MichiganCaliforniaConnecticutMissouri
WA state agency documentation (ISB, EAC, DOT)
Informal interviews with data experts5
Principles
Keys to achieving an effective data architecture strategyMaster Data ManagementCustomer Data IntegrationData governance
6
Principles (cont.)
Master Data ManagementFramework of processes & technologies Authoritative, reliable, sustainable,
accurate, & secureSingle version of the truthData cleaned, rationalized, validated, and
integrated into a statewide “system of record”
7
Principles (cont.)
Why Master Data Management?Consistent data managementCustomer-centric business model Single master data setComplete pictureReduces costs and errorsHigher trust value
8
Principles (cont.)
Customer Data IntegrationData consolidation techniqueVarious sourcesSingle source of truthCustomer data integrity
9
Principles (cont.)
Why Customer Data Integration?Creates value for the customerEliminates duplicative effortsCustomers own, update, & manage
10
Principles (cont.)
MDM & CDI Implementation ChallengesOrganizational and political obstaclesFear others may use data inappropriatelyCreation of a master data facilityHoarding and proliferation of duplicate dataData standards governed by other agenciesDetermining the data source to make masterSemantic inconsistency in data attributesDifferent business rules to transform dataAgreeing on who maintains the data
11
Principles (cont.)
Data GovernanceA quality control discipline for assessing,
managing, using, improving, monitoring, maintaining, and protecting organizational information
Supports…Decision makingAssigning accountabilityIdentifying business rulesDefining processes
12
Principles (cont.)
Data Governance (cont.)Helps…
Meet regulatory compliance mandatesIncrease revenue opportunitiesDecrease expendituresBuild better citizen, customer, & partner
relationships
13
Principles (cont.)
Governance ChallengesBusiness objectives conflict or interfereResources are limited or are in competitionPolitical agendasTerritorial issuesUnrealistic expectationsLack of organizational support & acceptanceReluctance to evaluate & redesign current
business processes
14
Approaches to Data Architecture
Super HeroSingle individual who ultimately fails
All or Nothing To achieve success…”boil the ocean”
Top-DownMost common, executive order, a state
priority, years before a return is recognized Iterative
Smaller data sets, measureable results15
Recommendations
Iterative Approach to Data Architecture Master Data Management (MDM) Customer Data Integration (CDI) Data Governance
16
Recommendations (cont.)
Why this strategy?Authorizing environmentEconomic conditionsLow state maturity levelGrowth from existing rootsPrinciples and methods of othersOpportunities for external fundingCitizen-centric
17
19
State of Washington ISB
Data Governance Committee
(DGC)
Senior Executive Sponsor
Data Creator Data
Steward
Data User
Provides oversight of the DGC
Appointed by the Governor
Data Creator, Data Steward and Data User represent state agencies.
Structure of Proposed Data Governance Committee
Members of the Committee· Student Achievement· Postsecondary Learning· Health· Vulnerable Children & Adults· Economic Vitality· Mobility· Public Safety· Natural Resources· Culture & Recreation· State Government
Recommendations (cont.) Data Standards Implementation &
Governance (cont.)Committee & Experts expectations
“System of record” for a subject domainComplete data set to grow businessImprove citizen-government interactions
10-year planning window
20
Recommendations (cont.) Data Standards Implementation &
Governance (cont.)First steps already underway
Data standards: Commodity codes, EmailVoluntary efforts: ESD - DOL
Next StepsInventory of all statewide systems, baseline3 to 4 initial data elementsData dictionary
21
Summary
Know your limits Learn from their successes or challenges Don’t reinvent the wheel It’s a long road…don’t rush it Understand the business problem Show value to the citizen
22
Questions? Will Saunders, DIS
[email protected] Susie LaPalm, DOP
[email protected] Randy Baker, WSDOT
[email protected] Rathnavel “Vel” Rajagopal, ESD
[email protected] Doug Beam, OFM
23