Attch 1 Hurlburt Field LTS PWS_v5 27 Feb 2026.pdf

CUI

PERFORMANCE WORK STATEMENT (PWS)

Local Telecommunication Services (LTS)

Hurlburt Field, FL

VERSION: 5

DATE: 27 Feb 2026

PWS Version 5

Date: 27 Feb 2026

Page i of 17

TABLE OF CONTENTS

1. INTRODUCTION

1.1. Objective

1.2. Background

2. SCOPE

2.1 Outages

2.2. Services Summary

3. GOVERNMENT PROVIDED SPACE AND SERVICES

3.1. Securing and Safeguarding

3.2. Rack Space

3.3. Environmental Controls

3.4. Wall Space

4. GENERAL REQUIREMENTS

4.1. Personnel

4.1.1 Scope of Personnel Management

4.1.2. PERFORMANCE REQUIREMENTS

4.1.3. Performance Requirements Summary

4.1.4. DELIVERABLES

4.2. Government Emergency Telecommunications Service (GETS)

4.3. Interconnection Agreements, and Cutover Plans

4.4. Safety, Health, and Fire Protection Requirements

4.5. Manpower Reporting

4.6. Contractor Software and Hardware Requirements

4.7. Protection of Critical Information

4.7.1. General

4.7.2. Critical Information and Indicators List (CIIL)

4.7.3. Handling and Transmission Requirements

5. APPENDICES

APPENDIX 1 – SITE SPECIFIC REQUIREMENTS

APPENDIX 2 - DEFINITIONS & ACRONYMS

1. INTRODUCTION

1.1. Objective

This requirement will provide essential Local Telecommunication Services (LTS) and Long-Distance services and features supporting Hurlburt Field. Site specific equipment connectivity requirements are identified in Appendix 1, along with required features. This LTS will support the installation 24 hours a day/seven days a week/365 days a year (24/7/365). The requirement is for IP trunking to the Hurlburt Field Call Manager.

1.2. Background

LTS does not include Defense Switching Network (DSN) services, which are beyond the scope of this action. Due to changes in technology, equipment, and processes, it has become evident that the Government should acquire these services in a performance-based manner, consistent with the principles contained in Air Force Instruction (AFI) 63- 138 “Acquisition of Services.” These services are considered Information Technology (IT) In Accordance With (IAW) Defense Federal Acquisition Regulation Supplement (DFARS)

239.74 “Telecommunications Services.” The requirement herein represents the site’s performance-based requirements for local “dial-tone”, local calling, nationwide long-distance, international, and ancillary services as defined herein. As a part of the new process, the Air Force (AF) encourages the Contractor to identify or suggest improvements to existing LTS processes, operating procedures, systems, or applications to the Contracting Officer (CO).

This service will be provided by the contractor through IP service circuitry and will handoff to the government system through PRI circuits. This configuration will create a separation between the contractor service and the government system and protect the government data system.

2. SCOPE

The Contractor shall provide all personnel management, labor, tools, facilities, materials, and services needed to perform and provide local access to the designated circuit demarcation point(s) identified in Appendix 1 to this PWS. These services shall include any equipment, wiring, or infrastructure to ensure the Contractor’s proposed solution is compatible with the Government’s current infrastructure without additional Government expense. These services shall not include residential or business services for non- Government entities or Government contractors. The Contractor shall follow all Federal Communications Commission (FCC), Public Utility Commission (PUC), Department of War (DoW), Air Force, and industry standards for this requirement.

