FTSS V RFP N6134021R0001 A003_11.19.21.docx

N6134021R0001

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION SF 30 - BLOCK 14 CONTINUATION PAGE

The following have been added by full text:

AMENDMENT A003 DESCRIPTION

The purpose of this amendment A003 is to provide minor solicitation updates.

1) L.2.1.2.a.1 Secret Facility Clearance Prerequisite was updated to clarify that the Facility Clearance must be in the name and Cage Code of the Offeror Prime Contractor in Block 15A in language consistent with L.1.1.d.

2) The M.3.1.3 Not Relevant Definition, paragraph i., was also changed to remove the requirement to provide defined roles and responsibilities in Table ES-1, and paragraph ii., the requirement for work that matches proposed role in ES-1 was also removed.

3) Section C has been updated to remove C-TXT-SCR. See DFARS 252.204-7023 ALT I for reporting requirements for contracted services.

4) In section L.1.1.2.1.1.c.a, the DOD SAFE Drop Off Request submission date was changed to 14:00 EST, 22 November 2021. All other terms and conditions remain unchanged. The proposal due date is extended until 30 Nov 2021.

Offerors who have already submitted a proposal(s) and do not have any changes to their proposal in response to this amendment, shall only return a signed copy of the SF30 along with a letter documenting the proposal remains unchanged, by the proposal due date.

An offeror who has previously submitted a proposal AND is making changes to the submission, shall submit with their updated proposal, a cover letter identifying the extent of the changes, along with the SF30.

The Government will send existing offerors a single DOD SAFE drop-off notice for submission the SF30 and letter documenting that the proposal remains unchanged or for submission of proposal changes. If additional DOD SAFE drop-offs are required, due to the 8GB limit, then the DOD SAFE Drop Off Requests shall be submitted by 22 November 2021 in accordance with L.1.1.2.1.1.c.a.

SECTION A - SOLICITATION/CONTRACT FORM

The required response date/time has changed from 09-Nov-2021 02:00 PM to 30-Nov-2021 10:00 AM.

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been deleted:

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

INSTRUCTIONS TO BIDDERS

SECTION L

L.1 PART A GENERAL INSTRUCTIONS

L.1.1 GENERAL

a) Offerors are required to submit sufficient information concerning all evaluation factors to enable Government personnel to fully assess the capabilities of the Offeror to perform all requirements. The proposal must be sufficient in detail and scope to enable evaluation and provide the evaluators a clear understanding of the Offeror’s approach, expertise, experience and capability as required by the solicitation. All proposals must clearly and convincingly demonstrate that the Offeror has a thorough understanding of all requirements; is able, willing, and competent to devote the resources necessary to meet all requirements. The Offeror shall not alter or rearrange the solicitation. The burden of proof for all substantiation within the proposal rests with the Offeror. Offerors are advised that the Government may incorporate any part of the Offeror’s proposal deemed beneficial to the Government, into the final contract, without discussions. Alternate proposals are not acceptable. The Government will not reimburse Offerors for any cost incurred for the preparation and submission of a proposal in response to this RFP.

b) In presenting material in the proposal, the Offeror is advised that quality of information is more important than quantity. Clarity, brevity, and logical organization should be emphasized during proposal preparation. It is the responsibility of the Offeror to present enough information to allow the Government to evaluate its proposal without discussions. Unsubstantiated statements that the prospective Offeror understands, can or shall comply with the specifications, or paraphrasing the requirements or parts thereof are considered inadequate and may render a rating of unacceptable. All proposal information is subject to verification by the Government. Falsification of any proposal submission, documents, or statements may subject the Offeror to civil or criminal prosecution under Section 1001 of Title 18 of the United States Code.

c) The Offeror shall include any data necessary to illustrate the adequacy of the various assumptions, approaches, and solutions to problems. There is no need to repeat information in more than one volume. The detailed information must be included in the most logical place and summarized and referenced in other areas if an overlap exists. Do not provide elaborate brochures or other presentation material beyond that sufficient to present a complete and effective proposal.

d) Throughout these instructions, Offeror is defined as the prime contractor with its CAGE code identified in Block 15A on Standard Form (SF) 33, Solicitation, Offer, and Award. “Prime Contractor” refers to the single legal entity that has privity-of-contract with the Government for all contractual obligations under a mutually binding legal relationship with the Government. In other words, when the Government awards a contract to a contractor, the contractor is considered the Prime Contractor.

e) A “Joint Venture” (JV) is a partnership or teaming arrangement that is formed for the purpose of responding to this solicitation when the prime contractor consists of more than one legal entity. “JV Team Members” are the entities that make up a Joint Venture. The term “entity” is used to mean any or all of the following: prime contractor, JV, JV team members, any subcontractor, and corporate parent, division, subsidiary, or affiliate (e.g., any contractor with a different CAGE Code/DUNS than the Offeror). The following entities are defined as principal entities and only principal entities will be used in the past performance and experience evaluations: (a) the prime contractor; and (b) JV Team Members. If proposing as a JV, Offerors shall provide copies of any approved JV agreements or JV agreement submissions not yet approved.

