Atch 1 BTS_PWS_07Dec21_signed.pdf

Attachment 1 Page 1 of 123

PERFORMANCE BASED WORK STATEMENT (PWS)

FOR

OPERATION AND MAINTENANCE (O&M) SERVICES

BASE TELECOMMUNICATIONS SYSTEM (BTS) Services

AT

HOLLOMAN AIR FORCE BASE, NEW MEXICO

CAMERON D. MCMULLEN TSgt, USAF Date Contracting Officer's Representative (COR) 49th Communications Squadron

JOSEPH C. MURPHY, Lt Col, USAF Date COR Supervisor 49th Communications Squadron

PATTI J. REN, Civ DAF Date Quality Assurance Program Coordinator (QAPC) 49th Contracting Squadron

APPROVED BY:

SALLY D. ROBERTS, Civ, DAF Date Contracting Officer (CO) 49th Contracting Squadron

Sol. # FA480122R0002

Attachment 1 Page 2 of 123

Table of Contents

1.0. DESCRIPTION OF SERVICES

1.1. Scope of Work

1.2. General Requirements

1.2.1. Hours of Operation

1.2.2. After Hours Notification

1.2.3. Continuation of Mission Essential Services

1.2.4. Accident/Incident Reporting and Investigation

1.2.5. Subcontractor Compliance

1.2.6. Base Civil Engineering Work Clearance Requests

1.2.7. Personnel

1.2.8. Key Personnel Listing

1.3. Operation and Maintenance (O&M) Requirements

1.3.1. Telephone Switch System O&M

1.3.2. ISP and OSP O&M

1.3.3. Enhanced-911 (E-911) System

1.3.4. Preventative Maintenance Inspections (PMIs)

1.3.5. System and Service Outages and Trouble Calls/Tickets

1.3.6. Alarm Notification

1.3.7. Cable Location, Staking, and Marking

1.3.8. System Cross-Connect and Disconnect Services

1.3.9. Fiber Optic Patching and Disconnect Services

1.3.10. Ethernet Patching & Disconnect Services

1.3.11. Call Accounting System (CAS)

1.3.12. Voice Protection System (VPS)

1.3.13. Traffic Measurement and Analysis

1.3.14. Contractor Support Services

1.3.15. Technical Solutions

1.3.16. Rough Order of Magnitude (ROM)

1.3.17. BTS Work Center Records

1.4. Work Orders

1.4.1. Work Order Procedures

1.4.2. Work Order Classifications

1.4.3. Required Information on Work Orders

1.4.4. Work Orders Subject to the Construction Wage Rate Requirements Statute

1.4.5. Submittal of Completed Work Orders

1.5. Special Project Requirements

1.6. Invoicing Instructions

1.6.1. Invoicing via PIEE/WAWF

1.6.2. Payment via GPC

1.6.3. Government Internal Instructions for GPC

1.7. Contractor Level I Antiterrorism Awareness Training (November 2019)

2.0. SERVICE SUMMARY (SS)

2.1. Inspection of Services

2.2. Non-Compliance

2.2.1. Memorandum For Record (MFR)

2.2.2. Contract Discrepancy Report (CDR)

3.0. GOVERNMENT-FURNISHED PROPERTY AND SERVICES

3.1. Air Force-Provided Spares\Contractor Logistic Support

3.2. Base Support

3.3. CVC Training

4.0. GENERAL INFORMATION

4.1. Contractor�s Quality Control Program

4.2. Security Requirements

Attachment 1 Page 3 of 123

4.2.1. Illegal Aliens

4.2.2. Foreign National Employees

4.2.3. Listing of Employees

4.2.4. In/Out Processing

4.2.5. Security Training

4.2.6. Pass and Identification Items

4.2.7. Retrieving Identification Media

4.2.8. Travel Restrictions

4.2.9. Traffic Laws

4.2.10. Weapons, Firearms, and Ammunition

4.2.11. For Official Use Only (FOUO)

4.2.12. Reporting Requirements

4.2.13. Physical Security

4.2.14. Investigative Standards

4.2.15. Information Technology/Information Systems (IT/IS) Access

4.2.16. Controlled/Restricted Areas

4.2.17. Photography

4.2.18. Key Control

4.2.20. Security Guidelines

4.2.21. National Agency Check with Inquiries (NACI)

4.3. Safety, Security, and Environmental Meeting

4.3.1. Environmental Concerns

4.4. Overtime

5.0. APPENDICES

Appendix 5.1 � Workload Estimates Appendix 5.2 � Items to be Maintained by the Contractor Appendix 5.3 � Glossary and Acronyms Appendix 5.4 � Voice Switching System (VSS) Sustainment Appendix 5.5 � Applicable Documents Appendix 5.6 � Instructions for Keeping CVC as-built records Appendix 5.7 � Global Positioning System Service Documents Appendix 5.8 � Equipment and Installation Performance Specification (EIPS) Appendix 5.9 � Operational Network Characteristics