The Contractor shall provide and install transmission equipment and cables for local exchange access and transport service circuits to the Government-provided floor space at the Government demarcation locations identified in Appendix 1. The Contractor shall connect to Government-provided power connection points and termination frames. The Contractor shall coordinate with the Government Point of Contact (POC) (primary and alternate names, emails, and telephone numbers shall be provided by the Government

No Later Than (NLT) five days after contract award and prior to any installation. The Government does not authorize aerial cable installations.

2.1 Outages

2.1.1. Scheduled Outage. The Contractor shall notify the Government POC of any scheduled outage that will affect any telecommunication service. The Contractor shall inform the Government POC NLT 30 days prior to the scheduled outage. The Contractor shall provide a detailed explanation for the outage to include the amount of downtime and end users affected. The Contractor shall notify the Government POC via email of the need for any scheduled service outages. Such outages shall be scheduled to minimize inconvenience to users. The Government POC must release all affected equipment and circuits prior to any service disruption. The Contractor shall follow procedures identified below for outages.

2.1.2. Unscheduled Outages. If multiple facilities, areas, primary trunks, or cables/fibers are impacted, the Government POC shall assign the category of the outage and establish the repair priority. The Contractor shall notify the Government POC verbally of problem(s) and follow-up with documentation via email within time specified for each outage type.

2.1.3. Outage Procedures. The Contractor shall follow procedures identified below for outages. In all cases, notification shall include:

• Reason for interruption.

• Duration.

• Start and stop times.

• Affected equipment, lines, and buildings; and

• Restoration action (what service was impacted and how service was restored)

2.1.4. Outage Priority, Restoration of Service, and Maintenance. The Contractor shall respond and restore service outages. From the time of receipt of the notification, the Contractor shall respond and coordinate with the Government POC within the time limits indicated below. For mission-essential functions, the Government POC shall identify and prioritize the essential contractor services. The Contractor shall prioritize and perform restorations IAW the Telecommunications Services Priority (TSP) and Restoration Priority List (RPL), which are provided by the Government POC. If the Contractor anticipates not being able to perform any of the essential contractor services (i.e. beyond the Contractor’s control) IAW the TSP and RPL during a crisis, the Contractor shall notify the Government POC as expeditiously as possible and use its best efforts to cooperate with the Government in the efforts to maintain the continuity of operations. If the Government POC determines that the outage restoration time frames cannot be met for other non-mission essential functions, the Government POC can declare any outage restoration priority level as catastrophic to emergency to serious to routine if the outage significantly affects the mission of the Government.

2.1.4.1. Catastrophic Outage. A catastrophic outage demands immediate attention, such as a total loss of service, loss of network control, and loss of call processing capability to 95% or more of equipped lines and/or trunks. The Government POC can declare any outage as a catastrophic outage if the outage significantly affects the mission of the Government. A catastrophic outage is normally a sudden and widespread disaster stemming from the result of a man made or natural disaster in which property and site network infrastructure are destroyed. Restore service time will be determined from the time the Contractor responds to the Government’s notification IAW the local TSP and RPL requirements. The Contractor must advise the Government POC of their restoration procedures for the base in a catastrophic situation. The Contractor shall respond to the outage NLT one hour of receipt of notification by the Government POC and advise the Government POC of its restoration procedures for a catastrophic situation. The Contractor shall provide the Government POC with updates NLT every four hours on the status of restoration actions.

2.1.4.2. Emergency Outage. An emergency outage demands rapid action. The Government POC can declare any outage as an emergency outage if an outage significantly affects the mission of the Government. Emergency is defined by the Government as any outage that severely hampers the Air Force mission and can be restored within the restoration parameters. The Contractor shall respond to the outage NLT one hour of receipt of notification by the Government POC. The Contractor shall restore service NLT eight hours from the time the Contractor responds to the Government notification.

2.1.4.3. Serious Outage. A serious outage demands timely action, such as degraded service or a fault condition that makes the system perform at a level less than that for which it is designed; condition discovered in automatic routing which has not shown in the operation of the equipment but requires attention. The Government POC can declare any outage as a serious outage if an outage significantly affects the mission of the Government. The Contractor shall respond to the outage NLT one hour of receipt of notification by the Government POC. The Contractor shall restore service NLT 24 hours from the time the Contractor responds to the Government notification.

2.1.4.4. Routine Outage. A routine outage minimally disrupts service to property, equipment, and site infrastructure. The Government POC can declare any outage as a routine outage if an outage does not seriously affect the mission but does hamper day-to-day operation of the Government installation. The Contractor shall respond to the outage NLT one hour of receipt of notification by the Government POC. The Contractor shall restore service NLT two calendar days from the time the Contractor responds to the Government’s notification.

2.2. Services Summary

2.2.1. Services Summary (SS)

Performance Element Number

Performance Objective

PWS

Paragraph

Performance Threshold

1 Perform and provide local access at the designated circuit demarcation points identified in Appendix 1 to this PWS.

2 Continuous operation local phone service 24/7/365 with 99.9% availability

2 Inform the Government POC NLT 30 days in advance of scheduled outage providing a detailed explanation for the outage.

2.1.1 Timely and detailed

notification provided 100% of time

3 Responds and restores Catastrophic Priority service outages IAW PWS, TSP, and RPL as coordinated with the Government POC.

2.1.4 and 2.1.4.1

Timely response to notification and timely restoration of services provided 100% of the time

4 Respond and restore Emergency Priority service outages IAW PWS, TSP, and RPL as coordinated with the Government POC.

2.1.4 and 2.1.4.2

Timely response to notification and timely restoration of services provided 100% of the time

5 Respond and restore Serious Priority service outages IAW PWS, TSP, and RPL as coordinated with the Government POC.

2.1.4 and 2.1.4.3

Timely response to notification and timely restoration of services provided 100% of the time

6 Respond and restore Routine service outages IAW PWS, TSP, and RPL as coordinated with the Government POC.

2.1.4 and 2.1.4.4

Timely response to notification and timely restoration of services provided 100% of the time

2.2.2. Inspection. The performance threshold briefly describes the minimum acceptable levels of service required for each requirement. The Government has the right to inspect all services identified within the contract (SS and Non-SS items), to the extent practicable during the term of the contract.

2.2.3. Grade of Service. Locations carrying contracted voice grade, which is packetized for transport across an IP, MPLS, or other IXC system require grade of service (GoS), implemented as quality of service (QoS), to ensure that end-to-end per-call latency and packet jitter remain within ITU standards. This requirement is applicable to VoIP traffic, video traffic, or other real-time traffic that has been identified and contracted for an elevated GoS. Vendor will ensure QoS end to end including through sub-contracted external LEC/CLEC facilities; implementation strategies that may include Committed Access Rates (CAR), Expedited Forwarding (EF), and traffic shaping determined by customer marked Differentiated Service Code Point (DSCP) packets or pre-contracted data flows.

3. GOVERNMENT PROVIDED SPACE AND SERVICES

3.1. Securing and Safeguarding

The Contractor shall secure Government facilities, equipment, and materials before leaving a facility. The Contractor shall safeguard the Government provided facilities and material contained therein.

3.2. Rack Space

The Government will provide 4U (7”) of rack space in a 19” rack at CPE locations 117 Howie Walters Road, Hurlburt Field, FL 32544 and 515 Cody Ave., Hurlburt Field FL 32544 for the installation of the Contractor’s provided transmission equipment. The floor space shall be coordinated with the Government POC to accommodate Contractor-provided relay rack(s), at each demarcation point. Space is available for relay rack(s) for Contractor equipment in the demarcation point.

3.3. Environmental Controls

The Government will provide sufficient environmental controls to maintain humidity and temperature within the Contractor’s equipment operating specifications. In addition, the Government will provide primary and emergency conditioned power sources to operate the Contractor’s equipment within manufacturer’s specifications.

3.4. Wall Space

The Government will provide no wall space.

4. GENERAL REQUIREMENTS

4.1. Personnel

The Contractor is solely responsible for ensuring sufficient personnel are assigned to this requirement. Appropriate personnel shall possess the qualifications and certifications to perform the requirements listed herein. These qualifications and certifications shall include those required by the Original Equipment Manufacturer (OEM) to maintain, install, and/or operate the equipment covered by this contract. Additionally, the contractor must ensure the contract is completed efficiently and in full compliance with all security and training requirements. The Government requires a reliable method to verify that all contractor personnel assigned to this effort meet the required standards for security clearance, citizenship, and annual training. The desired outcome is a fully compliant, cleared, and trained contractor workforce always.

4.1.1 Scope of Personnel Management

The contractor shall provide the necessary services, qualified personnel, and management to achieve the performance outcomes described in this PWS. The contractor has the flexibility to determine the methods and processes to achieve the standards outlined below.

4.1.2. PERFORMANCE REQUIREMENTS

The contractor shall manage its workforce to ensure 100% compliance with all contractual security and training requirements. The contractor shall provide the Government with regular, accurate, and timely reporting that validates this state of compliance. The report shall serve as the primary evidence that the performance standard has been met. This report is defined as CDRL A001 on the DD Form 1423.

The contractor shall maintain a current listing of employees. The list shall include each employee’s full name, aliases and social security number, security clearance, security clearance effective date and shall be marked Controlled Unclassified Information (CUI).

The original and one copy of this list shall be furnished to the Contracting Officer at the pre-performance conference. Personnel changes at Hurlburt Field, Florida that are made during the performance of this contract shall be sent to the CO and COR, within two (2) working days of the change.

4.1.3. Performance Requirements Summary

Performance Objective

Required Standard Acceptable Quality Level

Method of Surveillance

PO-1: Maintain a Compliant Workforce. The contractor shall ensure all personnel meet contract requirements for US Citizenship and background checks.

All personnel data is accurate and verifiable upon request. The submitted report

(CDRL A001)

contains no factual errors regarding citizenship or background check status.

99% accuracy per report. No more than 1 data field error per 100 personnel entries.

Zero errors related to citizenship are permissible.

100% inspection of the submitted

CDRL A001.

Periodic validation (e.g., random sampling of 5% of personnel records quarterly) by the

COR.

PO-2: Ensure Annual OPSEC Training. The contractor shall ensure 100% of assigned personnel complete the annual OPSEC training requirement.

All personnel listed on the report have a valid OPSEC training completion date within the last 365 days.

100% compliance.

No personnel may have lapsed training.

100% inspection of the training dates listed in CDRL A001.

PO-3: Deliver Timely and Accurate Reports.

The report is delivered on or before the due date

100% on-time delivery. Delivery no more than two

Monitor submission dates. Automated

The contractor shall deliver the Personnel Roster and Compliance Report (CDRL A001) on schedule.

specified in Block 12 and 13 of the DD Form 1423. The report is submitted to all addressees listed in Block 14.

(2) business days late is acceptable with prior notification and approval from the

COR.

tracking or manual log by the COR.

4.1.4. DELIVERABLES

The contractor shall provide the following data items in accordance with the attached DD Form 1423. The content of these deliverables will be used to assess performance against the standards in the PRS.

CDRL Seq.

No.

Title DID Reference PWS Reference

A001 Personnel Roster and Compliance Report

DI-MGMT-

81832

PWS 3.1, PO-1, PO-2,

PO-3

4.2. Government Emergency Telecommunications Service (GETS)

GETS will be used in an emergency or crisis when the Public Switched Telephone Network (PSTN) is congested and the probability of completing a call over normal telecommunication means has significantly decreased. The Contractor must have NPA

(710) in the switch to allow access to the GETS line assigned to a specific site. Authorized users are provided access to an emergency service by dialing 0/1+710-NXX-XXXX. The 710 NPA provides access to a tariffed service of the GETS interexchange carriers and the call is billed to the United States Government.

4.3. Interconnection Agreements, and Cutover Plans

In the event the award is made to a non-incumbent contractor, the incoming Contractor shall submit all Interconnection Agreements (IAs) via link, or as an addendum, to the Government with their quote. The addendum is not included in the technical quote and no page limitations apply to this submittal. Additionally, if providing a quote as a Competitive Local Exchange Carrier (CLEC) for any and/or all services, provide documented evidence of IAs and/or leasing agreements relevant to this effort.

For Government planning and funding purposes, the Contractor, as industry experts, is required to inform the Government of their anticipated cutover time frame. The Contractor shall develop and submit an Initial Cutover Plan to the Government with their technical quote. A Final Cutover Plan is required to be submitted NLT ten (10) working days after contract award. This plan shall include installation of the initial required services for cutover of LTS requirements, along with the recommended time frame to complete each phase of the cutover process. The Contractor shall coordinate deviations from the finalized Cutover Plan with the Government POC prior to any work commencing in the affected area. The Contractor shall ensure that all circuits, equipment, and service provided by the incumbent, under the prior contract, are disconnected/discontinued upon successful cutover. At this point, the Contractor shall inform the Government POC that the previous provider’s equipment is no longer needed and may be removed by the previous provider. Any omissions or discrepancies in the Cutover Plan does not relieve the Contractor of its responsibility to install, cutover, and perform all services identified in this requirement. It is the Contractor’s responsibility to resolve any issues associated with these efforts within a time agreed upon by the Government POC and the Contractor.

4.3.1. Cutover Plan Content. The Cutover Plan shall contain, at a minimum, the following site-specific information:

a) Overview/Scope of plan, indicating proposed timeframe to complete cutover.