L.1.1.2 PROPOSAL FORMAT AND SUBMISSION

a) Proposals must use Times New Roman, 12 pt. normal font (no reduction permitted), single-spaced, 1-inch margins all around, and must be formatted for/printed on standard 8.5 x 11 inch paper. If Government attachments have a different format/font, the Offeror may use the format/font in the attachment as provided. All pages shall be numbered with section and page numbers. Tables shall be presented in no smaller than a 10 pt. font. Text utilized in charts, figures, and graphics shall also be no smaller than a 10pt font and may use a font type selected by the Offeror. Each Volume shall be provided separate folder.

L.1.1.2.1 ELECTRONIC SUBMISSION OF PROPOSAL

a) This section is intended to provide information to the Offeror on the electronic format and application software to be used for submitting proposals. Use of the software and procedures described in this section will ensure that the proposals received are suitable for reading electronically.

L.1.1.2.1.1 ELECTRONIC PROPOSAL MEDIA

a) Method of proposal delivery shall be with https://safe.apps.mil. When submitting proposals in https://safe.apps.mil, the recipient shall be as listed below:

a. Name: Janet Fondriest

b. Email: Janet.fondriest@navy.mil

b) Offerors are advised the SAFE restricts the maximum file submission to 8 GB. Chrome and Edge are recommended. Internet Explorer limits SAFE uploads to 2GB; therefore, it is not recommended. Offerors shall include the following information in the SAFE upload comments block: Offeror’s name, Solicitation number, primary and alternate points of contact (POC) (include name, email, and telephone number(s) for each POC).

c) Offerors are advised the Government will only accept DOD proposal submissions from Offerors who have requested a SAFE drop-off for proposal submission as specified below. All CAC-Authenticated users and all Outside or Unauthenticated users shall request a SAFE drop-off for proposal submission.

a. Requesting a SAFE drop-off for proposal submission: In order to request a drop-off for proposal submission via SAFE, offerors must request a drop-off from Ms. Janet Fondriest (CC: Jana McEntegart, Jana.R.McEntegart.civ@us.navy.mil). Offerors shall submit the names and email addresses for two (2) Points of Contact (POCs) who will submit the Offeror’s proposal in the drop-off request. Due to the SAFE 8G maximum file submission per drop-off, multiple drop-offs may be required for complete proposal submission. The drop-off request shall include the number of drop-offs that will be needed for proposal submission. Offeror shall submit the request via email to Janet.fondriest@navy.mil and Jana.R.McEntegart.civ@us.navy.mil no later than 14:00 EST, 22 November 2021. Offeror will receive an email to each of the two (2) POCs provided with links for each of the drop-offs requested once the request has been processed by the Government. Each link is good for a one-time proposal submission.

d) Table G-3 (Proposal Structure) identifies the proposal structure for each volume. Each volume shall be clearly marked with the Offeror's name and address, the point of contact's name and phone number, the proposal volumes contained therein, and “CUI” and “Source Selection Information – See FAR 2.101 and 3.104”. CUI stands for Controlled Unclassified Information.

e) The Offeror shall submit all volumes of its proposal electronically compatible with the operating system and applications defined in Sections L.1.1.2.1.2 through L.1.1.2.1.7. The Offeror should put as much proposal material as possible on each file. The Offeror is responsible for ensuring electronic proposals are virus free in accordance with Section L.1.1.2.1.4.

L.1.1.2.1.2 OPERATING SYSTEM AND APPLICATIONS

a) The proposals will be accessed utilizing the Microsoft Windows Operating System. Proposal information shall be submitted using the following applications: Microsoft Word 2016, Microsoft Excel 2016, and Microsoft PowerPoint 2016; however, letters and other signed documents shall be provided as a fully searchable Portable Document Format (.pdf) file. All documents provided as pdf shall be fully searchable. Documents embedded within a proposal volume (i.e., CPARS, etc.) shall be provided in a fully searchable format. Use of other application software for submission of proposals is prohibited except where specific instructions for non-.pdf or Office 2016 applications are provided.

L.1.1.2.1.3 HYPERLINKS

a) Offerors may use hyperlinks within and among proposal volumes.

L.1.1.2.1.4 VIRUS FREE ELECTRONIC SUBMISSION

a) Offerors are responsible for ensuring that its electronic proposal is virus free. The Offeror shall certify, in its proposal cover letter, that all electronic proposal information delivered throughout the evaluation (e.g., original proposal submission, responses to evaluation notices, Final Proposal Revisions) has been checked for viruses and certify that its files are/will be virus free. The Offeror shall specify the software, version, and virus definition used to check the data. The Offeror shall not use macro and/or script enabled files.

L.1.1.2.1.5 MULTIMEDIA

a) The Offeror shall not embed sound or video (e.g., MPEG) files within the proposal submission.

L.1.1.2.1.6 GRAPHICS

