FRFP-014-019.pdf

FINAL RFP QUESTION/RESPONSE FORM

N61340-18-R-1199, Attachment 6

IDENTIFY IF PROPRIETARY: N/A

SPECIFIC QUESTION

Is there a requirement to return a signed copy of the SF 33 Solicitation N61340-18-R-1199 and any signed Amendments to the Solicitation as part of Volume 2 – Contract Administration?

REFERENCE DOCUMENT: FINAL RFP; Section L., Instructions to Offerors.

PAGE NUMBER: 87 and 88 of 91

GOVERNMENT RESPONSE

Yes. Please refer to Amendment 0001, Section L, Volume 2 – Contract Administration, paragraph 2.5.

FOR GOVERNMENT USE ONLY: CONTROL NUMBER: FRFP-014

PREPARED BY: DATE:

Per Amendment 001, Section L, Volume 2 – Contract Administration, states:

2.1 Model Contract Documents: The Offeror shall provide the model contract documents as a separate electronic file and as a separate section in this volume. In the event there is any discrepancy between these contract documents and any other volume, Volume 2 (Contract Administration) shall take precedence. The Offeror shall provide the following documents within this section:

a. Original signed SF33 (Solicitation, Offer, and Award) cover page of the solicitation and a signed SF30 cover page of each amendment (as applicable) with all applicable Blocks completed and acknowledgement of receipt of each amendment (as applicable) to this solicitation. The SF-33 Block 12 “fill-in” (proposal validity date) shall be completed to read “250” (valid 250 days from proposal due date); and

b. Signed Representations, Certifications, and Acknowledgements or Online Representations and Certifications Application (ORCA) reference.

Question: Is return of documents in 2.1 a. and b. for this volume sufficient or does the government require the contractor to resubmit the Final RFP (Sections B through M) as part of this Model Contract requirement?

REFERENCE DOCUMENT: FINAL RFP; Amendment 0001, Section L., Instructions to Offerors, Amend PAGE NUMBER: 15 of 16

An offeror shall submit a signed SF33 and signed SF30, as applicable. An offeror will not submit the Final RFP (Sections B through M) as part of this Model Contract requirement.

FOR GOVERNMENT USE ONLY: CONTROL NUMBER: FRFP-015

Per Amendment 001, Section L, Volume 1 – Technical; paragraph 1.3.4 states:

1.3.4 Cumulative Aircraft Maintenance Experience

The Offeror shall demonstrate (using authoritative documentation regarding contract performance) that the contract reference(s) identified in Table T-2 (Contract Summary) and submitted for evaluation in Table T-3 (Contracts for Aircraft Maintenance Experience) contain a minimum of three years of cumulative aircraft maintenance experience within the five years prior to the solicitation release date. Specifically, the Offeror is required to provide contract reference(s) demonstrating a minimum of three years of cumulative aircraft maintenance experience meeting all of the requirements identified in element 1.3.1 (Contract Reference Requirements) and 1.3.2 (Aircraft Maintenance Experience Requirements) and 1.3.3 (Management Experience Requirement) within five years of the solicitation release date. The three years of cumulative aircraft maintenance experience can be demonstrated through one contract reference or the accumulation of multiple contract references.

However, the 1.3.4 section goes on to say that this is not an accumulation of multiple contracts (i.e. P1, P2, P3 etc) but a stand-alone count of consecutive years/months of maintenance experience for EACH contract. It states:

“Cumulative aircraft maintenance experience is calculated based on the number of years and months of experience each contract reference (e.g., P1, T1) provides meeting all of the requirements identified in Evaluation Elements 1.3.1 (Contract Reference Requirements) and 1.3.2 (Aircraft Maintenance Experience Requirements), and 1.3.3 (Management Experience Requirement) within five years of the solicitation release date. “

Question 1: The underlined Section L instructions seem contradictory. Is the requirement for consecutive and cumulative maintenance experience per contract or accumulated over all contracts cited in T-2?

Question 2: If a contract (P1) that finished within the five years of the solicitation release date of 19 July 2018, has over 3 years of consecutive maintenance (See Table T-3 Item 16) but the duration of those years began prior to 19 July 2013 (e.g. an example where the maintenance POP is from 19 May 2012 to 19 June 2017) , should the value reflected as “cumulative” for this contract be shown as 5 years and 1 month, or does the clock only begin on 19 July 2013, making this contract’s cumulative maintenance experience only 3 years and 11 months?

