SectionCDec1807.doc

DOC document 669 KB Posted

Attached to
Regional Telecommunications Acquisition Services (RTAS) Federal contract opportunity
Solicitation number
RTAS-RFP-08002
Issued by
GSA Federal Acquisition Service

About this file

Solicitation-Section C

View the file

Other files for this federal contract opportunity

Other files attached to Regional Telecommunications Acquisition Services (RTAS), newest first.
File Type Posted
amend0009-RTAS-05-08-08.pdf PDF
Pricing Table- OH Apr 17 08.xls XLS spreadsheet
R5 Svcs By St Mar 03 08.xls XLS spreadsheet
RTAS SDP Requirements Feb 08.xls XLS spreadsheet
Section_F.doc DOC document
Section_L Apr 15 08 gd.doc DOC document
Pricing Table- WI Apr 17 08.xls XLS spreadsheet
Section B Apr 15 08 gd.doc DOC document
Section_E.doc DOC document
Section C Apr 15 08 gd.doc DOC document
Section_J Apr 15 08 gd.doc DOC document
Pricing Table- MI Apr 17 08.xls XLS spreadsheet
Pricing Table- IN Apr 17 08.xls XLS spreadsheet
Section_H Apr 9 08 gd.doc DOC document
Section_G Apr 15 08 gd.doc DOC document
npa nxx rev1.xls XLS spreadsheet
Round2 Q A 4-3-08.doc DOC document
ATTACHMENT J-3.doc DOC document
Historic Bldgs ATTACH J-2.doc DOC document
amend0007-RTAS-RFP-08002.pdf PDF
alltechnicalresponses3_10_08.rtf RTF text file
1_Section_F.doc DOC document
1_PricingTable-IL.xls XLS spreadsheet
SectionBMar1008.doc DOC document
1_Section_J.doc DOC document
1_PricingTable-OH.xls XLS spreadsheet
1_Section_G.doc DOC document
1_Section_H.doc DOC document
npanxxrev1.xls XLS spreadsheet
1_PricingTable-IN.xls XLS spreadsheet
1_Section_M.doc DOC document
1_PricingTable-MN.xls XLS spreadsheet
RTASSDPRequirementsFeb08.xls XLS spreadsheet
Amend0001RTAS02-04-08.pdf PDF
PricingTable-MI.xls XLS spreadsheet
SectionBDec1807.doc DOC document
SCA-IL.pdf PDF
Section_F.doc DOC document
PricingTable-WI.xls XLS spreadsheet
SCA-MI.pdf PDF
Section_D.doc DOC document
PricingTable-OH.xls XLS spreadsheet
PricingTable-MN.xls XLS spreadsheet
SCA-IN.pdf PDF
SCA-WI.pdf PDF
Section_I.doc DOC document
Section_K.doc DOC document
Section_J.doc DOC document
SCA-OH.pdf PDF
SF33-Final1-28-08.pdf PDF
Show all 50

Regional Telecommunications Acquisition Services (RTAS) has more files on GovTribe.

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

RTAS RFP 08002

Table of Contents

Section C: Descriptions/Specifications/Work Statement

Section

Page

C.1 Background

C.1.1 The Federal Acquisition Service (FAS)

C.1.2 RTAS Contract Objectives

C.1.3 RTAS Contract Scope

C.1.3.1 Authorized Users

C.1.3.2 Geographic Scope

C.1.3.3 RTAS Services

C.1.4 Organization of the Statement of Work

C.2 Telecommunications Services and Features

C.2.1 General Service Requirements

C.2.1.1 Service Delivery Points (SDP)

C.2.1.2 Inside Wiring

C.2.1.3 Site Preparation

C.2.1.4 Final Disposition of Government Owned Cable Plant and Equipment Manuals/Records

C.2.1.5 Local Loops

C.2.1.6 Offeror Compatibility

C.2.1.7 Interoperability

C.2.1.8 Numbering Plan and Dialing Plan

C.2.1.9 Performance

C.2.1.10 System Attributes

C.2.2 Voice Services

C.2.2.1 Capabilities and Features

C.2.2.2 Performance

C.2.2.3 Reserved

C.2.2.4 Interfaces

C.2.2.5 Additional Service Requirements

C.2.3 Circuit Switched Data Services

C.2.3.1 Basic Service Capabilities

C.2.3.2 Features

C.2.3.3 Performance

C.2.3.4 Interfaces

C.2.4 Dedicated Transmission Service (DTS)

C.2.4.1 Basic Service Capabilities

C.2.4.2 Features

C.2.4.3 Performance

C.2.4.4 Interfaces

C.2.5 Internet Access Service (IAS)

C.2.5.1 Basic Service Capabilities

C.2.5.3 Performance

C.2.6 Broadcast Access Services (BAS)

C.2.7 SONET Ring Service (SRS)

C.3 Management and Operations

C.3.1 Sales and Marketing Support

C.3.2 Service Ordering Support

C.3.2.1 Service Order Process

C.3.2.3 Ordering Period

C.3.2.4 Provide Price Quotes

C.3.2.5 Initiate Service Orders

C.3.2.6 Service Order Media

C.3.2.7 Service Order Format

C.3.2.8 Service Availability Intervals

C.3.2.9 Track Service Orders

C.3.2.10 Change Service Orders

C.3.2.11 Service Order Completion and Acceptance

C.3.2.12 Disconnect Service Orders

C.3.3 Operational Support Systems

C.3.3.1 Commercial Systems

C.3.3.2 Reserved

C.3.3.3 Moves/Adds/Changes and Service Visits

C.3.3.4 Professional Support

C.3.3.5 Operation, Administration and Maintenance

C.3.4 Billing/Invoicing Support

C.3.4.1 Submission Requirements

C.3.4.3 Invoice Requirements

C.3.5 Trouble Handling

C.3.5.1 Definition/Procedures

C.3.5.2 Support System Access

C.3.5.3 Process

C.3.5.4 Trouble Reporting

