02_Attachment_02_-_McConnell_BTS_PWS_22Feb17.pdf

PERFORMANCE BASED WORK STATEMENT (PWS)

FOR

OPERATIONS AND MAINTENANCE SERVICES

BASE TELECOMMUNICATIONS SYSTEM (BTS)

AT

McCONNELL AIR FORCE BASE KANSAS

Updated: 22 February 2017

BTS Services

FA4621-17-R-0004

Performance Work Statement 22 February 2017 Attachment 02

Table of Contents

1.0. DESCRIPTION OF SERVICES/GENERAL INFORMATION

1.1. Scope of Work

1.2. Operate and Maintain (O&M) Requirements

1.2.1. Telephone Switch System O&M

1.2.2. Perform Inside Plant (ISP) and Outside Plant (OSP) Maintenance O&M

1.2.3. Preventive Maintenance Inspections (PMIs)

1.2.4. System and Service Outages and Trouble Calls/Tickets

1.2.5. Alarm Notification

1.2.6. Cable Location, Staking, and Marking

1.2.7. System Cross-Connect and Disconnect Services

1.2.8. Call Accounting System (CAS)

1.2.9. Voice Mail

1.2.10. Voice Protection System (VPS)

1.2.11. Traffic Measurement and Analysis

1.2.12. Contractor Support Services

1.2.13. Technical Solutions

1.2.14. BTS Work Center Records

1.3. Work Order Requirements

1.3.1. Work Order Procedures

1.3.2. Work Order Classifications

1.3.3. Required Information on Work Orders

1.3.4. Work Orders Subject to the Construction Wage Rate (CWR) Requirements

Statute

1.3.5. Submittal of Completed Work Orders

1.4. Special Project Requirements

2.0. SERVICE SUMMARY (SS)

2.3. COR MONTHLY REPORT

2.4. PERIODIC PROGRESS MEETINGS

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

4.0. GENERAL INFORMATION

4.1. HOURS OF OPERATIONS

4.2. MILITARY EXERCISES

4.3. HOLIDAYS

BTS Services

FA4621-17-R-0004

4.4. PERFORMANCE OF SERVICES DURING CRISIS DECLARED BY THE

NATIONAL COMMAND AUTHORITY OR OVERSEAS COMBATANT

COMMANDER

4.5. CONTRACT MANAGEMENT

4.6. ENVIRONMENTAL COMPLIANCE

4.7. CONTRACT EMPLOYEES

4.8. SECURITY REQUIREMENTS

4.9. INTERFACES

4.10. SAFETY REQUIREMENTS AND REPORTS

4.11. REPORTS AND RECORDS

4.12. LABOR HOUR REPORTING

5.0 APPENDICES

APPENDIX 5.1 - WORKLOAD ESTIMATES

APPENDIX 5.2 - ITEMS TO BE MAINTAINED BY THE CONTRACTOR

APPENDIX 5.3 - GLOSSARY AND ACRONYMS

APPENDIX 5.4 - VOICE SWITCHING SYSTEM (VSS) SUSTAINMENT

APPENDIX 5.5 - APPLICABLE DOCUMENTS

APPENDIX 5.6 – GLOBAL POSITIONING SYSTEM SERVICE DOCUMENTS

BTS Services

FA4621-17-R-0004

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 22d

Communications Squadron at

McConnell Air Force Base, Kansas 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 within the scope of this requirement as 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 to include VOIP, the outside plant

(OSP) and inside plant (ISP) systems, network, transmission systems, and all associated equipment described in Appendix 5.2, which may include other systems (e.g. radio, etc.). The

Contractor shall operate and maintain all BTS equipment and systems in accordance with (IAW) the Original Equipment Manufacturers’ (OEM) technical manuals and specifications, Department of Defense (DoD) and US Air Force (AF) policy and regulations, applicable federal, state, and local laws and regulations. The contractor is expected to use innovative solutions to effectively accomplish PWS requirements in a timely manner at reduced costs and in a way that fosters pride and ownership.

