BTS_PWS.pdf

PDF 340 KB Posted

Attached to
Base Telecommunication Services at Robins AFB Federal contract opportunity
Solicitation number
FA8501-18-F-0175
Issued by
Department of the Air Force Materiel Command Lifecycle Management Center Robins Air Force Base

About this file

Performance Work Statement, dated 31 May 2018

View the file

Other files for this federal contract opportunity

Other files attached to Base Telecommunication Services at Robins AFB, newest first.
File Type Posted
EFO_-_BTS_Robins_AFB_-_redacted_Redacted.pdf PDF

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

PERFORMANCE WORK STATEMENT (PWS)

OPERATIONS AND MAINTENANCE SERVICES

BASE TELECOMMUNICATIONS SYSTEM (BTS)

ROBINS AFB GA

31 May 2018

1.0 DESCRIPTION OF SERVICES The contractor shall provide all personnel, equipment, parts, material, vehicles, tools, labor and services (except as listed in Section 3, Government Furnished Property and Services) necessary to provide operations and maintenance (O&M) for the Base Telecommunications System (BTS). Services include Avaya S8800 Telephone switching system, AirBus Enhanced 911, AS5300 Conference Bridge, Callegra Voice Mail, Interactive Voice Response (IVR), TeleBoss 850, Contract Telecommunications System (CTS Portal or CS Portal) and the Telecommunications Cable Assignment Information Retrieval System (CAIRS). All efforts shall be directed towards a Unified Convergence Network by identifying deficiencies and shortcomings of the current communication network when evaluated against an adopted IPv6 and VoIP standard. Suggested improvements of existing infrastructure shall apply to recurring support services as well. The BTS consists of the base switching system, the fiber optic and copper distribution systems on premise, Customer Premise wiring to include Voice, Data, Local Area Network (LAN) and Video in the base telephone inventory, all conference bridge equipment, and all associated equipment currently described in the Government Furnished Property (GFP) equipment list and any equipment added during performance of the contract. The service level requires the contractor to furnish commercial grade operation, administration and maintenance support services that recur on a monthly basis.

Basic Monthly Services (BMS) are standard support necessary to operate and maintain the base communications switching, LAN and distribution systems In Accordance With (IAW) the original equipment manufacturers’ recommended schedule and established commercial specifications, Department of Defense (DoD), Air Force standards and best practices.

The contractor shall perform operations and maintenance of the BTS 24 hours per day, 7 days per week. Contractor shall perform administration and O&M on the switching system(s), transmission equipment, ancillary equipment, customer premise equipment (CPE), inside and outside cable plant and perform recurring support services. When equipment interfaces with the Defense Switched Network (DSN), the contractor shall ensure the equipment is Joint Interoperability Test Command (JITC) certified and Information Assurance (IA) accredited. The contractor shall ensure any accreditation packages or interoperability procedures are fully compliant prior to recommending solutions that interfaces with the DSN network. The contractor shall ensure compliance with Certification and Accreditation (C&A) process for equipment installed or planned to be installed by evaluating current infrastructure which must transition to a data based voice/messaging system utilizing the Avaya 8800 series equipment supporting framework currently in production. Equipment installed or interfacing with LAN or voice networks requiring use of Internet Protocol shall be Internet Protocol (IP) version 6 compliant unless otherwise approved by AFMC/A6 and/or Air Force Sustainment Center (AFSC) personnel.

1.1 The contractor shall support base mission changes, major or minor BTS infrastructure modifications, and other support requirements necessary to meet mission requirements. Support requirements may originate from technology changes, hardware and software systems upgrade, reconfigurations, new or additional equipment, dial central office reconfigurations to include routing and diversity requirements, and any other environmental changes that impacts or alters the BTS requirements. The contractor shall advise technical personnel of upcoming trends for voice, data, LAN and video solutions and make recommendations for migration to these solutions. The push for convergence of voice, data, LAN and video shall be considered when recommending new solutions. Migration to Voice over IP (VoIP) is an ongoing process of converting Time Division Multiplexing base telephone numbers to a VoIP platform in direct support of the Air Force Unified Communications initiative. The contractor shall install telecommunications and LAN wiring throughout Robins AFB and in Dormitories, Military Family Housing, Visiting Airmen’s and Officer’s Quarters, Temporary Lodging Facilities, other communications systems and devices.

1.1.1 The contractor shall maintain the capability to create, update or post changes to drawings, plant records or documents using government or commercial software.

1.1.2 The contractor shall establish on an annual basis a partnership for software and engineering support, excluding the cost of hardware to support Tiers II and III actions for the following equipment:

a. Avaya equipment

b. Siemens HiPath 4000 Command Post switches

c. Air Bus E911 solution

d. Callware Callegra Voice Mail

e. SPOK, Inc. Interactive Voice Response (IVR)

f. Compunetix, Inc. Alert System

