RFP Exceptions.xlsx
XLSX spreadsheet 89 KB Posted
- Attached to
- STC Managed Cloud Services State and local contract opportunity
- Solicitation number
- 5400028075
- Issued by
- South Carolina
About this file
This document is an Exceptions to Requirements template for a state procurement solicitation involving the State Fiscal Accountability Authority (SFAA). The file provides instructions for potential offerors to document any exceptions they may have to standard terms, conditions, and requirements in the solicitation, with a strong discouragement against taking such exceptions. Offerors are instructed to complete a Microsoft Excel spreadsheet titled "ABC_Exceptions.xlsx" following specific guidelines, including sequentially numbering exceptions, identifying document sections, describing objections, and proposing alternative language using redline formatting.
The procurement document emphasizes that exceptions may negatively impact an offeror's proposal, potentially preventing down-selection for negotiations. The state expects compliance with solicitation requirements as written and wants offerors to price their responses accordingly. Unacceptable exception explanations include referencing negotiations in other contracts, citing internal division needs without valid reasons, indicating terms are "negotiable," or referencing internal company terms and conditions. The final contract terms will be negotiated, but minimum standard terms are already defined in the solicitation documents.
View the file
Other files for this state and local contract opportunity
Show all 33
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Title Page
| Managed Cloud Services |
| Exhibit J.2.1 |
| Exceptions to Requirements |
| Solicitation No. 5400028075 |
Instructions Exhibit J.2.1 (Exceptions to Requirements)
Offeror Name:
Date:
| Offeror Guidelines |
| The contract resulting from this Solicitation falls under the State Fiscal Accountability Authority (SFAA). Offerors are strongly discouraged from taking exceptions to the standard terms and conditions residing in the Solicitation. Any exceptions taken to the standard terms and conditions may result in an Offeror’s proposal not being down-selected for negotiations. |
Offerors should note that the State expects each Offeror to comply with the requirements of this Solicitation as written, and to price its Response accordingly. The State strongly discourages any Offeror from indicating that it does not agree or does not comply with a provision because the Offeror is unwilling to price it (for risk, liability, or any other reason).
The final terms and conditions of any Contract awarded as a result of this Solicitation shall be agreed upon during negotiation. However, the minimum standard terms and conditions that will be included in any awarded Contract are contained in the Solicitation documents.
This section contains the format for Offerors to note any exception to any standard provision, term, or condition specified in the Solicitation. An explanation as to why the Offeror cannot comply with the provision, term, or condition and why the proposed alternative language must be included in the Response. Examples of nonresponsive explanations include:
1. Referencing negotiation of revised language in another statewide or other state agency contract;
2. Referring to an internal division’s need for the revised language without a valid reason as to why the exception is necessary;
3. Indicating the proposed language is “negotiable”; and
4. Referencing an internal Offeror terms and conditions document.
| Instructions to Complete |
| Refer to the Tab named Exceptions: |
| 1) The column labeled # shall be a sequential number. |
| 2) The column labeled Offeror shall include Offeror's three-letter identifier. |
| 3) The column labeled Doc, Offeror shall use the Dropdown: “AttI.4” for Attachment I.4 (Negotiated Terms and Conditions), "Ex2.1.1" for Exhibit 2.1.1 (Managed Cloud Services SOW - State Agencies), "Ex3.0" for Exhibit 3.0 (Performance Model), "Ex4.0" Exhibit 4.0 (Business Model), etc. |
| 4) The column labeled “Section Number" should be used to identify the specific Section within the Solicitation document referenced that the exception language addresses. |
| 5) The column labeled Objection/Issue shall describe the Offeror's issue and/or objection to the term defined in the requirement documents, including the required explanation. |
| 6) The column labeled Proposed Alternative Language (redline) shall be updated as follows: copy the term “as-is” from the associated Solicitation document, use red strikethrough font for any removed text, use blue underlined text for any added text. |
| 7) Offeror shall not modify or remove any of the columns in the template, including the hidden columns. |
| 8) Offeror must provide this as a separate Microsoft Excel document, a file entitled “ABC_Exceptions.xlsx.” in the Proposal response. |
Exhibit J.2.1 (Exceptions to Requirements)
Solicitation No. TBD &P of &N
Exceptions # Offeror ID Doc Section Number Kyle Cox: Include Section Number of the Document at X.Y level (no further than 2 levels)
| Objection/Issue | Proposed Alternative Language (redline) | |
| 1 | 1 | |
| 2 | 2 | |
| 3 | 3 | |
| 4 | 4 | |
| 5 | 5 | |
| 6 | 6 | |
| 7 | 7 | |
| 8 | 8 | |
| 9 | 9 | |
| 10 | 10 | |
| 11 | 11 | |
| 12 | 12 | |
| 13 | 13 | |
| 14 | 14 | |
| 15 | 15 | |
| 16 | 16 | |
| 17 | 17 | |
| 18 | 18 | |
| 19 | 19 | |
| 20 | 20 | |
| 21 | 21 | |
| 22 | 22 | |
| 23 | 23 | |
| 24 | 24 | |
| 25 | 25 | |
| 26 | 26 | |
| 27 | 27 | |
| 28 | 28 | |
| 29 | 29 | |
| 30 | 30 | |
| 31 | 31 | |
| 32 | 32 | |
| 33 | 33 | |
| 34 | 34 | |
| 35 | 35 | |
| 36 | 36 | |
| 37 | 37 | |
| 38 | 38 | |
| 39 | 39 | |
| 40 | 40 | |
| 41 | 41 | |
| 42 | 42 | |
| 43 | 43 | |
| 44 | 44 | |
| 45 | 45 | |
| 46 | 46 | |
| 47 | 47 | |
| 48 | 48 | |
| 49 | 49 | |
| 50 | 50 |
Solicitation No. TBD &P of &N
List
| AttI.4 |
| Ex1.1 |
| Ex1.3 |
| Ex1.4 |
| Ex1.4,AttA |
| Ex1.4,AttB |
| Ex1.4,AttC |
| Ex1.4,AttD |
| Ex2.0 |
| Ex2.1.1 |
| Ex2.1.2 |
| Ex3.0 |
| Ex3.1 |
| Ex3.2 |
| Ex3.3 |
| Ex4.0 |
| Ex4.2 |
| Ex4.3 |
Solicitation No. 5400026039 &P of &N image1.png
File details come from the government source that posted it. Updated .