24Q0020 ANNEX A.docx

Naval Air Station Key West, Florida, Voice Over Internet Protocol Solution

ANNEX A

PERFORMANCE WORK STATEMENT (PWS)

1. Government Representative

1.1. Primary

Department of Defense Activity Address Code (DODAAC):

N70272

NCTAMS LANT – 1518 Piersey Ave, Norfolk, VA, 23511

Fax Number:

1.2. Alternate

Department of Defense Activity Address Code (DODAAC):

N70272

Fax Number:

2. TASK

NCTAMS LANT Base Communications Office (BCO) Key West Voice over Internet Protocol (VoIP) Solution/Plan

3. Background NCTAMS LANT BCO Key West, Florida (FL) provides critical base level communications and is integral to NAS Key West, which has a mission to support operational and readiness requirements for Department of Defense (DoD), Department of Homeland Security (DHS), National Guard units, federal agencies and allied forces. BCO Key West provides real time communications operations and support to their supported commands. NCTAMS LANT BCO Key West currently assigns and controls users’ voice features through the AT&T web portal.

AT&T is the local exchange carrier (LEC) for Key West and surrounding area. AT&T owns and operates the outside plant infrastructure and Switching Systems that support BCO Key West. NCTAMS LANT is seeking telecommunication vendors to conduct a site survey and develop a solution, which includes one-time/recurring costs (to include invoicing call details/format) and notional timeline to implement and transition from the current Time Division Multiplexing (TDM) telephony services (via a mixture of CENTREX, Integrated Services Digital Network [ISDN], and T-1 connections) to a Voice over Internet Protocol (VoIP) delivery system at NAS Key West. It is highly recommended that the vendor(s) develop the solution using the existing Inside Plant (ISP) infrastructure, and if possible the Outside Plant (OSP) infrastructure, to provide VoIP commercial telephony to support immediate deployment and transition.

4. Scope

4.1. NCTAMS LANT is seeking eligible telecommunication vendors to provide a speedy solution to transition thecurrent TDM telephony service to a VoIP delivery system at NAS Key West. Expectation is that the vendor(s) develop a plan with the high recommendation of utilizing the existing OSP/ISP infrastructure to provide VoIP commercial telephony service to approximately 2,200 current users (mixture of CENTREX, ISDN, and T-1 services) located in approximately 149 separate buildings on the base. The OSP infrastructure is owned/maintained by AT&T, consequently there is no Government Furnished Equipment/Infrastructure (GFE/I) OSP available. The Navy relies on this infrastructure and switching equipment to provide telephony service to all supported commands. Vendor(s) responding to this solicitation shall be prepared to provide the government an immediate solution(s) to transition current TDM Central Office services to their vendor VoIP/IP Central Office services; the only GFE/I available is the Category (CAT) 3 cabling inside the 149 buildings on NAS Key West.

4.2. Deliverables shall include description of the solution(s) along with estimated one-time and recurring costs (to include invoicing call details/format) for the service from a VoIP Central Office as well as a notional timeline to complete based on the government’s intention to proceed with solicitation and contract award on or about the 2nd or 3rd quarter of FY25. The resulting contract would be for a 5 year ordering period. The solicitation and resultant contract would also contain FAR 52.217-8, Option to Extend Services, thereby allowing a six (6) month extension if circumstances necessitate this option.

5. Objectives

5.1. The objective of this PWS is to define the requirements for the vendor to develop a plan for a fast turn-key VoIP telephone solution at NAS Key West, with approximately 2,200 current users located in approximately 149 separate buildings; recommend utilizing existing cable infrastructure. The Navy currently relies on AT&T infrastructure and TDM switching equipment to provide telephony service to all supported commands.

5.2. The vendor proposed solution(s) shall identify all necessary equipment installed in government spaces and must be in compliance with the latest version of the Department of Defense (DoD) Unified Communications Requirements (UCR) and shall conform to applicable requirements (dialing plan, voice mail, security, etc).

5.3. The government provides recommendation of cloud based solution(s) as result of limited available government space; however, the government would consider an on-premise solution if the solution identifies NAS Key West locations having adequate equipment installation space, power, and environmental support (i.e. HVAC).

5.4. The government recommends due to complexity considerations of collaborations with alternate sources to promote best outcome and is not opposed to subcontractor options to team up with to provide an alternate proposed solution with separate/second set of deliverables.