g. Integrated Collaborative Enterprise (ICE) Solutions, LLC

1.1.2.1 Phase-In Period. RESERVED

1.1.2.2 Successor Contractor. RESERVED

1.1.2.3 Phase-Out Period. RESERVED

1.1.2.4 Incumbent Contractor. The incumbent contractor shall ensure a seamless transition in the change of work effort. The incumbent contractor shall cooperate to the extent required to permit an orderly change over to a successor contractor. The Government reserves the right to conduct site visits in all contractor-operated facilities. The contractor shall cooperate to the extent required to permit an orderly change over to the successor contractor. With regard to the successor contractor’s access to existing employees, a recruitment notice may be placed in each facility. The incumbent contractor shall be fully responsible for operation and maintenance of the BTS until expiration of the incumbent’s contract.

1.1.3 Base Telecommunications System (BTS) Management. The BTS on-site management supervises all aspects of the BTS. This includes VoIP and Convergence efforts, telephone systems maintenance services, Base Distribution System, customer premise equipment, LAN, Video Teleconferencing (VTC), and is considered the technical expert for architecture and large scale development, deployment and implementation for LAN, VoIP and Convergence technologies, voice switching matters in an integrated environment of multi-vendor to include AVAYA, CISCO, SPOK, CALLWARE, COMPUNETIX and SIEMENS equipment.

1.1.4 Switching System Service. The contractor shall possess certification credentials in order to provide Tier 1 level support on the telephone systems to include DoD 8570.1. A minimum of five years’ experience is required to perform installation, translations, administration, operation and maintenance on the type(s)/model(s) of switching system(s) and interface equipment. This includes the ability to perform translations to support call routing, traffic measurement reports, line feature additions or changes, and establishing new lines and trunks. Responsibilities extend to fielding customer calls for password resets and offer guidance for switch system features for telephone sets and voicemail setup. Additional responsibilities include maintaining Siemens HiPath 4000 switches supporting Command Post and Robins E911 solutions comprised of an Air Bus Audio Code switch that interfaces with Air Bus equipment E911 VESTA solution. Work will also include support for setup, implementation and systems integration with multi-vendor switching systems to include AVAYA, CISCO, SPOK, CALLWARE, COMPUNETIX and SIEMENS equipment and network integration and setup with products such as Conference bridge operation, setup and maintenance and Voice Over Internet Protocol (VoIP) theory and implementation as well as Convergence technologies.

1.1.5 Premise Equipment Service. The contractor shall maintain premise equipment (transmission equipment, ancillary equipment, customer premise equipment), inside plant cable and outside plant equipment installation, and operation and maintenance of premise equipment.

Services shall comply with Category (CAT) VI installation certification practices.

1.1.6 Outside Plant (OSP) Cable Service. The contractor shall install and maintain copper and fiber optic cable (aerial when applicable to the site, direct buried and underground), protected terminals, cable grounding systems, manhole, hand hole and conduit systems, connectors and distribution frame on the vertical side of the frame, and in terminating, splicing (including fiber optic mechanical and fusion splicing), locating, marking, testing, tagging, and cross-connecting.

OSP Service shall be required to certify a convergence plan ensuring specification compliance of current and future infrastructure and to use the most recent version of Cyberspace Infrastructure Planning System (CIPS) Visualization Component (CVC) software to submit updates to base infrastructure drawings. Records will be recorded in CAIRS as well.

1.1.7 Site Survey Service. The contractor shall provide technical solutions and costing based on customer requirements for telephone adds, moves, changes and relocation efforts. It also includes technical solutions and costing for small and large scale E&I requirements for voice/data and video connectivity installation and implementation. The site survey procedures/cost estimates completion time frames when requested by the PM are from date of task order receipt:

Level of Service for Emergency - within three (3) hours of receipt Level of Service for Priority - within one (1) duty day of receipt Level of Service for Routine - within ten (10) duty days of receipt

Penalties for completed surveys deemed late will be assessed against the performance thresholds identified in paragraph 1.2.5.4.2 and Section 2.0 of the Services Summary.

1.1.8 CAIRS Records Service. The CAIRS service shall be responsible for maintaining all records and reports. The contractor shall maintain all records and the base phone book database entries in CAIRS used to update an E911 database for emergency calls in accordance with local CAIRS format standards. Some updates may require the contractor to manually enter the data fields upon completion of individual work orders or record changes. Any new, changed or deleted telephone numbers/circuits requires the contractor to ensure E911 data accuracy. The base telephone directory shall reflect all organizations office symbols changes affiliated with this installation. Personnel names associated with phone/circuit records are mandatory entries unless otherwise instructed by the CSO—Communications and Information Services Officer (CSO)/Contracting Officer Representative (COR).

