Atch 01 PWS Pt. Mugu.pdf

PERFORMANCE WORK STATEMENT (PWS)

FOR

NAVAL AIR WARFARE CENTER WEAPONS DIVISION (NAWCWD)

LOGISTICS AIRCRAFT AND DRONE RECOVERY SERVICES

10 MAY 2021

1.0 DESCRIPTION OF SERVICES

1.1 BACKGROUND. The Naval Base Ventura County, Pt Mugu, operates and maintains station facilities and provides logistics services and drone recovery for the Naval Air Warfare

Center, Weapons Division (NAWCWD) at Pt Mugu, CA and assigned tenants and activities. In support of this mission, commercial services are required to support air transportation of passengers/cargo in and around Pt Mugu as well as drone recovery operations and range test support at the Pt Mugu Sea Test Range as described below.

1.2 Description of Services. Except as otherwise stated, the contractor shall provide all personnel, facilities, equipment, supplies, materials, and services necessary for air transportation of passengers with personal baggage and/or cargo, drone recovery services and range test support to NAWCWD, Pt Mugu, CA. Fixed-wing transportation is required in and around the Southern

California area within a 200 nautical mile radius of Pt Mugu, CA. Rotary-wing transportation is required between Ventura County airports (Naval Base Ventura County, Pt Mugu, CA and

Oxnard Airport, Oxnard, CA) and San Nicolas Island, CA, Santa Cruz Island, CA, within a 1.5 flight hour duration of Pt Mugu. If possible, occasional flights will be scheduled outside of the

1.5 hour range. Drone recovery operations will be performed on the NAWCWD Pt Mugu Sea

Test Range and other ranges as required.

1.3 SPECIFIC REQUIREMENTS/TASKS

1.3.1 AIRCRAFT

1.3.1.1 Fixed Wing. Fixed-wing aircraft providing range test range support are required as follows:

1.3.1.1.1 Fixed-wing aircraft with a minimum payload capability of 800 lbs and flight range of

200 nautical miles and the capability of carrying up to four passengers, cargo, or any combination up to the capacity of the aircraft are required.

1.3.1.1.2 Fixed-wing aircraft with a minimum payload capability of 1600 lbs and flight range of

200 nautical miles and the capability of carrying up to eight passengers, cargo, or any

1.3.1.1.3 Fixed-wing aircraft must have a separate cargo area for large, bulky cargo. Aircraft must have the capability to be equipped with UHF radios capable of transmitting and receiving

Navy frequencies. If requested by the Government, the UHF radio will be contractor-provided.

1.3.1.2 Rotary-Wing. Rotary-wing aircraft providing test range support are required as follows:

1.3.1.2.1 Rotary-wing aircraft with a minimum payload capability of 1000 lbs and flight duration at least 1.5 hours and the capability of carrying up to five passengers, cargo, or any

1.3.1.2.2 Rotary-wing aircraft with a minimum payload capability of 2500 lbs and flight duration at least 2.0 hours and the capability of carrying up to nine passengers, cargo, or any

1.3.1.2.3 Rotary-wing aircraft must be equipped with night-flying equipment and have the capability of landing on pitching and rolling decks of ships at sea. Contractor pilots performing shipboard landings shall have completed training conducted by the Navy and meet subsequent proficiency and currency requirements to ensure standardization with shipboard guidelines.

1.3.1.2.4 Rotary-wing aircraft must have the capability to be equipped with UHF radios capable of transmitting and receiving Navy frequencies. If requested, by the Government, the UHF radio will be contractor-provided.

1.3.1.3 Drone Recovery. Rotary-wing aircraft capable of locating, recovering, and transporting

500 lb and 2500 lb drones from the open sea are required. Aircraft crew shall be capable of recovering and lifting drones with required equipment operating approximately three feet above the water IAW Federal Aviation Regulation (FAR) Part 133 and transporting recovered drones to

Pt Mugu, CA. Drone recovery missions take 1 - 1 1/2 hours to locate and hook up the target. An additional 20-30 minutes is average time to return drone to Pt Mugu CA.

1.3.1.4 Range Test Support. Range test support may include surveillance and clearance of marine vessels on the Sea Test Range, marine mammal monitoring, and the carriage of electronic test equipment and tracking devices as required.

