Proposal_Requirements.pdf

SOURCE SELECTION INFORMATION

SEE FAR 2.101 AND 3.104

FOR OFFICIAL USE ONLY

SOURCE SELECTION INFORMATION

SEE FAR 2.101 AND 3.104

FOR OFFICIAL USE ONLY

SSP Attachment 3

PROPOSAL REQUIREMENTS

A. The following instructions cover the preparation and submittal of the offeror’s proposal for this solicitation. To assure timely and equitable evaluation of proposals, offerors must follow the instructions contained herein. Offerors are cautioned that any noncompliance with the terms and conditions of the RFP may cause their proposal to be determined to be unacceptable and therefore not considered eligible for award. If a joint venture arrangement exists for this acquisition, the offeror shall provide a copy of the joint venture agreement that is signed and dated by all joint venture members as part of the proposal submission. Offerors shall submit only one proposal for the proposed effort. No additional proposals (i.e., one offeror submitting two proposals based on differing approaches) shall be submitted. The Government will review only one proposal per offeror. Initial proposal Proposals shall be submitted to the Government in (2) separate volumes as set forth below:

PAGE NUMBER

VOLUME LIMITS OF COPIES DESCRIPTION

I N/A 1 Electronic/2 Paper* Completed RFP and Clauses and a Copy of Joint Venture Agreement

(If applicable)

II 30 1 Electronic/3 Paper Written Technical Proposal

*Electronic copies shall be submitted in accordance with RFP Attachment 1, Electronic Format for All Proposal Volumes. Proposals shall be submitted in written form (paper) and digital form (CD-R or DVD- R)* (write once/read only) that is closed so that no further writes can be made to the media. CD-R/W or DVD-R/W media types are not acceptable. Media must be virus scanned by the offeror prior to submittal to the Government. For electronic copies, indicate on each CD-ROM the volume number and title.

In addition to the page limitations set forth above, proposals should comply with the following format:

(1) The sealed RFP package used to submit the proposal package must show the time and date specified for receipt. Each volume shall be marked with the RFP number and the offeror’s name and address, and the number of the Volume, i.e. I, II. Proposals shall be in the English language and all monies shall be proposed in United States dollars.

(2) Print shall be no smaller than a font size of 12 and should be on 8 1/2 x 11 inch paper, excluding any charts, graphs, drawings, diagrams, supporting illustrations, or spreadsheets, etc. Charts, graphs, drawings, diagrams, supporting illustrations, spreadsheets, etc. shall not be greater than 11” x 17”.

Double-sided printing shall count as (2) pages. Charts, graphs, drawings, diagrams, supporting illustrations, spreadsheets, etc. may be on fold-out pages, but must fold with the page size specified and

FOR OFFICIAL USE ONLY

SOURCE SELECTION INFORMATION

SEE FAR 2.101 AND 3.104

FOR OFFICIAL USE ONLY

will count as one page and shall not be greater than 11” x 17”. Each volume within the proposal shall be separately tabbed and identified. Margins shall be no smaller than 1 inch and each page within a volume (electronic and written copies) shall be numbered consecutively. Elaborate formats, bindings, or color presentations are not desired or required.

(3) The page limitation for Volume II, Written Technical Proposal, is 30 pages. The page limitation includes any charts, graphs, drawings, diagrams, supporting illustrations, spreadsheets, etc., but excludes any cover page, table of contents or list of acronyms (if utilized). A page is defined as each face of a sheet of paper containing information. Offerors are cautioned that any pages that exceed the page limitations shall not be read but shall be removed and either retained in the contract file without being considered in the evaluation, or, sent back to the offeror. The content and page size of electronic copies must be identical to the hard copies. When submitting proposals and attachments, file suppression utilities to include but not limited to zip files will not be accepted. In the event that hard copies and electronic copies of a proposal are submitted and if there are any discrepancies between the hard copies and the electronic copies of the proposal, the hard copies will be used for evaluation.