1.2. 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.2.14 BTS Work Center

Records) and the OEM’s recommended procedures. Appendix 5.2 identifies Government

Furnished Material (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.3. 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.2.1. Telephone Switch System O&M.

The Contractor shall operate and maintain the system(s) identified in Appendix 5.2. The

Government will measure the acceptable standard performance level by a determination of the total systems availability (up time) and reliability rating during any given month. All

BTS Services

FA4621-17-R-0004

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. Demarcation of

VoIP maintenance shall not extend beyond the Voice Gateway and Power Ethernet Switches(s).

See Paragraph 4.8 for security requirements.

1.2.2. Perform Inside Plant (ISP) and Outside Plant (OSP) Maintenance O&M.

Contractor shall maintain ISP and OSP cable and equipment as identified in Appendix 5.2 and

IAW applicable documents listed in Appendix 5.5 of this PWS.

1.2.3. Preventive Maintenance Inspections (PMIs).

Contractor shall perform PMIs as required on all systems covered in Appendix 5.2 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.2.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. Each power system shall be tested IAW OEM specifications. Test results shall be documented IAW PWS section 1.2.14.

1.2.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 Dial Central

Office. These PMI tests are to be accomplished quarterly. Test results shall be documented

IAW PWS section 1.2.14.

1.2.3.3. Manholes and/or Handholes. The Contractor shall inspect five COR-accepted manholes and/or Handholes per month under the O&M portion of this contract. Additional inspections (over five each) shall be accomplished as a work order IAW PWS section 1.3. If the Contractor is working in a manhole not scheduled for a PMI, the Contractor must correct any discrepancies before the job is considered complete. Then, the manhole will be counted in the monthly PMI schedule. The Contractor shall inspect each manhole/handhole for the following discrepancies and correct as required:

All cables will be identified and tagged. At each splice, tags will be placed on each side of the

FA4621-17-R-0004

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.2.3.4. Building Entrance Terminals. The Contractor shall inspect six COR identified terminals per month. Additional inspections (over six each) shall be accomplished as a work order IAW PWS section 1.3. 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.2.3.5. Distribution Pedestal Terminals. The Contractor shall inspect six COR accepted distribution pedestal terminals per year. The Contractor is responsible for ensuring inspections occur within the year regardless of weather conditions. Additional inspections (over six) shall be accomplished as a work order in accordance with PWS Section 1.3. 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 actions.

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

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

Update the CVC database with descriptive information.

1.2.3.6. Cable Analysis. The Contractor shall review TMS records quarterly and perform

FA4621-17-R-0004

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.2.4. System and Service Outages and Trouble Calls/Tickets.

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

1.2.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.2.14 (work center records).

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

Comm Focal Point (CFP) & COR on the corrective action and close the trouble ticket. The

Contractor shall co-ordinate with base CFP/COR to restore any Internet Protocol (IP) phone set outages. The Contractor shall log the outage IAW the guidance in PWS section 1.2.14

(work center records). Outage/trouble call categories are further defined as:

1.2.4.3.1. Emergency. Contractor shall respond on-site within two hours 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 CFP may declare the outage/trouble as an Emergency. Emergency outages/troubles are classified as any of the following:

BTS Services

FA4621-17-R-0004

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.2.4.3.2. Priority. Contractor shall respond on-site within six hours and restore service as soon as possible, but shall not exceed three normal duty 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.2.4.3.3. Routine. Contractor shall respond on-site within 24 hours and restore service as soon as practicable but not to exceed five normal duty days unless otherwise approved by the

COR in writing. Expedition of parts and/or labor is not required. Routine outages/troubles are any other outage(s) not included in the above categories.

1.2.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.2.5. Alarm Notification.

Contractor shall comply with the details of its alarm notification method as documented in the

Contractor’s Maintenance Support Plan (MSP). Alarm notification shall not interfere with any Government-owned system. Alarm notification of the switch system(s) shall not require

BTS Services

FA4621-17-R-0004

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 authorized, but must be disconnected when not in use. 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 Instruction (AFI) 33-111, Section G.

1.2.6. Cable Location, Staking, and Marking.

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

Marking shall be within three feet of the actual location at ten-foot intervals and at direction changes. The marking shall begin two feet from the point of entry into the work area and shall continue two feet past the point of exit from the work area. Contractor shall complete location, staking and marking within the specified time listed below from the time the COR advises the

Contractor of the requirement unless additional time is permitted by the COR. The Contractor shall document time extensions in writing, which includes the signatures of the COR and the

BTS project manager. Communication Feature Data (CFD) collection shall be accomplished via work order. See the Equipment and Installation Performance Specification (EIPS), as attached to the basic contract, and corresponding line item on the price list when directed to collect CFD data by the COR. The Contractor shall comply with the following timelines for location, staking, and marking:

Emergency: Within two hours of notification

Priority: Within six hours of notification.

Routine: Within three business days of notification.

1.2.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 Dial Control Office (DCO)), shall be included as part of the