C.3.5.5 Escalation Procedures

C.3.5.6 Routine Restoration

C.3.5.7 Emergency Restoration

C.3.6 Customer (End User) Training

C.4 Service Enabling Devices/General Requirements

C.4.1 General Requirements

C.4.1.2 Network Compatibility

C.4.2 Reserved

C.4.3 SPD Delivery Via House Cable/Wiring

C.4.3.1 Demarcation Point

C.4.3.2 Main/Intermediate Distribution Frame(s) (MDF/IDF)

C.5 Transition to RTAS

C.5.1 Coordinated Transfer

C.5.2 Fair Consideration

C.5.3 Transition Objectives and Responsibilities

C.5.4 Transition Planning and Implementation

C.6 Restoration of Facilities and Services

C.6.1 Offeror COOP

C.6.2 Reserved

C.6.3 Emergency Restoration of RTAS Facilities and Services

C.6.4 Priority Restoration

C.6.5 Status Reports

C.6.6 Contingency Document Deliverable

C.6.7 Network Facility Augmentation and Restoration

C.6.7.1 Augmentation

C.6.7.2 Transmission Facilities

C.6.7.3 Switching and Signaling Systems

C.6.8 Protection of Classification and Sensitive Information

C.7 General Management

C.7.1 Prime Contractor Responsibilities

C.7.2 Tier Relationship

C.7.3 Organization Structure

C.7.4 System Changes

C.7.5 Reserved

C.7.6 Network Monitoring

C.7.6.1 Offeror Provided Services and Facilities

C.7.7 Quality Control Plan

C.8 Transition from RTAS to the Follow-On Network

C.9 Transition Oversight

List of Tables

3Table C.1-1. RTAS Services and Products

12Table C.2-2. Definition of VS Basic Capabilities and Features

19Table C.2-3. Required VS Basic Capabilities and Features

25Table C.2-5. CSDS Features

26Table C.2-6. CSDS Key Performance Indicators

27Table C.2-7. CSDS User Network Interface Types

Table C.2-8. Required Basic Service Capabilities

Table C.3-1. Required Service Intervals

Table C.3-2. Representative RTAS Labor Categories

List of Figures

36Figure C.3-1. Centralized and Direct Ordering

Figure C.3-2. Centralized and Direct Invoice/Billing Figure C.3-3. Service Delivery Points C.1 Background

C.1.1. The Federal Acquisition Service (FAS) Information Technology Services (ITS) Network Services Division (NSD) of the General Services Administration (GSA) provides local telecommunications services in six states under multiple Metropolitan Area Acquisitions (MAA) contracts and a Regional Local Services Contract (RLSC).

C.1.1.1. The current RLSC and MAA contracts offer a broad portfolio of commercial services and products at very competitive prices – including voice, data, video, internet access, customer premises equipment (CPE), and technical services. With the contracts set to expire in 2008 and 2009, FAS is replacing all contracts with a program known as Regional Telecommunications Acquisition Services (RTAS). RTAS will entail a single solicitation with multiple awards. The awards will be for a four year base period with four one year options. RTAS will provide Government users continuity of services for local telecommunications and will serve as a stable platform for the user community to migrate to Networx Universal and Enterprise contracts based on individual agency requirements, funding availability, and timelines.

C.1.1.2. RTAS service requirements are based, in large part, on what RTAS customers are buying and using today. There shall be no loss of service functionality or disruption of service as customers’ transition from the MAA’s and RLSC to RTAS. Our customers are technologically sophisticated and increasingly demand new and emerging technology solutions in addition to traditional telecommunication services.

C.1.2 RTAS Contract Objectives

C.1.2.1 The Government will accomplish the following objectives:

C.1.2.1.1. Ensure Service Continuity. Ensure customers have access to comprehensive products and services currently available and in-demand in the GSA FAS six state Region 5 area.

C.1.2.1.2. Foster Competition. Leverage service volume and structure acquisition to attract multiple Offerors for award, drive favorable pricing, and foster competition over the life of the program.

C.1.2.1.3. Provide integrated modern Support Systems. Incorporate state-of-the-art web-enabled commercial Business Support Systems (BSS) and Operational Support Systems (OSS) where commercially available.

C.1.2.1.4. Enable Convergence. Promote migration to a converged environment through access to emerging technologies with continuous refreshment.

C.1.2.1.5. Grow Social Economic (i.e. Small Business) Opportunities. Promote small business participation.

C.1.2.1.6. Obtain alternate solutions and sources, equal to or better than, what is currently used.

C.1.3 RTAS Contract Scope

C.1.3.1 Authorized Users

This contract is for the use of all Federal agencies. All organizations listed in GSA Order ADM 4800.2E, Eligibility to Use GSA Sources of Supply and Services, January 3, 2000 (as updated) are eligible. The Government has the right to add authorized users at any time during the term of this contract up to the limits specified in Section H.3, Minimum Dollar Guarantee and Maximum Contract Limitation.

C.1.3.2 Geographic Scope

C.1.3.2.1 The geographical boundaries are defined as within the boundaries of the six states within the GSA FAS Region 5, Illinois, Indiana, Michigan, Minnesota, Ohio and Wisconsin. The total geographical area shall include all NPA/NXX’s and Local Access and Transport Areas (LATAs) that are in the RTAS service area and are split into adjoining towns or counties are considered part of the RTAS. If an NPA/NXX was overlooked, split or overlaid, the definition of the RTAS area in this section shall prevail and the NPA/NXX will be part of this agreement.

C.1.3.2.2 Multiple contract awards are preferred and shall be based on the Offerors’ ability to satisfy the functional requirements of the current RLSC and MAA contracts where currently commercially available. A single contract award may be limited in geographical coverage. Service locations and service delivery requirements, as dictated by the dynamics of the Government, may be adjusted over the period of the contract. Offerors shall provide voice and data telecommunication services with the capacity and capability for the Federal Government’s stated requirements. Offerors shall design, plan, implement, provide and maintain the services described in this solicitation. Any services discontinued during the course of this contract shall be replaced with a similar service at the contracted price or grandfathered for the life of this contract. The Offeror shall discuss these items with both the COTR and CO before any action on their part is taken.