(4) Page limitations may be placed on Evaluation Notices (ENs), if issued. The specified limits for EN responses will be identified in the letters forwarding the ENs to the offerors or on the EN form itself.

(5) Each page containing proprietary information should be so marked.

(6) Each page should contain the following legend at the bottom of each sheet:

SOURCE SELECTION INFORMATION--SEE FAR 2.101 and 3.104

FOR OFFICIAL USE ONLY

(7) Submission of the initial proposal packages via electronic mail will not be accepted.

Initial proposal packages shall either be mailed or hand-delivered.

Offerors are cautioned that Warner Robins Air Logistics Complex has visitor control procedures requiring individuals not affiliated with the installation to obtain a visitor pass prior to entrance. Some delay should be anticipated when hand-delivering proposal packages. Offerors should allow for sufficient time to obtain a visitor pass and arrive at the specified office PRIOR to the time specified for receipt of proposals. Contact Tim Hudson (478) 222-1755 or Davey Eades (478) 222-1877 to coordinate all hand-delivered proposals.

Communications:

Exchanges of source selection information, before and after submission of the initial proposal packages, between the Government and offerors, will be controlled by the Contracting Officer. Email may be used to transmit such information, preferably with the email can be sent encrypted, and must include “Source Selection Information – See FAR 2.101 and 3.104” in the subject line of the email. Otherwise, source selection information will be transmitted via direct mailing or facsimile. In order to facilitate the sending

FOR OFFICIAL USE ONLY

SOURCE SELECTION INFORMATION

SEE FAR 2.101 AND 3.104

FOR OFFICIAL USE ONLY

and receiving of encrypted emails, offerors must use MS Outlook email configured to support encryption or a different email product that is S/MIME compatible and configured to support encryption. If you intend to submit your source selection information via encrypted email, you will need to contact the Buyer/Contracting Officer indicated on the face page of the solicitation prior to that first submittal in order to exchange certificates used for encryption. To insure the process is working correctly, send a test encrypted message first (without including any source selection information). If an offeror’s computer system cannot support encryption technology, the offeror shall send the Contracting Officer correspondence at the time that it submits its proposal stating that it accepts the risk of sending and receiving unencrypted electronic mail if it chooses to utilize unencrypted email as a channel of communication. When submitting source selection information via email, file suppression utilities, to include but not limited to zip files, will not be accepted.

B. Volume I, Completed RFP and Clauses (including Copy of Joint Venture Agreement if applicable) shall consist of the completed and signed RFP with a cover letter delineating any exceptions taken to the RFP terms and conditions with accompanying rationale. However, offerors are cautioned that any noncompliance with the terms and conditions of the RFP may cause their proposal to be determined unacceptable and therefore not considered eligible for award. Offerors shall ensure that all clauses and provisions that require “fill-in” information are appropriately completed, including the proposed prices associated with the contract line items in the Schedule of the RFP.

The Government intends to award without discussions, but reserves the right to conduct discussions if determined necessary. Any discussions will be conducted in accordance with FAR 15.306. Proposals must be received by Support Eqpt-Services AFLCMC/WNKAC 235 Byron Street, STE 19A, Bldg 300, Attention: Davey Eades or Timothy G. Hudson, no later than 4:00 PM, Eastern Daylight Savings Time.

21 Apr 2017

C. Volume II, Written Technical Proposal:

1. The written technical proposal shall be clear, concise, and include all the information required by this provision in sufficient detail for effective evaluation. The proposal should not simply rephrase or restate the Government’s requirements, but rather shall provide convincing rationale to address how the offeror intends to meet these requirements. Offerors shall assume the Government has no prior knowledge of their capabilities, work processes, facilities, and experience and will base its evaluation on the information presented in the offeror’s technical proposal.

