Addendum No. 1 to RFP No. 26-04_.pdf
PDF 508 KB Posted
- Attached to
- RFP NO. 26-04 | CASE MANAGEMENT SOFTWARE SYSTEM
- Solicitation number
- NO. 26-04
- Issued by
- Los Angeles County, California
About this file
This is Addendum No. 1 to RFP No. 26-04 issued by the Los Angeles Community College District (LACCD) for a Case Management Software System. The addendum clarifies critical submission procedures and technical requirements for vendors responding to the procurement. Key clarifications include: pricing should be based on providing LACCD with an unlimited number of licenses for an estimated population of 267,000 employees and students; the RFP will not utilize Bonfire for document submission despite earlier references, with proposals instead mailed or delivered to 770 Wilshire Boulevard, 6th Floor, Los Angeles, California 90017, Attention Andrea Daniel, by 2:00 p.m. PDT on Monday, April 13, 2026; written questions must be submitted to Andrea Daniel at danielar2@laccd.edu by 2:00 p.m. Pacific Time on Wednesday, March 26, 2026, with responses posted to https://www.laccd.edu/offices/business-services/contract-services/bids-proposals; Exhibits A through K (excluding Exhibit J, which is identified as a duplicate of Exhibit E) must be signed by the proposer's authorized signatory and submitted with the proposal; and Exhibit K has been corrected to identify integral contract provisions addressing term of agreement, FERPA compliance, waiver of damages and indemnity, accessibility requirements, non-discrimination, federally-funded contract requirements, governing law, and board authorization.
The addendum emphasizes that proposals mandating use of a provider's standard services contract rather than LACCD's standard services agreement will be rejected as non-responsive, and that rejection of the identified integral contract provisions will result in proposal disqualification. Proposers must complete Exhibit K to either confirm acceptance of the Cloud Computing Services Agreement without exceptions or deviations, or identify specific exceptions and deviations for District consideration. The contract involves a three-year term with two optional one-year renewal periods, and pricing proposals must include all costs for software licensing, implementation, data migration, training, maintenance, and support services across the five-year period using the corrected cost proposal template (Appendix B). No parking accommodations are provided by the District for proposal submission.
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
RFP Number: 26-04: Case Management Software System Addendum Number: 1
NOTICE TO PROPOSERS: THIS ADDENDUM SHALL BECOME PART OF THE RFP, AND PROPOSERS SHALL ACKNOWLEDGE, IN WRITING, RECEIPT, AND INCORPORATION OF ALL ADDENDA AND CLARIFICATIONS IN THEIR
RESPONSE. FAILURE OF THE PROPOSER TO RECEIVE ADDENDA SHALL NOT RELIEVE THE PROPOSER FROM ANY OBLIGATION UNDER ITS PROPOSAL AS SUBMITTED. THE PROPOSER SHALL IDENTIFY AND LIST IN ITS PROPOSAL ALL
ADDENDA RECEIVED AND INCLUDED IN ITS PROPOSAL; FAILURE TO DO SO MAY BE ASSERTED BY THE DISTRICT AS A
BASIS FOR DETERMINING THE PROPOSAL NON-RESPONSIVE.
To Clarify Specific Sections in the RFP
Number RFP Narrative Clarification
1. ADDITIONAL PRICING INFORMATION FOR
Appendix B-Cost Proposal
The number of licenses needed by LACCD was not identified in the RFP.
APPENDIX B: COST PROPOSAL
All Proposers are required to submit a Cost Proposal using the “Appendix B – Cost Proposal” document. The Proposer is expected to provide pricing for the services requested, as outlined in this RFP.
Please note: Pricing should be based on providing LACCD with an unlimited number of licenses for the requested Case
Management Software System. The District’s estimated population of employees and students is approximately
267,000.
2.
The RFP states that Bonfire will be used for document submission.
This RFP will not utilize Bonfire, so disregard any reference to submitting information/documents via Bonfire.
3. For Section 4.8. Questions about RFP
The RFP notes: Written responses will be posted on the website:
https://laccd.bonfirehub.com/opportunities/private/72 d2e23200b4c744c374bf5cf692e241
For Section 4.8: Questions about RFP
Questions are to be emailed to Andrea Daniel at danielar2@laccd.edu on or before 2:00 p.m. Pacific Time, Wednesday, March 26, 2026. Please include “RFP 26-04 – Questions for Case Management Software System” in the subject line.
Written responses will be posted on LACCD’s website, noted below (not the bonfirehub):
https://www.laccd.edu/offices/business-services/contract-services/bids-proposals
4. This RFP will not utilize Bonfire
For Section 5.2.1: Proposals are to be submitted in 8 1/2” x 11” size, typed in a font size no less than 12, and submitted electronically via Bonfire.
This RFP will not utilize Bonfire
Section 4.2 Proposal Submission Notes:
Proposals are to be enclosed in a sealed package displaying the proposer’s name, California Secretary of State Certificate of registration/Entity File number, and the words: “PROPOSAL
RESPONDING TO RFP 26-04: CASE MANAGEMENT SOFTWARE
SYSTEM".
Mail or deliver proposals to:
Los Angeles Community College District 770 Wilshire Blvd, 6th Floor
Los Angeles, California 90017
ATTN: Andrea Daniel – Procurement Specialist
Proposals must be received by 2:00 p.m. PDT on Monday, April 13, 2026.
5.
Section 4.5. Authorized Signatures
Exhibits A through K (Mandatory documents /
Exhibit J excluded) must all be signed by the Proposer’s authorized signatory and must be submitted by the Proposer electronically via Bonfire. The District is unable to accept any proposal submitted without these statements completed and signed by the Proposer’s authorized signatory.
Exhibits A through K (Exhibit J excluded) must all be signed by the Proposer’s authorized signatory and must be submitted by the Proposer via Mail or delivered to the District to:
770 Wilshire Blvd, 6th Floor
Proposals must be received by 2:00 p.m. PDT on Monday, April 13, 2026.
6. This RFP will not utilize Bonfire
Exhibits A through K (Exhibit J excluded) must all be signed by the Proposer’s authorized signatory and must be submitted by the Proposer electronically via Bonfire. The District is unable to accept any proposal submitted without these statements completed and signed by the Proposer’s authorized signatory.
Exhibits A through K (Exhibit J excluded) must all be signed by the Proposer’s authorized signatory and must be submitted by the Proposer via Mail or delivered to the District to:
770 Wilshire Blvd, 6th Floor
Proposals must be received by 2:00 p.m. PDT on Monday, April 13, 2026.
The District does not provide parking accommodations to proposers submitting proposals.
7. Section 5.4.3 Appendix C – Mandatory Documents to be Submitted in Response:
a) Completed and signed Non-Collusion Affidavit
(Exhibit A)
b) Completed and signed Certificate of Non- Discrimination (Exhibit B)
c) Completed Confidentiality Agreement (Exhibit C)
Section 5.4.3 Appendix C – Mandatory Documents to be
Submitted in Response:
There is one extra document attached to the RFP, so you will not need to complete this document:
Exhibit J is a duplicate of Exhibit E (page 53). This item will not need to be submitted.
d) Acknowledgement of all addenda issued by the District (Exhibit D)
e) Completed and signed Russian
Economic Sanctions Certification
(Exhibit E)
f) Completed and signed Small, Local, Emerging Disabled Veterans (Exhibit
F)
g) Completed and signed Levine Act
Acknowledgment Form (Exhibit G)
h) Bid Protests Procedures (Exhibit H)
i) Verification (Exhibit I)
j) Exceptions and Deviations to the Cloud
Computer Services Agreement (Exhibit K)
8. Exhibit K: Exceptions and Deviations to the
Standard Form Agreement.
Listed below are the integral provisions of the District's contract terms and conditions, several of which are incorrect:
Section 9 – Term of Agreement
Section 12 - Family Educational Rights Privacy Act (FERPA)
Section 18 - Governing Law
Exhibit K (CORRECTED): Exceptions and Deviations to the Standard Form Agreement. Corrected document to read as:
Section 9 – Term of Agreement
Section 12 - Family Educational Rights Privacy Act
(FERPA)
Section 18 – Waiver of Damages; Indemnity Section 20 - Accessibility Requirements
Section 22 - Non-Discrimination
Section 23 - Requirements for Federally-Funded Contracts
Section 20 - Accessibility Requirements
Section 22 - Non-Discrimination Section 23 - Requirements for Federally-
Funded Contracts
Section 38 - Board Authorization
Section 27 – Governing Law
Section 38 - Board Authorization
Please see attached Exhibit K (CORRECTED): Exceptions and Deviations to the Standard Form Agreement to be completed and submitted with your proposal.
Exhibit K (CORRECTED): Exceptions and Deviations to the Standard Form Agreements
A. The Proposer acknowledges it has read and reviewed the Cloud Computing Services Agreement in Exhibit J and attests to the following:
B. Certain exceptions and deviations may deem the proposal non-responsive and result in rejection of the proposal.
1. Proposals that mandate the use of provider standard services contract, rather than utilizing the District’s standard services contract.
2. Proposals that reject the following integral provisions of the District's contract terms and conditions will be treated as a rejection of the District's contract and these proposals will be rejected.
Section 9 – Term of Agreement Section 12 - Family Educational Rights Privacy Act (FERPA) Section 18 - Waiver of Damages Section 20 - Accessibility Requirements Section 22 - Non-Discrimination Section 23 - Requirements for Federally-Funded Contracts Section 27 - Governing Law Section 38 - Board Authorization
In the event that exceptions and deviations to the Cloud Computing Services Agreement are requested after the contract has been awarded, the District may deem the proposal non- responsive and may disqualify the proposal at its discretion.
☐ We have no exceptions or deviations to the Cloud Computing Services Agreement ☐ We have the following or the attached exceptions and/or deviations to the Cloud Computing
Services Agreement
PROPOSER _______
(Type or Print Complete Legal Name of Provider)
By (Signature)
Name (Type or Print)
Title
Address City State Zip
RFP 26-04
File details come from the government source that posted it. Updated .