b) A detailed Implementation Plan in working days to complete requirements listed in

PWS as site-specific (see Appendix 1). The use of a Gantt or Milestone chart to illustrate your plan is suggested.

c) Conditions/Support required prior to the start of cutover.

d) A listing of Offeror responsibilities.

e) A listing of proposed Government responsibilities.

f) Key Departments essential to the Offeror’s Installation and Cutover Plan available to participate in routine progress meetings with the Government on a weekly or bi-weekly basis.

g) Key POC List for Contractor, Customer Site and Government Contracting Office must be included in the Final Cutover Plan.

4.4. Safety, Health, and Fire Protection Requirements

The Contractor shall follow local procedures established by the local safety and health offices. Reference the instructions in Code of Federal Regulations (CFR) 29, Part 1926.58, Appendix G for proximate to asbestos containing materials. The Contractor shall record and report to the CSO all available facts relating to each instance of accidental damage to Government property or injury to either Contractor or Government personnel.

4.5. Manpower Reporting

The Contractor shall report ALL Contractor labor hours (including subcontractors) required for performance of services provided under this contract. The Contractor shall completely fill in all required data fields using the Contractor Manpower Reporting Application (eCMRA) following web address: http://www.ecmra.mil/. Reporting inputs will be for the labor executed during the PoP during each Government FY, which runs Oct 1 through Sep 30. While inputs may be reported any time during the FY, all data shall be reported NLT Oct 31 of each calendar year, beginning with 2018. Contractors shall direct questions to the AF Support Desk. Information is proprietary in nature when the contract number and Contractor identity are associated with the direct labor hours and dollars. At no time will any data be released to the public with the Contractor name and contract http://www.ecmra.mil/ number associated with the data. Data for AF service requirements must be inputted into the AF eCMRA site. However, user manuals for Government and Contractors are available at the Army CMRA website.

