Attachment 1 - PWS (10 November 2021).pdf

Solicitation FA452821R0010 Attachment 1

U.S. Air Force 10 November 2021

BASE TELECOMMUNICATION

SERVICE

Performance Work Statement

1.0 DESCRIPTION OF SERVICES

1.1 Scope of the Work

The Contractor shall provide all personnel, equipment, tools, materials, vehicles, supervision and other items and services. Work under this PWS will support the mission of 5th Communications Squadron at Minot AFB as well as the Missile Alert Facilities (MAFs) by providing highly reliable wired telecommunications and networked voice, video and data services associated with AVAYA and CISCO (see appendix 2). The Contractor shall perform Operation and Maintenance (O&M) and other services required to ensure the Base Telecommunications System (BTS) is available 24 hours per day, 7 days per week. The BTS consists of the base telephone system switch, inside plant (ISP) systems, outside plant (OSP), network, transmission systems, and all associated equipment described in Appendix 2, which may include other systems (e.g. radio, etc.). The Contractor will be responsible for all cross-connects at each building that needs a telephone number changed. The Contractor shall operate and maintain all BTS equipment and systems in accordance with (IAW) the Original Equipment Manufacturers’ (OEM) technical manuals and specifications, Department of Defense (DoD) and AF policy and regulations, applicable federal, state, and local laws and regulations. Since this location is a northern tier base, contractor must plan appropriately for adverse winter conditions, and the follow-on increase in warm-weather construction activity base-wide.

1.2 General Requirements

1.2.1 Continuation of Mission Essential Services During Crisis IAW Defense Federal Acquisition Regulation Supplement (DFARS) clause 252.237.7023, it is determined that the O&M services in PWS paragraphs 1.3, 1.3.1, and 1.3.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. The Contractor may be required to support base mission changes; major or minor BTS infrastructure modifications; and other support requirements necessary for the BTS to meet mission requirements. Base exercises or real-world base security events frequently interrupt missions. Support requirements may originate from technology changes, hardware and software systems upgrade, reconfigurations, new or additional equipment, and Dial Central Office (DCO) reconfigurations.

This includes routing/diversity requirements and any other environmental changes that could impact or alter the

BTS.

1.2.2 Accident/Incident Reporting and Investigation

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

1.2.3 Subcontractor Compliance

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

The Contractor shall include a provision in all subcontracts to require Subcontractor compliance with terms and conditions of this contract.

1.2.4 Base Civil Engineering work Clearance Requests

The Contractor shall prepare and coordinate a Base Civil Engineering Work Clearance Request, AF Form 103, prior to any trenching, digging, manhole or handhole entry. The Contractor shall notify the facility manager to submit an AF Form 332, Base Civil Engineer Work Request, prior to any work requiring structural modification to the facility.

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, Air Force Occupational Safety and Health (AFOSH), any local procedures and other provisions of this contract.

1.2.5 Equipment

The contractor is responsible for ensuring all tools and test equipment needed for performing daily O&M functions and completing work orders are on site. (ADD) Any specialized equipment outside of daily use can be procured as needed. (ADD) (ie lift, jackhammer etc).

1.2.6 Personnel

The Contractor is solely responsible for ensuring sufficient personnel are assigned to this contract and all personnel are qualified and certified at a minimum on Security +, CUCM administration, AVAYA administration, and ISP/OSP installer II 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 including current certifications for all voice switching systems. The Contractor shall ensure personnel also meet the criterion stated in its proposal for this requirement. The Contractor is solely responsible for compliance with OSHA standards for the protection of their employees. The Contract Manager shall ensure specific safety requirements in AFOSH standards are complied with by Contractor Personnel when non-compliance would clearly present the potential to harm or damage government resources. The AF is not responsible for ensuring that Contractors comply with personal safety requirements that do not present the potential to damage government resources. The Contractor shall not employ persons for work on this contract if such employee is identified to the Contractor by the Contracting Officer as a potential threat to the health, safety, security, general well-being or operational mission of the installation and its population. Contractor Personnel shall present a neat appearance and be easily recognized as Contractor employees.

1.2.7 Key Personnel Listing

