PWS_REV4.pdf

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 an Internet Protocol (IP) based solution, with Voice over IP (VoIP) being the preferred implementation.

3.0.1 ALTERNATIVE AND HYBRID SOLUTIONS: While VoIP is the preferred solution, NCTAMS LANT will consider alternative or hybrid technological solutions if specific site conditions or mission requirements warrant them. Technologies such as Radio Frequency (RF), cellular, satellite, or other secure wireless communications may be deemed acceptable. Any proposed alternative must be fully justified by the offeror, detailing how it meets the requirement for seamless and reliable communication while integrating with the overall IP-based infrastructure.

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

If the proposal includes a Cloud Service Offering (CSO), it must comply with the current FedRAMP 20x framework and the DoD Cloud Computing Security Requirements Guide (CC SRG). At a minimum, the proposed CSO must possess the unified "FedRAMP Authorized" designation at the Moderate baseline, which is based on the NIST SP

800-53 (Revision 5) control set. The vendor must provide evidence of this authorization as part of their proposal. All work and requirements stated in this PWS must comply with the security controls required for this authorization level.

3.1.1 NAS Key West - 1113 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

h. Call Forward Don’t Answer – All Calls

i. Call Forward Variable

j. Call Transfer

k. Three-Way Calling

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

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

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

3.1.6 NSA Philadelphia – 350 endpoints

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

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

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.

5.0 Billing/Invoicing Reports: In addition to the submission requirements below, the contractor shall ensure the documents/reports are made available through a contractor portal for the Government to access on an as needed basis.

5.1 Monthly Invoices. The contractor shall bill in arrears on a monthly basis in accordance ith this PWS and the terms and conditions contained within the contract. The contractor shall utilize Wide Area Workflow (WAWF) to submit invoices and receiving reports electronically. Monthly invoices shall be submitted through WAWF at the task order level. Upon receipt of a task order the contractor shall establish an account number specific to that task order. Additional requirements are as follows:

5.1.1 Monthly invoices shall reflect all charges from the first day of the month to the last day of the month. The contractor shall charge for all services, features and equipment within one billing cycle after the services are rendered.

5.1.2 The contractor shall provide a monthly detailed invoice report for each account/task order. The contractor shall ensure that each detailed invoice contains all pricing components in sufficient detail to reconcile the charges with completed orders or actual usage. The contractor shall ensure that all charges, credits and debits are shown on the invoice. The detailed invoice report shall be provided electronically in both PDF and excel format and may be required to be attached to each WAWF invoice as substantiating documentation.

5.1.3 Monthly invoices shall reflect only charges for the current month of service. Any unpaid balances from prior periods shall not carryover to future invoices. Any unpaid balances shall be reconciled on a month to month basis. The Government shall not be double billed for the same services.

5.1.4 For other reimbursable charges, the contractor shall ensure that the invoices reflect the contractor’s actual charge for a specific service order. The Government will not pay any charges that are not agreed upon between the contractor and the Government point-of-contact, and that are not specifically stated in the service order. Examples of other reimbursable charge include but are not limited to the following: line connection, installation service charge and “add” service.

5.1.5 The Government reserves the right to withhold a partial or entire payment of an invoice in dispute as detailed in FAR 52.232-1 (Payments).

5.1.6 The Federal, State and Local Government Taxes, Fees, Surcharges, and Tariffs Not to Exceed Line Item established in the Pricing Spreadsheet shall account for any and all applicable taxes, fees and surcharges at the current prevailing rates in accordance with applicable law. To ensure these rates remain accurate during the term of the contract, the contractor shall provide substantiating documentation detailing the prevailing rates with each invoice. Each invoice shall contain the total amount and a breakdown of each service charge so that the Government may distinguish the taxes, fees and surcharges and verify that they are being billed in accordance with the prevailing rates.

5.1.7 The contractor shall prepare and deliver a Monthly Statement Report. The report is to be cumulative over the life of the Delivery Order and shall show changes during the current reporting period with respect to the previous reporting period.