Attachment 1 Page 4 of 123

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, unless specified in this contract as Government Furnished Property (GFP)/Government Furnished Equipment (GFE) and Government Furnished Material (GFM).

GFP is incidental in this requirement as defined in Federal Acquisition Regulation (FAR)

45.101. Work under this PWS will support the mission of 49th Communications Squadron at Holloman Air Force Base, New Mexico, by providing highly reliable wired telecommunications and networked voice, video and data services. The Contractor shall perform Operation and Maintenance (O&M) and other services required to ensure the Base Telecommunications System (BTS) is available 24 hours per day, seven (7) days per week. The BTS consists of the base telephone system switch, the outside plant (OSP) and inside plant (ISP) systems, network, transmission systems, and all associated equipment described in Appendix 5.2, which may include other systems (e.g., Voice over Internet Protocol (VoIP), etc.). The Contractor shall operate and maintain all BTS equipment and systems listed in Appendix 5.2 in accordance with (IAW) the Original Equipment Manufacturer (OEM) technical manuals and specifications, Department of Defense (DoD) and US Air Force (AF) policy and regulations, applicable federal, state, and local laws and regulations.

1.2. General Requirements.

1.2.1. Hours of Operation.

The Contractor shall perform the services required under this contract from 7:30 am � 4:30 pm, Monday through Friday except Government holidays.

1.2.2. After Hours Notification.

This contract does require the Contractor to respond to maintenance and work order after normal duty hours. The Contractor shall provide the Government with either an after duty phone number to recall personnel or a monthly standby roster providing name and phone number of standby personnel.

1.2.3. Continuation of Mission Essential Services.

IAW Defense Federal Acquisition Regulation Supplement (DFARS) 252.237-7023 policy, it is determined that O&M services in PWS paragraphs 1.3.2 and 1.3.4.3 are essential for Contractor performance during a crisis situation. In the event of a crisis, additional areas may be identified by the CO. The 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. Base exercises or actual ongoing base security events frequently interrupt missions. 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 BTS. Contractor shall submit its Mission-Essential Contractor Services Plan (MECSP) with proposal.

Attachment 1 Page 5 of 123

1.2.4. Accident/Incident Reporting and Investigation.

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

1.2.5. Subcontractor Compliance.

The Contractor shall be responsible for ensuring Subcontractors satisfy the requirements set forth in the contract. The Contractor shall include a provision in all subcontracts to require Sub-contractor compliance with terms and conditions of this contract.

1.2.6. Base Civil Engineering Work Clearance Requests.

The Contractor shall prepare and coordinate a Base Civil Engineering Work Clearance Request, AF Form 103, prior to any trenching or digging. The Contractor shall prepare and coordinate an AF Form 332, Base Civil Engineer Work Request, prior to any work requiring facility modification. 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, AF Occupational Safety and Health (OSH), any local procedures, and other provisions of this contract.

1.2.7. Personnel.

1.2.7.1. Contractor Responsibility. 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 OEM to maintain, install, and/or operate equipment listed in Appendix 5.2 and perform all contract support services covered by this contract. Technical support for equipment listed in Appendix

5.2 may require Tier I, II or III levels of troubleshooting support (ref. para 5.2.2 of Tier levels).

The Contractor shall ensure personnel also meet the criterion stated in its proposal for this requirement.

1.2.7.2. Contractor Employees. Contractor employees shall present a neat appearance and be easily recognized as contractor employees. The Contractor shall provide each employee with an identification badge that shall include the employee�s name, employee�s photograph, and contractor name. Identification shall be available prior to employment and shall be worn/attached to the outer garment above the waist at all times.

1.2.8. Key Personnel Listing.

The Contractor shall provide a key personnel listing, including contact information, to the CO and COR prior to commencing work. The Contractor shall update the listing when changes occur ensuring information is current and correct throughout the life of the contract. All personnel shall be proficient in understanding, reading, writing, and speaking the English language. The key personnel list shall list the employees� names, function they support, and whether they are supporting O&M or work orders, and what percentage of each support function the employee will perform.

Attachment 1 Page 6 of 123

1.3. Operation and Maintenance (O&M) Requirements.

Overall responsibility to properly operate and maintain the BTS shall rest with Contractor as described by the Maintenance Support Plan (MSP) (See PWS section 1.3.17.1 BTS Work Center Records) and the OEM�s recommended procedures. Appendix 5.2, Items to be maintained by Contractor, identifies GFM/GFE requirements. O&M actions include all actions taken by the Contractor to operate and maintain equipment and systems in a serviceable condition or to restore it to a serviceable condition to include purchasing of commercially available parts, inspection, periodic testing, adjustment, and repair. The effort may include the replacement of defective circuit packs and Customer Premise Equipment (CPE), preventive maintenance IAW applicable publications (OEM, Appendix 5.5, and otherwise specifically listed herein), and other routine work to optimize the life expectancy of the equipment and cable systems. Work orders will be accomplished IAW para 1.4. The Contractor shall not postpone or otherwise delay O&M efforts to accomplish work orders. The Contractor is responsible for completing both O&M and work orders simultaneously to ensure contractual timelines are met for both.