5.5. All “right to use” software licensing (if applicable) and the existing feature sets that may now not require right to use licensing, will be grandfathered and fully functional, as required per Government Representative, after the transition at no additional cost to the government.

6. Applicable Standards

6.1. The solution’s network equipment, equipment racks/cabinets, cables (communications, power, grounding, etc.), pathways, wire management, patch panels, etc. shall be IAW the most current versions of the standards referenced, and in secure areas, if applicable, comply with NSTISSAM Tempest/2-95 “National Security Telecommunications and Information Systems Security Advisory Memorandum (NSTISSAM) Red/Black Installation Guidelines”.

6.2. Joint Interoperability Test Center Approved Product List (JITC APL)

6.3. Vendor Manufacturer Systems Best Practices, Product List and Technical Specifications

6.4. National Electrical Code© NFPA 2018

6.5. BICSI Telecommunications Distribution Methods Manual (TDMM) ©, Latest Edition

6.6. International Standards Organization (ISO) Document: 33.040.35: Telephone networks

6.7. Defense Information Systems Agency (DISA) Defense Switched Network (DSN) Operational Procedures and Standards

6.8. Federal Communications Commission (FCC) Operational Procedures and Standards

6.9. Applicable Navy Technical Orders including installation grounding, and Electrostatic Discharge (ESD)

7. General Requirement

7.1. This is a proposed solution wherein the vendor shall develop a timely and quick turn-key installation design to include all labor, equipment, installation services, and programming/configuration required for successful installation. The vendor plan shall include provisioning of a completely functional solution utilizing the existing GFE/I ISP, and if possible the existing OSP infrastructure with required programming/configuration, hardware, software, Right-to-Use (RTU) licenses, ancillary equipment, cabling, parts as well as all material for identified requirements listed under paragraph 7.

7.1.1. Equipment identified in the solution(s) shall be on the JITC certified approved product list at time of proposal submission. All equipment or system installations shall be at the latest JITC certified software version, as applicable. See paragraph 9.4.2 for certification requirements.

7.1.2. All work shall be accomplished in reference to this PWS within the timeframes outlined in the award documents. Any request or justification for change shall be made to the Contracting Officer in writing and must be approved by the government.

7.1.3. The vendor solution shall include government furnished infrastructure, hardware, and software to the fullest extent possible, e.g., ISP, telephone devices if possible.

7.1.4. Resolution to any contradictions within the proposal shall be to the benefit of the government.

7.1.5. Pre-Proposal Conference: On-site pre-proposal conference meeting is strongly recommended. The vendor is fully responsible to capture the accurate configuration of the existing system for their proposal. The Government provided information is for reference only and shall not be accountable for the accuracy of the vendor’s final proposal.

7.2. Vendor shall provide a preliminary schedule within 14 days after award with a final schedule 30 calendar days prior to any on-site work.

7.3. Project Execution

7.3.1. Upon contract award, the vendor shall provide the Government Representative a project coordination call to review all planned vendor efforts in support of this effort.

7.4. Execution Management

7.4.1. Kick-Off Meeting: A Site Kick-Off shall be provided by the vendor no later than 14 days prior to the start of installation to review the overall project, goals, timelines, base support and any other pertinent information related to solution development.

7.4.2. Weekly Meeting. The vendor shall chair a weekly meeting that includes Technical Government Representative, the Government Contracting Officer (CO), and all required project personnel. The vendor shall provide a “Meet Me” Telecon capability for the duration of the project. The purpose of this meeting is to discuss project progress, problems being encountered, and other discussions necessary/beneficial to ensure success and timely completion of this order. The vendor shall be responsible for the meeting minutes. A copy of the minutes shall be provided to each attendee via e-mail.

7.4.3. The vendor shall identify by name a Provisioning Project Owner (PPO) responsible as the single point of contact for duration of the contract action.

7.4.4. The PPO shall direct the project implementation to ensure the solution plan is developed within prescribed timelines.

7.4.5. The PPO shall ensure the solution development is completed in a professional manner.

7.4.6. The PPO shall ensure that any damage that occurs incidental to the solution development shall be repaired, replaced, repainted and restored to the original pre-installation condition at the expense of the vendor.

7.4.7. The PPO shall upon request of the Government Representative or Contacting Officer, return to the site if it is determined through negative Quality Performance Assessments or project performance reports that a site visit is necessary.

