Reporting

Pre-Implementation Planning Checklist Report for State Unemployment Insurance Information Technology Modernization Projects

Pre-Implementation Planning Checklist Report

Reporting

OMB: 1205-0527

Document [doc]
Download: doc | pdf

U.S. Department of Labor OMB Control No. 1205-XXXX

Employment and Training Administration Expiration Date: XX/XX/XXXX

Form ETA 9177













Unemployment Insurance (UI) Information Technology (IT)

Modernization Pre-Implementation Planning Checklist

Report





U.S. Department of Labor

Employment and Training Administration

Form ETA 9177



UI IT Modernization Pre-Implementation Planning Checklist Report

State Name:

Date of Submission:

Project Name:


Contact Information:

(Name, Title, Address, Phone Number. Email Address)


Summary of Project:



  1. Functionality is Fully Available or Workaround in Place


    1. All benefit and tax functions have been fully tested and are fully operational (unless work around(s) planned for and tested) including, but not limited to:


      1. Claims Filing;

For all supported programs: Regular UI, Unemployment Compensation for Federal Employees, Unemployment Compensation for Ex-Servicemembers, Combined Wage Claim, Disaster Unemployment Assistance, Trade Readjustment Allowances, any extensions, etc.


      1. Monetary determinations;


      1. Non-monetary determinations

Including separation and non-separation issues including automated holds that flags issues requiring adjudication


      1. Continued Claims processing;


      1. Benefit payment mechanisms;

Including (as applicable): direct deposit, debit card, and checks


      1. Employer liability determinations;


      1. Tax rate computation;


      1. Employer Delinquency Enforcement;


      1. Employer Tax and Wage report processing;


      1. Benefit Charging;


      1. Appeals.


    1. Federal reporting functions, including Benefits Accuracy Measurement (BAM) and UI Data Validation, have been fully tested and are fully operational


    1. State UI program management reporting functions, such as tracking of initial and continued claims by age, management dashboard, and ad hoc and system logging reports, have been fully tested and are fully operational


    1. Interfaces with call center operations have been fully tested and are fully operational


    1. Interstate Connection (ICON) network interfaces have been fully tested and are fully operational


    1. Other external interfaces, such as those required to retrieve wage record data, automatic cross matches for identity or other integrity purposes, have been fully tested and are fully operational


    1. System generated forms and correspondence have been fully tested and are fully operational


    1. Printing processes have been fully tested and are fully operational


    1. Imaging and scanning, as needed, have been fully tested and are fully operational


    1. Batch Processes, including execution timelines, have been fully tested and are fully operational


    1. Workflows have been verified and adjusted by conducting thorough review of system generated issue flags/triggers to ensure they are necessary


    1. System error handling is in operation and will:



      1. Ensure process is in place to identify, track, and address system errors;


      1. Procedures developed to document and communicate any system work-around or resolution;


      1. Ensure Help Desk available to support staff


      1. System error messages are understandable


    1. Ensure workarounds are established and fully tested and exercised with staff for system functionality that is deferred or necessary to address known system issue


    1. Business knowledge has been transferred to appropriate agency/staff on how to operate system, including role management, configuration settings and management, dashboards and reporting


    1. End user support, problem reporting and resolution protocols are in place


    1. All user roles have been configured/set-up and tested


      1. Users with appropriate permissions can easily change staff role assignments directly in the application


  1. External Alternate Access Options and Usability Issues Addressed


    1. Alternative Access Options

