RFI's Amendment 1.docx

SUBJECT: FA9422-11-R-000x AMENDMENT 1

NUCLEAR ENTERPRISE TRACKING SYSTEM (NETS) - NEST

CS/Phone: Francine M. Chavez / 505-853-2483 Date: 27 October 2010

Amendment 1 is issued in response to RFI’s.

1. RFI RESPONSES

CONTRACTING

RFI #1: Our assumption is that all questions submitted by industry will be answered and posted to FedBizOps, is this assumption correct?

Answer: Yes

RFI #2: Based on the last paragraph of the Statement of Objectives (SOO) para 3.0 (“The offeror’s SOW shall specify in clear, understandable terms the work to be done by the contractor in developing or producing the technology demonstration and define what is required in specific performance based, quantitative terms.”) our assumption is that the RFP will require Offerors to develop and submit a Statement of Work (SOW) that addresses the information contained in the SOO. This approach provides an excellent opportunity to meet Air Force objectives given that:

Answer: Yes, that is correct. The offerors are to develop and submit a Statement of Work (SOW) that addresses the information contained in the SOO.

RFI #3: Our assumption is that the SOW will not have a limitation on the number of pages, is this assumption correct?

Answer: Anticipate limitation of 30 pages.

RFI #4: Our assumption is that the SOW and other deliverables required by the Request for Proposal (RFP) will not allow classified proposals. Is this assumption correct?

Answer: The solicitation and proposals will remain unclassified.

RFI #5: Our assumption is that a pre-proposal conference will be held that will brief industry on the program and to answer general questions, is this assumption correct?

Answer: Not yet determined.

RFI #6: Our assumption is that the Air Force will allow industry to participate in one-on-one meetings with Government contracting and technical representatives. Is this assumption correct?

Answer: One-on-one meetings will not be held. There is potential for an Industry Day but at present this is not being planned.

RFI #7: Will a draft RFP be released and will it include a CLIN structure and relationships to Deliverable and the revised SOO?

Answer: Yes anticipate releasing a draft RFP for industry comment mid-Nov 2010.

RFI #8: The SOO seems to imply that the contract will be awarded to a single contractor. Has an acquisition strategy been determined indicating the number of awards?

Answer: The acquisition strategy has not been approved at this time. There is potential for award to multiple contractors (dependent on funding constraints).

RFI #9: The SOO does not indicate the type of contract. Has the Air Force determined the type of contract (Cost Plus Fixed Fee, Firm Fixed Price or Level of Effort) for this acquisition?

Answer: The acquisition strategy has not been approved at this time. The contract type is anticipated to be Firm Fixed Price.

RFI #10: In Section 1.0 Background, the SOO states “This Statement of Objectives (SOO) expresses the concept and approach for a technical demonstration of an Information Technology (IT) solution…” The synopsis states “The United States Air Force Nuclear Weapons Center (AFNWC) intends t o issue a Request for Proposal, FA9422-11-R-000x (number to be determined), to acquire technology demonstrations related to Nuclear Enterprise Tracking System (NETS)…” indicating multiple demonstrations are going to be “acquired”. Our assumption is that a single task order contract will be awarded and that the selected contractor may conduct multiple demonstrations based on the number of Statements of Work that contractor submits. Each SOW will be executed as a Task Order with independent requirements, deliverables, and schedules. Additionally, the Government may also elect to issue a Task Order Request for Proposal with a SOO or a SOW that defines the demonstration they would like to see conducted that the Contractor will then respond to with their proposal to conduct that demonstration. This approach provides significant flexibility for the Air Force to achieve their overall NEST goals as it capitalized both on industry knowledge as well as internal Air Force Knowledge. Is this assumption correct?

Answer: A task order contract is not being contemplated. Therefore the concept you describe above is not the process or intent of the government at this time. Our concept shall become more clear upon release of the draft RFP.

