U.S. flag

An official website of the United States government

Dot gov

Official websites use .gov
A .gov website belongs to an official government organization in the United States.

Https

Secure .gov websites use HTTPS
A lock () or https:// means you’ve safely connected to the .gov website. Share sensitive information only on official, secure websites.

Plan: Washington PYs 2016-2017
Combined Plan C

Section: Unemployment Insurance Program

Narrative: a. 4.

Published
Located in:
  • Unemployment Insurance (UI)

    The Jobs for Veterans’ State Grants (JVSG) are mandatory, formula-based staffing grants to (including DC, PR, VI and Guam). The JVSG is funded annually in accordance with a funding formula defined in the statute (38 U.S.C. 4102A (c) (2) (B) and regulation and operates on a fiscal year (not program year) basis, however, performance metrics are collected and reported (VETS-200 Series Reports) quarterly (using four “rolling quarters”) on a Program Year basis (as with the ETA- 9002 Series). Currently, VETS JVSG operates on a five-year (FY 2015-2019), multi-year grant approval cycle modified and funded annually.

    In accordance with 38 U.S.C. § 4102A(b)(5) and § 4102A(c), the Assistant Secretary for Veterans' Employment and Training (ASVET) makes grant funds available for use in each State to support Disabled Veterans' Outreach Program (DVOP) specialists and Local Veterans' Employment Representatives (LVER) staff. As a condition to receive funding, 38 U.S.C. § 4102A(c)(2) requires States to submit an application for a grant that contains a State Plan narrative, which includes:

a. 4. Corrective Action Plans (caps)

Corrective Action Plans (CAPs): CAPs are expected as a part of the SQSP when State’s annual performance does not meet the established criteria for core measures, Secretary’s Standards, UI program, assurances, and other program deficiencies identified in the annual SQSP guidance provided by the Department. The CAP must list both specific milestones for key corrective actions or improvement activities, and the completion date for each milestone.

Current Narrative:

First Pay Promptness

A. Reason for the deficiency:

As mentioned in our non-monetary timeliness CAP, UI Claims Centers have struggled with staff resources for the past three years, due to reductions in force and deployment of staff to projects such as our new UI benefit system replacement. These vacancies have created opportunities for intake staff to promote to adjudication, further reducing the staffing available for initial claims taking. This has, at the end of the period, resulted in a drop in performance below the ALP for first payment promptness.

Washington continues to use Lean methodologies to improve processes and make gains on quality and timeliness of payment. However, the department took on a major technology project to upgrade our UI benefits computer system, which will come online in fall 2016. To assist with the success of this project, many of the "best and brightest" program staff were deployed to the project as business analysts and subject matter experts. We expect this painful investment to pay substantial dividends when the new system is deployed.

B. Provide a description of your “Plan-Do-Check-Act” corrective action plan which will be undertaken to achieve the acceptable level of performance:

The performance levels of late reflect the substantial investment of time and talent that we have made in getting the new system correctly programmed to meet our needs. As that system comes online, we expect much of the pressure to be relieved and to begin work on what issues remain.

As we prepare for the system’s deployment, all benefits staff will invest several days in training and process reengineering during the quarter prior to deployment. As such, we do not anticipate our numbers will immediately improve in the first two quarters of this CAP. Claims Centers have recently hired several new intake agents, who are currently beginning training for entry-level claims center work. While this training takes several weeks before the agents are available to assist with regular work, it does represent an investment toward future resource stability as we move into the new UI benefits system.

Technical training for all staff using the new UI Benefits system has so far consisted of 2.5 days of familiarization with the new program. During October and November 2016, all staff will receive up to ten more days of training on up to seventeen different modules, specifically oriented to each staff’s job description. This is to ensure staff can work efficiently in the new computer system on Day One, minimizing downtime and errors in the first weeks.

C. Previous years’ plan:

Not applicable

D. Plans for monitoring and assessing accomplishment of planned actions and for controlling quality after achieving performance goals:

UI benefits managers continue to monitor claim center metrics on a weekly basis, and adjust resources as available.

Milestones:

1. Complete all staff technical training in new UI Benefits system before Go-Live date in November 2016 - 100% staff in intake and adjudication units. (12/31/2016)

2. Complete intake and adjudication process (classroom and OJT) training for newly-hired staff cohorts (timeline TBD). (6/30/2018)

3. Implement ("Go-Live") new UI Benefits system in November 2016. Resolve any remaining technical issues with project vendor and IT staff. (3/31/2018)

4. Reintegrate 20 business analyst staff assigned to UI Benefits system (UTAB) project into claims center staffing, returning to fully-staffed levels of operation. (6/30/2017)

5. After system implementation, complete business process analysis to assess performance of new system and develop plan to address any performance issues that emerge. Plan will include timelines for improvements and corrections. (3/31/2018)

Nonmonetary Determination Timeliness

A. Reason for the deficiency:

Washington has struggled with nonmonetary determination timeliness for the past three years. The two main reasons for this have been reduced staffing levels due to technology investments, and challenges with current outdated computer systems.

Washington continues to use Lean methodologies to improve processes and make gains on quality and timeliness of payment. However, the department took on a major technology project to upgrade our UI benefits computer system, which will come online in Fall 2016. To assist with the success of this project, many of the "best and brightest" program staff were deployed to the project as business analysts and subject matter experts. We expect this painful investment to pay substantial dividends when the new system is deployed.

B. Provide a description of your “Plan-Do-Check-Act” corrective action plan which will be undertaken to achieve the acceptable level of performance:

As we have said in prior CAPs, we recognize that little progress will be made on the root causes of nonmonetary timeliness issues until we replace our current COBOL-based benefits system. The performance levels reflected during 2015 and 2016 reflect the substantial investment of time and talent that we have made in getting the new system correctly programmed to meet our needs. As that system comes online, we expect much of the pressure to be relieved and to begin work on what issues remain.

As we prepare for the system’s deployment, remaining adjudication staff are concentrating on clearing the backlog of decisions to ensure that the data converted to the new system is as fresh as possible. Additionally, all benefits staff will invest several days in training and process reengineering during the quarter prior to deployment. As such, we do not anticipate our numbers will immediately improve in the first two quarters of this CAP.

C. Previous years’ plan:

The prior plan recognized that little progress would be made on the root causes of nonmonetary timeliness issues until we replaced our current COBOL-based benefits system. The performance levels reflected during 2015 and 2016 reflect the substantial investment of time and talent that we have made in getting the new system correctly programmed to meet our needs. As that system comes online, we expect much of the pressure to be relieved and to begin work on what issues remain.

D. Plans for monitoring and assessing accomplishment of planned actions and for controlling quality after achieving performance goals:

UI benefits managers continue to monitor claim center metrics on a weekly basis, and adjust resources as available.

Milestones:

1. Meet timeliness standards for nonmonetary decisions by minimizing backlog of non-monetary issues to less than 5% of total open issues. (9/30/2018)

2. Complete all staff technical training in new UI Benefits system before Go-Live date in November 2016 - 100% staff in intake and adjudication units. (12/31/2016)

3. Complete intake and adjudication process (classroom and OJT) training for newly-hired staff cohorts (timeline TBD). *(Cohort 1 Feb 2017 - 5 staff; Cohort 2 Oct 2017 - 9 staff)* (12/31/2017)

4. Implement ("Go-Live") new UI Benefits system in November 2016. Resolve any remaining technical issues with project vendor and IT staff. Reintegrate 20 business analyst staff assigned to UI Benefits system (UTAB) project into claims center staffing, returning to fully-staffed levels of operation. (3/31/2018)

5. Reintegrate 20 business analyst staff assigned to UI Benefits system (UTAB) project into claims center staffing, returning to fully-staffed levels of operation. (6/30/2017)

6. After system implementation, complete business process analysis to assess performance of new system and develop plan to address any performance issues that emerge. Plan will include timelines for improvements and corrections. (3/31/2018)

Lower Authority Appeals Promptness

A. Reason for the deficiency:

With the launch of our new UI Benefits system in January 2017, claimants were given substantially greater access to file appeals independent of agents via our e-services interface. This led to a significant increase in the number of appeals filed, and placed great demand on existing staff at the claims centers and the Office of Administrative Hearings. Additionally, the new system required different processes and workflows to assemble appeals packages for submittal to OAH.

B. Provide a description of your “Plan-Do-Check-Act” corrective action plan which will be undertaken to achieve the acceptable level of performance:

We are beginning by reviewing the data to see specifically where the increase in appeals is impacting operations - whether it be an increase in specific types of appeals, system and workflow issues regarding appeal filing, the sheer volume of appeals filed, or the lack of agent involvement in the filing that may have resolved issues without the formal filing of an appeal. Our first step will be to take a quick and sober look at the number of changes and their impact on the appeals number, to determine where our best opportunities for improvement lie. After that, we will complete a full business process analysis with internal and external partners to find and fix issues that we identify. Throughout the process, we will be continually monitoring performance data to ensure our efforts are positively impacting those numbers.

C. Previous years’ plan:

Not applicable

D. Plans for monitoring and assessing accomplishment of planned actions and for controlling quality after achieving performance goals:

Lower Authority Appeals Time Lapse has not historically been a problem for Washington. We expect much of the shortfall to be due to technology and workflow changes associated with the new UI Benefits system. The analysis of processes will provide insight into the proper measures to monitor to ensure we achieve our goals. As stated above, we will be continually monitoring performance data to ensure our efforts are positively impacting those numbers throughout the process.

Milestones:

1. Review appeal filing data since January 2017 to understand root causes of increased appeals. Complete quick determination of potential factors involved in increase of appeals. This will include review of technology implementation(s), business processes, and staffing changes. (12/31/2017)

2. Develop action plan to address findings regarding root causes of increased appeals and develop additional milestones from that action plan. (12/30/2017)

3. Monitor workload and performance statistics to ensure progress toward acceptable levels of performance. (9/30/2018)

4. Complete business process analysis of appeals process with UI Benefits, Employment System Policy, and Office of Administrative Hearings. Determine potential opportunities for improvement, and enact plan to implement appropriate improvements. (This milestone may create more milestones moving forward) (3/31/2017)

Tax Quality

A. Reason for the deficiency:

The Next Generation Tax System (NGTS) defects continue to be greatly affecting the generating of correct billing statements, processing employer tax reports and payments, and correctly applying payments received. These errors continue to contribute to samples failing in Report Processing, Contributory and Reimbursing Debits/Billings, Credits/Refunds, Employer Tax Rates and Collections during the 2015 TPS reviews. New and Inactive Status Determinations deficiencies were result of NGTS defects and staff errors. Eight of thirteen different functions had more than the allowable number of failed samples. The main reason the Collection sample failing was because employers were not being contacted timely or at all on the majority of samples reviewed resulting in no collection actions being conducted.

B. Provide a description of your “Plan-Do-Check-Act” corrective action plan which will be undertaken to achieve the acceptable level of performance:

NGTS System defects have been continually monitored by the project’s business teams and steering committees, with bugs being logged, assigned, prioritized and corrected as quickly and effectively as possible.

In April 2016, the Collections function was merged with the Benefit Payment Control Unit to create a single Employment Security Collections unit. Additionally, staff developed tools to make visible all accounts on which collection actions are to be taken, and performance standards are in place requiring three collection actions per account per calendar quarter. As a result, employers are now being contacted for collection attempts while tax staff continue to respond to the large number of employer inquiries.

C. Previous years’ plan:

This has been previously identified as a multi-year CAP. We have made some progress, as demonstrated by passing more samples this year than the year before.

D. Plans for monitoring and assessing accomplishment of planned actions and for controlling quality after achieving performance goals:

UI Tax managers continue to monitor performance statistics regularly and adjust resources as needed. Leadership monitors all activity through regular updates on the tax floor.

Milestones:

1. Log, track, and resolve system defects until NGTS has reached stabilization as defined by the steering committee. Develop reporting and tracking tools to specifically respond to inquiries from RO for more frequent updates on ticket status in relation to Tax Quality, Data Validation, and reporting. (9/30/2018)

2. Work with Tax staff to identify root causes (both technical and process-based) for system inaccuracies, and determine and implement solutions to ensure correct account balances and samples. (9/30/2018)

3. Increase staff capacity to complete required activities by utilizing Lean techniques to improve efficiency and effectiveness. This will include increasing the number of Tax units having daily huddles to six, and completing and documenting 70 process improvements. (9/30/2018)

4. Implement business process analysis with new system tools to ensure our ability to adjust resources and work methods to best achieve and exceed standards for all tax functions. This includes monthly monitoring progress toward success and training staff on required TPS rules. (9/30/2018)

Improper Payments Measure

A. Reason for the deficiency:

Washington has historically had a good balance between prompt payment of UI benefits and strong efforts to identify and recoup benefits that may have paid erroneously. Washington has been a leader in work-search requirements and other strong measures that have been adopted nationally to improve the administration of UI benefits.

The time period measured for the Improper Payments Measure (June 28, 2015 to June 25, 2016) was uniquely turbulent in the administration of UI in Washington. Our UI tax system had been launched and was stabilizing; and our UI benefits system was in development with a significant number of business area staff lending their expertise to the project. The vacancies left in the operational areas by the business staff deployed to the project meant existing staff were stretching to cover the work, and new staff were learning the program. At the same time, our BAM program was struggling to fix long-standing staffing shortages and sampling deficiencies.

B. Provide a description of your “Plan-Do-Check-Act” corrective action plan which will be undertaken to achieve the acceptable level of performance:

It is our first priority to develop ways to track in real-time our improper payments, such that we’re not dependent on lagging measurements. This includes robust data available in our new system, as well as significantly improved efforts to communicate errors found in BAM reviews back to operations staff. At the same time, we will review our efforts to reduce improper payments; work with the new UI systems to ensure faster detection and stopping of invalid claims; and assisting our customers to understand their rights and responsibilities as beneficiaries of UI payments.

C. Previous years’ plan:

Not Applicable

D. Plans for monitoring and assessing accomplishment of planned actions and for controlling quality after achieving performance goals:

We are measuring the improper payment rate both quarterly (through roll-ups and reports of BAM case reviews) as well as anecdotally between the quality assurance team and UI Benefits. We will continue to explore both macro-level and case-level data to find potential improvement opportunities. This will also be communicated regularly between BAM staff and UIB management.

Milestones:

1. Collaborate with staff from the UTAB project, UI Benefits, and Quality Assurance teams to develop data tools from real-time data in UTAB to better track improper payments. These tools may include ad hoc reports developed in UTAB, SUN, and/or our data warehouse. Ensure reports and data tools give actionable data, and adjust as appropriate. (6/30/2018)

2. Implement, improve and operationalize communication tools between UI operations staff and UI Performs auditors (BAM, TPS, Benefit Self-Assessment teams) to more quickly collaborate and find root causes of errors found on claims. (9/30/2018)

3. Target improper-payment reduction efforts to errors as uncovered by data analysis, focusing on early detection and prevention of improper payments. (This milestone may create more milestones moving forward) (9/30/2018)

Benefits Data Validation

A. Reason for the deficiency:

As noted in prior years, Washington has limped along with an obsolete, COBOL-based UI benefits system which is highly troublesome to reprogram due to its structure. Multiple efforts to program federal and state law changes, especially during recessionary periods, exposed the limits of this system and caused cascading errors in some populations. With our current efforts to bring up a new UI benefits system as its replacement, IT staff have not been able to prioritize fixes to the old system that would address data validation errors.

Our issues with case sampling in the BAM unit may also have impacted the accuracy of certain reports, driving a high percentage of detected overpayments as described in our Narrative. We are addressing this potential issue with a deep dive into our reporting structure and data validation efforts, and will monitor the percentage as BAM’s case sampling returns to full standard.

B. Provide a description of your “Plan-Do-Check-Act” corrective action plan which will be undertaken to achieve the acceptable level of performance:

Our experience with implementation of our new UI Tax system (see DV Tax tab) brings into sharp relief the need for correct programming backed by thorough testing as we stand up our new UI Benefits system. During 2015 Washington contracted with a vendor for a commercial off-the-shelf benefits system to replace the current system (GUIDE). All efforts are now directed to standing up the new UI benefits system, which is due to come online in Fall 2016. DV staff are working with agency IT staff and the vendor to ensure that the underlying programming for data validation is correct in the new system, but we do not expect corrective programming to occur in the existing system.

Further, a significant aspect of our difficulties with data validation comes with the specialized knowledge required to thoroughly identify and evaluate the errors we see. We continue to review our resources that we have available for data validation, and pursue knowledge transfer and training (informal and possibly formal) to bring more resources to bear on the issues we find. This will become especially important as we complete the transition to modernized UI systems.

Our issues with case sampling in the BAM unit may also have impacted the accuracy of certain reports, driving a high percentage of detected overpayments as described in our Narrative. We are addressing this potential issue with a deep dive into our reporting structure and data validation efforts, and will monitor the percentage as BAM’s case sampling returns to full standard.

C. Previous years’ plan:

As noted above, previous corrective action plans have identified that the Benefits population issues will not likely be resolved until we can successfully replace the GUIDE system. The new UI Benefits system is expected to go live in Fall 2016.

D. Plans for monitoring and assessing accomplishment of planned actions and for controlling quality after achieving performance goals:

We continue to monitor our progress via the UTAB project team, who are programming and implementing identified fixes in the system.

Milestones:

1. Implement ("Go-Live") new UI Benefits system in November 2016. Verify programming is correct to pass data validation for all benefits populations. Resolve any remaining technical issues with project vendor and IT staff. (6/30/2018)

2. Determine appropriate resources and increase staff capacity to troubleshoot data validation issues by training and knowledge transfer. Create structure for training plan and succession planning to ensure smooth transfer of duties when vacancies arise. (6/30/2018)

3. Complete business process analysis (beginning with Lean kaizen event, date TBD) to fully catalog all ETA reports to be produced by the department. This will include multiple divisions and seek to identify and clarify responsibility to the unit and desk level for data production, data verification, system of record by field, and other goals established by the BPA team. (9/30/2018)

Tax Data Validation

A. Reason for the deficiency:

Washington’s new UI Tax system, NGTS, went live in March 2014. During system stabilization, several errors in programming and data conversion were discovered that greatly affected the system’s ability to generate correct billing statements, process employer tax reports and payments, and correctly apply payments received. These errors cascaded into several sample failures during data validation for the year.

Additionally, the overwhelming response from employers to UI Tax staff to request information, ask for corrections and recalculations, and argue penalty assessments overwhelmed staff’s ability to conduct normal business and drove the prioritization for IT staff to fix NGTS errors. As such, tickets relating to reports and data validation are prioritized behind tickets relating to critical system failures and direct service to employers.

Specific errors found in 2016 data validation include:

- Population 3 included Liability Dates that were further into the future than the Activation Processing Date.

B. Provide a description of your “Plan-Do-Check-Act” corrective action plan which will be undertaken to achieve the acceptable level of performance:

NGTS System defects have been continually monitored by the project’s business teams and steering committees, with bugs being logged, assigned, prioritized and corrected as quickly and effectively as possible. The vendor responsible for programming the system has been retained through the end of CY 2015 to continue providing corrective programming fixes, as well as completing work that had originally been included but later dropped due to time constraints. At the same time, agency IT staff are continuing to learn from the vendor so that they can provide programming support after the vendor’s contract is exhausted. Some fixes have been set aside until after the start of the new year to allow the programming team to concentrate on finding and fixing the root causes of incorrect processes. The emergent nature of the system errors and the lack of current knowledge regarding root causes for these errors means we cannot predict when we will completely resolve these issues. As such, our “milestones” have ongoing timelines for now, with the expectation that over the next several months timelines and prioritizations can be established as the full universe of system defects is identified. By identifying and resolving these basic defects, we expect the entire system to stabilize and all measures related to tax data (including TPS samples and data validation) to quickly improve.

Specific tickets to address 2016 errors include:

- A service request was submitted to resolve the Liability Date requirements in Population 3.

- A service request was submitted on 12/18/15 to resolve timely payments from being included in Population 4.

- A service request was submitted on 04/11/16 to correct the large employer criteria in Population 4.

- Module 4 Status New, Successor and Terminate was determined as "Not Submitted" but was reconsidered to be "Submitted" but failed.

- Service requests have been submitted to resolve the Liability Date for New and Successor Status Determinations and to resolve the difference in the TPS Universe count against the ETA 581 report.

- A service request was submitted to have exact filing methods saved to perform Module 5 wage item DV.

Lastly, a significant aspect of our difficulties with data validation comes with the specialized knowledge required to thoroughly identify and evaluate the errors we see. We intend to review our resources that we have available for data validation, and pursue knowledge transfer and training (informal and possibly formal) to bring more resources to bear on the issues we find. This will become especially important as we complete the transition to modernized UI systems.

C. Previous years’ plan:

We continue to work to fix the errors in our NGTS system, prioritizing errors that impact our customers ahead of internal issues.

D. Plans for monitoring and assessing accomplishment of planned actions and for controlling quality after achieving performance goals:

Senior managers of the UI, ESPIO and ITBI divisions meet regularly to discuss status of major UI infrastructure projects. Reporting and data validation is a standard agenda items for these meetings. Additionally, senior agency leadership meet quarterly to review and prioritize all IT projects to balance the needs of the agency. These meetings discuss both large IT replacement projects as well as smaller, emergent IT needs to balance projects and priorities.

Milestones:

1. Work with Tax and IT staff to identify action plan listing specific Tax populations and modules being targeted for correction and identify expected completion date for these corrections. Report plan to RO staff by December 31, 2016. (6/30/2018)

2. Log, track, and resolve system defects until NGTS has reached stabilization as defined by the steering committee. Develop reporting and tracking tools to specifically respond to inquiries from RO for more frequent updates on ticket status in relation to Tax Quality, Data Validation, and reporting. (9/30/2018)

3. Identify root causes for system inaccuracies, and determine and implement solutions to ensure correct account balances and samples. (9/30/2018)

4. Determine appropriate resources and increase staff capacity to troubleshoot data validation issues by training and knowledge transfer. Create structure for training plan and succession planning to ensure smooth transfer of duties when vacancies arise. (12/31/2017)

5. Complete business process analysis (beginning with Lean kaizen event, date TBD) to fully catalog all ETA reports to be produced by the department. This will include multiple divisions and seek to identify and clarify responsibility to the unit and desk level for data production, data verification, system of record by field, and other goals established by the BPA team. (12/31/2017)

Benefit Accuracy Measurement (BAM)

A. Reason for the deficiency:

The Benefit Accuracy Measurement (BAM) unit has endured several staff upheavals during the past four program years. Due to reductions in force, unexpected medical leave, reasonable accommodations, and the length of time necessary to train an investigator to do the audit, the team has struggled to maintain timeliness standards while pulling the mandated number of cases to review. Training multiple new staff over the years and transitioning cases in process for various reasons has heavily impacted the unit’s ability to maintain production standards. Prior State Quality Service Plans noted that staffing fluctuations in this unit would eventually impact its ability to maintain timeliness standards, though there was insufficient data to quantify the expected effect.

However, it should be noted that substantial progress was made in the past year. Case sampling improved from 79% to 85% of paid cases, and from 76% to 91% of denied cases, and the unit met seven of the eight timeliness standards, missing only on 90-day paid cases by less than two percent. With initial training of our new investigators complete and other staffing issues stabilized, the unit is projected to meet quarterly and annual case sampling requirements by Q1 2017.

Our issues with case sampling may also have impacted the accuracy of certain reports, driving a high percentage of detected overpayments as described in our Narrative. We are addressing this potential issue with a deep dive into our reporting structure and data validation efforts, and will monitor the percentage as BAM’s case sampling returns to full standard.

B. Provide a description of your “Plan-Do-Check-Act” corrective action plan which will be undertaken to achieve the acceptable level of performance:

The BAM unit will continue to build upon the substantial progress made during the last year. We rebuilt the supervisor role to create a technical lead, which has helped immensely with training new staff and consistency in the quality of investigations. We have stabilized our experienced staff, and brought on experienced adjudicators to learn BAM audit methodology. We also cross-trained several staff within the Employment System Policy division to both provide learning opportunities to those staff, and create a cadre of investigators who could assist if further staff disruptions arise. The team has also developed several Lean methods to track open cases, assist colleagues with investigative tasks, and make visible our progress toward our goals. This team ethic sets us up well to reengineer our processes as we move into the new UI benefits computer system.

During Q4 2016, we will continue to move toward full case sampling each week, though we anticipate our progress may be slowed when the new UI benefits system goes live during this quarter. We are projected to have all weeks at full sampling or better by the end of Q4 2016, and are projected to pull sufficient additional cases to exceed the federal standards of 480 paid and 450 denied cases for the 2016-17 program year.

Sampling Variance: Washington will implement a new UI Benefit computer system in Fall 2016. We expect the programming issues that exist in GUIDE will be corrected in the new system, either at go-live or immediately following. This will be monitored at case sampling on a weekly basis. We will also monitor any impact on ETA reports as BAM’s case sampling returns to full standard.

C. Previous years’ plan:

The manager’s first priority during this year has been to assess needs and develop training, sampling, and case assignment plans that honor the unit’s need to close existing cases and clear the backlog in order to retain timeliness goals. We identified and addressed several training issues, as well as deficiencies in the position’s job description that have been corrected with our human resources division. We also added staff resources to the unit. As timeliness continues to stabilize, case sampling is increasing to the standard level until we have reached our performance goals in that area as well. As the unit returns to full and fully-trained staffing levels, we will monitor timeliness and sampling against standard to evaluate further steps that may be needed. We also thoroughly reviewed and restructured the unit to maximize efficiency and create new opportunities for staff to learn and grow. These steps provide a solid foundation on which to continue to build our success and move to stable operational compliance.

D. Plans for monitoring and assessing accomplishment of planned actions and for controlling quality after achieving performance goals:

The unit manager is monitoring all metrics (timeliness, quality, sampling numbers and population variance) on a daily basis, and intervening to redirect resources as appropriate. While we will likely have a dip in performance immediately following the implementation of our new UI benefits computer system, we expect to have better visibility into the root causes of these issues and act accordingly.

Milestones:

1. Monitor and improve case timeliness by using daily management methods with BAM team to adjust resources with goal to close cases within 60 days. The team will work to achieve goals of (a) average of 135 open cases at any given time and (b) no more than ten cases open past 60 days at any given time. (9/30/2017)

2. Meet quarterly and annual case sampling requirements by using weekly monitoring and case assignment methods that more flexibly adjust team resources to meet workload demands. Increase case assignment until on track to maintain full case sampling requirements, then maintain that level by managing workloads. (6/30/2017)

3. Implement ("Go-Live") new UI Benefits system in November 2016. Ensure new system meets technical requirements (sampling variance, NDNH procedures). Resolve any remaining technical issues with project vendor and IT staff. (6/30/2018)

4. Complete and implement business process analysis with new system tools to ensure our ability to adjust resources and work methods to best utilize new tools to exceed standards. (6/30/2018)

5. Continue to stabilize team staffing by proactively cross-training division staff in BAM methods, improving staffing to exceed minimums as expected in ETA 395 6th ed., and improving our outreach to operations staff to increase awareness and enthusiasm for any potentially necessary recruitments. (multi-year)

a. Given that Washington has struggled with training and retaining qualified BAM staff for the past several years, we recognize that building awareness of our team’s work is an ongoing effort. As such, we look not only to immediate needs for staffing improvements, but also to building a strong path to the BAM team from our operational units. This will include measures such as developing "BAM 101" training for staff in the department, making our reports more visible and actionable, and other awareness activities. Additionally, we are working with HR and operational units to develop innovative ways to train staff in BAM methodology, including developmental assignments, shadowing, and other potential avenues to build skills. With these efforts, we hope to have a strong pool from which to draw enthused, engaged, and competitive recruits for openings that will arise in the future.

Nonmonetary Determination Issue Detection and Determination Date Accuracy

A. Reason for the deficiency:

Washington’s current benefit payment system (GUIDE) required three areas of reprogramming to properly identify the correct Issue Detection Date (IDD):

1) Properly set the IDD when an initial or continued claim is submitted outside of regular business hours,

