UIA Integrated SystemProject
Appendix B
Functional Requirements
UIA Integrated System
Table of Contents
Instructions
Benefits Functions
A.Claims
B.Monetary Determinations
C.Benefit Charging
D.Certifications
E.Benefit Payments
F.Non-Monetary Determination
F.Overpayment
H.Claimant Maintenance - Staff Options
I.Claimant - Self-Service
J.Special Programs
Tax Functions
A.Employer Registration
B.Rate Determination
C.Quarterly Reporting
D.Employer Maintenance - Staff Options
E.Employer Maintenance - Reimbursing
F.Employer Self-Service
G.Work Opportunity Tax Credit (WOTC)
H.Proof of Claim - Bankruptcy
I.Employer Compliance - Field Audit
Common Functions
Appeals
Quality Assurance
A.QA - General
B.QA - Benefits Accuracy Measurement (BAM)
C.QA - Benefits Timeliness and Quality (BTQ) Measures
D.QA – CrossMatch
E.QA - Fraud Investigations
F.QA - Misclassification
G.QA - State Unemployment Tax Act (SUTA)
H.QA - Tax Performance System (TPS)
Reporting Functions
A.Reports - Internal
B.Federal Reporting
Payments and Collections
A.Payments and Collections
B.Payments
C.Post
D.Recoupment
E.Collection Case
F.Assessment
G.Payment Plan
H.Lien
I.Withhold
J.Judgment
K.Waiver
L. Intercept
M.Write-Off
Trust Fund
Correspondence
Workflow
General Functions
A.Account Management
B.Audits
C.Forms Maintenance
D.Edits / Validation / Business Rules
E.Events / Scheduling
F.Interfaces / Interoperability
G.Notes
H.Online Help
I.Search
J.Security
K.User Interface
Instructions
The Bidder must respond whether or not their proposed solution complies with each requirement as follows:
- Check the box that applies to each requirement in the columns labeled: Yes, Yes with Modifications, or No.
Note: In order for your bid response to qualify for the selection process, all mandatory requirements responses must be Yes or Yes with Modifications
- Yes – is defined as the Bidder’s solution complies with all aspects of the requirement and is currently a standard feature.
In the comment box the Bidder must describe how their proposed solution complies with the requirement. If applicable, screen shots may be provided to show this functionality and included as an Appendix to the Bidders proposal.
- Yes with Modification – is defined as the solution does not currently comply with the requirement but the Bidder can modify the solution through configuration, programming or source code changes which, in the Bidder’s opinion, would result in their solution reaching full compliance with a requirement.
In the comment box the Bidder must describe the modification that will be made and how it will comply with the requirement. All such modifications are considered to be part of the solution being proposed and included in the bid price. If the modification will not be complete by the “go live” date, the Bidder must specify an anticipated date when the modification would be added to the solution, at no additional cost to the State. The State reserves the right to reject the Bidder’s proposed date and consider the solution not in compliance.
- No – is defined as the Bidder’s proposed solution does not comply with all aspects of the requirement.
In the comment box the Bidder must describe the impact of not meeting the requirement.
- Fill in the column labeled Requirement Response (REQ Response), for each requirementwith an A, B, C, D, or E, as defined below.
In the comment box the Bidder must provide any additional information related to the solution.
A.Currently provided as a standard feature
B.Not currently provided but is a planned enhancement or will be added at no additional cost and will be supported in future releases
C.Not currently provided but will be added at the additional cost detailed in the cost proposal and will require additional cost to transfer to future releases
D.Not currently provided but will be added at the additional cost detailed in the cost proposal and will be supported in future releases at no additional cost
E.Not supportable
______
Appendix B - UIA IS - Functional Requirements (Final).doc Page 1
UIA Integrated SystemProject
Functional and General System requirements will identify what the solution or product must run on or integrate with, including any standards that must be met, security requirements, and interfaces.
Technical/General System requirements will also identify the general framework in which the system or product must work, such as: capacity requirements (number of users, concurrent users, number of transactions to be handled, peak usage), documentation, audit and backup and recovery. Additional information may also be found and detailed in the Technical Overview Appendices.
Functional Requirement / Yes / Yes, with Modification / No / Requirements Response(A, B, C, D, E) / Comments
Benefits Functions
A.Claims
1 / The system must provide the ability to file a claim for unemployment benefits through multiple channels (i.e. web, IVR, file submit)2 / The system must provide the ability for staff and claimants to file a claim for unemployment benefits through a common claims intake applications
3 / The system must be able to automatically post unemployment claim records contained in files submitted by an employer on behalf of their employees.
4 / The system must be able to automatically transfer a claimant filing a claim for benefits via the IVR to a staff person.
5 / The system must provide the ability for claimants filing a claim for benefits via the IVR to transfer to a staff person for assistance with the filing process.
6 / The system must be able to submit and process 'no touch' claims filed via a self-service claimant option (IVR, Claim Portal).
7 / The system must provide the ability for claimants and staff to request (and display) an on-line pre-monetary determination prior to the unemployment claims filing process to estimate potential benefit entitlement.
8 / The system must provide the ability for staff and claimants to file a claim for benefits for all entitlement programs (UI, Federal/State Extensions, TRA, DUA).
9 / The system must collect all information needed to establish claim type, program of filing, and potential eligibility for benefits (monetary and non-monetary).
10 / The system must be able to automatically provide specific information to the claimant regarding why an unemployment claim cannot be filed. (e.g. claimant already has an existing benefit year with zero balance and no extensions are available).
11 / The system must be able to save partially completed unemployment claims and allow the return for completion of such claim during the remaining calendar week.
12 / The system must allow staff to access partially completed (claims in progress).
13 / The system must be able to dynamically display information and perform data capture and edits/validations based on the type of user filing the claim.
14 / The system must be able to automatically identify and establish the type of claim that must be filed (i.e. New Claim, Additional Claim, Reopened Claim, Transitional Claim, Extended Benefits (state or federal), TRA, DUA).
15 / The system must automatically establish a transitional new for unemployment claim benefits when an existing unemployment claim is reopened (Additional or Reopened) and the effective date is the last week of the existing claim.
16 / The system must dynamically display data entry screens based on the claim type and program under which the unemployment claim is filed.
17 / The system must dynamically collect information to establish the claim based on responses to questions asked during the claims filing process.
18 / The system must provide an electronic interface with various State and Federal Agencies to validate information collected as part of the claims filing process. Information to be validated includes SSN, Driver License ID and legal alien status.
19 / The system must be able to electronically interface with external software (during the unemployment claims filing process) to obtain an occupational code to the claimant based on the type of work previously performed.
20 / The system must be able to electronically interface with external software (during the unemployment claims filing process) to validate address information.
21 / The system must be able to automatically process and electronically transmit interstate unemployment claims where Michigan acts as an agent on behalf of the paying state.
22 / The system must be able to automatically set the effective date of an unemployment claim.
23 / The system must be able to collect information to establish a claim for unemployment benefits using non-Michigan employment wages. (i.e. Military, Federal, Out-of-State)
24 / The system must be able to automatically assign a claim designation based on source of wages (federal employment, military service, out-of-state or in-state employment) attached to the unemployment claim. (i.e. UCX, UCFE-UI; UCFE-UCX)
25 / The system must initiate an electronic request to Interstate Connection system (ICON) to validate employment and receive information needed to establish a claim if there is military, federal or out-of-state employment on the unemployment claim.
26 / The system must provide the ability to electronic interface to the Interstate Benefits Inquiry (IBIQ) system to verify claimant wages earned in another state or the status of an unemployment claim filed in another state.
27 / The system must allow staff to perform a search to identify the state to which wages were reported for claimants working in maritime employment.
28 / The system must support the filing of a claim for unemployment benefits when the claimant is fully employed at the time of filing.
29 / The system must provide the ability for claimants and staff to combine wages earned by the claimant under multiple Social Security Numbers into a single unemployment claim.
30 / The system must provide the ability for claimants and staff to add employment/wage information to the claim when there is missing base period or separating employer employment and/or wage information.
31 / The system must be able to automatically attach an employer to a claim for benefits where there is no valid account (UIA) number for employers (employment added to an unemployment claims by claimants or staff.)
32 / The system must be able to automatically generate a notice to employers to obtain a valid FEIN or UIA employer account number when an employer is added to a claim without a FEIN or UIA employer account number.
33 / The system must track wage information as self-reported when employment/wages are added to the claim by the claimant or staff.
34 / The system must be able to automatically create appropriate nonmonetary issue(s) identified during the claims filing process.
35 / The system must be able to bypass the creation of a nonmonetary issue based on a separation from employment when there are sufficient earnings subsequent to the last date worked to override any potential disqualification period.
36 / The system must be able to dynamically display fact finding questions specific to an opened issue (and circumstances attached to the issue) as part of the unemployment claims filing process.
37 / The system must be able to automatically allocate a post-separation employment remuneration payment to a specific future time period.
38 / The system must be able to automatically preserve a claimant’s benefit entitlement when they are laid off and unable to work due to a disability.
39 / The system must provide the ability for claimants or staff to select the method by which the claimant will receive the UIA Claimant Booklet.
40 / The system must be able to automatically inform a claimant of the requirement to register for work based on the claimant's job/Michigan labor market attachment.
41 / The system must be able to automatically inform a claimant or staff when the claimant is required to certify for weeks of unemployment benefits.
42 / The system must be able to display an estimated (tentative) monetary determination at the end of the claims filing process.
43 / The system must provide the ability for claimants to select a benefit payment method upon completion of the claims filing process.
44 / The system must have the ability, upon completion of the claims filing process, to automatically terminate a prior issue disqualification when the claimant has satisfied the rework provision attached to the disqualification through subsequent employment.
45 / The system must have the ability, upon completion of the claims filing process, to terminate a prior issue disqualification when the claimant has satisfied the requalification provision attached to the disqualification through subsequent weekly certification.
46 / The system must have the ability, upon completion of the claims filing process, to automatically, generate a notice to the claimant to provide proof of earnings when there is a prior issue disqualification where the claimant has not satisfied the rework/requalification
47 / The system must be able to automatically generate a notice to claimants and employers when there is a discrepancy between the family employment designation as reported by the claimant and the employer.
48 / The system must be able to automatically generate the Notice to Chargeable Employer of Claim Renewal to the last employer and chargeable employers only (not to all employers) when an additional claim for benefits is filed.
B.Monetary Determinations
1 / The system must be able to automatically calculate benefit entitlement for all submitted claims for unemployment benefits.2 / The system must be able to automatically establish the base period within which wages will be used to calculate monetary entitlement on a claim (using 1 of 4 different base periods in a defined order until entitlement is established.)
3 / The system must be able to automatically calculate monetary entitlement based on usable base period wages. (Usable wages are allowable wages for all or part of a benefit year)
4 / The system must be able to automatically disallow wages to be used to establish entitlement on a claim if wages were previously used to establish a claim for unemployment benefits (either in Michigan or transferred for use in another state).
5 / The system must be able to automatically calculate and add a dependency allowance to the calculated weekly entitlement.
6 / The system must be able to automatically calculate the potential employer charge for the claim separating employer and all base period claim employers.
7 / The system must be able to automatically calculate monetary entitlement and employer chargeability for Federal and State extended benefit claims.
8 / The system must be able to automatically generate a monetary determination to the claimant, the separating employer and all based period employers.
9 / The system must be able to automatically suppress the generation of a monetary determination to employers based on the program under which the monetary entitlement is calculated or wage source.
10 / The system must be able to automatically hold the generation of a monetary determination (i.e. there based period employers on the claim without a valid UIA Account Number, Federal Employment on the claim).
11 / The system must be able to automatically recalculate monetary entitlement and employer chargeability when certain claim information is changed (examples: wages, employer account number, dependency).
12 / The system must be able to automatically recalculate monetary entitlement and employer chargeability after a specified number of weeks of benefit payments when there are wages on the claim earned in family employment.
13 / The system must be able to automatically recalculate monetary entitlement and employer chargeability when wages have been removed from the claim due to a finding that wages were earned in non-liable employment.
14 / The system must be able to automatically recalculate monetary entitlement and employer chargeability when wages have been transferred from one employer to another as a result of a nonmonetary determination (i.e. quit to accept recall or new employment).
15 / The system must be able to automatically recalculate monetary entitlement when there is a nonmonetary determination which excludes the use of wages for defined periods of time.
16 / The system must be able to automatically recalculate monetary entitlement and employer chargeability when the effective date of a claim is modified which results in a change to the base period.
17 / The system must be able toautomatically recalculate monetary entitlement when there is a nonmonetary determination which excludes the use of wages for defined periods of time.
18 / The system must be able to automatically recalculate entitlement on the claim or set it to zero when a nonmonetary determination is issued resulting in the reduction of weeks of benefit entitlement or in a denial of a claim.
19 / The system must be able to automatically recalculate the monetary entitlement and employer chargeability when a claim is withdrawn.
20 / The system must be able to automatically generate a monetary redetermination when there is a change to the monetary entitlement or employer chargeability.
21 / The system must be able to automatically suppress the generation of a monetary redetermination when nonmonetary determinations are made which exclude wages used to establish the claim.
22 / The system must be able to automatically associate a redetermination with the original monetary determination.
23 / The system must be able to automatically notify employers when the effective date of a claim is modified and the employer is no longer a base period employer.
24 / The system must be able to notify the transferring state when a claim is withdrawn and there are out-of-state wages transferred for use on the claim.
25 / The system must be able to delete any open issues associated with a claim when a monetary redetermination results in the denial of a claim.
26 / The system must be able to automatically charge the UIA’s Non-Chargeable Benefit Account when an employer is relieved of charges/liability due to a non-charge situation.
27 / The system must be able to automatically relieve charges on a subsequent claim for any wages earned during the period of employment for which the employer was granted relief from benefit charges.
28 / The system must be able to automatically generate a Trade Readjustment Assistance (TRA) Monetary Determination when the system determines the claimant is eligible for TRA and there is no remaining entitlement for benefits under any other program.
29 / The system must be able to automatically associate the TRA claim with an existing UI claim and calculate the TRA entitlement based on the most recent monetary determination under the regular UI program entitlement.