1.3.1. Telephone Switch System O&M.

The Contractor shall operate and maintain the system(s) identified in Appendix 5.2. The Contractor must be Avaya qualified and certified to perform O&M on the switch. The Government will measure the acceptable standard performance level by a determination of the total systems availability (up time) and reliability rating during any given month. All equipment or services installed by the Contractor shall automatically become part of the O&M services.

This includes, but is not limited to: management; administration and maintenance; performing software functions (i.e., number reclamation) and translations for any trunk or circuit of configurations required by on-base systems or users; data administration; trouble assistance; and records administration. The Contractor shall also include VoIP operations as part of the BTS.

The O&M contractor shall be responsible for database administration of VoIP phones, software changes to include upgrades/patches, and troubleshooting. Demarcation of VoIP maintenance shall not extend beyond the end instrument and Ethernet ports of the switching equipment identified as the host and remote switches in Appendix 5.2.3.2 through 5.2.3.5.

Note: Contractor will not be responsible for base network equipment (i.e., Information Transport Node (ITNs), LAN switches, etc.).

1.3.2. ISP and OSP O&M.

The Contractor shall maintain ISP and OSP cable and equipment as identified in Appendix 5.2 and IAW applicable documents listed in Appendix 5.5 of this PWS.

1.3.3. Enhanced-911 (E-911) System.

Contractor shall perform daily updates, or as phone number changes occur, by adding telephone number, building number, and room number for new and existing entries to the Government provided E-911 database. The Contractor shall manually enter the data into Cable Assignment Information Retrieval System (CAIRS) or any substitute record system as directed by a COR upon completion of individual work. The Contractor shall notify the COR by the last day of each month with all changes made in the E-911 database.

Note: The Contractor will not be responsible for base E-911 equipment (i.e., consoles, servers, telephones, etc.).

Attachment 1 Page 7 of 123

1.3.4. Preventative Maintenance Inspections (PMIs).

The Contractor shall perform PMIs as required on all systems covered by this contract IAW OEM recommended or established schedules and/or manuals. Contractor shall elevate any problems and identify any trends to the CO and COR in writing within one (1) workday.

Contractor shall correct deficiencies IAW the subparagraphs below.

1.3.4.1. Switch Power Test. The Contractor shall perform scheduled PMI tests of the telephone switch backup power system. PMIs shall test and document the power systems identified in Appendix 5.2. Each power system shall be tested IAW OEM specifications. Test results shall be documented IAW PWS para 1.3.17.2.

1.3.4.2. Spare Conductor Test. The Contractor shall perform a scheduled PMI test of all spare conductors. PMIs shall test and document at least two (2) selected, out of service pair (one low and one high numbered pair) in each 25-pair group of every cable terminating in the DCO-Bldg 221, Bldg 878 and Bldg 1081. These PMI tests are to be accomplished quarterly. Test results shall be documented and available for COR review. Contractor shall update CAIRS to indicate unusable cable pairs.

1.3.4.3. Manholes Handholes and/or Pull Boxes. The Contractor shall inspect five (5) COR approved manholes, handholes and/or pull boxes per month under the O&M portion of this contract. Additional inspections (over five (5) each) shall be accomplished as a work order IAW PWS para 1.4. If the Contractor is working in a manhole, handholes and/or pull boxes not scheduled for a PMI in that month, the Contractor must correct any discrepancies before the job is considered complete. This manhole will not be counted in that month�s PMI schedule. The Contractor shall inspect each manhole/handhole for the following discrepancies and correct as required:

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.

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

3. All ducts (vacant or occupied) will be sealed.

4. All manholes or handholes will be cleaned of mud, water and any other debris.

5. Update the Cyberspace Infrastructure Planning System (CIPS) Visualization Component

(CVC) database for the manhole/handhole inspected and record all descriptive information for splices, cables, ducts and other communication features in the manhole/handhole to include third party installations (if not already documented).

6. All splice closures will be bonded and grounded as required.

1.3.4.4. Terminals. The Contractor shall inspect five (5) COR approved terminals per month.

Additional inspections over five (5) each shall be accomplished as a work order IAW PWS para

1.4. The Contractor shall inspect each terminal for the following discrepancies and correct as required:

1. Verify the correct location, number and cable count.

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

3. Ensure cable is tagged correctly.

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

Attachment 1 Page 8 of 123

5. Remove all unused cross-connects, including those outside the DCO.

6. Ensure terminal is properly secured to the wall and is clean.

7. Update Telecommunication Management System (TMS).

8. Update the CVC/CAIRS database with descriptive information.

1.3.4.5. Distribution Pedestal Terminals. The Contractor shall inspect five (5) COR approved Distribution Pedestal terminals per month. Additional inspections over five (5) each shall be accomplished as a work order IAW PWS para 1.4. The Contractor shall inspect each terminal for the following discrepancies and correct as required:

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