C.1.3.2.3 In this solicitation, Offerors are not expected to provide services to the Federal Government where they do not provide service to commercial users. However, Offerors are required to serve locations within the RTAS boundaries states where they currently sell or resell local telecommunications services as mentioned in Section B. The Government plans to award multiple contracts for the RTAS. Only offers that meet the capabilities defined in Section C and the requirements in Section M will be eligible for award. Award(s) will be made based on technical acceptability and price. If there is only one Offeror that meets the conditions of this solicitation, then only one award will be made. However, the Government reserves the right to reject all offers that do not offer a significant economic advantage.

C.1.3.3 RTAS Services

C.1.3.3.1. The Government has defined six service groups: Voice Services (VS), Circuit Switched Data Service (CSDS), Dedicated Transmission Service (DTS), Internet Access Service (IAS), Broadcast Access Service (BAS), and SONET Ring Service (SRS). Of the six service groups, there will be three mandatory services the offerors shall propose to be eligible for a RTAS award. The three services are: Voice Services, Dedicated Transmission Service, and Internet Access Service. Offerors shall provide the mandatory services to the Government and the other services where commercially available.

C.1.3.3.1.1 Voice services (VS). Offerors shall propose voice services to be eligible for a RTAS award. Voice services are specified in a functional manner in order to allow Offerors the flexibility to meet voice requirements with either traditional or emerging technologies. Offerors shall have the additional flexibility to determine the extent of service coverage within the RTAS service area, Offerors are also encouraged to propose a complementary set of technical support services that enhance their voice service offerings.

C.1.3.3.1.2 Circuit Switched Data Services (CSDS). Offerors shall propose data services to be eligible for a RTAS award. The Government has specified a required set of data services described herein. An Offeror shall meet all requirements associated with that service. Offerors are allowed the flexibility to meet the data service requirements with emerging technologies. Offerors are also encouraged to propose a complementary set of technical support services that enhance their data service offerings.

C.1.3.3.1.3 Dedicated Transmission Services (DTS). Offerors shall propose DTS to be eligible for a RTAS award. The Government has specified a required set of DTS described herein. An Offeror shall meet all requirements associated with these services. Offerors are allowed the flexibility to meet the DTS requirements with emerging technologies. Offerors are also encouraged to propose a complementary set of technical support services that enhance their DTS offerings.

C.1.3.3.1.4 Internet Access Services (IAS). Offerors shall propose IAS to be eligible for a RTAS award. The Government has specified a required set of IAS described herein. An Offeror shall meet all requirements associated with these services. Offerors are allowed the flexibility to meet the IAS requirements with emerging technologies. Offerors are also encouraged to propose a complementary set of technical support services that enhance their IAS offerings.

C.1.3.3.1.5 Broadcast Access Services (BAS). Offerors may propose BAS to be eligible for a RTAS award. The Government has specified a required set of BAS described herein. An Offeror shall meet all requirements associated with these services. Offerors are allowed the flexibility to meet the BAS requirements with emerging technologies. Offerors are also encouraged to propose a complementary set of technical support services that enhance their BAS offerings.

C.1.3.3.1.6 SONET Ring Services (SRS). Offerors may propose SRS to be eligible for a RTAS award. The Government has specified a required set of SRS described herein. An Offeror shall meet all requirements associated with these services. Offerors are allowed the flexibility to meet the SRS requirements with emerging technologies. Offerors are also encouraged to propose a complementary set of technical support services that enhance their SRS offerings.

C.1.3.3.2 A summary of the RTAS Service is provided in Table C.1-1. Offerors are encouraged to propose additional commercially available services and equipment that enable, enhance, or otherwise extend their service offerings and value to the Government.

C.1.3.3.3 RTAS services include local access; i.e., the dedicated or switched connection from the Offerors’ switch to the customer’s Service Delivery Point (SDP) and includes transmission. RTAS services include local access and transport, the connections between the Offerors locations serving the originating and terminating SDPs within the RTAS service area, and the Interexchange Carrier (IXC) access, the connection between the RTAS network and the IXC Point of Presence (POP). The Offeror shall support IXC access by providing customer organizations the ability to choose the Government-specified Government Designated Interexchange Carrier (GDIXC)/Pre-subscribed Interexchange Carrier (PIC) for long distance services.

Table C.1-1. RTAS Services (Note: Services may be provisioned with functional equivalents.)

Service Group
Services and Products
Voice Services (VS)
1. Analog Business Lines.

2. Analog Centrex Lines or Centrex type service.

3. EKL (Electronic Key Line)

4. Digital ISDN Direct BRI and ISDN Centrex

5. Digital ISDN PRI PBX System Access Line

6. Analog trunking

7. Internet Access-Dynamic DSL

8. Internet Access-Static DSL

9. T-1/DS1 Access Line

10. T-3/DS3 Access Line

11. SONET

12. Interface to the Federal Technology Service FTS2001 Network and/or subsequent contract(s) awarded as its replacement (i.e. Networx Universal and Enterprise).

13. Provide Voice Messaging Services to include Voice Mail boxes, Automated Attendants, Remote Access, and Call Processors where the service is requested.

14. Equal access to the long distance carrier selected as the inter-exchange carrier (PIC) by dialing 1 before the long distance number. The PIC selected may be a FTS2001 or Networx vendor.

Data Services (DS)
1. Circuit Switched Data Service (CSDS)
Dedicated Transmission Service (DTS)
1. Point to point services
Internet Access Service (IAS)
1. At download speeds from 768KB to but not limited to 1.544 MPS.
Broadcast Access Service (BAS)
1. Basic cable channels.
SONET Ring Services (SRS)
1. Self healing network.

2. Provide speeds from OC3 to OC 48 to include OC3c to OC48c.

