Attachment 2 - BTS PWS.pdf

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……………………………………………...4

1.1 SCOPE OF WORK……………………………………………………………………………………….4

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.2.7. Contractor Identification

1.2.8. Secuity

1.2.9. Safety, Security and Environmental Meeting

1.2.10. Overtime

1.2.11. Invoicing Instructions Utilizing the Government Purchase Card (GPC)

1.3. SYSTEM AND SERVICE OUTAGES AND TROUBLE CALLS/TICKETS

1.3.1. Contractor Availability

1.3.2. Scheduled Outages

1.3.3. Restoration/Completion of Outages, Trouble Calls/Tickets

1.3.4. System or Switch Alarm Notification

1.4. CONTRACTOR SUPPORT SERVICES

1.4.1. Contractor Support for Government

1.4.2. Contractor Interface and Support for other Vendors

1.4.3. Manhole, Handhole, and Building Terminal Inspection/Maintenance/Repair

1.4.4. Cable/Premise Installation/Repair/Remedy Test Results

1.5. CYBERSPACE INFRASTRUCTURE PLANNING SYSTEM (CIPS)

1.5.1. Maintaining Records

1.5.2. Maintaining CIPS Drawing Records

1.5.3. Inside Plant Drawing Records

1.5.4. Drawings

1.5.5. Electronic Submissions

1.5.6. Equipment Operational Records

1.5.7. CLIN/PID Utilization Record

1.5.8. AF Logistics Support Spares Records (Inventory)

1.5.9. Contractor Furnished Hazardous Material

1.5.10. Equipment Inventory Records (PWS Appendix 5.2/5.4)

1.5.11. Telecommunications Management System (TMS)

1.5.12. Work Order Records, Including Warranty Records

1.5.13. Traffic Measurement Records

1.5.14. System Capacity Records

1.5.16. System Security Audit Record

1.5.17. Call Accounting System (CAS)

1.6. GLOBAL POSITIONING SYSTEM (GPS) SERVICE DATA

1.6.1. Global Positioning System (GPS) Service

1.6.2. Software/Hardware and Tools for Electronic Media

1.6.3. Quality Control

1.6.4. Maintenance of GPS Service Data

1.6.5. Updating CVC with GPS Collected CFD

1.7. WORK ORDER REQUIREMENTS

1.7.1. Work Order Procedures

1.7.2. Work Order Classifications

1.7.3. Required Information on Work Orders

1.7.4. Work Orders Subject to the Davis Bacon Act (DBA) and Service Contract Act (SCA)

1.8. SPECIAL PROJECT REQUIREMENTS

1.8.1. Detailed Proposals

1.8.2. Direct and Indirect Proposal Cost

1.8.3. Proposal PIDs/CLINs

2.0. QUALITY CONTROL

2.1. QUALITY CONTROL PLAN (QCP)

2.2. CONTRACTOR’S QUALITY CONTROL PROGRAM

2.3. INSPECTION OF SERVICES

2.4. NON-COMPLIANCE

2.5.1. Memorandum for Record (MFR)

2.5.2. Contract Action Report (CAR)

2.5. SERVICE DELIVERY SUMMARY (SDS) TABLE

3.0. GOVERNMENT FURNISHED PROPERTY AND SERVICES

3.1. AIR FORCE PROVIDED SPARES/CONTRACTOR LOGISTIC SUPPORT

3.2. BASE SUPPORT

3.3. GOVERNMENT SUPPORT FOR CVC EFFORTS

3.3.1. Computers

3.3.2. CVC Training

4.0. SITE SPECIFIC INFORMATION

4.1. NELLIS AFB

4.1.1. Operate and Maintain (O&M) Requirements

4.1.2. Telephone Switch System O&M

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

4.1.4. Preventative Maintenance Inspections (PMIs)

4.1.5. Contractor Support Services

4.1.6. Site Surveys

4.1.7. BTS Work Center Records for Nellis

4.1.8. Government Furnished Property/Support – Nellis AFB

4.2. CREECH AFB

4.2.1. Operate and Maintain (O&M) Requirements

4.2.2. Telephone Switch System O&M

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

4.2.4. Preventative Maintenance Inspections (PMIs)

4.2.5. Contractor Support Services

4.2.6. Site Surveys

4.2.7. BTS Work Center Records for Nellis