1.2 Basic Monthly Services (BMS) Standard Monthly Maintenance, Operations, Administration and Mission Support The contractor shall provide services for software functions for data and switch translation efforts when required to complete work under Recurring Support Services. These software functions shall be accomplished in accordance with time frame thresholds for recurring support services.

1.2.1 Perform Systems Maintenance.

1.2.1.1 Contractor shall operate and maintain the switching system(s) equipment IAW the Original Equipment Manufacturer (OEM) manuals listed in section 5.3 or as may be released by the manufacturer. All equipment or services completed by the contractor shall automatically roll over and become part of the monthly maintenance services.

1.2.1.2 The contractor shall notify in writing or email to the CSO/COR the need for any scheduled service outages. The contractor shall follow established local procedures for scheduling and implementing scheduled outages and in all cases, notification shall include the reason for the interruption, duration, start and stop times, and the equipment, lines, and buildings affected. In the event of a major scheduled outage, the contractor shall provide at least 14 days’ advanced notice to allow for proper customer notification. All outages shall be scheduled to minimize inconvenience to users, based upon government user work schedules and every effort shall be taken to ensure outages are scheduled Sundays between 1700 and 2100. The user must release all affected equipment and circuits prior to any service disruption.

1.2.1.3 The contractor shall maintain inside and outside plant cable and equipment. The contractor shall accept all third party cable or equipment installations performed by another vendor which have been accepted and approved for maintenance under this contract. The BTS contractor shall not be held responsible for completing third party installations or bringing third party installations up to industry standard that are found to be improperly installed, except as negotiated by the contractor and the Contracting Officer (CO). The Communications Information Systems Officer (CSO) shall be notified of any installation found to be incomplete, not installed according to the work order, or not installed according to industry standards within 24 hours of identification. Changes to the cable infrastructure shall be provided to the cable engineer within 10 duty days of completion. The contractor shall maintain in-service availability on all systems infrastructure providing useable connectivity for all user network and end user systems and devices.

1.2.1.4 Preventive Maintenance Inspections (PMIs). Contractor shall perform PMIs as required on all switching and power systems IAW manufacturer recommended or established schedules and/or manuals. Electrical characteristics tests shall be conducted on the Base Distribution System (BDS) cables.

1.2.1.4.1 PMI on Spare Conductors. Contractor shall perform a scheduled PMI test of the spare conductors/fiber strands. PMIs shall test and document 10% of the spare conductors/fiber strands across each cable quarterly. Each cable, through its total count of selected conductors/fiber strands to be tested, shall be documented. The schedule shall prevent duplicate testing until all spares conductors/fiber strands have been tested. The contractor shall inform the CSO when cable saturation reaches 80%. CDRL A003, Cable Installation Test Reports

1.2.1.4.1.1 Cable Schedule. A schedule of the cables shall be coordinated with the CSO to determine when the cables shall be tested. The CSO shall be informed when the testing on each cable is completed where the test records shall be located. The PMI schedule test records shall include cable number and conductors (copper pair or fiber optic strands) tested. The record shall annotate the “new” bad conductors detected and the existing number of bad conductors. The records shall identify the extent and or cause of the bad conductor, copper or fiber, in an effort to determine feasibility to repair. Any bad copper or fiber conductor and or splice shall be repaired when feasible. The record shall be maintained in CAIRS. CDRL A001, Preventive Maintenance Schedule

1.2.1.4.2 PMI Manholes/Handholes Contractor shall inspect at least ten manholes/handholes per month. If, during the manhole PMI inspections discrepancies are found, the contractor shall correct the deficiency on the spot. The inspection documentation shall reflect the found discrepancy and the corrective action taken. This manhole/handhole shall not be counted in the month’s PMI schedule. Each manhole/handhole shall be inspected for the following discrepancies and corrected ensuring all efforts do not impede any functions of a Unified Convergence:

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

• All cables shall be racked to the manhole/handholes cable supports.

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

• All sump pumps will be inspected and checked for proper operation.

• All manholes/handholes shall be accurately identified with a 6” X 6” white paint background with the manhole/handhole number stenciled in black letters. No hand written numbering system will be acceptable. This system of identification shall be utilized as each manhole/handhole is inspected and/or during work efforts performed by the contractor.

1.2.1.4.3 PMI Building Terminals The contractor shall inspect at least ten terminals per month and verify circuits would support a convergence crossover. Each terminal will be inspected for the following discrepancies and corrected:

• Verify the correct terminal 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 circuits/numbers in the facility and remove any unused services.

• Remove all unused cross-connects in the terminal.

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

• Update CAIRS or appropriate cable distribution system solution employed to allow proper cable inventory.

1.2.1.4.4 Preventative Maintenance Plan. Contractor shall develop a master Preventive Maintenance plan for the scheduling and performance of PMIs. The contractor shall coordinate additions, deletions, and changes to the plan with the CSO. All preventive maintenance inspection records shall be documented IAW standard industry practices. Electronic copies of PMI records shall be maintained and accessible to the Contracting Officer’s Representative (COR). In all cases, PMI records shall reflect acknowledgement of completion by the user. If malfunctions or problems are noted as a result of the PMI, the contractor shall take corrective action to fix malfunction. CDRL A001, Preventive Maintenance Schedule