7.5. Delays associated with working on an active military installation, to include base entry access vetting requirements, are at the vendor’s risk and must be included in the Vendor’s Firm Fixed Price proposal.

7.6. Remote access, if required, must be coordinated with the Government Representative and comply with all applicable security guidelines and regulations.

7.7. Routine on-site work efforts shall be performed during normal installation operating hours, identified in paragraph 9, unless otherwise agreed to by the Government Representative.

7.8. The vendor shall be responsible for supervision of all contract personnel and performance of all vendor related functions.

7.9. All network topologies in the government/Department of Defense are considered both sensitive and proprietary.

7.10. Security Clearance. Contractor functions involve delivery of service to support the Department of the Navy mission and shall be accomplished by U.S. Citizens who have, at the minimum, a Fitness Trust Determination based on a final favorable Tier 1 background investigation adjudicated by the government in accordance with EO 13764. Contractors shall also be required to participate in the access control program Defense Biometric Identification System (DBIDS), sponsored by Commander, Navy Installations Command (CNIC). All participants in the DBIDS Program are also subject to comprehensive background screenings with ongoing additional screenings throughout the year. Further information regarding DBIDS can be found at https://www.cnic.navy.mil/om/dbids.html. All contracted personnel shall in-process with the NCTAMS LANT Security Manager prior to start of contract, to complete the required security documentation to obtain necessary badges required for entry to base installations and restricted or controlled areas, as applicable, to meet the requirements of this PWS. Interim access is authorized based on favorable security pre-screening while undergoing the Fitness background investigation. All contracted personnel shall comply with established security procedures for entering an installation and its facilities, including special security procedures for entry to restricted or controlled areas. The vendor shall coordinate with the site POC to obtain and return temporary badges and vehicle registrations upon favorable completion of the security vetting process. In the event of a final unfavorable security determination, the contract vendor will be advised immediately that the individual’s access to government information and/or facilities has been denied and performance on the contract is no longer authorized. The contract vendor must immediately remove the contractor employee from the NCTAMSLANT contract and may need to identify another candidate for the position.

7.11. Installation Plan. The vendor’s proposed solution shall include a system installation plan (SIP), system test plan (STP), system cutover plan (SCP), and project support agreement (PSA).

7.12. The vendor shall be responsible for the storage, staging and deployment of any materials required to support on-site work required to develop the solution.

7.13. The solution development shall be performed with little or no disruption to existing services. If a service disruption is required, the PPO shall submit a service interruption request 5 days prior to the interruption of service to the Government Representative.

7.14. Any unplanned service interruption/outage caused by on-site solution development activity shall be resolved as soon as possible by the vendor with immediate notification to the Government Representative.

7.15. Configuration Management. Documentation shall be provided in MicroSoft WORD, EXCEL, and/or Adobe PDF formats as indicated on applicable DD Form 1423-1, Contract Data Requirements List (CDRL). All proposed solution documentation shall include, but is not limited to:

7.15.1. Layout drawings and diagrams of installs in government spaces shall identify the chassis/shelf/cabinet, equipment, software version, model numbers and manufacturer specifications.

7.15.2. For installs in government spaces, drawing documentation shall include cable and power drawings/specifications, floor plans, and engineering specifications generated in support of the installation of the system.

7.15.3. Documentation shall include drawings that depict the overall solution configuration and network topology.

7.15.4. Any unified communications (UC) deployment accomplished by the vendor shall be shown on logical network diagrams and shall show what facilities the UC is deployed to and the numbers of users.

8. Safety

8.1. The vendor shall comply with all Federal Occupational Safety and Health Administration (OSHA), State, local and base safety requirements whichever is the most stringent. The vendor shall also comply with all Federal, State, local and base regulations pertaining to the environment, including but not limited to, water, air, solid waste, and noise pollution.

8.2. Unsafe/Hazardous Safety Conditions

The vendor shall notify the Government Representative and BCO site POC (i.e. email, voice mail or facsimile), of any unsafe or hazardous safety conditions within 30 minutes of becoming aware of the condition and inform them in writing within one (1) workday. If the condition is within the scope of the contractor’s responsibility as set forth in this document the vendor shall correct the unsafe condition immediately and notify the Government Representative and BCO site POC.

8.3. Injuries

