Atch 5 - Technical Proposal.pdf
PDF 208 KB Posted
- Solicitation number
- HTC71126RE137
About this file
This is a Technical Proposal template for solicitation HTC71126RE137, Point Mugu Range Air Transportation Services (PMRATS), issued by the federal government.
The document serves as an evaluation form requiring offerors to demonstrate technical capability across four subfactors: Fixed-Wing Radar Range Surveillance Requirements, Shipboard Landing, Aircraft Capabilities, and Operations Management & Subcontracting. For Subfactor 1, offerors must provide specific, quantitative performance data for proposed radar systems and aircraft, including radar make/model, ceiling/visibility minimums (200 ft / 0.5 mi threshold), positional accuracy (0.5 NM threshold), probability of detection on first pass (90% threshold), sea state capability (3), target size detection (3 m²), PD range (20 NM), and surveillance rate (3,600 NM²/hr). Aircraft capabilities must include persistence of 4 hours continuous flight time at 40 nm from Point Mugu and up to 8 hours with refueling, along with required communications systems: Maritime VHF Radio, VHF radios, UHF radios, UHF/VHF backup, and Automatic Identification System (AIS) with real-time radar correlation capability. Offerors must submit FAA certifications and approvals for radar installation, or if not yet installed, demonstrate FAA Supplemental Type Certificate (STC) approval. For Subfactor 2, offerors must describe FAA-approved procedures, training, and management controls for Navy shipboard landings per OPNAV Instruction 3100.8C. Subfactor 3 requires identification of specific aircraft proposed for seven capability categories ranging from fixed-wing passenger/cargo with 800-1,600 lbs payload to rotary wing drone recovery up to 2,500 lbs. Subfactor 4 addresses operations management procedures for on-time scheduling and subcontracting arrangements, including operational control definitions per 14 CFR §1.1. Each subfactor will be rated Acceptable or Unacceptable based on whether proposed technical capability meets identified PWS requirements.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| HTC71126RE1370001 SF 33.pdf | ||
| HTC71126RE1370001 SF 30.pdf | ||
| Atch 7 - PMRATS PPQ Rev. 1.docx | DOCX document | |
| Preproposal Conference Agenda_PMRATS.pdf | ||
| Atch 7 - PMRATS PPQ.docx | DOCX document | |
| Atch 10 - Government Furnished Property (GFP) Listing for Solicitation.pdf | ||
| Atch 2 - PMRATS Pricing Table.xlsx | XLSX spreadsheet | |
| Atch 6 - Past Performance Worksheet.pdf | ||
| Atch 8 - Entity Information and Eligibility Sheet.docx | DOCX document | |
| Solicitation - HTC71126RE137.pdf | ||
| Atch 3 - Aircraft Identification Sheet.docx | DOCX document | |
| Atch 4 - Business Compliance Checklist Coversheet.docx | DOCX document | |
| Atch 11 - 2015-5625 Rev 26 Wage Determination Rev 3 Dec 25.pdf | ||
| Atch 1 - PMRATS PWS_16 April 2026.pdf | ||
| Atch 9 - DD Form 254.pdf |
Show all 15
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Source Selection Information – See FAR 2.101 and 3.104 (When filled-in, this Document becomes CUI//SP-SSEL
HTC71126RE137 POINT MUGU RANGE AIR TRANSPORTATION SERVICES (PMRATS)
Attachment 5
Technical Proposal
Offeror Name: ____________________________________________________________
Instructions: Please complete all sections by checking the appropriate boxes (☐) or providing a written response where required. Your responses must be concise, directly address the PWS requirements, and adhere to the text box limitations provided. Additional space is provided on the last two pages to supplement any response. Each subfactor will be rated Acceptable or Unacceptable (see RFP Section M(d)(2)) based on whether the proposed technical capability meets the requirements identified in the questions and PWS references below.
Subfactor 1 – Fixed-Wing Radar Range Surveillance Requirements
1. Offeror shall respond to the following questions as it pertains to Radar Range Surveillance and Clearance requirements, PWS paragraph 1.3.1.1.5.
a. For each PWS paragraph 1.3.1.1.5 attribute listed in the table below, Offerors shall enter the specific, quantitative performance data of their proposed capability/system in Column
3. Replace any placeholder text or other directions in Column 3 with the corresponding information for your proposed aircraft. Cells grayed out do not require a response.
Table 1 Column 1 Column 2 Column 3
Attribute Requirement Threshold Detailed Info
Radar System Make/Model
Aircraft Make/Model
Radar System Capabilities
Ceiling/Visibility Minimums for Operation 200ft / 0.5mi
Positional Accuracy of Track at Probability of Detection (Pdet) Range
0.5 NM
Pdet on the first pass 90% Sea State 3 Target Size 3 m2
PD Range 20 NM Surveillance Rate 3,600 NM2/hr
HTC71126RE137 POINT MUGU RANGE AIR TRANSPORTATION SERVICES (PMRATS)
Attachment 5
Column 1 Column 2 Column 3
Attribute Requirement Threshold Detailed Info
Aircraft Capabilities
Persistence (Yes/No)
4 hours continuous flight time when surveillance area is 40 nm from Point Mugu, and up to 8 hours with refueling at greater distances or when tasked multiple sorties in a single day
Satellite Communications (SATCOM) (Yes/No;
Identify make/model)
Not required;
however, if marked Yes, please specify make/model
Vessel Classification (Yes/No; Describe how system accomplishes vessel classification)
Yes (required)
Maritime VHF Radio (Yes/No) Yes (required)
Very High Frequency (VHF) radios (Yes/No) Yes (required)
UHF radios (Yes/No) Yes (required) UHF and VHF backup (Yes/No) Yes (required)
High Frequency (HF) radio (Yes/No) Not required
Automatic Identification System (AIS) (Yes/No)
Yes (required). AIS tracks should be able to be correlated to the radar tracks real-time onboard
b. Is the proposed Radar installed and operational on the proposed aircraft?
☐ Yes ☐ No
If yes, please provide the date of installation of the system on the aircraft.
Installation Date: __________________
c. Submit all Federal Aviation Administration (FAA) certifications and approvals for the installation and operation of proposed radar as Attachment 1 to this Technical Proposal.
If radar system is not already installed (i.e., selected “No” in paragraph 1.b.), Offeror must demonstrate that the engineering plans have been approved for the proposed radar system via FAA Supplemental Type Certificate (STC) or similar FAA approval. Subfactor 1 will be rated Unacceptable if required certifications and approvals are not provided for the proposed radar system.
d. Describe your capability to perform multiple flights/sorties per day with the aircrew/aircraft (make/model) proposed in Table 1 assuming refueling is available (e.g., One sortie between 0700 – 1100, refueling break between 1100 – 1200, then another sortie between 1200 – 1600).
Response: Enter your response:
Subfactor 2 – Shipboard Landing
1. Describe your company's FAA-approved procedures, training and management controls for performing shipboard landings on Navy vessels in accordance with OPNAV Instruction
3100.8C/PWS 1.3.1.2.
Response: Enter your response here.
Subfactor 3 – Aircraft Capabilities
1. In Column 2, identify all aircraft proposed to satisfy each specified requirement in Column 1.
NOTE: Attachment 3 – Aircraft Identification Sheet to be used to provide additional details on each aircraft.
Column 1 Column 2
Requirement Proposed Aircraft Type/Model/Series/Tail Number
Fixed Wing Passenger/Cargo - 800 lbs.
Payload, 200 NM Range, 4+
PAX/Cargo at maximum ACL (PWS Section 1.3.1.1.1)
Fixed Wing Passenger/Cargo – 1,600 lbs. Payload, 200 NM Range, 8+
Section 1.3.1.1.2)
Fixed Wing Dedicated Large/Bulk Cargo Area (PWS Section 1.3.1.1.3)
Rotary Wing Passenger/Cargo – 1.5 HR Flight Duration @ 1,000 lbs. and
5+ PAX/Cargo at maximum ACL (PWS Section 1.3.1.2.1)
Rotary Wing Passenger/Cargo – 2 HR Flight Duration @ 2,500 lbs. and 9+
Section 1.3.1.2.2)
Rotary Wing Drone Recovery – 500 lbs. (PWS Section 1.3.1.2.3)
Rotary Wing Drone Recovery – 2,500 lbs. (PWS Section 1.3.1.2.3)
Subfactor 4 – Operations Management & Subcontracting
1. Describe your company’s operations management procedures to demonstrate the capability of ensuring on time scheduling per PWS Sections 1.3.3.1 – 1.3.3.7.
2. If using an affiliate, subsidiary, or subcontractor, describe the technical roles and responsibilities of the Offeror and each affiliate, subsidiary, or subcontractor (as applicable), identifying the specific PWS requirement (notated with PWS paragraph and requirement) that each entity will perform and which entity will have operational control, as defined in 14 CFR §1.1, of the aircraft offered to perform any aircraft tasks (PWS 1.3.1). For any aircraft tasks under which operational control is not by the Offeror, explain how the Offeror will maintain operational oversight over the aircraft to ensure all performance requirements are met, to include coordinating scheduling, mission changes and cancellations.
Additional Response Space - This page is provided for the Offeror to expand on their responses to any of the above items. For each response, please identify the item number from above associated with the response. If the Offeror chooses not to expand on any of the items, please indicate on this page “This page intentionally left blank.”
Response: Enter additional responses here.
Additional Response Space - This page is provided for the Offeror to expand on their responses to any of the above items. For each response, please identify the item number from above associated with the response. If the Offeror chooses not to expand on any of the items, please indicate on this page “This page intentionally left blank.”
Response: Enter additional responses here.
| Offeror Name: |
| Detailed InfoRadar System MakeModel: |
| Detailed InfoAircraft MakeModel: |
| 200ft 05mi: XX ft / XX mi |
| 05 NM: XX NM |
| 90: XX% |
| 3: # |
| 3 m2: X m2 |
| 20 NM: XX NM |
| 3600 NM2hr: XXX NM2/hr |
| 4 hours continuous flight time when surveillance area is 40 nm from Point Mugu and up to 8 hours with refueling at greater distances or when tasked multiple sorties in a single day: YES/NO |
| Not required however if marked Yes please specify makemodel: YES/NO |
| Yes required: YES/NO; Additional space provided in last two pages |
| Yes required_2: YES/NO |
| Yes required_3: YES/NO |
| Yes required_4: YES/NO |
| Yes required_5: YES/NO |
| Not required: YES/NO |
| Yes required AIS tracks should be able to be correlated to the radar tracks realtime onboard: YES/NO |
| If yes please provide the date of installation of the system on the aircraft: Off |
| Installation Date: |
| Response Enter your response: |
| Response Enter your response here: |
| Proposed Aircraft TypeModelSeriesTail NumberFixed Wing PassengerCargo 800 lbs Payload 200 NM Range 4 PAXCargo at maximum ACL PWS Section 13111: |
| Proposed Aircraft TypeModelSeriesTail NumberFixed Wing PassengerCargo 1600 lbs Payload 200 NM Range 8 PAXCargo at maximum ACL PWS Section 13112: |
| Proposed Aircraft TypeModelSeriesTail NumberFixed Wing Dedicated LargeBulk Cargo Area PWS Section 13113: |
| Proposed Aircraft TypeModelSeriesTail NumberRotary Wing PassengerCargo 15 HR Flight Duration 1000 lbs and 5 PAXCargo at maximum ACL PWS Section 13121: |
| Proposed Aircraft TypeModelSeriesTail NumberRotary Wing PassengerCargo 2 HR Flight Duration 2500 lbs and 9 PAXCargo at maximum ACL PWS Section 13122: |
| Proposed Aircraft TypeModelSeriesTail NumberRotary Wing Drone Recovery 500 lbs PWS Section 13123: |
| Proposed Aircraft TypeModelSeriesTail NumberRotary Wing Drone Recovery 2500 lbs PWS Section 13123: |
| Response Enter your response here_2: |
| Response Enter your response here_3: |
| Response Enter additional responses here: |
| Response Enter additional responses here_2: |
File details come from the government source that posted it. Updated .