Attachment A PWS ICEX2026.pdf

Performance Based Statement of Work

For

ICEX 2026 Operation Ice Camp Air Charter Services

To

Undersea Warfighting Development Center Detachment Arctic Submarine Laboratory

December 1, 2025

UWDC Detachment Arctic Submarine Laboratory Performance Work Statement

Table of Contents 1 Scope

2 References

Reference Documents

3 Requirements

Charter Aircraft Services

4 Government Furnished

Government Furnished Equipment / Services

Government Furnished Information

5 Period of Performance

6 Service Delivery Summary (SDS)

7 Cybersecurity ………………………………………………………………………………………….7

8 Security… ...………………………………………………………………………………………

9 References.…………………………………………………………………………………………

BACKGROUND

The U.S. Navy’s Undersea Warfighting Development Center (UWDC) Detachment Arctic Submarine Laboratory’s mission is to support the fleet as the “center of excellence” for Arctic matters to enable the submarine force to safely and effectively operate in the unique Arctic Ocean environment, develop and train forces in the tactics, techniques, and procedures required for Arctic operations and exercises; develop and maintain personnel with expertise in Arctic-specific knowledge, skills, and capabilities; plan and coordinate technical development, operations test and evaluations and employment of systems that assure access for Navy forces to engage in the Arctic region; and coordinate with organizations on Arctic-related matters.

A primary means to meet this mission is through an Ice Exercise (ICEX) or Operation Ice Camp (OIC).

ICEX/OIC is the Navy's RDT&E exercise used to validate and assess operational readiness of the submarine force in the Arctic while continuing research and military training in extreme cold conditions and the undersea environment. The U.S. Navy has been conducting Arctic and undersea exercises since the 1940's, to include the first under-ice dive by the USS Boarfish (SS 327) in 1947. These exercises extended to arctic exploring and submarine operations under the polar ice canopy became known as Ice Exercises. The frequency and scope of these ice exercises have changed over the years to include a more robust submarine support capability on the ice through an "ice station" or "ice camp." Aircraft that can take off and land on drifting sea ice is required to support these ice camps.

1 SCOPE

This performance work statement (PWS) describes the tasks required of the contractor to support the Undersea Warfighting Development Center Detachment Arctic Submarine Laboratory by providing air charter services to the drifting ice camp. INTERESTED AIR OPERATORS ARE NOT REQUIRED TO

PROVIDE ALL SERVICES IN THE PWS. AIR OPERATORS MAY PROPOSE TO MEET ANY ONE

OR MORE AIRCRAFT REQUIREMENT IN THE PWS.

2 REFERENCES

Reference Documents

a. CFR Title 32 Part 861, DOD Commercial Air Transportation Quality and Safety Review Program.

b. DOD Instruction 4500.3, DOD Commercial Air Transportation Quality and Safety Review

Program.

3 REQUIREMENTS

Charter Aircraft Services Contracts for Air Charter Services will be contingent upon air operators approval from the DoD Commercial Airlift Review Board (CARB) in accordance with References 2.1.a and 2.1.b. Air Operators do not need to be DoD approved to submit proposals for chartered air services but they will need to go through the DoD approval process and contract award is contingent upon receiving the DoD Approved Air Carrier authorization. Two pilots are required for all flights, even with single engine aircraft if that aircraft supports a second pilot.

All aircraft will conduct operations from Deadhorse, Alaska Airport (ICAO: PASC, IATA: SCC) and support a drifting ice camp approximately 100 NM to 225 NM from the airport. All aircraft must be equipped with GPS, navigation, and communication equipment. The ice camp will have communications, heated shelters, electrical power, real-time weather observations and forecasts, berthing, and food as required. Air Operators are expected to procure fuel for their aircraft.

The projected dates, service periods, service durations, and flight hours are notional and subject to change pending planning during the duration of the contract. All listed preferences are not requirements and aircraft that do not meet preferences will still be evaluated.

Ski-Wheel Equipped Aircraft #1 (Pioneering Landings, General Purpose) (CLIN 0001)