a) Large files require greater computer system resources and are discouraged. The Offeror shall not embed sound or video (e.g., MPEG) files within proposal elements. The Offeror is encouraged to:

1. Simplify the color palette used in creating figures;

2. Minimize size of graphics files; and

3. Avoid scanned images.

L.1.1.2.1.7 FILE NAMING CONVENTIONS

a) Valid extensions for files using their associated applications are listed below in Table G-1 (File Extensions):

Table G-1 File Extensions

a) The Offeror shall follow the basic structure of the file naming convention in Table G-2 (Offeror Electronic File Naming Convention) for electronic file submissions (e.g., proposal volumes, attachments, appendices), where "#" represents the sequential numbering of files (if needed), and [CAGE] represents the offeror’s CAGE code. Offerors shall keep the file name as short as possible (i.e., under 40 characters) so that the files are accessible on Government share drives. Files with longer names may become corrupt or inaccessible.

b) Offerors shall provide one folder for each volume or annex, containing all electronic files requested within the volume or annex. Please submit each volume, book, or annex as one file if possible. Offerors shall not provide each section/paragraph as separate files.

Table G-2 Offeror Electronic File Naming Convention

Table ES-1 Offeror Summary Table ES-2 Relevant Contract Summary

Vol 2 ES Tables [CAGE].xlsx and Vol 2 ES Tables [CAGE].xlsx

(where x = a or b to denote Lot 1 or Lot 2 and YY = the Contract Reference designation identified in table ES-2, L.2.2.1.2)

Annexes

Please note: The Offeror shall provide both a .pdf and .docx version if they are available. If not, a .pdf version only is acceptable.

Please note: The Offeror shall provide both a .pdf and .docx version if they are available. If not, a .pdf version only is acceptable.

Please note: Offerors shall provide both a .pdf and .docx version if they are available. If not, a .pdf version only is acceptable.

Note: * File names shall not exceed 40 characters in length inclusive of spaces and file extension.

L.1.1.2.2 PROPOSAL CONTENT AND VOLUMES

a) The Offeror shall present its proposal information in a manner that facilitates a one for one comparison between the information presented and Section L proposal instructions. Proposal information must be structured such that its paragraph numbers/letters correspond to the proposal instructions paragraph numbers/letters, although the Offeror may add lower tier sub paragraphs.

b) Each volume and annex of the proposal shall be submitted as original electronic copies as specified in Table G-3 (Proposal Structure). The Offeror shall submit all electronic copies of the proposal to the address provided in Section L.1.1.2.1.1. Suggested page counts for each volume, if any, are also specified in Table G-3 (Proposal Structure). The title and table of contents pages, as well as tables, are not included in the suggested page count. The Attachment L-3a and L-3b are considered tables, and are not included in the suggested page count. The CPARS embedded within the Volume 4 Past Performance narrative are not included in the suggested page count. The DCMA Form 640 and Summary Subcontracting Reports are not included in the suggested page count. Any glossary/acronym pages or cross-reference matrix will not be included in the suggested page count. A PWS Compliance Cross Reference Matrix is not required in this solicitation. If one is provided, it will only be used as a reference tool to facilitate review by evaluators, and any substantive content provided in the Compliance Cross Reference Matrix will not be considered in the evaluation of an Offeror. Each Lot proposed to by Offerors shall have its own set of Volumes and Annexes.

c) Information submitted as an Annex to a particular proposal volume could include manuals, specifications, plans, procedures, and company policies, as well as other information requested in Section L.2 Part B Specific Requirements and does not count towards the suggested page count.

Table G-3 Proposal Structure

1 Original

1 Original

1 Original

1 Original

As Needed

1 Original

d) Table G-4 lists the attachments provided to the Offeror within Section L.

Table G-4 Section L List of Attachments

L.1.1.2.3 PROPOSAL SUBMISSION AND PACKAGING

L.1.1.2.3.1 PROPOSAL SUBMISSION

a) All Proposals shall be UNCLASSIFIED.

b) Offerors shall clearly mark all electronic proposal submissions as identified in Section L.1.1.2.1.1 (Electronic Proposal Media).

c) Offerors shall submit electronic copies of the entire proposal in accordance with Table G-3.

d) Late Proposals: Offerors are advised that the time, identified on Block 9 of the Standard Form (SF) 33 (Solicitation, Offer and Award) of the solicitation, applies as the proposal submission date for all Volumes and Annexes of the proposal. Delivery is defined as having occurred based on the DOD SAFE’s (https://safe.apps.mil) email notification time stamp to the Janet.fondriest@navy.mil. If multiple drop-offs occur, any drop-off after the time identified on Block 9 of the SF 33 is considered “late.” Offerors are strongly encouraged to submit as early as possible to avoid any risk of late submission.

e) Offerors shall email Janet Fondriest at janet.fondriest@navy.mil within 15 minutes after proposal submittal on https://safe.apps.mil to notify of submission. The email subject shall be “FTSS V Proposal Submitted for Lot X by [CAGE]”, where X is either 1 or 2 for the Lot proposed, and [CAGE] is the proposing Offeror’s Cage Code. The Government will provide an email response identifying the proposal documents that were received. This is a courtesy extra check in an effort to help reduce incomplete proposal submission and receipt. This extra Government check and confirmation may not be performed prior to the time identified on Block 9 of the SF 33 if the Offeror fails to provide the notification email of proposal submittal as specified herein. This extra courtesy check and confirmation does not circumvent or diminish the Offeror’s responsibility for proposal submission under FAR 52.215-1(c)(3)(i).

