RFP Attachment 8 - MOSES II Task Order 1 PWS_30 Jul 2024.pdf

PERFORMANCE WORK STATEMENT (PWS)

FOR

MODELING, SOFTWARE, AND ENGINEERING SUPPORT (MOSES) II

Task Order (TO) 1 - AFTAC Information Management System (AIMS) Enhancements, Computation/Validation Studies, Cloud Deployment, and Subject Matter Expertise (SME)

Support

AIR FORCE TECHNICAL APPLICATIONS CENTER (AFTAC)

24TH Analysis Squadron

30 Jul 2024

1 DESCRIPTION OF SERVICES

1.1 INTRODUCTION

1.2 BACKGROUND

1.3 SCOPE

1.4 PERIOD OF PERFORMANCE

2 SPECIFIC TASKS

2.1 AIMS ENHANCEMENTS (CDRLS A001, A002, A003, A010, A024, AND A031-A035

APPLY) 5

2.2 COMPUTATIONAL / VALIDATION STUDIES (CDRLS A001, A002, A003, A010, AND A024

APPLY) 5

2.3 CLOUD DEPLOYMENT (CDRLS A001, A002, AND A031 – A035 APPLY)

2.4 SME SUPPORT (CDRLS A001 AND A002 APPLY)

3 SERVICES SUMMARY (SS)

4 GOVERNMENT FURNISHED PROPERTY AND SERVICES

4.1 SERVICES

4.2 FACILITIES

4.3 UTILITIES

4.4 PROPERTIES

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 (CDRL A001 APPLIES)

5.17 CONTRACTOR TRAVEL (CDRLS A001, A002, AND A021 APPLY)

6 DELIVERABLES

APPENDIX A - ACRONYMS AND ABBREVIATIONS LIST

APPENDIX B - ESTIMATED WORKLOAD DATA

SECTION 1

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

Air Force Technical Application Center (AFTAC) Environmental Modeling and Simulation (EMS) Program models various phenomena and events that occur in the atmosphere and on the ground.

1.3 Scope

This project will fund four O&M subtasks to enhance the AFTAC Information Management System (AIMS), provide SME across multiple physical science and engineering disciplines (chemistry, chemical engineering, nuclear engineering, meteorology, etc.), perform computational / validation studies, and deploy EMS tools to the cloud.

1.4 Period of Performance

The period of performance shall be 12 months beginning from the date of contract award.

SECTION 3

2 SPECIFIC TASKS

2.1 AIMS Enhancements (CDRLs A001, A002, A003, A010, A024, and A031-A035 apply)

2.1.1 The on-site contractor(s) shall identify Java clients and specify a suggested priority order for converting to an approved web framework based on JavaScript, HTML 5, and Cascading Style Sheets (CSS) like Vue, based on usage and ease of code conversion.

2.1.2 The on-site contractor(s) shall convert at least two (2) government selected applications to an approved web framework as contained in section 2.1.1 of the IDIQ.

2.1.3 The on-site contractor(s) shall fully test and deliver source code, clean security scan results, documentation, and installation plan based on an approved delivery schedule.

The contractor will support the installation of the application into AFTAC’s Continuous Integration (CI) pipeline and on the Joint Worldwide Intelligence Communication System (JWICS) Common Production Environment (CPE) pending software approval is obtained within the period of performance (A003, A010, A024, and A031-A035).

2.2 Computational / Validation Studies (CDRLs A001, A002, A003, A010, and A024 apply)

2.2.1 The contractor shall perform calculations for at least one (1) government defined chemical compound.

2.2.2 The contractor shall update model parameters for target compounds into the modeling system as contained in section 2.1 of the IDIQ.

2.2.3 The contractor shall validate existing model parameters by producing measurements for at least one (1) chemical property for at least one (1) Compound of Interest (COI) to support operational needs.

2.2.4 The contractor shall integrate validation data into on-site modeling suites.

2.2.5 The contractor shall use validation data to enhance the property estimation tool for chemical compounds.

2.2.6 The contractor shall deliver validation and calculated data with the monthly report.

2.2.7 At the contractor facility, the contractor shall fully test the Government-owned GeoWatch (as described in the TDP) modeling system. The contractor will provide clean security scan results, documentation, and installation plan to AFTAC. The Government will provide source code (A010, A024).

2.2.7.1 The contractor will support the installation of the application into AFTAC’s CI pipeline and on the High Performance Computing (HPC) pending software approval is obtained within the period of performance (A003, A010, A024).

2.3 Cloud Deployment (CDRLs A001, A002, and A031 – A035 apply)

2.3.1 The below sections may be performed on or off site depending on mission needs.

2.3.2 The contractor shall identify and recommend three of several Government-provided projects to be selected for the pilot cloud deployment project.

2.3.3 The contractor will work with the government to develop a plan to deploy the selected applications to the Amazon Web Services (AWS) cloud (i.e. lift and shift, refactoring, etc.).

2.3.4 The contractor shall assess the selected applications and their dependencies and identify any potential issues or risks that may affect the cloud migration, document them, and provide them to the customer.

2.3.5 The contractor will work with the government to determine the best way to upload large binary data files, and then provide access to these files using Public Key Infrastructure (PKI) authentication.

2.3.6 The contractor shall examine and identify what is necessary to port the selected applications to the high-side cloud and document their findings.

2.3.7 The contractor will investigate the use of AFTAC’s Data Fabric software environment – the IntelliEarth Integrator (IEI) – in the process of migration to the cloud, based on the information supplied by the government.

2.4 SME Support (CDRLs A001 and A002 apply).

2.4.1 The on-site contractor(s) shall provide subject matter expertise (chemical engineering, nuclear engineering, and meteorological) IAW section 2.3.8 of the IDIQ.

2.4.1.1 SME(s) shall support technical discussions/presentations to external customers for at least two (2) data analysis and/or modeling projects.

2.4.2 The on-site contractor(s) shall provide technical expertise and support enhancements of at least one (1) analytical approach and method to improve current environmental modeling and simulation tools.

2.4.3 The on-site contractor(s) shall create training materials for any enhancements made to analytical approaches and methods. These training materials will be compatible with on-site resources.

2.4.4 The on-site contractor(s) shall continue to implement the plan to run the Weather Research and Forecasting (WRF) model, the EMS Decision Aid Product Tool (EDAPT), the Sensor Placement Optimization Tool (SPOT), and other models necessary to perform standard analysis projects on the DoD Super Computing Resource Center Top Secret (TS) computing resources by deploying and/or testing at least two (2) models with necessary input data to a mission-dictated HPC system. Any information on current analysis models needed to help with this implementation will be made available to the contractor.

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

All Deliverables

The contractor shall provide all CDRLs within two (2) working days of due date with no more than one (1) late CDRLs per three (3) months. The contractors shall deliver complete and quality CDRLs with no more than one (1) CDRL per three (3) months requiring Government corrections for content or quality.

SS # 2

Comply with all security requirements Section 5 Zero Security Violations.

SS # 3

Respond to software problem calls by mission impact as determined by the

Government

Section 2

Urgent response and initial diagnoses no later than one (1) business day of notification Priority response and initial diagnoses no later than three (3) business days of notification Routine response and initial diagnoses no later than seven (7) business days of notification.

SS # 4

Install software patches within scheduled time period

Section 2

Urgent software modifications implemented no later than three (3) calendar days of notification Priority software modifications implemented no later than seven (7) calendar days of notification Routine software modifications implemented no later than thirty (30) calendar days of notification.

Performance Objective PWS PARA Performance Threshold

SS # 5

Provide accurate and timely technical and analytical support

Section 2

Contractor shall receive no more than two

(2) validated customer complaints or corrective action requests per task order.

Contractor shall successfully resolve customer complaints Within fourteen (14) calendar days of receipt with no exceptions.

SS # 6

Provide software configuration management

Section 2

Modifications are made in accordance with ISO-12207 and other pertinent

Government requirements made within ten (10) working days of expected completion.

SS # 7

Meet all stated baseline requirements on-time and within approved schedule

All Deliverables & Services

Implement in accordance with individually defined requirements for each paragraph listed. Software deliveries shall have no more than five (5) defects resulting in Partial Mission Capable (PMC). Zero (0) defects resulting in Non-

Mission Capable (NMC).

SECTION 5

4 GOVERNMENT FURNISHED PROPERTY AND SERVICES.

4.1 Services.

No Government furnished services will be provided.

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

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

4.4 Properties.

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

5.1.2 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 the aforementioned development process, existing applications, components, and platforms is preferred over creating custom solutions.

5.1.3 Software development shall make good faith efforts to align software solutions to 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 as soon as they are identified. (Reference Attachment X, “Software Development Strategy Document”).

5.1.4 All software developed for AFTAC, except software, hardware, processes and services that cannot be supported such as 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 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 Government has the ability to rebuild and deploy the system in the future regardless of the contractor. The contractor will develop 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 Oracle Docker 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 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 (CDRL A004) 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 run by a Government employee on AFTAC systems and it produces the results for which the software was developed.

5.2 Contractor Identification in the Government Workplace.

5.2.1 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 (TS) security clearance and be Intelligence Community Directive (ICD) 704 eligible with a current T5 investigation 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 HQ (Address Below) or contractor facility based on the needs outlined in the individual TOs.

AFTAC HQ

1020 South Patrick Drive

PSFB, 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 System for Award Management (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 Service Contract Reporting (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.

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

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 Department of Defense (DoD) Information System shall receive initial Information Awareness (IA) orientation as a condition of access and thereafter shall complete annual IA refresher awareness, as required by DoD Directive 8570.01, "Information Assurance Training, Certification, and Workforce Management."

5.15.2 DoD 8570 Registration.

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

https://dwp.dmdc.osd.mil/dwp/app/main.

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

5.16 Kick-off Meeting and Periodic Progress Meetings (CDRL A001 applies).

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 (CDRLs A001, A002, and A021 apply).

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.

The following table identifies all known travel requirements.

6 Deliverables.

Reports and other data required in this PWS shall be submitted IAW the CDRLs in Exhibit A of this task order contract.

CDRL

Data Item Number

Data Item Description

PWS

Para.

Delivery Schedule

A001

DI-MGMT-

80368A

Status Report Section 2 Due 15th Calendar Day of Each Month

Travel Purpose

Destination Number of

Trips (Estimated)

Number of Contractor Personnel

(Estimated)

Travel Dates (Estimated)

Duration of Travel (Days)

Technical Discussions / Training

Washington, DC

3 2 May, July, September

Lab Visit & Program Review

Columbus, OH

1 2 April 2

Technical Discussions / Training

Washington, DC

1 1 October 3

Data Item Number

Data Item Description

PWS

Para.

Delivery Schedule

A002

DI-MGMT-

81468

Contract Funds Status Report

(CFSR)

Section 2 Due 15th Calendar Day of Each Month

A003

DI-IPSC-

81441A

SOFTWARE

PRODUCT

SPECIFICATION

(SPS)

Section 2 Due 30 calendar days prior to task order annual anniversary or close, whichever is first.

A010

DI-IPSC-

81428A

SOFTWARE

INSTALLATION

PLAN (SIP)

Section 2 Due 10 calendar days prior to software delivery.

A021

DI-MISC-

80508B

TRIP REPORT Section 2 Trip report shall be delivered within 10 business days of return from each visit.

A024

DI-MCCR-

80700

COMPUTER

SOFTWARE

PRODUCT END

ITEM

Section 2

Minimum distribution shall include drafts and finals to AFTAC/SDB as appropriate. Other distribution requirements will be identified in individual CDRL. Deliveries shall be provided electronically on a CD or on Government furnished equipment. A letter of transmittal shall accompany both drafts and final reproducible copy.

A031

DI-MGMT-

81644B V2

OV-1

DoD Architecture Frameworks V2 Viewpoints and Models OV-1

Section 2 Shall be provided before the end of the task order.

A032

DI-MGMT-

81644B V2 StdV-1

DoD Architectures Frameworks Version 2 Viewpoints and Models StdV-1

Section 2 Shall be provided before the end of the task order.

A033

DI-MGMT-

81644B V2

SV-1 - SV-5

DoD Architectures Frameworks Version 2 Viewpoints and Models SV-1 - SV-

Section 2 Shall be provided before the end of the task order.

Data Item Number

Data Item Description

PWS

Para.

Delivery Schedule

A034 DoDAF V2

DIV-1 -

DIV-3

DoD Architectures Frameworks Version 2 Viewpoints and Models DIV-1 -

DIV-3

Section 2 Shall be provided before the end of the task order.

A035 DoDAF V2 SvcV-1 - SvcV-5

DoD Architectures Frameworks Version 2 Viewpoints and Models SvcV-1 - SvcV-5

Section 2

Shall be provided before the end of the task order.

APPENDIX A - ACRONYMS AND ABBREVIATIONS LIST

Acronym/Abbreviation Definition

AF Air Force

AFB Air Force Base

AFS Air Force Station

CDRL Contract Data Requirements List

CFR Code Federal Regulation

CLINT Continuous Laboratory Improvement in Nuclear Technology

CO Contracting Officer

COR Contracting Officer’s Representative

DOD Department of Defense

FAR Federal Acquisition Regulation

GSSCG Security Classification Guide

IAW In accordance with

NDA Non-Disclosure Agreement

OSHA Occupational Safety and Health Act

PBSA Performance Based Service Acquisition

PNNL Pacific Northwest National Laboratory

PWS Performance Work Statement

QA Quality Assurance

QASP Quality Assurance Surveillance Plan

QC Quality Control

RPMAP Reactor Products Mission Advisory Panel

RPP Reactor Products Program

SS Services Summary

STEM Spectrometry Technical Exchange Meeting

TWG Technical Working Group

USAF United States Air Force

APPENDIX B - ESTIMATED WORKLOAD DATA

The historical workload data provided is for informational use only and is based upon historical data. Contractor shall propose based on their own technical approach.

Tasking for O&M:

Off-Site Support Item Name Estimated Quantity 1 Program Manager 300 2 Security 200 3 Chemical Engineer (Principal) 400 5 Chemist (Principal) 400 6 Chemist (Sr) 800 7 Chemist (Mid) 800 8 Chemist (Jr) 650 10 Meteorologist (Mid) 440

SW Development Engineer (Principal)

12 SW Development Engineer (Sr) 800 13 SW Development Engineer (Mid) 1,200 14 SW Development Engineer (Jr) 1,200 15 SW Test Engineer (Sr) 1,000 16 SW Test Engineer (Mid) 1,000

Total 9,790

On-Site Support Item Name Estimated Quantity 1 Chemical Engineer (Sr) 1,000 2 Meteorologist (Principal) 200

Total 1,200

APPENDIX C - 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 GSSCG 22 Jun 23 Entire document applicable Section 2