Ohio Department of Job and Family Services Contract Amendment #9 C-2021-14-0677-9
Ohio Department of Job and Family Services Contract Amendment #9 C-2021-14-0677-9
C-2021-14-0677-9
This is Amendment #9 to the Contract for Services between the Ohio Department of Job and Family
Services (ODJFS) and Deloitte Consulting LLP (CONTRACTOR), signed by ODJFS on April 13, 2020, and
amended on April 23, 2020, September 24, 2020, November 13, 2020, January 6, 2021 and February 2,
2021, March 2, 2021, April 26, 2021 and August 25, 2021.
b. Updated Price and Payment Schedule section to include the fees for the amendment.
Pricing changes include Cloud Computing Capacity Adjustment and the Experian
usage adjustment.
Page 1 of 21
C-2021-14-0677-9
SIGNATURE PAGE
C-2021-14-0677-9
The parties have executed this Amendment #9 to the Contract as of the date of the signature of the Director
of the Ohio Department of Job and Family Services.
Printed Name
Date Date
180 East Broad Street Suite 1400 30 East Broad Street, 32nd Floor
Columbus, OH 43215 Columbus, Ohio 43215
Page 2 of 21
C-2021-14-0677-9
ATTACHMENT A
uFACTS PUA/DUA Statement of Work – Amendment #9
Project Approach
Deloitte will implement a cloud-based version of our Unemployment Framework for Automated Claim &
Tax Services (uFACTS) solution to meet Pandemic Unemployment Assistance (PUA) requirements of the
CARES Act and UI Disaster Unemployment Assistance (DUA) claims. The solution provides the State
Pandemic Unemployment Assistance (PUA) functionality necessary to support the CARES act, including
processing the additional claims load and making PUA and PFUC payments. The solution also supports
any regular DUA declarations, providing the State with a DUA solution.
Functional Overview
uFACTS is designed to let the State define and operate PUA/DUA programs. System administrators can
define program parameters for PUA and DUA benefit programs. The administrator enters the proper
program parameters (effective dates, eligibility criteria, monetary parameters, etc.) and creates the
program. The system creates the new program type and name and creates the necessary flows to allow
claimants to apply for and, if eligible, receive benefits.
• The system needs to comply with UIPL 16-20 and its associated attachments. Any out of scope
requirements will be subject to a standard change request and approval process.
• PUA/DUA Program Setup - The system allows staff to system administrators the program
parameters such as begin date, incident date, declaration date, etc. and to successfully establish
the program.
• Initial Screening – the system allows claimants to respond to initial screening questions. These
questions determine whether the claimant is most likely a traditional state UI claimant or
PUA/DUA claimant. If the claimant is a traditional UI claimant, they are directed to file an initial
claim with the existing State UI application. If the claimant is a PUA/DUA claimant, they are
directed to the uFACTS Initial Claims functionality.
• Initial Claim - uFACTS for PUA/DUA provides a responsive web framework solution which
captures the complete PUA/DUA UI claim process per USDOL UIPL rules and regulations. The
initial claims application collects pertinent claimant information (such as IRS withholdings and
backdating) upfront, and in detail, to increase the timeliness and accuracy of downstream
processes. Claimants are required to create a user id and password for uFACTS for PUA/DUA
during the initial claim process. Experion ID proofing will be used for identity proofing to
validate the claimant, unless the state and Deloitte mutually agree to an alternate solution for
SSA verification.
Page 3 of 21
C-2021-14-0677-9
• The state and Deloitte will work together to develop mechanisms to prevent claimants from
being paid from both the regular UI and PUA systems in the same week.
• Monetary Determination - For PUA/DUA claims, uFACTS establishes the PUA/DUA monetary
determination based on the earnings information provided by claimant during claim intake
process and uses configurable minimum PUA/DUA WBA and maximum PUA/DUA WBA values
established during the PUA/DUA Program Setup. Monetaries are recomputed based on revised
earnings information.
• Certifications – uFACTS for PUA/DUA provides weekly continued claim certifications
functionality. uFACTS displays the questions based on the current program type of the claimant.
It can accept the weekly certifications on both personal computers and mobile devices due to its
responsive web capabilities.
• Payments - uFACTS for PUA/DUA generates, through the State’s payment vendors, payments to
eligible PUA/DUA claimants that have completed a weekly certification. The process determines
the weekly amount based on the State’s rules for PUA/DUA weekly benefit amounts, as well as
PFUC. A nightly file is generated to the State’s current payment vendor(s) to generate the
payment via direct deposit or debit card. Overpayments established within the system can be
offset against future payments.
• Adjudication - The main purpose of Adjudication is to help staff determine eligibility for
PUA/DUA benefits when issues arise that should potentially prevent payment of benefits.
uFACTS has workflow to intelligently route issues to an adjudicator’s workflow inbox. This
process allows the State to set rules to route the issue to the right adjudicator, using criteria
such as the priority of the issue to the business, the skill set of the adjudicator and the
timeliness due date of the issue.
• Accounting - The uFACTS for PUA/DUA Fiscal Reporting component tracks all payments made at
the claimant level by week, and reports and interface files are generated to allow recording of
summary transactions in the State’s accounting system.
• Workflow - The uFACTS for PUA/DUA Solution provides workflow functionality through the
integrated Business Process Framework powered by IBM Case Foundation.
Page 4 of 21
C-2021-14-0677-9
7. Is designed with data accuracy and integrity, policy and business logic, and automated workflow
and incorporates integrated, intelligent workload management and distribution to help improve
business process efficiency.
uFACTS for PUA/DUA will be hosted on US Regions of Amazon Web Services Commercial Cloud, which
operates under multiple security compliance programs, such as CSA, ISO, FedRAMP, FISMA and many
others.
User Authentication
uFACTS for PUA/DUA includes OKTA’s FedRAMP compliant identity solution for authentication which
wraps around uFACTS Microsoft Active Directory for user management and for authorization services for
claimant and staff users. OKTA and IOP OHID portal integration (OH|ID) will occur after go live. As
detailed requirements unfold, the State and Deloitte will assess project impact and determine and agree
to the scope, schedule and an equitable adjustment to the fees using a standard change request and
approval process.
Deloitte will work with JFS to incorporate data from a JFS PUA Pre-Registration application that JFS will
implement on April 24. Deloitte will provide a table within the uFACTS application to load PUA Pre-
Registration data (SSN, First and Last Name, DOB, Gender, Email Address) prior to uFACTS
implementation. Deloitte shall modify the Initial PUA Triage screen to allow entry of a Pre-Registration
confirmation code, allowing data from the table to populate the subsequent Claimant Demographic
Page 5 of 21
C-2021-14-0677-9
screen. Data will be limited to the data currently displayed in that screen. No other changes to uFACTS
for this integration will be included.
Interfaces
With the timely assistance of State business and technical staff, uFACTS for PUA/DUA will incorporate
the interfaces below as part of the implementation. These interfaces must be completed and tested in
order to place the DUA application in production. Supported interfaces will consist of:
• Scanning and Indexing – for inbound paper documents such as wage verification documents,
eligibility verification information, etc. Interfaces will need to be established to the uFACTS
Document Management System
• Printing – to generate outbound correspondence to the PUA/DUA claimant
• Payment/Bank Interface – daily outbound payment file to existing bank or payment service
(direct deposit or EBT)
• Accounting– outbound interface to the State’s financial account system with summary
transaction data.
• UI Tax System – A routine (automated and scheduled) interface to uFACTS of all wage
information to verify that PUA applicants do not have wage information in the system
• UI Benefits System – A routine (automated and scheduled) interface that provides existing claim
information along with the status of the claim including exhausted and ineligible claims. This
interface will provide details required to administer the PUA program as defined by DOL in
related UIPL(s).
• Child Support Offset – allows for a nightly batch interface to SETS system to allow for offsets.
This is a bi-directional interface into and out of SETS.
Cloud Hosting
Deloitte will implement uFACTS for PUA/DUA on a dedicated, state specific account within a commercial
Cloud provider and configure and maintain the Cloud environment throughout the project. As part of
the scope of this SOW, Deloitte will provide all necessary infrastructure and 3rd-party software required
to support the uFACTS solution via this commercial Cloud provider.
In addition, Deloitte will manage the Cloud environment for the application, addressing the following
services:
• Cloud and Hosting Services Build and Configure
• Incident and Change Management
• Service Reporting
• Monitoring and Alarming
• Security
• Network Connectivity
• Performance and Capacity Management
• Cost Management
• Backup and Restore
• Operating System Management
Page 6 of 21
C-2021-14-0677-9
Training
Deloitte will conduct the following training service for the State users that will work with uFACTS to
service PUA customers: Deloitte will create a training region and training material and deliver training in
three training sessions for staff end users 1 week prior to go live. Deloitte will provide the State with all
the training materials in an editable format so they may maintain the training post go live. We will also
conduct one train the trainer to State training staff post go-live for PUA at a mutually agreeable
schedule. Further details of the training sessions are described below in the Deloitte Responsibilities
section.
Transition Services
Deloitte agrees to provide Transition Services to the State, that will, at a minimum:
Deloitte agrees to provide transition services during the transition of the solution to DAS OIT and at
Project close.
Page 7 of 21
C-2021-14-0677-9
During stabilization of the uFACTS PUA/DUA solution the State and Deloitte agree to transition Deloitte’s
instance of AWS to the State of Ohio Enterprise brokered public cloud service (AWS) currently hosted by
DAS OIT. At the time of this transition, the State and Deloitte will determine if an equitable adjustment
to the fees is necessary. The AWS transition occurred on 4/1/2021 and an equitable adjustment to the
monthly hypercare fee has been incorporated herein.
Project Timeline
Deloitte will complete the project in the Three Phases: Adaption and Implementation, Hypercare and
Maintenance and Operations (M&O):
• Adaptation and Implementation configures uFACTS for PUA/DUA to address the State-specific
requirements for user access, monetary calculations, scanning/imaging interface, payment and
accounting interfaces, other interfaces, testing and training.
• Hypercare is a twenty-two (22) month support and stabilization period. Deloitte is responsible
for maintenance and operations of uFACTS PUA/DUA during this period, consisting of
application monitoring, defect fixes (including material nonconformities to the product and
approved requirements) and ongoing project management. All system enhancements (changes
to the approved requirements) will be subject to a standard change request and approval
process and incorporated at no additional cost within the capacity of the Hypercare team,
approximately 17 FTEs during this period through 3/31/21 and expand to approximately 22 staff
for the period from 4/1/21 through 9/30/21; during the period of 10/1/21 through 3/31/22 the
Hypercare team will revert back to approximately 17 FTEs. Deloitte will respond to all Tier 1
(initial State user contact and troubleshooting), Tier 2 (generally application level
troubleshooting) and Tier 3 (supporting component and infrastructure troubleshooting) support
tickets, providing support to State users.
• Maintenance and Operations is a six (6) month period of ongoing maintenance and operations
support following Hypercare. Team size is reduced and uFACTS for PUA/DUA transition plan is
completed. Deloitte is responsible for maintenance and operations of uFACTS PUA/DUA during
this period, consisting of application monitoring, defect fixes (material nonconformities to the
approved requirements) and ongoing project management. All system enhancements (changes
to the approved requirements) will be subject to a standard change request and approval
process and incorporated based upon the capacity of the Maintenance and Operations team,
approximately 11 FTEs during this period. Deloitte will respond to all Tier 1, Tier 2 and Tier 3
support tickets, providing support to State users. Deloitte will work with OUI/OIS to Conduct
Knowledge Transfer of Maintenance & Operations as described in Transition Services above.
• Optionally, the State can negotiate Deloitte support beyond the Maintenance and Operation
period, in accordance with the standard Amendment, change request and approval process.
The following chart provides a high-level plan for the Hypercare and Maintenance and Operations
Project Phases.
ID Task Name Duration Start Finish
25 Hypercare 688 calendar days 5/12/2020 3/31/2022
27 Maintenance and Operations 182 calendar days 4/1/2022 9/30/2022
28 Maintenance and Operations 181 calendar days 10/1/2022 3/31/2023
(Optional)
Page 8 of 21
C-2021-14-0677-9
Deloitte Responsibilities
Deloitte’s responsibilities during the Project consist of the following:
Hypercare Phase
• Project Management
o Conduct Weekly Status Meeting with Project Sponsor
• Work to resolve prioritized defects (as defined above) and approved enhancements within team
capacity
• Monitor application performance
• Within the capacity of the Hypercare team, appeals will be addressed post implementation
• Deliverables:
o Weekly status reports
Page 9 of 21
C-2021-14-0677-9
State Responsibilities
State responsibilities consist of the following:
Hypercare
• Part Time Positions Required
o State Project Sponsor – provide overall state leadership and serve as a point of
escalation
o State Project Manager – responsible for management of the activities of the State
o State Interfaces Lead – responsible for any changes to interfaces on the State side are
made per the Schedule
Page 10 of 21
C-2021-14-0677-9
o Policy Staff – staff with ability to confirm State PUA/DUA business rules
o SIT and UAT Testers – staff to test the application
o PUA/DUA Staff – perform PUA/DUA operational activities
• Activities required:
o Develop and generate claimant and staff communications
o Perform all PUA/DUA operational activities
o Scanning and Indexing of returned PUA/DUA documentation
Page 11 of 21
C-2021-14-0677-9
o $4,780,806 ($565,667.67 per month for 6 months to extend hypercare and $346,700
per month for 4 months to extend M&O per Amendment #9)
1. From Oct 1 forward, $51,000 per month for Experian usage charges as included in the
Amendment #3 and based on our August fees and some confidence the claims volume had
stabilized.
2. The Experian usage continued to increase from October through December, well above the
$51,000/month budget resulting in a $706,587 adjustment.
• There will be a reduction in fees from $776,667.67 per month to $616,666.67 per month
effective when the Deloitte AWS environment is transitioned to the Ohio Cloud. This new
monthly fee will be pro-rated in the first month based on transition effective date. The new fees
assumes Deloitte will continue to be responsible for the operations and monitoring of the
environment and the State will continue to use the Deloitte cloud toolset. The fee adjustment
will be subject to a standard change request and approval process.
The following table includes the cost elements of the Change Order.
Hypercare 3 Month Extension Plus Additional Changes Below:
Page 12 of 21
C-2021-14-0677-9
*These licenses will be purchased by Deloitte and leveraged as part of the PUA computing
environment and may be transferred to ODJFS, if ODJFS contract with Deloitte terminates or
expires. These software expenses will be billed upon installation.
1. From October through end of Hypercare period, established a budget of $195,000 per month for
AWS (including Deloitte Cloud-Tools) charges(established with Amendment #3).
2. The AWS usage has fluctuated due to increased claims and subsequent updates to the
environment resulting in the following adjustment:
3. The AWS transition occurred on 4/1/21, a final Cloud Capacity adjustment will be subject to a
standard change request and approval process.
Page 13 of 21
C-2021-14-0677-9
2. Once the transition from Experian to LexisNexis is completed, the final Experian usage
adjustment will be subject to a standard change request and approval process.
Fee Adjustment Explanation
The following table details the expanded Hypercare team, AWS credit, and Experian credit.
O&M Period
Hypercare Period (Amendment #5) (Amendment #5)
April May June Oct Nov Total
Expanded Hypercare Team 119,460 119,460 119,460 N/A N/A 358,380
Less AWS -160,000 -160,000 -160,000 -160,000 -160,000 -800,000
Less Experian -51,000 -51,000 -51,000 -51,000 -51,000 -255,000
The following table details the Hypercare three month extension fees.
For clarity, the monthly hypercare and O&M fees, as adjusted, will be billed as follows:
Hypercare O&M
Monthly Fees 776,667.67 557,700.00
Expanded Team $119,460.00 $0.00
AWS/Exp Credit -$211,000.00 -$211,000.00
Updated Fees $685,127.67 $346,700.00
Performance Period April-Sept '21 Oct-Nov '21
Page 14 of 21
C-2021-14-0677-9
1. Hypercare and M&O extension fees by month (the N/A months represent the two months of
M&O included in the original contract).
Deloitte
Month Option FTE Cost
Oct 2021 Hypercare 17 $565,668
Nov 2021 Hypercare 17 $565,668
Dec 2021 Hypercare 17 $565,668
Jan 2022 Hypercare 17 $565,668
Feb 2022 Hypercare 17 $565,668
Mar 2022 Hypercare 17 $565,668
Apr 2022 M&O 11 N/A
May 2022 M&O 11 N/A
Jun 2022 M&O 11 $346,700
Jul 2022 M&O 11 $346,700
Aug 2022 M&O 11 $346,700
Sept 2022 M&O 11 $346,700
Total Hypercare & M&O Extension: $4,780,806
2. The AWS transition occurred on 4/1/21, a final Cloud Capacity adjustment, for March 2021, is
included below.
3. The Experian transition to LexisNexis occurred on 4/1/21, a final Experian Usage adjustment,
is included below.
Page 15 of 21
C-2021-14-0677-9
Assumptions
The following assumptions apply to this engagement, and parties acknowledge that departure from
these assumptions may affect the outcome and timeliness of the engagement and will require a change
order to address the impact on schedule, cost, and scope.
• In light of the COVID-19 crisis and the pressing need to implement PUA, the State and Deloitte
Consulting will be required to prioritize speed over non-critical functionality; decisions will be
governed by the need to pay eligible recipients and not non-essential or desirable functionality.
Customary State standards and rules for reporting, paperwork and process may require
suspension to meet the Project timeline. It is assumed that the implementation will commence
where the following criteria has been met:
o Interfaces listed above have been tested and may be executed, with or without
reasonable work-arounds
o State worker user ids have been created
o End user training has been performed
o Help desk has been established and trained
• The State acknowledges that it may need to authorize overtime for State staff to support the
Project and State responsibilities.
• The State will dedicate or obtain the staffing resources necessary to support the timely
execution of this critical project in accordance with the necessary aggressive project schedule.
• Deloitte Consulting will implement the base uFACTS for PUA/DUA solution; customizations to
Deloitte Consulting’s solution and other changes, including, without limitation, any due to new
Federal guidelines or State requirements, will require a mutually executed change order given
the need for additional resources and the impact of such changes on the project schedule and
pricing.
• The State will be responsible for aligning all 3rd party vendors and systems that are required to
interface with the new PUA system (i.e., payment systems, banks, EBT providers, State
accounting systems), coordinating the timely execution of any agreements, the coordination of
testing and the collaboration of participating partners. Deloitte will collaborate with the State
and 3rd party vendors in finalizing these interfaces for production, using existing interface
specifications.
• Current State technical documentation exists for each interface listed above and that it can rely
on such documentation in development of those interfaces.
• The State and its payment providers can accept payment and financial reporting files and agrees
to process payment files generated by the system, according to the interface standard.
• The State will work with existing State UI bank or payment service to ensure they can receive
and process PUA/DUA payment file separate from State regular UI Payment file, according to
the interface standard. The interfaces generated by uFACTS will contain PUA data only.
• The recent compromised performance of Federal integrity checks may require that such
integrity checks be suspended to ease the customer experience. Integrity may have to be
Page 16 of 21
C-2021-14-0677-9
enforced by the State on the back end, or through subsequent releases of cross-match or other
integrity capabilities.
• Offsets to collect amount due balances from other programs (e.g. UI) are not within the scope of
this agreement. If desired, automated interfaces may be considered to be built and deployed
post-implementation, subject to the capacity of the Hypercare team.
• Offsets for child support may be implemented as a secondary release and must be
accommodated within the capacity of the Hypercare team.
• There will be no interface from uFACTS for PUA/DUA to ICON Services.
• The PUA System will include integration with Experion identity services. Failure to authenticate
with the Experion services shall permit or withhold payment, as per the State’s choice, and
create an identity adjudication issue within the system that staff may elect to respond to.
• Users will authenticate with uFACTS built-in Active Directory Services, unless integration with an
enterprise IAM tool can be accomplished during the project timeline. Users will receive unique
login for uFACTS.
• Any interfaces other than those listed herein will be deferred to a post-implementation release,
and subject to Project Change Control processes.
• Due to the nature of social distancing requirements during the COVID-19 crisis, Deloitte staff will
work remotely until mutually agreed otherwise, and State staff will interact with the project
team using remote videoconferencing. Deloitte staff will be provided promptly with any access
credentials needed to complete the services.
• Development and implementation activities, such as coding and testing, may be conducted by
staff located offshore as well as onshore. No state data will be stored offshore and
unobfuscated production data shall not be viewed or accessed by offshore resources.
• There will be no data conversion included prior to implementation. The system will only serve
new PUA/DUA claimants. Any back conversion of data is subject to inclusion in the Hypercare
capacity.
• The processing capacity included in this SOW is based on an assumption of the AWS Production
Environment in Figure 1: uFACTS Production Environment. Should increased Cloud computing
power and capacity be required due to claimant volume, the parties will process an appropriate
change order to this SOW to adjust such capacity and associated Cloud hosting fees.
• The State and Deloitte agree to participate in Project Health Check Meeting(s), as deemed
necessary.
• From October 1, 2020 through Contract End, if the total number of incomplete claims and new
claims filed exceeds an average of 5,000 per day, an equitable adjustment to fees will be
deemed necessary to account for additional Experian fees. An equitable adjustment to the fees
must be mutually agreed to by the parties and will be subject to a change request and approval
process.
• Hypercare: The below list of hypercare items fall into three categories: (1) Ongoing support
requests, (2) Enhancements with clear scope and priority and (3) Enhancements without a clear
understanding of scope and priority (where it is difficult to estimate effort). Deloitte commits to
complete the items included in Category 1: Ongoing Support Items and Category 2:
Enhancements with clear scope and priority during the Amendment 5 hypercare extension. The
parties acknowledge that PUA is a dynamic program with changing priorities and therefore
Deloitte, working with JFS, will endeavor to complete the Category 3: Enhancments items (albeit
there is an overarching understanding that new federal legislation or guidance may change
these priorities).
Page 17 of 21
C-2021-14-0677-9
• Category 1: Ongoing Support Items, Deloitte will continue to provide support as requests
are made and prioritized by OUI and within the capacity of the hypercare team
a. Ad Hoc Data Requests
b. DOL Audit Findings
c. Mass Adjudication
• Category 2: Enhancements with clear scope and priority, Deloitte will complete during
Amendment #5 & Amendment #7 Hypercare extensions
a. OIG Data Extract
b. Website for Identity Theft (Deloitte understands this will entail an initial load and
daily interfaces, similar to the current wage/benefit interfaces with OJI)
c. LWA Closeout
d. Provide ability for repayments to be applied to overpayment debt
e. Prevent PUEC Paying benefits for same week ending date from both uFACTs and OJI
f. UIPL 16-20, Change 5
g. Lexis/Nexis Integration and Business Support
h. PUA Program changes necessitated by the American Rescue Plan Act (which extends
benefits through 9/6/21)
• Category 3: Enhancements without clear scope and priority, Deloitte will endeavor to
complete during Amendment #5 Hypercare extension as prioritized by OJI and within the
capacity of the hypercare team
a. National Directory of New Hires (NDNH)
b. Wage Record Cross Match
c. Overpayment Recovery Activities
• With regard to Amendment #7 and the transfer of the AWS account from Deloitte to the
State of Ohio, the following assumptions apply:
o Deloitte Cloud Managed Services (CMS) team will continue to provide AWS
infrastructure support once the account is transferred to the state organization.
o Deloitte CMS will maintain operational configuration of the AWS infrastructure (as
they exist today). The CMS staff will receive “I” accounts for Privileged access in
State AWS Organization.
o Deloitte CMS team is responsible for maintaining the management services for the
tools and services (SaaS) used by the shared Deloitte Cloud Management Platform
(GPS Service Hub).
o The cost of using the Deloitte Cloud Management Platform (GPS Service Hub) and
client specific CMP costs will be ongoing (as it works currently and subject to usage
adjustments).
o State will provide Deloitte with their master payer account. The ownership of AWS
accounts where the Application Infrastructure is hosted will be linked to this master
payer account.
o Deloitte will continue to have full administrative access on these accounts (as they
exist today).
o State will have access to AWS billing services and access to AWS console. For
configuration management reasons, it is understood, the State will not make any
configuration changes or limitations without approval of Deloitte.
Page 18 of 21
C-2021-14-0677-9
o State will be responsible for billing and all costs associated with these three AWS
accounts.
o State will leverage its Enterprise support agreement for AWS and provide Deloitte
CMS team with the ability to create support tickets.
o Deloitte has included the costs for the annual renewal of the FileNet/Datacap
licenses and the annual renewals for the Palo Alto licenses in this Amendment #7.
Page 19 of 21
C-2021-14-0677-9
ATTACHMENT C
uFACTS PUA/DUA COST SUMMARY
Description Amount
Contract Amendment #1
$ 9,919,000.00
a) uFACTS PUA/DUA SOW: updated functional and training scope and associated (Call Center)
cost. ($50,000)
$50,000 (uFacts)
b) Addition of PUA Call Center SOW for PUA Call Center Operations.
Contract Amendment #2
PUA Call Center SOW: addition of hours for Call Center to account for 150 staff $ 16,153,842.60
per interval hour and updated call center service coverage.
Contract Amendment #3
b) PUA Call Center SOW: reduction in interval hours to 100 and extended end
date to December 31, 2020. Adjusted cap amount for staffed hours.
Contract Amendment #4
PUA Call Center SOW: new call types, extended end date to June 30, 2021, $ 22,955,540.00
introduced new labor category rates starting January 1, 2021, increased interval
hours to 150, and adjusted cap amount for staffed hours.
Contract Amendment #5
uFACTS PUA/DUA SOW: additional five months of Hypercare and Experian usage $ 4,589,920.35
adjustment.
Contract Amendment #6
PUA Call Center SOW: addition of 200-250 more agents for the Call Center $ 10,845,472.00
operations through end of SOW.
Contract Amendment #7
uFACTS PUA/DUA SOW: additional three months of Hypercare, fraud services, 3,507,964.01
Experian usage adjustment, cloud capacity adjustment, software updates
Page 20 of 21
C-2021-14-0677-9
Description Amount
Updated and/or added SLAs for both uFACTS solution and call center services;
changed compensation and billing model to productive call per minute rate for call
center services; added KPIs, updated auditing requirements, and updated Costs.
Contract Amendment #9
uFACTS PUA/DUA SOW: final AWS & Experian adjustments, extension of $5,650,928.00
hypercare and M&O services
Original Original
$0.00 $9,609,900.00
Contract $9,609,900.00 Contract
Page 21 of 21