attach_1_BTS_PWS_revised_24Aug2017.pdf

pg. 1

PERFORMANCE BASED WORK STATEMENT (PWS)

FOR

OPERATIONS AND MAINTENANCE SERVICES BASE TELECOMMUNICATIONS

SYSTEM (BTS)

AT

GRAND FORKS AIR FORCE BASE NORTH DAKOTA

pg. 2

TABLE OF CONTENTS

COVER PAGE ……………………………………….…… 1

TABLE OF CONTENTS ……………………………………….…… 2

1.0 SCOPE ……………………………………….…… 7

1.1 SCOPE OF WORK ……………………………………….…… 7

1.2 GENERAL REQUIREMENTS ……………………………………….…… 7

1.2.1 CONTINUATIONS OF MISSION

ESSENTIAL SERVICES DURING CRISIS ……………………………………….…… 7

1.2.1.1 EMERGENCY RIGHTS OF THE GOVT ……………………………………….…… 7

1.2.2 ACCIDENT/INCIDENT REPORTING

AND INVESTIGATION ……………………………………….…… 8

1.2.3 SUB-CONTRACT COMPLIANCE ……………………………………….…… 8

1.2.4 BASE CIVIL ENGINEERING WORK

CLEARANCE REQUESTS ……………………………………….…… 8

1.2.5 PERSONNEL ……………………………………….…… 8

1.2.6 KEY PERSONNEL LISTING ……………………………………….…… 8

1.2.7 CONTRACTOR IDENTIFICATION ……………………………………….…… 8

1.2.7.1 CONTRACTOR BADGES/IDs ……………………………………….…… 9

2.0 DESCRIPTION OF SERVICES ……………………………………….…… 9

2.1 OPERATE AND MAINTAIN

REQUIREMENTS ……………………………………….…… 9

2.1.1 TELEPHONE SWITCH SYSTEM O&M ……………………………………….…… 9

2.1.2 PEFORM ISP AND OSP O&M ……………………………………….…… 9

2.1.3 PERVENTITIVE MAINTENANCE

INSPECTIONS ……………………………………….…… 9

2.1.3.1 SWITCH POWER TEST ……………………………………….…… 10

2.1.3.2 SPARE CONDUCTOR TEST ……………………………………….…… 10

pg. 3

2.1.3.3 MANHOLE AND/OR HANDHOLE ……………………………………….…… 10

2.1.3.4 TERMINALS ……………………………………….…… 10

2.1.3.5 DISTRIBUTIONS PEDESTAL

TERMINALS ……………………………………….…… 11

2.1.3.6 CABLE ANALYSIS ……………………………………….…… 11

2.1.3.6.1 CABLE LOCATING ……………………………………….…… 11

2.1.4 SYSTEM AND SERVICE OUTAGES

AND TROUBLE CALL/TICKETS ……………………………………….…… 11

2.1.4.1 CONTRACTOR AVAILABILITY ……………………………………….…… 11

2.1.4.2 SCHEDULED OUTAGES ……………………………………….…… 11

2.1.4.3 RESTORATION/COMPLETION OF

OUTAGES, TROUBLE CALLS/TICKETS ……………………………………….…… 12

2.1.4.3.1 EMERGENCY ……………………………………….…… 12

2.1.4.3.2 PRIORITY ……………………………………….…… 12

2.1.4.3.3 ROUTINE ……………………………………….…… 13

2.1.4.3.4 OUTAGE.TROUBLE CAUSE

IDENTIFICATION ……………………………………….…… 13

2.1.5 ALARM NOTIFICATION ……………………………………….…… 13

2.1.6 CABLE LOCATION, STAKING AND

MARKING ……………………………………….…… 13

2.1.7 SYSTEM CROSS-CONNECT AND

DISCONNECT SERVICES ……………………………………….…… 14

2.1.8 CALL ACCOUNTING SYSTEM ……………………………………….…… 14

2.1.9 VOICEMAIL ……………………………………….…… 14

2.1.10 VOICE PROTECTION SYSTEM (VPS) ……………………………………….…… 14

2.1.11 AUTOMATIC CALL DISTRIBUTION

(ACD) SYSTEM ……………………………………….…… 14

2.1.12 TRAFFIC MEASUREMENT AND

ANALYSIS ……………………………………….…… 14

2.1.13 CONTRACTOR SUPPORT SERVICES ……………………………………….…… 15

pg. 4