1.3.2 SCHEDULING

1.3.2.1 Prior to the start of the contract, the contractor will furnish to the Contracting Officer and the Contracting Officers Representative (COR) the name, address, telephone number and e-mail address of the agent who shall serve as a liaison between the contractor and the COR. This person must have authority to adjust schedules, engage substitute airlift, and make decisions pertinent to the airlift for the contractor. In addition, the contractor will provide a toll-free telephone number that shall be manned from 0700 to 1700 on all workdays.

1.3.2.2 Flights will normally be scheduled at least 24 hours in advance. Flights with less than 24 hours notice shall be scheduled only by mutual agreement between the contractor and the COR.

Normal duty hours are from 0600 to 1800 local time, Monday through Friday. Occasional flights may be required during the night hours, holidays, and weekends.

1.3.2.3 The contractor’s aircraft shall be in position, unless unavoidably delayed by inclement weather or air traffic control delays, so as to depart on time. The contractor shall give timely notification to the Government’s flight scheduler of all delays in accomplishing the flight schedule, including cancellations.

1.3.2.4 When directed, the contractor may be required by the contracting officer representative

(COR) to periodically standby for flights performed under the air transportation CLINs. The first hour of standby time, for each standby period, will be at no cost to the Government.

Standby time shall commence one hour after the scheduled departure time or one hour after the aircraft is in place ready for loading, whichever is later. Standby time shall commence one hour after the aircraft is offloaded at destination and shall end when the authorized government representative releases the aircraft for departure, makes the determination that the aircraft will remain overnight, or the COR cancels the flight. Standby time will not be chargeable to the

Government for contractor-controlled delays or for those caused by Acts of God or weather conditions below minimums, which preclude takeoff or flight to the destination. For the purpose of payment, standby time will be computed to the nearest one-tenth hour increment.

1.3.2.5 If the requirement changes after the confirmed schedule is provided to the contractor, the flight scheduler may cancel or reschedule flights. A notice of cancellation may be given to the contractor at any time prior to departure. The contractor shall be reimbursed 1 hour of flight time if a flight is cancelled after departure from base of operation. All efforts will be made by the government’s flight scheduler to provide the contractor with ample notice of changes or cancellations in the flight schedule. No changes in the prescribed flight schedule will be made without the authorization of the government’s flight scheduler. Any verbal changes made after-hours by the flight scheduler will be confirmed in writing the next day.

1.3.3 ADDITIONAL REQUIREMENTS

1.3.3.1 The government shall be entitled to transport passengers (including their personal baggage) and/or cargo up to the entire capacity of the aircraft without reconfiguration from what is required for normal contract performance. To compute aircraft payload, the contractor will use Federal Aviation Administration (FAA) approved weight and balance methods and procedures.

1.3.3.2 The contractor shall comply with all pertinent military regulations and/or directives, which pertain to the conduct of contractor personnel in military flight patterns and on military installations. Regulations can be obtained from the Airfield Operations Manager at Naval Base

Ventura County Air Operations Department (805) 989-8521, https://www.cnic.navy.mil/Ventura/OperationsAndManagement/Operations/AirOperations/index

.htm

Or NBVCINST 3710.1 (Air Operations Manual).

1.3.3.3 Emergency survival equipment must be carried on aircraft as outlined in Sec 135.167, 14CFR under Federal Aviation Regulation (FAR). The contractor shall comply with Federal

Aviation Regulation (FAR), part 135 concerning emergency equipment over extended over-water operations.

1.4 DELIVERABLES/NOTICES AND REPORTS

1.4.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, if any, on board

1.4.1.7 Number of injured and fatalities aboard the aircraft.

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

1.4.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.

1.4.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, as defined in 49 CFR, Part 830, the contractor shall transmit the information in paragraph 1.4.1 by the most expeditious means available on the next business day to HQ AMC/A3B, Scott IL (618)

229-4801 or (618) 229-4343.

1.4.4 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.

1.4.5 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)

1.4.6 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

1.4.6 SAFETY AND FINANCIAL INFORMATION. As required by the Air Safety Clause at

TRANSFARS 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.

1.5 CYBER SECURITY

1.5.1. General Cyber Security Requirements

1.5.1.1. Handling and Protection of Non-Public Information