Upon the start of the contract, the Contractor shall provide an onsite Prime Contract Manager who shall be responsible for the performance of the work. The name of this person, and an alternate or alternates, who shall act for the Contractor when the Manager is absent, shall be designated in writing to the Contracting Officer. The Contract Manager or alternate shall have full authority to act for the Contractor on all contract matters relating to daily operation of this contract. Contractor shall provide a key personnel listing and contact information to the COR prior to commencing work and update information on a continual basis as changes occur to ensure it is always current and correct throughout the life of the contract. All personnel shall be proficient in understanding, reading, writing, and speaking the English language. The key personnel list shall identify the employees’ names, function they support, whether they are supporting O&M or work orders, and what percentage of each.

1.2.8 Contractor Identification

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

1.3 Operate and Maintain (O&M) Requirements

Overall responsibility to properly operate and maintain the BTS shall rest with Contractor as described by the maintenance support plan (MSP) (see PWS section 1.3.12, BTS Work Center Records) and the OEM’s recommended procedures. Appendix 2 identifies equipment and items the contractor will be responsible to maintain.

O&M actions include all actions taken by the Contractor to operate and maintain equipment and systems in a serviceable condition or to restore it to a serviceable condition to include purchasing of commercially available parts, inspection, periodic testing, adjustment, and repair. O&M responsibilities include all pre-existing cabling infrastructure as is, to include ISP and OSP, all terminals, building terminals, pedestals, and copper and fiber optic splices. The effort may include the replacement of defective circuit packs and Customer Premise Equipment (CPE), preventive maintenance IAW applicable publications (OEM, Appendix 5, and otherwise specifically listed herein) and other routine work to optimize the life expectancy of the equipment and cable systems. Work orders will be accomplished IAW PWS Section 1.4. The Contractor shall not postpone or otherwise delay O&M efforts to accomplish work orders. The Contractor is responsible for completing both O&M and work orders simultaneously to ensure contractual timelines are met for both.

1.3.1 Telephone Switch System O&M

The Contractor shall operate and maintain the system(s) identified in Appendix 2. The Government will measure the acceptable standard performance level by a determination of the total systems availability (up time) and reliability rating during any given month. All existing, new equipment, cabling, or services installed by the Contractor shall automatically become part of the O&M services. This includes, but is not limited to, O&M Requests such as: basic switch actions such as installation of VOIP cards; removal of existing switch components; activation/de-activation of phone lines; installation of purchased parts covered under section 1.4 of existing equipment being maintained under Contract Line Item Numbers (CLIN) X001; management; administration and maintenance; performing software functions (i.e. number reclamation) and translations for any trunk or circuit of configurations required by on-base systems or users; data administration; trouble assistance; and records administration. O&M shall also include Voice over Internet Protocol (VoIP) operations as part of the BTS. Demarcation of VoIP maintenance shall not extend beyond the Voice Gateway and Call Manager(s). See Paragraph 1.5.2 for security requirements.

Approximately 50 O&M Requests are estimated per month which may affect multiple actions per request. The contractor will provide the COR with the completion date of O&M Requests IAW PWS section 1.3.4.3.

1.3.1.1 Voice over Internet Protocol (VoIP)

The Contractor shall provide CISCO and AVAYA VoIP operation to include installation of end user items as part of the BTS. This includes management, administration and maintenance, perform software functions and translations for any trunk or circuit configurations required by on base (to include the 15 MAFs) systems or users, perform add, move, change, delete, query of a circuit or system data, service/work order, trouble assistance and records administration. VoIP equipment is identified in Appendix 2. (Verify and update)

1.3.2 Perform Inside Plant (ISP) & Outside Plant (OSP) O&M

Contractor shall maintain ISP & OSP cable and equipment as identified in Appendix 2 and IAW applicable documents listed in Appendix 5 of this PWS. Upon request by the COR, the contractor will perform end to end testing on existing ISP/OSP cabling. Applicable commercial standards apply to all testing and test results will be delivered to the COR for acceptance. Preexisting cable infrastructure will be the responsibility of the contractor, as well as all repairs to include all demarcation points and faulty wiring to include horizontal cabling and cross connects.

1.3.3 Preventive Maintenance Inspections (PMIs)

