T-ATS_Pre-Proposal_Conference_Minutes.pdf

N00024-17-R-2207 Towing, Salvage, and Rescue Ship

Pre-Award Conference 11:00 AM - 12:30 PM EST, April 18, 2017

I. Introductions of NAVSEA personnel (Roxie Thomas)

a. Roxie Thomas – Contracting Officer

b. Brenda Uyeda – Contract Specialist

c. Kathy Andrias – Legal Counsel

d. Paul Conroy – T-ATS Principle Assistant Program Manager

e. Chris Paulus – Assistant Program Manager

f. Misha Heard – Project Manager

g. Jeff Fink – Ship Design Manager

II. Purpose of the call (Roxie Thomas)

Per FAR 15.409 (a) a pre-proposal conference may be held to brief prospective Offerors after a solicitation has been issued but before the offers are submitted. The purpose of this voluntary Pre- Proposal Conference Call is to provide an “Informal” forum for interested parties to ask questions and gain clarifications on the requirements identified in the RFP documents posted to FBO on 31 March 2017. You are advised that:

(1) Remarks and explanations during this conference shall not qualify the terms of the solicitation

(2) Attendees should not rely on verbal communications for information regarding the RFP; and

(3) Terms of the solicitation and specifications remain unchanged unless the solicitation is amended in writing.

III. Question and Answer (Roxie Thomas)

a. You may, but are not required to, ask questions in this forum. Questions will be accepted via email per the RFP. You may email questions directly to the following individuals during the call for review and consideration: brenda.uyeda@navy.mil and misha.j.heard@navy.mil

b. If you choose to ask questions on the conference call, do not identify yourself or your company.

c. All questions will be noted and answers will be published via an amendment per the RFP.

IV. General Information:

a. To ensure that a fair and competitive environment is maintained please DO NOT identify yourself or company at any point or time during the call.

b. Proposal due date is May 31 at 2:00 PM Eastern Time. Please allow time for proposals to arrive. If the proposal is late, even by a minute, it will not be accepted.

c. Award is anticipated Sept 2017

d. Offerors are advised that per the RFP the Government intends to make an award on the basis of initial proposals without conducting discussions with Offerors, but reserves the right to mailto:brenda.uyeda@navy.mil mailto:misha.j.heard@navy.mil conduct discussions if it is later determined by the Contracting Officer to be necessary (per FAR 52.215-1(f)(4)). Therefore, each initial offer should contain the Offeror’s best terms from a price and technical standpoint.

e. Statements and representations made in the Offeror’s proposal may be subject to verification by DCAA or others, or through an onsite survey by Navy evaluators.

f. There has been 1 Amendment to the RFP which contained the 3 domestic sourcing Q&As.

g. The Government reserves the right to conduct a pre-award survey or to require other evidence of technical, production, managerial, financial, and similar abilities to perform the required work prior to the award of a contract.

h. The deadline for receipt of questions is 21 April 2017. Any questions received after the deadline may not be answered prior to date for receipt of proposals.

V. Submission Requirements: (Roxie Thomas)

a. Proposals shall be submitted in two (2) separate volumes as described in Section L of the RFP

VI. Request for Proposal overview; the following items were highlighted to ensure proper attention is paid to all relevant portions of the RFP.

a. Section B (Chris Paulus)

i. Data License; please review carefully and work with the owners of your designs for this portion of the RFP.

b. Section C (Chris Paulus)

i. C4I Suite; will be installed by the Government; COR describes what shall be provided by

Offerors for the space.

ii. Cybersecurity

c. Section F (Chris Paulus)

i. Delivery dates; corresponds with Section L requirements for Delivery Schedule

d. Section H (Chris Paulus)

i. Economic Price Adjustment; self-explanatory, but please submit questions if unfamiliar with this

e. Section J (Chris Paulus)

i. Circular of Requirements

1. Desired Features; these are not mandatory and the evaluation method for Desired Features (Appendix B of the COR) is described in Sections L & M

VII. Price proposal overview (Brenda Uyeda)

a. Sections L & M

i. Section L is where you will find the instructions for formatting, organizing and submitting your proposal

ii. Section M is where you will find the criteria that will be used to determine the successful offeror

iii. If all required information is not included, your proposal may be deemed non-responsive

iv. Financial volume must be completely filled out and signed by the Offeror. All rates must be clearly entered in dollars and cents. These prices cannot be contingent on any other factors or conditions.

v. Financial Data - The Offeror shall include in its proposal the information requested in Attachment J-17. No award will be made unless the contracting officer makes an affirmative determination of responsibility. In the absence of information clearly indicating that the prospective contractor is responsible, the contracting officer will make a determination of nonresponsibility

b. Value Adjustments

i. Per Section M in order to maximize the achievement of program objectives, the

Government will adjust the Offeror’s Total Proposed Price (TPP) to arrive at a Total Evaluated Price (TEP) if the Offeror has included any of the Desired Capabilities described in Appendix B of the T-ATS COR, Attachment J-1 in the Offeror’s Proposed T- ATS Baseline Design.

ii. The following adjustments are the only adjustments that will be made to the Government’s price reasonableness assessment.

iii. The TEP is for evaluation purposes only and does not affect the Offeror’s proposed price or the resulting contract award amount.

iv. Adjustments based on the Desired Capability in COR and listed on page 167 of 169 listed cannot be used to lower the Offeror’s proposed price in order to achieve the maximum award amount.

c. Performance and Payment Bonds

i. The Government reserves the right to require Performance Bonds and/or Payment

Bonds in accordance with FAR 52.228-16. The Offeror shall acknowledge that this requirement may be levied by the Contracting Officer prior to award.

d. Step Ladder Pricing (Amendment 0002)

i. The Government is looking to add flexibility to the contract should funding become available and the Government can award more than one ship per year. This could result in adding stepladder pricing to Option years 3, 4, 5 and 6 for 2 ships. This will be addressed in a future RFP modification.

VIII. Technical Proposal Overview (Chris Paulus/Jeff Fink)

a. Parent Design; it is your responsibility to show how your Parent Design meets the 3 key requirements.

b. Contractor’s Ship Specification and COR Traceability Matrix

i. Examples given by Jeff Fink as to what level of detail the government is expecting.

ii. Offeror’s proposal shall clearly align contractor’s ship specification to the COR traceability matrix for evaluation.

iii. This will be an integral part of the contract once mapped out.

c. Performance Schedule; will become a part of the contract.

IX. Closing Remarks (Roxie Thomas)

a. Thank you

b. You are responsible for ensuring that Past Performance Questionnaires are submitted by the proposal due date; Questionnaires must come from vendors/customers directly to the Contracting Officer and may not be gathered by Offerors to submit on behalf of those filling them out, so please follow up with them as needed.

c. Leave yourself plenty of time to respond.

d. Read the requirements of the RFP. Your proposal must be based on the March 31 RFP; do not rely on your knowledge of the Draft RFP to respond to this solicitation.

X. Forum was opened up for questions. Five questions were asked and answered. They are included in the Q&A amendment to this RFP.