C.1.3.3.4 Throughout the life of the contract, the Offeror shall provide access to all telecommunications services within the Offerors respective suite of offerings. As new services and features become available, the Offeror shall propose their inclusion in the RTAS contract within 30 calendar days. If there is sufficient interest within the Government, the contract shall be modified in accordance with Section H.14, Technological Refreshment Services.

C.1.4 Organization of the Statement of Work

Section C.2 describes required telecommunications services and features, including performance and interface requirements; Section C.3 describes requirements for management and operations services; Section C.4 describes the requirements for equipment that may be acquired under this contract; Section C.5 describes transition and implementation requirements; Section C.6 describes requirements for priority service and restoration of services and facilities; and Section C.7 summarizes general management requirements.

C.2 Telecommunications Services and Features

The general format of the technical section is as follows:

General Service Requirements (C.2.1)

Voice Services (VS) (C.2.2)

Circuit Switched Data Services (CSDS) (C.2.3)

Dedicated Transmission Services (DTS) (C.2.4)

Internet Access Services (IAS) (C.2.5)

Broadcast Access Services (BAS) (C.2.6)

SONET Ring Services (SRS) (C.2.7)

C.2.1 General Service Requirements Multiple contract awards are preferred and will be based on the Offerors’ ability to satisfy the functional requirements of the current RLSC and MAA contracts where currently commercially available.

C.2.1.1 Service Delivery Points (SDP)

C.2.1.1.1 The SDP is the interface point for the physical delivery of a service, the point used by the Offeror to identify the charges for services rendered. Each SDP is defined as the combined physical, electrical, and service interface between the Offerors network and the Government’s on-premises equipment, off-premises switching and transmission equipment, and other facilities, such as those provided by telephone central offices.

C.2.1.1.2 The Government's requirements are for services and features to the SDP. Refer to Figure C.3-3. The Offeror shall deliver service to the SDP, and shall be responsible for service between the designated SDPs.

C.2.1.1.3 Agencies require flexible SDPs under the RTAS contract. They require freedom to select the SDP location, so that they can maintain as much control over their telecommunications infrastructure as they feel is necessary and make the best use of their assets.

C.2.1.1.4 The Offeror shall deliver service to the agency-specified SDP location. The SDP may be located at the Network Point of Presence (NETPOP) or the desktop. As the required SDP location moves away from the NETPOP and towards the desktop, the Offerors responsibilities increase. The Offerors maintenance and network management responsibilities increase when service is extended to the desktop equipment. The Offeror may become responsible for the inside wiring, service enabling equipment, and the operational management of the service up to the CPE. Contract Line Item Numbers (CLIN’s) have been established in Section B. for these flexible SDP requirements.

C.2.1.1.5 The User-to-Network Interface (UNI) specifications for some flexible SDP requirements are described service-by-service in C.2.2.4., C.2.3.4., and C.2.4.4.

C.2.1.2 Inside Wiring

C.2.1.2.1 The inside wiring for all orders shall be installed by the Offeror as part of the basic service up to the required SDP. For orders where the Government specified SDP is located beyond the NETPOP and the existing connection between the serving office and the SDP meets the technical requirements, the Offeror may use the existing connection. If the infrastructure does not meet the service parameter the Offeror shall assume responsibility for installing the inside wiring.

C.2.1.2.2 For orders where the existing connection between the serving office and the SDP is determined by the Offeror to be unsatisfactory, the Offeror shall provide notification of non-compliance in a Wiring Non-Compliance Report and propose a solution within five business days after service order acknowledgment. An unsatisfactory connection, by definition, does not allow the Offeror to provide service from the RTAS serving office to the SDP at the performance levels specified. The Offeror shall demonstrate, with appropriate engineering specifications and evidence, that the existing connection is unsatisfactory.

C.2.1.2.3 Existing inside wiring may be owned and maintained by other Offerors, the commercial building owner, or the Government. When the Government agrees with the Offerors assessment that the inside wiring is unsatisfactory, the Government may require that the Service Provider install inside wiring via a CLIN defined in Schedule B - Inside Wiring.

C.2.1.2.4 The Government reserves the right to use other Offerors to upgrade the existing inside wiring or to install the new inside wiring. The Offeror shall coordinate with the building manager, agency telecommunications manager, and the wiring Offeror and may act as the Government’s agent in accordance with Section G.1.3, Agent for the Government when directed in writing to do so by the CO or COTR.

C.2.1.2.5 Inside wiring shall conform to Federal Information Processing Standards-Publications (FIPS-PUBS) 175 (Federal Building Standards for Telecommunications Pathways and Spaces), 176 (Residential and Light Commercial Telecommunications Wiring Standards), 187 (Administrative Standards for Telecommunications Infrastructure of Federal Buildings), and 195 (Federal Building Grounding and Bonding Requirements for Telecommunications). Inside wiring shall also conform to U.S. cabling and safety standards and guidelines as published by Building Industry Consulting Services Institute (BICSI) and the American National Standards Institute (ANSI)/Electronic Industry Association/Telecommunications Industries Association (EIA/TIA) 568/569/606/TSC-36/TSC-40, ANSI/National Fire Protection Association (NFPA)-70, and EIA/TIA568A.

C.2.1.2.6 The complete inside cable distribution system shall be labeled in accordance with ANSI/EIA/TIA 606, Administration standard for the Telecommunications Infrastructure of Commercial Building, dated February 1993. Conductors shall be cabled so as to insure against induction in voice/data circuits. Each federal building shall be reviewed individually for this requirement by the offeror and any questions or concerns about its applicability shall be discussed with the COTR and CO.

C.2.1.2.7 All inside distribution cable installed under this contract shall meet the EIA/TIA/TSB-36 standard for data rates of 100 Mb/s for Category 5E or better. Unshielded Twisted Pair (UTP) cable shall conform to the EIA/TIA-568A, “Technical Systems Bulletin - 36 (TSB-36),” and to FIPS 174, “Federal Building Wiring Standard” for 5E cable, as appropriate, and shall be plenum rated.

