Crew Comm PWS_DRAFT.pdf

Performance-Based Work Statement for

Air Force (AF) Distributed Common Ground System (DCGS)

Engineering Services For

Crew Communications (CREW COMM) and Associated Systems

Sustainment Support

Program

21 August 2025

Prepared by

AFLCMC/C3IA

750 Third Street

Robins AFB, GA 31098

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. HANDLING AND DESTRUCTION NOTICE - Comply with distribution statement and destroy by any method that will prevent disclosure of the contents or reconstruction of this document.

REVISION SUMMARY

Revision Date Description Affected

Pages/Para.

Initial 21 Aug 25

Table of Contents

1.0 Description of Services: 8

1.1 Objective(s):

1.2 Benefit to United States Air Force (USAF):

1.3 Background:

2.0 Services Summary 10

3.0 Government Property 11

3.1 Contractor Responsibility:

3.2 Government Property to be Provided

3.2.1 Bonded Stock Operation and Administration

3.2.2 Property Administration

3.2.3 Specific Property Access or GFE in Possession of Contractor

3.2.4 Government System(s):

3.3 Reporting of Government Property

3.4 Loss of Government Property

3.4.1 Definition of Loss of Government Property:

3.4.2 Reporting Loss of Government Property:

3.5 Return or Retention of Government Property:

4.0 Technical Requirements 13

4.1 Period and Place of Performance:

4.1.1 Contract/Order Period of Performance:

4.1.2 Place of Performance

4.2 Contract Data Requirements List (CDRL):

4.2.1 Quality of CDRL Deliverable:

4.2.2 Receipt of CDRL Deliverable:

4.3 Advisory & Assistance Services

4.3.1 Item Unique Identification (IUID)

4.3.2 Packaging:

4.4 Configuration and Data Management:

4.4.1 Configuration Identification:

4.4.2 Configuration Baselines:

4.4.3 Configuration Change Management:

4.4.4 Data Management:

4.4.5 Technical Data:

4.4.5.1 Installation and Testing 25

4.4.5.2 Software Deliverable 26

4.5 Funding:

4.6 Personnel Report:

4.7 Cost Limitation (Applicable to Cost Reimbursement Contract Types):

4.8 Schedule:

4.9 Specific Work to Be Accomplished:

4.10 Program Management and Administrative Support:

4.11 Engineering Services

4.11.1 Specific Tasks

4.11.2 Deficiency Report (DR)/Serena Ticket Resolution

4.11.3 System Engineering/Installation Service

4.11.4 Security Engineering

4.11.5 Functional Verification

4.11.6 Kit Building

4.11.7 Team Demonstrations

4.11.7.1 Training 34

4.11.7.2 Documentation 35

4.11.8 Sustainment Engineering Services

4.11.9 Security Engineering

4.12 Cybersecurity Requirements:

4.12.1 Software Development:

4.12.2 Software Interfaces:

4.12.3 Software Tools:

4.12.4 Software Sustainment:

4.12.4.1 Vulnerability Management Plan 38

4.12.4.2 Software Patching Management Plan 39

4.12.4.3 Third Party Software Management Plan 39

4.12.4.4 Certificate to Field (CtF) 39

4.12.4.5 Plan of Action and Milestones (POA&M) 40

4.13 Sustainment

4.13.1 Deficiency Report (DR) Resolutions

4.14 Engineering Estimates

4.15 Supply Chain Management

4.16 Travel

5.0 General Information 42

5.1 Continuation of Mission-Essential Services During a Crisis:

5.1.1 Designation of Services as Mission-Essential

5.2 Security Requirements

5.2.1 Security Regulations43

5.2.2 Operations Security (OPSEC):

5.2.3 Communications Security (COMSEC):

5.2.4 Security Clearance:

5.2.5 Security Incident or Violation:

5.2.6 Access to Government System(s):

5.2.7 Access to Government Facility or Military Installation:

5.2.8 Common Access Card (CAC)

5.2.9 Protection of Information 45

5.3 Environmental Management System (EMS):

5.4 Agency Affirmative Procurement Programs:

5.5 Safety Requirements:

5.5.1. Contractor Environmental, Safety, and Occupational Health Compliance:

5.5.2 Mishap Notification/Investigation:47

5.6 Inspection of Services: 475

5.7 Service Contract Reporting:

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

5.9 Trafficking in Persons:

5.10 Fundamental Support and Service Responsibilities

5.10.1 Asset Management

5.10.2 Quality Assurance Program

5.10.3 System Support

5.10.4 DCGS System Integration Lab (DSIL) and DGS eXperimental (DGS X)

5.10.4.1 Enterprise Service Desk (ESD) 52

5.10.4.2 DSIL & DGS-X Support 52

5.10.4.3 Ground Software Library Support 52

5.11 Maintenance Support Facilities

5.12 Data Reporting

5.13 Material Procurement