The vendor shall notify the Government Representative and the BCO site POC (i.e. email, voice mail, or facsimile) within two (2) hours of the occurrence of all types of injuries sustained by a contractor employee arising from the performance of this document. The contractor shall provide a detailed written report within 24 hours.

8.4. Safety Plan: The vendor shall adhere to the safety guidance/policies of NAS Key West. The vendor shall ensure that all safety programs and provisions comply with Federal laws, rules, and regulations. For any questions, the vendor shall contact the Government Representative identified in paragraph 15 below.

8.5. Protective Equipment Requirements: The vendor shall provide, train, and require its employees to utilize appropriate personal protective equipment, such as gloves, safety shoes, and safety glasses IAW applicable safety regulations.

8.6. Fire Preparedness and Fire Prevention: The vendor shall render assistance as outlined in applicable station Standard Operating Procedures (SOP) and instructions regarding fire safety and response to fire alarms. The Government will ensure that Contractor employees are familiar with the unique characteristics of the facility's fire alarm and extinguishing systems. All vendor employees shall observe all requirements and directives for the handling and storage of combustible waste and trash.

9. Technical Requirements

9.1. Upon contract award, the expectation is that the vendor shall develop an immediate solution with the recommendation of using the existing GFE/I ISP infrastructure, and existing OSP if possible, to provide VoIP commercial telephony and voicemail service to approximately 2,200 users located in approximately 149 separate buildings. The OSP infrastructure is owned/maintained by AT&T, consequently there is no GFE OSP available; AT&T demarks all copper at each building. Vendor(s) should provide the government a solution(s) to transition the current TDM Central Office services to their vendor VoIP/IP Central Office services using the GFE/I Category (CAT) 3 cabling inside the 149 buildings on NAS Key West; deliverables include description of the solution(s) along with estimated one-time and recurring costs (to include invoicing call details/format) for the service from their VoIP Central Office.

9.2. All information and records provide herein are for reference only. The vendor is responsible to confirm accuracy for all NAS Key West information.

9.2.1. The solution shall comply with UCR 2013 and all applicable commercial manuals.

9.2.2. The solution must be modular/scalable in nature, supporting an existing subscriber base of 2,200 numbers.

9.3. System features & station features

The new VoIP solution must be compatible and interoperable with all the existing conventional and UC IP voice sub-systems at the minimum but not limited to followings:

a. Connectivity/Interfaces: Local City, Long Distance, intra-base nodes (if applicable), and any other connection required for users to access VoIP services.

b. End user instruments/equipment features: caller ID, call forwarding, voice mail, conference calling, etc.

c. Voice auxiliary/collaborated service systems: Voice Protection System (VPS), ION Defender, E-911, Primary Crash Net (PCN), Secondary Crash Net (SCN), and others. The vendor shall fully comply with emergency service requirements, including 911 and E911 services Next Generation 911 (NG911), 988 services and identify the location of originating stations and route them to the appropriate Public Safety Answering Point (PSAP) in accordance with Kari’s Law and Ray Baum’s Act 911 direct dialing.

d. The vendor’s solution shall include NG911 systems to enhance emergency communication capabilities. This includes deploying NG911 infrastructure to support advanced features such as text-to-911, multimedia communication, and real-time data sharing. The system must ensure seamless interoperability with existing 911 and E911 services and integrate with voice auxiliary and collaborated service systems including Voice VPS, ION Defender, E-911, PCN, and SCN. The NG911 implementation must comply with all relevant regulations, including Kari’s Law and Ray Baum’s Act, ensuring accurate identification of the location of originating stations and routing to the appropriate PSAP. The system should support efficient emergency response and provide reliable communication channels across various platforms.

e. The vendor’s proposed solution shall provide comprehensive Managed Network Services (MNS) to ensure the effective design, implementation, management, and optimization of the Key West network infrastructure. The services must include 24/7 network monitoring and performance management to ensure high availability and reliability. The vendor is responsible for proactive incident management, including rapid response and resolution to minimize downtime. Network security measures must be enforced, including regular vulnerability assessments and threat mitigation. The vendor shall also manage configuration changes, conduct performance optimization, and support capacity planning to meet current and future needs, working in conjunction with local technicians to ensure seamless integration and effective execution of these tasks. Detailed reporting and documentation of network activities, incidents, and performance metrics are required to maintain transparency and support decision-making. The services must comply with industry standards and organizational policies to ensure a secure and efficient network environment.