In performance of this contract, the contractor may have access to Controlled Unclassified

Information (CUI) , which for the purposes of this section shall mean any information developed or received in the course of planning, ordering, shipping, tracking, and invoicing in support of the requirements of this contract. To adequately protect this CUI, contractor information systems (IS) involved in the performance of this contract shall comply with the security requirements in the current version of the National Institute of Standards and Technology (NIST)

Special Publication (SP) 800-171, “Protecting Controlled Unclassified Information in Nonfederal

Information Systems and Organizations,”. Compliance with NIST SP 800-171 measures is required at the prime contractor level and does not apply to subcontractors and other entities that the prime contractor engages with in order to meet the requirements of this contract.

Additionally, the contractor agrees to use such information only for the purposes of fulfilling the contracted requirements and to protect such information from unauthorized release or disclosure.

Protection of the CUI does not abrogate any responsibilities of the contractor to comply with or implement additional cyber security requirements as part of generally accepted system security principles or as required by other categories of information that may be co-resident with the CUI on the contractor’s IS.

1.5.1.2. Operationally Critical Support

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

DFARS 252.204-7012 Safeguarding Covered Defense Information and Cyber Incident

Reporting.

1.5.2. Cyber Security Assessments and Mitigation Plans (Reserved)

1.5.3. Cybersecurity Incident Reporting

1.5.3.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:

1.5.3.1.1. Unauthorized data exfiltration, manipulation or disclosure of any DoD information resident on or transiting the contractor's unclassified or classified information systems or networks.

1.5.3.1.2. Unauthorized access to the contractor’s unclassified or classified information system(s) or networks(s) on which DoD information is resident or transiting.

1.5.3.1.3. Cyber-incidents as listed in the MITRE ATT&CK Framework available at https://attack.mitre.org/, incorporated herein by reference, which affect network or information systems where DoD information is resident or transiting.

1.5.3.1.4. 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.

1.5.3.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.

1.5.4. 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 practicable, but no later than 24 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-220-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@mail.mil.

1.5.5. Mandatory Reporting Data

1.5.5.1. The contractor shall work with the USTRANSCOM CyOC through resolution of the incident. Within 24 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)

1.5.5.2. The contractor shall provide a follow-on cyber-incident report to the USTRANSCOM

CyOC within 72 hours 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

1.5.6. Incident Reporting Coordination

1.5.6.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.

1.5.6.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.

1.5.6.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.

1.5.6.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 1.5.5.1.

and 1.5.5.2.

1.5.7. 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, counter intelligence, 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.

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.0 SERVICE DELIVERY SUMMARY

Performance Objective PWS Paragraph Performance Threshold

Contractor shall provide and maintain fixed- and rotary- wing aircraft and range test support as required.

1.3.1.1

1.3.1.2

95% of the time, within 24 hour notification measured monthly

Contractor aircraft shall depart on time.

1.3.2.2

1.3.2.3

90% monthly missions

Required Licenses 1.3.3.2

4.9.3

100% compliance with all licensing regulations and requirements.

3. 0 GOVERNMENT FURNISHED PROPERTY AND SERVICES

3.1 When the contractor is directed to land at Government installations, the following

Government services will be received at these stations at no cost to the contractor: ground handling of aircraft, air traffic control, and airfield safety protection.

3.2 The Government shall provide the contractor with a list of personnel authorized to schedule and request flights. While performing the services set forth in this contract, the contractor shall not permit any person to board the aircraft unless authorized by the COR.

4.0 GENERAL INFORMATION

4.1 The contractor shall not permit any unauthorized persons to board the aircraft. At each departure airfield the contractor will ensure that an accurate passenger manifest is left with appropriate airfield authorities, e.g. military air operators or civilian Fixed Base Operators (FBO) personnel.

4.2 BAGGAGE The contractor is responsible for the loss and/or damage to passenger baggage and personal equipment while such items are in his custody or on board his aircraft. Liability for these items is limited to the actual value thereof, coverage commensurate with the commercial standard.

4.3 BILLING INFORMATION

4.3.1 Except when otherwise noted at time of mission scheduling, billing will begin and end at

Pt. Mugu, CA.

4.3.2 The contractor shall submit invoices no more than twice a month. A detailed breakdown shall be submitted in the Misc Information area of Wide Area Work Flow (WAWF) as an attachment.

