TRANSCOM24C003 Ft Irwin RW Svcs RFI.pdf

REQUEST FOR INFORMATION (RFI)

FOR

UNITED STATES TRANSPORTATION COMMAND (USTRANSCOM)

FT. IRWIN ROTARY WING TRANSPORTATION SERVICES

TRANSCOM24C003 Ft. Irwin RW Services

1. RFI Overview

In 2025, USTRANSCOM plans to have a contract in place for contractor furnished rotary wing air transportation of 5 passengers with baggage and occasional external slings loads from Bicycle Lake Army Air Field at Ft Irwin CA to destinations within a 200 mile radius. USTRANSCOM seeks a solution that transports technicians and equipment to austere locations to support the operation and maintenance of the NTC communications/instrumentation network, located on a mountain top. USTRANSCOM is seeking information about what solutions currently exist in the market and is interested in learning about what information industry may need to scope a logical roadmap to succeed.

This announcement constitutes an RFI for informational and planning purposes only.

THIS IS NOT A REQUEST FOR PROPOSAL (RFP), nor is it to be construed as a commitment by the Government. No contract will be awarded as a result. Industry’s response to the RFI—or lack thereof—will have no impact on the evaluation of responses to any subsequent RFP or Request for Quote (RFQ) released. The information requested will be used within USTRANSCOM as market research to facilitate decision making (e.g., determining acquisition strategy, small business concerns) and will not be disclosed outside the Government.

Proprietary information submitted shall be appropriately marked. Do not submit confidential information in your response.

**Note** USTRANSCOM will NOT be responsible for any costs incurred by interested parties responding to this RFI.

1.1. RFI Contact(s)

We have designated the following individual(s) to serve as the official point(s) of contact (POCs) for this RFI. This/These individual(s) is/are the only authorized contact(s) permitted to communicate on behalf of USTRANSCOM about this RFI.

Contact information for RFI POC(s):

NAME TITLE OFFICE EMAIL PHONE

Mr. Matthew

Bowen Contracting

Officer TCAQ-C matthew.r.bowen4.civ@mail.mil

(618) 817-

TSgt Ryan LaFever

Contract Specialist

TCAQ-C ryan.c.lafever.mil@mail.mil

(618) 817-

1.2. Submission Details

Please submit your response to this RFI via email to the RFI POC(s) identified in Section 1.1. and ensure it is received prior to the due date identified in Section 1.3. If you have any questions about this RFI, please direct them to the RFI POC(s) listed in Section 1.1.

Physical (paper) copies of RFI responses will not be accepted.

1.3. RFI Timeline

The RFI timeline is outlined below. Dates may be modified by USTRANSCOM and posted as an amendment to this RFI.

RFI Released: 16-JUL-24 RFI One-on-Ones N/A Deadline for Questions: 12:00 PM (CT) on 17-JUL-24 Responses Due: 04:00 PM (CT) on 19-JUL-24

1.4. RFI One-on-One Information (if applicable)

N/A

2. Background Information

USTRANSCOM conducts globally integrated mobility operations, leads the broader Joint Deployment and Distribution Enterprise, and provides enabling capabilities in order to project and sustain the Joint Force in support of national objectives.

2.1. Scope of the Requirement

DOD APPROVAL AND ADDITIONAL STANDARDS. The carrier operating the aircraft must be an approved DoD air carrier, as determined by the Commercial Airlift Review Board (CARB), and must maintain this approval throughout the performance of this contract. The contractor shall comply with all Federal Aviation Administration (FAA) requirements or equivalent CAA requirements, and with all DoD additional standards including those established by DoD Commercial Airlift Division (i.e., the Air Mobility Command (AMC)/A3B) as published on the following website:

https://www.amc.af.mil/Home/AMC-Commercial-Services/.

The Draft Performance Work Statement (PWS) is as follows:

“1.0 DESCRIPTION OF SERVICES

1.1 Background. The National Training Center (NTC) at Ft Irwin CA requires contractor furnished rotary wing air transportation of 5 passengers with baggage and occasional external slings loads from Bicycle Lake Army Air Field at Ft Irwin CA to destinations within a 200 mile radius. The helicopters are needed to transport technicians and equipment to austere locations to support the operation and maintenance of the NTC communications/instrumentation network, located on a mountain top.

1.2 Scope. Except as otherwise stated in this contract, the contractor shall provide all personnel, equipment, tools, facilities, supervision, and direct materials necessary for the performance of the air transportation services for rotary wing passenger and/or cargo air transportation as identified in this PWS.

Contractor will be required to base the aircraft at Bicycle Lake Army Air Field and it is estimated that 350 hours per year of airlift services will be required. Services are to be performed within a 200 mile radius of Bicycle Lake Army Air Field as directed by the Contracting Officer Representative (COR).

1.3 Specific Requirements/Tasks.

1.3.1 Contractor shall be certified under Federal Aviation Regulation (FAR) Parts 133 and 135

1.3.2 Aircraft. As a minimum, the aircraft must be capable of carrying five passengers (plus pilot) and external sling loads. The aircraft must be capable of carrying internal or external loads of 1,000 pounds to including sling loads, pilot and payload, at 30 degrees Celsius at 8,000 feet out-of-ground effect (OGE).

Aircraft must be fueled by JP-8 government furnished fuel IAW paragraph 3.1 below.

Equipment required:

1.3.2.1 One flight meter to record flight time.

