PWS_FY14_BTS.pdf

PERFORMANCE WORK STATEMENT

FOR

OPERATIONS AND MAINTENANCE SERVICES

BASE TELECOMMUNICATIONS SYSTEM (BTS)

Reviewed By:

Cheryl A. Roberts Quality Assurance Program Coordinator

DOVER AFB, DELAWARE

June 11, 2013

PERFORMANCE BASED WORK STATEMENT (PWS)

FOR

OPERATIONS AND MAINTENANCE SERVICES

BASE TELECOMMUNICATIONS SYSTEM (BTS)

AT

DOVER AIR FORCE BASE

1.0 DESCRIPTION OF SERVICES

1.1. Scope of Work…………………………………………………………………………1

1.2.Requirements…………………………………………………………………………...1

1.2.1 Base Mission Requirements……………………………………………………1

1.2.2 Accident/Incident Reporting and Investigation………………………………...1

1.2.3 Subcontractor Compliance……………………………………………………...1

1.2.4 Base Civil Engineering Work Clearance Requests………………….………….1

1.2.5 Personnel Qualifications…………………………………………….…………..2

1.3. Monthly Maintenance…………………………………………………….…………

1.3.1 Perform Telephone Switch System Maintenance………………….……………2

1.3.2 Perform Inside and OSP Maintenance…………………………….……….……3

1.3.3 Preventive Maintenance Inspections (PMIs)…………………………..………..3

1.3.4 System and Service Outages…………………………………………..…….…..4

1.3.5 Voice Mail……………………………………………………………..…….…..6

1.3.6 System Cross-Connect and Disconnect Services………………………..………6

1.3.7 Voice Mail………………………………………………………………..……...7

1.3.8 Voice Protection System (VPS)………………………………………..….….…7

1.3.9 Traffic Measurement and Analysis………………………………………..….…7

1.3.10 Contractor Support Services……………………………………………..………7

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

1.3.12 BTS Work Center Records…………………………………………….……

1.3.13 TMS…………………………………………………………………….…..……11

1.4 Work Orders…………………………………………………………………….……..12

1.4.1 Work Orders Procedures………………………………………………….……..13

1.4.2 Global Positioning System (GPS)……………………………………….………14

2.0 SERVICE DELIVERY SUMMARY (SDS)……………………….……………….………16

3.0 GOVERNMENT-FURNISHED PROPERTY AND SERVICES……………….……….. .18

4.0 GENERAL INFORMATION…………………………………………………………….…21

4.1Quality……………………………………………………………………………………21

4.1.1 Quality Control Program…………………………….…………………………….21

4.1.2 Quality Control Plan………………………………….………………………

4.2 Security…………………………………………………….…………………………

4.2.1 Security Plan………………………………………….…………………………

4.2.2 For Official Use Only (FOUO)……………………….……………………………21

4.3 Safety, Security, and Environmental Meeting………………………………………….22

5.0 RECORDS MANAGEMENT…………………………………………..……….………….22

6.0 SECURITY…………………………………………………………………..………..…….23

7.0 CONTRACTOR BADGE POLICY………………………………………..……………….23

8.0 INSTALLATION ACCESS……………………………………………….……………..…24

9.0 ANTITERRORISM………………………………………………………..……………..…24

10.0FLIGHTLINE DRIVING…………………………………………………...………………24

11.0CONTRACTOR MANPOWER REPORTING…………………………………………

12.0SOLID AND HAZARDOUS WASTE REMOVAL………………………………………..25

13.0APPENDICES……………………………………………………………………………

13.1 Workload Estimates……………………………………………………….….……….26

13.1.1 General…………………………………………………………………………..26

13.1.2 Monthly Maintenance Service…………………………………………………..26

13.2 Items to be Maintained by the Contractor………………………...…..……………….27

13.3 Glossary and Acronyms…………………………………………………..……………82

13.3.1 Purpose……………………………………………………………………….….82

13.3.2 Definitions……………………………………………………………………….82

