The Employment Development Department (EDD) in California administers one of the nation's largest public benefit systems with over 21 million claimants and 63 million claims being filed for Unemployment Insurance (UI), Disability Insurance (DI), and Paid Family Leave (PFL) over the past decade. The EDD organization also supports many auxiliary business functions for hundreds of thousands of employers, medical providers, and other stake holders.
One significant objective of the EDDNext project is to create a seamless and consistent user experience across all of EDD’s different benefit programs and channels even through each program has vastly different processes, technologies, legal requirements, and customer needs. From the customer’s perspective all services come from EDD and so interactions and experiences should be consistent across programs and channels.
In order to achieve improvements, efficiencies, and uniformity across multiple program areas, EDD is going through transformation processes that incorporate several planning initiatives, standardization efforts, foundational changes, and input from multiple programs.
Currently, EDD operates multiple disparate data governance structures involving many stakeholders. This disparity introduces complexity and segregation of solutions amongst EDD business programs. The EDDNext project aspires to establish a singular data governance model supporting a primary data governance structure that will become the enterprise-wide standard, and will evolve, adapt, and mature as the project progresses.
As a results of these data standardization changes, we foresee the following challenges:
- An absence of existing data standards across multiple business programs
- Establishment of a unified data governance model and vocabulary across the programs and enterprise
- Potential delays in data governance reviews and approvals due to the volume of processes and concurrent / conflicting timelines
- Potential risk of data duplication across benefit programs
- Current lack of a singular, unified customer record across the benefit programs
- Inconsistencies in data dictionaries and catalog management across systems
- Senior stakeholders are stretched thin as they must often participate in multiple data governance structures
- Lack of consistent data formatting and editing controls for impending requisite data migrations and interface processes
- Absence of a comprehensive data management lifecycle
- Inconsistent data quality management