RDS Sustianment PWS v2 6Nov2026.pdf

Radio Distribution System (RDS) Sustainment PWS

CDRL Data Item # Title/Subtitle PWS Section Freq

A001 DI-MGMT-81900 RDS Product Roadmap 1.1 ASREQ & 30

DAC

A002 DI-IPSC-81756/T RDS HW and SW Documentation 1.1.1

Delivered 14 Days after Test complete

A003 DI-SESS-81639 RDS Repair and Replace Report 1.1.1 Delivered 14

Days after Repair complete

A004 DI-MISC-80508B/T RDS Major Updates and Emergency Fixes

1.1.2, 1.1.3, 1.1.5

Delivered 14 Days after Test

Complete A005 DI-MISC-80508B/T RDS Quarterly Security Updates (Cyber) 1.1.2, 1.1.3 Quarterly

A006 DI-SESS-81757A RDS Test and Training Suites 1.1.4

Delivered 10 Days prior to the

Final design Review & 60

DAC

A007 D1-PSSS-82210 RDS Training Materials 1.1.6

Delivered 30 Days prior to 1st Training and 30

Days prior to subsequent

Training Events

A008 DI-MISC-80508B/T RDS HD Summary Report 1.1.7 Quarterly & 30

DAC

A009 DI-MGMT-80441D RDS Government Property Inventory Report 1.1.8 ANNLY, ASREQ

& 30 DAC

1. Radio Distribution System (RDS)

Scope of this effort is sustainment of the RDS version 2.X baseline to maintain security and functionality.

This RDS effort shall begin when the prior SAIC RDS contract ends, so as not to have a duplicative sustainment and upgrade effort to said system.

The Contractor shall participate and contribute to RDS Weekly Meeting and various RDS related Government meetings as directed by the Government. The Contractor shall provide weekly RDS minutes and briefing slides.

1.1. RDS Sustainment

The Contractor shall provide sustainment support for the RDS v2.X baseline. The Contractor shall sustain a system that adheres to required current USAF and DoD Cybersecurity standards while providing the functionality required by the end user.

The Contractor shall develop and maintain an RDS product roadmap that notifies the Government of end of life, support, obsolesces, or other events that affect equipment and software availability, usefulness, and supportability.

[CDRL A001]

1.1.1. Hardware & Software Support

The Contractor shall provide hardware support for existing and newly installed hardware by replacement or repair. The Contractor shall provide three (3) year warranty on all hardware and leverage original equipment manufacturer (OEM) provided warranty to reduce costs. The hardware support and sustainment are a continuation from the SAIC RDS contract.

The Contractor shall provide the Government all software registration, license key, and annual support information for all, and any software purchased and/or installed and configured on the system equipment.

[CDRL A002]

The Contractor shall notify the Government of hardware that needs to be repaired or replaced and upon Government approval process sites Return Material Authorizations (RMA) requests.

The Contractor shall make the determination whether an item needs to be replaced within seventy-two (72) hours. The Contractor shall maintain RDS hardware as ready spares to meet replacement turn-around times for unit failures. The Contractor shall store the ready spares for Contiguous United States (CONUS) sites at their facility. Ready spares for Outside Contiguous United States (OCONUS) units (603rd and 607th) shall be delivered to the site for storage. The replacement hardware shall be shipped preprogrammed to the maximum extent possible, to include settings from the FAT or site installation checkouts. Replacements for CONUS units, to include Hawaii, can be shipped by FEDEX or UPS or another government approved carrier for overnight shipment. Equipment for OCONUS units shall be coordinated with the Government and moved by military air (MILAIR) including the RMA equipment. Hardware returned to the Contractor to be repaired can be returned to “Ready Spare” state for future use.

The Contractor shall provide a report when equipment has been repaired and/or replaced which includes details on the LRU or major assembly, description, part number, failure details, date replacement shipped, date equipment fixed, and tracking information as applicable. The current availability of ready spares should be included in this report. This report can be in the Contractor’s desired format.

[CDRL A003]

The Contractor shall ensure that all hardware delivered under this effort shall include associated software, documentation, and associated peripherals required for operations (such as controllers, connectors, cables, drivers, adapters, etc.) as provided by the Original Equipment Manufacturer (OEM). This is true only if the applicable OEM provides such items with the product itself.