1.3.2.2 Extended (Height) Skid-Type Landing Gear.

1.3.2.3 A remote hook-operating switch shall be mounted on the collective control to avoid confusion with the aircraft cargo hook release.

1.3.2.4 “Barrel Slings” or lifters to transport two 55-gallon drums by external load.

1.3.2.5 Cargo net 10’ x 10’ capable of carrying 1,500 pounds.

1.3.2.6 Cargo sling (tag) line at least 10” long with swivel attachment, rated at 1500 pounds.

1.3.2.7 Automatic portable or automatic fixed Emergency Locator Transmitter (ELT/AP or ELT/AF) as required by the FAA.

1.3.2.8 A uni-directional ELT shall be installed with the “arrow” aimed 45 degrees downward from the normal forward “direction-of-flight”. An omni-directional ELT may be mounted in any orientation. An external fixed type antenna will be used in all applications. The antenna will be mounted on the top or bottom in helicopter applications.

1.3.2.9 One 1360 channel VHF-AM (VHF-1) Aeronautical Transceiver shall be installed, operating in the 116.000 MHz to 149.975 MHz band on 25 kHz increments, and a minimum ten watts carrier power output (AN/ARC-115, AN/ARC-186, or equal).

1.3.2.10 One 920-channel VHF-FM (FM-1) Aeronautical Transceiver shall be installed, operating in the 30.00MHz to 75.95 MHz band on 25kHz channel increments, transmitter deviation of +/- 8.0 kHz, with a minimum of 10 watts carrier power output (AN/ARC-114 or equal).

1.3.2.11 One VHF aeronautical navigation VOR/LOC receiver with indicator, minimum 100 navigation receiver channels.

1.3.2.12 Audio Control Systems Equipment:

1.3.2.12.1 One audio control system shall be installed for the pilot and the observer, which provide control, selection and operation of multiple radio transceivers. Audio system controls shall be provided for the pilot and the observer to select specific receiver audio outputs and transmitter microphone/PTT inputs of multiple radios. An intercom system shall also be provided for the pilot, observer, and passenger positions at each aft cabin exit. Audio level controls shall be provided for the pilot and observer to adjust the intercom and receiver audio outputs to their respective earphones. The controls of the audio control system shall be located conveniently for both pilot and observer. Labeling and marking of controls must be clear, understandable, and permanent.

1.3.2.12.2 The system shall be designed for operation with 600 ohm earphones and carbon equivalent, noise canceling boom type microphones (Gentex electret type Model 5060-2, military dynamic type M- 87/AIC with CE-100 TR preamplifier, or equivalent) with U-75/U type connector plug. The only exception to this is the pilot’s position, which may be a low impedance (dynamic) configuration.

1.3.2.12.3 All earphone/microphone jacks in the aircraft, except the pilot’s, shall be military type U-61 which will accept the U-75/U plugs specified above. Adapter cables and connectors may be used as necessary to provide U-61/U jacks.

1.3.2.12.4 As a minimum, the audio control systems shall provide for selecting the following radios and systems: VHF-AM Aeronautical Radio (VHF-1) and VHF-FM Aeronautical Radio (FM-1).

1.3.2.12.5 Separate Push to Talk (PTT) switches shall be provided for radio transmitter operation and intercom operation at the pilot and observer positions. The pilot’s switches shall be located on the cyclic stick. The observer’s shall be located on the cord to the earphone/microphone connector. The passenger positions will have a PTT switch for intercom operation located on the cord to the earphone/microphone connector.

1.3.2.12.6 Transmitter Selection and Operation. A transmitter selection switch shall be provided for the microphone/PTT of the pilot and observer. The pilot or observer will be able to select a desired transmitter communicate using the respective microphone/PTT. When a transmitter is selected, the companion receiver audio shall automatically be selected for the associated earphone in use.

1.3.2.12.7 Receiver Audio Selection and Operation. Selector switches shall be provided for the pilot and observer earphones to permit selecting receiver audio from one or combination of all receivers. The passenger positions shall monitor the receiver(s) as selected by the observer. Performance specifications for receiver audio to all earphone connectors are as follows:

1.3.2.12.7.1 Audio Output: With an input of 10 mW (600 ohms) from any selected receiver, the audio output shall be capable of 100 mW (600 ohms) with less than 10% distortion.

1.3.2.12.7.2 Hum and Noise: 40 dB below specified audio output (100 mW).

1.3.2.12.7.3 Crosstalk: 40 dB below specified audio output (100 Mw). NOTE: The audio input is an adjustable output from any of the selected receivers. This is typically an adjustment of the radio volume control, which can range from 0 to 100 mW (600 ohms).

1.3.2.12.8 An intercom system shall be provided to serve the pilot, observer, and passenger positions at each aft cabin exit. Intercom audio shall mix with, but not mute, selected receiver audio (override type).

Adjustment of any station’s intercom audio level shall not affect the level at any other station. An intercom audio level control shall be provided on the pilot and observer audio control panel(s) and at each passenger position for adjusting the individual earphone audio to a comfortable listening level.

Microphone operation on the intercom system shall be via PTT switches. A “hot-mike” capability shall be provided via an activation switch accessible by the pilot and observer or may be voice actuated (VOX).

Side tone audio shall be provided to the earphone connector associated with the microphone in operation.

Performance specifications for the intercom system are as follows:

1.3.2.12.8.1 Audio Output. With an audio input test tone level of 250mV at 1 kHz, the audio output shall be capable of 100 mW (600 ohms) with less than 10% distortion.