4.6. Contractor Software and Hardware Requirements

All equipment and software used for the requirement must be provided through approved sources. All equipment and materials and software must be Trade Agreements Act (TAA, 19 U.S.C. §§ 2501–2581) compliant. TAA mandates that products sold to the U.S.

government on 5918 Schedule contracts must be manufactured or "substantially transformed" in the U.S. or a TAA-designated country. Contractor must supply a list of materials and software used in this effort along with country of origin and chain of custody.

4.7. Protection of Critical Information

4.7.1. General

The contractor shall be responsible for safeguarding all unclassified but sensitive government information related to this contract. This information is designated as Critical Information (CI) and includes, but is not limited to, Controlled Unclassified Information (CUI) and Personally Identifiable Information (PII). The loss, compromise, or disclosure of CI can be expected to adversely affect mission accomplishment.

4.7.2. Critical Information and Indicators List (CIIL)

The Government will maintain a CIIL identifying known items of CI. The contractor shall adhere to the handling and protection requirements for all information listed on the CIIL.

The CIIL is not all-inclusive, and the contractor is responsible for exercising judgment and protecting any unlisted information that could, if disclosed, impair the mission.

4.7.3. Handling and Transmission Requirements

The contractor shall adhere to the following minimum protection standards for all CI:

a. Access: Access to CI shall be restricted to personnel with a direct need-to-know who are working on this contract. Information shall be shared only between the contractor and the Government.