Contractor shall conduct Pioneering Landings. The Pioneering Landing flight is the aircraft that conducts the initial landing on the sea-ice; there is no person on the ice at this time, no physically measured ice thickness, and no groomed runway. The plane may use wheels, skis, or a combination and have endurance minimum of five hours to travel to various ice floes selected by the Navy through satellite imagery analysis, approximately 100 NM to 225 NM from Deadhorse Airport (SCC) in Prudhoe Bay, Alaska. The aircraft must be able to operate without a groomed runway.

The aircraft operator and pilot must have experience with Pioneering Landings. The aircraft must be able to take off and land on the sea-ice in under 2000 feet but a distance of 1500 feet or less is highly preferred. It is anticipated that this aircraft will support up to five planned Pioneering Landings on drifting sea ice to conduct pioneering efforts to select a suitable location to build an ice camp. It is expected that the aircraft will remain on the sea-ice for approximately 1 – 2 hours during Pioneering Flights to conduct ice surveys.

The aircraft shall accommodate at least the pilot and four passengers during Pioneering Landing flights. The experienced pilot will select a suitable landing site on the ice floe with guidance and concurrence from Operation Ice Camp personnel. Pilot must be capable of landing the aircraft on first year sea ice. Passengers will carry approximately 250 lbs. of ice auger equipment, scientific equipment, and emergency survival gear. Aircraft capacity to support at least 2000 lbs. payload while in ski-wheel configuration with 200 NM range (i.e., 200 NM from airport to sea ice and then 200 NM from the sea ice back to the airport without refueling) is required. Ability to take extra fuel and refuel on the drifting sea ice is preferred (up to 100 gallons of fuel).

After the pioneering stage, the ice runway will be built, and these aircraft will continue to support the ice camp by utilizing the ice runway. The ski-wheel configuration is still required throughout the duration of the period of performance as a contingency for ice breakups where landing on ungroomed ice may be required until a new ice runway is built. When operating from a runway, the aircraft must be able to operate from a 1500 ft. compacted snow or ice runway for both takeoff and landings with a payload of at least 2000 lbs. and seating capability for at least nine passengers.

Aircraft must be able to support at least two round trips to the ice camp each day; three round trips per day capability is preferred assuming the ice camp is 225 nautical miles from Deadhorse Airport.

Total Projected Service Period: Specific dates will be provided upon request.

Projected Flight Hours: 148 total flight hours

Minimum Flight Hours: 111 total flight hours

Ski-Wheel Equipped Aircraft #2 (Pioneering Landings, General Purpose) (CLIN 0002)

Contractor shall conduct Pioneering Landings. The Pioneering Landing flight is the aircraft that conducts the initial landing on the sea-ice; there is no person on the ice at this time, no physically measured ice thickness, and no groomed runway. The plane may use wheels, skis, or a combination and have endurance minimum of five hours to travel to various ice floes selected by the Navy through satellite imagery analysis, approximately 100 NM to 225 NM from Deadhorse Airport (SCC) in Prudhoe Bay, Alaska. The aircraft must be able to operate without a groomed runway.

The aircraft operator and pilot must have experience with Pioneering Landings. The aircraft must be able to take off and land on the sea-ice in under 2000 feet but a distance of 1500 feet or less is highly preferred. It is anticipated that this aircraft will support up to five planned Pioneering Landings on drifting sea ice to conduct pioneering efforts to select a suitable location to build an ice camp. It is expected that the aircraft will remain on the sea-ice for approximately 1 – 2 hours during Pioneering Flights to conduct ice surveys.

The aircraft shall accommodate at least the pilot and four passengers during Pioneering Landing flights, although the capability to accommodate five or more passengers is preferred. The experienced pilot will select a suitable landing site on the ice floe with guidance and concurrence from Operation Ice Camp personnel. The aircraft must also provide capacity for 250 lbs. of ice auger equipment and emergency survival gear; capacity to support higher payload is preferred.

Ability to take extra fuel and refuel on the drifting sea ice is preferred.