4.2.8. Government Furnished Property/Support – Creech AFB

5.0. APPENDICIES

5.1. Nellis Workload Estimates

5.2. Nellis Contractor Maintained Items

5.3. Creech Workload Estimates

5.4. Creech Contractor Maintained Items

5.5. Glossary and Acronyms

5.6. Voice Switching System (VSS) Sustainment

5.7. Applicable Documents

5.8. Global Positioning System Service Documents

1.0. DESCRIPTION OF SERVICES/GENERAL INFORMATION

1.1. Scope of Work. The Contractor shall provide all personnel, equipment, tools, materials, vehicles, permits, 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 432nd Support Squadron at Creech AFB, Nevada by providing highly reliable telecommunications with the current outside cable plant, telephone voice services, and premise infrastructure. The Contractor shall perform Operation and Maintenance (O&M) required ensuring the Base Telecommunications System (BTS) is available 24 hours per day, 7 days per week. This service contract is not to be used for new construction installing more than one manhole/handhold or when inside plant exceeds 100 new jack locations. Key personnel are required to be on site during normal duty hours from 0730 to 1630 i.e., Site Manager and Telecommunications Mechanics (Switch, Outside Plant (OSP), and Inside Plant (ISP) technicians). At a minimum Contractor shall have a Switch, OSP, and ISP telecommunications mechanics available to respond to both sites simultaneously during duty and after hours. The BTS Contractor shall be responsible for all equipment including VoIP, Time Division Multiplexing (TDM) switches, Enhanced 911 (E911) system, telephone system switches, OSP, ISP systems, network cabling, trunk systems, and all associated equipment described in Appendix 5.2. The Contractor shall operate and maintain all BTS equipment and associated 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: Government Contracting Officer Representative (COR) or appointed Subject Matter Expert (SME) have the right to perform any 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

4.1 and 4.2 are essential for Contractor performance during a crisis situation. In the event of a crisis, additional areas may be identified by the Contracting Officer (CO). Crisis is defined as an emergency such as Active Shooter, events involving the safety and health to Creech AFB or support of the maintaining communication keeping the Airplane in air supporting their mission, E911 services and Primary/Secondary Crash net. 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. (IAW para 1.8) 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, upgrades, 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/report all available facts relating to each instance of accidental Government property damage or Contractor personnel injury, to the COR immediately. If there is injury to person or persons, contact the COR as soon as it is stable and immediate medical need is resolved. The Contractor shall secure the scene of any accident and wreckage until released by the accident investigative authority or Security Forces. 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 and dust permits if required, prior to any trenching, digging, or placement of manhole or handhole. 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. Hydro-excavations is mandatory for Creech AFB any variance to this shall be approved by the CO, CA, or COR/SME prior to any performance of an assigned work order.

1.2.4.1. Base Civil Engineering Facility Clearance. 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 approved Data Base system for task/repair orders for any requirement that is expected to involve any penetration or disturbance of the surface, walls or ceiling before work commences. Contractor shall ensure they have a copy of the CE approval memo or email prior to start of any work.

1.2.5. Personnel. The Contractor shall provide a team dedicated to Nellis AFB and a team dedicated to Creech AFB with one (1) full-time site lead at each location. 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.

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 wear company approved uniforms (Company logoed Polo shirts, T-Shirts shall be sufficient) and identify themselves as Contractor. In addition, Contractor personnel shall appropriately identify themselves as Contractor employees in telephone conversations and in formal and informal written correspondence.

1.2.8. Security. The Contractor shall follow security guidelines IAW AF MAN 33-145, DoDI 8100.3, and the Defense Switched Network Security Technical Implementation Guide (DSN STIG). At the end of each work period, all Government facilities, equipment, and materials shall be secured.

1.2.8.1. Controlled Unclassified Information (CUI). If the Contractor determines that unauthorized personnel have access to Controlled Unclassified Information (CUI) material, such as the Base map or CVCs, the Contractor Site Manager will immediately notify the COR and cooperate fully with any investigation. The Contractor shall comply with DoD Directive 5400.07, Section 1.2, The DoD Freedom of Information Act (FOIA) Program. This directive establishes policy and procedures for the disclosure of records to the public and for marking, handling, transmitting, and safeguarding CUI material.