Additionally, the Contractor shall provide special asset tags in accordance with (IAW) Department of Defense Instruction (DoDI) 8320.04, Unique Identification (UID) Standards for Tangible Personal Property, to Include Unique Identification (IUID) tagging requested by non- DoD customers.

1.1.2. Software Upgrades

The Contractor shall sustain the RDS 2.X baseline via three release mechanisms to address changing functionality requirements, end of support/life issues, or cybersecurity concerns: major updates, minor updates, and emergency updates or fixes (eFIXes). Major updates include significant changes in hardware, functionality, or software (e.g. addition of WSUS server and WAVE server), minor updates include mainly security updates (e.g. quarterly security updates), and eFIXes address issues that arise in the field that have critical impacts to operations or cybersecurity posture and must be addressed immediately.

The Contractor shall load, configure, test, and provide security updates to maintain and improve the cybersecurity posture of the system via all three release mechanisms. Major and minor updates shall include DISA Information Assurance Vulnerability Alerts (IAVAs), STIGS, and antivirus updates. The required updates are set forth by DoD 8510.01 Risk Management Framework Information Technology. Specifically, the Contractor shall ensure that all application deliverables comply with the DISA Application Security & Development STIGs. The Contractor shall review the contents of each update with the Government and shall test all updates at the Contractor’s facility prior to delivery to ensure functionality is maintained and additional cybersecurity vulnerabilities are not created. The Government may approve/delete implementation or application of STIG or IAVA. The Contractor shall notify the Government of any changes that have a detrimental effect on the system for review prior to delivery. All three releases mechanisms shall be tested to ensure proper functionality and acceptable cybersecurity posture.

Major updates shall be denoted by changes to the second decimal point (e.g. 2.X or 2.2), minor updates shall be denoted by changes to the third decimal point (e.g. 2.2.X or 2.2.2), and eFIXes shall be denoted by changes to the fourth decimal point (e.g. 2.2.X.X or 2.2.1.1). This will allow for improved configuration and version control of the system. Additionally, the Contractor shall deliver all updates, eFIXes, and supporting documentation on either CD-R, DVD or DoD SAFE and provide a quarterly software update report detailing the contents of the update. The timeline and frequency of major updates and eFIXes will be based on the product roadmap, operational issues, and other factors such as DoD mandates.

The Contractor shall run the ACAS/Nessus and STIG scan on the proposed RDS version upgrade and send the ACAS/Nessus and STIG report to the AOC Radio PM for Cyber review prior to fielding.

[CDRL A004] & [CDRL A005]

1.1.3. Cybersecurity

The Contractor shall ensure all personnel performing cybersecurity activities obtain and remain current with required technical and/or management certifications IAW DoD 8570.01-M and DoD Directive 8140.0.1. The Contractor shall also have the ability to receive, safeguard, store, and report on classified vulnerabilities and functional issues (up to SECRET) with the Government.

The Contractor shall support the Government in maintaining the RDS Authorization and Accreditation (A&A) for operation IAW DoD and AF policy, specifically DoDI 8510.01, Risk Management Framework (RMF) for DoD Information Technology (IT) (RMF-IT) and Air Force Instruction (AFI) 17-101, Air Force RMF Program. The most current version of RDS (v2.3) has the System Categorization levels of Confidentiality: Low; Integrity: Low; and Availability:

Medium. Additionally, all application deliverables shall adhere to Public Law 111- 383 and all system deliverables shall comply with DoDI 8500.1, Cybersecurity (Incorporating Change 1, effective October 7, 2019), and AFI 17- 130, Air Force Cybersecurity Program Management.

The Contractor shall support the Government in the creation, maintenance, and execution of all RMF Security Authorization Package documentation and artifacts associated with obtaining an RMF ATO. This includes the classified Plan of Action & Milestone (POA&M), the Continuous Monitoring Plan, System Security Plan, and Security Assessment Report (SAR). Additionally, the Contractor shall recommend updates to the RDS Accreditation Boundary diagram as required to reflect changes to the system.

The Contractor shall support the Government in continuous monitoring of the system and cybersecurity testing conducted by the Government. Continuous monitoring involves evaluating the effectiveness of the system security controls and any proposed or actual changes to the system and its operational environment. At least one third of all required security controls are to be assessed and reviewed each year. The breadth, depth, and rigor of these annual assessments are reflective of the security categorization and threats to the system. Government cybersecurity testing includes the Cyber Vulnerability Identification (CVI) testing conducted by the 47th Cyber Test Squadron (47 CTS). The Contractor shall plan to support one (1) CVI test per major release or when the ATO is up for renewal.

