CBRAP Request for Proposal v.26 FINAL.docx

DOCX document 91 KB Posted

Attached to
Open Market Competitive Sealed Proposal IL|25-551HDA-INFOT-P-95909
Contract number
25-551HDA-INFOT-P-95909
Issued by
Illinois

About this file

Summary

This is a Request for Proposal issued by the Illinois Housing Development Authority (IHDA) for the Court Based Rental Assistance Program (CBRAP), solicitation number 25-551HDA-INFOT-B-48900. The IHDA seeks a cloud-based, end-to-end software solution to support emergency rental assistance for litigants in eviction court throughout Illinois. The solicitation requires vendors to submit technical responses, commitment to diversity documentation, pricing proposals, and standard vendor disclosures through the BidBuy procurement portal, with a proposal due date in October 2025 and vendor demonstrations scheduled for November 2025.

The resulting contract will have an initial two-year term commencing upon final execution, with options to renew for four additional two-year periods, not to exceed ten years total. The solution must be a fully web-based Software-as-a-Service system supporting up to 5,000 concurrent users and 300 remote application processors, with mandatory requirements including SOC2 Type 2 certification, 99.9% uptime availability, real-time address validation, multi-lingual support (English and Spanish), role-based access control with multi-factor authentication, and robust reporting capabilities integrated with Oracle and Power BI. The evaluation criteria allocate 575 points for technical requirements, 135 points for commitment to diversity (20% of technical points), 100 points for vendor demonstrations, and 162 points for pricing, totaling 972 maximum available points. The contract start date is targeted for February 2026 with a system go-live date of July 2026.

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

Illinois Housing Development Authority Request for Proposal Court Based Rental Assistance Program (CBRAP) Application and Grant Payment Management System

25-551HDA-INFOT-B-48900

Section A. SCOPE OF WORK

A.1. OVERVIEW AND PURPOSE

The Illinois Housing Development Authority (“IHDA”) is seeking a cloud-based and cross-platform, end-to-end software solution for public application submission, internal application review and grant payment management (“Solution”) to support its Court Based Rental Assistance Program (“CBRAP”). CBRAP will provide emergency rental assistance statewide to litigants in eviction court. CBRAP is only available to Illinois litigants in eviction court. Applications are reviewed on a first come, first served basis. Tenants with a court summons or an eviction notice from a circuit court can apply. IHDA may prioritize applications with an imminent eviction date. Submission of an application is not a guarantee of funding. The Solution should also allow for direct communication between parties, applicant status tracking, document upload, data extraction or integration with Oracle financial systems, and feature robust reporting capabilities or integration to Power BI.

1. Paperless Functions including, but not limited to:

· Receive custom-defined applications from the public via 100% internet web interface

· Support for N-1 versions of Firefox, Chrome, Edge, and Safari

· Receive custom-defined applications from the public via 100% native mobile interface for iPhone and Android phones

· Perform all internal application processing

· Request documents ad-hoc from specific individuals

· Provide applicant self-service application status lookups

· Have real-time address validation functionality (auto lookup/fill of USPS address)

2. Data Management including, but not limited to:

· All fields are customizable, able to support all standard input types (text, radio button, checkbox, etc.) and can add/update/move/drag fields, name and provide descriptions

· Ability to validate format and content of pre-defined data types

· Ability to support logic on data input screens to collect data based on previously inputted data

· Ability to track eviction number in apps and other data points collected

· Ability for internal users to be able to access application changes over time

· Ability for bulk uploads/updates to be able to make changes to groups of records

3. Support a multi-lingual interface with both English and Spanish

· Solution to have ability to make basic content edits.

· Any necessary automated emails need to be multi-lingual.

4. Securely support multiple, multi-step application processes (i.e., multiple programs supporting multiple rounds of federal funding):

· Initiated by Landlord, completed by Tenant

· Initiated by Tenant, completed by Landlord

· System able to match individual applications automatically and a manual process is available

· Landlords able to apply & upload more than one property address and tenant

5. Data Security

· Selected Landlord information not visible to Tenant

· Selected Tenant information not visible to Landlord

· All data in motion and data at rest fully encrypted

· Role-based functions and datapoint level access control

· User ability to set/reset password

· Back-end ability to control all levels of access

6. E-sign

· Ability to e-sign compliant with all 50 state’s e-signature regulations

7. Application Processing

· Ability to support up to 300 remote application processors

· Ability to selectively assign applications to processors in bulk

· Ability to assign specific applications to specific processors

· Ability to restrict application processors to view only applications assigned to the processor

· Ability for Managers, Quality Assurance (QA), and other identified personnel to view all applications

· Workflow options

· Ability to support multiple approval workflows

· Standard approval workflow

· QA workflow

· Up to three cure workflows

· Availability to make notes on the applications by different users and able to search comments for keywords

· Track application in different status, including days open and when submitted for each application or matched, touchpoints, and filter by dashboards (depending on status)

· Event log - touchpoints available by review for each application

· Have a timer or deadline for certain statuses and create standard workflows/timelines/milestones for each record

· Ability to create (back end) pop ups or alerts for users when certain criteria is met or not met

8. Non-Functional

· 24x7 availability

· SUB 5-second response time for all screens/interactions

· SOC2 Type 2 certified

· Application design that allows IHDA admins / power users to customize forms and business rules.

9. Reporting

· Ability to report on all application information and status in real-time

· Web-based On-line reporting capability

· Direct database connect capability for 3rd party reporting tools