L.1.1.2.3.2 PROPOSAL PACKAGING

a) The electronic files shall be marked “CUI”; and “Source Selection Sensitive – See FAR-2.101 and 3.104,” for the intended recipient identified in paragraph L.1.1.2.1.1.a (Electronic Proposal Media). Method of delivery shall be https://safe.apps.mil. Proposal recipients shall be Name: Janet Fondriest, Email: Janet.fondriest@navy.mil.

L.1.1.2.4 CHANGES TO RFP

a) The electronic RFP documents as posted on https://beta.sam.gov/ shall be the only official documents for the requirements of this RFP. All amendments to this RFP will be posted at https://beta.sam.gov/. Search the database for either Navy Fielded Training Systems Support (FTSS) or the RFP number: N61340-21-R-0001.

L.1.1.2.5 SOLICITATION QUESTIONS

a) The Contract Specialist identified in L.1.1.2.1.1.a is the sole point of contact for all questions and answers under this RFP.

b) Offerors shall address all questions via e-mail to the Contract Specialist identified in L.1.1.2.1.1.a, using the Attachment L-10, Solicitation Question & Answer Form Questions not submitted to this email address will not be answered.

c) Offerors shall include their Company Name, RFP Number, and Amendment Number in the subject line of the email.

d) Questions shall include the Page Number, Section Number, and Paragraph Number of the RFP that pertain to the Offeror’s questions, in the Attachment L-10, Solicitation Question & Answer Form.

e) Questions can be e-mailed any time after the notice is posted at https://beta.sam.gov; however, all questions must be received via e-mail no later than 20 days before the RFP closing date. The Government will answer all questions prior to the deadline for proposal submittal provided that those questions are received by 1400 Eastern Standard Time (EST) on the due date. The Government reserves the right not to respond to any questions received concerning this solicitation after the date above Accordingly, Offerors are encouraged to carefully review all solicitation requirements and submit questions to the Government early in the proposal preparation cycle.

f) Questions will be answered under an amendment and posted at https://beta.sam.gov prior to the RFP closing date. Offerors are cautioned not to include proprietary information in the questions because the government may release it to all Offerors.

g) Acknowledgement of receipt of questions may not be made by the Government.

h) CAUTION: Any question or request to add, remove, or revise any of the criteria in Section M will not be considered. This RFP and evaluation criteria will remain unchanged.

i) Please thoroughly review the entire RFP, including all the attachments in Section J, prior to submitting questions.

L.2 PART B SPECIFIC REQUIREMENTS

L.2.1 VOLUME 1: COVER LETTER

L.2.1.1 GENERAL

a) Offerors shall clearly identify whether they are proposing for the Lot I (Unrestricted), or the Lot II (Restricted – Small Business) effort. If any businesses desire to propose for more than one Lot, then separate and clearly identified proposals must be submitted for each Lot.

L.2.1.2 PREREQUISITES

a) Each Prime Offeror shall provide documentation to demonstrate that the Offeror meets the prerequisites listed below. The requirements will be validated on an Acceptable/Unacceptable assessment. Offerors who do not meet all of the prerequisites requirements for the Lot proposed, will be deemed UNACCEPTABLE and will be eliminated from this competition. As such, their proposal will not be evaluated.

1) Secret Facility Clearance (Lot 1 and Lot 2):

The Prime Contractor shall provide, with their proposal, evidence that they currently hold at time of proposal submission a Secret, or higher, Facility Clearance. The clearance shall be in the name of the Offeror defined as the Prime Contractor with its CAGE code identified in Block 15A on Standard Form (SF) 33, Solicitation, Offer, and Award. In the case of a Joint Venture, either the Prime JV entity with its CAGE code in Block 15A of the Offeror’s SF33 OR every JV Team Member with its CAGE code in the ES-1 Offeror Summary Table shall provide, with their proposal, evidence that they currently hold at time of proposal submission a Secret, or higher, Facility Clearance. This evidence shall be submitted with the proposal at the proposal submission date/time specified on Standard Form 33. The Secret, or higher, Facility Clearance shall be valid at time of proposal submittal. Any clearances that are pending or in process at the time of proposal submittal are not permissible and will result in an Unacceptable assessment for this Prerequisite requirement.

2) Small Business Participation Plan (Lot 1 only):