1.3.2.12.8.2 Hum and Noise. 40dB below specified audio output (100 mW).

1.3.2.12.8.3 Input Audio: As provided by station microphone or test tone input at microphone terminals.

1.3.2.13 The aircraft must be equipped with heating and ventilation/air conditioning, cabin storage for passenger hand carrier baggage, and clean air sickness bags.

1.3.3 Hazmat: The Government may require transportation of some hazardous materials. The carrier must be an approved HAZMAT carrier in accordance with 49 CFR and AR 95-27. Such transportation shall be in accordance with FAA regulations and National Training Center (NTC) Regulation 200-2, 200- 6 and the Hazardous Material Handbook.

1.4 Personnel

1.4.1 Contactor personnel shall comply with all pertinent military regulations and/or directives when in base flight patterns and on military installations.

1.4.2 Corporate Liaison. Prior to the start of the contract, the contractor shall furnish the COR with the name, address, e-mail address, and phone number of an agent who will serve as a liaison between the contractor and the COR. The agent must have authority to dispatch aircraft, adjust schedules, engage substitute airlift, and make decisions pertinent to the airlift service for the contractor. The agent will be available by telephone 24 hours per day, seven days per week.

1.4.3 Contractor Personnel Access/Termination/Replacement. The Contractor shall notify the CO and COR/ACOR within 72 hours of the employment, site visitation or termination of any on-site Contractor personnel by providing an updated list of personnel which includes, at a minimum, the following information: name (last, first, middle initial), primary position title, level of investigation/security clearance and date of interim/final approval, Driver License number and State, and date of on-site employment/visit or termination.

1.4.4 Removal from Worksite. If the CO or COR/ACOR notifies the Contractor that the employment or the continued employment of any contract employee is prejudicial to the interests or endangers the security of the United States of America, that person shall be removed, barred from the worksite and replaced at Contractor expense. This includes security deviations/incidents and credible derogatory information on Contractor personnel during the course of the contract period. The Contractor shall make any changes necessary in the appointments.

1.4.5 Aircrew. The Contractor shall provide at least one aircrew (including two pilots) for each primary aircraft assigned. The Contractor’s aircrew members shall be trained, qualified, and maintain proficiency and comply with duty day requirements in accordance with the applicable Federal Aviation Regulation (FAR) Part 133 and 135 or equivalent CAA regulations.

1.4.6 Aircraft Maintenance Personnel. Contractor’s aircraft maintenance personnel shall be trained, qualified, and maintain proficiency in accordance with the applicable Federal Aviation Regulation Part 133 and 135 (14 CFR Part 135), Code of Federal Regulations (CFR), 32 CFR Part 861, and/or other applicable Civil Aviation Authority regulations. Maintenance personnel will require a Post Access Request to the COR/ACOR within 72 hours of site visit (same information as para 1.4.3)

1.5 Mission Requirements

1.5.1 Availability. The contractor shall be available to provide service 7 days a week, including weekends and holidays. Mission scheduling will be limited daylight hours under Visual Flight Rules (VFR) conditions. Daylight hours are defined as 30 minutes before official sunrise to 30 minutes after official sunset. The contractor shall be positioned at the designated Ridge Runner pad on Bicycle Lake Airfield as directed by the COR. The contractor shall receive 24 hours advance notice and on occasion will have immediate notice for emergency repairs. A normal duty day shall not exceed 12 hours.

1.5.2 Department of Defense (DoD) personnel shall not be scheduled to fly on helicopter during external load operations.

1.5.3 Contractor shall comply with FAR Part 135.117 for required passenger briefings prior to each take-off.

1.5.4 The contractor shall meet the scheduled time of pickup as ordered by the COR. One-thirtieth (1/30th) of the aircraft monthly rate offered will be deducted for each day the contractor fails to provide an aircraft to meet mission requirements.

1.6 Aircraft Condition. Every aircraft shall be certified as airworthy by trained and certified mechanics for that specific airframe. Airworthiness certificates shall be made available to the Government upon request. The Government is entitled to perform an independent assessment of the condition of any contract aircraft at any time. The Government may also request that an independent assessment of any aircraft used in performance on this contract be conducted at contractor expense. The contractor will make available, at the CO’s request, a copy of each aircraft’s maintenance history. The Government reserves the right to inspect aircraft, maintenance records, and employee records at any time.

1.6.1 Alternate/Spare Aircraft. Alternate aircraft are not required under this contract nor is the Government under any obligation to accept performance by alternate aircraft. In order for aircraft to be added as an alternate aircraft, a written request with supporting documentation that the aircraft can meet all requirements of the TO PWS shall be submitted to the CO. The CO has sole discretion in permitting the contractor to change/add alternate aircraft.

1.6.2 Aircraft Replacement or Addition. The Contractor is only authorized to operate under this TO the specific tail numbers identified in the Aircraft Identification Table maintained by the USTRANSCOM CO at the TO level. Throughout the TO period of performance, a contractor may request approval from the CO to replace an aircraft with an aircraft of similar capability. Replacement aircraft shall be DoD approved prior to operation. Contractor shall submit a formal letter to CO detailing the reason for the change or addition. Contractors shall not utilize these aircraft until a modification to replace or add the aircraft has been executed.

1.6.3 Maintenance. The contractor shall perform both scheduled and unscheduled maintenance.

