BTS PWS 9 Dec 25.pdf

December 9, 2025

PERFORMANCE WORK STATEMENT (PWS)

FOR

OPERATIONS AND MAINTENANCE SERVICES

BASE TELECOMMUNICATIONS SYSTEM (BTS)

AT DOVER AIR FORCE BASE DELAWARE

Table of Contents

1.0 DESCRIPTION OF SERVICES

1.1 Scope of Work

1.2 Requirements

1.2.1 Base Mission Requirements

1.2.2 Accident/Incident Reporting and Investigation

1.2.3 Subcontractor Compliance

1.2.4 Base Civil Engineering Work Clearance Requests

1.2.5 Personnel Qualifications

1.2.6 Equipment Maintenance Requirements

1.2.7. Access to Base LAN

1.3 Monthly Maintenance

1.3.1 Perform Telephone Switch System Maintenance

1.3.2 Perform Inside and OSP Maintenance

1.3.3 Preventive Maintenance Inspections (PMIs)

1.3.3.1 PMI Switch Power Test

1.3.3.2 PMI Spare Conductor Test

1.3.3.3 PMI Manholes

1.3.3.4 PMI Terminals

1.3.3.5 PMI Distribution Pedestal Terminals

1.3.4 System and Service Outages

1.3.4.2 Scheduled Outages

1.3.4.3 Outage Restoration

1.3.4.3.1 Emergency Outage

1.3.4.3.2 Priority Outage

1.3.4.3.3 Routine Outage

1.3.4.4 Remote Monitoring (Response to NCC)

1.3.4.5 Outage Cause Identification

1.3.5 Cable Location Staking and Marking

1.3.5.1 Collection of Communication Feature Data (CFD)

1.3.6 System Cross-Connect and Disconnect Services

1.3.7 Voice Mail

1.3.8 Voice Protection System (VPS)

1.3.9 Traffic Measurement and Analysis

1.3.10 Contractor Support Services

1.3.10.2 Contractor Interface and Support for other Vendors

1.3.10.3 Design Review Meetings

1.3.11 Rough Order Magnitude (ROM)/Estimates/Technical Solutions

1.3.11.2 Technical Solution

1.3.12 BTS Work Center Records

1.3.12.1 Maintenance Support Plan (MSP)

1.3.12.2 PMI Inspection Records and Malfunction Report

1.3.12.3 Maintenance/Repair Logs

1.3.12.4 Manhole, Handhole, and Building Terminal Inspections

1.3.12.5 Cable Installation/Repair Test Results

1.3.12.6 Communications and Information Systems Installation Record (CSIR)

1.3.12.7 Scheduled Service Interruption Records

1.3.12.8 Switching System and Inside & OSP Equipment Operational Records

1.3.12.9 CLIN/PID Utilization Report

1.3.12.10 AF Logistics Support Spares Records

1.3.12.11 Contractor-Furnished Hazardous Material

1.3.12.11.1 Section 1, General Information

1.3.12.11.2 Section 2, Product Information

1.3.12.11.3 Section 3, Usage/Storage Amount

1.3.12.12 Global Positioning System (GPS) Service Data

1.3.13 TMS

1.3.13.1 Work Order Records, Including Warranty Records

1.3.13.2 Cable Pair Assignment Records

1.3.13.3 Traffic Measurement Records

1.3.13.4 Equipment Inventory Records

1.3.13.5 Call Accounting System (CAS)

1.3.13.6 System Security Audit Report

1.3.13.7 System Capacity Records

1.3.14. Switchboard Operations - RESERVED

1.4 Work Orders

1.4.1 Work Order Procedures

1.4.1.1 Pre-Priced Items

1.4.1.3 Work Order Classifications

1.4.1.3.1 Routine

1.4.1.3.2 Priority

1.4.1.3.3 Emergency

1.4.1.4 Required Information on Work Orders

1.4.1.7 Special Project Requirements

1.4.1.7.1. Contractor Proposals

1.4.1.8. Removal of Drops Work Orders

1.4.1.9. Submittal of Completed Work Orders

1.4.2 Global Positioning System (GPS) Service

2.0. SERVICE DELIVERY SUMMARY (SDS)

2.1 Inspection of Services

2.2 Corrective Action Report (CAR)

3.0 EQUIPMENT AVAILABLE FOR CONTRATOR USE

3.1 RESERVED

4.1 GENERAL INFORMATION

4.1 Quality

4.1.1 Quality Control Program

4.1.2 Quality Control Plan

4.2 Security

4.2.1 Security Plan

4.2.2 For Official Use Only (FOUO) Material

4.3 Safety, Security, and Environmental Meeting

4.4. Continuation of Mission Essential Services during Crisis

5.0. RECORDS MANAGEMENT

6.1. SECURITY

7.1. CONTRACTOR BADGE POLICIES

8.1. INSTALLATION ACCESS

9.1. ANTITERRORISM AWARENESS LEVEL I TRAINING

10.0. FLIGHTLINE DRIVING

11.0. CONTRACTOR MANPOWERREPORTING

12.0. SOLID and HAZARDOUS WASTE REMOVAL

13.0 APPENDICES

13.1.2 Monthly Maintenance Services .................................................................................. 37 Main Base Yearly Avg Total

13.1.2.2 Locate and Mark Cable. ............................................................................................. 37 Main Base Yearly Avg Total

13.1.2.3 Database Administration

13.1.2.4 Switchboard Operation Workload Estimates