b. Public Disclosure: No CI shall be released to the public, posted on any publicly accessible website, or discussed in any public forum.

c. Electronic Transmission: All CI transmitted over any electronic network (e.g., email, file transfer) must be protected using Government-approved encryption (e.g., FIPS 140-2 validated).

d. Physical Security: Printed documents containing CI must be stored in a secure, locked container when not in use and shredded before disposal.

4.7.3. Critical Information and Indicators List (CIIL)

Category Critical Information (What our Adversary needs)

Indicators (What our adversaries see/hear)

Personnel/Admin Specific Locations/Addresses: Physical addresses and building numbers for sensitive sites, including Customer Premise Equipment (CPE) and Local Exchange demarcation points.

Observable Activities:• Unencrypted emails or work orders containing site addresses.• Technicians discussing work locations in public.• Unmarked vehicles making repeated stops at specific facilities.• Social media posts geotagged at or mentioning a work site.

Personnel/Admin Key Personnel & Contact Information: A list of Government and contractor Points of Contact (POCs), including primary/alternate names, roles, direct-dial numbers, and email addresses.

Unsecure Communications:• Unencrypted email distribution lists.• "Out of Office" replies that provide detailed alternate POC info.• Contact lists posted on unsecured internal websites or shared drives.• Business cards or conference attendee lists left unattended.

Logistics/Equipment Equipment Details & Vulnerabilities: The specific make, model, software versions, and IP addressing schemes of network hardware. Knowledge of applied (or not applied) DISA STIGs.

Technical & Human Indicators:• Unencrypted network management traffic (e.g., SNMP).• Purchase orders or support tickets listing exact hardware models.• Job postings requiring experience with specific equipment/software.• Technicians discussing patching or vulnerabilities over unsecure channels.

Logistics/Equipment Contract & Budget Information: Details of the

Public & Semi-Public Records:• Vendor contract, including the vendor, budget, and specific technical requirements or specifications.

employees listing the specific project on public resumes (e.g., LinkedIn).• Unsanitized public contract award announcements.• Discussions about budget or contract scope in open forums or with uncleared personnel.

Network Operations Network Architecture & Diagrams: Configuration diagrams, service routing diagrams, VLAN information, routing protocols used, and overall network topology.

Data Leakage:• Improperly stored or transmitted network diagrams on unclassified systems.• "Shoulder surfing" an engineer's workstation.• Network discovery scans from a compromised machine.• Photos of network racks or diagrams in the background of pictures.

Network Operations Scheduled/Unscheduled Outages & Link Failures: Specifics of service interruptions, including the reason, exact start/stop times, duration, affected users, and restoration status.

Real-Time Communications:• Wide-distribution emails announcing maintenance or explaining an outage.• Unencrypted help desk chats or radio traffic discussing an outage.• A sudden spike in user complaints on forums or social media.• Changes in network traffic patterns visible to an outside observer.

Network Operations Call Data & Billing Records: Detailed call records from billing reports, including originating/destination numbers, time, and date, which can be used for pattern-of-life analysis.

Improper Data Handling:• Unencrypted transmission or storage of billing files.• Physical billing documents being discarded without shredding.• Unauthorized access to financial or telephony management systems.

Network Operations Directory Numbers (DIDs): The specific blocks of Direct-Inward- Dial numbers assigned to the installation, which could be used for targeted vishing or signals intelligence.

Leaked Internal Information:• An internal phone directory posted on a public-facing or improperly secured website.• Sequential dialing attempts by an adversary that receive a consistent pattern of responses (e.g., standard military greeting).

5. APPENDICES

APPENDIX 1 – SITE SPECIFIC REQUIREMENTS