a) Each Offeror (Large and Small Businesses) proposing under Lot 1 shall provide a Small Business Participation Plan, at this acquisition phase, which addresses a strategy for utilizing SB Concerns during task order performance. The Small Business Participation Plan shall be provided in Annex B (Small Business), but the Small Business Participation Plan will be evaluated as a part of Volume 1 Cover Letter Prerequisites.

For purposes of this solicitation, the term SB Concern includes the subcategories of Veteran-Owned Small Business (VOSB), Service-Disabled Veteran-Owned Small Business (SDVOSB), HUB Zone Small Business (HUB Zone), Small Disadvantaged Business (SDB), and Women-Owned Small Business (WOSB).

The Small Business Participation Plan is separate from, but shall be consistent with, the SB Subcontracting Plan. Large Business Offerors are advised that while the SB Subcontracting Plan must be submitted to be eligible for award, the acceptability of the content of that plan is part of the responsibility determination assessment and not part of the evaluation.

The Small Business Participation Plan shall include the following elements:

1. Specific plan of action to maximize participation in all categories of SB (SB, VOSB, SDVOSB, HUB Zone, and WOSB) the Offeror will take in preparing to propose for task orders under this MAC. The Offeror shall address their FTSS-program specific outreach events and SB industry engagements planned, any planned Mentor-Protégé relationships, and specific market research tools that will be used (may include, but not limited to using websites such as the NAVAIR Office of Small Business Programs website [http://www.navair.navy.mil/osbp] and the Small Business Administration’s Dynamic Small Business Search tool [http://dsbs.sba.gov/dsbs/search/dsp_dsbs.cfm) to locate small business concerns]; and

2. Any processes improvements and/or best practices that will be implemented under this MAC to correct past inabilities to meet proposed SB goals.

L.2.2 VOLUME 2: EXECUTIVE SUMMARY

a) The following is a list of Section L Attachments that the Offeror shall utilize to provide information for this volume:

1) Attachment L-1 Executive Summary Tables

b) The purpose of the Executive Summary is to provide the Government with an overview of the Offeror’s entire proposal. Each section within the Executive Summary shall contain the salient points contained in each of the proposal volumes. In addition, this volume should be used by the Offeror to identify and highlight significant features of its proposal. The Executive Summary volume shall be divided into the areas outlined below.

L.2.2.1 Executive Summary Tables

L.2.2.1.1 Offeror Summary Table

a) The Offeror shall complete a table similar to the one below and submit it within this volume. This table summarizes the Offeror and its subcontractors’ and JV Team Members’ roles and responsibility as well as their work commitment. Subcontractors will not be evaluated. “Subcontractors” includes any entity other than a Prime Offeror or JV Team Member.

b) The Offeror shall provide a written explanation if multiple CAGE codes/DUNS are provided in the ES-1 Table. The written explanation shall detail the distinct roles and responsibilities for entities with different CAGE codes/DUNs. The description shall include all changes in the organization as a result of a corporate acquisition, reorganization, merger, or other administrative reason.

ES-1 Offeror Summary Table

Offeror:

Estimated % of Work to be Performed (must add up to 100%)

100%

L.2.2.1.2 Relevant Contract Summary Table

The Offeror shall complete the Table ES-2 (Relevant Contract Summary) provided in Attachment L-1 (Executive Summary Tables), for all contracts proposed as relevant for Past Performance and for the Technical factor (Experience). The Offeror shall identify a maximum of five (5) contract references whose performance is within three (3) years of the solicitation release date for date for the Principal Entities (see definition in M.3.1.3), identified in Table ES-1 (Offeror Summary). This means in total, a maximum of five (5) contract references may be provided for any one or combination of the Principal Entities; NOT a maximum of five (5) contract references for each Principal Entity. All contract references listed in Table ES-2 are proposed as relevant for both Technical (Experience) Volume 3 and for the Past Performance Volume 4. Offerors shall not submit contracts for other than Principal Entities because their Experience and Past Performance will not be evaluated. Complete the table according to the instructions within the attachment and submit it within Volume 2 as a separate electronic file. The contract references designated in Table ES-2 (Relevant Contract Summary) shall be used in completing Volume 4 L-3 (Contract Data). Contract references provided, that are performed by contractors other than the Offeror (such as teaming partners or subcontractors) will NOT be evaluated as prime contractor Experience or Past Performance, unless those other contractors are part of a Joint Venture Offeror as demonstrated by a signed joint venture agreement.

ES-2 Relevant Contract Summary Table

Offeror:

Referenced in:

Reference

(Technical (Experience)) Volume 4 (Past Performance)

P2

T2

L2.2.2 Contract Administration

a) The Offeror shall provide a summary of any exceptions or deviations detailed in Volume 5 Contract Administration section L.2.5.a.6.

L.2.3 VOLUME 3: TECHNICAL (EXPERIENCE)

a) The Government will use the information provided in the Volume 4 Attachment L-3a Contract Data (Lot 1) and L-3b Contract Data (Lot 2), and the associated Annex A submissions (Complete Copy of Final Versions of Previous SOO/SOW/PWSs for Past Performance and Experience), for the contract references identified in Table ES-2 (Relevant Contract Summary), to evaluate the requirements in this volume.