After the pioneering stage, the ice runway will be built, and aircraft will continue to support the ice camp by utilizing the ice runway. The aircraft may switch (highly preferred) to a wheel configuration (i.e. remove skis) after the ice runway is built and keep the skis in the Operation Ice Camp hangar in Deadhorse, AK to allow for higher payload capacity. When operating from a runway, the aircraft must be able to operate from a 1500 ft. compacted snow or ice runway for both takeoff and landings with a payload of at least 2000 lbs. and seating capability for at least nine passengers. Aircraft must be able to support at least two round trips to the ice camp each day; three round trips per day capability is preferred assuming the ice camp is 225 nautical miles from Deadhorse Airport.

Total Projected Service Period: Specific dates will be provided upon request.

Projected Flight Hours: 167 total flight hours Minimum Flight Hours: 125 total flight hours

Rear Loading Aircraft (Personnel and Cargo) (CLIN 0003)

Contractor shall conduct charter aircraft service for a Rear Loading Aircraft to transport cargo and personnel. This aircraft will be required to support the ice camp to include the ice camp deployment, heavy load operations, and the ice camp demobilization. The aircraft must be able to operate from a 2500 feet compacted snow or ice runway for both takeoff and landings with a payload capacity of at least 4000 lbs.; 5000 lbs. payload capacity is preferred. Rear loading ramp and rollers (internal and rear ramp) are preferred. Aircraft must be able to transport objects with lengths up to 19 feet.

Aircraft will be used primarily for cargo and secondarily for personnel transport. Removable aircraft seating required for at least 16 passengers for occasional personnel transport. Ability to support aerial delivery operations is preferred (e.g. dropping small Ice Tracker buoys from the aircraft or parachute rigged pallets/equipment). Aircraft must be able to support at least two round trips to the ice camp each day, three round trips per day capability is preferred, assuming the ice camp is 225 nautical miles from Deadhorse Airport.

Projected Service Periods: Specific dates will be provided upon request.

Projected Flight Hours: 168 total flight hours* Minimum Flight Hours: 126 total flight hours

*Project Flight Hours for Cargo Aircraft based on capability of a Casa 212 aircraft. Other aircraft may provide different cargo transport capability (higher or lower), which accounts for the spread between minimum and projected flight hours for this requirement.

Rotary Wing Aircraft (Personnel and Cargo, 2 Aircraft) (CLIN 0004)

Contractor shall conduct charter aircraft service for helicopter services at the ice camp. This shall include helicopter transport of personnel and equipment between the ice camp and remote ice locations (e.g. several miles from the ice camp), emergency medical evacuations (from ice camp back to Prudhoe Bay, Alaska or Utqiagvik, Alaska depending upon location of the ice camp), and recovery of exercise equipment. One helicopter must be able to conduct external sling load operations with a 2900 lbs. object for a 20 minute flight, the other helicopter must be able to conduct sling load with at least 2000 lbs. Helicopters must have passenger capacity of at least seven passengers comfortably with passengers wearing Arctic grade clothing, although eight-passenger capacity is highly preferred. For reference, a Bell 212 and Bell 412 helicopter have provided adequate support for these requirements in the past. Rotary aircraft must be able to fly to the ice camp without refueling enroute, assuming the ice camp is 225 nautical miles from Deadhorse Airport. Rotary aircraft will be able to refuel at the ice camp.

The ice camp can provide fuel containment for the helicopter fuel at the ice camp along with other aircraft support equipment (e.g. berms, generator, aircraft heater). The air operator is required to procure the helicopter fuel and barrels for the fuel; the Navy can transport the fuel to the ice camp (see PWS 4.1.a). Recommend air operator provide their own aviation-grade fuel transfer pump at the ice camp. The ice camp will provide lodging and food on the ice for the helicopter crews, at no cost.

First Helicopter Projected Service Periods: Specific dates will be provided upon request.

Projected Flight Hours: 67 total flight hours Minimum Flight Hours: 50 total flight hours

Second Helicopter Projected Service Periods: Specific dates will be provided upon request.

Projected Flight Hours: 60 total flight hours Minimum Flight Hours: 45 total flight hours

Service period at the ice camp for the helicopter with 2900 lbs./20-minute sling load requirement;

helicopter that meets this heavier lifting requirement must be at the ice camp for specific duration.

(Specific dates will be provided upon request.)

4 GOVERNMENT FURNISHED

Government Furnished Equipment / Services