2.1.14 CONTRACTOR SUPPORT FOR

GOVERNMENT E&I ……………………………………….…… 15

2.1.15 CONTRACTOR INTERFACE AND

SUPPORT FOR OTHER VENDORS ……………………………………….…… 15

2.1.16 WORKLOAD/STATUS MEETINGS ……………………………………….…… 15

2.1.17 DESIGN REVIEW MEETINGS ……………………………………….…… 15

2.1.18 TECHNICAL SOLUTIONS ……………………………………….…… 16

3.0 RECORDS ……………………………………….…… 16

3.1 BTS WORK CENTER RECORDS ……………………………………….…… 16

3.2 MAINTENANCE SUPPORT PLAN ……………………………………….…… 16

3.3 PMI INSPECTION RECORDS AND

MALFUNCTION RECORD ……………………………………….…… 17

3.4 MAINTENANCE/REPAIR LOGS ……………………………………….…… 17

3.5 MANHOLE, HANDHOLE, AND

BUILDING TERMINAL ……………………………………….…… 17

3.6 CABLE INSTALLATON/REPAIR TEST

RESULTS ……………………………………….…… 17

3.7 CSIR & NEW DEVELOPMENT ……………………………………….…… 17

3.7.1 DRAWINGS MAINTENACE ……………………………………….…… 18

3.7.2 INSIDE PLANT DRAWING RECORDS ……………………………………….…… 18

3.7.3 CIPS AND CVC ……………………………………….…… 18

3.7.4 AS BUILT DRAWINGS ……………………………………….…… 19

3.7.5 CSIR MANAGER COORDINATION ……………………………………….…… 19

3.8 SWITCHING AND ISP & OSP

EQUIPMENT OPERATIONS RECORDS ……………………………………….…… 19

3.9 CLIN/SLIN/PID UTILIZATION ……………………………………….…… 19

3.10 AF LOGISITICS SUPPORT SPARES

RECORDS ……………………………………….…… 19

3.11 CONTRACTOR-FURNISHED

HAZARDOUS MATERIAL ……………………………………….…… 20

pg. 5

3.12 EQUIPMENT INVENTORY ……………………………………….…… 20

3.13 TELECOMMUNICATIONS

MANAGEMENT SYSTEM (TMS) ……………………………………….…… 20

3.14 WORK ORDER RECORDS, INCLUDING

WARRENTY RECORDS ……………………………………….…… 20

3.15 SYSTEM CAPACITY RECORSD ……………………………………….…… 21

3.16 SYSTEM SECURITY AUDIT RECORDS ……………………………………….…… 21

3.17 QUALITY CONTROL PLAN ……………………………………….…… 21

4.0 GLOBAL POSITIONING SYSTEM

(GPS) ……………………………………….…… 21

4.1 (GPS) SERVICE DATA ……………………………………….…… 21

4.2. QUALITY CONTROL ……………………………………….…… 21

4.2 MAINTENANCE OF GPS SERVICE

DATA ……………………………………….…… 22

4.3 UPDATING CVC WITH GPS

COLLECTED CFD ……………………………………….…… 23

5.0 WORK ORDERS ……………………………………….…… 24

5.1 WORK ORDER REQUIREMENTS ……………………………………….…… 24

5.2 WORK ORDER PROCEDURES ……………………………………….…… 24

5.3 WORK ORDER CLIASSIFICATION ……………………………………….…… 25

5.4 REQUIRED INFORMATION ON WORK

ORDER ……………………………………….…… 25

5.5 WORK ORDERS SUBJECT TO

CONSTRUCTION WAGE RATE ……………………………………….…… 25

5.6 SUBMITTAL OF COMPLETED WORK

ORDERS ……………………………………….…… 26

6.0 SPECIAL PROJECTS ……………………………………….…… 26

6.1 SPECIAL PROJECTS REQUIREMENTS ……………………………………….…… 26

7.0 CONTRACTOR GENERAL

INFORMATION ……………………………………….…… 26

7.1 CONTRACTORS QUALITY CONTROL

PROGRAM ……………………………………….…… 27

pg. 6

7.2 SECURITY ……………………………………….…… 27

7.2.1 CERTIFICATION STANDARDS FOR

TELEPHONE SWITCH OPERATIONS ……………………………………….…… 27

7.3 FOR OFFICIAL USE ONLY MATERIAL

(FOUO) ……………………………………….…… 27

7.4 FREEDOM OF INFORMATION ACT ……………………………………….…… 27