O&M service.

1.2.8. Call Accounting System (CAS)

The Contractor shall operate and maintain the CAS. This includes monthly storage and output of records. The Contractor is not responsible for input, manipulation, or analysis of data. The demarcation point will be at the switch port UCALL.

1.2.9. Voice Mail.

The Contractor shall provide voice mail O&M. This includes, but is not limited to:

BTS Services

FA4621-17-R-0004

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; proper functioning of the auto attendant feature and system backup. Functions also include diagnostic, maintenance, and minor programming changes on current software applications. System backup shall include backup of system configuration, names, and print “list all” of database.

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

1.2.11. Traffic Measurement and Analysis.

The COR may request up to four 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.2.12. Contractor Support Services.

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

1.2.12.1. Contractor Support for Government Engineering and Installation.

The Contractor shall provide technical support to include an interchange of information on technical parameters and capabilities of the BTS; location and identification of building terminals and communication rooms; and verification of cable record information as directed by the COR or CO. These efforts include setting of equipment options to determine proper operational conditions; restoration of service to existing equipment; establishment of service to new facilities; establishment of service for existing facilities under renovation; transfer from one system to another system; and support of hardware and software upgrades.

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

1.2.12.3. Workload/Status Meetings. The BTS Manager shall attend local meetings with the

COR(s), Communications Squadron Plans Office, and/or CO to discuss status of current and future work orders, trouble tickets, outages, PMIs, or any other work/event that may impact

BTS Services

FA4621-17-R-0004

contractual performance as required. The Contractor shall provide a list of work orders, trouble tickets, etc. at the meeting for reconciliation and discussion with the COR(s), Contracting

Officer, or other personnel (approved by the CORs or CO).

1.2.12.4. 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 design review meetings as required.

1.2.13. Technical Solutions.

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

1.2.14. BTS Work Center Records.

Contractor shall develop and maintain BTS work center records. The Contractor shall update work center records within two normal duty days after completion of the associated task(s) unless specified differently within this section. All BTS records and documents established and maintained by the Contractor are Government property and shall remain at the site and turned over to the COR for disposition upon contract completion. Failure to do so may result in withholding of final payment until all records are recovered or in a reduction in final payment for records lost or misplaced. The Government requires electronic maintenance and storage of records, unless otherwise specified herein. The Contractor shall identify all acronyms, codes, abbreviations, signs and symbols used in each record. The Contractor shall use the same format for initial and all subsequent submissions of the same record unless otherwise approved by the

CO. All records shall be readily available for review by the COR and CA, and other personnel

(authorized in writing by the CO). The Contractor shall update all errors found or identified during review of the work center records. Contractor shall develop, update and/or maintain accurate, complete, and readable work center records as listed below:

1.2.14.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 work days after the effective change (e.g. modification adding equipment) unless otherwise requested by

