B08 - W15P7T-27-R-A001 -Attachment 0001 -PWS - SETA PSC_19Aug2026_Final..pdf

CUI

PERFORMANCE WORK STATEMENT (PWS)

FOR

BASE EMERGENCY COMMUNICATIONS SYSTEM (BECS)

SYSTEMS ENGINEERING AND TECHNICAL ASSISTANCE (SETA) SUPPORT

Controlled By: Product Director Base Emergency Communications System (PD BECS) CUI Category: PROCUREMENT AND ACQUISITION

Distribution/Dissemination Control: Acquisition Sensitive POC: Christian Ross, 571-595-9793

Capability Program Executive (CPE)

Command and Control Information Network

(CPE C2IN)

Project Manager Integrated Enterprise Network (PM IEN)

Product Director Base Emergency Communications System (PD BECS)

19 August 2026

Controlled By: Product Director Base Emergency Communications System (PD BECS) CUI Category: PROCUREMENT AND ACQUISITION

Distribution/Dissemination Control: Acquisition Sensitive

Table of Contents

1. Introduction

1.1 PURPOSE

1.2 BACKGROUND

1.3 OVERVIEW

2. Scope

3. Objectives

4. Performance Requirements

4.1 CONTRACTOR-PROVIDED SERVICES

4.2 PERFORMANCE CRITERIA

4.3 PERFORMANCE STANDARDS

5. Task Description

5.1 ENTERPRISE ARCHITECTURE

5.1.1 PROGRAMMATIC SUPPORT AND PLANNING

5.1.2 Engineering and Integration Support

5.1.3 Cybersecurity Management

Controlled By: Product Director Base Emergency Communications System (PD BECS) CUI Category: PROCUREMENT AND ACQUISITION

Distribution/Dissemination Control: Acquisition Sensitive

5.2 PSAP MODERNIZATION

5.2.1 SYSTEM DESIGN AND PLANNING

5.2.2 SYSTEM IMPLEMENTATION AND INTEGRATION

5.2.3 CYBERSECURITY MANAGEMENT

5.3 NG-911 INFRASTRUCTURE MODERNIZATION

5.3.1 NG-911 INFRASTRUCTURE PLANNING AND INTEGRATION

5.3.2 CYBERSECURITY MANAGEMENT

5.4 COMMERCIAL NGCS AND ARMY ESINET IMPLEMENTATION

5.4.1 PROGRAMMATIC SUPPORT AND PLANNING

5.4.2 CYBERSECURITY MANAGEMENT

5.5 LMR MODERNIZATION

5.5.1 LMR SYSTEM MODERNIZATION AND PLANNING

5.5.2 SYSTEM TESTING AND INTEGRATION

5.5.3 CYBERSECURITY MANAGEMENT

5.6 ARMY EMWN MODERNIZATION

5.6.1 ARMY EMWN MODERNIZATION AND PLANNING

5.6.2 SYSTEM DESIGN, TESTING, AND DEPLOYMENT

5.6.3 CYBERSECURITY MANAGEMENT

5.7 CONFIGURATION MANAGEMENT

5.8 BECS MARKET ANALYSIS

5.9 PSC TEST AND VALIDATION SUPPORT

6.1 PROGRAMMATIC AND ENGINEERING SUPPORT

6.1.1 ARCHITECTURAL MODERNIZATION PLAN

6.1.2 SYSTEM DESIGN DOCUMENTS

6.1.3 INTEGRATION AND TESTING PLANS

6.1.4 CYBERSECURITY ASSESSMENT REPORTS

6.2 CONFIGURATION MANAGEMENT

6.2.1 ASSET DATABASE ENTRIES

6.2.2 ASSET DATABASE UPDATES

6.2.3 ASSET DATABASE SYNCHRONIZATION

6.2.4 ENGINEERING CHANGE PROPOSALS (ECPS)

6.3 CYBERSECURITY AND COMPLIANCE

6.3.1 RMF CERTIFICATION

6.3.2 POA&M’S

6.4 MODERNIZATION TRANSITION REPORTS

6.5 MONTHLY INVOICE

6.6 MONTHLY STATUS REPORT

6.8 QUARTERLY PROGRAM REVIEW (QPR)

6.9 RISK MANAGEMENT

6.10 CONTRACTOR TRAVEL

7. General Information

7.1 PLACE OF PERFORMANCE

7.1.1 Situational Telework

Controlled By: Product Director Base Emergency Communications System (PD BECS) CUI Category: PROCUREMENT AND ACQUISITION

Distribution/Dissemination Control: Acquisition Sensitive

7.3 CONTRACT TYPE

10. Security

11. Contractor Training

12. Government Furnished Equipment (GFE)

THE GOVERNMENT WILL ENSURE THE CONTRACTOR HAS A

13. Quality Assurance Surveillance Plan (QASP)

14. Organizational Conflicts of Interest

15. Accounting and Appropriation Data

16. Post Award Administration

16.1 Contract Administration Data

16.2 CONTRACT MANAGEMENT

16.3 SUBCONTRACT MANAGEMENT

17. Contract Administration

APPENDIX A

LABOR CATEGORY DESCRIPTIONS AND REQUIRED QUALIFICATIONS

Controlled By: Product Director Base Emergency Communications System (PD BECS) CUI Category: PROCUREMENT AND ACQUISITION

Distribution/Dissemination Control: Acquisition Sensitive

1. Introduction

1.1 Purpose

This Performance Work Statement (PWS) defines the requirements for providing support to

U.S. Army with Public Safety Communications (PSC) within the Product Director Base