1.2.1.4.5 PMI Battery Test. Contractor shall perform a scheduled PMI battery test of the Uninterrupted Power Supply (UPS) system according to OEM documentation. PMIs shall test and document the power systems. Copies of the test results shall be kept in electronic form and provided to the COR.

1.2.1.4.6 Special PMI Considerations: The contractor shall perform monthly PMI for communications systems infrastructure supporting Very Important Person (VIP) aircraft, support systems, and exercise facilities.

1.2.2 Trouble Ticket Outages. The contractor management personnel (BTS on-site management) shall be available for meetings to discuss ticket issues during normal duty hours.

For outside normal duty hours, the contractor shall respond no later than 60 minutes after being notified. The contractor shall be available via cell phone when circumstances do not permit an on-site manager to be physically available. When the BTS on-site management is not available, the contractor shall inform the CSO or COR and identify contractor personnel responsible during the absence. The BTS on-site manager’s representative shall have the same authority as the BTS on-site manager. The contractor shall provide a key personnel listing and contact information to the CSO and COR and maintain information on a monthly basis during the term of the contract.

The contractor shall submit an on call duty roster to the CSO used to contact contractor personnel for emergencies, outages, alerts and exercises after normal duty hours. If called, the contractor shall report for duty and provide support as necessary until the outage, emergency, alert or exercise is completed.

1.2.2.1 The contractor shall respond to all reports of service outage after notification by a user, service work order desk, vendor detection, notification via trouble ticket tool or otherwise learning of a system outage condition. Contractor shall be required to use the trouble ticket tool that will be provided and installed on Government furnished computer. Key personnel shall be required to use this tool to create trouble tickets, be notified of troubles and respond to them.

The contractor shall respond to customers report troubles for resetting of voicemail passwords and shall use the automated trouble ticket tool to receive these troubles via their computer terminal. The contractor shall create trouble tickets if one has not already been created by help desk personnel for telephone troubles received. The contractor shall ensure all employees’ requiring accounts to access the base network comply with all requirements necessary to obtain User Identifications and Passwords for these accounts. The contractor shall obtain user accounts, CAC and passwords for all personnel requiring correspondence with personnel via the base’s email system.

1.2.2.2 The contractor shall respond within 1 hour for critical and high outages and within 3 hours for medium and low outages from time of phone calls or E-mail message notifications and restore all system and service outages according to category thresholds listed below. If multiple facilities, areas, primary trunks or cables are impacted, the CSO will assign the category of the outage and establish the repair priority. The contractor shall restore services in the priority order determined by the definitions of outage category in section 5.3 and the Restoration Priority List (RPL). (See section 5.1 for workload estimates.) For critical and high outages, the contractor shall verbally notify CSO upon detection/notification of outage and restoration of service providing the time service was restored and a description of repair action. The CSO may grant exceptions to the established restoration time limits. If granted, the work shall be completed within the time specified by the CSO. The contractor shall submit a trouble ticket for all outages if one does not already exist, whether scheduled or not and shall include the reason for the interruption, authorizations, action taken, equipment or lines affected, and dates/times of coordination and restoration.

OUTAGE RESTORE TIME

Critical Within two hours High Within six hours Medium Within eight hours Low Within one duty day

1.2.2.3 The contractor shall provide remote monitoring of the switching system(s) without requiring assistance from base personnel. Notification of switch outages shall not be through a continuous direct line to the switching system for security reasons. If a remote diagnostics modem is used, it must be user name and password protected and must comply with security guidelines. Any modem used must have call back verification capabilities. The contractor is responsible for all materials and equipment necessary to implement remote monitoring and shall take all actions to implement the plan and comply with telephone switching security standards of any currently and future AFMC and or Robins directives.

The CSO shall be informed of all critical and high outages immediately during normal duty hours. If these outages occur during other than normal duty hours, the help desk shall be notified immediately, and the CSO shall be informed the following duty day.

Whenever remote monitoring is to be employed the contractor shall include a maintenance service plan and shall provide:

a. Remote monitoring of the telephone switching system(s)

b. Remote diagnostic performance

c. Remote alerting to local maintenance personnel

d. Emergency technical assistance support

e. Identification of the telephone switch related circuit cards

f. Translations development and change support

1.2.2.4 The contractor shall determine if a recorded problem or system failure is attributable to the switching system, BTS, or other causes. If the malfunction is due to other causes (outside the contractor-maintained system/equipment), the contractor shall immediately notify the CSO.

1.2.2.5 Cable repairs that are not a result of the O&M contractor’s negligence shall be handled as Recurring Support Service and will be issued as Emergency Orders unless otherwise stipulated by the CSO.