1.2.9. Safety, Security, and Environmental Meeting. The Contractor and COR shall initially meet with appropriate local safety and health, security, environmental, and civil engineering offices within ten days after start of contract performance to identify all local OSHA and safety requirements identified by Nellis/Creech AFB.

1.2.9.1. Identify Potential Concerns Within a Work Area. The Contractor shall identify any potential problems within the projected work in areas that may contain asbestos, hazardous materials, and/or hazardous wastes and local procedures to be followed in the event such problems are encountered.

1.2.9.2. Use and Disposal of Hazardous Material. The Contractor shall determine local procedures to be followed concerning the use, disposal, or reporting of use of hazardous materials. Material Safety Data Sheets (MSDS) shall be submitted IAW FAR Clause 52.223-3, “Hazardous Material Identification and Material Safety Data,” for any hazardous materials (paints, solvents, cleaners, encapsulating compound, etc.) to be used in performance of the contract. The MSDS must be on file with the Base Environmental Management Office prior to any use of the hazardous material.

1.2.9.3. Environmental Survey. An environmental survey is required at each site requiring demolition, construction or upgrade before work can begin. The Contractor shall not begin work until the environmental survey has been accomplished and any problems identified have been resolved or received clearance by civil engineering IAW PWS 1.2.4.

1.2.9.4. Security Site Specific. Determine any site-specific security requirements and ensure compliance by all personnel.

1.2.9.5. Environmental Management Systems (EMS). All Contractor employees will be required to complete Air Force provided initial Environmental Management Systems (EMS) awareness level training within 90 days of contract award or with a new contract employee beginning work on the Air Force Installation. The appropriate documentation of training will be provided to the COR office within five (5) duty days of completion.

1.2.10. Overtime. Overtime premiums are not reimbursed by the Government under the terms of the contract as it is included within the prices proposed; therefore, change in shift or shift premiums or reimbursement shall be negotiated solely between the Contractor and its employees IAW applicable labor laws.

1.2.11. Invoicing Instructions Utilizing the Government Purchase Card (GPC). The Contractor shall accept payment via GPC for any Pre-priced PID list work, as defined in Paragraph 1.7, 4.1.7/4.2.7, to be accomplished below $2,000.00 for Construction, $2,500.00 for Services, and below $10,000.00 for commodities to include incidental service and construction. The previous process shall also apply to repairs, work orders and task orders. The CO has the discretion to change the method of payment from GPC WAWF. This change will be notified prior to a Task order or Work Order issued/approved by the COR(s). The GPC surcharge shall not be charged back to the Government.

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

1.3.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.2. Scheduled Outages. The Contractor shall identify, coordinate, and schedule service outages with the COR/SME. 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.3. Restoration/Completion of Outages, Trouble Calls/Tickets. The COR will assign the category of the outage/trouble and establish the repair priority if an outage occurs. The Contractor shall respond on site and advise the COR/SME of repair actions required. Repairs that require funding above $75.00 shall have COR approval prior to implementation (this can be verbal for emergencies or after duty hours).

Repairs that cost less than $75.00 shall be covered under monthly maintenance per instance. 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/SME. The Contractor shall continue to work on repair actions until service is restored based on priority or until released by the COR/SME for repairs that occur after normal duty hours. The Contractor shall work closely with the COR/SME 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 Integration 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 4.1.7 and 4.2.7 (work center records). Outage/trouble call categories are further defined as:

1.3.3.1. Emergency/Remedy. 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 due to premise or outside plant cabling 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.3.2. Priority/Remedy. Contractor shall respond on-site within four (4) hours and restore service as soon as possible but shall not exceed two (2) workdays. 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/SME guidance Loss of LAN connectivity due to premise or outside plant cabling affecting 15-99 users.

1.3.3.3. Routine/Remedy. Contractor shall respond on-site within one (1) duty day and restore service as soon as practicable but not to exceed five (5) workdays. Expedition of parts and/or labor is not required.

Routine outages/troubles are any other outage(s) not included in the above categories.

****An average of 25 remedy tickets per month for Nellis AFB and 10 for Creech AFB, with a cost of less than $75.00 per incident shall be covered under monthly maintenances. Remedy over 25/10 incidents, respectively per base, per month shall be reimbursed for materials only monthly. Per incident Remedy repairs over the cost of $75.00 shall be reimbursed for materials only.***