5.13.1 Unique Spares

5.13.2 Replenishment Spares

5.13.3 Bonded Stock

5.13.4 Specialized Repair Activity (SRA)

5.13.4.1 Specialized Repair Activity/Work Orders 55

5.14 Information Assurance (IA) Requirements

5.15 Holidays and Facility Closings:

5.16 Contractor Manpower Reporting

5.16.1

5.16.2

5.16.3

5.17 Invoicing/Payment and Receipt/Acceptance

5.18 Protection of Information:

6.0 Appendices58

6.1 Appendix A: Government Documents

1.0 Description of Services:

This Performance-Based Work Statement (PWS) provides support and engineering services for Air Force Distributed Common Ground Systems (DCGS) through the Crew Communication (Crew Comm) Systems that are used in the assistance of 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. This is a follow-on to a previous contract, . Program status reporting of Delivery Orders ordered under this previous contract will be accomplished by this new follow-on effort. This status reporting will be accomplished as directed under a Task Order issued under the Defense Logistics Agency (DLA) Aberdeen RTX Corporation Umbrella Contract General Services Administration (GSA) OASIS contract vessel to support this effort.

This PWS describes tasks required for the sustainment of the Crew Comm systems listed below.

Modifications include the sustainment of the currently fielded Crew Comm 3.0. It also provides for the expansion in the number of the existing workstations in order to meet overall DCGS mission requirements. It also allows for the incorporation of new capability that may be developed and is required in order to meet changing sensor and DCGS mission requirements.

Finally, it allows for general DCGS system support which the Government may require. Major tasks include program management, material procurement, engineering services, repair activity, sustainment services, data reporting, and travel. Primary systems to be supported include: Crew Communications (Crew Comm)

1.1 Objective(s):

This PWS describes the services required to support the DCGS by providing sustainment, materials, software patching, services and other engineering support extending the life of the Air Force (AF) DCGS Crew Communication System (Crew Comm) until a suitable replacement is available. The support for tasks will include reviews, engineering services and support, updates associated with patching the software components and updating those components to maintain cyber security compliance and resolving identified and documented issues and defects.

This PWS is aligned to meet performance based contracting criteria for the Government.

The Contractor may be required to enter into an Associate Contractor Agreement (ACA) with other Contractors for Task Orders issued under this contract. Specific requirements for ACAs, including Contractor identification, will be included in individual Task Descriptions as required.

1.2 Benefit to United States Air Force (USAF):

The benefit to the United States Air Force is continued operational usage of Crew Communications (Crew Comm), and associated systems used for collection, correlation of data, collaboration, and dissemination of signals of interest and imagery intelligence from airborne, ground, and other systems in order to provide more accurate near-real time actionable intelligence to the war fighters.

1.3 Background:

The Crew Comm system is based on a commercial Trilogy, a Clear Comm company, proprietary hardware and software. Collins Aerospace, a Raytheon Technologies Company (RTX) developed and integrated the commercial hardware and software into a multi-security level capability meeting DCGS meeting Intelligence Community Directive Number 503 (ICD 503) requirements. RTX is the prime Contractor to Trilogy and contracted specific, AF DCGS required, design changes to the Trilogy commercial product. RTX developed and integrated the Crew Comm HUB-based Centralized Services Management Suite.

Life cycle projections for the Crew Comm System are very limited. All current related weapon systems and applications requiring the Crew Comm system are expected to be removed from inventory by FY 2027 due to the extension of the platform. It is feasible that the Crew Comm retirement can begin as early as the later part of FY 2027, but this is subject to change.

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. However, traditional Waterfall efforts still apply in some situations. Therefore, the Sections in this PWS include services for Waterfall and Agile and will be further clarified in the contract.

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.

Waterfall methods involve a sequential software delivery model following a linear and successive approach. It consists of distinct phases such as requirements analysis, design, implementation, testing, deployment, and maintenance. Each phase generally must be completed before the next one can begin. This method is suitable for projects with well-defined requirements and minimal changes expected during the development process however it can be less flexible to accommodating changes compared to Agile methodologies.

It is assumed that any continuing developments for the legacy Crew Comm platform will follow existing traditional (waterfall-based) developments and that most of the development for the OA DCGS platform will follow Agile practices.

If an effort is determined to be Agile, the Contractor will be required to adhere to the Agile portions of this document. In most cases, these paragraphs will be prefaced with the wording:

“Agile Efforts will be Performed per this Section”, but in some instances, Agile wording is incorporated within existing terminology.

2.0 Services Summary: This Services 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

Receipt of CDRL deliverable

4.2.2 There shall be no more than 1 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

CARNS, DWIGHT B CTR USAF AFMC AFLCMC/C3IAA

Does this need to be changed?

the revised delivery date acceptable to the Government.

Timeliness of Delivered Documentation

4.14 The target response time for the Contractor to