a. The government will provide fuel containment systems (i.e. berms) for the helicopter fuel at the ice camp. The government will transport the Air Charter Service-procured helicopter fuel to the ice camp if it is in 55 gallon drums or other similarly sized containers. The government can assist in fuel movements at the ice camp. Helicopter crew should bring an aviation fuel transfer pump.

b. The government will provide a heated working space up to 100 square feet at the ice camp for the helicopter crew equipment.

c. The government will provide 2KW portable inverter generators at the ice camp. The government will provide a higher rated portable inverter generator at the ice camp (e.g. 4.5 kW) if required. The government will also provide the fuel to run these portable generators as necessary to support aircraft electrical requirements.

d. The government will provide lodging and sustenance for helicopter personnel while at the ice camp. Lodging will be provided at the ice camp through tents that are shared with other ice camp personnel. All meals will be provided for the helicopter crew at the ice camp.

e. The government will rent a hangar facility in Deadhorse, Alaska. All aircraft supporting the ice camp will be able to utilize the hangar apron, and supplied electrical power, for the aircraft. Limited space inside the hangar may be provided for aircraft maintenance equipment. Limited space in the hangar facility may be utilized daily as office space for personnel.

Government Furnished Information

a. The government will provide information suitable for the ice camp operations. This information may include radar and satellite imagery, meteorological observations and forecasts, and sea ice measurements.

5 PERIOD OF PERFORMANCE

The overall projected period of performance is Mid-February 2026 through the End of March 2026, but each aircraft requirement has its own period of performance.

6 SERVICE DELIVERY SUMMARY (SDS)

Performance Objectives PWS Paragraph (s)

Performance Threshold

All aircraft arrive within one (1) hour after the scheduled arrival time.

3.1.1, 3.1.2, 3.1.3, and 3.1.4

95% or higher computed on average of all flights

Carry the scheduled loads of passengers/cargo on each flight.

3.1.3 100% of the time

Provide aircraft and services free of discrepancies. 3.1 95% of the time

Cyber-Incident Reporting 9.2 Provide timely cyber-incident reporting.

No more than one late cyber-incident report or unreported cyber-incident in a twelve (12) month period.

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 9.5.1. and 9.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.

7.7. Implementation of Cybersecurity Maturity Model Certification (CMMC) Program To ensure adequate safeguards for the CUI defined in para. 5.2.1., CMMC level 2 (self) certification is required. The Contractor shall have a current (i.e. not older than 3 years) CMMC certificate at the CMMC level required by this contract and maintain the CMMC certificate at the required level for the duration of the contract. Additional information related to the CMMC program may be found at https://dodcio.defense.gov/cmmc/Resources-Documentation/.