1.3.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/SME 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.4. 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.4. CONTRACTOR SUPPORT SERVICES. The Contractor shall comply with FAR 9.505, Conflict of Interest, IAW support services.

1.4.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 Equipment Locations

(CEL).

1.4.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 CO or COR.

1.4.3. 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 4.1 and 4.2 and identified in Section 4.1.7 and 4.2.7. The Contractor shall update the CVC (GPS shall be included) 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.4.4. Cable/Premise Installation/Repair/Remedy Test Results. Contractor shall develop and maintain a cable installation/repair test results record after the installation or repair of an outside plant cable or facility premise wiring. 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. The test results shall conform to the Nellis/Creech Addendum 2710.

All remedy orders shall be prepared via TMS, on DD Form 1367, Commercial Communications Work Order or approved equivalent form for the replacement of materials. Task order numbers shall be established by the COR/SME. The Contractor shall update the CVC database with pertinent CFD information resulting from installation or repair.

1.5. CYBERSPACE INFRASTRUCTURE PLANNING SYSTEM (CIPS).

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

1.5.1. Maintaining Records. 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 CVC information, for the outside plant, in the CVC database IAW AFI33-10, to 00-33D-3003, TO 00-33D-3004 and TO 00-33A-1001. Contractor shall transfer to the CVC database all pertinent outside plant CFD information from administrative and maintenance CVC, 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.6.5.

When the update is completed, the Contractor will close the session and notify the COR/SME the session edit is ready to be approved. The COR/SME 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 COR/SME 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.5.2. Maintaining CIPS Drawing Records. The Cyberspace Infrastructure Planning System (CIPS) Visualization Component (CVC) shall be the method of developing, maintaining, and editing information historically contained in installation drawings 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.

1.5.3. Inside Plant Drawing Records. The Contractor shall maintain Inside Plant Drawing records in the format directed by COR/SME. 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 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 CVC 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.5.4. Drawings and Records.

1.5.4.1. All Contractor and Third-Party As-Built Drawings. All third party as-built drawings shall be submitted to the COR/SME 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.

The Contractor shall produce drawings to support engineering initiatives.

1.5.5. Electronic Submissions

1.5.5.1. Government Electronic File. All changes/additions shall be made on the government provided electronic file.

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

1.5.7. CLIN/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.5.8. 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.5. Records include spares inventory list and spares replacement log. Spares inventory list shall include, at 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.5.9. 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.5.10. Equipment Inventory Records (PWS Appendix 5.2/5.4). Thirty days (30) after contract award, a joint inventory shall be accomplished to verify Appendix 5.2/5.4. The Contractor shall maintain a working copy. Appendix 5.2/5.4 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.5.11. 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.5.12. 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.5.13. 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.5.14. 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.5.15. System Security Audit Records. The Contractor shall develop and maintain an electronic weekly user event log that contains, at a minimum: the number of logins (remote and local); number of login attempts (remote and local); password changes; and/or any critical table modifications including new user accounts as allowed by the switch.

1.5.16. 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.6. 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.6.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.6.1.1. GPS. 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.7.

1.6.1.2. Geospatial Coordinates. 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.7.

1.6.1.3. Geospatial Coordinates for Manholes, Vaults, Pedestals, and Handholds. Geospatial coordinates for the location of manholes and cable vaults shall be recorded from 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.6.2. Software/Hardware and Tools for Electronic Media. 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.6.2.1. GPS/CFD Information. 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.6.2.1.1. GPS Horizontal Position. 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.6.2.1.2. CFD/GPS Data Loggers. 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.6.2.1.3. Metadata Elements. 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.7. 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.6.2.1.1.

1.6.2.2. National Standard for Spatial Data (NSSDA). Calculation worksheets showing compliance with National Standard for Spatial Data Accuracy (NSSDA) statement at the 95% confidence level as https://cipsaf.tinker.af.mil/cips/mycips.aspx required by Paragraph 1.6.2.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.6.2.3. GeoBase Common Installation Picture (CIP). Geospatial data shall overlay on the installation’s most current GeoBase Common Installation Picture (CIP) provided by the base Communications Squadron. The collected data will incorporate the coordinate and projection system of the CVC for:

Specify the CVC coordinate and projection system name of the local base CIP, for example: WGS 1984 Universal Transverse Mercator (UTM) Zone 12, Latitude Band S.).

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

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

