EMSS V PWS_7 Oct 2026.pdf

PERFORMANCE WORK STATEMENT (PWS)

FOR

ENVIRONMENTAL MODELING AND SIMULATION SUPPORT V (EMSS-V)

AIR FORCE TECHNICAL APPLICATIONS CENTER (AFTAC)

24TH ANS/ANE

7 October 2026

1 DESCRIPTION OF SERVICES

1.1 INTRODUCTION

1.2 BACKGROUND

1.3 SCOPE

1.4 PERIOD OF PERFORMANCE

2 SPECIFIC TASKS

2.1 GENERAL TASKING

2.2 RESEARCH, DEVELOPMENT, TEST, AND EVALUATION (RDT&E)

2.3 OPERATIONS AND MAINTENANCE (O&M) SUPPORT

3 SERVICES SUMMARY (SS)

4 GOVERNMENT FURNISHED PROPERTY AND SERVICES

4.1 SERVICES

4.2 FACILITIES

4.3 UTILITIES

4.4 EQUIPMENT

4.5 MATERIALS

5 SPECIAL REQUIREMENTS/INSTRUCTIONS

5.1 SPECIAL INFORMATION TECHNOLOGY (IT) REQUIREMENTS

5.2 CONTRACTOR IDENTIFICATION IN THE GOVERNMENT WORKPLACE

5.3 INDUSTRIAL SECURITY

5.4 PHYSICAL SECURITY

5.5 DELIVERABLES

5.6 PRIVACY ACT

5.7 LOCATION(S) OF WORK

5.8 ON-SITE HOURS OF OPERATION

5.9 CONSERVATION OF UTILITIES

5.10 RECORDS

5.11 CONTRACTOR MANPOWER REPORTING

5.12 ENVIRONMENTAL CONTROLS

5.13 SAFETY REQUIREMENTS

5.14 CONTRACTOR PERSONNEL TRAINING

5.15 SPECIAL TRAINING, CERTIFICATIONS AND QUALIFICATIONS

5.16 KICK-OFF MEETING AND PERIODIC PROGRESS MEETINGS

5.17 CONTRACTOR TRAVEL

6 APPENDIX

APPENDIX A - ACRONYMS AND ABBREVIATIONS LIST

APPENDIX C - APPLICABLE PUBLICATIONS & INSTRUCTIONS

1 DESCRIPTION OF SERVICES.

1.1 Introduction.

This is a non-personal services contract. The Government will neither supervise contractor employees nor control the method by which the contractor performs the required tasks. The contractor shall manage its employees and guard against any actions that are of the nature of personal services or give the perception of personal services. The contractor shall notify the Contracting Officer (CO) immediately if they perceive any actions constitute personal services.

These services shall not be used to perform any Inherently Governmental Functions. Contract Data Requirement List (CDRL) requirements will be identified in the appropriate sections throughout this PWS.

1.2 Background.

AFTAC's Environmental Modeling and Simulation (EMS) mission strives to provide the elite level of modeling and simulation necessary to support AFTAC’s mission space. The Government needs to identify the pathways commonly used for the production of chemicals, identify the many physical and chemical constants associated with their manufacture, the specific uses in these processes of important chemicals, and the potentially environmentally damaging particles/particulates and vapors produced. The purpose of this effort is to provide the EMS program with the highly technical scientific modeling and analytical laboratory support it needs to perform its unique modeling mission.

The Government has a need to identify the pathways commonly used for the production of chemicals, identify the many physical and chemical constraints associated with their manufacture, the specific uses in these processes of important chemicals, and the potentially environmentally damaging particles/particulates and vapors produced. The purpose of this task is to enhance existing methods and research new techniques to generate state-of-the-art models meeting the Government’s needs.

Assuring the integrity of sample collection and analysis data is of paramount importance to the evaluation process of AFTAC mission. Such assurance requires a reliable and continuous process of database updates and skilled data curation. Monitoring of laboratory process stability, ensuring inter-laboratory agreement on analysis results, performing comprehensive reviews of the validity of collection and analysis data for significant sample results, and ensuring integrity and completeness of sample data from special collection projects are essential pillars of the rigorous QA/QC program of AFTAC’s mission. Advances in laboratory technologies and procedures, new mission data streams, and the evolving data processing environment require focused effort to adapt and apply advanced scripted analytical tools and procedures to ensure continued high data quality.