13.3.3 Acronyms………………………………………………………………………..87

13.4 Voice Switching System (VSS) Sustainment…………………………...…………….91

13.5 Traffic Measurement & Analysis Terminology:……………………….……………92

13.6 Applicable Documents…………………………………………………….………….94

13.7 Reserved……………………………………………………………………..………..98

13.8 Global Positioning System Service Documents……………………………………...99

1.0 DESCRIPTION OF SERVICES

1.1 Scope of Work.

Contractor shall provide all personnel, equipment, tools, materials, vehicles, supervision and other items and services necessary to provide highly reliable telecommunications and networked voice, video and data services, unless specified in this contract as Government Furnished

Property (GFP) to support the mission of 436 Communication Squadron (CS) at Dover Air Force

Base, DE. Contractor shall perform monthly Operations and Maintenance (O&M) services 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 telephone system switch, the outside plant (OSP) and inside plant systems, and all associated equipment described in

Appendix 13.2. Contractor must operate and maintain all BTS equipment and systems in accordance with (IAW) publications in Appendix 13.6.

1.2 Requirements.

1.2.1 Base Mission Requirements.

Contractor may be required to support base mission changes; major or minor BTS infrastructure modifications; and other support requirements necessary for the BTS to meet mission requirements. Missions are frequently interrupted by base exercises or actual ongoing base security events. Support requirements may originate from technology changes, hardware and software systems upgrade, reconfigurations, new or additional equipment, local area network

(LAN) cable installations and upgrade, and Dial Central Office (DCO) reconfigurations. This includes routing/diversity requirements and any other environmental changes that could impact or alter the base BTS. Contractor will be required to install telecommunications wiring in dormitories, military family housing, visiting airmen’s and officer’s quarters, temporary lodging facilities, other communications systems and devices, etc., as directed by the CO or COR.

1.2.2 Accident/Incident Reporting and Investigation.

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

1.2.3 Subcontractor Compliance.

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

1.2.4 Base Civil Engineering Work Clearance Requests.

Contractor shall obtain a Base Civil Engineering Work Clearance Request, AF Form 103, and/or an AF Form 332, prior to any trenching or digging; facility work; or manhole/handhole entry.

Contractor will be required to obtain accounts for the electronic Digging Permit System provided by Base Civil Engineering. Contractor will be required to process Digging Permits for their own construction and also process and sign off on Digging Permits that are submitted by others for the Communications portion of the permit.

(Note: Base Civil Engineering may be required to schedule and perform this type of work.) Trenching, excavation, confined spaces entry, confined spaces atmospheric testing/forced air ventilation, and marking and barricading of open trenches are to be performed

IAW Occupational Safety and Health Act (OSHA) standards and other provisions of this contract.

1.2.5 Personnel Qualifications.

Contractor is solely responsible for ensuring that sufficient personnel are assigned to this contract and that all personnel are experienced and qualified to perform the services listed in this

PWS. Contractor shall identify the key personnel and notify the Contracting Officer

Representative (COR) prior to commencing work. Contractor shall provide a key personnel listing and contact information to the COR prior to commencing work and update information on a continual basis to ensure it is always current and correct throughout the life of the contract. All personnel shall be proficient in understanding, reading, writing, and speaking the English language.

1.2.6. Access to Base LAN.

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

1.3 Monthly Maintenance.

Overall responsibility to properly maintain and operate the BTS shall rest with Contractor as described by the maintenance support plan (see 1.3.12.1) and be performed IAW the commercial manufacturer’s recommended procedures. Monthly Maintenance is all actions taken by

Contractor to maintain equipment and systems in a serviceable condition or to restore it to a serviceable condition to include inspection, periodic testing, adjustment, and repair. The effort includes the replacement of defective circuit packs and Customer Premise Equipment (CPE), and preventive maintenance IAW applicable publications and other routine work to optimize the life expectancy of the equipment and cable systems. Work orders will be accomplished IAW 1.4 to include relocates and removals. Monthly Maintenance efforts shall not be postponed or otherwise delayed to accomplish work orders.