provide Engineering Estimates, once the entire scope is defined and presented to the Contractor by the Government, is five (5) business days or less.

Quality of Delivered Documentation

4.2.1 All final delivered documentation shall be

provided to the Government with no more than 1 technical error per 20 pages or one per report for reports fewer than 20 pages. A technical error includes logic errors or incorrect data.

Quality of Product or Service

4.11.1 5.12

The Contractor shall provide Change Request (CR) and Serena/Discrepancy Report (DR) solutions that can be merged and fielded with no additional rework following fielding unless authorized by the Government for an interim solution.

Provide on a consistent basis, services and/or products that meet specified performance as follows: Spares delivered to stock result in Quality Deficiency Report actions less than 5% of total annual activity.

Acceptance Testing Crew Comm Software

4.11.5 Ninety percent (90%) of all test cases conducted

IAW the Operational Testing (OT) shall pass with no CAT I deficiencies on the first attempt.

The remaining 10% shall pass with no CAT I deficiencies on the second attempt.

Compliance with Security Program

5.2.5 Zero security violations.

Mishap Notification and Reporting

5.5.2 No more than one instance of late mishap

notification per year.

3.0 Government Property

3.1 Contractor Responsibility:

The Contractor shall define all Government Furnished Property (GFP), Government Furnished Equipment (GFE), Government Furnished Material (GFM) and Services requirements necessary to execute the performance of the PWS requirements. The Contractor shall develop this list of requirements as part of the proposal effort. Revisions to this list shall be made by the Contractor throughout the period of performance of this contract. (CDRL A025 DI-PSSS-80727A/T, GOVERNMENT FURNISHED MATERIAL by NATIONAL STOCK NUMBER (NSN))

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.

(CDRL A01T DI-MGMT-80269/T, STATUS OF GOVERNMENT FURNISHED EQUIPMENT

(GFE) REPORT;)

3.2.1 Bonded Stock Operation and Administration

Government Bonded stock operations and administration will be provided if a DCGS bonded stock facility is maintained. Administration of this item will be in accordance with (IAW) this contract.

3.2.2 Property Administration

The Government will retain ownership of Government Furnished Property (GFP) upon contract completion. Administration will be IAW this IDIQ.

3.2.3 Specific Property Access or GFE in Possession of Contractor

Crew Comm Integration Lab 1 Month 1 ARO Program Completion

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.

3.2.4 Government System(s):

The Government will provide Contractor personnel access to systems necessary to perform tasks under the contract/order. The Contractor shall ensure Contractor personnel who require access to a Government Automated Information System (AIS) have a Department of Defense National Agency Check Plus Written Inquiries (DNACI) conducted in accordance with Department of Defense (DoD) 5200.2-R, Personnel Security Program. The Government will provide system access subject to approval of the DD Form 2875, System Authorization Access Request (SAAR).

Upon completion/termination of the contract/order or transfer/termination of Contractor personnel, the system account will be closed.

3.3 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 DFARS 252.245-7005. 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/. (CDRL A024 DI-MGMT-80441D/T, GOVERNMENT

PROPERTY INVENTORY REPORT)

3.4 Loss of Government Property

3.4.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.4.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 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 https://piee.eb.mil/ https://dodprocurementtoolbox.com/ https://piee.eb.mil/piee-landing/ 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 applicable to each task shall be specified in the task description. The base 6-month option period for the contract will cover 1 order from 25 JUL 26 to 25 JAN 27. An 2 additional options will cover a six (6) months of support from 26 JAN 27 to 25 JUL 27, and from 26 JUL 27 to 25 JAN 28The clause FAR 52.217-8, Option to Extend Services, will be included in the award that would allow up to six (6) months of coverage after 25 JAN 28.

4.1.2 Place of Performance: The Contractor’s primary location will be its own facility, in Dulles, VA. Other performance locations (labor and travel) for contractor includes: Pacific Classified Site (PCS), Langley Air Force Base (DGS-X) and Robins AFB (DSIL). Contact the program office for a complete list of performance locations overseas.

4.2 Contract Data Requirements List (CDRL):

Waterfall efforts will be performed per this Section:

Ensure all reports, data, and requested information are produced and delivered to the Government as required by the CDRL, this PWS, prior PWS, or a Task Order covered by this contract. The Contractor shall notify the Government of any missing documentation by the date required by the CDRL or applicable Task Order. All final delivered documentation shall be provided to the Government with no more than one (1) technical error per 20 pages or one (1) per report for reports fewer than 20 pages. A technical error includes logic errors or incorrect data.

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

Note: Actual CDRL requirements will only be directed by individual Task Descriptions. The following list is for reference only (If performing Waterfall Methodology, skip the Agile section directly below).

Agile Efforts will be performed per this Section:

Ensure all reports, data, and requested information are produced and delivered to the Government as required by the CDRL, this PWS, prior PWS, or a Task Order covered by this contract. 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 Confluence and are provided in the format of wiki pages. Re-use of existing documents will be necessary, vice creating new documents for each iterative delivery. This format will follow the twelve-step plan identified in the AF DCGS RMP with Guidance identified in Confluence. Link will be provided once contract is awarded.

Note: CDRL requirements will only be directed by individual Task Descriptions. The following list is for reference only. CDRLs for option years will have separate identifier/CDRL numbering.

ITEM

Base Year

TITLE SUBTITLE DID

A001 DATA ACCESSION

LIST (DAL)

DI-MGMT-81453B/T

A002 CONFERENCE

MINUTES

DI-ADMN-81250C/T

A003 PRESENTATION

MATERIAL

DI-ADMN-81373/T

A004 CONTRACT FUNDS

STATUS REPORT

(CFSR)

DI-MGMT-81468A/T

A005 CONTRACTOR’S

PROGRESS, STATUS

AND MANAGEMENT

REPORT

DI-MGMT-81928/T

A006 INTEGRATED

PROGRAM

MANAGEMENT DATA

AND ANALYSIS

REPORT (IPMDAR)

DI-MGMT-81861C/T

A007 INTERFACE CONTROL

DOCUMENT (ICD)

DI-SESS-81248B/T

A008 INTERFACE DESIGN

DESCRIPTION (IDD)

DI-IPSC-81436A/T

A009 SOFTWARE

REQUIREMENTS

SPECIFICATION (SRS)

DI-IPSC-81433A/T

ITEM

Base Year

TITLE SUBTITLE DID

A00A SOFTWARE DESIGN

DESCRIPTION (SDD)

DI-IPSC-81435B/T

A00B SOFTWARE VERSION

DESCRIPTION

DOCUMENT (SVDD)

DI-IPSC-81442A/T

A00C PARTS LIST Recommended Spare Part List (RSPL)

DI-SESS-81359B/T

A00D PRODUCT

ENGINEERING

DESIGN DATA AND

ASSOCIATED LISTS

ENGINEERING

DRAWINGS/DoDA

F PRODUCTS

DI-SESS-81000F/T

A00E TRAINING CONDUCT

SUPPORT DOCUMENT

Training Plan DI-PSSS-81523D/T

A00F TRAINING

MATERIALS

Computer Based Training (CBT)/

Classroom Materials

DI-ILSS-80872/T

A00G AF TECHNICAL

MANUAL CONTRACT

REQUIREMENTS

TIME

COMPLIANCE

TECHNICAL

ORDERS/TECH

MANUAL

TM-86-01R

A00H TECHNICAL REPORT-

STUDY/SERVICES

DATA OWNER'S

GUIDE

DI-MISC-80508B/T

A00J PROGRAM

MANAGEMENT PLAN

DI-MGMT-81797/T

A00K COMPUTER

SOFTWARE PRODUCT

END ITEMS

DI-AVCS-80700A/T

A00L TEST PLANS ACCEPTANCE

TEST ONLY

DI-NDTI-80566A/T

A00M TEST/INSPECTION

REPORT

FACTORY AND/OR

SITE

ACCEPTANCE

TEST REPORT

DI-NDTI-80809B/T

A00N TRUSTED FACILITY

MANUAL (TFM)

DI-TMSS-81352/T

A00P TECHNICAL REPORT –

STUDY/SERVICES

SECURITY RISK

ASSESSMENT

DI-MISC-80508B/T

A00Q TECHNICAL REPORT –

STUDY/SERVICES

SECURITY

ASSESSMENT

REPORT – POAM

DI-MISC-80508B/T

A00R TECHNICAL REPORT –

STUDY/SERVICES

System Security Plan

(SSP)

DI-MISC-80508B/T

ITEM

Base Year

TITLE SUBTITLE DID

A00S CONTRACT WORK

BREAKDOWN

STRUCTURE (CWBS)

DI-MGMT-81334D/T

A00T TECHNICAL REPORT –

STUDY/SERVICES

SPECIAL STUDIES DI-MISC-80508B/T

A00U SITE PREPARATION

REQUIREMENTS AND

INSTALLATION PLAN

(SPRIP)

DI-MGMT-80033A/T

A00V ENGINEERING

CHANGE PROPOSAL

(ECP)

DI-SESS-80639E/T

A00W SOFTWARE PRODUCT

SPECIFICATION (SPS)

DI-IPSC-81441A/T

A00X TECHNICAL REPORT –

STUDY/SERVICES

Design Change Notice (DCN) Engineering Change Order (ECO)

DI-MISC-80508B/T

A00Y SAFETY ASSESSMENT

REPORT (SAR)

DI-SAFT-80102D/T

A00Z BILL OF MATERIAL

(BOM) FOR LOGISTICS

AND SUPPLY CHAIN

RISK MANAGEMENT

Vanishing Vendor Report

DI-PSSS-81656B/T