C.2.1.2.8 The cable distribution system cable pair shall be fully tested with issuance of each task order. The cable records shall identify each cable as labeled, used cable pairs and bad cable pairs. Minimum test requirements are for opens, shorts, crosses, and split pairs on Category 3 or 5E voice cables, as appropriate. Crosstalk attenuation within the inside cable distribution system shall be within the applicable industry standards throughout the frequency range. All Category 5E cables, including connectors, shall be tested to ensure that proper installation practices were observed and that the installation meets the requirements of EIA/TIA TSB-36, “Additional Cable Specifications for Unshielded Twisted Pair Cables,” and EIA/TIA TSB-40, “Additional Transmission Specifications for Unshielded Twisted Pair Connecting Hardware.” These measurements shall be entered as part of the cable records. All cable records shall be available at acceptance testing and maintained thereafter in the agency’s Telephone Switch Room or Main Distribution Frame (MDF) room. All future changes (used pair, failed pair, etc.) shall be posted in these records as the change occurs by the Offeror. The Offeror shall assure the cable meets the requirements of ANSI/ Insulated Cable Engineers Association (ICEA) S-84-608, S-85-625, Telcordia Documents as applicable, National Electric Code (NEC) -800-3 (B) and Underwriters Laboratories (UL) Section 800-3 (b).

C.2.1.2.9 Cable shall be delivered to the existing NETPOP within all federal buildings and all buildings where federal agencies lease space. The Government may require the Offeror to perform a system certification of the inside wiring between Government-designated points (e.g., the NETPOP and the SDP) to document results prior to acceptance.

C.2.1.2.3 House Cable/Wire Installation and Maintenance C.2.1.2.3.1 The Offeror shall be responsible for providing all cable/wire, terminals, blocks, installation hardware, and miscellaneous materials required to provision service to the SDP. The Offeror is responsible for all cross connections required to accomplish the complete installation to the SDP requested. Each cross connection and termination shall be labeled and recorded in the facility cable records.

C.2.1.2.4. Existing Government House Cable / Wire C.2.1.2.4.1 Existing cable/wire may be used by the Offerors (wherever practical) with coordination/approval of the Government representative; however, the Offeror is responsible for ensuring the performance requirements of the ordered service. Prior to the reuse of existing cable not currently in use, the Offeror shall tone, test, and label to ensure compliance with Original Equipment Manufacturer (OEM) performance standards. The Offeror shall be responsible for maintaining any cable owned by others when the Offeror has used the existing infrastructure to deliver service. The Offeror shall be responsible for maintaining any cable the Offeror installs or uses in a building. The government reserves the right to require and direct the use of existing cable and/or cable termination facilities (cable frames) or the installation of new cable. Necessary cross-connects to include the labeling of all cross-connects shall be included as part of the Service Initiation Charge (SIC) for any service installation.

C.2.1.2.4.2.The Offeror shall maintain a current inventory of the NPA/NXXs and telephone numbers assigned through the contract services by state and city, which shall be available to the GSA FAS COTR at intervals to be determined by the Offeror and the Government. The Offeror shall include status information on the numbers, to include but not limited to those assigned, deleted and or modified. The Offeror shall provide number portability at no cost to the Government. The Offeror shall ensure that the numbers are available for use when requested.

C.2.1.3 Site Preparation

C.2.1.3.1. Any Offeror-provided equipment to be located on customer premises shall be placed in locations approved by the Government. Requests for Government-controlled space to house equipment shall include a primary and an alternate for each equipment location. The Offeror shall provide detailed information regarding floor space, ceiling height, electrical, environmental, and floor-loading requirements. The Government will provide space at the time of the Notice to Commence Work and will make every effort to provide the space in the primary location but in some cases may require use of the alternate space. This approval will be on a case‑by‑case basis. Where available, the Government will authorize the use of a reasonable amount of space and power without charge.

C.2.1.3.2. Requirements for commercial power, backup power, grounding, conduits, frames, terminals, room construction or environmental requirements shall be provided by the Offeror to the ordering agency. A site preparation survey report shall be provided to the Government by the Offeror for the proper equipment and service operation.

C.2.1.4 Final Disposition of Government Owned Cable Plant and Equipment Manuals/Records.

C.2.1.4.1. The Offeror shall convey to the government, on the final day of this contract, all current equipment and cable plant records, operational and maintenance manuals, and other pertinent documentation, at no additional cost to the Government. In addition, the Offeror shall make available all of the above information anytime requested by the Government representative throughout the contract term.

C.2.1.5 Local Loops.

C.2.1.5.1. RTAS VS and CSDS local access connections shall conform to the standards of Telcordia’s Notes on the Networks (SR‑2275).

C.2.1.6 Offeror Compatibility.

C.2.1.6.1. The Offeror, as part of the basic service, shall support the customer as necessary in testing hardware and software that interfaces with the RTAS network to assure that the customer’s systems, services, features, and applications function as required. When a non-standard solution is required to resolve a system incompatibility, the implementation of the solution shall be approved on an individual-case basis with the Government.

C.2.1.7 Interoperability

C.2.1.7.1. The Offeror shall support interoperability for service offerings to allow a user of a service from one RTAS contract to be able to communicate with users of services from other service providers, RTAS and others, with equivalent service. The GSA recognizes that different levels of interoperability (i.e., partial or full) exist commercially, particularly in the area of data networking. Interoperability shall be made available for any service offered by the Offeror and be interoperable with other RTAS Offerors’ service. The Offeror shall notify the GSA of the details regarding the degree of interoperability available for the services. In addition, the Offeror shall make any future service interoperable at no additional cost to the GSA when the Offeror proposes additional contract services.

C.2.1.8 Numbering Plan and Dialing Plan

C.2.1.8.1 The Offeror shall support a uniform numbering plan for all RTAS services that conforms to the North American Numbering Plan (NANP) and is consistent with the current FTS2001 and future Networx dialing plan. New services shall be accommodated within this framework. The NXX blocks that are being used by RTAS are identified in Section J.3.1.