Maintenance may occur on US Military installations with prior coordination and the express permission of the Government. The contractor will provide all parts, tools and equipment, labor, and expertise necessary to complete required maintenance tasks. Maintenance downtime will be coordinated between the contractor and the customer or COR. The contractor shall provide a timetable for scheduled maintenance and an estimated completion time for unscheduled maintenance.

1.6.4 Aircraft Safety Equipment. All aircraft will maintain serviceable first aid kits, fire extinguishers, and all aviation life support equipment required to be maintained in accordance with applicable FAA/CAA and DoD standards. The aforementioned items shall be inspected for serviceability in accordance with manufacturer’s inspection/serviceability instructions. Documentation of the inspection shall be provided to the COR/ACOR or designated Government representative within 10 calendar days of the inspection.

1.6.5 Safety Barriers. All passenger and cargo doors used for loading and unloading of passengers, baggage, and cargo aboard contract aircraft shall be equipped with a safety barrier at chest or waist level.

The safety barrier shall be in place when the cabin or cargo door is open except when actually on-loading or off-loading passengers/cargo or when loading stairs are positioned.

1.7 Deliverables

1.7.1 Contractor will provide written verification of insurance coverage to the Contracting Officer at USTRANSCOM TCAQ-R, 508 Scott Dr, Scott AFB IL 62225 prior to the contract award.

1.7.2 At each departure airfield, contractor will ensure that an accurate passenger manifest is left with appropriate airfield authorities, e.g. military air operations or civilian Fixed Base Operators (FBO) personnel.

2.0 SERVICE DELIVERY SUMMARY

Performance Objective PWS Paragraph Performance Threshold On-time performance 1.5.4 99% of monthly flights Equipment is in working Condition

1.3.2 99% of monthly flights

Contractor shall leave an accurate passenger manifest at departure airfields.

1.7.2 100% of monthly flights

3.0 GOVERNMENT FURNISHED EQUIPMENT (GFE) AND SERVICES

3.1 Fuel. The government will provide, at no cost to the contractor, JP-8 fuel for direct contract flying.

Fuel for positioning/repositioning, training, and maintenance flights is the responsibility of the contractor and will not be charged to the contract. The Aircraft shall not be refueled while engines are running, or rotor blades are turning, unless the aircraft refueling facility is equipped with an approved closed-circuit refueling system. Grounding and bonding cables shall be utilized. The contractor shall verify and certify Government fuel usage on the fuel worksheet provided.

3.2 Air traffic control and airfield safety protection. Ground handling of aircraft, ground support equipment units (if available), aircraft parking space, and military flight planning charts and publications shall be provided.

3.3 OCCS hand-held radios for dispatching and safety concerns while operating at the NTC shall be provided.

Note: The contractor is responsible for providing support equipment unique to its aircraft.

3.4 Landing Permits at Military Installations.

3.4.1 To permit the use of military installations, the contractor must obtain landing permits following Service specific regulations, no later than 30 days prior to required approved date. The contractor shall begin the renewal process at least 60 days prior to expiration to allow for any delays in processing and to avoid a suspension of operation.

3.4.2 Air Force Bases. Pursuant to AFI 10-1001, a Landing Permit (DD Form 2401) may be obtained from USTRANSCOM/TCAQ-R at Scott AFB, IL. In addition, a Hold Harmless Agreement (DD Form 2402) and the Certificate of Insurance (DD Form 2400) must be completed and forwarded to the CO at USTRANSCOM TCAQ-R, Scott AFB, IL. The Contractor shall submit these completed forms along with the DD Form 2401.

3.4.3 Deleted.

3.4.4 Army Installations. POC: Corey Howard - corey.d.howard8.civ@mail.mil

3.4.5 Extended Parking at Fort Irwin, CA Bicycle Lake Army Airfield is designated for the “Ridge Runner” Rotary Wing Air Transportation Service contract aircraft.

3.4.6 Positioning of aircraft in advance of time stipulated in the contract in order to prevent delays due to weather, crew limitations, or other reasons.

4.0 GENERAL INFORMATION

4.1 DoD approved air carrier prior to contract award. The contractor must satisfy DoD quality and safety requirements as described in 32 Code of Federal Regulation (CFR) Part 861. All aircraft utilized must be licensed, operated, and maintained in accordance with all applicable rules and regulations of the Federal Aviation Administration (FAA) and Department of Transportation (DOT), giving particular attention to the responsibility of the air carrier to perform air transportation with the highest degree of safety.

4.2 Aircraft performing missions under this contract shall not be considered public aircraft.

4.3 Contractor shall have a current FAA Authorization certificate to operate over routes and into airfields specified under both Instrument Flight Rules (IFR) and VFR conditions and rules. IFR capability authorization is not required for operations into airfields, which do not have published IFR approach procedures.

4.4 Insurance Requirements. Prior to performance of any services hereunder, the contractor shall, at its own expense, procure and maintain insurance during the entire performance period of this contract, with a financially and legally responsible insurance company or company’s minimum insurance coverage as set forth by the DOT

5.0 ADMINISTRATIVE REQUIREMENTS

5.1.1 REQUIREMENTS AFFECTING CONTRACTOR PERSONNEL PERFORMING MISSION

ESSENTIAL SERVICES

All services performed under this contract are deemed “Essential Contractor Services” as defined and described in DFARS 252.237-7023 “Continuation of Essential Contractor Services”. Hereafter, the personnel identified by the contractor to perform these services shall be referred to as “Essential Contractor Personnel.”

