RFP Attachment 1 - MOSES II PWS.pdf

CUI

PERFORMANCE WORK STATEMENT (PWS)

FOR

MODELING, SOFTWARE, AND ENGINEERING SUPPORT II (MOSES II)

AIR FORCE TECHNICAL APPLICATIONS CENTER (AFTAC)

7 Aug 2024

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

1 DESCRIPTION OF SERVICES

1.1 INTRODUCTION

1.2 BACKGROUND

1.3 SCOPE

1.4 PERIOD OF PERFORMANCE

1.5 PLACE OF PERFORMANCE

2 SPECIFIC TASKS

2.1 OPERATIONS AND MAINTENANCE (O&M)

2.2 RESEARCH AND DEVELOPMENT (R&D)

2.3 ONSITE TECHNICAL SUPPORT

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

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

5.18 DELIVERABLES

APPENDIX A - ACRONYMS AND ABBREVIATIONS LIST

APPENDIX B – ESTIMATED O&M/R&D WORKLOAD DATA…………………………….33

APPENDIX C - MISSION EQUIPMENT LISTS……………………………………………….35

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.

During previous contracts, individual contracts provided scientific and technological support for requirements for research, development, maintenance, sustainment, and enhancement of complex systems through both on-site and off-site personnel. The suite of software applications was developed or acquired for Air Force Technical Applications Center (AFTAC) evaluators to collect, process, analyze mission data and generate scientific and technical reports. These applications include databases and tools needed to model terrestrial phenomenology with material interactions to include transport and dispersion, nuclear and industrial processes, and production. Software was developed to provide easy to use user interfaces for running applications and analyzing data on computer systems with Commercial Off-The-Shelf (COTS) and Government Off-The-Shelf (GOTS) tools.

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.

The objective of this contract is to acquire contracted services for Modeling, Software, and Engineering Support at AFTAC. 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 services.

The contractor shall provide qualified personnel, services, materials, equipment, supplies and facilities necessary to perform scientific and technical support and services needed during the life of the contract. Task requirements include, but not limited to, those listed in Section 2 of this PWS.

Specific task requirements will be further identified at the individual TO level.

1.4 Period of Performance.

The period of performance of this Indefinite Delivery Indefinite Quantity (IDIQ) contract shall include a base ordering period of five (5) years (1 Apr 25 – 31 Mar 30) with a two-and-a-half (2.5) year optional ordering period (1 Apr 30 – 30 Sep 32) for a total ordering period of seven-and-a-half (7.5) years.

This contract shall include FAR 52.217-8 Option to Extend Services to provide an additional six

(6) months of services if necessary.

1.5 Place of Performance.

The place of performance of this Indefinite Delivery Indefinite Quantity (IDIQ) contract shall be, for on-site support, at the Headquarters (HQ) building of AFTAC, located at Patrick Space Force Base (PSFB), Florida. Additional work on this contract may be performed at the contractor’s location at the approval of the Government, provided that there are no gaps in on-site support for employee vacation, leave, and Temporary Duty Assignment (TDY) periods.

2 SPECIFIC TASKS.

CDRLs A001 - A035 apply.

2.1 Operations and Maintenance (O&M).

2.1.1 The contractor shall maintain and sustain contract software across multiple AFTAC enterprise information infrastructures. A complete list of software will be provided in a Technical Data Package (TDP).

Software sustainment is the processes, procedures, people, material, and information required to support, maintain, and operate a Computer Software Configuration Item (CSCI), CSCI subsystem, supporting and associated software after implemented software deliveries. Software sustainment addresses other issues not always an integral part of maintenance such as documentation, deployment, operations, security, configuration management, training, defect tracking, COTS product management, and technology refresh.

Software maintenance is the process of modifying a CSCI, CSCI subsystem, supporting and associated code or script after Government acceptance to correct faults, improve performance or other attributes to meet and maintain minimum operating criteria, or adapt to a changed environment. Maintenance also includes updating dependencies with current versions that can be approved for operational use on government systems.

The environment includes multiple operating systems, applications, security configurations, standards, and policies at multiple classification levels, operating on hardware located on-premises and off-site, including cloud platforms. The components requiring integration and support include, but are not limited to, web servers, databases, commercial applications, scientific and statistical modeling software, and scripts written in various programming languages (e.g. FORTRAN, UNIX Shells, Python, Pearl, tcl/tk, JavaScript, PHP, Ruby, VBA, PowerShell, HTML, Extended Markup Language (XML), Keyhole Markup Language Zipped (KMZ)).

All the above systems shall be compliant with and operate according to AFTAC Information and Technology standards (Section 5).

The contractor shall sustain all contractor and integrated software and their interfaces for fully functioning operational status. Functionality that is operational prior to a maintenance or sustainment delivery shall not have any degradation in performance following the maintenance or sustainment action.

Mandatory compliance orders for software patches may be required at any time. Patches can include operating system patches for Microsoft Windows and Linux, security patches for all servers (e.g., web, application, database, etc.), middleware and support applications.

Enterprise upgrades scheduled annually or biannually depending on vendor release and Government approval can include Microsoft Office, Oracle Relational DataBase Management System (RDBMS), OpenText Content Server, Web & Application Server, Linux, cluster management software (Bright, at the date of this document), Moab, and Torque. The contractor shall maintain all contractor and integrated software and their interfaces to maintain fully functioning operational status.

Required Operational Status. The contractor shall respond to software problem calls and provide an assessment of the problem according to the following three precedence levels:

- URGENT (non-mission capable) within 1 business day.

- PRIORITY (partially mission capable) within 3 business days.

- ROUTINE (fully mission capable) within 7 business days

Software Patches – Patches shall be implemented within the following time period, and the contractor shall comply with the facility policies and procedures for delivery and implementation of software

- URGENT within 3 calendar days following initial assessment of the problem.

- PRIORITY within 7 calendar days following initial assessment of the problem.

- ROUTINE within 30 calendar days following initial assessment of the problem.

2.1.2 Enhancements to Existing Systems, Modeling Applications, and Databases.

The contractor shall enhance the tool sets for evaluation and exploitation and corresponding user access to provide accurate input and ensure the security, integrity, and quality of the data are maintained, pending funding availability. Examples of enhancements include expansion of databases to accommodate new data streams, increased accessibility, management, visualization, and analysis of information, as well as increased functionality, compatibility, efficiency in data manipulation.

Tasks may include, but are not limited to, data analysis and curation for applied data science and Artificial Intelligence (AI)/Machine Learning (ML) applications, including implementation of enhancements to increase data throughput and analysis speed through automation and reduction of manual, time-intensive processes. The contractor shall implement enhancements within Government approved task schedule following Government approval of the development approach.

Maintain, integrate, and enhance algorithms which leverage datasets and state-of-health information to forecast future collection or analysis system failures, optimize acquisition of spare parts, and prioritize preventative maintenance. This will drive future procurement strategies of in-field, laboratory, or Information Technology (IT) infrastructure.

2.1.3 Data Quality Assurance (QA) and Quality Control (QC).

The contractor shall perform periodic queries and analyses to monitor and assess the quality of radionuclide data submitted to the mission area by its supporting laboratories.

The contractor shall evaluate lab data for trends and biases within, and between, laboratories through analysis of QA standards and mission sample measurements. The contractor shall report findings to the mission area leadership and summarize and present analytical results at selected working group meetings upon request of the Government.

The contractor shall provide analytical and statistical support to identify and diagnose data quality problems as part of these evaluations.

The contractor shall evaluate mission data for trends and biases within, and between, various data sources or providers. Types of data for QA/QC include analytical laboratory results and multi-phenomena sensor data, from government, commercial, academic, and/or publicly available sources. The contractor shall report the results to the mission managers and summarize and present the results at selected working group meetings upon request of the Government. The contractor shall provide analytical and statistical support to identify and solve data problems as part of these evaluations.

2.1.4 Information System Management and Integration.

The contractor shall provide software and IT support for mission operations, systems, applications, and data throughout the Government’s large heterogeneous IT infrastructure in an effort to provide continuous, efficient and effective performance. The contractor shall integrate data and tools into the AFTAC enterprise IT architecture to ensure flexible and interconnected access to support rapid algorithm prototyping, customized analysis tasks, and test/evaluation procedures to meet operational mission needs. The contractor shall provide support for on-site mission specific IT applications and resource management. The contractor shall provide AFTAC Information Management System (AIMS) technical support to include routine AIMS administration, data administration, and user assistance of AIMS clients and servers. The contractor shall function as first level technical support for all contract delivered applications to maintain all AIMS software subsystems, component software applications, models, and databases in continuous operational status. Specific software change requests for AIMS and its associated programs shall be requested through the Government. Functionality that is operational prior to a maintenance or sustainment shall not have any degradation in performance after the maintenance or sustainment action. These requests will be prioritized by the Government and submitted to the contractor to allow the Government to monitor ongoing and newly prioritized tasking. As directed by the Government, the contractor will convert legacy software tools to full web applications consistent with the modernized AIMS architecture. The contractor shall provide the results of technical interchange meetings to the Government.

Nuclear Data Integration: The contractor shall integrate nuclear data into the AIMS system and provide functionality for data mining, visualization, and exploitation.

Modeling System Integration: The contractor shall test and integrate modeling software and databases from external providers for use on AFTAC systems. Providers include government-owned, commercial, and open-source entities. Relevant weather models include: Weather Research and Forecasting (WRF), Global Forecast System (GFS), Land Information System (LIS), Ground to Space (G2S). Relevant transport and dispersion models include: the EMS Decision Aid Product Tool (EDAPT), Second-order Closure Integrated Puff (SCIPUFF) model, Sensor Placement Optimization Tool (SPOT), and Hazard Prediction Analysis Capability (HPAC). Relevant hydrological/geospatial models include: the GeoWatch vehicle mobility modeling system and the Hydrological Execution Framework (HEF).

Transition Nuclear Incident and Report Tools: The contractor shall integrate the mission area incident and report process into the AIMS system and provide functionality for workflow management, evaluation documentation and reporting automation.

2.1.5 Data Curation and Query Support.

The contractor shall perform database updates from transaction files of the mission area sample collections and laboratory analyses and diagnose and resolve data-ingest issues.

The contractor shall devise and execute data queries to summarize analysis results in accordance with the mission area formats and conventions and prepare graphical and tabular summaries for use in evaluation and reporting. The contractor shall perform ad hoc queries of the mission area sample data, post-process query results, prepare inputs for and/or evaluate outputs from background-estimation techniques or other statistical models upon request by the Government in response to real-world events.

2.1.6 Meteorological Special Studies.

The contractor shall provide scientific services comprising meteorological modeling to accomplish special studies of regions as specified by the Government. The contractor shall perform meteorological data quality assessments and screen data for suitability in subsequent analyses, perform queries of mission sample results, and execute and evaluate the outputs from mesoscale meteorological models and atmospheric transport and dispersion models as necessary to assess or refine effluent background models, identify mission samples with radionuclide concentrations significantly distinguished from background levels, evaluate specified source/receptor relationships, characterize climatological effects on transport, explain observed patterns of interest in mission sample data, or address other special study objectives.

2.1.7 Support for Chemical Dynamics Working Group (CDWG)

The contractor shall provide administrative and logistical support for CDWG meetings and technical exchanges. The CDWG, comprised of members from academia, industry, and government, collaborates to enhance accuracy of AFTAC modeling capabilities through coordinated experimental and theoretical data generation, methods development, and Verification and Validation (V&V) efforts.

2.1.8 Special Tasking.

The contractor shall support special in-scope O&M tasks as specified by the Government, pending funding availability.

2.2 Research and Development (R&D).

2.2.1 Model Development.

The contractor shall develop computationally efficient, multi-phenomena, source, and propagation models compatible with statistical processing methods. Development activities will include researching new and emerging modeling approaches, new algorithms, code modifications, integration of new capabilities into SPOT and the Database of Modeling and Emissions (DOME), synthetic/experimental verification and validation, and other activities to enable transition of capabilities to operations.

R&D activities will include, but are not limited to modeling of meteorology, hydrology, chemical or nuclear engineering processes, atmospheric transport and dispersion, seismo-acoustic propagation, and electromagnetic propagation at global to local spatial scales and time scales ranging from climatological (years) to short duration (minutes).

2.2.2 Special Tasking.

The contractor shall support special in-scope R&D tasks as specified by the Government, pending funding availability

2.2.3 Environmental Chemistry Modeling.

The contractor shall research, develop and implement modeling algorithms and input data to predict the environmental fate of compounds of interest in air, soil, water, and various surfaces (e.g., common building materials, vegetation) for use with existing transport and dispersion models (EDAPT, SPOT) and ground fate modeling tools such as the Windows Of Opportunity (WOOs)

The contractor shall research, develop, and employ computational chemistry techniques to develop methodologies for determining chemical reaction mechanisms, reaction rates, and reaction product pathways for compounds of interest. The contractor shall enter the calculated reaction rates into models. The contractor shall use existing and newly developed methodologies to calculate chemical and physical property data for compounds of interest, as defined by the Government.

The contractor shall obtain reaction rate constants and identify key reaction products for chemicals of interest in various environmental media (e.g., in air, in water, in soils, on surfaces) using experimental methods. Experimentally determined reaction rates and degradation compounds identified shall be used in the development of reaction mechanisms for use in modeling applications.

2.2.4 Spatial and Temporal Variation of Parameters.

The contractor shall identify, recommend, and develop methodologies for including the capability to vary spatial and temporal parameters within the modeling domains.

The contractor shall research industries in specific cities or regions to characterize the local environment and to identify production, research, and development, and/or other facilities that may produce confounding emission sources of effluents. The contractor shall characterize unique chemical and/or nuclear effluents, compounds of interest, and potential degradation products for inclusion into existing databases. Cities or regions of interest will be identified and prioritized by the Government.

2.2.5 Statistical Algorithms and Advanced Analytic Methods.

The contractor shall develop new methods to identify correlations, trends, and anomalies in large datasets using statistical algorithms and machine learning approaches. Developed methods will be agnostic to the specific types of data and can be leveraged against a multitude of problem sets.

The contractor shall perform analyses to quantify the sensitivity of various models including, but not limited to, numerical weather prediction models, transport and dispersion models, chemical engineering models, and chemical fate models to variations of their respective inputs, including environmental quantities, input parameters, and numerical tolerances. Relevant weather models include: WRF, GFS, LIS, and G2S.

Relevant transport and dispersion models include: EDAPT, SCIPUFF, SPOT, and HPAC.

The contractor shall use the sensitivity analyses to facilitate efforts to streamline simulation processes and models.

The contractor shall research, develop, evaluate, and integrate advanced statistical methods into AFTAC data analysis workflows within the broad application of Data Sciences, including, but not limited to multivariate analysis, Bayesian statistics, and AI/ML techniques.

2.2.6 Scientific Support.

The contractor shall conduct scientific investigation, data analysis and research and development support necessary to meet short notice requirements. Efforts required by this activity could include investigation and development of a new capability in a very short timeframe (i.e., weeks) or conduct a detailed scientific investigation (i.e., months) to support or clarify priority data interpretation needs by the Government.

2.3 Onsite Technical Support

2.3.1 Scientific Services Support.

The contractor shall provide onsite (i.e. work performed in the AFTAC HQ offices) scientific services support as specified by the Government for five interrelated operational components supporting the mission area: 1) Collections, 2) Sample Analysis & Technical Assessment, 3) Meteorological Modeling and Analysis, 4) Fate Parameter Evaluation, and 5) Evaluation & Reporting. As appropriate to the task, the contractor shall perform database queries or otherwise collect data from mission-relevant sources, post-process and summarize data, execute and evaluate mechanistic and statistical models, devise or adapt scripted analytics (in R, Python, or other suitable environments), or apply other scientific/technical expertise in statistics, meteorology, chemistry, physics, or nuclear engineering and/or modeling to analyze data and document analysis results.

2.3.2 Accomplish data analysis and lessons learned development.

2.3.3 Provide scientific technical reports for reviews, evaluations, and recommendation on subjects of highly specialized areas of concern.

2.3.4 Provide reviews, evaluations, and recommendations on subjects of highly specialized areas of concern.

2.3.5 Brief customers and present conclusions to multi-disciplined personnel regarding chemical engineering and chemical and meteorological analysis. The contractor shall develop and deliver briefing charts to the Government.

2.3.6 Perform specialized data evaluation and interpretation of laboratory results with respect to specific chemical processes to include atmospheric transport and degradation, soil deposition and degradation, and hydrology.

2.3.7 Perform specialized evaluation and interpretation of seismo-acoustic data.

2.3.8 Conduct chemical engineering, nuclear engineering, and meteorological evaluations as specified by the Government. The contractor shall provide preliminary feedback and recommendations within specified time (days/hours) of tasking by the Government.

2.3.9 Conduct geophysical evaluations as specified by the Government. The contractor shall provide preliminary feedback and recommendations within specified time (days/hours) of tasking by the Government.

2.3.10 Assess the significance of trace amounts of specific chemical compounds to include all possible precursor and degradation chemicals and interpret the data to characterize the chemicals.

2.3.11 Identify and address key operational mission gaps by recommending maintenance and enhancements of source term models.

2.3.12 Attend technical reviews, meetings, working groups, and meetings. The contractor shall generate and deliver meeting minutes to the Government for review and coordination.

The contractor may act as the meeting facilitator and recommend specific actions to resolve scientific or technical issues as specified in individual TOs.

2.3.13 Provide support to include performing technical studies, investigations, or analyses, special studies, performance analysis, new technology evaluation, and system capabilities analysis.

2.3.14 Prepare scientific or technical presentations and briefings on topics within the scope of this PWS as specified in individual TOs.

2.3.15 Perform specialized data evaluation with respect to specific atmospheric transport processes to include effluent decay and deposition, atmospheric stability, and wind patterns.

2.3.16 Apply scientific methods to study, analyze, and interpret complex laboratory data using computational models as well as data handling and display tools.

2.3.17 Conduct special studies on topics within the scope of this PWS but not specifically identified within this PWS as specified in individual TOs.

2.3.18 Identify, document, and notify the Government of actual or potential contractor program management problems and deficiencies and report unresolved problems to the Government within one business day.

2.3.19 Support periodic meetings and conferences convened at the direction of the Government. All travel shall be conducted In Accordance With (IAW) PWS Para 5.17.

2.3.20 Mission Area Web Tools.

The contractor shall maintain and enhance the operation of the current suite of Nuclear Debris Collection & Analysis (NDC&A) Web tools on requested networks. The NDCAWeb suite of tools includes Event Correlation Tool (ECT), Sample Export Tool (SET), Airborne Data Analysis Plot Tool (ADAPT), RMSMAN ZESPA Tool (RZT), and Quality Check Tool (QCT). The contractor shall also develop additional web interfaces for the NDC&A, National Technical Nuclear Forensics (NTNF), RMSMAN, and ZESPA database schemas as required by the government.

2.3.21 Mission Area Data Integration.

As required, the contractor shall develop tools to integrate appropriate mission areas data with other mission areas. To illustrate (but not limit), such software could be a service that harvests and transfers relevant data between two databases / schemas or an interface that allows a user to rapidly gather needed data, which it exports in a specified, custom format.

2.3.22 Sampler Operations and Maintenance Information System (SOMIS) Process.

The contractor shall maintain and enhance the software processes supporting: (1) SOMIS software application, (2) SOMIS/SODS, RMSMAN, and ZESPA database schemas, (3) dataflow management software, i.e., Niagara Falls Information (NiFi), and (4) processing function of the mission area laboratory data. Specific capabilities include the processing of Materials mission sensor state of health data, the Maintenance Information System (MIS) function, and new solutions to enhance Condition Based Maintenance (CBM+) by enabling data discoverability across varying monitoring phenomenologies. The contractor shall leverage Artificial Intelligence & Machine Learning (AI/ML) capabilities and cloud infrastructure functionality into the SOMIS process to support future operations. The contractor shall build and maintain the processes that increase efficiency of current maintenance operations and implements improved software design that delivers flexibility to the maintenance support needs.

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.

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.

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

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

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 mission Governing Bodies 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 mission CMB 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 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 mission CMB. 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 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 (if the code is unclassified) and provide the software source code for successful procession the CI pipeline. 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 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 COTS with support or GOTS software with restricted source code releasability, are not an acceptable delivery.

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

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

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

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 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.2 Steps for Submitting a SCR.

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

5.11.2.2 Select Entity Registrations and then select Service Contract Reporting.

5.11.2.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.2.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.2.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.2.6 Report any required Tier 1 subcontractor information by selecting the Add Tier 1 Subcontract Information button.

5.11.2.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.3 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 http://www.sam.gov/ 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 Government. 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.

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

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.

5.16.1 The contractor shall attend an initial kick-off meeting 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.

5.17 Contractor Travel.

5.17.1 The contractor may be required to travel as defined in specific TOs. All travel requirements (including destination, purpose, plans, agenda, itinerary, number and names of personnel, and dates) shall be pre-approved by the contracting officer and COR. Contractor shall submit a trip report upon completion of travel. Costs for travel shall be billed on a strictly cost reimbursable basis 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. CDRLs A002 and A021 apply.

5.18 Deliverables.

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

CDRL

ITEM

CDRL DESCRIPTION PARA

REFERENCE

DELIVERY

SCHEDULE

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

A001

Status Report

Section 2 Government will complete review within fifteen (15) calendar days of draft receipt.

Contractor will have fifteen (15) calendar days from receipt from government to submit final.

A002

CONTRACT FUNDS STATUS

REPORT (CFSR)

Section 2 and 5 Forty-five (45) calendar days after contract award. Due 15th calendar day of each month.

one electronic copy.

A003

SOFTWARE PRODUCT

SPECIFICATION (SPS)

Section 2 Government will complete review within fifteen (15) business days of draft receipt -contractor will have fifteen (15) business days from receipt from government to submit final.

Report due thirty (30) calendar days prior to task order annual anniversary or close whichever is first.

A004

SOFTWARE USER MANUAL

(SUM)

Section 2 Government will complete review within fifteen (15) business days of draft receipt -contractor will have fifteen (15) business days from receipt from government to submit final.

Report due thirty (30) calendar days prior to task order annual anniversary or close whichever is first.

A005

SOFTWARE

REQUIREMENTS

SPECIFICATION (SRS)

Section 2 Contractor format acceptable.