1.2.3 Perform System Operation Contractor shall perform all systems operating functions to include the following tasks:

1.2.3.1 Contractor shall operate system(s) IAW manufacturer manuals.

1.2.3.2 Contractor shall operate and maintain inside and outside plant equipment IAW with applicable documents.

1.2.3.3 Contractor shall start and configure the system(s), respond to console messages, execute available diagnostic routines, and continuously monitor system status.

1.2.3.4 Contractor shall power down and start up the system(s) and perform system backups and recovery process from machine stop or malfunction.

1.2.3.5 Contractor shall perform disk, cartridge, flash memory, or tape backup of the system(s) memory within 24 hours of data base changes. When no data base changes have occurred over a 7-day period, the contractor shall be required to perform system backup. All back-up media will be stored in fire retardant enclosures and in a central location as determined by the Government.

The contractor shall participate in disaster recovery efforts to recover or help to prevent failure of systems, to include the creation of disaster recovery documentation.

1.2.3.5.1 Voice Mail. The contractor shall support voice mail operations. Support shall include management and administration, additions, deletions and modifications to user’s mailbox to include password resets, distribution lists, holiday schedule tables, daylight savings time, and any other voice mail feature or function inherent to the system. Application support includes diagnostic, maintenance and minor programming change on current software applications.

System logs review shall be performed to ensure file size does not prevent service disruption.

1.2.3.6 Call Detail Records (CDR). The contractor shall support operations of the Call Detail Records on CAIRS. The contractor shall coordinate with CAIRS technical personnel to ensure telephone switches properly interface with the CAIRS CDR solution and that the system is accurate and functions properly for billing of telephone calls. This shall ensure Unit Communications Systems Officer (UCSO) receive their telephone invoices via CAIRS.

1.2.4 Perform System and Data Administration

1.2.4.1 The contractor shall perform System/Data Administration on all equipment and software associated with the BTS as Monthly Maintenance. This includes software capabilities, circuit, phone, data and phone translation, activation/assignment of ports, circuit packs, line assignments, class of service, class of restrictions, phone number assignments, translation for call routing, dial plan changes, and software related functions required to complete work performed under recurring support services.

1.2.4.2 Contractor shall perform software related functions and translations for all trunk or circuit configurations required by on base systems or users. The contractor shall perform software related functions for all add, move, change, delete, activation of and query of a circuit or system data, directory assistance information, service order, trouble assistance, records administration, and CAIRS billing.

1.2.4.3 Contractor shall perform telephone switch traffic measurement and analysis: within system capabilities and limitations, perform analysis and studies on the base switching system.

CDRL A002, Traffic Measurements & Analysis

1.2.4.4 Perform traffic measurements and analysis studies for the switching system(s). The information shall be provided on a Quarterly basis and shall cover consecutive two week period, and include 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. Group Number,

2. Group Size,

3. Group Type,

4. Group Direction,

5. Measure Hour,

6. Total Usage,

7. Total Seize,

8. Incoming Seize,

9. Group Overflow,

10. Queue Size,

11. Call Queued,

12. Queue Overflow

13. Queue Abandoned

14. Out Of Service

15. Percentage All Trunks Busy

16. Percentage Out Block Make recommendations based on the information provided in the analysis.

1.2.5 Perform Support Services:

1.2.5.1 Contractor Support for Government Engineering and Installation. The contractor shall provide technical support efforts to include an interchange of information about technical parameters and capabilities of the BTS, locate and identify building terminals, communication rooms, and verify cable record information. This effort includes setting of equipment options to determine proper operational conditions, restoration of service to existing equipment, establishment of service to new facilities, or transfer from one system to another. This includes support on hardware and software upgrade actions that occur during performance of this contract. Contractor shall coordinate with the COR during any BTS reconfigurations, relocations, expansions, and upgrades provided by CSO or other Government contracts. The contractor shall maintain and update records on all equipment and cable to include cable pair assignment.

1.2.5.2 Contractor Interface and Support for other Vendors. The contractor shall share and exchange technical and system equipment interface information with other vendors and the local exchange and long distance carriers in areas of voice service operations, equipment and software operation, cutover of services to new facilities and or equipment, and restoration of long haul and other Government-leased circuits. If relocation of existing equipment and or cable is required to satisfy cutover of services, work shall be performed as BMS. If additional equipment or cable is required for cutover, the equipment and or cable purchase shall be procured through a cost reimbursable line item; labor shall be included as BMS.

1.2.5.3 The contractor shall review program and drawings and provide comments concerning communications requirements within 10 duty days from receipt. The contractor shall attend designated design review meetings. The BTS on-site management shall attend local vicinity meetings as required.