4.4 REIMBURSABLE SERVICES AND COSTS

4.4.1. Reimbursable expenses, listed in the Schedule, shall be identified as separate items and shall be supported by paid receipts.

4.4.2. The Government will reimburse the Contractor, at cost, for airport fees assessed as a result of authorized performance under this contract. Examples of airport fees include landing and parking fees.

4.4.5. In the event the contractor’s crew is required to remain overnight on a mission, the contractor will be reimbursed per diem rates consistent with PL 99-234, Federal Civilian

Employees and Contractor Travel Expenses Act of 1985 and FAR 31.205-46(a)(2), during the performance period of this contract for each authorized overnight lodging. Food and lodging arrangements are the contractor’s responsibility. Claims for food/lodging expenses shall be supported by paid receipts to the maximum extent possible. In the event paid receipts cannot be furnished, other documentation must be submitted.

4.4.6. Economic Price Adjustment based on Actual Cost of Fuel – Airlift: In order to protect the contractor and the government from significant market fluctuations in the price of fuel, an adjustment will be made based on actual costs incurred.

4.4.6.1 Economic price adjustment (EPA) is limited to changes in the contractor’s cost for fuel only.

4.4.6.2 Allowable fuel adjustments will be made upward or downward only if the price of fuel varies by more than one cent per gallon from the following pegged rate for fuel:

FUEL TYPE PEGGED RATE (Base Price)

JP-8 $2.37

JET-A $2.90

JET-A-1 $2.90

Av Gas 100LL $5.18

4.4.6.3 When the average price per gallon paid by the contractor is greater than the established base price indicated above, the government will reimburse the contractor the difference between the price paid and the established base price.

4.4.6.4 When the average price per gallon paid by the contractor is below the established base price indicated above, the contractor will reimburse the government the difference between the price paid and the established base price. Under these circumstances, the contracting officer will issue a demand letter and funds will be reimbursed as directed.

4.4.6.5. Reporting requirements for adjustments are as stated in the contract, but no later than 30 days after month’s end.

4.4.6.6. The actual average cost per gallon under this EPA clause shall be rounded to four decimal positions (e.g., $2.3699).

4.4.6.7. For the contracting officer to consider any request for adjustment, the contractor shall submit data that clearly supports any request for adjustment. At a minimum, the contractor shall submit: 1) total mileage flown in performance of the contract; 2) fuel costs associated with that performance; and 3) associated financial data or receipts, as required by the contract.

4.4.6.8 Fuel adjustments will be made using the CLIN titled Fuel EPA Reimbursable. The following steps will be taken to determine the adjustment:

4.4.7 The contractor’s fuel burn rate, established in the List of Aircraft in the contract, is multiplied by the total mileage flown in performance of the contract. In the case of a substitute aircraft not listed in the schedule, the lower burn rate of the substitute aircraft or the aircraft normally used in performance of the contract shall be used.

4.4.8 The product is then multiplied by the difference between the average price per gallon paid and the established base price in the contract (also known as the variance).

Example:

Miles flown in support of the contract = 23,654

Burn rate for aircraft type (in schedule) = 4.21 gallons per mile

Base price of fuel established in the contract = $2.50

Actual average cost per gallon = $2.6308

Calculation:

Miles * Burn Rate * EPA Price Variance = Adjustment

23,654 * 4.21 = 99,583.34* $0.1308 = $13,025.50

4.5 AIR CARRIER INSURANCE REQUIREMENTS

4.5.1 Prior to performance of any services hereunder, the contractor shall, at its own expense procure and maintain during the entire performance period of this contract, with a financially and legally responsible insurance company, at least minimum insurance coverage as required by

FAA and DOT.

4.5.2 The contractor will provide written verification of insurance coverage to the Contracting

Officer at USTRANSCOM TCAQ-R, 508 Scott Dr, Scott AFB IL 62225-5357 prior to the contract award. The contractor shall provide annual proof of insurance from the insurance provider to the Contracting Officer. In the event of a planned cancellation or material change in policy coverage, thirty (30) days prior written notice shall be given to the Contracting Officer. In the event of an unplanned cancellation or material change in policy coverage, notice shall be given to the Contracting Officer as soon as possible.