5.1. Required Services and Features

The Contractor shall provide the following Government line of local commercial communications services for Hurlburt Field, FL at cutover. Innovative technical solutions are encouraged but must be compatible with the current requirement that is listed in the remainder of this Appendix. The quantity of these initial service requirements will be incorporated into the Pricing Schedule. The installation service requirement will be identified here in Appendix 1 and in the Pricing Schedule.

The government requires physically diverse service for this requirement and is described in paragraph 5.11.

The Government Communication Services Officer (CSO) and Technical Representative shall be identified at the post award conference and updates provided to the contractor as required by the CO.

5.2. Direct-Inward-Dialing (DID) Directory Numbers.

The Government requires the following DiD numbers for this requirement.

NPA- NXX-XXXX DID Directory Numbers

(850) 884-0001 to 9999 10000

(850) 881-0001 to 6999 7000

(850) 881-8000 to 9999 2000

TOTAL 19000

5.3. Local and Long-Distance Services. The contractor will provide access to local, long-distance, and international calling services for all the NPA-NXX DiD numbers assigned through this PWS to Hurlburt Field.

Outbound long distance via domestic United States VoIP network.

Uses SIP signaling protocol

Includes G.711 G.729A and G.729AB CODEC support

Unlimited Nationwide Long Distance at a flat rate.

International calls on a “Plan” Rate (preferred) and/or “Pay-Per-Use” rate. with detailed monthly billing reports for International Calls sent to 515 Cody Ave, Hurlburt Field, FL.

32544. Each International call detail should include at a minimum:

Date, Time, Originating Number, Destination Number, Rate of Charge, number of minutes charged, total charge.

Unlimited flat rate Intralata calling within the LATAs 44813 Pensacola FL. Pensacola EAEA, 44814 Pensacola FL Crestview EAEA, and 44815 Pensacola FL Fort Walton Beach EAEA if not covered under the Nationwide long-distance flat rate.

5.4. Local Exchange Digital SIP Trunks. 2 .

Circuit ID Quantity Concurrent Call Paths (CCPs) Demarcation 1 SIP Trunk ID

TBD 1 75 117 Howie Walters Road, Hurlburt Field, FL 32544

1 SIP Trunk ID TBD 1 75 515 Cody Ave., Hurlburt Field, FL 32544

5.5. Diversity/Diverse Routing.

Physical diversity will be required for this service. The Government telephone switching system is identified in two interface Customer Premise Equipment (CPE) locations as a Cisco UCS 240 M5 with the Software Revision/Version#: 14SU3a. The interface for the PRI handoff is a Cisco C8300-2N2S-4T2X Voice Gateway in both CPE locations. The first CPE location is building 91023 with address of 117 Howie Walters Road, Hurlburt Field, FL 32544. The second CPE location is building 90624 with address of 515 Cody Ave., Hurlburt Field, FL 32544. Diverse paths will ensure survivability if one circuit becomes disabled on the Commercial contractor side of the service or the Government side of the service. Conditioned facilities, Rack space and power will be provided for the contractor equipment by the government. Calls originating or terminating in any CPE location should be able to be initiated or received from anywhere in the Hurlburt Field VoIP system.

5.6. E911 Compatibility.

The Contractor shall provide configuration diagrams to show access to 911/E911 services, where available, through the local city or county emergency services organization.

NOTE! E911 calls placed on the 850-881-XXXX and 850-884-XXXX phone numbers go to the PSAP located in Bldg 90215 and are received at the Fire Department. Calls from the Hurlburt Billeting switch are also answered at the Fire Department. Calls placed from commercial lines and cell phones go to the Okaloosa County Dispatch Center and are transferred to the Hurlburt PSAP by personnel at the Okaloosa County Dispatch Center.

5.7. Special Services

Examples of vendor circuit/trunk routing supporting Appendix 1 requirements are provided in diagram 1 below. This example applies to Hurlburt Field for SIP trunking delivery. The contractor will follow (Defense Information Systems Agency) Security Technical Implementation Guides (STIGs) The Carrier, if providing a CPE installed digital loop carrier system or other IP based CPE gateway system, will provide the customer with IP, VLAN, routing protocols or other pertinent information to allow the customer to logically interface with the carrier system. The customer owned demarcation device will in most cases consist of an Edge Boundary Controller providing isolation and firewall services. The vendor shall provide a 24/7 capability to monitor the IP connection to the customer gateway equipment and alert the customer to a link failure; the customer must also be able to reach the vendor’s network operations center on a 24/7 basis.

5.8. Service Routing.

Contractor shall submit a service routing diagram (example below) and/or service routing description in their technical quote. Contractor may provide the requested diagram and legend using these formats or a similar format to be in compliance with paragraph 4.3.1.