The Contractor shall monitor system security posture and compliance IAW DoD patches, DISA STIGS, and TASKORDs (i.e. Two-Factor Authentication, Windows, etc.) and provide results of new vulnerabilities discovered, closed, and the total count of open and closed vulnerabilities each quarter. The list should be broken by category (Database, Operating System (OS), Application, etc.) and organized by severity. All open vulnerabilities must be added to the POA&M with the following columns completed: estimated date of completion, cost, level of effort, and mitigations to address the open vulnerabilities.

The Contractor shall conduct cybersecurity testing and Assured Compliance Assessment Solution (ACAS) scanning to identify vulnerabilities within the system. The Contractor shall review the test results/scans and either fix or justify why it cannot be fixed (e.g. functionality would be broken). The Contractor shall report these vulnerabilities and the state of each vulnerability (e.g.

open, fix in progress, fix being tested, fixed) to the Government. This support may require cybersecurity testing at Government facilities at Langley Air Force Base (AFB) (or alternative site as designated by the Government) annually or a less interval to maintain the ATO. All vulnerabilities shall be treated as classified and communicated to the Government. Additionally, the Contractor shall notify the Government of all security impacts, both positive and negative, contained within each update resulting from these security updates.

[CDRL A004] & [CDRL A005]

1.1.4. Test and Training Suite

The Contractor shall sustainment/maintain two (2) Test and Training Suites that shall be functionally representative of the fielded RDS baseline and shall be used to support onsite training and various test events. Two (2) suites are required to ensure that shipment from one site will not affect the start of the fielding to the next. The Contractor shall keep both suites updated and ensure it’s delivered in time to various sites in accordance with the training schedule. The Government shall work with the Contractor to coordinate the shipment of the suites from site to site.

The Contractor shall sustain the suites in transit cases to aide in shipping and minimizing tear down and setup times.

[CDRL A006]

1.1.5. Contractor Testing

The Contractor shall maintain a representative test environment and test iteratively to ensure early insight into development, cybersecurity, functional, interoperability, and integration issues.

The Contractor shall perform testing and inspections of all system services to ensure the technical adequacy and accuracy of all work, including reports and other documents required in support of that work, and provide the results of that testing in a report to the Government.

[ CDRL A004]

The Contractor will also support the Government’s plan for acceptance and cybersecurity testing to ensure the product is secure and works as intended. The plan shall consist of a program of tests, inspections, and demonstrations emulating real-world usage conditions to verify compliance with the requirements of this Performance Work Statement (PWS).

1.1.6. Training

The Contractor shall conduct an analysis at each version update to determine what level of training is required and ensure the training stays current with the services offered and system updates throughout the life of the contract. At a minimum, the Contractor will provide training on every major version and provide an overview of content and list of bugs fix descriptions with the delivery of minor security updates and eFIXes if there is a security feature or bug fix that requires some level of user awareness on the use of applications or maintenance procedures of the system.

The Contractor shall develop student and instructor training materials with supplemental PowerPoint presentations, and a curriculum which covers difference, maintenance, and operator training for System Administrator (SysAd), Network Administrator (NetAd), and Operators

(contractor and Government). The manuals can be in contractor format and must be kept updated.

The Contractor shall provide onsite training in a classroom environment provided by the Government and utilize the Training and Test Suite mentioned in Section 1.1.4. to provide the training as to not bring risk to the operational RDS suites. The training concept is “train the trainer”; the Contractor shall train a group of personnel that will be tasked to pass the training onto others in the unit. The class size is about seven (7) to twelve (12) students. The training schedule will be based on the fielding schedule as directed by the Government. Additionally, the completion of the classroom instruction should not be dependent on access to commercial internet connections or cell phone services.

The Government will provide a suitable classroom environment and equipment (e.g. projector, dry erase boards, etc.). In the case that a computer or laptop is not made available, the instructor may bring their own laptop to support the training. However, the instructor’s laptop must be cleared in advance for entry into any secure areas for each AOC site and may be required to be scanned. The Contractor shall notify the Government with the make, model, and software installed fifteen (15) business days prior to arrival so coordination can be accomplished. Additionally, the Government will assist with shipping in situations where the host country influences shipping of training and instructor materials.