REFERENCE DOCUMENT: FINAL RFP; Amendment 0001, Section L., Instructions to Offerors, Amend PAGE NUMBER: 15 of 16

1) Per Section L of the solicitation, contract reference(s) are NOT required to be consecutive. The three years of cumulative aircraft maintenance experience can be demonstrated through one contract reference or the accumulation of multiple contract references. Cumulative aircraft maintenance experience is calculated based on the number of years and months of experience each contract reference (e.g., P1, T1) provides meeting all of the requirements identified in Evaluation Elements 1.3.1 (Contract Reference Requirements) and 1.3.2 (Aircraft Maintenance Experience Requirements), and 1.3.3 (Management Experience Requirement) within five years of the solicitation release date.

2) Per Section L of the solicitation, “The Offeror shall demonstrate (using authoritative documentation regarding contract performance) that the contract reference(s) identified in Table T-2 (Contract Summary) and submitted for evaluation in Table T-3 (Contracts for Aircraft Maintenance Experience) contain a minimum of three years of cumulative aircraft maintenance experience [within the five years prior to the solicitation release date].”

FOR GOVERNMENT USE ONLY: CONTROL NUMBER: FRFP-016

IDENTIFY IF PROPRIETARY:

In Section L 2.1.2 (Operating System and Application) the government states that “…Proposal information shall be submitted using the following applications: Microsoft Word 2016, Microsoft Excel 2016, Microsoft PowerPoint 2016, and Microsoft Project 2016…”

Will the government accept Microsoft Word 2013, Microsoft Excel 2013, Microsoft PowerPoint 2013, and Microsoft Project 2013 since both versions are compatible and both produce .docx files?

REFERENCE DOCUMENT: CMMARS_Released_RFP_Final.docx

PAGE NUMBER: 76 of 91

PARAGRAPH: 2.1.2 Operating System and Applications

The Government updated the instructions in Section L under Amendment 0001 to the solicitation.

FOR GOVERNMENT USE ONLY: CONTROL NUMBER: FRFP-017

RFP Table G-2 The offeror is required to have a naming convention of Vol 1 Tech#.docx. However, there are no requirements to respond to for this to be a stand-alone document only requirements for completion of the T-1, T-2, and T-3 tables which have their own naming conventions.

Question: Will the Government please clarify as to what the offeror is to provide in the stand-alone document of Vol 1 Tech#.docx?

REFERENCE DOCUMENT: Table G-2

PAGE NUMBER: 078

PARAGRAPH:

GOVERNMENT RESPONSE

Under the Technical Volume 1, the only Technical element requiring a narrative is 1.3.3 (Management Experience Requirement).

It is the Offeror’s discretion to determine if a narrative is necessary or helpful for the other elements. For example:

• If a narrative statement would be helpful for the Technical team to be able to assess the documents provided in Annex A;

• If the CAGE code of a contract reference (e.g., P1 or P4) does not match, then such a statement could be included in a narrative response to 1.3.1.b., referring the Technical team to section 1.2.2b. or 1.2.2.c. for an explanation;

and/or

• If more than one contract reference is used to meet the requirements in 1.3.4, the Offeror could choose to provide a list of the contract references submitted that meet all of the requirements identified in element 1.3.1 (Contract Reference Requirements) and 1.3.2 (Aircraft Maintenance Experience Requirements) and 1.3.3 (Management Experience Requirement) within five years of the solicitation release date that includes the number of years and months of experience each contract reference provides.

FOR GOVERNMENT USE ONLY: CONTROL NUMBER: FRFP-018

Section L requires electronic submission in addition to the hard copy submission. While the RFP provide mailing addresses for the POCs, the RFP does not provide the email addresses for Lisa Nelson or Brianna Shaw.

Please provide the email addresses for offeror submission.

Additionally, please provide contact phone numbers as we typically give these numbers to the delivery companies in case they have access issues or there is no one to sign for the documents.

REFERENCE DOCUMENT: RFP

PAGE NUMBER: 78

PARAGRAPH: 4.1

The email address and phone number of the PCO are provided on the Standard Form (SF) 33 of the solicitation. The paper original, paper copy, and all electronic copies of the proposal (on the CD-ROM disks) shall be submitted in accordance with paragraph 4. [Proposal Submission and Packaging] instructions of the solicitation. Offeror’s are reminded proposals shall not be submitted by facsimile or email.

FOR GOVERNMENT USE ONLY: CONTROL NUMBER: FRFP-019