2. Ensure cable is grounded to a ground rod; notify COR immediately if ground rod is not available to complete maintenance action.

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

4. Ensure terminal is correctly installed.

5. Verify all working numbers and remove any unused.

6. Remove all unused cross-connects.

7. Update the CVC/CAIRS database with descriptive information.

1.3.4.6. Fiber Optic Distribution Panels. The Contractor shall inspect ten (10) COR approved Fiber Optic Distribution Panels (FODP) per month. Additional inspections over ten (10) each shall be accomplished as a work order IAW PWS para 1.4. The Contractor shall inspect each FODP for the following discrepancies and correct as required:

1. Identify and label each cable entering in the FODP if not already labeled.

2. Ensure cable is properly grounded; notify COR immediately if ground point is not available to complete maintenance action.

3. Inspect condition of cable, splice trays, and individual buffered strands for damage.

4. Ensure panel is correctly installed and labeled.

5. Verify all working circuits.

6. Remove all unused fiber patches.

7. Clean fiber connector end faces in panel bulkheads and replace dust cap.

8. Update the CVC/CAIRS database with descriptive information.

1.3.4.7. Ethernet Patch Panels. The Contractor shall inspect ten (10) COR approved Ethernet Patch Panels per month. Additional inspections over ten (10) each shall be accomplished as a work order IAW PWS para 1.4. The Contractor shall inspect each panel for the following discrepancies and correct as required:

1. Ensure panel is correctly installed and labeled.

2. Ensure adequate cable management has been installed.

3. Verify all working circuits.

4. Remove all unused patch cables.

1.3.4.8. Cable Analysis. The Contractor shall review TMS records quarterly and perform cable analysis. The Contractor shall determine the number of bad pair(s) in each cable and report the

Attachment 1 Page 9 of 123 percentage in each cable to COR. The Contractor shall also determine the cable fill rates and report to COR. The CVC will be updated as necessary to record accurate cable information.

1.3.4.9 Network Switch Power Test. The Contractor shall perform scheduled PMI tests of the network switch backup power system. PMIs shall test and document the power systems identified in Appendix 5.2. Each power system shall be tested IAW OEM specifications. Test results shall be documented IAW PWS para 1.3.17.2.

1.3.5. System and Service Outages and Trouble Calls/Tickets.

1.3.5.1. Contractor Availability. The Government shall be able to contact Contractor personnel 100 percent of the time. The Contractor shall respond in case of emergencies, outages, alerts and exercises, 24 hours a day, seven (7) days per week. If contacted, the Contractor shall report for duty and provide services as necessary until the emergency, alert, or exercise is completed.

1.3.5.2. Scheduled Outages. The Contractor shall identify, coordinate, and schedule service outages with the COR. The Contractor shall schedule such outages to minimize inconvenience to users based upon Government user work schedules. This may require working outside of normal duty hours. The user must release all affected equipment and circuits prior to any service disruption. The Contractor shall follow established local procedures for scheduling and implementing scheduled outages. Notification will be in writing and shall include the reason for the interruption, start and stop times, duration and the equipment, lines, and buildings affected.

1.3.5.3. Restoration/Completion of Outages, Trouble Calls/Tickets. The COR will assign the category of the outage/trouble and establish the repair priority if an outage occurs. The Contractor shall respond on-site and initiate repair actions within the specified time listed in the below sub-paragraphs from the time the COR advises the Contractor of the problem. However, exceptions to time limits may be allowed, with the written approval of the COR or CO, with appropriate justification. The Contractor shall restore services in the priority order determined by the COR. The Restoration Priority List (RPL) shall apply in the absence of the COR. The Contractor shall continue to work on repair actions until service is restored based on priority.

The Contractor shall work closely with the COR on all service or system outages, trouble calls/tickets and notify the COR in writing upon restoration of service providing the time service was restored and a description of repair action. The Contractor shall coordinate with base Network Control Center (NCC) to restore any Internet Protocol (IP) phone set outages. The Contractor shall log the outage IAW the guidance in PWS para 1.3.17 (BTS Work Center Records). Outage/trouble call categories are further defined as:

1.3.5.3.1. Emergency. The Contractor shall respond on-site within one (1) hour, provide a fix action in writing within one (1) hour, and restore service within 12 hours of approved written fix or as approved by the COR, depending on the complexity of the requirement. Expedition of parts and/or labor is required at no additional charge to the Government. If an outage/trouble significantly affects a mission, the COR may declare the outage/trouble as an emergency.

Emergency outages/troubles are classified as any of the following:

1. Loss of over 75 percent or more of total call handling capability of any communications system

Attachment 1 Page 10 of 123

2. Loss of any secondary crash system or any portion thereof

3. Failure of one or more circuits listed in the base RPL

4. Loss of LAN connectivity affecting 100 or more users

5. Affects security or emergency type operations, including Emergency Operations Center