1.3.1 Perform Telephone Switch System Maintenance.

Contractor shall operate and maintain the switching system(s) identified in Appendix 13.2 IAW

Original Equipment Manufacturer (OEM) procedures. Acceptable standard performance level shall be measured by a determination of the total systems availability (up time) and reliability rating during any given month. A period of five minutes down time shall not be exceeded during any one month period. All equipment or services completed by Contractor shall automatically become part of the monthly maintenance services.

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

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

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

1.3.2 Perform Inside and OSP Maintenance.

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

1.3.3 Preventive Maintenance Inspections (PMIs).

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

1.3.3.1 PMI Switch Power Test.

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

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

1.3.3.2 PMI Spare Conductor Test.

Contractor shall perform a scheduled PMI test of the spare conductors. PMIs shall test and document at least two selected, out-of service pair (one low and one high numbered pair) in each

25-pair group of every cable terminating in the DCO. These PMI tests are to be accomplished quarterly. Test results shall be documented and a copy provided to the COR.

1.3.3.3 PMI Manholes.

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

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

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

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

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

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

1.3.3.4 PMI Terminals.

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

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

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

1.3.3.4.3 Ensure cable is tagged correctly.

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

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

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

1.3.3.5 PMI Distribution Pedestal Terminals.

Contractor shall inspect at least one Distribution Pedestal terminals per month. Each terminal will be inspected for the following discrepancies and corrected:

1.3.3.5.1 Evaluate condition of Distribution Pedestal terminal.

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

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

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

1.3.3.5.5 Ensure that terminal is correctly installed.

1.3.3.5.6 Verify all working numbers and remove any unused.

1.3.3.5.7 Remove all unused cross-connects in the terminal.

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

1.3.4 System and Service Outages.

1.3.4.1 Contractor Availability.

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

1.3.4.2 Scheduled Outages.

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

1.3.4.3 Outage Restoration.

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

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

Contractor shall work closely with the COR on all service or system outages and verbally notify the COR upon restoration of service providing the time service was restored and a description of repair action. Contractor shall maintain an accurate and readable record of all scheduled interruptions and shall include the reason for the interruption, authorizations, action taken, equipment or lines affected, and dates/times of coordination and restoration. (See definitions in

Appendix 13.3 and workload estimates in Appendix 13.1.) If an outage significantly affects a mission, the COR may designate the category of outage as the mission dictates. Contractor will be required to obtain an account for any electronic tools used in support of locally established processes (i.e. Remedy/CIPS) in order to process trouble tickets. Trouble tickets will be reported to the Comm Focal Point (CFP) who will obtain at a minimum, the following information:

Customer Name, working customer contact number, bldg. number, and floor or room number, clear explanation of the problem they are experiencing. CFP will forward the Trouble Ticket to the contractor for processing. The contractor shall be required to close the ticket when it’s completed.

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

1.3.4.3.1 Emergency Outage.

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

1.3.4.3.2 Priority Outage.

On-site response is required within six hours of notification. Priority outages are classified as a loss of over 25% or more of total call handling capability of any communications system; major alarm of any switching system identified in Appendix 13.2; loss of the Commanders Net or Land

Mobile Radio (LMR) telephone/radio circuits; total loss of telephone service within a building;

or loss of LAN connectivity affecting 15-99 users.

1.3.4.3.3 Routine Outage.

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

1.3.4.4 Remote Monitoring (Response to NCC).

Contractor shall coordinate the details of any proposed Remote Monitoring method with base personnel and be documented in the Contractor’s Maintenance Support Plan. Remote monitoring shall not interfere with any government owned system. Remote monitoring of the switch system(s) shall not require assistance from base personnel. Notification of switch outages shall not be through a continuous direct line to the switching system for security reasons.

Remote diagnostics modems must be user name and password protected. Contractor is responsible for all materials and equipment necessary to implement remote monitoring and shall take all actions to implement the plan and comply with telephone switching security standards.