7.5 SAFETY, SECURITY, AND

ENVIROMENTAL MEETING ……………………………………….…… 27

7.6 OVERTIME ……………………………………….…… 28

8.0 SERVICE DELIVERY SUMMARY

(SDS) ……………………………………….…… 28

8.1 INSPECTION OF SERVICES ……………………………………….…… 30

8.2 CONTRACTOR DISCREPANCY

REPORT ……………………………………….…… 30

9.0 GOVERNMENT FURNISHED

PROPERTY AND SERVICES ……………………………………….…… 30

9.1 AIR FORCE PROVIDED

SPARES/CONTRACTOR LOGISITCS ……………………………………….…… 30

9.2 BASE SUPPORT ……………………………………….…… 30

9.2.4 GOVERNMENT SUPPORT TO BE

FURNISHED UNDER CONTRACT ……………………………………….…… 31

9.3 CVC SUPPORT ……………………………………….…… 32

9.3.1 COMPUTERS ……………………………………….…… 32

9.3.2 CVC TRAINING ……………………………………….…… 32

APPENDIX 1 – WORKLOAD

ESTIMATES ……………………………………….…… 33

APPENDIX 2 – EQUIPMENT ITEMS ……………………………………….…… 34

APPENDIX 3 – GLOSSARY AND

ACRONYMS ……………………………………….…… 40

APPENDIX 4 – VOICE SWITCHING

SYSTEM (VSS) ……………………………………….…… 51

APPENDIX 5 – APPLICABLE

DOCUMENTS ……………………………………….…… 51

APPENDIX 6 – GLOBAL

POSITIONING SYSTEM SERVICE

DOCUMENTS

……………………………………………. 53

pg. 7