(EOC) as well as those affecting safety

6. Affect specifically identified events and/or exercises

1.3.5.3.2. Priority. The Contractor shall respond on-site within four (4) hours, provide fix action in writing within one (1) hour of arrival and restore service soon as possible, but shall not exceed three (3) work days. Expedition of parts or labor may be required at no additional charge to the Government. Priority outages are classified as:

1. Loss of over 25 percent or more of total call handling capability of any communications system

2. Major alarm of any switching system identified in Appendix 5.2

3. Loss of the Commanders Net or Land Mobile Radio (LMR) telephone/radio circuits

4. Total loss of telephone service within a building IAW RPL or COR guidance

5. Loss of LAN connectivity affecting 15-99 users

1.3.5.3.3. Routine. The Contractor shall respond on-site within 24 hours and restore service as soon as practicable but not to exceed five (5) work days. Expedition of parts and/or labor is not required. Routine outages/troubles are any other outage(s) not included in the above categories.

1.3.5.3.4. Outage/Trouble Cause Identification. The Contractor shall determine if a recorded problem or system failure is attributable to the BTS or other causes. The Contractor shall immediately notify the COR if the malfunction is determined to be due to other causes (outside the Contractor-maintained system/equipment). The Contractor may be liable for the cost of any third party service calls or charges necessary to isolate and repair the problem if it is later determined that the cause of failure is related to the BTS or failure of proper O&M of the system.

1.3.6. Alarm Notification.

The Contractor shall comply with the details of its alarm notification method as documented in the Contractor�s MSP and its proposal. Alarm notification shall not interfere with any Government-owned system. Alarm notification 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. Contractor is responsible for all materials and equipment necessary to implement alarm notification and shall take all actions to implement the MSP.

1.3.7. Cable Location, Staking, and Marking.

The Contractor shall locate, stake, and mark up to 75,000 feet of encased or direct buried conduits/cable per base period and each option period (if exercised) when requested by the COR.

Marking shall be within three (3) feet of the actual location at ten (10)-foot intervals and at direction changes. The marking shall begin two (2) feet from the point of entry into the work area and shall continue two (2) 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 the Contractor of the requirement unless additional time is permitted by the COR.

The Contractor shall document time extensions in writing, which includes the signatures of the

Attachment 1 Page 11 of 123

COR and the BTS Manager. Communication Feature Data (CFD) collection shall be accomplished via work order. See Appendix 5.7, Global Positioning System Service Documents and Appendix 5.8, Equipment and Installation Performance Specification (EIPS) when directed to collect CFD data by the COR. The Contractor shall comply with the following timelines for location, staking, and marking:

1.3.7.1. Emergency: Within two (2) hours of notification.

1.3.7.2. Priority: Within six (6) hours of notification.

1.3.7.3. Routine: Within twenty-four (24) hours of notification.

1.3.8. System Cross-Connect and Disconnect Services.

The Contractor shall perform system cross-connect and disconnect services. All cross-connects and disconnects, which are required or incidental to the performance of O&M actions (including those outside of the DCO), shall be included as part of the O&M service.

1.3.9. Fiber Optic Patching and Disconnect Services.

The Contractor shall perform fiber patching and disconnect services. All patches and disconnects, which are required or incidental to the performance of O&M actions (including those outside of the Fiber Expansion Room), shall be included as part of the O&M service. Final connections from the Fiber Optic Distribution Panel to the Equipment will be performed by the 49 CS. Patch cables shall be labeled with the circuit ID.

1.3.10. Ethernet Patching and Disconnect Services.

The Contractor shall perform Ethernet patching and disconnect services. All patches and disconnects, which are required or incidental to the performance of O&M actions (including those outside of the NCC, Building 202), shall be included as part of the O&M service.

1.3.11. Call Accounting System (CAS).

The Contractor shall operate and maintain the CAS to ensure data filled from base switch. This includes storage and output of records and formatting of the switching system. The Contractor is not responsible for input, manipulation, or analysis of data. The Contractor�s responsibility for any billing CAS will be limited to the same functions.

1.3.12. Voice Protection System (VPS).

The routine maintenance of the VPS system is via Major Command (MAJCOM) Communication Control Center (MCCC). The Contractor shall respond to any requests for local maintenance as directed by the COR.

1.3.13. Traffic Measurement and Analysis.

The COR may request up to six (6) traffic measurements and analysis per switch a year. The Contractor shall perform traffic measurement and analysis within system capabilities and limitations and perform analysis and studies on the base switching system when requested by the COR. The information required by the contract must cover no less than a five (5) day period, (Monday-Friday, excluding holidays). The Government may also request measurement and analysis reports for a particular line or group of lines.

Attachment 1 Page 12 of 123

1.3.14. Contractor Support Services.

The Contractor shall comply with FAR 9.5 and DFARS 209.5, Organizational and Consultant Conflicts of Interest, IAW support services.