Emergency Communications System (PD BECS) program office. The level of effort shall include the delivery of professional services and engineering expertise focused on the integration, modernization, standardization, and enhancement of the Army’s PSC architecture to align with the Common Transport Layer and Services infrastructure within the greater Army

Global Unified Network. These services shall ensure that PD BECS provides mission command to emergency assets to guarantee a coordinated response to emergency incidents worldwide.

1.2 Background

PD BECS is responsible for establishing a single integrated acquisition program for the design, procurement, fielding, new equipment training and life-cycle management of emergency management/critical communications capabilities in support of installation public safety organizations and functions, including first responder, force protection and other installation management functions. This effort encompasses capabilities that deliver Computer Aided

Dispatch (CAD), Enterprise Mass Warning and Notification (EMWN), Land Mobile Radio

(LMR), Next Generation 911 (NG-911), and the First Responder Broadband Network - LTE-5G

(FRBN) and Emergency Services IP Network (ESINet).

This scope of work is to provide Subject Matter Experts (SMEs) in the field of Public Safety to support PD BECS’s mission to provide new or improved critical communications capabilities in response to the end users.

1.3 Overview

The Contractor shall provide programmatic support, systems engineering expertise, and cybersecurity management services to ensure the continued development and integration of interoperable emergency communications systems for the Army. The programmatic support required under this PWS shall include support related to NG-911 telecommunications infrastructure; LMR; Public Safety Answering Point (PSAP) Modernization (e.g., Computer-

Aided Dispatch (CAD), NG-911 Call Handling Equipment (CHE) capabilities); FRBN or

“FirstNet” interoperability; EMWN Giant Voice or “ALERT!”; and integration with Commercial

NGCS and Army / Department of War (DoW) ESINet deployment.. The Contractor shall provide required Systems Engineering and Cybersecurity support to PD BECS to oversee the modernization and maintenance of these systems to ensure interoperable, secure, and compliant operations.

2. Scope

The tasks described in this PWS require comprehensive support for the Army’s PSC Ecosystem, with emphasis on updating and modernizing existing public safety and telecommunications systems, integrating new technologies, and maintaining operational capability across installations worldwide. The Contractor shall update the PSC Ecosystem, ensuring that the components, such as NG-911 infrastructure (i.e., telecommunications, Location Information Services (LIS) and

Controlled By: Product Director Base Emergency Communications System (PD BECS) CUI Category: PROCUREMENT AND ACQUISITION

Distribution/Dissemination Control: Acquisition Sensitive

Geographic Information Systems (GIS)), LMR, EMWN, FRBN, and PSAP systems (i.e., CAD and NG-911 CHE), are fully integrated, interoperable, and compliant with Army and Department of War (DoW) standards.

The Contractor shall provide the following services:

1. Programmatic support for all tasks.

2. Systems engineering support for infrastructure and technology integration.

3. Cybersecurity management for compliance with Army and DoW standards.

4. Oversee testing, installation, and acceptance of updated systems.

5. Documentation and reporting related to system updates and ongoing operations.

6. Risk management to address any potential challenges in system integration and operation.

7. Market Analysis to establish cost alternatives.

3. Objectives

PD BECS requires continued systems engineering expertise in strategic planning, acquisition and technical planning, technical documentation, functional/system/technical requirements definition, legacy/existing capability modernization, convergence, interoperability, system and data architecture and design, and technical performance. The Contractor shall participate in activities associated with overall program execution, to include managing cost, schedule, and performance within the requirements baseline and programmatic constraint.

The Contractor shall ensure that consistency between DoW/Army Enterprise and PD BECS architectures is maintained as program capability evolves within the enterprise. This includes addressing integrated functionality and timely, accurate data exchange to conduct core mission operations.

The Contractor shall achieve the following results:

1. Fully integrated and modernized PSC Ecosystem.

2. Compliance with DoW cybersecurity regulations and Risk Management Framework

(RMF) certification.

3. Enhanced interoperability across systems to include:(PSAPs, NG-911 infrastructure, LMR, and EMWN).

4. Establish Key Performance Indicator thresholds for PSC systems that meet operational needs and mission requirements.

4. Performance Requirements

4.1 Contractor-Provided Services

The Contractor shall provide all services required under this contract and ensure all tasks are completed within established schedules, within allocated funding, and to the performance standards outlined in the PWS. The Contractor shall coordinate with the Army to provide technical oversight to ensure that BECS systems are integrated and functional.

Controlled By: Product Director Base Emergency Communications System (PD BECS) CUI Category: PROCUREMENT AND ACQUISITION

Distribution/Dissemination Control: Acquisition Sensitive

4.2 Performance Criteria

1. Oversee system integration and modernization to ensure they meet the technical specifications outlined in the PWS.

2. Cybersecurity compliance must be continuously maintained, with support towards achieving Authority to Operate (ATO) approvals.

4.3 Performance Standards

All performance outcomes shall be in accordance with Army and DoW objectives for emergency communications systems. The Contractor shall adhere to the DoW Cybersecurity policies and ensure PD BECS systems will meet DoW RMF certification and accreditation requirements.

5. Task Description

The Contractor shall provide subject matter expertise support across the program life cycle to meet program and mission execution requirements in accordance with defense acquisition policies and procedures to support achievement of program goals and milestones.

The Contractor shall perform the following tasks to ensure successful execution of the contract.

These tasks encompass programmatic support, engineering services, and cybersecurity management, all of which are essential to achieving interoperability, operational effectiveness, and compliance with DoW, Army, and applicable industry standards.

5.1 Enterprise Architecture

5.1.1 Programmatic Support and Planning

The Contractor shall provide programmatic support to update and modernize the Enterprise