b) The Technical Factor is composed of Experience (Lot 1 and Lot 2). Experience relates to Corporate Experience, which is the Experience gained through contracted work at the organization level.

c) In order to receive an Acceptable rating for the Technical factor, the Offeror’s Technical proposal must meet each of the requirements in L.2.3.1.1 Contract Experience Requirements (Lot 1 and Lot 2).

L.2.3.1 Capability to Perform the Work: Evaluation Elements

L.2.3.1.1 Contract Experience Requirements

a) The Relevancy (i.e., scope, magnitude and complexity) of submitted Experience and Past Performance contract references will be determined by the government through the process discussed in subparagraphs L.2.4.3 and L.2.4.4. The Offeror shall demonstrate that the contract reference(s) identified in Table ES-2 (Relevant Contract Summary) and submitted for evaluation in Attachment L-3a Contract Data (Lot 1) and L-3b Contract Data (Lot 2) meet the Experience requirements identified below.

b) Only the contract reference(s) identified in Table ES-2, and submitted for evaluation in Attachment L-3a Contract Data (Lot 1) and L-3b Contract Data (Lot 2), and determined by the Government to be Relevant in accordance with L.2.4.c-e, L.2.4.3 and L.2.4.4, will be considered in the Experience assessment. Offerors are advised that contracts assessed as Not Relevant by the Government will not be considered in the Experience assessment.

L.2.3.1.1.1 Lot 1

a) In order to receive an Acceptable rating, the relevant contract reference(s) when combined, shall meet all eight (8) of the Experience requirements below:

1) Contract experience demonstrates having performed Simultaneous Operations at two (2) or more sites for the scope attribute COMS in at least one of the five (5) contract reference submissions. This requirement can only be fully satisfied by one of the contract references. Performance on multiple contract references cannot be aggregated to meet the requirement. The information provided in L-3a 14.a.1, L-3a 14.c.i, and Annex A for contract references found to be Relevant will be used by the government to determine whether this requirement has been satisfied.

2) Contract experience demonstrates having performed Simultaneous Operations at two (2) or more sites for the scope attribute CIS in at least one of the five (5) contract reference submissions. This requirement can only be fully satisfied by one of the contract references. Performance on multiple contract references cannot be aggregated to meet the requirement. The information provided in L-3a 14.a.2, L-3a 14.c.i, and Annex A for contract references found to be Relevant will be used by the government to determine whether this requirement has been satisfied.

3) Contract experience demonstrates having performed COMS maintenance on ten (10) or more Military Aircraft Flight Simulators in at least one of the five (5) contract reference submissions. This requirement can only be fully satisfied by one of the contract references. Performance on multiple contract references cannot be aggregated to meet the requirement. The information provided in L-3a 14.a.1, L-3a 14.c.ii, and Annex A for contract references found to be Relevant will be used by the government to determine whether this requirement has been satisfied.

4) Contract experience demonstrates having performed at a Minimum Activity Level for the scope attribute of COMS in at least one of the five (5) contract reference submissions. The Minimum Activity Level is defined as COMS average CTT or availability on one Military Aircraft Flight Simulator for eight (8) hours, or more, per day at a single site. This requirement can only be fully satisfied by one of the contract references. Performance on multiple contract references cannot be aggregated to meet the requirement. The information provided in L-3a 14.a.1, L-3a 14.c.iii, and Annex A for contract references found to be Relevant will be used by the government to determine whether this requirement has been satisfied.

5) Contract experience demonstrates having performed at a Minimum Activity Level for the scope attribute of CIS in at least one of the five (5) contract reference submissions. The Minimum Activity Level is defined as CIS average of sixty (60) hours of instruction or more per day at a single site. This requirement can only be fully satisfied by one of the contract references. Performance on multiple contract references cannot be aggregated to meet the requirement. The information provided in L-3a 14.a.2, L-3a 14.c.iii, and Annex A for contract references found to be Relevant will be used by the government to determine whether this requirement has been satisfied.

6) Contract experience demonstrates, while performing COMS or CIS, managed Service Contract Labor Standards (SCLS) Employees at two (2) or more separate CBA/WD localities simultaneously in at least one of the five (5) contract reference submissions. This requirement can only be fully satisfied by one of the contract references. Performance on multiple contract references cannot be aggregated to meet the requirement. The information provided in L-3a 14.a.1, L-3a 14.a.2, L-3a 14.c.iv, and Annex A for contract references found to be Relevant will be used by the government to determine whether this requirement has been satisfied.

7) Contract experience demonstrates, while performing COMS or CIS, managed sixty (60) or more SCLS Employees simultaneously in at least one of the five (5) contract reference submissions. This requirement can only be fully satisfied by one of the contract references. Performance on multiple contract references cannot be aggregated to meet the requirement. The information provided in L-3a 14.a.1, L-3a 14.a.2, L-3a 14.c.v, and Annex A for contract references found to be Relevant will be used by the government to determine whether this requirement has been satisfied.

