B. Performance Work Statement - FA487725QA001 - BTS (signed).pdf

Performance Work Statement for

Base Telecommunications System Operations and Maintenance Services

355th Communications Squadron

Davis-Monthan AFB

Review/Coordination:

Services Acquisition Lead

Quality Assurance Program Coordinator

Contracting Officer

Table of Contents

Paragraph Title Page

1.0. Description of Services 1

1.1. Description of Services 1

1.1.1. Scope of Work 1

1.1.2. Normal Duty Hours 1

1.1.3. On-Site Contract Manager 1

1.1.4. Contractor Employee Qualifications 2

1.1.5. Personnel Clearances 2

1.2. Operation and Maintenance (O&M) Requirements 2

1.2.1. Telephone Switch System O&M 2

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

1.2.3. Preventive Maintenance Inspections (PMIs) 3

1.2.4. System and Service Outages and Trouble Calls/Tickets 5

1.2.5 Alarm Notification 6

1.2.6. Cable Location, Staking, and Marking 7

1.2.7. System Cross-Connect and Disconnect Services 7

1.2.8. Accident/Incident Reporting and Investigation 8

1.2.9. Traffic Measurement and Analysis 8

1.2.10. Government Engineering and Installation Support 8

1.2.11. Technical Solutions 9

1.2.12. Work Center Records 9

1.2.13 Contractor Maintained Items with Government Tier 2 & 3 Support 15

1.2.14 Contractor Maintained/Government Repaired Items 20

1.2.15 Government Maintained/Contractor Operated VoIP Systems 23

1.2.16 National Airborne Operations Center (NAOC) Aircraft Support 23

1.2.17 O & M Workload Estimates 24

1.3. Work Orders 24

1.4. Non-Priced Items 26

1.5 Base Civil Engineering Work Clearance Requests 26

2.0. Services Summary 27

3.0. Government Property and Services 29

3.1. Space 29

3.2. Utilities 29

3.3. Storage 29

3.4. Government E-Mail Access 29

3.5. Telephone Services 29

3.6. Base Refuse Collection 29

3.7. Recycling Program 29

3.8. Emergency Services 29

3.9. Insect and rodent control 29

3.10. Forms and Publications 29

3.11. Base Civil Engineers 29

3.12. Furniture and Equipment 29

3.13. Government Support for CVC Efforts 30

4.0. General Information 30

4.1. Contractor Employee Restrictions 30

4.2. Contractor Travel on DMAFB 31

4.3. Smoking In AF Facilities 31

4.4. Personnel Appearance 31

4.5. Quality Control Program 31

4.6. Environmental Protection Compliance 32

4.7. Spill Containment Kit 33

4.8. Continuation of Essential DoD Contractor Services During Crisis 33

4.9. Federal Holidays 34

4.10 Safety 34

4.11 Security Requirements 35

Appendix A Global Positioning System Service Reference Table A-1

Appendix B References B-1

Appendix C Glossary and Acronyms C-1

Performance Work Statement for Base Telecommunications System Operations and Maintenance Services

1.0. DESCRIPTION OF SERVICES

1.1. Description of Services. The contractor will provide all, equipment, tools, materials, vehicles, personnel, labor, supervision, and management to perform Base Telecommunications System Operations and Maintenance Services in support of the 355th Communications Squadron (355 CS) at Davis-Monthan Air Force Base (DMAFB), AZ.

1.1.1. Scope of Work. The contractor will perform Operation and Maintenance (O&M) 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, outside plant (OSP) and inside plant (ISP) systems, telephone network, telephone transmission systems, and all associated equipment. The contractor will 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.

1.1.2. Normal Duty Hours. Contractor personnel and technicians necessary to perform services will be available Monday through Friday, 7:30 a.m. to 4:30 p.m., excluding holidays specified within the applicable Service Contract Wage Determination.

1.1.2.1. Overtime. Overtime premiums are not reimbursed by the Government under the terms of the contract, and are included within the installation prices listed on the pre-priced pricing table; therefore changes in shift or shift premiums/reimbursement will be negotiated solely between the contractor and the contractor’s employees in accordance with applicable labor laws.