4.6 LANDING PERMITS

4.6.1 To permit the use of military installations, the contractor must obtain landing permits following service specific instructions no later than 30 days prior to required approval 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 on operator.

4.6.1.1 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.

4.6.1.2 NAVY/MARINE CORP AIR STATIONS. Call Ms. Audrey Taylor for instructions at

(202) 685-9202, audrey.taylor@navy.mil or access https://portal.navfac.navy.mil/portal/page/portal/extranet/afl/afl_airfields_tab Begin the process no later than 60 days prior to required approval date.

4.6.1.3 ARMY INSTALLATIONS. POC: Corey Howard - corey.d.howard8.civ@mail.mil

4.7 AIRFIELD SUITABILITY AND RESTRICTIONS/CERTIFICATION AIRFIELDS

4.7.1 Contractors are reminded that airfield restrictions exist at certain military and commercial airfields worldwide. An Air Mobility Command (AMC) publication, entitled "Airfield

Suitability and Restrictions Report," identifies airfield restrictions specifically for AMC aircrews. This publication also lists "certification airfields" which are equivalent to FAA-designated "special airfields." These fields have unique airfield hazards and operating procedures requiring increased awareness and familiarity by aircrews. Contractors can obtain the current edition of this publication, at no cost, by contacting the following office:

HQ AMC/A3A3 TELEPHONE: (618) 229-3112

402 Scott Drive Unit 3A1 FAX: (618) 256-2019

Scott AFB IL 62225-5302

4.7.2 This publication is prepared for use by AMC aircrews and is made available to contractors for advisory purposes only.

4.7.3 Additionally, DOD, through the Defense Imagery Management Operations Center

(DIMOC), produces “Airport Qualification Program” (AQP) videos for some certification airfields. This contract requires that at least one pilot member of an aircrew, operating a DOD contract mission into a DOD- designated certification airfield, shall have performed pilot duties to that airfield within the past 12 months or reviewed an FAA- accepted pictorial, e.g., video, detailing airfield hazards within 30 days prior to performing the DOD contract mission. These are available for advisory purposes only, at no cost (one copy per contractor), by contacting the following office:

mailto:corey.d.howard8.civ@mail.mil

DIMOC TELEPHONE: (888) 743-4662

Building 3, Room 105 FAX: (570) 895-6106

11 Hap Arnold Blvd. E-Mail: askdimco@dma.mil

Tobyhanna, PA 18466-5102 Website:http://defenseimagery.mil

4.7.4 Contractors shall ensure that aircrews are adequately briefed on all restrictions at applicable airfields, including certification airfields, and properly trained before performing any

DOD contract mission into these airfields.

4.8 POST AWARD PRE-PERFORMANCE CONFERENCE

The contractor shall attend a post-award conference conducted by the Contracting Officer, if one is held, prior to the start of performance. The contractor, at a minimum, shall be represented by his designated agent. The contractor shall be notified of the exact time and location of the conference not later than (7) days prior to the scheduled conference date.

4.9 SECURITY: Physical, Personnel, Information, Antiterrorism/Force Protection and

Industrial Security

4.9.1 General Security Information:

The majority of daily work associated with this PWS is at the UNCLASSIFIED level; however contractor personnel may have access to classified areas and equipment which require SECRET eligibility and access posted in the Joint Personnel Adjudications System (JPAS). In addition all contractor personnel involved in the actual recovery and transportation of classified drones will have personnel clearances at the SECRET level. Furthermore, contractor personnel with access to Information Assurance (IA) administrative privileges and/or who will monitor Department of

Defense IT systems or software as designated by DOD 8500.1/5200.2-R may be rated at the various levels listed in paragraph 4.8.2 below. The stipulation of the numbers and what IT/ADP levels the contractors will have is directed by the COR or the CO before the start of the contract.

The contractor shall not divulge any financial, planning, programming, or budgeting information without the express consent of the Government as outlined in Operational Security (OPSEC) and

Information Security regulations. The contractor shall comply with all appropriate provisions of applicable security regulations. Specific security requirements are identified in the DD Form

254, DOD Contract Security Classification Specification. A completed/signed DD Form 254 is attached to the contract.

4.9.2 Personnel Security Requirements:

The contractor’s, subcontractors, and/or partner’s personnel performing services under this contract, shall be citizens of the United States of America. Personnel who are dual citizens must be identified to the COR and must obtain a final security clearance before reporting to perform services under this contract. Dual citizens will not be given access to classified information/areas on the basis of an interim clearance. The contractor, subcontractor(s), and/or partner(s) shall possess the capability to articulate well, speak and write fluently in the English

Language, and comprehend the English Language. Overall, all contractor personnel shall possess the appropriate personnel security investigation for the position occupied. Contractor personnel shall be required to have a background investigation that corresponds with the sensitivity level of the tasks to be performed.

The following guidance will be followed when determining background investigation and clearance levels for this contract depending on requirements. No personnel will require

IT/ADP/Critical Sensitive levels in support of this requirement.

IT-II/ADP-II/Non-Critical Sensitive Positions

Those positions in which the incumbent is responsible for the direction, planning, design, operation, or maintenance of a computer system, and whose work is technically reviewed by a higher authority of the ADP-I category to ensure the integrity of the system.

(IT-II/ADP-II/Non-Critical Sensitive) Background Investigation Requirements:

Positions designated by the Government at the Non-Critical Sensitive/ADP-II/IT-II rating require a National Agency Check with Local Credit (NACLC) (or acceptable periodic reinvestigation) favorably adjudicated (a favorable adjudication grants eligibility at the SECRET level as prescribed by DOD 5200.2-R). The IT-II/ADP-II requirement mandates the contractor have a minimum FCL at the SECRET (or higher) level due to investigation submissions as directed in

DOD 5220.22-M, DOD 5200.1-R and JPAS.

IT III/ADP III/Non-Sensitive Positions

All other positions involved in computer activities and Common Access Card / PIV Card issuance. No clearance is granted for classified access and only a Position of Trust is awarded and posted in the Joint Personnel Adjudication System (JPAS).

(IT-III/ADP-III/Non-Sensitive) Background Investigation Requirements:

Positions designated by the Government at the Non-Sensitive/ADP-III/IT-III rating require a