Architecture for the Army’s PSC Ecosystem. The Contractor shall ensure the architecture is fully aligned with the Army Unified Network Strategy and supports interoperability across all communication systems. Required tasks include assessing the current architecture, identifying capability and integration gaps, and developing recommendations to address current and future

Army operational needs.

5.1.2 Engineering and Integration Support

The Contractor shall provide engineering expertise to oversee the integration and optimization of existing systems and ensure alignment with the Army's strategic vision for communications. The

Contractor shall develop a technical roadmap for architecture modernization that addresses performance, security, and scalability requirements.

5.1.3 Cybersecurity Management

The Contractor shall review vulnerability scans and cybersecurity assessments of the Enterprise

Architecture to verify compliance with DoW Cybersecurity policies. The Contractor shall develop and maintain Plans of Action and Milestones (POA&Ms) for all identified vulnerabilities and ensure timely remediation of security findings. All systems shall meet DoW

RMF requirements for certification and accreditation.

Controlled By: Product Director Base Emergency Communications System (PD BECS) CUI Category: PROCUREMENT AND ACQUISITION

Distribution/Dissemination Control: Acquisition Sensitive

5.2 PSAP Modernization

5.2.1 System Design and Planning

The Contractor shall support the modernization of PSAPs by providing engineering expertise to design and implement interoperable NG-911 CHE, CAD systems, and LMR Dispatch Consoles.

The Contractor shall ensure all systems are interoperable with other components of the PSC

Ecosystem and comply with applicable Army operational and cybersecurity standards, including

DoDD 8510.01 Risk Management Framework for DoD Systems (July 2022).

5.2.2 System Implementation and Integration

The Contractor shall provide engineering support for the installation, configuration, and testing of modernized PSAP systems to ensure seamless integration with existing Army infrastructure.

The Contractor shall ensure full operational capability and interoperability between CAD, NG-

911 CHE, and LMR systems.

5.2.3 Cybersecurity Management

The Contractor shall monitor and analyze the results of recurring cybersecurity scans of the

PSAP modernization systems to ensure compliance with DoW/Army cybersecurity standards.

The Contractor shall document all identified vulnerabilities in POA&Ms and ensure timely remediation of all findings. All systems shall achieve certification in accordance with RMF guidelines.

5.3 NG-911 Infrastructure Modernization

5.3.1 NG-911 Infrastructure Planning and Integration

The Contractor shall provide programmatic and engineering support for the implementation of

NG-911 infrastructure. The Contractor shall address GIS and LIS requirements and ensure accurate data integration to support efficient 911 call routing and handling.

5.3.2 Cybersecurity Management

The Contractor shall ensure that the NG-911 infrastructure, including the GIS and LIS systems, complies with all applicable DoW/Army cybersecurity regulations. The Contractor shall monitor and analyze cybersecurity scan results to ensure all vulnerabilities are addressed with POA&Ms.

The Contractor shall ensure the systems are compliant with DoW RMF for full accreditation.

5.4 Commercial NGCS and Army ESINet Implementation

5.4.1 Programmatic Support and Planning

The Contractor shall support connectivity of BECS NG-911 systems to commercial ESINets

(NGCS) and the projected development of the Army or DoW ESINet to ensure interoperability with the Army’s NG-911 infrastructure. The Contractor shall provide engineering support for the design, development, and deployment of these core services to meet Army operational and technical requirements.

5.4.2 Cybersecurity Management

Controlled By: Product Director Base Emergency Communications System (PD BECS) CUI Category: PROCUREMENT AND ACQUISITION

Distribution/Dissemination Control: Acquisition Sensitive

The Contractor shall ensure that the NGCS and Army ESINet comply with all applicable DoW and Army cybersecurity regulations. The Contractor shall monitor and analyze cybersecurity scans to ensure all vulnerabilities are addressed with POA&Ms.

5.5 LMR Modernization

5.5.1 LMR System Modernization and Planning

The Contractor shall provide engineering support for the P25 evolution of the LMR system and ensure compliance with DoW and Army interoperability and security standards. The Contractor shall support Enterprise Modernization efforts, including the integration of the Inter-RF

Subsystem Interface (ISSI), Radio over IP (ROIP) Gateway, and Location Tracking systems.

5.5.2 System Testing and Integration

The Contractor shall oversee testing and validation of the upgraded LMR system to ensure full compliance with P25 standards and verify all components (ISSI, ROIP, Location Tracking) are fully interoperable with Army communications networks. The Contractor shall review and provide detailed technical documentation and performance verification reports for the upgraded

LMR system as delivered by the integrator.

5.5.3 Cybersecurity Management

The Contractor shall oversee cybersecurity vulnerability scans for the LMR modernization system and ensure compliance with all applicable DoW and Army security policies. The

Contractor shall address identified vulnerabilities through POA&Ms, ensuring the system is compliant with the current RMF version for certification and accreditation.

5.6 Army EMWN Modernization

5.6.1 Army EMWN Modernization and Planning

The Contractor shall provide programmatic and engineering support for the modernization of the

Army's EMWN system. This effort includes upgrading the ALERT! and Giant Voice systems to enhance mass communication capabilities across Army installations. The Contractor shall ensure that the modernized EMWN system is interoperable with NG-911, LMR, and FRBN

(“FirstNet”) systems as appropriate.

5.6.2 System Design, Testing, and Deployment

The Contractor shall provide design and interoperability support for ALERT! and Giant Voice systems to ensure reliable and timely delivery of emergency notifications to Army personnel and dependents. The Contractor shall conduct interoperability testing as appropriate between

ALERT! and Giant Voice systems and ensure that all elements of the EMWN system comply with DoW security policies and Army communication standards.