13.1.2.5 Technical Solution. .................................................................................................... 37 Main Base Yearly Avg Total

13.1.6 Work Orders

Main Base

37 APPENDIX 13.2

................................................................................................................................ 39 13.2.2.1 Customer Premise Equipment

13.2.3.1 Dial Central Office (DCO) Switch

13.2.3.3. Paging System for Medical Treatment Facility

13.2.3.4 Command Post Headquarter Switch

Cable Type/Size Installation Method Length

APPENDIX 13.3

13.3.2 Definitions

Contractor Furnished Equipment (CFE)/Contractor Furnished Material (CFM) Equipment/Property Available For Contractor Use

5.3.3 ACRONYMS

APPENDIX 13.4

APPENDIX 13.5

APPENDIX 13.6

58 13.6.1.1 Air Force Instructions (AFI)

13.6.1.2 Other Air Force Document(s)

13.6.1.3 Federal Standards and Specifications

13.6.2 Vendor Documents

APPENDIX 13.7 RESERVED

APPENDIX 13.8

63 13.8.3 Quality Control

13.8.4 Submittal of Deliverables

13.8.5 Uploading CFD into CVC

TABLE A

A.1 Feature Attributes for Comm-Path Entities A.1.1.3 Attributes

A.1.2 GPS_VAULT

A.1.2.3 Attributes

A.1.3 GPS_PEDESTAL

A.1.3.3 Attributes

A.1.4 GPS_DBSPLICE

A.1.4.3 Attributes

A.1.5 GPS_PATH_SEGMENT

A.1.5.3 Attributes A.2 Domain Values for Attributes of Comm-Path Feature Entities A.2.1.3 Attributes A.2.2.3 Attributes A.2.3.3 Attributes A.2.4.3 Attributes

A.2.5.3. Attributes 71 A.2.6 D_DPOBJ: disposition list – object A.2.6.3. Attributes

A.2.7.3 Attributes A.2.8 D_SPCCAS: communications - splice case type A.2.8.3 Attributes A.2.9.3 Attributes

1.0 DESCRIPTION OF SERVICES

1.1 Scope of Work.

The Contractor shall provide all personnel, equipment, tools, materials, vehicles, supervision and other items and services necessary to provide highly reliable telecommunications and networked voice, video and data services, unless specified in this contract as Equipment/Property Available For Contractor Use, to support the mission of 436 Communication Squadron (CS) at Dover Air Force Base, DE. The Contractor shall perform monthly Operations and Maintenance (O&M) services and any other services required to ensure the Base Telecommunications System (BTS) is available 24 hours per day, 7 days per week. The BTS currently consists of an Avaya LSC with Internet Exchange (IX) Voicemail, Sonus Session Border Controllers (SBC), legacy CS1K, the outside plant (OSP) and inside plant systems to include the construction of manhole/handhole, duct systems, and all associated equipment described in Appendix

13.2. A Manhole is typically a 4’x4’x4’ (also other sizes) concrete box the base uses for copper/fiber cable junctions/splices etc. A handhole is a much smaller 24”x36” fiberglass rectangular box with a Quazite lid, and is used much the same as a manhole but on a smaller scale. Both “Boxes” do require certain equipment and physical labor to install them, and/or open their lids. They both require locks to prevent unauthorized personnel from entering them. The equipment required to enter them are Manhole Lid lifting tools. Once the lids are removed, the technicians use high volume water pumps to drain the accumulated water. The Contractor must operate and maintain all BTS equipment and systems in accordance with (IAW) publications in Appendix 13.6.

The Government is currently under contract to decommission and remove the legacy CS1K and transfer all users over to the Avaya Aura platform. Upon decommission and removal of the CS1K, all verbiage and contract support related to the decommissioned equipment will become obsolete. At the conclusion of the decommissioning efforts, the telecommunication environment will contain the CS1K equipment, replaced by Avaya Communications Manager (CM) equipment. At this time exact quantities of the Avaya CM Telephones are unknown but are estimated at approximately 3,500 EI. The Analog and Digital EI are supported by approximately 20ea G-450 Media Gateways distributed throughout 20 geographically separated areas. At this time the Contractor must provide complete O&M as detailed in this PWS to completely support the Avaya LSC, IX voicemail suite and the Sonus SBCs.

The Contractor must completely support the Avaya LSC, IX voicemail suite and Sonus SBCs to include line manipulations. In addition, primary DSN services will be facilitated by a pair of High Availability (HA) Sonus Session Border Controller (SBCs) while primary PSTN (Local and Long Distance) will be facilitated by media gateways via the Avaya LSC.

1.2 Requirements.

1.2.1 Base Mission Requirements.

Contractor may be required to support base mission changes; major or minor BTS infrastructure modifications; and other support requirements necessary for the BTS to meet mission requirements. Missions are frequently interrupted by base exercises or actual ongoing base security events. Support requirements may originate from technology changes, hardware and software systems upgrade, reconfigurations, new or additional equipment, local area network (LAN) cable installations and upgrade, and Dial Central Office (DCO) reconfigurations. This includes routing/diversity requirements and any other environmental changes that could impact or alter the base BTS. Contractor will be required to install telecommunications wiring, other communications systems devices and etc. in dormitories, military family housing, visiting airmen’s and officer’s quarters, temporary lodging facilities as directed by the CO or COR.

1.2.2 Accident/Incident Reporting and Investigation.

