Attachment_1-_PWS_Nellis-Creech_Sept_2014.pdf

PWS-10-001 – Sept 2014 Nellis & Creech AFB

PERFORMANCE BASED WORK STATEMENT (PWS)

FOR

OPERATIONS AND MAINTENANCE SERVICES

BASE TELECOMMUNICATIONS SYSTEM (BTS)

AT

NELLIS & CREECH AFB NV

1.0. DESCRIPTION OF SERVICES/GENERAL INFORMATION

1.1. SCOPE OF WORK

1.2. GENERAL REQUIREMENTS

1.2.1. Continuation of Mission Essential Services

1.2.2. Accident/Incident Reporting and Investigation

1.2.3. Sub-Contractor Compliance

1.2.4. Base Civil Engineering Digging/Trenching Clearance Requests

1.2.5. Personnel

1.2.6. Personnel Listing

1.3. OPERATE AND MAINTAIN (O&M) REQUIREMENTS

1.3.1. Telephone Switch System O&M

1.3.2. Perform ISP and OSP O&M

1.3.3. Preventive Maintenance Inspections (PMIs)

1.3.4. System and Service Outages and Trouble Calls/Tickets

1.3.5. System or Switch Alarm Notification

1.3.6. Cable Location, Staking, and Marking

1.3.7. System Cross-Connect and Disconnect Services

1.3.8. Call Accounting System (CAS)

1.3.9. Voice Mail

1.3.10. Voice Protection System (VPS)

1.3.11. Automatic Call Distribution (ACD) System

1.3.12. Traffic Measurement and Analysis

1.3.13. Contractor Support Services

1.3.14. Technical Solutions

1.3.15. BTS Work Center Records for Nellis/Creech

1.4. WORK ORDER REQUIREMENTS

1.4.1. Work Order Procedures

1.4.2. Work Order Classifications

1.4.3. Required Information on Work Orders

1.4.4. Work Orders Subject to the Davis Bacon Act

1.4.5. Submittal of Completed Work Orders

1.5 SPECIAL PROJECT REQUIREMENTS

1.6.1. CONTRACTOR’S QUALITY CONTROL PROGRAM

1.6.2. SECURITY

1.6.3. SAFETY, SECURITY, AND ENVIRONMENTAL MEETING

1.6.4. OVERTIME

2.0. SERVICE DELIVERY SUMMARY (SDS)

2.1. INSPECTION OF SERVICES

2.2. NON-COMPLIANCE

Attachment 1- PWS Nellis-Creech September 2014

2.2.2 CONTRACT DISCREPANCY REPORT (CDR)

3.0. GOVERNMENT-FURNISHED PROPERTY AND SERVICES

3.1. AIR FORCE-PROVIDED SPARES\CONTACTOR LOGISTIC SUPPORT

3.2. BASE SUPPORT

3.3. GOVERNMENT SUPPORT FOR CVC EFFORTS

APPENDIX 5.2.A

NELLIS AFB

5.2.A ITEMS TO BE MAINTAINED BY THE CONTRACTOR

APPENDIX 5.2.B

CREECH AFB ................................................................................................ ERROR! BOOKMARK NOT DEFINED.

5.2.B ITEMS TO BE MAINTAINED BY THE CONTRACTOR ................... ERROR! BOOKMARK NOT DEFINED.

APPENDIX 5.3 - GLOSSARY AND ACRONYMS

APPENDIX 5.4 - VOICE SWITCHING SYSTEM (VSS) SUSTAINMENT

APPENDIX 5.5 - APPLICABLE DOCUMENTS

APPENDIX 5.6 – GLOBAL POSITIONING SYSTEM SERVICE DOCUMENTS

Attachment 1- PWS Nellis-Creech September 2014

1.0. DESCRIPTION OF SERVICES/GENERAL INFORMATION

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 99th Communications Squadron at Nellis AFB and 799th Communications Squadron at Creech AFB, Nevada by providing highly reliable wired telecommunications and networked voice, video, and data services. The Contractor shall perform Operation and Maintenance (O&M) and other services required to ensure the Base Telecommunications System (BTS) is available 24 hours per day, 7 days per week. Key personnel are required to be on site during normal duty hours from 0730 to 1630 i.e.