5.6.3 Cybersecurity Management

Controlled By: Product Director Base Emergency Communications System (PD BECS) CUI Category: PROCUREMENT AND ACQUISITION

Distribution/Dissemination Control: Acquisition Sensitive

The Contractor shall review regular cybersecurity scans provided by the vendors delivering the

EMWN system to ensure compliance with applicable DoW cybersecurity standards as appropriate. The Contractor shall document all identified vulnerabilities in POA&Ms and ensure they are remediated within the required timeframes to maintain system security and operational functionality.

5.7 Configuration Management

The Contractor shall provide comprehensive Configuration Management (CM) support to ensure all systems and documentation are properly identified, controlled, tracked, and maintained. The

Contractor shall establish and maintain configuration baselines; manage configuration items and associated records in the asset database, administer change control processes; support

Configuration Control Boards, and ensure all changes are documented, reviewed, approved, and implemented in accordance with Government policies and industry best practices. The

Contractor shall conduct configuration audits, maintain CM repositories (e.g. BECS Asset

Database), and provide timely reporting to ensure accuracy, traceability, and compliance across all program activities.

5.8 BECS Market Analysis

The Contractor shall analyze market conditions to support the development of cost alternatives associated with system architecture variants prepared for Government consideration and planning. The Contractor shall obtain pricing from a minimum of three (3) sources for all identified material and software identified in each architecture variant. The Contractor shall document the composite results into a Cost Benefit Analysis (CBA) that presents each variant as an independent Course of Action (COA) and identifies associated risks and opportunities for each COA.

5.9 PSC Test and Validation Support

The Contractor shall provide independent test and validation support to assess interoperability between PD BECS capabilities and other public safety related applications (e.g. Voice

Modernization), to include interoperability testing and staging proof of concept demonstrations in a controlled test environment.

6. Deliverables/Deliverables Schedule

The Contractor shall provide deliverables on or before the specific completion date(s). All deliverables identified below shall be submitted to the Contracting Officer Representative

(COR). The COR is responsible for tracking and acceptance.

Key milestones will be outlined in the Key Deliverables Schedule, with specific deadlines for the completion of each task. The Contractor is expected to meet these milestones to maintain cost, schedule and performance.

Table 1 – Deliverables Schedule:

Controlled By: Product Director Base Emergency Communications System (PD BECS) CUI Category: PROCUREMENT AND ACQUISITION

Distribution/Dissemination Control: Acquisition Sensitive

PWS

Reference

Deliverable Due Date Milestone/Task

Section 6.6 A001 - Monthly Progress

Reports

Monthly, on the 5th calendar day Submit progress of deliverables, identifying potential risks, and highlighting any delays or challenges.

Section 6.3.2 A002 – POA&M’s As Required. Submit POA&M’s detailing vulnerabilities and actions taken.

Section 6.9 A003 - Risk Management

Plan (RMP)

60 business days from award. Plan for documenting and mitigating

PD BECS risks.

Section 6.8 A004 – Quarterly

Program Management

Review (QPR)

Quarterly. Month following each reporting quarter. Distribute briefing slides five

(5) business days before the scheduled briefing; distribute meeting minutes within three (3) business days following the briefing

Section 6.2.4 B001 – Engineering

Change Proposals (ECPs)

As Required Manage and submit BECS ECPs for requested modifications related to modernizations.

Section 6.1.2 B002 - System Design

Documents

Draft due-60 days after approved

Architectural Modernization Plan

Final due-90 days after approved

Architectural Modernization

Plan.

Deliver the finalized system designs for

NG-911, LMR, CAD, and other BECS systems.

Section 6.1.1 B003 - Architectural

Modernization Plan

Draft Plan-90 days after award

Final Plan-120 days after award

Submit a plan outlining the Enterprise

Architecture updates and integration strategy.

Section 6.1.3 D001 - Integration and

Testing Plans

As Required. Submit the integration and testing plans for Army installations.

Section 6.1.4 D002 - Cybersecurity

Assessment Reports

Quarterly, on the last day of the month.

Provide cybersecurity reports, including any vulnerabilities and fixes and upload them to Enterprise Mission

Assurance Support Service (eMASS).

Section 6.2.1 E001 – Asset Database

Entries

As Required. Populate asset database with “as built” data after BECS modernizations.

Section 6.2.2 E002 – Asset Database

Updates

As Required. Update asset database to reflect necessary changes.

Section 6.2.3 E003 – Asset Database

Synchronization

Monthly. Meet monthly with BECS logisticians to ensure synchronization across database platforms (e.g. asset database, DPAS, etc.)

Controlled By: Product Director Base Emergency Communications System (PD BECS) CUI Category: PROCUREMENT AND ACQUISITION

Distribution/Dissemination Control: Acquisition Sensitive

Section 6.5 F001 – Monthly Invoice Monthly, five (5) calendar days after the month in which services were performed.

Submit Contractor invoice in WAWF monthly.

Section 6.5 F001 – Monthly Invoice Monthly, five (5) calendar days after the month in which services were performed.

Submit Contractor invoice in WAWF monthly.

Section 6.10 G001 - Contractor Travel Request: Ten (10) business days before travel.

Report: Five (5) business days after travel.

Submit travel request authorization

(TAR) to government lead and travel report for Contractor travel

Section 6.7 G002 – Non-Disclosure

Agreement (NDA)

During employee in-processing Submit NDA for each employee.

Controlled By: Product Director Base Emergency Communications System (PD BECS) CUI Category: PROCUREMENT AND ACQUISITION

Distribution/Dissemination Control: Acquisition Sensitive

6.1 Programmatic and Engineering Support

6.1.1 Architectural Modernization Plan