National Agency Check with Inquiries (NACI) (or acceptable investigation/reinvestigation) favorably adjudicated (a favorable adjudication issues a Position of Trust determination as prescribed by DOD 5200.2-R and DOD DTM 08-003 (Dated Dec 08). Favorable NACI or equivalent investigation results must be posted in JPAS before a Common Access Card (CAC) or

NIPRNET access will be granted. To obtain interim CAC/NIPRNET access, NACI investigations will be opened with fingerprint, name and criminal records checks returned favorably before the credentials (CAC and NIPRNET) are issued. NACI submissions will be completed on the Standard Form (SF) 85P and submitted with fingerprint cards (FP 258) to

USTRANSCOM Force Protection, Security Services Center (SSC) for processing. No classified access will be granted based on the NACI investigation.

NOTE: The above requirements for IT-III/ADP-III/Non-Sensitive Positions are for access to unclassified systems only. Contractors who require access to classified systems or areas must have interim or final adjudication of background investigations at the Critical or Non-Critical

Sensitive levels.

The contractor needs to understand and be aware that USTRANSCOM will only process

NACI/Position of Trust investigations. These background investigations are not the DoD prescribed personnel security investigations for classified access. It is incumbent upon the contractor to have the appropriate investigations completed upon start of the contract.

4.9.3 Facilities Clearance Level (FCL):

The contractor must have a valid Secret FCL at time of request for proposal. FCL procedures and security guidelines for adjudicative requirements are outlined in DoD 5220.22-M Operating

Manual. FCLs and Interim FCLs must be awarded by the Defense Counterintelligence and

Security Agency (DCSA) Facility Clearance Branch.

4.9.4 Personnel and Facilities Clearance Validation:

Upon contract award, the contactor shall submit the names of contractor personnel to the

USTRANSCOM Mission Assurance Division (TCJ34) Industrial Security Manager for vetting through JPAS to ensure investigative and clearance requirements have been satisfied. This shall be completed before the COR/Trusted Agent (TA) accesses the DoD Trusted Associate

Sponsorship System (TASS) to create and approval a CAC application. If a contractor’s employee does not have the required investigative or security clearance level based on the

Government’s determination, the contractor’s employee will be denied the ability to work in support of this contract.4.8.5 Additional Security Conditions:

Upon completion of this contract, the contractor’s personnel shall surrender all Government supplies, materials and equipment to the COR. Any assigned contractor personnel who possess a security badge shall turn in those badges to the SSC in person during out-processing. Contractor personnel shall out-process on the last day of the contract or upon termination or reassignment from duties under this contract.

4.9.6 The Government shall ensure the roles/privileges assigned to contractor personnel on the

Government computing platforms are limited to the roles/privileges essential to that individual’s performance of his/her assignments. The Government may limit or revoke these roles or privileges for any reason.

4.9.7 If the Government notifies the contractor that the employment or the continued employment of any contractor personnel is prejudicial to the interests of or which endangers the security of the United States of America (USA), that employee shall be removed and barred from the worksite. Matters prejudicial to the interests of or which endangers the security of the USA include, but are not limited to, security deviations/incidents. This also includes credible derogatory information uncovered in background investigations and any information received through law enforcement channels. In such cases the contractor shall make any changes necessary in the appointment(s) of personnel at no cost to the Government.

4.9.8 No antiterrorism (AT) measures are required except compliance with those in force at the military installation the contractor employees may access.

4.9.9 Contractor employees with Transportation Worker Identification Credentials (TWIC) issued by the Transportation Security Administration (TSA) do not satisfy the DoD requirement for a background investigation for accessing classified information.

Security Regulation Guidance:

Department of Defense (DOD):

2000.16 (DOD Antiterrorism (AT) Standards)

5200.1-R (DOD Information Security Program)

5200.2-R (DOD Personnel Security Program)

5200.08-R (DOD Physical Security Program)

5220.22-M (National Industrial Security Program Operating Manual)

8500.1 (Information Assurance (IA))

2000.12 (DOD Antiterrorism (AT) Program)

8500.2 (Information Assurance (IA) Implementation)

DOD regulations found at: http://www.dtic.mil/whs/directives/corres/pub1.html

Scott Air Force Base:

SAFB Instruction 31-101 (Installation Security Instruction)

(Restricted publication. Sent only to .mil domains when forwarding. Not for public distribution.)

Forms:

DD 254, DOD, Contract Security Classification Specification

DOD forms found at:

http://www.dtic.mil/whs/directives/corres/pub1.html

Security Section Acronyms:

Acronym Definition

ANACI Access National Agency Check and Inquiries

AT Antiterrorism

CAC Common Access Card

CAGE Commercial and Government Entity

DISCO Defense Industrial Security Clearance Office

DOD Department of Defense

FP Force Protection

FCL Facilities Clearance Level

FOUO For Official Use Only

FSO Facilities Security Officer

JPAS Joint Personnel Adjudication System

GFP Government Furnished Property

NACLC National Agency Check with Local Agency and Credit Check

OPSEC Operations Security

OCA Original Classification Authority

PCL Personnel Clearance Level

SAFB Scott Air Force Base

SMO Security Management Office

USAF United States Air Force

USTRANSCOM United States Transportation Command

VAL Visit Authorization Letter

VAR Visit Authorization Request

USTRANSCOM Protection Programs Division (Industrial Security) Points of Contact:

USTRANSCOM

Attn: TCJ34 (Steve Stegen or Steven Strait)

508 Scott Drive

Scott AFB IL 62225

Commercial: 618-220-7892/220-6531 (respectively)

Email at steven.g.stegen.civ@mail.mil or steven.m.strait.civ@mail.mil

USTC TCJ34 Approval: Steven M. Strait, Chief, Protection Programs, USTC TCJ34 Tracking #: USTRANSCOM-FP-0027-20

SECURITY REFERENCES:

Defense Electronic libraries:

Assist – Quick Search: http://quicksearch.dla..mil

Department of Defense: http://www.esd.whs.mil/dd/dod-issuances/

USTRANSCOM: https://ww2.ustranscom.mil/publications/pubs_index.cfm

Governing guidance and directives:

DD Form 254, Contract Security Classification Specification, November 1, 2017

DoD 5200.08-R, “Physical Security Program,” May 27, 2009 DoD

5220-22-M, National Industrial Security Program Operating Manual (NISPOM),”

May 18, 2016

DoD Directive 5230.25, “Withholding of Unclassified Technical Data from Public Disclosure,”

August 18, 1995 DoD Instruction

2000.12, “DoD Antiterrorism (AT) Program,” May 8, 2017 DoD Instruction O-

2000.16, “DoD Antiterrorism (AT) Standards Program Implementation, Volume 1: DoD AT

Standards,” May 5, 2017 DoD Instruction O-

2000.16, “DoD Antiterrorism (AT) Standards Program Implementation, Volume 2: DoD force

Protection condition (FPCON) System, May 8, 2017 DoD Instruction

5200.01, “DoD Information Security Program and Protection of Sensitive Compartmented

Information (SCI), April 21, 2016 DoD Instruction

5200.02, “Personnel Security Program,” September 9, 2014 DoD Instruction

8330.01, “Interoperability of Information Technology (IT), Including National Security Systems

(NSS),” December 18, 2017 DoD Instruction 8500.01, “Cybersecurity,” March 14, 2014 DoD Instruction 8510.01, “Risk

Management Framework (RMF) for DoD Information Technology (IT),” July 28, 2017

DoD Instruction 8582.01, “Security of Unclassified DoD Information on Non-DoD Information

Systems,” October 27, 2017

DoD Manual 1000.13, Volume 1, “DoD Identification (ID) Cards: ID Card Life-Cycle,” January

23, 2014 http://quicksearch.dla..mil/ http://www.esd.whs.mil/dd/dod-issuances/ https://ww2.ustranscom.mil/publications/pubs_index.cfm

DoD Manual 5200.01, Volume 1, “DoD Information Security Program: Overview, Classification, and Declassification”, February 24, 2012

DoD Manual 5200.01 Volume 2, “DoD Information Security Program: Marking of Classified

Information,” March 19, 2013

DoD Manual 5200.01 Volume 3, “DoD Information Security Program: Protection of Classified

Information,” March 19, 2013

DoD Manual 5200.02, “Procedures for the DoD Personnel Security Program (PSP),”

April 3, 2017

DoD Manual 5220.22, Volume 3, “National Industrial Security Program: Procedures for

Government Activities Relating to Foreign Ownership, Control, or Influence (FOCI),” April 17, FD Form 258, fingerprint Card

USTRANSCOM Instruction 31-02, “Security Classification Guide,” 6 April 2018

USTRANSCOM Instruction 31-12, “Operations Security,” February 19, 2015

Scott Air Force Base: AF Instruction 31-101_AMC, January 4, 2014 Scott AFB

Supplement is a restricted publication: Send only to .mil domains when forwarding - Not for public distribution

Federal Information Processing Standards (FIPS) and National Institute of Standards and

Technology (NIST): https://csrc.nist.gov/publications

FIPS 199, “Standards for Security Categorization of Federal Information and Information

Systems,” February 2004

FIPS 200, “Minimum Security Requirements for Federal Information and Information Systems,”

March 2006

NIST SP 800-18 Revision 1, “Guide for Developing Security Plans for Federal

Information Systems” February 2006

NIST SP 800-30 Revision 1, “Guide for Conducting Risk Assessments,” September 2012

NIST SP 800-37 Revision 1, “Guide for Applying the Risk Management Framework to

Federal Information Systems: a Security life Cycle Approach,” June 5, 2014

NIST SP 800-53, Revision 4, “Security and Privacy Controls for Federal Information

Systems and Organizations,” January 22, 2015

NIST SP 800-53A Revision 4, “Assessing Security and Privacy Controls in Federal

Information Systems and Organizations: Building Effective Assessment Plans,”

December 18, 2014

NIST SP 800-60 Volume 1, Revision 1, “Guide for Mapping Types of Information and

Information Systems to Security Categories,” August 2008

NIST SP 800-61 Revision 2, “Computer Security Incident Handling Guide,” August

NIST Special Publication 800-171 Revision 1 “Protecting Controlled Unclassified

Information in Nonfederal Systems and Organizations, “ December 2016

Committee on National Security Systems (CNSS):

https://www.cnss.gov/CNSS/issuances/Instructions.cfm

CNSS Instruction 1253, “Security Categorization and Control Selection for National Security

Systems,” March 27, 2014 https://csrc.nist.gov/publications https://www.cnss.gov/CNSS/issuances/Instructions.cfm