RFP Attachment 1 - MMAS II PWS (1 Feb 24).pdf

PERFORMANCE WORK STATEMENT (PWS)

FOR

METEOROLOGICAL MODELING, ANALYSIS, AND SUBJECT MATTER

EXPERTISE 2 (MMAS 2) SERVICES

AFTAC/24ANS

1 February 2024

(U) This contecnt is controlled unclassified information (CUI), unclassified or information classified at a lower level than the overall classification displayed. This content shall not be used as a source of derivative classification; refer instead to AFTAC SCG, 22 June 2023. This content must be reviewed for both Classified National Security Information (CNSI) and CUI in accordance with DODI 5230.09 prior to public release.

Controlled by: DAF Controlled by: AFTAC/24 ANS/ANP CUI Category: OPSEC Distribution/Dissemination Control: FEDCON POC: alex.lake@us.af.mil

SECTION 1

1 DESCRIPTION OF SERVICES

1.1 INTRODUCTION

1.2 BACKGROUND

1.3 SCOPE

1.4 PERIOD OF PERFORMANCE

2 SPECIFIC TASKS. (CDRLS A001 THROUGH A006 APPLY)

2.1 SOFTWARE DEVELOPMENT AND OPTIMIZATION SERVICES (O&M OR R&D)

2.2 EXPERT PANEL SERVICES (O&M)

2.3 SPACE WEATHER MODELING SERVICES (O&M OR R&D)

2.4 SUBJECT MATTER EXPERTISE SERVICES (O&M OR R&D)

2.5 ATMOSPHERIC MODELING SERVICES (O&M OR R&D)

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 IT REQUIREMENTS

5.2 CONTRACTOR IDENTIFICATION IN THE GOVERNMENT WORKPLACE

5.3 INDUSTRIAL SECURITY

5.4 PHYSICAL SECURITY

5.5 PRIVACY ACT

5.6 LOCATION(S) OF WORK

5.7 RECORDS

5.8 DATA

5.9 SPECIAL TRAINING, CERTIFICATIONS AND QUALIFICATIONS

5.10 CONTRACTOR MANPOWER REPORTING

5.11 KICK-OFF MEETING AND PERIODIC PROGRESS MEETINGS

5.12 CONTRACTOR TRAVEL

5.13 DELIVERABLES

APPENDIX A - ACRONYMS AND ABBREVIATIONS LIST

APPENDIX B - APPLICABLE PUBLICATIONS & INSTRUCTIONS

SECTION 5

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.

1.2 Background.

AFTAC’s 24th Analysis Squadron Meteorological mission has a new requirement for atmospheric modeling, weapons of mass destruction (WMD) analysis, meteorological and modeling expertise support.

1.3 Scope.

This Indefinite Delivery/Indefinite Quantity (IDIQ) contract will provide subject matter expertise, atmospheric science, modeling, and the development of technical capabilities with emphasis in the following areas: (a) urban environment transport and dispersion (T&D); (b) Space Weather modeling (c) development and implementation of airborne material source term estimation (STE) methodologies for WMD defense applications (d) Weather Research and Forecast (WRF) model for meteorological prediction and atmospheric event reconstructions; (b) atmospheric T&D with emphasis on WMD; (f) operational software development. Both R&D and O&M tasks are expected; however the specific labor categories required will be identified by task at the task order level.

1.4 Period of Performance.

Five (5) year ordering period.

2 SPECIFIC TASKS. (CDRLs A001 through A006 apply)

2.1 Software Development and Optimization Services (O&M or R&D)

2.1.1 The contractor shall develop, optimize, and implement operational numerical weather prediction and AT&D modeling solutions demonstrated with the following modeling systems

2.1.1.1 WRF

2.1.1.2 Hazard Prediction and Analysis Capability (HPAC)

2.1.1.3 Joint Effects Model (JEM)

2.1.2 The contractor shall design and implement modeling and software solutions utilizing a variety of languages and software including the following

2.1.2.1 FORTRAN

2.1.2.2 C/C++

2.1.2.3 Java

2.1.2.4 Python

2.1.2.5 Container Software (Singularity[Apptainer] and Docker)

2.1.3 The contractor shall profile the computational performance of scientific modeling capabilities and implementing performance optimizations using High Performance Computing (HPC) technologies

2.1.4 The contractor shall provide software architecture for scientific modeling applications

2.1.5 The contractor shall manage and execute within an Agile software development lifecycle

2.1.6 The contractor shall provide project management of software development using the following tools:

2.1.6.1 Version control (e.g., GIT, Rational Team Concert)

2.1.6.2 Issue tracking (e.g., Jira, Rational Team Concert)

2.1.6.3 Integration tools (e.g., Jenkins, Rational Team Concert)

2.1.7 The contractor shall provide expertise for the Team Awareness Kit (TAK), including but not limited to WebTAK and TAK server.

2.2 Expert Panel Services (O&M)

2.2.1 The contractor shall provide meterological modeling expert panel support for programs within AFTAC. The expert panel technical expert shall have the ability to give expert advice on briefings, presentations, data calculations as they pertain to AFTAC-related topics, and travel to foster relationships between outside entities and AFTAC.

2.3 Space Weather Modeling Services (O&M or R&D)

2.3.1 The contractor shall provide upper atmosphere modeling, analysis, and model validation with space weather tools

2.3.2 The contractor shall provide hardware and software development related to space weather modeling and analysis

2.3.3 The contractor provide internationally recognized expertise in upper atmosphere and space weather topics

2.4 Subject Matter Expertise Services (O&M or R&D)

2.4.1 The contractor shall provide expertise in atmospheric modeling with demonstrated expertise applying these models to problems that range from continental (1000’s of km) to micro (1-2 meters) scales

2.4.2 The contractor shall provide expertise in the development and implementation of airborne material STE methodologies for WMD defense applications

2.4.3 The contractor shall provide expertise in the following disciplines

2.4.3.1 Boundary layer meteorology processes

2.4.3.2 Turbulence

2.4.3.3 Atmospheric Transport and Dispersion

2.4.3.4 DoD WMD applications (e.g., HPAC, JEM)

2.4.4 The contractor shall provide technical reports and subject matter expert panel reports, demonstrated by a record of peer-reviewed publications on relevant science and technical topics and subject matter expert panel reports

2.5 Atmospheric Modeling Services (O&M or R&D)

2.5.1 The contractor shall use and adapt of the WRF model for meteorological prediction and atmospheric event reconstructions

2.5.2 The contractor shall provide atmospheric modeling and simulation of the following:

2.5.2.1 Atmospheric phenomena from continental (1000’s of km) to micro (1-2 meters) scales

2.5.2.2 Atmospheric transport and dispersion (AT&D) with an emphasis on problems involving WMD.

2.5.3 The contractor shall provide urban environment transport and dispersion modeling, including the modeling of atmospheric conditions, wind flow, and material transport and dispersion within urban environments where buildings and surface obstructions are present. The contractor shall have demonstrated experience with a diverse set of models including:

2.5.3.1 The Quick Urban Industrial Complex (QUIC) modeling system

2.5.3.2 “Building-aware” Large Eddy Simulation (LES) based atmospheric models with in-line AT&D capabilities

2.5.4 The contractor shall provide development and implementation of airborne material STE methodologies

2.5.5 The contractor shall conduct detailed testing, verification, and validation (V&V) of meteorological and AT&D models and tools.

2.5.6 The contractor shall implement and execute scientific models on advance computing platforms such as Graphics Processing Unit (GPU) based platforms

2.5.7 The contractor shall have demonstrated experience with a diverse set of models including:

2.5.7.1 Second-order Closure Integrated PUFF (SCIPUFF) model

2.5.7.2 Hybrid Single Particle Integrated Trajectory (HYSPLIT) model

2.5.7.3 Gaussian Plume Models

2.5.7.4 WRF-CHEM with in-line AT&D capability

2.5.7.5 LES-based atmospheric models with in-line AT&D capabilities

2.5.8 The contractor shall have demonstrated experience working on large software development teams developing operational software for DoD operational modeling and analysis systems. The contractor shall have demonstrated experience with a diverse set of models including:

2.5.8.1 HPAC modeling system

2.5.8.2 JEM modeling system

2.5.9 The contractor shall have demonstrated experience modeling the upper-atmosphere (stratosphere, mesosphere, ionosphere, and thermosphere) with the following models:

2.5.9.1 The Thermosphere-Ionosphere-Electrodynamic General Circulation Model (TIE-

GCM)

2.5.9.2 The Thermosphere-Ionosphere-Mesosphere-Electrodynamic General Circulation Model (TIME-GCM)

2.5.10 The contractor shall provide internationally recognized experts in the development and implementation of airborne material STE methodologies and atmospheric transport and dispersion models for WMD defense applications

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 Services Summary (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.

Performance Objective

PWS PARA

Performance Threshold

SS # 1.

The contractor shall develop and provide timely and quality CDRLs

2 All CDRLs shall be delivered on-time, with no more than one late CDRL per quarter. If late, that CDRL must be delivered within 2 days of the original due date

SS # 2.

The contractor shall meet all stated baseline requirements on-time and within approved schedule

2 Implement in accordance with individually-defined requirements for each paragraph listed. Software deliveries no more than five (5) defects resulting in PMC. Zero (0) defects resulting in NMC.

4 GOVERNMENT FURNISHED PROPERTY AND SERVICES.

4.1 Services.

No Government-furnished services will be provided.

4.2 Facilities.

No Government-furnished facilities will be provided.

4.3 Utilities.

No Government-furnished utilities will be provided.

4.4 Equipment.

Determined on a task order basis. The Government may provide Government-Furnished Equipment if required to complete a task order.

4.5 Materials.

Determined on a task order basis. The Government may provide Government-Furnished Materials if required to complete a task order.

5 SPECIAL REQUIREMENTS/INSTRUCTIONS.

5.1 Special IT Requirements

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 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 for approval.

This program expects the adoption and execution of the Preferred Agile Framework outlined by the Department of the Air Force, ensuring an architectural framework that can be adjusted throughout the period of performance. If feasible, adopting existing applications, components, and platforms is preferred over creating custom solutions.

Software solutions shall adhere to the AFTAC Software Development Strategy Document (SDSD), to include software security and quality considerations. Any deviations shall be presented to the AFTAC Software Strategy Council as soon as they are identified. (Reference Attachment C, “Software Development Strategy Document”).

All software developed for AFTAC will first be installed and tested in a development environment such as the Common Development Environment (CDE) at the appropriate classification level. The

Contractor shall supply on-site support 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. Some software will remain in the CDE indefinitely. This software is intended for installation in the CDE and the operational environment.

The Contractor shall provide documentation as requested to support certification and accreditation processes as needed.

Software deliveries shall consist of source code of noncommercial software, 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. 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. Binaries or executables without source code, unless identified as Commercial off the Shelf (COTS) with support, are not an acceptable delivery.

All software deliveries are complete after integration into AFTAC’s CI Pipelines, installed and running in the CDE, and contain clean security scans (to include source code scans, third-party dependency scans, and 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 run by a Government employee on AFTAC systems and it produces the results the software was developed for.

The contractor shall perform an Agile software engineering Discovery and Framing effort on the design and integration of the toolset(s) identified in this PWS. The analysis includes eliciting requirements from stakeholders within 24th ANS. The goal of the analysis is not to produce a complete requirements specification (as one would experience with a waterfall development methodology), but rather record the constraints (such as technologies supported by CYS and design considerations recommended by SDD) and the use cases/user stories from each stakeholder group. The outcome of the effort, accounting for projected deployment location and data accessibility considerations, will be preliminary architectural designs. Designs must meet government infrastructure and strategic plans. The system design will be presented to the government for approval before development begins.

The Contractor shall provide software changes and problem fixes as needed to support the operations, maintenance, and sustainment of the system. The contractor shall provide to the Government all developed, modified, or converted source modules, processes, programs, scripts, operating instructions, databases, system files, documentation, test files and test conditions used to develop each approved systems change request. When specified by the Government, the contractor shall participate with the Government in testing the system. The Contractor shall provide documentation as requested to support certification and accreditation processes as needed.

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.

5.3.1.1 All personnel working on this effort shall be a United States citizen. The work at the contractor facility will be unclassified, however any personnel participating in expert panel and Government-site training and work shall have a TOP SECRET clearance with a DCID 6/4 eligibility. The DD Form 254 dictates the number of personnel that shall meet these requirements.

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 Control. The contractor shall establish and implement methods of ensuring that all keys and key cards issued to the contractor by the Government are not lost or misplaced and are not used by unauthorized persons.

5.4.2 The contractor shall immediately report the occurrences of a lost or duplicate key to the

COR.

5.4.3 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.4 The contractor shall prohibit the use of keys 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.5 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.6 Access lock combinations are “CUI” and shall be protected from unauthorized personnel.

5.4.7 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.8 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 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.6 Location(s) of Work.

The work to be performed under this contract shall be performed at the contractor facility

5.6.1 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 Presidents’ Day Veterans Day Memorial Day Juneteenth Day

Thanksgiving Day Christmas Day

Independence Day

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

5.7 Records.

The contractor shall create, maintain and dispose of only those Government required records that are specifically cited in this PWS. 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.8 Data.

The Government has unlimited rights to all deliverables of this task order to include intellectual property rights.

5.9 Special Training, Certifications and Qualifications.

5.9.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 8570.01, "Information Assurance Training, Certification, and Workforce Management".

5.9.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 8570.01 “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.9.3 DoD 8570 Registration.

For those employees with privileged access to AFTAC systems, the contractor shall register all DoD 8570 certifications into the Defense Workforce Certification Application (DWCA) using the following web address:

https://www.dmdc.osd.mil/appj/dwc/index.jsp.

DWCA is the authoritative database of DoD Military, Civilian and Contractor personnel who hold active 8570 certifications used by the DoD CIO office to validate, monitor and report on the certification status of certified IA workforce members.

5.10 Contractor Manpower Reporting.

5.10.1 Contractors shall begin reporting manpower data relating to the performance services contracts into the System for Award Management (www.sam.gov).

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

Logistics management services;

Equipment related services;

Knowledge-based services;

Electronics & comms services.

5.10.3 SAM receives contract information from FPDS-NG. It will only enable reporting for entities with contracts that meet the above stated SCR thresholds.

5.10.4 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 reporting thresholds.

5.10.5 Steps for Submitting a Service Contract Report (SCR).

Go to www.sam.gov and log in.

https://www.dmdc.osd.mil/appj/dwc/index.jsp http://www.sam.gov/

Select Entity Registrations and then select Service Contract Reporting.

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.

Next, select Add for the service contract against which you want to create a Service Contract Report. Each service contract which meets the FAR Subpart 4.1703 reporting thresholds is displayed.

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:

5.10.5.1 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).

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

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

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.10.6 Annual Reporting. Reporting inputs will be for the direct labor executed during the period of performance (PoP) for each Government fiscal year (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 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.11 Kick-off Meeting and Periodic Progress Meetings.

The contractor shall conduct an initial kick-off meeting (15 of days) after contract award. 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 in their monthly status report. (CRDL A001 & A002 apply)

5.12 Contractor Travel.

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

The contractor shall travel in support of this contract in support of specific tasks to include attend meetings, conferences, and to provide training. Travel requirements shall be approved by Contracting Officer (CO) and COR during the travel approval process. All travel requirements (including destination, purpose, plans, agenda, itinerary, number and names of personnel, and dates) shall be pre-approved by the COR. Travel within the continental United States (CONUS) may be required in support of the PWS effort. Travel for this effort, if taken, will be in accordance with the Government Joint Travel Regulation (JTR). The Contractor shall prepare a Contractor Travel Cost Worksheet and will submit it to the COR for approval. All worksheets shall be accompanied by a cumulative list of travel and associated actual and estimated costs.

Reimbursement includes full travel costs and per diem reimbursement consistent with the JTR, and reimbursement of general and administrative expense as appropriate. Contractor shall submit a trip report within five (5) working days after completion of travel. Costs for travel shall be billed on a strictly cost reimbursable basis (no profit or fee added) 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. (CRDLs A001 & A002 apply)

5.13 Deliverables.

Reports and other data required in this PWS shall be submitted IAW the Contract Data Requirements List (CDRL) in Exhibit A of the contract.

CDRL

ITEM

CDRL

DESCRIPTION

PARA

REFERENCE

DELIVERY

SCHEDULE

A001 STATUS REPORT Section 2, 5.8, 5.9

Delivery by email is acceptable. Work progress status reports shall be provided monthly with first report due NLT fifteen (15) calendar days after end of TO’s 1st month period. Reports shall not be disseminated beyond AFTAC

A002 CONTRACTOR

FUNDS STATUS

REPORT

Section 2, 5.8, 5.9

Delivery by email is acceptable. Work progress status reports shall be provided monthly with first report due NLT fifteen (15) calendar days after end of TO’s 1st month period. Reports shall not be disseminated beyond AFTAC

A003 TECHNICAL

REPORT –

STUDY/SERVICES

Section 2 Draft shall be provided NLT fifteen (15) calendar days after completion of research.

Final report due NLT twenty (20) calendar days after draft submission. Reports shall not be disseminated beyond AFTAC

A004 SOFTWARE

PRODUCT

SPECIFICATION

(SPS)

Section 2 SPS shall be provided when the software development and testing are completed and NLT thirty (30) calendar days prior to end of Task Order POP.

A005 SOFTWARE USER

MANUAL (SUM)

Section 2 SUM shall be provided NLT the time of software delivery for implementation.

Reports shall not be disseminated beyond

AFTAC

A006 FINAL SCIENTIFIC

AND TECHNICAL

REPORT

Section 2 Report due NLT seven (7) calendar days prior to end of Task Order POP. Report shall not be disseminated beyond AFTAC

APPENDIX A - ACRONYMS AND ABBREVIATIONS LIST

Acronym/Abbreviation Definition

AF Air Force

AFB Air Force Base

CDRL Contract Data Requirements List

CFR Code Federal Regulation

CO Contracting Officer

COR Contracting Officer’s Representative

DOD Department of Defense

FAR Federal Acquisition Regulation

IAW In accordance with

NDA Non-Disclosure Agreement

OSHA Occupational Safety and Health Act

PBSA Performance Based Service Acquisition

PWS Performance Work Statement

QA Quality Assurance

QASP Quality Assurance Surveillance Plan

SS Services Summary

USAF United States Air Force

APPENDIX B - APPLICABLE PUBLICATIONS & INSTRUCTIONS

Compliance with all publications, regulations and operating instructions provided by the Government is required 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 is required to acquire and work on the latest version of the publication.

Publication/Instruction - Title Applicable Paragraph/Chapter

PWS

Paragraph

AFTAC General Security Classification Guide, 22 June 2023

Entire Document Applicable All