1.3.4.5 Outage Cause Identification.

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

1.3.5 Cable Location Staking and Marking.

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

Emergency: Within two hours.

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

1.3.5.1 Collection of Communication Feature Data (CFD).

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

GPS to the geospatial accuracy specified in Appendix 13.8 and record the GPS portion of the

CFD in the CVC database within four duty days of collecting the data.

1.3.6 System Cross-Connect and Disconnect Services.

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

1.3.7 Voice Mail.

Contractor shall provide voice mail operations. This includes management and administration of system network table and networking plan for multiple systems, additions, deletions and modifications to user’s mailbox, distribution list, holiday schedule tables, and daylight saving time. Functions include diagnostic, maintenance and minor programming change on current software applications. System backup includes backup of system configuration, names, and print

“list all” of database.

1.3.8 Voice Protection System (VPS).

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

1.3.9 Traffic Measurement and Analysis.

Contractor shall perform semi-annual traffic measurement and analysis within system capabilities and limitations and perform analysis and studies on the base switching system (see

Appendix 13.5 and PWS Section 1.3.13.3). The information required by the contract must cover no less than a five-day period, (Monday-Friday).

1.3.10 Contractor Support Services.

1.3.10.1 Contractor Support for Government Engineering and Installation.

Upon direction of the COR, Contractor shall provide technical support to include an interchange of information on technical parameters and capabilities of the BTS; location and identification of building terminals and communication rooms; and verification of cable record information.

These efforts include setting of equipment options to determine proper operational conditions;

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

1.3.10.2 Contractor Interface and Support for other Vendors.

Contractor shall cooperate, share and exchange routine or available technical and system equipment interface information with other vendors.

1.3.10.3 Design Review Meetings.

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

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

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

The ROM shall be prepared as follows: provide a proposed technical solution using existing

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

1.3.11.2 Technical Solution.

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

1.3.11.2.2 Upon receipt of a requirement and written request from the COR, Contractor shall review the requirement and provide a detailed technical solution using existing Contract

Line Item Numbers (CLINS)/product identifications (PIDS).

1.3.11.2.3 Response to emergency surveys will be within two hours and completion will be within four hours. Priority survey will be completed within two duty days of request.

Routine surveys will be completed within five duty days of request unless a longer period is agreed to by the COR and documented on the requirement. (See Appendix 13.1 for workload estimates). Emergency surveys may be tasked by COR verbally. See paragraph 1.4. for implementation procedures.

1.3.12 BTS Work Center Records.

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

1.3.12.1 Maintenance Support Plan (MSP).

The MSP shall enable the tracking of preventive maintenance actions on contractor-maintained equipment. Electronic copies shall be provided to the COR and CA (Block 9 of the SF Form

1449). When changes occur that affect the plan, revisions shall be submitted within 10 work days after the effective change (e.g. modification adding equipment) unless otherwise requested by the CO (e.g. with the proposal to add new equipment to maintenance). The Government will review and approve, or provide the contractor with required corrections, within 30 calendar days.

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

1.3.12.2 PMI Inspection Records and Malfunction Report.

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

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

1.3.12.3 Maintenance/Repair Logs.

Contractor shall establish and maintain an accurate and legible BTS Maintenance/Repair Log

(integrated into locally established maintenance processes) to show all maintenance and inspections (other than PMIs) performed during each 24-hour period as a result of trouble report actions or scheduled/unscheduled outages. The log shall be initialed by the BTS Manager and shall include, as a minimum, initials of the first and last name of the person reporting a discrepancy; time a discrepancy was reported (start time); short description of the discrepancy

(reason for scheduled/unscheduled outages); identification of the customer/user by station line affected (telephone number or circuit number); location of equipment (building and room number, etc.); time a technician(s) was dispatched; time discrepancy was corrected (stop time) and annotation of log with the person or office contacted to provide status information;