8) Contract experience demonstrates a minimum of two (2) years of cumulative Prime Contractor experience for the scope attribute COMS, and a minimum of one (1) year cumulative Prime Contractor experience for the scope attribute CIS, within the three (3) years prior to the solicitation release date. The two (2) years of cumulative COMS and the one (1) year of cumulative CIS experience can be demonstrated through one (1) of the five (5) contract references, or the accumulation of multiple contract references.

The information provided in L-3a 11 & 12, L-3a 14.a.1, L-3a 14.a.2, and Annex A for contract references found to be Relevant will be used by the government to determine whether this requirement has been satisfied.

L.2.3.1.1.2 Lot 2

a) In order to receive an Acceptable rating, the relevant contract reference(s) when combined, shall meet both of the Experience requirements below:

1) Contract experience demonstrates, while performing COMS or CIS managed fifteen (15) or more SCLS Employees simultaneously in at least one of the five (5) contract reference submissions. This requirement can only be fully satisfied by one of the contract references. Performance on multiple contract references cannot be aggregated to meet the requirement. The information provided in L-3b 14.a.1, L-3b 14.a.2, L-3b 14.c.i, and Annex A for contract references found to be Relevant will be used by the government to determine whether this requirement has been satisfied.

2) Contract experience demonstrates a minimum of two (2) years of cumulative Prime Contractor experience for the scope attribute COMS, and a minimum of one (1) year cumulative Prime Contractor experience for the scope attribute CIS, within the three (3) years prior to the solicitation release date. The two (2) years of cumulative COMS and the one (1) year of cumulative CIS experience can be demonstrated through one (1) if the five (5) contract references, or the accumulation of multiple contract references.

The information provided in L-3b 11 & 12, L-3b 14.a.1, L-3b 14.a.2, and Annex A for contract references found to be Relevant will be used by the government to determine whether this requirement has been satisfied.

L.2.4 VOLUME 4: PAST PERFORMANCE

a) The following is a list of Section L Attachments that the Offeror shall utilize to provide information for this volume:

Statement A Contractor Operation and Maintenance Services (COMS)

5) Attachment L-5 FTSS V Representative Historical Requirement Performance Work Statement B Contractor Instructional Services (CIS)

b) The Government will use the information provided in the Volume 4 Attachment L-3a Contract Data (Lot 1) and L-3b Contract Data (Lot 2), and the associated Annex A submissions (Complete Copy of Final Versions of Previous SOO/SOW/PWSs for Past Performance and Experience), for the contract references identified in Table ES-2 (Relevant Contract Summary), to evaluate the Relevancy requirements (Sections L.2.4.c-e, L.2.4.3 and L.2.4.4) in this volume.

c) The Offeror shall identify a maximum of five (5) contract references whose performance is within three (3) years of the solicitation release date for date for the Principal Entities (see definition in M.3.1.3), identified in Table ES-1 (Offeror Summary). The contract references identified shall be the same for this Past Performance Volume 4 and for the Technical (Experience) Volume 3. Offerors shall not submit contracts for other than Principal Entities because their Experience and Past Performance will not be evaluated. Submitted contracts shall be from a CAGE code/DUNS that is the same as the Principal Entities proposed in Table ES-1 (Offeror Summary). Offerors shall also identify any contracts, task orders, or delivery orders within three (3) years of the solicitation release date that had any show-cause notices, cure notices, or termination for default and shall provide copies of these documents in Volume 4. The Offeror shall complete Table ES-2 (Relevant Contract Summary for Past Performance and Experience) provided in Attachment L-1 (Executive Summary Tables), for all contracts proposed for Past Performance and Experience. All contract references shall be numbered the same throughout all of the Offeror’s proposal volumes (i.e. the contracts identified as P1, P2, etc.).

d) Task or delivery orders awarded under Multiple-Award Contracts (MACs) will be considered standalone “contracts” for purposes of past performance and experience evaluations. Thus, Offerors may not propose an entire MAC as a past performance or experience contract reference. Individual Task or Delivery Orders are considered separate contract references, regardless if the Offeror performed as a Prime or Subcontractor.

e) In Annex A (Final Versions of Previous Statement of Work (SOW)/Performance Work Statement (PWS)/Other Supporting Documentation for Past Performance and Experience), the Offeror shall provide the following for each contract or delivery/task order reference identified in Table ES-2 (Relevant Contract Summary): a complete copy of the contractually executed final version of the substantiating documents (drafts are not acceptable) including the most recent conformed copy of the contract, and statement of work (SOW) or performance work statement (PWS). Other supporting documentation may also be provided. Together these documents must clearly demonstrate the similarity of the scope, magnitude and complexity performed by the Offeror on the contract reference to the solicitation requirements. The Offeror shall also provide Annex A supporting documents that clearly substantiate performance of the Technical (Experience) Contract Experience Requirements in Volume 3 for the Lot proposed. Annex A references shall be provided in fully searchable electronic format. For contract references that contain delivery/task orders, additionally provide the work description for each specific delivery/task order. For contract references where the Offeror performed as a subcontractor, the Offeror shall also provide a complete electronic copy of the SOW/PWS or other documentation of the agreement between the prime and subcontractor that clearly defines the portions of the work effort of the Prime’s SOW/PWS that the Offeror performed as a subcontractor. A requirement not specifically identified in the SOW/PWS or otherwise supported through documents as discussed herein may not clearly reflect the level of scope, magnitude, and complexity performed by the Offeror.