Submission of a generic diagram or not explaining the service routing may be determined technically unacceptable.

5.8. National Institute of Standards and Technology (NIST) Compliance.

The Contractor shall include specific security requirements for the control and monitoring of VoIP technologies IAW NIST directives. The SIP trunking must comply with these standards, specifically NIST SP 800-171 revision 3.

Diagram 1

Diagram 2 Current Hurlburt Field Configuration

APPENDIX 2 - DEFINITIONS & ACRONYMS

Table A. Definitions

TERM DEFINITION

Call Setup Success Rate (CSSR)

The fractionalized amount of calls that make a successful connection to a dialed number, this is divided by the total number of calls placed. (As defined by International Telecommunication Union).

Circuit Termination Circuit termination at the Government installation includes the Main Distribution Frame (MDF) for analog signals, metallic cable pairs, Digital Signal Cross-Connect (DSX)-1 patch, cross connect panel(s) for T-1 and/or T-3 circuits, fiber optic patch and cross connect panels for optical interface equipment such as the optical carrier or SONET or MPLS systems, optical multiplexer equipment, and may extend to Cat 3/5/6 RJ-45 jack fields if directed by the Government POC to ensure adequate hand off of the circuit to the Government. Other wall-mounted, punch-down, terminal blocks are used for isolation and termination of Contractor metallic facilities.

Communications Focal Point (CFP)

A 24/7 Focal Point located on an Air Force Facility that provides one stop notification services and provides reporting and tracking of communications outages to Government users of the communication systems.

Commercial Subscriber lines

(CSL)

A CSL is defined by Government standards as a voice grade subscriber line serving directly from the Contractor’s central office switch to customer’s location.

Competitive Local Exchange Carrier

(CLEC)

A telephone company that competes with the already established local telephone business by providing its own network and switching.

Contractor A supplier or vendor awarded a contract to provide specific supplies or service to the Government. The term used in this contract refers to the prime.

TERM DEFINITION

Customer Premise Equipment (CPE)

Also known as Customer-Provided Equipment is any equipment located at a subscriber's premises and connected with a carrier's telecommunication network at the contractually established demarcation point. The demarcation point contractually separates the customer equipment from the equipment located in either the distribution infrastructure or central office of the communications service provider. Vendor installed CPE devices are fully vendor owned, maintained, and monitored by the Vendor’s management platform. CPE equipment can be powered from the customer source electrical system, but a sufficient emergency power source must be available during periods of customer power interruption for any services contractually requiring a high level of reliability.

Customer Service Record (CSR)

Report that details the fixed monthly charges billed by the local telephone company. The CSR is composed of computer codes called USOCs, which in turn correspond to a particular tariffed service.

Defective Service A service output that does not meet the standard of performance associated with the PWS.

Deliverable Anything that can be physically delivered, but may include non-manufactured things such as meeting minutes or reports.

Dropped Call Rate

(DCR)

The fractionalized amount of calls that experience a lost connection after a successful initial call establishment. (As defined by International Telecommunication Union).

DS-1 A DS level and framing specification for synchronous digital streams, over circuits in the North American digital transmission hierarchy, at the DS1 transmission rate of 1,544,000 bits per second. DS1 is commonly used to multiplex 24 DS0 channels.

Each DS0 channel, originally a digitized voice-grade telephone signal, carries 8000 bytes per second (64,000 bits per second). A DS1 frame includes one byte from each of the 24 DS0 channels and adds one framing bit, making a total of 193 bits per frame at 8000 frames per second. The result is 193*8000 = 1,544,000 bits per second.

TERM DEFINITION

Edge Boundary Controller (EBC)

A customer provided network node device that provides firewall, intrusion detection, routing, QoS, and packet equalization between the Vendors IP Wide Area Network and the interior customer IP network. The EBC will provide the logical demarcation point between IP SIP delivered services when applicable and will physically interface to the vendor’s CPE Gateway Router device.

Extended Area Calling Service

A geographic area beyond the local service area to which traffic is classified as local for selected customers, i.e., telephone service that allows subscribers in one exchange to call subscribers of another exchange without a toll charge or for a negotiated fixed rate.

Flat Rate A non-fluctuating monthly rate for telephone service in which an unlimited number of local calls can be made without further charge the extent of the contract. The monthly rate is established in the contract.

Government Emergency Telecommunications Service (GETS)

A White House-directed emergency phone service provided by the National Communications System (NCS) in the Cyber Security & Communications Division, National Protection and Programs of the Department of Homeland Security. GETS supports Federal, State, local, and tribal Government, industry, and non-Governmental organization (NGO) personnel in performing their National Security and Emergency Preparedness (NS/EP) missions. GETS provides emergency access and priority processing in the local and long distance segments of the Public Switched Telephone Network (PSTN). It is used in an emergency or crisis situation when the PSTN is congested and the probability of completing a call over normal or other alternate tele-communication means has significantly decreased. The servicing LEC must have NPA (710) in the switch to allow access to the GETS line assigned to a specific site. Dialing 0/1+710-NXX-XXXX provides access to an emergency service for authorized users. The 710 NPA provides access to a tariffed service of the GETS interexchange carriers (AT&T, MCI WorldCom, and Sprint) and the call is billed to the U.S.