corrective action(s) taken.; and restoration priority (emergency, priority, or routine outage(s)).

See Paragraph 1.3.4.3. for implementation guidance.

1.3.12.4 Manhole, Handhole, and Building Terminal Inspections.

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

1.3.12.5 Cable Installation/Repair Test Results.

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

(e.g., instrument readings) (if extensive, provide as an appendix); conclusions/recommendations;

and authentication/authentication of results and acceptability.

1.3.12.6 Communications and Information Systems Installation Record (CSIR).

Contractor shall create, update, and post changes to drawings, plant records or documents using

Government provided forms, software and web browser applications. Contractor shall load, edit, update and maintain CSIR information in the CVC database IAW AFI 33-101. Contractor shall transfer to the CVC database all pertinent CFD information from administrative and maintenance

CSIR, Legacy CSIRs, work orders, inspection reports, as-built and as-installed marked-up drawings, and GPS services, that are created as a result of the Contractor’s operations. The

Contractor shall update the CVC database with information from as-built drawings or other pertinent documents or electronic data pertaining to work done by third parties (organic or contractor) when tasked through the work order process. A separate pre-priced SLIN/PID shall be used for conversion of third party as-built drawings, document, or electronic data information.

Contractor is responsible for verifying Contractor entered information accuracy and completeness. Contractor will update the CVC with as-built information and will import shape files created in accordance with Appendix 13.8, by creating a new O&M Workspace with the

CVC Editor tool. When the update is completed, the contractor will promote the Workspace for

CSIR Manager’s approval. After each promoted O&M workspace has been approved and merged to the CVC database by the CSIR Manager. The Contractor shall create and promote a new O&M Workspace for each proposed subsequent CVC update. The CSIR Manager will approve and merge or reject each promoted O&M Workspace. The Contractor shall coordinate with the Base CSIR Manager, and develop and maintain CSIR IAW AFI 33-101 training and instructions published at the CVC accessible website: https://cipsaf.tinker.af.mil/cips or search for CIPS at the Air Force Portal. Dover AFB has a standalone data base created for CVC input locally. The records shall be for the inside and outside telephone plant portion of the telecommunication system.

1.3.12.7 Scheduled Service Interruption Records.

Contractor shall maintain records of all scheduled interruptions and shall include the reason for the interruption, authorizations, action taken, equipment or lines affected, and dates/times of coordination and restoration. COR approval and Communications Focal Point coordination for any scheduled service interruption shall be coordinated 5 duty days prior.

1.3.12.8 Switching System and Inside & OSP Equipment Operational Records.

Contractor shall retain reports on site, and make available for COR or CO/CA review.

1.3.12.9 CLIN/PID Utilization Report.

On a monthly and cumulative basis, Contractor shall be responsible for creating and maintaining an electronic record of the CLINs/SLINs/PIDs, descriptions, and quantities used under the contract, excluding price information. Contractor shall submit this report to the COR monthly.

When subcontractor effort is used, Contractor shall identify individual material components to accomplish the job and sub-contractor labor quantity as a lump sum number of hours.

1.3.12.10 AF Logistics Support Spares Records.

Contractor shall maintain and update the AF Logistics Spares records in the on-site work center.

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.12.11 Contractor-Furnished Hazardous Material.

Contractor shall provide this report when bringing or using hazardous material on Government facilities. Contractor shall provide the COR and CA/CO with this report electronically not later than 30 calendar days after contract award and quarterly thereafter. The report shall consist of the following:

https://cipsaf.tinker.af.mil/cips

1.3.12.11.1 Section 1, General Information.

This section shall contain: Contract number; contract performance period; Contractor's name;

date of report; 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.

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

1.3.12.11.3 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.12.12 Global Positioning System (GPS) Service Data.

Contractor shall collect and maintain the Communication Feature Data (CFD) and use the data to update the location and attributes of communication features in the CVC database in accordance with 1.3.12.6 and Appendix 13.8 (for GPS requirement).

1.3.13 TMS.