Contractor shall perform PMIs as required on all systems covered by this contract IAW OEM recommended or established schedules and/or manuals. Contractor shall elevate any problems and identify any trends to the COR in writing within 1 workday. Contractor shall correct deficiencies IAW 1.3.12.14.

1.3.3.1 Switch Power Test

The Contractor shall perform scheduled PMI tests of the telephone switch backup power system. PMIs shall test and document the power systems identified in Appendix 2. Each power system shall be tested IAW OEM specifications.

Test results shall be documented IAW PWS section 1.3.12.14.

1.3.3.2 Spare Conductor Test

Contractor shall perform a scheduled PMI test of all spare conductors. PMIs shall test and document at least two selected, out of service pair (one low and one high numbered pair) in each 25-pair group of every cable terminating in the DCO. These PMI tests are to be accomplished quarterly. Test results shall be documented IAW PWS section 1.3.12.14.

1.3.3.3 Fiber Strand Utilization

The Contractor shall inspect 25 COR-accepted fiber terminals (which will not be the same terminals) per year.

Additional inspections over 25 each shall be accomplished as a work order IAW PWS section 1.4. The Contractor shall inspect each terminal for the following discrepancies and correct as required:

Verify the correct location, number and cable count.

Document open fiber ports

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

Ensure cable is tagged correctly.

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

Ensure terminal is properly secured and is clean.

Update the CVC database with descriptive information.

1.3.3.4 Manholes and/or Handholes

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

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

All cables will be racked to the manhole cable supports.

All ducts (vacant or occupied) will be sealed.

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

Update the CVC database - for the manhole or handhole and record all descriptive information for splices, cables, ducts and other communication features in the manhole or handhole.

Check Locking lids/identify and place work order with COR for new locks.

1.3.3.5 Terminals

The Contractor shall inspect 25 COR-accepted copper terminals (which will not be the same terminals) per year.

Additional inspections over 25 each shall be accomplished as a work order IAW PWS section 1.4. The Contractor shall inspect each terminal for the following discrepancies and correct as required:

Verify the correct location, number and cable count.

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

Ensure cable is tagged correctly.

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

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

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

Update CAIRS or approved cable tracking systems (i.e. cable record book)

1.3.3.6 Distribution Pedestal Terminals

The Contractor shall inspect 12 COR-accepted Distribution Pedestal terminals (which will not be the same terminals) per year. Additional inspections over 12 each shall be accomplished as a work order IAW PWS section

1.4. The Contractor shall inspect each terminal for the following and correct as required:

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

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

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

If conductors are found to be damaged or unserviceable, repair damage conductors with a new section and a buried splice case or with remaining slack.

Ensure terminal is correctly installed.

Verify all working numbers and remove any unused.

Remove all unused cross-connects.

1.3.3.7 Cable Analysis

The Contractor shall review Configuration Accounting Information Retrieval System (CAIRS) records quarterly and perform cable analysis and phone population accuracy. The Contractor shall determine the number of bad pair(s) in each cable and report the percentage in each cable to COR. The Contractor shall also determine the cable fill rates and report to COR. Update CVC as necessary to record accurate cable information.

1.3.4 System and Service Outages and Trouble Calls/ Tickets

1.3.4.1 Contractor Availability

The Government shall be able to contact Contractor personnel 100% of the time. The Contractor shall respond in case of emergencies, outages, alerts and exercises, 24 hours a day, 7 days per week. If contacted, the Contractor shall report for duty and provide services as necessary until the emergency, alert, or exercise is completed. There will be approximately 15 trouble tickets per month. The contractor will provide the COR with the completion date of Trouble Tickets IAW PWS section 1.3.4.3.

1.3.4.2 Scheduled Outages

Contractor shall identify, coordinate, and schedule service outages with the COR. The Contractor shall schedule such outages to minimize inconvenience to users based upon Government user work schedules. This may require working outside of normal duty hours. The user must release all affected equipment and circuits prior to any service disruption. The Contractor shall follow established local procedures for scheduling and implementing scheduled outages. Notification shall include the reason for the interruption, start and stop times, duration and the equipment, lines, and buildings affected. The Contractor shall log the outage IAW the guidance in PWS section 1.3.12.14.