1.1.2.2. On-Call Duty. Technicians are not required to be physically present in the work center, except during normal duty hours. However, personnel performing on-call duty must have a means of being contacted (telephone, etc.) so they can respond to outages within the designated time limit.

1.1.3. On-site Contract Manager (CM). The contractor will designate an on-site primary CM, and at least one alternate CM, who is responsible for contractor-performed services. The primary CM or alternate CM may be an employee providing services. The alternate CM will act for the primary CM when absent. The CM (or alternate CM) must have the ability to make decisions regarding the contract and work orders, however, will be required to have a three duty day turn around response to the Government Contracting Officer’s Representative (COR). Upon contract award and prior to the contract start date, the contractor will submit the names and telephone numbers of the primary and alternate(s) CM, in writing, to the Contracting Officer. The primary or alternate CM will have full authority to act for the contractor on all matters relating to daily execution of the contract and must be available by phone to respond to Government service calls, 24 hours per day, 7-days per week, including holidays. The CM will be present and available within 2 hours of notification to meet on the installation with Government personnel designated by the Contracting Officer to discuss any contract issues or problem areas.

1.1.4. Contractor Employee Qualifications. The contractor will provide a sufficient number of fully trained contractor employees that possess all professional certifications and licenses required to provide BTS operations and maintenance services. The contractor will provide proof of contractor employee qualifications to the Government upon contract award and within 3 working days of the request. The contractor will provide a technician with Cisco Certified Network Associate (CCNA) certificate. The contractor must have the ability to work in: (1) manhole systems (confined spaces) to perform maintenance or any required operation; (2) Cisco Unified Call Manager (CUCM) and Unified Messaging for VoIP phone configurations; (3) the Cyberspace Infrastructure Planning System (CIPS) Visualization Component (CVC) database.

1.1.5. Personnel Clearances. All contractor personnel performing BTS services under the contract must possess and maintain at a minimum a favorably completed National Agency Check with Inquiries (NACI) investigation prior to individual providing services under this contract. All contractor employees must also be US citizens. The contractor may be required to provide employee background information to comply with contract clearance requirements, including Common Access Cards (CACs) and building access badges.

1.1.5.1. Clearance Revocation/Suspension. If the contractor is notified by any Government official having security cognizance over the contract that an employee’s National Agency Check with Inquiries (NACI) investigation has been revoked or suspended, the contractor must notify the Contracting Officer the same day the contractor receives the notice.

