FA855226RB001 RFP Attachment 14 Section L.pdf

18 June 2026

Source Selection Information -- See RFO 2.101 and 3.104 – FOR OFFICIAL USE ONLY

Section L – Instructions to Offerors

I. Proposal Format

A. General:

The following instructions cover the preparation and submittal of the offeror’s proposal for this solicitation.

Offerors must follow the instructions contained herein. Offerors are cautioned that any noncompliance with the terms and conditions of the Request for Proposal (RFP) may cause their proposal to be determined not eligible for award. If a joint venture arrangement exists for this acquisition, the offeror shall provide a copy of the joint venture agreement that is signed and dated by all joint venture members as part of the proposal submission. A joint venture is defined as a contractual agreement joining together two or more parties to undertake a particular business transaction or project and is intended to exist for a limited time period. The individual entities may retain their individuality and operate under a joint venture agreement, or the joint venture creates a separate corporation, limited liability company, or membership.

Offerors shall submit only one proposal for the HH-60W Degraded Visual Environment System (DVES) as the Government will review only one proposal per offeror. Proposals received are subject to the requirements specified in Revolutionary FAR Overhaul (RFO) 52.212-1, unless otherwise tailored in the Addendum to the solicitation. Proposals must be received electronically by AFLCMC/WIUKB (Attn:

Millie Danko, millie.danko@us.af.mil; Theresa Younce, theresa.younce@us.af.mil; and Jason Grizzard, jason.grizzard@us.af.mil no later than the date and time specified in Block 8 on the face page of the RFP. All submissions must follow the instructions in Section B.

Offerors are requested to submit Volume IV, Past Performance Information, so that it is received ten (10) calendar days prior to the required due date for proposals. Failure to submit Volume IV by the earlier date will not result in offeror disqualification.

B. Communications All exchanges of source selection information between the Government and offerors will be controlled by the Contracting Officer through the Contracting Specialist. If email is used to transmit such information, it must be sent in an encrypted format and include "Source Selection Information – See RFO 2.101 and 3.104” in the subject line. To facilitate the sending and receiving of encrypted emails, offerors are required to use either MS Outlook configured to support encryption or another email product that is S/MIME compatible and similarly configured. If you intend to submit your source selection information via encrypted email, you will need to contact the Contracting Officer indicated on the face page of the solicitation prior to the proposal due date in order to exchange certificates used for encryption. To ensure the secure transmission process functions correctly, offerors are requested to complete the encryption certificate exchange at least seven (7) days prior to the proposal due date. If an offeror's computer system cannot support encryption technology, the offeror shall send the PCO correspondence at the time that it submits its proposal stating that it accepts the risk of sending and receiving unencrypted electronic mail if it chooses to utilize unencrypted email as a channel of communication.

When submitting source selection information electronically, file suppression utilities, to include but not limited to zip files, will not be accepted. If an offeror's computer system cannot support encryption technology, the offeror shall send the PCO correspondence at the time that it submits its proposal stating that it accepts the risk of sending and receiving unencrypted electronic mail if it chooses to utilize unencrypted email as a channel of communication.

Note: When sending files via encrypted email, please note there is a size limit of 20MB.

https://www.google.com/url?q=mailto%3Amillie.danko%40us.af.mil mailto:theresa.younce@us.af.mil https://www.google.com/url?q=mailto%3Ajason.grizzard%40us.af.mil

Proposals must be submitted electronically utilizing the Solicitation Module in Procurement Integrated Enterprise Environment (PIEE), accessible at https://piee.eb.mil. For detailed proposal submission guidance, refer to How to Post Offer on PIEE (RFP Attachment 2). Offerors are responsible for ensuring they are registered in PIEE with the necessary "Proposal Manager" role; for registration assistance Instructions to register a PIEE account (RFP Attachment 1).

Offerors unable to access Solicitation Module may submit proposals through Department of Defense Secure Access File Exchange, also known as DoD SAFE at https://safe.apps.mil/security.php. Offerors shall notify Millie Danko, millie.danko@us.af.mil, Theresa Younce, theresa.younce@us.af.mil, and Jason Grizzard jason.grizzard@us.af.mil prior to proposal submittal. This is a mandatory step for all submissions made outside of the primary Solicitation Module. Proposals must be submitted by the time specified in this solicitation. Submission by any other means, such as mail, hand-delivery, or email, is not authorized and will not be considered. Late submissions will be handled in accordance with RFO provisions.

Note: When sending files via DoD SAFE, please note there is a size limit of 8GB, as well as a 25 files number limit. Offerors shall advise the PCO and buyer of any submissions that will be outside of these limitations so that multiple DoD SAFE drop-off request links can be sent. A formal notice must be sent to the PCO and Contracting Specialist for a drop-off link to be sent. Drop-off request/links sent to companies by the Government are only valid for 14 days. Additionally, drop-off request/links are only good for one submittal per use.

II. Volume Organization

A. General:

Proposals shall be submitted to the Government in Six (6) separate volumes as set forth below:

VOLUME PAGE

LIMITS

DESCRIPTION

I (*) 6 Completed RFP

II 80 Technical Proposal

III 15 Schedule

IV (**) 15 Past Performance

V 10 Small Business Participation

VI (***) N/A Cost/Price Proposal

Proposal Submission and Formatting: Offerors are required to submit the Technical Proposal, Schedule, Past Performance, Small Business Participation, and Cost/Price Proposal electronically via the Solicitation Module in PIEE, DoD SAFE, or encrypted email. Offerors shall use the instructions set forth in the RFP Attachment (Attachment 3), Past Performance Information (PPI) for Offerors, to electronically submit the Past Performance information. RFP Attachment 3, PPI Tool is attached to the solicitation posting.

Note: Media must be virus scanned by the offeror prior to submitting to the Government.

https://piee.eb.mil/ https://usg02.safelinks.protection.office365.us/?url=https%3A%2F%2Fsafe.apps.mil%2Fsecurity.php&data=05%7C02%7Clayne.churchill%40gtri.gatech.edu%7C36622c42673a43b981a608de90b97a49%7Cb2b2cc37ea504f2a803b2368611460b8%7C0%7C0%7C639107323447607959%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=tcTPvE%2FDPDbrDkcgML0UY6jMa8JT2as6EliTcQpnPE4%3D&reserved=0 mailto:millie.danko@us.af.mil mailto:theresa.younce@us.af.mil mailto:jason.grizzard@us.af.mil

* The completed RFP shall include all applicable administrative and compliance documents, specifically the Voluntary Protection Program (VPP) Information, Cross Reference Matrix, Small Business Subcontracting Plan, Supplier Performance Risk System rating, Joint Venture Agreement, and Cybersecurity Maturity Model Certification.

** Past Performance (Volume IV) must adhere to the instructions in Past Performance Information for Offerors (RFP Attachment 3) and include the completed FACTS Sheet (RFP Attachment 4).

*** Volume VI shall serve as the official Cost/Price Proposal and must consist of the fully populated Cost Model (RFP Attachment 11), alongside Cost Price Spreadsheet (RFP Attachment 12).

Note: If applicable, add Summary Page, Contractor Performance Assessment Report System (CPARS), Proposed Critical Subcontractor Signed Commitment, FACTS Sheet, Client Authorization Letter, Transmittal Letter, Proposed Critical Subcontractor/Joint Venture Member Consent Form In addition to the page limitations specified herein, all proposal volumes submitted electronically via the Solicitation Module in PIEE, DoD SAFE, or encrypted email must comply with the following format, and each volume within the proposal shall be separately tabbed and identified:

1. Document Formatting:

• All proposal documents shall be in English, with any monetary values expressed in United States dollars.

• The text must use a Times New Roman font, size 12 or larger.

• Page margins must be at least one (1) inch on all sides.

• The standard page size shall be 8.5" x 11". Pages containing charts, graphs, or illustrations may be up to 8.5" x 14".

• All pages within each volume must be numbered consecutively. Elaborate formatting or color presentations are not required.

2. File Naming and Identification:

• Each electronic file must be clearly marked with the RFP number, the offeror’s name, and the corresponding Volume number (e.g., Volume I, Volume II).

• To verify formatting, the Technical Proposal must be submitted in both Microsoft Word and searchable PDF formats.

3. Page Limitations:

• Volume II, Technical Proposal: Limited to 80 pages.

• Volume III, Schedule: Limited to 15 pages

• Volume IV, Past Performance: Limited to 15 pages

• Volume V, Small Business Participation: Limited to 10 pages.

• These limits are inclusive of all content (cover pages, charts, tables, etc.) but exclude a table of contents or a list of acronyms. Any pages exceeding these limitations will be removed and will not be considered in the evaluation.

• Page limitations for responses to Evaluation Notices (ENs), if issued, will be specified in the EN itself.

4. Proprietary Information:

• Each page containing proprietary information must be marked appropriately by the offeror.

• Offerors must ensure that each page containing proprietary information is clearly and appropriately marked.

5. Proposal Submission Method:

• All proposal documents, including the initial submission, must be submitted electronically via PIEE, DoD SAFE, or encrypted email.

B. Volume I, Completed RFP

1. General:

Volume I, Completed RFP, shall consist of the completed and signed Request for Proposal (RFP) including all issued amendments accompanied by a cover letter delineating any exceptions taken to the terms and conditions with their associated rationale, the Voluntary Protection Program (VPP) Information (RFP Attachment 10), and a Cross Reference Matrix (RFP Attachment 5).

Offerors shall ensure that all clauses and provisions that require “fill-in” information are appropriately completed. Offerors shall not include prices in the submitted RFP. Proposed prices shall be submitted in Volume VI, (RFP Attachment’s 11 and 12). See paragraph Volume VI Section 9 below for further instructions on submitting proposed prices/costs.

Be advised that any noncompliance with the terms and conditions of the RFP may result in the proposal being determined ineligible for award. The Government reserves the right to independently identify exceptions taken to the terms and conditions of the RFP outside of those identified in the offeror’s cover letter.

2. Voluntary Protection Plan (VPP):

Voluntary Protection Plan: Air Force Voluntary Protection Program (VPP) requirements are applicable to this acquisition as work on an Air Force installation will be required by contractor employees working 1,000 hours or more in any calendar quarter and the employees are not directly supervised by the Air Force installation. As part of Volume I, for each of the past three (3) calendar years immediately prior to the calendar year in which this solicitation is being issued (i.e., calendar years 2025, 2024 and 2023, submit your Total Case Incidence Rates (TCIR) and Day Away, Restricted, and or Transfer Case Rates (DART) for the standard Industrial Classification System (SIC) code or North American Industrial Classification Systems (NAICS) code for the applicable industry as identified on the face page of this solicitation. If TCIR/DART rates are not maintained, submit comparable rates by completing RFP Attachment 10, DART – TCIR Chart. This VPP information shall be no more than four (4) pages.

Note: This VPP information pertains to the offeror. If an unpopulated joint venture is formed (a joint venture in which the employees are employed by the joint venture partners and not the joint venture itself), each joint venture partner must submit these rates. Any proposed subcontractor with employees working 1,000 or more hours in any calendar quarter on an Air Force installation whose subcontractor employees are not directly supervised by the Air Force installation must submit these rates as well. For information on TCIR/DART rates, visit the following VPP site: https://www.osha.gov/dcsp/vpp/index.html.

3. Cross Reference Matrix:

The offeror shall complete the Cross-Reference Matrix (RFP Attachment 5). This matrix must clearly indicate the page and section number in the proposal that corresponds to each requirement listed in the RFP. The Cross Reference Matrix will be utilized as a tool to show critical interrelationships and dependencies among the technical requirements documents (System Requirements Document (SRD), Performance-Based Work Statement (PWS), the Contract Line Item Number (CLIN), the Contract Data Requirements List (CDRL), Section L (Proposal Requirements), and Section M (Evaluation Basis for Award). The cross-reference matrix will help an offeror ensure it has responded to all the evaluation criteria and proposal submittal requirements identified in the solicitation. If the matrix conflicts with any other requirement, direction, or provision of this solicitation, the other reference shall take precedence over the matrix. Additionally, Section M references in the matrix are for informational purposes only, and the Government shall be obligated to evaluate proposals solely in conformance with Section M of the solicitation.

https://www.osha.gov/dcsp/vpp/index.html

4. Small Business Subcontracting Plan:

The small business subcontracting plan required by RFO Clause 52.219-9, as supplemented by the Revolutionary Defense Federal Acquisition Regulation Supplement (R-DFARS) and Department of Air Force (DAF) Contract Compass shall be submitted by large business offerors. The plan shall set forth the offeror’s plan for subcontracting with small businesses to the maximum extent practicable, in accordance with RFO Clause 52.219-9 as supplemented by the R-DFARS and DAF Contracting Compass. The small business subcontracting plan shall include the information required by RFO Clause 19.206-2 and all associated clauses within this RFP.

Note: The small business subcontracting plan is required by large business offerors only.

5. Cybersecurity Maturity Model Certification (CMMC):

Offerors shall have a current, as defined in R-DFARS 240.371.2, CMMC Level two (2) posted within SPRS as required by R-DFARS provision 252.204-7025 and clause 252.204-7021 as of the RFP due date in paragraph I.A above.

6. Supplier Performance Risk System:

If available, offerors shall have a current assessment in the Supplier Performance Risk System (SPRS) as required by R-DFARS 252.204-7019 and R-DFARS 252.204-7020. An assessment date is considered current within the last three years of this solicitation issuance. The Government will consider the offeror’s risk assessment for item, price, and supplier risk, as applicable. Offerors are able to access their risk assessments by following the access instructions in the SPRS users guide available at https://www.sprs.csd.disa.mil/reference.htm.

C. Volume II, Technical Proposal

1. General:

The technical proposal shall be clear, concise, and include all the information required by this provision in sufficient detail for effective evaluation. The proposal should not simply rephrase or restate the Government’s requirements. Rather, the offeror shall provide convincing rationale to address how the offeror intends to meet these requirements. Offerors assume the Government has no prior knowledge of their capabilities, work processes, facilities, and experience and will base its evaluation on the information presented in the offeror’s technical proposal.

2. Format and Specific Content:

The following information shall be provided in the technical proposal and will be evaluated to assess the proposed technical approach and associated technical risk in accordance with Section M-900, Evaluation Basis for Award. The technical proposal shall address each of the following subfactors to describe the offeror’s proposed approach to performing the requirements set forth in the PWS and SRD. For each subfactor, the offeror shall identify risks, if any, associated with the proposed approach and actions the offeror will take to mitigate the identified risks. If no risks/mitigations are identified in the offeror’s proposal, it indicates the offeror does not consider there to be any risk associated with their proposed approach. The Government reserves the right to independently identify risks with the proposed approach outside of those risks identified by the offerors themselves. The proposal shall provide a detailed narrative and supporting documentation that illustrates the offeror's understanding of, approach to, and current and planned capability to address all the following technical subfactors.

Note: To assist with streamlining the evaluation, offerors shall address only one subfactor per section in the technical proposal, avoid including subfactor discussions in multiple sections, and use the same headings, subfactor numbers, and paragraph numbers as used in this paragraph.

https://www.sprs.csd.disa.mil/reference.htm

a. Subfactor One: Technical Readiness Level (TRL) and Manufacturing Readiness Level (MRL) The offeror shall address this subfactor by assessing the TRL and MRL of their proposed materiel solution and providing evidence to support the assessment. DVES is designated as a Permanent Safety modification to the HH-60W. To minimize technical risk and expedite fielding, the Government seeks a mature materiel solution at a TRL of eight (8) or greater, and a MRL of nine (9) or greater. It is expected, however, that to meet the specific requirements for DVES, offerors may need to include in their proposal some lower TRL/MRL physical or logical components requiring further development. Per the instructions that follow, offerors are encouraged to clearly state and delineate those physical or logical components of the proposed system requiring further development and provide a development plan and schedule for them.

The offeror shall assess the TRL and MRL of their proposed solution in accordance with (IAW) the Office of the Under Secretary of Defense for Research and Engineering (OUSD(R&E)) Technology Readiness Assessment Guidebook and Manufacturing Readiness Level Deskbook, as referenced in the PWS. The offeror may also use Human Readiness Level (HRL) as defined in ANSI/HFES 400-2021 in their assessment of Pilot-Vehicle Interface (PVI) and maintainer-vehicle interface (MVI) components of the system. The offeror shall provide evidence supporting their assessment in the form of analyses, test results and data, production numbers, field reports, operational statistics, and/or roadmaps for incremental and generational product improvement based on operational lessons learned. Specifically, the offeror shall provide an assessment and supporting evidence for the following:

(1) The TRL and MRL of the system components.

(2) The TRL and, as appropriate, HRL of the integrated system, encompassing the end-to-end data acquisition, processing, and pilot-vehicle interface (PVI) controls and displays with respect to the specific application of rotary wing operations in Degraded Visual Environments (DVE) as described in the DVES Concept of Operations (CONOPS) and DVES System Requirements Document (SRD) Sections 3.2.1 – 3.2.3. The assessment must clearly and explicitly address all aspects of the integration approach provided in response to Subfactor Two and the PVI approach provided in response to Subfactor Three.

(3) The TRL of integrated system capabilities for providing improved situational awareness (SA) for aircrew in the following:

(a) aircraft-induced DVE (i.e., brownout, whiteout), per SRD Sections 3.2.3.5 – 3.2.3.10

(b) ambient DVE (i.e., smoke, rain, fog, smog, clouds, darkness, flat light, and blowing sand, dust, and snow), per SRD Sections 3.2.3.4 and 3.2.3.11

(c) adverse mission conditions such as GPS-Degraded/Denied Navigation (SRD Section

3.2.10.8) and engagement of platform weapons (SRD Section 3.6.12.22) The assessment must address all hardware, software, and algorithmic components involved in delivering the stated capabilities. The assessment shall specifically cover the offeror’s methodology for implementing the “see-and-remember” technique to recall previously sensed obstacles and hazards in conditions where the sensor(s) may be degraded by DVE conditions per SRD Section 3.2.10.2.

(4) The TRL for any physical or logical component of the proposed system requiring additional development prior to or during the DVES program to specifically meet the requirements of DVES as documented in the DVES SRD. This assessment must include a development plan and schedule for the identified component(s).

b. Subfactor Two: Integration The offeror shall describe their approach to integrating DVES into the HH-60W aircraft and its use into operational tactics, techniques, and procedures (TTPs) IAW the DVES SRD and CONOPS as described below. The offeror shall provide block diagrams indicating hardware and software interfaces between DVES components and existing HH-60W hardware and software, including ground support and mission planning hardware and software. The offeror shall clearly identify and scope any modifications to existing platform systems that would be required to integrate their proposed solution. The offeror shall assume, IAW SRD Section 3.2.4, that the scope of DVES integration is limited to the following under the current program:

• Interfaces to the specific systems identified in SRD Sections 3.2.4.4, 3.2.4.5, 3.2.4.6, and 3.2.4.10

• Implementation of Logical Interfaces (SRD Section 3.1.3.1) and provision of Physical Interfaces (SRD Section 3.1.3.2) for other aircraft systems as prescribed throughout the SRD

Implementation of Logical Interfaces on existing platform systems to fully functionalize the interfaces developed under the second bullet above is outside the scope of the current DVES program. The Government may, at its discretion, choose to implement these Logical Interfaces under a separate effort concurrent with or subsequent to the current DVES program. The offeror shall refer to the descriptions they provide in this Subfactor in their assessment of TRL in number (2) of Subfactor One. Specifically, the offeror shall describe their approach to satisfying the following HH-60W integration requirements:

(1) Integration of DVES with existing MFDs to provide two (T) or four (O) independent video sources supplying the four-pilot station MFDs and two crew station MFDs IAW SRD Sections

3.2.4.5 and 3.2.8.

(2) Integration of DVES with the Flight Management System (FMS) or other aircraft bus or subsystem to ingest flight plans, waypoints, and storepoints IAW SRD Sections 3.2.4.6, 3.2.12.1 – 3.2.12.5, and 3.2.12.7.1 – 3.2.12.7.2, and to save storepoints to the FMS IAW SRD Sections

3.2.4.7 and 3.2.12.6.

(3) Integration of DVES with the Integrated Vehicle Health Management System (IVHMS) for publishing maintenance data IAW SRD Section 3.2.4.10.

(4) Integration of DVES with mission planning software and processes IAW SRD Section 3.2.4.12, including the ability to utilize the DVES World Model to inform After Action Reports (AARs) and future mission planning IAW SRD Sections 3.2.10.1 – 3.2.10.7.

(5) Integration of DVES in a manner that satisfies the following physical integration requirements:

(a) size, weight, and power requirements IAW SRD Sections 3.2.4.1, 3.6.2, 3.6.8.2, and

3.6.12.14; and PWS Sections 4.7.7, 4.7.8, 4.7.23, and 4.7.26

(b) EMI/EMC requirements in SRD Section 3.6.4

(c) Functional isolation requirements in SRD Section 3.6.1.

c. Subfactor Three: Pilot-Vehicle Interface (PVI) The offeror shall describe their approach to providing PVI controls and displays to meet the DVES requirements as documented in the DVES SRD. In addition to describing display content, the contractor shall describe the complete end-to-end data acquisition and processing chain used to render the display IAW the Dynamic Latency limit set in SRD Section 3.2.7.19 and with Sensor Latency within the limits implied by SRD Section 3.2.3. The offeror shall refer to the descriptions they provide in response to this Subfactor in their assessment of TRL as referenced in section two (2) of Subfactor One. Specifically, the offeror shall describe their approach to providing the following PVI elements:

(1) Spatially and temporally registered sensor imagery and symbology that enables aircrew to assess closure rates and distances to obstacles, including terrain, IAW SRD Sections 3.2.1 – 3.2.3, and

3.2.7.1 – 3.2.7.3.

(2) Spatially and temporally registered sensor imagery and terrain-conformal landing zone symbology as described in SRD Section 3.2.9.4 – 3.2.9.5 under the scenario of a direct approach using DVES Sensors to measure the elevation landing point IAW SRD Section 3.2.5.1.

(3) Controls for system and display configuration functions IAW SRD Section 3.2.6, 3.2.7.7 – 3.2.7.9, 3.2.8.3, 3.2.8.5, and 3.2.15.

(4) Controls and displays for previewing the DVES Flight Plan and DVES World Model data IAW SRD Sections 3.2.13.5 – 3.2.13.13.

(5) Visual and aural warnings, cautions, and advisories (WCAs) IAW SRD Section 3.2.14 and indication of diminished DVES Sensors capability IAW Section 3.2.5.7.

d. Subfactor Four: Sustainment The offeror shall describe and provide supporting evidence for the overall sustainability of their proposed materiel solution, addressing all aspects of DVES to include hardware, software, and documentation. The offeror shall describe their design approach for ensuring reliability and maintainability of the system. The offeror shall also describe their recommended approach to sustaining DVES throughout all phases of the program from Engineering and Manufacturing Development (EMD), through production and deployment (P&D), to Operations and Sustainment (O&S). The offeror shall also describe their recommended approach and experience for developing and releasing training material, technical data products (to include diagrams, drawings, technical documentation of hardware and software, logistical documentation) and Technical Orders (TOs). Specifically, the offeror shall address the following:

(1) The approach for transitioning DVES to organic Government sustainment at the outset of the O&S phase of the program. The approach must address all aspects of DVES sustainment related to hardware, firmware, software, support equipment, and documentation as listed below. Aspects of DVES sustainment that will require continuing Contractor Logistics Support (CLS) from the OEM and/or subcontractors must be clearly identified and defined in the proposal. The proposal should highlight options that may exist for pursuing greater logistical efficiency through partnering with other services already using DVES or DVES component LRUs. Tasks related to sustainment include repair, replacement, overhaul, recurring maintenance, calibration/alignment, installation, upkeep, tooling, support equipment, diagnostics and troubleshooting, obsolescence and potential for upgrade/replacement, and maintenance design (“design for maintainers”). Reference SRD Section 3.4.1 and PWS Sections 4.4 and 4.13 for further tasks and requirements.

(2) The approach for transitioning DVES software to full life-cycle, organic Government sustainment to enable the Government to develop and field software modifications and enhancements, apply cybersecurity updates, and change configuration settings. The proposal must address all aspects of software/firmware sustainment, including software/firmware tools, licensing, data rights, Integrated Development Environment (IDE), source/binary, and build/release items to enable full government sustainment IAW PWS Section 4.6 and 4.14. Additionally, the proposal must address the approach to delivering the technical data necessary to support organic Government sustainment, including all technical data related to software design, interfaces, operation, and development/release environments.

(3) The approach for developing and modifying Technical Orders (TOs). The proposal must address the approach for developing DVES kit installation procedures and performing modifications to the 1H-60(H)W-1 Flight Manual and elements of the Interactive Electronic Technical Manual (IETM) for the HH-60W platform to address system operation, crew duties, diagnostics, troubleshooting, and maintenance. The proposal must address the “design-for-maintainer” approach to be used. The proposal must also address the approach for developing and delivering training materials and initial in-person DVES training and familiarization, enabling “Train-the-Trainer” functionality, and implementing DVES trainer devices and simulators such that aircrew and maintainers alike can become proficient with all aspects of DVES as installed, operated, and maintained on the HH- 60W. The proposal must also address the approach for developing and releasing technical drawings, functionality descriptions, diagrams, illustrations, notes, and other documentation per PWS Sections 4.9, 4.10, and 4.13, and all relevant CDRLs.

(4) The offeror shall provide evidence supporting the sustainability of their proposed materiel solution in the form of projected reliability, availability, and maintainability metrics based on current actual operational factors and metrics; relevant failure reporting, analysis, and corrective action system (FRACAS) metrics for existing relevant systems, and/or a Basis of Estimate (BoE) for LRU repair costs, spares/provisioning, and CLS.

Document supply, support, and logistics including packaging, handling, storage, and transportation (PHS&T), to include kit production and distribution/installation, item marking and tracking, and overall implementation of an Integrated Logistics Support Plan (ILSP) across the life-cycle of the system.

D. Volume III, Schedule

1. General:

The offeror shall submit a proposed project schedule that aligns with the contract baseline schedule in the Statement of Objectives (SOO), which is included as an appendix in the DVES PWS. The offeror shall present a realistic schedule that adequately accounts for non-recurring engineering (NRE), integration, and testing of the DVES materiel solution IAW the technical approach described in Volume II, Technical Proposal.

2. Format and Specific Content:

The offeror shall provide a Gantt chart that features, at minimum, the program meetings and technical reviews prescribed by PWS Section 4.13 and all major tasks to be performed to accomplish the technical approach described in Volume II, Technical Proposal. The offeror shall also provide a narrative that identifies any assumptions made in developing the schedule and any external factors outside the offeror’s control that may impact the critical path of the program. The combined Gantt chart and narrative shall conform to the page limit specified in Section L, II(A). The offeror shall clearly indicate in the schedule when the first complete DVES kit will be ready for integration into the HH-60W SIL, and when the Prototype Installation (PI) kit will be ready for integration into the designated HH-60W test aircraft. The offeror shall clearly indicate, either in the schedule or the accompanying narrative, when Government- Furnished Information and/or Equipment (GFI/GFE) will be required to maintain the proposed schedule during the Engineering & Manufacturing Development (EMD) phase of the program. Examples of GFI/GFE required during the EMD phase may include, for example,

(1) Pilot and aircrew input to support Crew Station Working Groups (CSWGs).

(2) Software interfaces for DVES developed under Government direction for existing equipment (e.g., AMC, FMS, SGBA, etc.) to support component level interface testing.

(3) Site surveys of the HH-60W SIL and Prototype Installation (PI) aircraft.

(4) Government reviews and feedback on technical deliverables.

E. Volume IV, Past Performance

1. General:

The offeror shall submit present and past performance information for itself and any joint venture member, as well as each proposed critical subcontractor in accordance with the format contained in Facts Sheet (RFP Attachment 4), and the following paragraphs. A critical subcontractor is defined as an entity (subcontractor and/or teaming contractor), other that the offeror itself, that will perform more than 30 percent of the overall effort, based on the sum of the price proposed for each contract line item and/or possesses the business license the prime contractor is relying on to perform the effort of the Performance Work Statement (PWS) and SRD. If proposed critical subcontractor experience is submitted for consideration as part of the proposal, the offeror shall include a commitment signed by the offeror and the proposed critical subcontractor certifying that if a contract is awarded resulting from the proposal, the parties commit to joint performance as proposed. If the signed commitment is not fully executed by both parties and provided with the Past Performance Proposal, proposed critical subcontractor references will not be evaluated or considered.

2. Past Performance Format:

The requested present and past performance information shall be provided in a separate volume labeled "Volume IV - Past Performance". A summary page shall be provided for this acquisition, describing the proposed role of the offeror, any joint venture member and critical subcontractor (nature of work and percentage of overall work). Summary page information must clearly communicate that proposed critical subcontractor(s) meet the definition of a critical subcontractor established above. Efforts submitted for proposed critical subcontractors in which a signed commitment is not fully executed by both parties or is not provided with the proposal will not be evaluated ach offeror/joint venture member and critical subcontractor collectively shall complete information for three (3) active or completed efforts in the past seven (7) years from the issuance date of the RFP that the offeror/joint venture member and critical subcontractor consider relevant in demonstrating its ability to perform the proposed effort. Each effort's summary page be limited to one (1) page to ensure concise and focused responses. If the total number of such contracts exceeds three (3), each offeror/joint venture member/critical subcontractor collectively shall address its three (3) most recent and relevant contracts.

The Government reserves the right to independently identify recent and relevant efforts outside of those submitted by the offerors themselves.

The offeror's/joint venture member’s or critical subcontractor’s present and past performance information may collectively include data on efforts performed by other predecessor companies, affiliates, other divisions or corporate management if such was provided for evaluation and if the offeror’s past performance volume demonstrates the company, affiliate, or division will provide the offeror with resources for the instant proposed effort, such as workforce, management, facilities, or other capabilities demonstrating direct and meaningful involvement in the performance of the instant proposed effort. The information shall clearly indicate the division or corporate organization that performed or is presently performing the contract. Contracts listed may include those with the Federal Government, state and local governments or their agencies, and commercial customers. If submitting this information via DoD SAFE or encrypted email, utilize the FACTS Sheet (RFP Attachment 4). Offerors/joint venture members/critical subcontractors shall furnish all available CPARS for the efforts submitted for evaluation, as applicable.

Submittal of any CPARS for the efforts submitted for evaluation are not included in the page limitations.

Note: All past performance summaries, including those for critical subcontractors, must be submitted directly by the Prime Offeror. Independent submissions from subcontractors will not be accepted.

3. Ordering Type Contracts Submission:

If the contract you are submitting is an ordering type contractual vehicle (for example, including but not limited to an Indefinite Delivery “D” type contract per RFO Clause 16.5), only after issuance of a delivery/task order does performance occur. Given this, an individual order (or series of orders) under the basic ordering contract shall be submitted, in lieu of just the basic ordering contract itself. All information provided to the Government, for an ordering type contractual vehicle, shall be at the order level (i.e. a delivery/task order). Offerors are hereby cautioned that the Government will not evaluate basic ordering contracts without associated orders identified When submitting an individual order (or series of orders) under an ordering type contractual vehicle, it is important that the offeror’s past performance information be accurate, complete, and in the correct format.

If the information is not submitted in the correct format, the Government will not be able to evaluate the effort for recency, relevancy, and quality. There are specific places for submission of this information in the FACTS Sheet RFP Attachment 4. Please ensure the information submitted, in the FACTS Sheet RFP Attachment 4, is for each order (or series of orders), in lieu of just the basic ordering contract itself. This includes but is not limited to information such as the dollar value, period of performance, quantity produced, and type and complexity of data deliverables for each order or series of orders. See paragraph

3.1 below for further information on how to submit series of orders.

3.1 Series of Orders:

When submitting a series of orders for evaluation, the offeror should list the orders under the basic ordering type contractual vehicle that demonstrate relevancy, as defined in the Relevancy Definitions in Section M paragraph II.E. Per the Note in Section M paragraph II.E, relevancy consists of not only scope and magnitude (i.e. dollar value and period of performance) and the complexities (body of work), but also the programmatic and logistical considerations. The programmatic/logistical considerations include dollar value, length of effort, quantity produced, and type and complexity of data deliverables.

If an offeror submits a series of orders for evaluation, the total dollar value of each order (in the series of orders), the period of performance dates of each order (in the series of orders), the total quantity produced on each order (in the series of orders) and the type and complexity of data deliverables for each order (in the series of orders) shall be submitted. The total dollar value of each order (in the series of orders) shall be added up to calculate the Total Dollar Value to be used in the evaluation, for the submitted effort. The total period of performance of each order (in the series of orders) shall be added up to calculate the Total Period of Performance to be used in the evaluation, for the submitted effort. The total quantity produced on each order (in the series of orders) shall be added up to calculate the Total Quantity Produced to be used in the evaluation, for the submitted effort. The type and complexity of data deliverables provided on each order (in the series of orders) shall be evaluated as a whole for the series of orders.

Offerors must submit past performance information in the specific format required by Present and Past Performance Questionnaire (RFP Attachment 6). To ensure a complete evaluation under RFO Clause 15.305, information must be provided for each individual order (or series of orders) rather than just the basic ordering contract. Submissions must include specific details for each order, including but not limited to the Dollar Value and Period of Performance.

CAUTION: All orders within the series of orders being submitted should be for the same continuous technical scope demonstrating relevancy to the instant acquisition. The Government reserves the right to request additional information from the offeror or Points of Contacts provided to verify that the series of orders is for the same continuous technical scope.

4. Key Personnel:

Offerors, joint venture members, or proposed critical subcontractors that are newly formed entities (in existence less than three (3) years from the issuance date of this solicitation) who either have no prior contracts or do not possess relevant corporate past performance, but have key personnel with relevant past performance while employed by another company, may demonstrate the performance of such key personnel. Such performance may be demonstrated by submitting FACTS Sheets for four (4) of their most recent and relevant contracts under which such key personnel performed the same role currently being proposed on the instant acquisition and this performance occurred during the past three (3) years from the issuance date of this solicitation.

Note: The quality of the key personnel’s performance under the submitted contract must be able to be verified by the Past Performance Team in order to be considered in the confidence assessment. Any such key personnel must already be employed by the offeror/joint venture member/proposed critical subcontractor; a letter of intent to hire does not constitute employment.

5. Proposed Critical Subcontractor/Joint Venture Member Consent Form:

In addition to the information provided in the FACTS Sheet (RFP Attachment 4 for each entity as required above, the offeror must submit a consent letter executed by each of its proposed joint venture member(s) and/or proposed critical subcontractors authorizing release of adverse past performance information to the prime offeror to allow the prime offeror an opportunity to respond. A sample Proposed Critical Subcontractor/Joint Venture Member Consent Form is attached to this RFP (see RFP Attachment 9). The consent form shall be completed by the joint venture member(s) and/or proposed critical subcontractors identified in your proposal. The completed consent forms shall be submitted as part of your Past Performance Volume IV.

Note: Please note this proposed critical subcontractor/joint venture member consent form is separate from the required signed proposed critical subcontractor commitment.

6. Small Business Compliance in Past Performance Efforts:

For the three (3) past performance efforts submitted in Volume IV, the offeror’s, joint venture members, and critical subcontractors must include relevant compliance information regarding FAR Clause 52.219-8 (Utilization of Small Business Concerns) or FAR Clause 52.219-9 (Small Business Subcontracting Plan), if these clauses were active in those contracts. Submit this information using the PPI Tool, DoD SAFE or encrypted email.

Note: RFO Clause 52.219-8 does apply to ALL businesses, whereas RFO Clause 52.219-9 only applies to large businesses.

* When subcontracting possibilities existed on the contracts submitted by the Offeror/Joint Venture member and/or critical subcontractor, address whether or not the Offeror/Joint Venture member and/or critical subcontractor awarded subcontracts to small business concerns to the fullest extent consistent with efficient contract performance. If none of the submitted contracts included these clauses, whenever subcontracting possibilities existed in the performance of these contracts, address whether or not it was the offeror’s/joint venture member’s and/or critical subcontractor’s policy to utilize small business concerns to the fullest extent consistent with efficient contract performance.

** Small business offerors shall not simply identify themselves as a small business, as that does not address how the offeror utilized small business concerns in the performance of the submitted effort. Small business concerns include small business categories of veteran-owned small business concerns, service-disabled veteran-owned small business concerns, HUBZone small business concerns, small disadvantaged business concerns, and women-owned small business concerns.

7. Facts Sheet:

The offeror/joint venture member and proposed critical subcontractor, if applicable, shall focus its FACTS Sheet (RFP Attachment 4) responses so that they clearly correlate present and past performance with the requirements of this RFP. The FACTS Sheet responses must clearly describe the relevance of the effort to the work proposed. The answering space on the FACTS Sheet may be expanded so that the filled-in FACTS Sheet for each relevant contract covers no more than three (3) additional 8 ½ x 11 inch pages (i.e., no more than eight (8) pages. Provide the most current information for the Points of Contact (POCs) identified on the FACTS Sheets. At least two of the following (in descending order of availability) should be identified as current POCs on the FACTS Sheets:

(a) Contracting Officer’s Representative (COR)

(b) Procuring Contracting Officer/Contract Negotiator or equivalent

(c) Program/Project Manager, or equivalent

(d) Administrative Contracting Officer/Contract Administrator or equivalent

(e) Other (As specified in your FACTS Sheet

If problems were encountered during the performance of the identified contracts, provide evidence of the ability to isolate the root causes of problems and include in the FACTS Sheet a description of programs or actions taken to resolve those causes. Problems not addressed in the FACTS Sheet but found by the Government during the evaluation of the information in this volume, will be assumed to still exist.

Note: In the case of CPARS, if your input has already been provided and the rationale/circumstances have not changed, DO NOT repeat them here.

8. Past and Performance Questionnaire:

The Present and Past Performance Questionnaire (RFP Attachment 6) will be one of the means used by the Government to obtain Present and Past Performance information. The Government reserves the right to change, alter, and/or supplement the questionnaire without further notice to the offeror(s). The offeror shall send out and track the completion of the Present and Past Performance Questionnaires (RFP Attachment 6) to each of the offeror’s, joint venture members and/or critical subcontractors’ (i.e., each entity’s) Points of Contact identified in each RFP Attachment 4 (FACTS Sheet). The responsibility to send out and track the completion of the Present and Past Performance Questionnaires rests solely with the offeror - i.e., it shall not be delegated to any other entity. The Transmittal Letter (RFP Attachment 7) shall be used by the offeror in sending out the Present and Past Performance Questionnaires. Exert your best effort to ensure that at least two POCs per relevant contract submit a completed Present and Past Performance Questionnaire directly to the Government not later than the date established in the RFP for receipt of proposals. POCs may submit their completed Present and Past Performance Questionnaire electronically utilizing the Solicitation Module in PIEE or DoD SAFE.

Once the Present and Past Performance Questionnaires are completed by your POCs, the information contained therein shall be considered source selection sensitive and shall not be released to you, the offeror/joint venture member or critical subcontractor. Therefore, any exchange/contact between the offeror/joint venture member and/or critical subcontractor and its own POCs in regards to comments made on the questionnaire is not permitted.

9. Client Authorization Letter:

In the event that commercial contracts are presented as Present and Past Performance sources of information, a client authorization letter shall be issued to those commercial POCs requesting/authorizing them to complete a Present and Past Performance Questionnaire. A sample Client Authorization Letter is attached to this RFP (RFP Attachment 8). The offeror/joint venture member is required to send the client authorization letter(s) with the Present and Past Performance Questionnaire(s) to each POC on commercial contracts. A separate copy of client authorization letter(s) for each commercial contract shall be included in the offeror’s Present and Past Performance submission for the Government’s use in case additional questionnaires need to be sent by the Government after the RFP due date.

10. Follow-Up Discussions:

The Government may conduct follow-up discussions with any of the people identified in the FACTS Sheets or in the offeror’s Present/Past Performance Volume. The Government may obtain other information by sending out additional questionnaires and/or through other sources, other than those listed within the FACTS Sheets.

11. RFP Attachment Legend:

RFP Attachments 4 (FACTS Sheet) and 6 (Present and Past Performance Questionnaire) must include the following legend at the top and bottom of the page: SOURCE SELECTION INFORMATION - See RFO

2.101 and 3.104 FOR OFFICIAL USE ONLY F. Volume V, Small Business Participation

1. General:

The Small Business Participation proposal is required from all offerors, including small businesses and companies with Master, Individual, commercial subcontracting plans and/or comprehensive subcontracting plans.