C.2.1.8.2 The Offeror shall be responsible for administering changes in the NANP affecting the RTAS network users. Changes shall be implemented no later than 30 calendar days after notification of NANP changes.

C.2.1.8.3 The Offeror shall be responsible for the compatibility of the RTAS numbering scheme with the numbering plan of both the GDIXC networks and the local exchange network. Current FTS2001 and future Networx subscriber numbers shall be maintained whenever technically possible. Detailed information regarding the FTS2001 and Networx numbering and dialing plans will be provided to Offerors after contract award through the release of individual TOPS orders.

C.2.1.9 Performance C.2.1.9.1 The Offeror shall be responsible for all aspects of the Quality of Service (QoS), security, interconnectivity, and interoperability in support of delivery of RTAS services. The applicable performance parameters for each service are specified in C.2.2 through C.2.5. Each performance parameter is defined in terms of the minimum acceptable level of performance for the service or feature. The Offeror shall deliver services at a performance level equal to or greater than prevailing standards. If the available commercial performance parameter is more demanding than the minimum acceptable level specified in this contract, the available commercial performance parameter shall prevail.

C.2.1.10 System Attributes

The Offeror shall meet the following general system minimum requirements over the life of this contract, or the prevailing industry standard, whichever is more stringent:

C.2.1.10.1 Reliability

The maintainable design life of all Offeror-provided components, circuits, and equipment shall be at least seven years. The design life shall be on the basis that normal recommended maintenance procedures will be followed. Systems shall be designed with sufficient redundancy to ensure system availability as referenced in C.2.1.10.4.

C.2.1.10.2 Robustness

The Offerors infrastructure shall be sufficiently robust that failure of any single system, sub system or component will not cause loss of service to more than 10% of their RTAS subscribers at any given geographic location. Downtime consists of all time required to restore the system.

C.2.1.10.3 Warranty Period

All equipment and components procured as a unit under this contract shall be warranted for a period not less than the time specified in the original equipment manufacturer's warranty. Repair or replacement of any item during the warranty period shall be at no cost to the Government, and the Offeror shall provide substitute equipment during the period of repair. These rights shall be in addition to those provided by FAR 52.246-20 (Warranty of Services), Section I-92., C.2.1.10.4 Availability of Service

RTAS services shall be available 24 hours a day, seven days a week. The availability of each required service shall be at least 99.5 percent at each SDP. For purposes of the RTAS contract, the availability shall be calculated as follows:

Total uptime is the total amount of time the service is available within a one-month period. Total downtime is the total amount of time that the service is unavailable within a one-month period. Total downtime includes scheduled maintenance downtime if the service is unavailable for use.

C.2.1.10.5 Network Synchronization

The RTAS network shall be capable of supporting a common and highly accurate timing mechanism traceable back to a Stratum 3 source.

C.2.1.10.6 Network Architecture

The Offeror shall implement a network architecture that delivers specified services and features throughout the RTAS service area and interfaces with the Public Switched Network in a manner that meets the requirements of this Performance Based Statement of Work (PBSOW). The Offeror is responsible for all maintenance, administration, upgrades, etc., for all network based systems and service.

C.2.1.10.7 The service, including all hardware and software, must be maintained and upgraded in accordance with industry and manufacturer specifications and standards. As part of the baseline service, Offeror shall provide modifications to switching platform mandated by industry changes and/or manufacturer’s requirements. Advance notification shall be provided a minimum of two weeks for any change affecting service delivery.

C.2.1.10.8 The current service/system/station, feature information is provided in Section J, Attachments J-2. The information is not intended to be all inclusive. The government seeks a solution that is commercially available and comparable to the existing functionality.

C.2.1.10.9 Offeror shall provide electronic billing media capable of interfacing with the Government Telecommunications Ordering and Pricing System (TOPS). The file formats are provided in Section J.6.

C.2.1.10.10. Service Reliability and Automatic Processor Reload

The service(s) shall be based on technology that has critical component redundancy as well as automatic system re-initialization to the identical level of service prior to need for reload.

C.2.1.10.11. Transmission Service

Voice, Data and Video Transmission Service offerings shall be provided where commercially available. Service requirements may include, but are not limited to the functionality supporting DOD/DID trunks, business lines, Centrex -like service and related features, internet access services, broadcast access services, T-1, T-3, SONET (point to point and ring), ISDN BRI/PRI, and VOIP service (this shall also include all loop and ground start related services). These services may include digital information transport and processing for connection of voice, video, and data terminals to the Public Switched Network (PSN), Internet Protocol/World Wide Web (IP/WWW), Local/Wide Area Networks (LAN/WANs), and Point-to-Point connectivity.

C.2.1.10.12. Conformity to Standards

C.2.1.10.12.1 Throughout Section C, references are made to standards (including interim standards, Internet Engineering Task Force [IETF], Requests for Comments [RFCs], or defacto standards) as they exist at the time of issuing this RFP. Compliance with the latest versions of these standards is expected throughout the duration of the contract. Considering the evolving nature of standards in the telecommunications industry, discussions may be held annually between the Offeror and the Government to assess the impact of any changes in standards on the RTAS network. The Offeror shall prepare a draft Technology Refreshment Plan with the initial proposal, a final no later than 30 calendar days after award, and updates (see Sections H. and G.) annually thereafter that incorporates the agreed changes.

C.2.1.10.12.2. Service provided to the Government shall conform to the standard commercial offerings. If the Offeror implements a new or modified standard for any customer in the RTAS service area for a service in the RTAS contract, the Offeror shall propose to implement the change into the RTAS network within six months in accordance with C.7.2, Systems Changes. If a customer organization wants conformance to a new standard earlier, than the Offerors commercial plan for development, then it shall be negotiated on an individual-case basis.

C.2.1.10.12.3. Where multiple standards are cited, the order of precedence shall be effective in the following order of precedence unless otherwise noted:

C.2.1.10.12.3.1. Federal Information Processing Standards

C.2.1.10.12.3.2 Other Federal Standards

C.2.1.10.12.3.3. Federal Telecommunications Recommendations (FTRs)

C.2.1.10.12.3.4. Industry forums (e.g., North American Integrated Services Digital Network (ISDN) Users Forum [NIUF], Frame Relay Forum, Asynchronous Transfer Mode Forum [ATMF])

C.2.1.10.12.3.5. Internet Activities Board (IAB)

C.2.1.10.12.3.6. ANSI, Electronic Industries Association [EIA], Institute for Electrical and Electronic Engineers (IEEE), Insulated Cable Engineers Association (ICEA), National Electric Code (NEC), Telecommunications Industry Association [TIA] Telecommunications Industry Forum (TCIF), and Underwriters Laboratories (UL) standards

C.2.1.10.12.3.7. Telcordia

C.2.1.10.12.3.8. International Telecommunications Union-Telecommunications Service Sector (ITU-TSS)

C.2.1.10.12.3.9. Proprietary standards

C.2.1.10.12.4.The Government reserves the right to waive the standards requirement for any service.

C.2.1.10.12.5.The Offeror shall support connections for switched and dedicated applications and shall provide service at the highest commercially-available standards over the life of the contract. The services shall conform to the following publications:

C.2.1.10.12.5.1

ANSI T1.101

C.2.1.10.12.5.2

ANSI ISDN

C.2.1.10.12.5.3 ANSI SS7 standards

C.2.1.10.12.5.4 Telcordia Notes on the Networks, Issue 4, October 2000

C.2.1.10.12.5.5 All applicable Telcordia, ANSI and ITU standards

C.2.1.10.12.5.6 ITU-Terminating Equipment (TE) 164 as interpreted by the Industry Number

Committee of ATIS

C.2.1.10.12.5.7 The Offeror shall comply with all new versions, amendments, and modifications to the above documents and standards as they become applicable.

C.2.1.10.12.5.8. The Offeror shall support any combination of custom ISDN lines and ISDN lines that conform to the national standard at specified Government buildings throughout the life of the contract.

As applicable, voice services shall also conform to:

C.2.1.10.12.5.9

IEEE 802.1p/q, 802.3x

C.2.1.10.12.5.10 Internet Engineering Task Force (IETF) RFC 2132 for Dynamic Host

Configuration Protocol (DHCP)

C.2.1.10.12.5.11 IETF RFC’s 2916 (ENUM), 2806

C.2.1.10.12.5.12 IETF RFC’s for Internet Protocol (IP) IPv4. IPv6 when and where offered commercially by the Offeror.

C.2.1.10.12.5.13 ITU RFC 1349 ToS, 2474, 2475 DiffServ

C.2.1.10.12.5.14 ITU-TE.164 as interpreted by the Industry Number Committee of

Alliance for Telecommunications Industry Solutions (ATIS).

C.2.1.10.12.5.15

ITU-T G.107

C.2.1.10.12.5.16 ITU-T G.711, G.723.x, 7.26, G.728, or G.729.x

C.2.1.10.12.5.17 ITU-T H.248.1 MEGACO, H.323, H.350 when and where offered commercially by the Offeror.

C.2.1.10.12.5.18 ITU-T Q.700 series recommendations for Signaling System No. 7

C.2.1.10.12.5.19 ITU-T T.30, T.37, and T.38

C.2.1.10.12.5.20 Lightweight Directory Access Protocol (LDAP)

C.2.1.10.12.5.21 Media Gateway Control Protocol (MGCP) IETF RFC 3435 when and where offered commercially by the Offeror

C.2.1.10.12.5.22 Real-Time Transport Protocol (RTP) IETF RFC 3550

C.2.1.10.12.5.23 Session Initiation Protocol (SIP) IETF RFC 3261 when and where offered commercially by the Offeror

C.2.1.10.12.5.24 Transmission Control Protocol (TCP) IETF RFC 793

C.2.1.10.12.5.25 User Datagram Protocol (UDP) IETF RFC 768

C.2.2. Voice Services

C.2.2.1 Capabilities and Features C.2.2.1.1 Multiple contract awards are preferred and will be based on the Offerors’ ability to satisfy the functional requirements of the current RLSC and MAA contracts where currently commercially available. Basic capabilities shall be included in the base price of the service. Features are additional service functionalities that shall be provided by the Offeror and may be priced separately from the base price of the service. Basic capabilities and features that are required for RTAS voice services are discussed in this section. The offeror shall provide a bundled feature package with reduced pricing for dial tone service ordered with the need for basic line features. Such a package as an example would include voice mail, call forwarding (busy, No Answer and variable), call hold, call P/U and hunting, and 3 way conference.

C.2.2.1.2 Requirements Identification and Definition

A service feature is a quality of the service that is required by the customer, either a basic capability that is included in the base price of the service or a feature that may be priced separately from the basic price of the service. If the Offeror elects not to separately price a feature, then it becomes a basic capability. Required basic capabilities and features are described in this section and listed in Table C.2-2. A service functionality such as one-digit speed calling may be a required basic capability for one product and a feature for another. The following basic capabilities/features listed in Table C.2-2 shall be provided by the Offeror:

Table C.2-2 Definition of VS Basic Capabilities and Features (Note: Functional equivalency is required.)

Basic Capability/Feature
Definition

Access to 311 service

Subscribers shall be able to obtain non-emergency service/assistance by dialing 311, where available.

