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:
Functionality is Fully Available or Workaround in Place
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:
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.
Monetary determinations;
Non-monetary determinations
Including separation and non-separation issues including automated holds that flags issues requiring adjudication
Continued Claims processing;
Benefit payment mechanisms;
Including (as applicable): direct deposit, debit card, and checks
Employer liability determinations;
Tax rate computation;
Employer Delinquency Enforcement;
Employer Tax and Wage report processing;
Benefit Charging;
Appeals.
Federal reporting functions, including Benefits Accuracy Measurement (BAM) and UI Data Validation, have been fully tested and are fully operational
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
Interfaces with call center operations have been fully tested and are fully operational
Interstate Connection (ICON) network interfaces have been fully tested and are fully operational
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
System generated forms and correspondence have been fully tested and are fully operational
Printing processes have been fully tested and are fully operational
Imaging and scanning, as needed, have been fully tested and are fully operational
Batch Processes, including execution timelines, have been fully tested and are fully operational
Workflows have been verified and adjusted by conducting thorough review of system generated issue flags/triggers to ensure they are necessary
System error handling is in operation and will:
Ensure process is in place to identify, track, and address system errors;
Procedures developed to document and communicate any system work-around or resolution;
Ensure Help Desk available to support staff
System error messages are understandable
Ensure workarounds are established and fully tested and exercised with staff for system functionality that is deferred or necessary to address known system issue
Business knowledge has been transferred to appropriate agency/staff on how to operate system, including role management, configuration settings and management, dashboards and reporting
End user support, problem reporting and resolution protocols are in place
All user roles have been configured/set-up and tested
Users with appropriate permissions can easily change staff role assignments directly in the application
External Alternate Access Options and Usability Issues Addressed
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.
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
All staff are fully trained on how to assist individuals with access barriers to alternative filing options
Staff and customer system access to new system are defined, including processes to migrate existing credentials and/or establish new credentials
Usability
Websites meet 508 compliance standards and are translated for identified significant population language groups within the state, including correspondence as applicable.
On-line Web content is clear, understandable(preferably tested by appropriate customer population)
Ensure Interactive Voice Response (IVR) phraseology is clear and understandable
Policy and procedural changes coinciding with UI system modernization are developed and disseminated
Policies for data security, including those for handling privacy and confidential data are developed and disseminated
Policies for data retention and data disposal are developed and disseminated
Staff is fully trained on new policies and procedures
Any updates to organizational structure are coordinated with human resources department and disseminated agency-wide
Any new or modified roles are clearly defined, and staff are appropriately trained
Data conversion is complete and successful, including:
New system results checked and reconciled against legacy system results:
Spot checks conducted for particular areas of interest:
System blackout period is benchmarked, if appropriate
Independent Verification &Validation conducted, as needed
Bridging processes between applications/systems in place as needed (for example, new benefits system to legacy tax system or the inverse)
Comprehensive User Acceptance Testing (UAT)
UAT conducted with positive results and conducted again following any additional system changes
System defects are systematically tracked and remedied
Defect tracking processes are in place post “go-live” (in conjunction with development vendor)
System help verified
Logging and exception handling verified
Capacity developed to rapidly identify system flaws and make immediate fixes
Contingency / Back-up plan is in place if new system fails – particularly if no overlap of legacy and new system at “go live” point
Incoming phone capacity (lines and staff) are adjusted for anticipated increases in call volume, including:
Call Centers, as applicable;
Any other Agency unit that will conduct triage of system issues with customers
“Go-Live” decision points (show stoppers) outlined and followed
System performance is checked under peak user loads, including complex transactions, prior to “go-live”
System availability
Demonstrated system availability under heavy loads for sustained period of times
Monitor computing resource consumption (processors, memory, Input/Output, etc.)
IT system operations reporting is available, including management dashboard, ad hoc reports, and system logging and audit trails, as needed
Production configuration defined and in place
Automated production build /testing/environment promotion process is in place for post-deploy defect fixes and enhancements
All agency users and their roles established and verified in the system
Data and System security verified and validated, including systems required for data exchanges for Social Security Administration and Treasury Offset Program interfaces
Other internal system controls are verified and validated to ensure security and confidentiality of data
IT knowledge transfer to ensure agency can maintain and support the system
Transition planning and execution post-warranty or maintenance phase is validated with vendor
Service delivery strategies at “go-live”
Ensure service delivery strategies are clearly identified, made known to staff, and fully communicated to customers
Ensure adequate communications regarding expectations to customers if black-out periods are utilized
Call Center /Customer Service Operations
Call center standard operational procedures adapted, as appropriate
Call Center Staff and/or customer service representatives (CSRs) fully trained, including:
CSRs/agents participated in system UAT
CSRs/agents, supervisors, managers trained in the use of the new system
Cross train staff and/or staff augmentation, particularly to manage inquiries
Modernization system and operations help desk information provided to all front-line CSR staff
Front-line and management staff know triage process when a system issue arises, and issue escalation processes are clearly defined and understood by staff
Scheduled team meetings daily and, as needed, to address:
New System Issues
Customer Complaints
New operational or procedural issues
Staffing/Staff Training on New System Operations
Training materials and tools to support new processes (desk guides, handbooks, etc.) are fully developed and provided to management and staff
Management and staff fully trained on new system features and operations broadly and in relation to their specific job responsibilities.
Additional Staffing Needs Identified and Secured to address:
Call Center(s) (calls can dramatically increase during a conversion)
Adjudication Staff (modernized systems tend to contain more automated flags that raise issues requiring adjudication)
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)
Other support functions such as integrity-related activities
Staff and Customer Help Desk Support
Procedures established for escalation processes, triage processes of system technical/functional issues, communication channels, and coordination with Call Centers, as applicable
Dry-runs of procedures with Help Desk staff are conducted
Adequately staffed with modernization testers / Subject Matter Experts/Business Analysts, and Project Team members
Contact information is published and disseminated to appropriate personnel
Procedures to categorize and track system issues based on help request are in place
(e.g., credential/access issue, performance, questions needing clarification, etc.)
Management Oversight
Managers are fully trained on management features and reporting processes in the system
Managers are prepared to support staff if system issues arise
Additional management meetings are scheduled during transition to identify and resolve issues
Vendor Support/Communications
Process for addressing post implementation system fixes with vendor is in place prior to implementation
Process for tracking system and scheduling post-implementation system issues are in place
Routine, daily meetings with the vendor during transition scheduled to identify and prioritize system issues for as long as needed
Ensure a process to track the implementation of deferred functionalities
Communications
Staff Communications
Staff are fully briefed on implementation plan (in addition to being fully trained)
Staff are provided with clear instructions on how to handle system issues if they arise
Claimant and Employer Communications
Employer and Claimant outreach regarding roll-out of new system
System “go-live” date disseminated
System black-out period, if needed, and methods to conduct business during this phase will be clearly communicated
Agency contact information is disseminated
System “how-to information” provided
Public Communications
State stakeholders notified in advanced
System “go-live” date disseminated
System black-out period, if needed, is communicated
Certification |
||
Certifying Official: (Name, Title) |
|
|
Signature: |
|
|
Telephone Number: |
|
Date: |
Email Address: |
|
File Type | application/msword |
Author | Jagruti Patel |
Last Modified By | Windows User |
File Modified | 2017-02-02 |
File Created | 2017-02-02 |