Attachment 3 - AFRL SOW -PWS Supplemental Requirements.pdf

FA237726RB011

Attachment 3

Attachment No. _3___

Statement of Work (SOW)

AFRL Supplemental Requirements

14 September 2026

Contract No. FA237726RB011

1. INTRODUCTION. The following paragraphs are also considered to be a part of the SOW requirements and the Contractor is responsible for compliance to the same extent as the rest of the SOW.

2. PACKAGING AND MARKING.

a. All hardware deliverable contract items shall be packaged in accordance with established commercial practices.

b. When special delivery and/or handling instructions are required, all boxes and/or crates must contain the following statement in plain sight and in bold letters:

INSTRUCTION TO RECEIVING OFFICE – DO NOT OPEN; CONTENTS ARE SENSITIVE

TO DAMAGE WHEN IMPROPERLY OPENED OR HANDLED. CONTACT THE

RESPONSIBLE TECHNICAL PROJECT OFFICER IMMEDIATELY UPON RECEIPT.

CONTACT INFORMATION:

Robert Desonia Phone: (312) 986-8426 E-mail: robert.desonia.1@us.af.mil

3. COMMUNICATIONS SECURITY (COMSEC) MONITORING

All communications with DoW organizations are subject to Communications Security (COMSEC) review. Contractor personnel will be aware that telecommunications networks are continually subject to interception by unfriendly intelligence organizations. The DoW has authorized the military departments to conduct COMSEC monitoring and recording of telephone calls originating from or terminating at DoW organizations. Therefore civilian Contractor personnel are advised that any time they place a call to or receive a call from a USAF organization they are subject to COMSEC procedures. The Contractor will assume the responsibility for ensuring wide and frequent dissemination of the above information to all employees dealing with official DoW information.

4. ACKNOWLEDGMENT OF SPONSORSHIP

(a) The Contractor agrees that in the release of information relating to this contract such release shall include a statement to the effect that the project or effort depicted was or is sponsored by the Air Force Research Laboratory (AFRL).

(b) For the purpose of the clause at DFARS 252.235-7010, "information" includes but is not limited to material presented in news releases articles manuscripts brochures advertisements still and motion pictures speeches presentations meetings conferences symposia etc.

(c) Nothing in the foregoing shall affect compliance with the requirements of the clause (if applicable) of this contract entitled "Security Requirements".

(d) The Contractor further agrees to include this requirement in any subcontracts awarded as a result of this contract.

5. GUARANTEED FINAL REPORT

If this contract is terminated prior to completion, the Contractor agrees to provide a final report in accordance with Exhibit A, DI-MISC-80711A, Scientific and Technical Reports. During the life of the contract, the Contractor shall continuously reserve sufficient funds from the amount allotted to guarantee the preparation and delivery of said final report.

6. CONTRACTOR SYSTEMS DECLARATION AND TRACKING

Compliance with Air Force Manual (AFMAN) 17-1301 is mandatory. Air Force policy requires that all contractor-owned or operated information systems equipment on-site be tracked for purposes of operational awareness and to locate system owners in the event that such a device is recovered by AFRL/RIOS or another entity. Whenever contractor personnel will be on-site at AFRL/WPAFB and a contractor-owned or operated system (e.g.; laptop) will be brought into any of the facilities, the Contractor Systems Declaration Template at https://usaf.dps.mil/sites/20708/rios/cybersecurity/requests/sitepages/Home.aspx#contractorsystem must be completed. In the event Contractor personnel have not been issued a Common Access Card (CAC), and therefore cannot complete the template, the Contractor shall provide the required information to the COR/COTR for input into the template.

7. IMPLEMENTATION OF PATENT RIGHTS CLAUSE

(a) Interim* and final Invention Reports shall be submitted as follows:

(1) Invention Reports stating that there are no subject inventions to disclose (i.e., “negative reports”) shall be sent to the Administrative Contracting Officer (ACO) at the address located on the face of the contract, the Contracting Officer’s Technical Representative (COTR), and the cognizant AFRL/RFLW Branch Office inbox at robert.desonia.1@us.af.mil within the timeframes specified in the Patent Rights clause of this contract.

(2) Invention Reports that do list subject invention(s) (i.e., “positive reports”) and stating that all subject inventions have been disclosed, shall be sent to the Administrative Contracting Officer (ACO) at the address located on the face of the contract, the Patent Administrator at email:

afmlco.jaz@us.af.mil., the COTR, and the cognizant Branch Office inbox specified in paragraph (a)(1) above, within the timeframes specified in the Patent Rights clause of this contract.

(3) Please include in the subject line of the e-mail the contract number followed by the words "Invention Reporting." Also include in the body of the e-mail the names of the COTR and his/her office symbol. Contractors are highly encouraged to use DD Form 882, Report of Invention and Subcontracts to submit these reports. The DD Form 882 may also be used for the notification of an award of any subcontract(s) for experimental, developmental or research work which contain a "Patent Rights" clause.

(b) All other notifications (e.g., disclosure of each subject invention to the Contracting Officer within 2 months after the inventor discloses it) shall also be sent to the e-mail addresses in paragraph (a).