1.3.4.3 Restoration/ Completion of Outages, Trouble Calls/ Tickets, Work Orders, and O&M Requests The COR will assign the category of the outage/trouble and establish the repair priority. The Contractor shall respond and initiate repair actions within the specified time listed below from the time the COR advises the Contractor of the problem. However, exceptions to time limits may be allowed, with the written approval of the COR or CO, with appropriate justification.

The contractor shall repair and/or restore services in the priority order determined by the COR. The Restoration Priority List (RPL) shall apply in the absence of the COR. The Contractor shall continue to work on repair actions until service is restored based on priority. The Contractor shall work closely with the COR on all repairs/service or system outages, trouble calls/tickets, O&M Requests, and Work Orders and notify the COR in writing upon restoration of service providing the time service was restored and a description of repair action. The Contractor shall coordinate with Network Infrastructure to restore any Internet Protocol (IP) phone set outages. The Contractor shall log the outage IAW the guidance in PWS section 1.3.12.14. Outage/trouble ticket call, Work Orders, and O&M Request categories are further defined as:

1.3.4.3.1 Emergency

Contractor shall respond on-site within 2 hours and restore service within 8 hours unless otherwise approved by the COR in writing. Expedition of parts and/or labor is required (at contractors expense) at no additional charge. If an outage/trouble ticket, Work Order, or O&M Request significantly affects a mission, the COR may declare an Emergency classification. Emergencies are classified as any of the following:

Loss of over 50% or more of total call handling capability of any communications system

Loss of any Primary or Secondary Crash System or any portion thereof Affects security or emergency type operations, including Emergency Operations Center (EOC);

as well as those affecting safety Affect specifically identified events and/or exercises

Loss of Voice service affecting 100 or more users

Failure of one or more circuits listed in the Base RPL

1.3.4.3.2 Priority

Contractor shall respond on-site within 6 hours and restore service as soon as possible, but shall not exceed 3 working days. Expedition of parts or labor may be required at no additional charge. Priority is 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 2

Total loss of telephone service within a building IAW RPL or COR guidance Loss of LAN connectivity affecting 15-99 users

1.3.4.3.3 Routine

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

1.3.4.3.4 Outage/Trouble Cause Identification

The Contractor shall determine if a recorded problem or system failure is attributable to the BTS or other causes.

The Contractor shall immediately notify the COR if the malfunction is determined to be due to other causes (outside the Contractor-maintained system/equipment). The Contractor may be liable for the cost of any third-party service calls or charges necessary to isolate and repair the problem if it is later determined that the cause of failure is related to the BTS or failure of proper O&M of the system.

1.3.5 Cable Location, Staking, and Marking

The Contractor shall locate, stake, and mark up to 60,000 feet of encased or direct buried conduits/cable per year when requested by the COR. Marking shall be within one foot of the actual location at ten-foot intervals and at direction changes. The marking shall begin two feet outside the point of entry into the work area and shall continue two feet past the point of exit from the work area.

Contractor shall complete location, staking and marking within the specified time listed below from the time the COR advises the Contractor of the requirement unless additional time is permitted by the COR. The Contractor shall comply with the following timelines for location, staking, and marking:

Emergency: Within 1 hour of notification to include off duty and weekends.

Priority: Within 6 Hours of notification.

Routine: Within 3 business days of notification.

1.3.6 System Cross-Connect and Disconnect Services

Contractor shall perform system cross-connect and disconnect services. All cross-connects and disconnects, which are required or incidental to the performance of O&M actions (including those outside of the DCO), shall be included as part of the O&M service. Ex. Phone circuit moves, relocating a phone etc.

1.3.7 Voice Mail

The Contractor shall provide voice mail O&M. This includes, but is not limited to: management and administration of system network table and networking plan for multiple systems; additions; deletions; modifications to user’s mailbox; password resets; distribution list; holiday schedule tables; daylight savings time; synchronization with the phone switch; and proper functioning of the auto attendant feature, and CISCO UNITY and AVAYA voice mail system, to include replacement and repair of malfunctioning voice mail related hardware. Functions also include diagnostic, maintenance, and minor programming changes on current software applications. System backup includes backup of system configuration, names, and print “list all” of database.

1.3.8 Voice Protection System (VPS)