1.3 Scope.

The contractor shall have a Top-Secret Facility Clearance with Secret Safeguarding capability.

Additionally, the contractor shall have the ability to provide TS/SCI personnel to conduct the scope outlined in Section 2 at the time of award.

This Performance Work Statement (PWS) establishes the requirements for contractor-provided services that will include, but not be limited to technical, programmatic, acquisition, expert panel, analyses, engineering, logistical, and consultation support on a Task Order (TO) basis.

The contractor shall meet all requirements and responsibilities in support of AFTAC as identified in this PWS including all subsequent TOs. All support and staff shall be fully trained, professional, and customer oriented to consistently provide responsive, flexible, innovative, and cost-effective support serv

This "level of effort" project's primary objective is to perform both operations and maintenance (O&M) and research and development (R&D) tasks that support the EMS Program. The majority, if not all of this work will be done at the Contractor site.

1.4 Period of Performance:

1 Nov 2027 – 31 Oct 2035 (8 years)

2 SPECIFIC TASKS.

2.1 General Tasking.

2.1.1 Task Order (TO) Management.

2.1.1.1 The contractor shall appoint a program manager and perform project management activities for all task orders. These activities shall include, but not be limited to, the following: subcontractor management, task order tracking, monitoring, reporting, and executing corrective actions in order to perform the needs of specific task orders.

2.1.2 Management and Administration.

2.1.2.1 The contractor shall provide contract management and administration support.

This shall include the technical and administrative planning, coordination, analysis, and tracking of the diverse efforts required to provide the support described in this PWS, and subsequent TO. The contractor shall track sub-tasks within each TO.

2.1.3 Technical Library.

2.1.3.1 The contractor shall maintain all documentation gathered in support of this contract such as the PWS specifications, contractor data, and all other information relevant to efforts for which TO have been issued. The contractor shall develop and maintain a document version tracking system.

2.1.4 Performance Requirements.

2.1.4.1 The contractor shall perform all technical tasks included in the following paragraphs (or as specified in subsequent TOs) of this PWS and all ancillary tasks to include administrative actions, attendance at meetings, conferences, and all other tasks required to successfully accomplish the work within each TO.

2.1.5 TO Reporting.

2.1.5.1 The contractor shall report on all Tos to include cost, schedule, and performance status. This information shall be tracked down to the TO and sub-task level. All sub-tasks shall be sufficiently broken down so the Government contracting officer’s representative (COR) can successfully monitor the progress of each individual tasking. All required adjustments to the baselines shall be documented in the monthly reports.

2.1.6 TO Deliverables.

2.1.6.1 All deliverables generated shall be submitted in accordance with requirements specified in each TO and in the CDRL of this contract.

2.1.7 Inter-contractor Agreements.

2.1.7.1 The contractor shall sign an Associate Contractor Agreement and/or Non- Disclosure Agreement with third-party contractors specified by the Government.

2.2 Research, Development, Test, and Evaluation (RDT&E).

2.2.1 General Category Tasks.

2.2.1.1 The contractor shall plan, organize, staff, and perform studies, evaluations, research, testing, and generate reports in support on all aspects of the EMS program. The contractor shall perform, but is not limited to, the following RDT&E tasks:

(1) Research and Development of ChemCAD models

(2) New analytical methods and technology

(3) Analysis support for novel materials

(4) Provide RDT&E re-engineering support

(5) Other unique research

(6) Technical reports

(7) Technical conferences

(8) Presentation materials

2.2.2 RDT&E of New Analytical Methods and Technology.

2.2.2.1 The contractor shall perform RDT&E of new analytical methods and technologies for laboratory use.

2.2.2.2 All protocols developed from this tasking shall allow the laboratory to selectively concentrate target compounds from complex background matrices to enhance forensic analysis of field samples.

2.2.2.3 The contractor shall conduct basic literature searches, develop analyte-class or analyte specific analytical methods, and produce required reports.

2.2.3 R&D and Analysis Support for Novel Materials.

2.2.3.1 The contractor shall engage in the report on all the following tasks:

(1) Develop new or evaluate existing analytical instrumentation for performance of this task.

(2) Investigate R&D technologies that result in enhancing existing methods of detection in order to further characterize, detect, and quantify specific materials of interest.

