MODIFICATION
A -- Personnel Recovery Vehicle (PRV)
- Notice Date
- 3/18/2005
- Notice Type
- Modification
- Contracting Office
- 1895 5th Street, Bldg. 46 Wright-Patterson AFB, OH, 45433-7200
- ZIP Code
- 45433-7218
- Solicitation Number
- FA8629-05-R-2350
- Archive Date
- 10/30/2009
- Point of Contact
- Noah Oliver,937.255-2379
- E-Mail Address
-
SOF.PRV@wpafb.af.mil; Noah.Oliver@wpafb.af.mil; Donald.Fisher@wpafb.af.mil
(SOF.PRV@wpafb.af.mil; Noah.Oliver@wpafb.af.mil; Donald.Fisher@wpafb.af.mil)
- Small Business Set-Aside
- N/A
- Description
- COMBAT SEARCH AND RESCUE-X AMENDMENT 040 (05 OCT 05) Formal Request for Proposals The CSAR-X Flight has issued a Request for Proposals. Potential offerors are to consider the latest versions of the SRD (dated 15 Sep 05), Addendum 1 to the SRD (dated 23 Aug 05), and Attachment 17 to Section L (provided 21 Sep 05) in their possession to be the final versions. All other attachments to Section L remain available on PIXS. COMBAT SEARCH AND RESCUE-X AMENDMENT 039 (29 SEP 05) Response to Industry Question Concerning Program Protection Plan The CSAR-X Program Protection Plan (PPP), as identified with the PRV Security Classification Guide, is a Government document providing information to CSAR-X test and operational users on the requirements to protect the CSAR-X aircraft within the test or operational environments. The draft RFP includes the requirement for the offerors to propose the efforts necessary to support the CSAR-X program office in developing the CSAR-X Program Protection Plan. The PPP should not drive any design requirements. All design efforts for the CSAR- X program should focus on the technical requirements as set forth in the CSAR-X SRD and RFP. Technology that needs to be protected in the test and operational environment includes, but is not limited to, the following; 1. Technology used to defeat a threat 2. Information used to accomplish a threat defeat. 3. Examples: sensor performance, countermeasures performance, intelligence receiver performance, CNI performance, encryption/decryption methods/equipment. 4. Any deficiencies related to the above. The CSAR-X Extended Reference Library document has also been updated to include a link to TO 00-35D-54 in the unrestricted documents section. COMBAT SEARCH AND RESCUE-X AMENDMENT 038 (22 SEP 05) Draft RFP Sections L+M The CSAR-X Flight has issued an updated draft RFP Sections L+M for SDD and initial Production efforts for industry review and comment. Please provide review comments to SOFSG/THK by COB 26 September 2005. Attachments to L+M remain unchanged except for attachment 2 (posted on PIXS 21 Sep) and attachment 17 (provided to potential offerors 21 Sep). The CSAR-X Extended Reference Library document has also been updated and moved into the regular document library. COMBAT SEARCH AND RESCUE-X AMENDMENT 037 (17 AUG 05) Response to Industry Request for Cargo Air Load Model The Air Force no longer supports the Cargo Air Load Model (CALM). The current program is the Automated Air Load Planning System (AALPS), and is available at https://www.tis.army.mil/aalps/default.htm. AALPS helpdesk requests must be directed to 1 (866) 822-4672. The AALPS program is available on 3 disks and is free of charge. COMBAT SEARCH AND RESCUE-X AMENDMENT 036 (22 JUL 05) Draft RFP and Draft Sections L+M and Attachments The CSAR-X Flight has issued an updated draft RFP and updated draft Sections L+M with attachments for SDD and initial Production efforts for industry review and comment. Please provide review comments to SOFSG/THK by 27 July 2005. The CSAR-X Extended Reference Library has also be updated. COMBAT SEARCH AND RESCUE-X AMENDMENT 035 (24 JUN 05) Draft Production Contract Data Requirements List (CDRL) and Attachments The CSAR-X Flight has issued a draft CDRL package and attachments for production efforts for industry review and comment. Please provide review comments to ASC/LUH by 29 June 2005. PERSONNEL RECOVERY VEHICLE AMENDMENT 034 (20 JUN 05) Program name change The Personnel Recovery Vehicle program has been renamed Combat Search and Rescue-X (CSAR-X). The formal RFP, and supporting documentation, will be updated to reflect the change. PERSONNEL RECOVERY VEHICLE AMENDMENT 033 (26 MAY 05) Draft Contract Data Requirements List (CDRL) and Attachments The PRV Flight has issued a draft CDRL package and attachments for SDD efforts for industry review and comment. Please provide review comments to ASC/LUH no later tha Codes (AFSCs) supporting the HH-60? Answer: Due to the highly integrated systems there are now AFSCs that address this. To date, the most current use of these AFSCs is on emerging platforms. It is anticipated the AFSCs will be based on the new Integrated Systems AFSC. PERSONNEL RECOVERY VEHICLE AMENDMENT 028 (08 MAR 05)- Correction of Capt Thompson+s phone number (reference: Amendment 027) Phone: 937-255-4560 Email: Gary.Thompson@wpafb.af.mil PERSONNEL RECOVERY VEHICLE AMENDMENT 027 (07 MAR 05) - Draft SRD An updated version of the draft Systems Requirement Document (SRD), Rev 3, dated 7 March 2005 is available for review and comment. Please note this document falls under "DISTRIBUTION STATEMENT D: Distribution authorized to Department of Defense and DOD Contractors only to protect technical or operational data..." To receive a copy of the SRD, please send an email request to SOF.PRV@wpafb.af.mil, stating your name, organization, and CAGE code (Contractors only). It is requested that comments be forwarded to ASC/LUH, Attention Capt Thompson, by COB 18 March 2005. For those prime offerors that request a "face-to-face" discussion of the draft SRD, we encourage you to contact Capt Thompson at 937- 255-4600 to make the arrangements. We plan to hold these sessions 29 March through 1 April at Wright Patterson AFB, Dayton, Ohio. PERSONNEL RECOVERY VEHICLE AMENDMENT 026 (28 FEB 05) - PRV LIBRARY DOCUMENTS See below documents for Integrated Risk Management Plan (AFMCP 63-101 dated 9 July 1997; and Risk Management Guide, dated June 2003). PERSONNEL RECOVERY VEHICLE AMENDMENT 025 (28 FEB 05) - Request for Information (RFI) 1. The Personnel Recovery Vehicle (PRV) is currently required to be fielded in FY10 with IOC in FY 11. This schedule includes a 2 year Government flight test program. For Block 0, the current PRV acquisition strategy has changed to allow a two-year development program. In order to meet various AFSOC requirements, a Link-16 capability will be required in Block 0. 2. Provide the following information: a. Identify if you will be able to develop a Link-16 capability in the shortened development timespan. b. Identify what Link-16 hardware would be integrated. c. Identify if you would be re-using software developed on another program. If so, please identify program source. d. Identify what Link-16 messages you believe is required for PRV and which messages you would be able to provide in Block 0. e. Identify Block 10 migration plan to transition your proposed Link-16 implementation to a MIDS-JTRS implementation. f. What is your assessment of the risk of this effort and your proposed mitigation plan? g. Would you be integrating Common Link Integration Processing (CLIP) in Block 0 for GIG and/or Airborne Network communication? Explain why or why not. 3. Provide your response not later than 4:00 PM, EST, 7 Mar 05. PERSONNEL RECOVERY VEHICLE AMENDMENT 024 (11 FEB 05) - UPDATED PRV LIBRARY DOCUMENTS The below attached file as of 11 February 2005 is updated to include: AFI 63- XXX, June 2003, Reformed Supply Support; Mil-HDBK-514, 28 March 2003, DoD HDBK, Operational Safety, Suitability, + Effectiveness for the Aeronautical Enterprise; Mil-HDBK-516A, 5 February 2004, DoD HDBK, Airworthiness Certification Criteria. PERSONNEL RECOVERY VEHICLE AMENDMENT 023 (11 JAN 05) SRD RFI extension and Q+A on SRD RFI SRD RFI as shown in Amendment 20 has extended the deadline for response from 11 Jan 05 to 26 Jan 2005. Clarification on SRD RFI: Question: Requirements of sections 3.3.7.8, 3.3.9.3.4, 3.3.9.3.5, and 3.3.9.4.1.4 appear to exceed the CDD. We just wanted to confirm the intent, understanding that this is certainly your prerogative. Response: With respect to 3.3.7.8., the SRD does not necessarily exceed the CDD but rather reflects the use of this capability for night missions and reducing crew workload. (Ref CDD: "Night missions and crew workload require the use of artificial aids to enable night operations. Night operations include the use of Night Vision Imaging System (NVIS) goggles, infrared detection set (IDS), and helmet mounted displays (HMD) or other technologies.") However, at this point in time we do not know the full extent to which HMDs will be used. Question: "The PRV attributes needed to support Initial Operational Capability (Block 0) are addressed by Section 3 statements without symbol markings and those that are followed by "T", unless specifically marked as Block 10 (defined as full capability). ..." This essentially says that anything with no markings or a "T" is a Block 0 requirement, which means nearly everything is a Block 0 requirement. Is this correct? Response: Yes, items with no markings or a "T" are Block 0 requirements as stated by the User. PERSONNEL RECOVERY VEHICLE AMENDMENT 022 (07 JAN 05) - Request for Information See below attached file for RFI (MS word document) and CDD-RFI (MS Excel document). Responses are due NLT 1600 EST, 13 Jan 05. PERSONNEL RECOVERY VEHICLE AMENDMENT 021 (14 DEC 04)- Risk/schedule reduction efforts The Air Force intends to issue four contracts in support of risk/schedule reduction efforts in support of the planned competition for the Personnel Recovery Vehicle (PRV). These contracts will be issued to the contractors who have currently expressed interest in proposing for the PRV program. The goal of the contracts will be to enable the acceleration of the performance of the PRV program after award. The four contracts are planned to be issued to Northrop Grumman, Bell-Boeing, Lockheed Martin and Sikorsy at an estimated value of $1.25M each. PERSONNEL RECOVERY VEHICLE (09 DEC 04) Archived solicitation/synopsis information See below attached file for archived PIXS soliciation synopsis information (initial through Amendment 20). For more information on PRV--Personnel Recovery Vehicle (PRV) please refer to http://www.pixs.wpafb.af.mil/pixslibr/PRV/PRV.asp NOTE: THIS NOTICE MAY HAVE POSTED ON FEDBIZOPPS ON THE DATE INDICATED IN THE NOTICE ITSELF (18-MAR-2005). IT ACTUALLY APPEARED OR REAPPEARED ON THE FEDBIZOPPS SYSTEM ON 19-OCT-2007, BUT REAPPEARED IN THE FTP FEED FOR THIS POSTING DATE. PLEASE CONTACT fbo.support@gsa.gov REGARDING THIS ISSUE.
- Web Link
-
PRV-Personnel Recovery Vehicle (PRV)
(http://www.fbo.gov/spg/USAF/AFMC/ASC/FA8629-05-R-2350/listing.html)
- Record
- SN01438132-F 20071021/071019230023 (fbodaily.com)
- Source
-
FedBizOpps Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's FBO Daily Index Page |