NCTAMS LANT AOR_Commercial Telephone Contract_PWS.pdf

PERFORMANCE WORK STATEMENT (PWS)

NCTAMS LANT

REQUEST FOR INFORMATION

COMMERCIAL TELEPHONE (DIAL TONE) CONTRACT

1.0 INTRODUCTION: This Performance Work Statement supports a Request for Information (RFI) to determine commercial interest in the development of a comprehensive commercial telephone contract in the Naval Computer and Telecommunications Area Master Station Atlantic (NCTAMS LANT) Area of

Operations (AOR). Below are the contract service locations;

Naval Air Station (NAS) Key West, Florida, (FL).

Naval Station (NAVSTA) Great Lakes, Illinois, (IL).

NAVSTA Norfolk, Virginia (VA).

Joint Expeditionary Base (JEB) Little Creek, Virginia, (VA).

Naval Support Activity (NSA) Mechanicsburg, Pennsylvania (PA).

NSA Philadelphia, Pennsylvania (PA).

Philadelphia Naval Yard Annex (PNYA) Pennsylvania, (PA).

2.0 BACKGROUND: NCTAMS LANT provides critical base level communications to base users and supported commands and is integral to the mission for all users onboard NAS Key West, NAVSTA Great

Lakes, NAVSTA Norfolk, JEB Little Creek, NSA Mechanicsburg, NSA Philadelphia, and PNYA

Philadelphia by providing critical commercial telephone services to all users and supported commands.

Those commands have many critical National Defense missions to support operational and readiness requirements for Department of War (DoW), Department of Homeland Security (DHS), National Guard units, federal agencies and allied forces. NCTAMS LANT currently provides commercial telephone service to these locations via Time Division Multiplexing (TDM) Central Exchange (CENTREX) business lines.

3.0 SCOPE OF WORK:

3.1 NCTAMS LANT is seeking a comprehensive contract for the replacement of existing TDM commercial telephony services encompassing the installations and long-term support for approximately 20,560 endpoints, at the following locations.

3.1.1 NAS Key West - 1,900 endpoints to include IP replacement for one (1) T-1 circuit and three (3) Primary

Rate Interface (PRI) circuits with Session Initiation Protocol (SIP) capabilities.

3.1.2 NAVSTA Great Lakes - 2300 endpoints

3.1.3 NAVSTA Norfolk – 10,560 endpoints

3.1.4 JEB Little Creek – 4,100 endpoints

3.1.5 NSA Mechanicsburg - 425 endpoints

3.1.6 NSA Philadelphia - 350 endpoints

3.1.7 PNYA - 925 endpoints

4.0 System Compatibility and Compliance Requirements

The vendor’s solution must be fully compatible and interoperable with the current Information Systems Platform

(ISP) infrastructure and end-user instruments at each location. The solution will operate on an independent vendor owned/maintained distribution network and is not expected to interface directly with existing legacy or conventional voice sub-systems. However, it must support all functional and interoperability requirements necessary for reliable connectivity to end-user devices, ISP integration, and provide essential services such as Next Generation 911

(NG911), and crash nets, where applicable.

4.1 System Features: The system must support DoW-specific features including, but not limited to, Automatic Call

Distribution (ACD), Uniform Call Distribution (UCD), Call Trace, Pre-Set Conference, call forwarding and voice mail availability.

4.2 End-User Instruments and Equipment: The solution should support continued use of various existing endpoint types including digital and Internet Protocol (IP) phones, Video Teleconferencing (VTC) systems, Secure

Terminal Equipment (STE), Voice over Secure IP (VoSIP) devices, TSG-6 approved phones, voice mail systems, and other approved peripheral devices.

4.3 Auxiliary and Collaborative Voice Systems: The system should interoperate with all currently deployed voice auxiliary and collaborative systems, including but not limited to: Enhanced 911 (E-911), Primary Crash Net

(PCN), and Secondary Crash Net (SCN). Compliance with all emergency communication requirements is mandatory, including NG911 and 988 services.

4.4 NG911 Integration: The vendor shall interface with NG911 infrastructure to enable advanced emergency communications features including text-to-911, multimedia messaging, and real-time data sharing. The NG911 implementation shall integrate seamlessly with existing 911 and E911 services and support accurate station-level location identification and routing to the appropriate Public Safety Answering Point (PSAP), in accordance with Kari’s Law and the Ray Baum’s Act. Interoperability with all listed voice auxiliary systems is required, and the system must enable efficient and reliable multi-platform emergency communications.

4.5 The vendor shall be responsible for delivering reliable commercial telephone services with a minimum service availability of 99.9% per calendar month, excluding government-approved maintenance windows. The vendor shall maintain and operate their solution to ensure consistent voice service delivery to all government-designated endpoints.