The routine maintenance of the VPS system is via MAJCOM Communication Control Center (MCCC). The Contractor shall respond to any requests for local maintenance as directed.

1.3.9 Traffic Measurement and Analysis

The Contractor shall perform traffic measurement and analysis reporting once every quarter and up to 8 additional reports in a year as requested by the COR. The Contractor shall perform traffic measurement and analysis within system capabilities and limitations and perform analyses and studies on the base switching system when requested by the COR. The Government may also request measurement and analysis for a particular line or group of lines. The information required by the contract must cover no less than a 5-day period, (Monday-Friday, excluding holidays), and include, at a minimum, the following:

A. Trunk Traffic Summary identifying each trunk group by: number, name, description, direction, and the desired Grade of Service (GOS).

B. Individual analysis of each trunk group by:

1. Number and name

2. Type

3. Quantity (total and working)

4. Average busy hour

5. Maximum usage

6. Average minimum usage

7. Average maximum usage/trunk

8. Percent occupancy at average maximum usage

9. Current GOS at average maximum usage

10. Number of trunks required for recommended GOS

11. Recommendations based on the information provided in the analysis

1.3.10 Contractor Support Services

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

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

1.3.10.2 Contractor Interface and Support for Other Vendors

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

1.3.10.3 Workload/ Status Meetings

The BTS Manager shall attend local meetings with the COR(s) and Communications Squadron Plans Office to discuss status of current and future work orders, trouble tickets, outages, PMIs, or any other work/event that may impact contractual performance. The Contractor shall provide a list of work orders and trouble tickets at the meeting for reconciliation and discussion with the COR(s), Contracting Officer, or other personnel (approved by the CORs or CO).

1.3.10.4 Design Review Meetings

The Contractor shall review program or project drawings and provide comments concerning communications requirements within ten working days from receipt when requested by the COR. The Contractor shall participate in designated design review meetings identified by the COR. The BTS manager shall attend up to four design review meetings per month.

1.3.11 Technical Solutions

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

1.3.12 BTS Work Center Records

The Contractor will use Remedy and CIPS to document all work performed. Contractor may develop and maintain separate BTS work center records. The Contractor shall update work center records within 2 duty days after completion of the associated task(s) unless specified differently within this section. All BTS records and documents established and maintained by the Contractor are Government property and shall remain at the site and be turned over to the COR for disposition upon contract completion. Failure to do so may result in withholding of final payment until all records are recovered or in a reduction in final payment for records lost or misplaced. The Government requires electronic maintenance and storage of records, unless otherwise specified herein. The Contractor shall identify all acronyms, codes, abbreviations, signs and symbols used in each record. The Contractor shall use the same format for initial and all subsequent submissions of the same record unless otherwise approved by the CO. All records shall be readily available for review by the COR and CA, and other personnel (authorized in writing by the CO). The Contractor shall update all errors found or identified during review of the work center records. Contractor shall develop, update and/or maintain accurate, complete, and readable work center records as listed below:

1.3.12.1 Maintenance Support Plan (MSP)

The MSP shall enable the scheduling and tracking of preventive maintenance actions on Contractor- maintained equipment. This record shall be available within 30 calendar days after period of performance begins. When changes occur that affect the MSP, revisions shall be submitted within 10 work days after the effective change (e.g.

modification adding equipment) unless otherwise requested by the CO (e.g. with the proposal to add new equipment to maintenance). The Government will review and approve, or provide the Contractor with required corrections.

Changes may be implemented only after CO approval. The MSP shall contain as a minimum: a schedule of PMIs due on each piece of equipment being maintained (Appendix 2) for the life of the contract IAW equipment manufacturer’s recommendations; alarm notification procedures; and specific maintenance tasks to be performed on each system.

1.3.12.2 PMI Inspection Records and Malfunction Record

PMI Inspection records shall, at a minimum, contain: the date and time inspection was performed; a short description of inspection conducted; malfunctions or problems annotated on record with equipment data, serial number, etc.; the corrective action taken by the Contractor; and the initials of the technician performing the inspection. The Contractor shall use IMDS (or COR-approved substitute) for tracking purposes.