6.0 PERIOD OF PERFORMANCE: The period of performance for this requirement is:

Ordering Period 1 is 01 February 2027 through 31 January 2028

Ordering Period 2 is 01 February 2028 through 31 January 2029

Ordering Period 3 is 01 February 2029 through 31 January 2030

Ordering Period 4 is 01 February 2030 through 31 January 2031

Ordering Period 5 is 01 February 2031 through 31 January 2032

FAR clause 52.217-8 Ordering Period is 01 February 2032 through 31 July 2032

6.1 For this Performance Work Statement, “business days” shall be construed to mean all weekdays excluding the eleven

Government holidays to include New Years’ Day, Dr. Martin Luther King, Jr. Day, President’s Day, Memorial Day, Juneteenth, July 4th, Labor Day, Columbus Day, Veteran’s Day, Thanksgiving Day, and Christmas Day.

7.0 LOCATION OF SERVICES: 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).Technical Points of Contact

7.1 Technical Points of Contract (TPOC): Below are NCTAMSLANT BCO (TPOC)

Naval Air Station (NAS) Key West, Florida, (FL)- Shannon Cox - shannon.c.cox.civ@us.navy.mil

Naval Station (NAVSTA) Great Lakes, Illinois, (IL)- Greg Powroznik - greg.m.powroznik.civ@us.navy.mil

NAVSTA Norfolk, Virginia (VA)- Lachana Hill - lachana.j.hill.civ@us.navy.mil

Joint Expeditionary Base (JEB) Little Creek, Virginia, (VA)- Lachana Hill - lachana.j.hill.civ@us.navy.mil

Naval Support Activity (NSA) Mechanicsburg, Pennsylvania (PA)- Jewanna Owens - jewanna.f.owens.civ@us.navy.mil

NSA Philadelphia, Pennsylvania (PA)- Jewanna Owens - jewanna.f.owens.civ@us.navy.mil

Philadelphia Naval Yard Annex (PNYA) Pennsylvania, (PA)- Jewanna Owens - jewanna.f.owens.civ@us.navy.mil

8.0 Service-Contractor Reporting

9.0 Contractor Unclassified Access to Federally Controlled Facilities, Sensitive Information, Information

10.0 Technology (IT) Systems or Protected Health Information

Homeland Security Presidential Directive (HSPD)-12, requires government agencies to develop and implement

Federal security standards for Federal employees and contractors. The Deputy Secretary of Defense Directive-Type

Memorandum (DTM) 08-006 – “DOD Implementation of Homeland Security Presidential Directive – 12 (HSPD12)” dated November 26, 2008 (or its subsequent DOD instruction) directs implementation of HSPD-12. This clause is in accordance with HSPD-12 and its implementing directives.

APPLICABILITY

This clause applies to contractor employees requiring physical access to any area of a federally controlled base, facility or activity and/or requiring access to a DON or DOD computer/network/system to perform certain unclassified sensitive duties. This clause also applies to contractor employees who access Privacy Act and Protected

Health Information, provide support associated with fiduciary duties, or perform duties that have been identified by

DON as National Security Position, as advised by the command security manager. It is the responsibility of the responsible security officer of the command/facility where the work is performed to ensure compliance.

Each contractor employee providing services at a Navy Command under this contract is required to obtain a 5512

Defense Biometric Identification System (DBIDs). Additionally, depending on the level of computer/network access, the contract employee will require a successful investigation as detailed below.

ACCESS TO FEDERAL FACILITIES

Per HSPD-12 and implementing guidance, all contractor employees working at a federally controlled base, facility or activity under this clause will require a 5512 DBIDs. When access to a base, facility or activity is required, contractor employees shall in-process with the Navy Command’s Security Manager upon arrival to the Navy

Command and shall out-process prior to their departure at the completion of the individual’s performance under the contract.

ACCESS TO DOD IT SYSTEMS

