BAA-RQKM-2015-0011-Amd2.doc

Questions and Responses on BAA-RQKM-2015-0011 Agile Manufacturing for ISR Program Amendment 2 Dated 23 Jan 2015

General Comment: Based on input from potential offerors the page limitation for the Technical/Management Proposal (reference BAA para IV.2.b.i.a and IV.2.b.i.f) is increased from 30 to 35 pages.

Question 1: Is the door mounted pylon a SABIR arm unit, or is a new version planned?

Response: The planned arm for use will be provided via NAVAIR’s roll On Sensor System for Contingency Airborne Response (OSSCAR) system, with potential to fall back to AirDyne’s Special AirBorne Mission Response (SABIR) system as a risk mitigation effort. In either selection, the Multi-INT demonstration pod developed on this effort will attach to the selected arm via a BRU-14 mount protruding from the aircraft paratroop door.

Question 2: What are the weight and aerodynamic load capacity of the door mount?

Response: Weight allowance will vary dependent upon arm / mission payload selection. The OSSCAR arm has been demonstrated up to 750 lbs, with capability to handle up to 2,000 lbs. The SABIR arm has a weight allowance of 400 lbs. Detailed pod structural and aerodynamic load design should be considered by the offeror and determined in the early stages of this effort.

Question 3: What are the size limitations for door mounted stores?

Response: Size limitations of the Multi-INT demonstration pod, will be reliant upon both aircraft integration constraints and specific pod design of length, shape, and diameter chosen by the offeror. The government will work with the contractor to determine exact constraints based on design and inspection of aircraft interface and draft pod designs, after award, but before design review.

Question 4: What is the targeted mission payload weight capacity requirement for the pod?

Response: The targeted mission payload weight will be approximately 500 lbs (2 – 100 lbs turreted sensors, 1 – 200 lbs gimbaled sensor, 100 lbs communications and networking), but will vary dependent upon the selection of the combination of sensors for mission requirements and door mount option. The Multi-INT demonstration pod should demonstrate the capability to house any selected combination of sensors noted to meet the required mission while not exceeding the weight allowance.

Question 5: Are simultaneous carriage of the 3 mission packages (two turret and one gimbaled) and datalinks required?

Response: Yes Question 6: SOW Paragraph 2.1: Please clarify "gimbal mounted" sensor requirements.

Are they similar to the Thales iMaster?

Response: Gimbal mounted sensors would be non-standard mounted sensors that may or may not have environmentally controlled installations. These sensors will be carried internally to the pod, have the capability of transmitting/receiving through the pod, a window, or opening in the pod and mounted in such a way to provide required field of view for the sensor. One example of this would be an EO camera system mounted on a quickset QPT-130 gimbal. The Thales iMaster system would be considered a turret mounted solution.

Question 7: SOW Paragraph 4.4: Will BRU-14 bomb rack include a 30" lug adapter?

Response: Yes Question 8: Is active temperature control of the pod required? Is active cooling required on ground for significant durations?

Response: Active pod temperature control is not required for this effort but could be proposed by an offeror if required for their pod design.

Question 9: Is the roll-on/roll-off palletized PED station provided as GFE or do you want the contractors to provide as part of BAA effort?

Response: Offerors need to provide the means of interfacing the demonstration pod to the PED station. The PED station will be part of the C-130 flight demonstration and not a deliverable on this BAA effort or GFE provided to the contractor, reference SOW para 4.4.

Question 10: Clarify that technical proposal, SOW and cost volume all need to be double-spaced 12 point business Arial text?

Response: Yes Question 11: Can you please clarify if the Attachments, which are typically page numbered separately, are meant to be included as part of the page-limited 30-page portion of the proposal (to include as requested prior past work, equipment and facilities, and resumes)?

Response: IAW BAA para IV.2.b.i.f); The revised 35 page limitation covers all information including indices, photographs, foldouts, tables, charts, appendices, attachments, resumes, etc. Past work, equipment and facilities and resumes are included in the page count. However, an exception will be made in this case for resumes. Include resumes as an attachment to the Technical/Management proposal but resume pages will not be counted against the 35 page limitation.

Question 12: Should the SOW be included as a separate attachment to the Technical Volume?

Response: Yes IAW BAA para IV.2.b.ii

Question 13: Should the list of all Government property the offeror or its subcontractors propose to use on a rent-free basis be included in the Technical Volume or as an attachment to the Technical Volume? If an attachment to the Technical Volume is this page limited?