site manager, switch technician. The BTS consists of the base telephone system switch, the cable plant (OSP) and inside plant (ISP) systems, network, transmission systems, and all associated equipment described in Appendix 5.2, which may include other systems (e.g. 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 U.S. Air Force (USAF) policy and regulations, applicable federal, state, and local laws and regulations.

NOTE: Rights of the Government to perform function with its own personnel during periods of disaster, war and other identified emergencies or situations to meet mission needs.

1.2. General Requirements.

1.2.1. Continuation of Mission Essential Services.

IAW Defense Federal Acquisition Regulation Supplement (DFARS) clause 252.237.7023, it is determined that the O&M services in PWS paragraphs 1.3.2 and 1.3.3 are essential for Contractor performance during a crisis situation. In the event of a crisis, additional areas may be identified by the CO. The Contractor may be required to support base mission changes; major or minor BTS infrastructure modifications; and other support requirements necessary for the BTS to meet mission requirements. Base exercises or actual ongoing base security events frequently interrupt missions. Support requirements may originate from technology changes, hardware and software systems upgrade, reconfigurations, new or additional equipment, local area network (LAN) cable installations and upgrade, and Dial Central Office (DCO) reconfigurations. This includes routing/diversity requirements and any other environmental changes that could impact or alter the BTS.

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 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 Contracting Officer (CO). If the Government elects to conduct an investigation of the incident, the Contractor shall cooperate fully with the COR, CO, and other Government investigation personnel until the investigation is completed.

1.2.3. Sub-Contractor Compliance.

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

1.2.4. Base Civil Engineering Digging/Trenching Clearance Requests.

The Contractor shall prepare and coordinate a Base Civil Engineering Work Clearance Request, AF Form 103, prior to any trenching, digging, manhole or hand hole entry. 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.4.1 Base Civil Engineering Facility Clearance/AF Form 332.

The customer (normally building custodian) will be required to submit an approved document (i.e. clearance letter, email or memo) by Civil Engineering (CE) and uploaded to the Work Order Management System (WOMS) for any requirement that is expected to involve any penetration or disturbance of the surface, walls or ceiling.

1.2.5. Personnel.

The Contractor is solely responsible for ensuring sufficient personnel are assigned to this contract and all personnel are qualified and certified to perform the requirements listed herein, including those qualifications and certifications required by the OEM 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. Personnel Listing.

Contractor shall provide a personnel listing and contact information to the Lead COR prior to commencing work and update information on a continual basis to ensure accuracy for the life of the contract. Contact information shall include recall personnel for duty and non-duty periods to cover situations such as emergencies. All personnel shall be proficient in understanding, reading, writing, and speaking the English language. The personnel information shall list the employees’ names, function they support, and whether they are supporting O&M or work orders.

1.2.7. Contractor Identification.

Contractor employees shall identify themselves as contractor personnel by introducing themselves or being introduced as contractor personnel and displaying distinguishing badges or other visible identification for meetings with Government personnel. In addition, contractor personnel shall appropriately identify themselves as contractor employees in telephone conversations and in formal and informal written correspondence.

1.3. Operate and Maintain (O&M) Requirements.

Overall responsibility to properly operate and maintain the BTS shall rest with Contractor as described by the maintenance support plan (MSP) (See PWS section 1.3.15.1, BTS Work Center Records) and the OEM’s recommended procedures. Appendix 5.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.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 1.4. The Contractor shall not postpone or otherwise delay O&M efforts to accomplish work orders. The Contractor is responsible for completing both O&M and work orders simultaneously to ensure contractual timelines are met for both.

1.3.1. Telephone Switch System O&M.

The Contractor shall operate and maintain the system(s) identified in Appendix 5.2/5.2.B. 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. O&M shall also include Voice over Internet Protocol (VoIP) operations as part of the BTS. VoIP equipment is identified in Appendix 5.2/5.2.B. Demarcation of VoIP maintenance shall not extend beyond the end instrument and Ethernet ports of the switching equipment identified as the host and remote switches in Appendix 5.2/5.2.B

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

1.3.2. Perform ISP and OSP O&M.

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

1.3.3. Preventive Maintenance Inspections (PMIs).

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. Contractor shall correct deficiencies IAW the paragraphs below.

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

1.3.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 1.3.15.5.

1.3.3.3. Manholes and/or Handholes. The Contractor shall inspect at both locations of Nellis/Creech, two (2) each COR-accepted manholes per month under the O&M portion of this contract. Additional inspections (over 2 each) shall be accomplished as a work order IAW PWS section 1.4. If the Contractor is working in a manhole not scheduled for a PMI and discovers discrepancies during performance, the Contractor must notify the COR before job is complete.

The discovered discrepancy will not 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 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.

1.3.3.4. Terminals. The Contractor shall inspect at both locations of Nellis/Creech, two (2) COR-accepted terminals per month. Additional inspections (over 2 each) shall be accomplished as a work order IAW PWS section 1.4. The Contractor shall inspect each terminal for the following discrepancies and correct as required:

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

Update the CVC database with descriptive information.

1.3.3.5. Distribution Pedestal Terminals. The Contractor shall inspect at both locations two

(2) COR-accepted Distribution Pedestal terminals per month. Additional inspections (over 2 each) shall be accomplished as a work order IAW PWS section 1.4. 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.

1.3.3.6. Cable Analysis. The Contractor shall review Telephone Management System (TMS) records quarterly and perform Copper/Fiber Optics 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.

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

1.3.4.1. Contractor Availability. The Government shall be able to contact Contractor personnel 100% of the time based on the updated personnel list or recall roster provided on a monthly basis. 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.

1.3.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 1.3.15 (work center records).

1.3.4.3. Nellis/Creech 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. The Contractor shall restore services in the priority order determined by the COR. The Restoration Priority Lists (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 the sequence/repair action. The Contractor shall coordinate with base Network Control Center (NCC)/Identified work center to restore any Internet Protocol (IP) phone set outages. (note the contractor will not work on any network equipment) The Contractor shall log the outage IAW the guidance in PWS section 1.3.15 (work center records). Outage/trouble call categories are further defined as:

1.3.4.3.1. Emergency. Contractor shall respond on-site within one (1) hour 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 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 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

1.3.4.3.2. Priority. Contractor shall respond on-site within four (4) hours and restore service as soon as possible, but shall not exceed two (2) 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 5.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

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

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

1.3.5. System or Switch 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 Air Force Manual 33-145, and DISA STIG Voice and Voice Over IP.

1.3.6. Cable Location, Staking, and Marking.

The Contractor shall locate, stake, and mark up to 25,000 (Creech)/50,000 (Nellis) feet of encased or direct buried/underground 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. Communication Feature Data (CFD) collection shall be accomplished via work order. See EIPS and Contract Line Item Number (CLIN) X008 when directed to collect CFD data by the COR. The Contractor shall comply with the following timelines for location, staking, and marking:

Emergency: Within one (1) hour of notification Priority: Within 16 duty hours of notification.

Routine: Within five (5) duty days of notification.

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

1.3.8. Call Accounting System (CAS).

The Government is responsible for O&M of the CAS workstations and CAS software. The Contractor shall provide support for the Voice Switching System (VSS) System Message Detailed Recording (SMDR) and the output formatting records for CAS integration. The Contractor shall also provide support on the VSS for CAS troubleshooting.

1.3.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 maintenance includes backup of system configuration, names, and print “list all” of database.

1.3.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 or MCCC.

1.3.11. Automatic Call Distribution (ACD) System.

The Contractor shall provide O&M for the ACD system installed under the TelMod program which will be identified under Appendix 5.2. 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.

1.3.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 information required by the contract must cover no less than a five-day period, (Monday-Friday, excluding holidays). The Government may also request measurement and analysis for a particular line or group of lines.

1.3.13. Contractor Support Services.

The Contractor shall comply with FAR 9.505, Conflict of Interest, IAW support services.

1.3.13.1. Contractor Support for Government. The Contractor shall provide technical advice to include an interchange of information on parameters and capabilities of the BTS. Information shall include equipment location, identification of building terminals, cables and communication rooms.

1.3.13.2. Contractor Interface and Support for other Vendors. The Contractor shall cooperate, share and exchange routine or available technical and system equipment interface information with other vendors as directed by the COR or CO. This work may include programming of the base telephone switch to existing equipment; transfer from one system to another system; and support of hardware and software upgrades.

1.3.13.3. Nellis/Creech Workload/Status Meetings. The BTS or site Manager shall attend up to four (4) 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) and/or Contracting Officer.

1.3.13.4. Nellis/Creech Design Review Meetings. The Contractor shall review program or project drawings and provide comments concerning communications requirements within ten 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 four (4) design review meetings per month with the 99th Com Squadron for communication services.

1.3.14. Site Surveys.

Contractor shall perform detailed/in-depth technical solutions for work intended to be performed under this contract upon receipt of a written request from the COR. The site surveys 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 1.4. The Contractor shall provide the proposed solution to the COR within two (2) working days from receipt of requirement unless a longer period is agreed to by the COR and documented on the requirement.

1.3.15. BTS Work Center Records for Nellis/Creech.

Contractor shall develop and maintain BTS work center records. The Contractor shall update work center records within two duty days after completion of the associated task(s). 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. In the event of lost or misplaced records, there will be a reduction in final payment. 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 within two duty days. Contractor shall develop, update and/or maintain accurate, complete, and readable work center records as listed below:

1.3.15.1. Maintenance Support Plan (MSP). The MSP shall enable the scheduling and tracking of preventive maintenance actions on Contractor-maintained equipment. This record shall be available within 30 calendar days after period of performance begins. When changes occur that affect the MSP, revisions shall be submitted within 10 duty days after the effective change. The Government will review and approve recommended changes or provide the feedback to the Contractor. If corrections are required, Contractor has two (2) duty days to correct. 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 (Appendix 5.2/5.2.B) for the life of the contract IAW equipment manufacturer’s recommendations; alarm notification procedures; and specific maintenance tasks to be performed on each system.

1.3.15.2. PMI Inspection/Outage Records. PMI Inspection records shall, at a minimum, contain: the date and time; a short description of inspection, outages or problems; list equipment data, serial number, etc.; the corrective action taken by the Contractor and the initials of the technician.

1.3.15.3. 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 reported (start time); short description; 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.

1.3.15.4. 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 1.3 and identified in Section 1.4. 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 (other than identified Government CIPS system).

1.3.15.5. 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 cable identification and test equipment used; identify complete description of the physical set-up (e.g., item, facility, and equipment used); copy of results/analysis; actual recorded data (e.g., instrument readings) (if extensive, provide as an appendix); corrective actions, conclusions and recommendations (solution and costing); and authentication of results and acceptability delivered to COR upon request. The Contractor shall update the CVC database with pertinent CFD information resulting from installation or repair.

1.3.15.6. Communications and Information Systems Installation Record (CSIR).

1.3.15.6.1. New Developments for Maintaining CSIR Drawing Records. 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 Drawing and Design (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 AFI 33-101, TO 00-33A-1001, TO 00-33D-3004 and TO 00- 33D-3003.

1.3.15.6.2. 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 AFI33-10, to 00-33D-3003, TO 00-33D-3004and 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. For previously documented duct and duct bank GPS coordinates, Contractor shall use these coordinates to update CVC for newly installed cable into the duct or duct bank path. 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 Contractor) 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 Contractor-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

1.3.16.19. 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 Contractor’s Live Direct Session Edit by inspecting each feature added or modified during the Live Direct Edit Session. The CSIR Manager will notify the Contractor of each feature that was rejected during the quality control approval process in order for the Contractor to take corrective action.

1.3.15.6.3. Inside Plant Drawing Records. The Contractor shall maintain Inside Plant Drawing records in the format directed by COR. Contractor shall transfer to inside plant drawing records all pertinent inside plant information from administrative and maintenance CSIR, Legacy CSIRs, work orders, inspection records, as-built and as-installed marked-up drawings or other information produced as a result of the Contractor’s operations. The Contractor shall also develop and maintain correct, manually annotated paper copies of changes to the inside plant in addition to the electronic drawing files. Once the CSIR Manager or COR has verified that the Contractor has properly updated the electronic drawing with the annotated changes, the paper copy may be discarded. Color plots of electronic files are acceptable providing they display the same information as a manually marked-up drawing. The Contractor shall update Legacy CSIR drawing records with inside plant 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. The work order process shall also be used for conversion of third party as-built drawings, document, or electronic data information. The Contractor shall not produce new electronic files unless no file exists. In cases when no electronic file exists, the Contractor shall produce a new drawing for ISP permanent drawing records. The Contractor shall also update any associated drawings to incorporate any changes/additions made to a drawing record; for example, if a floor plan has changes, the changes shall also be posted to the equipment data list/face equipment diagram, as applicable.

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

1.3.15.6.5. This expands on the guidance provided in above Paragraph(s).

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

1.3.15.6.5.1. All Contractor and Third Party as-built drawings submitted to the CSIR Manager will be in Microstation J (V7), AutoCAD 2000 format, 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.

1.3.15.6.5.2. Contractor’s will produce drawings to support engineering initiatives.

1.3.15.6.5.3. All electronic submissions shall comply with the following standard:

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

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

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

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

1.3.15.8. 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 and submitted with monthly invoices. The record shall exclude price information.

1.3.15.9. AF Logistics Support Spares Records (Inventory). Contractor shall maintain the AF Logistics Spares records in the on-site work center. Thirty days (30) after award, contractor and COR will conduct a joint initial inventory of all spares identified for use under Appendix

5.3. 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.15.10. 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 Contractor point of contact; emergency phone number; and address or physical location of the Contractor’s on-base field office.

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

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

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

1.3.15.11. Equipment Inventory Records (PWS Appendix 5.2). Thirty days (30) after contract award, a joint inventory shall be accomplished to verify Appendix 5.2/5.2.B. The Contractor shall maintain a working copy. Appendix 5.2/5.2.B 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.

1.3.15.12. Telecommunications Management System (TMS). The Contractor shall perform daily record updates using TMS system used at the base as identified by the COR. Some updates may require the Contractor to manually enter the data upon completion of individual work orders or record changes. Contractor shall also maintain cable pair assignment records using TMS.

1.3.15.13. Work Order Records, Including Warranty Records. The Contractor shall develop and maintain work orders. The Contractor shall update work center records within two (2) duty 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). Notification of completed work orders or warranty records submitted electronically is acceptable and preferred but all paper copies of completed work orders will be returned to the COR office.