1.2.5.4 The contractor shall perform site surveys and provide Technical Solution and Costing (TS&C) to the COR in an effort to allow for the creation and issuance of a DD Form 1367, Commercial Communications Work Order (CCWO) or other requirements document approved by the Government for routine, priority and emergency work orders based on pre-negotiated line items. The contractor shall receive customer requirements and coordinate with them to ensure requirements are clearly defined and work can be performed on a timely manner prior to performance of survey. The contractor shall review the requirement and provide a draft Technical Solution and Costing (TS&C) for implementation for routine, priority and emergency requirements to the COR. The contractor shall also perform site surveys and provide Rough Order of Magnitude (ROM) estimates or actual costs for E&I Requirement work orders. The submitted TS&C will use the pre-negotiated Sub-Contract Line Item Numbers on Exhibit B. The COR will validate all technical solutions and determine cost effectiveness. If a more cost effective solution exists, the contractor and the COR will make appropriate changes to the estimate. If a consensus cannot be reached as to a proper technical solution and costing, the contractor and the government COR shall bring the matter to the CSO for resolution. The COR or Project Manager and the contractor will negotiate a timeframe for the contractor to provide technical solutions and costing for surveys on E&I Requirements. The contractor has three duty days to notify the COR if a requirement, not already identified as such, is deemed as an E&I Requirement. Otherwise the contractor shall provide the technical solution for routine work orders within 10 duty days, within 1 duty day for priority work orders and within 3 hours for emergency work orders from receipt of customer requirement document. Upon acceptance of the draft technical solution by the CSO or COR, a work order will be issued if funding is acquired and available. The contractor shall satisfy the requirement without a DD Form 1367 if a telephone is relocated where an active jack is and no hardware is to be issued. This work falls under firm fixed price duties as software. The contractor shall annotate this work on the requirement document and make appropriate database entries to identify new location of customer phone number. This situation shall apply to any software related requirement, where the capability already exists on our voice systems and no hardware is necessary to satisfy customer requirement.

No profit shall be paid under this CR CLINs, use of DCAA approved burden rates is authorized.

ODCs must be purchased IAW the contractor’s approved purchasing system, as applicable.

All products proposed to provide solutions for E&I Requirements not listed on exhibit B shall be purchased from the NETCENTS-2 Netcentric Products Contract. In accordance with para 4.1 of the basic NETCENTS-2 contract PWS, at least two quotes shall be provided as proof of price reasonableness. CDRL A012, Funds and Manhour Expenditure Report

1.2.5.4.1 Engineering and Installation (E&I) Requirements. E&I Requirements are Firm Fixed Price (FFP) negotiated requirements. The CO will request a proposal from the Contractor for E&I requirements. The Government may negotiate a special project into the contract when an effort is needed that is not covered by current line items on the contract. These are one-time efforts that are within the scope of the contract. Proposals shall be submitted on DD Form 1367, Commercial Communications Work Order or equivalent format and include as a minimum, the information below.

1.2.5.4.1.1 Contractor shall submit detailed and itemized proposals for work intended to be performed under special projects as requested by the CO at no additional price. Contractor shall provide its proposal to the CO/COR within three work days. The Contractor’s proposal shall provide adequate detail of efforts/items required to complete the job, including but not limited to item description, quantity, unit of issue and extended prices.

1.2.5.4.1.2 Contractor’s proposal shall include all direct and indirect expenses and profit within the price of the items specified. Contractor’s proposal shall be priced for inspection/acceptance at final destination.

1.2.5.4.1.3 Contractor’s proposal shall identify existing CLINs/PIDs, proposed for use on the E&I.

1.2.5.4.2 Penalty for Late Surveys. Penalties will be assessed for surveys completed past the performance thresholds identified in Section 2.0 of the Services Summary. The government will utilize Information Technology Service Management (ITSM) to retrieve a listing of surveys completed for the month and will utilize reporting tools to measure performance standards. The ITSM report will be used to identify performance outside stated expectations. The government will assess a penalty of $10 per duty day for each day that Priority or Critical surveys are submitted late, and $5 per duty day for each day that Routine and regular scope surveys are submitted late. The reduction will be taken from the appropriate CLIN for the firm-fixed monthly price of Survey Services.

1.2.5.5 Instruction. The contractor shall provide telephone instrument and voice mail procedure instructions for base customers. Before Voicemail passwords are reset, the contractor shall inquire as to the reason for the voicemail reset. If the reason is due to a recent move of the customer, the contractor shall inform the customer to contact their UCSO in an effort to submit a requirement document to allow communications personnel to relocate the customer’s assigned phone number which will also relocate their voicemail box. The contractor shall inform the customer to contact the COR to resolve any issues.