BTS Services

FA4621-17-R-0004

the CO (e.g. with the proposal to add new equipment to maintenance). The

Government/COR will review and approve, or provide the Contractor with required corrections. Changes may be implemented only after CO approval. The MSP shall contain as a minimum: a schedule of PMIs due on each piece of equipment being maintained

(Appendix 5.2) for the life of the contract IAW equipment manufacturer’s recommendations;

alarm notification procedures; and specific maintenance tasks to be performed on each system.

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

1.2.14.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 a discrepancy was reported (start time); short description of the discrepancy;

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

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

For scheduled outages, also include the Government authorization.

1.2.14.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.2. The Contractor shall update the Cyberspace Infrastructure Planning System (CIPS) Visualization Component

(CVC) database with pertinent CFD information gathered during the inspections. The record shall be available for inspection and analysis by the Government. If other electronic documentation is implemented, the Contractor shall grant the Government access to those records.

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

BTS Services

FA4621-17-R-0004

the purpose of test/inspection; complete identification of item tested/inspected and test equipment used; complete description of the physical set-up (e.g., item, facility, and equipment used); complete description of procedures used; copy of results/analysis; actual recorded data

(e.g., instrument readings) (if extensive, provide as an appendix); conclusions and recommendations; and authentication of results and acceptability. The Contractor shall update the CVC database with pertinent CFD information resulting from installation or repair.

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

1.2.14.6.1. New Developments for Maintaining CSIR Drawing Records. The Air Force has implemented the Cyberspace Infrastructure Planning System (CIPS) Visualization Component

(CVC). It changes the method of developing, maintaining, and editing information historically contained in installation drawings (CSIRs) from a Computer Aided Design and Drafting

(CADD) process to a Geographic Information Systems (GIS) process that interfaces with the

Geobase initiative and provides an Air Force portal accessible, enterprise-wide database structure suitable for storing, visualizing, editing, and analyzing base-level communications and information systems infrastructure. At this time, CVC is not designed to store inside plant information. Until such time as the CVC has standard provisions for recording inside plant information, inside plant record drawings shall be maintained in Base’s existing drawing record systems. The Contractor shall coordinate with the Base CSIR Manager, and develop and maintain CSIR IAW AFI 33-101, TO 00-33A-1001, and TO 00-33D-3003.

1.2.14.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-101and TO 00-33A-1001. Contractor shall transfer to the CVC database all pertinent outside plant CFD information from administrative and maintenance

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

