RFQ 2032H8-24-Q-00037 Amend 00001.pdf
PDF 197 KB Posted
- Solicitation number
- RFQ2032H824Q00037
About this file
This document is a solicitation amendment for Request for Quotation (RFQ) 2032H8-24-Q-00037 from the Internal Revenue Service (IRS) for support in creating a public dataset for the Department of Education's Gainful Employment / Financial Value Transparency (GE/FVT) regulation.
The purpose of this amendment is to provide answers to 9 questions related to the requirement, and to extend the due date for quotations to August 14, 2024 at 12:00 ET. The key details include that the contractor will need to provide support to develop a calculator tool to release datasets with counts and medians broken down by attributes (e.g., college, program) under a common differential privacy budget. The IRS prefers Python-based software and does not allow installation of software on IRS systems. The contractor must provide detailed documentation on the approach, performance, system requirements, testing, inputs/outputs, and configuration. The privatization algorithm must include a formal privacy guarantee, and the IRS is open to tradeoff visualizations between privacy budgets and alternative data privacy methods.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| RFQ 2032H8-24-Q-00037 (7-24-24).pdf |
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
Previous edition unusable STANDARD FORM 30 (REV. 11/2016) Prescribed by GSA FAR (48 CFR) 53.243
AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT
1. CONTRACT ID CODE
PAGE OF PAGES
1 3
Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods:
(a) By completing items 8 and 15, and returning or (c) By separate letter or electronic communication which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by letter or electronic communication, provided each letter or electronic communication makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.
2. AMENDMENT/MODIFICATION NUMBER 3. EFFECTIVE DATE 4. REQUISITION/PURCHASE REQUISITION NUMBER 5. PROJECT NUMBER (If applicable)
7. ADMINISTERED BY (If other than Item 6) CODE
FACILITY CODE
9A. AMENDMENT OF SOLICITATION NUMBER
9B. DATED (SEE ITEM 11)
10A. MODIFICATION OF CONTRACT/ORDER NUMBER
10B. DATED (SEE ITEM 13)
11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS
The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offers is extended. is not extended.
12. ACCOUNTING AND APPROPRIATION DATA (If required) copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;
13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.
IT MODIFIES THE CONTRACT/ORDER NUMBER AS DESCRIBED IN ITEM 14.
CHECK ONE A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT ORDER
NUMBER IN ITEM 10A.
B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation data, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(b).
C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:
D. OTHER (Specify type of modification and authority)
6. ISSUED BY CODE
8. NAME AND ADDRESS OF CONTRACTOR (Number, street, county, State and ZIP Code) (X)
CODE
E. IMPORTANT: Contractor is not is required to sign this document and return copies to the issuing office.
14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)
Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.
2032H8-24-Q-00037
Office of Procurement Operations-Support Contracts Branch 200 W 2nd St Dayton, OH 45402-1443 Attn: Michael Kreacic Tel: Email: michael.d.kreacic@irs.gov
Office of Procurement Operations-Support Contracts Branch 200 W 2nd St Dayton, OH 45402-1443 Attn: Michael Kreacic
15C. DATE SIGNED
15A. NAME AND TITLE OF SIGNER (Type or print)
16C. DATE SIGNED
16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)
15B. CONTRACTOR/OFFEROR
(Signature of person authorized to sign)
16B. UNITED STATES OF AMERICA
(Signature of Contracting Officer)
00001 08/12/2024
The purpose of amendment 00001 is as follows:
1. To provide Answers to Questions 1.
2. To extend the due date and time for quotations until 08/14/2024 12:00 ET.
x x
Office of Research Analysis and Statistics (RAAS) Internal Revenue Service (IRS) Support for Creating a Public Dataset for the Department of Education’s Gainful Employment /
Financial Value Transparency (GE/FVT)
RFQ 2032H8-24-Q-00037
Questions and Answers #1
Question 1:
- How complex is the raw data file from ED and IRS in terms of size, format, and variability?
Answer: ED file will likely range from 7-8 million records (300MB) in a fixed-width format. The IRS file returned to ED will be aggregated statistics and can range from 6,500 to 7,500 (1MB) rows of data in a fixed-width format.
Question 2:
- What is the current state of the IRS\RAAS server, and how much configuration work is anticipated?
Answer: IRS does not allow installation of software on IRS systems. Therefore, preference for software based in open-source language. The IRS preference is is Python.
Question 3:
- Are there existing test cases or benchmarks that the contractor can use to validate the schema and the initial runs of the calculator?
Answer: Yes, there are test cases and benchmarks.
For disclosure reasons, the IRS cannot provide test/benchmark data unless and until the contract awardee has the authority to review confidential information. However, potential vendors can review College Scorecard outputs as published on the College Scorecard website.
Question 4:
- What kind of visualizations for privacy-utility tradeoffs are required, and are there preferred libraries or tools for creating these visualizations?
Answer: The offeror should show the tradeoffs between privacy budgets and the use of alternative data privacy methods. However, IRS is open to additional options.
Question 5:
- What level of detail is expected in the documentation, and are there specific formats or templates that need to be followed?
Answer: At minimum, documentation should outline in detail: approach (on how the approach/algorithmic design is to be applied in order to meet the objective.), performance, system requirements, testing, description of inputs/outputs, configuration files, etc.
Question 6:
- What criteria will be used to evaluate the effectiveness of privatization algorithms?
Answer: Privatization algorithm must include the formal privacy guarantee.
Question 7:
- How much consultation time is anticipated with the COR for post-delivery research?
Answer: This will depend on the interest and inquiries raised as a result of work delivered/output produced.
Question 8:
- We typically host source code on platforms like Github / Gitlab / Azure DevOps / Bitbucket.
Will one of these platforms be used? Also will CI automation be expected to integrate test cases with the calculator?
Answer: Gitlab on IRS server is an option.
Question 9:
- How will the source code be packaged for reuse? For example, some projects require Docker containerization as an image delivery mechanism.
Answer: No specific guidance/preference and not a requirement. Refer to Question 2 for additional context.
| Page[1]: |
| ZZSF30[0]: |
| Page1[0]: |
| Subform_01to13[0]: |
| ZBLK10ASF30[0]: Off |
| ZBLK9ASF30[0]: Off |
| ZBLK11ASF30[0]: Off |
| CheckBox1[0]: Off |
| CheckBox2[0]: Off |
| CheckBox3[0]: Off |
| CheckBox4[0]: Off |
| CheckBox5[0]: Off |
| CheckBox6[0]: Off |
| CheckBox7[0]: Off |
| CheckBox8[0]: Off |
File details come from the government source that posted it. Updated .