In compliance with ETA guidance, the new system supports alternative access options for individuals with barriers to filing by phone or on-line, such as those with Limited English Proficiency (LEP), disabilities, literacy issues including computer literacy, and computer access issues, etc.


    1. Websites and other forms of communications, such as brochures and posters, are in place to clearly identify alternative access points that effectively communicate to the population with such barriers as described in section 2.1


    1. All staff are fully trained on how to assist individuals with access barriers to alternative filing options


    1. Staff and customer system access to new system are defined, including processes to migrate existing credentials and/or establish new credentials


    1. Usability


      1. Websites meet 508 compliance standards and are translated for identified significant population language groups within the state, including correspondence as applicable.


      1. On-line Web content is clear, understandable(preferably tested by appropriate customer population)


      1. Ensure Interactive Voice Response (IVR) phraseology is clear and understandable

  1. Policies/Procedures Development and Dissemination


    1. Policy and procedural changes coinciding with UI system modernization are developed and disseminated


    1. Policies for data security, including those for handling privacy and confidential data are developed and disseminated


    1. Policies for data retention and data disposal are developed and disseminated


    1. Staff is fully trained on new policies and procedures


    1. Any updates to organizational structure are coordinated with human resources department and disseminated agency-wide


    1. Any new or modified roles are clearly defined, and staff are appropriately trained

  1. Technical Preparation


    1. Data conversion is complete and successful, including:


      1. New system results checked and reconciled against legacy system results:


      1. Spot checks conducted for particular areas of interest:


      1. System blackout period is benchmarked, if appropriate


    1. Independent Verification &Validation conducted, as needed


    1. Bridging processes between applications/systems in place as needed (for example, new benefits system to legacy tax system or the inverse)


    1. Comprehensive User Acceptance Testing (UAT)


      1. UAT conducted with positive results and conducted again following any additional system changes


      1. System defects are systematically tracked and remedied


      1. Defect tracking processes are in place post “go-live” (in conjunction with development vendor)


      1. System help verified


      1. Logging and exception handling verified


    1. Capacity developed to rapidly identify system flaws and make immediate fixes



    1. Contingency / Back-up plan is in place if new system fails – particularly if no overlap of legacy and new system at “go live” point


    1. Incoming phone capacity (lines and staff) are adjusted for anticipated increases in call volume, including:


      1. Call Centers, as applicable;


      1. Any other Agency unit that will conduct triage of system issues with customers


    1. “Go-Live” decision points (show stoppers) outlined and followed


    1. System performance is checked under peak user loads, including complex transactions, prior to “go-live”


    1. System availability


      1. Demonstrated system availability under heavy loads for sustained period of times


      1. Monitor computing resource consumption (processors, memory, Input/Output, etc.)


    1. IT system operations reporting is available, including management dashboard, ad hoc reports, and system logging and audit trails, as needed


    1. Production configuration defined and in place


    1. Automated production build /testing/environment promotion process is in place for post-deploy defect fixes and enhancements


    1. All agency users and their roles established and verified in the system


    1. Data and System security verified and validated, including systems required for data exchanges for Social Security Administration and Treasury Offset Program interfaces


    1. Other internal system controls are verified and validated to ensure security and confidentiality of data


    1. IT knowledge transfer to ensure agency can maintain and support the system


    1. Transition planning and execution post-warranty or maintenance phase is validated with vendor


    1. Service delivery strategies at “go-live”


      1. Ensure service delivery strategies are clearly identified, made known to staff, and fully communicated to customers


      1. Ensure adequate communications regarding expectations to customers if black-out periods are utilized


  1. Call Center /Customer Service Operations


    1. Call center standard operational procedures adapted, as appropriate


    1. Call Center Staff and/or customer service representatives (CSRs) fully trained, including:


      1. CSRs/agents participated in system UAT


      1. CSRs/agents, supervisors, managers trained in the use of the new system


      1. Cross train staff and/or staff augmentation, particularly to manage inquiries


    1. Modernization system and operations help desk information provided to all front-line CSR staff


    1. Front-line and management staff know triage process when a system issue arises, and issue escalation processes are clearly defined and understood by staff


    1. Scheduled team meetings daily and, as needed, to address:


      1. New System Issues


      1. Customer Complaints


      1. New operational or procedural issues


  1. Staffing/Staff Training on New System Operations


    1. Training materials and tools to support new processes (desk guides, handbooks, etc.) are fully developed and provided to management and staff


    1. Management and staff fully trained on new system features and operations broadly and in relation to their specific job responsibilities.


    1. Additional Staffing Needs Identified and Secured to address:


      1. Call Center(s) (calls can dramatically increase during a conversion)


      1. Adjudication Staff (modernized systems tend to contain more automated flags that raise issues requiring adjudication)


      1. Appeals Staff (the number of appeals may increase following a conversion as a result of new automated processes that may impact claimants’ benefits or employers’ liability)


      1. Other support functions such as integrity-related activities



  1. Staff and Customer Help Desk Support


    1. Procedures established for escalation processes, triage processes of system technical/functional issues, communication channels, and coordination with Call Centers, as applicable


    1. Dry-runs of procedures with Help Desk staff are conducted


    1. Adequately staffed with modernization testers / Subject Matter Experts/Business Analysts, and Project Team members



    1. Contact information is published and disseminated to appropriate personnel


    1. Procedures to categorize and track system issues based on help request are in place

(e.g., credential/access issue, performance, questions needing clarification, etc.)


  1. Management Oversight


    1. Managers are fully trained on management features and reporting processes in the system


    1. Managers are prepared to support staff if system issues arise


    1. Additional management meetings are scheduled during transition to identify and resolve issues



  1. Vendor Support/Communications


    1. Process for addressing post implementation system fixes with vendor is in place prior to implementation


    1. Process for tracking system and scheduling post-implementation system issues are in place


    1. Routine, daily meetings with the vendor during transition scheduled to identify and prioritize system issues for as long as needed


    1. Ensure a process to track the implementation of deferred functionalities


  1. Communications


    1. Staff Communications


      1. Staff are fully briefed on implementation plan (in addition to being fully trained)


      1. Staff are provided with clear instructions on how to handle system issues if they arise


    1. Claimant and Employer Communications


      1. Employer and Claimant outreach regarding roll-out of new system


      1. System “go-live” date disseminated



      1. System black-out period, if needed, and methods to conduct business during this phase will be clearly communicated


      1. Agency contact information is disseminated


      1. System “how-to information” provided


    1. Public Communications


      1. State stakeholders notified in advanced


      1. System “go-live” date disseminated


      1. System black-out period, if needed, is communicated



Certification

Certifying Official:

(Name, Title)


Signature:


Telephone Number:


Date:

Email Address:



2


File Typeapplication/msword
AuthorJagruti Patel
Last Modified ByWindows User
File Modified2017-02-02
File Created2017-02-02

© 2024 OMB.report | Privacy Policy