b. Features shall be snapped where applicable, for example, GPS_Dbsplice snapped to GPS_Path_Segment.

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

d. No sliver polygons.

e. All polygons completely close and have a single unique centroid.

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

1.6.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. (Location/media will be directed by the COR office) Contractor shall make available such documentation to COR, when requested, for reviews to ensure compliance with GPS service guidance.

1.6.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 https://cips.cce.af.mil/CIPS5 or search for CIPS at the Air Force Portal.

1.7. 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 Task 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 any item(s) required to complete a work order is part of the current pre-priced PIDs (Attachment 1), the Government may negotiate the addition of these items via a special project (PWS Section 1.5), or opt to use another vehicle to accomplish the task.

http://www.fgdc.gov/

1.7.1. Work Order Procedures.

1.7.1.1. Work orders (aka Technical Solution and Costing TSC) prepared by the Contractor shall be approved by the COR before work starts. All work orders shall be prepared via TMS, on DD Form 1367, Commercial Communications Work Order or approved equivalent form. Task order numbers shall be established by the COR. Contractor shall analyze and gather all pertaining information required and may walk-through the proposed work site if necessary to ensure understanding of the work to be performed, which is not the same as a Site Survey solution and costing (SS-TSC) (see FAR 52.236-2 Site Investigation). The Contractor may be accompanied by Government personnel. See also item descriptions within the schedule of the basic contract. This is not to be confused with a Site Survey. 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.7.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.7.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 and must be coordinated and approved by the CO.

The Contractor shall be responsible for covering such situations with adequate personnel and completing the work within the stipulated time. Premium pay per appropriate labor law is included within the pre-priced items for work orders.

1.7.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 considered an adequate reason for an extension. All cable cut repairs shall be classified as an emergency unless determined otherwise by the COR.

Routine Work Orders. Complete within 10 business days (unless approval received by COR) Examples of routine are office relocations, software changes such as voice mail or class of restriction changes. Installation of new numbers, installation of new LAN/Data drops

Priority. Complete within 3 business days (unless approval received by COR) Examples of Priority, condemned facility, downward directed office relocates that were not previously notified at base level.

Emergency. Respond on work site within two (2) 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 until completed. Examples of Emergency shall consist of the status of aircraft being able to fly, or Safety of personnel, or Active Shooter response, or Accident Investigation Board

1.7.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, Work Order number.

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

The work order priority and established completion time.

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.

Include the statement “Invoice Work Order Against Funding SLIN(s) _____” prior to work order approval (do not use “x” placeholders, e.g. x011AA on work orders)

1.7.4. Work Orders Subject to the Davis Bacon Act (DBA) and Service Contract Act (SCA). The COR is authorized to place work orders directly with the Contractor for all CLINs/PIDs. The COR shall identify work orders where the DBA applies on the face of the work order. Work orders using CLINs x005-007 and may be subject to DBA dependent upon work effort to be performed. A copy of all DBA work orders shall be forwarded to the CA/CO for DBA determination and approval.

1.7.5. Submittal of Completed Work Orders. The Contractor shall provide copies of all completed work orders issued under this contract to the COR by dropping them into a designated location or updated in the approved data base within two duty days of completion. Completed work orders shall have the date of completion of the work, the completion date of applicable deliverables, and customer or COR and Contractor initials.

Note: Unavailability of customer after two attempts (documented by phone calls or emails) for a completed task, Contractor shall proceed without by providing date and signature of technician

1.8. Special Project Requirements. The Government may negotiate a special project into the contract when an effort needed is not covered by current product item description items on the contract or shall be used when level of effort exceeds OSP connectivity of fiber or copper to closet, more than one manhole/handhole or when ISP premise wiring exceeds installation of more than 100 jacks. Special projects are Firm Fixed Price (FFP) negotiated task orders and Davis Bacon work orders. The CO will request a proposal from the Contractor for special projects. Proposals shall be submitted on DD Form 1367, Commercial Communications Task Order or equivalent format and include the information below, as a minimum. Estimated frequency not to exceed 10 per base/option year period.

1.8.1. Detailed Proposals. The Contractor shall submit detailed proposals for work intended to be performed under special projects as requested by the CO at no additional price. Contractor shall provide its proposal to the CA/CO within ten duty/work days.