Revised_Instructions_to_Offerors.pdf

ADDENDUM

52.212-1 INSTRUCTIONS TO OFFERORS – COMMERCIAL ITEMS

A. The following instructions cover the preparation and submittal of the offeror’s proposal for this solicitation. Non-conformance with any instructions provided below may result in an unfavorable proposal evaluation. Proposals shall be submitted to the Government in two (2) separate volumes as set forth below:

PAGE NUMBER

VOLUME LIMITS OF COPIES DESCRIPTION

I N/A 1 electronic copy Completed RFQ with pricing

II 50 1 electronic copy Technical Proposal

Completed RFQ with pricing and Technical Proposal shall be submitted in electronic format through AMRDEC SAFE following the Communications paragraph below.

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

(1) Print shall be no less than 12 point and page size shall be 8.5 x 11 inches.

(2) Margins shall be no smaller than 1 inch on the top and bottom and 3/4-inch side margins.

(3) Pages shall be numbered sequentially by volume. Offerors are cautioned that any pages exceeding the limitations set forth above will not be read or considered in the evaluation of the proposal.

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

(5) 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

Communications:

1. Due to the AMRDEC SAFE site being shut down and transitioned to the DOD SAFE site, proposals for this RFQ will be accepted by drop-off at https://safe.apps.mil/ or by email. Send proposals to Frank Capuano at frank.capuano@us.af.mil or to Kathryn Vaccaro at kathryn.vaccaro@us.af.mil . Upon email submission, offerors are advised to contact Frank Capuano at 740-788-5046 or Kathryn Vaccaro at 740-788-5078 to verify successful submission of proposals. Offerors are cautioned that some or all documents may be removed due to Air Force network security settings. Offerors bare the risk for receipt of submitted offers being untimely. All other terms and conditions remain unchanged.

Attachment 3 https://safe.amrdec.army.mil/safe/

2. Files shall be submitted in a format readable by Microsoft (MS) Word 2016 or earlier, MS Excel 2016 or earlier, MS PowerPoint 2016 or earlier, or Adobe Portable

Documentation Format (PDF). If submitting a PDF file, the Offeror shall create the file to enable textual search and copy functions. Macros or other embedded objects or features within files will be disabled as part of regular security precautions.

3. Uploaded files must be timestamped by the offer due date and time. Offerors shall allow sufficient time for receipt of electronic submissions by the due date and time.

Offerors bare the risk for receipt of offers being untimely.

Attachment 3

B. Volume I – Completed RFP with Pricing

a. Shall consist of the completed and signed RFQ with a cover letter delineating any exceptions taken to the RFQ terms and conditions. However, offerors are cautioned that any noncompliance with the terms and conditions of the RFQ may cause their proposal to be determined unacceptable. 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 RFQ, pages 3-5.

b. Discussions may be conducted, but the Government reserves the right, in limited circumstances, to award without discussions. Proposals received are subject to the requirements specified in FAR 52.212-1, unless otherwise tailored in the Addendum to the solicitation.

C. Volume II - Technical Proposal

a. Technical proposals shall be clear, concise, and include sufficient detail for effective evaluation. Technical proposals shall include a written response to EACH paragraph of the Purchase Description with sufficient supporting technical literature.

Proposals shall include descriptive literature, brochures, and a technical proposal response.

Sufficient technical literature, documentation, etc., shall be submitted in order for the Government to make an adequate technical assessment of the proposed unit. Solely restating the paragraphs of the Purchase Description or limiting the response to a simple statement of compliance is not acceptable. Where technical literature demonstrates that the proposed unit meets the requirement of a specific Purchase Description paragraph the page number and paragraph of the technical literature may be referenced in lieu of restating it. Offerors shall assume the Government has no prior knowledge of their proposed unit and will base its evaluation solely on the information presented in the offeror’s proposal.

b. The offeror shall provide documentation that demonstrates the verification and validation of the software in use. This documentation shall include the software revision number, date of verification, testing plan, and testing results.

The testing plan shall consist of steps and procedures performed to verify the software.

The testing results shall consist of the measured results and conclusions drawn from the testing plan.

https://safe.amrdec.army.mil/safe/guide.aspx