RFI #11: Based on the SOO in para. 5.0, Period of Performance (“Proposed by contractors in the Statement of Work”), will the contractor specified periods of performance define the overall period of performance for the Contract?

Answer: Offerors will be requested to provide the period of performance for their proposed demonstration. Each offerors technology is at different stages of readiness and therefore offerors will be provided an opportunity to propose the period of performance it will require them to complete the SOO tasks. This may become part of the evaluation criteria.

RFI #12: The SOO does not specify a level of security classification required to perform on this contract. Is the contractor to identify the security classification in their SOW?

Answer: The final requirement anticipated in the RFP will be at the secret level.

RFI #13: Has an acquisition schedule been defined? If so, can you release it to industry?

Answer: Schedule may be released to Industry after we receive formal acquisition strategy approval. An interim schedule will be provided upon release of the draft RFP.

RFI #14: Has the Air Force determined their budget for this acquisition and can that budget information be shared with the Offerors at this time?

Answer: The budget is known and it is anticipated that this will indeed be shared with industry at time of release of the formal RFP.

RFI #15: Our assumption is that the Air Force will release a draft RFP that will include a refined/updated SOO, is this assumption correct?

Answer: Yes, if applicable.

RFI #16: Are funds available for the procurement of demonstration hardware and software?

Answer: No as this is a technical demonstration of current capability.

TECHNICAL

RFI #1: Does the biometric security have to be constrained to the handheld device?

Answer: The handheld device will have to demonstrate biometric security to safeguard information but there is no predisposition on a possible solution.

RFI #2: Is the area access controlled as well? If so, are biometrics, which protects the general areas required?

Answer: Most areas are controlled access. Only IT solutions have to demonstrate biometric security to safeguard information and users.

RFI#3: Will the handheld devices require access to the command or enterprise network?

Answer: Yes

RFI #4: Will the handheld device require access to specific enterprise applications such as ERP, Maintenance Management and PLM?

Answer: Reference para. 3.0 item 4.

RFI #5: Are biometrics restricted to fingerprints? Would a retina scan, facial recognition or voice recognition biometric capability be an acceptable, suitable substitute?

Answer: We have no predisposed solution so demonstration of any and all capabilities is acceptable.

RFI #6: The SOO mandates integration into a number of systems. Does the solution need to integrate into ECSS?

Answer: Reference para. 3.0 item 4.

RFI #7: Will the system require 24/7 real-time QPS tracking of assets in transit and on the shelf or is that an option?

Answer: Unknown at this time. Please provide all capabilities you presently have available.

RFI #8: How granular do you need the tracking system to be?

Answer: Unknown at this time. Please provide all capabilities you presently have available.

RFI #9: Is the combination of COTS products and customer designed products acceptable?

Answer: Yes, as long as IT solution meets all certification and information assurance requirements.

RFI #10: Is there an identified date for the Initial Operating Capability or Full Operational Capability for the demonstrated systems?

Answer: No

RFI #11: Are the Mission Owners and Acquisition Decision Milestone authorities identified for the purpose of certification and accreditation?

Answer: Revising the SOO therefore standby for the release of the draft RFP.

RFI #12: Please describe the Air Force resources, personnel, equipment, data, and data access that will be available during the SOW development period, during program execution.

Answer: Revising the SOO therefore standby for the release of the draft RFP.

RFI #13: What provisions are in place to secure access to the identified Air Force Data systems during the demonstration period?

Answer: Revising the SOO therefore standby for the release of the draft RFP.

RFI #14: Will access to SIPRNet via a sponsored contractor SCIF be provided during the Period of Performance of this effort?

Answer: Not needed.

RFI #15: Has any hardware or software already been selected for demonstration?

Answer: No

RFI #16: What portions of capability is already available on the Air Force network?

Answer: Revising the SOO therefore standby for the release of the draft RFP

**NOTE: All other paragraphs, provisions, and conditions to Nuclear Enterprise Tracking System (NETS) - NEST REMAIN UNCHANGED**