1.2. Operation and Maintenance (O&M) Requirements. The contractor will operate and maintain the BTS as described by the Maintenance Support Plan (MSP) (see PWS paragraph 1.2.12.1., Maintenance Support Plan (MSP) and the OEM’s recommended procedures). O&M tasks 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 commercially available parts, inspection, periodic testing, adjustment, and repairs. The effort may include the replacement of defective circuit packs and Customer Premise Equipment (CPE), preventive maintenance in accordance with applicable publications (OEM, PWS Appendix B, References, 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 in accordance with PWS Paragraph 1.3. The contractor will not postpone or otherwise delay O&M efforts to accomplish work orders. The contractor will complete both O&M and work orders simultaneously to ensure contractual timelines are met for both. The contractor will provide consumable items (tie wraps, tape, labels, etc.).

1.2.1. Telephone Switch System O&M. The contractor will operate and maintain the system(s) identified in PWS Paragraph 1.2.13, Contractor Maintained Items. The Government will measure the acceptable standard performance level by a determination of the total systems availability (up time) and reliability rating during any given month. All equipment or services installed by the contractor will automatically become part of the O&M services. This includes, but is not limited to, management; administration and maintenance; performing software functions (e.g. number reclamation); translations for any trunk or circuit of configurations required by on-base systems or users; data administration; trouble assistance; air filter replacements; and records administration.

1.2.1.1. Voice over Internet Protocol (VoIP) Operations. The contractor will operate and maintain the configuration feature of adding, deleting, programming, and troubleshooting of VoIP phones in the VoIP System identified in PWS Paragraph 1.2.15. VoIP phone equipment are identified in PWS Paragraph 1.2.15. The VoIP System is controlled and maintained by the 355 CS Infrastructure work center (SCOI): items include Cisco Voice Gateway, Cisco Unified Communications Manager (CUCM), Cisco Unified Messaging, patch chords to switch, and Ethernet ports of the switching equipment. The contractor is not responsible for base network equipment (e.g. Information Transfer Node (ITN), Local Area Network (LAN) switches, and Secure (or higher) VoIP phones).

1.2.1.2. Voicemail System/Cisco Unified Messaging. The contractor will operate and maintain the Voicemail System (). The contractor will only operate the configuration feature of voicemail, such as adding, deleting, programming, and troubleshooting (e.g. voicemail reset), in Cisco Unified Messaging. The Cisco Unified Messaging is controlled and maintained by 355

CS/SCOI.

1.2.1.3. The contractor will maintain and operate all back-plane configurations on all Voice Gateway Routers on Davis-Monthan Air Force Base.

1.2.2. Inside Plant (ISP) and Outside Plant (OSP) O&M. The contractor will maintain ISP and OSP cable and equipment as identified in PWS Paragraph 1.2.14. and in accordance with applicable documents listed in PWS Appendix B.

1.2.2.1. The contractor will extend the ISP for copper and Fiber, from the patch panel to the NIPR access nodes for the following items: VOIPS, workstations, Printers/multi-function devices, Video-Teleconference systems, Specialized products not managed by base communications squadron. . When tasked by the COR, the contractor will provide communication closet and ITN wire management services IAW industry standards.

1.2.3. Preventive Maintenance Inspections (PMIs). The contractor will perform PMIs on all systems covered by this contract IAW OEM recommended or established schedules and/or manuals. The contractor will elevate any problems and identify any trends to the COR, in writing within one workday of discovery. The contractor will correct deficiencies in accordance with PWS paragraphs 1.2.3.1.-1.2.3.6. below.

1.2.3.1. Switch Power Test. The contractor will perform scheduled PMI tests of the telephone switch backup power system. The contractor will test and document the power systems identified in PWS paragraph 1.2.13. Each power system will be tested in accordance with OEM specifications. The contractor will accomplish PMI tests monthly and document test results in accordance with PWS paragraph 1.2.12., Work Center Records.

1.2.3.2. Spare Conductor Test. The contractor will perform a scheduled PMI test of all spare conductors. The contractor will 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 (DCO). The contractor will accomplish PMI tests quarterly and document test results in accordance with PWS paragraph 1.2.12., Work Center Records.

a. Manholes and/or Handholes. The contractor will inspect twenty (20) manholes/handholes per month (actual manholes/handholes to be approved by COR prior to each inspection and included in the end of month report) under the O&M portion of this contract. The contractor will accomplish additional inspections as a work order in accordance with PWS paragraph 1.3., Work Orders. If the contractor is working in a manhole not scheduled for a PMI, the contractor will correct any discrepancies before the job is considered complete, and the manhole will be counted in the monthly PMI schedule. The contractor will inspect each manhole/handhole for the following discrepancies and make corrections as required:

b. All existing as well as newly installed cables will be identified and tagged. At each splice, tags will be placed on each side of the splice identifying each cable. In manholes with pull-through cables, each cable will be identified with a tag.

c. All existing as well as newly installed cables will be racked to the manhole cable supports.

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

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

f. Install manhole locking lids as part of monthly PMI’s as needed.

g. Update the Cyberspace Infrastructure Planning System (CIPS) Visualization

Component (CVC) database - for the manhole or handhole and record all descriptive information for splices, cables, ducts and other communication features in the manhole or handhole. After updating CVC, the contractor will inform the COR of all updates, via the work order management system (WOMS) or e-mail.

h. Manhole and handhole drawings (Butterfly drawings) will be accomplished during all PMI’s and work orders being accomplished in manhole and handhole systems that are not currently updated.

1.2.3.3. Terminals. The contractor will inspect five (5) terminals per month. Additional inspections will be accomplished as a work order in accordance with PWS paragraph 1.3. The contractor will inspect each terminal for the following discrepancies and make corrections as required:

a. Verify the correct location, number, and cable count.

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

c. Ensure cable is tagged correctly.

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

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

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

g. Update Telecommunications Management System (TMS).

h. Update the CVC database with descriptive information.

1.2.3.4. Distribution Pedestal Terminals. The contractor will inspect three (3) Distribution Pedestal terminals per quarter. Additional inspections will be accomplished as a work order in accordance with PWS paragraph 1.3. The contractor will inspect each terminal for the following discrepancies and make corrections as required:

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

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

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

d. Ensure terminal is correctly installed.

e. Verify all working numbers and remove any unused numbers.

f. Remove all unused cross-connects.

g. Update the CVC database with descriptive information.

1.2.3.5. Cable Analysis. The contractor will review TMS records included in the monthly preventative maintenance inspection report and perform cable analysis. The contractor will incorporate and determine the number of bad pair(s) in each cable and report the percentage in each cable to the COR in the monthly PMI report. The contractor will also determine the cable fill rates and report to the COR, via WOMS or e-mail. 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 contractor’s CM will be available to the COR at all times. The contractor will respond in case of emergencies, outages, alerts and exercises, 24 hours a day, seven days per week. If contacted by the COR, the contractor will report on-site and provide services as necessary until the emergency, alert, or exercise is completed.

1.2.4.2. Scheduled Outages. The contractor will identify, coordinate, and schedule service outages with the COR, via WOMS or e-mail. Notification will include the reason for the interruption, start and stop times, duration, and the equipment, lines, and buildings affected. The contractor will schedule such outages to minimize inconvenience to Government personnel, based upon Government user work schedules, which may require working outside of normal duty hours at no additional cost to the government. The Government end user must release all affected equipment and circuits prior to any service disruption. The contractor will follow established local procedures for scheduling and implementing scheduled outages. The contractor will log the outage in accordance with the guidance in PWS paragraph 1.2.4.3., Restoration/Completion of Outages, Trouble Calls/Tickets.

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 when an outage occurs. The contractor will respond on-site and initiate repair actions within the specified time listed below upon COR notification. Exceptions to time limits may be allowed, with appropriate written justification from the contractor and written approval by the COR. The contractor will restore services in the priority order determined by the COR. The Restoration Priority List (RPL) will apply in the absence of the COR. The Government will provide the RPL to the contractor upon contract award. The contractor will continue repairs until service is restored based on priority.

The contractor will work closely with the COR on all service or system outages and trouble calls/tickets, notify the COR in writing upon restoration of services immediately via telephone, email, Enterprise Information Technology as a Service (EITaaS), or CIPS, and provide the time services were restored and a description of repair action. The contractor will coordinate with the 355 CS Communication Focal Point (CFP) to restore any phone, analog or VoIP, outages. The contractor will log outages IAW the guidance in PWS section 1.2.12.3., Maintenance/Repair Logs.

1.2.4.3.1. Emergency. The contractor will respond on-site within two hours and restore service within eight hours of COR notification, unless otherwise approved by the COR in writing.

Expedition of parts or labor may be required, at no additional cost to the Government. If an outage/trouble significantly affects a mission, the COR may declare the outage/trouble as an Emergency. Emergency outages/troubles are classified, but not limited to, any of the following:

a. Loss of over 75% or more of total call handling capability of any communications system

b. Loss of any Primary or Secondary Crash System or any portion thereof

c. Failure of one or more circuits listed in the Base RPL

d. Loss of Local Area Network (LAN) connectivity affecting 100 or more users

e. Affects security or emergency type operations, including Emergency Operations Center

(EOC); as well as those affecting safety

f. Affects specifically identified events and/or exercises

1.2.4.3.2. Priority. The contractor will respond on-site within six hours of COR notification and restore service as soon as possible, but will not exceed two (2) workdays. Expedition of parts or labor may be required, at no additional cost to the Government. Priority outages are classified, but not limited to, any of the following:

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

b. Major alarm of any switching system identified in Appendix A

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

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

e. Loss of LAN connectivity affecting 15 to 99 users

1.2.4.3.3. Routine. The contractor will respond on-site within one (1) duty day of COR notification and restore service as soon as practicable, but not to exceed five (5) workdays. Routine outages/troubles are those not classified as Emergency or Urgent.

1.2.4.3.4. Outage/Trouble Cause Identification. The contractor will determine if a recorded problem or system failure is attributable to the BTS or other causes, and immediately notify the COR, via WOMS or e-mail, 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. The contractor will comply with the details of their alarm notification method as documented in the contractor’s MSP. Alarm notification will not interfere with any Government-owned system. Alarm notification of the switch system(s) will not require assistance from government personnel. Notification of switch outages will not be through a continuous direct line to the switching system, for security reasons. Remote diagnostics modems are not authorized. The contractor is responsible for all materials and equipment necessary to implement alarm notification and will take all actions to implement the MSP and comply with telephone switching security standards IAW industry standards and Defense Information Systems Agency (DISA) Security Technical Implementation Guide (STIG) Voice and Voice Over IP.

1.2.6. Cable Location, Staking, and Marking. The contractor will locate, stake, and mark, up to 50,000 feet of encased or direct buried conduits/cable during the contract base period of performance. 50,000 feet for each option period of performance at no additional cost to the Government and will be included in the monthly maintenance CLIN. Any and all costs of blue staking above and beyond 50,000 feet can be charged per the pricing table. Marking will be within three feet of the actual location at ten-foot intervals and at direction changes. The marking will begin two feet from the point of entry into the work area and will continue two feet past the point of exit from the work area. Upon completion, the contractor will take photographs of the staking and marking and provide the photographs to the COR with the blue stake. The photographs will be labeled and include the blue stake number. The contractor will complete location, staking, and marking within the specified time listed below from the time the contractor is notified by the COR of the requirement, unless additional time is approved in writing by the COR. The contractor will document time extensions in writing on the work order, including the signatures of the COR and the contractor’s CM. Communication Feature Data (CFD) collection will be accomplished via work order. See Equipment and Installation Performance Specification (EIPS) and corresponding Contract Line Item Number (CLIN) when directed to collect CFD data by the COR. The contractor will comply with the following timelines, as designated by the COR, for location, staking, and marking:

Emergency: Within one (1) duty day of notification Priority: Within three (3) duty days of notification Routine: Within ten (10) duty days of notification

1.2.6.1 Digging Permits and Blue Staking. The contractor is also responsible for contacting Arizona Blue Stake, if required, but the Government makes no such timeline approximations as Arizona Blue Stake response time is outside the Government’s control. The contractor will submit the AF Form 103, Base Civil Engineering Work Clearance Request, prior to commencement of any work order requiring such. Although the Government reviews the contractor’s AF Form 103 request, it is ultimately the contractor’s responsibility to ensure that the form is submitted correctly. The contractor must mark all areas with white paint that they wish the Government to clear, prior to the AF Form 103 submittal. The contractor will also include a site drawing of the area to be cleared with the AF Form 103 submittal. Upon submittal, the contractor will provide the AF Form 103 tracking number to the COR. Once a construction site has been marked for existing utilities, the contractor will maintain the markings through completion of work.

1.2.7. System Cross-Connect and Disconnect Services. The contractor will perform system cross-connect and disconnect services. All cross-connects and disconnects, which are required or incidental to the performance of O&M actions (including those outside of the DCO), will be included as part of the O&M services.

1.2.8. Accident/Incident Reporting and Investigation. The contractor will record and report all available facts relating to each instance of accidental Government property damage or contractor personnel injury to the COR within two hours of the incident. The contractor will secure the scene of any accident and wreckage until released by the accident investigative authority through the Contracting Officer. If the Government elects to conduct an investigation of the incident, the contractor will cooperate fully with the COR, Contracting Officer, and other Government investigation personnel until the investigation is complete.

1.2.9. Traffic Measurement and Analysis. The COR may request up to two (2) traffic measurements and analysis per switch a year. The contractor will 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 traffic measurement and analysis will 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.10. Government Engineering and Installation Support. The contractor will 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 Contracting Officer. 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.10.1. Contractor Interface and Support with other Contractors. The contractor will cooperate, share, and exchange routine or available technical and system equipment interface information with other contractors as directed by the COR or Contracting Officer.

1.2.10.2. Workload/Status Meetings. The contractor’s CM will attend a minimum of four (4) local workload/status meetings per month with the COR, Communications Squadron Plans Office, and/or Contracting Officer to discuss status of current and future work orders, trouble tickets, outages, PMIs, or any other work/event that may impact contractual performance. The contractor will provide a list of open work orders, trouble tickets, etc. at the meeting for reconciliation and discussion with the COR(s), Contracting Officer, or other personnel.

1.2.10.3. Design Review Meetings. The contractor will review program or project drawings and provide comments concerning communications requirements within ten working days from receipt when requested by the COR. The contractor will participate in designated design review meetings identified by the COR. The contractor’s CM will attend all design meetings that pertain to BTS/Communication services. These design meetings are generally hosted by the 355th Civil Engineer Squadron (355 CES) and 355th Contracting Squadron (355 CONS) at the commencement of a construction project. The contractor’s CM will provide input on design matters related to the base telecommunication system.

1.2.11. Technical Solutions. The contractor will perform detailed technical solutions 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 will be provided to the COR using the work order format specified in PWS paragraph 1.3. The contractor will provide proposed solutions to the COR within five (5) working days from receipt of requirement unless a longer period is agreed to in writing by the COR and documented. The contractor must submit time extension requests to the COR, in writing, at least 48 hours in advance of due date, and approval will be made on a case by case basis. The contractor will provide technical solutions at no additional cost to the Government. Costs associated with technical solutions will be included in the monthly maintenance price.

1.2.12. Work Center Records. The contractor will develop and maintain BTS work center records, and update the records within two duty days after completion of the associated task(s) unless specified differently in the PWS. All BTS records and documents established and maintained by the contractor are Government property and will remain at the site and submitted to the COR 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 contractor will maintain and store records electronically, unless otherwise specified herein. The contractor will identify all acronyms, codes, abbreviations, signs, and symbols used in each record. The contractor will use the same format for initial and all subsequent submissions of the same record unless otherwise approved by the COR. All records will be readily available for review by the COR, and other designated personnel. The contractor will update all errors found or identified during review of the work center records. The contractor will develop, update and/or maintain accurate, complete, and readable work center records as listed below:

1.2.12.1. Maintenance Support Plan (MSP). The contractor will develop, maintain, and utilize an MSP. The MSP will enable the scheduling and tracking of preventive maintenance actions on contractor-maintained equipment. The contractor will submit the MSP to the COR within 30 calendar days of the contract start date. The COR will review and accept, or return the MSP with required corrections. When changes occur that affect the MSP, revisions will be submitted to the COR within 10 work days after the effective change (e.g. modification adding equipment) unless otherwise requested by the COR (e.g. with the proposal to add new equipment to maintenance).

Changes may be implemented only after COR acceptance. The MSP will contain as a minimum:

a schedule of PMIs due on all contractor-maintained equipment in this PWS 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.12.2. PMI Inspection Records and Malfunction Record. PMI records will contain at a minimum, 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. The contractor will retain hard copies of these inspection/malfunctions records, and submit one (1) hard copy to the COR within five working days of the first of the month.

1.2.12.3. Maintenance/Repair Logs (e.g. maintenance actions, trouble tickets). The contractor will develop and maintain an accurate and legible BTS Maintenance/Repair Log to record 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 contractor’s CM will initial the log and the log will 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. The contractor will retain hard copies of these maintenance/Repair logs, and submit one (1) soft copy to the COR by close of business of each duty day.

1.2.12.4. Manhole, Handhole, and Building Terminal Inspection/Maintenance/Repair. The contractor will maintain manhole, handhole, distribution pedestal terminal, and building terminal inspection records IAW PWS paragraph 1.2.12., Work Center Records. The contractor will update the CVC database with pertinent CFD information obtained during the inspections. The record will be available for inspection and analysis by Government personnel. If other electronic documentation is implemented, the contractor will grant the Government access to those records.

1.2.12.5. Cable Installation/Repair Test Results. The contractor will 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 will contain, at a minimum, 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 will update the CVC database with pertinent CFD information resulting from installation or repair.

1.2.12.6. Switching System and ISP & OSP Equipment Operational Records. The contractor will retain records on site and make available for COR or Contracting Officer review upon request.

1.2.12.7. Contract Line Item Number (CLIN)/Subcontract Line Item Number (SLIN)/Product Identification (PID) Utilization Record. The contractor will produce and maintain an electronic record of the CLINs/SLINs/PIDs, ordered under the contract. The record will include: the CLIN, SLIN, or PID number; description; and quantities of each item. The record will exclude price information. The contractor will update this record within two work days of work order task(s) completion.

1.2.12.8. Equipment Inventory Records. The contractor will maintain current a working copy of the equipment listed under paragraphs 1.2.13. through 1.2.16. The record will identify equipment installed, changed, or removed as a result of contract modification or the work order process. The record will 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 will update the record when individual work orders are completed using the “track changes” feature in MS Word® software.

1.2.12.9. Work Order Records. The contractor will develop and maintain work orders, including warranty records. Physical records of work orders in process will be retained and available locally (on-base). The contractor will update work center records within two (2) duty days after completion of the task(s) specified on individual work orders. Once the work order task(s) is completed, the contractor will submit the original work order to the COR. The COR will verify the completed work order task(s) and return the work order document to the contractor for their records. Electronic storage of completed (accepted by the COR) work orders 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.12.10. Traffic Measurement Records (TMR). Switch-generated reports are used to generate a TMR. The record will contain an analysis of the traffic measurements including a trunk traffic summary and individual analysis of each trunk group. The contractor will provide printed records to the COR on an as-needed basis, but 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 will be maintained on site and made available to the COR within three work days from occurrence of Traffic Measurement analysis.

1.2.12.11. System Capacity Records. The contractor will produce system capacity records monthly and upon request by the COR. Monthly system capacity records include outside plant cables and building records. Records will include each cable and terminated cable count, type of cable (bad and spare), and number of conductors used. Quarterly system capacity records will be produced for the host switch and remotes. The records will include total line ports, line ports in use, line port type (analog/digital/Integrated Services Digital Network (ISDN)/etc.) total used, and DS-1 digital trunk ports (total ports used and available)

1.2.12.11.1. Cable Assignment Information Retrieval System (CAIRS) Telephone Management System. CAIRS.net servers are maintained at Hill AFB. The contractor will perform weekly record updates using CAIRS (e.g. building /terminal/cable/telephone/LEN/pair count updates/Trouble Ticket inputs & updates). Some updates may require the contractor to manually enter the data upon completion of individual work orders or record changes. The contractor will also maintain cable pair assignment records using CAIRS. The contractor will ensure their employees are fully trained on CAIRS.net as needed.

1.2.12.11.2. Account Set-up & Training. The contractor will establish a CAIRS account for each assigned Government COR, and provide system program training. The contractor will perform CAIRS account set-up and conduct training quarterly, and/or upon appointment of a new

COR.

1.2.12.12. CVC

1.2.12.12.1. Maintain CVC. The contractor will provide a CVC technician to update all cable plant records in CVC for DMAFB. The contractor will update and maintain CVC when provided red line drawing from the COR, or upon installing any new communications infrastructure on

DMAFB. The contractor will coordinate with the COR and maintain the CVC, IAW industry standards, Technical Order (TO) 00-33A-1001, General Cyberspace Support Activities Management Procedures and Practice Requirements, and Methods and Procedures Technical Order (MPTO) 00-33D-3003, Managing the Cyberspace Infrastructure with the Cyberspace Infrastructure Planning System. Technical Order (MPTO) 00-33D-3004-WA, Managing Cable and Antenna with the Cyberspace Infrastructure Planning System (CIPS) Visual Component

(CVC).

1.2.12.12.2. Update CVC. The contractor will produce, update, and post changes to drawings, plant records or documents using Government-provided forms, software, and web browser applications (CIPS). The contractor will load, edit, update and maintain base drawing information, for the outside plant, in the CVC database IAW industry standards and TO 00-33A- 1001. The contractor will transfer to the CVC database all pertinent outside plant CFD information from administrative and maintenance 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 will 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 (Government or contractor) when tasked through the work order process. A separate pre-priced Sub-contract Line Item Number (SLIN)/Product Identifications (PID) will be used for conversion of third party as-built drawings, document, or electronic data information. The contractor will verify contractor-entered information, accuracy, and completeness. The 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.12.16.1, Global Positioning System (GPS) Service Data. When the update is completed, the contractor will close the session and notify the Communications- Computer Systems Installation Record (CSIR) Manager that the session edit is ready to be approved. The COR will review the contractor’s edit session and quality control approve or reject each contractor’s Live Direct Session Edit by inspecting each feature added or modified during the Live Direct Edit Session.

1.2.12.12.3. CIPS Account. The contractor and all on-site staffed employees will have a CIPS account in order to use CVC. The contractor will 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. CIPS accounts should be activated once on-site personnel are hired.

1.2.12.12.4. As-Built Records. Once a project is completed and the new base infrastructure is loaded into CVC, the contractor will submit the soft copy of the newly constructed area to the COR. The COR will then load that file into a share drive for filing purposes.

1.2.12.12.5. As-Built Drawings. All contractor and third party as-built drawings submitted to the COR will be in VISIO or CVC format as directed by the COR. The contractor will provide correctly annotated paper copies in addition to the electronic files until the electronic submittal process has been validated at which time the paper copy requirement may be waived. Color plots of electronic files are acceptable, providing they show the same information that would be shown in a manually marked up drawing.

1.2.12.12.5.1. The contractor will produce drawings to support engineering initiatives.

1.2.12.12.5.2. All electronic submissions will comply with the industry standards:

1.2.12.12.5.3. The contractor’s as-built drawings will be submitted to the COR and input into CVC. The 38th Cyberspace Engineering Group (38 CEG) will quality assure updates/as-builts from any Government or contracting activity, the COR, or the contractor.

1.2.12.13. Global Positioning System (GPS)

1.2.12.13.1. Global Positioning System (GPS) Service Data (for any GPS requirement). The contractor will 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 PWS paragraph

1.2.12.15. and Appendix A, Global Positioning System Service Documents.

1.2.12.13.2. Global Positioning System (GPS) Service. The contractor will 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. The contractor will ensure data compatibility with the CVC database and will upload the data into the CVC database.

1.2.12.13.2.1. The contractor will use GPS equipment and technology supplemented with electronic underground cable locating equipment and land surveying operations necessary to collect required CFD following the Federal Geographic Data Committee (FGDC)-STD-007.4- 2002 specified in PWS Appendix B.

1.2.12.13.2.2. Each communication feature requiring geospatial coordinates will 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 Federal Geographic Data Committee (FGDC)-STD-007.3-1998, specified in PWS Appendix A.

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

Geospatial coordinate data for the location of utility lines will 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.2.12.13.2.4. The contractor will provide 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.12.13.2.5. The contractor will store and submit GPS collected CFD attribute, metadata, and location information 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/. Its format will 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 will 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 will have a geospatial reference (.prj) file included that specifies the parameters of the coordinate system.

1.2.12.13.2.6. The contractor will 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 in Appendix A, Global Positioning System Service Documents.

1.2.12.13.2.7. The contractor will collect CFD in GPS data loggers and will use Table A to produce the CFD data dictionary for use in the logger.

1.2.12.13.2.8. For each set of CFD collected using GPS, the contractor will complete all metadata elements marked mandatory as defined by the Content Standard for Digital Geospatial Metadata FGDC –STD-001-1998 specified in PWS Appendix B. Metadata will be formatted and stored as an XML document compatible with the submitted shape files and software of the organization specified in PWS paragraph 1.2.12.16.2.1.

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

1.2.16.16.1.2. will 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.12.13.2.10. Geospatial data will overlay on the installation’s current GeoBase Common Installation Picture (CIP) provided in the Air Force Porta1 accessible CVC. The collected data will incorporate the coordinate and projection system of the CVC. The collected data will incorporate the datum and the coordinate and projection system of Davis Monthan AFB, AZ CIP which is: World Geodetic System 1984 (WGS1984) UTM Zone 12, (108 to 114 degrees West) Latitude Band S (32 to 40 degrees North).

1.2.12.13.3. Quality Control. The contractor will 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 will 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.2.12.13.4. GPS Service Data Maintenance. The contractor will maintain CFD shape files, metadata XML files, the quality control report, and calculation worksheets validating the NSSDA accuracy statement on-site in an orderly manner. The contractor will make available such documentation to COR, when requested, for reviews to ensure compliance with GPS service guidance.

Updating CVC with GPS Collected CFD. The contractor will store the collected OSP infrastructure features and communications pathways shape files in the local Government-provided computer workstation, and will 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/ or search for CIPS at the Air Force Portal

1.2.13. Contractor Maintained Items with Government Tier 2 & 3 Support. This section identifies the items, equipment, material, and facilities to be maintained by contractor.

1.2.13.1.