SP7000-12-R-1002 _Amendment_12.pdf

Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods:

(a) By completing items 8 and 15, and returning or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment your desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT 1. CONTRACT ID CODE

2. AMENDMENT/MODIFICATION NO. 3. EFFECTIVE DATE 4. REQUISITION/PURCHASE REQ. NO. 5. PROJECT NO. (If applicable)

7. ADMINISTERED BY (If other than Item 6) CODE

STANDARD FORM 30 (REV. 10-83)

Prescribed by GSA FAR (48 CFR) 53.243

FACILITY CODE

9A. AMENDMENT OF SOLICITATION

NO.

9B. DATED (SEE ITEM 11)

10A. MODIFICATION OF CONTRACT/ORDER NO.

10B. DATED (SEE ITEM 13)

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offers is extended, is not extended.

12. ACCOUNTING AND APPROPRIATION DATA (If required) copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

13. THIS ITEM ONLY APPLIES TO MODIFICATION OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

CHECK ONE A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT ORDER NO.

IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(b).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15C. DATE SIGNED

15A. NAME AND TITLE OF SIGNER (Type or print)

16C. DATE SIGNED

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

PAGE OF PAGES

6. ISSUED BY CODE

8. NAME AND ADDRESS OF CONTRACTOR (No., street, county, State and ZIP Code) (X)

CODE

15B. CONTRACTOR/OFFEROR

(Signature of person authorized to sign)

16B. UNITED STATES OF AMERICA

(Signature of Contracting Officer)

NSN 7540-01-152-8070

Previous edition unusable

SP7000

1. The purpose of this amendment is to provide responses to solicitation questions.

2. The solicitation close date/time remains unchanged at 10/06/2016 at 4 PM EST.

SP7000

DLA Document Services 5450 Carlisle Pike, Bldg. 09, P.O. Box 2020 Mechanicsburg, PA 17050-2411

Maria E. Anguiano Phone: 559-836-2294 Email: maria.anguiano@dla.mil

SP7000-16-R-1002

1 1

09/23/2016

02/26/2016

SP7000 16 R 1002 Attachment 1 – Responses to Solicitation Questions Page 1 of 3

Responses to Solicitation Questions

Question from Vendor:

As the Government wants offerors to provide datasheets/signed letter from OEMs to prove compliance of offered solutions with Government’s requirements, The RFP instructions to offerors and evaluation criteria for technical volume have not been updated to reflect the Government’s requirements. It still states “Technical Requirements: One IDIQ contract will be issued to the offeror that has the Lowest Priced Technically Acceptable proposals, subject to testing and approval. The offeror must demonstrate compliance with ALL the Technical Requirements set forth in the Statements of Work. Please respond to each numbered portion of the Statements of Work and applicable attachments, and write “Will Comply” behind each numbered portion.”

We request that the Government to update the instructions to offerors and evaluation criteria in the original solicitation so that all offerors are following the same instructions based on what is in evaluation criteria.

Response:

In addition to entering “Will Comply” on the SOWs to demonstrate compliance, offerors must provide device data sheets or signed OEM letters verifying the technical compliance for all proposed devices for each Volume Band.

Question from Vendor:

Since offerors may bid the same products for multiple CLINs, just providing technical spec sheets/signed letter from OEMs for all products bid is insufficient for the Government to know what specific solution an offeror has bid for each of the CLINs. If the Government wishes to validate offerors' solutions against the Government's requirements, then we recommend the Government also require offerors to provide a table of what products/solutions and from which OEMs are specifically being offered for each CLIN, which at present, the RFP does not require.

Response:

Offerors must provide the make and model of the proposed devices for each CLIN.

Question from Vendor:

Based on the following Q&A in the latest Q&A document (italic text below)

Does every single point (requirement) need to be verified by technical specification documents?

For example, some of the requirements were not found by Akira in the published technical specs but then verified via email with the OEM. Response: Yes, every requirement must be verified by technical specification documents.