The Contractor shall provide a detailed roadmap for updating the Enterprise Architecture to meet the Army Unified Network Strategy. The draft plan shall be delivered 90 days after contract award and the final plan shall be delivered 120 days after contract award.

[CDRL B003 – Architectural Modernization Plan]

6.1.2 System Design Documents

The Contractor shall review and provide feedback on the design and interoperability specifications for NG-911, LMR, CAD, EMWN, and other relevant public safety systems.

[CDRL B002 – System Design Documents]

6.1.3 Integration and Testing Plans

Submit specific plans for the integration and testing of new systems (e.g. ESINet) into the

Army’s PSC Ecosystem. [CDRL D001 – Integration and Testing Plans]

6.1.4 Cybersecurity Assessment Reports

Submit Quarterly reports in eMASS detailing the cybersecurity assessments, identified vulnerabilities, and remediation actions per RMF standards. [CDRL D002 – Cybersecurity

Assessment Reports]

6.2 Configuration Management

6.2.1 Asset Database Entries

Populate site asset database with “as built” BECS capabilities delivered per installation. [CDRL

E001 – Asset Database Entries]

6.2.2 Asset Database Updates

Update site asset database with a BECS related “adds, moves, or changes” to existing BECS capabilities supporting Army installations. [CDRL E002 – Asset Database Changes]

6.2.3 Asset Database Synchronization

Monthly coordination of BECS related information with Army logistics to ensure data synchronization across logistics database platforms. [CDRL E003 – Logistics Synchronization]

6.2.4 Engineering Change Proposals (ECPs)

Manage, submit, and track ECPs from users and system integrators, when received, to maintain, improve, or correct system performance, supportability, safety, or compliance with program requirements. [CDRL A001 – Engineering Change Proposals]

Controlled By: Product Director Base Emergency Communications System (PD BECS) CUI Category: PROCUREMENT AND ACQUISITION

Distribution/Dissemination Control: Acquisition Sensitive

6.3 Cybersecurity and Compliance

6.3.1 RMF Certification

Oversee integrator submittal of documentation in support of Authorization to Operate certification.

6.3.2 POA&M’s

Develop POA&Ms for addressing vulnerabilities discovered during regular cybersecurity assessments of modernization efforts. [CDRL A002 – POA&Ms]

6.4 Modernization Transition Reports

Review the integrator’s comprehensive plans for transitioning completed systems and responsibilities to the Army’s operational teams.

6.5 Monthly Invoice

The contractor shall submit a proper invoice in accordance with FAR clause 52.232-25 Prompt

Payment and DFARS clause 252.232-7003 Electronic Submission of Payment Requests and

Receiving Reports. The contractor’s invoice shall be submitted monthly not later than five (5) calendar days after the month in which services are performed. The Government payment office will not make disbursement to the Contractor without evidence of receipt and acceptance, or certification of the items invoiced from the COR. [CDRL F001 – Monthly Invoice]

6.6 Monthly Status Report

The Contractor shall provide a monthly report which summarizes overall work performed under the contract. The report shall detail work performed under each executed task area of this PWS

(Section 5), addressing completed tasks and the status of on-going tasks. For in-process tasks, the

Contractor shall identify accomplishments for the month, identify planned accomplishments for the coming month and potential risks that might negatively impact performance and proposed mitigation plans. Reports shall be submitted monthly on the 5th calendar day for the preceding month to the COR with a copy to the cognizant Contracting Officer. [CDRL A001 – Monthly

Status Report]

6.7 Non-Disclosure Agreements (NDA)

The Contractor shall submit a signed NDA to the COR via email during the assignment or in-processing of any Contractor employee performing work in support of this contract. The NDA will be provided during in-processing. If required by a Contracting Officer, in support of any acquisition and/or contracting support effort, the contractor shall be required to submit an additional signed NDA provided by and in accordance with said Contracting Officer guidance.

[CDRL G002 – Non-Disclosure Agreements (NDA)]

6.8 Quarterly Program Review (QPR)

The Contractor shall: (1) provide QPR briefings and perform the administrative functions to schedule the briefings, invite designated attendees, reserve conference rooms, and facilitate audio bridges; (2) draft and distribute agendas and briefing slides five (5) business days before the scheduled briefing and meeting minutes within three (3) business days of the briefing; and (3)

Controlled By: Product Director Base Emergency Communications System (PD BECS) CUI Category: PROCUREMENT AND ACQUISITION

Distribution/Dissemination Control: Acquisition Sensitive identify services that exceeded PRS level(s) that additionally provided a benefit(s) to the government by increasing efficiencies, saving costs, or other means. QPRs will provide an overview of Contractor accomplishments in all areas identified in the PWS and the degree to which the Contractor failed to meet, met or exceeded the performance standards. The reviews will identify or provide updated status on issues and risks that impact or could impact system or application availability, Contractor actions to correct or mitigate, and all Government dependencies. The QPR will address any high visibility or priority issues as identified by the

Government. The QPR will in all cases address continuous process improvement and staffing levels. The Contractor will provide an overview of compliance with performance metrics, the

Deliverable Schedule, and cost management during the preceding quarter. [CDRL A004 -

Quarterly Program Management Review]

6.9 Risk Management

The Contractor shall develop and implement a Risk Management Plan (RMP) which, at a minimum, addresses the following:

• Identify potential risks to system integration and performance.

• Mitigate risks related to system failure or delays.

• Cybersecurity risks through regular vulnerability assessments.