Within 30 Days, the Contractor shall provide a written list (see below sample) of all “Essential Contractor Personnel” to the Contracting Officer or designee. The list shall identify names and country (ies) where each employee will perform work under this contract and whether the employees have military mobilization recall commitments.

As required to comply with or perform pursuant to DoD or USTRANSCOM requirements, the Contracting Officer shall direct the contractor to comply with requirements intended to safeguard the safety and health of Essential Contractor Personnel. The Contracting Officer may communicate the requirements through a letter of notification or other means, and subsequently modify the contract to incorporate the requirements via full text or by reference.

The Contractor may file a proposal for cost or other impacts under the Changes clause or a Request for Equitable Adjustment.

This language shall be inserted in all subcontracts meeting the criteria in paragraph 5.1.1 above.

ESSENTIAL CONTRACTOR PERSONNEL

Employee Name Country/Countries Mobilization Recall (Y or N)

Performance of Services during Crisis Declared by the President of the United States, the Secretary of Defense, or Overseas Combatant Commander The performance of these services is not considered mission essential during time of crisis. Should a crisis be declared, the Contracting Officer will verbally advise the contractor of the revised requirements, followed by written direction.

5.1.2. IDENTIFICATION OF POTENTIAL ORGANIZATIONAL CONFLICTS OF

INTEREST (OCI)

All personnel (military, Government civilian, and support contractor) within the TCJ8 will have access and work with acquisition/proprietary information governed by Federal Acquisition Regulation (FAR). Organizational conflict of interests shall be avoided, neutralized or mitigated

IAW FAR 9.505.

5.1.3. Health and Safety on Government Installations

5.1.3.1. In performing work under this contract on a Government installation, the contractor shall:

5.1.3.1.1. Take all reasonable steps and precautions to prevent accidents and preserve the health and safety of contractor and Government personnel performing or in any way coming in contact with the performance of this contract; and

5.1.3.1.2. Take such additional immediate precautions as the contracting officer may reasonably require for health and safety purposes.

5.1.3.2. The contracting officer may, by written order, direct health/safety standards as may be required in the performance of this contract and any adjustments resulting from such direction will be in accordance with the Changes clause of this contract.

5.1.3.3. Any violation of these health and safety rules and requirements, unless promptly corrected as directed by the contracting officer, shall be grounds for termination of this contract in accordance with the Default clause of this contract.

5.2. BILLING. Invoices will be submitted either monthly or semi-monthly, at vendor discretion, through Procurement Integrated Enterprise Environment (PIEE) Wide Area Workflow (WAWF) in accordance with DFARS 252.232-7006 Wide Area Workflow Payment Instructions. If invoicing semi-monthly, the dates shall be fixed (1st and 15th or 15th and 30th). Monthly Basing fee may only be invoiced monthly. The contractor shall bill for actual miles flown. Estimated KNZY—KNUC round trip is 208 GCSMs. The contractor may invoice for additional live miles caused by circumstances outside their control, including weather, aborted missions, and other unexpected events as soon as reasonably possible with appropriate documentation. Fuel invoicing may be submitted at the same time as mileage or monthly basing invoice or may be invoiced separately when all records for a particular billing period are received. Initial positioning miles to KNZY and end-of-day repositioning miles from KNZY, including maintenance shuttle miles, are not billable.

6.0 Operations Security

OPSEC must be included in contracts to ensure that critical information is protected. Disclosing this information to the adversary could potentially affect mission success and cause harm to military members, civilians, and contractors and their families. OPSEC is a process used to protect unclassified sensitive information from exploitation by an adversary. Sensitive unclassified information—which is also referred to as critical information or critical program information (CPI)—is defined as information that is not classified but which needs to be protected from unauthorized disclosure. Examples are information labeled CUI, such as proprietary information, contractor sensitive information, limited distribution information, or PII.

6.1 Operations Security Requirements. The prime contractor and all subcontractors shall provide protection for sensitive unclassified information to limit unauthorized disclosures of critical information. The prime contractor and all subcontractors shall employ the countermeasures listed below to protect that information. These OPSEC requirements will be in effect throughout the life of the procurement from award through the conclusion of services at the end of the period of performance or other procurement termination. In any case where uncertainty or ambiguity regarding OPSEC measures exists, the contractor shall consult the requirements or contracting office’s OPSEC coordinator as soon as possible.

6.2 Countermeasures to Unauthorized Disclosure of Critical Information. Countermeasures are required to negate the susceptibility of critical information to exploitation by an adversary or competitor. The contractor shall protect all critical information listed in a manner appropriate to the nature of the information, including use of the necessary countermeasures as listed below applicable to specific items:

Refrain from including critical information in contract and budget documents, presentations, press releases, and other publications to that which is essential to the performance of this requirement.

Encryption or password protection of electronically stored critical information.

Encryption or password protection of e-mail containing critical information.

Storage of hard copy critical information and storage media in locked containers when not in use.

Transmission of critical information to the minimum set of recipients with a need to know.

Immediate and appropriate destruction in a manner precluding reconstruction of all critical information no longer needed under this contract.

Restricting verbal discussion of critical information to venues and circumstances that prevent the monitoring and interception of the discussion by unauthorized personnel.

Refraining from the use of unencrypted telephones to transmit critical information.

Refraining from the use of foreign postal systems to ship critical information.

