B.2.4 The System must assign a two digit NAICS code based on information provided during the registration process. The two digit NAICS code will be used to determine the new business rate based on Ohio law. C B.2.5 The System must be capable of creating a workflow process providing the Labor Market Information section the ability to assign the NAICS code. C B.2.6 The System must be capable of receiving a file from the Labor Market Information section of all NAICS codes changed and adjust the new business rate according to Ohio law and rule. C B.2.7 The System must staff to view the information used in the calculation of a tax rate for an employer (i.e. history of benefit charges, taxable payroll and taxes paid, credits, adjustments, etc.). C B.2.8 The System must allow for annual taxable wage base to be a parameter based on calendar year and calculate the taxable wage base based on the value entered. C B.2.9 The System must allow staff to perform 'what if' scenarios to view the outcome of new tax rate calculations prior to the outcome becoming official. C B.2.10 The System must allow staff to suspend the automated rate calculation on an employer account. C B.2.11 The System must allow staff to manually restart the automated rate calculation on an employer account. C B.2.12 The System must be able to automatically calculate the components (history of benefit charges, taxable payroll and taxes paid) used in the rate calculation before calculating the employer tax rate. C B.2.13 The System must be able to automatically calculate the tax rate of a successor employer(s) account when there is a full or partial transfer of business based on Ohio law and rule. C
B.2.14 The System must provide the ability to combine two or more transfers of employer experience/financial data when calculating tax rates. C B.2.15 The System must automatically calculate and assign tax rate penalties to the appropriate employer accounts. C B.2.16 The System must automatically calculate and solvency tax to the appropriate employer tax rate. C B.2.17 The System must automatically calculate and apply a surcharge tax to appropriate employers tax rate. C B.2.18 The System must recalculate tax rates when a benefit charge/credit is applied/moved to or from an employer account based on Ohio law and rule. C B.2.19 The System must automatically recalculate the employer's rate upon receipt of a voluntary payment. C B.2.20 The System must automatically process the appropriate tax rate recalculation, when multiple liability and tax rate (re)determinations on the same business day i.e. liability date changes, reconsidered decisions, etc. C B.2.21 The System must automatically recalculate and remove tax rate penalties and solvency tax when applicable. C B.2.22 The System must allow staff to modify an employer's rating experience by adjusting values within each category used in the rate calculation, i.e. between fiscal years, between employer accounts, rate balance, etc. C B.2.23 The System must allow staff to remove penalties. C B.2.24 The System must staff to change tax rate component information. C B.2.25 The System must staff to suppress the generation of a tax rate notice. C
B.3.43 The System must automatically post the Quarterly Wage Detail/Quarterly Summary Reports or the Quarterly Wage Detail/Payroll Reports to the successor employer account if the report is submitted by a deactivated employer. This may generate a work item. C B.3.44 The System must automatically post the Amended Quarterly Wage Detail/Quarterly Summary Reports or the Amended Quarterly Wage Detail/Payroll Reports to the successor employer account if the report is submitted by a deactivated employer. This may generate a work item. C B.3.45 The System must generate a monthly statement to the Employers a payment, credit or change in balance due is posted to the Employer account. C B.3.46 The System must generate a Notice of Failure to File report to the contributing Employers who fail to file their Quarterly Wage Detail/Quarterly Summary report. C B.3.47 The System must generate a Notice of Failure to File Wage Detail/Payroll report to the reimbursing Employers who fail to file their Quarterly Wage Detail/Payroll report. C B.3.48 The System must be capable of posting prior quarter reports and adjusting the employer account accordingly (e.g. taxes, rates, taxable wages, penalties, interest, etc.) C B.3.49 The System must provide the capability for staff, employers and TPA’s to correct wage information during input process and after the acceptance of the data. The System must correct and post the information and calculate and tax and/or benefit changes as a result of the amendment. C B.3.50 The System must perform a reconciliation between the wage and quarterly summary reports and create a work item to be processed by staff if not corrected automatically. C
B.4.56 The System must calculate the amount of contributions, forfeiture, interest, surcharge and assess/provide a monthly statement to include the amount due and/or any credits available. C B.4.57 The System must allocate any payments made to employer accounts on Ohio law and rule. C B.4.58 The System must be capable of allocating payments made on the total rate and breaks down the distribution of the payment between the different rate factors. This includes contributions, mutual, surcharge and penalties. C B.4.59 The System must allow staff to reallocate payments. C B.4.60 The System must provide a process to allow staff to create a coupon for checks received without coupons that can be processed on our check process equipment. C B.4.61 The System must staff to request and/or view statements for an employer account (i.e. IRS Certification of Accounts, Summary of Benefit Charges and Credits, Monthly Statements, etc.). C B.4.62 The System must allow staff to generate employer account statements (i.e. Zero Balance). C B.4.63 The System must allow staff to view the tax appeal history for an employer account. C B.4.64 The System must allow staff to enter/update/view a tax appeal (tax rate, tax liability, and/or assessment/collection) or an appeal of a an employer account. C B.4.65 The System must allow staff to enter/update/view information related to an employer's request/designation as a Seasonal Employer. C B.4.66 The System must automatically generate a determination to designate an employer as a seasonal employer. C B.4.67 The System must allow staff to enter/update/view yearly school calendar information for an employer (educational institutions). D
C.3.29 The System must calculate/generate/make available a fund reconciliation report for UI Tax that shows the total dollar amount of activity that occurred in the mutual account. C C.3.30 The System must account for the prohibition of noncharging (employer penalty) when a pattern of untimeliness/inadequacy is established for responding to requests for separation information. C C.3.31 The System must have the ability to credit an employer and charge the mutual account when a BWC reimbursement payment is received for a specific claimant, amount, and time period. C C.3.32 The System must have the ability to credit the mutual account when a BWC repayment can't be credited to an employer. C C.4 Benefits Processing C.4.1 The System must provide a method for filing continued claims for the following program; Ohio UI (including all sub-types), State EB, UCX, UCFE, DUA, interstate, TRA, STC, R/ATAA, SharedWork, and federal extension programs. C C.4.2 The System must provide the ability for claimants or staff to file weekly continued claims for benefits by various methods including web and mobile responsive screens. C C.4.3 The System must provide the ability for claimants or staff to certify for multiple weeks during a certification session (i.e. backdating a claim, retroactive eligibility and extended benefits). C C.4.4 The System must automatically create a nonmonetary issue when the weeks being claimed are untimely during the certification process. C C.4.5 The System must automatically create a nonmonetary issue when the weeks being claimed result in a break in registration. C
C.4.15 The System must identify if claimant quit, refused an offer of work, or was discharged from employment during the week being claimed. C C.4.16 The System must automatically create an based on the responses to the questions answered during the continued claim filing process C C.4.17 The System must automatically create an issue when a claimant is certifying for benefits under the TRA program if the claimant is not enrolled in training and there is no valid training waiver for the certified week(s). C C.4.18 The System must automatically create an issue when a claimant is certifying for benefits under the additional TRA, including completion TRA program and the weeks being claimed fall within an extended school break period greater than 30 days. C C.4.19 The System must automatically prompt claimants or to certify responses to continued claim questions prior to final submission during the weekly claim process. C C.4.20 The System must provide the ability for claimants or staff to respond to questions specific to an opened issue (and circumstances attached to the issue) as part of the weekly claim process. C C.4.21 The System must automatically establish the new (transitional) claim for benefits when the benefit year has ended with the current weekly claim. D C.4.22 The System must automatically notify the claimant to file a claim for extended benefits (State or Federal) provided an extension is available. D? C.4.23 The System must automatically establish a new claim for benefits, in a quarter change situation, when a claimant can establish eligibility for regular state UI payments when filing under an extended benefit program. D? C.4.24 The System must prevent issuance of a benefit payment if a waiting week has yet to be served. C
C.5.31 The System must identify when non-monetary issues require a tally according to Department of Labor standards. C C.5.32 The System must automatically capture appeals in the system at all levels of appeal. C C.5.33 The System must only allow interested parties to the particular determination to have the ability to appeal it and provide supporting documentation. C C.5.34 The System must provide the ability for staff to manually enter/update/view/withdraw an appeal. C C.5.35 The System must process appeals at various adjudication levels, including initial, redetermination, appeals, UCRC, and appeals to court. C C.5.36 The System must capture particular appeal information such as date appeal received, reason for appeal, appealing party, date of filing (postmark or metered mail), and level of appeal. C C.5.37 The System must create a nonmonetary if appeals have been filed untimely based upon a configurable time period. C C.5.38 The System must notify interested parties that an appeal has been filed. C C.5.39 The System must allow for appeals to be remanded to a lower level. C C.5.40 The System must provide staff the ability to generate earnings eligibility notices that includes the week(s) claimed. D C.5.41 For non-monetary issues that involve a claimant that used to work for the Ohio Department of Job and Family Services (ODJFS), the claimant's claim must be flagged so it can be handled by an objective party. C C.5.42 The System must capture, for a specific business location, a mass layoff's general information and create non-monetary issues associated claimants file for benefits. C C.5.43 The System must process benefit decisions associated to labor disputes (strikes/lockouts). C C.5.44 The System must determine if a dispute involves more than 25 individuals, if so, a hearing must be scheduled. C
C.7.24 The System must staff to access ICON transactional functionality, such as IBIQ, WIC, IB13, and Interstate Handbook. C C.7.25 The System must allow staff to view, resend, add UCX/UCFE transactions. C C.7.26 The System must allow staff to view, resend, add IB transactions. C C.7.27 The System must allow staff to select a choice between a straight Ohio and Combined Wage Claim on behalf of the claimant. C C.7.28 The System must process and produce the yearly federal form. C C.7.29 The System must allow staff to produce a 1099-G correction. C C.7.30 The System must staff to administer (add/modify/delete) notes to a claimant's or employer's account. C C.7.31 The System must allow staff to view separation requests and responses that are processed through the SIDES interface. C C.7.32 The System must staff to process repayments to be applied to outstanding overpayments. C C.7.33 The System must allow staff to view/update DUA certification information. C C.7.34 The System must allow staff to view/update information related to a DUA claimant/claim. C C.7.35 The System must capture and establish presidentially-declared disaster information (i.e. disaster date, declaration date, disaster number, disaster type, counties affected). C C.7.36 The System must capture disaster announcement date, as it is used to determine timeliness of application. C C.7.37 The System must capture maximum duration of benefits for the declared disaster. C C.7.38 The System must establish a disaster-specific benefits fund account for funding estimates and requesting advance of funds through DOL. C C.7.39 The System must display fund balance (benefits paid subtracted from disaster-specific funds received from DOL). C G
C.10.3 The System must the BAM paid case sample with the National Directory of New Hires (NDNH) and provide a report to staff. C C.10.4 The System must allow staff to manually adjust the DOL random number and sample size for each BAM batch week. C C.10.5 The System must electronically transmit a file of BAM cases selected for assessment to the USDOL Federal SUN System. C C.10.6 Each quarter, the system must randomly select separation and non-separation issues that were initially determined for Benefit Timeliness Quality (BTQ) review. C C.10.7 The System must provide a population of employer accounts that were chargeable in a given year so samples can be pulled for employer charging TPS activities. C C.10.8 The System must produce a cross match report that identifies EFT account numbers utilized by multiple claimants. C C.10.9 The System must produce a cross-match report that identifies potential fictitious employer schemes. D C.10.10 The System must crossmatch benefit payments against the UI Quarterly Wage data. C C.10.11 The System must automatically generate forms to employers and/or claimants soliciting information to validate a cross match finding. C C.10.12 The System must crossmatch benefit applications with overlapping incarceration periods. C C.10.13 The System must display the information that is a result of the internal cross match used to identify situations where benefits payments are being issued to multiple claimants with the same mailing address. C C.10.14 The System must crossmatch benefit payments against the National Directory of New Hires for wages/dates of hire and create a non-monetary issue for adjudication. C C.10.15 The System must crossmatch benefit payments against the State Directory of New Hires and create a non-monetary issue for adjudication. C
C.13.33 The System is not required to withhold child support from SWO benefits (already being withheld by employer). C C.13.34 The System must allow staff and employers/TPAs to submit plan modifications to an originally approved SWO plan, including adding to the SWO participating employee list. C C.13.35 The System must allow a SWO claim to transition to/from other UI programs based upon business factors such as plan is terminated, shut down, etc. C C.13.36 The System must allow staff to terminate a plan for good cause and notify the employees and employers/TPAs of such decision. C C.13.37 The System must not breaks in claims under traditional UI rules to impact SWO claims. C C.13.38 The System will allow multiple SWO plans for an employee in a single benefit year. C C.13.39 The System will move SWO employee data between benefit programs (e.g., SWO, UI, etc.). C
D.5.3 Provide a high-level architecture diagram, including logical and physical components. C D.5.4 System documentation must describe error logging and how to access the error logs. C D.5.5 System documentation must describe any batch processing requirements for the application. C D.5.6 A detailed network/server diagram must be provided illustrating the relative architecture of the proposed system. It must include: Network security zones and firewalls; Server and network components (e.g., switches); Ports and protocols used to cross security zones; How users will access the system; and Clustering of servers C D.5.7 Provide conceptual and logical application data-flow models. C D.5.8 Provide a technology roadmap for the proposed system showing a five (5) year plan for new software version releases, support window, and sun setting. C D.6 Conversion D.6.1 Must describe their strategy and approach for data conversion, including descriptions of prior similar projects. C D.6.2 Must provide conversion of data from the current benefits system into the proposed system is sufficient to provide a historical record of participation episodes based on federal requirements. C D.7 Security and Recovery D.7.1 Must describe how the system security supports role security and protects access to sensitive data. C D.7.2 Must provide a recovery plan for restoring services in the of a disaster including system and data restoration. C
D.8.1 Application authentication and authorization must be by individual user. User account information must be stored securely. may belong to groups and roles. C D.8.2 The application must enforce the following rules on individual passwords for allowable characters, length and expiration period: Standard Window characters allowed; Minimum of 8 characters in length; Expires every 90 days; and Cannot reuse passwords for 1 year C D.8.3 The application must lock out after five invalid login attempts due to bad passwords. C D.8.4 The application must provide the system administrators with the capabilities to define different roles with different privileges. C D.9 System Performance and Capacity D.9.1 The application must provide performance-optimization capabilities. C D.9.2 The application must maintain optimum performance over both Wide Area Network (WAN) and Local Area Network (LAN). C D.9.3 System documentation must clearly describe all versions of the package that are deployed for different scaling situations. C D.9.4 System documentation must clearly describe all activities that affect optimum performance such as service recycling, rebooting, or batch jobs and their frequency. C D.9.5 The System must provide a response time of less than 2 seconds for accessing low complexity pages composed of mostly static text and other non-computationally intensive elements. C
D.10.1 The System must be robust, responsive, and highly available. Must describe the hosting and infrastructure used to provide services to C D.10.2 A documented Media Protection policy that addresses purpose scope, roles, responsibilities, and procedures, developed and distributed to all employees, must be provided. C D.10.3 Media is sanitized and disposed of based on written policies and procedures approved by ODJFS. C D.10.4 A documented Physical and Environmental protection policy that addresses purpose scope, roles, responsibilities, and procedures, developed and distributed to all employees, must be provided. C D.10.5 The proposed solution delivers standard reports/information useful for assessing the overall status, operation and debugging of the solution. C D.10.6 A documented Systems and Information Integrity policy that addresses purpose roles, responsibilities, and procedures, developed and distributed to all employees, must be provided. C D.10.7 Must identify, report, and correct information system flaws. C D.10.8 Must implement malicious code protection and techniques. C D.11 Single Sign-on D.11.1 The System must support single sign-on for all functions within the System (i.e. staff must not have to separately logon to conduct case management and job matching functions). C D.11.2 The uses a Microsoft active directory environment; other entities may utilize active directory or other authentication mechanisms for their local domains. Please describe options for importing and synchronizing user accounts with preexisting log on mechanisms.