Contractor shall update the CVC database with outside plant information from as-built drawings or other pertinent documents or electronic data pertaining to work done by third parties (organic or 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.2.14.18. When the update is completed, the Contractor

BTS Services

FA4621-17-R-0004

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.2.14.6.3. Inside Plant Drawing Records. The Contractor shall maintain Inside Plant

Drawing records in hardcopy as directed by the CSIR Manager. 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. 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.2.14.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.2.14.6.5. This expands on the guidance provided in Paragraph 1.2.14.6 above. (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.2.14.6.5.1. Contractor and Third Party as-built drawings submitted to the CSIR Manager will be in VISIO, or CVC format as directed by the COR. The Contractor shall provide correctly

BTS Services

FA4621-17-R-0004

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.2.14.6.5.2. The Contractors will produce drawings to support engineering initiatives.

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

1.2.14.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.2.14.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.2.14.8. Price List/PID Utilization Record. The Contractor shall produce and maintain an electronic record of the Price List Items/Product IDs (PIDs), ordered under the contract. The record shall include: the Price List Item, or PID number; description; and quantities of each item. The record shall exclude price information. Contractor shall update this record within two days of work order completion.

1.2.14.9. AF Logistics Support Spares Records (Inventory). Contractor shall maintain the

AF Logistics Spares records in the on-site work center. The COR will provide the initial inventory to the Contractor for maintenance. Records include spares inventory list and spares replacement log. Spares inventory list shall include, as a minimum, Product Engineering Code

(PEC), serial number, description, quantity, and vendor. Spares 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.2.14.10. Contractor-Furnished Hazardous Material. The Base Material Manager is responsible for documenting and keeping record of all Hazardous Materials. The Contractor shall send a list of all hazardous material used/brought on to the government facility, and send them to the local Material Manager (22 CE/CEIEC). Contractor shall provide location, quantity and name of hazardous material to Material Management.

1.2.14.11. Equipment Inventory Records (PWS Appendix 5.2). The Contractor shall

FA4621-17-R-0004

maintain a working copy of Appendix 5.2. Appendix 5.2 shall identify equipment installed, changed, or removed via contract modification or the work order process identified in PWS section 1.3. 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.2.14.12. Telecommunications Management System (TMS). The Contractor shall perform daily record updates using TMS. Some updates may require the Contractor to manually enter the data upon completion of individual work orders or record changes.

Contractor shall maintain cable pair assignment records and E-911 database using TMS.

1.2.14.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) work days after completion of the task(s) specified on individual work orders and notify

COR in writing. Physical records of work orders in process shall be retained and available locally (on- base). Electronic storage of completed (accepted by the COR) is acceptable and preferred.

Paper copies of completed work orders may be destroyed by using a cross cut shredder to prevent unauthorized disclosure after electronic storage is complete.

1.2.14.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 work days from occurrence of

Traffic Measurement analysis.

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

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

BTS Services

FA4621-17-R-0004

1.2.14.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.2.14.17. Call Accounting System (CAS). The Contractor shall gather and electronically store records output from the CAS as formatted by Unique/Ucall -32 system. The Contractor shall make stored records available to the COR.

1.2.14.18. 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.2.14.6 and Appendix 5.6

(for any GPS requirement).

1.2.14.18.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.2.14.18.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.2.14.18.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.2.14.18.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

BTS Services

FA4621-17-R-0004

accuracy.

1.2.14.18.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.2.14.18.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.2.14.18.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.

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

1.2.14.18.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.2.14.18.2.1.

1.2.14.18.2.1.4. Calculation worksheets showing compliance with National Standard for Spatial

Data Accuracy (NSSDA) statement at the 95% confidence level as required by Paragraph

1.2.14.18.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.2.14.18.2.1.5. Geospatial data shall overlay on the installation’s most current GeoBase

Common Installation Picture (CIP) provided in the Air Force Porta1 accessible CVC. The collected data will incorporate the datum, coordinate and projection system of McConnell AFB, KS CIP which is: World Geodetic System 1984 (WGS 1984) Universal Transverse Mercator

(UTM) Zone 14 (96 to 102 degrees West, Latitude Band S (32 to 40 degrees North).

BTS Services

FA4621-17-R-0004

Performance Work Statement http://www.fgdc.gov/

1.2.14.18.3. Quality Control. The Contractor shall utilize a topology build and clean routine and assure the Shape files containing CFD have the following:

No erroneous overshoots, undershoots, dangles or intersections in the line work.

Features shall be snapped where applicable, for example, GPS Dbsplice snapped to

GPS Path Segment.

Lines should all be continuous, with no pseudo-nodes. Nodes should only exist where the attributes of a line change.

No sliver polygons.

All polygons completely close and have a single unique centroid.

Digital representation of the common boundaries for all graphic features must be coincident, regardless of feature layer.

1.2.14.18.4. Maintenance of GPS Service Data. CFD shape files, metadata XML files, the quality control report and calculation worksheets validating the NSSDA accuracy statement shall be maintained on site in an orderly manner. Contractor shall make available such documentation to COR, when requested, for review to ensure compliance with GPS service guidance.

1.2.14.18.5. Updating CVC With GPS Collected CFD The Contractor shall store the collected outside plant infrastructure features and communications pathways shape files in the local government provided computer workstation, and shall transcribe information from the local workstation shape file into the CVC database using the CVC Viewer/Editor web-browser application, accessible at https://cipsaf.tinker.af.mil/cips/mycips.aspx or search for CIPS at the

Air Force Portal.

1.3. Work Order Requirements.

The Contractor shall comply with the following requirements. Examples of work orders include, but are not limited to, equipment purchases, installations, removals, or relocations.

Additionally, work orders may include installation or removal of cables/transmission media, as required for new requirements, and follow-on O&M of these equipment items/media. The COR will be notified of any installation found to be incomplete or not installed according to industry standards. The Contractor shall maintain the installed infrastructure and will not be held responsible for completing third party installations or bringing third party installations up to industry standard unless so directed by issuance of a work order or contract modification. The

Equipment and Installation Performance Specification (EIPS) provides detailed descriptions of the material and labor effort (e.g. material, labor, and incidentals for installation, removal, and/or relocation) required by the attached Pricing Table and identified by PIDs. When an item

BTS Services

FA4621-17-R-0004

required to complete a work order is not pre-priced within the Pricing Table (Contract

Attachment 1), the Government may negotiate the addition of these items, negotiate a special project (PWS Section 1.4), or opt to use another vehicle to accomplish the task.

1.3.1. Work Order Procedures.

1.3.1.1. Work orders shall be primarily prepared by the Contractor; however, CORs shall have the option to prepare work orders. Work orders prepared by the Contractor shall be approved by the COR before work starts. All work orders shall be prepared via Microsoft Access database or equivalent form. Work order numbers shall be established by the COR. If necessary, the

Contractor shall walk-through the proposed work site to ensure understanding of the work to be performed. The Contractor may be accompanied by Government personnel.

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

Contractor shall refer any questions, concerns, or disputes concerning work orders to the COR in writing within 24 hours (two hours for emergencies) of receipt of the work order. In the case of misunderstanding or concern, the Contractor does not have the right to reject work orders.

Should questions, concerns, or disputes occur, the Contractor shall continue work while elevating to the CO in writing for direction/resolution.

1.3.1.3. Work orders will be accomplished during normal duty hours; however, occasions may arise that require work to be accomplished outside of these hours. The Contractor shall be responsible for covering such situations with adequate personnel and completing the work within the stipulated time.

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

The 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 or CO, with appropriate justification. Failure to obtain materials due to supplier delay is not typically considered an adequate reason for an extension. All cable cut repairs shall be classified as emergency unless determined otherwise by the

COR.

Routine. Complete within 10 duty days

Priority. Complete within three duty days

FA4621-17-R-0004

Emergency. Respond on work site within four hours and complete work as soon as possible upon approval. The COR may provide initial notification to the Contractor verbally, with a written follow-up within two hours.

The Contractor will keep the COR apprised of emergency work order status.

1.3.3. Required Information on Work Orders.

Work orders placed under the contract will contain the following information as a minimum:

Date of preparation.

Contract number, Task Order number, and work order number.

Price List Item/PID, description, quantity ordered, building number, room number, and contract unit and extended prices and total Not to Exceed (NTE) price.

The work order priority and established completion time.

A statement that “Changes to work orders, as permitted by the terms within this PWS, shall reflect mutual agreement by attaching supporting documentation; signatures of the

COR and Contractor; and dates of signatures”.

When complete, a stamp or other text block indicating customer acceptance, Contractor initials and dates of completion for work and applicable work center records.

Any other pertinent information required to properly document work performed. To include, but not limited to customer POC and contact info, associated Telephone Control

Officer (TCO), etc. Include the statement “Invoice Work Order against Funding

CLIN(s) & items from Pricelist” prior to work order approval.

1.3.4. Work Orders Subject to the Construction Wage Rate (CWR) Requirements Statute.

The COR is authorized to place work orders directly with the Contractor for all Price List

Items/PIDs. The Contractor shall identify work orders where the CWR applies on the face of the work order.