1.SCOPE

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). Work under this PWS will support the mission of 319 Communications Squadron at Grand Forks Air Force Base by providing highly reliable wired telecommunications and networked voice, video over data, data services, and records support. 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, 7 days per week. The BTS consists of the base voice system switch, the outside plant (OSP) and inside plant (ISP) systems, network, transmission systems, and all associated equipment described in Appendix 2, which may include other systems (e.g. radio, etc.). The Contractor shall operate and maintain all BTS equipment and systems in accordance with (IAW) the Original Equipment Manufacturers’ (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. All applicable equipment purchased/replaced must be compatible with planned future standards.

1.2. GENERAL REQUIREMENTS

1.2.1. Continuations of Mission Essential Services During Crisis IAW Defense Federal Acquisition Regulation Supplement (DFARS) clause 252.237.7023, it is determined that the O&M services in PWS paragraphs 2.1.1 and 2.1.2 are essential for cContractor performance during a crisis situation. In the event of a crisis, additional areas may be identified by the Contracting Officer (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, Dial Central Office (DCO) reconfigurations, and implementation of voice, video, and data collaborative services IAW AFMAN 17-1702 . This includes routing/diversity requirements and any other environmental changes that could impact or alter the base BTS.

1.2.1.1. Emergency Rights of the Government

The Government reserves the right to perform or supplement performance of mission critical contract functions with Government personnel during periods of disaster, war, or emergency.

The Contractor Ccontractor shall not be due payment for any functions not performed by the ContractorCcontractor. The Contracting Officer (CO) may enact this right through written notification to the contractor which shall state, at the minimum, the contract functions to be performed by Government personnel, the period of performance, and the applicable contract line items, to include the extent they may be affected.

pg. 8

1.2.2. 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 Contracting Officer’s Representative (COR) within two hours of the incident. The Contractor shall secure the scene of any accident and wreckage until released by the accident investigative authority through the Ccontracting Officer (CO). If the Government elects to conduct an investigation of the incident, the Contractor Ccontractor shall cooperate fully with the COR, CO, and other Government investigation personnel until the investigation is completed.

1.2.3. Sub-Contract Compliance

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

1.2.4. 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, digging, and manhole or hand hole entry. The cContractor will also coordinate with any non-governmental company prior to trenching, digging, and manhole or hand hole entry. The Contractor shall prepare and coordinate an AF Form 332, prior to any work requiring structural modification to the facility. 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, AFOSH, any local procedures and other provisions of this contract.

1.2.5. Personnel

The Contractor is solely responsible for ensuring sufficient personnel are assigned to this contract and appropriate personnel are qualified and certified to perform the requirements listed herein, including those qualifications and certifications required by the OEM requirements to maintain, install, or operate the equipment covered by this contract. The Contractor shall ensure personnel also meet the criterion stated in its proposal for this requirement. (as revised during the discussion process).

1.2.6. Key Personnel Listing

Contractor shall provide a key personnel listing and contact information to the COR prior to commencing work and update information on a continual basis as changes occur 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 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.

1.2.7. Contractor Identification

Contractor employees shall identify themselves or being introduced as contractor personnel and displaying distinguishing badges or other visible identification for meetings with Government

pg. 9 personnel. In addition, contractor personnel shall appropriately identify themselves as contractor employees in telephone conversations and in formal and informal written correspondence.

1.2.7.1. Contractor Badges/IDs

Contractor’s on site, employees will maintain Common Access Cards (CAC) to allow access to the base at all times and without the need of an escort. Contractor employees will also maintain Restricted Area Badges to critical locations for emergency outages.

2. DESCRIPTION OF SERVICES

2.1. OPERATE AND MAINTAIN (O&M) REQUIREMENTS

Overall responsibility to properly operate and maintain the BTS shall rest with the Contractor as described by the maintenance support plan (MSP) (See PWS sSection 3, BTS Work Center Records) and the OEM’s recommended procedures. Appendix 2 identifies GFM 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, 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 Section 5. 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

2.1.1. Telephone Switch System O&M

The Contractor shall operate and maintain the system(s) identified in Appendix 2. 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.

2.1.2. Perform ISP and OSP & O&M

Contractor shall maintain Inside Plant (ISP) and Outside Plant (OSP) cable and equipment as identified in Appendix 2 and IAW applicable documents listed in Appendix 5 of this PWS.

2.1.3. Preventative Maintenance Inspections (PMIs)

pg. 10

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 COR in writing within one workday. All manholes, handholes, cables, and terminals that have not been inspected within the last 3 years will take priority in the next inspection cycle. Contractor shall correct deficiencies IAW the paragraphs below.

Contractor shall document all PMI’s IAW Section 3 of this PWS.

2.1.3.1. Switch Power Test

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

PMIs shall test and document the power systems identified in Appendix 2. Each power system shall be tested IAW OEM specifications. Test results shall be documented IAW PWS sSection 3.

2.1.3.2. Spare Conductor Test

Contractor shall perform a scheduled PMI test of all 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 IAW PWS section Section 3).

2.1.3.3. Manhole and/or Handhole

The Contractor shall inspect 70 COR-accepted manholes per year under the O&M portion of this contract. The Contractor is responsible for ensuring inspections occur within the year regardless of weather conditions. Additional inspections (over 70) shall be accomplished as a work order IAW PWS section Section 5. If the Contractor is working in a manhole not scheduled for a PMI, the Contractor must correct any discrepancies before the job is considered complete. Then, the manhole will be counted in the monthly PMI schedule. The Contractor shall inspect each manhole/handhole for the following discrepancies and correct as required:

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

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

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

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

• Update the CIPS Visualization Component (CVC) database - for the manhole or handhole and record all descriptive information for splices, cables, ducts and other communication features in the manhole or handhole.

2.1.3.4. Terminals

The Contractor shall inspect 48 COR-accepted terminals per year. The Contractor is responsible for ensuring inspections occur within the year regardless of weather conditions. Additional inspections (over 48) shall be accomplished as a work order IAW PWS section Section 5. The Contractor shall inspect each terminal for the following discrepancies and correct as required:

pg. 11

• Verify the correct location, number and cable count.

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

• Ensure cable is tagged correctly.

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

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

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

• Update the Telecommunication Management System (TMS).

• Update the CVC database with descriptive information.

2.1.3.5. Distribution Pedestal Terminals

The Contractor shall inspect six COR-accepted Distribution Pedestal terminals per year. The Contractor is responsible for ensuring inspections occur within the year regardless of weather conditions. Additional inspections (over six) shall be accomplished as a work order IAW PWS section 5. The Contractor shall inspect each terminal for the following discrepancies and correct as required:

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

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

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

• Ensure terminal is correctly installed.

• Verify all working numbers and remove any unused.

• Remove all unused cross-connects.

• Update the CVC database with descriptive information.

2.1.3.6. 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 percentage in each cable to COR. The Contractor shall also determine the cable fill rates and report to COR. Update CVC as necessary to record accurate cable information.

2.1.3.6.1. Cable Locating

The contractor shall locate and GPS 10 cable pathways per year and verify CVC for accuracy.

2.1.4. System and Service Outages and Trouble Call/Tickets

2.1.4.1. Contractor Availability

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

pg. 12

2.1.4.2. Scheduled Outages

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 shall include the reason for the interruption, start and stop times, duration and the equipment, lines, and buildings affected. The Contractor shall log the outage IAW the guidance in PWS section 3(work center records).

2.1.4.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 below 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 co-ordinate with base Communications Focal Point (CFP) to restore any Internet Protocol (IP) phone set outages.

The Contractor shall log the outage IAW the guidance in PWS section 3 (work center records).

Outage/trouble call categories are further defined as:

2.1.4.3.1. Emergency

Contractor shall respond on-site within one hour after notification and restore service within eight hours unless otherwise approved by the COR in writing. Expedition of parts and/or labor is required at no additional charge. 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:

• Loss of over 50% or more of total call handling capability of any communications system or any portion thereof

• Loss of any Primary or Secondary Crash System or any portion thereof

• Failure of one or more circuits listed in the Base RPL

• Loss of LAN connectivity affecting 100 or more users

• Affects security or emergency type operations, including Emergency Operations Center

(EOC); as well as those affecting safety

• Affect specifically identified events and/or exercises

2.1.4.3.2. Priority

pg. 13

Contractor shall respond on-site within six hours and restore service as soon as possible, but shall not exceed three work days. Expedition of parts or labor may be required at no additional charge.

Priority outages are classified as any of the following:

• Loss of over 25% or more of total call handling capability of any communications system

• Major alarm of any switching system identified in Appendix 2

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

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

• Loss of LAN connectivity affecting 15-99 users

2.1.4.3.3. Routine

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

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

2.1.5. Alarm Notification

Contractor shall comply with the details of its alarm notification method as documented in the Contractor’s MSP. 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. Remote diagnostics modems are not authorized. Contractor is responsible for all materials and equipment necessary to implement alarm notification and shall take all actions to implement the MSP and comply with telephone switching security standards IAW AF MPTO 00-33A-1108, Voice Systems Management, Ch. 2.

2.1.6. Cable Location, Staking, and Marking

The Contractor shall locate, stake, and mark up to 150,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 feet 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 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 COR and the BTS manager. Communication Feature Data (CFD) collection shall be accomplished via work

pg. 14 order. The Contractor shall comply with the following timelines for location, staking, and marking:

• Emergency: Within two hours of notification

• Priority: Within 24 hours of notification.

• Routine: Within three business days of notification.

2.1.7. System Cross-Connect and Disconnect Services.

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.

2.1.8. Call Accounting System (CAS)

The Contractor shall operate and maintain the CAS. 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 billeting CAS will be limited to the same functions; the demarcation point will be at the switch port.

2.1.9. Voice Mail

The Contractor shall provide voice mail O&M. This includes, but is not limited to: management and administration of system network table and networking plan for multiple systems; additions;

deletions; modifications to user’s mailbox; password resets; distribution list; holiday schedule tables; daylight savings time; synchronization with the phone switch; and proper functioning of the auto attendant feature. Functions also include diagnostic, maintenance, and minor programming changes on current software applications. System backup includes backup of system configuration, names, and print “list all” of database.

2.1.10. Voice Protection System (VPS)

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

COR.

2.1.11. Automatic Call Distribution (ACD) System.

The Contractor shall provide O&M for the ACD system installed under the TelMod program.

O&M includes (but is not limited to) adds, moves, changes, and deletions; reconfiguration;

blocking/busying out trunks; configuring and modifying call routing; monitoring system operations; updating firmware; initiating least cost routing; and updating the dial plan.

2.1.12. Traffic Measurement and Analysis

The COR may request up to two 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 Government may specify which particular line or group of lines will be measured.

pg. 15

The information required by the contract must cover no less than a five-day period, (Monday- Friday, excluding holidays), and include, at a minimum, the following:

2.1.12.1. Trunk Traffic Summary identifying each trunk group by: number, name, description, direction, and the desired Grade of Service (GOS).

2.1.12.2. Individual Analysis of Each Trunk Group by:

• Number and name

• Type

• Quantity (total and working)

• Average busy hour

• Maximum usage

• Average minimum usage

• Average maximum usage/trunk

• Percent occupancy at average maximum usage

• Current GOS at average maximum usage

• Number of trunks required for recommended GOS

• Recommendations based on the information provided in the analysis

2.1.13. Contractor Support Services

Reserved.

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

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

2.1.16. Workload/Status Meetings

The BTS Manager shall attend up to two local meetings per month 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. 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).

