QA_JEDI_Solicitation_031518_Response.pdf
PDF 70 KB Posted
- Attached to
- Joint Threat Emitter Enhanced Delivery Initiative (JEDI) Federal contract opportunity
- Solicitation number
- FA8210-18-R-5000
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| QA_JEDI_Solicitation_040918_Response.pdf | ||
| FA821018R5000_______0003.pdf | ||
| FINAL_Pricing_Workbook.xlsx | XLSX spreadsheet | |
| FA821018R5000_______0002.pdf | ||
| Pricing_Workbook.xlsx | XLSX spreadsheet | |
| DD254.pdf | ||
| Section_L_Completed_03-05-18.pdf | ||
| FA821018R5000_______0001.pdf | ||
| QA_JEDI_Solicitation_030518_Response.pdf | ||
| Exhibit_A_CDRLS.pdf | ||
| GFP_Attachment.pdf | ||
| Section_L.pdf | ||
| Sample_Task.pdf | ||
| Special_Packaging_Instructions.pdf | ||
| Section_M.pdf | ||
| FA821018R5000.pdf | ||
| MRL_Users_Guide.xls | XLS spreadsheet | |
| Pricing_Workbook.xlsx | XLSX spreadsheet | |
| Statement_of_Work.pdf | ||
| TechDataPackageRequest.pdf | ||
| MRL_Deskbook.pdf | ||
| TechDataPackageRequest.pdf | ||
| JEDI_DRAFT_RFP_QA.pdf |
Show all 23
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
Section Paragraph Text Comment/Question Government Response
FA821018R5000 Section I Missing FMS clauses As the solicitation includes FMS requirements, shouldn’t the solicitation include FAR 52.227‐9 and DFARS 252.228‐7003?
The FAR clause 52.227‐9 will not be added but DFARS
252.228‐7003 will be added to the Solicitation.
FA821018R5000 Section I FAR 52.219‐9 Small Business (SB) Subcontracting Plan What mix of units should be in the Small Business
Subcontracting Plan?
The SB Subcontracting Plan should be based on the total IDIQ Estimated Maximum of $450M, with the contractor deciding on what mix of Contract Orders may reach that estimate and how that would impact their subcontracting goals.
FA821018R5000 Section I The JEDI Solicitation contains a mix of FAR and DFARS Rights in
Data clauses.
To eliminate conflicting guidance, can FAR 52.227‐14 be eliminated since it conflicts with DFARS 252.227‐7014?
FAR 52.227‐14 has been removed and DFARS 252.227‐
7014 has been retained in the Solicitation.
FA821018R5000 Section I FAR 52.227‐17 RIGHTS IN DATA‐‐SPECIAL WORKS Can FAR 52.227‐17 be removed as the JEDI
Solicitation/Contract will not meet any of the criteria for inclusion listed in 27.405‐1 ‐‐ Special Works.
FAR 52.227‐17 has been removed from the
Solicitation.
Pricing_Workbook.xlsx Labor Category Definitions The Contractor shall employ qualified personnel according to the categories listed in the following table to support modification tasks under this contract.
Would it be acceptable to provide our contractor‐specific
Labor Categories and Rates in lieu of the requested categories?
No, Offerors are to follow the Pricing Workbook instructions and not change the Labor Categories.
FA821018R5000 Security DD254 not included with Solicitation Can the Government provide the DD254 which will be included with the contract so the requirements can be properly assessed?
Yes, the Government has added the DD254 as one of the attachments within Section J as "DoD Contract
Security Classification Specification."
Section L Paragraph 2.20.3 & 4.2 Section L Paragraph 2.20.3 states that each volume shall contain a
“glossary of all abbreviations and acronyms used with a definition for each”. While Section L Paragraph 4.2 Volume Organization lists
“Acronym List and Definitions” and “Glossary”
The first reference describes a “glossary of abbreviations and acronyms used with a definition for each” as a single list. The second reference describes the “Acronym List and definitions” as a list separate from the “glossary”. Do we need to provide two different types of lists?
Section L has been amended to reflect "Acronym List and Definitions on the same line as Glossary in
Paragraph 4.2.
The responses contained in this document represent the Governments current information at the time of posting. The Government reserves the right to change any information through the official release of the RFP.
The Above Questions and Answers (Q&A ‐1) were posted to FBO on 6 March 2018
The Above Questions and Answers (Q&A ‐2) were posted to FBO on 15 March 2018
FA821018R5000 Section I DFARS 252.204‐7012 SAFEGUARDING COVERED DEFENSE
INFORMATION AND CYBER INCIDENT
A check of the solicitation does not identify any Covered
Defense Information (CDI) associated with the program.
Please identify any CDI associated with the program.
Please advise what portions of the solicitation are considered
CDI. Also we need to know what byproducts of the contract will be considered CDI.
The Government TDP is considered Covered Defense
Information (CDI), specifically under the categories
Export Control and Controlled Technical Information, and the TDP is marked accordingly. The JEDI contract may require the development of additional CDI on task orders, and will be marked or otherwise identified on applicable Task/Delivery orders. The DFARS 252.204‐
7012 clause defines CDI as "unclassified controlled technical information or other information, as descried in the Controlled Unclassified Information
(CUI) Registry at http://www.archives.gov/cui/registry/category‐ list.html , that requires safeguarding or dissemination controls pursuant to and consistent with law, regulations, and Governmentwide policies, and is ‐
(1) Marked or otherwise identified in the contract, task order, or delivery order and provided to the contractor by or on behalf of DoD in support of the performance of the contract; or
(2) Collected, developed, received, transmitted, used or stored by or on behalf of the contractor in support of the performance of the contract."
As this is a flexible IDIQ contract, with an ECP CLIN, the
Government cannot feasibly define all CDI that may be created during the period of performance of this contract.
File details come from the government source that posted it.