f. All solution equipment, supplies, and materials provided shall be “new”. All new equipment must comply with Federal Information Processing Standard (FIPS) requirements and current United States State Department, DoD, and USN restrictions on the country of origin. No equipment, even if listed as new, shall have origin as an “open box”, “demo” device, or surplus stock from previous contracts. All equipment shall be delivered with factory seals intact.

9.4. Additional requirements:

9.4.1. Site Survey

It is understood that the vendor may need a site survey in order to develop the technical deliverables. Permission to perform a site survey must be granted by the Government Representative prior to the vendor completing a site survey.

9.4.2. FedRAMP

The vendor must have at least a DoD Moderate Impact Federal Risk and Authorization Management Program (FedRAMP) Authorization To Operate (ATO) issued by the General Services Administration (GSA). Moderate Impact category is based on the federal government mission and the FIPS Publication 199. All work and requirements, such as the deliverables, stated in this PWS shall specially address how your firm complies with DoD impact-level 2 (moderate) alongside the FedRAMP ATO/certification.

10. Deliverables

10.1. The vendor shall provide a comprehensive site survey report to the government, identified in Contract Data Requirements List (CDRL) A001, within 30 days of completion of the site survey.

10.2. The vendor shall deliver electronic copies of all documents, records, proposed drawings (CDRL A002, A003), financial and timeline reports (A004), and equipment to the Government Representative.

10.3. All proposed solution documentation shall include but is not limited to:

10.3.1. Layout drawings and diagrams of the base and annexes identifying demarks and potential equipment required for solution implementation to reach each current telephony user.

10.3.2. Documentation shall include ISP and OSP cabling and power drawings/specifications, floor plans, and engineering specifications generated in support of the installation of the system.

10.3.3. Documentation shall include drawings that depict the overall installed system configuration and network topology.

10.3.4. The vendor solution shall depict a logical network diagrams and shall show what facilities are required to ensure telephony service is delivered to each current user.

10.4. All deliverables shall be produced using software tools/versions identified in the CDRLs as specified or accepted by the Government Representative.

10.5. All documentation and records produced by the vendor under this PWS shall become the property of the U.S. Government, which shall have unlimited rights to all materials and determine the scope of publication and distribution.

10.6. The vendor shall deliver electronic copies as identified in the CDRLs, of all documents, records, and proposed drawings to the Government Representative upon completion of contract actions.

10.7. Deliverables must be transmitted with a cover letter on the prime vendor’s letterhead, describing the contents, within 30 days of completing the site survey. Additionally, an electronic copy of all deliverables shall be provided to the Government Representative identified in paragraph 15 below.

11. Service Delivery Summary:

Work is to be accomplished in accordance with the following Service Delivery Summary and the Performance Plan. Certification by the Government of satisfactory services provided is contingent upon the vendor performing in accordance with the terms and conditions of this document. The Government and the vendor’s representative(s) shall meet when deemed necessary at the contracting officer’s request. Meetings shall occur at the place determined by the contracting officer.

Table 1.1. Deliverable Summary

12. KEY DEFINITIONS

12.1. Shall

The word SHALL is used to express a provision that is binding.

13. Work Schedule

13.1. All work performed by the vendor will be performed during normal duty hours, Monday- Friday 0730-1630 local time. Work will not be performed on weekends or observed federal holidays unless mission or base operations dictate. Observed federal holidays are:

- New Year’s Day - 1 January

- Martin L. King Day - Third Monday in January

- Washington's Birthday - Third Monday in February

- Memorial Day - Last Monday in May

- Juneteenth - 19 June

- Independence Day - 4 July

- Labor Day - First Monday in September

- Columbus Day - Second Monday in October

- Veterans Day - 11 November

- Thanksgiving Day - Fourth Thursday in November

- Christmas Day - 25 December

14. DELIVERY ADDRESS

NAS Key West, Florida

15. POINTS OF CONTACT

15.1. Contracting Officer

Robert Joas (NCTAMS LANT N00FM) Email: Robert.joas.civ@us.navy.mil Office: 757-400-9344

15.2. Government Representative

TBD ARO

15.2.1. TBD (Alternate)

15.3. On-Site BCO Technician

TBD ARO

15.3.1. TBD ARO

15.4. NCTAMS LANT (Norfolk) Plans and Projects Representative

15.4.1. TBD ARO

15.4.2. TBD ARO