(c) This requirement also constitutes the request for the following information for any subject invention for which the contractor has retained ownership: (1) the filing date, (2) serial number and title, (3) a copy of the patent application, (4) patent number and issue date, and (5) a confirmatory instrument securing the Governments rights. Submittal shall be to the Patent Administrator e-mail address listed above, with a courtesy copy (cc:) to the COTR.

https://usaf.dps.mil/sites/20708/rios/wing_cyber_office/request_portal/sitepages/Home.aspx#contractorsystem

*DFARS 252.227-7038 states interim reports are due every twelve (12) months or such longer period as specified by the Contracting Officer. As such, if there are no interim subject inventions to disclose, interim reporting is not required and only a final report is required for submittal. If, at any time during contract performance, the status of subject inventions changes, the Contractor shall submit an interim Invention Report in accordance with paragraph (a).

8. OMBUDSMAN

An ombudsman has been appointed to hear and facilitate the resolution of concerns from offerors, potential offerors, and others for this acquisition. When requested, the ombudsman will maintain strict confidentiality as to the source of the concern. The existence of the ombudsman does not affect the authority of the program manager, contracting officer, or source selection official. Further, the ombudsman does not participate in the evaluation of proposals, the source selection process, or the adjudication of protests or formal contract disputes. The ombudsman may refer the interested party to another official who can resolve the concern.

Before consulting with an ombudsman, interested parties must first address their concerns, issues, disagreements, and/or recommendations to the contracting officer for resolution. Consulting an ombudsman does not alter or postpone the timelines for any other processes (e.g., agency level bid protests, GAO bid protests, requests for debriefings, employee-employer actions, contests of OMB Circular A-76 competition performance decisions).

If resolution cannot be made by the contracting officer, the interested party may contact the ombudsman:

Ombudsman: AFRL/PK Technical Director Alternate Ombudsman: AFRL/PK Deputy Director 1864 4th Street

WPAFB OH 45433

Phone: (937) 904-9700

FAX: (937) 656-7321

Email: Afrl.pk.workflow@us.af.mil

Concerns, issues, disagreements, and recommendations that cannot be resolved at the Center/MAJCOM/FLDCOM/DRU ombudsman level, may be brought by the interested party for further consideration to the Department of the Air Force ombudsman, Associate Deputy Assistant Secretary (ADAS) (Contracting), SAF/AQC, 1060 Air Force Pentagon, Washington DC 20330-1060, phone number (571) 256-2395, facsimile number (571) 256-2431.

The ombudsman has no authority to render a decision that binds the agency.

Do not contact the ombudsman to request copies of the solicitation, verify offer due date, or clarify technical requirements. Such inquiries shall be directed to the contracting officer.

9. ELIMINATION OF USE OF CLASS I OZONE DEPLETING SUBSTANCES (ODS)

(a) Contractors shall not:

1. Provide any service or product with any specification, standard, drawing, or other document that requires the use of a Class I ODS in the test, operation, or maintenance of any system, subsystem, item, component, or process; or

a. Provide any specification, standard, drawing, or other document that establishes a test, operation, or maintenance requirement that can only be met by use of a Class I ODS as part of this contract/order.

mailto:Afrl.pk.workflow@us.af.mil

2. For the purposes of Department of the Air Force policy, the following products that are pure (i.e., they meet the relevant product specification identified in AFI 32-7086[AR2] ) are Class I ODSs:

a. Halons: 1011, 1202, 1211, 1301, and 2402;

3. Chlorofluorocarbons (CFCs): CFC-11, CFC-12, CFC-13, CFC-111, CFC-112, CFC-113, CFC-114, CFC-115, CFC-211, CFC-212, CFC-213, CFC-214, CFC-215, CFC-216, and CFC- 217, and the blends R-500, R-501, R-502, and R-503; and

a. Carbon Tetrachloride, Methyl Chloroform, and Methyl Bromide.

10. INSURANCE CLAUSE IMPLEMENTATION

The Contractor shall obtain and maintain the minimum kinds and amounts of insurance during performance of this contract as specified by FAR 28.307-2, Liability, and contemplated by FAR 52.228-5, Insurance--Work on a Government Installation, and/or 52.228-7, Insurance--Liability to Third Persons.

11. INFORMATION REGARDING NON-US CITIZENS ASSIGNED TO THIS PROJECT

(a) Contractor employees requiring access to USAF bases, AFRL facilities, and/or access to U.S.

Government Information Technology (IT) networks in connection with the work on this contract must be U.S. citizens. For the purpose of base and network access, possession of a permanent resident card (“Green Card”) does not equate to U.S. citizenship. This requirement does not apply to foreign nationals approved by the U.S. Department of Defense or U.S. State Department under international personnel exchange agreements with foreign governments. It also does not apply to dual citizens who possess US citizenship, to include Naturalized citizens. Any waivers to this requirement must be granted in writing by the Contracting Officer prior to providing access.