Promptly retrieving documents containing critical information printed on printers accessible by persons without a need to know the critical information.

Use of cover pages or other appropriate means to prevent the viewing of critical information by unauthorized persons.

The contractor shall notify the COR and USTRANSCOM security office immediately of all known and suspected compromises of critical information. If the COR cannot be reached, the contractor shall notify the supported command duty officer if after normal work hours.

7. CYBERSECURITY

7.1. Operationally Critical Support

The services designated under this contract are “operationally critical support” as defined in

DFARS 252.204-7012.

7.2. Cybersecurity Incident Reporting

7.2.1. In addition to the DFARS 252.204-7012 reporting requirements for unclassified systems and DoD Manual (DoDM) 5220.22, National Industrial Security Program Operating Manual (NISPOM) for classified systems, reportable cyber-incidents include, but are not limited to, the following:

7.2.1.1. Cyber-incidents as defined in Table 1.

7.2.1.2. Notifications by a federal, state, or local law enforcement agency or cyber-center (i.e., National Cyber Investigative Joint Task Force (NCIJTF), National Cybersecurity & Communications Integration Center (NCCIC)) of being a victim of a successful or unsuccessful cyber-event, anomaly, incident, insider threat, breach, intrusion, or exfiltration.

Table 1.

Incident Category Description

Root Level Intrusion Unauthorized privileged access to an IS. Privileged access, often referred to as administrative or root access, provides unrestricted access to the IS. This category includes unauthorized access to information or unauthorized access to account credentials that could be used to perform administrative functions (e.g., domain administrator). If the IS is compromised with malicious code that provides remote interactive control, it will be reported in this category.

User Level Intrusion Unauthorized non-privileged access to an IS. Non-privileged access, often referred to as user level access, provides restricted access to the IS based on the privileges granted to the user. This includes unauthorized access to information or unauthorized access to account credentials that could be used to perform user functions such as accessing Web applications, Web portals, or other similar information resources. If the IS is compromised with malicious code that provides remote interactive control, it will be reported in this category.

Denial of Service Denial of Service (Incident)—Activity that denies, degrades, or disrupts normal functionality of an IS or DoD information network.

Malicious Logic Installation of software designed and/or deployed by adversaries with malicious intentions for the purpose of gaining access to resources or information without the consent or knowledge of the user. This only includes malicious code that does not provide remote interactive control of the compromised IS. Malicious code that has allowed interactive access should be categorized as Root or User Level Intrusion incidents. Interactive active access may include automated tools that establish an open channel of communications to and/or from an IS.

Ransomware Malware designed to encrypt files on a device, rendering any files and the systems that rely on them unusable. Malicious actors then demand ransom in exchange for decryption. Ransomware actors often target and threaten to sell or leak exfiltrated data or authentication information if the ransom is not paid. Ransomware is a reportable incident that may be associated with multiple incident categories depending on the attack vector and execution.

7.2.2. If the cyber-incident affects a classified system, vulnerabilities associated with the incident will be classified per the current version of USTRANSCOM Instruction 31-02, Security Classification Guide.

7.3. Cybersecurity Incident Reporting Timelines

In addition to providing the notification required by DFARS 252.204-7012, the contractor is required to notify USTRANSCOM as soon as practical, but no later than 72 hours after discovering a reportable cyber-incident. The reporting timeline begins when the incident is discovered or reported to the company, its employees, contractors, or cybersecurity firm responsible for providing cybersecurity and response for the company. The contractor shall contact the USTRANSCOM Cyber Operations Center (CyOC) via phone at 618-817-4222. If the contractor does not immediately reach the CyOC via phone, the contractor shall send an email notification to transcom.scott.tcj6.mbx.cyoc-dodin-operations@mail.mil.

7.4. Mandatory Reporting Data

7.4.1. The contractor shall work with the USTRANSCOM CyOC through resolution of the incident. Within 72 hours of becoming aware of a reportable cyber-incident, the contractor shall provide an initial notification of the incident, even if some details are not yet available, which includes, but is not limited to, the following information:

(a) Company Name

(b) Who will be the POC with contact information

(c) Contracting Officer POC (name, telephone, email)

(d) Overall Assessment –Description of incident, data at risk, mitigations applied

(e) Indicators of compromise

(f) Vector of attack (if known)

(g) Estimated time of attack (if known)

7.4.2. The contractor shall provide a follow-on cyber-incident report to the USTRANSCOM CyOC within 5 days of becoming aware of a reportable cyber-incident, which includes, but is not limited to, the following information:

(a) Contractor unique Commercial and Government Entity (CAGE) code

(b) Contract numbers affected

(c) Facility CAGE code where the incident occurred if different than the prime Contractor location

(d) POC if different than the POC recorded in the System for Award Management (name, address, position, telephone, email)

(e) Contracting Officer POC (name, telephone, email)

(f) Contract clearance level

(g) DoD programs, platforms, systems, or information involved

(h) Location(s) of compromise

(i) Date incident discovered

(j) Type of compromise (e.g., unauthorized access, inadvertent release, other)

(k) Description of technical information compromised

(l) Any additional information relevant to the information compromise

7.5. Incident Reporting Coordination

7.5.1. In the event of a cyber-incident, USTRANSCOM may conduct an on-site review of network or information systems where DoD information is resident on or transiting to assist the contractor in evaluating the extent of the incident and to share information in an effort to minimize the impact to both parties. Date and time of on-site visits will be mutually agreed upon by USTRANSCOM and the contractor in advance.