The Contractor shall manage program risks through the BECS SharePoint Risk Tracking System, ensuring all risks are captured, assessed, and actively monitored on a day-to-day basis. The Contractor shall keep the SharePoint repository current and provide the Government with real-time visibility into risk status and mitigation progress. The Contractor shall adhere to the following procedures for identifying and reporting potential risks. [CDRL A003 – Risk Management Plan]

6.10 Contractor Travel

Travel to other Government facilities while in the performance of the contract will be required for systems engineering support, testing support, and training support. All travel beyond the local area shall be approved in advance by the Contracting Officer Representative (COR) or the

Contracting Officer. All travel will be pre-approved by the COR with a ten (10) business day advanced notice of intent. The trip report will be submitted five (5) business days after travel.

The estimated number of trips for each contract year is 58. The travel and ODC’s will be on a cost no fee basis. Travel expenses will be reimbursed in accordance with the Joint Travel

Regulations (JTR). [CDRL G001 - Contractor Travel]

Controlled By: Product Director Base Emergency Communications System (PD BECS) CUI Category: PROCUREMENT AND ACQUISITION

Distribution/Dissemination Control: Acquisition Sensitive

7. General Information

7.1 Place of Performance

The primary place of performance will be at PL BECS’s government facilities, located on Fort

Belvoir, Virginia. Situational telework may be authorized for remote work on or outside of Ft.

Belvoir, VA to include any emergency, administrative closing or similar Government direct closings. Remote work is approved on a case-by-case basis for individuals who reside further than 75 miles of the places of performance listed above. Approval for remote work shall be approved by the Contracting Officer Representative (COR) prior to the Contractor working remotely. Additionally, the COR may approve situational/ad-hoc telework to meet mission requirements. The COR shall approve all telework prior to the Contractor employee working telework.

The Contractor is responsible for providing services between the hours of 0800-1700 hours

Monday thru Friday, except Federal Holidays or when the Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings. The Contractor shall always maintain an adequate workforce for the uninterrupted performance of all tasks defined within this PWS when the Government facility is not closed for the above reasons.

The Contractor will follow the Operational Status (workdays and hours) as established by the

Installation Commander and/or the Office of Personnel Management (OPM).

The Contractor will not be required to work the following Federal Holidays:

• New Year's Day (1st of January)

• Martin Luther King's Birthday (3rd Monday in January)

• President’s Day (3rd Monday in February)

• Memorial Day (Last Monday in May)

• Juneteenth (19th of June)

• Independence Day (4th of July)

• Labor Day (1st Monday in September)

• Columbus Day (2nd Monday in October)

• Veteran's Day (11th of November)

• Thanksgiving Day (4th Thursday in November)

• Christmas Day (25th of December)

Any other day designated by Federal Statute, Executive Order, and/or Presidential Proclamation.

7.1.1 Situational Telework

Approved Telework can be authorized by the Contracting Officer Representative (COR).

Telework shall adhere to the following conditions:

• At their own expense, have Internet provider services at their approved situational telework location/home;

• Forward all office calls to personal landline or cellular for the duty day;

• Available via phone to PD BECS during duty hours;

• Complete all assigned work according to procedures defined in this PWS

Controlled By: Product Director Base Emergency Communications System (PD BECS) CUI Category: PROCUREMENT AND ACQUISITION

Distribution/Dissemination Control: Acquisition Sensitive

• Participate telephonically/virtually in announced Government staff meetings and support on-site mission requirements as needed;

• Keep Government leads informed on the status of assigned tasks, deliverables, and suspense’s;

• Use Government issued office automation equipment, Government provided Collaboration and Network access tools in compliance with Cyber Security requirements and policies;

• Safeguard Government information from unauthorized disclosure, use, or damage. Report any instances to the Government POC immediately. However, no later than (NLT) 24 hours after identification of such an occurrence,

• All work provided in support of PD BECS must be done on GFE (laptops); Contractors are

NOT authorized to use personal computers. If employees do not have access to their GFE at home, they are NOT permitted to telework, even if telework is authorized.

7.2 Period of Performance

The Period of Performance for this contract is three (3) years. A base period of one (1) year, with two (2) one-year option periods. The Government may exercise the option periods in accordance with FAR 52.217-8, Option to Extend Services.

7.3 Contract Type

This contract will be awarded on a Cost-Plus Fixed Fee-(Term) with a Cost non-fee bearing

CLIN for travel. The travel CLIN will be a “not to exceed” cost CLIN.

8. Personnel Qualifications

The Contractor shall provide personnel possessing the education, experience, certifications, and security clearances necessary to successfully perform the requirements of this PWS. All personnel shall meet the minimum qualification requirements identified in Appendix A - Labor

Category Descriptions and Minimum Qualifications.

Contractor personnel shall possess demonstrated experience supporting DoW acquisition, systems engineering, cybersecurity, public safety communications, or other applicable technical disciplines commensurate with the labor category proposed.

The Government reserves the right to review personnel qualifications at any time during contract performance.

9. Key Personnel

The positions identified below are designated as Key Personnel due to their critical role in successful contract performance. Personnel proposed for these positions shall be available at contract award and shall remain assigned to the contract unless replacement is approved by the Contracting Officer.

Controlled By: Product Director Base Emergency Communications System (PD BECS) CUI Category: PROCUREMENT AND ACQUISITION

Distribution/Dissemination Control: Acquisition Sensitive

• Engineering Program Manager

• Next Generation 9-1-1 (NG-911) PSAP Engineer - Principal

• Next Generation 9-1-1 (NG-911) PSAP Voice Engineer - Principal

• Land Mobile Radio Engineer - Principal

The Contractor shall not remove, replace, or reassign Key Personnel without prior written approval of the Contracting Officer. Requests for replacement shall be submitted no fewer than fifteen (15) calendar days before the proposed replacement.

