F-16 Electronic Technical Order (TO) Capability Project

The following are some questions I have received and answers: 1. The pre-solicitation states that "Solicitation date for Request for Proposals (RFPs) will begin 12 August 2011. Interested potential offerors should respond to the RFP at that time." How long will offerors have to prepare proposals, given the Government's intent to award by 30 September 2011? Answer: Because the award date is 30 September 2011, we are planning a twenty (20) day solicitation. This not set in stone and could change. 2. The Pre-solicitation states that the solicitation date for the RFPs will begin on 12 August 2011. However, the response date for the pre-solicitation is 11 August 2011. Is the purpose of this pre-solicitation to get a list of interested vendors or to actually receive proposal per the PWS and requirements by 11 August 2011? In other words, what is due by 11 August 2011? Answer: The purpose of this pre-solicitation is to let interested vendors know that the Government has a requirement and plans on soliciting a future RFP for this requirement. Please do not submit any proposals. 3. In the RFP, it references the use of BidSync to submit proposals. How do you get access to this system? Answer: Please disregard the first document post on 7/29/2011 and reference the second document post on 8/1/2011. The first document was erroneously posted. 4. The PWS references the installation of software on the OEM network in Fort Worth. Is the OEM Lockheed Martin? Answer: Yes 5. The RFP as written states the Contractor is to provide the stylesheets to support each of the document types in the PWS. Without any method to protect or copyright stylesheets, what protection do offerors have that the intellectual property provided for evaluation is secure? > > > > Answer: Clauses will be added to the solicitation from the Federal Acquisition Requirements (FAR) to protect any intellectual property provide for evaluation. >6. The Specification list in para 2.2.1 of the PWS does not specify what release version or date of the specification to conform to, although para 9 states that "as a minimum, Version 6.n of all document type definitions (DTDs)." Specification release differences are in some cases dramatic and impact how stylesheets render data. Is there a specific version and release to be supported or will stylesheets supporting "Version 6.n" be considered compliant? > > Answer: Besides 38784BV7 all the rest are v6a. > > > 7. There are style presentation rules included in the PWS that are unique to the F-16 that don't appear to be industry standard OR are optional presentation modes. As an example, in para 7.6.4 "When Labels are not applied to the input SGML file, then the ETO Publisher / Viewer shall apply them per the applicable military specifications and standards." In para 7.6.2, "The ETO Viewer shall denote changed data for display by using one or more of these indicators: change bar next to the changed data; a color change in the data; or a shaded overlay." Is the Government's intent to solicit a contract to deliver this capability in 30 days or is there already a "shrink wrapped" F-16 solution to be acquired by this RFP? > > > Answer: The Government intends to solicit a contract to deliver this capability in 30 days.