· Ability to download all reported data sets into 3rd party reporting tools

· Create Standard Reports

· Create Ad-hoc Reports

· Give team members ability to create/export reports on department specific dashboards, views and end user custom pages

· Ability to customize/write (i.e. SQL) customer reporting

· Ability to distribute pre-defined standard/ad-hoc reports to selected lists of e-mail recipients

· Ability to identify applications coming from the same addresses (IP, e-mail and unit address)

· Ability to have a payment system with import and export of data, status, and other pertinent data

· Export feature where all the documents that were uploaded by all parties exported into a zip type like folder, as well as other reports such as FOIA and audits

· Meta data options – field name and descriptions and detailed data dictionary noting all information and relationships

· All fields are reportable

10. Interfaces

· Ability to create pre-defined formatted data extracts or use established Application Programming Interface (APIs) to feed 3rd party systems like Oracle, Encompass, and Wells Fargo (payment process and monitoring including Automated Clearing House (ACH)

· Ability to process pre-defined formatted data imports or use established APIs from 3rd party systems like Oracle, Encompass, and Wells Fargo (payment process and monitoring including ACH)

11. Retention and Archiving

· State maintains ownership of data at all times

· Ability to retain all data and documents for five (5) calendar years after end of program(s)

· Ability to be able to migrate all data within system to IHDA servers

A.2. DESIRED OUTCOMES OF THIS PROJECT/ENGAGEMENT

CBRAP is intended to act as a safety net for litigants who are on the brink of an eviction judgement. Goals of the CBRAP include:

· Help ensure housing stability and prevent homelessness for tenants

· Help tenants avoid an eviction judgment that could significantly limit their ability to secure housing in the future

· Encourage landlord (i.e., housing provider) participation so both parties can reach a mutually beneficial agreement

· Tenants are able to pay back past due rent; and

· Housing Providers recoup money owed to them

· Procure an end-to-end software solution

· A public facing application including:

· Ability to upload documents and view documents that were uploaded

· Application status updates displayed for applicant to see progress of review

· Download of submitted applications with documents

· Direct communication between staff and applicants

· Cloud-based and cross-platform including support

· Multiple language support, minimum English and Spanish

· Internal application review including:

· Pipeline management and application assignment

· Multiple milestones and workflows

· Application linked notes log

· Audit tracking

· Post approval and grant payment management

· Generate payment requests through check or ACH

· Payment tracking

· Robust reporting abilities including:

· Ability to extract all application and review data fields

· Data extraction for or integration to Oracle financial systems

· Built in data report building or integration to Power BI

· Support for multiple user roles and permissions both internal and external

· Internal administrative rights to:

· Add, remove or edit user roles/permissions

· Open or close the portal (prevent new application submissions)

· Edit/update application questions

· Access a test environment before changes are deployed to live environment

· Offer user-friendly tools that allows tenants at risk of eviction to easily apply, including uploading necessary documents, for assistance to avoid eviction.

· Offer a way to keep applicants updated about the status of their application as it progresses through review.

· To raise approval numbers through ease of reviewing applications and information available via dashboards.

· Reduce call center volume with more/better information available and simplified application process for both Tenant and Landlord.

· To easily adjust the application and submission portal as needed, through application field editability and ability to activate or deactivate the portal to new application submissions.

· To have a unified software solution that covers end-to-end from application submission through post-approval management and grant payment.

· Use reporting to identify problems, trends and drill down into the data to find ways to improve future iterations of the program.

A.3. SCHEDULE & BUDGET

Below is a general timeline outlining the process steps with estimated dates for each step of the procurement process. All dates listed below are subject to change at the sole discretion of IHDA.

Task
Completion Date
Pre-Submission Conference
September 2025
Due Date for Proposals
October 2025
Vendor Demonstrations
November 2025
Notice of Award Publication
December 2025 (Please note: Award remains subject to approval of the Board Members of the Authority at the December 2025 Board Meeting)
IHDA Board Meeting
December 2025
Contract Start Date
February 2026 (Dependent on length of contracting process)
Go-Live
July 2026

A.4. TERM

A.4.1. TERM OF THIS CONTRACT: The contract resulting from this procurement will have an initial term commencing upon the last dated signature of the Parties and for a two (2) year contract term. In no event will the total term of the contract, including the initial term, any renewal terms, and any extensions, exceed ten (10) years. Vendor shall not commence billable work in furtherance of the contract prior to final execution of the contract except when permitted pursuant to 30 ILCS 500/20-80.

A.4.2. RENEWAL: Subject to the maximum total term identified above, the State has the option to renew for the following term(s):

· Renewal #1: Two (2) Years

· Renewal #2: Two (2) Years

· Renewal #3: Two (2) Years

· Renewal #4: Two (2) Years

A.4.2.1. Pricing for the renewal term(s), or the formula for determining price, is in the Pricing section of this solicitation.

A.4.2.2. Any renewal of the resulting contract is subject to the same terms and conditions that apply to the initial term of the contract unless otherwise provided. The State may renew the contract for any or all of the option periods specified, may exercise any of the renewal options early, and may exercise more than one option at a time based on continuing need and favorable market conditions, when in the best interest of the State. The contract may neither renew automatically nor renew solely at the Vendor’s option.

Section B. CURRENT CONDITIONS

B.1. OVERVIEW & BACKGROUND

IHDA is currently using two applications with one for the front-end and one for the back-end payment processing. The back-end application processes daily imports of data from the front-end system. We are able to pull reporting from both applications with limitations. There is a separate export process from the back-end application to process payments.

B.2. VOLUMES & QUANTITIES

•Ability to support 300 concurrent, active application processors, QA, and cure personnel
•Ability to support 5,000 concurrent, active users entering applications into the system

B.3. AREAS OF CONCERN/CHALLENGES

•Payment process and different options including tracking
•Timeline of files (status, changes, updates, deadlines) able to give alarms/alerts for each app on dates and criteria
•File size and types for uploads
•Support and backup for any issues or crashes of platform.

Section C. PROPOSAL REQUIREMENTS Only Electronic Submissions through BidBuy of Offers will be Accepted

C.1. REQUIRED DOCUMENTS TO COMPLETE AND SUBMIT

The Offeror shall submit the listed documents in BidBuy under the Attachments tab in the appropriate “Required Attachments” spaces.

· Vendor Disclosure or IPG Active Registered Vendor Disclosure

· Technical response

· Offer to the State of Illinois Information and Technology

· Commitment to Diversity

· Pricing Blank documents may be found on the Chief Procurement Officer for General Service’s website at https://cpo-general.illinois.gov/solicitation-and-contract-templates.html and on the BidBuy posting under “File Attachments:”. Business Enterprise Program/Veterans Small Business Program Utilization Plan may be downloaded from the Commission on Equity and Inclusion’s website at https://cei.illinois.gov/purchasing-entity-resources/compliance.html.

Failure to submit Vendor Disclosure or IPG Active Registered Vendor Disclosure, as applicable, and the Utilization Plan(s), as applicable, with the Offer submitted in BidBuy shall render the Offer non-responsive.

Offerors are required to submit their response to the State’s solicitation through BidBuy. Any information sent to the State outside of BidBuy, for example by US Mail, FedEx, UPS, e-mail, or hand delivery, will neither be accepted nor considered. Offeror submissions will only be considered if they are received through BidBuy and on or before the time and date indicated as the “Bid Opening Date” on the BidBuy posting. Any required attachments must be submitted via BidBuy.

Price entries on the Items tab will be locked automatically upon submission of the quote. Entering cost, pricing or discount information in the Alternate Description may result in disqualification. If the agency requires pricing to be submitted in an attachment, Offeror shall upload pricing under the “Required Documents” section on the Attachments tab and check the box “Does the attachment contain any pricing, cost or discount information?”. Failure to check this box allows your pricing to be viewed when bids are opened and will result in disqualification of your offer. NOTE: Do not check “Does the attachment contain any pricing, cost or discount information” if the attachment does NOT include pricing, cost, or discount information.

Documents shall be submitted in an electronic format that is accessible and readable using Microsoft Office suite software or Adobe Reader. Corrupted files shall not be considered. It is the Offeror’s responsibility to check that files are accessible and legible after uploading.

The Offeror is solely responsible for ensuring timely submission of their electronic solicitation response. Failure to allow adequate time prior to the Bid Opening Date to complete and submit a response to a solicitation, particularly in the event technical support assistance from the State is required, places the Offeror and their offer or response at risk of not being accepted.

The State encourages the Offeror to ensure that their BidBuy account is up-to-date. It is recommended that you access your BidBuy account prior to the solicitation due date and time to make sure that your company’s information is up-to-date and your password is current. Files may be uploaded at any time prior to submission.

File size may impact the uploading and downloading speed and may lead to browser time-outs, resulting in failed upload/download attempts. Please consider this dependency when attaching very large documents.

OFFEROR INSTRUCTIONS TO SUBMIT IN BIDBUY

Create Quote:

General Tab
: Save and Continue
Items Tab
Follow instructions in the Pricing section of the solicitation document as to whether pricing will be entered in the Unit Cost of the Items Tab or submitted as a separate Pricing Document in the Attachments Tab.

Note: any pricing entered in the Unit Cost of the Items Tab will be locked until after Technical Evaluations take place. Do not enter cost, pricing, or any discount information in the Alternate Description field. Entering cost, pricing or discount information in the Alternate Description may result in disqualification.

Terms and Conditions Tab
: Select “Yes”, “No”, or “Yes with Exceptions”

Note: If taking any exceptions to Standard Terms and Conditions an offeror must submit a redline version of the Standard Terms and Conditions with their proposal.

Attachments Tab
For each required quote attachment listed:

: “Upload” (next to each required attachment) : “Choose File” Note: If a pricing document is required, mark the box next to the question, “Does this attachment contain any pricing, cost, or discount information?”

Failure to mark this box when attaching a pricing document will result in disqualification.

Check this box ONLY if a separate pricing document is required.

Do NOT check this box for any other required quote attachment such as the Technical Proposal, Vendor Disclosure / IPG Active Registered Vendor Disclosure, or Utilization Plan(s), or Offer.

Summary Tab
: “Submit Quote”

Offerors may also view the “Request for Proposal (RFP) Vendor Submission Instructions Video found at https://cpo-general.illinois.gov/vendor-resources.html

C.2. DUE DATE AND TIME FOR SUBMISSION OF OFFERS

Each solicitation contains the Offer due date and time, appearing as the “Bid Opening Date:” on the BidBuy posting. Offeror shall submit Offers in BidBuy, and the State shall open Offers electronically in BidBuy on the “Bid Opening Date”. The Offer must remain firm for 180 days from opening.

C.3. CONFLICT BETWEEN INFORMATION IN ELECTRONIC DOCUMENTS AND ON BIDBUY

If the State provides information in electronic documents (i.e., the RFP and other attachments) that is different or in conflict with the information the State provides on BidBuy, then the information in electronic documents is presumed to represent the State’s intent. If the Offeror provides information in electronic documents that is different or in conflict with the information the Offeror provides in BidBuy through their Seller Account, then the information in electronic documents shall represent the Offeror’s intended submission.

C.4. PUBLISHED PROCUREMENT INFORMATION

The State publishes procurement information, including solicitations, awards, and amendments, on the Chief Procurement Officer for General Services’ Illinois Procurement Bulletin, known as the Bulletin or BidBuy (https://www.bidbuy.illinois.gov/bso/). Procurement information may not be available in any other form or location. Offeror is responsible for monitoring BidBuy. The State will not be held responsible if Offeror fails to receive the optional e-mail notice of future amendments to the solicitation.

C.5. INFORMATION CONTACT

The individual listed in the “Info Contact:” field on the BidBuy posting shall be the single point of contact for this solicitation. Unless otherwise directed, Offeror should only communicate with the Information Contact. The State/Agency shall not be held responsible for information provided by or to any other person.

Suspected errors should be immediately reported to the Information Contact. Do not discuss, directly or indirectly, the solicitation or any Offer with any State officer or employee other than the Information Contact.

C.6. OFFEROR QUESTIONS AND AGENCY RESPONSE

All questions, other than questions raised at the Pre-Submission Conference, pertaining to this solicitation must be submitted in writing to the Information Contact no later than September 22, 2025. Questions received and Agency responses may be posted as a Bid Amendment to the original solicitation on BidBuy; only these posted answers to questions shall be binding on the State. Offeror is responsible for monitoring BidBuy and BidBuy email notifications.

C.7. PRE-SUBMISSION CONFERENCE

The Agency may conduct a Mandatory or Non-Mandatory Pre-Submission Conference, listed in the “Pre-Bid Conference:” field of the BidBuy posting. Please refer to BidBuy for this information.

If attendance is mandatory, Offeror (current contractor included) will be disqualified and considered non-responsive if Offeror does not attend, is not on time, leaves early, or fails to sign the attendance sheet. Offeror must allow adequate time to accommodate security screenings at the site.

Microsoft Teams Need help?

Join the meeting now Meeting ID: 287 014 234 031 Passcode: qG2BE23U

Dial in by phone +1 872-267-6689,,823256744# United States, Chicago Find a local number Phone conference ID: 823 256 744#

C.8. SMALL BUSINESS SET-ASIDE

In the Bulletin posting, if “Yes” is shown to the question “Is this a Small Business Set-Aside Procurement?”, then Offeror must be registered by the Illinois Small Business Set-Aside Program at the time Offers are due for the Offer to be evaluated. For requirements on qualifying Offeror’s business in the Small Business Set-Aside Program, please go to the Chief Procurement Office for General Service’s website at https://cpo-general.illinois.gov/sell-2-illinois.html .

C.9. SECURITY

Bid/Performance Bond: $N/A. If a bond is required, Offeror must submit the Bid Bond with your offer or Performance Bond to the Information Contact within ten (10) days after contract execution. The bond must be from a surety licensed to do business in Illinois. An irrevocable letter of credit is an acceptable substitute. The form of security must be acceptable to the State.

C.10. TERMS AND CONDITIONS

Information and Technology Standard Terms and Conditions will become a part of any resulting contract. To view the Information and Technology Standard Terms and Conditions, please go to https://cpo-general.illinois.gov/solicitation-and-contract-templates.html.

Section D. EVALUATION PROCEDURES

D.1. EVALUATION PROCESS

The State assesses each Offer for Responsibility (E.10) and Responsiveness. The State considers the information provided and the quality of that information when assessing Offers. If the State finds a failure or deficiency, the State may reject the Offer or reflect the failure or deficiency in the assessment.

There are three scored parts to each proposal – technical, commitment to diversity, and pricing. Each part of the proposal is evaluated and ranked independently of the other parts of the proposal. The results of the evaluation of all three parts shall be used in ranking the proposals.

The State may award to the most responsive and responsible offeror whose offer best meets the specified criteria.

D.2. RESPONSIVENESS

A responsive offeror is one who submits an offer that conforms in all material respects to the Request for Proposal and includes all required forms.

D.2.1. The State will determine whether the Offeror complied with the instructions for submitting offers. Except for late submissions, and other requirements that by law must be part of the submission, the State may require that an Offeror correct deficiencies as a condition of further evaluation.

D.2.2. Subcontractor Disclosure: If the Offer includes any subcontractors, then Offeror shall complete the Subcontractor Disclosure section of the Offer to the State of Illinois.

D.2.3. If completing IPG Active Registered Vendor Disclosure, then responsiveness may include and may not be limited to:

· Active Illinois Procurement Gateway registration # with expiration date

· Certifications timely to this solicitation

· Disclosure of lobbyists for Offeror and parent entity(ies)

· Disclosure of pending and current contracts

D.2.4. If completing Vendor Disclosure, required parts may include and may not be limited to:

•Business and Directory Information: Offeror should complete and return the Business and Directory Information form in Vendor Disclosure, Part 1.
•Illinois Department of Human Rights (IDHR) Public Contracts Number: Offeror shall complete and return the IDHR Public Contracts Number form in Vendor Disclosure, Part 2.
•Authorized to Transact Business or Conduct Affairs in Illinois: A person (other than an individual acting as a sole proprietor) must be a duly constituted legal entity prior to submitting an Offer and authorized to transact business or conduct affairs in Illinois prior to execution of the contract. For more information, see Authorized to Transact Business or Conduct Affairs in Illinois in Vendor Disclosure, Part 3.
•Standard Illinois Certifications: Offeror shall complete and return the Standard Illinois Certifications form in Vendor Disclosure, Part 4.
•State Board of Elections Registration: Offeror may be prohibited from making political contributions and be required to register with the State Board of Elections. For more information, see State Board of Elections in Vendor Disclosure, Part 5.
•Disclosure of Business Operations with Iran: Offeror should complete and return the Disclosure of Business Operations with Iran form in Vendor Disclosure, Part 6.
•Financial Disclosures and Conflicts of Interest: Offeror shall complete and return the Financial Disclosures and Conflicts of Interest form in Vendor Disclosure, Part 7.
•Taxpayer Identification Number: Offeror should complete and return the Taxpayer Identification form in Vendor Disclosure, Part 8.

D.2.5. The State will determine whether the Offer meets the stated Technical requirements. Minor differences or deviations that have negligible impact on the price or suitability of the supply or service to meet the State’s needs may be accepted or corrections allowed. If no offeror meets a particular Technical requirement, the State may waive that requirement.

D.2.6. When the specification calls for “Brand Name or Equal,” the brand name product is acceptable. Other products will be considered with proof that the other product meets stated specifications and is equivalent to the brand product in terms of quality, performance, and desired characteristics.

D.3. EVALUATION METHODOLOGY

The Technical Requirements are described in Sections F.2., F.3., F.5, and F.6. The State evaluates the Technical Requirements without consideration of price.

D.3.1. Total Number of Points Available for Technical Requirements is: 575.

D.3.2. Offeror shall complete and return Sections F.2., F.3.

D.3.3. Relative Weight in Point Format

Technical Requirements
Points Available
Mandatory Requirements with Evidence
0; all must be met and are evaluated as pass or fail
Proposed Technical Solution (Desirable elements)
575
Demonstration
100

D.4. COMMITMENT TO DIVERSITY ELEMENTS

Sections 20-15 and 35-30 of the Illinois Procurement Code (30 ILCS 500/) require offerors to be evaluated on their commitment to diversity. The points available for Commitment to Diversity are described in Section F.4. and are equivalent to 20% of the Technical Requirements points. The State evaluates Commitment to Diversity without consideration of price.

D.4.1. The total number of points for Commitment to Diversity is 135.

D.4.2. Offeror shall complete and return Section F.4 Commitment to Diversity

D.4.3. Commitment to Diversity Categories: The percentages at the end of each section reflect the weighted distribution of points available identified in D.4.1.

Commitment to Diversity Categories

Category 1 – BEP Compliance - Whether the Offeror meets the set goal for contracting or subcontracting with businesses owned by women, minorities, or persons with disabilities or completed a Good Faith Effort Waiver for this procurement. 5%

Category 2 – Subcontracting/Contracting with any WMD businesses (not limited to BEP vendors) - Whether the Offeror has contracted/subcontracted within the prior calendar year with businesses owned by women, minorities, or persons with disabilities. 10%

Category 3 – Diversity, Equity and Inclusion (DEI) Spend – Offeror’s percentage of business, education and/or community spend from prior calendar year gross revenue that involves businesses owned by women, minorities and/or persons with disabilities. The assisted businesses are not required to be certified in the Illinois Business Enterprise Program. 20%

Category 4 – DEI Time - Offeror’s hours spent in the prior calendar year on promoting DEI in the workplace, the community, education institutes, or supporting businesses owned by women, minorities, or persons with disabilities. The assisted business is not required to be certified in the Illinois Business Enterprise Program. The success or failure of each event does not impact the points achieved. The event may be voluntary or paid time. 20%

Category 5 – DEI Policies - Entity has provided a written copy of, or link to, their current written workforce diversity, equity, and inclusion policy. Policies must be actionable plans, not overarching concepts around DEI. 10%

Category 6 – Diversity in Staffing - % of individuals on governing board and/ or Senior executives who identify as women, minorities or person with disabilities. 10% % of individuals in management /supervisor positions who identify as women, minorities or person with disabilities. 13% % of total staff who identify as women, minorities or person with disabilities. 12%

D.5. PRICE

The State opens Price proposals after evaluating all Technical and Commitment to Diversity proposals.

If the State does not consider the price to be fair and reasonable and negotiations fail to meet an acceptable price, the State reserves the right to cancel the award and take appropriate action to meet the needs of the State. The State determines whether the price is fair and reasonable by considering the offer, including the offeror's qualifications, the offeror's reputation, all price proposals submitted, other known prices, the project budget, and other relevant factors.

D.5.1. The total number of points for Price is 162.

D.5.2. The State will determine Price points using the following formula:

Maximum Price Points X (Lowest Price/Offeror’s Price) = Total Price Points

D.6. MAXIMUM AVAILABLE POINTS

The maximum number of points is 575 (Technical) + 135 (Commitment to Diversity) + 100 (Vendor Demonstration) + 162 (Price) = 972 maximum available points.

Section E. ADMINISTRATIVE REQUIREMENTS

E.1. GOVERNING LAW AND FORUM

Illinois law and rules govern this solicitation and any resulting contract. Offeror must bring any action relating to this solicitation or any resulting contract in the appropriate court in Illinois. This document contains statutory references designated with “ILCS”. To view the full text, go to https://ilga.gov/Legislation/ILCS/Chapters . The Illinois Procurement Code (30 ILCS 500) and the Standard Procurement Rules (44 ILL. ADM. CODE PART 1) are applicable to this solicitation. To view them respectively, go to and Illinois General Assembly - ADMINISTRATIVE CODE.

E.2. PUBLIC RECORDS AND REQUESTS FOR CONFIDENTIAL TREATMENT

Offers become the property of the State. All offers will be open to the public under the Illinois Freedom of Information Act (FOIA) (5 ILCS 140) and other applicable laws and rules, unless Offeror requests in its Offer that the State treat certain information as confidential. A request for confidential treatment will not supersede the State’s legal obligations under FOIA. The State will not honor requests to keep entire Offers confidential. Offerors must show the specific grounds in FOIA or other law or rule that support confidential treatment. Regardless, the State will disclose the successful Offeror’s name, the substance of the Offer, and the price.

If Offeror requests confidential treatment, Offeror must submit additional copy/copies (see Instructions for Submission of Offers in Section C.) of the Offer with proposed confidential information redacted. This redacted copy must tell the general nature of the material removed and shall retain as much of the Offer as possible. In a separate attachment, Offeror shall supply a listing of the provisions identified by section number for which it seeks confidential treatment and identify the statutory basis or bases under Illinois law, including a detailed justification for exempting the information from public disclosure.

Offeror will hold harmless and indemnify the State for all costs or damages associated with the State defending Offeror’s request for confidential treatment. Offeror agrees that the State may copy the Offer to facilitate evaluation, or to respond to requests for public records. Offeror warrants that such copying will not violate the rights of any third party.

E.3. MINORITY CONTRACTOR INITIATIVE

The State requires a fee of $15 to cover expenses related to the administration of the Minority Contractor Opportunity Initiative. Any offeror awarded a contract of $1,000 or more under Section 20-10, 20-15, 20-25 or 20-30 of the Illinois Procurement Code (30 ILCS 500) is required to pay a fee of $15. The Comptroller shall deduct the fee from the first check issued to the Vendor under the contract and deposit the fee in the Comptroller’s Administrative Fund. 15 ILCS 405/23.9.

E.4. FEDERAL FUNDS

The resulting contract may be partially or totally funded with Federal funds. Upon notice of intent to award, the percentage of supplies and/or services involved that are Federally funded and the dollar amount of such Federal funds will be disclosed.

E.5. EMPLOYMENT TAX CREDIT

Offerors who hire qualified veterans and certain ex-offenders may be eligible for tax credits. 30 ILCS 500/45-67 and 45-70. Please contact the Illinois Department of Revenue (217-524-4772) for information about tax credits [35 ILCS 5/216, 5/217].

E.6. RESERVATIONS

Offeror must read and understand the solicitation and tailor the Offer and all activities to ensure compliance. The State reserves the right to amend the solicitation, reject any or all offers, award by item/services, group of items/services, or grand total, and waive minor defects. The State may request a clarification, inspect Offeror’s premises, interview staff, request a presentation, or otherwise verify the contents of the Offer, including information about subcontractors and suppliers. The State may request Best & Final Offers when appropriate. The State will make all decisions on compliance, evaluation, and terms and conditions, and shall make decisions in the best interests of the State and in accordance with the Illinois Procurement Code, rules and other applicable State and Federal statutes and regulations. This competitive process may require that Offeror provide additional information and otherwise cooperate with the State. If an offeror does not comply with requests for information and cooperate, the State may reject the offer as non-responsive to the solicitation. Submitting an offer does not entitle Offeror to an award or a contract. Posting a vendor’s name in a Bulletin notice does not entitle the vendor to a contract. The State is not responsible for and will not pay any costs associated with the preparation and submission of any offer.

Awarded Offeror(s) shall not commence and will not be paid for any billable work undertaken prior to the date all parties execute the contract, unless approved in writing in advance by the State Purchasing Officer or the Chief Procurement Officer (or designee).

E.7. AWARD

The State is not obligated to award a contract pursuant to this solicitation. If the State issues an award, the award will be made to the responsive and responsible offeror whose offer best meets the specified criteria unless otherwise permitted by the Illinois Procurement Code and Illinois Administrative Code. However, if the State does not consider the price to be fair and reasonable and negotiations fail to meet an acceptable price, then the State reserves the right to cancel the award and take appropriate action to meet the needs of the State. The State will determine whether the price is fair and reasonable by considering the offer, including the offeror's qualifications, the offeror's reputation, all prices submitted, other known prices, the project budget and other relevant factors. The State will post a notice to the Bulletin identifying the apparent most responsive and responsible offeror.

E.8. INVOICING ADDRESS

The awarded Vendor shall invoice at the completion of the contract unless invoicing is tied in the contract to milestones, deliverables, or other invoicing requirements agreed to in the contract. The Bulletin posting contains the “Bill-to Address:” where invoices should be sent.

Vendor shall not bill for any taxes unless accompanied by proof that the State is subject to the tax. If necessary, Vendor may request the applicable Agency’s Illinois tax exemption number and Federal tax exemption information.

E.9. PROTEST REVIEW OFFICE

Offeror may submit a written protest to the Protest Review Office following the requirements of the Standard Procurement Rules. 44 ILL. ADM. CODE 1.5550. For protests related to specifications, the Protest Review Office must physically receive the protest no later than fourteen (14) days after the solicitation or related addendum was posted to the Bulletin. For protests related to rejection of individual proposals or awards, the protest must be received by close of business no later than fourteen (14) days after the protesting party knows or should have known of the facts giving rise to the protest. The Protest Review Office’s information is as follows:

Chief Procurement Office Attn: Protest Review Office Email: cpogs.pro@illinois.gov

E.10. RESPONSIBILITY

A responsible Offeror is one who has the capability in all respects to perform fully the contract requirements and who has the integrity and reliability that will assure good faith performance. The State determines whether the Offeror is a “responsible” offeror; an offeror with whom the State can or should do business. For example, the State may consider the following:

E.10.1. A “prohibited bidder” includes any person assisting an employee of the State of Illinois by reviewing, drafting, directing, or preparing any invitation for bids, a request for proposal, or request of information, or providing similar assistance unless such assistance was part of a publicly issued opportunity to review drafts of all or part of these documents. For purposes of this section, an employee of the State of Illinois means one who, by the nature of his or her duties, has the authority to participate personally and substantially in the decision to award a State contract. No person or business shall submit specifications to a State agency unless requested to do so by an employee of the State. No person or business that contracts with a State agency to write specifications for a particular procurement need shall submit a bid or proposal or receive a contract for that procurement need.

Nothing herein is intended to prohibit a vendor from bidding or offering to supply developing technology, supplies or services after providing the State with a demonstration of the developing technology, supplies, or services; provided the subject of the demonstration to the State represents industry trends and innovation and is not specifically designed to meet the State's needs. Nothing herein is intended to prohibit a person or business from submitting a bid or offer or entering into a contract if the person or business: (i) initiates a communication with an employee to provide general information about products, services, or industry best practices and, if applicable, that communication is documented in accordance with Section 50-39 of the Illinois Procurement Code or (ii) responds to a communication initiated by an employee of the State for the purposes of providing information to evaluate new products, trends, services, or technologies.

E.10.2. Other factors that the State may use to evaluate to determine responsibility include, but are not limited to: political contributions, certifications, conflict of interest, financial disclosures, taxpayer identification number, past performance in business or industry, references (including those found outside the Offer), compliance with applicable laws, financial responsibility, insurability, effective equal opportunity compliance, payment of prevailing wages if required by law, capacity to produce or sources of supply, and the ability to provide required maintenance service or other matters relating to the offeror’s ability to deliver in the quality and quantity within the time and price as specified in this solicitation.

E.10.3. Awarded offerors must always have financial resources sufficient, in the opinion of the State, to ensure performance of the contract and must provide proof upon request. The State may require a performance bond if, in the opinion of the State, it ensures performance of the contract. The State may terminate the contract, consistent with the termination for cause provision of the contract, if the vendor lacks the financial resources to perform under the contract.

E.10.4. The State may require that an offeror correct any deficiencies as a condition of further evaluation.

E.11. BidBuy Terminology and Guidance: BidBuy is an online e-procurement system. There may be some difference between the procurement terminology used in this solicitation and the terms used in BidBuy. Please learn more about BidBuy by accessing the online resources found here:

https://www2.illinois.gov/cpo/PathwayToProcurement/Pages/Guides-and-Manuals.aspx

Section F. PROPOSAL FORMS Offeror must complete and return:

· The following three (3) tables include: Contract Requirements (Section F.1), and Technical Requirements: Mandatory Requirements with Evidence (Section F.2), and Proposed Technical Solution (Section F.3)

· Commitment to Diversity (Section F.4)

· Offer to the State of Illinois Information and Technology Please read and follow each instruction carefully.

F.1. CONTRACT REQUIREMENTS

Please read each contract requirement carefully in F.1. These contract requirements shall be included in any contract resulting from this solicitation.

CONTRACT REQUIREMENTS

F.1.1. All web application screens that contain Confidential Information must be non-cacheable.
|_| Agree

F.1.2. Authority system data must not appear in URLs.

|_| Agree

F.1.3. Confidential information must not be stored on any server/system/error logs.

|_| Agree

F.1.4. The Vendor must keep private keys confidential, implement key lifecycle management, and protect all keys in storage or in transit.

|_| Agree

F.1.5. Vendor must provide data dictionary for reporting and custom development.

|_| Agree

F.1.6. Vendor must provide ability to integrate to/from the Authority’s systems as needed (via API, XML, etc.).

|_| Agree

F.1.7. Vendor must commit to compliance with relevant regulations related to personally identifiable information including 305 ILCS 5/11-9 and 5 ILCS 140/7(1)(b). .
|_| Agree

F.1.8. For HTTP and other protocols that use SSL/TLS, Vendor shall use the TLS 1.2 or later protocol with 128-bit or larger key size and shall make previous protocols and smaller keys unavailable.

|_| Agree

F.1.9. Web applications must be available only over Transport Layer Security (“TLS”). Attempts to use the Application without encryption shall be rejected. Encrypted and non-encrypted content shall not be mixed.

|_| Agree

F.1.10. All systems must encrypt all Authority data at rest and in-flight using algorithms and key lengths consistent with the most recent National Institute of Standards and Technology (NIST) guidelines.

|_| Agree

F.1.11. Solution must be e-sign compliant with all 50 state’s e-signature regulations.
|_| Agree
F.1.12. Solution must have real-time address validation functionality (auto lookup/fill of USPS address).
|_| Agree
F.1.13. Data management must include the ability to validate format and content of pre-defined data types.
|_| Agree
F.1.14. Data management must include the ability to support logic on data input screens to collect data based on previously inputted data.
|_| Agree
F.1.15. Data management must have the ability for internal users to be able to access application changes over time.
|_| Agree
F.1.16. Data management must have the ability for bulk uploads/updates to be able to make changes to groups of records.
|_| Agree
F.1.17. System must be able to match individual applications automatically, with a manual process available, if needed.
|_| Agree
F.1.18. Landlords must have the ability to apply and upload more than one (1) property address and tenant.
|_| Agree
F.1.19. Data security must include the ability to make selected Landlord information not visible to the Tenant and selected Tenant information not visible to the Landlord.
|_| Agree
F.1.20. All data in motion and data at rest must be fully encrypted.
|_| Agree
F.1.21. Solution must have role-based functions and datapoint level access control.
|_| Agree
F.1.22. Solution must include User ability to set/reset password.
|_| Agree
F.1.23. Solution must have back-end ability to control all levels of access.
|_| Agree
F.1.24. Solution must be provided as a completely web-based, Software-as-a-Service system.
|_| Agree

F.1.25. Solution cannot have a requirement for any local client software or virtualization software such as Citrix.

|_| Agree

F.1.26. Authority data will not be used or made available through AI models to any other customers.

|_| Agree

F.1.27. All operating systems, servers, storage, and network devices that support Authority Systems or data must be kept hardened, be on currently supported software versions, and be fully patched.
|_| Agree
F.1.28. All critical security-related patches must be installed on systems within 72 hours of their release.
|_| Agree
F.1.29. All non-critical security-related patches must be installed on systems within 30 days of their release.
|_| Agree
F.1.30. Application processing capability must include the ability to support a minimum of 300 remote application processors.
|_| Agree
F.1.31. Application processing capability must include the ability to selective assign applications to processors in bulk and assign specific applications to specific processors.
|_| Agree
F.1.32. Application processing must include the capability to restrict application processors to view only applications and the ability for Managers, Quality Assurance and other identified personnel to view all applications.
|_| Agree
F.1.33. Vendor must have the ability to migrate all data within the system to IHDA servers.
|_| Agree

F.1.34. The system must handle increased load without performance degradation.

|_| Agree

F.1.35. All Vendor systems that are used to host, transfer, or otherwise interact with Authority Systems or data must enforce strict separation from any non-Authority systems. The separation must be auditable and able to be proven at the request of the Authority.
|_| Agree
F.1.36. Solution must have the ability to create pre-defined formatted data extracts or use established Application Programming Interface (APIs) to feed 3rd party systems like Oracle, Encompass and Wells Fargo (payment process and monitoring including Automated Clearing House (ACH).
|_| Agree
F.1.37. Authority data must not be co-mingled with non-Authority data. Data should be segregated by a separate database instance for Authority data.
|_| Agree
F.1.38. Vendor must be able to provide an audit report or log of existing Authority data being migrated into the system. Vendor mut have the ability to test administrative setup of user accounts and configuration settings of the system.
|_| Agree

F.1.39. Vendor must provide the following Access Control:

· Role-Based Access Control (RBAC) – able to define user roles (e.g., admin, manager, employee) with minimal privileges necessary for the job function.

· Multi Factor Authentication (MFA) is required for accessing the system, especially for privileged accounts.

· Single Sign-On (SSO) for seamless and secure authentication across platforms.

|_| Agree

F.1.40. Solution must have a multi-lingual interface with both English and Spanish, have the ability to make basic content edits and have all automated emails be multi-lingual.
|_| Agree
F.1.41. Solution must have the ability to receive custom-defined applications from the public via 100% internet web interface and support for N-1 versions of Firefox, Chrome, Edge and Safari.
|_| Agree
F.1.42. Solution must have the ability to receive custom-defined applications from the public via 100% native mobile interface for iPhone and Android phones.
|_| Agree
F.1.43. Solution must maintain logs of all user activity, including login attempts, data changes and access history.
|_| Agree
F.1.44. Solution must have the ability to report on all application information and status in real-time. All fields must be reportable.
|_| Agree
F.1.45. Solution must have web-based online reporting capability.
|_| Agree
F.1.46. Solution must have direct database connect capability for 3rd party reporting tools and the ability to download all reported data sets into 3rd party reporting tools.
|_| Agree
F.1.47. Solution must have a payment system with import and export of data, status and other pertinent data, using common data formats (e.g., CSV, SQL).
|_| Agree
F.1.48. Solution must have an export feature where all documents that were uploaded by all parties exported into a zip type like folder, as well as other reports such as Freedom of Information Act (FOIA) and audits.
|_| Agree
F.1.49. Solution must have meta data options including field name and descriptions and detailed data dictionary noting all information and relationships.
|_| Agree

By submitting an offer to this solicitation. The offeror agrees that will meet the contract requirements in Section F.1.

F.2. MANDATORY REQUIREMENTS WITH EVIDENCE

Please check “Met” to each of the mandatory requirements for the proposed solution. An Offeror that does not provide substantiating evidence for each requirement will be disqualified and the rest of the proposal will not be scored.

These Mandatory Requirements shall be included in any contract resulting from this solicitation.

Please provide substantiating evidence in your Proposed Technical Solution. Use the column on the right to indicate the section and page number where your evidence/response to each item may be found.

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated .