Combat Coder PWS DRAFT V2.docx

Performance Work Statement for

Air Force Distributed Common Ground System

Combat Coder Program

Prepared by

AFLCMC/C3IA

750 Third Street Robins Air Force Base, GA 31098

REVISION SUMMARY

Initial

Table of Contents

1.0 Description of Services

1.1 Objective(s)

This Performance Work Statement (PWS) describes the services required to provide a dedicated, contractor-operated software engineering team to design, engineer, test, integrate, deploy, and sustain software capabilities for the Distributed Common Ground System (DCGS) enterprise. The primary objective is the continuous delivery of secure, high-quality, and mission-effective software that rapidly responds to emerging DCGS enterprise intelligence, surveillance, and reconnaissance (ISR) requirements.

To achieve this, the contractor shall operate within a DevSecOps framework. The contractor will perform full software development life cycle (SDLC) support—spanning planning, analysis, design, testing, delivery, and sustainment—which includes the following key service areas:

· Agile Methodologies and Tracking: Strictly adhere to iterative Agile methodologies (e.g., Scrum, Kanban) for all development efforts. The contractor shall track all user stories and documentation in the government-provided JIRA instance. This includes full participation in standard Agile ceremonies (Sprint Planning, Daily Stand-ups, Sprint Reviews, and Retrospectives) to deliver tested and integrated software code increments at the end of each sprint.

· Software Design, Development, and Platforms: Design, develop, and test resilient software applications engineered to degrade gracefully in contested or low-bandwidth environments. Code shall be clean, efficient, maintainable, and written in accordance with secure coding practices (e.g., OWASP Top 10). All development shall occur on authorized government platforms, including but not limited to Maven Smart Systems, ArcGIS, Dagster, and Apache Airflow, utilizing open standards and Application Programming Interfaces (API) for DCGS interoperability.

· DevSecOps & Integrated Cybersecurity: Integrate security into all phases of the software lifecycle. Source code, configuration files, and deployment scripts shall be maintained in the government-provided GitLab repository using a "GitFlow" branching strategy. Code must undergo peer-reviewed Merge Requests (MRs) and pass automated pipeline checks, including processing through Government-approved security scanning applications to ensure zero (0) new critical or high vulnerabilities. Furthermore, the contractor shall enforce multiple testing levels (Unit, Integration, End-to-End) and maintain a minimum of 80% unit test coverage for all new code.

· 24/7 Software Sustainment and Incident Response: Provide rapid engineering support for the DCGS production environment. In accordance with government-defined incident response processes, the contractor shall respond to critical, mission-impacting operational bug reports within four (4) business hours of notification. The contractor must provide a technical mitigation plan, root cause analysis, or an emergency hotfix within 24 business hours to restore operational capability, and ensure documented rollback procedures are in place for every release.

1.2 Benefit to United States Air Force

This acquisition will benefit the United States Air Force (USAF) by enhancing the operational effectiveness and lethality of the DCGS weapon system. By integrating an agile software development team, the USAF can accelerate the delivery of critical ISR capabilities to the warfighter, improve data analysis and exploitation, and maintain a technological advantage over adversaries. This directly supports the USAF DCGS’s core mission of producing and disseminating actionable, near-real-time intelligence to warfighters, Joint Task Force (JTF) Commanders, and the larger intelligence community.

1.3 Background

The DCGS is the USAF's primary weapon system for processing, exploiting, and disseminating ISR data. To maintain its superiority and adapt to a rapidly changing global security environment, DCGS requires a continuous modernization effort. This PWS establishes a contract for an "organic" software development team that will be deeply integrated with government product owners and operational users, enabling a more responsive and effective development process to meet the needs of the modern battlespace.

2.0 Services Summary

Agile Software Development and Delivery

All code shall pass security scans with zero (0) new critical or high vulnerabilities. Unit test code coverage shall be maintained at or above 80% for all new code.

3.0 Government Property

3.1 Contractor Responsibility

The Contractor shall define all Government Furnished Property (GFP), Government Furnished Equipment (GFE), Government Furnished Material (GFM) and Services requirements necessary to execute the performance of the PWS requirements. The Contractor shall develop this list of requirements as part of the proposal effort. Revisions to this list shall be made by the Contractor throughout the period of performance of this contract. [CDRL A025, Government Furnished Material (GFM) by National Stock Number (NSN)]

3.2 Government Property to be Provided

Government property to be provided includes Government Furnished Equipment (GFE) such as development workstations, required peripherals, and access to classified networks (SIPRNet/JWICS). The Government will also provide Government Furnished Information (GFI), including access to the DCGS technical baseline, software development environments, testing platforms, and all necessary security documentation. [CDRL A01T, Status of Government Furnished Equipment (GFE) Report]

3.3 Base Support

The Government will furnish property incidental to the place of performance including office space and equipment, i.e., computer equipment, software, phone/phone line, and reproduction equipment.

3.4 Reporting of Government Property

The Contractor shall have a system of internal controls to manage (control, use, preserve, protect, repair, and maintain) Government property in its possession in accordance with Federal Acquisition Regulation (FAR) 52.245-1, and its property management system shall be adequate to satisfy the requirements of this clause. The contractor shall record receipt and return of all Government Furnished Property (GFP), as well as the reporting of shipment, consumption, disposal, or transfer to another contract, in the GFP Module in Procurement Integrated Enterprise Environment (PIEE), https://piee.eb.mil, as stipulated by Defense Federal Acquisition Regulation Supplement (DFARS) 252.245-7005. This reporting requirement does not change any liability provisions or other reporting requirements that may exist under the contract. GFP training and guidance is located at the DoD Procurement Toolbox at https://dodprocurementtoolbox.com/.

3.5 Loss of Government Property

3.5.1 Definition of Loss of Government Property

“Loss of Government property” means unintended loss of or damage to Government property including property that cannot be found after a reasonable search, loss due to inadequate storage, loss due to lack of security, theft, damage requiring repair to restore the item to usable condition, or damage that renders the property useless for its intended purpose or Beyond Economical Repair (BER). Loss of Government property does not include manufacturing defects, obsolescence, normal wear and tear, or purposeful destructive testing. Unless otherwise stated in the contract/order, loss of Government property does not include normal and reasonable inventory adjustments, i.e., losses of low priority consumable material, such as common hardware, as agreed to by the Contractor and the Government Property Administrator.

3.5.2 Reporting Loss of Government Property

The Contractor shall report loss of Government property in the GFP Module located in PIEE, https://piee.eb.mil/piee-landing/. [A024, Government Property (GP) Inventory Report]

3.6 Return or Retention of Government Property

All property provided by the Government remains the property of the Government and shall be returned to the Government as directed, but no later than completion of the contract/order, unless the Procuring Contracting Officer (PCO) directs the Contractor to retain the property for continued use under a successor contract. All Government property shall be returned to the Government in the condition provided unless approved in advance by the PCO. All material generated under the contract/order becomes the property of the Government and shall be returned to the Government as directed, but no later than completion of the contract/order, unless the PCO directs the Contractor to retain the material for continued use under a successor contract.

4.0 Technical Requirements

4.1 Period and Place of Performance

4.1.1 Contract/Order Period of Performance

The period of performance for the contract/order will extend 12-month base period with four (4) 12-month option periods.

4.1.2 Place of Performance

These services will be performed at Government facilities located primarily at Langley Air Force Base (AFB), VA; McConnell AFB, MO; and Beale AFB, CA. Temporary Duty Travel may be needed to support at Hickam AFB, HI; Ramstein AB, GER; and Osan AB, ROK.

4.2 Contract Data Requirements List(s) (CDRL)

ITEM

Base Year

DI-MGMT-81453B/T

DI-ADMN-81250C/T

DI-ADMN-81373/T

DI-MGMT-81468A/T

DI-MGMT-81928/T

DI-MGMT-81861C/T

DI-IPSC-81442A/T

DI-MGMT-81797/T

DI-IPSC-81441A/T

DI-PSSS-81535A/T

DI-SESS-80858D/T

DI-FNCL-80331A/T

DI-MGMT-81580/T

DI-ADMN-81249C/T

DI-MGMT-81928/T

DI-SESS-81022E

DI-MISC-80508B/T

DI-NDTI-81351T

DI-MGMT-81808/T

DI-MGMT-81809/T

DI-MGMT-81861C/T

DI-MGMT-80269/T

DI-MISC-81943/T

DI-MGMT-80441D

DI-PSSS-80727A

DI-SESS-81704

4.2.1 Quality of CDRL Deliverable

There shall be no more than one rejection of any deliverable. There shall be no more than one (1) rejection of the same category of deliverable per 12-month period of performance (PoP). The USAF DCGS Program Management Office (PMO) will reject a deliverable if one (1) or more technical error per 20 pages or one (1) per report for reports fewer than 20 pages. A technical error is defined as the format not being in accordance with the data requirements list or the content not being accurate and complete in accordance with the data requirements list, PWS, or contract/order. A minor error is exemplified by a typographical error, a grammatical error, etc. Contractor shall correct and resubmit the rejected deliverable(s) within five (5) business days of notification of Government rejection. Business days are defined as 0700 - 1700 Eastern Standard Time (EST), Monday through Friday, excluding Federal holidays.

4.2.2 Receipt of CDRL Deliverable

CDRL deliverables shall be submitted via Wide Area WorkFlow (WAWF) and submitted directly to the MFT member identified on the CDRL. There shall be no more than 1 late submission(s) of deliverables per quarter. The Contractor shall notify the Government if the delivery of any data/document will not meet the scheduled delivery date and negotiate a revised delivery date. The data/document shall be delivered by the revised delivery date acceptable to the Government.

4.3 Program Management and Administrative Support

The Contractor shall establish and maintain a program management office in support of all tasks related to the contract and its task orders. The Contractor shall also provide a point of contact for the Government. The Contractor shall assign a program manager (PM) to plan, organize staff, administer, and control all contract activities, and to ensure cost, schedule and objectives are achieved. The Contractor shall establish budgets and schedules to meet overall program objectives. Periodic status updates shall be conducted to monitor cost and schedule performance. Contractor’s Progress Status and Management Report, Cost Funds Status Reports, Funds & Man Hours Expenditure Report, and Integrated Program Management Report will be submitted to the Government for each task order as required by the applicable CDRL. The Contractor shall attend/support management meetings as deemed necessary by the Government program office. The Contractor shall assign a program manager to each task order. The Contractor may assign PMs to one or more programs as required to meet task order requirements. Program Managers shall be available during normal business hours and be available during a regular 40 hour work week. The Contractor shall provide technical/programmatic liaison support to DCGS Program Execution. Expected support includes, but is not limited to, tasks such as facilitator, coordination of activities, investigation and analysis, problem resolution, engineering interface, programmatic support, documentation preparation and ad hoc requests by the Government. The Contractor shall prepare Conference Minutes for Program Management Reviews. [CDRL A005, Contractor’s Progress Status and Management Report; CDRL A004, Cost Funds Status Reports; CDRL A014, Funds & Man Hours Expenditure Report; CDRL A00J, Program Management Plan; CDRL A01Q, Integrated Program Management Report; and CDRL A002, Conference Minutes]

4.3.1 Risk Management

The Contractor shall develop and maintain a Risk Management Plan to identify, assess, and mitigate risks related to cost, schedule, and performance. A monthly Risk Management Status Report shall be provided to document progress in risk management activities. [CDRL A01N, Risk Management Plan; CDRL A01P, Risk Management Status Report]

4.4 Engineering Services

The Contractor shall generate and deliver presentations for all design reviews, Program Management Reviews (PMR), and Technical Exchange Meetings. The Contractor shall review, update, and deliver these documents to the Government as required by individual Task Orders and applicable CDRL. [CDRL A003, Presentation Material; CDRL A00B, Software Version Description Document (SVDD); and CDRL A00M, Factory and/or Site Acceptance Test Report]

4.4.1 Software Development Life Cycle (SDLC) Activities

The Contractor shall provide all necessary personnel, supervision, and services to perform continuous software development within a Government-defined DevSecOps framework.

4.4.1.1 Agile Methodology

As Agile methodology emerges as a leading software development approach across the industry and federal government, this Performance Work Statement (PWS) directs programmatic practices primarily towards Agile efforts, though traditional Waterfall methodologies will still apply in specific situations as identified in individual task orders. For all efforts determined to be Agile, the contractor shall strictly adhere to the Agile requirements outlined in this document. The contractor shall perform all work using an iterative Agile methodology (such as Scrum or Kanban) producing working software and sufficient documentation with each iteration until a fully functional release is achieved. Furthermore, the Contractor team is required to participate in all standard Agile ceremonies, including but not limited to Sprint Planning, Daily Stand-ups, Sprint Reviews, and Retrospectives.

4.4.1.2 Software Design and Development

The Contractor shall design, develop, and test software applications and components. Code shall be clean, efficient, maintainable, and written in accordance with secure coding practices. All reporting, tracking, and documentation procedures must be followed and completed in a timely manner. [CDRL A00W, Software Product Specification (SPS) and CDRL A02H, Test Plan/Test Procedure]. Software design requirements include, but are not limited to:

· Development of automated connection scripts between data sources

· Development of new software functions, methods, object types, and classes to facilitate data connections required by the customer

· Development of newly requested features that have been approved by the Product Owner/ Scrum Master for the team

4.4.1.3 DevSecOps Integration

The Contractor shall employ DevSecOps practices to integrate security and reliability into all software engineering efforts. All Contractor-produced code shall be processed through Government approved applications including but not limited to ArcGIS and Maven Smart Systems. The Contractor shall ensure all engineered code passes scans with zero (0) new Critical or High vulnerabilities. Additionally, the Contractor shall ensure a minimum of 80% unit test coverage for all newly engineered code to guarantee system resilience within the DCGS operational environment. [CDRL A00L, Test Plans; CDRL A01M, Security Test Plan; CDRL A004, Security Risk Assessment; CDRL A00R, Security Plan; and CDRL A01M, Security Test Plan]

4.4.1.4 Software Sustainment

The Contractor shall provide rapid engineering support for critical, mission-impacting software defects within the live DCGS production environment. Due to the 24/7 operational nature of the DCGS weapon system, the Contractor shall respond to critical operational bug reports within four (4) business hours of notification. Furthermore, the Contractor shall provide a technical mitigation plan, root cause analysis, or emergency hotfix within 24 business hours to restore operational capability and minimize mission disruption. [CDRL A011, Deficiency Report (DR)]. Software sustainment requirements include, but are not limited to:

· Monitoring of implemented connection stability

· Providing sustainment and maintenance training to Airmen as needed to maintain non-interference based software solutions to avoid using Combat Coder resources

· Document and report critical operational bugs after resolution

· Evaluate testing procedures and DevSecOps practices to investigate causes of critical operational bugs

4.5 Personnel Qualifications:

The Contractor shall staff the modernization team exclusively with highly vetted, experienced, and certified professionals capable of operating within complex, classified DCGS architectures. The Contractor shall maintain 100% compliance with all minimum labor category qualifications specified in this PWS at all times. This includes, but is not limited to, required years of engineering experience, technical proficiencies, DoD 8570 cybersecurity certifications, and active Top Secret/SCI clearance requirements.

4.5.1 Lead Software Engineer

Shall have a minimum of 10 years of software development experience and a Bachelor's degree in a technical field. Must have experience leading agile teams and expertise in Python (other languages also preferred).

4.5.2 Senior Software Engineer

Shall have a minimum of 5 years of software development experience and expertise in languages relevant to the DCGS baseline.

4.5.3 Cybersecurity Engineer

Shall have a minimum of 5 years of experience with DoD cybersecurity practices (RMF, STIGs) and tools (e.g., Fortify, SonarQube).

4.5.4 General Requirement

All personnel must possess a DoD 8570 IAT Level II certification at a minimum (e.g., Security+).

4.6 Holidays and Facility Closings

Contractor/subcontractor personnel shall observe holidays and facility closings as authorized for government personnel. Contractor/subcontractor personnel shall only be permitted access to Government facilities when Government personnel are present.

4.7 Travel

Contractor shall travel to support the various efforts associated with this PWS as required by individual task order(s) and directed and approved by the AF DCGS PMO Program Manager (PM) and Procurement Contracting Officer (PCO). Travel shall be accomplished and reimbursed in accordance with FAR 31.205-46. For all planned travel, contractor shall notify the PCO and the DCGS PMO in writing at least five (5) business days before the travel date. In the case of an emergency, contractor is required to notify the PCO and PMs as soon as is practical upon determining the need for such travel. Travel will be reimbursed according to the rates outlined in the Federal Travel Regulations for travel within the CONUS; Joint Travel Regulations (JTR) for travel to Alaska, Hawaii and outlying areas of the United States. The applicable rates are those in effect at the time of travel and are subject to the limitations outlined in FAR Part 31.205-46. Airfare shall be limited to coach class seating while vehicle rentals shall be consistent with the most economic and reasonable rates available. In most circumstances, economy class vehicles will suffice. [CDRL A01X, Trip/Travel Report]

Travel costs incurred will be invoiced in the following manner:

• Lodging: actual and reasonable up to per diem

• Lodging taxes: separate charge, reimbursed

• M&IE: straight per diem; but 75% on the first and last day, no exceptions

5.0 General Information

5.1 Continuation of Mission-Essential Services During a Crisis

5.1.1 Designation of Services as Mission-Essential

The Functional Commander/Director has determined certain services under this contract/order are mission-essential and will continue in the event of a crisis. The designation of services as mission-essential will apply to an entire contract, but will apply only to services specifically identified as mission-essential by the government. The mission-essential services under this contract/order include all software development, integration, and sustainment activities required to maintain the operational availability and continued development of the DCGS software baseline.

5.1.2 Mission-Essential Contractor Services Plan

The Contractor shall submit a plan describing procedures for continuing performance of mission-essential services during a crisis. The Contractor shall identify provisions for ensuring required personnel and resources are available to support continuity of operations for up to 30 calendar days or until normal operations can be resumed. The Contractor shall submit any revision to the plan for approval prior to implementation. The Contractor shall activate the plan only if authorized by the PCO acting under the direction of the Commander/Director. [CDRL A01J, Technical Report – Study/Services]

If the Contractor anticipates not being able to perform the mission-essential services, they shall notify the PCO as soon as possible and fully cooperate with the Government’s efforts to maintain continuity of operations.

5.2 Security Requirements

5.2.1 Protection of Controlled Unclassified Information

Controlled Unclassified Information (CUI) is any information that law, regulation, or government wide policy requires to have safeguarding or disseminating controls, excluding information that is classified under Executive Order 13526, Classified National Security Information, December 29, 2009, or any predecessor or successor order, or the Atomic Energy Act of 1954, as amended.

The National Archives and Records Administration (NARA) CUI Registry (http://www.archives.gov/cui/registry/category-list.html) identifies approved CUI categories and subcategories, provides general descriptions for each, identifies the basis for controls, and sets out procedures for the use of CUI.travel

· Contractor shall comply with DoDI 5200.48, Controlled Unclassified Information (CUI), 6 March 2020, Air Force Instruction (AFI) 16-1404 Air Force Information Security Program, and Air Force Guidance Memorandum 2020-16-01, Air Force Guidance Memorandum for CUI, 23 July 2020. Contractor shall consult the applicable security classification guide to monitor CUI aggregation for potentially generating classified information by compilation.

· Contractor shall comply with DoDM 5400.07/Air Force Manual 33‑302, DoD Freedom of Information Act (FOIA) Program, 26 April 2018, requirements.

Protection of CUI and unclassified DoD information not approved for public release on non-DoD Information Systems shall be protected by contractor IAW DoDI 8582.01, Security of Non-DoD Information Systems Processing Unclassified Nonpublic DoD Information, 9 December 2019. Unless specific categories of CUI require more stringent controls, non-DoD Information Systems shall be protected using the guidelines set forth in NIST Special Publication 800-171 Rev. 3, Protecting Controlled Unclassified Information in Nonfederal Information Systems and/Organizations, May 2024.

5.2.2 Covered Defense Information

Contractor shall comply with DFARS 252.204-7012 Safeguard Covered Defense Information and Cyber Incident Reporting (Dec 2019) This applies to contracts and subcontracts requiring contractors and subcontractors to safeguard covered defense information that resides in or transits through covered contractor information systems by applying specified network security controls. It also requires reporting of cyber incidents. The subpart does not abrogate any existing contractor physical, personnel, or general administrative security operations governing the protection of unclassified DoD information, nor does it impact requirements of the National Industrial Security Program.

5.2.3 Security Regulations

Contractor shall comply with the provisions of the National Industrial Security Program Operating Manual (NISPOM) 32 Code of Federal Regulations (CFR) Part 117). Contractor shall ensure requirements for safeguarding classified information and classified materials, for obtaining and verifying personnel security clearances, for protecting Government property, and for the security of automated and non-automated information systems (AIS).

Contractor will maintain a security program in accordance with this PWS, Intelligence Community Directive (ICD) 503, the Joint DODIIS/Cryptologic SCI Information Systems Security Standards (JDCSISSS), the Contract Security Classification Specification (DD254), and any other applicable directives outlined in the individual task orders. In case any of these publications contain conflicting guidance as to the classification of information, the higher classification will take precedence. Contractor will abide by the following additional security regulations:

· DoDD 5205.02E, DoD Operations Security (OPSEC) Program, 20 June 2012, Incorporating Change 2, Effective 20 August 2020

· DoDM 5205.02, DoD Operations Security (OPSEC) Program Manual, 3 November 2008, Incorporating Change 2, Effective 29 October 2020

· AFI 10-701, Air Force Operations Security (OPSEC) 24 July 2019, Incorporating Change 1, Effective June 9, 2020

· DoDI 5200.02, DoD Personnel Security Program (PSP) 21 Mar 2014, Incorporating Change 3, Effective 24 Sept 2020

· DoDM 5200.02 Procedures for The DoD Personnel Security Program (PSP), 3 Apr 2017, Incorporating Change 1, Effective 29 Oct 2020

· DoDM 5200.02_DAFMAN16-1405, Dept of Air Force Personnel Security Program 1 Aug 18; Incorporating DAFGM2-26-01, 8 Jan 2026

· DoDI 5200.48, Controlled Unclassified Information (CUI), 6 Mar 2020

· DoDI 5200.48_Department of the Air Force Instruction (DAFI) 6-1403, Controlled Unclassified Information (CUI), 5 Oct 2021; Incorporating DAFGM2025-01, 4 Dec 2025

· NIST SP 800-171A, Protecting Controlled Unclassified Information in Non-federal Systems and/organizations CSR May 2024, REV 3, 25 June 2024, SP 800-171 Rev. 3

· DoDI 8510.01, Risk Management Framework for DoD Systems, 19 Jul 2022

· DoDI 8582.01, Security of Non-DoD Information Systems Processing Unclassified Nonpublic DoD Information, 9 December 2019

· DoDM 5200.01-V1, DoD Information Security Program: Overview, Classification, and Declassification, 24 Feb 2012, Incorporating Change 3, Effective 17 Jan 25

· DoDM 5200.01V1_DAFMAN16-1404V1, DoD Information Security Program: Overview, Classification and Declassification, 6 Apr 2022; Incorporating DAFGM2025-01, 28 Aug 2025

· DoDM 5200.01-V2, DoD Information Security Program: Marking of Information, 24 Feb 2012, Incorporating Change 4, Effective 28 Jul 2020

· DoDM 5200.01V2_DAFMAN16-1404V2, Department of Air Force Information Security Program: Marking of Information 7 Jan 2021, Certified Current, 17 Jun 2025

· DoDM 5200.01-V3, DoD Information Security Program: Protection of Classified Information 24 Feb 2012, Incorporating Change 4, Effective 17 Jan 2025

· DoDM 5200.01V3_DAFMAN 16-1404V3, Information Security Program: Protection of Classified Information, 12 Apr 2022

· DoDM 5400.07, DoD Freedom of Information Act (FOIA) Program, 25 Jan 2017

· DODM 5400.07_AFMAN 33-302, Freedom of Information Act Program 27 Apr 2018

· AFMAN 14-403, Sensitive Compartmented Information Security and Intelligence, Surveillance, and Reconnaissance Systems Cybersecurity and Governance, 3 Sept 2019.

As the Department of Defense (DoD) makes the transition from DCID 6/3, ICD 503, and JDCSISSS to the Committee on National Security Systems Instruction (CNSSI) 1253 and the National Institute of Standards and Technology (NIST) 800-53 control standards, contractor shall abide by all required security standards. These security requirements are defined and directed by the Air Force Intelligence, Surveillance, and Reconnaissance Agency (AFISRA) Director of Information Assurance (DIA).

5.2.4 Operations Security (OPSEC)

The purpose of OPSEC is to reduce the vulnerability of USAF missions to adversary collection and exploitation of critical information. DoDD 5205.02E and DoD Manual 5205.02-M require contractors supporting DoD activities use OPSEC to protect critical information for specified contracts, subcontracts, and information used in the performance of duties in support of Air Force requirements/missions. The Contractor shall ensure Contractor personnel who perform work on (or in) a Government facility comply with the OPSEC procedures and training requirements of the facility as specified in AFI 10-701.

5.2.5 Communications Security (COMSEC)

The Contractor shall use only secure communications methods and/or equipment to transmit or otherwise transfer classified information and/or Controlled Unclassified Information (CUI) in accordance with 32 CFR Part 117, National Industrial Security Program Operating Manual (NISPOM), § 117.7(a). Applicable equipment shall be safeguarded, maintained and operated in accordance with 32 CFR Part 117, National Industrial Security Program Operating Manual (NISPOM), § 117.7(a).

5.2.6 Security Clearance

The Contractor shall ensure applicable contractor/subcontractor personnel have security clearance(s) at the Top Secret/Sensitive Compartmented Information (TS/SCI) level for proper accomplishment of contract/order requirements. The security clearance(s) shall be obtained in accordance with the Department of Defense (DD) Form 254, Department of Defense Contract Security Classification Specification.

5.2.7 Security Incident or Violation

The Contractor shall immediately notify the 480th ISR Wing security office of any potential or actual security incident or violation.

5.2.8 Access to Government System(s)

The Government will provide contractor/subcontractor personnel access to system(s) necessary to perform tasks under the contract/order. The Contractor shall ensure contractor/subcontractor personnel who require access to an unclassified or classified Government Automated Information System (AIS) have the respective background check or security investigation conducted. At a minimum, the Contractor shall ensure contractor/subcontractor personnel who require access to an unclassified AIS have a National Agency Check with Inquiries (NACI) conducted. Upon completion/termination of the contract/order or transfer/termination of contractor/subcontractor personnel, the Contractor shall ensure the system account(s) are closed.

5.2.9 Access to Government Facility or Military Installation

The Contractor shall ensure contractor/subcontractor personnel who require access to a Government facility or military installation comply with the security requirements of the facility or installation.

5.2.10 Common Access Card (CAC)

The Contractor shall ensure a CAC is obtained by all contractor/subcontractor personnel who require access to DoD computer networks/systems, for DoD facility entry control and/or for physical access to facilities and buildings to perform tasks under the contract/order. The Contractor shall provide a list of contractor/subcontractor personnel who require a CAC to the PCO. The Government will provide the Contractor instruction on how to utilize Mission Partner Identity, Credential and Access Management (MP-ICAM) and notify the Contractor of approval/disapproval of contractor/subcontractor personnel application. Contractor/subcontractor personnel shall obtain the CAC from the local Real Time Automated Personnel Identification Documentation System (RAPIDS) issuing facility.

The Contractor shall immediately report a lost or stolen CAC as directed by local Government policy. The Contractor shall notify the PCO of any change to the list of contractor/subcontractor personnel who require a CAC and provide an updated list within five business days. The Contractor shall return a CAC within five business days once contractor/subcontractor personnel no longer require computer network/system access and/or facility access. The Contractor shall return an expired CAC within five business days after the expiration date. The Contractor shall return any and all CACs within five business days after completion/termination of the contract as directed by local Government policy.

5.3 Environmental Management System (EMS)

Contractor/Subcontractor personnel who perform work on any Government facility shall comply with the EMS requirements established by the facility. Contractor/Subcontractor personnel may be required to complete EMS training prior to beginning work.