Any proposed replacement shall possess qualifications, education, certifications, security clearance eligibility, and relevant experience that are equal to or greater than those of the individual originally proposed.

The Government reserves the right to review and approve all proposed Key Personnel replacements.

This contract will be awarded on a Cost-Plus Fixed Fee-(Term) with a Cost non-fee bearing

CLIN for travel. The travel CLIN will be a “not to exceed” cost CLIN.

10. Security

The Contractor personnel performing under this contract will be U.S. Citizens and are required to obtain/retain a security clearance. All personnel staffed on this requirement shall have Active or

Interim SECRET Security Clearance prior to commencement of work and must maintain the level of security required for the life of the contract. All personnel shall have relevant certifications and experience in PSC systems and be familiar with DoW/Army regulations and requirements.

The Contractor shall be responsible for safeguarding all Government equipment, information, and property provided for Contractor use. At the close of each work period, Government facilities, equipment, and materials shall be secured.

The work associated with this contract is classified as Controlled Unclassified Information

(CUI).

11. Contractor Training

The Contractor shall comply with the following cybersecurity and Contractor training and certification requirements which may change over time should DoW or the Army change their requirements:

• Anti-Terrorism (AT) Level 1 Training. The Contractor requiring access to Army installations, facilities, and controlled access areas shall complete AT Level I awareness training within 14 calendar days after contract start date.

• Cybersecurity Awareness Training. The Contractor must complete the DoW cyber-security awareness training before issuance of network access and annually thereafter. All

Contractor employees working cybersecurity/IT functions must comply with DoW and

Controlled By: Product Director Base Emergency Communications System (PD BECS) CUI Category: PROCUREMENT AND ACQUISITION

Distribution/Dissemination Control: Acquisition Sensitive

Army training requirements in DoW 8570.01, DoW 8570.01-M, and AR 25-2 within six

(6) months of employment.

• OPSEC Training. Per AR 530-1, Operations Security, new Contractors must complete

Level I OPSEC training within 30 calendar days of their reporting for duty. All

Contractor employees must complete annual OPSEC awareness training.

• Threat Awareness Reporting Program (TARP). Training applies to all Contractors with security clearances. Per AR 381-12 all security clearance holders must receive

TARP training by a Counterintelligence (CI) Agent or other trainer as specified in 2-4b of

AR 381-12. The Contractor must complete training within two (2) weeks of onboarding.

All Contractor employees shall complete annually thereafter.

12. Government Furnished Equipment (GFE)

The Contractor shall provide the necessary professional services and personnel to perform the work outlined in the PWS. The Contractor shall ensure all personnel are qualified and experienced, with the appropriate security clearance, training, and certifications as outlined in the

PWS.

Access to Government offices and equipment, such as computers (to include all necessary hardware and software), an e-mail account, and Virtual Private Network (VPN) access, as required, shall be provided to the Contractor to coordinate completion of assigned tasks. All GFE shall be returned to the Government upon completion of the contract. The Contractor shall establish Contractor property management, inventory and accountability procedures and records, as well as maintenance procedures for the GFE. Government property shall be subject to the terms of the Federal Acquisition Regulation (FAR) Part 45.

The Government will ensure the Contractor has access to Army installations to support system installation and testing and access to data and documentation related to existing Army public safety communications systems.

13. Quality Assurance Surveillance Plan (QASP)

The Government will develop and maintain a QASP to evaluate the Contractor’s performance in meeting the requirements of this PWS. The QASP will outline the methods and metrics the

Government will use to monitor, assess, and document performance, including inspection, sampling, reporting reviews, and customer feedback. The QASP is a Government-managed document and may be updated at any time to ensure effective oversight; however, changes to the

QASP do not alter the Contractor’s responsibilities under the contract.

14. Organizational Conflicts of Interest

The Contractor performing work under this contract may receive, have access to, proprietary or source selection information (e.g., cost or pricing information, budget information or analyses, specifications or work statements, etc.) which may create a current or subsequent Organizational

Conflict of Interests (OCI) as defined in FAR Subpart 9.5.

Controlled By: Product Director Base Emergency Communications System (PD BECS) CUI Category: PROCUREMENT AND ACQUISITION

Distribution/Dissemination Control: Acquisition Sensitive

The Contractor shall notify the Contracting Officer immediately whenever it becomes aware that such access or participation may result in any actual or potential OCI and shall promptly submit a plan to the Contracting Officer to avoid or mitigate any such OCI. The Contractor’s mitigation plan will be determined to be acceptable solely at the discretion of the Contracting Officer and in the event the Contracting Officer unilaterally determines that any such OCI cannot be satisfactorily avoided or mitigated, the Contracting Officer may affect other remedies as he or she deems necessary, including prohibiting the Contractor from participation in subsequent contracted requirements which may be affected by the OCI.

The Contractor agrees that if it gains access to proprietary data of other companies, it will protect such data, and it will not use such proprietary data in supplying systems or components in future competitive procurements (FAR 9.505-4). In addition, the Contractor agrees to protect the proprietary data and rights of other organizations disclosed to the Contractor during performance of this contract with the same caution that a reasonably prudent Contractor would use to safeguard highly valuable property. The Contractor also agrees that if it gains access to the proprietary information of other companies, it will enter into an agreement with the other companies to protect their information from unauthorized use or disclosure for as long as it remains proprietary and refrain from using the information for any purpose other than that for which it was furnished.

The Contractor agrees that it will not distribute reports, data, or information of any nature arising from its performance under this contract, except as provided by this contract or as may be directed by the Contracting Officer.

15. Accounting and Appropriation Data