Contractor shall record and report to the COR all available facts relating to each instance of accidental Government property damage or contractor personnel injury. Contractor shall secure the scene of any accident and wreckage until released by the accident investigative authority through the Contracting Officer (CO). If the Government elects to conduct an investigation of the incident, the Contractor shall cooperate fully with the COR until the investigation is completed.

1.2.3 Subcontractor Compliance.

Contractor shall be responsible for ensuring subcontractors satisfy the requirements set forth in the contract.

1.2.4 Base Civil Engineering Work Clearance Requests.

Contractor shall obtain a Base Civil Engineering Work Clearance Request, AF Form 103, and/or an AF Form 332, prior to any trenching or digging; facility work; or manhole/handhole entry. Contractor will be required to obtain accounts for the electronic Digging Permit System, or locally developed process provided by Base Civil Engineering. Contractor will be required to process Digging Permits for their own construction and also process and sign off on Digging Permits that are submitted by others for the Communications portion of the permit.

(Note: Base Civil Engineering may be required to schedule and perform this type of work.)

Trenching, excavation, confined spaces entry, confined spaces atmospheric testing/forced air ventilation, and marking and barricading of open trenches are to be performed IAW Occupational Safety and Health Act (OSHA) standards and other provisions of this contract.

1.2.5 Personnel Qualifications.

Contractor is solely responsible for ensuring that sufficient personnel are assigned to this contract and that all personnel are experienced and qualified to perform the services listed in this PWS. Contractor shall identify the key personnel and notify the Contracting Officer Representative (COR) prior to commencing work. Contractor shall provide a key personnel listing and contact information to the COR prior to commencing work and update information on a continual basis to ensure it is always current and correct throughout the life of the contract.

All personnel shall be proficient in understanding, reading, writing, and speaking the English language.

The following are the minimum personnel who shall be designated as “key personnel.” The Government does not intend to dictate the composition of the ideal team to perform this task order (i.e.

if the contractor intends to propose additional labor categories as “key”). The Government desires that key personnel be assigned for the duration of the task order (TO).

a. On-Site Certified Call Manager Technician

Individuals proposed for key personnel positions under this TO are expected to remain dedicated to the TO. Substitutions will not be accepted unless specifically agreed upon and shall be made in accordance with this clause. All proposed substitutions of key personnel must be submitted in writing at least ten

(10) days in advance of the proposed substitution and must be sent to the Contracting Officer (CO) and the Contracting Officer Representative (COR). All requests for substitutions must provide a detailed explanation of the circumstances necessitating the proposed substitution(s) and any other information requested by the CO or COR to make a determination as to the appropriateness of the proposed substitution(s). Substitution requests shall clearly identify how the proposed replacement meets or exceeds applicable standards established in the solicitation (i.e. evaluation criteria minimum qualifications), the task order, and any betterment made thereto by the Contractor via its offer. All proposed substitutes must have qualifications at least equal to the person being replaced. The Government will evaluate requests for substitutions and the CO or COR will notify the Contractor of approval or disapproval.

The successful Contractor must be or must subcontract a Federally Authorized Avaya Partner. The Contractor is solely responsible for ensuring sufficient personnel are assigned to this contract and all personnel are qualified and certified to perform the requirements listed herein, including those qualifications and certifications required by the Original Equipment Manufacturer (OEM), to maintain, install, or operate the equipment covered by this contract. The Contractor must provide personnel who meet the following requirements:

• Any Personnel working with the Avaya CM8 under this Contract must maintain a current approved DoDD 8570 IAT Level II Certification.

A list of approved certifications can be found at the following location:

https://iase.disa.mil/iawip/Pages/iabaseline.aspx

• Key personnel assigned to this Contract must maintain the most current Avaya Call Manager (CM) training.

• Government will offer an Optional class with 2 seats, in the most current Avaya Call Manager (CM) training class at Sheppard AFB, TX per Contract Year if seats are available. There is no cost for the Course itself. The Contractor is responsible for funding Travel, Per Diem and all other expenses associated with this training.

1.2.6. Equipment Maintenance Requirements: Contractor must possess available resources to provide the following on an as needed basis:

Local Session Controller The Contractor shall provide complete Operation and Maintenance (O&M) on the Local Session Controller (LSC) and all peripheral equipment to include any and all security requirements. The Contractor shall ensure that all equipment or services installed, maintained or performed are conducted in accordance with (IAW) the current Joint Interoperability Test Command (JITC) and Military or Department of Defense (DoD) specific Original Equipment Manufacturer (OEM) documentation, unless specified by the Government. The Government has final authority over the deployment and configurations of the LSC and telephony supporting equipment and services. The

Contractor shall inform the Government of any changes to the JITC configuration, Interoperability (IO) tests or the Department of Defense Information Network (DoDIN) Approved Products List (APL) pertaining to the LSC and all systems connected to the LSC within 3 business days of new documentation being released.

AVP Environment The Contractor shall be responsible for O&M of the underlying Avaya Voice Portal (AVP) environment associated to the LSC. The Contractor shall ensure full security compliance of the environment by applying and following all OEM patches, Military Unique Deployment Guide (MUDG), Security Technical Implementation Guide (STIG)s, IO documentation and any controls required by the local IA office.

Linux Operating System The Contractor shall be responsible for O&M of the underlying Linux Operating System (OS) environment associated to the LSC. The Contractor shall ensure full security compliance of the environment by applying and following all OEM patches, MUDG, STIGs, IO documentation and any controls required by the local IA office.