2. The following information shall be provided in the written technical proposal and will be evaluated to assess technical acceptability in accordance with, Evaluation Basis for Award provision. The written technical proposal shall address each of the following subfactors to describe the offeror’s proposed approach to performing the requirements set forth in the Commercial Item Description A-A- 59932, dated 24 June 2016 and any revisions.

FOR OFFICIAL USE ONLY

SOURCE SELECTION INFORMATION

SEE FAR 2.101 AND 3.104

FOR OFFICIAL USE ONLY

Subfactor One: Performance. Each offeror’s written technical proposal shall provide a complete and detailed narrative specifically addressing the offeror’s proposed approach to meeting all the requirements mandated by CID A-A-59932 in each of the following paragraph(s):

2.7 Performance.

2.7.1 Payload.

2.7.2 Towing capacity.

2.8 Mobility.

2.8.5 Brakes.

Each offeror shall provide detailed explanations and rationale of how each offeror intends to meet the following sub-paragraph requirements of 2.8: (a) Maximum speed (b) Gravel roads (c) Cross-country terrain (d) Acceleration (e) Clearances (f) Gradeability (g) Ramp negotiation (h) Side slope negotiation (i) Turning diameter (j) Steering force (k) Parking brakes (l) Service brakes.

Each offeror’s written technical proposal shall include in their response:

1. A detailed explanation and rationale of how each of the requirements is met when the vehicle is at maximum GVWR.

2. A detailed explanation and rationale of how each of the requirements is met when the vehicle is at maximum GVWR with a fully loaded trailer, to comply with 2.7.1 and 2.7.2 of CID A-A-59932.

Explanation shall include drawings and schematics, where applicable, that are clear, legible, easy to follow, and appropriately labeled.

Subfactor Two: Common Remote Operated Weapon Station (CROWS) Compatibility. Each offeror’s written technical proposal shall provide a complete and detailed narrative specifically addressing the offeror’s proposed approach to meeting all the requirements mandated by CID A-A-59932 in each of the following paragraph(s):

2.12 Turret and hatch.

2.12.1 Gun mount.

2.12.2 Gunner’s seat.

2.12.3 Gunner’s visibility and protection.

2.13 CROWS compatibility.

Each offeror’s written technical proposal shall include in their response:

1. An engineering analysis to demonstrate the integration of the CROWS on the vehicle including, but not limited to, detailed explanations of the design approach and clear, legible and properly scaled drawings depicting the installation process.

2. An engineering analysis to demonstrate the integration of the turret and Gunner’s system including, but not limited to, detailed explanations of the design approach and clear, legible and properly scaled

FOR OFFICIAL USE ONLY

SOURCE SELECTION INFORMATION

SEE FAR 2.101 AND 3.104

FOR OFFICIAL USE ONLY

drawings depicting the assembly process. The analysis shall detail the compatibility of the Gunner’s system with the vehicle if the CROWS is not assembled on the vehicle.

3. Documentation of test results, if the offeror has previously installed CROWS on the vehicle. If CROWS has previously not been installed, test results are not required. Explanation shall include drawings and schematics, where applicable, that are clear, legible, easy to follow, and appropriately labeled.

Subfactor Three: Armor. Each offeror’s written technical proposal shall provide a complete and detailed narrative specifically addressing the offeror’s proposed approach to meeting all the requirements mandated by CID A-A-59932 in each of the following paragraph(s):

2.15 Armor and ballistic protection.

Each offeror’s written technical proposal shall include in their response:

1. A detailed explanation of the design approach to show the armor’s performance against various caliber rounds.

2. A detailed explanation of the design approach of how the armor will be integrated onto the chassis including, but not limited to, an illustrated parts breakdown of the armor panels to demonstrate how the cab will be protected.

3. Material specifications supporting the requirements (including but not limited to type of metal and mechanical characteristics)

4. Certifications and/or test results, if the offeror has previously armored the vehicle. If the offeror has not previously armored the vehicle, certifications and/or test results are not required.