1.3.14.1. Contractor Support for Government Engineering and Installation. The 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 as directed by the COR or CO. These efforts include setting of equipment options to determine proper operational conditions; restoration of service to existing equipment; establishment of service to new facilities; establishment of service for existing facilities under renovation; transfer from one system to another system; and support of hardware and software upgrades.

1.3.14.2. Contractor Interface and Support for other Vendors. The Contractor shall cooperate, share and exchange routine or available technical and system equipment interface information with other vendors as directed by the COR or CO.

1.3.14.3. Workload/Status Meetings. The BTS Manager shall attend up to five (5) local meetings per month with the COR(s) and Communications Squadron Plans Office to discuss status of current and future work orders, trouble tickets, outages, PMIs, or any other work/event that may impact contractual performance. The Contractor shall provide a list of work orders, trouble tickets, etc., at the meeting for reconciliation and discussion with the COR(s) or other personnel (approved by the CORs and CO).

1.3.14.4. Design Review Meetings. The Contractor shall review program or project drawings and provide comments concerning communications requirements within five (5) working days from receipt when requested by the COR. The Contractor shall participate in designated design review meetings identified by the COR. The BTS Manager (Contractor) shall attend up to four

(4) design review meetings per month.

1.3.15. Technical Solutions.

The Contractor shall perform detailed technical solutions for work intended to be performed under this contract upon receipt of written request from the COR. The technical solution includes a listing of those efforts/items required to complete the job using existing Contract Line Item Numbers (CLINs)/product identifications (PIDs) and shall be provided to the COR using the work order format specified in PWS para 1.4.3. The Contractor shall provide the proposed solution to the COR within five (5) working days for ISP and ten (10) working days for OSP from receipt of requirement unless a longer period is agreed to by the COR and documented on the requirement.

1.3.16. Rough Order of Magnitude (ROM).

The Contractor shall submit a ROM for work intended to be performed under this contract upon receipt of written request from the COR. The Contractor shall use existing CLINs/PIDs to calculate a �not to exceed� cost. The ROM shall be submitted to the COR on company letter head stationary. The Contractor shall provide the proposed solution to the COR within five (5) working days for ISP and ten (10) working days for OSP from receipt of requirement unless a longer period is agreed to by the COR and documented on the requirement.

Attachment 1 Page 13 of 123

1.3.17. BTS Work Center Records.

The Contractor shall establish and maintain BTS work center records. The Contractor shall update work center records within two (2) duty days after completion of the associated task(s) unless specified differently within this section. All BTS records and documents established and maintained by the Contractor are Government property and shall remain at the site and be turned over to the COR for disposition upon contract completion. Failure on the part of the Contractor to provide required records may result in the Government withholding of final payment until all records are recovered or a reduction in final payment for records lost or misplaced. The Government requires electronic maintenance and storage of records unless otherwise specified herein. The Contractor shall identify all acronyms, codes, abbreviations, signs and symbols used in each record. The Contractor shall use the same format for initial and all subsequent submissions of the same record unless otherwise approved by the CO. All records shall be readily available for review by the COR and CA, and other personnel (authorized in writing by the CO). The Contractor shall update all errors found or identified during review of the work center records. Contractor shall develop, update and/or maintain accurate, complete, and readable work center records as listed below:

1.3.17.1. Maintenance Support Plan (MSP) Record. The MSP shall enable the scheduling and tracking of preventive maintenance actions on Contractor-maintained equipment. This record shall be available within 30 calendar days after period of performance begins. When changes occur that affect the plan, revisions shall be submitted within ten (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 the revisions, or provide the Contractor with required corrections. Changes may be implemented only after CO approval. At a minimum, the MSP shall contain: a schedule of PMIs due on each piece of equipment being maintained (Appendix 5.2) for the life of the contract IAW equipment manufacturer�s recommendations; alarm notification procedures; and specific maintenance tasks to be performed on each system.

1.3.17.2. PMI Inspection Records and Malfunction Record. PMI records shall, at a minimum, contain: the date and time inspection was performed; a short description of inspection conducted; malfunctions or problems annotated on record with equipment data, serial number, etc.; the corrective action taken by the Contractor and the initials of the technician performing the inspection.

1.3.17.3. Maintenance/Repair Log Record. The Contractor shall establish and maintain an accurate and legible BTS Maintenance/Repair Log (e.g., maintenance actions, trouble tickets) 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 utilizing the local base trouble ticket monitoring system (i.e., BMC Remedy IT Service Management Suite Software, TMS etc.). The log shall be initialed by the BTS Manager and shall include, as a minimum, initials of the person reporting a discrepancy; time a discrepancy was reported (start time); short description of the discrepancy; 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; dates/times of coordination and restoration; 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, Attachment 1 Page 14 of 123 priority, or routine outage(s)). For scheduled outages, also include the Government authorization.