A010 SYSTEM/SUBSYSTEM

SPECIFICATION (SSS)

DI-IPSC-81431A/T

A011 DEFICIENCY REPORT

(DR)

DI-PSSS-81535B/T

A012 SUPPLIER’S

CONFIGURATION

MANAGEMENT PLAN

DI-SESS-80858D/T

A0013 SYSTEMS

ENGINEERING

MANAGEMENT PLAN

(SEMP)

DI-SESS-81785B/T

A014 FUNDS & MAN HOURS

EXPENDITURE

REPORT

DI-FNCL-80331A/T

A015 STATUS REPORT Technical Progress Report

DI-MGMT-80368A/T

ITEM

Base Year

TITLE SUBTITLE DID

A016 ACCIDENT/INCIDENT

REPORT

MISHAP AND

NOTIFICATION

REPORTING

DI-SAFT-81563/T

A017 CONTRACTOR’S

STANDARD

OPERATING

PROCEDURES (SOP)

SAFETY AND

HEALTH PLAN

DI-MGMT-81580/T

A018 QUALITY CONTROL

SYSTEMS

REQUIREMENTS

Quality Control Plan FED-STD-368A/T

A019 PERFORMANCE AND

COST REPORT

DI-FNCL-80912A/T

A01A SECURITY FEATURES

USER’S GUIDE (SFUG)

DI-AVCS-81349/T

A01B PROGRAMMATIC

ENVIRONMENTAL

SAFETY AND HEALTH

EVALUATION (PESHE)

DI-ENVR-81840/T

A01C QUALITY PROGRAM

PLAN

DI-QCIC-81722/T

A01D CONFERENCE

AGENDA

DI-ADMN-81249C/T

A01E CONTRACTOR’S

PROGRESS, STATUS

AND MANAGEMENT

REPORT

Total Case Incident Rate (TCIR)/ Days Away, Restricted and/or Transferred (DART) Rate, or Injury and Illness

DI-MGMT-81928/T

Rates, Annual Reporting

A01F CONFIGURATION

AUDIT SUMMARY

REPORT AND

CERTIFICATION

DI-SESS-81022E/T

A01G TECHNICAL REPORT –

STUDY/SERVICES

Diminishing Manufacturing

Source Mitigation Plan

DI-MISC-80508B/T

A01H PERSONNEL REPORT Contractor Manpower Reporting

DI-MISC-81419/T

A01J TECHNICAL REPORT –

STUDY/SERVICES

Mission Essential Services Contractor

Contingency Plan for Mission Essential

Sites

DI-MISC-80508B/T

ITEM

Base Year

TITLE SUBTITLE DID

A01K ITEM UNIQUE

IDENTIFICATION

(IUID) MARKING PLAN

DI-MGMT-81803A/T

A01L IUID MARKING

ACTIVITY,

VALIDATION, AND

VERIFICATION

REPORT

DI-MGMT-81804A/T

A01M SECURITY TEST PLAN DI-NDTI-81351/T

A01N RISK MANAGEMENT

PLAN

DI-MGMT-81808/T

A01P RISK MANAGEMENT

STATUS REPORT

DI-MGMT-81809/T

A01Q INTEGRATED

PROGRAM

MANAGEMENT

REPORT

Integrated Master Schedule

DI-MGMT-81861C/T

A01R DOD

ARCHITECHTURE

FRAMEWORK

DOCUMENTATION

DoDAF Products DI-MGMT- 81644B/T

A01S Cost Software Data Reporting (CSDR)

CONTRACT WORK

BREAKDOWN

STRUCTURE

DI-MGMT-81334D

A01T STATUS OF

GOVERNMENT

FURNISHED

EQUIPMENT (GFE)

REPORT

DI-MGMT-80269/T

A01U MAINTENANCE

SERVICE REPORT

Material Support Requests

DI-MGMT-80995A/T

A01V PRESERVATION AND

PACKAGING DATA

Shipping Log DI-PACK-80120D/T

A01W LOGISTICS PRODUCT

DATA SUMMARIES

Incident Report/ Log DI-SESS-81759A/T

A01X TRIP/TRAVEL REPORT DI-MISC-81943/T

ITEM

Base Year

TITLE SUBTITLE DID

A01Y PROGRAM

PROTECTION

IMPLEMENTATION

PLAN (PPIP)

DI-ADMN-81306/T

A01Z MAINTENANCE AND

REPAIR PART DATA

REPORT

DI-MGMT-82163/T

A020 QUANTITY DATA

REPORT

"DI-MGMT-

82164/T"

A021 ENTERPRISE

RESOURCE PLANNING

(ERP) SOFTWARE

DEVELOPMENT

REPORT

(DD FORM 3026-3)

"DI-MGMT-

82035A/T"

A022 SOFTWARE

DEVELOPMENT

REPORT

(DD FORM 3026-1)

