RFP-_ORR_Collection_Software_Appendix_B.pdf
PDF 25 KB Posted
- Attached to
- Revenue Recovery Collection Technology Solution
- Solicitation number
- RFP-2022-0003
- Issued by
- Tuolumne County, California
About this file
This document is Appendix B of a Request for Proposal (RFP) from Tuolumne County, California, for a Revenue Recovery Collection Technology Solution. The RFP seeks a comprehensive, centralized debt collections and delinquency management system that can migrate historical data from the existing Ontario Systems Revenue Plus Collection System (dating back over 20 years), interface with multiple external systems including CentralSquare ONESolution, local Superior Court's eCourt system, California Franchise Tax Board, credit reporting agencies, and California Employment Development Department.
The proposed solution must include a detailed implementation plan with methodology, timeline, project milestones, and a completion schedule. The county requires segmented quality assurance (QA) testing with weekly check-ins and approval sign-offs for each implementation stage. Vendors must provide a high-level overview of their proposed solution, demonstrate the ability to handle data migration, explain data exchange strategies (batch vs. real-time), and ensure all proposed information can be verified by documentation if requested. Failure to provide accurate information may result in proposal rejection or award rescission.
View the file
Other files
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Request for Proposal Revenue Recovery Collection Technology Solution Page 1 of 1
APPENDIX B
BUSINESS REQUIREMENTS AND RESPONSE FORM
Please provide a detailed and comprehensive narrative response to each item in the order listed below.
Do not include or refer to links or websites but include the written material from those sites/sources in your response below.
Please use letters and numbers to identify your response as it correlates to each item. Do not modify the order, format, or font.
All information provided should be verifiable by documentation if requested by the County. Failure to provide information, inaccuracy or misstatement may be sufficient cause for rejection of the proposal or rescission of an award.
A General Requirement A.1 System shall be a single comprehensive solution for a centralized operation for debt collections and delinquency management.
Please provide a high-level overview of your proposed solution.
B Data Migration and Data Extraction Requirement B.1 System shall have the ability to incorporate migrated and stored data from Ontario Systems
Revenue Plus Collection System (RPCS) with data dating back more than 20 years. Data currently includes active and inactive accounts.
Please explain how your solution will handle this data conversion and migration.
C. Interface with Required Software Applications and Systems C.1 System will be required to interface with existing County systems to transfer business process information to allow for collaboration between CentralSquare ONESolution (Finance Enterprise) and its business partners and vendors.
Please explain how your solution will address this requirement. In your description, please include the strategy for data exchange i.e. batch vs real-time.
C.2 System will be required to interface with existing local Superior Court system, Journal Technologies eCourt, to receive applicable case-related information, including fines and Court-Ordered Debt.
C.3 Ability to interface with California Franchise Tax Board for Court-Ordered Debt and Tax Intercept programs.
C.4 Ability to interface with Experian and TransUnion credit reporting agencies on collection accounts.
C.5 Ability to interface with California Employment Development (EDD) on employment data of debtors.
D. Implementation Plan D.1 Provide a detailed project implementation plan which includes:
• Implementation methodology
• Proposed timeline
• Project milestone
• Schedule for project completion
E. Quality Assurance (QA) Testing (must be included in the data migration plan).
E.1 QA testing and check-in approach for each path.
E.2 Segmented QA testing with periodic (at minimum weekly) check-in and approval sign-off on the completion of each stage of implementation.
Appendix B
File details come from the government source that posted it. Updated .