Government. Web link:

http://gets.ncs.gov/

Incumbent Local Exchange Carrier

(ILEC)

The dominant phone carrier within a geographic area as determined by the FCC Section 252 of the Telecommunications Act of 1996 provided local exchange service to specific area.

TERM DEFINITION

Interconnection Agreement

A business contract between telecommunication organizations for interconnecting their networks and exchanging telecommunication traffic. These agreements are present in both public switched telephone networks and the Internet.

Intra LATA Local toll service (also called intra-Local Access and Transport Area (LATA), local long distance, or regional toll service) provides calling within a geographic area known as a LATA. Per-minute toll charges usually apply to these calls.

Local Exchange Access and Service Areas

Areas shall include the areas/zones coverage as currently defined by the incumbent local service provider(s) and/or the State PUC for the Site and shall be applied under the scope of this contract and provide a list of these local exchange access service areas and any updates as they accrue. When the Contractor provides services to a Government installation, the LATA boundary shall not be limited or restricted to a Contractor’s service area. Connection to intra-LATA exchange areas and with inter-LATA exchange carriers is required.

Measured Rate A message rate structure in which the monthly phone line rental includes a fixed rate on calls within a defined area. Measured services are often charged on the number of calls, the time of day, the distance traveled and/or the length of the call.

Non-Recurring Charges

A one-time fee IAW the established tariff rates at time of award that is associated with adding a local exchange service, including installment, activation and/or equipment.

Physical Security Actions that prevent the loss or damage of Government property.

Quality Assurance The Government procedures to verify that services being performed by the Contractor are performed according to acceptable standards.

Quality Control All necessary measures taken by the Contractor to assure that the quality of an end product or service shall meet contract requirements.

Reliability The probability that a system will not fail during a specified period of time.

TERM DEFINITION

Resilience The ability of a system to recover to its normal operating form after a failure or an outage.

Session Initiation Protocol (SIP)

A communications protocol for signaling, call setup/teardown, and communication of telephone and Video Real-Time Systems over an IP Based Unified Communication System. (As defined by Internet Assigned Numbers Authority & Request for Comments).

Session Initiation Protocol (SIP) Trunking

A Voice over Internet Protocol (VoIP) and streaming media service Based on the SIP by which Internet telephone service providers (ITSPs).

SIP Trunk An IP Based virtual connector between Unified Communication Systems designed to transport high-density unicast & multicast telephone/video traffic channels.

Traffic Analysis Inference of information from observable characteristics of data flow(s), such as the identities and locations of the source(s) and destinations(s), and the presence, amount, frequency and duration of occurrence.

TABLE B ACRONYMS:

ACRONYM EXTENDED

AF Air Force AFI Air Force Instruction BRI Basic Rate Interface BS Basic Services BTN Billing Telephone Number CSSR Call Setup Success Rate CFP Communications Focal Point CLEC Competitive Local Exchange Carrier CO Contracting Officer CPE Customer Premise Equipment CSL Commercial Subscriber Lines CSO Communications Services Officer DCO Dial Central Office DCR Dropped Call Rate DFARS Defense Federal Acquisition Regulation Supplement DID Direct In Dial DOD Department of Defense DP Dial Pulse

ACRONYM EXTENDED

DSN Defense Switching Network DSX Digital Signal Cross-Connect DTMF Dual Tone Multi-Frequency EBC Edge Boundary Controller FCC Federal Communications Commission FD Full Duplex FR Flat Rate FX Foreign Exchange GETS Government Emergency Telecommunications Service GS Ground Start HD Half Duplex IAW In Accordance With IC Incoming ILEC Incumbent Local Exchange Carrier ISDN Integrated Services Digital Network IT Information Technology LATA Local Access Transport Area LS Loop Start LTS Local Telecommunications Services MF Multi-Frequency MDF Main Distribution Frame MR Measured Rate NCS National Communications System NS/EP National Security and Emergency Preparedness NGO Non-Governmental Organization NLT No Later Than OEM Original Equipment Manufacturer OG Outgoing POC Point of Contact PRI Primary Rate Interface PUC Public Utility Commission PWS Performance Based Work Statement PSTN Public Switched Telephone Network RPL Restoration Priority List SIP Session Initiation Protocol SS Services Summary TS Telecommunication Services TSP Telecommunications Services Priority WS Wink Start

APPENDIX 2 - DEFINITIONS & ACRONYMS