Specific format for waiver request will be provided upon request to the Contracting Officer. The above requirements are in addition to any other contract requirements related to obtaining a Common Access Card (CAC).

(b) In compliance with the REAL ID Act of 2005 and DoDM 5200.08V3_DAFMAN 31- 101V3_DAFGM 2024-01, Installation Perimeter Access Control, effective 7 May 2025, all entrants to a Department of Air Force installation will be required to present REAL ID-compliant identification

(c) For purposes of paragraph (a) above, if an IT network/system does not require AFRL to endorse a contractor’s application to said network/system in order to gain access, the organization operating the IT network/system is responsible for controlling access to its system.

If an IT network/system requires an U.S. Government sponsor to endorse the application in order for access to the IT network/system; AFRL will only endorse the following types of applications;

consistent with the requirements above:

(1) Contractor employees who are U.S. citizens performing work under this contract.

(2) Contractor employees who are non-U.S. citizens and who have been granted a waiver.

Any additional access restrictions established by the IT network/system owner apply.

12. NOTIFICATION OF GOVERNMENT SECURITY ACTIVITIES

This contract contains a DD Form 254, DOW Contract Security Classification Specification, and requires performance at a government location in the U.S. or overseas. Prior to beginning http://static.e-publishing.af.mil/production/1/af_a4/publication/afi32-7086/afi32-7086.pdf https://usaf.dps.mil/sites/AFCC/AQCP/KnowledgeCenter/SitePages/DAF-Contracting-Compass/Part-23---Environment,-Sustainable-Acquisition,-and-Material-Safety.aspx?CID=dc7c8322-d1f4-42a2-9d82-62dcc05ddf79#_msocom_2 http://www.esd.whs.mil/Portals/54/Documents/DD/forms/dd/dd0254.pdf operations involving classified information on an installation identified on the DD Form 254, the contractor shall take the following actions:

(a) At least thirty days prior to beginning operations, notify the Information Protection Office shown in the distribution block of the DD Form 254 as to:

1. The name, address, and telephone number of this contract company’s representative and designated alternate in the U.S. or overseas area, as appropriate;

2. The contract number and military contracting command;

3. The highest classification category of defense information to which contractor employees will have access;

4. The Department of the Air Force installations in the U.S. (in overseas areas, identify only the APO number(s)) where the contract work will be performed;

5. The date contractor operations will begin on base in the U.S. or in the overseas area;

6. The estimated completion date of operations on base in the U.S. or in the overseas area;

and,

7. Any changes to information previously provided.

13. SECURITY INCIDENT REPORTING AND PROCEDURES

(a) The contractor shall follow the below guidance when a contract contains a DD Form 254, DOW Contract Security Classification Specification:

1. The contractor shall notify the Government Contracting Activity (GCA) of any security incident involving the potential or actual loss, compromise, or suspected compromise of Top Secret, Secret, and/or Confidential information, referred to as classified information, when the incident is discovered at the contractor’s location.

i. The contractor shall conduct the requisite inquiry(ies) in accordance with 32 CFR Part 117 and Cognizant Security Office (e.g., Defense Counterintelligence and Security Agency) guidance.

2. Security incidents occurring at government performance locations where the contractor is categorized as a visitor will be processed and reported in accordance with government host security procedures.

3. Security incidents involving the potential or actual loss, compromise, or suspected compromise of Special Access Program and/or Sensitive Compartmented Information is under the jurisdiction of the GCA and the contractor shall follow GCA guidance in lieu of this requirement.

4. This requirement does not relieve the contractor from reporting requirements set forth in 32 CFR Part 117, DFARS 252.204-7012, or as otherwise directed by contract requirements and/or its Cognizant Security Office (e.g., Defense Counterintelligence and Security Agency).

5. This requirement does not relieve the contractor from adhering to security incident guidance set forth by its Cognizant Security Office (e.g., Defense Counterintelligence and Security Agency).

6. The contractor is responsible for ensuring all applicable subcontracts include these security incident reporting requirements.

7. If the lost or compromised information is beyond the jurisdiction of the U.S. Government and cannot be recovered (e.g., media leak, public website posting, or loss in a foreign country), the notification and location of the compromise (e.g., geographic location of unrecoverable equipment) shall be classified commensurate with the classification level of the compromised material to prevent further unauthorized disclosure in accordance with DoDM5200.01 Volume 3, Enclosure 6. The contractor will contact the GCA for instructions on how to communicate the notification prior to submission in all cases where lost or compromised information is beyond the jurisdiction of the U.S. Government and cannot be recovered.

8. The contractor shall ensure all notifications determined to contain classified information are properly transmitted and marked in accordance with derivative classification and overarching marking guidelines in accordance with 32 CFR Part 117.

(b) Initial Notification of Security Incident

1. The contractor shall provide an initial notification of security incident to the GCA within 72 hours of discovery of any incident where classified information may have been subjected to loss, compromise, or suspected compromise for all security incidents involving the contractor’s location unless otherwise directed by contract requirements.