1.3.12.3 Maintenance/ Repair Logs (e.g. maintenance actions, trouble tickets) Contractor shall use Remedy or approved AF GIS system per the COR to maintain an accurate and legible BTS Maintenance/Repair Log to show all maintenance and inspections (other than PMIs) performed during each 24-hour period as a result of trouble report actions or scheduled or unscheduled outages.

1.3.12.4 Manhole, Handhole, and Building Terminal Inspection/ Maintenance/ Repair Contractor shall maintain manhole, handhole, distribution pedestal terminal, and building terminal inspection records as defined in PWS Section 1.3.3.4, 1.3.3.5, and 1.3.3.6. The Contractor shall update the CVC database with pertinent cable feature data (CFD) information gathered during the inspections. The record shall be available for inspection and analysis by the Government. If other electronic documentation is implemented, the Contractor shall grant the Government access to those records

1.3.12.5 Cable Installation/Repair Test Results

Contractor shall develop and maintain a cable installation repair test results record after the installation or repair of an outside plant cable. Graphics and pictorials may be used to illustrate. The record shall, at a minimum, contain the purpose of test/inspection; complete identification of item tested/inspected and test equipment used; complete description of the physical set-up (e.g., item, facility, and equipment used); complete description of procedures used;

copy of results/analysis; actual recorded data (e.g., instrument readings) (if extensive, provide as an appendix);

conclusions and recommendations; and authentication of results and acceptability. The Contractor shall update the CVC database with pertinent CFD information resulting from installation or repair.

1.3.12.6 Communications and Information Systems Installation Record (CSIR)

1.3.12.6.1 Contractor shall produce, update, and post changes to drawings, plant records or documents using Government-provided forms, software, and web browser applications. Contractor shall load, edit, update and maintain CSIR information, for the outside plant, in the CVC database IAW AFI33-101 and TO 00-33A-1001.

Contractor shall transfer to the CVC database all pertinent outside plant CFD information from administrative and maintenance CSIR, Legacy CSIRs, work orders, inspection records, as-built and as-installed marked-up drawings, and GPS services produced as a result of the Contractor’s operations. The Contractor shall update the CVC database with outside plant information from as-built drawings or other pertinent documents or electronic data pertaining to work done by third parties (organic or Contractor) when tasked through the work order process. Contractor is responsible for verifying Contractor-entered information, accuracy, and completeness. Contractor will use the CVC Viewer/Editor to update the CVC by opening and utilizing Live Direct Edit Sessions. During the edit session, the Contractor will update CVC with as-built information or with information transcribed from shape files created or produced in accordance with PWS paragraph

1.3.12.6.2 When the update is completed, the Contractor will close the session and notify the CISR Manager the session edit is ready to be approved. The CSIR Manager will review the Contractor’s edit session and Quality Control (QC) approve or reject each Contractor’s Live Direct Session Edit by inspecting each feature added or modified during the Live Direct Edit Session. The CSIR Manager will notify the Contractor of each feature that was rejected during the QC process in order for the Contractor to take corrective action.

1.3.12.6.3 The Contractor shall have a CIPS account in order to use CVC. The Contractor shall apply for a new account by visiting the website at https://cipsaf.tinker.af.mil/cips.

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

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

1.3.12.8 Contractor-Furnished Hazardous Material

Contractors must obtain an authorization prior to bringing any hazardous materials (Federal Standard 313) on Air Force installations. Contractors must submit all required documentation including appropriate Hazardous Materials Authorization Information Form, Material Safety Data Sheet (MSDS) and projected usage information to 5 CES/CEAN through the Contracting Officer at least 15 days before the HAZMAT is brought onto Minot AFB and facilities within the Missile Field. This review is to ensure that no Air Force restricted hazardous materials are being proposed for use. The contractor will comply with current Federal Acquisition Regulation (FAR) 52.223-5. Prime contractors shall be responsible for reporting hazardous material used by subcontractors. FAR 52.223-3 provides guidance on Hazardous Material Identification and Material Safety Data. The contractor shall maintain MSDSs for all hazardous materials used on base and the MSDSs shall be on file on site at the construction site office at all times. The contractor shall send 5 CES/CEAN via the Contracting Officer a MSDS for any new material not initially identified, the volume being brought on base, and its storage location. The MSDS shall be submitted to 5 CES/CEAN. All hazardous materials used by the contractor on Minot AFB property shall be stored properly in segregated areas in accordance with all regulatory and MAFB Fire Department requirements. 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. Contractor will comply with base HAZMAT policy.