"DI-MGMT-

82035A/T"

A023 SOFTWARE

MAINTENANCE

REPORT

(DD FORM 3026-2)

"DI-MGMT-

82035A/T"

A024 GOVERNMENT

PROPERTY (GP)

INVENTORY REPORT

GFE Inventory Report

DI-MGMT-80441D/T

A025 GOVERNMENT

FURNISHED

MATERIAL (GFM) BY

NATIONAL STOCK

NUMBER (NSN)

DI-PSSS-80727A/T

A026 MATERIAL

IMPROVEMENT

PROJECT (MIP)

DI-MGMT-80258C/T

A027 FAILURE SUMMARY

AND ANALYSIS

REPORT

DI-SESS-80255B/T

A028 SYSTEM/SOFTWARE

INTEGRATION PLAN

DI-SESS-82044/T

A02A TEST PROCEDURES DI-NDTI-80603A/T

A02B PHASE-IN TRANSITION

PLAN N/A DI-SESS-82299/T

A02C PHASE-OUT

TRANSITION PLAN

DI-MGMT-81945A/T

A02D COMMERCIAL ASSET

VISIBILITY AIR FORCE

(CAV

AF)/GOVERNMENT

FURNISHED

MATERIAL REPORT

Government Furnished Material (GFM) End Item

Reporting

DI-MGMT-81634C/T

A02E COMPUTER

PROGRAMMING

MANUAL

DI-IPSC-81447A/T

A02F SOFTWARE

ARCHITECTURE

DESCRIPTION

(SWARD)

DI-SESS-82176/T

A02G SOFTWARE

TRANSITION PLAN

(STRP)

DI-IPSC-81429A/T

4.2.1 Quality of CDRL Deliverable:

The Contractor shall notify the Government of any missing documentation by the date required by the CDRL or applicable Task Order. All final delivered documentation shall be provided to the Government with no more than one (1) technical error per 20 pages or one (1) per report for reports fewer than 20 pages. A technical error includes logic errors or incorrect data.

https://quicksearch.dla.mil/qsDocDetails.aspx?ident_number=283463

Task Order Integrated Master Schedules of all planned and contracted work being delivered to any system covered by this contract 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 contract.

4.2.2 Receipt of CDRL Deliverable:

CDRL deliverables shall be submitted via Wide Area WorkFlow (WAWF) and submitted directly to the MFT member identified on the CDRL. There shall be no more than 1 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

4.3 Advisory & Assistance Services

The Contractor shall follow all IUID requirements for each qualifying Air Force asset in the Contractor’s possession. The IUID Program requires each qualifying Air Force (AF) asset to be uniquely identified with a permanent marking that can sustain its information throughout the life of the asset. The program addresses two categories of assets—those already in the AF inventory and those currently under contract but not currently in the AF inventory. For assets under contract, IUID requirements are specified in Defense Federal Acquisition Regulation Supplement (DFARS) 252-211.7003, Item Identification and Valuation and Department of Defense (DoD) 4100.39-M, Federal Logistics Information System (FLIS). All assets subject to marking must be recorded in the DoD IUID Registry.

4.3.1 Item Unique Identification (IUID)

Unique Item Identification is required for all items to be delivered to the Department of Defense (DoD) that meet the criteria established by the FAR. (CDRLs A01K DI-MGMT-81803AT, ITEM UNIQUE IDENTIFICATION MARKING PLAN; A01L DI-MGMT-81804A/T, IUID

MARKING ACTIVITY, VALIDATION, AND VERIFICATION REPORT)

4.3.1.1 Reporting in IUID Registry

4.3.1.1 Marking Requirement: Unique Item Identification is required for all items to be delivered to the Department of Defense (DoD) that meet the criteria established by the FAR.

4.3.1.2 Reporting in IUID Registry

4.3.1.2.1 Transmission of Government property must be recorded in the IUID Registry. The Government is required to record the transfer of GFP to the Contractor. The Contractor is required to record the receipt of GFP from the Government. The Contractor is required to record the return of GFP to the Government.

4.3.1.2.2 The Government or Contractor/Sub-contractor personnel responsible for causing a “life cycle event” (i.e., abandoned, consumed, destroyed by accident, destroyed by combat, donated, exchanged – repair, exchanged – sold, exchanged – warranty, expended – experimental/target, expended – normal use, leased, loaned, lost, reintroduced, retired, scrapped, sold – foreign Government, sold – historic, sold – Non-Government, sold – other federal, sold – state/local, and stolen) will update the item record in the IUID Registry.

4.3.2 Packaging:

The Contractor shall package and mark material in accordance with the contract/order Air Force Materiel Command (AFMC) Form 158, Packaging Requirements, and applicable Government regulations. The Contractor shall ensure that classified material is packaged, marked and delivered in accordance with DoD 5220.22-M, National Industrial Security Program Operating Manual (NISPOM). (CDRL A01V DI-PACK-80120D/T, PRESERVATION AND

PACKAGING DATA)

