Located in:
- III. Operational Planning ElementsThe Unified or Combined State Plan must include an Operational Planning Elements section that support the State’s strategy and the system-wide vision described in Section II.(c) above. Unless otherwise noted, all Operational Planning Elements apply to Combined State Plan partner programs included in the plan as well as to core programs. This section must include—
- b. State Operating Systems and PoliciesThe Unified or Combined State Plan must include a description of the State operating systems and policies that will support the implementation of the State strategy described in Section II Strategic Elements . This includes—
- 6. Program Data
- A. Data Alignment and IntegrationDescribe the plans of the lead State agencies with responsibility for the administration of the core programs, along with the State Board, to align and integrate available workforce and education data systems for the core programs, unemployment insurance programs, and education through postsecondary education, and to the extent possible, the Combined State Plan partner programs included in this plan. The description of the State’s plan for integrating data systems should include the State’s goals for achieving integration and any progress to date.
- A. Data Alignment and Integration
- 6. Program Data
- b. State Operating Systems and Policies
III. b. 6. A. ii. Describe the State’s Plans to Integrate Data Systems to Facilitate Streamlined Intake and Service Delivery to Track Participation Across All Programs Included in This Plan.
Current Narrative:
Streamlined intake and service delivery across the MIS’s of WIOA Combined plan partners would be a very complicated project, not to be undertaken without thorough assessment of feasibility and schedule — nor without realistic expectations about the availability of funds and expertise. The existing MIS’s vary greatly in technology, vintage, complexity, confidentiality and security rules and interaction with other systems. Outside of the Title 1 & 3 programs, almost every other program operates under a completely different MIS.
As there have been no potential sources identified for either federal or state funding of the magnitude required for a major common intake and service delivery project, the state’s initial efforts will be concentrated on more affordable strategies to provide a small number of key data across system partners on a near “real—time” basis. The approach is derived from the Client Registry operated across the ten divisions of DSHS. The basic approach is to identify a very limited set of key data elements, to be updated frequently on a new central database, and made available over an appropriate interface within each of the component systems. In the case of WIOA, the key information identified so far are the information necessary to unduplicate a person known to more than one MIS, which programs the person is known to, and the current service status of that person. It is not clear whether funds will be available for even this limited type of automated operational data exchange. Cost estimates for this or more ambitious approaches to operational data sharing or interoperability compete with other WIOA and non—WIOA demands on a limited number of agency staff with the requisite knowledge — and may be premature until final federal data specifications are available.
Retrospective tracking of services across programs for reporting and program assessment purposes is already conducted on an annual basis by the Workforce Board or many of the proposed Combined Plan partners, and will be continued and modified under WIOA. This is much less complicated and expensive than operational implementation of common intake and service delivery systems across different MIS’s.