Contractor shall perform daily record updates using TMS or locally developed data base. Some updates may require the contractor to manually enter the data upon completion of individual work orders or record changes. Contractor shall complete record updates within two duty days after the circuits/service have been installed/relocated/disconnected or changed. Contractor shall provide the following TMS-generated records upon request by the COR:

1.3.13.1 Work Order Records, Including Warranty Records.

Contractor shall provide TMS or locally developed data base generated service order reports upon request from the COR.

1.3.13.2 Cable Pair Assignment Records.

Contractor shall maintain cable pair assignment records in hard copy and computerized format using TMS or locally developed data base at the discretion of the COR.

1.3.13.3 Traffic Measurement Records.

Contractor shall provide the report with printed, tabulated data from the traffic measuring system. The report shall provide measurements for five consecutive business days, on an hourly basis, unless a shorter interval is required. The report shall contain an analysis of the traffic measurements and recommendations based on the analysis. Recommendations shall address expansion of switch hardware and software. The report shall also include a trunk traffic summary and individual analysis of each trunk group.

1.3.13.4 Equipment Inventory Records.

Contractor shall review the list of equipment (Appendix 13.2) and prepare an update of equipment inventory for equipment installed or removed via contract modification or the work order process. Include all assemblies of the equipment configuration, which would be logically disassembled from the total configuration for the purpose of packing and shipping. The inventory shall be formatted on the report in the same manner as in Appendix 13.2. The report shall be submitted to the COR, CA, and CSI-B electronically and be continually updated and submitted annually not later than the last work day of August.

1.3.13.5 Call Accounting System (CAS).

Contractor shall operate the CAS. This includes storage and output of records and formatting of the switching system. Contractor is not responsible for input, manipulation, or analysis of data.

Contractor’s responsibility for any billeting CAS will be limited to the above functions; the demarcation point will be at the switch port.

1.3.13.6 System Security Audit Report.

Contractor shall maintain a weekly user event log, which shall contain, 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.13.7 System Capacity Records.

Contractor shall produce system capacity reports on demand via TMS or locally developed data base.

1.4 Work Orders.

Work orders will be accomplished during normal duty hours; however, occasions may arise that require work to be accomplished outside of these hours (see Appendix 13.1). Contractor shall be responsible for covering such situations with adequate personnel and completing the work within the stipulated time. Examples of work orders include, but are not limited to, future equipment purchases, installations, removals, or relocations. Additionally, work orders may include installation or removal of cables/transmission media as required for new requirements, and

Monthly Maintenance of these equipment items/media. The COR will be notified of any installation found to be incomplete or not installed according to industry standards. 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 modification. Contractor will be required to obtain an account in

Cyberspace Infrastructure Planning Systems (CIPS) (or locally established process) in order to process work orders using the Work Order Management System (WOMS) or locally established process. Emergency/Priority requirements may be submitted to contractor by phone or in person.

Contractor will be required to follow current workflow process for WOMS requirements.

Contractor shall interface with the Telephone Control Officer (TCO) who submits the requirement. Contractor shall make 3 attempts on 3 separate days to contact the TCO. If those 3 attempts fail, the contractor shall send the WOMS requirement to the Pending Customer Action

(PCA) box for the TCO’s action. When the contractor has made contact with the TCO and has a clear definition of the requirement, the contractor shall complete a Technical Solution and

Costing. Contractor shall completely fill out the DD Form 1367 or equivalent with the exception of the Work Order Number which will be completed by the COR, and forward the attached DD

Form 1367 or equivalent with the WOMS requirement to the COR for review, approval and electronic signature. The work order at that point is approved for processing. Contractor will make every effort possible to satisfy the customer’s requirement at the lowest cost possible; i.e.

recommend programming changes or features that the TCO may not be aware of before providing a cost.

1.4.1 Work Order Procedures.

Contractor shall comply with the following work order procedures and requirements.

1.4.1.1 Pre-Priced Items.

