Questions_and_Answers._FA8224-16-C-0014.docx

Questions and Answers FA8224-16-R-0014 MMC Chassis Tester

Q1.) CLIN 0002 is FFP for software support however there is no statement of work (section 3.4). One option if this is to be on an as needed basis, is we can quote time and materials as we did on the last contract for emergency service.

A1.) History shows that there is no need for the software support, this CLIN has been removed.

2.) CLIN 0003 is FFP for travel expenses. On the last contract we submitted the actual costs for each trip in the form of receipts and were reimbursed. We did not have to submit the request in advance as we will be doing under this RFP. Does this have to be FFP or can it be "Cost" as last year?

A2.) We are getting push back on cost and T&M contracts, since you have a history of travel it should not be to difficult to FFP your travel cost, but since it is FFP you will not berequired to submitt your travel plans in adavnace, I have removed that rquirement for the PWS.

Q3.)Reference SF 1449, Items 0002, 1002, 2002, 3002, and 4002, software support: “Contractor to provide software support IAW with sec. 3.4 of the PWS revised 29 DEC 2015.” There is no paragraph 3.4 in the released PWS dated 29 Dec 2015. Please clarify.

A3.) Section 3.3 and 3.4 have been removed from the PWS.

Q4.) Reference proposal instructions, page 18, “Subfactor 1 - Multilayer circuit card repair and ribbon cable replacement/repair: Describe your company’s capabilities and experiences on similar type work/contracts showing a minimum of three years’ experience on component repair and pneumatic actuators as listed in PWS Paragraph 3.3.1. To be technically acceptable the offeror must detail its knowledge and experiences per PWS Paragraph 3.3.1.” Paragraph 3.3.1 states: “3.3.1. All Software modified or created will remain or become property of the US Government.” Is there a missing PWS paragraph that details the expected experience on component repair and pneumatic actuators? Please clarify.

A4.) Subfactor 1 - Multilayer circuit card repair and ribbon cable replacement/repair: has been moved to section 3.2.1.2 of the PWS. The software requirement has been moved from the PWS.

Q5.) Reference PWS paragraph 2.3: “The contractor shall provide software support. All software updates and data generated under this contract will be delivered to the government with unlimited rights as defined in DFARS 227 with no proprietary markings or restrictive legends. The contractor shall be responsible for updating CPINs.” In order to prepare an accurate proposal TQS requests the following information:

Specifics of the MMC Chassis Tester software to include:

Available GFI software documentation to include: FRD, SDD, VDD (with version release notes), CMP (with a description of the executable build process), software development environment (development tools, hardware, compliers, etc.), source code (and size, e.g., SLOCs), the language(s) the code was written in, and the CPIN paperwork.

Software development tools used to support the chassis tester software and information regarding the availability of these tools from the Air Force as GFP A5) This requirement has been removed from the PWS and the solicitation A6.) Reference PWS paragraph 2.4: “The Contractor shall provide personnel, equipment, tools, replacement parts, materials, and other items necessary to complete the tasks.” If the contractor is responsible to provide replacement parts as a part of the cost of the FFP contract, TQS requests the following information in order to prepare an accurate proposal:

A. TO 33D7-3-98-1

B. TO 11F13-14-11-3

C. TO 11F13-14-11-3 Foldouts D. Any additional parts lists not included above including parts price information E. Maintenance history (including cost), technical inspection intervals and reports, and other technical reports from the previous support contract in order to baseline estimated costs.

A6) Unfortunately the TO’s cannot be released until after award, but I have compiled a report of the maintenance history for the last 3 years to help with your proposal.

For maintenance history reports please contact: Brenda Keesler at brenda.keesler@us.af.mil