The contractor shall submit a proper invoice in accordance with FAR clause 52.232-25 Prompt

Payment and DFARS clause 252.232-7003 Electronic Submission of Payment Requests and

Receiving Reports. The contractor’s invoice shall be submitted monthly not later than five (5) calendar days after the month in which services are performed. The contractor may invoice only for the direct productive labor hours and services performed in direct support of this requirement.

The Government payment office will not make disbursement to the Contractor without evidence of receipt and acceptance, or certification of the items invoiced from the COR.

Contractor’s failure to comply with the instructions above will render the invoice as improper, and resubmission of the invoice will be required to obtain invoice payment.

16. Post Award Administration

16.1 Contract Administration Data

Notwithstanding the Contractor's responsibility for total management during the performance of this contract, the administration of the contract requires maximum coordination between the

Government and the contractor.

Controlled By: Product Director Base Emergency Communications System (PD BECS) CUI Category: PROCUREMENT AND ACQUISITION

Distribution/Dissemination Control: Acquisition Sensitive

16.2 Contract Management

The Contractor shall attend any post award conference convened by the contracting activity or contract administration office in accordance with Federal Acquisition Regulation. The contracting officer, or the Contracting Officers Representative (COR), may meet periodically with the Contractor to review the Contractor's performance.

16.3 Subcontract Management

The contractor shall be responsible for any subcontract management necessary to integrate work performed on this requirement and shall be responsible and accountable for subcontractor performance on this requirement. The prime contractor will manage work distribution to ensure there are no OCI considerations.

17. Contract Administration

The Contractor shall designate a Contract Manager for communication with the government. The government will designate a COR to oversee contract performance.

Controlled By: Product Director Base Emergency Communications System (PD BECS) CUI Category: PROCUREMENT AND ACQUISITION

Distribution/Dissemination Control: Acquisition Sensitive

APPENDIX A

Labor Category Descriptions and Required Qualifications

Note: The minimum education and experience requirements identified in this appendix establish the baseline qualifications for each labor category. Offerors may propose personnel possessing qualifications that exceed these minimum requirements. Equivalent combinations of education, professional certifications, and directly relevant experience may be considered when they demonstrate the knowledge, skills, and abilities necessary to successfully perform the duties of the labor category, subject to Government approval.

A.1 ENGINEERING PROGRAM MANAGER (Key Personnel)

Position Description: The Engineering Program Manager shall provide overall technical leadership, program management, systems engineering oversight, and strategic planning support for the Product Director Base Emergency Communications System. The individual shall serve as the Contractor's primary technical interface with the Government and oversee execution of all engineering, cybersecurity, and modernization activities performed under this contract.

Minimum Education

Bachelor’s Degree in Engineering, Computer Science, Information Systems, or a related technical discipline.

Minimum Experience

Fifteen (15) years of progressively responsible experience supporting complex Department of

Defense engineering or acquisition programs.

Required Qualifications

• Project Management Professional (PMP)

• Defense Acquisition Workforce Improvement Act (DAWIA)/Back-to-Basics Acquisition

Certification

• Information Technology Infrastructure Library (ITIL)

• Systems Engineering experience

Security Clearance

SECRET: Active or ability to obtain

Controlled By: Product Director Base Emergency Communications System (PD BECS) CUI Category: PROCUREMENT AND ACQUISITION

Distribution/Dissemination Control: Acquisition Sensitive

A.2 CYBERSECURITY SPECIALIST

Position Description

The Cybersecurity Specialist shall provide cybersecurity engineering and Risk Management

Framework (RMF) support for the Army's Public Safety Communications ecosystem. The individual shall support cybersecurity planning, security control implementation, vulnerability assessment analysis, Plans of Action and Milestones, Authorization to Operate activities, and compliance with applicable Department of War and Army cybersecurity policies throughout the system lifecycle.

Minimum Education

Bachelor's Degree in Cybersecurity, Information Technology, Computer Science, Information

Systems, Engineering, or a related technical discipline.

Minimum Experience

Eight (8) years of progressively responsible experience supporting cybersecurity, RMF implementation, information assurance, or enterprise information technology systems within the

Department of Defense or other Federal agencies.

Required Qualifications

• Security+

• Certified Information Systems Security Professional (CISSP)

• Certified Authorization Professional (CAP)

• Certified Ethical Hacker (CEH)

• Risk Management Framework (RMF)/ Enterprise Mission Assurance Support Service

(eMASS) tool experience

• DoD 8140 compliance

Security Clearance

SECRET: Active or ability to obtain

SA.3 NEXT GENERATION 9-1-1 (NG-911) PSAP ENGINEER - PRINCIPAL (Key

Personnel)

Position Description

The NG-911 PSAP Engineer - Principal shall serve as the Government's senior technical advisor for Public Safety Answering Point modernization activities. The individual shall provide engineering expertise supporting Computer Aided Dispatch, Call Handling Equipment, Next

Generation 9-1-1, interoperability, system integration, testing, implementation planning, and modernization activities supporting Army emergency communications capabilities.

Minimum Education

Controlled By: Product Director Base Emergency Communications System (PD BECS) CUI Category: PROCUREMENT AND ACQUISITION

Distribution/Dissemination Control: Acquisition Sensitive

Bachelor’s Degree in Engineering, Computer Science, Telecommunications, Information

Systems, or a related technical discipline.

Minimum Experience

Twelve (12) years of experience supporting emergency communications systems, NG-911 technologies, public safety communications, systems engineering, or enterprise telecommunications.

Required Qualifications

• National Emergency Number Association (NENA) certifications

• Association of Public-Safety Communications (APCO) certifications

• CAD implementation experience

• NG-911 implementation experience

• Systems…