LSC Database The Contractor is required to keep the LSC database updated, organized and accurate. The Contractor will be required to develop a standardized naming or labeling convention with the Government after contract award to be used in all configurations. The Contractor will ensure that all moves, adds, changes or disconnects are accurately depicted in the LSC database to ensure seamless turnover of the Governments systems. Under no circumstance should the LSC database contain configurations or programming for excess or removed equipment. Upon the Government’s request, the Contractor must produce an accurate report of the current subscriber and trunk counts by type within one business day of the requested report

Trunks The Government is leveraging a hybrid environment using both Primary Rate Interface (PRI) and Session Initiation Protocol (SIP) trunks for external and lateral (other telecommunications switches) services. The Contractor shall provide O&M on all trunks related to the LSC regardless of protocol or service. In the event of an outage, the Contractor shall handle all coordination to restore the service within the timelines derived from the Unique Client Registration (UCR). The Contactor is required to troubleshoot transport issues related to SIP trunks and is responsible for coordinating with network infrastructure personnel to resolve any issues. This may include the analysis Call-Detail Record (CDR) information, SIP ladders, ports and protocols, or other in depth data analysis. The Contractor must be able to produce a usage report by trunk within one business day of the request.

Line Moves, Adds, Changes and Disconnects The Contractor shall provide O&M for all subscribers receiving service from the LSC. This includes but is not limited to moving existing lines, adding existing lines, changing protocol (analog to VoIP or vice versa), disconnecting lines, removing configurations, tracking dial plans, etc. The Contractor shall use Government-Furnished Equipment (GFE) equipment from the Government inventory to complete this task. In the event additional software or hardware is needed to perform O&M of the system, including licenses that cannot be leveraged via Government inventory or in-place support contracts, the Contractor must notify the COR immediately.

STIGS/UCR/IA

The Contractor shall be responsible for the assisting the Government with Information Assurance (IA) compliance of the entire telecommunications enclave to include the virtual environment, the server operating systems and the telephony applications. Additionally, the Contractor shall assist Government infrastructure personnel in the applications and tracking of VoIP STIGs as they relate to the network transport. The Contractor must verify the application of STIGs and OEM best practices throughout the entire telecommunications enclave and must notify the COR within 48 hours of a applicable STIG or UCR change.

When there is an update to any STIG or UCR documentation that is applicable to the Dover enclave, the Contractor is required to present a full report indicating the implications of the new STIG or UCR change. This report should contain a timeline associated to the work, required personnel to complete the work and a recommendation for implementation or mitigation process.

The Government has the final authority on whether the STIG or UCR change is applied to the enclave.

Sustainment The Contractor will be required to use the United States Air Force (USAF) Cyber Transport Systems (CTS) Contract or the Air Mobility Command (AMC) CTS Contract for all “break fix” maintenance actions on the Avaya CM8. In the event of an outage due to hardware failure, the Contractor shall attempt to restore the outage with spare equipment that is on hand. Whether the equipment is on hand or a replacement is need, the Contractor must leverage the in place support contracts to get a new part or replace the part from spare inventory. In the event the CTS contracts can be leveraged in lieu of the Contractor’s provided services for the Avaya CM8, the Contractor must liaison with the CTS contract to ensure seamless support.

Patch and Upgrade Management The Contractor shall be responsible for all labor associated to the patch and upgrade management of the Avaya LSC, IX voicemail suite, Sonus SBCs and all underlying hypervisor and server operating systems. The Government shall leverage in place support contracts or other means of acquisition to procure any and all software or hardware needed to facilitate the upgrade and patch management of the before mentioned systems. The OSE shall be required to register for a Single Sign On (SSO) with Avaya in order to receive notification of available patches and upgrades related the LSC and IX voicemail suite. The Contractor shall liaison with local IA to receive notification of patches or upgrade pertaining to the hypervisors or server operating systems.

Upon notification of an upcoming software release, the Contractor is required to present a software upgrade execution plan to the Government within one week. These plans should include security implications, features gained or lost, downtime, any IA documentation needed and suggested Authorized Service Disruptions (ASI) time frames.

Design Improvements In the event the Contractor recognizes an opportunity to optimize or improve overall efficiency related to O&M of the telecommunications enclave, the Contractor may present these to the Government for review. The Government reserves to the right to make all decisions pertaining to the design and overall organization of the telecommunications enclave.

Record Keeping and Logging The Contractor shall be required to thoroughly document all activities related to the O&M of the telecommunications in an attempt to create continuity during Government turn overs. This should include updates to topologies during expansion or reorganization, update to line side records and dial plans via Configuration Accounting Information Retrieval System (CAIRS), records of work orders and completed tasks, inventory counts, open issues, etc. The Contractor shall be responsible for maintaining user accounts and credentials used to access the system for their Contractor personnel.

3rd Party Support The Government reserves the right to solicit third parties to perform upgrades, patches, redesigns, expansions, system removal and all other aspects pertaining to the telephony and transport environment. The Government reserves the right to leverage these services in lieu of the Contractor’s provided services and any cost associated to those services.

1.2.7. Access to Base LAN.

Contractor will be required to obtain a Common Access Card for each individual requiring access to the Base LAN System. All contractors requiring access to the Air Force Network will comply with associated training and guidance in accordance with all applicable guidance.

1.3 Monthly Maintenance.