1.3.12.9 Equipment Inventory Records (PWS Appendix 2)

The Contractor shall maintain a working copy of Appendix 2. Appendix 2 shall identify equipment installed, changed, or removed via contract modification or the work order process identified in PWS section 1.4. The record shall include all assemblies of the equipment configuration, which would be logically disassembled from the total configuration for the purpose of packing and shipping. The Contractor shall update the record when individual work orders are completed using approved information systems.

1.3.12.10 Telecommunications Management System (TMS)

The TMS currently in use at Minot AFB is Configuration Accounting Information Retrieval System. The Contractor shall perform daily record updates using the current TMS. 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 the current TMS. The Contractor shall conduct at a minimum but not limited to; 75 telephone circuit audits which are to include different telephone circuits per month, update records using the current TMS and inform the COR when monthly audit has been completed.

1.3.12.11 Work Order Records, Including Warranty Records

The Contractor shall develop and maintain work orders. The Contractor shall update work center records within 2 working days after completion of the task(s) specified on individual work orders and notify the COR in writing.

Physical records of work orders in process shall be retained and available locally (on base). Upon completion of work order, documentation will be uploaded into CIPS.

1.3.12.12 System Capacity Records

Contractor shall produce system capacity records quarterly and upon request by the COR. Records shall include each cable and terminated cable count, type of cable (bad and spare), and number of conductors used. Quarterly system capacity records shall be produced for the host switch and remotes. The records shall include total line ports, line ports in use, line port type (analog/digital/ISDN/etc.) total used, and DS-1 digital trunk ports (total ports used and available).

1.3.12.13 System Security Audit Record

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

1.3.12.14 Quality Control Plan (QCP)

Contractor shall develop a highly effective QCP for all services provided under this PWS. The Contracting Officer will notify the Contractor of acceptance or required modifications to the plan before the contract start date. The Contractor shall make appropriate modifications and obtain acceptance of the plan by the Contracting Officer. The QCP shall remain in effect during the term of the contract (including any option periods if exercised). The Contractor shall: maintain the QCP; retain a copy on site; and ensure availability at all times to all members of their on-site staff, as well as the COR and CA. The Contractor’s QCP shall reflect depot-level Contractor logistic support, centralized maintenance and remote monitoring from the Integrated Network Operations and Security Center (I- NOSC) and refrain from relying on Government CORs as a means to ensure their own quality control. The Contractor shall notify the parties specified in this paragraph of any changes to the QCP at least 10 work days prior to implementation of those changes. The contractor shall develop, implement and maintain a comprehensive QC Program that assures compliance with all requirements of this PWS. Safety violation(s) and deviation(s) from established technical data will constitute an unsatisfactory condition(s) and will be documented as such.

If the Contractor exceeds the error rate as listed on the Service Summary, they may be subject to a lower performance evaluation rating. The QCP shall also include procedures for training, qualification and any required certification of employees prior to performance of assigned duties under this contract. Procedures shall include assignment of management responsibility for employee task qualification to specific positions/individuals within the Contractor’s organization, as well as the quality control process that will be utilized to ensure compliance and a description of the records to be kept to document inspections and corrective or preventive actions taken. The records of inspections shall be kept and made available to the Government throughout the contract performance period and for the period after contract completion until final settlement of any claims under this contract.

1.3.12.15 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.12.17.1 and 1.3.12.17.2 for any GPS requirement.

1.3.12.16 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 CVC database and shall upload the data into the CVC database.

1.3.12.16.1 The Contractor shall use GPS equipment and technology supplemented with electronic underground cable locating equipment and land surveying operations necessary to collect required Communication Feature Data (CFD) following the Federal Geographic Data Committee (FGDC)-STD-007.4-2002 specified in PWS Appendix 5.

1.3.12.16.2 Each communication feature requiring geospatial coordinates shall be located to within one meter of its true ground position, in the horizontal plane, with a 95% spatial accuracy confidence level as defined in FGDC- STD-007.3-1998, specified in PWS Appendix 5.

