ODJFS Child Support SETS Modernization RFP

THIS AMENDMENT 1 UPDATES THE COST WORKBOOK.At the heart of this modernization effort is a commitment to human-centered design. Technologically, SETS is embracing a cloud-native architecture. The modernization plan is structured around the following key initiatives: Intake / Case Initiation: To modernize state/federal data exchanges and automated locate Case process related batch jobs running in mainframe and associated data to the modernized child support architecture. Data Exchange Migration: Modernize some of the Data exchange jobs running on the Mainframe as COBOL and JCL batch programs scheduled through Control-M. Case Management: Modernize the core business capabilities involved in managing the lifecycle of a child support case after intake. Financial Management: Modernize the critical financial operations components of the child support system. Data Analytics: To modernize the data analytics platform and integrate actionable insights directly into case management functions. Supporting Solutions: To modernize smaller, peripheral modules that support specific OCS operations alongside the core case management system. This project is for enhancement, not a new application.
Please find resources below to aid with using OhioBuys and solicitations:Using OhioBuys: https://procure.ohio.gov/bidders-and-suppliers/resources/03_Using+OhioBuysSubmitting a response: https://procure.ohio.gov/bidders-and-suppliers/resources/04_Submitting+a+ResponseAdditional Webinars regarding OhioBuys and Solicitations: https://procure.ohio.gov/bidders-and-suppliers/resources/bidder-and-supplier-training/01_Supplier+WebinarsTo participate or submit an inquiry for this RFx, you need to be registered in the OhioBuys Supplier Portal. Suppliers are not required at this time to be registered in OAKS. If you have a need to seek technical support, clearly specify you need access to an active Ohio Buys solicitation.Technical Support 1-877-644-6771
Information technology consultation services
Inquiries Inquiry 91880 | Should the proposed Solution be designed to operate within the State's current cloud tenancy, or may the Offeror propose a dedicated, managed cloud environment that meets all State security and compliance requirements? | Answer: As long as the proposed hosting meets all security requirements it may be acceptable. | Answered: 7/7/2026 Inquiry 91883 | Is the State open to evaluating Solutions hosted on any FedRAMP-authorized commercial cloud platform, provided the Offeror meets all State IT security and compliance requirements outlined in Supplement 3? | Answer: As long as the proposed hosting meets all security requirements it may be acceptable. | Answered: 7/7/2026 Inquiry 91886 | Is there an incumbent on this project? Is there a budget ceiling available for this project? | Answer: This is a new set of work and thus there is not an incumbent. Currently there is not any budget details that the State is prepared to share. | Answered: 7/7/2026 Inquiry 91969 | Where would JFS like the Vendors to include software costs in our proposal? Should we add another tab to the Costs spreadsheet or add it to our technical response? | Answer: No cost information should be in the technical response, only in the cost workbook. If there are additional costs associated with software, please include a total cost for software as an additional deliverable line item under the Deliverables tab, and then a line item breakdown of software costs can go in the Cost Assumptions tab. | Answered: 7/9/2026 Inquiry 92035 | General Data Screens (GDS) is the only place in the Scope of Work where an explicit data-content exclusion is stated (no FTI, Confidential, or Family Violence data). Is GDS modernization in scope under one of the named initiatives, such as Case Management or Supporting Solutions, or is it considered part of the existing baseline and therefore out of scope for this Contract? | Answer: GDS Screens are in scope for modernization under this Contract. The Scope of Work notes that GDS does not provide caseworkers with access to data containing FTI or Family Violence Information (FVI), and this clarification is intended only to describe the type of data available through GDS—not to indicate that GDS is out of scope. | Answered: 7/10/2026 Inquiry 92038 | The Scope of Work states the modernization must "continue to meet the required federal certification requirements" while core architecture (RACF, batch processing, data platform) is replaced incrementally across multiple SOWs. Will ODJFS require formal OCSE re-certification checkpoints after each individual initiative, or only a single re-certification at the conclusion of the full modernization program? | Answer: No checkpoints or recertification will be required. As the (already completed) line-for-line code conversion ensured that the OCSE certified functions are intact, no recertification tasks are required. All future enhancements will leverage certified legacy code (converted line-for-line from COBOL to .NET) to deliver enhanced user experience through upgraded front-end functionality and navigation. | Answered: 7/10/2026 Inquiry 92041 | Beyond the exclusions noted for GDS access, the Scope of Work does not include a dedicated "out of scope" section, leaving scope boundaries to be inferred from what each initiative description does and does not mention. Can ODJFS confirm whether any current SETS functionality, interface, or user-facing capability is explicitly intended to remain untouched or excluded from modernization under this Contract? | Answer: ODJFS has not defined any existing SETS functionality, interface, or user-facing capability as being explicitly out of scope at this time. The Contractor must work with designated ODJFS staff in the development of the Scope of Work (SOW) and associated deliverables for each initiative listed, and for any additional initiatives as necessary throughout the duration of this Contract. Deliverables and scope boundaries will be established and negotiated prior to the start of each new SOW. | Answered: 7/10/2026 Inquiry 92045 | The Supporting Solutions initiative lists "Other Toolbox Features" — Third Party Search, Medical Support Adjustment, TPN Management, Casino Racino, and Central Registry — without any scope, objective, or functional description comparable to what is provided for PAAR, ROPAA, or Worker Portal Migration. Can ODJFS provide the functional scope and relative priority of each of these five features so Offerors can meaningfully estimate effort at the proposal stage? | Answer: his subsection under Supporting Solutions is included to provide vendors with insight into additional peripheral modules that support specific OCS operations. We do not expect vendors to respond with detailed scope for each distinct module. At a high level, vendors should simply acknowledge that these modules could become part of a future Scope of Work and indicate any relevant experience they may have. | Answered: 7/10/2026 Inquiry 92048 | Is the State of OH at this time in compliance with general requirements, OCSE, and IRS Publication 1075? | Answer: Yes to both. | Answered: 7/10/2026 Inquiry 92161 | Supplement 3 §5.2.2 describes the IOP User Experience Service Offering (centralized site hosting, page templates, Form.io-based web forms). For the internal caseworker/supervisor application (Angular / ASP.NET Core MVC per §2.7), how does the State distinguish between UX delivered through IOP's centralized services and custom application UX delivered by the Contractor? Should the HCD Analysis address both, and where is the intended boundary? | Answer: Internal Caseworker/supervisor application will be independent of the IOP centralized hosting service | Answered: 7/13/2026 Inquiry 92164 | The RFP requires State AI Council review and approval of proposed Generative AI capabilities in accordance with IT Policy IT-17. To support accurate project planning, can ODJFS clarify the expected approval process and timeline, including whether approval will occur prior to Notice to Proceed or initiation of individual Statements of Work? If approval is delayed or a proposed AI capability is not approved, how should Offerors account for any resulting impacts to project schedule, staffing, or pricing? | Answer: ODJFS will need State AI council approval prior to individual SOW and we will need an AI readiness assessment approved by State AI sub-committee prior to production deployment. | Answered: 7/13/2026 Inquiry 92167 | Of the 598 IRS Publication 1075 requirements in the compliance matrix, 425 (71%) are assigned primarily to the Agency (ODJFS) rather than to the system or Contractor. For those Agency-owned controls, what level of Contractor involvement is expected, for example, building system features that support ODJFS's compliance (audit logging, access restriction, reporting), providing documentation support during IRS safeguard reviews, or no involvement at all? | Answer: The Office of Child Support is required to adhere to IRS Pub. 1075 requirements. For the controls designated as Agency‑owned, ODJFS expects the vendor to understand our obligation to comply with this regulation. In some cases, this may mean the vendor will need to develop system features that support compliance. The vendor may also be asked to provide documentation or system‑related clarification during IRS safeguard reviews, as appropriate. ODJFS does not expect the vendor to own Agency‑assigned controls. | Answered: 7/13/2026 Inquiry 92170 | The Data Exchange Migration initiative references ODJFS's completed analysis identifying "target state for main categories" of the 115 COBOL/JCL data-exchange batch jobs, without stating whether all 115 jobs are in scope for migration under this initiative. Can ODJFS confirm whether all 115 COBOL batch programs are to be migrated, or whether some are intentionally being retained on the current architecture indefinitely? | Answer: All processing performed by the 115 COBOL/JCL data exchange batch jobs is included in scope and will be migrated to the target platform. | Answered: 7/13/2026 Inquiry 92173 | ODJFS has already completed a UX study, released the Self-Assessment Modernization tool in November 2025, and is actively developing the Basic Case Dashboard & Foundational Features project, which is described as producing "reusable building blocks for future modules." In what form will these existing components be delivered to the Contractor (source code, a design system/component library, APIs), and is the Contractor expected to extend, refactor, or potentially replace this inherited work under later initiatives? | Answer: The primary output from the UX study consists of wireframe screens, which will be provided to the awarded vendor at the appropriate time to serve as a starting point. These wireframes will be delivered along with the detailed requirements that have already been developed. | Answered: 7/13/2026 Inquiry 92176 | Supplement 1(a) §2.1.1 references a completed UX study and established UI solutions, design patterns, and UI standards described as "the foundation of the modernized system's user experience." Will these artifacts be made available to offerors during the inquiry period, or to the awarded Contractor at project initiation? Additionally, should the Human Centered Design Analysis and Recommendation Document (Cost Workbook, Deliverables) include validation or assessment of these existing assets against user needs, or are they considered established and out of scope for evaluation? | Answer: 1. The State will make all existing UX study artifacts, UI solutions, design patterns, and UI standards available to the awarded Contractor at project initiation.2. The Human Centered Design Analysis and Recommendation Document should incorporate a review and validation of the existing UI/UX artifacts to ensure continued alignment with user needs. While the State considers these foundational materials established, the Contractor is expected to evaluate their applicability within the context of the modernization effort, identify any gaps, and provide recommendations where updates or enhancements may be warranted. | Answered: 7/13/2026