Overall responsibility to properly maintain and operate the BTS shall rest with Contractor as described by the maintenance support plan (see 1.3.12.1) and be performed IAW the commercial manufacturer’s recommended procedures. Monthly Maintenance is all actions taken by Contractor to maintain equipment and systems in a serviceable condition or to restore it to a serviceable condition to include inspection, periodic testing, adjustment, and repair. The effort includes the replacement of defective circuit packs, replacement of Gateways and Cards in Gateway’s or any other equipment associated with the Call Manager and Customer Premise Equipment (CPE), and preventive maintenance IAW applicable publications and other routine work to optimize the life expectancy of the equipment and cable systems. Work orders will be accomplished IAW 1.4 to include relocates and removals. Monthly Maintenance efforts shall not be postponed or otherwise delayed to accomplish work orders.

1.3.1 Perform Telephone Switch System Maintenance.

Contractor shall operate and maintain the switching system(s) identified in Appendix 13.2 IAW Original Equipment Manufacturer (OEM) procedures. Contractor shall operate and maintain the CM equipment in paragraph 1.2.6. Acceptable standard performance level shall be measured by a determination of the total systems availability (up time) and reliability rating during any given month. A period of five minutes down time shall not be exceeded during any one month period. All equipment or services completed by Contractor shall automatically become part of the monthly maintenance services.

1.3.1.1 Contractor shall perform disk, cartridge, or tape backup of the switching system(s) memory within 24 hours of data base changes. When no database changes have occurred over a seven-day period, Contractor shall perform switching system backup.

1.3.1.2 Contractor shall perform System/Data Administration on all equipment and software associated with the BTS specified in Appendix 13.2.

1.3.1.3 Contractor shall perform software functions and translations for any trunk or circuit configurations required by on-base systems or users; perform adds, moves, changes, deletes, and query of a circuit or system data; and provide directory assistance information, service orders, trouble assistance, records administration, and billing as a function of switch operations.

1.3.2 Perform Inside and OSP Maintenance.

Contractor shall maintain inside and OSP cable and equipment as identified in Appendix 13.2 and IAW applicable documents listed in Appendix 13.6 of this PWS.

1.3.3 Preventive Maintenance Inspections (PMIs).

Contractor shall perform PMIs as required on all switching and power systems IAW manufacturer recommended or established schedules and/or manuals. Contractor shall elevate any problems and identify any trends to the COR in writing.

1.3.3.1 PMI Switch Power Test.

Contractor shall perform scheduled PMI tests of the telephone switch backup power system.

PMIs shall test and document the power systems identified in Appendix 13.2. Each power system shall be tested IAW manufactures specifications.

1.3.3.2 PMI Spare Conductor Test.

Contractor shall perform a scheduled PMI test of the spare conductors. PMIs shall test and document at least two selected, out-of-service pair (one low and one high numbered pair) in each 25-pair group of every cable terminating in the DCO. These PMI tests are to be accomplished quarterly. Test results shall be documented and a copy provided to the COR.

1.3.3.3 PMI Manholes.

Contractor shall inspect at least five COR-accepted manholes per month. If the Contractor is working in a manhole that is not scheduled for a PMI in that month, Contractor must still correct any discrepancies before job is considered complete. This manhole will be counted in that month’s PMI schedule. Each manhole will be inspected for the following discrepancies and corrected.

1.3.3.3.1 All cables will be identified and tagged. At each splice, tags will be placed on each side of the splice identifying each cable. In manholes with pull through cables, each cable will be identified with a tag.

1.3.3.3.2 All cables will be racked to the manhole cable supports.

1.3.3.3.3 Update the CVC database indicating the correct GPS location for the manhole and record all descriptive information for splices, cables, ducts and other communication features in the manhole.

1.3.3.3.4 All vacant ducts will be sealed; ducts with cables installed will also be sealed.

1.3.3.3.5 All manholes will be cleaned of mud, water and any other debris.

1.3.3.4 PMI Terminals.

Contractor shall inspect at least five COR-accepted terminals per month. Each terminal will be inspected for the following discrepancies and corrected.

1.3.3.4.1 Verify the correct location (GPS if on the building exterior) of the building entry terminal, the terminal number and cable count.

1.3.3.4.2 Ensure cable is properly clamped to the wall and entrance conduits are sealed.

1.3.3.4.3 Ensure cable is tagged correctly.

1.3.3.4.4 Verify all working numbers in the facility and remove any unused numbers.

1.3.3.4.5 Remove all unused cross-connects in the building entry terminal.

1.3.3.4.6 Ensure that building entry terminal is properly secured to the wall and is clean.

1.3.3.5 PMI Distribution Pedestal Terminals.

Contractor shall inspect at least one COR-accepted Distribution Pedestal terminals per month.

Each terminal will be inspected for the following discrepancies and corrected:

1.3.3.5.1 Evaluate condition of Distribution Pedestal terminal.

1.3.3.5.2 Identify and tag each cable in the terminal if not already tagged.

1.3.3.5.3 Make sure that cable is grounded to a ground rod.

1.3.3.5.4 Inspect condition of cable and cable pairs for dry rot, exposed conductors and any damage by rodents.

1.3.3.5.5 Ensure that terminal is correctly installed.

1.3.3.5.6 Verify all working numbers and remove any unused.

1.3.3.5.7 Remove all unused cross-connects in the terminal.

1.3.3.5.8 Update the CVC database indicating the correct GPS (if on the building exterior) location of the distribution pedestal terminals and record all descriptive information for the distribution pedestal terminals.

