TSA IV Final RFP Q-As.docx
DOCX document 40 KB Posted
- Attached to
- Training Systems Acquisition (TSA) IV Federal contract opportunity
- Solicitation number
- FA8621-21-R-0030
About this file
This document provides questions and answers regarding the final Request for Proposal for the Training Systems Acquisition IV contract opportunity. Key details include that the solicitation seeks to award multiple ID/IQ contracts to streamline training system acquisition and support processes, with work under the contracts focusing predominantly on sustainment activities such as contractor logistics support, technical support service centers, and software upgrades of existing training systems. The scope also includes courseware development and instruction, as well as development of new training systems. The responding agency is the Department of the Air Force Materiel Command Lifecycle Management Center located at Wright Patterson Air Force Base. Proposal submission dates were updated through Amendment 0001, with Volume III now due May 10, 2021 and the full proposal due May 20, 2021.
View the file
Other files for this federal contract opportunity
Show all 50
Training Systems Acquisition (TSA) IV has more files on GovTribe.
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
TSA IV – FA8621-21-R-0030 - Questions/Answers on RFP Documents
Questions and Answers – RFP Amendment 0001
| Reference |
| Question/Comment |
| Government Response |
| 1. |
| Draft Q&A dated 10 Mar 21 |
L,2.3 Page Size and Format According to the Q&A from March 10th, 2021, the question was asked as to whether Offerors could use Arial Narrow font no smaller than 10-point for tables, charts, graphics, figures, diagrams, and schematics. The Government clarified that “Yes, Arial font may be used for tables, charts, graphs, etc. as long as no smaller than 10-point.”
Section L2.3 was not updated to reflect this. Will the Government please confirm and update section L accordingly, to reflect the use of Arial family of fonts may be used for tables, charts, graphs, etc. as long as no smaller than 10-point?
The Government does not intend to restrict the font style used for tables, charts, graphs, etc. as long as the font size is no smaller than 10-point. No changes are required in Section L.
L, 2.3 states, “Legible tables, charts, graphs, figures, diagrams, and schematics shall be used wherever practicable to depict organizations, systems and layout, implementation schedules, plans, etc. These displays shall be uncomplicated and legible and shall not exceed 11x17 inches in size and shall be counted as two pages. For these displays, the text shall be no smaller than 10-point.” {emphasis added}
| 2. |
| Draft Q&A dated 31 Mar 21 |
L, 2.2.6 According to the Q&A from March 31st, 2021, it was clarified that “the PP volume shall contain the organizational change history and all information generated from the PPI tool (Business Relationships page and contract citations).” The reports do include a header/footer that reads: “Source Selection Information -- See FAR 2.101 and 3.104. For Official Use Only” Section L2.2.6 states all proposal pages shall include the following legend at the bottom of each page:
SOURCE SELECTION INFORMATION
CONTROLLED UNCLASSIFIED INFORMATION
See FAR 3.104 and 2.101 When incorporating the Business Relationship Page and PPI report for the contract citations into our Volume III file, will the Government please confirm Offerors shall use the legend noted in section L2.2.6 and not the header/footer that is generated in the PPI Tool Report?
The header/footer generated from the PPI tool is acceptable, unless the offeror can edit the printout and change “For Official Use Only” to “Controlled Unclassified Information”.
We understand the printouts from the PPI tool may have different headers/footers than the remaining pages for Volume III.
| 3. |
| L, 2.2 |
| Section L.2.2 (the table) states “all Attachments have a 25 page limit,” while Section L.4.2 states “the SEMP will have a 45 page limit and the others have 25 page limits.” Please confirm that the 45-page limit for the SEMP is correct |
| Section L, 2.2 table states the following under the Page Limit column: |
· 25 pages maximum per plan for the CMP, RMP, and QAPP (not included in 30-page Technical Volume maximum)
· 45 pages maximum for the SEMP (not included in 30-page Technical Volume maximum) Section L, 4.2 discusses each attachment (e.g., master plan) individually with page limits. Make sure you are following Section L which was posted as part of the final RFP.
| 4. |
| L, 2.2 |
L, 5.3
| There is a place for Business Relationships and a place for the Past Performance. Yet the table in Section L. 2.2 states that for Volume 3, “20 pages maximum to allow for introductory information, including Business Relationship page”. Section L.5.3 Organizational Change History is required, yet the PPI Tool does not allow for a specific location for it. Is the Organizational Change History included in page count? Should it be included in the Business Relationship page? |
| The Organizational Change history is required as part of Volume III submission. It is not an entry in the PPI tool. The offeror has 20 pages to include all required information: Organizational Change History and all printouts from the PPI tool. |
| 5. |
| L, 2.2 |
| In the ITO on Page 4 Section 2.2 it states Volume III Factor 2 Program Management is 30 Pages Maximum. And the Management Plan is 10 pages maximum. Can the Government please clarify if the Management Plan is excluded from the page count of Volume III? |
| You may be referencing a different ITO other than Section L of the TSA IV RFP. Under TSA IV, Volume III is the PP volume. Volume II is the Technical Acceptability Volume with a 30-page limit. There is no requirement for a Management Plan under TSA IV. |
| 6. |
| L, 2.2.6 |
| All proposal pages shall include the following legend at the bottom of each page: |
SOURCE SELECTION INFORMATION
CONTROLLED UNCLASSIFIED INFORMATION
See FAR 3.104 and 2.101 Can the signed digital copy of the Model Contract in Vol IV be excluded from the marking requirement? The RFP pdf file does not allow for additional header/footer.
Yes, the signed digital copy of the model contract does not require the header/footer markings.
| 7. |
| L, 2.3 |
| The Data Item Description documents for each plan (SEMP, CMP, RMP, QAPP) states that the format shall be selected by the contractor. Can the Government please confirm whether or not the contractor developed plans need to follow the instructions in section L 2.3 Page Size and Format? |
| The offeror may prepare the plans in a format selected by the offeror as long as it remains within the margins, spacing, and font constraints indicated in Section L, 2.3. |
| 8. |
| L, 2.3 |
| Section L 2.3 “Except for the reproduced sections of the proposal request document, the text size shall be no less than 12-point Times New Roman. |
Legible tables, charts, graphs, figures, diagrams, and schematics shall be used wherever practicable to depict organizations, systems and layout, implementation schedules, plans, etc. These displays shall be uncomplicated and legible and shall not exceed 11x17 inches in size and shall be counted as two pages. For these displays, the text shall be no smaller than 10-point” Can offerors use other than Times New Roman font type for tables and graphics?
The Government does not intend to restrict the font style used for tables, charts, graphs, etc. as long as the font size is no smaller than 10-point. No changes are required in Section L.
L, 2.3 states, “Legible tables, charts, graphs, figures, diagrams, and schematics shall be used wherever practicable to depict organizations, systems and layout, implementation schedules, plans, etc. These displays shall be uncomplicated and legible and shall not exceed 11x17 inches in size and shall be counted as two pages. For these displays, the text shall be no smaller than 10-point.” {emphasis added}
| 9. |
| L, 2.3 |
| Section L 2.3: “Except for the reproduced sections of the proposal request document, the text size shall be no less than 12-point Times New Roman.” |
Please confirm that pre-existing documents such as contractor’s comprehensive SBSP are excluded from formatting requirements.
Yes, if an offeror has a pre-existing Comprehensive SBSP, it may be excluded from the formatting requirements; however, if the offeror is preparing a SBSP specifically for TSA IV, that plan must comply with formatting requirements.
| 10. |
| L, 2.3 |
| Section L 2.3: “Legible tables, charts, graphs, figures, diagrams, and schematics shall be used wherever practicable to depict organizations, systems and layout, implementation schedules, plans, etc. These displays shall be uncomplicated and legible and shall not exceed 11x17 inches in size and shall be counted as two pages. For these displays, the text shall be no smaller than 10-point.” |
Can the offerors use 10 pt font for tables and figures titles and action captions?
Yes, as table/figure titles and action captions are considered part of the tables/figures so they may be no smaller than 10-point type.
| 11. |
| L, 2.3 |
| Will the Government allow less than 1"margins on the top/bottom of PDF pages pulled from the PPI tool and then placed into the Past performance volume provided they are legible and fit within the page limits of the volume? |
| Yes, the printouts from the PPI tool are excluded from the margin constraints because these pages cannot be manipulated and the PPI tool does not allow for margin restrictions. |
| 12. |
| L, 2.4 |
| Section 2.4 states, “It is permissible to shorten these file names as long as the Volume number and title, Factor/Subfactor number, and a keyword or phrase is utilized to ensure clarity and consistency.” Section 2.4 further details the file naming conventions of “Executive Summary”, “Technical Acceptability”, “Past Performance”, etc. with no volume number. |
Will the Government please confirm the below file names are acceptable?
· Vol I_Executive Summary
· Vol II_Technical Acceptability
· Vol II_Attachment 1_SEMP
· Vol II_Attachment 2_CMP
· Vol II_Attachment 3_RMP
· Vol II_Attachment 4_QAPP
· Vol III_Past Performance
· Vol IV_Contract Documentation The listed file names are acceptable.
| 13. |
| L, 2.4 |
| Attachment 8, Section L, ITO, Page 8, 2.4 Electronic Offers states: “Offerors may submit their proposal via CD-R/DVD-R or through DoD SAFE (https://safe.apps.mil/) ensuring whichever delivery method is used gets the proposal submitted on the required due date.” |
In order for bidders to create a drop-off for proposal submission via SAFE, they must receive a drop-off request from the Government. This request would be needed twice, for both the past performance and the proposal submission. Will the Government provide a POC for this request?
We recently confirmed that a drop-off code is required for DoD SAFE for non-CAC users. In light of this, we have changed proposal submission requirements to state all volumes must be received via electronic media (CDR/DVD-R).
The logistics required to ensure all offerors request and receive a drop-off code to ensure timely proposal submission presents an unacceptable risk to the Government; therefore all offerors shall submit proposals via CD/DVD and delivered to the address provided in L, 2.5. This includes any offerors who may have CAC access to DoD SAFE.
Section L proposal submission requirements, including an extension of the proposal deadline, have been updated via Amendment 0001.
| 14. |
| L, 2.4 |
L, 2.5 In order to submit proposals in the DOD Safe platform, an authenticated user must first execute the "Request a Drop-Off" procedure to obtain a "Request Code" for external delivery to the non-authenticated user. Passwords are only valid up to 14 days.
When should we expect to receive a Request Code in order to submit Volume III (due 6 May) and the remaining submission due on 17 May?
We recently confirmed that a drop-off code is required for DoD SAFE for non-CAC users. In light of this, we have changed proposal submission requirements to state all volumes must be received via electronic media (CDR/DVD-R).
The logistics required to ensure all offerors request and receive a drop-off code to ensure timely proposal submission presents an unacceptable risk to the Government; therefore all offerors shall submit proposals via CD/DVD and delivered to the address provided in L, 2.5. This includes any offerors who may have CAC access to DoD SAFE.
Section L proposal submission requirements, including an extension of the proposal deadline, have been updated via Amendment 0001.
| 15. |
| L, 2.5 |
| 1. In order to meet the May 6th and May 17th dates, does the Government plan to send out SAFE the Drop-off (upload) codes the day before the deadlines or does each Contractor reach out and request their individual code? |
1. If a SAFE code is time-sensitive, how will the final code be handled, given May 17th is a Monday. Will the time sensitivity be adequate if provided the prior week?
We recently confirmed that a drop-off code is required for DoD SAFE for non-CAC users. In light of this, we have changed proposal submission requirements to state all volumes must be received via electronic media (CDR/DVD-R).
The logistics required to ensure all offerors request and receive a drop-off code to ensure timely proposal submission presents an unacceptable risk to the Government; therefore all offerors shall submit proposals via CD/DVD and delivered to the address provided in L, 2.5. This includes any offerors who may have CAC access to DoD SAFE.
Section L proposal submission requirements, including an extension of the proposal deadline, have been updated via Amendment 0001.
| 16. |
| L, 2.5 |
| Section L2.5 permits Offerors to submit their proposal via the DoD SAFE site. |
Will the Government please advise if there are any limitations when submitting via the DoD SAFE site? For instance, limitations with files size, number of files, etc.
If there are certain limitations, will the Government confirm multiple uploads to submit all proposal volumes and contents is acceptable?
We recently confirmed that a drop-off code is required for DoD SAFE for non-CAC users. In light of this, we have changed proposal submission requirements to state all volumes must be received via electronic media (CDR/DVD-R).
The logistics required to ensure all offerors request and receive a drop-off code to ensure timely proposal submission presents an unacceptable risk to the Government; therefore all offerors shall submit proposals via CD/DVD and delivered to the address provided in L, 2.5. This includes any offerors who may have CAC access to DoD SAFE.
Section L proposal submission requirements, including an extension of the proposal deadline, have been updated via Amendment 0001.
| 17. |
| L, 2.6 |
| Section L.2.6 states Vol III is “due 6 May” and Section L Attachment 9 states on page 7 the “PPQ is due back to Steve Godby and Marcia Hall by May 6,” while Section L.5.1 states they are due back “not later than 17 May.” Please confirm the correct date for Vol III and PPQs. |
| In Amendment 0001, Section L, 2.6 has been updated to reflect a change in requested date of 3:00pm EST 10 May 2021 for the PP volume and Section L, 5.1 and the PPQ (L, Atch 9) have been updated to reflect a due date of 3:00pm EST 20 May 2021 to coincide with a proposal deadline of 3:00pm EST 20 May 2021. |
| 18. |
| L, 2.6 |
| Section L2.6 states “Offerors are requested to submit Volume III, Past Performance by 6 May 2021”, but does not provide a specific time. |
Will the Government please confirm that Volume III Past Performance is also due by 3:00PM EST on May 6th?
In Amendment 0001, Section L, 2.6 has been updated to reflect a change in requested date of 3:00pm EST 10 May 2021 for the PP volume and Section L, 5.1 and the PPQ (L, Atch 9) have been updated to reflect a due date of 3:00pm EST 20 May 2021 to coincide with a proposal deadline of 3:00pm EST 20 May 2021.
| 19. |
| L, 4.1 Proposal Cross Reference Matrix |
| The cross-reference matrix includes a reference to the SOO paragraphs, however Section L 4.1 states “... In this volume, address your proposed processes to meeting the requirements of each Technical subfactor. We are not looking for approaches to everything in the Statement of Objectives (SOO), just a top level process so we can determine that the offeror has the capability to perform TSA IV requirements.” Additionally, the SOO references are deleted from Section L instructions and M and evaluation criteria. |
· Please confirm that the Technical Acceptability Volume should address the offeror’s proposed processes and not approach to accomplishing the SOO tasks.
· If approach to SOO not required, should offerors delete the SOO column from the cross-reference matrix?
· If the SOO column is to be retained, please update to most current SOO paragraph.
Section L, 2.2.3 and the Proposal Cross Reference Matrix (L, Atch 1) have been updated to remove the reference to the SOO via Amendment 0001.
The Technical Acceptability Volume should address what is instructed in Section L.
| 20. |
| L, 4.3.4.b Risk Management |
| "In addition, the offeror shall identify any risk (if any) associated with the proposed processes/approaches for each subfactor and the mitigation the offeror intends to implement to reduce/eliminate these risks." |
The Government removed the sentence (at left) from the Risk Management requirement within Subfactor 4; however, in other areas of Section L (4.3.1, 4.3.2, 4.3.3, and 4.3.4) this same requirement exists. Would the Government confirm whether Offerors are to identify risks associated with the proposed processes for each subfactor and the mitigations the offeror intends to implement to reduce/eliminate these risks within our Technical proposal?
The sentence was removed from L, 4.3.4.b because the requirement is to include self-identified risks for each subfactor. The Government does not want offerors to place self-identified risks in the RMP. The RMP will be a master plan to be applied to each TSA IV task orders. The Government wants the self-identified risks included within the 30-page volume limit.
| 21. |
| L, 5.1 |
| The PPI Tool generates a full-page PDF for this section, but most of the page is blank. Since business relationships on the expected TOs are unknown at this time, please confirm we can use part of this page to explain our overall approach to identifying potential teammates. |
| The offeror may include additional information on the Business Relationships page, if desirable, as long as the PP volume does not exceed the page limitations as stated in Section L, 5.1. |
| 22. |
| L, 5.1 |
| Dates are in conflict for PPQ deadlines. It appears the Government prefers an earlier submission date (May 6) but will accept PPQ submission aligned with the full proposal (May 17). Please confirm we can adjust wording on the PPQ document to be 17 May, providing we alert PPQ recipients of the preferred earlier date. [PPQ document is L., Att. 9.] |
| In Amendment 0001, Section L, 2.6 has been updated to reflect a change in requested date of 3:00pm EST 10 May for the PP volume and Section L, 5.1 and the PPQ (L, Atch 9) have been updated to reflect a due date of 3:00pm EST 20 May 2021 to coincide with a proposal deadline of 3:00pm EST 20 May 2021. |
| 23. |
| L, 5.1 |
| Attachment 8, Section L, ITO, Page 14 states: “Offerors shall send a Past Performance Questionnaire (Section L, Attachment 9) directly to the POCs for the efforts identified.” |
Will the Government consider not requiring Past Performance Questionnaires (PPQs) be sent for efforts in which completed CPARs are available detailing contract performance? Our customers have expressed concerns with the number of PPQs they are fielding and have, in some instances, refused to respond.
PPQs are requested to assist the Government in evaluating the performance on contracts submitted. The PPQ is tailored to the Technical Subfactors to allow the POCs to indicate specifically what the offeror performed on the contract and how well they performed. CPARs are generic in nature and do not include specific information relating to TSA IV.
It is at the offeror’s discretion if and who PPQs are sent to. However, it should be made clear to offerors that if sufficient information is not available to the Government to verify performance on contracts submitted, the offeror is at risk of receiving a Neutral Confidence assessment.
| 24. |
| L, 5.1 |
L, Atch 9
| PPQ due date on Attachment 8, Section L, 5.1 and Attachment 9 PPQ differs. Should questionnaires be returned by May 6 with the PPI submission or on May 17 with the rest of the proposal? |
| In Amendment 0001, Section L, 2.6 has been updated to reflect a change in requested date of 3:00pm EST 10 May for the PP volume and Section L, 5.1 and the PPQ (L, Atch 9) have been updated to reflect a due date of 3:00pm EST 20 May 2021 to coincide with a proposal deadline of 3:00pm EST 20 May 2021. |
| 25. |
| L, 5.1, PPQs |
L, Atch 9 PP Questionnaire Section L5.1 states, “All respondents shall be instructed that all responses are to be provided directly to the Government CO (Steve Godby, steven.godby@us.af.mil) or Contract Specialist (Marcia Hall, marcia.hall@us.af.mil) not later than 17 May 2021.” In Attachment 9, it states, “Email questionnaires to Steve Godby, steven.godby@us.af.mil and Marcia Hall, marcia.hall@us.af.mil NLT 3:00pm EST, 6 May 2021” Will the Government please confirm that while the Past Performance Volume III is required to be submitted by offerors on May 6th NLT 3:00PM EST, the Past Performance Questionnaires can be submitted by the RFP close date of May 17th, 2021, to allow the Offerors’ customers time to complete the questionnaires?
In Amendment 0001, Section L, 2.6 has been updated to reflect a change in requested date of 3:00pm EST 10 May 2021 for the PP volume and Section L, 5.1 and the PPQ (L, Atch 9) have been updated to reflect a due date of 3:00pm EST 20 May 2021 to coincide with a proposal deadline of 3:00pm EST 20 May 2021.
| 26. |
| L, 5.2 |
| Additional list of relevant contracts: “In addition to the three contracts submitted by the offeror, the Government requests a list of contracts the offeror considers to be relevant to TSA IV. This list will aid the Government when searching for additional contracts through the CPAR System. Please provide the contract number and a point of contact for each contract listed. This listing is excluded from the volume page count.” |
Please clarify if the POC requested for these additional contracts are intended to be Government POCs (e.g., program manager, contracting officer) or POCs from the Offeror (e.g., our program manager supporting this work).
The POCs provided should be a Government POC so that the TSA IV team can contact them to verify performance.
| 27. |
| L, 5.2 |
| To verify page count meets requirements, please confirm this list can be placed at the end of the volume (with other material excluded from page count). |
| It is at the offeror’s discretion where they place the list. As stated in L, 5.2, the list is excluded from the volume page count. |
| 28. |
| L, 6.0 |
| Section L of the solicitation, it describes Volume IV as Contract Documentation. In the Chapter 6.1 sections, it skips section "D". Is that intentional? |
| The solicitation/model contract required to be included in Volume VI, Contract Documentation includes Section D. |
The exclusion of Section D reference in Section L, Paragraph 6 was in error. Section L has been updated via RFP Amendment 001 to include a reference to Section D.
| 29. |
| L, 6.1 |
Model Contract/ Representation and Certifications The Offeror is required to provide a signed digital copy of the Model Contract, and Sections A through K. However, the RFP document appears to be password protected.
· Can the Government provide an editable PDF file for completion of this requirement?
The Model Contract is generated from our contract writing system and cannot be manipulated to allow for fill-ins. It is recommended the offeror print those pages needed to be completed and then scan to digital format to include in proposal submission.
| 30. |
| L, 6.1.1 |
| Section A states, “Signature by the offeror on the SF33 constitutes an offer, which the Government may accept. The “original” signed copy should be clearly marked.” |
Since this is not a hard copy submission requiring an original and copy, will the Government please remove “Original” requirement from the SF33 in Vol IV?
The statement, “The “original” signed copy should be clearly marked.” Has been removed from Section L, 6.1.1 via Amendment 0001
| 31. |
| L, 6.1.10, Section J Attachments |
| Can the Government please provide an editable version of form DD254? |
| The Government does not require the offeror to make any changes to the draft DD254. As stated in RFP Atch, 2, Draft DD254, box 9, “This draft RFP DD254 is provided to address the general security requirements to participate in TSA IV.” The DD254 will be completed by the Government with the prospective awardee information at the Final Proposal Revision (FPR) stage of the source selection. |
| 32. |
| L, 6.4 |
| Offerors are advised that contractors will participate as non-Government advisors in the evaluation of proposals. These advisors will sign non-disclosure agreements and will be authorized access to only those portions of the proposal data and discussions that are necessary to enable them to provide specific advice on specialized matters or on particular problems. |
Please clarify, is the government agreeable to contractors pursuing nondisclosure agreements directly with the identified non-government advisors, or does the government require contractors to confirm their awareness of such advisors based upon the established NDA directly between PESystems and the government?
Offerors are required to indicate any objections to the use of non-Government advisors, based upon the established NDA directly between PESystems and the Government, within the Contract Documentation Volume of its proposal. However, if the offeror chooses to pursue an NDA with PESystems, it may do so at its own discretion as long as the offeror complies with L, 6.4 instructions.
| 33. |
| L, 6.5 |
| Will the Government provide small business utilization goal percentages for each socio-economic class for the IDIQ? |
| No, the Government does not have small business goals; it is at the offeror’s discretion to provide its goals for each socio-economic class. Note that the offeror must comply with the 20% small business subcontracting requirement for each task order as stated in TSA IV-H014. |
| 34. |
| L, 6.5 |
| Large business shall submit a SBSP (see FAR 19.701) that contains all the elements required by the clause at FAR 52.219-9, Small Business Subcontracting Plan. The SBSP shall be submitted as part of Volume IV and has no page limit. The SBSP shall include the subcontracting goals expressed at the ID/IQ contract level as a percentage of annual total obligated dollars on awarded task orders for each of the following: small business, veteran-owned small business, service-disabled veteran owned small business, HUBZone small business, small disadvantaged business, and women owned small business. |
The FAR and the Section L instructions state that subcontracting goals expressed at the ID/IQ contract level shall be included as a percentage of annual total obligated dollars on awarded task orders; however, at this time there are no obligated dollars or awarded task orders. Given the multiple award nature of this contract, using the ceiling value for obligated dollars is also not practical or realistic. Would the Government please provide guidance as to the total dollar amount offerors should assume when calculating the goals within our SBSP?
As stated, there are no dollars associated with the ID/IQ, which is why we are requesting offerors provide its subcontracting goals at the ID/IQ level expressed as percentage of annual total obligated dollars. The intent is for the Government to evaluate that the offeror is complying with FAR 52.219-9 expressing subcontracting goals as percentages only. An offeror should be able to state subcontracting goals as percentages it plans to subcontract on an annual basis.
As task orders are competed under the Unrestricted Pool, the offeror will be required to update its SBSP, as well as submit a Small Business Subcontract Commitment Document specific to that task order.
| 35. |
| L, Atch 1, Proposal Cross Reference Matrix |
L4.1 The Proposal Cross Reference Matrix instructions state, “The cross-reference matrix shall reference the Proposal Volume/Paragraph and applicable SOO, Section L, and Section M paragraphs..” and provides the same references that were included in the last Draft RFP, that have since been removed in the Final RFP. Section L4.1 states, “We are not looking for approaches to everything in the Statement of Objectives (SOO), just a top level process so we can determine that the offeror has the capability to perform TSA IV requirements”, which resulted in the removal of the SOO references in the RFP.
Since the SOO references have been removed from the L and M requirements, will the Government please confirm there is no need to include the SOO paragraph column within the Cross References Matrix, and to only include section L and M along with the Proposal Volume/Paragraph columns?
Section L, 2.2.3 and the Proposal Cross Reference Matrix (L, Atch 1) have been updated to remove the reference to the SOO via Amendment 0001.
| 36. |
| L, Atch 1, Proposal Cross Reference Matrix |
| The Proposal Cross Reference Matrix instructions state, “The offeror shall complete a cross-reference matrix which correlates the RFP with the offeror’s proposal for Volume II only.” Attachment 1 also provides a format that outlines the applicable L and M sections (L4.3.1-4.3.4 & M2.1.1-M2.1.4). |
Will the Government please confirm Offerors are to provide a Cross Reference Matrix only for those L and M sections and not for the four master plan instructions that are required within Volume II?
Section L, 2.2.3 and the Proposal Cross Reference Matrix (L, Atch 1) have been updated to remove the reference to the SOO via Amendment 0001.
| 37. |
| L, Atch 1, Proposal Cross Reference Matrix |
| Most SOO requirements have been deleted from Section L. |
L, 4.1 General “… We are not looking for approaches to everything in the Statement of Objectives (SOO), just a top level process so we can determine that the offeror has the capability to perform TSA IV requirements” Attachment 1 Cross reference matrix for Volume II includes a SOO column. Given the statement in L, 4.1 referenced above, should the offer delete the SOO reference column. Please clarify.
Section L, 2.2.3 and the Proposal Cross Reference Matrix (L, Atch 1) have been updated to remove the reference to the SOO via Amendment 0001.
| 38. |
| L, Atch 1, Proposal Cross Reference Matrix |
| Please clarify whether SOO references in SOO Paragraph column are there only as an example of how to present the information or SOO paragraphs represent a suggested mapping of SOO paragraphs to Section L instructions and Section M evaluation criteria. |
| Section L, 2.2.3 and the Proposal Cross Reference Matrix (L, Atch 1) have been updated to remove the reference to the SOO via Amendment 0001. |
| 39. |
| L, Atch 1, Proposal Cross Reference Matrix |
| Section L, Attachment 1 matrix sample references SOO parapragh 12 for Section L.4.3.4.c shall the reference stay as noted? |
| Section L, 2.2.3 and the Proposal Cross Reference Matrix (L, Atch 1) have been updated to remove the reference to the SOO via Amendment 0001. |
| 40. |
| L, Atch 1, Proposal Cross Reference Matrix |
| Most of the Statement of Objectives (SOO) paragraphs referenced in the sample matrix do not appear to be the most applicable SOO section. Will the Government clarify the correct SOO paragraph references for this matrix? |
| Section L, 2.2.3 and the Proposal Cross Reference Matrix (L, Atch 1) have been updated to remove the reference to the SOO via Amendment 0001. |
| 41. |
| L, Atch 2, SEMP DID |
| Section 3.3: “Contain an annotated mapping between contractor and government SE processes. Identify any technical or technical management processes not mapped, including rationale for why they are not needed.” |
Please clarify if annotated mapping between the contractor and Government SE process in the SEMP and the OSEP can be excluded as part of the overall SEMP page count.
The SEMP page count has been increased from the original 25 pages to 45 pages; this should be more than enough page count to prepare the SEMP IAW the DID.
| 42. |
| L, Atch 6, RMP DID |
| The Risk Management Plan instructions include a requirement for a cover and title page that identifies items such as plan date of issue; plan document number/revision number or letter; contract number; contractor name and address, among other items. However, the instructions for the SEMP, CMP, and QAPP do not include this requirement. |
While our intent is to include a cover page for all master plans and to include these items, will the Government please confirm this requirement in Attachment 6 for the RMP is not included in the 25 page limit, as cover/title pages usually are excluded from page count?
Section L, 4.2 has been updated, via Amendment 0001, to exclude cover/title pages for each Attachment (SEMP, CMP, RMP, and QAPP).
| 43. |
| L, Atch 6, RMP DID |
| Reference: Reference Attachment 6, Contractor’s Risk Management Plan data item description which states in part, “2. Content. The plan shall contain a cover and title page . . . “ |
Question: It is unclear whether two pages are necessary (i.e., a cover page and a title page), or if a cover and title page are the same thing. If two pages are required, can the Government please confirm whether both are non-counted?
Section L, 4.2 has been updated, via Amendment 0001, to exclude cover/title pages for each Attachment (SEMP, CMP, RMP, and QAPP).
| 44. |
| L, Atch 8, Past Performance Information Tool |
| Under the “Printing Reports and Submitting PPI Tool” instructions, item 4 provides instruction to generate the Business Relationships and Past Performance PDF files for submission. |
Will the Government please clarify if we are to submit the two PPI report files separately, in addition to the reports being included in our Volume III Submission, or is it only required to generate the reports to then be incorporated into our Volume III file?
Will the Government also confirm offerors are to submit their saved version of the database as well?
The “printed” PPI reports should be included with Volume III submission. If the offeror prepares the volume in MS Word and the PPI tool reports in “pdf” that is ok, as long as the total count of the information does not exceed the 20-page volume limit.
As stated in the PPI Tool Instructions, Printed Reports and Submitting PPI Tool Section, item 4 and the following note, offerors are required to submit the completed database file with the proposal. The database is necessary to upload the offeror’s PP information into our EZSource tool.
| 45. |
| L, Atch 8, PPI Tool Instructions |
| The Government had released a version of the PPI Tool with the DRFP for this bid, and most teams submitting will have already done preliminary work in the PPI Tool included in the DRFP. Q&A information had mentioned an update of the tool was in process. Please confirm the PPI Tool included in the final RFP is the same as released with the DRFP. |
| What was stated in the draft RFP Q&As is that a new tool is being developed but will not be available for TSA IV submission. Therefore, offerors are to work within the “confines” of the tool that was released with the RFP. |
The PPI tool has not changed from what was posted with the draft RFP.
| 46. |
| L, Atch 9, Past Performance Questionnaire |
| The Past Performance Questionnaire (Attachment 9) page 7 states “Email questionnaires to Steve Godby, steven.godby@us.af.mil and Marcia Hall, marcia.hall@us.af.mil NLT 3:00pm EST, 6 May 2021” However, Section L 5.1 states “...All respondents shall be instructed that all responses are to be provided directly to the Government CO (Steve Godby, steven.godby@us.af.mil) or Contract Specialist (Marcia Hall, marcia.hall@us.af.mil) not later than 17 May 2021...” |
· Request that the date in Attachment 9 be changed to reflect 17 May to allow sufficient time for offeror’s to prepare and distribute the questionnaires and for recipients to complete and return.
In Amendment 0001, Section L, 2.6 has been updated to reflect a change in requested date of 3:00pm EST 10 May 2021 for the PP volume and Section L, 5.1 and the PPQ (L, Atch 9) have been updated to reflect a due date of 3:00pm EST 20 May 2021 to coincide with a proposal deadline of 3:00pm EST 20 May 2021.
| 47. |
| M, 2.1.1 |
M, 2.1.2 M, 2.1.3
| “A sound . . . “ Evaluation criteria is for “sound” plans and processes. The word “sound” appears 14 times in Section M. Will the Government please provide their definition for “sound?” |
| Section M, 1 states, “While the Government source selection evaluation team, the Source Selection Advisory Council (SSAC), and the Source Selection Authority (SSA) will strive for maximum objectivity, the source selection process, by its nature, is subjective and, therefore, professional judgment is implicit throughout the entire process.” Therefore, the Government will not provide a definition for “sound”. The offeror may use the standard definition of sound as a guide. |
| 48. |
| M, 2.2.4 |
| Relevance Assessment – “Since the details of specific tasks to be performed under TSA IV are not known at the time of this source selection, the offeror’s past performance will be judged on the basis of their application of general processes which are anticipated to be required for TSA IV task orders, rather than close similarity of prior products or services.” |
The assessment information in M.2.2.4 appears to be somewhat at odds with the relevance criteria listed in both the table “Relevancy Ratings” within Sec. M. 2.2.4 and within Sec. M. Att.1. In the table of Att. 1, the Government appears to judge as more favorable something that DOES match close similarity of prior products or services. The “Relevancy Ratings” table and the Att. 1 rating read ‘very relevant’ is shown as “Present/Past performance effort involved essentially the same scope and magnitude of effort and complexities this solicitation requires.”
If possible, please clarify which of these relevance assessment approaches will be used since it may directly impact how Offerors present past performance.
L, 2.2.4 states, “In determining relevance, the Government will evaluate how an offeror’s performance involves aircraft training systems and is relevant to the Technical Subfactors: 1) Engineering and Innovation, 2) Sustainment, 3) Courseware Development/Instruction, and 4) Program Management using the Past Performance Relevancy Matrix (Section M, Attachment 1) as its guide.”
The relevancy ratings and associated definitions in the M, 2.2.4 table provide a general statement of relevancy and the relevancy matrix (M, Atch 1) will be used as a guide to help the PP team determine the level of relevancy of each contract.
It is advised the offeror select contracts showing relevance to the technical subfactors with emphasis on what is provided in the PP Relevancy Matrix.
| 49. |
| M, Atch 1, Past Performance Relevancy Matrix |
| Introduction: “Note: It is not the Government’s intent to analyze or associate any dollar values to the contract references provided in terms of defining magnitude of effort.” |
Since magnitude is frequently defined by contract value, please indicate the alternative means the Government will use to differentiate between “same scope and magnitude” (very relevant); “similar scope and magnitude” (relevant), “some of the scope and magnitude” (somewhat relevant).
As stated in M, 2.2.4 and M, Atch 1, “It is not the Government’s intent to analyze or associate any dollar values to the contract references provided in terms of defining magnitude of effort.”
The relevancy ratings and associated definitions are required under FAR Part 15 and the DoD Source Selection Procedures; however, the Government has determined that “magnitude” will not be assessed under TSA IV. The Government will use the Relevancy Matrix (M, Atch 1) as a guide to determine the level of relevancy for scope and complexities for each contract submitted by the offeror.
| 50. |
| RFP Model Contact, Section B |
| Does the Government envision a remote Post Award Conference (PAC), conducted within the initial $1,000 budget or would an offeror have an opportunity to propose for a face-to-face PAC? |
| The Post Award Conference (Task Order 0001) will be held with all TSA IV awardees as a single event with all awardees required to be in attendance. At this time, the Government anticipates the conference will be held “in-person” at WPAFB. Awardees will be given sufficient notification of the date, time, and place for the conference. |
| 51. |
| RFP Model Contract |
| The referenced form is locked and password protected by the author. |
Will the Government please provide a file that can be unlocked or a fillable file, to allow offerors to complete the SF 33 and Section K?
The Model Contract is generated from our contract writing system and cannot be manipulated to allow for fill-ins. It is recommended the offeror print those pages needed to be completed and then scan to digital format to include in proposal submission.
| 52. |
| RFP Model Contract |
52.222-46 EVALUATION OF COMPENSATION FOR PROFESSIONAL EMPLOYEES (FEB 1993)
| While the requirement for a PECP was removed from Section L during the DRFP phase, FAR clause 52.222-46 (which does require a PECP) remains in the RFP. Please confirm that a PECP is not required with the base proposal submission. |
| A PECP is not required for the TSA IV proposal submission. The clause will be included in the awarded TSA IV basic ID/IQ contracts for use at the task order level, as applicable. |
| 53. |
| RFP Model Contract, Section H, H011 |
| The OCI clause references a Government-approved OCI Mitigation Plan. The Section L requirements do not contain any requirements for offerors to disclose any actual, perceived or potential organizational conflicts of interest nor to submit an OCI Mitigation Plan with their proposal. Is it the Government's intent that the OCI Mitigation Plan will be submitted by the successful contractor(s) post-award? Do offerors need to include a statement regarding their agreement with the provisions of the OCI clause and/or not having a conflict of interest in their proposal and, if so, in which Volume? |
| The Section H clause will be included on the awarded ID/IQ contract. Its applicability will be specified at the task order level. |
| 54. |
| RFP Model Contract, Section H, H012 |
| The applicable NAICS codes and size standards are delineated below: |
NAICS Code Size Standard Unrestricted Pool – 336413, 1,250 Employees Small Business Set-Aside Pool – 336413, 1,250 Employees Noting that the Government is soliciting Training Systems through this acquisition and manufacturing is the activity associated with the referenced NAICS code, will the Government please verify and confirm that NAICS Code 336413 “Other Aircraft Parts and Auxiliary Equipment Manufacturing” is the applicable/principal purpose NAICS code for this solicitation and resultant ID/IQ contract?
The NAICS Code stated in TSA IV-H012 of 336413 for TSA IV has been approved and will be the NAICS Code for the resulting TSA IV ID/IQ contracts and applied to all resulting task orders issued under TSA IV.
| 55. |
| RFP Model Contract, Section K |
| Page 49 of the RFP references 252.234-7002 EARNED VALUE MANAGEMENT SYSTEM (DEVIATION 2015-O0017) (SEP 2015) … relaying in essence that “If this contract has a value of $100 million or more, the Contractor shall use an EVMS that has been determined to be acceptable by the Cognizant Federal Agency (CFA) …” indicating further that the government will determine whether to audit EVMS capability. |
Under Section K (certifications) on RFP page K-27 of 42 the following is referenced: 52.234-02 NOTICE OF EARNED VALUE MANAGEMENT SYSTEM -PRE-AWARD IBR (NOV 2016) … indicating that there will be an IBR pre-award … (3) The Government will review and approve the offeror's plan for an EVMS before contract award.
Later, under Section K (certifications) RFP page K-41 of 42 references: 252.234-7001 NOTICE OF EARNED VALUE MANAGEMENT SYSTEM (DEVIATION 2015-O0017) (SEP 2015) … relaying in essence that “(a) If the offeror submits a proposal in the amount of $100,000,000 or more- …” What are the USG requirements for the TSA-IV IDIQ submission? If the requirement is:
(1) The offeror shall provide documentation that the Cognizant Federal Agency (CFA) has determined that the proposed Earned Value Management System (EVMS) complies with the EVMS guidelines in the American National Standards Institute/Electronic Industries Alliance Standard 748, Earned Value Management Systems (ANSI/EIA-748) (current version at time of solicitation). The Government reserves the right to perform reviews of the EVMS when deemed necessary to verify compliance.
Or, depending on contractor level of certification
(2) If the offeror proposes to use a system that has not been determined to be in compliance with the requirements of paragraph (a)(1) of this provision, the offeror shall submit a comprehensive plan for compliance with the guidelines in ANSI/EIA-748 Note: The TSA IV ID/IQ contract has no value, but rather a ceiling value. Offerors are not required to have an approved EVMS for TSA IV. The clauses are included in the ID/IQ and will apply as appropriate at the task order level. Offerors will be notified within a task order fair opportunity proposal request (FOPR) if an approved EVMS is required for that task order.
Offerors are required to submit proposals based on the instructions in Section L.
| 56. |
| RFP Model Contract, Section K, Page 27 of 42 |
SOO, 4.3
Section K of the Model Contract includes FAR Clauses 52.234-02, Notice of Earned Value Management System-Pre-Award IBR (NOV 2016), and 52.234-03, Notice of Earned Value Management System-Post-Award Integrated Baseline Review (NOV 2016). Inclusion of these Earned Value Management System (EVMS) clauses at the TSA IV-level appears to indicate that Offerors are required to have a Defense Contract Management Agency (DCMA) approved EVMS to qualify for award of a TSA IV IDIQ contract, while the “Cost, Schedule and Performance Control” requirements in Section 4.3 of the Statement of Objectives do not indicate a requirement for an approved EVMS.
Are Offerors required to have an approved EVMS to be awarded a TSA IV contract, or will the applicability of FAR Clause 52.234-02 and 52.234-03 requirements be identified at the individual task order-level based on the supported task order scope?
Offerors are not required to have an approved EVMS for TSA IV. The clause is included in the ID/IQ and will apply as appropriate at the task order level. Offerors will be notified within a task order fair opportunity proposal request (FOPR) if an approved EVMS is required for that task order.
| 57. |
| SOO General |
| Is there a forecast for the expected percentage of learning asset development that will be online versus in person? |
| Offerors are required to submit proposals based on the instructions in Section L. There are no instructions to address any SOO paragraphs. Specific requirements relating courseware development/instruction will be provided in the PWS of the applicable task order. |
| 58. |
| SOO General |
| Is there an expectation for in-person courses to be held anywhere other than Dayton? |
| Offerors are required to submit proposals based on the instructions in Section L. There are no instructions to address any SOO paragraphs. Specific requirements relating courseware development/instruction will be provided in the PWS of the applicable task order. |
| 59. |
| SOO General |
| Would offerors be involved in the content gap analysis process as well as course design, development, implementation and evaluation? |
| Offerors are required to submit proposals based on the instructions in Section L. There are no instructions to address any SOO paragraphs. Specific requirements relating courseware development/instruction will be provided in the PWS of the applicable task order. |
| 60. |
| SOO General |
| Is there a specific LMS already utilized that will be maintained or will there potentially be a change in LMS and subsequent data migration efforts involved? |
| Offerors are required to submit proposals based on the instructions in Section L. There are no instructions to address any SOO paragraphs. Specific requirements relating courseware development/instruction will be provided in the PWS of the applicable task order. |
| 61. |
| SOO, 4.11 |
| Does the offeror have to include a copy of the Government provided DD254 form in their proposal and if so what block numbers are required to be filled out? |
| The Government does not require the offeror to make any changes to the draft DD254. As stated in RFP Atch, 2, Draft DD254, box 9, “This draft RFP DD254 is provided to address the general security requirements to participate in TSA IV.” The DD254 will be completed by the Government with the prospective awardee information at the Final Proposal Revision (FPR) stage of the source selection. |
File details come from the government source that posted it. Updated .