7.8 Operational Security (OSPEC). Protecting critical information (friendly activities, intentions, capabilities, or limitations) is crucial to prevent adversaries from gaining advantage. Therefore, contractors must adhere to OPSEC requirements throughout the contract lifecycle. All information provided is for official use only. Additionally, mandatory initial and annual OPSEC training is required after contract award for all contractors working on-site at a DoD facility or off-site accessing a Federally controlled information system. Proof of completion must be available to the COR/CO. Training can be accessed at the following website: (https://securityawareness.usalearning.gov/opsec/index.htm ).

Immediately consult the contracting office’s OPSEC coordinator regarding the USTRANSCOM Critical Information and Indicators List (CIIL) and any OPSEC questions. Protect critical information (e.g., mission details, units, cargo) from unauthorized disclosure and coordinate with the government to minimize shared information. Report suspected/known compromises immediately to the COR and security office. Safeguard information (including FOUO and CUI) per the CIIL using measures like: encryption; locked storage;

restricted distribution; secure destruction; limiting verbal discussions; avoiding unencrypted phones/foreign mail; prompt document retrieval; cover pages; and minimizing public disclosure. Contact the COR/CO for clarification.

8.0 Security (Industrial, Personnel, Physical, Information, and Antiterrorism/Force Protection)

8.1. General Security Information: The majority of daily work associated with this PWS/SOW is at the unclassified level. Access to classified information is NOT authorized on this contract.

8.2. Citizenship and Clearance Requirements: All personnel that will have Information Technology (IT)/Automated Data Processing (ADP) privileged access (i.e. Privileged Users) to US Information Systems (IS), and/or classified information, classified systems, or classified areas, shall be US citizens. Foreign Nationals or Local Nationals employed by the DoD are not authorized to have privileged access to US Information Systems. Non-US citizens are not eligible for Common Access Cards (CACs) unless they meet the parameters stated in Department of Defense Manual (DoDM) 1000.13, Volume 1.

8.3. Information Systems (IS) Roles/Categories and Associated Suitability Requirements (Federal Investigative Standards): Contractor personnel with IA administrative privileges and/or who will monitor DoD IT systems or software as designated by DoD Instruction 8500.01 and DoD Manual

5200.02 may be rated at the various levels listed below. The IS roles/categories and the number of personnel assigned to each role is approved by the COR or the CO before the start of the contract/task order. The contractor shall comply with the appropriate provisions of applicable security regulations while assigned to this contract/task order for DOD and USTRANSCOM. The following guidance https://dodcio.defense.gov/cmmc/Resources-Documentation/ https://securityawareness.usalearning.gov/opsec/index.htm will be followed when determining background investigation levels for this contract/task order depending on requirements:

IS Role/Category Classified Access Required Investigation

General User (Non-Privileged Access) (IT/ADP-III, Non-Sensitive)

NO Tier 1 (T1)

Privileged User (e.g. System Administrator) (IT/ADP-I, Critical Sensitive)

NO Tier 5 (T5)

NOTE: USTRANSCOM Joint Security Office (TCCS-S) will initiate/administer Tier 1 investigations to determine CAC eligibility only, classified access will not be granted based on the Tier 1 investigation. Tier 5 investigations are the responsibility of the contractor. It is incumbent upon the contractor to have the appropriate investigation completed upon the start of the contract/task order.

8.4. Common Access Card (CAC) Issuance Procedures:

a) Facility Security Officer (FSO) will verify, via the DOD personnel security system of record, contractors on the contract/task order have the required background investigation to obtain a CAC and provide those names to the CO/COR. Contractors that require a Tier 5 investigation is the responsibility of the contractor. Contractors that only require a Tier 1 as determined by the FSO will submit to the TCCS-S Personnel Security Program Manager (through the CO or COR) an OF Form 306 (Declaration for Federal Employment) and a MP ICAM Form 1 with Section 1 completed. TCCS-S will initiate the SF-85 (questionnaire for Non-Sensitive Positions) via the National Background Investigation Services (NBIS) for completion and submission to DCSA, for Tier 1 investigations only.

b) At the same time, the contractor company will coordinate and obtain electronic fingerprinting for their employee. The third-party company will “electronically” capture the applicant’s fingerprints, using the USTRANSCOM (Submitting Office (SON), Security Office (SOI), and Agency Location Code (ALC)). Hardcopy fingerprint cards are NOT acceptable. These steps shall be completed before the COR/Mission Partner Affiliation Sponsor (MPAS) accesses the Mission Partner Identity, Credential, and Access Management (MP ICAM) system to create a CAC application.

c) Basic US Citizen Contractor CAC Requirements:

1. Requires access on a continual basis of 6 months or more.

2. Contractor personnel require access to a DoD facility or networks, either on-site or from a remote location.

3. Users need access to systems for platforms that requires CAC login or user authentication.

d) Basic Non-US Citizen Contractor CAC Requirements:

1. Meet (as direct/indirect DoD hire personnel), as identified in the DoDM 1000.13, Volume 1, the investigative requirements for DoD employment as recognized through international agreements pursuant to DoDI 1400.25, Civilian Personnel Management, Volume 1231. In addition to these investigative requirements, a fingerprint check against the FBI criminal history database, an FBI investigations files (name check search), and a name check against the Terrorist Screening Database shall be required prior to CAC issuance IAW Office of

Personnel Management Memorandum, “Final Credentialing Standards for Issuing Personal Identity Verification Cards under HSPD-12”, July 31, 2008.

2. Possess (as foreign military, employee, or contract support personnel), a visit status and security assurance that has been confirmed, documented, and processed IAW international agreements pursuant to DoDI 1400.25, Civilian Personnel Management.