pg. 16

2.1.17. Design Review Meetings

The Contractor shall review program or project drawings and provide comments concerning communications requirements within five 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 shall attend up to six design review meetings per month.

2.1.18. Technical Solutions

Contractor shall perform detailed technical solutions for work intended to be performed under this contract upon receipt of a written request from the COR. The technical solution includes a listing of those efforts/items required to complete the job and shall be provided to the COR using the work order format specified in PWS Section 5. The Contractor shall provide the proposed solution to the COR within seven working days from receipt of requirement unless a longer period is agreed to by the COR and documented on the requirement.

3. Records

3.1. BTS Work Center Records

Contractor shall develop and maintain BTS work center records. The Contractor shall update work center records within three 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 turned over to the COR for disposition upon contract completion. Failure to do so may result in withholding of final payment until all records are recovered or in 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.

3.2. Maintenance Support Plan (MSP)

The MSP shall enable the scheduling and tracking of preventive maintenance actions on cContractor-maintained equipment. This record shall be available within 30 calendar days after period of performance begins. When changes occur that affect the MSP, 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. Changes may be implemented only after CO approval. The MSP shall contain as a minimum: a schedule of PMIs due on each piece of equipment being maintained

pg. 17

(Appendix 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.

3.3. PMI Inspection Records and Malfunction Record

PMI Inspection 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.

3.4. Maintenance/Repair Logs (e.g. maintenance actions, trouble tickets) Contractor shall develop and maintain an accurate and legible BTS Maintenance/Repair Log 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 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, priority, or routine outage(s)). For scheduled outages, also include the Government authorization.

