MODIFICATION
A -- Personnel Recovery Vehicles (PRV)- Industry Day
- Notice Date
- 4/2/2004
- Notice Type
- Modification
- Contracting Office
- 1895 5th Street, Bldg. 46 Wright-Patterson AFB, OH, 45433-7200
- ZIP Code
- 45433-7200
- Solicitation Number
- PRV
- Archive Date
- 1/31/2005
- Point of Contact
- Amy Ellis,937.255.2898
- E-Mail Address
-
Email your questions to SOF.PRV@wpafb.af.mil
(SOF.PRV@wpafb.af.mil)
- Small Business Set-Aside
- N/A
- Description
- PERSONNEL RECOVERY VEHICLE AMENDEMENT 007 (2 Apr 04)- Risks The Government held a risk workshop for the PRV program on 23-25 Mar 04. There were over 88 risks identified against a PRV IOC of 2010. Out of the risks identified the Government selected those of which had the highest level of risks and would likely involve industry. Comments/inputs to these risks would be beneficial to the Government. 1. Insufficient manufacturing capabilities 2. GFE not available or identified to meet IOC 3. Inability to obtain timely long lead for test and/or production 4. Based on the ORD, inability to incorporate required technology for IOC 5. Training capabilities may not be timely or integrated to support IOC 6. Inability to complete selection/contracting process in time to support IOC 7. Inadequate funding profile to meet IOC 8. Insufficient DT/IOT+E (including live fire testing) planning, resources, schedule to meet IOC 9. Inability to meet all ORD thresholds by IOC 10. Kirtland may be unable to provide facilities and space to provide training in time to support IOC 11. Engine shaft horsepower (SHP) and specific fuel consumption (SFC) not adequate to meet ORD requirements 12. If horsepower is increased to meet ORD, gearboxes may not be adequate to meet ORD 13. Inability to integrate and meet interoperability requirements 14. Unable to develop/implement system sustainment concept by IOC 15. Insufficient capability to plan, develop, integrate and sustain software 16. Inability to complete Government studies (Downwash, crew station/battlefield airman workload, Phase 1 and Phase 2 mix, defensive weapon study, environmental studies, SATAF planning and implementation, survivability/vulnerability analysis, campaign analysis) in time to support aircraft development, test and operations. 17. Unable to adequately integrate avionics, EW and defensive systems to meet ORD 18. Inadequate digital environment to communicate data/deliverables to meet IOC 19. Inability to verify current systems performance and safety in time to start IOT+E. 20. Inability to use competition effectively to modify and sustain the system cost effectively without obtaining data rights 21. Inability to complete system information security certification prior to IOT+E. 22. Inability to accurately translate user requirements between user and the contractor This is not a Request for Proposal. The Government does not intend to award a contract on the basis of this announcement. Responses to this announcement are voluntary, and participants shall not be compensated. Please submit all responses and/or any additional questions to the PRV mailbox SOF.PRV@wpafb.af.mil . Please do not call. If you wish to speak to someone directly, send an e-mail to the PRV mailbox with the request. PERSONNEL RECOVERY VEHICLE AMENDEMENT 006 (31 Mar 04)- Sikorsky Briefing In response to questions during the one-on-on sessions between Prime Contractors and the ASC/LUH at the 4 March Industry Day, Sikorsky plans to brief the SPO on 14 April at 15:00 for about 1hour. PERSONNEL RECOVERY VEHICLE AMENDEMENT 005 (22 Mar 04)- Team 101 Briefing In response to questions during the one-on-on sessions between Prime Contractors and the ASC/LUH at the 4 March Industry Day, Lockheed Team 101 plans to brief the SPO on 13 April at 10:00 for about 1 hour. PERSONNEL RECOVERY VEHICLE AMENDEMENT 004 (19 Mar 04)- Questions and Answers The following questions were submitted to the government. All questions and answers have been cleared through the Public Affairs office. 1. Question: Could you give a brief description of the areas that are not currently met by the existing fleet of helicopters now or in the expected future that are driving the need for a new platform? Answer: Current deficiencies are: -Service Life. The HH-60G is approaching the end of its useful service life. -Survivability. Insufficient survivability (susceptibility and vulnerability) to ensure mission success against the Defense Planning Guidance (DPG) validated threat environment. This includes a limited electronic warfare suite, insufficient defensive armament for suppression of air and ground threats, and inadequate protection from small arms fire -Range / Combat radius. Aircraft and rotor system design limit unrefueled combat radius. In certain theaters, these characteristics do not meet Combatant Commanders mission requirements for mission execution. -Payload capacity / Cabin volume. Extremely limited cabin space for stowage and employment of mission equipment and crew served weapons, infiltration of Recovery Teams, exfiltration of Recovery Teams and isolated personnel, and medical treatment of isolated personnel. -Battlespace awareness. Lack of line-of-sight (LOS) and BLOS high speed LPE data links for battle space/situational awareness of isolated personnel?s location, threat information, and location of friendly forces. -Mission react time. Deployment shortfalls that prevent current combat rescue forces from being mission ready upon commencement of hostilities ? the most likely time for losses. -Adverse weather capability. Lack of adverse weather penetration system(s) to perform PR missions in a combat environment. ACC conducted an AoA to evaluate potential solutions to current validated deficiencies. A new medium-lift helicopter was recommended as the most cost- effective solution to replace the aging HH-60G. This recommendation was briefed to and approved by the AFROC in June 01. 2. Question: Could you describe the KPPs as they exist for the program now? Answer: ?The PRV with a full, standard configuration load (SCL) must have a straight- line unrefueled combat mission radius of 325 nautical miles (nm). ?The downwash in and around the recovery vehicle produced by the PRV during Hot Day tactical hover operations in all environments (to include heavily forested, steep mountainous, smooth-level, rough-level, smooth-sloped, and rough-sloped terrain in calm and high crosswind conditions with loose particles such as tree limbs, sand, water or rocks in the hover zone) at mid-mission gross weights with SCL in Appendix C must not prevent recovery team or injured and uninjured isolated personnel safe operations (hover extraction operations (hoist), providing emergency lifesaving measures to isolated personnel, placement of a non-ambulatory personnel in a hoist recovery device, overland movement, self- protection, communication, and swimming). ?The PRV must satisfy 100% of top level information exchange requirements (IER) designated as critical. Satisfaction is defined as sender/receiver must be able to execute the required function/mission task without operator intervention. (Interoperability KPP). ?To support Air and Space Expeditionary Force (ASEF) tasking requiring little or no warning, mission ready PRV aircraft, weapons, and support equipment must be capable of worldwide self-deployment (4000 nm) and mission ready within 24 hours of notification or configurable to fit within existing transport aircraft (USAF AMC C-5 and C-17 transport aircraft) within 3 hours of initial notification and capable of being made mission ready within 3 hours upon arrival at destination. 3. Question: What is the projected timeline for the program? Answer: To accelerate procurement and fielding as much as possible from the currently planned IOC of 2014 4. Question: Does the PRV program expect to utilize other platforms, such as UAVs as part of its organic group of systems? Answer: The mission area of CSAR is expected to utilize UAV gathered information to support successful mission execution. 5. Question Mr Vokits spoke of the "Technical Descriptions + Challenges." Could any of those be shared? Answer: The PIXS PRV website contains a downloadable copy of all the briefings used at Industry Day, including those on Technical Descriptions + Challenges. These are related to translating operational requirements into specific technical understanding of the performance requirements. The user, the acquirer, the sustainer and Industry must maintain an active interface and continual interaction throughout the acquisition and sustainment phases to ensure there is minimal confusion on requirements interpretation. This is especially true when using an evolutionary acquisition approach (today+s standard DOD approach to weapons systems procurement). 6. Question: Milestone dates for RFP, SDD award, first flight, opeval, LRIP, RAA, FRP? Answer: No milestone dates have been set. Programmatics are still being developed. A draft schedule leading to contract award was part of the information provided to industry. Please refer to ASC PIXS web site as these dates are developed. 7. Question: Structure and details of competitive phase Answer: Programmatics are still being developed. Please refer to ASC PIXS web site for updates. 8. Question: Specific Block 0 vs. Block 10 capabilities Answer: The block approach requirements are still under development. Please refer to ASC PIXS web site for updates. 9. Question: Concepts for future spirals Answer: Technology insertion and future requirements will be addressed in the Draft RFP. 10. Question: Development and operational test plans? How many test flights are planned Answer: The details have not been worked out. The Test + Evaluation Master Plan (TEMP) has not been drafted but is anticipated on being completed by RFP release. 11. Question: How is the program balancing the risks poised by the aggressive development timeline Answer: The Air force has a Risk Management Process. This process will begin with a Risk Workshop on 23 Mar 04 and will continue throughout the development acquisition phase. 12. Question: From lessons learned in Iraq and Afghanistan, any changes to requirements for performance, range, onboard capabilities, fleet size Answer: The PRV ORD was developed from requirements derived during the CSAR AoA. Lessons learned from Afghanistan and Iraq were incorporated during the draft and coordination process. They will continue to be analyzed as we write and coordinate Change 1 to the ORD. The process to produce Change 1 to incorporate a Block modification approach has already begun. 13. Question: Any participation with navy and marines at this stage in the program? Answer: Not at this time. PERSONNEL RECOVERY VEHICLE AMENDEMENT 003 (15 Mar 04)- Classified Documents The following information is required to request classified PRV documents: - Cage Code - Name of the Document - Your Company+s Security Manager+s (SM) name, phone number and classified mailing address NOTE 1: If ASC/LUH (PRV) is not the originator of the requested document, approval would be required from the originator prior to releasing the document to the requestor. Document requests will be forwarded to the originator by ASC/LU Security Office. You should expect a delay in the receipt of the requested document if prior approval is required. NOTE 2: Foreign Nationals: Visit Notifications must be requested through the appropriate embassy for visit approval. Please direct all requests and questions concerning classified documents to: Ms. Denise D. Quick Chief, ASC/LU Security 937-255-4713 1895 5th Street, Bldg 46 WPAFB, OH 45433 PERSONNEL RECOVERY VEHICLE AMENDEMENT 002 (27 Feb 04)- One-On-One Questions The following questions are to be addressed during one-on-one meetings with the Government and potential prime contractors: 1. What are the main technical/capability differences between your current production or anticipated design(s) and the aircraft needed to meet PRV ORD thresholds. At a subsystem level, characterize the technical effort it would take you to modify your current or anticipated design(s) to (a) a design with the same capability as the current CSAR aircraft (HH-60G) and (b) a design that meet all of the thresholds in the PRV ORD. 2. Using your current production or anticipated design(s) as a technical starting point, what would be the minimum timeframe, including long lead procurement, and minimum number of test assets that would be required to design, integrate, test, ensure adequate production capacity, and produce four LRIP aircraft in both of the configurations listed above? PERSONNEL RECOVERY VEHICLE AMENDEMENT 001 (6 Feb 04)- Industry Day Announcement The Special Operations Forces-Combat Search and Rescue Systems Program Office SOF-CSAR SPO) will host an Industry Day on 4 March 2004 at the Holiday Inn in Fairborn, Ohio to inform industry of a new program to develop and procure 132 Personnel Recovery Vehicles (PRV). This procurement activity is scheduled to begin sometime later this year, and will be a very aggressive, quick moving development program. This Industry Day will be a one day event where the program office will brief industry on what the program entails to ensure that industry has an understanding of the requirements and intent of the PRV program. The agenda is being developed at this time. It will include government briefings on the program, possible acquisition strategies, operator requirements and a question and answer session in the morning. The afternoon will be reserved for prime contractors to meet one-on-one with government representatives to ask questions of a proprietary nature and describe their unique abilities to meet the requirements stated in the operational requirements document. Individuals wishing to attend this Industry Day must register online via the MarketSpace link at the bottom of this page. This Industry Day is restricted to United States citizens. All attendees must present a government issued photo identification, as well as a birth certificate or U.S. passport for registration on the day of the event. The Industry Day will be oriented toward rotary wing prime contractors; contractors who have the ability to design and manufacture medium lift vertical take-off/landing medium lift class vehicles. Suppliers to these prime contractors will also be eligible to attend. Contractors who are interested in obtaining a copy of the draft Operational Requirements Document (ORD) and a draft of the Statement of Objectives (SOO) may request them by sending an e-mail message to SOF.PRV@wpafb.af.mil. All requests must include the company name as well as the Commercial and Government Entity (CAGE) code. REGISTER FOR PRV INDUSTRY DAY: All individuals planning on attending the PRV Industry Day must register online through MarketSpace via the link at the bottom of the announcement. PERSONNEL RECOVERY VEHICLE (Initial) (29 Jan 04) The Special Operations Forces-Combat Search and Rescue Systems Program Office at Aeronautical Systems Center (ASC) is starting up a new program to develop and procure 132 Personnel Recovery Vehicles (PRV). This effort is follow-on to the Analysis of Alternatives (AoA) completed by Air Combat Command (ACC) in 2001 which recommend replacing 104 HH-60G light helicopters with 132 medium- lift helicopters for the combat search and rescue mission. The responsibility for combat search and rescue was transferred from ACC to Air Force Special Operations Command (AFSOC) on 1 October 2003. The operational requirements developed by ACC at the end of the Analysis of Alternatives remain essentially the same. Recently, the USAF has decided to evaluate the possibility of accelerating Initial Operational Capability of the PRV Program. An Industry Day will be held on a date TBA (March 2004 timeframe) at a location TBA in the Dayton, Ohio area. A follow-up announcement specifying the date and place is forthcoming. This is an initial opportunity for industry to meet with cognizant government representatives and discuss the known requirements and intent of the PRV program. This Industry Day will also provide industry an opportunity to comment on the Operational Requirements Document (ORD), to be provided at a later date, and for industry to express an interest in becoming a contender in the PRV program. Contractors will be given an overview of the PRV program. Contractors will also be given an opportunity to discuss their understanding of the program and to present their capabilities/ concepts in general terms during subsequent meetings with the government. This is to be considered an initial step in establishing industry understanding of the PRV program and to allow the government team to determine market understanding and capability to integrate and complete the program. This is not a Request for Proposal. The Government does not intend to award a contract on the basis of this announcement. Submitting capabilities and concepts in response to this announcement is voluntary, and participants shall not be compensated. Any organization or company can obtain Personnel Recovery Vehicle announcements and instructions via the Web at http://www.pixs.wpafb.af.mil. Questions regarding technical information and/or this announcement should be directed to SOF PRV Program office at the following email address: SOF.PRV@wpafb.af.mil. For more information on PRV--Personnel Recovery Vehicles (PRV)- Industry Day please refer to http://www.pixs.wpafb.af.mil/pixslibr/PRV/PRV.asp
- Web Link
-
PRV-Personnel Recovery Vehicles (PRV)- Industry Day
(http://www.pixs.wpafb.af.mil/pixslibr/PRV/PRV.asp)
- Record
- SN00559052-W 20040404/040402212022 (fbodaily.com)
- Source
-
FedBizOpps.gov Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's FBO Daily Index Page |