In accordance with SECNAV M-5510.30, contractor employees who require access to DON or DOD networks are categorized as IT-I, IT-II, or IT-III. The IT-II level, defined in detail in SECNAV M-5510.30, includes positions, which require access to information protected under the Privacy Act, to include Protected Health Information (PHI).

All contractor employees under this contract who require access to Privacy Act protected information are therefore categorized no lower than IT-II. IT Levels are determined by the requiring activity’s Command Information

Assurance Manager. Contractor employees requiring privileged or IT-I level access, (when specified by the terms of the contract) require a Single Scope Background Investigation (SSBI) which is a higher level investigation than the

National Agency Check with Law and Credit (NACLC) described below. Due to the privileged system access, a

SSBI suitable for High Risk public trusts positions is required. Individuals who have access to system control, monitoring, or administration functions (e.g. system administrator, database administrator) require training and certification to Information Assurance Technical Level 1, and must be trained and certified on the Operating System or Computing Environment they are required to maintain.

Access to sensitive IT systems is contingent upon a favorably adjudicated background investigation. When access to

IT systems is required for performance of the contractor employee’s duties, such employees shall in-process with the Navy Command’s Security Manager and Information Assurance Manager upon arrival to the Navy command and shall out-process prior to their departure at the completion of the individual’s performance under the contract.

Completion and approval of a System Authorization Access Request Navy (SAAR-N) form is required for all individuals accessing Navy Information Technology resources. The decision to authorize access to a government IT system/network is inherently governmental. The contractor supervisor is not authorized to sign the SAAR-N;

therefore, the government employee with knowledge of the system/network access required or the COR shall sign the SAAR-N as the “supervisor”.

The SAAR-N shall be forwarded to the Navy Command’s Security Manager at least 30 days prior to the individual’s start date. Failure to provide the required documentation at least 30 days prior to the individual’s start date may result in delaying the individual’s start date.

When required to maintain access to required IT systems or networks, the contractor shall ensure that all employees requiring access complete annual Information Assurance (IA) training, and maintain a current requisite background investigation. The Contractor’s Security Representative shall contact the Command Security Manager for guidance when reinvestigations are required.

INTERIM ACCESS

The Navy Command's Security Manager may authorize issuance of a 5512 DBIDs and interim access to a DON facilities upon a favorable review of the investigative questionnaire and advance favorable fingerprint results. When the results of the investigation are received and a favorable determination is not made, the contractor employee working on the contract under interim access will be denied access to the computer network and this denial will not relieve the contractor of his/her responsibility to perform.

DENIAL OR TERMINATION OF ACCESS

The potential consequences of any requirement under this clause including denial or termination of physical or system access in no way relieves the contractor from the requirement to execute performance under the contract within the timeframes specified in the contract. Contractors shall plan ahead in processing their employees and subcontractor employees. The contractor shall insert this clause in all subcontracts when the subcontractor is permitted to have unclassified access to a federally controlled facility, federally-controlled information system/network and/or to government information, meaning information not authorized for public release.

CONTRACTOR’S SECURITY REPRESENTATIVE

The contractor shall designate an employee to serve as the Contractor’s Security Representative. Within three workdays after contract award, the contractor shall provide to the requiring activity’s Security Manager and the

Contracting Officer, in writing, the name, title, address and phone number for the Contractor’s Security

Representative. The Contractor’s Security Representative shall be the primary point of contact on any security matter. The Contractor’s Security Representative shall not be replaced or removed without prior notice to the

Contracting Officer and Command Security Manager.

BACKGROUND INVESTIGATION REQUIREMENTS AND SECURITY APPROVAL PROCESS FOR

CONTRACTORS ASSIGNED TO NATIONAL SECURITY POSITIONS OR PERFORMING SENSITIVE

DUTIES

Navy security policy requires that all positions be given a sensitivity value based on level of risk factors to ensure appropriate protective measures are applied. Navy recognizes contractor employees under this contract as NonCritical