2.2.3.2 The Government will identify the specific materials of interest at the TO level.

2.2.4 RDT&E Re-engineering and Environmental Chemistry Support.

2.2.4.1 The contractor shall recommend, develop, and demonstrate comprehensive and significant improvements to the technical and operational capabilities.

2.2.4.2 The contractor shall identify and evaluate potential research topics that minimize impacts to cost, schedule, and technical baselines, and improve mission capabilities.

2.2.4.3 Technical areas of interest to this program are related to analytical chemistry, atmospheric chemistry, chemical kinetics, environmental chemistry, chemical process modeling, and physical properties.

2.2.5 Unique Research.

2.2.5.1 The contractor shall provide support to unique research tasks of special interest to the Governments EMS program.

2.2.6 Reports.

2.2.6.1 The contractor shall prepare and provide a technical and management work plan addressing technical approaches, schedule, and cost.

2.2.6.2 At the completion of all technical support tasks a technical report shall be submitted.

2.2.7 Technical Conference.

2.2.7.1 The contractor shall provide conference facilities to support classified meetings (of up to approximately 50 people) at the contractor’s facility on an as-needed basis by the Government.

2.2.7.2 The contractor shall provide a conference room(s) with appropriate security arrangements, coordinate conference accommodations, and document meeting minutes and action items during these functions.

2.2.8 Presentation Materials.

2.2.8.1 The contractor shall provide presentation materials to support technical and programmatic Government meetings such as kick-off meetings, program reviews, and final TO review meetings.

2.3 Operations and Maintenance (O&M) Support.

2.3.1 The contractor shall provide O&M support in areas such as “subject matter expert”, upgrades and enhancements (maintenance) of ChemCAD models and other software, laboratory hardware, maintenance of records and data files, support of various field operations, and other O&M work required.

2.3.2 Laboratory QA and Sample Data Curation

2.3.2.1 The contractor shall perform periodic queries and produce charts and summaries of data quality indicators from AFTAC sample collections and laboratory analyses; prepare quarterly technical reports of findings from inter-laboratory QA evaluations; summarize findings in presentations for semiannual technical working group meetings; develop or modify scripted analytics using R (or other suitable environments) to accomplish QA analyses efficiently and reproducibly. These quarterly reports shall utilize control charts and models to identify measurement process instabilities and to provide updated indications of the adequacy of reported uncertainty values.

2.3.2.2 The contractor shall perform analyses to identify and validate significant mission samples for evaluation; develop or modify scripted analytics using R (or other suitable environments) to accomplish these analyses efficiently and reproducibly;

summarize and record QA validation assessments in accordance with AFTAC workflow conventions (database incident workflow or equivalent); communicate with laboratories and/or collections supervisors to facilitate resolution of data quality concerns.

2.3.2.3 The contractor shall monitor progress on laboratory processing and analysis of special Sample Analysis Request (SAR) sets; accomplish database updates at Governments direction of the SAR-related data, perform inter-laboratory consistency checks on sample analysis results; devise and execute data queries to summarize analysis results in accordance with specified formats and conventions, and prepare graphical and tabular summaries for use in evaluation and reporting.

2.3.3 Onsite Subject Matter Expert support for R-scripted Operational Analytical Tools.

2.3.3.1 The contractor shall provide periodic onsite subject matter expert (SME) consultations throughout the course of anticipated Task Orders to assist in the formulation, maintenance, documentation and application of R-scripted analytical tools for use operationally in support of the RPP mission.

2.3.3.2 On each occasion of onsite SME consultation, the contractor shall provide documentation, continuity instructions, and a bullet-point summary of any modifications to the R-scripted tools that were implemented.

3 SERVICES SUMMARY (SS).

The contract service requirements are summarized in performance objectives that relate directly to mission essential items. The performance threshold briefly describes the minimally acceptable levels of service required for each requirement. The SS provides information on contract requirements and the expected level of contractor performance to be successful. These thresholds are critical to mission success. Procedures as set forth in the applicable Inspection clause in the contract will be used to remedy all deficiencies. The Government retains the right to inspect any item included in the contract. The following are Performance Objectives and Performance Thresholds for this TO.

Performance Objective PWS Paragraph Performance Threshold

SS # 1.