1.3.4 System and Service Outages.

1.3.4.1 Contractor Availability.

Contractor shall respond in case of emergencies, outages, alerts and exercises, twenty four hours a day, 365 days a year. If contacted, Contractor or required personnel should report for duty and provide services as necessary until the emergency, alert, or exercise is completed. Normal business hours are 0730 – 1630, Monday – Friday.

1.3.4.2 Scheduled Outages.

Contractor shall identify and coordinate verbally with the COR the need for any scheduled service outages. Such outages shall be scheduled to minimize inconvenience to users, based upon Government user work schedules. The user must release all affected equipment and circuits prior to any service disruption. Notification shall include the reason for the interruption, duration, start and stop times, and the equipment, lines, and buildings affected.

1.3.4.3 Outage Restoration.

If multiple facilities, areas, primary trunks or cables are impacted, the COR will assign the category of the outage and establish the repair priority. Contractor shall respond on site and initiate repair actions within the specified time listed below from the time the COR advises the contractor of the problem. Contractor shall restore services in the priority order determined by the COR, and the Restoration Priority List (RPL) shall apply in the absence of the COR.

Contractor shall continue to work on repair actions until service is restored based on priority.

Contractor shall work closely with the COR on all service or system outages and verbally notify the COR upon restoration of service providing the time service was restored and a description of repair action. Contractor shall maintain an accurate and readable record of all scheduled interruptions and shall include the reason for the interruption, authorizations, action taken, equipment or lines affected, and dates/times of coordination and restoration. (See definitions in Appendix 13.3 and workload estimates in Appendix 13.1.) If an outage significantly affects a mission, the COR may designate the category of outage as the mission dictates. Contractor will be required to obtain an account for any electronic tools used in support of locally established processes (i.e. Remedy/CIPS) in order to process trouble tickets. Trouble tickets will be reported to the Communication Focal Point (CFP) who will obtain at a minimum, the following information: Customer Name, working customer contact number, bldg. number, and floor or room number, clear explanation of the problem they are experiencing. CFP will forward the Trouble Ticket to the contractor for processing. The contractor shall be required to close the ticket when it’s completed.

Any loss of call handling capability or network connectivity is further defined as follows:

1.3.4.3.1 Emergency Outage.

On-site response is required within two hours of notification. If an outage significantly affects a mission, the COR may declare the outage as Emergency. Emergency outages are classified as a loss of over 75% or more of total call handling capability of any communications system; loss of any Primary or Secondary Crash System or any portion thereof; failure of one or more circuits listed in the Base RPL; or loss of LAN connectivity affecting 100 or more users.

1.3.4.3.2 Priority Outage.

On-site response is required within six hours of notification. Priority outages are classified as a loss of over 25% or more of total call handling capability of any communications system; major alarm of any switching system identified in Appendix 13.2; loss of the Commanders Net or Land Mobile Radio (LMR) telephone/radio circuits; total loss of telephone service within a building;

or loss of LAN connectivity affecting 15-99users.

1.3.4.3.3 Routine Outage.

On-site response is required within twenty-four hours of notification. Routine outages are any other outages not included in the above categories.

1.3.4.4 Remote Monitoring (Response to NCC).

Contractor shall coordinate the details of any proposed Remote Monitoring method with base personnel and be documented in the Contractor’s Maintenance Support Plan. Remote monitoring shall not interfere with any government owned system. Remote monitoring of the switch system(s) shall not require assistance from base personnel. Notification of switch outages shall not be through a continuous direct line to the switching system for security reasons. Remote diagnostics modems must be user name and password protected. Contractor is responsible for all materials and equipment necessary to implement remote monitoring and shall take all actions to implement the plan and comply with telephone switching security standards.

1.3.4.5 Outage Cause Identification.

Contractor shall determine if a recorded problem or system failure is attributable to the switching system, BTS, or other causes. If the malfunction is determined to be due to other causes (outside the Contractor-maintained system/equipment), Contractor shall immediately notify the COR. If the cause of failure is determined at a later time to be related to the BTS, Contractor may be liable for the cost of any third party service calls or charges necessary to isolate and repair the problem.

1.3.5 Cable Location Staking and Marking.

Contractor shall provide location, staking, and marking services on BTS encased or direct buried conduits/cable when requested by the COR. Contractor shall mark up to 120,000 feet of cable and 200 GPS features (Manholes, Pedestals, DB Splices, etc.) per contract period and each option period (if exercised). Additional quantities of marking and staking services will be ordered via work order. Contractor shall locate and mark buried cable within one foot of the actual location at ten-foot intervals and at direction changes. The marking shall begin two feet from the point of entry into the work area and shall continue two feet past the point of exit from the work area. Contractor shall complete location, staking and marking within the specified time listed below from the time the COR advises Contractor of the requirement.

• Emergency: Within two hours IAW paragraph 1.3.4.1.

• Routine: Within five business days or according to Civil Engineering standard.

1.3.5.1 Collection of Communication Feature Data (CFD).

In addition to location staking and marking IAW paragraph 1.3.5, Contractor shall collect geospatial CFD using GPS and record CFD for the staked features in the CVC database when requested by the COR. Contractor shall collect and record CFD for up to 100,000 feet of cable and number of GPS features (Manholes, Pedestals, DB Splices, etc.) per base period and each option period (if exercised). Additional quantities of collecting geospatial CFD using GPS and recording CFD using CVC will be ordered via work order. Contractor shall locate features using GPS to the geospatial accuracy specified in Appendix 13.8 and record the GPS portion of the CFD in the CVC database within four duty days of collecting the data.