3.5. Manhole, Handhole, and Building Terminal Inspection/Maintenance/Repair The Contractor shall maintain manhole, handhole, distribution pedestal terminal, and building terminal inspection records as defined in PWS Section 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.

3.6. Cable Installation/Repair Test Results

Contractor shall develop and maintain a cable installation/repair test results record after the installation or repair of an outside plant 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.

3.7. Communication and Information Systems Installation Record (CSIR) & New Developments

pg. 18

The Air Force is in the process of developing and implementing the Cyberspace Infrastructure Planning System (CIPS) Visualization Component (CVC) It changes the method of developing, maintaining, and editing information historically contained in installation drawings (CSIRs) from a Computer Aided Design and Drafting (CADD) process to a Geographic Information Systems (GIS) process that interfaces with the Geobase initiative and provides an Air Force 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 inside plant information. Until such time as the CVC has standard provisions for recording inside plant information, inside plant record drawings shall be maintained in Base’s existing drawing record systems. The Contractor shall coordinate with the Base CSIR Manager, and develop and maintain CSIR IAW TO 00-33A-1001, and TO 00-33D- 3003.

3.7.1. Drawings Maintenance

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 outside plant, in the CVC database IAW TO 00-33A-1001. Contractor shall transfer to the CVC database all pertinent outside plant 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 outside plant information from as-built drawings or other pertinent documents or electronic data pertaining to work done by third parties (organic or cContractor) when tasked through the work order process. A separate pre-priced Sub-contract Line Item Number (SLIN)/Product Identifications (PID) shall be used for conversion of third party as-built drawings, document, or electronic data information. Contractor is responsible for verifying cContractor-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 in accordance with PWS paragraph 3.6.2. When the update is completed, the Contractor will close the session and notify the CISR 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 Ccontractor’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.

3.7.2. Inside Plant Drawing Records

Inside Plant 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.

3.7.3. CIPS & CVC

pg. 19

The Contractor shall have a CIPS account in order to use CVC. The Contractor shall apply for a new account by visiting the website at https://cipsaf.tinker.af.mil/cips, selecting Create New Account, and providing the required information.

• (Note: This section provides for keeping As-Built records. At this time, the CVC is not designed to keep as-built records for specific installation projects. Information put into the CVC is merged into a dynamic, ever-changing, database and information as to the cause of changes or modifications is not automatically recorded. Until such time as the CVC has standard provisions for providing a static as-built picture of completed projects, or for recording the nature and cause of changes within CVC, the CSIR Manager requiring as-built records not subject to change, must keep non-CVC as-built records in either paper or electronic file format.)

