TSA IV Draft RFP Q-As - 31Mar21.docx
DOCX document 66 KB Posted
- Attached to
- Training Systems Acquisition (TSA) IV Federal contract opportunity
- Solicitation number
- FA8621-21-R-0030
About this file
This document provides information about the Training Systems Acquisition (TSA) IV solicitation. The Air Force Life Cycle Management Center plans to competitively award multiple TSA IV indefinite-delivery/indefinite-quantity contracts to streamline and standardize training system acquisition and support procurement processes. The majority of work will involve sustainment of existing training systems, including contractor logistics support, technical support center services, and concurrency modifications. Additional scope includes courseware development, instruction, and development of new training systems. Interested parties can find current information on the TSA IV effort through the attached What's New document. The agency is the Air Force Materiel Command Lifecycle Management Center located at Wright Patterson Air Force Base.
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 Regarding Draft RFP Documents
Questions and Answers – 31 March 2021
| Reference |
| Question/Comment |
| Government Response |
| 1. |
| L, 2.2 |
M, 2.1
| Given that Factor 1 – Technical contains four Subfactors and a total of 14 Measures of Merits (MoMs), we respectfully request the Government consider increasing the Technical Volume page count from 30 pages to 40 pages to allow offerors adequate space to fully address the multi-dimensional list of requirements and evaluation criteria while remaining compliant to page layout, font restrictions, etc. At 40 pages, a volume overview/introduction and each MoM could average approximately 2.5 pages. Since MoM complexity varies and the details of four of the MoMs will be provided in Plan attachments, initial development of our Technical response to the ITO and EFFA indicates that 30 pages is too restrictive, but 40 pages is adequate. In comparison to TSA III, the Technical volume also had four Subfactors, but with fewer (13) MoMs and a page limit of 50 pages. Please consider giving page-count relief of 40 pages for the Technical volume. |
| The page count for the Technical Volume for TSA IV will remain at 30 pages. We think it is sufficient count to “answer” those areas not required in a master plan. Note that a good amount of the technical volume is made up solely of the master plans (e.g., SEMP, CMP, RMP, and QAPP). Offerors should be able to comply with Section L and M for the remaining areas within the 30 pages. |
| 2. |
| L, 2.3 |
| Paragraph states, “Pages shall be single-spaced as defined in paragraph settings/spacing in Microsoft Word, with a double space between paragraphs.” |
Will the Government re-evaluate the double spacing requirements between paragraphs and replace with single space between paragraphs to accommodate addressing the requirements of the RFP?
We use double-spacing between paragraphs for ease of reading. This has become a best practice for proposal submission since the majority of proposals are submitted electronically now. TSA IV will remain with double-spacing between paragraphs.
| 3. |
| L, 4.3.1.d |
| Draft RFP, Section L 4.3.1.d is titled “Integration”. However, the text in the paragraph appears to request a discussion from offerors on more than simply integration. |
Please advise whether the Government will retitle Section L 4.3.1.d to “Technology Insertion” to match the wording of the paragraph.
L, 4.3.1.d is titled, “Technology Integration”. It will remain with this title. Although, we are asking for processes for identifying, evaluating, and integrating new technologies, as a whole it is about technology integration into the simulator environment.
| 4. |
| L, 4.3.1.d |
| Draft RFP, Section L 4.3.1.d has the phrase “two or more families of simulators”. |
Please clarify the phrase, “two or more families of simulator”. Is it correct to interpret this phrase as referring to more than one aircraft Mission Design Series (MDS) for a given training device type (e.g., the B-1 WSTs as the first family and the KC-135 OFTs as the second family)? Alternatively, is it correct to interpret this phrase as referring to more than one training device type for a given MDS (e.g., the B-1 WSTs as the first family of trainers and the B-1 CPTs as the second family of trainers)?
See Q17 from the 12 November Q&As where this question was originally answered. A “family of simulators” refers to a single program (KC-10 TS, KC-135 ATS, C-17 TS, C-130J MATS, etc.) training system devices. What is being stated here is when you use two or more of these programs or “families”.
| 5. |
| L,5.3 |
L, Attachment 8 Section L5.3 requires Offerors to provide a “roadmap” describing all organizational changes of the company within the last five years, and to include it in Volume III Past Performance. Attachment 8, indicates Offerors will generate reports for the Business Relationships and for the three Past Performance citations, to then combine the two reports as our Past Performance Volume.
Will the Government confirm that in addition to the Business Relationship report and the Past Performance report (that contains the three citations) generated from the PPI tool, Offerors are also to include the Organizational Structure Change History “roadmap” within the Past Performance Volume, but not something that is generated through the PPI tool?
Yes, that is correct. The PP volume shall contain the organizational change history and all information generated from the PPI tool (Business Relationships page and contract citations).
The volume has a 20-page limit. This count is based on an estimate of 5 pages per contract (i.e., 15 pages), 1 page for the Business Relationships printout from the tool, which leaves 4 pages for introductory information (which includes the organizational change history). However, the offeror may use the page limit as necessary to fit its contract information as long as all information required is submitted within the 20 pages.
| 6. |
| L, Attachment 8 |
| Section L, Attachment 8 requires offerors to submit Past Performance information using the Past Performance Information Tool. Some of the required fields, such as “Program Title” seem to have a character limit and truncates the information entered. |
Will the Government remove or increase the character limit, so information does not get truncated?
Offerors must work within the character limit constraints of the PPI tool. A new tool is being developed with a new version of EZSource, which will not be available for TSA IV and the developers of the current tool is not doing any more modifications to the current tool. I suggest you provide a short title and if you need a more detailed program title, include it under the Brief Description block.
| 7. |
| L, Attachment 8 |
| Section L, Attachment 8 requires offerors to submit Past Performance information using the Past Performance Information Tool. Due to security requirements, some contracts may restrict the release of information in fields required such as Contr Agency/Customer, Contract Number, Contract Dollar Value, and Points of Contact. |
Will the Government confirm, entering “Not Releasable” is an acceptable response in fields where the Contractor is contractually restricted from releasing specified information and that such response will not result in a lower or non-compliant rating?
If this information is not included, the Government cannot verify the offeror’s performance on the contract; therefore, it would likely result in insufficient data being available for that contract, which could result in a Neutral assessment for that contract. It is at the offeror’s discretion what you provide for past performance, but it would serve you well if the Government has the ability to look up a contract in CPARs based on contract number and be able to verify the offeror’s performance through CPARs and/or PPQs.
Note: L, 2.2.2 states, “No classified information is required or permitted in the offeror’s response.”
| 8. |
| Draft Q&A dated 10 Mar 21 |
L, Attachment 8 In the answer to question 5 of the TSA IV Draft RFP Q-As - 10Mar21.docx, it was indicated that “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 Attachment 8, it indicates that PPI reports (Business Relationship and Past Performance) shall be saved to a CD and submitted.
Will the Government adjust the requirement to coincide with the adjusted requirement in Section L that Offerors may submit via either CD or through DoD SAFE?
Good catch . Section L, Attachment 8, Section ‘Printing Reports and Submitting PPI Tool’ has been modified to read: “Submit an electronic copy via CD-R/DVD-R or through DoD SAFE of the saved PPI database file with your proposal.”
| 9. |
| Draft Q&A dated 20 Nov 20 |
| The Government response #4 to Questions and Answers from 2nd draft Posting – 12 November 2020, states that, “The clause in TSA IV will read the same as in TSA III. The statement allows for the CO to require proposal receipt within a time period other than 45 days; however, if the CO fails to indicate a date in the change proposal request, the contractor is required to submit the proposal within 45 days.” |
How many calendar days will the Government allow between final RFP release and proposal receipt?
As stated in the clause, it is at the CO’s discretion for that task order as to what the proposal due date will be for a change proposal. However, if the CO, does not provide a specific due date within the change proposal request, then in compliance with the TSA IV H clause, the proposal must be submitted within 45 days.
Questions and Answers – 10 March 2021
| Reference |
| Question/Comment |
| Government Response |
| 1. |
| L.2 – Proposal Preparation Instructions |
| Section L.2 Proposal Preparation Instructions, states, “The offeror shall make a clear statement in Section A of the proposal documentation volume that the proposal is valid until the date specified in Section A of the model contract/solicitation.” |
Will the Government confirm the intent is to provide this statement in Section A of the Contract Documentation volume, and not a proposal documentation volume?
Yes, the statement shall be included in the Contract Documentation Volume. Section L has been updated.
| 2. |
| L2.2.3 – Cross Referencing |
| Section L2.2.3 Cross Referencing, states, “The offeror shall complete the cross-reference matrix located at Section L Attachment 1, which correlates the RFP with the offeror’s proposal, for Volume II only. The offeror may prepare a cross-reference matrix in another format as long as it adheres to these instructions. The cross-reference matrix will reference the Proposal Volume/Paragraph and applicable SOO, Section L, and Section M paragraphs. The matrix will not be included in the volume page count.” |
Will the Government clarify where within Volume II the Cross Reference Matrix should be included (e.g., In the front matter along with the Table of Contents and Glossary, or as an Appendix to Volume II)?
It is at the offeror’s discretion where the matrix is located within Volume II, as long it is within Volume II. However, L, 4.2 provides a “general” outline of volume organization.
| 3. |
| L2.2.3 – Cross Referencing |
| Section L2.2.3 Cross Referencing, states, “Additionally, to the extent this matrix discloses details as to the manner by which the Government intends to evaluate the offeror’s proposal for award, evaluation factor references in the matrix are for information purposes only, and the Government shall be obligated to evaluate proposals solely in conformance with the provisions of the evaluation criteria in Section M (RFP Attachment 11) of the RFP.” |
Will the Government confirm the Attachment 11 reference should be Attachment 10, which is the attachment number of section M?
Attachment 10 is correct for Section M. Section L has been updated.
| 4. |
| L2.3 Page Size and Format |
| Section L2.3 Page Size and Format, 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.” |
For the purpose of providing legible tables, charts, graphs, figures, diagrams, and schematics, will the Government confirm that the use of 10-point font other than Times New Roman (i.e. Arial Narrow) is allowed? Arial Narrow allows for more legible tables, charts, figures, etc.
Yes, Arial font may be used for tables, charts, graphs, etc. as long as no smaller than 10-point.
| 5. |
| L2.4 Electronic Offers |
| Section L2.4 Electronic Offers, states, “Submit proposal Volumes I, II, and IV on a single CD-R/DVD-R. Submit Volume III, Past Performance on a separate CD-R/DVD-R. Offerors shall also submit all proposal volumes via DoD SAFE (https://safe.apps.mil/).” |
As COVID-19 continues to impact the United States and global community, we are following all recommendations from the Centers for Disease Control and Prevention, U.S. Department of State, and World Health Organization. While we have been successful to mitigate any impacts to our business operations, the health and safety of our employees is of the utmost importance. We have implemented a number of requirements company-wide to limit potential employee and community exposure including:
· Working remotely, away from company facilities, whenever possible;
· Avoiding non-essential business travel; and
· Conducting virtual meetings via Skype, WebEx or other available conference call services The production of CD-R/DVD-Rs will require offerors to work in person at company facilities, and since offerors proposals will also be submitted via the DoD SAFE site will the Government remove the requirement to also submit CD-R/DVD-R versions of the proposal?
Section L, 2.4 has been modified to state, “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.”
| 6. |
| L2.4 Electronic Offers |
| Section L2.4 Electronic Offers, states, “Each volume shall be in separate directories on the CD-R/DVD-R. Use separate files to permit rapid location of all portions, including exhibits, annexes, addenda, and attachments, if any”. Section 2.4 further provides individual file naming conventions for Volumes I – IV. |
Will the Government confirm we are allowed to submit Volume attachments within the applicable volume files and not have to be separate files. For example, since the SEMP, CMP, RMP, and QAPP are attachments to Volume II it makes the most sense to include those in the Volume II file.
It is preferred that the master plans be submitted as separate files as attachments to Volume II. It is more difficult for the Government to have to separate these attachments out from a large volume file for evaluation purposes. In addition, these master plans will become attachments to the awarded contract and will need to be separate files for that purpose.
| 7. |
| L2.4 Electronic Offers |
| Section L2.4 Electronic Offers, states, “Do NOT submit any documents in PDF format that are copied as “images”. When creating PDF files always submit with textual search and copy functions enabled.” |
Will the Government confirm this does not include any images that offerors may need to provide to meet an RFP requirement (e.g. screenshots of SAM Dashboard or certifications)?
If an offeror is copying an image into a document then converts that document to pdf that is fine as long as the pdf document has textual search and copy functions enabled.
| 8. |
| L3.2 Table of Contents |
| Section L3.2 Table of Contents states, “A master table of contents of the entire proposal (Volumes I through IV)” should be provided with Volume I. |
As with section 2.2.4 (Indexing), will the Government confirm this Master Table of Contents does not apply to the Volume I 5-page limit? Should the Master Table of Contents be submitted as an Appendix to Volume I?
As stated in L, 2.2.4 table of contents do not count against the page limitations for their respective volumes. This applies to all volumes including Volume I.
| 9. |
| L4.3.1.a |
| Section L4.3.1.a Systems Engineering, references SOO paragraph 4.2, which is Mission Essential Services. This SOO reference does not appear to be the most applicable SOO section. |
Will the Government clarify if this should be SOO 4.6 Systems Engineering and not SOO 4.2?
SOO references for all technical subfactors have been removed from Sections L and M.
| 10. |
| L4.3.1.b |
| Section L4.3.1.b Configuration Management (CM), references SOO paragraph 4.13, which is Simulator Common Architecture Requirements and Standards (SCARS). This SOO reference does not appear to be the most applicable SOO section. |
Will the Government clarify if this should be SOO 4.14 Configuration Management (CM) and not SOO 4.13?
SOO references for all technical subfactors have been removed from Sections L and M.
| 11. |
| L4.3.1.c |
| Section L4.3.1.c Concurrency Modifications, references SOO paragraph 4.14, which is Configuration Management (CM). This SOO reference does not appear to be the most applicable SOO section; especially if 4.14 is realigned to section L4.3.1.b per the question above. |
Will the Government clarify if section L4.3.1.c should only reference SOO 5, which covers concurrency modifications or if there should be a different SOO reference(s)?
SOO references for all technical subfactors have been removed from Sections L and M.
| 12. |
| L4.3.1.d |
| Section L4.3.1.d Integration, references SOO paragraph 4.6, which is Systems Engineering. This SOO reference does not appear to be the most applicable SOO section. |
Will the Government clarify if this should be SOO 4.10 System Integration and not SOO 4.6?
SOO references for all technical subfactors have been removed from Sections L and M.
| 13. |
| L4.3.2.a |
| Section L4.3.2.a TSSC, references SOO paragraph 6.3, which is Maintenance. This SOO reference does not appear to be the most applicable SOO section. |
Will the Government clarify if this should be SOO 6.7 Training System Support Center (TSSC) and not SOO 6.3?
SOO references for all technical subfactors have been removed from Sections L and M.
| 14. |
| L4.3.2.c |
| Section L4.3.2.c DMO, references SOO paragraph 6.2, which is Operations. This SOO reference does not appear to be the most applicable SOO section. |
Will the Government clarify if this should be SOO 6.4 Distributed Mission Operations (DMO) and not SOO 6.2?
SOO references for all technical subfactors have been removed from Sections L and M.
| 15. |
| L4.3.3 |
| Section L4.3.3 Subfactor 3: Courseware Development/Instruction, references SOO paragraph 6.4, which is Distributed Mission Operations (DMO). This SOO reference does not appear to be the most applicable SOO section. |
Will the Government clarify if this should be SOO 6.8 Instructions Services and not SOO 6.4?
SOO references for all technical subfactors have been removed from Sections L and M.
| 16. |
| L4.3.4.a |
| Section L4.3.4.a Program Management, references SOO paragraphs 4.1 and 4.10 (including subparagraphs), which are Contractor Manpower Reporting and System Integration, respectively. The SOO reference for 4.10 does not appear to be the most applicable SOO section. |
Will the Government clarify if these should be SOO 4, 4.1-4.5 and SOO 4.11 (including subparagraphs), and not SOO 4.10?
SOO references for all technical subfactors have been removed from Sections L and M.
| 17. |
| L4.3.4.b |
| Section L4.3.4.b Risk Management, references SOO paragraphs 4.1 which is Contractor Manpower Reporting, and 4.10.1, which does not exist in this version of the SOO. |
Will the Government clarify the appropriate SOO sections, if any, to be written to in Section L4.3.4.b Risk Management?
SOO references for all technical subfactors have been removed from Sections L and M.
| 18. |
| L4.3.4.c |
| Section L4.3.4.c Quality Assurance, references SOO paragraph 12 and subparagraphs, which is Deliverables and does not contain subparagraphs in this version of the SOO. |
Will the Government clarify if this should be SOO 13 Summary Services (which includes subparagraphs 13.1 Quality Assurance and 13.2 Quality Control) and not SOO 12?
SOO references for all technical subfactors have been removed from Sections L and M.
| 19. |
| L5.1 |
| Section L5.1 states, “The Business Relationships page generated from the Past Performance Information Tool is counted within the Introductory Information in the Past Performance Volume.” |
Will the Government clarify if the Business Relationship page is the same as the Organizational Structure Change History that is required in section L5.3 or something additional within the Past Performance Information Tool?
The Business Relationship page in the PPI tool is required to identify the offeror for the PP information entered into the PPI tool. It will result in a single page “printout”.
The Organizational change history is a different requirement to be included within the PP Volume per the instructions in L, 5.3.
| 20. |
| L5.1 |
| Section L5.1 states, “For each identified effort for a commercial customer, the offeror shall also submit a Client Authorization Letter (Section L, Attachment 10), authorizing release to the Government of requested information on the offeror’s performance.” |
Will the Government confirm the Client Authorization Letters can be included as an appendix to Volume III Past Performance and not be included within the Past Performance 20-page limit?
If Client Authorization Letters are submitted for commercial contracts, they are not included in the PP volume page count and should be submitted as an attachment/appendix to the volume.
| 21. |
| SOO 13 Services Summary |
| SOO Section 13 Services Summary contains a table that outlines the Performance Objective and applicable SOO Paragraph. Most of which do not align to the SOO paragraphs/headers within the SOO. |
Recommend the Government review the Services Summary Table, SOO Paragraphs, and Section L instructions to verify all references align. This will be beneficial to do this prior to Final RFP release to avoid any confusion and additional questions from Offerors.
The Services Summary in the SOO has been verified and updated to reflect appropriate SOO references. In addition, SOO references for all technical subfactors have been removed from Sections L and M.
Note: L, 4.1 has been modified to include the following statement: “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.”
| 22. |
| General |
| Section L contains references to multiple RFP attachments, however, some attachments have not been released yet. Attachments such as Attachment 1 (Cross Reference Matrix), Attachment 8 (Past Performance Information Tool), Attachment 9 (Past Performance Questionnaire), and Attachment 10 (Client Authorization Letter). |
Will the Government release these attachments prior to Final RFP release so Offerors can review and provide any questions and recommendations prior to the RFP release, as necessary?
The PPI tool and associated instructions were posted on betaSAM 20 November 2020.
The remaining attachments will be posted with the final RFP.
Questions and Answers from 2nd draft Posting – 12 November 2020
| Reference |
| Question/Comment |
| Government Response |
| 1. |
| DID |
| DI-MGMT-81808 – RMP, last sentence required Word 2003-2007 format, is that correct? |
| The DID has been modified to state MS Word 2010 or later to be consistent with Section L instructions. |
| 2. |
| General |
| Would you be able to define task order participation requirements? How are prime evaluated for task order participation? |
| The H clause for task order participation states, “TSA IV awardees will be required to propose on a minimum of two competitive task orders during the 5-year base period. This includes task orders proposed as a prime or a subcontractor.” This will be tracked by the TSA IV Core Team as proposals are submitted for task orders. |
| 3. |
| General |
| Would you be able to provide examples of types of contract incentives at the task order level? |
| There are a variety of incentives connected contract type (i.e., CPFF, CPIF, FPIF, etc.) that a program team may implement on a task order. These incentives are used to encourage contractor performance. |
| 4. |
| General |
| It was stated by the Government during the one on one session that change proposal turnaround time would be determined at the Task Order level. Within TSA III H-004 states “the contractor shall submit a proposal, in Microsoft Word and/or Excel, to the Government within 45 days, or within the time specified by the contracting officer”. Will the proposal turnaround requirement be removed from the H-Clauses for TSA IV or will language be included which states the proposal turnaround requirements in the Task Order take precedence over the IDIQ? |
| The clause in TSA IV will read the same as in TSA III. The statement allows for the CO to require proposal receipt within a time period other than 45 days; however, if the CO fails to indicate a date in the change proposal request, the contractor is required to submit the proposal within 45 days. |
| 5. |
| General |
| According to the 10 Nov 2020 Draft RFP, Section M, the Government anticipates awarding multiple ID/IQ TSA IV contracts (approximately 10-15 in the Unrestricted Pool and approximately 10-15 in the Small Business Pool). During TSA III source selection, the Government reportedly limited the number of Unrestricted proposals in the competitive range to a maximum of 12, for the purpose of efficiency. Please clarify if it is the Government's intention to award to each and any qualifying offerors on TSA IV, as long as the number of qualified offerors does not exceed 15 within the respective Unrestricted or Small Business pools? |
| As stated in Section M, 1, “Award will be made to each and all qualifying offerors.” There is no perceived limit on how many awards that may be. The range of awards for each pool indicated in M, 1.2 is based on our market research. Typically, industry wants a range of number of awards so we base that on market research with the disclaimer that the Government reserves the right to award to more or fewer ID/IQ contracts. |
| 6. |
| General |
| The Government clearly allows joint ventures (JV's) to compete for a spot on TSA IV. Is it allowable for a prime offeror to compete individually, and also to compete as part of a JV? Similarly, what is the Government's position regarding the eligibility of different divisions or business units within a large corporation, each competing separately for a spot on TSA IV? |
| If a SB is part of a JV with other SBs and submits a proposal for TSA IV as a JV, that SB may also submit a proposal as a prime for TSA IV. However, that SB must be able to meet the requirement of being technical acceptable with Satisfactory Confidence or better for PP to receive an award as a prime awardee. Typically, JVs are formed because a single SB does not have the capabilities to meet the criteria as a prime offeror. |
In addition, if a Mentor-Protégé JV is formed between a SB and LB for the SB Pool, that LB may also submit a proposal as a prime offeror in the Unrestricted Pool.
| 7. |
| General |
| Please explain the lengthy delay between the proposal due date in March 2021 and the expected TSA IV award in November 2022. Much might change during that 20-month time period (e.g., mergers & acquisitions, fresh past performance, etc.) that could be very relevant and useful to the Government for TSA IV source selection. In that regard, what updated information will the Government accept from offerors after proposal submission but prior to source selection? |
| The length in schedule is to cover the evaluation of the proposals received. We anticipate a large number of proposals and each proposal must be evaluated IAW the evaluation criteria stated in Section M. The schedule also allows for the FAR 15, process we must follow and is based on the standard process for a FAR 15 source selection. We will not allow for alternate proposals or updated proposals unless specifically requested by the Government during Discussions or Final Proposal Requests (FPR). |
| 8. |
| Industry Day Slide 25 |
| 16 Nov 20 Industry Day chart #25 indicates that Operations & Integration (O&I) contracts like DMON 3.0 and MAF DMO are potential TSA IV programs. |
What SOO paragraph(s) cover the O&I work scope?
SOO, 6.4 provides the top level requirements for DMO. If/when the DMON 3.0 and/or MAF DMO programs utilize TSA IV, the specific requirements will be documented in a PWS for that program.
| 9. |
| L General |
| There is a disparity between references to the attachments. For example, Section L, Section 6 (Volume IV Contract Documentation) references Section J Attachments (6.1.9). These attachments include Attachment 4/5/6/7/8: Attachment 4 (SEMP), Attachment 5 (CMP), Attachment 6 (RMP), Attachment 7 (QAPP), and Attachment 8 (SBSP). Section 4.3.1 Subfactor 1 Engineering and Innovation Item a, Systems Engineering references Section L, Attachment 2 for the SEMP, but Paragraph 6.1.9 references Attachment 4. Section 4.2 Volume Organization references the SEMP as Attachment 1. |
Would you be able to clarify which attachment is required for what volume, and where it should be contained?
Are they appended to the Technical as attachments (IAW Section 4) included in Volume IV Contract Documentation as attachments (IAW section 6)?
L, 2.2 and 4.2 instruct offerors to submit the master plans (SEMP, CMP, RMP, QAPP) in Volume II.
L, 2.2 and 6.5 instruct the SBSP be submitted in Volume IV.
L, 6.1.9 is informing the offeror how the plans will be incorporated into the awarded TSA IV contract. L, 6.1.9 states, “The following Section J attachments will be included as part of the TSA IV contract:” There are no instructions to the offeror to submit the master plans, except the SBSP, in Volume IV.
| 10. |
| L, 2.3 |
| Section 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. |
Does “shall be counted as two pages” in the last sentence apply to only 11x17-inch pages or to all tables, charts, graphs, figures, diagrams, and schematics?
It applies to only to the use of 11x17 pages that will be counted as 2 pages.
| 11. |
| L, 4.3.1.a |
| The cited section cross-references SOO paragraph 4.2 for development of the SEMP. However, Section 4.2 concerns Mission Essential Services, while 4.6 concerns systems engineering. Please confirm the correct cross reference. |
| The SOO paragraph references in Section L have been corrected. |
| 12. |
| L, 4.3.1.a |
| Please confirm that the Contractor’s processes for systems engineering requirements are to be detailed in a standalone 25-page SEMP plan and are not required to be restated within the confines of the 30-page technical volume. |
| Section L states the SEMP shall not exceed 25 pages and is not included in the 30-page volume limit. It is at the offeror’s discretion how they comply with Section L instructions for Volume II. Make sure you are reading what is required for each subfactor. If the instructions state submit a plan (e.g., 4.3.1.a), then it would imply the plan is all that is required for that area. It is not the Government’s intent or desire to read the same information in two different places within the proposal. |
| 13. |
| L, 4.3.1.a |
| Section L 4.3.1.a states: The Simulators Division’s Organizational Systems Engineering Plan (OSEP) is provided as Section L Attachment 3 to assist in developing the SEMP. (SOO paragraph 4.2) |
SOO Paragraph 4.2 is Mission Essential Services. Should this refer to SOO Paragraph 4.6 Systems Engineering?
The SOO paragraph references in Section L have been corrected.
| 14. |
| L, 4.3.1.b |
| The cited section cross-references SOO paragraph 4.13 for development of the CMP. However, Section 4.13 concerns SCARS, while 4.14 concerns configuration management. Please confirm the correct cross reference. |
| The SOO paragraph references in Section L have been corrected. |
| 15. |
| L, 4.3.1.b |
| Section L 4.3.1.b states: The Agile Combat Support (ACS) Directorate CMP is provided as Section L Attachment 5 to assist in developing the offeror’s CMP. (SOO paragraph 4.13) |
SOO Paragraph 4.13 is Simulator Common Architecture Requirements and Standards (SCARS). Should this refer to SOO Paragraph 4.14 Configuration Management?
The SOO paragraph references in Section L have been corrected.
| 16. |
| L, 4.3.1.c |
| Section L 4.3.1.c states: In addition, provide innovative concepts the offeror would apply to training system concurrency. (SOO paragraph 4.14 and 5) |
SOO Paragraph 4.14 is Configuration Management. Should this refer to SOO Paragraph 4.15 Sustaining Engineering?
The SOO paragraph references in Section L have been corrected.
| 17. |
| L, 4.3.1.d |
| Section L 4.3.1 states: Integration: Describe the offeror’s process or identifying, evaluating, and integrating beneficial new technologies into the Air Force Simulator environment, generally across two or more “families” of simulators, to improve performance, reduce cost, or enhance lifecycle supportability. (SOO paragraph 4.6). |
Please provide a definition of “families of simulators” for this requirement.
A “family of simulators” refers to a single program (KC-10 TS, KC-135 ATS, C-17 TS, C-130J MATS, etc.) training system devices. What is being stated here is when you use two or more of these programs or “families”.
| 18. |
| L, 4.3.2.a |
| Section L 4.3.2.a states: TSSC: Describe the offeror’s process for TSSC operations, responsibilities, and interaction with development teams. Include the offeror’s process to augment the technical staff to flex and meet greater TSSC demands. (SOO paragraph 6.3) |
SOO Paragraph 6.3 is Maintenance. Should this refer to SOO Paragraph 6.7 Training System Support Center?
The SOO paragraph references in Section L have been corrected.
| 19. |
| L, 4.3.2.c |
| Section L 4.3.2.c states: DMO: Describe offeror’s process for executing DMO requirements, to include resource allocation, scheduling, coordination, establishing connectivity for pre-mission briefings, mission execution, post-mission debriefing activities, and security. (SOO paragraph 6.2) |
SOO Paragraph 6.2 is Operations. Should this refer to SOO Paragraph 6.4 Distributed Mission Operations (DMO)?
The SOO paragraph references in Section L have been corrected.
| 20. |
| L, 4.3.3 |
| Section L 4.3.3 states: The offeror shall submit the following processes for training system courseware development and instruction. (SOO paragraph 6.4) |
SOO Paragraph 6.4 is Distributed Mission Operations (DMO). Should this refer to SOO Paragraph 6.8 Instructional Services?
The SOO paragraph references in Section L have been corrected.
| 21. |
| L, 4.3.4.a |
| Section L 4.3.4.a states: Program Management: Describe the offeror’s program management approach that includes: (SOO paragraphs 4.1 and 4.10 with its subparagraphs) |
SOO Paragraph 4.1 is a subparagraph of 4 Program Management, and 4.10 has no subparagraphs. Should this refer to SOO Paragraph 4 and its subparagraphs?
The SOO paragraph references in Section L have been corrected.
| 22. |
| L, 4.3.4.b |
| The cited section cross-references SOO paragraphs 4.1 and 4.10.1 for development of the RMP. However, Section 4.1 concerns contractor manpower reporting, while 4.10 concerns system integration; there is no 4.10.1. Please confirm the correct cross reference. |
| The SOO paragraph references in Section L have been corrected. |
| 23. |
| L, 4.3.4.b |
| Section L 4.3.4.b states: Risk Management: Provide a RMP IAW DI-MGMT-81808 (Section L Attachment 6) that describes the offeror’s risk management system and associated tools and processes, and how the risk management system will be applied to improve program performance. In addition, the offeror shall identify any risk (if any) associated with the proposed processes/approaches for each subfactor and the mitigations the offeror intends to implement to reduce/eliminate these risks. (SOO paragraphs 4.1 and 4.10.1) |
SOO Paragraph 4.1 is Contractor Manpower Reporting and 4.10 is System Integration. Paragraph 4.10.1 is not included in the SOO. Should these refer to SOO Paragraph 4 Program Management?
The SOO paragraph references in Section L have been corrected.
| 24. |
| L, 4.3.4.c |
| Section L 4.3.4 states: Quality Assurance: Provide a QAPP IAW DI-QCIC-81794A (Section L Attachment 7) that describe the offeror’s process for implementing a quality management system that addresses the offeror’s accountability for contract requirements. (SOO paragraph 12 and subparagraphs) |
SOO Paragraph 12 is Deliverables. Should this reference be SOO Paragraph 13 and subparagraphs? (i.e., Quality Assurance and Quality Control) The SOO paragraph references in Section L have been corrected.
| 25. |
| L, 4.3.4.c |
| If TSA IV requires compatibility with AS9100, are DCMA approvals and coordination necessary to transition existing TSA programs to the new standard? |
| TSA IV does not require compatibility with AS9100. The DID provided is intended to provide a recommended format and content guide to ensure all QAPPs cover the essential items for a quality program as it relates to TSA IV. |
| 26. |
| L, 4.3.4.c |
SOO 13
| The Quality Assurance Program Plan (QAPP) Data Item Description (DI-QCIC-81794A) requires compatibility with SAE AS9100, Quality Management Systems – Requirements for Aviation, Space and Defense Organizations. Will you confirm that the Government intends to move beyond ISO 9001 to AS9100 for TSA IV? |
| TSA IV does not require compatibility with AS9100. The DID provided is intended to provide a recommended format and content guide to ensure all QAPPs cover the essential items for a quality program as it relates to TSA IV. |
If there are specific requirements for ISO 9001 or AS9100 compatibility beyond the QAPP Master Plan for a task order, those requirements will be explicitly stated in the task order FOPR.
| 27. |
| L, 5.1 |
| The sections states "... In addition to the data provided in this volume, the Government may use the Contractor Performance Assessment Reporting System (CPARS)." Will copies of CPARS be required with the proposal submittal? |
| Offeror are not required to submit CPARs with their proposal submission. The Government Past Performance Team will search for all applicable CPARs. |
| 28. |
| L, 5.1 |
| The section states "Offerors shall send a Past Performance Questionnaire (Section L, Attachment 9) directly to the POCs for the efforts identified." There are some organizations, such as the U.S. Navy, who do not complete PPQs. Will a recent CPARS submitted with the proposal be a sufficient to fulfill this requirement? |
| Offeror are not required to submit CPARs with their proposal submission. The Government Past Performance Team will search for all applicable CPARs. |
Suggest you send the PPQs to your customers even if it’s unlikely they will respond. Offerors are required to provide a listing of the individuals to whom the questionnaires were sent. The Government will make an attempt to reach out to all PPQ contacts who have not responded to try and get feedback regarding an offeror’s performance.
| 29. |
| L, 5.2 |
| The draft RFP states “…Offerors are required to explain what aspects of contracts are deemed relevant to the proposed effort, and to what aspects of the proposed effort they relate…” |
Should this information be included in the proposal as part of the “Introductory Section” or within the PPI Tool Past Performance Program Details tab?
This information should be documented in the PPI tool for each contract relating the work performed on the contract to Subfactors 1 through 4.
| 30. |
| L, 6.5 |
| Draft RFP states “Large businesses shall submit, on a plant or division-wide basis, a SBSP (see FAR 19.701) that contains all the elements required by the clause at FAR 52.219-9, Small Business Subcontracting Plan.” |
Primes can submit a Comprehensive, Master, Individual or Commercial Small Business Subcontracting Plans to fulfil RFP requirements. Comprehensive, Master and Commercial Plans can be established at the plant or division level.
Individual Subcontract Plans are contract specific and are not established at a plant or division level.
Would the government confirm that the plant or division requirement doesn’t apply to Individual Subcontracting Plan requirement?
That is correct, the plant or division requirement does not apply. Section L has been modified to remove the statement.
| 31. |
| L, Atch 3, OSEP |
| The OSEP includes a number of hyperlinks that provide additional detail to the requirements such as guides for technical reviews and risk management (pag 12, para 3.3 - AFLCMC Standard Process to Execute Risk and Issue Management in Acquisition Program; pg 18, para 4.5.2 - AFLCMC Systems Engineering Technical Review Guide; Will these references be made available? |
Additionally, some of the publicly available references have bad links in the document but can be found. Other references are instructions for the program office use in developing the SEP so are not really important to bidders.
We understand the hyperlinks are not active; however, they are not necessary for an offeror to prepare their SEMP. The links point back to WNS specific information. The purpose of providing the OSEP is to help offerors understand how the systems engineering process works within the Sims Division. It’s the most current version available.
| 32. |
| L, Atch 8, PPI Tool |
| The PP Information Tool Contract Information Tab fields don’t seem to be formatted to allow multiple Delivery/Task Order information to be listed. |
As discussed in our 1on1, please confirm that an IDIQ contract, with multiple relevant Delivery/Task Orders, can be used as single past performance reference.
If so, should the Contract Information Tab reflect the overall IDIQ contract information, or individual Delivery/Task Order information (i.e., DO/TO Number, Program Title, PoP, Contract Value, Points of Contact)?
If the IDIQ Delivery/Task Order information is required, how should this information be entered in the PP Information Tool? Should the information be included within the Program Details tab?
If an offeror is submitting a contract reference at the ID/IQ level, then indicate that contract number in the Contract Information Tab of the tool. Then under the Program Details Tab, discuss the relevant DOs/TOs as they apply to each of the subfactors.
If an offeror is submitting a single DO/TO as an independent contract reference, then provide the DO/TO number under the Contract Information Tab. I suggest also including the overall ID/IQ contract number in the Program Details Tab in case we need to use that number for CPAR searches.
| 33. |
| M, 1 and 1.4 |
| Section 1.0 states, "award will be made to each and all qualifying offerors." Section 1.4 discusses competitive ranges to be used as well. Do these sections mean that if a company qualifies, they could still be removed as not one of the highest rated qualifiers? What would be the competitive range criteria if this is the case? |
| A competitive range determination is made after initial evaluations. The SSA will make a determination if we can award without discussions or enter into discussions. The Government reserves the right to award without discussions if there is a sufficient number of offerors who meet the qualifying offeror criteria after initial evaluation. If this is not the case, then the Government would enter into discussions with those offerors who are considered the most highly rated. Since one of the criteria for a qualifying offeror is to have Satisfactory Confidence or better for PP, then an offeror with Neutral Confidence or worse after initial evaluation would likely not be among the most highly rated. |
| 34. |
| M, 2.1.1.b |
| Does the CMP have to be consistent with ACS CMP? Similar to the SEMP in item "a" |
| The ACS CMP is provided to help offerors understand the CM process utilized within the ACS Directorate to include the Sims Division. It is available as a guide and at the offeror’s discretion oh how it is utilized in developing it’s CMP. |
| 35. |
| M, 2.2.1 (also Q&A #72) |
| The section states that an overall PP rating of satisfactory is required and that Factor 2 PP will be rated IAW the table. It also states that each subfactor will be evaluated as well but does not specify how the subfactors will be rated. Can the government clarify how the PP on each subfactor will be rated and how those individual ratings will inform the overall Factor 2 PP rating? What are the ratings for each subfactor as discussed in para 1 and how do they play into the overall rating? |
| The Government will use the same confidence assessment ratings for the Subfactors and the overall Factor rating. |
M, 2.2.1 has been revised to state, “Past performance will be rated for each Technical Subfactor, using the confidence assessments ratings in the table below, with the order of importance for the subfactors in descending order with Subfactor 1 being the most important. The resulting Performance Confidence Assessment rating assessed for the offeror will be made at the Factor level.”
| 36. |
| M, 2.2.4 |
| M, 2.2.4 provides a description of what equates to the different Past Performance Relevancy Ratings, but what is the effective impact of each of the different Past Performance Relevancy Ratings on evaluating Past Performance and calculating a Quality Assessment Rating? |
| The relevancy rating and performance quality ratings are separate distinct ratings that will be assessed for each contract for each subfactor. Relevancy – did you provide a relevant contract and how relevant is that cont6ract; Performance Quality – how well did you perform on that contract. The Government will then review all of the relevancy ratings and performance quality ratings for all of the contracts for each subfactor to assess subfactor confidence ratings. |
| 37. |
| M, 2.2.4, para 2 |
| This section and the PP Relevancy Matrix state that dollar value will not be used to estimate magnitude, but the tables state magnitude will be assessed. How will magnitude be assessed? |
| The relevancy definitions are required from the DoD SS Procedures and cannot be altered. However, we do not intend to assess magnitude so we are informing offerors of this fact in M, 2.2.4. |
| 38. |
| M, 2.2.5 |
| M, 2.2.5 Quality Assessment states that “for each recent and relevant past performance effort reviewed, the performance quality of the work performed will be assessed for Technical Subfactors 1 through 4”. Since this paragraph specifically uses the terms “recent and relevant”, does that mean past performance evaluated as “Somewhat Relevant” will not be eligible for a quality assessment for the Technical Subfactors? |
| Somewhat relevant contracts are still considered “relevant” so they will be assessed for performance quality. If a contract is found to not fall within the recency criteria, it will not be evaluated further. If a contract is recent but not relevant, it will not be assessed for performance quality. If it’s not relevant, it’s not rated. |
| 39. |
| M, Atch 1 |
| Past Performance Relevancy Matrix - Will the past performance relevancy rating matrix be applied: (a) to each past performance citation individually per sub-factor or, (b) will the relevancy rating matrix be applied to the complete body of work of all PP citations collectively per sub-factor? The method in which the Past Performance Relevancy Matrix is applied could result in vastly different Relevancy Ratings. For example in the case of Subfactor 3, if a JV has one member providing a PP citation covering a portion of Subfactor 3 MoMs on an aircraft training systems program and another member providing a PP citation for the remainder of Subfactor 3 MoMs on an aircraft training systems program, vastly different outcomes could occur based on how the Past Performance Relevancy Matrix is applied. In the case of (a) above, the best relevancy rating the JV could receive on each of the two PP citations is “Somewhat Relevant’. Using method (b), the JV could potentially receive “Very Relevant” past performance relevancy ratings. |
| The PP Relevancy Matrix will be applied to each contract for each subfactor. Here’s how it works: Each contract will be evaluated for relevancy and performance quality for each subfactor. The following is a sample view of how this could play out with 3 contracts: |
| SF 1 |
| SF 2 |
| SF 3 |
| SF 4 |
| C1 |
| R |
| VG |
| VR |
| S |
| R |
| E |
| VR |
| E |
| C2 |
| SR |
| S |
| R |
| E |
| SR |
| S |
| SR |
| VG |
| C3 |
| NR |
| NR |
| R |
| VG |
| SR |
| S |
| VR |
| S |
| 40. |
| M,1.1, para 2, item 3 |
| With no price evaluation, what reasons might the contracting officer have to believe a bidder would offer other than fair and reasonable pricing? |
| It is unlikely there would be a reason not to assume a potential awardee would offer fair and reasonable pricing. The Government has the option to conduct Pre-Award Surveys (PAS) on offerors. We will follow FAR 9.104 to make responsibility determinations. |
| 41. |
| PP Matrix |
| Is the change from "performed [or provided] and managed" in the very relevant line to only "performed [or provided]" or only "managed" in the relevant line intentional, because it then goes back to "provided and managed" in the somewhat relevant line? |
| The VR for SF1, SF2, and SF3 is “performed and managed”; SF is “managed”. R is “performed” for SF 1 and SF2; and “managed for SF 3 and SF4. |
| 42. |
| Q58 |
| Small Business Requirement: Q&A States “The goals should be based on the percentage of subcontracted work at the ID/IQ level as a percentage of total annual obligated dollars. Large businesses will be required to update this Master SBSP with each task order proposal submission to indicate percentage of subcontracted dollars for that task order.” |
Would the Government please clarify if a Prime submits an Individual Subcontracting Plan the small business percentage goals should be reflected as a percentage of subcontracted dollars as noted for Master SBSPs?
Due to the nature of the acquisition, it is unknown how many or if a large business will ever be awarded a task order. Therefore, it is virtually impossible for large businesses to provide a statement of the total dollars planned to be subcontracted and a statement of the total dollars planned to be subcontracted to small business concerns, as a percentage of total subcontract dollars as part of their initial subcontracting plan submission. After coordination with the AFLCMC Small Business Office, it was determined to obtain the initial plans without goals for the total dollars to be subcontracted. As a large business wins a task order they will update their subcontracting plan to include these required goals.
| 43. |
| SOO, 12 |
| SS-10 states “Training system is concurrent with aircraft 30 days prior to aircraft fielding”. It was stated by the Government during the one on one session that the concurrency requirements would be determined at the Task Order level. Will the concurrency requirement be removed from the SOO or will language be included which states the concurrency requirements provided in the Task Order take precedence over the IDIQ? |
Regarding the prior question, if the requirement will not be removed from the SOO and the TO is silent on a concurrency requirement, does that imply that the 30 day requirement applies to the TO?
The SS element has been modified to indicate “xx” so that if the element is applied to a task order, the program team can define…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .