SAET_Draft PWS_22 Jul 2025.pdf

Performance-Based Work Statement (PWS) for the

Sensor Agnostic Emulator and Trainer

(SAET) and Signal Generator xx Dec 25

CONTRACT NUMBER: TBD

TASK ORDER: TBD

Prepared by AFLCMC/C3IA

750 Third Street Robins AFB, GA 31098-1670

DISTRIBUTION STATEMENT D. Distribution authorized to the Department of Defense and U.S. DoD contractors only (Critical Technology) (5 October 2022). Other requests shall be referred to AF DCGS Data Management Office, AFLCMC/C3IA, 235 Byron St., Suite 19A, Robins AFB, GA 31098-1670

WARNING – This document contains technical data whose export is restricted by the Arms Export Control Act (Section 2751 of Title 22, United States Code) or the Export Control Reform Act of 2018 (Chapter 58 Sections 4801-4852 of Title 50, United States Code). Violations of these export laws are subject to severe criminal penalties. Disseminate in accordance with provisions of DoD Directive 5230.25 and DoD Instruction 2040.02.

HANDLING AND DESTRUCTION NOTICE - Comply with distribution statement and destroy by any method that will prevent disclosure of the contents or reconstruction of the document.

REVISION SUMMARY

Revision Date Description Affected Pages/Para.

Contents

1.0 Description of Services:

1.1 Objective(s):

1.2 Benefit to United States Air Force (USAF):

1.3 Background:

2.0 Services Summary:

3.0 Government Property

3.1 Contractor Responsibility:

3.1.1 Protection of Information: Controlled Unclassified Information (CUI)

3.2 Government Property to be Provided:

3.2.1 Additional Property Access of GFE/GFI

3.3 Base Support:

3.4 Reporting of Government Property:

3.5 Loss of Government Property

3.5.1 Definition of Loss of Government Property:

3.5.2 Reporting Loss of Government Property:

3.5.3 Return or Retention of Government Property:

4.0 Technical Requirements

4.1 Period and Place of Performance

4.1.1 Contract/Order Period of Performance:

4.1.2 Place of Performance:

4.2 Configuration and Data Management:

4.2.1 Configuration Identification:

4.2.2 Configuration Baselines:

4.2.3 Configuration Change Management:

4.2.4 Data Management:

4.2.5 Technical Data:

4.2.5.1 Installation and Testing:

4.2.5.2 Software Deliverable:

4.3 Contract Data Requirements List (CDRL):

4.3.1 Quality of CDRL Deliverable:

4.3.2 Receipt of CDRL Deliverable:

4.3.3 Limitations and Performance Criteria:

4.3.4 Data Accession List:

4.3.5 Contractor’s Program Multi-Functional Team (MFT):

4.3.6 Deficiency Reports (DRs):

4.3 Material Procurement:

4.4 Funding:

4.5 Personnel:

4.6.1 Personnel Report:

4.8 Schedule:

4.9 Specific Work to Be Accomplished:

4.10 Sustainment:

4.11 Program Management and Administrative Support:

4.12 Engineering Estimates:

4.13 Engineering Services:

4.13.1 Engineering and Testing:

4.13.2 Specific Tasks:

4.13.3 System Engineering/Installation Service:

4.13.4 Security Engineering:

4.14 System Support:

4.15 Packaging:

4.16 Commercial Asset Visibility-Air Force (CAV-AF):

4.17 Holidays and Facility Closings:

5.0 Technical Data:

5.1 Configuration Management:

5.2 Test Support:

5.3 Acceptance Testing (AT), Integrated Acceptance Testing:

5.4 Team Demonstrations:

5.5 Quality Assurance Program:

5.5.1 Quality Management System (QMS):

5.7 Special Studies:

5.9 Inspection of Services:

5.10 Cybersecurity Requirements:

5.11 Travel:

6.0 General Information

6.2 Security Requirements

6.2.1 Security Regulations:

6.2.2 Operations Security (OPSEC):

6.2.3 Cybersecurity:

6.2.3.1 Vulnerability Management Plan:

6.2.3.2 Software Patching Management Plan:

6.2.3.3 Third (3rd) Party Software Management Plan:

6.2.3.4 Certificate to Field (CtF):

6.2.3.5 Plan of Action and Milestones (POA&M):

6.2.4 Communications Security (COMSEC):

6.2.5 Security Clearance:

6.2.6 Security Incident or Violation:

6.2.7 Access to Government System(s):

6.2.8 Access to Government Facilities or Military Installations:

6.2.8.1. Access to Robins Air Force Base (AFB):

6.2.8.2 Identification (ID) Card/Badge

6.2.8.3 Physical Security:

6.2.8.4 Key Control:

6.2.8.5 Lock Combinations:

6.2.8.6 Common Access Card (CAC):

6.3 Information Assurance Requirements:

6.4 Environmental Management System (EMS):

6.5 Affirmative Procurement Programs (APP):

6.6 Safety Requirements

6.6.1 Contractor Environmental, Safety, and Occupational Health Compliance:

6.6.2 Contractor Safety & Health Program/Plan:

6.6.3 Mishap Notification/Investigation:

6.6.4 Voluntary Protection Program (VPP):

6.7 Inspection of Services:

6.8 Trafficking in Persons:

6.9 Service Contract Reporting:

6.10 Invoicing/Payment and Receipt/Acceptance:

6.11 Associate Contractor Agreements:

6.12 Quality Control Plan/Quality Management System (QMS):

7.0 Appendices

7.1 Appendix A: References

1.0 Description of Services:

This Performance-Based Work Statement (PWS) describes the services required to provide support for the Air Force Distributed Common Ground System (DCGS) that is used for collection, correlation of data, and collaboration of signals of interest from airborne, ground, and other systems in order to provide near real time actionable intelligence to the war fighters.

Development efforts include enhancing and sustaining the capability of the systems through changes to the software. It also provides for the expansion of the existing systems/sites in order to meet overall DCGS requirements. The Contractor shall support Government configuration control, development, and integration of the Open Architecture (OA) Identification, and Authorization baseline. Finally, it allows for the incorporation of new capabilities that may be developed and required in order to meet changing DCGS mission requirements. This system may also be deployed to the National Mission Partner Network to support operations and training there.

This is a non-personal services contract. The Government shall 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 Procuring Contracting Officer (PCO) immediately if they perceive any actions constitute personal services. These services shall not be used to perform any inherently governmental functions.

All tasks will be specifically directed by individual Task Descriptions (TD) issued under an Indefinite Delivery, Indefinite Quantity (IDIQ) contract. Major tasks include program management and support functions including Agile Project Management, Finance, Contracts, Quality Assurance, Configuration Management, Data Management, Systems Administration, In-plant engineering, Software Maintenance, and Security. Additionally, the Contractor shall support the DCGS and provide logistics support, modernization support, development support, and sustainment services to include: Furnishing the necessary personnel and facilities, software fixes for Deficiency Reports (DRs) and Problem Reports (Serena tickets, or any repository specified by the Government) as prioritized by the Government, testing, delivery of software, and remote and phone support as required to support mission operation including developing and testing software applications and software fixes in a classified System Integration Lab (SIL) and delivering classified releasable software for the Classified site. This includes updates to engineering documentation, training material, user documentation, and fielding documentation.

1.1 Objective(s):

This PWS describes the services to develop and/or modify a Sensor Agnostic Emulator and Trainer (SAET) and signal generator to meet operations and cybersecurity requirements under the requirements section of this document and the cybersecurity requirements called out in this document and applied to all delivered software. The emulator development is a part of the System Transformation Authority-To-Operate (ATO) risk decision packages governed by Intelligence

Community Directive (ICD) 503 for the Distributed Common Ground Station (DCGS) in support of the fielded baselines.

The Contractor shall deliver and install a complete suite of SAET xxx software, providing a multi-hub-based version that supports standalone operations without intranet connectivity. This effort will also modify SAET version xxx to create a classified site releasable version for the currently fielded Enterprise and Releasable baselines. The SAET will be updated as needed to generate new and more complex signals. SAET will be available in two configurations: 1) a full SAET suite, consisting of supporting software and hardware (if applicable) which, for accreditation purposes, can be considered a system; and 2) a software-only version. If hardware is required for either configuration, the OA STACK v2.0 hardware will be used to support SAET operations.

1.2 Benefit to United States Air Force (USAF):

This acquisition will benefit the USAF by providing the hardware and software necessary to emulation and simulation of the current and future sensor baseline systems allowing for realistic verification and validation during development, as well as, testing and training capabilities. This capability will enable DCGS operators and maintainers the ability to train in a simulated environment that replicates real-world scenarios while not impacting real-world operations of a low-density high demand (LDHD) platform/ sensor. Additionally, it allows for accurate development, modifications and checkout of future mission application upgrades without impacting real-world operations. At minimum, the signal generation, emulator and simulation capability shall be capable of delivering three separate signals simultaneously in order to support multi-mission and to allow for training at multiple sites using the hub-based system.

1.3 Background:

Based on the fact that Agile methodology has emerged as a leading industry software development approach, and its adoption has grown across the federal government, this PWS contains sections and verbiage that are directed towards Agile efforts. Agile methods involve successive iterations of software development, with each iteration producing working software, and enough documentation to develop and support the associated code delivered. While the code produced within an iteration is useable, it may not have enough functionality to be released to the end-user until multiple iterations making up a release are completed. This will be discussed in more detail in individual Task Descriptions.

2.0 Services Summary:

This Service Summary identifies the performance objectives that will be monitored and the performance thresholds in which these objectives will be evaluated. Metrics regarding the evaluation of these performance objectives can be found in the Quality Assurance Surveillance Plan (QASP).

Performance Objective PWS Reference Performance Threshold Provide accurate inventory of GFP and GFE

3.4 Inventory of all GFP and GFE shall be

conducted within 30 calendar days of contract award and within 30 calendar days prior to contract completion.

Quality of Product or Service

4.3.1 Provide services and/or products, on a

consistent basis, that meet the specified performance required by individual task orders, as required for: Change Request and Discrepancy Report solutions. These fixes shall be merged and fielded, with no additional rework, unless authorized by the Government for an interim solution.

Acceptance Testing (AT), Integrated Acceptance Testing (IAT) and Functional Checkout

5.3

Ninety percent (90%) of all testing in accordance with (IAW) the approved test procedures shall pass on the first attempt with no Category I (CAT I) Emergency or Category I Urgent deficiencies IAW T.O.

00-35D-54, USAF Deficiency Reporting, Investigation, and Resolution. The remaining 10% shall pass on the second attempt with no CAT I Emergency or Urgent deficiencies.

Demonstrations: Sprint Demos, Team Demos, Solution Demos, System Demos

5.4 The Contractor shall employ an iterative, incremental process to design/develop software and associated interfaces in small testable builds with a well-defined, agreed-to exit criteria also referred to as “Definition of Done.”

Receipt of CDRL deliverable 4.3.2 There shall be no more than two (2) late submission(s) of deliverables per quarter.

The Contractor shall notify the Government if the delivery of any data/document will not meet the scheduled delivery date and negotiate a revised delivery date. The data/document shall be delivered by the revised delivery date acceptable to the Government.

Delivered Documentation 4.3.1 There shall be no more than one rejection of any deliverable. There shall be no more than 1 total rejection(s) of deliverables per option year. The Government will reject a deliverable if 1 or more technical errors or 5 or more minor errors are found within the deliverable. The rejected deliverable shall be corrected and resubmitted within 5 business days of notification of Government rejection.

Management of Key Personnel

4.11 The Contractor shall provide qualified

personnel (both technical and management) in order to meet these tasks.

Upon identification of any shortcomings that will impact tasks assigned under this PWS or any task orders associated with this effort, the Contractor shall undertake corrective action and notify the Government within 15 calendar days.

Mishap Notification and Reporting

6.6.3 No more than one instance of late mishap

notification per contract year.

3.0 Government Property

3.1 Contractor Responsibility:

The Contractor shall be responsible for Government property in accordance with the Federal Acquisition Regulation (FAR) and as specified in the contract/order.

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

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

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

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

Protection of CUI and unclassified DoD information not approved for public release on non- DoD Information Systems will be protected IAW DoDI 8582.01, Security of Non-DoD Information Systems Processing Unclassified Nonpublic DoD Information. Unless specific categories of CUI require more stringent controls, non-DoD Information Systems must be protected using the guidelines set forth in NIST Special Publication 800-171, Protecting Controlled Unclassified Information in Nonfederal Information Systems and Organizations.

Covered Defense Information [Required for all solicitations and contracts, including solicitations and contracts using FAR part 12 procedures for the acquisition of commercial items]

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

3.2 Government Property to be Provided:

Government Furnished Property (GFP) to include Government Furnished Equipment (GFE), Government Furnished Material, Government Furnished Information (GFI), and Services shall be identified and directed by individual task order as required. The Contractor shall specifically request access to, or possession of, any GFP required to complete task orders under this IDIQ.

(CDRLs A00C DI-SESS-81359B/T, RECOMMENDED SPARE PARTS LIST (RSPL); A01T

DI-MGMT-80269/T, STATUS OF GOVERNMENT FURNISHED EQUIPMENT (GFE)

REPORT, A025 DI-PSSS-80727A, GOVERNMENT FURNISHED MATERIAL (GFM) BY

NATIONAL STOCK NUMBER (NSN))

3.2.1 Additional Property Access of GFE/GFI

Required Government Furnished Equipment/Government Furnished Information (GFE/GFI) includes the following:

Item Description Quantity Date Required Period Required

Access to the Continuous Integration Environment

(CIE) -DSIL MTE, CTE,

and DGS-X

1 ARO

Through program completion testing of new releases in the CTE. This will be collaboratively scheduled, and testing continues through DGS-X.

Access to Government Design Architecture and Related OA-DCGS Documentation

1 ARO

Through Program Completion

Access to Confluence, associated Jira tools or any repository specified by the Government

1 ARO

Through Program Completion

3.3 Base Support:

The Government will furnish property incidental to the place of performance including office space and equipment, i.e., computer equipment, software, output device(s), phone/phone line, facsimile equipment, reproduction equipment and office supplies.

3.4 Reporting of Government Property:

The Contractor shall have a system of internal controls to manage (control, use, preserve, protect, repair, and maintain) Government property in its possession in accordance with FAR 52.245-1, and its property management system shall be adequate to satisfy the requirements of this clause.

The contractor shall record receipt and return of all Government Furnished Property (GFP), as well as the reporting of shipment, consumption, disposal, or transfer to another contract, in the GFP Module in Procurement Integrated Enterprise Environment (PIEE), https://piee.eb.mil, as stipulated by FAR 252.245-7002. This reporting requirement does not change any liability provisions or other reporting requirements that may exist under the contract. GFP training and guidance is located at the DoD Procurement Toolbox at https://dodprocurementtoolbox.com/.

(A024 DI-MGMT-80441D/T, GOVERNMENT PROPERTY (GP) INVENTORY REPORT)

3.5 Loss of Government Property

3.5.1 Definition of Loss of Government Property:

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

3.5.2 Reporting Loss of Government Property:

The Contractor shall report loss of Government property in the GFP Module located in PIEE, https://piee.eb.mil/piee-landing/.

3.5.3 Return or Retention of Government Property:

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

4.0 Technical Requirements

4.1 Period and Place of Performance

4.1.1 Contract/Order Period of Performance:

The period of performance for this contract will be a one (1) year basic period with four (4) 12-month option periods. The period of performance for individual requirements will be specified in the task order.

4.1.2 Place of Performance:

The Contractor’s primary location will be its own facility as well as government sites and designated facilities supporting the ST ACAT in the Continental United States (CONUS) and/or Outside CONUS (OCONUS), as specified in individual task orders.

4.2 Configuration and Data Management:

The Contractor shall conduct Configuration Management (CM) in accordance with SAE EIA-

649. The Contractor shall comply with CM requirements listed below and in accordance with the Contractor’s CM Plan (CMP). The Contractor shall levy these same CM requirements to any tier of Subcontractor. The Contractor shall use a CM process to control and tie, trace, and link all configuration information representing or comprising the system/configuration item. The Contractor shall use Digital Engineering (DE) tools for configuration and data management processes, activities, and artifacts. The Contractor shall implement CM addressing Configuration Planning and Management, Configuration Identification, Configuration Change Management, Configuration Status Accounting (CSA), Configuration Verification and Audits, Data Management, and Deficiency Reporting. The Contractor shall generate updates to the CM Plan for Government approval. The Contractor shall measure the CM performance metrics identified in the CM Plan. (A012 DI-SESS-80858D/T, SUPPLIER'S CONFIGURATION

MANAGEMENT PLAN).

4.2.1 Configuration Identification:

The Contractor shall use a documented process for configuration identification IAW the CMP and the following paragraphs. The Contractor shall recommend potential CIs/CSCIs for Government review and selection concurrence utilizing the criteria in the CMP. The Contractor shall mark or label items and information with their applicable identifiers.

The Contractor shall establish and generate a CI and CSCI structure and hierarchy. In addition, the Contractor shall ensure configuration information and artifacts tie, trace, and link from top-level/end item to the lowest component. (CDRL A029, DI-SESS-82333B/T, ACQUISITION

AND SUSTAINMENT DATA PACKAGE (ASDP) CONFIGURATION STATUS

ACCOUNTING (CSA) INFORMATION)

The link to the CI Listing is:

https://intelshare.intelink.gov/sites/isrdcgsaf/DCGS/library/PPPP/04_Configuration_Data_Mana gement/02-Policies/DCGS-BRF-ENT-0001_Rev-3_Configuration_Item_Listing_20230720.pdf

The link to the CI ID and Naming Schema is:

https://intelshare.intelink.gov/sites/isrdcgsaf/DCGS/library/PPPP/04_Configuration_Data_Mana gement/02-Policies/DCGS-PLC-CDM-0008_Rev- 1_Configuration_Item_(CI)_ID_and_Naming_Schema.pdf

4.2.2 Configuration Baselines:

Contractor shall generate the configuration information required for the configuration baselines being established by the Government IAW MIL-STD-961 and shall tie, trace and link all configuration information and artifacts to the lowest component that makes up a configuration baseline(s). The Contractor shall maintain the current approved configuration information creating a new revision to configuration information after a change approval. (CDRLs A00B DI-

IPSC-81442A/T, SOFTWARE VERSION DESCRIPTION DOCUMENT (SVDD); A00K DI-

AVCS-80700A/T, COMPUTER SOFTWARE PRODUCT END ITEMS; A00W DI-IPSC-

81441A/T, SOFTWARE PRODUCT SPECIFICATION (SPS); A010 DI-IPSC-81431A/T,

SYSTEM/SUBSYSTEM SPECIFICATION (SSS))

4.2.3 Configuration Change Management:

The Contractor shall apply configuration control to each CI/CSCI and its components and configuration information. The Contractor shall confirm configuration baselines are maintained and controlled, configuration identification control of all CIs/CSCIs and their associated configuration information is maintained, all configuration information and artifacts are tied, traced and linked, and the Authoritative Source of Truth (ASoT) is updated. The Contractor shall support a joint Government/Contractor Configuration Control Board(s) chaired by the Government and IAW the CM.

4.2.4 Data Management:

The Contractor shall establish a data management program for identifying, generating/acquiring, and controlling technical and management product data and related information. The Contractor shall implement and maintain data management procedures for preparation, quality control, administration and delivery of data required by the CDRL(s) and tie, trace and link the data to build the digital thread.

The Contractor shall utilize the AFLCMC approved data repository and management tool to deliver CDRL data to the Government in accordance with the CDRLs and the CDRL Instructions that are part of the CDRL package and contract. The Contractor shall maintain data status and delivery schedules for all CDRL items. The Contractor shall provide a central point of contact for data management.

4.2.5 Technical Data:

The Contractor shall provide material and labor necessary to maintain engineering drawings (A00G), AF Technical Manual Contract Requirements (A018), Operation and Maintenance (O&M) manuals (A00G) and other system documents as it applies to the baseline system and software. All documentation provided shall be prepared and administered IAW the CDRLs.

(CDRLs A00D DI-SESS-81000F/T, PRODUCT ENGINEERING DESIGN DATA AND

ASSOCIATED LISTS); (A00G, TM-86-01R, AF TECHNICAL MANUAL CONTRACT

REQUIREMENTS)

4.2.5.1 Installation and Testing:

The Contractor shall deliver the updated software under this effort, in accordance with AFDCGS Software Delivery Policy. The Contractor shall provide detailed installation instructions and source data required for Time Compliance Technical Order (TCTO) and Technical Order generation and support to the DCGS System Integration Lab (DSIL) team either in-plant or at DSIL and Distributed Ground Station (DGS) eXperimental (X) as required. The Contractor shall accomplish the recurring engineering activities necessary to install the updated baseline through agile-based incremental deliveries to the DSIL as key capabilities mature throughout continuous agile release cycles to facilitate early integration opportunities with associated DCGS subsystems. (A00G, TM-86-01R, AF TECHNICAL MANUAL CONTRACT

REQUIREMENTS; CDRL A00K DI-AVCS-80700A/T, COMPUTER SOFTWARE PRODUCT

END ITEMS; A00L DI-NDTI-80566A/T, Test Plans, ACCEPTANCE TEST ONLY)

The Contractor shall leave a copy of all executed redline installation instructions and any document used during the site visit to the sites management team prior to departure. Contractor shall deliver a final version of the corrected documents within 5 business days after the departure of site. Fridays do not count as business days in establishing the delivery date.

The Contractor shall update the inventory of software contents which includes all software (changed and COTs/GOTs). For modernized software and COTs/GOTs, the Contractor shall provide the Manufacturer, Product Name, and Version. The Contractor shall also document licensed software products to reference subscription services, licensing, and warranty information, and deliver in the latest approved Government provided format. (CDRL A00B DI-

IPSC-81442A/T, SOFTWARE VERSION DESCRIPTION DOCUMENT (SVDD))

The Contractor shall also provide the software executable(s) to AFLCMC/C3IEA ISR Ground Software Management Team (through AFLCMC/C3IEAC3IEA Data Management) for the DSIL's Nexus SW Repository after acceptance test/at the DSIL/DGS-X and as changes are made as applicable. The Contractor will provide systems and data flows. (CDRL A00D DI-SESS-

81000F/T, PRODUCT ENGINEERING DESIGN DATA AND ASSOCIATED LISTS)

The Contractor shall explicitly identify the computer software executables (e.g., modules), computer software documentation and technical data to be modified, and to deliver the same to the Government with the proper defense federal acquisition regulation system (DFARS) marking. Valid marking for computer software or computer software documentation shall be either unlimited, Government purpose rights (GPR), restricted rights, small business innovation research (SBIR) program rights, or special license rights. (CDRLs A001 DI-MGMT-81453C/T, DATA ACCESSION LIST (DAL); A01K DI-MGMT-81803A/T, ITEM UNIQUE

IDENTIFICATION (IUID) MARKING PLAN; A01L DI-MGMT-81804A/T, IUID MARKING

ACTIVITY, VALIDATION, AND VERIFICATION REPORT)

4.2.5.2 Software Deliverable:

All software source code, a listing of compilers, build notes, and all other items covered under A00W will be delivered to the government at the end of each program increment. The vendor will also deliver to the government the executable software. The government will own this software and will be able to have a third party execute the building of the products moving forward. The Contractor will deliver a Software Product Specification (SPS) and the Software Version Description Document (SVDD) for each application and all other documentation required to field this software. These deliverables must enable the Government the ability to build executable binary (gold disk) files for release to the field at Robins AFB. Detailed requirements for these technical specifications shall be as defined by data items associated with the technical deliverables identified herein. (CDRLs A001 DI-MGMT-81453C/T, DATA

ACCESSION LIST (DAL); A00B DI-IPSC-81442A/T, SOFTWARE VERSION

DESCRIPTION DOCUMENT (SVDD); A00K DI-AVCS- 80700A/T COMPUTER

SOFTWARE PRODUCT END ITEMS; A00W DI-IPSC-81441A/T, SOFTWARE PRODUCT

SPECIFICATION (SPS))

Source Code Ownership and Maintenance:

The Government shall own, without restriction, all rights, title, and interest in all source code, documentation, scripts, configuration files, and any associated materials created, developed, or delivered, as well as the initial hardware and software deliveries under this contract.

The Contractor shall provide the Government with:

Complete source code: All source code, including any supporting libraries, scripts, configuration files, and assets, shall be delivered in a clear, organized, and build-ready format.

Compilation and Build Instructions: Detailed step-by-step instructions on compiling, building, and deploying the software. These instructions must enable Government personnel or third-party contractors to independently compile and deploy the software without further assistance from the Contractor.

Maintenance Documentation: Comprehensive documentation covering the configuration, update procedures, dependencies, and any required build tools, including version-specific information and installation steps.

Version Control Access: Access to the version control repository used during development to capture all code changes, commit history, and release versions for

Government auditing and future reference. In lieu of this, a guide behind how to set up a mirrored environment may be acceptable as determined by the Government.

All materials, including the source code and build instructions, shall be updated and maintained to reflect any modifications, patches, or upgrades during the project lifecycle. The Government retains the right to review, modify, distribute, and utilize the software and supporting materials without restriction or further compensation to the Contractor.

The contractor will compile and build the initial set of software for each delivery and install that software on the designated system to conduct verification and validation of the software product.

As defined under CDRL A00P and CDRL A00W Software Product Specification.

4.3 Contract Data Requirements List (CDRL):

Ensure all reports, data, and requested information are produced and delivered to the Government as required by the CDRL, this PWS, or a task order covered by this IDIQ. These documents will be delivered per the schedule set by the Government and will be composed of incremental deliveries. Document templates provided by AF DCGS must be used by the Contractor. These templates are located on an AF DCGS collaboration website, currently, but not limited to Confluence, and are in the form of wiki pages. Re-use of existing documents is preferred, vice creating new documents for each iterative delivery. This format will follow the twelve-step plan identified in the Air Force (AF) Command, Control, Intelligence, Surveillance and Reconnaissance (C2ISR) Risk Management Plan with guidance identified in the AF DCGS collaboration website, i.e. Confluence. Link will be provided once contract is awarded.

The Contractor shall notify the Government of any missing documentation by the date required by the CDRL or applicable task order.

Task order Integrated Master Schedules of all planned and contracted work being delivered to any system covered by this IDIQ will be generated, maintained and delivered as assigned by the applicable CDRL per the task order.

The Contractor shall consolidate monthly financial reports into an integrated program level document. This consolidated document will cover all task orders covered under the IDIQ.

Note: Actual CDRL requirements will only be directed by individual task descriptions. The following list is for reference only.

BASE OY1 DID TITLE

PWS

REFERENCE

A001 B001

DI-MGMT-

81453C/T

DATA ACCESSION LIST (DAL) 4.2.5.1

A002 B002

DI-ADMN-

81250C/T

CONFERENCE MINUTES 4.13.2

A003 B003

DI-ADMN-

81373/T

PRESENTATION MATERIAL

4.11; 4.13.1;

4.13.2

A004 B004

DI-MGMT-

81468A/T

CONTRACT FUND STATUS

REPORT (CFSR)

4.11

A005 B005

DI-MGMT-

81928/T

CONTRACTOR'S PROGRESS

STATUS AND MANAGEMENT

REPORT

4.3.3; 4.11

A006 B006

DI-MGMT-

81861C/T

INTEGRATED PROGRAM

MANAGEMENT DATA AND

ANALYSIS REPORT (IPMDAR)

4.11

A007 B007

DI-SESS-

81248B/T

INTERFACE CONTROL

DOCUMENT (ICD)

4.13.1

A008 B008

DI-IPSC-

81436A/T

INTERFACE DESIGN

DESCRIPTION (IDD)

4.13.1

A009 B009

DI-IPSC-

81433A/T

SOFTWARE REQUIREMENTS

SPECIFICATION (SRS)

4.13.1

A00A B00A

DI-IPSC-

81435B/T

SOFTWARE DESIGN

DESCRIPTION (SDD)

4.13.1

A00B B00B

DI-IPSC-

81442A/T

SOFTWARE VERSION

DESCRIPTION DOCUMENT

(SVDD)

4.2.2; 4.2.5.1;

4.2.5.2; 4.13.1

A00C B00C

DI-SESS-

81359B/T

PARTS LIST 3.2

A00D B00D

DI-SESS-

81000F/T

PRODUCT ENGINEERING

DESIGN DATA AND

ASSOCIATED LISTS

4.2.5; 4.2.5.1;

4.13.2

A00E B00E

DI-PSSS-

81523D/T

TRAINING CONDUCT

SUPPORT DOCUMENT

4.13.2

A00F B00F

DI-ILSS-

80872/T

TRAINING MATERIALS 4.13.2

A00G B00G TM-86-01R

AF TECHNICAL MANUAL

REQUIREMENTS

4.2.5; 4.13.1

A00J B00J

DI-MGMT-

81797/T

PROGRAM MANAGEMENT

PLAN

4.3.5

A00K B00K

DI-AVCS-

80700A/T

COMPUTER SOFTWARE

PRODUCT END ITEMS

4.2.2; 4.2.5.1

A00L B00L

DID DI-

NDTI-

80566A.T

TEST PLANS 4.2.5.1; 4.13.1

A00M B00 M

DI-NDTI-

80809B/T

TEST/INSPECTION REPORT

4.13.1

A00N B00N

DI-TMSS-

81352/T

TRUSTED FACILITY MANUAL

(TFM)

4.13.1; 6.2.3.1;

6.2.3.2

A00P B00P

DI-MISC-

80508B/T

TECHNICAL REPORT –

STUDY/SERVICES

4.13.2; 6.2.3.1;

6.2.3.2

A00Q B00Q DI-MSC-

80508B/T

TECHNICAL REPORT –

STUDY/SERVICES

4.13.2; 6.1.2;

6.2.3.1; 6.2.3.2;

6.2.3.3; 6.2.3.5;

A00R B00R

DI-MISC-

80508B/T

TECHNICAL REPORT –

STUDY/SERVICES

4.13.2; 6.2.3.1;

6.2.3.2

A00S B00S DI-MGMT-

81334D/T

CONTRACT WORK

BREAKDOWN STRUCTURE

(CWBS)

4.11

A00T B00T

DI-MISC-

80508B/T

TECHNICAL REPORT –

STUDY/SERVICES

4.13.2

A00U B00U DI-MGMT-

80033A/T

SITE PREPARATION

REQUIREMENTS AND

INSTALLATION PLAN (SPRIP)

4.9; 4.13.2; 5.3

A00V B00V

DI-SESS-

80639E/T

ENGINEERING CHANGE

PROPOSAL (ECP)

4.3.6

A00W B00 W

DI-IPSC-

81441A/T

SOFTWARE PRODUCT

SPECIFICATION (SPS)

4.2.2; 4.2.5.2;

4.13.2

A00X B00X

DI-MISC-

80508B/T

TECHNICAL REPORT –

STUDY/SERVICES

4.13.2

A00Y B00Y

DI-SAFT-

80102C/T

SAFETY ASSESSMENT

REPORT

6.6.2

A00Z B00Z DI-PSSS-

81656B/T

BILL OF MATERIAL (BOM)

FOR LOGISTICS AND SUPPLY

CHAIN RISK MANAGEMENT

4.14

A010 B010

DI-IPSC-

81431A/T

SYSTEM/SUBSYSTEM

SPECIFICATION (SSS)

4.2.2; 4.13

A011 B011

DI-PSSS-

81535A/T

DEFICIENCY REPORT (DR) 4.3.6

A012 B012 DI-CMAN-

80858D/T

CONTRACTOR'S

CONFIGURATION

MANAGEMENT PLAN

4.2

A014 B014

DI-FNCL-

80331A/T

FUNDS & MAN HOURS

EXPENDITURE REPORT

4.11

A015 B015

DI-MGMT-

80368A/T

STATUS REPORT 4.11

A016 B016

DI-SAFT-

81563/T

ACCIDENT/INCIDENT REPORT 6.6.3

A017 B017 DI-MGMT-

81580/T

CONTRACTOR’S STANDARD

OPERATING PROCEDURES

(SOP)

6.6.2

A018 B018

FED-STD-

368A/T

QUALITY CONTROL SYSTEMS

REQUIREMENTS

5.5.1

A019 B019

DI-FNCL-

80912A/T

PERFORMANCE AND COST

REPORT

4.11

A01B B01B

DI-ENVR-

81840/T

PROGRAMMATIC

ENVIRONMENTAL SAFETY

AND HEALTH EVALUATION

(PESHE)

6.6.2

A01C B01C

DI-QCIC-

81722/T

QUALITY PROGRAM PLAN 5.5.1

A01D B01D

DI-ADMN-

81249C/T

CONFERENCE AGENDA 4.13.1

A01E B01E DI-MGMT-

81928/T

CONTRACTOR’S PROGRESS,

STATUS AND MANAGEMENT

REPORT

6.6.3

A01G B01G

DI-MISC-

80508B/T

TECHNICAL REPORT –

STUDY/SERVICES

4.13.4

A01H B01H

DI-MISC-

81419/T

PERSONNEL REPORT 4.6.1

A01J B01J

DI-MISC-

80508B/T

TECHNICAL REPORT –

STUDY/SERVICES

6.1.2

A01K B01K DI-MGMT-

81803A/T

ITEM UNIQUE

IDENTIFICATION (IUID)

MARKING PLAN

4.2.5.1

A01L B01L DI-MGMT-

81804A/T

IUID MARKING ACTIVITY,

VALIDATION, AND

VERIFICATION REPORT

4.2.5.1

A01M B01 M

DI-NDTI-

81351/T

SECURITY TEST PLAN

4.13.2; 6.2.3.1;

6.2.3.2

A01N B01N

DI-MGMT-

81808/T

RISK MANAGEMENT PLAN 4.13.4

A01P B01P

DI-MGMT-

81809/T

RISK MANAGEMENT STATUS

REPORT

4.13.4

A01Q B01Q DI-MGMT-

81861C/T

INTEGRATED PROGRAM

MANAGEMENT DATA AND

ANALYSIS REPORT (IPMR)

4.11

A01R B01R DI-MGMT-

81644B/T

DOD ARCHITECHTURE

FRAMEWORK

DOCUMENTATION

4.10

A01S B01S DI-MGMT-

81334D/T

CONTRACT WORK

BREAKDOWN STRUCTURE

(CWBS)

4.11

A01T B01T DI-MGMT-

80269/T

STATUS OF GOVERNMENT

FURNISHED EQUIPMENT (GFE)

REPORT

3.2

A01U B01U

DI-MGMT-

80995A/T

MAINTENANCE SERVICE

REPORT

A01V B01V

DI-PACK-

80120DT

PRESERVATION AND

PACKAGING DATA

4.13.2

A01W B01 W

DI-SESS-

81759A/T

LOGISTICS PRODUCT DATA

SUMMARIES

6.6.3

A01X B01X

DI-MISC-

81943/T

TRIP/TRAVEL REPORT 5.11

A01Y B01Y DI-MISC-

81306/T

PROGRAM PROTECTION

IMPLEMENTATION PLAN

(PPIP)

6.6.2

A024 B024

DI-MGMT-

80441D/T

GOVERNMENT PROPERTY

(GP) INVENTORY REPORT

3.4

A025 B025

DI-MGMT-

80727A

GOVERNMENT FURNISHED

MATERIAL (GFM) BY

NATIONAL STOCK NUMBER

(NSN)

3.2

A026 B026

DI-MGMT-

80258C/T

MATERIAL IMPROVEMENT

PROJECT (MIP)

4.2

A027 B027

DI-SESS-

80255B/T

FAILURE SUMMARY AND

ANALLYSIS REPORT

4.3.6

A028 B028

DI-SESS-

82044/T

SYSTEM/SOFTWARE

INTEGRATION PLAN

4.9

A029 B029

DI-SESS-

82333B/T

ACQUISITION AND

SUSTAINMENT DATA

PACKAGE (ASDP)

CONFIGURATION STATUS

ACCOUNTING (CSA)

INFORMATION

4.2.1

A02A B02A

DI-NDTI-

80603A/T

TEST PROCEDURES 5.3

4.3.1 Quality of CDRL Deliverable:

There shall be no more than one (1) rejection of any deliverable. There shall be no more than one (1) total rejection(s) of deliverables per option year. The Government will reject a deliverable if one (1) or more technical errors or five (5) or more minor errors are found within the deliverable. The rejected deliverable shall be corrected and resubmitted within five (5) business days of notification of Government rejection. The Contractor shall work with government POC to obtain and revise any documentation that is under government configuration control in lieu of producing new documentation.

4.3.2 Receipt of CDRL Deliverable:

CDRL deliverables may be submitted via Wide Area WorkFlow e-Business Suite / Invoicing, Receipt, Acceptance, and Property Transfer (iRAPT) or be submitted directly to the MFT member identified on the CDRL. There shall be no more than two (2) late submission(s) of deliverables per quarter. The Contractor shall notify the Government if the delivery of any data/document will not meet the scheduled delivery date and negotiate a revised delivery date.

The data/document shall be delivered by the revised delivery date acceptable to the Government.

The Contractor shall notify the Government if the delivery of any data/document will not meet the scheduled delivery date and negotiate a revised delivery date. The data/document shall be delivered by the revised delivery date acceptable to the Government.

4.3.3 Limitations and Performance Criteria:

The following fundamental requirements and management support services shall be specified as a basic work requirement of all task orders. Reporting shall be provided at the end of each sprint.

All the tasks listed in this PWS are subject to the following limitations and performance criteria.

(CDRL A005 DI-MGMT-81928/T, CONTRACTOR’S PROGRESS, STATUS, AND

MANAGEMENT REPORT)

4.3.4 Data Accession List:

The Government will be provided rights in accordance with the clauses of this contract for all technical data, computer software, and computer software documentation. The Contractor shall provide a DAL listing all data and software developed by the Contractor and maintained for accomplishment of this contract which is not provided under a Contract Data Requirements List (CDRL). The Contractor shall maintain and make available data listed in the DAL as requested by the Government. The Government's access to the Contractor's data will be as required by the clauses and provisions of the contract.

4.3.5 Contractor’s Program Multi-Functional Team (MFT):

The MFT membership will be reflective of the program structure and will include key discipline leaders and appropriate support organization representatives to aid in formulating plans and guidelines. (CDRL A00J DI-MGMT-81797/T, PROGRAM MANAGEMENT

PLAN)

Developing management initiatives to maximize the system performance to achieve performance criteria and report contractor and subcontractor (if applicable) performance.

Developing pre-approved methods for the cost reimbursable CLINs.

Ensuring the requirements of the contract are met.

Fiscal year site staffing, site planned man-hours, CLIN/Sub-Contract

Line-Item Number (SLIN)/dollar breakout reports.

Pricing tool to include CLINs/SLINs, company, and site estimates in editable format.

4.3.6 Deficiency Reports (DRs):

The Contractor shall investigate DRs submitted from the Government as Tier 4. All of these will be reviewed through the defect process in place in AF DCGS. The Contractor may prepare DRs to report problems noted during missions, test and evaluation activities conducted at field sites or during field installation activities. Investigation activities shall identify root cause of failure and provide a proposed technical approach to resolve the problem reported. DRs shall be tracked in a Government approved system and reported to the Government. (CDRLs A00V DI-SESS-

80639E/T, ENGINEERING CHANGE PROPOSAL (ECP); A011 DI-PSSS-81535B/T,

DEFICIENCY REPORT (DR); A027 DI-SESS-80255B/T, FAILURE SUMMARY AND

ANALYSIS REPORT)

4.3 Material Procurement:

The Contractor shall procure spares at the required levels to support the SAET and all associated support equipment and related products necessary to meet mission requirements, as directed by the Government’s Material Manager. The Contractor shall not change the design of a COTS end item without prior approval of the Government. The Contractor shall process purchase directives (PDs) for acquisition primarily of expense and investment spares. The Contractor shall also process Government PDs for requirements other than spares. The Contractor shall provide the Government Material Manager with assistance in determining buy, repair, or hold/delay requirements, conducting marketing surveys to determine best competitive pricing and delivery dates, and accomplishing procurement activities as directed by the Government. The Contractor shall receive, inspect, stock, and issue parts, and maintain inventory control.

The Contractor shall collect bonded stock information and administer the program IAW this PWS and Attachment 3 of the IDIQ. Contractor shall prepare receiving reports and assist in support of bonded stock inventory and semi-annual consumption reporting.

4.4 Funding:

Tasks shall be performed subject to funding limitations of the individual task order issued under this IDIQ.

4.5 Personnel:

AF DCGS identified collaborated website(s), currently, but not limited to, Confluence and JIRA, account(s) will be maintained by Contractor personnel and the Contractor shall be proactive in training and retaining qualified personnel (technical, managerial, and administrative) in order to meet these tasks. Upon identification of any shortcomings by the Contractor, that will impact tasks assigned by any task order associated with this effort, the Contractor shall undertake corrective action, notify the Government within fifteen (15) calendar days, and provide a corrective action plan that resolves the deficiency. Individual task orders will identify the extent of Contractor participation.

4.6.1 Personnel Report:

The Contractor shall deliver to the Government a monthly Production Personnel Manning and Schedule Report. (CDRL A01H DI-MISC-81419/T, PERSONNEL REPORT).

4.8 Schedule:

The Contractor shall meet all specific schedules delineated by each task order for products and services required by the Government under this IDIQ. Key milestones may include, but are not limited to Product Backlog Planning, Sprint Retrospectives, Program Increments, Planning

Events, System Demos, Solution Demos, Team Demos, and Release Planning. If a schedule slippage occurs, the Government PM and CO will be notified within two (2) working days, in writing (via e-mail). All notifications to a delay in schedule will include an associated recovery plan. Task order Integrated Master Schedules of all planned and contracted work being delivered to any system covered by this IDIQ will be generated, maintained, and delivered on a monthly basis.

4.9 Specific Work to Be Accomplished:

The Contractor shall support the DCGS by providing operation and support, as well as development, modifications, updates, verification and validations to build and update/enhance the capability of the SAET and all associated and related products including those associated with the Test Facilities, Sensitive Compartmented Information Facility (SCIF), and Development/Integration Laboratories. This support will include review and updates for ground systems technical refresh. The Contractor shall provide the following support required during the period of performance of this IDIQ: program management, sustainment, engineering and technical services, software development and support, system testing support, training (operator and maintenance, administrator and/or privileged user), technical data, data reporting, and travel.

Individual task orders will define the specific tasks required for funded activities.

The Contractor shall provide services and/or products, on a consistent basis, that meet the specified performance required by individual task orders, as required for: Change Request and Discrepancy Report solutions. These fixes shall be merged and fielded, with no additional rework, unless authorized by the Government for an interim solution.

The Contractor shall provide support, both technical and administrative, which includes, but is not limited to, the general tasks and responsibilities identified below. The Government will provide specific task descriptions for each task order. Administration of all tasks listed below shall be IAW Attachments to the IDIQ, as applicable.

The Contractor shall be participating as part of a Government run team using Agile principles including iterative processes, as directed by individual task orders. All tasks performed shall be subject to the funding limitations of individual task orders.

The Contractor shall provide qualified personnel (both technical and managerial) in order to meet these tasks. Upon identification of any shortcomings that will impact tasks assigned under this PWS or any task orders associated with this effort, the Contractor shall identify this task as a blocker to performance, report it, and undertake corrective action.

Even though the software will not be deployed throughout the lifecycle, multiple and small increments allow the program to monitor quality, incrementally integrate and test software, and allow early identification of defects.

All new development and or development efforts performed by the Contractor shall be executed in compliance with OA PaaS and integrate with the OA provided Enterprise Services or in accordance with updated government provided direction for Cloud / Cloud-ready initiatives as defined within the individual Task Orders

Development activities performed under this IDIQ shall be executed using Agile/SwAP development processes with open source-nonproprietary software. The Contractor shall perform Program Increment pre-planning, planning, execution, and demonstrations. Specific details on the implementation and requirements of these processes will be defined in the individual Task Orders.

The Site Preparation Requirements and Installation Plan (SPRIP) shall also include, but not be limited to Data Connectivity and Data Flow Diagrams including all connections to a Port level and shall include system delivery to site, system inventory, system installation, setup, configuration, integration, system acceptance testing, training, and security accreditation. The Integration Plan shall provide detailed steps and timeframes for transitioning operations from existing AF DCGS site systems to the upgrade systems and initiating operations where no AF DCGS existing system exists. Plan should include dates for factory install, System Integration Laboratory (SIL) testing, DGS X testing and site / operational testing. To avoid duplication of effort and maintain consistency throughout the system documentation, the contractor shall include or reference the data presented in other deliverable documentation. (CDRLs A00U DI-

MGMT-80033A/T, SPECIAL STUDIES; A028 DI-SESS-82044/T, SYSTEM/SOFTWARE

INTEGRATION PLAN)

4.10 Sustainment:

The main objective of this contracting effort is the Development, Integration, Fielding, Cyber Security and Sustainment activities required to meet AF DCGS/ Operational Requirements Document (ORD) requirements to maintain compliance with the Command, Control,…