e) CAC Applications:

1. The CAC applications (MP ICAM Form 1 with Section 1 completed) must have an adjudication Tier 1 or Tier 5 background investigation posted in the DoD personnel security system of record, or

2. An interim CAC may be approved when the contractor employee has a favorable fingerprint, name and criminal records check completed and has either a Tier 1 or Tier 5 background check “open” with DCSA.

3. The MP ICAM MPAS will not approve the CAC applications in MP ICAM until that MPAS has verified, with a member of USTRANSCOM TCCS-S, one of the above requirements.

8.5. Visits by Contractors to USTRANSCOM/SDDC Buildings: Any visit(s) by contractor personnel assigned to this contract/task order will submit the name(s), social security number(s), date of visit, and POC coordinating visit to the COR. COR will (1) work with TCCS-S Joint Security Desk on obtaining escort badges upon check-in and (2) conduct escort duties during contractor visit.

8.6. Security and Emergency Operations Training: USTRANSCOM Contractor personnel shall attend/complete the following training as prescribed by DoD, USTRANSCOM and Air Force Instructions: Workplace Violence, Annual Security Awareness, Operations Security (OPSEC), DOD Antiterrorism Level I, Active Shooter/Attacker, Emergency Operations, Combating Trafficking in Person (CTIP), Controlled Unclassified Information (CUI), and any Security Stand-down Day Training scheduled by the Commander, USTRANSCOM. Contractor personnel assigned elsewhere shall attend security training established by their respective Government security offices and/or installations. CUI training can be accessed via https://www.cdse.edu/Training/eLearning/IF141/.

8.7. Derogatory Information: Any member of the contracted company team (Program Manager, FSO, or other supervisory staff) aware of pending human resource activity of consequence (to include termination or suspension), behaviors or patterns of concern, or misconduct, to include reporting requirements in accordance with Security Executive Agent Directive (SEAD) 3 (for contractors with classified security eligibility), for any contractors supporting this contract/task order during the established period of performance, will immediately contact the USTRANSCOM Joint Security Office (TCCS-S) Attn: Industrial Security Program Manager. If the Government notifies the contractor that the employment or the continued employment of any contractor personnel is prejudicial to the interests or endangers the security of the United States of America and/or USTRANSCOM personnel, information, or assets; that employee shall be removed and barred from the worksite. This includes security deviations / incidents and credible derogatory information on contractor personnel as noted in the DoD personnel security system of record. Personnel who have incident reports posted in the DoD personnel security system of record will be denied the ability to support the contract/task order until the issues have been resolved and the incident has been removed in the DoD personnel security system of record. The contractor shall make any changes necessary in https://www.cdse.edu/Training/eLearning/IF141/ the appointment(s), at no additional cost to the Government. If any incident involves or may involve the mishandling of classified information or a potential Negligent Discharge of Classified Information, the USTRANSCOM Joint Security Office Attn: Industrial Security Program Manager, will be notified within 24 hours during the normal work week and within 72 hours if the incident occurs over the weekend.

8.8. Antiterrorism/Force Protection: Contractor employees will comply with antiterrorism Force Protection conditions (FPCONs) at the location they are performing work, whether it is CONUS or

OCONUS.

8.9. NOTE TO THE PRIME CONTRACTOR FACILITY SECURITY OFFICER (FSO): The prime contractor will forward the name, address, email address and telephone number of the Company FSO and backup to the USTRANSCOM Joint Security Office (TCCS-S) at:

transcom.scott.tccs.mbx.industrial-security@mail.mil

8.10. USTRANSCOM Joint Security Office (Industrial Security) POCs:

USTRANSCOM

Attn: TCCS-S (Industrial Security Specialist)

508 Scott Drive

Scott AFB, IL 62225

Commercial: 618-817-4078

8.11. USTRANSCOM TCCS-S Approval:

Jennifer Rodriguez, Industrial Security Program Manager, USTRANSCOM Joint Security Office

8.12. USTRANSCOM TCCS-S Tracking #: TCCS-S-028-2025

mailto:transcom.scott.tccs.mbx.industrial-security@mail.mil

References 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