4.4 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. (CDRLs A011 DI-PSSS-81535B/T, DEFICIENCY REPORT; A012 DI-SESS-

80858D/T, SUPPLIER'S CONFIGURATION MANAGEMENT PLAN).

4.4.1 Configuration Identification (CI):

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 A00A, DI-IPSC-81435B/T, SOFTWARE

DESIGN DESCRIPTION (SDD))

The Contractor shall develop Eracent custom software signatures IAW DCGS-PRCD-ENT- 0003_Rev-7, Eracent Custom Software Integration Guide.

The link to the CI Listing is:

https://intelshare.intelink.gov/sites/isrdcgsaf/DCGS/library/PPPP/Forms/AllItems.aspx?RootFold er=%2Fsites%2Fisrdcgsaf%2FDCGS%2Flibrary%2FPPPP%2F04%5FConfiguration%5FData% 5FManagement%2F02%2DPolicies&FolderCTID=0x012000867F24C9A599214F84823D7099 D300B7&View=%7B6E034859%2DE9E5%2D491E%2D8D0A%2D02F3A36250AB%7D

The link to the CI ID and Naming Schema is:

https://intelshare.intelink.gov/sites/isrdcgsaf/DCGS/library/PPPP/Forms/AllItems.aspx?RootFold er=%2Fsites%2Fisrdcgsaf%2FDCGS%2Flibrary%2FPPPP%2F04%5FConfiguration%5FData% 5FManagement%2F02%2DPolicies&FolderCTID=0x012000867F24C9A599214F84823D7099 D300B7&View=%7B6E034859%2DE9E5%2D491E%2D8D0A%2D02F3A36250AB%7D

4.4.2 Configuration Baselines:

The 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); A01F DI-SESS-81022E/T,

CONFIGURATION AUDIT SUMMARY REPORT AND CERTIFICATION)

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

When directed by a Task Order, the Contractor shall maintain hardware and software configuration control of all products addressed by this effort. This activity shall include baseline management and change control. The Contractor shall provide documentation needed for the Government to maintain configuration control. For DCGS, the Contractor shall prepare drawings in accordance with AF-DCGS Standard Operating Procedure (SOP) 102, version 3, to reflect the hardware baseline.

https://intelshare.intelink.gov/sites/isrdcgsaf/DCGS/library/PPPP/Forms/AllItems.aspx?View=% 7B6E034859%2DE9E5%2D491E%2D8D0A%2D02F3A36250AB%7D#InplviewHash6e03485 9-e9e5-491e-8d0a-02f3a36250ab=

4.4.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 IAW Exhibits X, XX, 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.4.5 Technical Data:

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

Agile Efforts will be performed per this Section:

In addition to the above, deliveries will be made in appropriate increments as defined by the Government. (CDRLs A00D DI-SESS-81000F/T, PRODUCT ENGINEERING DESIGN DATA

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

REQUIREMENTS)

4.4.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 Compliant Technical Order (TCTO) and Technical Order generation and support to the 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 DGS-X 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)

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/HBGB ISR Ground Software Management Team (thru AFLCMC/HBGB Data Management) for the Nexus SW Repository after acceptance test/at 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))

4.4.5.2 Software Deliverable:

All software source code, build environment and associated data files that the Contractor asserts as Government Purpose Rights shall be delivered to the Government for the current operational baseline every PI. As a minimum the Contractor shall deliver a Software Product Specification (SPS) and the Software Version Description (SVDD) for each application. 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); A00W DI-IPSC-81441A/T,

SOFTWARE PRODUCT SPECIFICATION (SPS))

4.5 Funding:

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

4.6 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.7 Cost Limitation (Applicable to Cost Reimbursement Contract Types):

The Contractor shall meet or stay within cost for all products and services delivered under the task order. In accordance with FAR 52.232-20, the Contractor shall notify the Contracting Officer in writing whenever it has reason to believe that:

• The costs the Contractor expects to incur under this contract in the next 60 days, when added to all costs previously incurred, will exceed 75 percent of the estimated cost specified in the Schedule; or contract.

• The total cost for the performance of this contract, exclusive of any fee, will be either greater or substantially less than had been previously estimated.

• As part of the notification, the Contractor shall provide the Contracting Officer and Program Manager a revised estimate of the total cost of performing this contract. Except as required by other provisions of this contract, specifically citing and stated to be an exception to this clause:

• The Government is not obligated to reimburse the Contractor for costs incurred in excess of the estimated cost specified in the Schedule or, if this is a cost-sharing contract, the estimated cost to the Government specified in the Schedule, and contract.

