The file's text, extracted by GovTribe without its formatting.
Question Set 2 for RFP FA8106-09-R-0007
| Question # |
| RFP QUESTIONS |
| ANSWER |
| 1 |
| Reference: RFP, CLIN 2018, Page 21 of 106; RFP, CLIN 2016, Page 20 of 106 |
Background: CLIN 2018 starting in FY13 includes Aircrew Training Device development and delivery of one Flight Training Device (FTD) in FY14; and CLIN 2016 starting in FY13 includes delivery of one WST in FY14. Option year 2 in FY13 does not include any additional FTD or Weapons System Trainer (WST) spares to support new FTD and WST delivery in FY14.
Question: How will the one additional FTD and one additional WST delivered in FY14 be spared?
CLIN 2018 is delivery of one FTD. Development of all Aircrew Training Devices (FTDs, WSTs and other) is accomplished under CLIN 0006. All ATD spares will be negotiated and delivered on CLIN 1019 based on the recommended spares listing.
| 2 |
| Reference: RFP, CLIN 3016, Page 28 of 106 |
Background: CLIN 3016 starting in FY14 includes Aircrew Training Device (ATD) delivery of two Weapons System Trainers (WST) in FY15 but does not include a CLIN for ATD (WST) spares to support the additional WSTs.
Question: How will the two additional WSTs delivered in FY15 be spared?
ATD spares will be procured on CLIN 1019 for all FTDs and WSTs. This is a TBN CLIN based on the delivered recommended spares list. Delivery dates for ATDs and ATD Spares are for the offeror’s to propose.
| 3 |
| Reference: Section M, Table 1, page 100 of 106 |
Background: CLIN 1018 is listed as Flight Training Device Modification; FFP for 1 EA Modification to Flight Training Device IAW SOO/SRD On page 13 of 106, CLIN 1018 is listed as “Reserved”. Page 100 of 106 shows CLIN description and calculation for CLIN 1018.
Question: Should the reference to CLIN 1018 be CLIN 2018?
On page 100, CLIN 1018 in the table will be removed. On page 102, CLIN 2018 will be added for FFP for one (1) EA Modification to FTD IAW SOO/SRD. This will be reflected in a RFP amendment.
| 4 |
| Reference: RFP, Section B, CLIN 1021, page 14 |
Background: The government data repository, JEDMICS (Joint Engineering Data Management Information and Control System), contains valuable technical data crucial to developing an effective modification package for the aircraft. The data in the Technical Orders is insufficient to perform the engineering required for systems integration and installation. JEDMICS includes wiring diagrams, installation drawings, kit fabrication drawings, and other data that would be crucial for the modification effort. Additionally, JEDMICS contains dimensional data on aircraft structures and aircraft skin that would be needed to perform the engineering for the KC-10 CNS/ATM modification.
Question: Will the Government provide JEDMICS access to the KC-10 CNS/ATM integrating contractor(s)?
The KC-10 does not have any data or drawings in JEDMICS.
| 5 |
| Reference: Section L 7.3.5; page 77 of 106 |
Background: “Include a Data Rights List IAW special contract requirement H036, Identification and Assertion of Restrictions on Technical Data and Computer Software (Dec 2006).”
Question: The RFP does not contain a Section “H”. Will the government provide the full text for this special contract requirement clause?
Section L 7.3.5; page 77 of 106 should be changed to reflect clause 252.227-7013 Rights in Technical Data—Noncommercial items – Alternate I
| 6 |
| Clause 5352.209-9002 - The prescribing language for this clause, found at AFMCFARS 5309.507-2 states that the clause should be inserted in solicitations when the contractor's eligibility for future prime contract or subcontract awards shall be restricted because of services being provided as stated in FAR 9.505-1 through 9.505-4. These rules prescribe limitations on contracting as the means of avoiding, neutralizing, or mitigating organizational conflicts of interest that might otherwise exist in the stated situations. This clause is not appropriate for this soliciation; can it be deleted? |
| Clause will be removed. |
| 7 |
| Reference Section L, paragraph 6.1 on page 73: Instructions in this paragraph indicate that pricing related information should only be included in the Cost/Price volume, but the Pricing Matrix is listed as an attachment to the Model Contract to be included under paragraph 7.3.6 of the Contracts Volume. Should this Pricing Matrix be included in both places? |
| Pricing Matrix will be part of the Cost and Pricing volume. Amendment will reflect change to Section L para 7.3.6 deleting Pricing Matrix from Model Contract. |
| 8 |
| Reference Section L, paragraph 6.2, page 74: The RFP states that "The Cost/Price Volume shall consist of fully completed Table 1 unit pricing as provided under 'Method of Calculating Overall Evaluated Proposal Price'. Also, provide extended pricing per CLIN as well as per year." It is our understanding that Table 1 provides the instructions / directions for completing the Price Matrix and that Table 1 itself requires no modification nor is it to be included in the Cost/Price Volume, or anywhere else. Is this the correct assumption? |
| The assumption is correct; however, Section L para 6.2 will be corrected to read: "…fully completed Pricing Matrix in accordance with Table 1..." |
| 9 |
| Reference CDRL A027, Monthly Status Reporting: This CDRL is the Monthly Status Report and calls for the itemizing of expenditures. The CDRL instructons say that "Itemized cost expenditures (billings) for all CLINs by category and task for the reporting period and total contractual expenditures to date." Under a Firm, Fixed Price Contract, this reporting is not required. Can this clause be deleted, or is it meant to cover only cost reimbursable CLIN 0007, Travel? |
| EMD funding (RDT&E) is an "expenditure based" appropriation. Even for a Firm Fixed Price contract, Expenditures (Invoicing data) must be captured for reporting purposes. The expenditures that are reflected in DFAS lag consistently far behind actual billings. The intent of this requirement is for the contractor to provide the accumulation of the billing information, so the Program Office has insight into dollars being expended versus waiting for billing thru DFAS. CDRL A027, DD form 1423 tailoring will be revised to read: "Itemized cost expenditures (invoice billings) for all CLINs for the reporting period and total contractual expenditures to date." |
| 10 |
| In SOO paragraph 1.3.1, what is the minimum number of aircraft required to meet IOC? |
| SOO paragraph 1.3 states that IOC will be attained when the first squadron of KC-10 aircraft is modified with CNS/ATM capabilities and is mission capable. Depending on which base AMC selects to be the first to receive modified aircraft, it could be from 14 to 16 aircraft. McGuire AFB has 32 acft and Travis AFB has 27 acft. |
| 11 |
| SOO paragraph 5.3.5 addresses Integrated Baseline Reviews (IBRs), which are typically conducted as part of an Earned Value Management System (EVMS) during performance of a cost reimbursement contract and only used for fixed price efforts if approved by Milestone Decision Authority. Since anticipated award is to be FFP and SOO/ CDRLs do not address EVMS, please confirm that planned IBRs do not imply a derived requirement for further implementation of EVMS or EVMS reporting requirements. |
| Planned IBRs do not imply a derived requirement, now or later, for implementation of EVMS or EVMS reporting requirements. |
| 12 |
| Regarding SOO paragraph 5.4 and CDRL A011, Data Acquisition Document DI-ILSS-80095/T is outdated since the underlying standard, DOD-STD-1702, was canceled without replacement in May of 1998. |
| CDRL will be deleted |
| 13 |
| Regarding SOO paragraph 5.4.6 and CDRLs A051 and A054, will the Contractor be responsible for cataloging and obtaining National Stock Numbers (NSNs)? |
| No, CDRLs A051 (Provisioning Parts List Index) and A052 (Provisioning Parts List) will be removed. |
| 14 |
| Regarding SOO paragraph 5.4.6 and CDRLs A051 and A052 DS-84, Data Standard for the Preparation and Submission of Provisioning Technical Documentation, email from SIAO@NSA.gov as of 03 June 2009 indicates that this document is not available for public release. Please provide either a copy of the document or means of downloading or otherwise accessing the document. |
| CDRLs A051 (Provisioning Parts List Index) and A052 (Provisioning Parts List) will be removed. |
| 15 |
| SOO, SRD, and CLIN coverage of training devices combine to make it clear that full logistics support including spares is expected for those items. Turning to aircraft spares, however, SOO 5.4.6 (as confirmed by SRD and CLIN structure) makes it clear that, although contractor will provide a list of items, pricing of initial spares will be by negotiation after award so that prices are not to be included in the proposal. There appears to be no requirement for proposal to include aircraft spares other than addressed by SOO 5.4.6.3 for items covered by commercial warranty. Please clarify. |
| The requirement is to deliver a recommended spares list for the aircraft and the ATDs. All Spares CLINs ATDs and aircraft are To Be Negotiated (TBN). CLINs 1011, 2011 and 3011 are for Aircraft initial spares which are TBN. CLIN 1019 is for ATD initial spares which is TBN. |
| 16 |
| SOO 5.5.8 requires “one paper set of marked-up contractor source data.” Since “marked-up” could indicate a degree of informality ranging up to handwritten, please clarify intent. |
| The preferred delivery of source data is that all verification comments would be incorporated, but sometimes schedule does not permit this, so as worst case the Gov't could authorize handwritten changes. This would be the type of questions that will be part of the discussions held during the TO guidance conference. |
| 17 |
| SRD paragraph 1.1.1.2 requires system support Net-Centric military operations. It is understood that AOC messaging as defined in OV-2 and OV-3 of Appendix A is required. Is this AOC messaging required to be encrypted or secured in some manner? Are there any other specific military Net-Centric features required for FOC by 2015? If yes, what are the data, protocol and security requirements? |
| AOC messaging is not required to be encrypted or secured. There are no other known Net-Centric requirements required by 2015. |
| 18 |
| SRD paragraph 3.2.4.2.1.7 addresses a 10db VHF fade margin at 200NM LOS. What are the characteristics of the off-board transmitter/receiver (i.e. antenna gains, Receiver sensitivity and Transmit power) to be used in the link analysis |
| SRD paragraph 3.2.4.2.1.7 will be deleted. This response supersedes the posted response to question #25 from Question Set 1 for RFP FA8106-09-R-0007. |
| 19 |
| Regarding CDRL A013, LSA-080, Bill of Material, Data Acquisition Document DI-ILSS-81169A has been canceled. |
| DI-ILSS-81169A/T will be replaced with DI-SESS-81359B/T Parts List. The DD form 1423 will be amended and the DID will be tailored to the minimum requirement. |
| 20 |
| FAR 5352.209-9002 appears not to apply to this effort. |
| Clause will be removed. Concurrent with Question 6 above. |