7.5.2. The contractor agrees to allow follow-on actions by the Government (e.g., USTRANSCOM, Federal Bureau of Investigation, Department of Homeland Security, DC3, etc.)

to further characterize and evaluate the suspect activity. The contractor acknowledges that damage assessments might be necessary to ascertain an incident methodology and identify systems compromised as a result of the incident. Once an incident is identified, the contractor agrees to take all reasonable and appropriate steps to preserve any and all evidence, information, data, logs, electronic files and similar type information (reference NIST Special Publication 800- 61, Computer Security Incident Handling Guide, (current version)) related to the incident for subsequent forensic analysis so that an accurate and complete damage assessment can be accomplished by the Government.

7.5.3. The contractor is not required to maintain an organic forensic capability, but must ensure data is preserved (e.g., remove an affected system, while still powered on, from the network) and all actions documented until forensic analysis can be performed by the Government or, if the Government is unable to conduct the forensic analysis, a mutually agreed upon third party (e.g., Federally Funded Research and Development Center (FFRDC), commercial security contractor, etc.). Any follow-on actions shall be coordinated with the contractor via the Contracting Officer.

7.5.4. The contractor agrees to indemnify and hold the government harmless for following any recommendations to remedy or mitigate the cyber-incident following the actions under 7.5.1. and 7.5.2.

7.6. Confidentiality and Non-Attribution Statement

The Government may use and disclose reported information as authorized by law and will only provide attribution information on a need-to-know basis to authorized persons for cybersecurity and related purposes (e.g., in support of forensic analysis, incident response, compromise or damage assessments, law enforcement, counterintelligence, threat reporting, and trend analysis).

The Government may share threat information with other USTRANSCOM industry partners without attributing or identifying the affected contractor.

Add the following surveillance item to the Service Delivery Summary (SDS):

PWS Para Performance Objective Performance Threshold Cyber-Incident Reporting Provide timely cyber-incident reporting.

No more than one late cyber-incident report or unreported cyber-incident in a twelve

(12) month period.

The Quality Assurance Surveillance Plan (QASP) shall also be updated to incorporate the above SDS entry with the method of surveillance established as 100% inspection of all cyber-incidents and reports.

Add the following entries to the reference documents section (if applicable):

Executive Order (E.O.) 13691 of February 13, 2015. Promoting Private Sector Cybersecurity Information Sharing NIST Special Publication 800-61 Computer Security Incident Handling Guide USTRANSCOM Instruction 31-02 Security Classification Guide

8.0 NOTICES AND REPORTS.

8.1.1 Notice of Accidents or Incidents – All Carrier Operations (both Commercial and Government customers). When a Contractor’s aircraft is involved in any accident, DoD or otherwise, the Contractor shall transmit the information in paragraph #1-8 below to Headquarters AMC, via HQ AMC/A3B, Scott AFB IL (618) 229-4801/DSN 779-4801 or the HQ AMC/A3B Safety Manager at 618-229-2106/DSN 779-2106 and to the CO and the COR. Accident and incident information shall be provided to HQ AMC, the CO and the COR/ACOR by the most expeditious means available. Accidents and incidents are defined in 49 CFR Part 830.

1. Contractor and trip number

2. Aircraft type and number

3. Date and time of the accident or incident

4. Last point of departure and point of intended landing of the aircraft, as applicable

5. Nature of the accident or incident and extent of known damage to the aircraft, if any

6. Total number of crewmembers and passengers on board

7. Number of injured and fatalities aboard the aircraft

8. Condition of baggage or Government-owned material and/or cargo, if any, on board

8.1.2 Notice of Accidents or Incidents - Missions Operating under USTRANSCOM WASP-135 TOs.

The contractor shall also provide information to US Transportation Command’s Deployment Distribution Operations Center (DDOC), Scott AFB, Illinois, via (618) 220-7700/7001 or DSN 312-770-7700/7701.

Accident and incident information listed in Paragraph 5.1.1 #1-8 above, shall be provided to the DDOC by the most expeditious means available. Accidents and incidents are defined in 49 CFR Part 830.

8.1.3 Notice of Accidents – Non-USTRANSCOM Missions. When the contractor’s aircraft is involved in an accident in support of a mission not associated with this contract, and as defined in 49 CFR, Part 830, and the contractor will transmit the information in paragraph 5.7.1 by the most expeditious means available and on the next business day notify HQ AMC/A3B, Scott IL (618) 229-4801 or (618) 229-4343.

8.1.11 Aircraft Medical Incidents. Aircraft Medical Incidents. Report all aircraft medical incidents in flight, or while passengers are under the control of the pilot in command, to the first available COR/ACOR, at the next enroute station for in flight incidents, or the station where the incident occurs.

On the next business day, notification shall also be made to the CO, via telephone or E-Mail.

8.1.12 DoD Casualties. In cases where a death occurs on a contractor’s aircraft, the following information shall be furnished via telephone to the phone numbers listed below: Name, Social Security Number (SSN), and component of service identified as Army-USA, Air Force-USAF, Navy-USN, Marine Corps-USMC, Coast Guard-USCG. The following is a list of phone numbers for service casualty offices:

US Army (800) 626-3317 US Navy: (800) 368-3202

US Marines: (800) 847-1597 US Air Force: (800) 433-0048