The contractor shall provide a Baseline Report describing the proposed methods to meet project objectives.

Section 2 The contractor shall provide a proposed approach that rationally addresses 100% of project goals and delivered to sponsor within three (3) working days of schedule. Processes shall mirror the approach provided in baseline.

SS # 2.

Develop and provide accurate project schedule and cost estimates.

Section 2 Completes all work required in accordance with the task order schedule and the estimated costs at least 90% of the time.

SS # 3.

Develop and provide software model updates detailing thermodynamics, emission data and emission methodology.

Section 2 Emissions data generated at the government site using the contractor delivered thermodynamic model is comparable to the contractor's emissions data within 5%.

SS#4.

Provide list of materials for likely release materials and criteria.

Section 2 Based on previously determined government criteria, 100% of predicted particles/particulates or vapor emissions are included in the end of year technical report.

SS # 5.

Review Meetings

Section 2 Periodic project review meeting to be held approximately every four (4) months, will typically cover all active task orders and in conjunction with other task order review meetings.

Performance Objective PWS Paragraph Performance Threshold

SS # 6.

Update physical properties database.

Section 2 Functionality and usability of derived data is satisfactory based on requirements in 2.2, and 2.3

SS # 7.

Provide timely CDRL deliveries.

Section 2 No more than one (1) late CRDL per quarter, and if late, no deliverable shall be more than two (2) working days late.

SS # 8.

Provide quality CDRL deliveries.

Section 2 Only minor revisions are acceptable and no more than one (1) CDRL per quarter shall require revision. All corrections shall be completed within five (5) working days after notification by the Government COR.

SS # 9.

Provide analytical methods and results.

Section 2 Methods developed for government defined compounds are included in the end of year technical report.

4 GOVERNMENT FURNISHED PROPERTY AND SERVICES.

4.1 Services.

The Government will provide no Government Furnished Services.

4.2 Facilities.

Determined on a TO basis. The Government will provide the necessary workspace for the contractor staff to provide the support outlined in the PWS to include desk space, telephones, computers, and other items necessary to maintain an office environment if the TO performed at the Government facilities.

4.3 Utilities.

All utilities in AFTAC HQ will be available for the contractor’s use in performance of tasks outlined in this PWS while on site. No Government furnished services will be provided for work conducted at contractor facilities.

4.4 Equipment.

Determined on a TO basis. The Government may provide GFP if required to complete a TO.

4.5 Materials.

Determined on a TO basis. The Government may provide Government Furnished Materials if required to complete a TO.

5 SPECIAL REQUIREMENTS/INSTRUCTIONS.

5.1 Special Information Technology (IT) Requirements.

5.1.1 This program expects the adoption and execution of a Preferred Agile Framework outlined by the Department of the Air Force which include SCRUM, Kanban, and Lean methodologies tailored to the specific DevSecOps and software factory model being used, which emphasizes iterative development and frequent user feedback ensuring an architectural framework that can be adjusted throughout the period of performance. If feasible, adopting the aforementioned development process, existing applications, components, and platforms is preferred over creating custom solutions.

5.1.2 Guidance and Standards Compliance: Software development shall make good faith efforts to rely and align solutions to the DoD Enterprise DevSecOps Fundamentals, Air Force Capability Development Guidebook, and the AFTAC Software Development Strategy Document (SDSD) where supported, to include software security and quality considerations. Any deviations shall be presented to the AFTAC Software Strategy Council or its functionally equivalent as soon as they are identified. (Reference Attachment X, “Software Development Strategy Document”).

5.1.3 All IT products (requirements and solutions), to include software, hardware, processes and security products delivered to AFTAC as a requirement of this PWS shall adhere to the AFTAC Enterprise Infrastructure Baseline with any deviations approved by the AFTAC Infrastructure Strategy Council or its functional equivalent before delivery of the IT product. All IT deliveries are expected to integrate and conform to AFTAC’s Enterprise Infrastructure Baseline. Hardware, storage, and database requirements must be identified as soon as possible and presented to the AFTAC Infrastructure Strategy Council or its functional equivalent for approval.

5.1.4 All software developed for AFTAC, except software, hardware, processes and services that cannot be supported such as High-Performance Computing (HPC), will first be installed and tested in a development environment such as the Common Development Environment (CDE) at the appropriate classification level. Note: The AFTAC CDE is currently unavailable to support this software at this time. For any software project that cannot be supported by the CDE, the project plan will be presented and approved by the appropriate software cross functional team.

The Contractor shall supply on-site support, if required, for installation of software into AFTAC’s Continuous Integration (CI) Pipeline. The contractor shall also provide support to install and configure any middleware necessary to run the delivered software. This software is intended for installation in the operational environment. The Contractor shall provide documentation as requested to support certification and accreditation processes as needed.

5.1.5 The contractor shall ensure the Government has the ability to rebuild and deploy the system in the future regardless of the contractor availability. The contractor shall deliver the software tools and integrate them with AFTAC’s .GOV CI Pipeline and provide the software source code in a Gitlab project along with the Gitlab YML file. The Government will ensure Continuous Integration and Continuous Deployment (CI/CD) components are available, configured, and operational in the AFTAC .GOV CI Pipeline and that AFTAC CDE workstations are available to the contractor for this effort.

5.1.6 The GitLab CICD project will build the source code, run automated tests against an pre-approved container created and configured with test schema and test data, create a code coverage report and submit to SonarQube for quality and code coverage analysis. Pipeline https://dodcio.defense.gov/Portals/0/Documents/Library/DoD%20Enterprise%20DevSecOps%20Fundamentals%20v2.5.pdf https://afacpo.com/AQDocs/A57_Capability_Development_Guidebook_Vol2I.pdf https://afacpo.com/AQDocs/A57_Capability_Development_Guidebook_Vol2I.pdf stages will be added to run the Government's Fortify for security scanning and Black Duck for library scanning. Fortify scanning will result in no Critical or High findings. The resulting build artifacts and reports will be stored in the Government's Artifactory Repository. When complete, the User Manual will also be uploaded to the Artifactory repository.

5.1.7 Software deliveries shall consist of source code of noncommercial software (except where such source code is unavailable), all software dependencies, unit tests, related data, and associated license rights that are necessary across the life cycle of that software, including development, testing, operations, and maintenance as specified by CDRL’s. This includes all artifacts necessary to reproduce, build, or recompile the software from its source code and required software libraries; to conduct required software testing; and to deploy on relevant system hardware as specified by CDRL’s. Binaries or executables without source code, unless identified as Commercial off the Shelf (COTS) with support or Government Off-The-Shelf (GOTS) software with restricted source code releasability, are not an acceptable delivery.

5.1.8 All software deliveries are complete after integration into AFTAC’s CI Pipelines, installed and running in the CDE if the appropriate environment exists, and contain clean security scans (to include source code scans, third-party dependency scans, and Assured Compliance Assessment Solution (ACAS) scans) if intended for the operational environment. Onsite support for installation onto CDE and production/operational networks may be required, as well as assistance with integration and system testing efforts. The final software product is considered completed once it can be operated by a Government employee on AFTAC systems and it produces verified results for which the software was developed.

5.2 Contractor Identification in the Government Workplace.

When conversing with Government personnel during business meetings, over the telephone or via electronic mail, the contractor shall identify themselves as such to avoid situations arising where sensitive topics might be better discussed solely between Government employees. The contractor shall identify themselves on any attendance sheet or any coordination documents they may review.

Electronic mail signature blocks shall identify their company affiliation.

5.3 Industrial Security.

5.3.1 DD Form 254. Overarching security requirements and contractor access to classified information will be as specified in the DD Form 254, Department of Defense Security Classification attached to the contract. The contractor shall have a final U.S.

Government issued TOP SECRET security clearance and be DCID 6/4 eligible with a current SSBI at contract award.

5.4 Physical Security.

The contractor shall safeguard all Government property provided for contractor use. At the close of each work period, Government facilities, property, and materials shall be secured.

5.4.1 Key Card Control. The contractor shall establish and implement methods of ensuring that all key cards issued to the contractor by the Government are not lost or misplaced and are not used by unauthorized persons.

5.4.1.1 The contractor shall immediately report the occurrences of a lost or duplicate key cards to the COR.

5.4.1.2 In the event keys, other than master keys, are lost or duplicated, the contractor shall, upon written direction of the CO, rekey or replace the affected lock or locks;

however, the Government, at its option, may replace the affected lock or locks or perform rekeying. When the replacement of locks or rekeying is performed by the Government, the total cost of rekeying or the replacement of the lock or locks shall be deducted from the monthly payment due the contractor. In the event a master key is lost or duplicated, all locks and keys for that system will be replaced by the Government and the total cost shall be deducted from the monthly payment due the contractor.

5.4.1.3 The contractor shall prohibit the use of key card issued by the Government by any persons other than the contractor’s employees. The contractor shall prohibit the opening of locked areas by contractor employees to permit entrance of persons other than contractor’s employees engaged in the performance of assigned work in those areas, or personnel authorized entrance by the COR.

5.4.2 Combinations and Codes. The contractor shall establish and implement methods of ensuring that all combinations and codes are not revealed to unauthorized persons. The contractor shall ensure that lock combinations are changed when personnel having access to the combinations no longer have a need to know such combinations.

5.4.2.1 Access lock combinations are “Controlled Unclassified Information” (CUI) and shall be protected from unauthorized personnel.

5.4.2.2 Combinations to security containers, secure rooms, or vaults are classified information and shall properly safeguarded. Only the contractor employees with proper security clearance and need-to-know will be given combinations to security containers, secure rooms, or vaults.

5.4.2.3 Security alarm access codes are “CUI” and shall be protected from unauthorized personnel. Security alarm access codes will be given to contractor employees who require entry into areas with security alarms. The contractor shall properly safeguard alarm access codes to prevent unauthorized disclosure.

5.5 Deliverables.

5.5.1 The Government requests unlimited rights to all deliverables specified in individual TOs, to include intellectual property rights.

5.6 Privacy Act.

Work on this contract requires the contractor to have access to Privacy Information. The contractor shall adhere to the Privacy Act, Title 5 of the US Code, Section 552a and applicable Agency rules and regulations.

5.7 Location(s) of Work.

5.7.1 The work to be performed under this contract shall be performed at ether AFTAC Headquarters (HQ) (Address Below) or contractor facility based on the needs outlined in the individual TOs.

AFTAC HQ

1020 South Patrick Drive

Patrick SFB, FL 32925

5.8 On-Site Hours of Operation.

5.8.1 Normal Hours of Operation. The contractor shall perform the services required under this contract during the following hours: Mon - Fri, 0700-1800, core hours 0900-1500, except federal holidays. Any changes to the core schedule shall be approved under direction of the COR.

5.8.2 Recognized Holidays. The contractor is not required to provide service on the following days:

New Year’s Day Labor Day Dr. Martin Luther King’s Birthday Columbus Day

Washington’s Birthday Veterans Day Memorial Day Thanksgiving Day

Juneteenth Independence Day

Christmas Day

5.8.2.1 If the holiday falls on Saturday, it is observed on Friday. If the holiday falls on a Sunday, it is observed on Monday.

5.8.2.2 The contractor shall not report to work and will not be reimbursed by the Government when the Government facility is closed due to a Federal holiday, local or national emergencies, administrative closings, or similar Government directed facility closings.

5.9 Conservation of Utilities.

The contractor shall operate under conditions which prevent the waste of utilities which include the following:

5.9.1 Lights shall be used only in areas where and when work is actually being performed.

5.9.2 Mechanical equipment controls for heating, ventilation, and air conditioning systems shall not be adjusted by the contractor unless authorized.

5.9.3 Water faucets or valves shall be turned off after the required use has been accomplished.

5.9.4 Government telephones shall be used only for official Government business.

5.10 Records.

The contractor shall create, maintain, and dispose of only those Government required records that are specifically cited in this PWS or required by the provisions of a mandatory directive. If requested by the Government, the contractor shall provide the original record, or a reproducible copy of any such record within five (5) workdays of receipt of the request.

5.11 Contractor Manpower Reporting.

5.11.1 Effective Fiscal year (FY) 2020, the Department of Defense (DoD) will no longer require contractors to report into the Enterprise-wide Contractor Reporting Application (eCMRA). For FY 2020, contractors shall begin reporting manpower data relating to the performance services contracts into the System for Award Management (SAM).

(www.sam.gov).

5.11.2 The following contracts are subject to Service Contract Reporting (SCR): Any purchase of services by a military DoD Agency, in excess of $3 Million, for services in the following Service Acquisition Portfolios:

5.11.2.1 Logistics management services;

5.11.2.2 Equipment-related services;

5.11.2.3 Knowledge-based services;

5.11.2.4 Electronics & comms services.

5.11.3 Contractor shall be an entity registered in SAM, an individual SAM user account with the Entity Administrator, Entity Registration Representative, or Reporter role for that entity, and one or more contracts awarded to that entity which meet the SCR requirements. Contractors shall report manpower data relating to the performance services contract into SAM (www.sam.gov).

5.11.4 Steps for Submitting a SCR.

5.11.4.1 Go to www.sam.gov and log in.

5.11.4.2 Select Entity Registrations and then select Service Contract Reporting.

5.11.4.3 SAM displays your entities which have service contracts and meet the reporting criteria. Select View by entity to see the service contracts for each entity.

5.11.4.4 Next, select Add for the service contract against which you want to create a Service

Contract Report. Each service contract which meets the Federal Acquisition Regulation (FAR) Subpart 4.1703 reporting thresholds is displayed.

5.11.4.5 Next, the Complete Service Contract Report page will be displayed. SAM displays the contract details and allows you to report. Contractor is required to enter the following information:

- Total Amount Invoiced: Total dollar amount invoiced for services performed during the previous Government fiscal year under the contract (this amount should include the prime and any subcontract amount).

- Prime Contractor Hours Expended: Prime contractor direct labor hours expended on the services performed during the previous Government fiscal year. The amount you enter is automatically divided by 2,080 hours to calculate a Full Time Employee (FTE) equivalent, displayed under the Prime Contractor Hours Expended as Prime Contractor FTEs.

5.11.4.6 Report any required Tier 1 subcontractor information by selecting the Add Tier 1 Subcontract Information button.

http://www.sam.gov/ http://www.sam.gov/ http://www.sam.gov/

5.11.4.7 When you are ready to submit the report, select Submit. This saves your report and returns you to the Select Service Contract page where you can create other SCRs or edit an existing SCR.

5.11.5 Annual Reporting. Reporting inputs will be for the direct labor executed during the Period of Performance (PoP) for each Government FY, which runs 1 October through 30 September. While inputs may be reported any time during the FY, all data shall be reported no later than 31 October of each calendar year. The contractor shall provide reporting inputs for the final PoP of this contract no later than thirty (30) calendar days after contract expiration. The contractor may direct technical questions about the SAM Service Contract Reporting tool to the Federal Service Desk (FSD) at https://www.fsd.gov/fsd-gov/home.do.

5.12 Environmental Controls

5.12.1 Compliance with Laws and Regulations. The contractor shall be knowledgeable of and comply with all applicable Interstate, Federal, State, and Local laws, regulations, and requirements regarding environmental protection. In the event environmental laws or regulations change during the term of this contract, the contractor shall comply as such laws come into effect. If there is an increase or decrease in cost as a result of the change, the contractor shall inform the CO pursuant to notice requirements and negotiate a modification to the contract.

5.12.2 Notification of Environmental Spills. If the contractor spills or releases any substance contained in 40 Code of Federal Regulation (CFR) 302 into the environment, the contractor shall immediately report the incident to the COR. The liability for the spill or release of such substance’s rests solely with the contractor.

5.13 Safety Requirements

In performing work under this contract, the contractor shall:

5.13.1 Conform to the safety requirements contained in the contract for all activities related to the accomplishment of the work.

5.13.2 Take such additional immediate precautions as the CO may reasonably require for safety and mishap prevention purposes.

5.13.3 Record and report promptly (within one hour) to the CO or COR, all available facts relating to each instance of damage to Government property or injury to either contractor or Government personnel.

5.13.4 In the event of an accident/mishap, take reasonable and prudent action to establish control of the accident/mishap scene, prevent further damage to persons or property, and preserve evidence until released by the accident/mishap investigative authority through the CO.

5.13.5 If the Government elects to conduct an investigation of the accident/mishap, the contractor shall cooperate fully and support Government personnel conducting the investigation.

5.14 Contractor Personnel Training.

https://www.fsd.gov/fsd-gov/home.do

5.14.1 The contractor shall be fully capable to support the tasks as described in section 2.0.

5.15 Special Training, Certifications and Qualifications.

5.15.1 Contractor personnel requiring access to a DoD Information System shall receive initial Information Assurance (IA) awareness orientation as a condition of access and thereafter shall complete annual IA refresher awareness, IAW by DoD Directive 8140.03, "Information Assurance Training, Certification, and Workforce Management".

5.15.2 Any contractor requiring access to an AFTAC-managed IT system (on premises or cloud) in order to write or edit software destined for the production system will require IAT Level II certification IAW DoD Directive 8140.03 “Information Assurance Training, Certification, and Workforce Management”. Contractors requiring elevated privileges to an AFTAC-managed IT system (on premises or cloud) will require certifications based on the level of elevated privileges that will be determined on a case-by-case basis but will require a minimum of IAT Level II certification.

5.15.3 DoD 8140.03 Registration.

5.15.3.1 The contractor shall register all DoD 8140.03 certifications into the Defense Workforce Certification Application (DWCA) using the following web address:

https://public.cyber.mil/wf-element-sub/cybersecurity/.

5.15.3.2 DWCA is the authoritative database of DoD Military, Civilian and Contractor personnel who hold active 8140.03 certifications used by the DoD CIO office to validate, monitor and report on the certification status of certified IA workforce members. Additional information can also be found at DoD Cyber Workforce.

5.16 Kick-off Meeting and Periodic Progress Meetings.

The contractor shall attend an initial kick-off meeting after contract award if requested. The CO, COR, and other Government personnel, as appropriate, may meet periodically with the contractor to review the contractor's performance. At these meetings the CO will apprise the contractor of how the Government views the contractor's performance and the contractor will apprise the Government of problems, if any, being experienced. Appropriate action shall be taken to resolve outstanding issues. The contractor shall provide minutes of these meetings to the Government.

5.17 Contractor Travel.

The contractor shall be required to travel to support progress meetings and the demonstration. All travel requirements (including destination, purpose, plans, agenda, itinerary, number and names of personnel, and dates) shall be pre-approved by the COR. Contractor shall submit a trip report upon completion of travel. Costs for travel shall be billed on a strictly cost reimbursable basis In Accordance With (IAW), the regulatory implementation of Public Law 99-234, FAR subpart 31.205-46 entitled Travel Costs and the limitation of funds specified in this contract. Any travel requirements not identified will need to be negotiated and the contract/order will need to be modified.

https://public.cyber.mil/wf-element-sub/cybersecurity/ https://dodcio.defense.gov/Cyber-Workforce/DoDCW.aspx

6 APPENDIX.

APPENDIX A - ACRONYMS AND ABBREVIATIONS LIST

Acronym/Abbreviation Definition

ACAS Assured Compliance Assessment Solution AFTAC Air Force Technical Applications Center CDE Common Development Environment CDRL Contract Data Requirement List CFR Code of Federal Regulation CI Continuous Integration CI/CD Continuous Integration and Continuous Deployment CO Contracting Officer COR Contracting Officer's Representative COTS Commercial Off-The-Shelf CUI Controlled Unclassified Information DoD Department of Defense eCMRA Enterprise-wide Contractor Reporting Application EMS Environmental Modeling and Simulation EMSS Environmental Modeling and Simulation Support FAR Federal Acquisition Regulation FSD Federal Service Desk FTE Full Time Employee FY Fiscal Year GFP Government Furnished Property GOTS Government Off-The-Shelf HPC High Performance Computing HQ Headquarters IA Information Awareness IAW In Accordance With IT Information Technology O&M Operations and Maintenance PoP Period of Performance PWS Performance Work Statement R&D Research and Development RDT&E Research, Development, Test, and Evaluation SAM System for Award Management SCR Service Contract Reporting SDSD Software Development Strategy Document SOW Statement of Work

SS Services Summary TO Task Order TS Top Secret

APPENDIX C - APPLICABLE PUBLICATIONS & INSTRUCTIONS

The contractor shall comply with all publications, regulations and operating instructions provided by the Government when they pertain to the procedures for materials expediting herein and where the contractor is authorized by the PWS to accomplish the work specified in the publication, regulation or operating instructions. The publications prescribe USAF policies, use of materials, procedures and processes applicable to the work requirements. The contractor shall acquire and work on the latest version of the publication.

Publication/Instruction - Title Applicable Paragraph/Chapter PWS Paragraph AFTAC SCG (current version) Entire document applicable All