2. The initial notification to the GCA is considered Controlled Unclassified Information (CUI) [CUI category OPSEC, FEDCON Distribution/Dissemination Control] unless otherwise determined by the GCA, marked in accordance with DoDI5200.48, and shall be transmitted to the GCA through authorized means (e.g., encrypted email or DoD SAFE).

3. If the initial notification contains classified information either by content or through classification through compilation, the contractor will contact the GCA for submission guidance and ensure the notification is properly marked in accordance with derivative classification and overarching marking guidelines in accordance with 32 CFR Part 117.

4. The initial notification shall contain the following information, as available at the time of report:

i. Prime contract number associated with the security incident.

ii. Date of security incident occurrence.

iii. Date of security incident discovery if different from date of occurrence.

iv. Security Classification Guide (SCG) or guidance used to validate classification level of information involved (unclassified title/date); if SCG title is either classified or if listing SCG information will cause the notification to be classified by compilation, do not include and indicate as such in the initial notification.

v. Classification level of information involved (e.g., Top Secret, Secret, or Confidential)

vi. Brief description of incident prompting initial notification. If incident directly or indirectly involved government personnel, include government personnel name(s), email address(s), and office information.

vii. Communicate whether it is possible for the contractor to properly retain and/or provide the suspected information in question for GCA classification review and/or damage assessment.

(c) Final Notification of Security Incident

1. The contractor shall provide a final notification to the GCA 10 business days from date of initial notification. If the final notification cannot be made 10 business days from the date of the initial notification, the contractor shall request an extension and receive approval in writing from the GCA.

2. The final notification to the GCA does not relieve the contractor from reporting requirements set forth by 32 CFR Part 117, DFARS 252.204-7012, or as otherwise directed by contract requirements and/or its Cognizant Security Office (e.g., Defense Counterintelligence and Security Agency).

3. The final notification will be considered CUI [CUI category OPSEC, FEDCON Distribution/Dissemination Control] unless otherwise determined by the GCA, marked in accordance with DoDI5200.48, and sent through authorized means (e.g., encrypted email or DoD SAFE).

4. If the final notification contains classified information either by content or through classification through compilation, the contractor is required to contact the GCA for submission guidance and ensure the notification is properly marked in accordance with derivative classification and overarching marking guidelines in accordance with 32 CFR Part 117.

5. The final notification shall contain the following information:

i. Prime contract number associated with the security incident.

ii. Date of security incident occurrence.

iii. Date of security incident discovery if different from date of occurrence.

iv. Security Classification Guide (SCG) or guidance used to validate classification level of information involved (unclassified title/date); if SCG title is either classified or if listing SCG information will cause the report to be classified by compilation, do not include this information, and indicate as such in the final notification.

v. Classification level of information involved (e.g., Top Secret, Secret, or Confidential)

vi. Detailed description of incident and include the following:

Sequence of events: When, where, and how did the incident occur?

What persons, situations, and/or conditions caused or contributed to the incident?

If incident originated with government personnel, include government personnel name(s), email address(s), and office information.

Include the name(s), email address(s), and office information of all government personnel involved, either directly or indirectly, as appropriate

If classified information is alleged to have been physically lost (e.g., lost classified document), what steps were taken to locate the material?

If security incident was categorized as a data spill, include measures taken to properly sanitize all impacted assets.

vii. Corrective actions taken to prevent future occurrences

viii. Result of inquiry (e.g., loss, compromise, suspected compromise, or no compromise)

ix. A copy of the supporting DD Form 254(s) associated with prime contract. If DD Form 254 cannot be provided, the contractor shall indicate the reasons why in the final report.

(d) Definitions

“32 CFR Part 117” means National Industrial Security Program Operating Manual. “Business days” means days that do not include federal holidays or weekends.

“Classified information” means information the government designates as requiring protection against unauthorized disclosure in the interest of national security, pursuant to E.O. 13526, Classified National Security Information, or any predecessor order, and the Atomic Energy Act of 1954, as amended. Classified information includes national security information (NSI), restricted data (RD), and formerly restricted data (FRD), regardless of its physical form or characteristics (including tangible items other than documents).

“Cognizant security agencies (CSAs)” means agencies E.O. 12829, sec. 202, designates as having National Industrial Security Program implementation and security responsibilities for its own agencies (including component agencies) and any entities and non-CSA agencies under their cognizance. The CSAs are: Department of War (DoW); Department of Energy (DOE);

Nuclear Regulatory Commission (NRC); Office of the Director of National Intelligence (ODNI);

and Department of Homeland Security (DHS).

“Cognizant Security Office” means an organizational unit to which the head of a CSA delegates authority to administer industrial security services on behalf of the CSA.

“Compromise” means an unauthorized disclosure of classified information.

“Data spill” means electronic transmission of classified information via unsecure means such as classified information transmitted over an unclassified network.

“DD Form 254” means the Department of Defense Contract Security Classification Specification.

“Derivative classification” means incorporating, paraphrasing, restating, or generating in new form information that is already classified, and marking the newly developed material consistent with the classification markings that apply to the source information. Includes the classification of information based on classification guidance. The duplication or reproduction of existing classified information is not derivative classification.

