What this opportunity is
The Department of Defense is seeking a contractor to provide comprehensive commercial telephone services, specifically Voice over Internet Protocol (VoIP) solutions, across seven sites in Virginia, supporting approximately 19,773 endpoints. This opportunity is open to all businesses as there is no set-aside, making it suitable for small and large contractors alike. Interested vendors should note that the solicitation is a Combined Synopsis/Solicitation, indicating that they will need to track the notice closely for proposal submission details rather than submitting a formal bid.
Analysis by Mindy, grounded in the SAM.gov notice.
Description
PERFORMANCE WORK STATEMENT (PWS)
NCTAMS LANT
COMMERCIAL TELEPHONE CONTRACT
1.0 INTRODUCTION: This Performance Work Statement requires the development and sustainment of a
comprehensive commercial telephone contract in the Naval Computer and Telecommunications Area Master Station
Atlantic (NCTAMS LANT) Area of Operations (AOR). The PWS defines the contractor efforts required to provide
commercially available integrated voice services via Central Office based, dial tone facilities to defense activities.
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 Naval Air Station (NAS) Key West, Naval Station
(NAVSTA) Great Lakes, NAVSTA Norfolk, Joint Expeditionary Base (JEB) Little Creek, Naval Support Activity
(NSA) Mechanicsburg, NSA Philadelphia, and Philadelphia Navy Yard (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.
3.0 SCOPE OF WORK: NCTAMS LANT requires a comprehensive contract for the complete replacement of existing
Time-Division Multiplexing (TDM) commercial telephony services. This effort shall include the installation and
long-term support for a new system supporting approximately 19,773 endpoints at the specified locations The core
requirement is for a Voice over Internet Protocol (VoIP) implementation.
3.0.1 FEDERAL RISK AND AUTHORIZATION MANAGEMENT PROGRAM (FEDRAMP) REQUIREMENTS: If
the proposal includes a Cloud based solution, the vendor must have at least a DoW Moderate Impact FedRAMP
Authorization To Operate (ATO) issued by the General Services Administration (GSA). Moderate Impact category
is based on the federal government mission and the Federal Information Processing Standard (FIPS) Publication
199. All work and requirements, such as the deliverables, stated in this PWS shall specially address how your firm
complies with DoW impact-level 2 (moderate) alongside the FedRAMP ATO/certification.
3.1.1 NAS Key West – 1,113 endpoints to include IP replacement for seven (7) T-1 circuit and five (5) ISDN circuits.
3.1.1.1 Features:
a. Local and Long-Distance Dialing
b. Voicemail
c. Caller ID
d. E9111
e. Call Waiting
f. Call Hold
g. Call Forwarding Busy Line
h. Call Forward Don’t Answer – All Calls
i. Call Forward Variable
j. Call Transfer
k. Three-Way Calling
l. Direct Inward Dialing
m. Direct Outward Dialing
3.1.1.2 Key West Specific Features
a. Airfield Crash Net Support: The proposed solution must support and seamlessly integrate with the existing
Primary and Secondary Crash Alarm Systems at NAS Key West. The system must provide instant, simultaneous,
non-blocking voice conferencing with priority override to all designated emergency response endpoints (e.g., ATC,
Fire/Rescue, Medical) without degradation of service.
3.1.2 NAVSTA Great Lakes – 2,300 endpoints
3.1.2.1 Features
a. Local and Long-Distance Dialing
b. Voicemail
c. Caller ID
d. E9111
e. Call Waiting
f. Call Hold
g. Call Forwarding Busy Line
-- 1 of 8 --
h. Call Forward Don’t Answer – All Calls
i. Call Forward Variable
j. Call Transfer
k. Three-Way Calling
l. Direct Inward Dialing
m. Direct Outward Dialing
3.1.3 NAVSTA Norfolk – 10,560 endpoints
3.1.3.1 Features
a. Local and Long-Distance Dialing
b. Voicemail
c. Caller ID
d. E9111
e. Call Waiting
f. Call Hold
g. Call Forwarding Busy Line
h. Call Forward Don’t Answer – All Calls
i. Call Forward Variable
j. Call Transfer
k. Three-Way Calling
l. Direct Inward Dialing
m. Direct Outward Dialing
3.1.4 JEB Little Creek – 4,100 endpoints
3.1.4.1 Features
a. Local and Long-Distance Dialing
b. Voicemail
c. Caller ID
d. E9111
e. Call Waiting
f. Call Hold
g. Call Forwarding Busy Line
h. Call Forward Don’t Answer – All Calls
i. Call Forward Variable
j. Call Transfer
k. Three-Way Calling
l. Direct Inward Dialing
m. Direct Outward Dialing
3.1.5 NSA Mechanicsburg – 425 endpoints
3.1.5.1 Features
a. Local and Long-Distance Dialing
b. Voicemail
c. Caller ID
d. E9111
e. Call Waiting
f. Call Hold
g. Call Forwarding Busy Line
h. Call Forward Don’t Answer – All Calls
i. Call Forward Variable
j. Call Transfer
k. Three-Way Calling
l. Direct Inward Dialing
m. Direct Outward Dialing
3.1.6 NSA Philadelphia – 350 endpoints
3.1.6.1 Features
a. Local and Long-Distance Dialing
b. Voicemail
c. Caller ID
-- 2 of 8 --
d. E9111
e. Call Waiting
f. Call Hold
g. Call Forwarding Busy Line
h. Call Forward Don’t Answer – All Calls
i. Call Forward Variable
j. Call Transfer
k. Three-Way Calling
l. Direct Inward Dialing
m. Direct Outward Dialing
3.1.7 PNYA – 925 endpoints
3.1.7.1 Features
a. Local and Long-Distance Dialing
b. Voicemail
c. Caller ID
d. E9111
e. Call Waiting
f. Call Hold
g. Call Forwarding Busy Line
h. Call Forwarding Don’t Answer – All Calls
i. Call Forward Variable
j. Call Transfer
k. Three-Way Calling
l. Direct Inward Dialing
m. Direct Outward Dialing
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 Confe…
Source: SAM.gov, as posted. Verify the current solicitation before responding.