In the SOWs, where the word “contractor,” for example, “The contractor will be required to perform operating system updates and patches IAW future DoD or DLA directives.” please

SP7000 16 R 1002 Attachment 1 – Responses to Solicitation Questions Page 2 of 3 confirm that for such requirements, the offerors do not have to ask the OEM to sign, only the offeror’s “will comply” response in technical volume should suffice, please advise.

Response:

Offerors do not have to ask the OEM to provide a signed letter for the requirement such as “The contractor will be required to perform operating system updates and patches IAW future DoD or DLA directives.” Device data sheets or signed OEM letters verifying technical compliance are required for the following SOW items numbers/sub numbers:

SOW 1: 1.1.1 through 1.1.10 SOW 2: 1.1 and 1.1.2 through 1.1.3 SOW 3: 1.1.1 through 1.1.10 SOW 4: 1.1 and 1.1.2 through 1.1.3

Question from Vendor:

Do we need to ask OEM(s) to verify the requirements like “Delivery of Equipment”?

Response:

No, device data sheets or signed OEM letters verifying technical compliance are required for the following SOW items numbers/sub numbers:

SOW 1: 1.1.1 through 1.1.10 SOW 2: 1.1 and 1.1.2 through 1.1.3 SOW 3: 1.1.1 through 1.1.10 SOW 4: 1.1 and 1.1.2 through 1.1.3

Question from Vendor:

We request the Government to identify the exact requirements that offerors need to verify either by technical datasheet(s) or OEM’s letter etc. Please note that not all requirements are technical or need verification. The Government’s response in reference question above indicates that requirements like “3.B.1.D.2. (U//FOUO) Assured Compliance Assessment Solution (ACAS) assigns severity scored of critical, high, medium and low to plug in findings” need to be verified. Please advise.

Response:

Device data sheets or signed OEM letters verifying technical compliance are required for the following SOW items numbers/sub numbers:

SOW 1: 1.1.1 through 1.1.10 SOW 2: 1.1 and 1.1.2 through 1.1.3 SOW 3: 1.1.1 through 1.1.10 SOW 4: 1.1 and 1.1.2 through 1.1.3

SP7000 16 R 1002 Attachment 1 – Responses to Solicitation Questions Page 3 of 3

Question from Vendor:

In the SOW(s) for certified device, the Government has listed four attachments under “Testing and Certification Process”, some requirements cannot be verified by datasheets only and offerors have to request OEMs for letters. Do offerors need to show compliance with requirements in “PMW205_HW_Certification”, if yes , please advise “how” as this document seems to be for information purpose. Same is the case with “DLA Document Services Testing Checklist”. Is it possible for the Government to identify the exact requirements that offerors need to verify either by technical datasheet(s) or OEM’s letter etc?

Response:

Device data sheets or signed OEM letters verifying technical compliance are required for the following SOW items numbers/sub numbers:

SOW 1: 1.1.1 through 1.1.10 SOW 2: 1.1 and 1.1.2 through 1.1.3 SOW 3: 1.1.1 through 1.1.10 SOW 4: 1.1 and 1.1.2 through 1.1.3

Question from Vendor:

Please confirm that the if an offeror bids a certified device (a device that the Government has already tested and is listed in the attachment) for an NGEN certified CLIN, the Government will not need offeror to provide a device for testing. Please advise.

Response:

If an offeror’s proposed device has already been tested and is listed on the attachments for NGEN/NMCI and ONENET, then the proposed device does not have to be submitted for testing.

Question from Vendor:

For the Guam shipments, will the ship to address be an APO or FPO address?

Response:

The shipment address will usually be an FPO AP address, but it could also be a local Guam street address.

Question from Vendor:

Where should the description of the items quoted be noted? The spreadsheet is locked in the description cells.

Response:

Vendors can provide their own table separately that lists the make and model of their proposed devices for each VB CLIN.