3.7.4. As Built Drawings

All cContractor and Tthird Pparty as-built drawings submitted to the CSIR Manager will be in Microstation J (V7), AutoCAD, VISIO, or CVC format as directed by the COR. The Contractor shall provide correctly annotated paper copies in addition to the electronic files until the electronic submittal process has been validated at which time the paper copy requirement may be waived. Color plots of electronic files are acceptable providing they show the same information that would be shown in a manually marked up drawing. Contractors will produce drawings to support engineering initiatives.

3.7.5. CSIR Manager Coordination

All changes/additions shall be made on the government provided electronic file. The electronic files shall be renamed in the CSIR Manager designated naming and numbering format. The Contractor as-built drawings shall be transmitted to the CSIR Manager. The 38 CEG will no longer accept updates/as-builts from any Government or contracting activity, the COR, or the Contractor. The Base CSIR Manager will manage all updates/as-builts and permanent drawing records.

3.8. Switching and ISP & OSP Equipment Operational Records

Contractor shall retain records on site and make available for COR or CO/CA review at any time.

3.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;

description; and quantities of each item. The record shall exclude price information. Contractor shall update this record within two days of work order completion.

3.10. AF Logistics Support Spares Records (Inventory)

Contractor shall maintain the AF Logistics 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 https://cipsaf.tinker.af.mil/cips/mycips.aspx

pg. 20 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.

3.11. Contractor-Furnished Hazardous Material

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 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 cContractor point of contact; emergency phone number; and address or physical location of the cContractor’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 cContractor.

3.12. Equipment Inventory Records (PWS Appendix 2)

The Contractor shall maintain a working copy of Appendix 2. Appendix 2 shall identify equipment installed, changed, or removed via contract modification or the work order process identified in PWS section 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 using the “track changes” feature in MS Word® software.

3.13. Telecommunications Management System (TMS)

The TMS currently in use at Grand Forks AFB is Configuration Accounting Information Retrieval System (CAIRS). The Contractor is required to use CAIRS.net. The Contractor shall perform daily record updates using the current TMS. 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 the current TMS.

3.14. Work Order Records, Including Warranty Records

pg. 21

The Contractor shall develop and maintain work orders. The Contractor shall update work center records within two (2) work days after completion of the task(s) specified on individual work orders and notify COR in writing. Physical records of work orders in process shall be retained and available locally (on-base). Electronic storage of completed (accepted by the COR) 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.

3.15. Systems Capacity Records

Contractor shall produce system capacity records quarterly and upon request by the COR. Semi-annual system capacity records include outside plant 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, fiber patch to patch panels, line port type (analog/digital/ISDN/VOIP, etc.) total used, and DS-1 digital trunk ports (total ports used and available).

3.16. System Security Audit Records

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.

3.17. Quality Control Plan (QCP)

Contractor shall develop a highly effective QCP for all services provided under this PWS within 30 calendar days of contract award. 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 cContractor logistic support, centralized maintenance and remote monitoring from the I-NOSC 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 work days prior to implementation of those changes.

4. Global Positioning System (GPS)

4.1. (GPS) Service Data 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 in accordance with 3.7.3 and Appendix 6 (for any GPS requirement).

pg. 22

4.2. Global Positioning System (GPS) Service. Contractor shall use GPS technology to provide geospatial coordinates and feature description data of cable installation pathway, which includes but is not limited to data on new, modified, and repaired underground, buried and aerial communications cables, cable trenches, ducts, duct banks, manholes, handholes, building entries, terminals, distribution pedestal terminals, and splices. Contractor shall ensure data compatibility with the CIPS Visualization Component (CVC) database and shall upload the data into the CVC database.

4.2.1. The Contractor shall use GPS equipment and technology supplemented with electronic underground cable locating equipment and land surveying operations necessary to collect required Communication Feature Data (CFD) following the Federal Geographic Data Committee (FGDC)-STD-007.4-2002 specified in PWS Appendix 5.

4.2.2. Each communication feature requiring geospatial coordinates shall be located to within one meter of its true ground position, in the horizontal plane, with a 95% spatial accuracy confidence level as defined in FGDC-STD-007.3-1998, specified in PWS Appendix 5.

4.2.3. Geospatial coordinates for the location of manholes and cable vaults shall be recorded for the center of the manhole lid. Geospatial coordinates for the location of handholes, pull boxes, pedestals, and buried splices shall be recorded for the top center of the feature.