“Final Notification of Security Incident” means contractor (or subcontractor) notification to the Government Contracting Activity communicating the results of the inquiry conducted.

“Government Contracting Activity” means an element of a Component designated and delegated by the Component head or designee with broad authority regarding acquisition functions to include the appropriate resources and personnel (e.g., contracting officers or their designees, program managers, program offices, and security personnel) as defined in DoDM 5220.32, Volume 1.

“Initial Notification of Security Incident” means the contractor’s (or subcontractor) notification to the Government Contracting Activity of a security incident occurrence and surrounding details of occurrence.

“Inquiry” means the initial fact-finding and analysis process to determine the facts of any security incident and conducted to determine whether or not there was a loss of classified information or whether or not unauthorized personnel had, or could have had, access to the information.

“Loss” means the inability to physically locate or account for classified information.

“Security classification guide” means a documentary form of classification guidance issued by an Original Classification Authority that identifies the elements of information regarding a specific subject that must be classified and establishes the level and duration of classification for each such element.

“Security Incident” means an incident that results from the mishandling of classified information.

“Suspected Compromise” means when a result of no loss or compromise of classified information cannot be determined with certainty.

14. VISIT REQUESTS

All requests for Government certification of Contractor employees' need-to-know and visit authorizations to other Government installations or Contractor facilities shall be forwarded for approval to the Government Program Manager, whose mailing address is:

ATTN: Robert Desonia Air Force Research Laboratory/AFRL/RFLW 2241 Avionics Circle, Wright Patterson AFB, OH 45433-7304

In compliance with the REAL ID Act of 2005 and DoDM 5200.08V3_DAFMAN 31-101V3_DAFGM 2024-01, Installation Perimeter Access Control, effective 7 May 2025, all entrants to a Department of Air Force installation will be required to present REAL ID-compliant identification.

15. BASE SUPPORT

Base support will be provided by the Government to the Contractor in accordance with this requirement. Failure by the Contractor to comply with this requirement shall release the Government, without prejudice, from its obligation to provide base support by the date(s) required. If warranted, and if the Contractor has complied with the requirements of this requirement, an equitable adjustment shall be made if the Government fails to provide base support by the date(s) required.

(a) The Contractor will require use of base support on a rent-free, non-interference basis, to include Government-controlled working space, material, equipment, services (including automatic data processing), or other support (excluding use of the Defense Switched Network (DSN)) which the Government determines can be made available at, or through, any Air Force installation where this contract shall be performed.

(b) Unless otherwise stipulated in the contract schedule, the Contractor will use base support on a no-charge-for-use basis and the value shall be a part of the Government's contract consideration.

(c) The Contractor shall immediately report (with a copy to the cognizant CAO) inadequacies, defective base support, or nonavailability of support stipulated in this SOW requirement, together with a recommended plan for obtaining the required support. Facilities shall not be purchased under this contract by the Contractor. Additionally, the Contractor (or authorized representative) shall not purchase, or otherwise furnish any base support requirement provided by this SOW (or authorize others to do so), without prior written approval of the Contracting Officer regarding the price, terms, and conditions of the proposed purchase, or approval of other arrangements.

(d) In compliance with the REAL ID Act of 2005 and DoDM 5200.08V3_DAFMAN 31- 101V3_DAFGM 2024-01, Installation Perimeter Access Control, effective 7 May 2025, all entrants to a Department of Air Force installation will be required to present REAL ID-compliant identification.

(e) Following are installations where base support will be provided:

AFRL/RFLW: 2241 Avionic Circles, WPAFB, OH 45433-7304

(f) The base support to be furnished under this contract is as follows:

(i) Office space for thirty-five (35) personnel.

(ii) Use of computers, hardware, software, databases, documentation, and other related material necessary to accomplish the contract requirements.