5.4 Agency Affirmative Procurement Programs

This acquisition does not require the purchase of Environmental Protection Agency (EPA)-designated products or United States Department of Agriculture (USDA)-designated products; therefore, the requirement does not apply.

5.5 Safety Requirements

5.5.1 Contractor Environmental, Safety, and Occupational Health Compliance

The Contractor shall comply with Government Safety and Health regulations including, but not limited to, Public Law 91-596, Occupational Safety and Health Act (OSHA), and DoD Directive 4715.1E, Environmental, Safety, and Occupational Health (ESOH). The Contractor shall require all subcontractors to comply with required safety, health and fire standards.

5.5.2 Mishap Notification/Investigation

In accordance with DAFI91-204, Safety Investigations and Reports, the Contractor shall report mishaps including damage to DoD property; occupational illness to DoD military or civilian personnel; injury to on- or off-duty DoD military personnel; injury to on-duty DoD civilian personnel; and damage to public or private property or injury or illness to non-DoD personnel caused by Government operations. In the event of a mishap, the Contractor shall ensure the USAF is notified of the mishap. The Contractor shall contact the organizations listed below within four business hours. The Contractor shall immediately secure the mishap scene (and damaged property) and impound pertinent maintenance and training records until released by the Government’s Safety Office (AFLCMC/SE). Such release shall be accomplished through the Contracting Officer. The Contractor shall cooperate and assist Government personnel in the investigation of the mishap and submit an Accident/Incident Report within 24 hours of the mishap. There shall be no more than one (1) instance of late mishap notification per contract year. [CDRL A016, Accident/Incident Report; CDRL A017, Safety and Health Plan; CDRL A01E, Contractor’s Progress Status and Management Report]. The Contractor shall ensure the following are notified:

a. PCO

b. MFT (Contracting Officer’s Representative (COR), if available, or another MFT member),

c. The closest USAF base command post (to relay notification to AFLCMC/SE).

The following information shall be provided in support of the Mishap notification as soon as it becomes available:

a. Contract, contract number, name and title of person(s) reporting

b. Date, time and exact location of accident/incident

c. Brief narrative of accident/incident (events leading to accident/incident)

d. Cause of accident/incident, if known

e. Estimated cost of accident/incident (material and labor to repair/replace)

f. Nomenclature of equipment and personnel involved in accident/incident

g. Corrective actions (taken or proposed)

h. Other pertinent information

5.5.3 Voluntary Protection Program (VPP)

Contractor personnel performing work on a USAF installation shall participate in the local VPP. Information on the VPP can be accessed at http://www.osha.gov/dcsp/vpp/index.html.

5.5.4 Department of Labor (DoL) Inspection of Contractor Operations

The Contractor is subject to DoL inspections and enforcement by OSHA health and safety officials while performing work on a Government installation. OSHA health and safety officials may access workplaces on Government installations at any time, scheduled or unscheduled, during regular work hours. OSHA health and safety officials must meet security requirements to enter restricted or classified areas. The Contractor shall immediately notify the COR and the contracting unit’s Safety Office upon notification of a visit.

5.6 Inspection of Services

In accordance with the Inspection of Supply/Services clause(s) identified in the contract/order, the Government reserves the right to inspect Contractor performance.

5.7 Service Contract Reporting (SCR)

The contract does not meet the DoD Contract Reporting criteria or reporting dollar threshold; therefore, SCR does not apply.

5.8 Invoicing/Payment and Receipt/Acceptance

The Contractor shall submit/process payment requests and receipt/acceptance documents via WAWF.

5.9 Trafficking in Persons

The Contractor shall comply in accordance with the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract as it relates to Trafficking in Persons. Additional information about Trafficking in Persons is available at the site for the Department of State’s Office to Monitor and Combat Trafficking in Persons. https://www.state.gov/

5.10 Inspection of Services

USAF DCGS PMO reserves the right to inspect contractor performance of this PWS.

PR: FD2060-__-_____ PWS REVISION: 0 14

6.0 Appendices

6.1 Appendix A: Acronyms

6.2 Appendix B, References

Joint Travel Regulations (JTR)