2) Give staff the ability to update the IDD when information identifying a separation issue is received from an employer,

3) Correct a system incident to properly re-set the IDD when a claim becomes monetarily valid.

These technology issues were the major factor in our IDD error rate for BTQ results. Due to competing technology priorities including federal and state legislative mandates, additional required system fixes remain incomplete. We have said in past years that we would be unable to completely resolve this issue until we replace our GUIDE system.

We are nearing the replacement of GUIDE with an updated UI Benefits payment system (UTAB), which is scheduled to go live in Q4 2016. As such, our efforts changed over the past year from prioritizing the fix in GUIDE to ensuring that IDD is correctly identified in the new system. In addition to the technology improvements, we are using Lean practices to complete a thorough review of processes and procedures in all areas of benefit payment. With this dual effort, we expect to see significant improvement in several deficient areas, to include IDD.

B. Provide a description of your “Plan-Do-Check-Act” corrective action plan which will be undertaken to achieve the acceptable level of performance:

This issue will not be remedied until we complete the replacement of our UI benefits system. We are nearing completion of the project to replace our UI Benefits system with a Commercial-Off-the-Shelf (COTS) product. The projected implementation date for the project is Q4 2016. This system is currently being tested to ensure that it correctly identifies the issue detection date, and to re-program any pieces that require it.

C. Previous years’ plan:

As stated in past SQSP and CAPs, this issue was set aside until replacement of our UI benefits system. That new system is scheduled to go live in Q4 2016.

D. Plans for monitoring and assessing accomplishment of planned actions and for controlling quality after achieving performance goals:

We will continue to monitor IDD identification via BTQ to ensure it is properly programmed in the new system.

Milestones:

1. Implement ("Go-Live") new UI Benefits system in November 2016. Verify programming correctly identifies Issue Detection Date for separations and nonseparations. (12/31/2017)

2. Monitor IDD identification via BTQ to ensure it is properly programmed in the new system. (12/31/2017)

3. After system implementation, complete business process review of procedures to determine and correct any non-technical causes for IDD errors, and develop plan to address any performance issues that emerge. Plan will include timelines for improvements and corrections. (12/31/2017)