Final Q A posted 12 Jan 11.doc

SUBJECT: FA9422-11-R-0002 (12 Jan 11)

NUCLEAR ENTERPRISE TRACKING SYSTEM (NETS) - NEST

CS/Phone: Joe C. Castillo / 505-853-5137

Date: 12 January 2011

The purpose of this posting to FedBizOps is to address the final questions received in response to the formal RFP and the telecom held with all interested vendors on 11 Jan 11. We will not be posting meeting minutes from the

11 Jan 11 telecom. The telecom primarily consisted of a restatement of the goal and intent of the program that was posted for all interested parties to review on 7 Jan 11.

Please ensure when you draft your proposal that you are using the RFP that was posted on FEDBIZOPS on 20 Dec. We are concerned that vendors are inadvertently using the draft document we posted earlier. Dramatic changes occurred between the draft and the final RFP so please ensure you use the correct one.

In addition, please ensure you acknowledge all RFP amendments in your proposal. Amendments 1 and 2 were posted 23 Dec 10 and Amendment 3 was posted 11 Jan 11.

We expect to post Amendment 4 to the RFP by COB Friday, 14 Jan 11. The purpose of Amendment 4 will be to add appropriate Intellectual Property and Data Rights clauses. The proposal due date remains unchanged. Proposals are due 2:00 pm MST on 25 Jan 11.

Contracting/RFP Related:

RFI #1: Regarding 6.3.2, the Contractor is used to providing contact information for the cognizant DCAA office but not for the Government Paying Office, ACO, and/or the Contract Administration Office. Other than the contact information for the cognizant DCAA office, can the Government provide additional details regarding what it is looking for to satisfy requirements in this section?

Answer: The requirement is to provide DCAA and DCMA point of contract information. Government paying office is not required.

RFI #2: Because it seems as if the Government is looking for Contractors to complete representations and certifications in Section 6.1.5 and exceptions to solicitation in Section 6.2, what is the Government looking for in Section 6.1.3?

Answer: You are correct 6.1.5 requires representations and certifications and 6.2 requires offerors to note any exceptions, should they have any. For 6.1.3, there are no fill-ins required for commercial contract clauses, therefore no action is required by contractors. This section is simply stating that the final contract will include the clauses outlined in the solicitation. The two clauses contained in the RFP that will not be contained in the final contract are 52.212-01 and 52.212-02 and their respective addendums. By submitting a signed proposal, offerors are agreeing to the clauses that will be contained in the final contract.

RFI #3: It was not clear in Section 5.1.1 if the Government requires a specific pricing format. May Contractors offer their own formatting to satisfy pricing requirements?

Answer: The only cost/price proposal information offerors are required to submit with their proposal is to simply fill in the offerors overall firm-fixed-price for the entire effort on CLIN 0001 located within Section B of the contract. No other supporting information is required or desired.

RFI #4: In an effort to provide a simpler means of procurement, will Government allow the use of price options in a single RFP response, rather than a single vendor turning in multiple RFP responses?

Answer: Each solution to the SOO shall be offered as a separate proposal submission. Each proposal submission will be separately evaluated. Once all evaluations are completed, if an offeror has multiple successful solutions that have been selected for award, the government reserves the right to consolidate the offeror’s successful proposal submissions into a single contract vehicle to ease contract administration burden for both parties.

Technical Related:

RFI #1: What size and what material are the assets made of - can one simply place an adhesive barcode tag on them?

Answer: (A) Since current knowledge of asset size/material is not a contract requirement, this information will not be provided. (B) There is no predisposed identification type specified. The government will evaluate all innovative options provided by industry.

RFI #2: How are your assets currently tracked?

Answer: Since knowledge of current AF asset tracking is not a contract requirement, this information will not be provided.

RFI #3: How many locations do they have?

Answer: Since knowledge of current AF asset tracking locations are not contract requirements, this information will not be provided.

RFI #4: Barcode OR RFID OR both? -

Answer: RFID is not currently used by the Air Force. At present, unique serial numbering is used. However, with this contract requirement, there is no predisposed identification type specified. The government will evaluate all innovative options provided by industry.

RFI #5: How many people in the company would need CONCURRENT access to the application?

Answer: The number of people involved in each tech demo, concurrently or otherwise, is at contractor discretion as appropriate to the objectives/product outcomes that will be satisfied by their technology.

RFI #6: Would WEB integration suit their business model?

Answer: WEB integration is at contractor discretion as appropriate to the objectives/product outcomes that will be satisfied by their technology.