1.3.6 System Cross-Connect and Disconnect Services.

Contractor shall perform system cross-connect and disconnect services. Cross-connects and disconnects, which are required or incidental to the performance of systems maintenance actions, .7shall be included as part of the monthly service. Cross-connects and disconnect services, which are associated with installation per work orders or to establish new services, shall be ordered separately.

1.3.7 Voice Mail.

The Contractor shall provide complete O&M of the IX Voicemail solution and all peripheral equipment to include any and all security requirements. The Contractor shall ensure that all equipment or services installed, maintained or performed are conducted IAW the current JITC and Military or DoD specific OEM documentation, unless specified by the Government. The Government has final authority over the deployment and configurations of all voicemail supporting equipment and services. The Contractor shall inform the Government of any changes to the JITC configuration, IO tests or the DoDIN APL pertaining to the IX voicemail solution and peripherals.

The Contractor shall be responsible for O&M of the underlying VMWARE environment associated to the IX voicemail applications. The Contractor shall ensure full security compliance of the environment by applying and following all OEM patches, MUDG, STIGs, IO documentation and any controls required by the local IA office. The Government must provide proof of compliance at the time of award.

The Contractor shall be responsible for O&M of the underlying Windows Server OS environment associated to the IX voicemail applications. The Contractor shall ensure full security compliance of the environment by applying and following all OEM patches, MUDG, STIGs, IO documentation and any controls required by the local IA office. The Government must provide proof of compliance at the time of award.

The Contractor shall be required to keep the voicemail database updated, organized and accurate. The Contractor will be required to develop a standardized naming or labeling convention with the Government after contract award to be used in all configurations. The Contractor will ensure that all adds, move, changes or removals are accurately depicted in the voicemail database to ensure seamless turnover of the Governments systems. Under no circumstance should the voicemail database contain configurations or programming for excess or removed voicemail boxes, call trees, etc.

The Contractor shall be responsible for any moves, adds, changes, or disconnects associated to the IX voicemail suite. This may include but not limited to setting up and deleting voicemail boxes, password resets, call tree conceptions, changes or deletions, user intervention and education, etc. In the event additional software or hardware is needed to perform O&M of the system including licenses that cannot be leveraged via Government inventory or in place support contracts, the Contractor must notify the COR immediately.

1.3.8 Voice Protection System (VPS).

The routine maintenance of the VPS system is via MAJCOM NOSC. Contractor shall respond to any requests for local maintenance as directed by the COR.

1.3.9 Traffic Measurement and Analysis.

Contractor shall perform semi-annual traffic measurement and analysis within system capabilities and limitations and perform analysis and studies on the base switching system (see Appendix 13.5 and PWS Section 1.3.13.3). The information required by the contract must cover no less than a five-day period, (Monday-Friday).

1.3.10 Contractor Support Services.

1.3.10.1 Contractor Support for Government Engineering and Installation.

Upon direction of the COR, Contractor shall provide technical support to include an interchange of information on technical parameters and capabilities of the BTS; location and identification of building terminals and communication rooms; and verification of cable record information. These efforts include setting of equipment options to determine proper operational conditions;

restoration of service to existing equipment; establishment of service to new facilities; transfer from one system to another system; and support of hardware and software upgrades.

1.3.10.2 Contractor Interface and Support for other Vendors.

Contractor shall cooperate, share and exchange routine or available technical and system equipment interface information with other vendors. Contractor shall program telephones, PRI’s, etc. in support of systems interfacing with the telephone system, i.e. Voicemail, E911, CAIRS, TMS, T-Metrics, etc. as directed by the COR, CA or CO.

1.3.10.3 Design Review Meetings.

At the request of the COR, Contractor shall review program or project drawings and provide comments concerning communications requirements within five working days from receipt. The estimated quantity is five per month. Contractor shall participate in designated design review meetings as identified by the COR. The BTS manager shall attend up to five local vicinity meetings per month. Contractor shall attend contract review meetings to be held semi-annually at the base.

1.3.10.4 Workload/Status Meetings.

The BTS Manager shall attend local meetings with the COR(s), Communications Squadron

Plans Office, and/or CO to discuss status of current and future work orders, trouble tickets, outages, PMIs, or any other work/event that may impact contractual performance as required. The contractor shall provide a list of work orders, trouble tickets, etc. at the meeting for reconciliation and discussion with the COR(s), Contracting Officer, or other personnel (approved by the CORs or CO).

1.3.11 Rough Order Magnitude (ROM)/Estimates/Technical Solutions.

1.3.11.1 Contractor shall perform ROM/desktop/budgetary estimates as directed by the COR.

The ROM shall be prepared as follows: provide a proposed technical solution using existing Contract Line Item Numbers (CLINS)/product identifications (PIDS). The Contractor shall provide the draft within two working days from receipt which may be extended up to 10 additional work days from the COR at the time the ROM or estimate is requested. Extensions shall be clearly annotated on the request and initialed by both the Contractor and COR. Upon acceptance of the draft technical solution by the COR, a work order will be issued if funding is acquired.

1.3.11.2 Technical Solution.