1.3.17.4. Manhole, Handhole, Pull Boxes, Building Terminal and Distribution Pedestal Terminals Inspection/Maintenance/ Repair Records. The Contractor shall maintain manhole, handhole, distribution pedestal terminal, and building terminal inspection records as defined in PWS para 1.3. 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. If other electronic documentation is implemented, the Contractor shall grant the Government access to those records.

1.3.17.5. Cable Installation/Repair Test Results Record. The Contractor shall develop and maintain a cable installation/repair test results record after the installation or repair of an OSP cable. Graphics and pictorials may be used to illustrate. The record 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 and recommendations; and authentication of results and acceptability. The Contractor shall update the CVC database with pertinent CFD information resulting from installation or repair.

1.3.17.6. Communications and Information Systems Installation Record (CSIR) and Cyberspace Infrastructure Planning System (CIPS).

1.3.17.6.1. New Developments for Maintaining CSIR Drawing Records. The AF is in the process of developing and implementing the CIPS/CVC. It changes the method of developing, maintaining, and editing information historically contained in installation drawings (CSIRs) from a Computer Aided Drawing and Design (CADD) process to a Geographic Information Systems (GIS) process that interfaces with the GeoBase initiative and provides an AF portal accessible, enterprise-wide database structure suitable for storing, visualizing, editing, and analyzing base-level communications and information systems infrastructure. At this time, CVC is not designed to store ISP information. Until such time as the CVC has standard provisions for recording inside plant information, ISP record drawings shall be maintained in the base�s existing drawing record systems or as directed by the CSIR Manager.