[CDRL A007]

1.1.7. Help Desk Support

The Contractor shall provide both remote and on-site RDS v2.X Tier 1 Help Desk support (as needed) to the AOC Tier 0 Help Desks. The Contractor shall provide an email and telephone capability to the AOC units to alert the Contractor of any issues. All requests shall be logged, recorded, actioned as appropriate, with results recorded in the trouble ticketing system and passed along to the Tier 2 RDS Help Desk. The Contractor shall notify the Government of any issues that would require a change in the system for resolution and direction.

The Contractor shall provide an email and telephone capability to the AOC units to alert the Contractor of any issues. All requests shall be logged, recorded, acted as appropriate, with results recorded in the trouble ticketing system. Additionally, the Contractor shall provide on-site support as directed by the Government in support of critical trouble tickets that remain unsolvable through phone support and replication. Travel is estimated at about six (6) trips a year for one to two (1-2) personnel for one to two (1-2) weeks at a time and includes both normal troubleshooting efforts as well as support for exercises. The Contractor shall be responsible to ensure their personnel have the required passports, visas, licenses, and permits to support this effort.

The Contractor shall provide and have the ability to maintain a classified trouble ticket reporting system that tracks the issues, the fix action, open and closure metrics, and other similar information. The Contractor shall deliver a report that summarizes and presents this data to the Government. This report is to be unclassified and shall at a minimum contain a number of calls by site (general reference), type, and date.

The Contractor shall provide a standard response time for issues within eight (8) hours by either phone or email.

The Contractor shall provide 24 x 7 hours support 365 days as follows: Manned Help Desk operations Monday – Friday from 0800 – 1700 Eastern Time, excluding Federal Holidays. An after-hours cell phone will be used for all after hour, weekend, and federal holiday calls.

The Contractor shall provide an RDS Help Desk call number (xxx) xxx-xxxx for 24 x 7, 365-day support.

[CDRL A008]

1.1.8. Government Property Management and Physical Inventory Review

The Contractor shall establish, maintain, and administer an auditable property management system in accordance with Federal Acquisition Regulation (FAR) 52.245-1, Government Property; Defense Federal Acquisition Regulation Supplement (DFARS) 252.245-7003, Contractor Property Management System Administration; DFARS 252.245-7005, Management and Reporting of Government Property; DFARS 252.245-7002, Reporting Loss of Government Property; and DFARS 252.211-7003, Item Unique Identification and Valuation.

Additionally, the Contractor’s property management and sustainment procedures shall comply with DoDI 5000.64, Accountability and Management of DoD Equipment and Other Accountable Property; DoDI 4161.02, Accountability and Management of Government Contract Property;

DAFMAN 23-122, Materiel Management Procedures; and DAFI 63-101/20-101, Integrated Life Cycle Management.

The Contractor shall maintain 100 percent custodial accountability and life-cycle visibility for all Government Property (GP), including both Government-Furnished Property (GFP) and Contractor-Acquired Property (CAP), in the possession of the Prime Contractor and its lower-tier subcontractors, including By Light.

1.1.8.1 Annual Physical Inventory Requirement

Inventory Execution: The Contractor shall perform a complete 100 percent wall to wall physical inventory of all Government Property held under this contract/task order at least once annually, not to exceed 365 365 calendar days from the previous inventory or modification-award date.

This scope encompasses all serialized equipment suites, ancillary support items, and Overseas Contingency equipment, whether in transit, in storage, undergoing maintenance/modification or located at subcontractor facilities. This requirement includes the two (2) RDS Test and Training Suites maintained to be functionally representative of the fielded RDS baseline.

Baseline Reconciliation and Readiness Tracking: The Contractor shall reconcile physical inventory counts, serial numbers, Item Unique Identification (IUID)/Unique Item Identifiers (UII), physical locations, and Federal Condition Codes against internal property accountability records, the DoD IUID Registry, and the approved GFP Attachment within the Procurement Integrated Enterprise Baseline Reconciliation and Readiness Tracking. The Contractor shall reconcile physical inventory counts, serial numbers, Item Unique Identification (IUID)/Unique Item Identifiers (UII), physical locations, and Federal Condition Codes against internal property accountability records, the DoD IUID Registry, and the approved GFP Attachment within the Procurement Integrated Enterprise Environment (PIEE) GFP Module. All discrepancies, unrecorded configuration changes, duplicate records, or unaccounted assets shall be documented with root-cause findings and corrective-action plans. Environment (PIEE) GFP Module. All discrepancies, unrecorded configuration changes, duplicate records, or unaccounted assets shall be documented with root-cause findings and corrective-action plans.