1.2.5.6 Cable/Fiber Location Staking and Marking. The contractor shall provide location, staking, and marking cable services on encased or direct buried conduits/cable within one (1) foot of the actual location at 10-foot intervals and at direction changes. The marking shall begin two feet from the point of entry into the work area and shall continue two feet past the point of exit from the work area. When requested by the CSO, the contractor shall provide for marking and staking of the base cable plant to reduce the likelihood of damage to the cable during ongoing or planned excavation in a designated area. The contractor shall provide services for all cables located on the base premise. As part of the standard BMS maintenance fee, the contractor shall mark up to 2100 - 2300 jobs per contract year, to include approximately 1,200,000 feet of cable. The contractor shall provide this service for any additional new cable installed on the base premise. For routine requirements, the CSO will provide notification to the contractor 48 hours before the location and marking service is required. Under an emergency condition as determined by the CSO, the contractor will be notified immediately. An emergency condition is one that impacts the organization’s ability to fulfill its mission. The period for completion of this effort shall be negotiated between the CSO and the contractor. Nominal times for completion are:

Emergency: Two hour completion from time of notification.

Routine Marking: Within 48 hours.

1.2.5.7 Switching System Post-Cutover Support. The contractor shall support BTS cutover requirements. The contractor shall provide the support necessary to correct the inside plant, outside plant, and premise equipment cutover errors and anomalies expected with a complete switching system and/or outside cable plant replacement. The CSO will provide prioritization of corrections as needed. The period shall also include the first weekend after switch cutover.

Efforts shall include trouble shooting, repairing, and isolating failures.

1.2.6 Work Center Records.

1.2.6.1 Contractor shall create, establish and maintain BTS system records in CAIRS or other authorized solution. Where the capability does not exist to enter data in the correct format, the contractor may use a contractor provided database. All BTS records and documents created and maintained by the contractor remain the property of the Government. The contractor shall update work center records within three duty days after completion of task or work order. All records shall be retained and be available locally (on-base) for review or use by the CSO, CO, COR, and other authorized personnel. The contractor shall have no more than 3 errors in accuracy of each set of work center records per month and update all errors found or identified during review of the work center records. When deficiencies of these records are identified to the contractor by the COR, the contractor shall resolve these deficiencies within 24 hours of finding. The contractor shall work with the Government OSP personnel on records depicting cable deficiencies.

The contractor shall create and maintain work center records (outside of AF systems) as listed below:

a. PMI Schedules

b. Cable Installation Test Results

c. Communications and Information Systems Installation Records (CSIRs)

d. Quality Control Records

e. Inside & Outside Plant Equipment Records

f. Cable Pair Assignment Records

g. Air Force Logistics Support Spares Records

h. Description of Items usage under Exhibit B

i. Equipment Inventory Records

j. System Security Audit Report

k. System Capacity Records

l. Contractor-Furnished Hazardous Material Safety Data Sheet (MSDS)

m. Traffic Measurement Records

n. Cable Repair Records

1.2.6.2 The contractor shall receive ticket from the help desk (or create a ticket if one does not exist for data, telephone, voicemail, or other data/voice systems related troubles) and shall verify entries include as a minimum:

a. Person reporting a discrepancy.

b. The time a discrepancy was reported (start time).

c. A short description of the discrepancy (reason for scheduled/unscheduled outages).

d. Identification of the customer/user by station or data line affected (telephone number or circuit number).

e. Priority (critical, high, medium or low) outage(s).

The contractor shall ensure that the following fields are completed on these tickets when information is not filled in by help desk personnel or when the contractor creates the trouble ticket.

f. Location of equipment (building and room number, etc).

g. The time a service(s) was dispatched.

h. The time discrepancy was corrected (stop time). Annotate the log with the person or office contacted to provide status information.

i. Corrective action(s) taken.

1.2.6.3 Cable Installation Test Results. Quarterly, the contractor shall perform cable installation tests and provide results. All discrepancies found shall be reported within 10 duty days to the 78 ABW/SC cable Point of Contact (POC). CDRL A003, Cable Installation Test Reports

1.2.6.4 Communications and Information Systems Installation Record (CSIR).

1.2.6.4.1 Create, Update, and Maintain CSIR.

The contractor shall update the Communications and Information’s Systems Installations Records (CSIR) no later than 10 duty days after completion of work required to be identified in the base CSIR drawings. Two copies of the updated cable diagrams and manhole drawings shall be given to the Cable Plant Manager. The contractor shall create, update, and post changes to drawings, plant records or documents using 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 AFI 21-404. Contractor shall transfer to the CVC database all pertinent outside plant information from administrative and maintenance CSIR, Legacy CSIRs, work orders, inspection reports, as-built and as-installed marked-up drawings, and Global Positioning System (GPS) services that are created as a result of the contractor’s operations.

CDRL A006, Communications & Information Systems Installation Records