Work orders for pre-priced items may be prepared by the COR or by Contractor. Work orders prepared by Contractor shall be submitted for approval to the COR. All work orders shall be prepared on DD Form 1367, Commercial Communications Work Order (CCWO) or equivalent form. Work order numbers shall be established by the COR. If required, the Contractor shall visit the proposed work site with the COR to ensure agreement on the work to be performed.

Authorization to deviate from pre-priced (competed) PID items requires appropriate justification, price support (See FAR 15.4) and CO approval.

1.4.1.2 All work orders issued hereunder are subject to the terms and conditions of the contract.

In the event of conflict with any work order, the contract will take precedence. Refer any disputes concerning work orders to the CO within 24 hours, or two hours for emergencies.

1.4.1.3 Work Order Classifications.

The COR will classify work orders as routine, priority, or emergency. The COR is authorized to reclassify/reprioritize work orders without cost before work commences. Contractor shall comply with the time limits listed below from the time of receipt of the work order; however, exceptions to time limits may be allowed, with the written approval of the COR. All cable cut repairs shall be classified as emergency unless determined otherwise by the COR.

1.4.1.3.1 Routine.

Contractor shall complete routine work orders within ten duty days (see Appendix 13.1).

1.4.1.3.2 Priority.

Contractor shall complete priority work orders within three duty days (see Appendix 13.1).

1.4.1.3.3 Emergency.

Contractor shall complete emergency work orders within four hours (see Appendix 13.1).

1.4.1.4 Required Information on Work Orders.

Work orders placed under the contract will contain the following information, consistent with the contract terms:

date of preparation;

contract number and work order number;

CLIN/SLIN/PID, description, quantity ordered, building number, room number, and contract unit and extended prices;

work order priority and established completion time;

statement “Davis Bacon Act applies ____ Y or ____ N _____ (Contractor Initials)”;

changes to work orders, as permitted by terms within this PWS that reflect mutual agreement by attaching supporting documentation, signatures of COR and Contractor, and dates of signatures;

any other pertinent information.

1.4.1.5 Work orders will be accomplished during normal duty hours; however, occasions may arise that require work to be accomplished outside of these hours (see Appendix 13.1). The

Contractor shall be responsible for covering such situations with adequate personnel and completing the work within the stipulated time.

1.4.1.6 Work orders subject to the Davis Bacon Act. The COR is authorized to place work orders directly with the contractor for all CLINs/PIDs. The Contractor shall identify work orders where the DBA applies on the face of the work order (see paragraph 1.4.1.4 above). Work orders using CLINs X002-X007 MAY be subject to DBA dependent upon work effort to be performed.

1.4.1.7 Special Project Requirements

Special projects are Firm Fixed Price (FFP) negotiated requirements. The CO will request a proposal from the contractor for special projects. The government may negotiate a special project into the contract when an effort is needed that is not completely covered by current line items on the contract. These are one-time efforts that are within the scope of the contract. Special projects will not cumulatively total more than 25% of the total price of CLINs X001 - X007 for the Base

Period and all Option Periods. Proposals shall be submitted on DD Form 1367 (Commercial

Communications Work Order) or equivalent format and include the information below, as a minimum.

1.4.1.7.1. Contractor Proposals

Contractor shall submit detailed proposals for work intended to be performed under special projects as requested by the COR/CO at no additional price. Contractor shall provide its proposal to the COR/CO within five workdays or an agreed timeline negotiated between the contractor and the COR depending on the size of the project. The contractor’s proposal shall provide adequate detail of efforts/items required to complete the job, including, but not limited to item description, quantity, unit of issue and extended prices. The contractor shall identify if DBA applies in the proposal.

1.4.1.7.2. Contractor’s proposal shall include all direct and indirect expenses and profit within the price of the items specified. Contractor’s proposal shall be prices for inspection/acceptance at final destination.

1.4.1.7.3. If the Contractor uses any existing pre-priced CLINs/PIDs from the original price list, they shall notify the CO upon submittal of their proposal.