Coast Guard (USCG): Atlantic Area Op’s Center: (757) 398-6390(Accidents east of Mississippi) Pacific Area Op’s Center: (510) 437-3701(Accidents west of Mississippi)

8.1.13 an information copy shall be provided to US Transportation Command’s Deployment Distribution Operations Center (DDOC), Scott AFB, Illinois, via (618) 220-7700/7001 or DSN 312-770-7700/7701

8.1.14 Safety and Financial Information. As required by the Air Safety Clause at TRANSFAR 5552.247-9000, the contractor must satisfy the requirements of 32 CFR, Part 861, Section 861.4. The DoD will conduct periodic evaluations to assess the contractor’s ability to perform safely. To complete the evaluation, the government may contact the contractor in order to obtain information bearing upon the contractor’s practices, resources, and capabilities. Upon request, the contractor shall provide data pertinent to such evaluations, including current audited financial statements, to HQ AMC A3B, 402 Scott Drive, Unit 3A1, Scott AFB IL 62225-5302.”

End Draft PWS.

NOTE: Data furnished pursuant to this paragraph may be utilized by the U.S. Government or its representative for any matter related to this contract

2.2. Place of Performance

Fort Irwin San Bernadino, CA. 92310

2.3. Anticipated Award Timeline

The current contract expires 31-MAR-25. A follow-on contract is anticipated to be awarded on or about 31-JAN-25.

3. Information Requested

Parties interested in assisting USTRANSCOM with this market research are requested to submit the following information in the format outlined below. The response should be detailed (but no more than 10 pages). Title pages and cover letter will not count against the page limit. Respondents are highly encouraged to submit a tailored response rather than a generic capability statement to ensure the requested information is provided.

3.1. Company Information

Company Name Unique Entity ID CAGE Code POCs, to include name, title, phone number, and email address

3.2. Business Size

The anticipated North American Industry Classification System (NAICS) for this effort is 481211. The Small Business Administration’s small business size standard for this NAICS is 1,500 employees. Based on this NAICS, identify your business size as a LARGE or SMALL business. If a small business, identify any of the following socio-economic categories that apply to your business under this NAICS: Historically Under-utilized Business Zones (known as “HUBZone”), Service-Disabled Veteran-Owned, Veteran-Owned, Small Disadvantaged Business, 8(a), Women-Owned, or Economically Disadvantaged Women-Owned.

3.3. Who We’re Looking For

USTRANSCOM highly encourages responses from capable businesses of all sizes, including large and small business concerns and all socioeconomic categories. However, it should be noted that small business set-aside opportunities are being considered for the NAICS identified in Section 3.2.

3.4. What We’re Looking For

Interested Parties are invited to provide information on the following subjects of interest, specifically describing your capabilities in successfully executing the following:

Obtain/Retain CARB approval Transport a minimum of 5 passengers daily Transport up to 200 miles in a radius around Ft. Irwin.

Perform an estimated 350 hours per year.

Provide the following project or contract information for requirements deemed similar to this effort:

A brief description of the project Contract number Period of performance Was your company a prime or subcontractor?

Dollar value of the project Scope of the portion of the effort your company supported

If your company is a large business, specify whether you partnered or subcontracted with small business concerns to provide the same or similar services as this requirement.

If your company has no direct performance or experience with the above, explain how you will perform tasks utilizing experienced subcontractors through a proposed teaming arrangement or the hiring of qualified personnel.

3.5. Commercial Availability

Commercial Practices. Request responses to the following questions as they pertain to providing Ft. Irwin Rotary Wing Air Transportation Services support.

Is this service available commercially? If so, what commercial solutions can address the requirement?

What applicable industry standards, terms and conditions, regulations, trade journals, or process guides are germane to the service to be acquired?

What types of contracts are normally used in the commercial marketplace for this type of service (e.g., single-award, multiple-award, firm-fixed price, cost reimbursement, labor hour, time-and-materials)?

What contract length is normally used in the commercial marketplace for this type of service (e.g., base year plus four options)?

What is the recommended pricing structure, and what are the largest cost-drivers for this type of service (e.g., labor, equipment, leases, depreciation, fuel)?

What evaluation criteria are typical for use in selecting a contractor to provide this type of service?

Are there any organizational conflict of interest concerns?

Are there technologies the Government should adopt, if feasible, to improve this requirement?

Are there challenges posed to non-incumbent interested parties that should be addressed?

4. Other Important Information

Please list existing contract vehicles available for use in procuring this effort to include Federal Supply Schedules, GSA Governmentwide Acquisition Contracts, DoD Indefinite Delivery Indefinite Quantity contracts (known as “IDIQs”), or any other Government Agency contract vehicles. (This information on available contract vehicles is for market research only and does not preclude your company from responding to this notice.)

Please list any existing contracts you have which could be used to procure this effort.

Provide any other suggestions or considerations to improve this procurement. Are there software advancements, industry developments, or innovative solutions to be considered?

Please feel free to provide questions and/or comments on the draft Performance Work Statement (attached), citing any information you feel may improve/innovate this requirement.

5. Conclusion

USTRANSCOM would like to thank you for taking the time to review this important RFI, and we look forward to reviewing your response.

RYAN C. LAFEVER MATTHEW R. BOWEN

Contract Specialist Contracting Officer

(618) 817-0228 618-578-4067 ryan.c.lafever.mil@mail.mil matthew.r.bowen4.civ@mail.mil

Attachment: (if applicable) DRAFT Performance Work Statement