1.3.15.14. Traffic Measurement Records.

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

1.3.15.15. System 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 (copper and Fiber). Records shall include each cable and terminated cable count, type of cable (bad and spare), and number of conductors used. Quarterly system capacity records shall be produced for the host switch and remotes. The records shall include total line ports, line ports in use, line port type (analog/digital/ISDN/etc.) total used, and DS-1 digital trunk ports (total ports used and available).

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

1.3.15.17. Call Accounting System (CAS). The Contractor shall gather and electronically store records output from the CAS as formatted by the system identify by the COR.

1.3.15.18. 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 Contractor 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 duty days prior to implementation of those changes.

1.3.15.19. Global Positioning System (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 1.3.15.6 and Appendix 5.6 (for any GPS requirement).

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

1.3.15.19.1.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.5.

1.3.15.19.1.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.5.

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

Geospatial coordinate data for the location of utility lines shall be recorded at a minimum every 50 feet, and each turn or bend in a cable installation pathway must also be recorded so the coordinates for any point along the turn pathway will fall within the allowable accuracy.

1.3.15.19.2 The Contractor shall be responsible for providing all required equipment including software, hardware, and any other tools, labor, and materials necessary to provide CFD on electronic storage media in the specified formats.

1.3.15.19.2.1. The GPS collected CFD attribute, metadata, and location information shall be stored and submitted in an Environmental Systems Research Institute (ESRI) Shape File format.

The shape files must be compatible with the CVC Viewer/Editor web-browser application, currently accessible at https://cipsaf.tinker.af.mil/cips/mycips.aspx . Its format shall be within a folder named the same as the prefix of the shape file. For Example, if the shape file is named "points_lafb_28.shp" the folder would be named "points_lafb_28”. The folder shall contain all the files that make up the general shape file, i.e., “.shp”, “.shx”, “.dbf”, etc. along with the specified metadata file. The shape files shall have a geospatial reference (.prj) file included that specifies the parameters of the coordinate system.

1.3.15.19.2.1.1. The Contractor shall use GPS to determine horizontal position of communication features and will format CFD entry using the entity naming convention, attribute fields and domain values as specified by Table A.6.

1.3.15.19.2.1.2. The Contractor shall collect CFD in GPS data loggers and will use Table A.6 to produce the CFD data dictionary for use in the logger.

1.3.15.19.2.1.3. For each set of CFD collected using GPS, the Contractor shall complete all metadata elements marked mandatory as defined by the FGDC –STD-001-1998 specified in PWS Appendix 5.5. Metadata shall be formatted and stored as an XML document compatible with the submitted shape files and software of the organization specified in Paragraph 1.3.15.19.2.1.

1.3.15.19.2.2. Calculation worksheets showing compliance with National Standard for Spatial Data Accuracy (NSSDA) statement at the 95% confidence level as required by Paragraph

1.3.15.19.1.2 shall be submitted as an Excel (.xls) file. Example calculation worksheets in Excel format can be downloaded from a FGDC website: http://www.fgdc.gov/.

1.3.1…