1.2.6.4.2 Cyberspace Information Planning System (CIPS) Visualization Component (CVC) The contractor shall load, edit, update and maintain CSIR information, for outside plant, in the CVC database IAW AFI 21-404. Contractor shall transfer to the CVC database all pertinent outside plant CFD information from administrative and maintenance CSIR, Legacy CSIRs, work orders, inspection reports, as-built and as-installed marked-up drawings, and GPS services that are created as a result of the contractor’s operations under an issued order.

1.2.6.4.3 Create and Promote Workspace.

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 update the CVC with as-built information and will import shape files created in a new O&M Workspace with the CVC Editor tool. When the update is completed, the contractor will promote the Workspace for CSIR Manager approval. After each promoted O&M Workspace has been approved and merged to the CVC database by the CSIR Manager, the contractor shall create and promote a new O&M Workspace for each proposed subsequent CVC update. The CSIR Manager will approve and merge or reject each promoted O&M Workspace. The contractor shall coordinate with the Base CSIR Manager, and develop and maintain IAW AFI 21-404 and instructions published.

1.2.6.4.4 Global Positioning System (GPS) Service Data.

Contractor shall collect, update and maintain the Communication Feature Location Data (CFLD) and use the data to update the location and attributes of communication features in the CVC database. Updates shall be accomplished within two days of completion of the requirement, and if electronic documentation is implemented, access shall be granted to vendor databases, storage media, or files.

1.2.6.4.5 Global Positioning System Service Documents 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, ductbanks, manholes, handholes, building entries, terminals, distribution pedestal terminals, and splices. Contractor shall ensure data compatibility with the CIPS Visualization Component (CVC) database and shall upload the data into the CVC database.

1.2.6.4.6 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 Location Data (CFLD) following the Federal Geographic Data Committee.

1.2.6.4.7 Each communication feature requiring geospatial coordinates shall be located to within one (1) foot of its true ground position, in the horizontal plane, with a 95% spatial accuracy confidence level as defined in Federal Geographic Data Committee.

1.2.6.4.8 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, pullboxes, 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 10 feet and each turn or bend in a cable installation pathway must also be recorded so that the coordinates for any point along the turn pathway will fall within the allowable accuracy.

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

1.2.6.4.10 The GPS collected CFLD 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 current CVC software used. Its format shall be within a folder named the same as the prefix of the shape file. For Example, if the shape file is named "points_lafb_28.shp" the folder would be named "points_lafb_28”. The folder shall contain all the files that make up the general shape file, i.e., “.shp”, “.shx”, “.dbf”, etc. along with the specified metadata file. The shape files shall have a geospatial reference (.prj) file included that specifies the parameters of the coordinate system.

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

1.2.6.4.12 The contractor shall collect CFLD in GPS data loggers and will use Table A to create the CFLD data dictionary for use in the logger.

1.2.6.4.13 For each set of CFLD collected using GPS, the contractor shall complete all metadata elements marked mandatory and mandatory-if-applicable as defined by the FGDC–STD-001- 1998 specified in PWS section 5.3. Metadata shall be formatted and stored as an XML document that is compatible with the submitted shape files specified in Paragraph 1.2.6.4.10.

1.2.6.4.14 Calculation worksheets showing compliance with National Standard for Special Data Accuracy (NSSDA) statement at the 95% confidence level as required by Paragraph 1.2.6.4.7 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/ or go the CVC website:

https://cipsaf.tinker.af.mil/cips/mycips.aspx; At CIPS Related Sites, click on the CIPS Community of Practice (CoP), under the heading, CIPS Documents click on CSIR Manager CVC Reference Materials.

1.2.6.4.15 Geospatial data shall overlay on the installation’s most current GeoBase Common Installation Picture (CIPS). The collected data will incorporate the coordinate and projection system of the CIP: WGS 1984 UTM Zone 14N Meters.

1.2.6.4.16 Quality Control. The contractor shall utilize a topology build and clean routine and assure the CFLD has the following:

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

b. Features shall be snapped where applicable, for example, GPS Dbsplice snapped to GPS Path Segment.

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

http://www.fgdc.gov/

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.6.4.17 Submittal of Deliverables CFLD shape files, metadata XML files, the quality control report and calculation worksheets validating the NSSDA accuracy statement shall be submitted on CD-ROM storage media to the COR.

1.2.6.4.18 Uploading CFLD into CVC. The contractor shall upload the collected CFLD shape files, 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.2.6.4.19 Global Positioning System (GPS) Service. (See section 1.2.6.4.4) GPS Service for third-party installed work shall be issued under the CLIN for labor. The contractor shall provide a GPS Service to collect geospatial data on the repairs, modifications or additions to the outside plant cable installation pathway when the work has been performed by other contractors or AF personnel and GPS Service is requested by the PM/COR. This data, known as CFLD, consist of geospatial location and attribute information on physical features in the cable installation pathway. Features include, but are not limited to, communications cables (buried, underground, open trench, and above ground) and associated structures and equipment such as manholes, handholes, ductbanks, conduits, splice points, and pedestals.

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it.