(iii) Parking for personal vehicles. Access will be provided for the duration of the contract during normal work hours (0800-1700), Monday through Friday, excluding Federal holidays (New Year's Day, Dr. Martin Luther King, Jr. Day, President's Day, Memorial Day, Juneteenth, Independence Day, Labor Day, Columbus Day, Veteran's Day, Thanksgiving, Christmas). Other times and days are available only upon coordination and approval by the cognizant Program Manager, (insert name and contact information).

Contractor personnel working within the facility are required to have Common Access Cards (CAC).

(iv) Compliance with Air Force Instruction (AFI) 33-119 and AFI 33-200 is mandatory. It should be noted that such access requires, at a minimum, a National Agency Check or Entrance National Agency Check in accordance with DoD 5200.2-R, Personal Security Program. Contractors should make themselves familiar with local procedures for processing such requirements, and be prepared to be in compliance on the first day of contract performance. Failure to comply with this requirement may be considered a failure to perform.

(g) Because of the nature and location(s) of the work performed, the value of such support is undeterminable. The Contractor shall not incur any cost resulting from nonsupport prior to Contracting Officer direction.

(h) In the performance of this contract or any major subcontract, no direct or indirect costs for support will be incurred if the Government determines that support is available at, or through any Air Force installation where this contract shall be performed.

16. IMPLEMENTATION OF POLLUTION PREVENTION AND RIGHT-TO-KNOW INFORMATION

To comply with FAR 52.223-5, Pollution Prevention and Right-to-Know Information, and Environmental Management System (EMS) requirements, the Contractor is required to complete EMS Awareness Training for all personnel working on an Air Force installation.

a. The installation office responsible for providing the EMS training is 88 CEG/CEIE:

Environmental Branch, Home - Environmental Branch (CEIE)

b. The training consists of reviewing the 88 CEG/CEIE Policy Memo and the EMS Awareness Training located at: EMS Documents - All Documents. If unable to access the training, contact Jason.baldwin.17@us.af.mil.

c. The training shall be accomplished within 30 days of contract (or modification) award. New contract employees shall be trained within 30 days of starting work on the installation.

d. Upon completion of the training, the contractor members shall sign and date the signature page of the training; and then provide the AF Program Manager (PM) and the EMS Coordinator (identified in the training) a copy of the signature page.

17. HEALTH AND SAFETY ON GOVERNMENT INSTALLATIONS

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

https://usaf.dps.mil/teams/21020/WPAFB/CEI/CEIE/default.aspx https://usaf.dps.mil/teams/21020/WPAFB/CEI/CEIE/EMS%20Documents/Forms/AllItems.aspx mailto:Jason.baldwin.17@us.af.mil

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

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

2. The contracting officer may, by written order, direct Department of the Air Force Occupational Safety and Health (AFOSH) Standards and/or 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.

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.

18. CONTRACTOR ACCESS TO DEPARTMENT OF THE AIR FORCE INSTALLATIONS.

The contractor shall obtain base or installation identification and vehicle passes, if required, for all contractor personnel who make frequent visits to or perform work on the Department of the Air Force installation(s) cited in the contract. Contractor personnel are required to wear or prominently display installation identification badges or contractor-furnished, contractor identification badges while visiting or performing work on the installation. Contractor personnel shall identify themselves as Contractors during meetings, telephone conversations, in electronic messages, or correspondence related to this contract.

The contractor shall submit a written request on company letterhead to the contracting officer listing the following: contract number, location of work site, start and stop dates, and names of employees and subcontractor employees needing access to the base or installation. The letter will also specify the individual(s) authorized to sign for a request for base or installation identification credentials or vehicle passes. The contracting officer will endorse the request and forward it to the issuing base pass and registration office or Security Forces/Police for processing.

When reporting to the registration/security police office, the authorized contractor individual(s) should provide a valid driver’s license, current vehicle registration, valid vehicle insurance certificate to obtain a vehicle pass.

During performance of the contract, the contractor shall be responsible for obtaining required identification for newly assigned personnel and for prompt return of credentials and vehicle passes for any employee who no longer requires access to the work site.

When work under this contract requires unescorted entry to controlled or restricted areas, the contractor shall comply with [insert any additional requirements to comply with DAFI 31-101, Integrated Defense, and DODMAN5200.02_DAFMAN 16-1405 , Air Force Personnel Security Program] citing the appropriate paragraphs as applicable.

Upon completion or termination of the contract or expiration of the identification passes/badges, the prime contractor shall ensure that all base or installation identification passes issued to employees and subcontractor employees are returned to the issuing office.

The contractor shall provide an after-hours contact number or after-hours email in the Emergency Mass Notification System (EMNS) for each of their personnel, whose normal place of duty is on a DoW installation or within a DoW facility. The contractor shall comply with any additional requirements in DAFMAN 10-206 for emergency operational reporting. Foreign Nationals may participate and may remove themselves from the Emergency Mass Notification System at any time. To update information, personnel can access the globe icon on their system desktop screens and choose the “Access Self-Service” option.

Failure to comply with these requirements may result in withholding of final payment.

https://static.e-publishing.af.mil/production/1/af_a4/publication/dafi31-101/controlled_unclassified_information.pdf https://static.e-publishing.af.mil/production/1/af_a4/publication/dafi31-101/controlled_unclassified_information.pdf https://static.e-publishing.af.mil/production/1/saf_aa/publication/dodman5200.02_dafman16-1405/dodm5200.02_afman16-1405.pdf https://static.e-publishing.af.mil/production/1/saf_aa/publication/dodman5200.02_dafman16-1405/dodm5200.02_afman16-1405.pdf

19. COMMON ACCESS CARDS (CAC) FOR CONTRACTOR PERSONNEL.

For installation(s)/location(s) cited in the contract, contractors shall ensure Common Access Cards (CACs) are obtained by all contract or subcontract personnel who meet one or both of the following criteria:

o Require logical access to Department of Defense computer networks and systems in either:

the unclassified environment; or the classified environment where authorized by governing security directives.

o Perform work, which requires the use of a CAC for installation entry control or physical access to facilities and buildings.

Contractors and their personnel shall use the following procedures to obtain CACs:

o Contractors shall provide a listing of personnel who require a CAC to the contracting officer. The government will provide the contractor instruction on how to complete the Contractor Verification System (CVS) application and then notify the contractor when approved.

o Contractor personnel shall obtain a CAC from the nearest Real Time Automated Personnel Identification Documentation System (RAPIDS) Issuing Facility (typically the local Military Personnel Flight (MPF)).

While visiting or performing work on installation(s)/location(s), contractor personnel shall wear or prominently display the CAC as required by the governing local policy.

During the performance period of the contract, the contractor shall:

o Within 7 working days of any changes to the listing of the contract personnel authorized a CAC, provide an updated listing to the contracting officer who will provide the updated listing to the authorizing government official;

o Return CACs in accordance with local policy/directives within 7 working days of a change in status for contractor personnel who no longer require logical or physical access;

o Return CACs in accordance with local policy/directives within 7 working days following a CACs expiration date; and o Report lost or stolen CACs in accordance with local policy/directives.

Within 7 working days following completion/termination of the contract, the contractor shall return all CACs issued to their personnel to the issuing office or the location specified by local policy/directives.

Failure to comply with these requirements may result in withholding of final payment.

20. ASSOCIATE CONTRACTOR AGREEMENTS

(a) The Contractor shall enter into Associate Contractor Agreements (ACA) for any portion of the contract requiring joint participation in the accomplishment of the Government’s requirement. The agreements shall include the basis for sharing information, data, technical knowledge, expertise, and/or resources essential to the integration of the ADEPT program, which shall ensure the greatest degree of cooperation for the development of the program to meet the terms of the contract. Associate contractors are listed in paragraph (g) below.

(b) ACAs shall include the following general information:

(1) Identify the associate contractors and their relationships.

(2) Identify the program involved and the relevant Government contracts of the associate contractors.

(3) Describe the associate contractor interfaces by general subject matter.

(4) Specify the categories of information to be exchanged or support to be provided.

(5) Include the expiration date (or event) of the ACA.

(6) Identify potential conflicts between relevant Government contracts and the ACA; include agreements on protection of proprietary data and restrictions on employees.

(c) A copy of such agreement shall be provided to the Contracting Officer for review before execution of the document by the cooperating contractors.

(d) The Contractor is not relieved of any contract requirements or entitled to any adjustments to the contract terms because of a failure to resolve a disagreement with an associate contractor.

(e) Liability for the improper disclosure of any proprietary data contained in or referenced by any agreement shall rest with the parties to the agreement, and not the Government.

(f) All costs associated with the agreements are included in the negotiated cost of this contract.

Agreements may be amended as required by the Government during the performance of this contract.

(g) The following contractors are associate contractors with whom agreements are required:

Contractor Address Program / Contract

21. CONTRACTOR IDENTIFICATION

(a) Contractor personnel and their subcontractors must identify themselves as Contractors or subcontractors during meetings, telephone conversations, in electronic messages, or correspondence related to this contract.

(b) Contractor-occupied facilities (on AFMC or other Government installations) such as offices, separate rooms, or cubicles must be clearly identified with Contractor supplied signs, name plates, or other identification, showing that these are work areas for Contractor or subcontractor personnel.

22. TRAVEL

(a) The Contractor may be required to travel within the contiguous United States and overseas. The Contractor may be required to travel by Government-provided transportation.

Travel requirements will be reimbursed by separate voucher and must be approved in advance by the Contracting Officer and Program Manager. Travel requirements will be identified, proposed, and negotiated on an as required cost-reimbursement basis. Billable travel costs are air fare, ground transportation, and per diem costs - not labor hours. The Contractor shall be responsible for obtaining any passports or visas and making travel arrangements to and from any CONUS location.

(1) Per diem, air fare, and all other allowable travel costs shall be reimbursed in accordance with the Federal Acquisition Regulation. All travel within overseas areas shall be approved in advance by the Contracting Officer and Program Manager.

(2) The Government may provide travel to and from overseas work sites via Air Mobility Command (AMC) flights if available. AMC travel fees may be Contractor-paid and invoiced to the Government. The Government will be responsible for obtaining travel clearances and issuance of any required special orders.

(b) Use of AMC transportation shall be approved in advance by the Contracting Officer's Representative or the Contracting Officer. Orders authorizing AMC travel will specify the Contractor's Customer Identification Code (CIC). If the Contractor does not have CIC number the orders will state "special account handling: billing for AMC transportation will be forwarded to (insert Contractor's address)." Use of AMC transportation is subject to availability.

(c) The travel CLIN is intended to pay for travel occurring at the direction of the Government performed in conjunction with a specific trip authorized in a task order.

Travel by clerical support personnel shall be approved in advance by the Contracting Officer's Representative or Contracting Officer.

23. KEY POSITIONS AND MINIMUM QUALIFICATIONS

(a) Contractor personnel holding the position titles and having the qualifications listed below are considered essential to the work being performed under this contract:

Key Positions: Minimum Qualifications:

(list by job title) (list minimum qualifications in terms of education and/or experience)

(b) The Contractor shall notify the Contracting Officer before the departure of any individual in a key position and identify the proposed substitution. Any proposed personnel substitution that does not meet the minimum qualification requirements described above requires the prior written approval of the contracting officer.

24. ORGANIZATIONAL CONFLICT OF INTEREST

(a) The following restrictions and definitions apply to prevent conflicting roles which may bias the Contractor's judgment or objectivity, or to preclude the Contractor from obtaining an unfair competitive advantage in concurrent or future acquisitions.

(1) Descriptions or definitions:

"Contractor" means the business entity receiving the award of this contract, its parents, affiliates, divisions and subsidiaries.

"Development" means all efforts towards solution of broadly-defined problems. This may encompass research, evaluating technical feasibility, proof of design and test, or engineering of programs not yet approved for acquisition or operation.

"Proprietary Information" means all information designated as proprietary in accordance with law and regulation, and held in confidence or disclosed under restriction to prevent uncontrolled distribution. Examples include limited or restricted data, trade secrets, sensitive financial information, and computer software; and may appear in cost and pricing data or involve classified information.

"System" means the system that is the subject of this contract.

"System Life" means all phases of the system's development, production, or support.

"Systems Engineering" means preparing specifications, identifying and resolving interface problems, developing test requirements, evaluating test data, and supervising design.

"Technical Direction" means developing work statements, determining parameters, directing other Contractors' operations, or resolving technical controversies.

(2) Restrictions: The Contractor shall perform systems engineering and/or technical direction, but will not have overall contractual responsibility for the system's development, integration, assembly and checkout, or production. The parties recognize that the Contractor shall occupy a highly influential and responsible position in determining the system's basic concepts and supervising their execution by other Contractors. The Contractor's judgment and recommendations must be objective, impartial, and independent. To avoid the prospect of the Contractor's judgment or recommendations being influenced by its own products or capabilities, it is agreed that the Contractor is precluded for the life of the system from award of a DoW contract to supply the system or any of its major components, and from acting as a subcontractor or consultant to a DoW supplier for the system or any of its major components.

(b) The Contractor may gain access to proprietary information of other companies during contract performance. The Contractor agrees to enter into company-to-company agreements to: (1) protect another company's information from unauthorized use or disclosure for as long as it is considered proprietary by the other company; and, (2) to refrain from using the information for any purpose other than that for which it was furnished. For information purposes, the Contractor shall furnish copies of these agreements to the contracting officer. These agreements are not intended to protect information which is available to the Government or to the Contractor from other sources and furnished voluntarily without restriction.

(c) The Contractor agrees to accept and to complete all issued task orders, and not to contract with Government prime Contractors or first-tier subcontractors in such a way as to create an organizational conflict of interest.

(d) The above restrictions shall be included in all subcontracts, teaming arrangements, and other agreements calling for performance of work which is subject to the organizational conflict of interest restrictions identified in this clause, unless excused in writing by the contracting officer.

25. PROGRAM PROTECTION

(a) Contractor employees during the performance of this effort may be required to have access to Critical Technology Elements (CTE), Enabling technologies, Critical Program Information (CPI) or other potential sensitive information. Contractor employees will be required to protect this information from disclosure to unauthorized personnel and companies.

(b) Provide a security plan to comply with the requirements of protection for this sensitive information when requested by the Government COTR/COR.

(c) Notify the Government immediately within 24hrs of all security incidents involving loss, compromise, or suspected compromise of CTE/CPI IAW DoDM 5200.01-V3, Enclosure 6.

CTE/CPI involved in the incident shall be specifically identified in inquiry and investigation reports.

(d) Employees shall be required to accomplish an initial Standard Form 424, “Research and Related Senior/Key Person Profile (Expanded)”. Provide an initial report of personnel working on the contract at time of award. Provide an updated SF 424 on an annual basis and be required to provide an updated list anytime new personnel join. Electronic submission of SF 424 shall be emailed to the AFRL COTR and AFRL.RIOF@us.af.mil.

(e) In the event a security risk is identified and the government has determined the security risk exceeds the acceptable threshold, the contractor will be notified and informed of the termination/decline of award. Government will be only required to provide a general statement of the reasoning due to government OPSEC measures.

(f) If Controlled Unclassified Information (CUI) and associated Critical Information is involved in this effort, CUI shall be protected to prevent adversary collection and exploitation.

Comply with DoDI 5200.48 CUI.

(g) If requested by the Government COTR/COR, provide a security plan (or extract thereof) and any associated plans of action developed to satisfy the adequate security requirements of DFARS 252.204-7012, and in accordance with National Institute of Standards and Technology (NIST) Special Publication (SP) 800-171, “Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations” in effect at the time the solicitation is issued or as authorized by the contracting officer, to describe the contractor’s unclassified Information System(s)/network(s) where Covered Defense Information (CDI) is associated with the execution and performance of this contract and is processed, is stored, or transmitted.

(h) If applicable, ensure that all personnel involved in this effort take CUI training through MyLearning https://lms-jets.cce.af.mil/moodle/ (if they have CAC) or through CDSE at https://securityawareness.usalearning.gov/cui/index.html.

(i) Operations Security (OPSEC).