1.3.17.6.2. CVC Database Records. The Contractor shall produce, 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, for the OSP, in the CVC database. Contractor shall transfer to the CVC database all pertinent OSP CFD information from administrative and maintenance CSIR, Legacy CSIRs, work orders, inspection records, as-built and as-installed marked-up drawings, and GPS services produced as a result of the Contractor�s operations. The Contractor shall update the CVC database with OSP 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 CLIN/PID (Schedule B � CLIN X007 and GPS-CVC PIDs (8000-8003, 8100, and 8151-8153) on the Purchase, Installation, Relocation, Removal and Miscellaneous (PIRRM) Pricing Schedule shall be used for conversion of third party as-built drawings, document, or electronic data information. Contractor is responsible for verifying Contractor

Attachment 1 Page 15 of 123 entered information, accuracy and completeness. Contractor will use the CVC Viewer/Editor to update the CVC by opening and utilizing Live Direct Edit Sessions. During the edit session the Contractor will update CVC with as-built information or with information transcribed from shape files created or produced IAW Appendix 5.7 (paragraph 5.7.5 and Table A). When the update is completed, the Contractor will close the session and notify the CSIR Manager the session edit is ready to be approved. The CSIR Manager will review the Contractor�s edit session and Quality Control (QC) approve or reject each Contractor�s Live Direct Session Edit by inspecting each feature added or modified during the Live Direct Edit Session. The CSIR Manager will notify the Contractor of each feature that was rejected during the quality control approval process in order for the Contractor to take corrective action.

1.3.17.6.3. Inside Plant Drawing Records. ISP Drawing Records are not being currently maintained in CVC at this time. However, this paragraph is provided as reference only as it is expected that during the life of the contract it may be added via negotiated modification.

Note: As of February 2020, still a work in progress.

1.3.17.6.4. CIPS Account Records. The Contractor shall have an account in order to use CVC.

The Contractor shall apply for a new account by visiting the CIPS website at https:// cipsaf.tinker.af.mil/cips5, selecting Create New Account and providing the required information.

1.3.17.7. Global Positioning System (GPS) Service Data Records. The Contractor shall collect, update and maintain the CFD and use the data to update the location and attributes of communication features in the CVC database IAW para 1.3.17.6 and Appendix 5.7 (for any GPS requirement).

1.3.17.8. Switching System and ISP & OSP Equipment Operational Records. The Contractor shall retain records on-site and make available for COR or CO/CA review at any time.

1.3.17.9. CLIN/SLIN/PID Utilization Record. The Contractor shall produce and maintain an electronic record of the CLINs/SLINs/PIDs, ordered under the contract. The record shall include: the CLIN, SLIN, or PID number; descriptions; and quantities of each item. The record shall exclude price information. Contractor shall update this record within two (2) days of work order completion.

1.3.17.10. AF Logistics Support Spares Records (Inventory). The Contractor shall maintain and update the AF logistics support spares records in the on-site work center. The COR will provide the initial inventory to the Contractor for maintenance. Records include spares inventory list and spares replacement log. Spares inventory list shall include, as a minimum, Product Engineering Code (PEC), serial number, description, quantity, and vendor. Spares replacement log shall include, as a minimum, name of calling and called personnel, time, requesting description, Material Return Authorization (MRA) number, equipment item�s PEC and serial number, shipping date, and material return date.

1.3.17.11. Contractor-Furnished Hazardous Material Records. The Contractor shall develop this record to document bringing or using hazardous material on Government facilities.

Contractor shall develop this record not later than 30 calendar days after contract award and develop and maintain electronic updates to records quarterly thereafter. If no hazardous material

Attachment 1 Page 16 of 123 is used in performance of the contract during the quarterly period, the Contractor shall indicate �none� on the applicable quarterly record. The record shall consist of the following:

Section 1, General Information. This section shall contain: Contract number;

contract performance period; Contractor's name; date of record; name and phone number of on-base Contractor point of contact; emergency phone number; and address or physical location of the Contractor�s on-base field office.

Section 2, Product Information. This section shall contain: product nomenclature;

product trade name; product part number; manufacturer�s name and address; physical location(s) of on-base usage and storage; description of how product is used;

justification for use.

Section 3, Usage/Storage Amount. This section shall contain: unit of measure (e.g., gallons, quarts, pints, fluid ounces, pounds, other (specify); amount brought on installation; amount used during reporting period; amount stored; amount removed; and signature of responsible Contractor.

1.3.17.12. Equipment Inventory Records (Appendix 5.2). The Contractor shall maintain a working copy (in an MS Excel® document) of Appendix 5.2, which will be provided by the Government at the pre-performance conference. Appendix 5.2 shall identify equipment installed, changed, or removed via contract modification or the work order process identified in para 1.4. The record shall include all assemblies of the equipment configuration, which would be logically disassembled from the total configuration for the purpose of packing and shipping.

The Contractor shall update the record when individual work orders are completed annotating changes as necessary (i.e. showing adds or deletions, dates, amounts, etc.) using MS Excel® software.

1.3.17.13. Telecommunications Management System (TMS) Record. The Contractor shall perform daily record updates using the TMS employed at the base. Some updates may require the Contractor to manually enter the data upon completion of individual work orders or record changes. Contractor shall also maintain cable pair assignment records using TMS.

1.3.17.14. Work Order Records, Including Warranty Records. The Contractor shall develop and maintain work order records. The Contractor shall update work center records within two

(2) business days after completion of the task(s) specified on individual work orders and notify COR in writing. All physical records of work orders shall be retained and be available locally (on base). Electronic storage of completed (accepted by the COR) work orders is acceptable and preferred. Paper copies of completed work orders may be destroyed by using a cross cut shredder to prevent unauthorized disclosure after electronic storage is complete.

1.3.17.15. Traffic Measurement Records. The switch-generated record shall be used to satisfy this requirement as needed. The record shall contain an analysis of traffic measurements including a trunk traffic summary and individual analysis of each trunk group. The printed record shall be provided to the COR on an as-needed basis, not more than quarterly. The Government may also request measurement and analysis records for a particular line or group of lines. This selective record shall be maintained on site and made available to the COR within two (2) work days from occurrence of the traffic measurement analysis.

Attachment 1 Page 17 of 123

1.3.17.16. System Capacity Records. The Contractor shall maintain system capacity records quarterly and be available upon request by the COR. Semi-annual system capacity records include OSP cables and building records. Records shall include each cable and terminated cable count, type of cable (bad and spare), and number of conductors used. Quarterly system capacity records shall be produced for the host switch and remotes. The records shall include total line ports, line ports in use, line port type (analog/digital/Integrated Service Digital Network (ISDN), etc.) total used, and DS-1 digital trunk ports (total ports used and available).

1.3.17.17. System Security Audit Record. The Contractor shall develop and maintain an electronic weekly user event log that contains, at a minimum: the number of logins (remote and local); number of login attempts (remote and local); password changes; and/or any critical table modifications including new user accounts as allowed by the switch.

1.3.17.18. Quality Control Plan (QCP) Record. The Contractor shall develop and maintain a highly effective QCP for all services provided under this PWS within thirty (30) calendar days of contract award for CO acceptance. Once accepted, the QCP shall remain in effect during the term of the contract (including any option periods if exercised). The Contractor shall maintain the QCP; retain a copy on site; and ensure availability at all times to all members of their on-site staff, as well as the COR and CA. The Contractor�s QCP shall reflect depot-level Contractor logistic support, centralized maintenance and remote monitoring from the I-Network Operations Center (OSC) and refrain from relying on Government CORs as a means to ensure their own quality control. The Contractor shall notify the parties specified in this paragraph of any changes to the QCP at least ten (10) work days prior to implementation of those changes.

1.4. Work Orders.

The Contractor shall comply with the following work order requirements. Examples of work orders include, but are not limited to, equipment purchases, installations, removals, or relocations. Additionally, work orders may include installation or removal of cables/transmission media, as required for new requirements, and follow-on O&M of these equipment items/media. The COR will be notified of any installation found to be incomplete or not installed according to industry standards. The Contractor shall maintain the installed infrastructure and will not be held responsible for completing third party installations or bringing third party installations up to industry standard unless directed by issuance of a work order or contract modification. The EIPS provides detailed descriptions of the material and labor effort (e.g., material, labor, and incidentals for installation, removal, and/or relocation) required by the PIRRM pricing schedule and identified by PIDs.