Sensitive [ADP/IT-II] when the contract scope of work require physical access to a federally controlled base, facility or activity and to perform unclassified sensitive duties. This designation is also applied to contractor employees who access Privacy Act and Protected Health Information (PHI), provide support associated with fiduciary duties, or perform duties that have been identified by DON as National Security Positions. At a minimum, each contractor employee must be a US citizen and have a favorably completed NACLC to obtain a favorable determination for assignment to a non-critical sensitive or IT-II position. The NACLC consists of a standard NAC and a FBI fingerprint check plus law enforcement checks and credit check. Each contractor employee filling a noncritical sensitive or IT-II position is required to complete:

• SF-86 Questionnaire for National Security Positions (or equivalent OPM investigative product)

• Two FD-258 Applicant Fingerprint Cards (or an electronic fingerprint submission)

• Original Signed Release Statements

Failure to provide the required documentation at least 30 days prior to the individual’s start date shall result in delaying the individual’s start date. Background investigations shall be reinitiated as required to ensure investigations remain current (not older than 10 years) throughout the contract performance period. The Contractor’s

Security Representative shall contact the Command Security Manager for guidance when reinvestigations are required.

The Contractor employees shall accurately complete the required investigative forms prior to submission to the

Navy Command Security Manager. The Navy Command’s Security Manager will review the submitted documentation for completeness prior to submitting it to the Office of Personnel Management (OPM).

Suitability/security issues identified by the Navy may render the contractor employee ineligible for the assignment.

An unfavorable determination made by the Navy is final (subject to SF-86 appeal procedures) and such a determination does not relieve the contractor from meeting any contractual obligation under the contract. The Navy

Command’s Security Manager will forward the required forms to OPM for processing. Once the investigation is complete, the results will be forwarded by OPM to the DON Central Adjudication Facility (CAF) for a determination.

If the contractor employee already possesses a current favorably adjudicated investigation, the contractor shall submit a Visit Authorization Request (VAR) via the National Background Investigation System (NBIS) or a hard copy VAR directly from the contractor’s Security Representative. Although the contractor will take NBIS

“Owning” role over the contractor employee, the Navy Command will take NBIS "Servicing" role over the contractor employee during the hiring process and for the duration of assignment under that contract. The contractor shall include the IT Position Category per SECNAV M-5510.30 for each employee designated on a VAR. The VAR requires annual renewal for the duration of the employee’s performance under the contract.

BACKGROUND INVESTIGATION REQUIREMENTS AND SECURITY APPROVAL PROCESS FOR

CONTRACTORS ASSIGNED TO OR PERFORMING NON-SENSITIVE DUTIES

Contractor employee whose work is unclassified and non-sensitive (e.g., performing certain duties such as lawn maintenance, vendor services, etc.) and who require physical access to publicly accessible areas to perform those duties shall meet the following minimum requirements:

• Must be either a US citizen or a US permanent resident with a minimum of 3 years legal residency in the

United States (as required by The Deputy Secretary of Defense DTM 08-006 or its subsequent DOD instruction) and

• Must have a favorably completed National Agency Check with Written Inquiries (NACI) including a FBI fingerprint check prior to installation access.

To be considered for a favorable trustworthiness determination, the Contractor’s Security Representative must submit for all employees each of the following:

• SF-85 Questionnaire for Non-Sensitive Positions

• Two FD-258 Applicant Fingerprint Cards (or an electronic fingerprint submission)

• Original Signed Release Statements

The contractor shall ensure each individual employee has a current favorably completed National Agency Check with Written Inquiries (NACI) or ensure successful FBI fingerprint results have been gained and investigation has been processed with OPM.

Failure to provide the required documentation at least 30 days prior to the individual’s start date may result in delaying the individual’s start date.

* Consult with your Command Security Manager and Information Systems Security Manager for local policy when

IT-III (non-sensitive) access is required for non-US citizens outside the United States