1.4.1.8 Submittal of Completed Work Orders.

Contractor shall update the work completed through WOMS or locally established process within one duty day of completion.

1.4.2 Global Positioning System (GPS) Service.

GPS Service shall be issued under CLIN X007. Contractor shall provide a GPS Service to collect Geospatial data on the repairs, modifications or additions to the OSP cable installation pathway. These data, included in Communication Feature Data (CFD), consist of geospatial location and attribute information on physical features in the cable installation pathway.

Features include, but are not limited to, communications cables (buried, underground, open trench, and above ground) and associated structures and equipment such as manholes, handholes, ductbanks, conduits, splice points, and pedestals. The method for collecting and formatting data shall be done IAW Appendix 13.8. Contractor shall provide GPS data on electronic media as directed by the COR. The data model and file format shall be as specified in Appendix 13.8.

2.0 SERVICE DELIVERY SUMMARY (SDS).

The Government has the right to inspect all services called for by the contract (SDS and Non-

SDS items), to the extent practicable at all times and places during the term of the contract.

Performance

Objective

PWS

Reference

Performance

Threshold (Monthly)

Operate and maintain minimum switching system(s)

1.3.1 A period of 5 minutes downtime shall not be

exceeded

Perform PMI tests of spare conductors 1.3.3.2

Test & document at least 2 out-of-service pair

(one low/one high numbered pair) in each 25-pair group of every cable terminating in DCO

Respond to all system and service outages within the required time constraints:

Emergency – 2 Hours

Priority – 6 Hours

Routine – 24 Hours

1.3.4.3.1

1.3.4.3.2

1.3.4.3.3

Emergency - Zero instances exceeding 2 -hour response time

Priority - One instance exceeding 6-hour

Routine - One instance exceeding 24 hours

Provide location, staking, and marking services

Emergency: provide within 2 hours

Routine: provide within 5 business days

1.3.5 Emergency - Zero instances exceeding 2-hour

Routine - One instance exceeding 5 business days

Perform disk, cartridge, or tape backup of switching systems memory

1.3.1.1

Zero systems memory mismatch achieved

(synchronized)

Review program/project drawings and provide comments; attend vicinity

Meetings

1.3.10.3

Drawing comment response—No more than one instance exceeding 10 working days

No more than one unexcused meeting absence

Update work center records after completion of new task/work orders

1.3.12

1.3.13

No more than two instances exceeding two days

No more than one work-center record update error

Comply with established timeframes for completion of work orders

Routine - 10 duty days

Priority - 3 duty days

Emergency - 4 hours

1.4.1.3.1

1.4.1.3.2

1.4.1.3.3

Routine – Two instances exceeding 10 duty days

Priority – Zero instances exceeding 3 duty days

Emergency – Zero instances exceeding 4 hours

Performance

Objective

PWS

Reference

Performance

Threshold (Monthly)

Update the CVC by recording manhole location and communication feature information

1.3.3.3.3 Update the CVC to record the correct manhole

location and descriptive information for splices, cables, ducts and other communication features within manholes specified in PWS reference.

No more than one instance of incorrect information submitted for government review.

Update the CVC by recording descriptive information for the terminals

1.3.3.4 Update the CVC to record the correct location

and descriptive information for terminals specified in PWS reference.

No more than one instance of incorrect information submitted for government review.

Update the CVC by recording descriptive information for

Distribution Pedestal Terminals

1.3.3.5 Update the CVC to record the correct location

and descriptive information for distribution pedestal terminals specified in PWS reference.

No more than one instance of incorrect information submitted for government review.

Accurately locate communication feature, collect CFD, and record

CFD in the CVC database

1.3.5.1 No more than 2 instances of exceeding 4 duty

days to record CFD in the CVC.

No more than one instance of not accurately locating communication features.

2.1 Inspection of Services.

The Government has the right to inspect all services called for by the contract (SDS and Non-

SDS items), to the extent practicable at all times and places during the…