f) Any submitted contract reference must contain performance within three (3) years of the solicitation release date. Offeror shall provide all CPARS within the three (3) year Recency period for each of its submitted past performance references. The CPARS shall be provided embedded within the Volume 4 Past Performance narrative, not as separate files, and not as a part of Annex A. The embedded documents shall be provided in a fully searchable format. Contract Performance Assessment Reporting System (CPARS) and Questionnaires will be the primary customer feedback data used to evaluate the Offeror’s past performance. The Past Performance Information Reporting System (PPIRS) will be the primary method used to validate the CPARS provided for this source selection and to retrieve available CPARS within the Recency period that were not provided.

g) For all active contracts identified where the CPARS ended more than six months ago, the Offeror shall forward Attachment L-9 (CPARS Update Questionnaire) to that contract’s Procuring Contracting Office (PCO), Administrative Contracting Officer (ACO), Program Manager (PM), and any additional points of contact (POC) that can provide an assessment on the Offeror’s proposed past performance effort. The Offeror shall complete section 1 of the L-9 prior to forwarding to the PCO, ACO, PM, and other POCs. Please forward all applicable questionnaires within two weeks from this solicitation’s release date to allow adequate time for the recipient to respond. Note that the Offeror should not reference this solicitation’s number when distributing the contractor performance assessment questionnaires to customers. The Offeror shall include instructions for the customers to send completed questionnaires within two weeks of its receipt via e-mail to the PCO/Contract Specialist, identified in L.1.1.2.1.1.a (Electronic Proposal Media). The Offeror shall ensure that all points of contact are current and include an email address and phone number. The Offeror shall not conduct follow-up actions with regard to this questionnaire, other than to confirm receipt by the recipient.

h) For all contracts identified that do not have a completed CPARS, the Offeror shall forward a copy of Attachment L-2 Contractor performance assessment questionnaire to that contract’s Procuring Contracting Officer (PCO), Administrative Contracting Officer (ACO), Program Manager (PM), and any additional points of contact (POC) that can provide an assessment on your proposed past performance effort. Please forward all applicable questionnaires within two weeks from this solicitation’s release date to allow adequate time for the recipient to respond. Note that the Offeror should not reference this solicitation’s number when distributing the contractor performance assessment questionnaires to customers. The Offeror shall include instructions for the customers to send completed questionnaires within two weeks of its receipt via e-mail to the PCO/Contract Specialist, identified in L.1.1.2.1.1.a (Electronic Proposal Media). The Offeror shall ensure that all points of contact are current and include an email address and phone number. The Offeror shall not conduct follow-up actions with regard to this questionnaire, other than to confirm receipt by the recipient.

i) The Government may contact customers identified by the Offeror to obtain follow-up Past Performance Information as needed. If the Government identifies any recent, relevant contracts not included in the Offeror’s Past Performance volume, e.g. relevant efforts within the FTSS III and FTSS IV MACs, the Government reserves the right to include Past Performance information from those contracts in its evaluation.

j) Offerors are reminded that the Government reserves the right, but is not required to, use information to evaluate past performance obtained from sources other than those identified by the Offeror including, but not limited to, the Past Performance Information System (PPIRS), the Federal Award Performance and Integrity Information System (FAPIIS), the System for Award Management (SAM), and Electronic Data Access (EDA). The Government may send additional questionnaires and/or obtain information from other sources.

k) Any contractor performance documentation not provided in this volume and not otherwise requested by the Government will not be evaluated in the Relevancy, Experience or Past Performance Assessments. The Government is only interested in the performance contract references and will give no consideration to an offeror’s self-described assertions of relevancy or demonstrated performance.

L.2.4.1 Past Performance Information Point of Contact

a) In accordance with FAR 15.306, the Offeror may be given the opportunity to discuss adverse past performance information obtained from any questionnaire if they have not previously responded through Contractor Performance Assessment Reporting System (CPARS) or similar system. However, the names of individuals providing the information shall not be disclosed. Adverse past performance is defined as past performance information that supports a less than satisfactory rating from sources where the information is from other than formal rating systems such as Federal Awardee Performance and Integrity Information System (FAPIIS). Any such exchanges are Clarifications, and do not constitute discussions. Any Past Performance information that requires further coordination will be with the Principal Entity Point of Contact identified in Volume 5 – Contract Administration.

L.2.4.2 Authorization Letter(s)

a) The Offeror should submit a signed “Release of Adverse Past Performance Authorization Letter(s)” with…