• The Contractor is not obligated to continue performance under this contract (including actions under the Termination clause of this contract) or otherwise incur costs in excess of the estimated cost specified in the Schedule, until the Contracting Officer (i) notifies the Contractor in writing that the estimated cost has been increased and (ii) provides a revised estimated total cost of performing this contract. If this is a cost-sharing contract, the increase shall be allocated in accordance with the formula specified in the Schedule.

• For under-running CLINs with expiring funds, this notification shall occur NLT 1 July of the current fiscal year.

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 contract. 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 PCO 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 contract will be generated, maintained, and delivered on a monthly basis.

4.9 Specific Work to Be Accomplished:

Crew Comm:

• Provide investigation, analysis, evaluation, testing and solutions for problems identified by the field and in-plant personnel.

o Investigate problems and provide recommended solutions resulting from material DRs, design deficiencies, quality assurance deficiencies, Vanishing Vendor Items (VVI), failures, and malfunction of material or components. The Contractor shall provide solutions that can be merged and fielded with no additional rework following fielding unless authorized by the Government for an interim solution.

o Diagnostic routines to determine system readiness and locate fault conditions.

o Evaluation and analysis of any data collected relating to field operations.

o Develop requirements including, in addition to the development of Waterfall requirements, developed other requirements, such as, but not limited to, Epics and User Stories for system improvements.

o Furnish technical cost data and support required for the development this TD.

• Provide engineering and technical services in support of updates as requested by the Government Program Manager.

• Provide general engineering and other technical information on the overall system as requested by the Government Program Manager.

• Provide an integrated logistics program covering planning, deployment, and in-plant control systems and spare parts. Provide the planning, deployment, and in-plant control of other logistics support efforts such as handbooks, training, field service operations, and field returns. These activities will be provided until such time as the applicable AF DCGS sustainment activities are transitioned to the DSIL. (CDRL A01W DI-SESS-

81759A/T, LOGISTICS PRODUCT DATA SUMMARIES)

• The Contractor shall manage and maintain a provisioning database to support the customer’s spares management program in compliance with the AF IUID program. Parts will be registered and marked according to AF IUID guidelines. Spares Status Reports

(SSR) shall be prepared and delivered to the Government on a quarterly basis to support this effort from the UID database.

• Provide software and system engineering services by maintaining a capability to investigate improvements in the areas of processing throughput, accuracy, reliability, diagnostic fault testing, and overall performance. Establish and maintain a Software Configuration and Control System.

• Furnish technical assistance and coordination for spare parts acquisition, SRA assistance, and technical documentation.

• The Contractor shall perform special studies when directed by the Government to investigate potential obsolescence parts issues, user capabilities suggestions, software enhancements, or reliability and maintainability improvements with the system.

• Coordinate efforts as necessary with other agencies/Contractors to ensure that systems, equipment, and support equipment requirements are properly established and implemented.

• Annual Crew Comm Lab Inventory at Collins Aerospace (RTX) Dulles facility, to either be done in person or via table top review, if feasible.

• Execute Crew Comm System upgrades required to maintain Authority to Operate (ATO);

o Execute monthly Operating System Security Patching and validation.

o COTS software update to latest approved and required baseline.

o Generate and provide documentation, media, and instructions necessary to incorporate software upgrades noted above in Government designated testing facilities.

o Support generating documentation necessary to release fielding Time Compliance Technical Orders (TCTO) for upgrades.

o Support initial installation, integration, and functional verification of upgrades at the designated Government testing location.

o Provide required media and software for Security assessment to attain and maintain Certificate to Field (CtF).

4.10 Program Management and Administrative Support:

The Contractor shall establish and maintain a program management office in support of all tasks related to the contract and its task orders. The Contractor shall also provide a point of contact for the Government. The Contractor shall assign a program manager (PM) to plan, organize staff, administer, and control all contract activities, and to ensure cost, schedule and technical objectives are achieved. The Contractor shall establish budgets, schedules, and specific tasks to meet overall program objectives. Periodic status updates shall be conducted to monitor cost and schedule performance.

Contractor’s Progress Status and Management Report (CPSMR) (A005), Cost Funds Status Reports (CFSR) (A004), Contract Work Breakdown Structures (CWBS) (A00S), Status Report (A015), Funds & Man Hours Expenditure Report (A014), and Integrated Program Management Report (IPMR) (A01Q) will be submitted to the Government for each task order as required by

CARNS, DWIGHT B CTR USAF AFMC AFLCMC/C3IAA

Does this need to change?

the applicable CDRL. The Contractor shall attend/support management meetings as deemed necessary by the Government program office. The Contractor shall assign a program manager to each task order. The Contractor may assign PMs to one or more programs as required to meet task order requirements. Program Managers shall be available during normal business hours and be available during a regular 40 hour work week. The Contractor shall provide technical/programmatic liaison support to DCGS Program Execution. Expected support includes but is not limited to tasks such as facilitator, coordination of activities, investigation and analysis, problem resolution, engineering interface, programmatic support, documentation preparation and ad hoc requests by the Government.