Loss, Damage, Destruction, and Theft (LDDT): Any shortages, damage, or unaccounted-for property identified during the physical inventory or normal operations shall be documented and formally reported through the PIEE GFP Module / Property Loss Tool in accordance with FAR 52.245-1(f)(1)(vii) and applicable contract requirements within ten (10) business days of discovery.

1.1.8.2 Government On-Site Review and Verification

Right of Access & Oversight: The Government reserves the right to conduct on-site inventory reviews, Property Management System Analysis (PMSA) audits, product support readiness inspections, and physical count verifications at any Prime Contractor or subcontractor facility housing Government Property under this contract.

On-Site Physical Review Support: Upon receipt of Government notification with a minimum of ten (10) business days advance written notice, unless exigent mission or audit circumstances warrant immediate access, the Contractor shall:

• Grant authorized Government representatives, including the Procuring Contracting Officer (PCO), Administrative Contracting Officer (ACO), as applicable, Contracting Officer's Representative (COR), Government Property Administrator (GPA), and Plant Clearance Officer (PLCO),and Program Office Logistics/Product Support personnel, unrestricted physical access to facilities, test laboratories, staging bays, stockrooms, and secure storage locations housing Government Property, subject to applicable installation security, safety, access-control, and information-handling procedures.

• Designate a qualified Contractor Property Administrator or equivalent subcontractor lead, to accompany Government personnel throughout the on-site physical review.

• Provide all necessary material handling equipment, test-area access, safety equipment, counting aids, and secure staging areas to facilitate physical verification, photographic or visual serial number inspections, and barcode/Unique Item Identifier (UII) scans.

• Make all property records, custodial ledgers, PIEE receipt and shipment transactions, maintenance and configuration logs, and sub-tier vendor records available for immediate audit and sampling.

Joint Count / Discrepancy Resolution: If the Government elects to execute a joint sample or wall-to-wall count during the on-site visit, the Contractor shall participate in real-time reconciliation, co-sign count sheets, and initiate immediate corrective action on identified variances in accordance with DAFMAN 23-122.

1.1.8.3 Inventory Deliverables and CDRL Reporting

Reporting Obligation: The Contractor shall prepare and submit an annual Government Property Inventory Report in accordance with Exhibit C, CDRL C010, RDS Government Property Inventory Report. To support audit readiness and product-support baseline requirements, the report shall capture complete physical inventory results, reconciliation status, nomenclature, National Stock Number (NSN), if assigned; manufacturer part number; serial number; UII, if registered in the IUID Registry; quantity; unit acquisition cost; current physical location, including subcontractor facilities; and Federal Condition Code.

Delivery Frequency: In accordance with CDRL A009, the inventory deliverable shall be submitted annually, no later than thirty (30) calendar days following the completion of the annual physical count, as required upon PCO or COR request, and upon contract/task order completion or termination as a Final Inventory Report and Disposition Report.

[CDRL A009]

1.2. RDS Locations

Below is the current list of RDS locations that need to be supported.

Order Site Location 1 217th ARC Battle Creek, MI 2 152nd ARC Syracuse, NY 3 157th ARC St Louis, MO (Jefferson Bks) 4 183rd ARC Springfield, IL 5 193rd ARC State College, PA 6 603rd AOC Ramstein AB, Germany 7 607th AOC Osan AB, Korea 8 608th AOC Barksdale AFB, LA 9 609th AOC Shaw AFB, SC 10 609th AUID TBD 11 612th AOC Davis-Monthan AFB, AZ 12 613th AOC Hickam AFB, HI 13 TTS Test and Training Suite 14 700 & Help Desk Langley AFB, VA 15 701st AOC March ARB, CA 16 FTU 505th Hurlbert Field, FL 17 PC Langley AFB, VA

18 TBD TBD

19 TBD TBD

20 TBD TBD