Response: IAW BAA para IV.2.b.ii.a); The list of Government property the offeror or its subcontractors propose to use on a rent-free basis should be included in the Technical Volume or as an attachment to the Technical Volume. In either case the 35 page limitation applies.

Question 14: In Part II of the BAA Guide it states, “1) Organization Chart(s) with Personnel: Include prime offeror and subcontractor organization charts.”

Are these org charts to exclude all company/personnel names and subcontractor company/personnel names consistent with not including names in the resumes. (2) Do you only want to see functional roles?

Response: Include functional roles in org charts—names not required.

Question 15: If we include a color cover page for the proposal volume notebooks; and an inside title (cover) page with all the requested information, does the color cover page count or can we count from the inside title (cover page) of the volumes?

Response: The color cover page and the title cover page count against the page limitation.

Question 16: Is it acceptable to cross references within the page-limited sections of the proposal to non-page limited sections, volumes, and Attachments?

Response: Cross referencing between page-limited volumes (e.g. Technical Proposal) and non-page limited volumes (e.g. Cost Proposal) is acceptable to clarify points. Cross referencing should not be used to merely circumvent the technical proposal page count. Do not use cross referencing to merely add content to the Technical Volume.

Question 17: Is the cover/transmittal letter included in the page count and can it be included in the volume?

Response: IAW BAA para IV.2.b.i.f), attachments to the Technical/Management Proposal the count toward the 35 page limit (with resumes as noted in question 11 as an exception). The proposal transmittal letter can be included in the Technical/Management Proposal Volume or separate. If included it counts against the 35 page limitation.

Question 18: Regarding the Government Furnished Equipment List, can you provide information (manufacturer, size, etc) on the Electro-Optic Wide Area Motion Imagery Sensor with G-tag G281858 and G283593?

Response: Exact sensor specifications, to include the EO WAMI sensor manufacturer, size, etc, will be delivered after award.

Question 19: Reference SOW paragraph 2.6 “Investigate other platform mounting options

(e.g. wing mount)” and BAA Overview Information Document, page 9, Paragraph

III. Eligibility Information, Item 5.c. “There are no limits to the number of proposals an offeror may submit”. Would an offeror be in compliance with the BAA if an alternate mounting solution was provided without addressing a

POD solution using the GFE mount?

Response: To be responsive to Government requirements, an offeror’s solution should demonstrate ability to attach the pod to a GFE mount. Alternate mounting solution are desired in an offeror’s proposal per SOW para 2.6. SOW para 4.4 further highlights the demonstration pod developed on this contract will attach via BRU-14 carriage rack.

Question 20: There are multiple places within the BAA Overview Information document that requires the offeror to provide a Statement of Work (SOW) as a proposal deliverable document. Yet the BAA included a document titled BAA-RQKM-2015-0011-SOW. Is this document more of a Statement of Objective document used as a baseline to create the SOW proposal deliverable? Please provide additional guidance that a SOW is required and should be based on the offeror’s specific proposed approach.

Response: A SOW from the offeror is required with offeror’s proposal. The SOW provided in the BAA can be considered a baseline document capturing the Government’s objectives in this BAA.

Question 21: The BAA Overview states that resumes of personnel who will be participating in this effort should also be included as attachments to the technical proposal. Are resumes required for ALL personnel or KEY personnel? (If resumes are required for ALL personnel and the BAA Overview states that attachments (resumes being one of these attachments) are part of the page count, respectfully request the page count be increased by 10 pages or not count resumes towards the page count).

Response: Include resumes for just key personnel. As noted in response to question 11 above, resume pages will not count toward page limit on the Technical/Management Proposal.

Question 22: Please provide concurrence that the Technical/Management Proposal may contain proprietary data, if so marked, and will be protected from being used/distributed even if the offeror is not successful with this bid.

Response: The Technical/Management proposal may contain proprietary data but do not include proprietary data in the SOW (as noted in para IV.2.b.ii). Any proprietary data submitted will be appropriately protected.

Question 23: What are the required/expected interfaces from the pod to the PED?

Response: There are a variety of connections required between the pod and PED, to include power, C2, etc. Interfaces will vary depending on sensor/mission payload selection. While Interface Control Documents (ICDs) will be produced post award, proposals should include an approach on how to address varying combinations of interfaces.