Access to 411 service
Subscribers shall be able to obtain information service/assistance by dialing 411.
Access to 7XX service
Subscribers will be able to obtain access when using their Government Emergency Telecommunications Service (GETS) cards and the LD vendor 7XX numbers for testing purposes.
Access to 911 service
Subscribers shall be able to obtain emergency service/assistance by dialing 911.
Additional directory number
Feature over analog and ISDN lines to provide two voice, voice/data, or two data channels utilizing two Service Profile Identifier and Directory (SPID) numbers.
Agency-Recorded Message Announcements
Authorized Government personnel shall be able to record message announcements within the network after authentication of user-ID and password/token.
Special Character dialing
A term pertaining to a character set that contains letters, digits, and sometimes other characters, such as punctuation marks.
Alternate call directory listings
A feature that allows alternate numbers to be indicated under a directory listing.
Authorization code
A code that, once entered, can permit the user to gain access to a system or service.
Automatic call-back
Allows a user to place a call-back on a busy line. When the called station goes on-hook, the originating station is rung and when answered, the original call is automatically placed.
Automatic Route Selection
Allows calls to be routed automatically in accordance with a Government-specified routing plan.
Backup of ISDN PRI Shared D Channel
Shared-D channel backup/redundancy, for PRI’s with a 24B+0D configuration.
Billing Account Codes (BAC)
A multiple-digit number (usually three) that is assigned by the Government to uniquely identify agency cost centers.
Blocked exchanges
The process of denying access to a NPA.
Blocking caller-paid information phone numbers
Blocks caller-paid calls from a station to an “information” or Directory Assistance number (e.g., 900 & 976).
Blocking Operator Assisted Calls – Collect Calls
Blocks collect calls from an operator (Directory Assistance service).
Blocking dialed Carrier Identification Code (CIC)
Blocks calls to carriers other than the pre-subscribed carrier on a per-call basis.
Blocking of selected numbers
Blocks calls incoming from pre-determined numbers.
Call consultation
A feature that allows a user to alternate between a party on hold and an existing conversation.

Call Detail Records (CDR)

RTAS lines (but not RTAS trunks) require the basic capability to prepare CDR’s. A CDR records certain characteristics of a telephone call, including the time and duration of the call, the called number, the calling number (when passed through), and the charge. The associated CDR Report (see Section G.) is sent to the billing office address specified in the order. The Offeror shall identify the designated level of call origination possible; i.e., the originating station calling number, authorization code, or trunk as appropriate. The Government considers CDR data to be sensitive information, and the Offeror shall take appropriate safeguards to protect it.

Call forward – busy
A feature that permits calls attempting to reach a busy station line to be redirected to a predetermined line when the called station is in use.
Call forward – no answer
A feature that provides for forwarding of incoming calls to a predetermined line when the called station line does not answer within a prescribed number of rings.
Call forward – variable
A feature that allows a user to choose to reroute incoming calls to another specified telephone number. It shall be possible for the station to activate or cancel this feature.
Call forwarding – off-net
A feature that allows all calls destined to a station to be routed to another off-net station, designated during activation, regardless of the busy or idle state of the called station. It shall be possible for the station to activate or cancel this feature.
Call hold
A feature that allows a station user to “hold” any call in progress by flashing and then dialing a “hold” code or function key, thus freeing the line for the purpose of originating another call or returning to a previously held call.
Call hunting
Routes incoming calls through a series of stations. If the first station is busy, the calls will be routed to the second station in the series, and so on.
Call park
Allows a call to be parked at a directory number for retrieval by another line or trunk.
Call pick-up
A feature that allows a station user to answer any calls directed to another station line within his or her own preset pickup group by dialing a pickup code from an idle or busy station.
Call trace
Allows the user on any line to initiate identification of the calling party by dialing a code.
Call transfer
A feature that allows a station user to transfer any call in progress to another station within the same system without the assistance of the attendant.
Call waiting
A feature that allows a call to a busy station line to be held waiting while a tone signal is directed towards the busy station user. (Only the called station user shall hear this tone.)

Caller ID

Serving switch provides the basic capability of passing the calling number to the terminating station.

Caller ID, with name
Serving switch provides the basic capability of passing the calling number and registered name of account to the terminating station.
Calling number suppression
Provides the originating user with the capability to block the station number from being passed to the terminating station. It shall be possible to enable this function either on a per-call basis or indefinitely.
Circuit Switched Data on B Channel
Data provided at a bandwidth of 64 Kbps maximum.
Class of Service (COS)
Privileges given to a particular station. The COS functionality shall establish classes of service available to each subscriber line. Due to the diverse nature of the customers served, it shall be possible to assign a COS to each subscriber line, independent of the COS assigned to other subscriber lines;

It shall be possible to change the COS without requiring a station number change. The Government will select a variety of classes, some of which may be unique. The class of service applicable to each line will be determined by the Government at the time of the Notice to Commence Work. The Offeror shall provide the following seven minimum access level plans:

COS 1 – Limited Service: Any seven-digit RTAS number served by the same RTAS switch as the calling number COS 2 - Limited Service: intercom, 911 and toll free

COS 3 – Standard Service: Any RTAS number.

COS 4 – Commercial Service: COS 2 plus access to the local exchange network commercial NXX’s plus Government credit card service

COS 5 – Government Service: COS 3 plus access to national GDIXC service (on-net)

COS 6 – Extended Service: COS 4 plus access to national FTS service (on-net and off-net)

COS 7 – National Service: COS 5 plus operator-assisted (local and national) calls

COS 8 – International Service: COS 6 plus access to International Direct Distance Dialing (IDDD) service

Customized group dialing plan
A service functionality that allows the dialing plan to be customized for a defined group of stations within the system.
Customized Intercept and Recorded Announcement
A feature whereby the customer can set the recorded announcement or intercept message when a call cannot be completed.
Data call setup
Provides ability to set up a data call: by 1) data terminal (keyboard) dialing; 2) voice terminal dialing; or 3) dedicated voice terminal.
Data hot line
Provides for automatic non-dial placement of a data call to an endpoint when the originator goes off-hook.
Data line privacy
Protects data calls from being interrupted by any of the system’s overriding or ringing features.
Dial tone denial
Used in conjunction with Priority Treatment, enables critical personnel to make outgoing calls during conditions of severe system overload
DID number block assignment and maintenance
Assigns and maintains DID number blocks for a new DID-PBX installation.
DID/DOD two way

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