1.3.12.16.3 Geospatial coordinates for the location of manholes and cable vaults shall be recorded for the center of the manhole lid. Geospatial coordinates for the location of handholes, pull boxes, pedestals, and buried splices shall be recorded for the top center of the feature. Geospatial coordinate data for the location of utility lines shall be recorded at a minimum every 50 feet, and each turn or bend in a cable installation pathway must also be recorded so the coordinates for any point along the turn pathway will fall within the allowable accuracy.

1.3.12.17 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 format.

1.3.12.17.1 The GPS collected CFD attribute, metadata, and location information shall be stored and submitted in an Environmental Systems Research Institute (ESRI) Shape File format. The shape files must be compatible with the CVC Viewer/Editor web-browser application, currently accessible at https://cipsaf.tinker.af.mil/cips/mycips.aspx.

Its format shall be within a folder named the same as the prefix of the shape file. For Example, if the shape file is named "points_lafb_28.shp" the folder would be named "points_lafb_28”. The folder shall contain all the files that make up the general shape file, i.e., “.shp”, “.shx”, “.dbf”, etc. along with the specified metadata file. The shape files shall have a geospatial reference (.prj) file included that specifies the parameters of the coordinate system.

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

1.3.12.17.2.1 The Contractor shall collect CFD in GPS data loggers and will use a CFD data dictionary for use in the logger.

1.3.12.17.2.1.1 For each 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. Documents should be compatible with the submitted shape files and software of the organization specified in Paragraph 1.3.12.17.1.

1.3.12.17.2.2 Calculation worksheets showing compliance with National Standard for Spatial Data Accuracy (NSSDA) statement at the 95% confidence level as required by Paragraph 1.3.12.19 shall be submitted as an Excel (.xls) file. Example calculation worksheets in Excel format can be downloaded from a FGDC website:

http://www.fgdc.gov/.

1.3.12.17.2.3 Geospatial Data

Geospatial data shall 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 datum and the coordinate and projection system of Minot AFB, ND “GCS_North_American_1983” UTM Zone 14N, 15N, 16N.

1.3.12.18 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 overshoot, undershoots, dangles or intersections in the line work.

B. Features shall be snapped where applicable, for example, GPS Db splice 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.3.12.19 Maintenance of GPS Service Data

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

1.3.12.20 Updating CVC with GPS Collected CFD

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

1.4 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 wiring 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. All work orders will include a technical solution. 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. The Equipment and Installation Performance Specification (EIPS), Solicitation Attachment 15, provides detailed descriptions of the material and labor effort (e.g. material, labor, and incidentals for installation, removal, and/or relocation) required by the attached Pricing Table and identified by PIDs. When an item required to complete a work order is not pre-priced within the Pricing Table, the Government may negotiate the addition of these items, negotiate a special project or opt to use another vehicle to accomplish the task.

1.4.1 Work Order Authorization

Any work order required that is $10,000 or less shall be the price that is most advantageous to the Government and is authorized for approval by the COR. Any work order that exceeds this amount is required to be approved by the CO. Orders shall not be split to avoid exceeding the threshold.The contractor shall provide backup documentation to support price reasonableness (best value to the Government) for work orders. Work order items that include services require appropriate justification for pricing reasonableness.

1.4.2 Work Order Procedures

1.4.2.1 Work Orders modified by the Contractor after issuance shall be submitted to the COR for approval prior to work completion. All work orders shall be submitted to the contractor through CIPS work order system (WOS).

1.4.2.2 All work orders issued hereunder are subject to the terms and conditions of the contract.The Contractor shall refer any questions, concerns, or disputes concerning work orders to the COR in writing within 24 hours (2 hours for emergencies) of receipt of the work order. In the case of misunderstanding or concern, the Contractor does 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.4.2.3 Work orders will be accomplished during normal duty hours; however, occasions may arise that require work to be accomplished outside of these hours. The Contractor shall be responsible for covering such situations with adequate personnel and completing the work within the stipulated time. Premium pay per appropriate labor law is included within the pre-priced items for work orders (see PWS Section 1.4.7)

1.4.3 Work…