1.3.11.2.1 Contractor shall perform detailed technical solutions as directed by the COR and provide to the COR using the standard work order format, listing those efforts/items and cost required to complete the job. See paragraph 1.4. for implementation procedures.

1.3.11.2.2 Upon receipt of a requirement and written request from the COR, Contractor shall review the requirement and provide a detailed technical solution using existing Contract Line Item Numbers (CLINS)/product identifications (PIDS). This effort shall include contacting the customer for a site visit to the location of the work if necessary.

1.3.11.2.3 Response to emergency surveys will be within two hours and completion will be within four hours. Priority survey will be completed within two duty days of request. Routine surveys will be completed within five duty days of request unless a longer period is agreed to by the COR and documented on the requirement. (See Appendix 13.1 for workload estimates).

Emergency surveys may be tasked by COR verbally. See paragraph 1.4. for implementation procedures.

1.3.12 BTS Work Center Records.

Contractor shall establish and maintain BTS work center records. All BTS records and documents created and maintained by the Contractor are Government property. All records and record-generating software will remain at the location designated by the COR and shall be available for review by the Communications Systems Officer, CO, COR, and other authorized personnel. Contractor shall update work center records within one duty day after completion of the associated task(s) and preserved for the term of the contract. The Government may require electronic format. Contractor shall make provisions for Government access to databases, servers, media or other documentation. Contractor shall update all errors found or identified during review of the work center records. Contractor shall create and/or maintain accurate, complete, and readable work center records as listed below:

1.3.12.1 Maintenance Support Plan (MSP).

The MSP shall enable the tracking of preventive maintenance actions on contractor-maintained equipment. Electronic copies shall be provided to the COR and CA (Block 9 of the SF Form 1449). When changes occur that affect the plan, revisions shall be submitted within 10 work days after the effective change (e.g. modification adding equipment) unless otherwise requested by the CO (e.g. with the proposal to add new equipment to maintenance). The Government will review and approve, or provide the contractor with required corrections, within 30 calendar days.

Changes may be implemented only after CO approval. The MSP shall, at a minimum, contain a schedule of PMIs due on each piece of equipment being maintained (Appendix 13.2) for the life of the contract IAW equipment manufacturer’s recommendations; specific maintenance tasks to be performed on the system; malfunctions or problems annotated on record with equipment data, serial number, etc.; and the corrective action taken by the Contractor.

1.3.12.2 PMI Inspection Records and Malfunction Report.

PMI records shall, at a minimum, contain the initials of person’s name performing the inspection; date and time inspection was performed; short description of inspection conducted;

repair action required; and corrective action(s) taken.

1.3.12.3 Maintenance/Repair Logs.

Contractor shall establish and maintain an accurate and legible BTS Maintenance/Repair Log (integrated into locally established maintenance processes) to show all maintenance and inspections (other than PMIs) performed during each 24-hour period as a result of trouble report actions or scheduled/unscheduled outages. The log shall be initialed by the BTS Manager and shall include, as a minimum, initials of the first and last name of the person reporting a discrepancy; time a discrepancy was reported (start time); short description of the discrepancy (reason for scheduled/unscheduled outages); identification of the customer/user by station line affected (telephone number or circuit number); location of equipment (building and room number, etc.); time a technician(s) was dispatched; time discrepancy was corrected (stop time) and annotation of log with the person or office contacted to provide status information; corrective action(s) taken.; and restoration priority (emergency, priority, or routine outage(s)). See Paragraph 1.3.4.3. for implementation guidance.

1.3.12.4 Manhole, Handhole, and Building Terminal Inspections.

Contractor shall maintain manhole, handhole, distribution pedestal terminal, and building terminal inspection records as outlined in 1.3.3.3 - 1.3.3.5. The Contractor shall update the CVC database with pertinent CFD information gathered during the inspections. The record shall be available for inspection and analysis by the Government to facilitate repair actions. If electronic documentation is implemented, Government access shall be granted to vendor databases, storage media, or files.

1.3.12.5 Cable Installation/Repair Test Results.

Contractor shall furnish a cable installation/repair test results report to the COR within five work days after the installation or repair of an outside plant cable. The report shall be provided by electronic transmission. The data shall be capable of being printed on 81/2 inch standard-size paper. Identify all acronyms, codes, abbreviations, signs and symbols and retain same format for all submissions. Graphic and pictorial may be used to illustrate. The report shall, at a minimum, contain the purpose of test/inspection; complete identification of item tested/inspected and test equipment used; complete description of the physical set-up (e.g., item, facility, and equipment used); complete description of procedures used; copy of results/analysis;

actual recorded data (e.g., instrument readings) (if extensive, provide as an appendix);

conclusions/recommendations; and authentication/authentication of results and acceptability.

1.3.12.6 Communications and Information Systems Installation Record (CSIR).

Contractor shall create, update, and post changes to drawings, plant records or documents using Government provided forms, software and web browser applications. Contractor shall load, edit, update and maintain CSIR information in the CVC database IAW AFI 33-101. Contractor shall transfer to the CVC database all pertinent CFD information from administrative and maintenance CSIR, Legacy CSIRs, work orders, inspection reports, as-built and as-installed marked-up drawings, and GPS services, that are created as a result of the Contractor’s operations. The Contractor shall update the CVC database with information from as-built drawings or other pertinent documents or electronic data pertaining to work done by third parties (organic or contractor) when tasked through the work order process. A separate pre- priced SLIN/PID shall be use for conversion of third party as-built drawings, document, or electronic data information.