section c - cell phones, mobile phones & wireless … · web viewvincent and the grenadines...

Contract No. GS00T99NRD2001

TABLE OF CONTENTS

SECTION PAGE

C DESCRIPTION/SPECIFICATION/STATEMENT OF WORK........................................................C-1

C.1 Background................................................................................................................................... C-1C.1.1 Federal Telecommunications Services Program Objectives..................................................C-2C.1.2 FTS2001 Objectives.............................................................................................................C-2C.1.3 Scope................................................................................................................................... C-3C.1.4 Upgrades and Enhancements................................................................................................C-4

C.2 SERVICE DESCRIPTIONS, TECHNICAL REQUIREMENTS, AND PERFORMANCE.............C-4C.2.1 General Requirements..........................................................................................................C-4C.2.2 Circuit Switched Services...................................................................................................C-45C.2.3 Switched Data Services....................................................................................................C-120C.2.4 Dedicated Transmission Service.......................................................................................C-141C.2.5 Wireless Services (Optional).............................................................................................C-141C.2.6 Satellite Services (Optional).............................................................................................C-141C.2.7 Value Added Services.......................................................................................................C-141C.2.8 Emerging Services............................................................................................................C-141

C.3 Management and Operations.....................................................................................................C-141C.3.1 General Information.........................................................................................................C-141C.3.2 Program Administration...................................................................................................C-141C.3.3 Program Management Office............................................................................................C-141C.3.4 Customer Service Office...................................................................................................C-141C.3.5 Service Ordering..............................................................................................................C-141C.3.6 Billing.............................................................................................................................. C-141C.3.7 Network Management.......................................................................................................C-141C.3.8 Planning and Engineering................................................................................................C-141C.3.9 Trouble and Complaint Reporting.....................................................................................C-141C.3.10 Training........................................................................................................................... C-141

C.4 TRANSITION, MIGRATION AND IMPLEMENTATION.......................................................C-141C.4.1 Introduction...................................................................................................................... C-141C.4.2 Transition......................................................................................................................... C-141C.4.3 Migration......................................................................................................................... C-141C.4.4 Implementation.................................................................................................................C-141

C.5 NATIONAL SECURITY AND EMERGENCY PREPAREDNESS...........................................C-141C.5.1 Introduction...................................................................................................................... C-141C.5.2 NS/EP Capabilities for Voice Services..............................................................................C-141C.5.3 NS/EP Capabilities for Data Services...............................................................................C-141C.5.4 NS/EP Capabilities for Network Facilities and Infrastructure...........................................C-141C.5.5 Signaling System..............................................................................................................C-141C.5.6 Satellite Communications Command Link Protection........................................................C-141C.5.7 NS/EP Interface with the Contractor................................................................................C-141C.5.8 Contractor’s Emergency Management..............................................................................C-141C.5.9 Readiness of NS/EP Capabilities......................................................................................C-141

C-iii


SECTION PAGE

C.6 PERFORMANCE DATA REPORTING REQUIREMENTS......................................................C-141C.6.1 General Performance Data Reporting Requirements........................................................C-141C.6.2 Service-Specific Monthly Performance Reports................................................................C-141C.6.3 Daily Performance Data Requirements.............................................................................C-141C.6.4 General Services Administration Management Services Fee Performance Data

Requirements....................................................................................................................C-141

C-iv


LIST OF FIGURES

FIGURE PAGE

C.2.1.1.1-1 STRUCTURE OF MANDATORY TELECOMMUNICATIONS SERVICES DESCRIPTIONS....................................................................................................................C-7

LIST OF TABLES

TABLE PAGE

C.2.1.1.1.1-1 REQUIREMENTS FOR MANDATORY TELECOMMUNICATIONS SERVICES......C-8

C.2.1.2-1 DOMESTIC ACCESS FEATURE UNAVAILABILITY TABLE.........................................C-13

C.2.1.2-2 DOMESTIC TRANSPORT FEATURE UNAVAILABILITY TABLE................................C-14

C.2.1.2-3 NON-DOMESTIC ACCESS FEATURE UNAVAILABILITY TABLE...............................C-14

C.2.1.2-4 NON-DOMESTIC TRANSPORT FEATURE UNAVAILABILITY TABLE.......................C-15

C.2.1.2-5 SERVICE TYPES...................................................................................................................C-16

C.2.1.2-6 COUNTRY/JURISDICTION IDENTIFICATIONS..............................................................C-17

C.2.1.16-1 ACCESS TYPES...................................................................................................................C-37

C.2.1.16.3.3.1.1-1 MANDATORY INTEGRATED SERVICES DIGITAL NETWORK ACCESS.....C-42

C.2.1.16.3.3.1.2-1 OPTIONAL INTEGRATED SERVICES DIGITAL NETWORK ACCESS..........C-43

C.2.2.1.1.4.1.1-1 MANDATORY USER-TO-NETWORK INTERFACE FOR SWITCHED VOICE SERVICE........................................................................................................C-49

C.2.2.1.1.4.1.2-1 OPTIONAL USER-TO-NETWORK INTERFACE FOR SWITCHED VOICE SERVICE........................................................................................................C-50

C-v


TABLE PAGE

C.2.2.2.1.4.1.1-1 MANDATORY USER-TO-NETWORK INTERFACE FOR CIRCUIT SWITCHED DATA SERVICE....................................................................................C-66

C.2.2.2.1.4.1.2-1 OPTIONAL USER-TO-NETWORK INTERFACE FOR CIRCUIT SWITCHED DATA SERVICE....................................................................................C-67

C.2.2.3.1.4.1.1-1 MANDATORY USER-TO-NETWORK INTERFACE FOR TOLL FREE SERVICES...................................................................................................................C-77

C.2.2.3.1.4.1.2-1 OPTIONAL USER-TO-NETWORK INTERFACE FOR TOLL FREE SERVICES...................................................................................................................C-78

C.2.2.4.1.4.1.1-1 MANDATORY USER-TO-NETWORK INTERFACE FOR 900 SERVICE..........C-103

C.2.2.4.1.4.1.2-1 OPTIONAL USER-TO-NETWORK INTERFACE FOR 900 SERVICE...............C-104

C.2.3.1.1.4.1.1-1 MANDATORY USER-TO-NETWORK INTERFACES FOR PACKET SWITCHED SERVICE..............................................................................................C-125

C.2.3.1.1.4.1.2-1 OPTIONAL USER-TO-NETWORK INTERFACES FOR PACKET SWITCHED SERVICE..............................................................................................C-127

C.2.3.2.1.4.1.1-1 MANDATORY USER-TO-NETWORK INTERFACES FOR FRAME RELAY SERVICE.....................................................................................................C-137

C.2.3.2.1.4.1.2-1 OPTIONAL USER-TO-NETWORK INTERFACES FOR FRAME RELAY SERVICE...................................................................................................................C-139

C.2.3.3.1.4.1.1-1 MANDATORY USER-TO-NETWORK INTERFACES FOR INTERNET PROTOCOL INTERNETWORKING SERVICE....................................................C-148

C.2.3.3.1.4.1.2-1 OPTIONAL USER-TO-NETWORK INTERFACES FOR INTERNET PROTOCOL INTERNETWORKING SERVICE....................................................C-149

C.2.3.4.1.4.1.1-1 MANDATORY USER-TO-NETWORK INTERFACES FOR ASYNCHRONOUS TRANSFER MODE SERVICE.................................................................................C-160

C.2.3.4.1.4.1.2-1 OPTIONAL USER-TO-NETWORK INTERFACES FOR ASYNCHRONOUS TRANSFER MODE SERVICE.................................................................................C-161

C.2.4.1.4.1.1-1 MANDATORY USER-TO-NETWORK INTERFACES FOR DEDICATED TRANSMISSION SERVICE.......................................................................................C-175

C-vi


TABLE PAGE

C.2.4.1.4.1.2-1 OPTIONAL USER-TO-NETWORK INTERFACES FOR DEDICATED TRANSMISSION SERVICE.......................................................................................C-176

C.3.2.7.6.2-1 FORMAT FOR FTS2001 SERVICE DELIVERY POINT IDENTIFICATION CODE.............................................................................................................................. C-212

C.3.5.4.1.2 (e) HIERARCHY CODES.................................................................................................C-224

C-vii


SECTION C

DESCRIPTION/SPECIFICATION/STATEMENT OF WORK

C.1 BACKGROUND

The Federal Technology1 Service (FTS) provides Government users with up-to-date, cost-effective, and easy to utilize telecommunications services. Working in partnership with the Interagency Management Council (IMC), which advises the Administrator of General Services on all matters related to telecommunications services, FTS seeks to involve its users to achieve the best possible service. The program is designed to enhance the goals of the National Information Infrastructure (NII) and to support implementation of key information technology recommendations of the National Performance Review (NPR). The FTS program is expected to provide the bulk of the telecommunications services for the emerging Government Services Information Infrastructure (GSII). The FTS program comprises many contracts and acquisition activities, of which FTS2001 (see Section C.1.2) is one. Other contracts and acquisitions include but are not limited to Federal Wireless Telecommuni-cations Services, International Direct Distance Dialing, Technical and Management Support, Metropolitan Area Acquisitions (MAAs), and Wire and Cabling.

The FTS Program will be market oriented. It is explicitly recognized that:

(a) Multiple contracts will be required to most effectively meet Government requirements. The General Services Administration (GSA) and other agencies will compete and administer these contracts for the benefit of the overall program.

(b) The Government will encourage competition through multiple contracts of the same or overlapping scope.

(c) Acquisitions will be initiated and contracts awarded in the best interest of the Government. All contracts will be available to all users as authorized by law.

(d) Agencies will generally have the right to choose which contract they use to meet their needs, to buy from multiple contracts, and to change contractors and services within the FTS Program when appropriate to meet their requirements, subject to the limitations necessary to meet Minimum Revenue Guarantees.

1 Prior to October 1, 1997, the Federal Technology Service was called the Federal Telecommunications Service.

C-1


C.1.1 Federal Telecommunications Services Program Objectives

The principal objectives of the FTS program are to:

(a) Meet the functional requirements of the Federal Government and its agencies in a technically-effective and cost-effective manner.

(b) Support the implementation of the NII and GSII, and the recommendations of the NPR, including the implementation of electronic Government applications within the GSII.

(c) Provide access and interoperability between authorized users, for improved effectiveness and efficiencies, and to provide better services, at less burden.

The vision for the FTS Program is that communications should be transparent, flexible, and efficient for all FTS Program users including users of other systems with which Government users and systems interconnect or interoperate, irrespective of which FTS Program contract or contracts they may be using. In the Government’s view, flexible and efficient service is generally aided when end-to-end service is available. For example, this solicitation seeks to acquire up-to-date and price-competitive end-to-end (i.e., Service Delivery Point (SDP)-to-SDP) services through this solicitation. Thus, the majority of telecommunications services to be acquired by this solicitation are presently expected to include both access and transport. Access is defined as the portion of the service between the user and the contractor’s Point of Presence (POP), while transport is defined as the portion between the contractor’s POPs. Generally, a service will therefore comprise an originating access portion, a transport portion, and a terminating access portion.

The Government realizes that the telecommunications industry, in the United States (U.S.) and worldwide, is undergoing rapid and far-reaching changes. The pursuit of flexibility and efficiency in this changing environment may lead the Federal Government to acquire separately the access portion(s) or the transport portion for some or all of the services defined in this solicitation. This solicitation has been structured so that access and transport can be easily unbundled in support of such actions. However, the Government will continue to regard end-to-end transparent service as highly desirable.

C.1.2 FTS2001 Objectives

This solicitation is for telecommunications services and related services. Resulting contracts are collectively referred to as FTS2001. The Government intends to make two FTS2001 awards to one or two contractors. The term of each FTS2001 contract is 96 months, a 48 month basic contract period with four option periods of 12 months each. The contracts

C-2


also include provisions for internal competitive contract administration actions (Price Redetermination), at the Government’s discretion.

Services to be acquired include: circuit switched services (voice and data), switched data services, and dedicated transmission services. Additional services may be acquired if proposed. Following award, each contractor shall be responsible for all aspects of the provisioning and operation of its telecommunications services over the life of the contract.

Acquiring services, tracking their performance, invoicing for services rendered, and periodic reports are examples of activities under the contract(s) resulting from this Request for Proposal (RFP), requiring an exchange of information between the contractor(s) and the Government. It is the Government’s intent to conduct these exchanges electronically according to the developing standards defining Electronic Data Interchange (EDI). To the extent possible, given the current level of acceptance of these standards throughout industry, and the commercial availability of systems meeting these standards by the vendor(s) awarded FTS2001 contract(s), it is the Government’s intent to continually improve on these capabilities through the life of the contract. To this end the Information Exchange Guide (IEG), is attached to the RFP/contract, for the purpose of defining the details (e.g., format, data elements) of how the Government and the contractor(s) will exchange the information essential to administering and managing the contract(s) and the services acquired via the contract(s).

C.1.3 Scope

The scope of each resultant FTS2001 contract will include all services necessary for the Government to satisfy its worldwide telecommunications requirements for the life of the contract(s). In addition to the specific requirements set forth in Section C, the scope of this contract includes, at the discretion of the Government, local services2 including, but not limited to those described in MAA program RFP(s), technological enhancements, service improvements, and all new and/or emerging telecommunications services offerings. In particular, the scope of each FTS2001 contract will include all telecommunications services,

2 Local services are defined as services within a local environment such as an office or group of offices within a building, a building, a campus, a military base/port/camp/station, or metropolitan area - areas normally served by Private Branch Exchanges, Centrexes, Local Area Networks, Metropolitan Area Networks (e.g., the Government’s MAA contract(s)), etc.

C-3


features, functions, and offerings that will be generally available as a part of the contractor’s commercial offerings, as well as offerings available in the commercial marketplace, during the term of these contract(s), plus services for which there may not be commercial offerings.

The scope of this contract also includes management, support, maintenance, design and engineering services which are provided as a part of or adjunct to commercial telecommunications services in support of unique customer requirements.

This contract is for the use of all Federal agencies, authorized Federal contractors, agency-sponsored universities and laboratories, other organizations as defined in Section H.2, and, when authorized by law or regulation, state, local, and tribal Governments.

C.1.4 Upgrades and Enhancements

The Government recognizes that telecommunications technologies and services are rapidly evolving and advancing. The Government wishes FTS2001 services, features, etc. to remain up-to-date with commercial equivalents. Accordingly, the Government anticipates that services, features, etc., available under this contract will be increased, enhanced, and upgraded as these improvements become available.

In particular, the contractor shall provide upgrades to its commercial support systems, (including but not limited to systems for billing and invoicing, service ordering and tracking, trouble and complaint handling, and management and administrative reporting) at no additional cost to the Government as these upgrades become available to commercial customers at no or minimal costs.

C.2 SERVICE DESCRIPTIONS, TECHNICAL REQUIREMENTS, AND PERFORMANCE

C.2.1 General Requirements

This section defines the services that the Government intends to acquire under this procurement. Included in this section are the specifications of these services and their performance, features, and interfaces.

C-4


C.2.1.1 Services

The contractor shall provide the following types of services:

(a) Telecommunications Services. These services will be used for communications between users.

(b) Security Services. These services are divided into two categories -- basic security services, which shall be included as an intrinsic part of the telecommunications services provided, and which are intended to ensure availability and connectivity; and fee-based security services, which offer additional specialized forms of protection and which are ordered separately as desired by the user. Both categories are mandatory.

(c) Management and Operations Services. These services will be used to effectively manage and control telecommunications resources, reduce network management and operations costs, and administer the contract.

(d) National Security and Emergency Preparedness. This service will ensure that the network is maintained in a state of readiness for national emergencies.

Security, Management and Operation, and National Security and Emergency Preparedness (NS/EP) are regarded as integral to the provisioning of the telecommunications services.

These are described in more detail below.

C.2.1.1.1 Telecommunications Services

Mandatory telecommunications services are presented individually in detail in Sections C.2.2 through C.2.4 and in C.2.7.4. In order to assure that all facets of the requirements for each service are clearly presented each service description is structured in identical fashion. Two primary objectives largely determined how the service descriptions were structured. Understanding these objectives and the resulting organizational structure of Section C.2 will aid in understanding the RFP. The objectives considered in organizing this structure are:

C-5


(a) The need to identify separately the access and transport requirements for each service to allow for unbundling of access from transport in the future if the Government chooses to do so (e.g., access may be acquired under the Government’s MAA contract(s))

(b) The need to identify features, performance parameters, and interfaces unique to the access and transport segments of each service

The access and transport requirements for each mandatory telecommunications service are described separately. Requirements for both access and transport are described under the headings of:

(a) The basic service(b) Features(c) Performance(d) Interfaces

Interfaces are further subdivided into User-to-Network Interfaces (UNIs) and Local Access to Network Interfaces (LANIs). Mandatory and optional items are described separately in each category. Figure C.2.1.1.1-1 illustrates the structure. The specifications for mandatory telecommunications services in Sections C.2.2, C.2.3, and C.2.4 conform to this structure. (Note that the description of access in Section C.2.1.16 and the description of Video Teleconferencing Service (VTS) in Section C.2.7.4 have different structures).

As used in this RFP/contract, the term “Mandatory” identifies core items that must be offered. The contractor is not permitted to provide prices for mandatory items unless a pricing element exists in Section B. If a price is provided by the contractor then it must be in the format specified in Section B. Each mandatory item must meet or exceed the associated performance requirements as specified in this RFP.

As used in this RFP/contract the term “Optional” identifies items that may or may not be offered, at the option of the contractor. Specifications for optional items are provided throughout Section C.2. If offered, the contractor need not fully comply with the specifications provided. If offered, the contractor shall fully describe the optional item, including price, and how it differs from the specifications provided.

C-6


The telecommunications services are categorized below.

ServiceC.2.Y.X

AccessC.2.Y.X.1

TransportC.2.Y.X.2

InterfacesC.2.Y.X.1.4

UNIC.2.Y.X.1.4.1

LANIC.2.Y.X.1.4.2

Basic ServiceDescriptionC.2.Y.X.1.1

Features C.2.Y.X.1.2

PerformanceC.2.Y.X.1.3

InterfacesC.2.Y.X.2.4

Basic ServiceDescriptionC.2.Y.X.2.1

Features C.2.Y.X.2.2

PerformanceC.2.Y.X.2.3

LANIC.2.Y.X.2.4.1

Mandatory C.2.Y.X.1.2.1

Optional C.2.Y.X.1.2.2

Mandatory C.2.Y.X.1.4.2.1

Optional C.2.Y.X.1.4.2.2





Optional C.2.Y.X.2.2.2

Mandatory C.2.Y.X.2.2.1

(Y = 2, 3 or 4)

Figure C.2.1.1.1-1. Structure of Mandatory Telecommunications Services Descriptions

C.2.1.1.1.1 Mandatory Telecommunications Services

The contractor shall offer and provide the following services throughout the life of the contract:

(a) Circuit Switched Service (CSS), in which communications resources are shared among many users through the use of one or more circuit switching devices:

(1) Switched Voice Service (SVS)

(2) Circuit Switched Data Service (CSDS)

C-7


(3) Toll Free Service (including 800, 888, and other Service Access Code [SAC] services as they develop)

(4) 900 Service (including other equivalent SAC services as they develop)

(b) Switched Data Service (SDS), in which communications resources are shared among many users through the use of a packet/cell/frame switching device:

(1) Packet Switched Service (PSS)(2) Frame Relay Service (FRS)(3) Internet Protocol Internetworking Service (IPS)(4) Asynchronous Transfer Mode Service (ATMS)

(c) Dedicated Transmission Service (DTS), in which communications circuits are allocated to one user or a group of users.

(d) VTS, which is a Value Added Service (VAS).

Table C.2.1.1.1.1-1 contains a listing of the section numbers where the requirements for mandatory telecommunications services are specified. The section numbers in this table correspond to the “X.X.X” values in Figure C.2.1.1.1-1.

Table C.2.1.1.1.1-1. Requirements for Mandatory Telecommunications Services

Service SectionSwitched Voice Service C.2.2.1Circuit Switched Data Service C.2.2.2Toll Free Service C.2.2.3900 Service C2.2.4Packet Switched Service3 C.2.3.1Frame Relay Service C.2.3.2Internet Protocol Internetworking Service

C.2.3.3

Asynchronous Transfer Mode Service C.2.3.4Dedicated Transmission Service C.2.4

The detailed specifications for each of the above services are described in Sections C.2.2 through C.2.4 and in Section C.2.7.4 including performance parameters and the associated

3 The contractor may discontinue PSS after giving 24 months notice in writing to the Contracting Officer, provided that the contractor has ceased to offer and provide PSS as a commercial service at the time notice is given.

C-8


thresholds. Performance data reporting requirements and methods are specified in Section C.6.

As part of the service offering, the contractor shall provide, when requested by the user, support activities that may be required to ensure proper delivery and full and/or improved utilization of all telecommunications services as described in Sections C.2.2 through C.2.4 and in Section C.2.7.4. Such support activities include, but are not limited to, management, maintenance, design, and engineering services which are provided by the contractor as a part of or adjunct to commercial telecommunications services in support of unique customer requirements. Each request will be negotiated on a case by case basis.

C.2.1.1.1.2 Additional Offerings (Optional)

Additional offerings,4 that is, any optional telecommunications services, features, and functions that fall within the scope as defined in Section C.1.3, may be proposed at any time. In particular the contractor is encouraged to propose any additional offerings at any time over the life of the contract, as described in Sections C.2.1.1.5 and H.15.

Additional offerings comprise non-mandatory items as follows:

(a) Specific optional features and interfaces associated with mandatory telecommunications services, as defined in Sections C.2.2 through C.2.4 and Section C.2.7.4

(b) Additional services. The Government particularly wishes to encourage offerors to propose additional services that are provided commercially. Such services include (as specified in Sections C.2.5 through C.2.7 except Section C.2.7.4):

(1) Cellular Voice Service (CVS)

(2) Wireless Digital Packet Data Service (WDPDS)

(3) One-Way Paging Service (OPS)

(4) Mobile Satellite Service (MSS)

(5) Fixed Satellite Service (FSS)

4 Capability exceeding requirements that are provided as part of the basic service at no additional cost are not considered additional offerings.

C-9


(6) Electronic Mail (E-Mail) (X.400 and Simple Mail Transfer Protocol [SMTP]-based)

(7) Electronic Commerce Service (ECS)

(8) Extensions to VTS as specified in Section C.2.7.4 to bring the service “to the eyeball”

(c) Local Services as defined in the MAA program acquisitions (e.g., local transport and interexchange carrier access)5

(d) Emerging Services (ES), including but not limited to those listed in Section C.2.8

(e) Other enhancements which reduce the Government’s risk, meet new or changed Government needs, improve performance, or otherwise present a service advantage to the Government (see Section H.15)

Any local service, feature, function or equipment proposed under (c) above shall conform to all requirements defined under the MAA program for that particular service, feature, function or equipment, except for those requirements relating to geographic coverage.

C.2.1.1.2 Security Services

Telecommunications services under this contract will carry nonsensitive programmatic and administrative traffic, Unclassified But Sensitive (UBS) traffic, and higher levels of sensitive and/or classified traffic that has been encrypted by agency users. Therefore, security services are required. Such security services shall include protecting all network services, information, and information processing resources against threats, attacks, or failures of systems. After award, the contractor shall update the security plan that was submitted with its proposal, and perform the risk analysis described in the plan. The security plan and risk analyses shall address all aspects of security, including but not necessarily limited to those described in Section C.2.1.12. The risk analyses shall identify all risks, including identification of critical risks. The risk analyses shall include identification of measures to ameliorate risks. The risk analysis results must be approved by the Government. The security plan and related risk analyses shall ensure compliance with requirements outlined in this section, Section C.2.1.12 Security of Contractor Infrastructure, and any additional requirements of the Office of Management and Budget (OMB) Circular A-130.

5 Note that “access” as used in this FTS2001 RFP means access for FTS2001 users to FTS2001 long distance services. It is not a local service under the definition given in Section C.1.3, although it is also included in the mandatory requirements for the MAA program acquisitions.

C-10


In order to support the Government security needs, the contractor shall provide the following security-related service features and functionalities:

(a) Basic security of contractor infrastructure (see Section C.2.1.12)

(b) Fee-based security services

(1) Protection of airwave propagation or wireline assurance. When a user requests wireline assurance, the contractor shall ensure that all communications links shall be either wireline links (i.e., copper or fiber optic) or encrypted radiowave links.

(2) Other security features, as required by the user. The cost of these features shall be negotiated on an individual case basis.

C.2.1.1.3 Management and Operations Services

The contractor shall support a multitiered (i.e., contractor, GSA oversight, and agency) management approach and a centralized contractual and system/operations management capability. This capability shall enable the Government to effectively manage and control its telecommunications resources and reduce network management costs by specializing, consolidating skills, simplifying processes, integrating functions, using increased automation, and utilizing network management standards. This capability shall also enable agencies to manage the operation of their service environment effectively.

In order to facilitate integration of network management information produced by all FTS Program contractors, the contractor shall provide data as defined in Section C.3. The overall objective shall be to provide near real-time telecommunications management information efficiently and cost-effectively, Government-wide and agency-specific.

The contractor shall be fully responsible for the management of its services and network resources. The domain of contractor management of telecommunications services is defined at a minimum by the SDPs, which delineate the end points of the delivered service. The contractor shall provide the Government the capability to oversee the delivery of all services, and to monitor the status and performance of services between all SDPs, including all aspects of contractor compliance. The contractor shall also provide the Government the capability to provide directions to the contractor with regard to service priority, planned and unplanned reconfigurations, and other changes as required by natural disasters or emergencies. Management services shall also be made available to individual agencies to enable them to obtain timely operational and administrative data, to monitor services that originate from their SDPs, and as applicable to control services and features. Finally, the

C-11


contractor shall deliver service in the most cost effective and resource efficient fashion possible, and shall identify to the Government redundancies, under-utilized circuits, and other network management issues.

The detailed specifications of these management services are described in Section C.3.

C.2.1.1.4 National Security and Emergency Preparedness

A National Emergency is any Federally-declared circumstance/crisis (local, national, or international) that causes, or could cause, injury or harm to the population, or damage to or loss of property, or that degrades or threatens the NS/EP posture of the U.S. under conditions of natural and man-made disasters and emergencies. Within the context of telecommuni-cations services, Emergency Preparedness is the maintenance of a telecommunications capability that is in a state of readiness to meet the needs of authorized Government users as permitted by law (e.g., Federal, state, local, and tribal) during National Emergencies. Therefore, the contractor’s network is also required to be maintained in a state of readiness for any emergencies. The detailed specifications of NS/EP requirements are described in Section C.5.

C.2.1.1.5 Intention to Add to Services

The Government desires and intends that additional offerings, as stated in Section C.2.1.1.1.2, will be made as the Government’s requirements evolve and as new or improved services become commercially available. These additional offerings may be to reduce the Government’s risk, to save money, to meet new or changed Government needs, to improve performance and reliability, or for any other purpose which presents an advantage to the Government.

C-12


C.2.1.2 Features

Basic services, as specified in the “Basic Service Description” for each of the telecommunications services described in C.2.2 through C.2.4 and in Section C.2.7.4, are those services that are included in the base price and that cannot be unbundled (see Section B.1.2). Features are additional capabilities that are priced separately. Note that some features are mandatory, which means that they must be offered. Optional and additional features will be evaluated as described in Section M.6 and those that are accepted by the Government will be included in the contract.

After award and throughout the term of the contract, the contractor shall provide updates to the Program Management Office (PMO) for Tables C.2.1.2-1 through C.2.1.2-4 and for Table C.2.1.2-6 as soon as modifications are made to a table as a consequence of changes in the availability of features or in the identity of countries/locations listed in Table C.2.1.2-6 or when new features for new or existing services are added to the contract. Refer to Section C.3.2.7 for the media of delivery and Section F for other deliverable requirements.

Table C.2.1.2-1 indicates which features are unavailable by Numbering Plan Area/Exchange Area (NPA/NXX). The contractor shall complete the right-most column of Table C.2.1.2-1 after contract award and continually update the availability dates for features as a function of NPA/NXX. (All other columns of this table are to be provided in the proposal, as described in Section L.38).

Table C.2.1.2-1. Domestic Access Feature Unavailability Table

Service Type*

Unavailability By NPA/NXX

FeatureName

Section C Reference

Availability Date

* For service types, see Table C.2.1.2-5.

C-13


Table C.2.1.2-2 indicates which feature are unavailable by POP route. The contractor shall complete the right-most column after contract award and continually update the availability dates for features as a function of POP routes. (All other columns of this table are to be provided in the proposal, as described in Section L.38).

Table C.2.1.2-2. Domestic Transport Feature Unavailability Table

Service Type*

FeatureName

Section C Reference

Unavailability By POP Route

Availability Date

From POP ID**

To POP ID**

* For service types, see Table C.2.1.2-5.** The contractor shall use the same POP Identifications (IDs) that are used for the tables in Section B.

Table C.2.1.2-3 indicates which non-domestic access features are unavailable by country/jurisdiction. The contractor shall complete the right-most column after contract award and update the availability dates as these change for features as a function of country/jurisdiction. A feature is considered unavailable in a country/jurisdiction if the feature is not offered at any location within the country/jurisdiction. (All other columns of this table are to be provided in the proposal, as described in Section L.38).

Table C.2.1.2-3. Non-Domestic Access Feature Unavailability Table

Service Type*

FeatureName

Section C Reference

Unavailability By Country/Jurisdiction

Availability Date

* For service types, see Table C.2.1.2-5.

C-14


Table C.2.1.2-4 indicates which features are unavailable by country/jurisdiction route. The contractor shall complete the right-most column after contract award and update the availability dates as these change for features as a function of country/jurisdiction route. (All other columns of this table are to be provided in the proposal as described in Section L.38). After contract award, the contractor shall also update Table C.2.1.2-6 whenever any changes are made to the identities of countries and locations listed therein. As a consequence of such changes, the contractor shall also update Tables C.2.1.2-3 and C.2.1.2-4.

Table C.2.1.2-4. Non-Domestic Transport Feature Unavailability Table

Service Type*

FeatureName

Section C Reference

Unavailability By Country/Jurisdiction Route**

Availability Date

From Country/Jurisdiction

To Country/Jurisdiction

* For service types, see Table C.2.1.2-5.** Country/Jurisdictions are found in Table C.2.1.2-6.

C-15


Table C.2.1.2-5. Service Types

Service Category Service Sub-

Category

Service Type Service Type ID No.

Circuit-Switched Service Narrowband Switched Voice Service 0162Toll Free Service 0134900 Service 0136Circuit Switched Data Service - DS0 0137Circuit Switched Data Service - DS0x2 0138Circuit Switched Data Service - DS0x6 0142Circuit Switched Data Service - DS0x12 0148Circuit Switched Data Service - PRI/DS1 0160

Switched Data Services Network Layer Data Services

Packet Switched Service 0230

Internet Protocol Internetworking Service 0227Link Layer Data Services

Frame Relay Service 0213

Asynchronous Transfer Mode Service 0216Dedicated Transmission Service

Narrowband 4 kilohertz (kHz) Analog Bandwidth 0169

Subrate DS0 - 4.8 kilobit per second [kb/s] 0183Subrate DS0 - 9.6 kilobit per second [kb/s] 0184DS0 0170Fractional T1 - DS0x2 0171Fractional T1 - DS0x4 0173Fractional T1 - DS0x6 0175Fractional T1 - DS0x8 0177Fractional T1 - DS0x12 0181T1 0187E1 2233

Wideband Fractional T3 - DS1x3 0195Fractional T3 - DS1x4 0196Fractional T3 - DS1x5 0197Fractional T3 - DS1x7 0198T3 0201

Value Added Service Application Level Service

Video Teleconferencing Service 0205

C-16


Table C.2.1.2-6. Country/Jurisdiction Identifications

Country/Jurisdiction Country/JurisdictionAFGHANISTAN BURUNDIALBANIA CAMBODIAALGERIA CAMEROONAMERICAN SAMOA CANADAANDORRA CAPE VERDE ISLANDSANGOLA CAYMAN ISLANDSANGUILLA CENTRAL AFRICAN REPUBLICANTARCTICA (Casey and Scott Bases) CHADANTIGUA (Includes BARBUDA) CHILEARGENTINA CHINA (MAINLAND)ARMENIA CHRISTMAS ISLAND ARUBA COCOS ISLANDSASCENSION ISLAND COLOMBIAINMARSAT ATLANTIC OCEAN REGION-EAST COMOROSINMARSAT ATLANTIC OCEAN REGION-WEST CONGO (Democratic Republic of the)AUSTRALIA CONGO (Republic of the)AUSTRIA COOK ISLANDSAZERBAIJAN COSTA RICABAHAMAS CROATIABAHRAIN CUBABANGLADESH CYPRUSBARBADOS CZECH REPUBLICBELARUS DENMARKBELGIUM DIEGO GARCIABELIZE DJIBOUTIBENIN DOMINICABERMUDA DOMINICAN REPUBLICBHUTAN EASTER ISLANDBOLIVIA ECUADORBOSNIA - HERZEGOVINA EGYPTBOTSWANA EL SALVADORBRAZIL EQUATORIAL GUINEABRITISH VIRGIN ISLANDS (Includes Anegada, Camanoe Islands, Guana Islands, Jost Van Dyke, Little Thatch, Marina Cay, Mosquito Islands, North Sound, Peter Islands, Salt Islands, Tortola, and Virgin Gorda)

ERITREA

BRUNEI ESTONIABULGARIA ETHIOPIABURKINA FASO FAEROE ISLANDSBURMA FALKLAND ISLANDS

C-17


Table C.2.1.2-6. Country/Jurisdiction Identifications (Continued)

Country/Jurisdiction Country/JurisdictionFIJI ISLANDS KENYAFINLAND KIRIBATIFRANCE KOREA (NORTH)FRENCH ANTILLES (Includes Martinique, Saint Barthelemy, and Saint Martin)

KOREA (SOUTH)

FRENCH GUIANA KUWAITFRENCH POLYNESIA (Includes Islands of Moorea and Tahiti)

KYRGYZSTAN

GABON LAOSGAMBIA LATVIAGEORGIA LEBANONGERMANY LESOTHOGHANA LIBERIAGIBRALTAR LIBYAGREECE LIECHTENSTEINGREENLAND LITHUANIAGRENADA (Includes CARRIACOU) LUXEMBOURGGUADELOUPE MACAOGUANTANAMO BAY (U.S. Naval Base) MACEDONIAGUATEMALA MADAGASCARGUINEA - BISSAU MALAWIGUINEA MALAYSIAGUYANA MALDIVESHAITI MALIHONDURAS MALTAHONG KONG MARSHALL ISLANDSHUNGARY MAURITANIAICELAND MAURITIUSINMARSAT INDIAN OCEAN REGION MAYOTTE ISLAND INDIA MEXICOINDONESIA MICRONESIAIRAN MIDWAY ISLANDIRAQ MOLDOVAIRELAND MONACOISRAEL MONGOLIAITALY (Includes VATICAN CITY) MONTSERRATIVORY COAST MOROCCOJAMAICA MOZAMBIQUEJAPAN (Includes OKINAWA) NAMIBIAJORDAN NAURUKAZAKHSTAN NEPAL

C-18


Table C.2.1.2-6. Country/Jurisdiction Identifications (Continued)

Country/Jurisdiction Country/JurisdictionNEPAL SAO TOMENETHERLANDS SAUDI ARABIANETHERLANDS ANTILLES (Includes Bonaire, Curacao, Saba, Saint Eustatius, and Saint Maarten)

SENEGAL

NEVIS SERBIA and MONTENEGRONEW CALEDONIA SEYCHELLES ISLANDSNEW ZEALAND (Includes Chatham Island) SIERRA LEONENICARAGUA SINGAPORENIGER SLOVAKIANIGERIA SLOVENIANIUE SOLOMON ISLANDSNORFOLK ISLAND SOMALIANORWAY (Includes SVALBARD ) SOUTH AFRICAOMAN SPAIN (Includes Balearic Islands, Canary Islands,

Ceuta, and Melilla)INMARSAT PACIFIC OCEAN REGION SRI LANKAPAKISTAN SUDANPALAU SURINAMEPANAMA SWAZILANDPAPUA NEW GUINEA (Includes Admiralty Islands, Bougainville, New Britain, and New Ireland)

SWEDEN

PARAGUAY SWITZERLANDPERU SYRIAPHILIPPINES TAIWANPITCAIRN ISLAND TAJIKISTANPOLAND TANZANIAPORTUGAL (Includes Azores and Madeira Islands) THAILANDQATAR TOGOREUNION ISLAND TONGA ISLANDSROMANIA TRINIDAD and TABAGORUSSIA TUNISIARWANDA TURKEYST. HELENA TURKMENISTANST. KITTS TURKS and CAICOS ISLANDSST. LUCIA TUVALUST. PIERRE and MIQUELON UGANDAST. VINCENT and THE GRENADINES UKRAINESAN MARINO UNITED ARAB EMIRATES (Includes Abu Dhabi,

Ajman, Dubai, Fujairah, Ras al Khaimah, Sharjah, and Umm al Qaiwain)

C-19


Table C.2.1.2-6. Country/Jurisdiction Identifications (Concluded)

Country/Jurisdiction Country/JurisdictionUNITED KINGDOM (Includes the Channel Islands, England, Isle of Man, Northern Ireland, Scotland, and Wales)

WALLIS AND FUTUNA ISLANDS

URUGUAY WESTERN SAHARAUZBEKISTAN WESTERN SAMOAVANUATU YEMEN (Includes Aden and Almahrah)VENEZUELAVIETNAM ZAMBIAWAKE ISLAND ZIMBABWE

C.2.1.3 Service Coverage

The contractor shall provide services and features for both domestic and non-domestic locations. Domestic locations are those within the U.S., Puerto Rico, the U.S. Virgin Islands, Guam, and the Northern Marianas. All other locations are defined as non-domestic for the purposes of this contract.

The Government wishes the geographic coverage to be as broad as possible for all services. The Government’s minimum requirements for coverage are described in Section J.8.3.

C.2.1.4 On-Net and Off-Net Locations

The contractor shall provide services to on-net and off-net locations, which are defined as follows:

(a) On-net locations are locations that have presubscribed to one or more services provided by the FTS2001 contractor. However, an on-net location must subscribe to a specific FTS2001 service before receiving that service at that location. Service to on-net locations may be implemented using either dedicated, circuit switched, or optional internetworked access.

(b) Off-net locations do not subscribe to any services provided by the FTS2001 contractor. Service to and from off-net locations is required only if specified in the individual service description.

C.2.1.5 Service Delivery Point and Network Interfaces

The Government’s requirements, as stated within this solicitation, include services and features between SDPs. An SDP is the interface point at which a service is delivered by the

C-20


contractor to the user. Thus it is the point at which responsibility for the service transfers from the service provider to the Government. The SDP is the interface point for the physical delivery of a service, one of the points at which performance parameters are measured to determine compliance with the contract, and the point used by the contractor to identify charges for services rendered. Each SDP has an associated interface. The SDP defines where service is delivered and the interface defines what and how service is delivered. There are two types of interface associated with SDPs:

(a) User-to-network interface (UNI), which is used where the contractor provides access

(b) Local access-to-network interface (LANI), which is used where the Government provides access. In this case, the SDP shall be at the standard carrier demarcation point at the contractor’s POP.

The SDP and its associated UNI or LANI define the physical and service interface between the contractor provided facilities and the Government provided facilities.

One and only one interface (UNI or LANI) is associated with each SDP. However, where integrated access is used with a Government-provided Access Adaptation Function (AAF) (e.g., multiplexing), there may be more than one service (e.g., SVS and CSDS) at the SDP. None, one, or many features may be subscribed for a given SDP.

C.2.1.5.1 Service Delivery Point Location

The contractor is responsible for delivering service to the SDP. The physical location of SDPs will be determined by the Government on an order by order basis. Unless otherwise specified by an authorized user, the location of the SDP will be at the network side of the user provided equipment or service.

SDPs may be located on or off Government premises. Possible SDP locations include but are not limited to:

(a) Network side of a Private Branch Exchange (PBX), Centrex system, or other communications system or network.

(b) User side of contractor-provided access facilities (e.g., gateway router).

(c) Standard carrier/user demarcation point.

(d) Minimum Point of Penetration (MPOP).

C-21


(e) Desktop (e.g., telephone set, personal computer [PC]).

(f) Contractor’s POP, when access6 (whether dedicated or switched) service and transport7 service are required to be provided unbundled (see Section C.2.1.16).

The detailed interface specifications of SDPs are described in each service description.

C.2.1.5.2 On Premises Wiring

The SDP location may be at the standard commercial demarcation on premises or may be elsewhere inside the premises. Depending on the location, on premises wiring may be required within a building, and/or between buildings in a campus or military base environment to reach the SDP.

If existing wiring is to be used, the contractor shall verify that all such wiring meets the technical standards for the services being provided (e.g., U.S. cabling and safety standards and guidelines as published by American National Standards Institute (ANSI) Electronic Industries Association/Telecommunications Industries Association (EIA/TIA) 568/569/606/TSB-36/TSB-40, ANSI/National Fire Protection Association (NFPA)-70, and EIA-T568A). However, for non-domestic locations, the contractor shall follow country-specific applicable wiring/cabling standards and guidelines.

If the existing or installed inside wiring does not meet technical standard, the contractor shall identify the standard to the user at no additional cost to the Government.

When provided with appropriate authority by the ordering agency, the contractor shall order inside wiring from the Government’s designated contractor. In addition, the contractor shall also coordinate installation, trouble reporting, and trouble rectification of inside wiring with the entity selected by the user for inside wiring.

When requested by the user, the contractor shall provide inside wiring which shall be negotiated on an individual case basis.

The contractor shall be responsible for isolating and identifying to the user any service problem caused during or after acceptance of the service by the existing or installed inside wiring so that user can rectify the inside wiring problem. However, the contractor will not be responsible for rectification of the problem associated with the existing inside wiring.

6 Connection from SDP to POP.7 Connection from POP to POP.

C-22


C.2.1.6 Numbering and Addressing Plan

The Government in the future wants to move toward a numbering and addressing plan for on-net stations receiving switched services that is uniform across all FTS program networks for all switched services and follows the International Telecommunications Union/Telecommunications Service Sector (ITU-TSS) Integrated Services Digital Network (ISDN) E.164 uniform numbering and addressing plan. However, a service-specific numbering and addressing plan has been specified in each specific switched service description, such as ITU-TSS X.121 for packet-switched service for on-net users located in North America. The contractor shall support each of the specified numbering plans. When E.164 is commercially available for a given service, then the Government reserves the right to select either the ITU-TSS ISDN E.164 uniform numbering and addressing plan for that switched service or the service-specific numbering and addressing plan supported for that service at the time of contract award.

The selection, at the time of contract award, of either the ITU-TSS ISDN E.164 or the service-specific numbering and addressing plan shall be at no additional cost to the Government.

If the ITU-TSS ISDN E.164 uniform numbering and addressing plan for all switched services is proposed, the contractor shall be responsible for keeping track of each on-net station’s capabilities (i.e., Class-of-Service [COS] markings) to receive and transmit multiple switched services as these are ordered and changed by the station’s users.

The contractor shall be responsible for the numbering plan associated with its network, as well as providing its numbering plan information to the Number Administrator to ensure that the same number is not assigned to different users in different FTS2001 program contractors’ networks (see Section C.3.2.7.4).

C.2.1.7 Conformity to Standards

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 existed at the time of issuing this RFP. If a standard is defined in the RFP by a specific version and/or date, then that specific version of the standard shall be implemented. Otherwise, compliance with the latest versions of these standards is expected. American national standards shall supersede international standards for services to be provided to on-net users located in the U.S. Where multiple standards are cited, the order of precedence shall be industry forum specification (e.g., ATM Forum [ATMF]), followed by ANSI, followed by Bellcore, followed by ITU-TSS, unless otherwise specified.

C-23


C.2.1.8 Performance

The contractor shall be responsible for all aspects of service quality, security, intercon-nectivity, and interoperability of services between SDPs. The applicable performance parameters for each service and feature are specified in each service description. These parameters shall apply to all domestic service. Performance parameters for non-domestic service shall be as specified in Section C.2.1.13. Each performance parameter is defined in terms of the minimum acceptable level of performance for the service or feature. In addition, the performance provided shall always be at a level not less than what is available commercially. Thus, if the available commercial performance parameter is more demanding than the minimum acceptable level specified in the contract, the available commercial performance parameter shall prevail. See Section C.6 for measurement and calculations of specific performance parameters and monthly data reporting requirements.

The contractor shall be responsible for delivering all services at the required performance levels as specified in this solicitation. In case a given service is disrupted at an SDP, the contractor shall, in at least 98 percent of the cases, restore the service within four hours of the notification of such disruptions. In addition, the contractor shall meet the specified performance regardless of traffic congestion in the contractor’s commercial or other private networks.

C.2.1.9 Compatibility

In addition to the other requirements stated in this solicitation, the contractor shall ensure that its network is interoperable with any Government equipment connected to the Federal Telecommunications System 2000 (FTS2000) network at the time of contract award, or ordered prior to contract award, which is intended to be transitioned to the contractor’s network. Any interoperability problems resulting from the transition of FTS2000 Government equipment to the FTS2001 contractor’s SDPs or interoperability problems resulting after transition shall be resolved by the contractor, who shall provide the necessary technical support, development, operations, procedures, software, and equipment to resolve the problems with its network at no additional cost to the Government. However, the Government will be responsible for costs associated with equipping or modifying its switches to accomplish call routing to the contractor’s network. In addition, the contractor shall also continue to use the existing FTS2000 SVS numbers (including toll free (800) numbers) assigned to on-net stations when these stations are transitioned from FTS2000 network to the contractor’s network.

The contractor shall not be responsible for achieving compatibility with its network for any non-compatible Government equipment ordered for connection to the FTS2000 network after the award of the FTS2001 contract. However, the contractor shall be responsible for

C-24


providing whatever assistance is necessary to help determine compatibility requirements with the users and vendors of equipment that is to be connected to the contractor’s network and/or services regardless of when the equipment is purchased.

C.2.1.10 Originating Station Identification

The Government requires Call Detail Records (CDRs) by originating station for station-specific billing and authorized call verification purposes. The contractor shall provide the Government with station identified CDR information. CDR information shall include, at a minimum, the provisions specified in Section C.3.6.1, C.3.6.3.1, and C.3.6.5.6.4. Station identification may also be used within the contractor’s network for call screening purposes. The contractor shall submit Station Identified Call Detail record information - Centralized Billing to the PMO on a monthly basis or when requested. The contractor shall also submit Station Identified Call Detail record information - Direct Billing to the agencies or sub-agencies monthly or as requested. Refer to Section C.3.2.7 for the media of delivery and Section F for other deliverable requirements.

Switched voice station identification may be provided by Automatic Identification of Outward Dialing (AIOD), Automatic Number Identification (ANI) (including Feature Group D type ANI), authorization code, or the North American implementation of ITU-TSS No. 7 (i.e., Signaling System Number 7 [SS7]). The associated standards are EIA RS-464/464-1 for AIOD, Bellcore SR-TSV-002275 for ANI, Bellcore GR-246-CORE for SS7, and ITU-TSS Q.931 for ISDN Basic Rate Interface/Primary Rate Interface (BRI/PRI). If voice station identification is available at an SDP and conforms to any of the above mentioned standards, the contractor shall be able to accept the originating station identification for CDRs purposes. As used in this contract, the term ANI includes all above-mentioned methods of voice station identification.

C-25


The contractor shall provide a network capability to trace/identify the on-net/off-net originating station and/or trunk group number by date, time and duration of calls placed through the contractor’s network to a previously identified station. Suppression of calling number delivery shall be provided as specified in Section C.2.2.1.2.2.1(g). The contractor shall coordinate with law enforcement officials having appropriate authorization for obtaining call trace information and provide them with required information.

C.2.1.11 Interoperability

The contractor shall support interoperability for a given service offering so that a user of that service from one FTS2001 contractor shall be able to communicate with another user of that service from a different FTS2001 contractor with performance equivalent to that commercially available. The Government recognizes that different levels of interoperability (i.e., partial or full) exist commercially. Interoperability shall be made available for any service that is currently commercially offered by the contractor and is interoperable with another FTS2001 contractor’s network. The contractor shall notify the Government of the details of the level of interoperability available for the service. In addition, the contractor shall make available any future FTS2001 service interoperability at no additional cost to the Government when the contractor offers commercially the interoperability for its regularly provided service, whether provided by tariff or contract.

The contractor shall provide interoperability of its SVS, Toll Free Service, and 900 Service with the Public Switched Telephone Network (PSTN). The contractor shall also provide interoperability of its IPS with the Internet and with Federal Government Internet Protocol (IP) networks at established Federal Internet Exchange (FIX) points, or their replacements. As a minimum, the contractor shall provide connectivity with the following Network Access Points (NAPs):

(a) Chicago NAP (Ameritech)(b) New York NAP (Sprint)(c) San Francisco NAP (Pacific Bell)(d) Washington, DC NAP (Also known as MAE East, MFS)(e) MAE West (MFS)

After contract award the contractor shall coordinate with the Federal Networking Council for interconnection standards. If a user wants interoperability for any other FTS2001 service(s), the contractor shall provide such interoperability on an individual case basis.

C-26


In addition, the contractor shall also support interconnection with other Government networks/acquisitions (e.g., city specific MAA) at the contractor’s POP. The interconnection interface shall be the LANI as specified in the individual service description. The interfacing Government networks/acquisitions will be responsible for implementing the LANI for any gateway function required including address translations required to make the Government network’s/acquisition’s addressing and/or numbering plan compatible with the FTS2001 addressing and/or numbering plan. In addition, the FTS2001 contractor shall support and work cooperatively with other Government networks/acquisitions and shall be responsible for all testing, maintenance, outage time, and trouble repair associated with its LANI.

C.2.1.12 Security of Contractor Infrastructure

The contractor shall provide basic security-related service, which represents the security within the infrastructure of the contractor’s network in accordance with the contractor’s standard commercially available security services. This support is not considered a fee-for-service type of security offering. Basic security-related service support under the FTS2001 Program is directed at ensuring availability of service, confidentiality, and data integrity of both the contractor’s transmission systems and databases being maintained by the contractor in support of its services. The contractor’s infrastructure shall support best commercial practices against threats from hacker, criminal, and terrorist activities.

Instructions to offerors relating to this Section are provided in Section L.38.1.3.3.

C.2.1.12.1 Security Plan (OMB Circular A-130)

The contractor shall update its security plan that was provided with its proposal and submit it to the Government for approval at least annually or more frequently at the request of the Government. Refer to Section C.3.2.7 for the media of delivery and to Section F for other deliverable requirements.

C.2.1.12.2 Denial of Service

The contractor shall protect against threats that deny service and thus reduce availability of the contracted service by providing mechanisms to protect the transmission facilities, switching components, network management systems and other essential service provider facilities from unauthorized denial-of-service attacks, insider attacks, unauthorized or unexpected user actions, unauthorized intrusions, and other perceived threats.

C-27


The Government will have the right to make random spot checks, both from SDPs on the contractor’s network and from within the contractor’s network, to assess the protection against denial of service.

C.2.1.12.3 Confidentiality

Following best commercial practices for the transmission media utilized, the contractor shall protect Government information from disclosure to unauthorized persons.

The contractor shall provide confidentiality protection for sensitive information maintained in the network such as subscriber profiles, billing data, network performance statistics, and network vulnerabilities.

For some FTS2001 services, subscribers may use Government equipment for encryption of user information only. The contractor’s infrastructure shall support the transmission of all encrypted information that is generated by the Government equipment in a transparent manner when such equipment meets the service specific UNI requirements.

C.2.1.12.4 Data Integrity

The contractor shall protect the Government information during transmission from unauthorized modification.

C.2.1.12.5 Identification and Authentication

The contractor shall provide mechanisms to identify and authenticate contractor personnel and Government personnel who are authorized to access network management information or place orders.

C.2.1.12.6 Access Control

The contractor shall provide access controls to protect the network management systems and switching systems from attacks via publicly accessible ports on “end” devices such as PBXs, routers, and packet switches or from ports on end devices that may be accessed via the Public Switched Network (PSN) (e.g., maintenance ports).

The contractor shall provide access controls to ensure that only authorized contractor personnel and Government personnel have access to network management information.

C-28


C.2.1.12.7 Alarms and Audit Trails

The contractor shall identify and report all security violations and breaches within four (4) hours. The contractor shall be responsible for resolving all security violation and breaches. The contractor shall report all security breaches, related to the contractor’s network, as provided in this contract, to the affected agency and to the PMO. The contractor shall work closely with agencies to resolve all security violations, and shall cooperate with the Government in any criminal investigations resulting from a security breach related to the contractor’s network.

The contractor shall provide audit and alarm mechanisms that log all security-related events and report service affecting (Section C.3.7.1) events to the PMO and affected agency (or site as designated by the agency) immediately. The contractor shall maintain these logs and reports as audit trails for one year; however, the PMO may request that audit trails be maintained longer (for a maximum of three years) or turned over to the PMO via electronic medium, at no additional cost to the Government.

The contractor shall provide and maintain real-time operational procedures and capability for detecting and monitoring suspected abuse or intrusions to the network and set off alarms for those events that require immediate attention by PMO, affected agency or site, and/or contractor staff. These procedures shall be provided within 60 calendar days after contract award with updates as requested by the Government.

Refer to Section C.3.2.7 for the media of delivery and Section F for other deliverable requirements.

C.2.1.12.8 Assurance

The contractor shall provide protection for the databases and information processing systems that are critical for the continuous, reliable operation of its network. The contractor shall provide protection against unauthorized access by external communications means, whether from authorized or unauthorized devices such as terminals.

Security Evaluation Class (C2) of the Department of Defense (DOD), Trusted Computer System Evaluation Criteria, (DOD 5200.28-STD) “Orange Book” shall be used as a guideline for providing protection for the contractor’s computer systems, particularly with regard to sensitive computer systems. Sensitive computer systems shall include but are not limited to the billing system, audit trail repositories, network management information databases, network management monitoring and control systems, audio and video teleconference reservation systems, repositories of users’ identification and authorization information, and CDRs. Where these security functions and controls cannot be satisfied,

C-29


access to these systems will be restricted to small populations of authorized users and protected against unauthorized access. When these security functions and controls are not available for sensitive computer systems, the contractor shall provide to the Government an updated plan and schedule, within 30 calendar days after contract award, to implement these security functions and controls for all sensitive computer systems. The Government will provide a review of the updated security plan within 30 calendar days of its receipt and the contractor shall submit a revised plan within 30 calendar days after receiving the review from the Government. The Government intends to approve a final plan within 30 calendar days after receiving the revised plan. Upon approval by the Government, the contractor shall implement the plan. The Government has the option to refuse service until the plan is implemented.


C.2.1.12.9 Personnel Security

Contractor, including subcontractor, employees to be assigned to agency sites on a regular basis will be, at the Government’s discretion, required prior to their assignment to pass a national agency check. At the Government’s discretion higher clearances and access authorization will be required for access to certain Government facilities or information. The contractor shall initiate requests for background investigations of personnel requiring national agency checks.

Performance under the contract(s) may require the contractor to have access to information classified “Top Secret.” Therefore, upon award, the successful offeror shall obtain the appropriate personnel and facility clearances to have access to such information. The Contracting Officer will initiate and coordinate the clearance request. If the contractor is not granted Top Secret clearance within a reasonable period of time, the Government may terminate the contract.

Information about obtaining the Top Secret and other security clearances may be obtained from the following organization:

Defense Investigative Service Clearance OfficeP.O. Box 2499Columbus, OH 43216-5006(614) 692-3176

C.2.1.12.10 Physical Security

C-30


The contractor shall protect its facilities from entry by unauthorized persons.

C.2.1.12.11 Procedural Security

The contractor shall establish, and provide to the Government security procedures, including:

(a) Procedures for controlling access to Government-related sensitive databases and information

(b) Procedures to prevent fraudulent use of Government information or services

(c) Procedures to prevent fraudulent use of FTS2001 Calling Cards

These procedures shall be provided within 60 days after contract award. Refer to Section C.3.2.7 for the media of delivery and Section F for other deliverable requirements.

C.2.1.12.12 Ongoing Security Improvements

The contractor shall incorporate, following Government approval, new security-related standards for telecommunications transmission and switching technologies as they mature and become accepted practice in the commercial environment. For those instances where this occurs, the contractor shall submit as part of its security plan a procedure for incorporating these standards into their operations as they become accepted commercially. If these security-related standards are implemented at no additional cost to any commercial customers then the Government shall receive the same treatment. Additionally, the security plan shall also indicate how improved security-related processes are to be included either as part of the basic security-related service support, or as a new fee-for-service offering to be made available to the Government under this contract as they become commercially available.

The contractor shall work with the Government on an ongoing basis to certify and enhance the strength of security. The security plan shall describe planned enhancements to security of the network and shall be updated annually as a minimum after contract award. Post award activities shall include:

(a) Providing the Government with summaries of security related events as described in Section C.6.

C-31


(b) Working with the Government to reassess the severity of new or perceived threats and to take countermeasures to assure the specified network availability in accordance with the security plan.

(c) Preparation of security practices and briefings for GSA and agency representatives and, upon request, conducting the briefings.

C.2.1.13 Non-Domestic Services

The contractor shall supply services globally. Global coverage includes delivery of service from domestic SDPs to non-domestic SDPs, from non-domestic SDPs to domestic SDPs, and from non-domestic SDPs to non-domestic SDPs. The following requirements for numbering plan, features, performance, interfaces, security, and management and operations considera-tions that are applicable to the non-domestic services shall supersede the corresponding requirements specified for the domestic services:

(a) Numbering Plan. The numbering plan for non-domestic locations shall conform to country specific numbering plans for switched services.

(b) Features. All features identified as mandatory in each service description shall be provided to non-domestic SDPs when they become commercially available in the areas involved.

(c) Dial-In. The contractor shall support country-specific non-domestic PSN numbers and/or toll free numbers, if commercially available, for dial-in access of services.

(d) Performance. The performance parameters for each service between non-domestic SDPs or between domestic and non-domestic SDPs shall be compliant with the best commercial values or practices for those parameters within the foreign country(ies) hosting the foreign SDPs.

(e) Interfaces. When a service is delivered to an SDP at a non-domestic location, the UNI (i.e., interface type, payload data rate, protocol type) standard for the SDP shall comply with the country-specific interface standards when delivering service to the country-specific Government equipment. However, if the Government equipment conforms to a North American standard, then the UNI standard at the SDP shall comply with the North American standard where permitted by local law and regulations.

(f) Security. The contractor shall provide the best commercial security practices in supporting service delivery to non-domestic locations. The contractor shall

C-32


monitor the performance of its foreign subcontractor’s business partners’ and PTT’s services and report to the PMO and the Contracting Officer (CO) any unusual or suspicious outage, blockage, or tampering that may indicate that users of services are being denied service or are being compromised. Additionally, the contractor shall provide, in addition to its required security plan (see Section C.2.1.12), associated mechanisms that shall be implemented to protect their domestic infrastructure from any information warfare activities (e.g., threats from hackers, criminals, and terrorist activities) carried out by a non-domestic subcontractor. Any connectivity to the Internet or a commercial network service provided by the contractor to non-domestic SDPs shall meet the security requirements identified in Section C.2.1.1.2.

(g) Management and Operations. The contractor shall provide the full range of management and operations functions, defined in Section C.3, or the best commercially available.

C.2.1.14 Hardware and Software

Hardware and software, where specified within this contract, shall be provided as an integral part of the services. Any such hardware and software (excluding data) shall remain the property of the contractor, unless otherwise specified or agreed.

C.2.1.15 Transition, Migration, and Implementation

Transition is the process of planning for and transferring services from existing FTS2000 networks to the contractor’s network.

Migration is the process of planning for and transferring services from existing agency networks (i.e., those networks not currently associated with FTS2000 networks) to the contractor’s networks. Migration also includes planning for and transferring services from one FTS2001 contractor’s network to another FTS2001 contractor’s network after transition.

Implementation is the process of planning for and adding new services to user locations provisioned under this contract. Implementation may involve the addition at specific user locations of a service that is comparable to a current FTS2000 service offering but which has not before been provisioned at that particular location. Implementation may involve the

C-33


addition of a completely new service offering at a user location, (i.e., services that have never before been offered by FTS2000 nor by legacy systems at a particular location). Implementation also may involve enhancements, changes, and additions to existing service offerings.

The Government’s goals and objectives for transition, migration, and implementation are:

(a) Provisioning of new services as soon as commercially available at users’ locations

(b) Introduction of new technologies associated with services as soon as they become commercially available

(c) Minimizing disruptions and maintaining the continuity of services to the users

(d) Ensuring cost effective transition, migration and implementation of services

(e) Adopting best commercial practices

The transition, implementation and migration strategies shall satisfy, at a minimum, the above Government goals and objectives. The details of transition, migration and implementation are defined in Section C.4.

C.2.1.16 Access

Access is the means for providing connection for on-net locations between an SDP and the contractor’s POP. Through interoperability with the PSN, access is also the means of connecting off-net locations, which are not SDPs, with FTS2001. Connectivity to off-net locations is accomplished by using off-net circuit-switched access.

Each domestic PSTN location has a wire center associated with it in the Local Exchange Routing Guide (LERG); similarly, each domestic SDP that is also a PSTN location has an associated wire center8. For serviced PSTN locations and SDPs that are associated with the same wire center, the contractor shall provide all services offered by the contractor at those PSTN locations and SDPs from the same POP.

The contractor shall always provide access unless the Government specifically requests that access not be provided by the contractor i.e., unbundling of access service from transport service. For access provisioning, the contractor shall conform to a UNI specification at the SDP or to a LANI specification at the POP as defined in the individual service descriptions

8 Some SDPs may not be PSTN locations. In those cases, the Government will define an associated wire center to be used for FTS2001 purposes.

C-34


(see Sections C.2.2 through C.2.4), except that (a) where the contractor-provisioned access circuit is being used for access service integration and the Government is supplying the multiplexer, the contractor shall conform to a UNI specification at the SDP as defined in Section C.2.4 and (b) where a Government-provided access circuit is being used for access service integration, the contractor shall conform to a LANI specification for termination of such circuit at the POP as defined in Section C.2.4. The contractor shall accept at its listed POPs, connections for originating and terminating access with other access providers, as specified by the Government from time to time, providing that these connections conform to the LANI specifications.

The contractor shall support the following access types:

(a) Dedicated access

(1) Class 1. Where a user agency orders access circuits from either the FTS2001 contractor or another contractor and is responsible for the Grade of Service (GOS). Users are expected but not required to acquire the number of access circuits recommended by the contractor to achieve a P.03 grade of service.

(2) Class 2. Where a user agency orders a service including access from the FTS2001 contractor, but the contractor is responsible for the GOS. Users are responsible for acquiring the number of access circuits as advised/specified by the contractor. Where a user does not acquire the number of circuits specified by the contractor for whatever reason or subscribes to or uses the make-busy arrangement, the dedicated access Class 2 shall revert to Class 1.

(b) Circuit-switched access from the serving local central office. The user is responsible for the local loop from the user equipment to the central office and associated local exchange service.

(c) Internetworked access is optional

For access provisioning of services, a user shall be able to select an access arrangement for a particular service type from the access types as specified in Table C.2.1.16-1, provided that access type is available in the user’s location as specified in Section J.8.3.

The performance provided for the above access types shall always be within the specifications of Section C and at least as good as what is available commercially. In addition, the contractor shall provide all necessary hardware and software for provisioning of the access to the user equipment at the SDP as an integral part of the service. The Government will allow the housing of contractor equipment at Government premises, where

C-35


necessary, to provide the specified UNI and will authorize the use without charge of a reasonable amount of space and power.

In addition, the contractor shall also provide all necessary AAFs for:

(d) Access service integration when channels associated with multiple UNIs of lower bandwidths (e.g., SVS, PSS) are multiplexed into a higher bandwidth access type (e.g., T1).

(e) When a channel associated with a single UNI of lower bandwidth (e.g., 384 kb/s) can only be accessed by a higher bandwidth access type (e.g., T1) at that location.

The contractor shall also provide a cooperative transport demultiplexing function for transport at a POP for access connection when an AAF, whether contractor provided or Government provided, is implemented at a user site.

Access requirements and features are described in the following subsections.

C.2.1.16.1 Access Requirements

For dedicated access types excluding ISDN PRI, the contractor shall conform to the requirements as specified in Section C.2.4.1. For ISDN PRI access types, the contractor shall conform to the requirements as specified in Section C.2.1.16.3.

For circuit-switched access types, excluding ISDN PRI, the contractor shall conform to the requirements as specified in Sections C.2.2.1.1, C.2.2.2.1, C.2.2.3.1, and C.2.2.4.1. For ISDN PRI access types, the contractor shall conform to the requirements as specified in Section C.2.1.16.3.

For optional internetworked access types, the contractor shall conform to the requirements as specified in Section C.2.3.1.1 for PSS, Section C.2.3.2.1 for FRS, Section C.2.3.3.1 for IPS, and Section C.2.3.4.1 for ATMS.

C-36


Table C.2.1.16-1. Access Types

Legend:x Denotes a valid access type that can be selected by the user[x] Denotes an optional access type* Denotes that there are 7 Virtual Tributary (VT) groups in a OC-1 and each VT group

can independently carry either 4 T1s or 3 E1s or 2 DS1Cs or 1 DS2

Notes:1. When a high bandwidth access type (e.g., T1 or T3) is selected for a low bandwidth

service (e.g., SVS or PSS), channelized circuit is assumed.

C-37


C.2.1.16.2 Dedicated Access Features

The contractor shall provide the following access features for connecting an SDP to its associated POP via dedicated access when requested by the Government:

(a) Access Route or Path Diversity

(1) Mandatory

Between an SDP and its associated connecting POP, or at the Government’s option between an SDP and at least two POPs, the contractor shall supply at least two physically-separated routes for access. These diverse routes shall not share any common telecommunications facilities or offices including common building entrance. The contractor shall maintain a minimum separation of 30 feet throughout all diverse routes, except for cable crossovers, between premises/buildings where an SDP and its associated POP are housed. However, for cable crossovers, the contractor shall maintain a minimum vertical separation of two feet, with cables encased (separately) in steel or concrete. The Government recognizes that uncompromised (i.e., adhering to the minimum separation requirements as described above) diversity may not be available in some locations. Where uncompromised diversity is not available, the contractor shall exert best efforts to propose an acceptable arrangement along with documentation describing the compromise. If diversity is not available or the compromised diversity is not acceptable to the Government, an acceptable alternative shall be negotiated on an individual case basis.

When access diversity has been provided by the contractor, the Government may at its discretion, elect to send telecommunications traffic over only one route (i.e., the primary route) thereby keeping the second route (i.e., the diverse route) inactive until needed. The Government may also elect to send telecommunications traffic over both routes on an ongoing basis, except where automatic re-routing equipment is utilized.

(2) Optional

The contractor shall provide the capability for the automatic switching of transmission in real-time from the primary access route to the one or more diverse access routes, including satellite connection, and from the diverse access route to the primary access route. This shall be negotiated on an individual case basis.

C-38


(b) Access Route or Path Avoidance. Between an SDP and its associated connecting POP, the contractor shall supply the capability for a customer to define a geographic location or route to avoid. However, the Government recognizes that avoidance may not be available in some locations. Where avoidance is not available, the contractor shall exert best efforts to propose an acceptable arrangement along with documentation describing the reasons for the unavailability.

The contractor shall provide within 30 calendar days of the implementation of access diversity or avoidance and again thereafter when a change is made, a graphical representation (e.g., diagrams, maps) of access circuit routes to show where diversity or avoidance has been implemented. The contractor shall provide to the agency, with a copy to the PMO, written notification for Government approval of any proposed reconfiguration of routes, previously configured for access diversity or avoidance at least 30 calendar days in advance of implementation. The contractor shall conform to the requirements for performance for each diverse or avoidance route as specified in Section C.2.4.2.2.1(c)(1) and C.2.4.2.2.1 (c)(2). Refer to Section C.3.2.7 for the media of delivery and Section F for other deliverable requirements.

In addition, the contractor shall establish internal control (i.e., electronic flagging of routes) to prevent the accidental dismantling of diversified/avoidance routes, especially during routine route optimization initiatives by the contractor.

C.2.1.16.3 Integrated Services Digital Network Access Requirements

ISDN Access shall support both circuit-mode and packet-mode of data transmission to provision voice and data, access through a single UNI.

The ISDN access shall follow the North American adaptations of the ANSI T1 standards and ITU-TSS G, H, I, Q, X, and V series recommendations for the provision of ISDN, including common channel Signaling System Number 7 (SS7) for interexchange signaling. In particular, the ISDN access arrangement shall conform to ANSI T1.620/607/606/610/614/608/602/609/612/626 and ITU I.300/610.

The ISDN PRI shall comprise twenty-three 64 kb/s B channels and one 64 kb/s D channel (23B+D). Where more than one PRI is provisioned at one SDP, it shall be possible to arrange for them to share one D channel whenever this is commercially available from the contractor, thus freeing the other D channels for use as bearer channels (24B+0D) when directed by the Government.

C-39


The contractor shall provide originating and/or terminating access for circuit-mode and packet-mode calls. The ISDN access shall provide access to and from transport-network via PRI. Originating ISDN access shall connect on-net originating locations with the associated POP. Terminating access shall connect the terminating POP with the on-net terminating locations.

ISDN PRI shall be delivered directly to the end user equipment (e.g., PBX, Centrex, multiplexer, video codec) at an ANSI ISDN defined T reference point.

For circuit-mode switched services, the ISDN access shall support user-to-user signaling via D channel during a call.

For SVS, the ISDN access shall support digitized voice (i.e., 64 kb/s speech using Pulse Code Modulation [PCM] over one B channel) as specified in ANSI T1.620, T1.603 and T1.604.

For all SDS and CSDS, the ISDN access shall support the following restricted (i.e., 56 kb/s) and unrestricted (i.e., 64 kb/s clear channel) digital information data rates over B channels via circuit-mode, as specified in ANSI T1.620, T1.603 and T1.604:

(a) Baseband at 64 kb/s over one B channel

(b) Wideband/Multirate at N times 64 kb/s over NxB channels (where N = 2 to 23 for PRI)

The ISDN access shall support the following packet-mode data rates over B channels as specified in ANSI T1.614, T1.603 and T1.604 for PSS; and, ANSI T1.606 for FRS:

(c) Baseband at 64 kb/s over one B channel

(d) Wideband/Multirate at N times 64 kb/s over NxB channels (where N = 2 to 23 for PRI)

C.2.1.16.3.1 Features

The following ISDN access features shall be supported:

(a) Mandatory

C-40


(1) Backup of Shared-D Channel. For PRI(s) with 24B+0D, shared-D channel backup/redundancy shall be supported when the associated (i.e., primary) PRI with 23B+D is down/inoperative.

(b) Optional

(1) User Packets Over D Channel. Packet-mode data transfer of user packets over both BRI and PRI D channels shall be supported.

C.2.1.16.3.2 Performance

The ISDN access shall meet the following performance parameters for originating or terminating access connection between a POP and an SDP for providing switched services:

(a) Transmission Performance

(1) All digital transmission parameters shall satisfy at least the values and ranges set forth in the Integrated Services Digital Network (ISDN): Network Transmission Interface and Performance Specifications (Bellcore Pub: TR NWT-000938).

(b) GOS

(1) For circuit switched access, the blockage shall be 3 percent or less.

(c) Availability

(1) The ISDN access shall provide an availability of at least 99.8 percent.

C.2.1.16.3.3 Interfaces

C.2.1.16.3.3.1 User-to-Network Interface

C.2.1.16.3.3.1.1 Mandatory

The contractor shall support the following interfaces at the SDP for the provisioning of ISDN access:

(a) Interface

C-41


(1) PRI (at line-rate of 1.544 Mb/s and information-payload data rate of 1.472 Mb/s for [23B+D] and 1.536 Mb/s for [24B+0D]) (Standard: ANSI ISDN T reference point)

(b) Signaling

(1) ANSI T1.615 “Telecommunications ISDN - Digital Subscriber Signaling System No. 1 (DSS1) - Layer 3 Overview for ISDN signaling”

(2) ANSI T1.602 “Telecommunications ISDN - Data-Link Layer Signaling Specification for Application at the User-Network Interface for D channel signaling”

(3) ANSI T1.609 “Telecommunications - Interworking Between the ISDN User-Network Interface Protocol and the Signaling System Number 7 ISDN User Part”

(4) ANSI T1.612 “Telecommunications - ISDN - Terminal Adaptation Using Statistical Multiplexing” while providing rate adaptation for ISDN Customer Premises Equipment (CPE)

(5) ANSI T1.626 “Telecommunications - Switch-Computer Applications Interface” while providing a computer to ISDN switch interface

(6) SS7 Signaling Interface (Standard: ANSI (T1. 110 through T1.116 and T1.611) and Bellcore GR-246-CORE)

In addition to the above generic requirements, the contractor shall support the following UNI types as specified in Table C.2.1.16.3.3.1.1-1.

Table C.2.1.16.3.3.1.1-1. Mandatory Integrated Services Digital Network Access

UNI Type

Interface Type Payload Data Rate Signaling Type

1 PRI at ANSI ISDN T reference point

Up to 1.536 Mb/s ITU-TSS Q.931

C-42


C.2.1.16.3.3.1.2 Optional

The contractor shall support the following interfaces at the SDP for the provisioning of ISDN access:

(a) Interface

(1) BRI

(i) TE1: (Standard: ANSI ISDN S reference point)(ii) TE2: (Standard: ANSI ISDN R reference point)(iii) NT2: (Standard: ANSI ISDN T reference point)


Table C.2.1.16.3.3.1.2-1. Optional Integrated Services Digital Network Access

UNI Type


1 BRI at ANSI ISDN S reference point

Up to 128 kb/s ITU-TSS Q.931

2 BRI at ANSI ISDN R reference point


3 BRI at ANSI ISDN T reference point


C.2.1.16.3.3.2 Local Access to Network Interface

Pursuant to Section C.2.1.16, the contractor shall support/provide the following interfaces to connect to a POP listed for the provisioning of ISDN Access.

C.2.1.16.3.3.2.1 Dedicated Access

(a) Mandatory

(1) ISDN PRI (Standard: ANSI T1.607 and 610)(2) E1 for non-domestic use (Standard: ITU-TSS G.702)

C-43


(b) Optional

(1) Synchronous Optical Network (SONET) OC-1 (Standard: ANSI T1.105 and 106)

(2) T3 Channelized (Standard: Bellcore Pub: GR-499-CORE)

(3) E3 Channelized, for non-domestic use (Standard: ITU-TSS G.702)

C.2.1.16.3.3.2.2 Circuit Switched Access

(a) Mandatory

(1) Integrated Digital Loop Carrier System Generic Requirements, Objectives, and Interfaces (Bellcore Pub: GR-303-CORE)

(2) Switching System Generic Requirements for Interexchange Carrier Interconnection using ISDN User Part (ISDNUP) (Bellcore Pub: GR-394-CORE)

(3) National ISDN-1 (Bellcore Pub: SR-NWT-001937)

(4) National ISDN-2 (Bellcore Pub: SR-NWT-002120)

(5) All applicable sections, related to Local Exchange Carrier (LEC) to Interexchange Carrier/International Carrier (IC/INC) interconnections for circuit-switched services, Bell Operating Company (BOC) Notes on the LEC Networks (Bellcore Pub: SR-TSV-002275)

(6) Compatibility Information for Feature Group D Switched Access Service (Bellcore Pub: TR-NPL-000258)

(7) Exchange Access Interconnection FSD-20-24-0000 (Bellcore Pub: GR-690-CORE)

(8) Bellcore Specification of SS7 (Bellcore Pub: GR-246-CORE)

(9) SONET Transport Systems: Common Generic Criteria (Bellcore Pub: GR-253-CORE)

(b) Optional

C-44


(1) None

C.2.2 Circuit Switched Services

CSS provides connectivity on a dial-up basis between Government users, from Government users to the public at large, and from the public to essential Government services. These services include the traditional switched voice and toll free services and the increasingly important 900 and CSDS. The Government community is the largest single consumer of CSS in the industry, demonstrating the importance of CSS as a vital communications tool for Government operations.

C.2.2.1 Switched Voice Service

The Government has an extremely large user community of switched voice users. In addition, much of the business it conducts is with the public and the commercial world as well as foreign entities which use SVS. The following sections provide the requirements for SVS.

C.2.2.1.1 Switched Voice Service Access Requirements

C.2.2.1.1.1 Basic Service Description

SVS shall support connections for voice and for analog data up to at least 9.6 kb/s using an ITU-TSS V.32 modem and 28.8 kb/s using an ITU-TSS V.34 modem. It shall allow voice calls, initiated from on-net locations as well as from off-net locations after verification of authorization code, to be connected to all on-net and off-net locations by direct station-to-station dialing.

SVS shall comply with ANSI T1.101 and all applicable Bellcore and ANSI standards, primarily Bellcore’s BOC Notes on the Local Exchange Carrier (LEC) Networks, and ANSI ISDN and SS7 standards.

Pursuant to Section C.2.1.16, the contractor shall provide dedicated and switched originating and/or terminating access connections for SVS calls. Originating access connections shall connect SVS on-net originating locations with the associated POP. Terminating access connections shall connect the terminating POP with SVS on-net terminating locations.

C-45


SVS access shall be delivered directly to the user’s terminal equipment including but not limited to the following types: single-line telephones; multiline key telephone systems; conference-room audio equipment; electromechanical, analog, and digital PBXs; Centrexes; data circuit terminating equipment (9.6 kb/s using ITU-TSS V.32 modem and 28.8 kb/s using ITU-TSS V.34 modem); T1 Multiplexer; ITU-TSS Group I, II, and III Facsimile (FAX) apparatus; ITU-TSS Group IV FAX (for digital access); Government secure voice and secure data equipment (e.g., Secure Telephone Unit III [STU-III]); and any other equipment typically found or proposed for use on customer premises for connection to public and private switched voice networks. The interfaces to the equipment are defined in Section C.2.2.1.1.4.1.

When SVS access is provided via switched access arrangement (see Section C.2.1.16), the following additional capabilities shall be provided:

(a) The contractor shall support a uniform numbering plan for all on-net Government locations whereby each station receiving service shall be identified by a unique directory number. The numbering plan shall support commercial PSN numbers, and contractor’s network-specific private numbers. The contractor shall implement new area codes and area code changes by the announced initial effective date of operation for that area. Any subsequent changes to commercial numbering plans that may occur during the contract life shall be included.

(b) The numbering plan established for on-net stations shall accommodate current FTS2000 numbers already following North American Numbering Plan (NANP), and commercial non-domestic numbers, although some exceptions may be approved or requested by the Government at no additional cost. The contractor shall identify numbers to be reserved for special uses, such as access to contractor’s operators, trouble reporting, or other special applications.

(c) The contractor shall provide network intercept to recorded announcements as an inherent network capability when a call cannot be completed. At a minimum, such announcements shall be provided for the following conditions: time out during dialing, network congestion, denial of access to off-net and non-domestic calls, denial of access to features, and other related conditions.

SVS shall provide the capability for calls to terminate via Inmarsat (terminal types A, B, M, Mini-M, and Aeronautical). (Inmarsat origination is addressed in Section C.2.6.1 as an optional item.)

C-46


The contractor may exceed the basic requirements by providing the ability to have customized network intercept recorded announcements. The contractor would be responsible for recording the network announcements after obtaining Government approval of proposed scripts. The contractor would have the capability of implementing scripts customized for the Government.


The following SVS access features shall be supported.

C.2.2.1.1.2.1 Mandatory

None.

C.2.2.1.1.2.2 Optional

None.


The access performance parameters for originating or terminating access connection between a POP and an SDP shall meet the following:


(1) All analog transmission parameters shall satisfy at least the values and ranges set forth in Sections 7, Transmission, BOC Notes on the LEC Networks (Bellcore Pub: SR-TSV-002275).

(2) All digital transmission parameters shall satisfy at least the values and ranges set forth in the High-Capacity Digital Special Access Service - Transmission Parameter Limits and Interface Combinations (Bellcore Pubs: GR-342-CORE, GR-54-CORE, and GR-334-CORE).

(b) GOS

(1) For switched access arrangement and dedicated - Class 2 access arrangement trunk groups, the blockage shall be 3 percent or less.

C-47


(c) Availability of Service

(1) SVS access shall provide an availability of at least 99.8 percent.

(d) Post-Dialing Delay

(1) Post-dialing delay shall not exceed best commercial practice.



The contractor shall support the following interfaces at the SDP for the provisioning of SVS access.

C.2.2.1.1.4.1.1 Mandatory

(a) Analog Line

(1) Two-wire and Four-wire loop access circuits (Standard: Bellcore’s BOC Notes on the LEC Networks [SR-TSV-002275])

(b) Analog Trunk

(1) Two-wire access circuit (Standard: Bellcore’s BOC Notes on the LEC Networks [SR-TSV-002275])

(2) Four-wire E&M access circuit (Standard: Bellcore’s BOC Notes on the LEC Networks [SR-TSV-002275])

(c) Digital Trunk

(1) T1 channelized (with Extended Super Frame [ESF] format) at line-rate of 1.544 Mb/s and information-payload data rate of 1.536 Mb/s. (Standard: Bellcore’s BOC Notes on the LEC Networks [SR-TSV-002275], and ANSI T1.102/107/403)

C-48


(2) ISDN PRI at line-rate of 1.544 Mb/s and information-payload data rate of 1.472 Mb/s for (23B+D) and 1.536 Mb/s for (24B+0D) for dedicated access. (Standard: ANSI T1.607 and 610)

(3) T3 channelized at line-rate of 44.736 Mb/s and information-payload data-rate of 43.008 Mb/s. (Standard: Bellcore PUB GR-499-CORE)

(4) E1 channelized at line-rate of 2.048 Mb/s and information-payload data-rate of 1.92 Mb/s. (Standard: ITU-TSS G.702) - For Non-Domestic Use Only

In addition to the above generic requirements, the contractor shall support the UNI types as specified in Table C.2.2.1.1.4.1.1-1.

Table C.2.2.1.1.4.1.1-1. Mandatory User-to-Network Interface for Switched Voice Service

UNI Type Interface Type Payload Data Rate or Bandwidth

Signaling Type

1 Analog Line: Two-Wire

4 kHz Bandwidth Line - Loop Signaling

2 Analog Line: Four-Wire


3 Analog Trunk: Two-Wire

4 kHz Bandwidth Trunk - Loop Signaling (loop and ground start)

4 Analog Trunk: Four-Wire

4 kHz Bandwidth Trunk - E&M Signaling

5 Digital Trunk: T1 Up to 1.536 Mb/s T1 Robbed-Bit Signaling

6 Digital Trunk: ISDN PRI T Reference Point

Up to 1.5.36 Mb/s ITU-TSS Q.931

7 T3 Channelized Up to 43.008 Mb/s T1 Robbed-Bit Signaling

8 (Non-

Domestic)

E1 Channelized Up to 1.92 Mb/s E1 Signaling

C-49


C.2.2.1.1.4.1.2 Optional

(a) Digital Trunk

(1) SONET OC-1 at line-rate of 51.840 Mb/s and information-payload data-rate of 49.536 Mb/s. (Standard: ANSI T1.105 and 106)

(2) E3 channelized at line-rate of 34.368 Mb/s and information-payload data-rate of 30.72 Mb/s. (Standard: ITU-TSS G.702) - For Non-Domestic Use

(3) SS7 Signaling Interface. (Standard: ANSI [T1.110 through T1.116 and T1.611] and Bellcore GR-246-CORE)

(b) Digital Line

(1) ISDN BRI for dedicated access (Standard: ANSI T1.607 and 610)

If the option is proposed, the contractor shall support the following UNI types as specified in Table C.2.2.1.1.4.1.2-1 in addition to the above generic requirements.

Table C.2.2.1.1.4.1.2-1. Optional User-to-Network Interface for Switched Voice Service

UNI Type Interface Type Payload Data Rate or Bandwidth

Signaling Type

1 SONET OC-1 49.536 Mb/s SS72

(Non-Domestic)

E3 Channelized Up to 30.72 Mb/s SS7, E1 Signaling

3 T3 Channelized Up to 43.008 Mb/s SS74 E1 Channelized Up to 1.92 Mb/s SS75 Digital Line: ISDN

BRI S and T Reference Point

Up to 128 kb/s (2x64 kb/s)

ITU-TSS Q.931


Pursuant to Section C.2.1.16, the contractor shall support/provide the following interfaces to connect to a POP listed for the provisioning of SVS access.

C-50



(a) Mandatory

(1) T1 and Fractional T1 channelized with ESF (Standard: Bellcore Pub: SR-TSV-002275; ANSI T1.102/107/403)

(2) ISDN PRI (Standard: ANSI T1.607 and 610)

(3) T3 and Fractional T3 channelized(Standard: Bellcore Pub: GR-499-CORE)

(4) E1 channelized for non-domestic use (Standard: ITU-TSS G.702)

(5) Analog (Standard: Bellcore Pub: SR-TSV-002275)

(b) Optional

(1) SONET OC-1 and OC-1 VT (Standard: ANSI T1.105 and 106)

(2) E3 channelized for non-domestic use (Standard: ITU-TSS G.702)


(a) Mandatory

(1) All applicable sections, related to LEC to IC/INC interconnections for CSSs, BOC Notes on the LEC Networks (Bellcore Pub: SR-TSV-002275)


(3) Exchange Access Interconnection FSD 20-24-0000 (Bellcore Pub: GR-690-CORE)

(4) Bellcore Specification of Signaling System Number 7 (Bellcore Pub: GR-246-CORE)

(b) Optional

(1) None

C-51


C.2.2.1.2 Switched Voice Service Transport Requirements


SVS transport shall support connections for voice and for analog data up to at least 9.6 kb/s using an ITU-TSS V.32 modem and 28.8 kb/s using an ITU-TSS V.34 modem. It shall allow voice calls, initiated from on-net locations as well as from off-net locations after verification of authorization code, to be connected to all on-net and off-net locations by direct station-to-station dialing.

SVS shall comply with ANSI T1.101 and all applicable Bellcore and ANSI standards, primarily Bellcore’s BOC Notes on the LEC Networks, and ANSI ISDN and SS7 standards.

Pursuant to Section C.2.1.16, the contractor shall provide SVS POP-to-POP connections between the contractor’s listed POPs. The contractor shall accept at any of its listed POPs which support the appropriate on-net service, originating SVS calls via dedicated and/or switched access arrangement from the associated access providers. The contractor shall hand off terminating SVS calls via dedicated and/or switched access arrangement from any of its listed POPs which support the appropriate on-net service to the associated access providers.

The contractor shall support a uniform numbering plan for all on-net Government locations whereby each station receiving service shall be identified by a unique directory number. The numbering plan shall support commercial PSN numbers, non-commercial agency specific private numbers, and contractor’s network-specific private numbers.

The numbering plan established for on-net stations shall accommodate current FTS2000 numbers already following NANP, and commercial non-domestic numbers, although some exceptions may be approved or requested by the Government at no additional cost. The contractor shall identify numbers to be reserved for special uses, such as access to contractor’s operators, trouble reporting, or other special applications.

The contractor shall provide network intercept to recorded announcements as an inherent network capability when a call cannot be completed. At a minimum, such announcements shall be provided for the following conditions: number disconnected (disconnected number shall not be reassigned for at least 90 days for those situations where the contractor controls number assignment), time out during dialing, network congestion, denial of access to off-net and non-domestic calls, denial of access to features, and other related conditions.

C-52


The contractor shall provide authorization codes. The purpose of an authorization code is to provide to the network a calling identification and COS for users. The same authorization code shall be used for originating on- and off-net calls if identification cannot be made by other means for billing and COS purposes, or when override capabilities are desired.

The COS derived from an authorization code shall take precedence over that derived from any other means. Actual requirements for calling party identification, COS assignment, and the limit on the amount of dollars billable, either in total or in a billing period, and the expiration date for SVS authorization codes will be specified by the Government as part of service ordering.

The format of the authorization code shall be determined by the contractor except as described in Section C.5.2.1. The contractor shall provide credit card-sized authorization code card(s), also called FTS2001 Calling Cards, unless otherwise directed by the Government, which shall be made of durable plastic with magnetic strip (swipe) coding and imprinted with authorization code, user’s name, and organization. The FTS2001 Calling Cards and user instructions shall be issued and delivered at no cost to the Government. The contractor shall take safeguards against potential fraud and theft regarding issuance, distribution, and activation of authorization codes. Personal Identification Numbers (PINs) shall be delivered independently from the calling cards. In addition, the last 4 digits of authorization codes (i.e., PIN), shall not be included in billing records. If the calling card has sufficient space, the Federal Relay “TDD/800-877-8339” shall be included on the back of the calling card.

While the contractor shall determine the dialing sequence for entering an authorization code, the Government requires that the dialing sequence be such that the network shall be alerted that an authorization code is about to be entered so as not to delay the processing of calls not requiring the use of this feature.

It shall be possible to temporarily override COS restriction assigned to a caller’s station to allow an individual user to place a call at a higher network COS for the duration of the call by entering a valid authorization code. This shall be accomplished without excessive delays caused by waiting for all digits to be dialed before recognizing the call as one involving an override. CDRs shall reflect all relevant data, on the call, which shall be charged to the authorization code rather than to the originating station. (See also Section C.2.2.1.2.2.1(h) for additional requirements).

C-53


The contractor shall allow authorized users to gain access, after validation of authorization codes, to on-net SVS and features from off-net locations by dialing certain toll free and message unit-free (to the callers) commercial directory numbers. The commercial toll free number shall be provided by the contractor. The number may be a local number, a Foreign Exchange number, an NANP number, or some other service type (e.g., toll free service) for which toll free and message unit-free service has been arranged for predesignated regions. This toll free and message unit-free commercial directory number (e.g., toll free number) shall be printed on the back of the calling card. The boundaries of these regions shall be defined by the contractor. A user shall be able to select by service order the regions of the country from which access is to be allowed and the service type that provides the most economical service for a given application.

The Government provides certain individuals with credit cards, called travel cards, for their use while traveling on official Government business. The Government is planning to conduct an acquisition for travel card contractor(s). As a result of this acquisition, the Government’s travel card contractor may provide the capability for the traveler to utilize his/her travel card to make FTS2001 telephone calls. If requested by the Government, the FTS2001 Contractor shall coordinate directly with the Government’s travel card contractor(s) to enable this use of the travel card. The FTS2001 Contractor shall therefore be prepared to provide to the Government’s travel card contractor(s) all necessary information so that the Government’s travel card contractor(s) can include this information on the back side of the travel card. Note that the Government’s travel card is not intended for the billing or payment of telephone services. Billing of any calls made with the aid of the travel card will take place through the channels specified in Section C.3.

The contractor may exceed the basic requirements by providing the ability to enter an authorization code via spoken word. The contractor may require a unique dialing sequence for the entry of an authorization code via spoken word.

The contractor may exceed the basic requirements by providing the capability for implementing network intercept announcement scripts customized for the Government. In this case, the contractor shall record customized network announcements after obtaining Government approval of scripts.

Contractors may offer portable Dual-Tone Multifrequency (DTMF) tone dialers to facilitate usage of various system features where tone dialing equipment is not available.

C-54



The following SVS transport features shall be supported.


(a) Agency-Recorded Message Announcements. This feature shall allow authorized Government personnel to record message announcements within the network. The recording shall be assigned an on-net number, and shall be accessible from on-net and off-net stations. The contractor shall provide the capability of a three-minute message announcement length. The length of each message provided by the Government will be determined on a case-by-case basis and be up to three minutes in length (or longer if the contractor capability exists and is provided at no additional cost to the Government). A call to the announcement must be answered within five rings, and barge-in access to the announcement shall be permitted. The contractor shall provide a system-wide capability for storing a minimum of 300 recorded messages. This feature shall enable a minimum of 250 callers, concurrently, to access an announcement.

(b) Operator Services. Operators shall provide support services (in English) for users. This service shall be made available 24 hours per day, 7 days per week. Users shall not receive a busy tone when calling for operator services. Calls to operators shall be answered within five rings 90 percent of the time. The following services shall be provided by operators:

(1) In cases where automatic network audio conferencing is not possible, operators shall have the capability to set up conferences and connect all conferees.

(2) Operators shall be available to assist users encountering dialing difficulties while using the contractor’s services. The operator shall remain on the line until the call has been connected.

(3) Operators shall provide callers with locator service numbers for all agencies subscribing to FTS2001 contracts. These are agency numbers through which callers can receive further information from the agency regarding completion of a call. These numbers will be provided to the contractor by the Government, and will be updated periodically. The contractor shall maintain its locator database for the Government.

C-55


(4) Operators shall be able to complete calls for accessing the network from off-net and on-net locations. Operators shall be able to verify authorization codes given verbally by callers accessing the network, and upon confirmation shall be able to complete the call.

(5) A user shall be able to call an operator by dialing a special number to report and deactivate a stolen or lost authorization code or calling card, or to obtain a credit adjustment for a completed call to a wrong number, an interrupted call, or unsatisfactory transmission.

(c) Call Screening. Call screening comprises a set of features that determine a call’s eligibility to be completed as dialed, based upon COS information associated with the user, the station, or the trunk group. These call screening features are described below:

(1) Class of Service and Restrictions. The contractor shall provide, at a minimum, 128 classes of service available to each user, station, or trunk. However, given the Government’s diverse needs and the uncertainty of future offerings the provision of more than the minimum number is encouraged.

COS shall be determined from ANI, authorization code, traveling classmark, or trunk group. The COS derived from an authorization code shall take precedence over that derived from other means. Classes of service shall identify, but not be limited to, access and feature restrictions:

(i) Access restrictions shall include, but not be limited to, access to toll free and 900 calls, access to off-net calling, access to other Government networks, access to non-domestic calling, and access to other than specified NPA/NXXs.

(ii) Feature restrictions shall allow or restrict access to network features by users or groups of users.

(2) Time of Day. Time of day, day of the week, and day of the year restrictions shall be possible, and implementable on a per station, per location, and per authorization code basis. This type of restriction can be used, for example, to prevent unauthorized use of the service after normal business hours.

C-56


(3) Traveling Classmark. This feature shall provide for the acceptance of traveling classmarks from all locations served by PBXs and Centrexes that are able to provide these classmarks, including calls extended by operators. Traveling classmarks (TCOS) shall conform to the TCOS format (i.e., called number + TCOS). User calling characteristics and limitations may be determined from the traveling classmark.

(4) Code Block. This feature screens ineligible users, stations, and trunks with certain class-of-service access restrictions from calling specified area codes, exchange codes, and countries. Blocked calls shall be intercepted to appropriate network recorded announcements.

(d) Off-Net Information Calls. A user shall be able to call off-net directory assistance by dialing NPA-555-1212. NPA also includes service access codes (e.g., 800) for this feature.

(e) Network Audio Conference. The contractor shall provide network audio conferencing for two- and four-wire audio conference equipment, as well as to any telephone accessible via the contractor’s network.

The following capabilities shall be supported:

(1) User-Initiated Conference. This capability shall allow authorized users to place such calls by dialing a designated number to access the service, followed by an authorization code established for that service. The following two modes of user-initiated voice conference capabilities shall be supported:

(i) Automated Mode - where a user initiates a previously scheduled conference as follows:

(A) Meet-Me Conference - this capability shall allow at least 400 users to be connected in a conference by each user dialing a designated number (NANP number or a toll free or special billing SAC [e.g., 800 number]), at a predetermined time or as directed by the operator, then followed by an authorization code established for

C-57


that conference. For recurring meet-me conferences, the contractor shall permit the participants to reuse the same dial access number and conference authorization code, and allow bookings of recurring conferences in three month increments (e.g., be able to book a recurring conference every Monday morning at 10:00 AM eastern time for the next three months).

(B) Preset Conference - this capability shall allow an authorized user to activate a previously defined conference with associated conferees, by dialing an access number followed by an authorization code. Once activated, the system will attempt to connect the pre-designated participants.

(ii) Manual Mode - where a user dials each conferee in succession to set up a conference. This capability shall allow the user, who is the call controller, to add conferees to an existing conference, up to at least 12 conferees. This feature is also known as “Add-on/Progressive Conference.”

(2) Operator-Controlled Conference. This capability shall allow operators to establish a conference. Conferees shall be able to recall an operator during a conference for immediate attention such as general assistance, or adding or dropping participants. This service shall be made available 24 hours per day, 7 days per week.

The voice conferencing service for user-initiated as well as operator-controlled conferences shall support conference bridging capability up to a minimum of 800 ports. The number of simultaneous conferences to be supported by the conference bridge shall be limited only by the capacity of the conference bridge utilizing all ports. The service shall allow storage and retrieval of up to at least 1,000 predefined conferences of an average seven ports per conference. The service shall also allow selective two-way or one-way conversations between conferencing ports. This feature is intended to allow one subset of conferees to participate in a two-way conference, while the second subset of conferees are listeners only.

This service shall provide transmission bridging arrangements, including automatic, dynamic control of volume, noise, and echo, with minimum break-in difficulties. It shall also minimize the need for special user and operator instructions and training. These arrangements shall minimize the impact of network difficulties, such as

C-58


“ring/no answer,” “noise on a conferee leg,” and “conference interrupted without explanation,” as well as the facilitation for monitoring and troubleshooting capability of network difficulties by an operator while establishing a conference and during a conference in order to take corrective actions immediately.

The service shall be made available to all types of common voice equipment, such as two-wire conference rooms, desk-type speaker phones, and standard telephones, as well as four-wire conference rooms. The following capabilities shall be supported:

(3) Sufficient capacity to support an average daily conference load of 300 conferences (of all the types of conferences above combined) averaging seven conferees and/or ports per conference and establishment of 20 conferences in a 5-minute period for all conference types on the schedule.

(4) Operator assistance shall be available at any time during a conference.

(5) At least 36 simultaneous conference calls shall be able to be monitored by operator(s).

(6) Establishment of unscheduled operator-controlled conferences within ten minutes of a request, 24 hours per day, 7 days per week.

(f) Automated Verification of Authorization Codes. When an authorization code is used for the service, it shall be verified without involving an operator before the service is provided.

(g) Suppression of Calling Number Delivery. Based on the COS of the originating station or FTS2001 Calling Card, the contractor shall inhibit the delivery of the calling number (i.e., ANI) by setting the Privacy Indicator at the originating end and honoring it at the terminating end.

(h) Internal Agency Accounting Code. For calls involving an FTS2001 Calling Card or originating station with a special COS, it shall be possible to enter additional (up to a maximum of eight) digits to identify internal agency accounting codes for the call (i.e., these accounting codes will be transferred to the CDR without any further processing). CDRs shall reflect all relevant data, including these internal agency accounting code digits, on the call, which shall be charged to the authorization code rather than to the originating station.

C-59



(a) Network Audio Conference Security. The contractor shall support voice conferencing capability for sensitive voice conferences with end-user encryption to support discussions of an unclassified, sensitive, or private nature between multiple locations with protection from unauthorized interception.

(b) User-to-User Signaling Via ISDN D-Channel. In order to support user-to-user signaling via ISDN D-channel during a call, the contractor shall accept and forward (i.e., relay) user-to-user signals from/to ISDN D-channels at the POPs where ISDN access arrangement is supported in accordance with ANSI T1 and ITU-TSS standards for ISDN and SS7.


The network transport performance parameters for POP-to-POP connection shall meet the following:

(a) Transmission (Digital) Performance

(1) All digital transmission parameters shall satisfy at least the values and ranges set forth in the ANSI T1.510 for T1, Bellcore PUB GR-499-CORE for T3, and ANSI T1.105 and 106 for SONET.

(b) GOS

(1) The blockage shall be 1 percent or less.


(1) SVS transport shall provide an availability of at least 99.8 percent.



C-60



C.2.2.1.2.4.1 Local Access to Network Interfaces

Pursuant to Section C.2.1.16, the contractor shall support/provide the following interfaces (i.e., LANI) at each POP listed for the provisioning of SVS transport.


(a) Mandatory



(3) T3 and Fractional T3 channelized (Standard: Bellcore Pub: GR-499-CORE)

(4) E1 channelized for Non-Domestic use (Standard: ITU-TSS G.702)

(5) Analog (Standard: Bellcore Pub: SR-TSV-002275)

(b) Optional




(a) Mandatory



C-61




(b) Optional

(1) None

C.2.2.2 Circuit Switched Data Service

As data and multimedia applications grow within the Government, there is an increasing need for digital connectivity on a dial-up basis. The Government has a large community of CSDS users, particularly for on-demand video conferencing applications. Additionally, it is expected that there is a growing need for CSDS in the Government for applications, such as dial-up back-up circuits and circuits required for a short duration. The following sections provide the requirements for CSDS.

C.2.2.2.1 Circuit Switched Data Service Access Requirements


CSDS access shall provide a synchronous, full duplex, totally digital, SDP-to-POP service at data rates up to DS1, including certain integral multiples of DS0 data rates to on-net and off-net locations. However, for calls terminating to off-net locations, the bandwidth requested by the originating on-net location shall be limited to the bandwidth limitations in the PSN between the terminating POP and the terminating location.

CSDS shall comply with ANSI X3.189, ITU E.721, and all applicable Bellcore and ANSI standards for digital transmission including SONET; and ITU-TSS and EIA standards for Data Terminal Equipment (DTE) interfaces.

Pursuant to Section C.2.1.16, the contractor shall provide dedicated and switched originating and/or terminating access connections for CSDS calls. Originating access connections shall connect CSDS on-net originating locations with the associated POP. Terminating access connections shall connect the terminating POP with CSDS on-net terminating locations.

C-62


CSDS dedicated access shall be delivered directly to user’s terminal equipment including but not limited to the following types: DTE (e.g., workstation, host computer, PC, video codec, Group 4 FAX, and other communicating office equipment), digital PBX, or Intelligent multiplexer. The interfaces to these equipment types are defined in Section C.2.2.2.1.4.1.

CSDS shall provide network-derived clocking to the DTE or PBX/multiplexer (MUX) at the SDP. Once a call has been established, all bit sequences transmitted by the DTE shall be transported as data/bit transparent, maintaining data/bit sequence integrity.

CSDS shall support the following categories of information-payload bandwidth:

(a) DS0 Category. For this category of service, the dialable bandwidth shall be DS0 (i.e., 56 kb/s and 64 kb/s) data rate.

(b) DS1 Category. For this category of service, the dialable bandwidth shall be DS1 (i.e., 1.536 Mb/s) data rate.

(c) Multirate DS0 Category. For this category of service, the dialable bandwidth shall be two times DS0, six times DS0, and twelve times DS0.

When CSDS is provided via switched access arrangement (see Section C.2.1.16), the following additional capabilities shall be supported:

(d) The contractor shall support a uniform numbering plan for all on-net Government locations whereby each station receiving service shall be identified by a unique directory number which will be employed by CSDS users for calling each other. This numbering plan shall use the NANP as proposed for SVS (refer to Section C.2.2.1.1.1), and shall be integrated with that plan. Calling capability shall be spontaneous and shall not require scheduling.

(e) For a multirate (e.g., Multirate DS0 category), the contractor shall provide appropriate dialing sequence for initiating calls with different bandwidths. Once a call has been established by this dialing sequence, all bit sequences transmitted by the DTE shall be transported as data/bit transparent.

The contractor may exceed the basic requirements by providing a synchronous, full duplex, totally digital, SDP-to-POP service at data rates up to SONET OC-3, including integral multiples of DS1 data rates to on-net and off-net locations. This would support the following categories of information-payload bandwidth:

C-63


(f) Multirate DS1 Category. For this category of service, the dialable bandwidth range would be available from DS1 to N times DS1 data rates, where N varies from 2 to 27.

(g) DS3 Category. For this category of service, the dialable bandwidth would be DS3 (i.e., 43.008 Mb/s) data rate.

(h) SONET Level-I (i.e., OC-1) Category. For this category of service, the dialable information-payload bandwidth would be SONET OC-1 (i.e., 49.536 Mb/s) data rate.

(i) SONET Level-II (i.e., Multirate OC-1) Category. For this category of service, the dialable information-payload bandwidth range would be available from SONET OC-1 to N times OC-1 data rates, where N varies from two to three.

(j) SONET Level-III (i.e., Multirate OC-3) Category. For this category of service, the dialable information-payload bandwidth range would be available from SONET OC-3 to N times OC-3 data rates, where N varies from two to four. SONET OC-3 would support information-payload data-rate of 148.608 Mb/s.

When CSDS is provided via switched access arrangement (see Section C.2.1.16), the following additional capabilities would be supported:

(k) For a multirate (e.g., Multirate DS1 category), the contractor would provide appropriate dialing sequence for initiating calls with different bandwidths. Once a call has been established by this dialing sequence, all bit sequences transmitted by the DTE would be transported as data/bit transparent.


The following CSDS access features shall be supported.


None.


None.


C-64


The access transmission performance parameters for originating or terminating access connection between a POP and an SDP shall meet the following:


(1) All digital transmission parameters shall satisfy at least the values and ranges set forth in the High-Capacity Digital Special Access Service - Transmission Parameter Limits and Interface Combinations (Bellcore Pub: GR-342-CORE).

(b) GOS

(1) For switched access arrangement and dedicated - Class 2 access arrangement trunk groups, the blockage shall be 3 percent or less.


(1) CSDS access shall provide an availability of at least 99.8 percent.



The contractor shall support the following interfaces at the SDP for the provisioning of CSDS access.


(a) ITU-TSS V.35

(b) EIA RS-449

(c) EIA RS-530

C-65

(d) ISDN PRI with multirate facility at line-rate of 1.544 Mb/s and information-payload data rate of up to 1.472 Mb/s for (23B+D) and 1.536 Mb/s for (24B+0D) for dedicated access. (Standard: ANSI T1.607 and 610)

(e) T1 (with ESF format) at line-rate of 1.544 Mb/s and information-payload data rate of up to 1.536 Mb/s. (Standard: Bellcore’s BOC Notes on the LEC Networks [SR-TSV-002275], and ANSI T1.102/107/403)

(f) SS7 signaling interface (Standard: ANSI T1.110 through T1.116 and T1.611)

In addition to the above generic requirements, the contractor shall support the following UNI types as given in Table C.2.2.2.1.4.1.1-1.

Table C.2.2.2.1.4.1.1-1. Mandatory User-to-Network Interface for Circuit Switched Data Service

UNI Type Interface Type Payload Data Rate Signaling Type1 ITU-TSS V.35 Up to 1.536 Mb/s RS366A (dialing)2 EIA RS-449 Up to 1.536 Mb/s RS366A (dialing)3 EIA RS-530 Up to 1.536 Mb/s RS366A (dialing)4 ISDN PRI (Multirate)

(T Reference Point)Up to 1.536 Mb/s ITU-TSS Q.931

5 T1 (with ESF) Up to 1.536 Mb/s SS7

C.2.2.2.1.4.1.2 Optional

(a) T3 at line-rate of 44.736 Mb/s and information-payload data-rate of 43.008 Mb/s. (Standard: Bellcore PUB GR-499-CORE)

(b) E1 at line-rate of 2.048 Mb/s and information-payload data-rate of 1.92 Mb/s. (Standard: ITU-TSS G.702) - For Non-Domestic Use

(c) E3 at line-rate of 34.368 Mb/s and information-payload data-rate of 30.72 Mb/s. (Standard: ITU-TSS G.702) - For Non-Domestic Use

(d) SONET OC-1 at line-rate of 51.840 Mb/s and information-payload data-rate of 49.536 Mb/s. (Standard: ANSI T1.105 and 106)

C-66

(e) SONET OC-3 at line-rate of 155.520 Mb/s and information-payload data-rate of 148.608 Mb/s. (Standard: ANSI T1.105 and 106)

(f) SONET OC-12 at line-rate of 622.080 Mb/s and information-payload data-rate of 594.432 Mb/s. (Standard: ANSI T1.105 and 106)

If an option is proposed, the contractor shall support the UNI types as given in Table C.2.2.2.1.4.1.2-1 in addition to the above generic requirements.

Table C.2.2.2.1.4.1.2-1. Optional User-to-Network Interface for Circuit Switched Data Service

UNI Type


1 T3 Up to 43.008 Mb/s SS72

(Non-Domestic)

E1 Up to 1.92 Mb/s SS7, E1 Signaling

3 (Non-

Domestic)

E3 Up to 30.72 Mb/s SS7, E1 Signaling

4 SONET OC-1 Up to 49.536 Mb/s SS75 SONET OC-3 Up to 148.608 Mb/s SS76 SONET OC-12 Up to 594.432 Mb/s SS77 ISDN BRI (Multirate)

(S and T Reference Point)



Pursuant to Section C.2.1.16, the contractor shall support/provide the following interfaces to connect to a POP for the provision of CSDS access.


(a) Mandatory

(1) T1 and Fractional T1 with ESF (Standard: Bellcore Pub: SR-TSV-002275; ANSI T1.102/107/403)


C-67


(4) DS0 and Subrate DS0 (Bellcore Pub: SR-TSV-002275)

(b) Optional


(2) SONET OC-3 (Standard: ANSI T1.105 and 106)

(3) E1 for Non-Domestic use (Standard: ITU-TSS G.702)



(a) Mandatory





(5) Switched DS0 (Bellcore Pub: SR-TSV-002275

(b) Optional

(1) Synchronous Optical Network (SONET) Transport Systems: Common Generic Criteria (Bellcore Pub: GR-253-CORE)

C-68

C.2.2.2.2 Circuit Switched Data Service Transport Requirements


CSDS transport shall provide a synchronous, full duplex, totally digital, POP-to-POP CSS at data rates up to DS1, including certain integral multiples of DS0 data rates to on-net and off-net locations. However, for calls terminating to off-net locations, the bandwidth requested by the originating on-net location shall be limited to the bandwidth limitations in the PSN between the terminating POP and the called location.

CSDS shall comply with ANSI X3.189, ITU E.721, and all applicable Bellcore and ANSI standards for digital transmission including SONET.

Pursuant to Section C.2.1.16, the contractor shall provide CSDS POP-to-POP connections between the contractor’s listed POPs. The contractor shall accept at any of its listed POPs which support the appropriate on-net service, originating CSDS calls via dedicated and/or switched access arrangement from the associated access providers. The contractor shall hand off terminating CSDS calls via dedicated and/or switched access arrangement from any of its listed POPs which support the appropriate on-net service to the associated access providers.

The contractor shall support a uniform numbering plan for all on-net Government locations whereby each station receiving service shall be identified by a unique directory number which will be employed by CSDS users for calling each other. This numbering plan shall use the NANP as proposed for SVS (refer to Section C.2.2.1.1.1), and shall be integrated with that plan. Calling capability shall not require scheduling. Once a call has been established, all bit sequences transmitted shall be transported as data/bit transparent, maintaining data/bit sequence integrity.

CSDS shall support the following categories of information-payload bandwidth:

(a) DS0 Category. For this category of service, the dialable bandwidth shall be DS0 (i.e., 56 kb/s and 64 kb/s) data rate.

(b) Multirate DS0 Category. For this category of service, the dialable bandwidth range shall be two times DS0 (i.e., 64 kb/s clear channel), six times DS0, and twelve times DS0.

(c) DS1 Category. For this category of service, the dialable bandwidth shall be DS1 (i.e., 1.536 Mb/s) data rate.

C-69

For a multirate (e.g., Multirate DS0 category), the contractor shall provide a dialing sequence for initiating calls with different bandwidths. Once a call has been established by this dialing sequence, all bit sequences transmitted shall be transported as data/bit transparent.

The contractor may exceed the basic requirements by providing a synchronous, full duplex, totally digital, POP-to-POP CSS at data rates up to SONET OC-3, including integral multiples of DS0 or DS1 data rates to on-net and off-net locations.

If the contractor exceeds the basic requirements then CSDS would support the following categories of information-payload bandwidth:

(d) Multirate DS1 Category. For this category of service, the dialable bandwidth range would be available from DS1 to N times DS1 data rates, where N varies from 2 to 27.

(e) DS3 Category. For this category of service, the dialable bandwidth would be DS3 (i.e., 43.008 Mb/s) data rate.

(f) SONET Level-I (i.e., OC-1) Category. For this category of service, the dialable information-payload bandwidth would be SONET OC-1 (i.e., 49.536 Mb/s) data rate.

(g) SONET Level-II (i.e., Multirate OC-1) Category. For this category of service, the dialable information-payload bandwidth range would be available from SONET OC-1 to N times OC-1 data rates, where N varies from two to three.

(h) SONET Level-III (i.e., Multirate OC-3) Category. For this category of service, the dialable information-payload bandwidth range would be available from SONET OC-3 to N times OC-3 data rates, where N varies from two to four. SONET OC-3 would support information-payload data-rate of 148.608 Mb/s.

For a multirate (e.g., Multirate DS1 category), the contractor would provide a dialing sequence for initiating calls with different bandwidths. Once a call has been established by this dialing sequence, all bit sequences transmitted shall be transported as data/bit transparent.

The contractor may also exceed the basic requirements by providing authorization codes for this service as specified for SVS (refer to Section C.2.2.1.2.1).

C-70


The following CSDS transport features shall be supported.


None.


(a) Dial-In. The contractor shall support toll free numbers, in addition to 10-digit PSN numbers, dial-in access from off-net locations (i.e., PSN) via ISDN access arrangement where available commercially. Access to CSDS shall only be provided after verification of the authorization code entered by the user. Therefore, the contractor shall accept, as a minimum, at any of its listed POPs which support the appropriate service , CSDS calls originating from the PSN.

(b) User-to-User Signaling Via ISDN D-Channel. In order to support user-to-user signaling via ISDN D-channel during a call, the contractor shall accept and forward (i.e., relay) user-to-user signals from/to ISDN D-channels at the POPs where ISDN access arrangement is supported in accordance with ANSI T1 and ITU-TSS standards for ISDN and SS7.


The network transport transmission performance parameters for POP-to-POP connection shall meet the following:


(1) All digital transmission parameters shall satisfy at least the values and ranges set forth in the ANSI T1.503/510 for T1, Bellcore PUB GR-499-CORE for T3, and ANSI T1.105 and 106 for SONET.

(b) GOS


C-71


(1) CSDS transport shall provide an availability of at least 99.8 percent.


Pursuant to Section C.2.1.16, the contractor shall support/provide the following interfaces (i.e., LANI) at each POP listed for the provision of CSDS transport.

C.2.2.2.2.4.1 Dedicated Access

(a) Mandatory





(b) Optional

(1) E1 for International use (Standard: ITU-TSS G.702)

(2) E3 for International use (Standard: ITU-TSS G.702)

(3) SONET OC-1 and OC-1 VT(Standard: ANSI T1.105 and 106)


C.2.2.2.2.4.2 Circuit Switched Access

(a) Mandatory


C-72




(5) Switched DS0 (Bellcore Pub: SR-TSV-002275)

(b) Optional

(1) Synchronous Optical Network (SONET) Transport Systems: Common Generic Criteria (Bellcore Pub: GR-253-CORE)

C.2.2.3 Toll Free Services

The Government is in the business of providing services to wide varieties of user communities. In most cases, its best method for reaching its citizen base is through the use of toll free voice services. Government applications for toll free service are among the largest and most sophisticated in the industry and must be support by a flexible set of advanced features. The following sections provide the requirements for Toll Free Service.

C.2.2.3.1 Toll Free Services Access Requirements


The toll free service shall allow the caller to be connected from on-net or off-net locations to predesignated stations or locations by dialing certain toll free and message-unit-free (e.g., 800 and 888) service access code numbers.

The toll free services shall comply with all Bellcore and ANSI standards, primarily Bellcore’s BOC Notes on the LEC Networks, and ANSI ISDN and SS7 standards.

Pursuant to Section C.2.1.16, the contractor shall provide dedicated and switched access connections for the toll free service calls. Access connections shall connect the terminating POP with the toll free services on-net terminating locations.

C-73

Terminating access for toll free services shall be delivered directly to the user’s terminal equipment including but not limited to the following types: single-line telephones; multiline key telephone systems; electromechanical, analog, and digital PBXs; Centrexes; data circuit terminating equipment (9.6 kb/s using International Telegraph and Telephone Consultative Committee [CCITT] V.32 modem and 28.8 kb/s using CCITT V.34 modem); T1 multiplexer; CCITT Group I, II, and III FAX apparatus; Automated Call Distributors (ACDs); automated call-handling equipment (e.g., interactive voice response/transaction processing systems) for providing opinion polling; and database access, and any other equipment typically found or proposed for use on user premises for connection to public and private switched voice networks. The interfaces to these equipment types are defined in Section C.2.2.3.1.4.1.

The toll free services shall permit bundling, at the Government’s discretion, of multiple toll free trunk groups; of toll free and 900 service specific trunk groups; and of toll free and/or 900 service specific trunk groups with SVS trunk groups into a single trunk group to be shared between toll free, 900 and/or SVS incoming calls.

The contractor shall provide network intercept to recorded announcements as an inherent network capability when a call cannot be completed. At a minimum, such announcements shall be provided for the following conditions: time out during dialing, network congestion, denial of access to non-domestic calls, denial of access to features, and other related conditions. As a default, the contractor shall provide a busy signal for all calls encountering network congestion and/or terminating egress congestion.



At a minimum, the toll free service access features in the subsections below shall be supported.


(a) Make Busy Arrangement. This feature shall permit the user to make one or more access lines within a service group appear busy by operation of user equipment (e.g., terminal) located at the agency subscriber’s premises or at the Government’s

C-74

option, by notification to the contractor (e.g., via telephone, E-Mail, etc.). The contractor shall provide the subscribing agency with the capability of busying-out individual circuits within a trunk group or an entire trunk group. The contractor shall provide an input system such that the subscribing agency shall have the capability of entering the needed information. The input system shall be such that the subscribing agency can busy out multiple lines within a trunk group with one entry (i.e., a separate entry for each line is not required). The contractor shall execute all subscribing agency-entered requests within one hour. The contractor shall be responsible for providing software necessary for the subscribing agency to utilize this feature on a subscribing agency-provided terminal.


None.




(1) All analog transmission parameters shall satisfy at least the values and ranges set forth in Section 7, Transmission, BOC Notes on the LEC Networks (Bellcore Pub: SR-TSV-002275).


(b) GOS

(1) For switched access arrangement and dedicated - Class 2 access arrangement trunk groups, the blockage for toll free services shall be 3 percent or less.

C-75


(1) For toll free services access shall provide an availability of at least 99.8 percent.





The contractor shall support the following interfaces at the SDP at the call terminating end for the provisioning of toll free services access.


(a) Analog Line

(1) Two- and four-wire access circuits (Standard: Bellcore’s BOC Notes on the LEC Networks [SR-TSV-002275])

(b) Analog Trunk

(1) Two-wire loop start or ground start access circuit (Standard: Bellcore’s BOC Notes on the LEC Networks [SR-TSV-002275])


(c) Digital Trunk

(1) T1 channelized (with ESF format) at line-rate of 1.544 Mb/s and information-payload data rate of 1.536 Mb/s. (Standard: Bellcore’s BOC Notes on the LEC Networks [SR-TSV-002275], and ANSI T1.102/107/403)

(2) ISDN PRI at line-rate of 1.544 Mb/s and information-payload data rate of 1.472 Mb/s for (23B+D) and 1.536 Mb/s for (24B+0D). (Standard: ANSI T1.607 and 610)

C-76

(3) SS7 Signaling Interface (Standard: ANSI [T1. 110 through T1.116 and T1.611] and Bellcore GR-246-CORE)



Table C.2.2.3.1.4.1.1-1. Mandatory User-to-Network Interface for Toll Free Services

UNI Type

Interface Type Payload Data Rate or Bandwidth

Signaling Type





3 Analog trunk: Two-Wire

4 kHz Bandwidth Trunk - Loop Signaling (loop/ground start)




6 Digital Trunk: ISDN PRI (T Reference Point)


7 T3 Channelized Up to 43.008 Mb/s SS7, T1 Robbed-Bit Signaling

C.2.2.3.1.4.1.2 Optional

(a) Digital Trunk


(b) Digital Line

(1) ISDN BRI (Standard: ANSI T1.607 and 610)

C-77


Table C.2.2.3.1.4.1.2-1. Optional User-to-Network Interface for Toll Free Services

UNI Type


Signaling Type

1 SONET OC-1 49.536 Mb/s SS72 Digital Line:

ISDN BRI (S and T Reference Point)


ITU-TSS Q.931


Pursuant to Section C.2.1.16, the contractor shall support/provide the following interfaces to connect to a POP listed for the provisioning of toll free services access.


(a) Mandatory




(4) Analog (Bellcore Pub: SR-TSV-002275)

(b) Optional



(a) Mandatory


C-78




(b) Optional

(1) None

C.2.2.3.2 Toll Free Services Transport Requirements


The toll free service shall allow the caller to be connected from on-net or off-net locations to predesignated stations or locations by dialing certain toll free and message-unit-free service access code numbers (e.g., 800 and 888).

The toll free services shall comply with all Bellcore and ANSI standards, primarily Bellcore’s BOC Notes on the LEC Networks, and ANSI ISDN and SS7 standards.

Pursuant to Section C.2.1.16, the contractor shall provide toll free services connections between the contractor’s listed POPs. The contractor shall accept at any of its listed POPs which support the appropriate on-net service, originating toll free service calls via switched access arrangement from the associated access providers. The contractor shall hand off terminating toll free service calls via dedicated and/or switched access arrangement from any of its listed POPs which support the appropriate on-net service.

The toll free services shall be available from on-net and off-net locations. For domestic services, numbering shall be consistent with 800, 888, and other toll free service access codes services. For non-domestic service, numbering shall be consistent with requirements or practices in the host country or shall be consistent with toll free domestic service where no standard exists. Therefore, the contractor shall accept, as a minimum, at any of its listed POPs which support the appropriate service, calls originating from the PSN.

C-79

The toll free service contractor shall accommodate the presently assigned Government 800 and 888 numbers. It shall be possible to assign Government requested 800 and 888 “vanity” numbers (e.g., 1-800-CALLGSA), as available. In addition, the contractor shall support number portability when a user moves its existing toll free service to the contractor’s toll free service. Also, when a user moves its existing toll free service from the contractor’s network the available toll free number shall be released by the contractor.

The toll free service contractor shall provide network intercept to recorded announcements as an inherent network capability when a call cannot be completed. At a minimum, such announcements shall be provided for the following conditions: time out during dialing, network congestion, denial of access to off-net and non-domestic calls, denial of access to features, and other related conditions. As a default, at the subscribing agency’s discretion the contractor shall provide a busy signal or recorded announcement for all calls encountering network congestion and/or terminating egress congestion.

The contractor shall provide a means for tracing any call made to an agency’s toll free number.



The toll free service transport features in the subsections below shall be supported. These features shall be capable of being used independently of each other or in any combination except where noted.

The combination of features associated with routing functions unique to each toll free number will constitute a Call Routing Plan. The maximum permissible size of a Call Routing Plan shall be at least 5,000 nodes. Call Routing Plans shall be subject to programmable control by the subscribing agency via the Routing Control feature described in this section.


The contractor shall provide the capability to have all mandatory announcements recorded and stored in English and Spanish.

C-80

(a) Toll Free Number Assignment and Maintenance. This feature shall allow users to request assignment and maintenance of toll free numbers.

(b) Terminating Announcement. This feature shall permit calls to be directed and terminated to a network recorded announcement scripted by the user and recorded by the contractor or to a contractor provided generic announcement to assist in the completion of calls. The recorded announcement may be toll free number specific or site specific as specified by the agency subscriber. This feature need not be a stand-alone feature. The purpose of this announcement is to provide the caller further information on the disposition of the call. The contractor shall provide capability for announcements up to two minutes in length. Such announcements shall always be played from the beginning for each caller. The recorded announcement shall be made available in either voice or electronic form as specified by the subscriber. When recorded announcement in electronic form is specified, the message must be receivable by the callers’ terminal (e.g., Telecommunications Device for the Deaf [TDD]) designed to transmit/receive information in Baudot or American Standard Code for Information Interchange/Teletypewriter (ASCII/TTY) code formats. When so specified, there is no requirement for the same dialed number to service voice as well.

(c) In-Route Announcements. This feature shall permit an announcement up to two minutes in length to be played to callers during call setup at any point without affecting the final destination/route of the call. The contractor shall provide for all the capabilities associated with recorded announcements (see Section C.2.2.3.2.2.1(b)). An example of an application for this feature is an announcement that might say “Thank you for pressing 2. Please have your account number ready as we route your call.”

(d) Routing Control. This feature shall permit the user to review, create, validate, change, or execute his call routing plans via a terminal located at the subscribing agency premises. The contractor shall provide adequate security procedures that will prevent unauthorized access to this feature. The contractor shall provide any hardware/software (e.g., terminal, modem) necessary to permit the user to utilize this feature. A user may provide its own terminal equipment when it meets contractor-provided specifications. Subscribing agencies shall have direct access to this feature a minimum of 20 hours a day, 7 days a week. The feature shall be available with no break during the period from 6:00 AM to 12:00 midnight, local prevailing time. The contractor shall support a minimum of 12 predefined alternative call routing plans for a subscribing agency.

C-81

Uploading of a call routing plan shall be completed no later than 15 minutes after the uploading procedure is completed by the user. Validation of routing plans shall be completed 15 minutes after completion of the upload. Execution of a validated routing plan shall be accomplished within 15 minutes of notification to the contractor.

(e) Dialed Number Identification (DNI). This feature shall permit a user with multiple toll free numbers in the same service group to identify electronically the specific toll free number that was dialed by the calling party.

(f) Interactive Announcement/Response Arrangement. This feature shall be available 24-hours a day, 7 days a week, and shall permit callers to hear generic or agency-specific information after dialing a toll free number. In conjunction with interactive prompting, the contractor shall provide a means for callers to:

(1) Select via DTMF signal, pre-recorded informational messages. The contractor shall provide capability for announcements up to two minutes in length. Such announcements shall always be played from the beginning for each caller. The contractor shall provide the capability to have the announcements recorded and stored in English and other languages after obtaining subscribing agency script approval.

(2) Leave caller information via DTMF signal or speech (e.g., names, addresses, account information, phone numbers, responses).

(3) Query a database (via DTMF) that delivers agency-provided information (e.g., the address of the nearest subscribing agency office in response to the caller entry of his or her residential zip code). The database may be housed in the subscribing agency or, at the subscribing agency’s discretion, housed in a contractor location and updated by the subscribing agency. If housed in the subscribing agency, the user will be responsible for providing connections to the contractor’s system. Database queries shall be via Transmission Control Protocol (TCP)/IP, User Datagram Protocol (UDP)/IP or LU 6.2 protocols at the agency’s discretion.

The contractor shall also provide a similar capability to allow callers to hear and verify their names and addresses in an agency-provided name and address database after the caller has entered their telephone number via DTMF, or based on the caller’s ANI. The matched street name shall then be spoken back to the caller to verify the correct address.

C-82

The contractor shall provide a means for verification of caller entered information. For example, after callers have entered a date, the contractor’s system shall ask the caller to verify (e.g., by pressing or saying “one”) that they just entered, for example, “October 25, 1998”.

To accommodate callers with dial-pulse telephone sets, the contractor shall support speech recognition as a valid caller input. The contractor shall support at a minimum, all spoken numeric digits as well as “yes” and “no.” English and Spanish language callers shall be supported. The contractor shall be able to accept and process at a minimum 95 percent of the above speech responses. The speech responses which are not accepted shall at the Government’s option be routed to a contractor’s operator for assistance or to the subscribing agency’s default routing.

The contractor shall provide a means for the subscribing agency to retrieve caller-entered DTMF or speech messages.

Features equivalent to the above shall be available to individuals who are deaf, hard of hearing or have speech disabilities via electronic means in Baudot and ASCII/TTY code formats. These electronic form lines need not be voice feature enabled.

(g) Percentage Routing. This feature shall permit calls to be distributed between two or more agency subscriber locations and/or service groups based on an agency subscriber’s specified percentage distribution from zero percent to 100 percent in one percent increments.

(h) NPA/NXX Routing. This feature shall permit calls originating from within agency subscriber-selected geographic areas, defined by one or more NPAs and/or NPA/NXX combinations, to be routed to an agency subscriber specified location. Where NPA/NXX is not available, calls shall be routed to an agency defined default location.

(i) ANI-Based Routing. This feature shall permit calls to be routed based on the full ANI of the callers. Default routing defined by the subscribing agency shall be used if ANI is not available.

(j) Time of Day Routing. This feature shall permit calls to be routed to different agency specified locations depending on the time of day. At least 48 time of day increments shall be allowed with minimum separation of 15 minutes between time increments.

C-83

(k) Day of Week Routing. This feature shall permit calls to be routed to different agency specified locations depending on the day of the week.

(l) Command Routing. This feature shall permit an agency subscriber who has subscribed to one or more of the above routing features to route calls differently (i.e., select a different predefined routing path alternative) on command at any time. This feature is dependent upon one or more of the above features. For example, under Percentage Routing where the paths of 20 percent, 30 percent, and 50 percent have been previously defined, the subscribing agency shall be able to select on command a path that is different from the currently-active path. The command may be issued from a subscriber’s command terminal (See Routing Control feature) or orally via call-in through authorized personnel. The routing command shall be executed within 10 minutes of issuance. The contractor shall provide adequate security procedures that can be used to prevent unauthorized activation of this feature. The contractor shall also support a minimum of 12 predefined alternative call routing plans for a subscribing agency.

(m) Cascade Routing. This feature shall permit the destination of calls to be changed on a subscribing agency-defined predetermined basis based on the availability of egress circuits at the original subscribing agency SDP destination. The contractor shall provide for the capability of a call to be rerouted within the contractor’s network to a second (or third or fourth, and so on) subscribing agency SDP if all egress circuits are occupied at the original SDP or if a subscribing agency predefined threshold of calls in progress at the original SDP is exceeded or if the subscribing agency does not respond to ringing. Up to 99 such SDP locations shall be made available in a sequence to be defined by the subscribing agency. If none of the terminations are able to accept that call, then the call shall be, at the subscribing agency’s option, terminated in a predefined user agency terminations announcement or to network queuing feature (see Section C.2.2.3.2.2.1(o)) until a termination becomes available, or to a busy signal.

(n) Network Call Distributor Routing. This feature shall provide call routing capabilities based on real-time information obtained from the subscribing agency’s automatic call distributors.

The contractor shall poll all of the subscribing agency’s ACDs every 20 to 60 seconds for real-time ACD operating status information to update a call routing processor which shall use call routing logic/algorithms that have been predefined by the agency, to determine the best location to terminate the inbound call.

C-84

Real-time ACD operating status reflects the agency’s current call center operating condition. The call routing processor containing the call routing logic/algorithms shall be able to use, in subscribing agency defined combinations, all real-time operating status information collected from the agency’s ACDs.

The type of ACD information that shall be polled at a minimum shall include:

(1) Number of incoming trunks

(2) Number of incoming trunks available to receive a call

(3) Queue size

(4) Number of calls in queue

(5) Average delay in queue

(6) Number of answering agents logged on

(7) Number of answering agents unavailable to answer a call (e.g., engaged in after-call wrap-up work)

(8) Number of answering agents available to answer a call

(9) Number of answering agents available to answer a call by skill group

(10) Longest available answering agent

(11) Average speed of answer

(12) Average call handling time (includes agent talk time and after-call wrap-up work)

(13) Number of calls abandoned

(14) Average time to abandonment

C-85

The type of network information that shall also be available to the call routing processor for utilization by the call routing logic/algorithms shall include:

(15) The dialed toll-free number(16) The caller’s originating 10 digit number(17) The caller’s entered digits

Call routing logic/algorithms that shall be accommodated at a minimum shall include:

(18) Routing to the most idle answering agent(19) Routing to the most idle answering agent by skill group(20) Routing based upon expected wait times(21) Routing based upon least cost.

This feature shall be capable of processing up to 100 incoming calls per second per toll-free number without any degradation in performance. Degradation means failure of the call routing processor to return the correct routing response more than one time per every 100,000 incoming calls.

The call routing processor shall not be unavailable for more than one second at a time, and shall not be unavailable for more than two seconds in any hour, and shall not lose information.

The contractor shall permit the call routing processor up to 250 milliseconds from receipt of a call query to respond with the destination (or next node). In the event that the 250 milliseconds is exceeded, the contractor shall route the call using a default routing plan previously defined by the subscribing agency.

The contractor shall provide all software and hardware necessary for subscriber agency access, via a graphical user interface, to the call routing processor to permit agency definition of the call routing logic/algorithms.

The subscribing agency will be responsible for providing telecommunication connections to the contractors system.

C-86

The feature shall be offered in two versions:

(22) Contractor-provided and contractor-based

(i) All necessary software and hardware required for the provision of this feature (e.g., call routing processor but not the ACD) shall be provided by the contractor and shall be housed (i.e., physically located) within the contractor’s network.

(23) Contractor-provided and agency-based

(i) All necessary software and hardware required for the provision of this feature (e.g., call routing processor but not the ACD) shall be provided by the contractor and shall be housed at the subscribing agency’s designated location.

When housed at the agency’s location, the contractor shall permit the ability to incorporate a look-up from a subscribing agency database external to the call routing processor using IBM O/S 390 SNA LU6.2 (APPC), TCP/IP, or UDP at the agency’s discretion.

(o) Network Queuing. This is a hybrid routing/announcement feature that shall allow a caller to be held in queue in the contractor’s network until a subscribing agency’s terminating SDP(s) becomes available to receive the call. Upon entering the queue, the caller shall hear an initial announcement, and shall hear a reassurance announcement every 30 seconds thereafter. The subscribing agency shall be able to define the time for calls that can be held in queue, up to 15 minutes before being sent to a terminating announcement. The contractor shall be responsible for recording announcements after subscribing agency script approval. This feature need not be a stand-alone feature.

(p) Agency Based Routing Database. This feature shall permit queries to a subscribing agency provided call routing processor which will allow call by call routing based upon information returned from the agency’s call routing processor.

The contractor shall provide a call by call query to a subscribing agency provided call routing processor housed at the subscribing agency’s location. The query shall contain at a minimum:

C-87

(1) The dialed toll-free number(2) The caller’s originating 10 digit number(3) The caller’s entered digits

When queried, the agency’s call routing processor will return a destination (or next node) instruction to the contractor’s call routing system along with (at the agency’s discretion) an identification number for the call to be transported by the contractor with the call (similar in fashion to the transport of a Dialed Number Identification Service [DNIS] code). The contractor shall permit a minimum of 250 milliseconds from agency receipt of the query for the agency’s call routing processor to return a routing instruction to the contractor’s call routing system.

If the agency’s routing processor does not respond to the network query in 250 milliseconds, an agency defined default routing shall be used.

The feature shall be capable of processing up to 100 call inquiries per second per toll-free number without any degradation in performance. Degradation means failure of the call routing processor to return the correct routing response more than one time per every 100,000 incoming calls.

The agency’s routing processor will be connected to the contractor’s network by dedicated access. The agency will be responsible for providing telecommunication connections to the contractor’s system. The contractor shall be responsible for providing any communications software necessary for the connection.

If the subscribing agency is using multiple call routing processors, the contractor shall provide a query to the appropriate call routing processor as mutually agreed upon by the subscribing agency and the contractor.

(q) Call Redirection. This feature shall allow an incoming toll free call to be transferred by the called party/agent to another toll free number or any PSN number by utilizing, at the Government’s discretion, any one of the three modes of call transfer: (i) blind transfer, (ii) verification by the agent that the called number is not busy and then transfer, or (iii) three-way conference and then transfer. In addition, the contractor shall provide for up to a minimum of 2,000 speed-dial codes for use of this feature.

C-88

(r) Call Prompter Routing. This feature shall allow callers to be routed to various network locations by dialing via DTMF or speaking specific route selection information. Once a caller has been connected, the network shall provide a recorded announcement identifying one or more DTMF selection digits that will provide further routing of the call. An example of an application for this feature is a taxpayer who wants information from an Internal Revenue Service (IRS) Regional Information Center. After dialing the IRS commercial toll free number, the caller would receive a recorded announcement instructing him/her to “press 2 to ask for tax forms, 4 to file late tax returns, 6 to register complaints,” etc. After dialing 6, for example, the caller would be routed to a location/station of the IRS complaint department.

The contractor shall support multi-tiered prompting such that another series of options can be provided to the caller after making the initial selection. An example of an application for this feature is a citizen who wants information from the Social Security Administration regarding a retirement claim. After dialing the Social Security Administration commercial toll free number, the caller would receive a recorded announcement instructing him/her to “press 1 for a benefit estimate, press 2 for a retirement information, press 3 for disability information,” etc. After pressing 2, for example, the caller would receive another recorder announcement instructing him/her to “press 1 for information on how to file, press 2 for discussing a claim recently filed,” etc. The contractor shall support a minimum of 8 options per tier and 3 tiers per call.

At the Government’s option at the initial call connection to the agency location, the caller’s selection(s) shall be passed to the agency in a manner similar to DNI or ANI information transfer.

To accommodate callers with dial-pulse telephone sets, the contractor shall support speech recognition as a valid caller input. The contractor shall support at a minimum, all spoken numeric digits as well as “yes” and “no.” English and Spanish language callers shall be supported. The contractor shall be able to accept and process at a minimum 95 percent of the above speech responses. The speech responses which are not accepted shall at the Government’s option be routed to a contractor’s operator for assistance or to the subscribing agency’s default routing.

(s) Call Prompter Routing - Electronic Access. This feature shall permit callers with terminals designed for individuals who are deaf, hard of hearing, or have speech disabilities to have access to a toll free number and receive prompts and/or selection instructions displayed in electronic form and enter desired selections. This feature shall support callers’ terminals (e.g., TDD) transmitting or receiving

C-89

information in Baudot Code and/or ASCII format. These electronic access lines are separately ordered and not part of the Federal Information Relay Service.

(t) Call Status Report. This report shall provide the subscribing agency with information about the status of calls placed to each toll free number. The contractor shall provide this information on a daily, weekly, monthly, and quarterly basis. Daily, weekly, monthly, and quarterly reports shall contain information summarized in 60 minute increments. Multiple report formats shall be available which further summarize the information by time zone or subscribing agency region.

All time indicators within the report will be set to Eastern Prevailing Time with presentation of hours using either a 24 hour clock or a 12 hour clock with an AM/PM indicator.

Unless affected by a weekend or a Federally-observed holiday, reports for a given day shall be available within 24 hours after the end of any given day or by 6:00 AM or the first Government business day after the weekend or holiday. For example, the report for a Friday shall be available by 6:00 AM on Monday. Refer to Section C.3.2.7 for the media of delivery and Section F for other deliverable requirements. Electronically delivered reports defined above shall have, as alternative delivery protocols the following:

(1) Network Data Mover™ (using System Network Architecture [SNA]/System Network Interconnect [SNI])

Each report shall contain standard information including:

(1) The title of the report(2) The date of the report(3) The period covered by the report(4) Name of the subscribing agency(5) The toll free number

For any given toll free number, the contractor shall, at a minimum, provide the following information within the reports:

(6) The number of calls from each area code that dialed the toll free number (i.e., call attempts)

C-90

(7) The number of calls and the percentage of all calls that encounter a busy signal (i.e., that are blocked):

(i) In the contractor’s network(ii) At the user’s terminating access

(8) The number of calls offered to the user’s terminating access (i.e., egress trunk group)

(9) The number of calls received at each user’s terminating access

(10) The number of received calls at each user’s terminating access that resulted in successful answerback supervision

(11) The average duration of calls answered at each user’s terminating access

(12) The average duration of all calls answered for a given toll free number at all users terminating access serving the toll free number

For any given toll free number utilizing Call Prompter Access, the contractor shall, at a minimum, provide the following information within the reports:

(13) The number of calls offered to the call prompter

(14) The number of calls to the call prompter that were abandoned without making a selection

(15) The average duration of all calls while in the caller prompter

(16) The number and percentage of calls selecting each option

For any given toll free number utilizing Interactive Announcement/Response Arrangement (IA/RA), the contractor shall, at a minimum, provide the following information within the reports by application:

(17) The number of calls offered to the IA/RA

(18) The number of calls completed (i.e., successfully accessing) to the IA/RA

(19) The number and percentage of calls completed to the IA/RA but abandoned

C-91


(21) The average duration of calls selecting each option

For any given toll free number utilizing Terminating Announcement or In-Route Announcements, the contractor shall, at a minimum, provide the following information within the reports:

(22) The number of calls offered to the announcement

(23) The number of calls blocked at the announcement

(24) The number of calls completed in the announcement

(25) The average duration of calls to each announcement

(26) The number of abandoned calls for In-Route announcements

For any given toll free number utilizing Cascade Routing, the contractor shall, at a minimum, provide the following information within the reports:

(27) The number of calls that were rerouted to an alternate SDP (Cascade Routing) or toll free service group (Alternate Routing)

(u) Caller Profile Report. The following caller information, at a minimum, shall be provided:

(1) Lost Callers. The number of callers who never called back after an incomplete attempt during the reporting period.

(2) Average Number of Attempts Per Caller. The grand total number of call attempts divided by the number of first call attempts during the reporting period.

(3) Average Number of Contacts Per Caller. The number of attempts generated from each telephone number on average during this reporting period. This is calculated by dividing the total number of first call attempts by the total number of unique telephone numbers from which the calls were made.

C-92

(4) 50 Percent of Successful Attempts Within 1,000 Calls. Represents the number of attempts it took to access the network for 50 percent of the callers who completed.


Unless affected by a weekend or a Federally-observed holiday, reports shall be available within 24 hours after the end of any given day or by 6:00 AM the first Government business day after the weekend or holiday. Refer to Section C.3.2.7 for the media of delivery and Section F for other deliverable requirements. Electronically delivered reports defined above shall have, as alternative delivery protocols the following:

(1) Network Data Mover™ (using SNA/SNI)

(v) Caller Information Report. This report provides information about the ANI of all callers to a given toll free number. The Government recognizes that ANI, although available in most cases, is not yet being universally provided. In those instances where ANI is not available, the NPA or NPA-NXX (as available) of the caller shall be provided. Zeroes shall be substituted in place of any missing digits.

For any given toll free number, the contractor shall, at a minimum, provide the following information within the report regarding each call:

(1) Date of call

(2) Time of call (expressed using either a 24 hour clock or a 12 hour clock with an AM/PM indicator, eastern prevailing time)

(3) ANI of caller (if available)

(4) Dialed (i.e., destination) 10 digit number

(5) Duration of call (to the nearest 6 seconds)

(6) Disposition of call (i.e., using an alpha or numeric code to include at a minimum the following:

(i) Call blocked within contractor’s network

C-93

(ii) Call blocked at user’s terminating access

(iii) Call completed to user’s terminating access

(iv) Other (e.g., caller abandoned enroute to user’s terminating access, no answer back supervision received, etc.)

The contractor shall provide this information on a daily basis and shall present information chronologically sequenced. Unless affected by a weekend or a Federally-observed holiday, reports shall be available within 24 hours after the end of any given day or by 6:00 AM the first Government business day after the weekend or holiday. Refer to Section C.3.2.7 for the media of delivery and Section F for other deliverable requirements. Electronically delivered reports defined above shall have, as alternative delivery protocols the following:


(w) Caller Response Report. The contractor shall be able to retrieve, format and provide caller-entered DTMF or speech messages and provide such information to subscribing agency. Unless affected by a weekend or a Federally-observed holiday, reports shall be available within 24 hours after the end of any given day or by 6:00 AM the first Government business day after the weekend or holiday. Refer to Section C.3.2.7 for the media of delivery and Section F for other deliverable requirements. Electronically delivered reports defined above shall have, as alternative delivery protocols the following:


(x) Real-Time Call Status. This feature shall permit the user to receive information about the status of the calls in progress on a near real-time (e.g., refreshed within five minutes) basis. The contractor shall provide all necessary hardware/software (including terminals) to provide this information in a graphical format to the subscribing agency. The user will be responsible for providing connections to the contractor’s system. At a minimum, the contractor shall provide the following:

(1) The number of calls from each area code who have dialed a given toll free number.

(2) The number of calls directed to a subscribing agency’s terminating SDP.

C-94

(3) The number of calls directed to a subscribing agency’s terminating SDP(s) that could not be completed (i.e., connected to the users premise equipment) due to an All-Trunks-Busy (ATB) condition.

(4) The percentage of trunks busy at a users terminating SDP.

(5) Any other reports or information available to commercial users.

(y) Operator Connect Bridging. This feature shall allow toll free inbound calls to connect directly to the contractor’s operator allowing the caller to speak with the operator (at any time, rather than continue to prompt through messages) based either on caller’s prompt defined in the announcement or announcement logic. The contractor’s operator shall assist the caller in reaching an agency location based on agency pre-determined default routing.

(z) FAX Catalog. This feature shall permit callers to retrieve documents or forms from an agency-specific FAX catalog (i.e., contractor’s database) by dialing an agency-specific toll free number. It shall be possible for an agency to store and update documents in the FAX catalog by dialing a toll free number and using a Group-III compatible FAX terminal (e.g., a FAX machine or a PC equipped with FAX modem). Once a document is stored in the FAX catalog, it shall be immediately made available to the callers for retrieval. Callers shall be able to interact with the contractor’s FAX catalog system, using DTMF prompts, to request one or more documents to be faxed to the caller’s Group-III compatible FAX terminal. The contractor shall FAX requested document(s) within one hour after the call. If the caller’s FAX machine is busy or experiencing problems, the contractor shall retry for a minimum of 13 attempts over a six hour period to FAX requested document(s). Each FAX shall include a cover sheet, which could be customized to include an agency logo, to be defined at service ordering time.

(aa) Basic ATB Rerouting. This feature shall automatically route a toll free call to an agency predefined local PSN number when an ATB condition at the subscribing agency egress trunks is encountered.

(bb) Service Assurance Rerouting. This feature shall allow inbound toll free calls to be routed to a predefined announcement or agency defined telephone number, within five minutes, when a network problem(s) is encountered.


C-95

(a) User-to-User Signaling Via ISDN D-Channel. In order to support user-to-user signaling via ISDN D-channel during a call, the contractor shall accept and forward (i.e., relay) user-to-user signals from/to ISDN D-channels at the POPs where ISDN access arrangement is supported in accordance with ANSI T1 and ITU-TSS standards for ISDN and SS7.

(b) Custom Vocabularies. This feature shall allow subscribing agencies to create custom speaker-independent vocabularies of up to 2,000 words. Callers can then speak the name of the function they want rather than having to remember a numbered prompt and then provide a response via DTMF or speech recognition.

(c) Reserved

(d) Reserved

(e) Electronically Delivered Reports. Electronically delivered reports defined above shall have as alternative delivery protocols the following:

(1) Network Job Entry™

(2) Remote Job Entry™

(f) FAX Catalog. The contractor shall provide FAX machine compatibility for Group I and/or Group II FAX formats.

(g) Other Languages. The contractor shall provide the capability to have announcements recorded and stored in languages other than English or Spanish.



C-96



(b) GOS



(1) The toll free services transport shall provide an availability of at least 99.8 percent.





Pursuant to Section C.2.1.16, the contractor shall support/provide the following interfaces (i.e., LANI) at each POP listed for the provisioning of toll free services transport.


(a) Mandatory



(3) T3 and Fractional T3 channelized(Standard: Bellcore Pub: GR-499-CORE)


C-97

(b) Optional



(a) Mandatory





(b) Optional

(1) None

C.2.2.4 900 Services

The Government has a need to provide certain kinds of services to the public which is reimbursed by the applicable user community. It will use 900 services as one method for accomplishing that goal. The service must be reliable and feature rich in order to provide quality service to a paying community. The following sections provide the requirements for 900 Service.

C.2.2.4.1 900 Services Access Requirements


The 900 service shall allow the public to be connected from off-net locations to predesignated users and information providing systems (by dialing certain 900 [and its equivalent] service access code numbers), located at Government designated location(s), to receive information provided by prerecorded messages and in combination with voice

C-98

response systems or answering agents. The information to be provided by 900 service call-handling equipment could be passive (e.g., caller listens to prerecorded messages), interactive (e.g., the caller interacts with the message via menu of options, with selections made by pressing designated numbers on a DTMF telephone), opinion polls (e.g., call or peg counters for a basic yes or no, for or against, or choice A or B response to a question); and, database access from callers.

The 900 service shall comply with all Bellcore and ANSI standards, primarily Bellcore’s BOC Notes on the LEC Networks, and ANSI ISDN and SS7 standards.

Pursuant to Section C.2.1.16, the contractor shall provide dedicated access connections for the 900 service calls. Access connections shall connect the terminating POP with the 900 service on-net terminating locations.

Terminating access for 900 service shall be delivered directly to the user’s terminal equipment including but not limited to the following types: single-line telephones; multiline key telephone systems; electromechanical, analog, and digital PBXs; Centrexes; data circuit terminating equipment (9.6 kb/s using International Telegraph and Telephone Consultative Committee [CCITT] V.32 modem and 28.8 kb/s using CCITT V.34 modem); T1 multiplexer; CCITT Group I, II, and III FAX apparatus; ACDs; automated call-handling equipment (e.g., voice response/transaction processing systems) for providing opinion polling; and database access, and any other equipment typically found or proposed for use on user premises for connection to public and private switched voice networks. The interfaces to the user equipment types are defined in Section C.2.2.4.1.4.1.

The contractor shall provide network intercept to recorded announcements as an inherent network capability when a call cannot be completed. At a minimum, such announcements shall be provided for the following conditions: time out during dialing, network congestion, denial of access to non-domestic calls, denial of access to features, and other related conditions. As a default, the contractor shall provide a busy signal for all calls encountering network congestion and/or terminating egress congestion.

The contractor may exceed the basic requirements by providing:

(a) Switched Access. The contractor would provide switched access connections for the 900 service calls. Access connections would connect the terminating POP with the 900 service on-net terminating locations.

C-99

(b) Customized Network Intercept Messages. The contractor would provide the ability to have customized network intercept recorded announcements. The contractor would be responsible for recording the network announcements after obtaining Government approval of proposed scripts. The contractor would have the capability of implementing scripts customized for the Government.


The 900 service access features in the subsections below shall be supported.


None.


(a) Make Busy Arrangement. This feature shall permit the user to make one or more access lines within a service group appear busy by operation of user equipment (e.g., terminal) located at the agency subscriber’s premises or at the Government’s option, by notification to the contractor (e.g., via telephone, E-Mail, etc.). The contractor shall provide the subscribing agency with the capability of busying-out individual circuits within a trunk group or an entire trunk group. The contractor shall provide an input system such that the subscribing agency shall have the capability of entering the needed information. The input system shall be such that the subscribing agency can busy out multiple lines within a trunk group with one entry (i.e., a separate entry for each line is not required). The contractor shall execute all subscribing agency-entered requests within one hour. The contractor shall be responsible for providing all hardware (e.g., modem) and software necessary for the subscribing agency to utilize this feature on a subscribing agency-provided terminal.

C-100




(1) All analog transmission parameters shall satisfy at least the values and ranges set forth in Section 7, Transmission, BOC Notes on the LEC Networks (Bellcore Pub: SR-TSV-002275).


(b) GOS

(1) For Dedicated - Class 2 access arrangement trunk groups, the blockage for 900 service shall be 3 percent or less.


(1) For 900 service the access shall provide an availability of at least 99.8 percent.



C-101



The contractor shall support the following interfaces at the SDP at the call terminating end for the provisioning of 900 service access.


(a) Analog Line

(1) Two- and four-wire access circuits (Standard: Bellcore’s BOC Notes on the LEC Networks [SR-TSV-002275])

(b) Analog Trunk

(1) Two-wire loop start or ground start access circuit (Standard: Bellcore’s BOC Notes on the LEC Networks [SR-TSV-002275])


(c) Digital Trunk

(1) T1 channelized (with ESF format) at line-rate of 1.544 Mb/s and information-payload data rate of 1.536 Mb/s. (Standard: Bellcore’s BOC Notes on the LEC Networks [SR-TSV-002275], and ANSI T1.102/107/403)

(2) ISDN PRI at line-rate of 1.544 Mb/s and information-payload data rate of 1.472 Mb/s for (23B+D) and 1.536 Mb/s for (24B+0D). (Standard: ANSI T1.607 and 610)


C-102


Table C.2.2.4.1.4.1.1-1. Mandatory User-to-Network Interface for 900 Service

UNI Type


Signaling Type





3 Analog trunk: Two-Wire

4 kHz Bandwidth Trunk - Loop Signaling (loop/ground start)




6 Digital Trunk: ISDN PRI (T Reference Point)


7 T3 Channelized Up to 43.008 Mb/s T1 Robbed-Bit Signaling

C.2.2.4.1.4.1.2 Optional

(a) Digital Trunk


(2) SS7 Signaling Interface (Standard: ANSI [T1. 110 through T1.116 and T1.611] and Bellcore GR-246-CORE)

(b) Digital Line

(1) ISDN BRI (Standard: ANSI T1.607 and 610)

C-103


Table C.2.2.4.1.4.1.2-1. Optional User-to-Network Interface for 900 Service

UNI Type


Signaling Type

1 SONET OC-1 49.536 Mb/s SS72 T3 Channelized Up to 43.008 Mb/s SS73 Digital Line:

ISDN BRI (S and T Reference Point)


ITU-TSS Q.931


Pursuant to Section C.2.1.16, the contractor shall support/provide the following interfaces to connect to a POP listed for the provisioning of 900 service access.


(a) Mandatory





(b) Optional



(a) Mandatory

None

C-104

(b) Optional





C.2.2.4.2 900 Services Transport Requirements


The 900 service shall allow the public to be connected from off-net locations to predesignated users (e.g., answering agents) and information providing systems (by dialing certain 900 [and its equivalent] service access code numbers), located at Government designated location(s), to receive information provided by prerecorded messages and in combination with voice response systems. The information to be provided by 900 service call-handling equipment could be passive (e.g., caller listens to prerecorded messages), interactive (e.g., the caller interacts with the message via menu of options, with selections made by pressing designated numbers on a DTMF telephone), opinion polls (e.g., call or peg counters for a basic yes or no, for or against, or choice A or B response to a question); and, database access from callers.

The 900 service shall comply with all Bellcore and ANSI standards, primarily Bellcore’s BOC Notes on the LEC Networks, and ANSI ISDN and SS7 standards.

Pursuant to Section C.2.1.16, the contractor shall provide 900 service connections between the contractor’s listed POPs. The contractor shall hand off terminating 900 service calls via dedicated access arrangement from any of its listed POPs which support the appropriate on-net service.

The 900 services shall be available from off-net locations. Therefore, the contractor shall accept, as a minimum, at any of its listed POPs which support the appropriate service, calls originating from the PSN.

C-105

For 900 service calls, the contractor shall bill callers directly for call charges that have been agreed to between the contractor and the agency subscribing to the 900 service and the contractor shall bill GSA (or the agency, if the agency is directly billed) for the 900 service charges provided for in Section B. When the capability is commercially available from the contractor, the contractor shall accommodate the Federal Government’s currently assigned 900 numbers. Call charges to callers shall begin at a time set by agreement with the agency.

The 900 service shall block all 900 service calls from locations that are unbillable (e.g., pay phones and cellular phones for which ANI is not available).

The 900 service contractor shall provide network intercept to recorded announcements as an inherent network capability when a call cannot be completed. At a minimum, such announcements shall be provided for the following conditions: time out during dialing, network congestion, denial of access to off-net and non-domestic calls, denial of access to features, and other related conditions. As a default, the contractor shall provide a busy signal for all calls encountering network congestion and/or terminating egress congestion.

The contractor may exceed the basic requirements by providing:

(a) Switched Access. The contractor would provide 900 service connections between the contractor’s listed POPs. The contractor would accept at any of its listed POPs which support the appropriate on-net service, originating 900 service calls via switched access arrangement from the associated access providers. The contractor would hand off terminating 900 service calls via switched access arrangement from any of its listed POPs which support the appropriate on-net service to the associated access providers.

(b) Network Intercept to Customized Recorded Announcements. The contractor would have the capability of implementing scripts customized for the Government. The contractor would be responsible for recording customized network announcements after obtaining Government approval of proposed scripts.


The 900 service transport features in the subsections below shall be supported. These features shall be capable of being used independently of each other or in any combination except where noted.

C-106


The combination of features associated with routing functions unique to each 900 service number will constitute a Call Routing Plan. The maximum permissible size of a Call Routing Plan shall be at least 5,000 nodes. Call Routing Plans shall be delivered to the contractor via any normal delivery method including, but not limited to E-mail, voice telephone or U.S. Postal Service. The plan shall be executed within 2 hours of delivery or at a time specified in the plan.


The contractor shall provide the capability to have all mandatory announcements recorded and stored in English or Spanish.

(a) 900 Number Assignment and Maintenance. This feature shall allow users to request assignment and maintenance of 900 numbers.

(b) Preamble Message. The 900 service shall provide a preamble message stating the 900 call charges to the callers and providing the caller the opportunity to hang up without being charged. The contractor shall be responsible for recording the preamble message after obtaining Government approval of scripts.

(c) Terminating Announcement. This feature shall permit calls to be directed and terminated to a network recorded announcement scripted by the user and recorded by the contractor or to a contractor provided generic announcement to assist in the completion of calls. The recorded announcement may be 900-number specific or site specific as specified by the agency subscriber. This feature need not be a stand-alone feature. The purpose of this announcement is to provide the caller further information on the disposition of the call. The contractor shall provide capability for announcements up to two minutes in length. Such announcements shall always be played from the beginning for each caller. The recorded announcement shall be made available in either voice or electronic form as specified by the subscriber. When recorded announcement in electronic form is specified, the message must be receivable by the callers’ terminal (e.g., Telecommunications Device for the Deaf [TDD]) designed to transmit/receive information in Baudot or ASCII/TTY code formats. When so specified, there is no requirement for the same dialed number to service voice features as well.

(d) Dialed Number Identification. This feature shall permit the user with multiple toll free or 900 numbers in the same service group to identify electronically the specific toll free or 900 number that was dialed by the calling party.

C-107


(e) Interactive Announcement/Response Arrangement. This feature shall be available 24-hours a day, 7 days a week, and shall permit users to provide agency-specific dial-up information to callers dialing a 900 number. In conjunction with interactive prompting, the contractor shall provide a means for callers to:

(1) Select via DTMF signal, pre-recorded informational messages provided by the subscribing agency.

(2) Leave caller information via DTMF signal or speech (e.g., names, addresses, account information, phone numbers, responses).

(3) Query a database (via DTMF) that delivers agency-provided information (e.g., the address of the nearest subscribing agency office in response to the caller entry of his or her residential zip code). The database may be housed in the subscribing agency or, at the subscribing agency’s discretion, housed in a contractor location and updated by the subscribing agency. If housed in the subscribing agency, the user will be responsible for providing connections to the contractor’s system.

The contractor shall also provide a similar capability to allow callers to hear and verify their names and addresses in an agency-provided name and address database after the caller has entered their telephone number via DTMF, or based on the caller’s ANI. The matched street name shall then be spoken back to the caller to verify the correct address.

The contractor shall provide a means for the subscribing agency to retrieve caller-entered DTMF or speech messages.

Features equivalent to the above shall be available to individuals who are deaf, hard of hearing or have speech disabilities via electronic means in Baudot and ASCII/TTY code formats. These electronic format lines need not be voice feature enabled.

(f) Percentage Routing. This feature shall permit calls to be distributed between two or more agency subscriber locations and/or service groups based on an agency subscriber’s specified percentage distribution from zero percent to 100 percent in one percent increments.

(g) NPA/NXX Routing. This feature shall permit calls originating from within agency subscriber-selected geographic areas, defined by one or more NPAs and/or NPA/NXX combinations, to be routed to an agency subscriber specified location.

C-108


(h) Time of Day Routing. This feature shall permit calls to be routed differently depending on the time of day.

(i) Day of Week Routing. This feature shall permit calls to be routed differently depending on the day of the week.

(j) Command Routing. This feature shall permit an agency subscriber who has subscribed to one or more of the above routing features to route calls differently (i.e., select a different predefined routing path alternative) on command at any time. This feature is dependent upon one or more of the above features. For example, under Percentage Routing where the paths of 20 percent, 30 percent, and 50 percent have been previously defined, the subscribing agency shall be able to select, on command, a path that is different from the currently-active path. The command may be issued from a subscriber’s command terminal (See Routing Control feature) or orally via call-in through authorized personnel. The routing command shall be executed within 10 minutes of issuance. The contractor shall provide adequate security procedures that can be used to prevent unauthorized activation of this feature. The contractor shall also support a minimum of 12 predefined routing alternatives that can be accommodated by this feature.

(k) Call Status Report. This report shall provide the subscribing agency with information about the status of calls placed to each 900 number. The contractor shall provide this information on a daily, weekly, monthly, and quarterly basis. Daily, weekly, monthly, and quarterly reports shall contain information summarized in 60 minute increments. Multiple report formats shall be available which further summarize the information by time zone or subscribing agency region.

All time indicators within the report will be set to Eastern Prevailing Time with presentation of hours using either a 24 hour clock or a 12 hour clock with an AM/PM indicator.

Unless affected by a weekend or a Federally-observed holiday, reports for a given day shall be available within 24 hours after the end of any given day or by 6:00 AM or the first Government business day after the weekend or holiday. For example,

C-109


the report for a Friday shall be available by 6:00 AM on Monday. Refer to Section C.3.2.7 for the media of delivery and Section F for other deliverable requirements. Each report shall contain standard information including:

(1) The title of the report(2) The date of the report(3) The period covered by the report(4) Name of the subscribing agency(5) The 900 number

For any given 900 number, the contractor shall, at a minimum, provide the following information within the reports:

(6) The number of calls from each area code that dialed the 900 number (i.e., call attempts)

(7) The number of calls that encounter a busy signal (i.e., that are blocked):

(i) In the contractor’s network(ii) At the user’s terminating access

(8) The number of calls offered to the user’s terminating access (i.e., egress trunk group)

(9) The number of calls received at each user’s terminating access

(10) The number of received calls at each user’s terminating access that resulted in successful answerback supervision

(11) The average duration of calls answered at each user’s terminating access

(12) The average duration of all calls answered for a given 900 number at all users terminating access serving the 900 number

For any given 900 number utilizing Interactive Announcement/Response Arrangement (IA/RA), the contractor shall, at a minimum, provide the following information within the reports by application:

(13) The number of calls offered to the IA/RA

(14) The number of calls completed (i.e., successfully accessing) to the IA/RA

C-110


(15) The number and percentage of calls completed to the IA/RA but abandoned


(17) The average duration of calls selecting each option

For any given 900 number utilizing Terminating Announcement, the contractor shall, at a minimum, provide the following information within the reports:

(18) The number of calls offered to the announcement

(19) The average duration of calls to each announcement

(l) Caller Profile Report. The following caller information, at a minimum, shall be provided:

(1) Lost Callers. The number of callers who never called back after an incomplete attempt during the reporting period.

(2) Average Number of Attempts Per Caller. The grand total number of call attempts divided by the number of first call attempts during the reporting period.

(3) Average Number of Contacts Per Caller. The number of attempts generated from each telephone number on average during this reporting period. This is calculated by dividing the total number of first call attempts by the total number of unique telephone numbers from which the calls were made.



C-111


The contractor shall provide this information on a daily basis. Unless affected by a weekend or a Federally-observed holiday, reports shall be available within 24 hours after the end of any given day or by 6:00 AM the first Government business day after the weekend or holiday. Refer to Section C.3.2.7 for the media of delivery and Section F for other deliverable requirements.

(m) Caller Information Report. This report provides information about the ANI of all callers to a given 900 number. The Government recognizes that ANI, although available in most cases, is not yet being universally provided. In those instances where ANI is not available, the NPA or NPA-NXX (as available) of the caller shall be provided. Zeroes shall be substituted in place of any missing digits.

For any given 900 number, the contractor shall, at a minimum, provide the following information within the report regarding each call:

(1) Date of call

(2) Time of call (expressed using either a 24 hour clock or a 12 hour clock with an AM/PM indicator, eastern prevailing time)

(3) ANI of caller (if available)

(4) Dialed (i.e., destination) 10 digit number

(5) Duration of call (to the nearest 6 seconds)

(6) Disposition of call (i.e., using an alpha or numeric code to include at a minimum the following:

(i) Call blocked within contractor’s network

(ii) Call blocked at user’s terminating access

(iii) Call completed to user’s terminating access

(iv) Other (e.g., caller abandoned enroute to user’s terminating access, no answer back supervision received, etc.)

C-112


The contractor shall provide this information on a daily basis and shall present information chronologically sequenced. Unless affected by a weekend or a Federally-observed holiday, reports shall be available within 24 hours after the end of any given day or by 6:00 AM the first Government business day after the weekend or holiday. Refer to Section C.3.2.7 for the media of delivery and Section F for other deliverable requirements.

(n) FAX Catalog. This feature shall permit callers to retrieve documents or forms from an agency-specific FAX catalog (i.e., contractor’s database) by dialing an agency-specific 900 number. It shall be possible for an agency to store and update documents in the FAX catalog by dialing a toll free number and using a Group-III compatible FAX terminal (e.g., a FAX machine or a PC equipped with FAX modem). Once a document is stored in the FAX catalog, it shall be immediately made available to the callers for retrieval. Callers shall be able to interact with the contractor’s FAX catalog system, using DTMF prompts, to request one or more documents to be faxed to the caller’s Group-III compatible FAX terminal. The contractor shall FAX requested document(s) within one hour after the call. If the caller’s FAX machine is busy or experiencing problem, the contractor shall retry for a minimum of 13 attempts over a six hour period to FAX requested document(s). Each FAX shall include a cover sheet, which could be customized to include an agency logo, to be defined at service ordering time.


(a) Reserved

(b) Speech Responses. For those features above and below requiring DTMF response to Interactive Announcements, Fax Catalog/Form Ordering or special Routing features, it shall be possible to provide speech responses. To accommodate callers with dial-pulse telephone sets, the contractor shall support speech recognition as a valid caller input. The contractor shall support at a minimum, all spoken numeric digits as well as “yes” and “no.” The contractor shall be able to accept and process at a minimum 95 percent of the above speech responses. English and Spanish language callers shall be supported. The speech responses which are not accepted shall at the Government’s option be routed to an operator for assistance or to the subscribing agency’s default routing.

C-113


(c) In-Route Announcements. This feature shall permit an announcement up to two minutes in length to be played to callers during call setup at any point without affecting the final destination/route of the call. The contractor shall provide for all the capabilities associated with recorded announcements (see Section C.2.2.4.2.2.1(b)). An example of an application for this feature is an announcement that might say “Thank you for pressing 2. Please have your account number ready as we route your call.”

(d) Other Languages. The contractor shall provide the capability to have announcements recorded and stored in languages other than English and Spanish.

(e) Routing Control. This feature shall permit the user to review, create, validate, change, or execute his call routing plans via a terminal located at the subscribing agency premises. The contractor shall provide adequate security procedures that will prevent unauthorized access to this feature. The contractor shall provide any hardware/software (e.g., terminal, modem) necessary to permit the user to utilize this feature. A user may provide its own terminal equipment when it meets contractor-provided specifications. Subscribing agencies shall have direct access to this feature a minimum of 20 hours a day, 7 days a week. The feature shall be available with no break from 6:00 AM to 12:00 midnight, local prevailing time.

The following features shall give a user agency capability to have calls to a single 900 number directed to multiple agency locations and/or multiple groups of lines at the same agency location. The combination of these features unique to each 900 number will constitute a call routing plan and be subject to programmable control by the subscribing agency via the Routing Control Feature described above:

(f) ANI-Based Routing. This feature shall permit calls to be routed based on the full ANI of the callers. Default routing defined by the subscribing agency shall be used if ANI is not available.

(g) Cascade Routing. This feature shall permit the destination of calls to be changed on a subscribing agency-defined predetermined basis based on the availability of egress circuits at the original subscribing agency SDP destination. The contractor shall provide for the capability of a call to be rerouted within the contractor’s network to a second (or third or fourth, and so on) subscribing agency SDP if all egress circuits are occupied at the original SDP or if a subscribing agency predefined threshold of calls in progress at the original SDP is exceeded or if the subscribing agency does not respond to ringing. Up to 99 such SDP locations shall

C-114


be made available in a sequence to be defined by the subscribing agency. If none of the terminations are able to accept that call, then the call shall be, at the subscribing agency’s option, terminated in a predefined user agency termination announcement.

(h) Network Call Distributor Routing. This feature shall provide look-ahead routing capabilities by linking the subscribing agency’s ACDs to contractor’s routing processor. The contractor shall poll the subscribing agency’s ACDs every 20 to 60 seconds to pull in ACD statistics which shall be used, along with parameters that have been predefined by the agency, to determine the best location to terminate the inbound call.

(i) Agency Based Routing Database. This feature shall permit queries to a subscribing agency database that will allow call-by-call routing based on information from the agency’s routing processor. When queried by the contractor’s network call routing system, the agency routing processor will return a destination (or next node) instruction to the contractor’s call routing system. Agencies may develop and maintain their own software and algorithms which reside on their own workstations or may use contractor provided software; the contractor shall provide such software at no additional charge if required. The agency’s routing processor will respond to a network query in 20 milliseconds or default routing shall be used. Contractors may require certification of the agency’s routing processor before it is connected to their network call routing system. The agency’s routing processor will be connected to the contractor’s network by dedicated access.

(j) Call Prompter Routing(Additions). This feature shall allow callers to be routed to various network locations by dialing or speaking specific route selection information. Once a caller has been connected, the network shall provide a recorded announcement identifying one or more DTMF selection digits that will provide further routing of the call. An example of an application for this feature is a taxpayer who wants information from an IRS Regional Information Center. After dialing the IRS number, the caller would receive a recorded announcement instructing him/her to “press 2 to ask for tax forms, 4 to file late tax returns, 6 to register complaints,” etc. After dialing 6, for example, the caller would be routed to a location/station of the IRS complaint department.

The contractor shall support multi-tiered prompting such that another series of options can be provided to the caller after making the initial selection. An example of an application for this feature is a citizen who wants information from the Social Security Administration regarding a retirement claim. After dialing the Social Security Administration number, the caller would receive a recorded announcement

C-115


instructing him/her to “press 1 for a benefit estimate, press 2 for a retirement information, press 3 for disability information,” etc. After pressing 2, for example, the caller would receive another recorder announcement instructing him/her to “press 1 for information on how to file, press 2 for discussing a claim recently filed,” etc. The contractor shall support a minimum of 8 options per tier and 3 tiers per call.

To accommodate callers with dial-pulse telephone sets, the contractor shall support speech recognition as a valid caller input. The contractor shall support at a minimum, all spoken numeric digits as well as “yes” and “no.” The contractor shall be able to accept and process at a minimum 95 percent of the above speech responses. English and Spanish language callers shall be supported. The speech responses which are not accepted shall at the Government’s option be routed to an operator for assistance or to the subscribing agency’s default routing.

(k) Call Status Report (Additions). For any given 900 number utilizing Call Prompter Access, the contractor shall, at a minimum, provide the following information within the reports:

(1) The number of calls offered to the call prompter

(2) The number of calls to the call prompter that were abandoned without making a selection

(3) The average duration of all calls while in the caller prompter


For any given 900 number utilizing In-Route Announcements, the contractor shall, at a minimum, provide the following information within the reports:

(5) The number of calls offered to the announcement(6) The average duration of calls to each announcement

For any given 900 number utilizing Cascade Routing, the contractor shall, at a minimum, provide the following information within the reports:

(7) The number of calls that were rerouted to an alternate SDP (Cascade Routing) or 900 service group (Alternate Routing)

C-116


(l) Caller Response Report. The contractor shall be able to retrieve, format and provide caller-entered DTMF or speech messages and provide such information to the subscribing agency. Refer to Section C.3.2.7 for the media of delivery and Section F for other deliverable requirements.

(m) Real-Time Call Status Report. This report shall permit the user to receive information about the status of the calls in progress on a near real-time (e.g., refreshed within five minutes) basis. The contractor shall provide all necessary hardware/software (including terminals) to provide this information in a graphical format to the subscribing agency. At a minimum, the contractor shall provide the following:

(1) The number of calls from each area code who have dialed a given 900 number.

(2) The number of calls directed to a subscribing agency’s terminating SDP.

(3) The number of calls directed to a subscribing agency’s terminating SDP(s) that could not be completed (i.e., connected to the users premise equipment) due to an ATB condition.

(4) The percentage of trunks busy at a users terminating SDP.

(5) Any other reports or information available to commercial users.

(n) Electronically Delivered Reports. Electronically delivered reports defined as either mandatory or optional above shall have, as alternate delivery protocols, the following:

(6) Network Data MoverTM (using SNA/SNI)

(7) Network Job EntryTM

(8) Remote Job EntryTM

(o) Custom Vocabularies. This feature shall allow subscribing agencies to create custom speaker-independent vocabularies of up to 2,000 words. Callers can then speak the name of the function they want rather than having to remember a numbered prompt and then provide a response via DTMF or speech recognition.

C-117


(p) User-to-User Signaling Via ISDN D-Channel. In order to support user-to-user signaling via ISDN D-channel during a call, the contractor shall accept and forward (i.e., relay) user-to-user signals from/to ISDN D-channels at the POPs where ISDN access arrangement is supported in accordance with ANSI T1 and ITU-TSS standards for ISDN and SS7.

(q) FAX Catalog (Additions). The contractor shall provide FAX machine compatibility for Group I and/or Group II FAX formats.





(b) GOS



(1) The 900 service transport shall provide an availability of at least 99.8 percent.





Pursuant to Section C.2.1.16, the contractor shall support/provide the following interfaces (i.e., LANI) at each POP listed for the provisioning of 900 service transport.

C-118



(a) Mandatory





(b) Optional



(a) Mandatory

(1) None

(b) Optional





C.2.3 Switched Data Services

Government requirements for data connectivity have traditionally been met by individual private networks. Technology has evolved to the point where a common, high performance

C-119


data transport utility serving the Government community is feasible. The goal of the services which comprise SDS is to realize the economic and performance benefits that derive from having a true Government Information Infrastructure. These benefits include efficient use of resources, economy of procurement, a common security infrastructure, and a common platform to support cross-agency applications such as E-Mail and electronic commerce. Each of the four services described below addresses particular needs within the data communications community.

C.2.3.1 Packet Switched Service

This service, based on the X.25 protocol, is the traditional solution to the problem of consolidating multiple networks using different protocols. It provides reliable end-to-end connectivity at moderate transmission speeds. The Government has an installed base of PSS users. The following sections provide the requirements for PSS.

C.2.3.1.1 Packet Switched Service Access Requirements


PSS shall provide a packet-switched, connection-oriented, data transmission service at data rates up to DS0.

PSS shall conform to the ITU-TSS X.25/X.28/X.29/X.3/X.32/X.121 and optionally X.75 recommendations, Federal Information Processing Standard-Publication (FIPS-PUB) 100-1, Federal-Standard (FED-STD) 1013/1020A/1030A/1033, and ANSI T1.504/614. The contractor shall support packet lengths of 64, 128, 256, 512 and 1024 bytes, at a minimum.

Pursuant to Section C.2.1.16, the contractor shall provide dedicated, and optionally internetworked originating and/or terminating access connections for PSS calls. Originating access connections shall connect PSS on-net originating locations with the associated POP. Terminating access connections shall connect the terminating POP with PSS on-net terminating locations.

C-120


PSS access shall be delivered directly to the user’s terminal equipment. The user’s terminal may be either “packet-mode DTE” which supports X.25 protocol or “non-packet-mode DTE or terminal,” which does not support X.25 protocol. User equipment supported shall include, but not be limited to, multiplexing/switching devices such as PBXs, channel banks, routers, or Multiplexers; DTE (or packet-mode DTE); asynchronous ASCII terminals; IBM Binary Synchronous Communications (BSC) protocol terminals; IBM SNA/Synchronous Data Link Control (SDLC) terminals; Unisys Poll/Select terminals. The contractor shall provide Packet Assembly/Disassembly (PAD) capability. The interfaces to these equipment types are defined in Section C.2.3.1.1.4.1.

The contractor may exceed the basic requirements by providing PSS access via internetworked access arrangement (see Section C.2.1.16). When this access is provided the following additional capabilities would be supported:

(a) The capability for a DTE to send and receive data by setting up Permanent Virtual Circuits (PVC) and/or Switched Virtual Circuits (SVC).

(b) The capability to support a numbering plan that would follow the ITU-TSS X.121 numbering plan.

(c) The contractor would support the following capabilities as specified in FIPS-PUB 100-1:

(1) Reverse charging

(2) Reverse charging acceptance

(3) Local charging prevention

(4) Nonstandard default packet size

(5) Nonstandard default window size

(6) Incoming calls barred

C-121


(7) Outgoing calls barred

(8) One-way logical channel outgoing

(9) One-way logical channel incoming

(10) Default throughput classes assignment

(11) Flow control parameter negotiation

(12) Throughput class negotiation

(13) Closed User Group (CUG)-related facilities, including CUG with outgoing access, CUG with incoming access, incoming calls barred within user group, outgoing calls barred within user group, bilateral CUG, bilateral CUG with outgoing access, and CUG with outgoing access selection

(14) Fast select

(15) Fast select acceptance

(16) Hunt group facilities, including round robin, closest, and ordered list

(17) Support for throughput classes of 1.2 kb/s, 2.4 kb/s, 4.8 kb/s, 9.6 kb/s, through 48 kb/s

(18) Transit delay selection and notification

(19) Abbreviated address calling

(20) Charging information

(21) Call redirection notification

(22) Called line address modification notification

(23) On-line facilities registration

(24) Extended packet sequence numbering (modulo 128)

C-122


(25) Packet retransmission

(26) Multilink procedure

(27) Direct call

(28) D-bit modification

(29) Call redirection

(30) Network User Identification (NUI)

(31) Extended frame sequence numbering

(32) Call deflection subscription

(33) Call deflection selection


The following PSS access features shall be supported.


None.C.2.3.1.1.2.2 Optional

None.C.2.3.1.1.3 Performance

The access performance parameters for originating or terminating access between a POP and an SDP shall meet the following:


(1) For dedicated access arrangements, the PSS access delay shall not exceed the delay caused by the access line speed.

C-123


(b) Availability of Service

(1) The availability of the PSS access shall be at least 99.8 percent.



The contractor shall support the following interfaces at the SDP for the provisioning of PSS access.


(a) DTE (Packet-Mode and Non-Packet-Mode)

(1) Interface

(i) ITU-TSS V.35(ii) EIA RS-232(iii) EIA RS-422(iv) EIA RS-449(v) EIA RS-530(vi) ISDN PRI (Standard: ANSI T1.607 and 610)

(2) Data Transfer Speeds: Asynchronous (300/1200/2400/4800/9600/14400/28800 bits per second [b/s]); Synchronous (4.8/9.6/19.2/56/64 kb/s)

(3) Protocols: X.25; asynchronous ASCII protocol; IBM BSC protocol (including at a minimum IBM 3270 and 3780); IBM SNA/SDLC protocol; X.25 Link Access Protocol B (LAPB) for use over ISDN B-channel; Unisys Poll/Select protocol.

In addition to the above generic requirements, the contractor shall support the UNI types as given in Table C.2.3.1.1.4.1.1-1.

C-124


Table C.2.3.1.1.4.1.1-1. Mandatory User-to-Network Interfaces for Packet Switched Service

UNI Type

Interface Type Payload Data Rate Protocol Type

1 ITU-TSS V.35 Synchronous (up to 56/64 kb/s)

X.25

2 EIA RS-232 Synchronous (up to 19.2 kb/s)

X.25

3 EIA RS-422 Synchronous (up to 56/64 kb/s)

X.25


X.25


X.25

6 ISDN PRI Synchronous (up to 56/64 kb/s)

X.25

7 EIA RS-232 Asynchronous (up to 28.8 kb/s)

Asynchronous ASCII


Asynchronous ASCII


Asynchronous ASCII


Asynchronous ASCII

11 ITU-TSS V.35 Synchronous (up to 19.2 kb/s)

IBM BSC


IBM BSC


IBM BSC


IBM BSC


IBM BSC


IBM SNA/SDLC


IBM SNA/SDLC


IBM SNA/SDLC


IBM SNA/SDLC

C-125


Table C.2.3.1.1.4.1.1-1. Mandatory User-to-Network Interfaces for Packet Switched Service (Concluded)

UNI Type



IBM SNA/SDLC

21 ISDN PRI Synchronous (up to 56/64 kb/s)

ISDN LAPB


Unisys Poll/Select


Unisys Poll/Select


Unisys Poll/Select


Unisys Poll/Select


Unisys Poll/Select

C.2.3.1.1.4.1.2 Optional

(a) DTE (Packet-Mode and Non-Packet-Mode)

(1) Interface

(i) ISDN BRI and PRI D-Channel (Standard: ANSI T1.607 and 610)(ii) ITU-TSS X.21 (Non Domestic)

(2) Data Transfer Speed: Synchronous (16/64 kb/s) for ISDN BRI and PRI D-channels; ITU-TSS X.21 to 64 kb/s.

(3) Protocols: X.25; X.25 ISDN Link Access Protocol for D-channel (LAPD)


C-126


Table C.2.3.1.1.4.1.2-1. Optional User-to-Network Interfaces for Packet Switched Service

UNI Type Interface Type Payload Data Rate Protocol Type1 ISDN BRI

(D-Channel)Synchronous (16 kb/s) ISDN LAPD

2 ISDN PRI (D-Channel)

Synchronous (64 kb/s) ISDN LAPD

3 (non domestic)

ITU-TSS X.21 Synchronous (up to 64 kb/s)

X.25

4 ISDN BRI Synchronous(up to 56/64 kb/s)

ISDN LAPB


Pursuant to Section C.2.1.16, the contractor shall support/provide the following interfaces to connect to a POP for the provision of PSS access.


(a) Mandatory







(b) Optional


(2) E3 Channelized for Non-Domestic use (Standard: ITU-TSS G.702)

C-127


C.2.3.1.1.4.2.2 Reserved

C.2.3.1.1.4.2.3 Internetworked Access

(a) Mandatory

(1) None

(b) Optional

(1) ITU-TSS Recommendation X.75 protocol

(2) Section 14.11, BOC Notes on the LEC Networks (Bellcore Pub: SR-TSV-002275)

C.2.3.1.2 Packet Switched Service Transport Requirements


PSS shall provide a packet-switched, connection-oriented, data transmission service at data rates up to DS0.

PSS shall conform to the ITU-TSS X.25/X.28/X.29/X.3/X.32/X.75/X.121 recommendations, FIPS-PUB 100-1, FED-STD 1013/1020A/1030A/1033, and ANSI T1.504/614. The contractor shall support packet sizes up to 1024 bytes in length, including, at a minimum, sizes of 64, 128, 256, and 512 bytes.

Pursuant to Section C.2.1.16, the contractor shall provide PSS POP-to-POP connections between the contractor’s listed POPs. The contractor shall accept at any of its listed POPs which support the appropriate on-net service, originating PSS calls via dedicated, and/or internetworked access arrangement from the associated access providers. The contractor shall hand off terminating PSS calls via dedicated, and/or internetworked access arrangement from any of its listed POPs which support the appropriate on-net service to the associated access providers.

The contractor shall support dial-in capability to PSS. Authorized users will access this capability through the appropriate CSS (options include SVS, Toll Free Service, or CSDS [see Section C.2.2]). The dial-in location(s) for PSS shall be within the transport network. The PSS shall support both on-net FTS2001 phone numbers and toll free phone numbers for

C-128


dial-in access to PSS through asynchronous access and through synchronous packet-switched access using the X.32 protocol. Access to the network shall be provided only after verification of the authorization code entered by the user. If toll free phone numbers are utilized, the contractor shall bill the CSS charges to the appropriate user organization. The contractor shall support the following data rates:

(1) Asynchronous up to 28.8 kb/s(2) X.32 up to 28.8 kb/s using analog facilities(3) X.32 at 56/64 kb/s using digital facilities

The PSS transport shall support the following capabilities:

(a) The capability for a POP to send and receive data to another POP for a PSS connection by setting up PVC and/or SVC.

(b) The capability to support a numbering plan that shall follow the ITU-TSS X.121 numbering plan.

(c) The contractor shall support the following capabilities as specified in FIPS-PUB 100-1:

(1) Reverse charging

(2) Reverse charging acceptance

(3) Local charging prevention

(4) Nonstandard default packet size

(5) Nonstandard default window size

(6) Incoming calls barred

(7) Outgoing calls barred

(8) One-way logical channel outgoing

C-129


(9) One-way logical channel incoming

(10) Default throughput classes assignment

(11) Flow control parameter negotiation

(12) Throughput class negotiation

(13) Fast select

(14) Fast select acceptance

(15) Hunt group facilities, including round robin, closest, and ordered list

(16) Support for throughput classes of 1.2 kb/s, 2.4 kb/s, 4.8 kb/s, 9.6 kb/s, through 48 kb/s

(17) Transit delay selection and notification

(18) Abbreviated address calling

(19) Call redirection notification

(20) Called line address modification notification

(21) On-line facilities registration

(22) Extended packet sequence numbering (modulo 128)

(23) Packet retransmission

(24) Multilink procedure

(25) Direct call

(26) D-bit modification

(27) Call redirection

C-130


(28) NUI

(29) Extended frame sequence numbering

(30) Call deflection subscription

(31) Call deflection selection

The contractor may exceed the basic requirements by providing CUG-related capabilities, including CUG with outgoing access, CUG with incoming access, incoming calls barred within user group, outgoing calls barred within user group, bilateral CUG, bilateral CUG with outgoing access, and CUG with outgoing access selection. A minimum of 200 CUGs would be supported. CUGs and members of a CUG will be defined by the Government at service ordering time and will be allocated on a first come first serve basis. There would be no limitation on the number of DTE, that belong to a CUG.

The contractor may exceed the basic requirement by providing local telephone numbers for dial-in users.

The contractor may exceed the basic requirements by providing the following options after successful logon for the asynchronous dial-in users:

(32) Agency Menus. With this option, a user shall be provided with agency-specific menus after each successful logon for host connectivity. The contractor shall provide for up to ten agency menus per logon-ID/password combination, which will be defined at service ordering time. Each menu shall contain at least 24 host connectivity entries.

(33) Direct Access Without Menu. With this option, a user can have direct access to a host without menu options, such as (1) automatic connectivity to one host after successful logon or (2) user going directly into X.28 command mode after successful logon.


The following PSS transport features shall be supported.


None.

C-131



None.


The transport performance parameters for POP-to-POP transmission shall meet the following:


(1) The PSS transport performance (e.g., packet delay, packet loss, errored packet, misdelivered packet, duplicated packet, out of sequence packets, dial-up terminal GOS for Blockage) shall satisfy at least the values and ranges set forth in the ANSI T1.504 and Bellcore Public Packet Switched Network (PPSN) service standard (i.e., Public PSN Generic Requirement (PPSNGR), Bellcore Pub: TR-TSY-000301 and GR-2816-CORE).


(1) The availability of the PSS transport shall be at least 99.8 percent.



Pursuant to Section C.2.1.16, the contractor shall support/provide the following interfaces (i.e., LANI) at each POP listed for the provision of PSS transport.


(a) Mandatory



C-132






(b) Optional



C.2.3.1.2.4.1.2 Reserved


(a) Mandatory

(1) None

(b) Optional

(1) ITU-TSS Recommendation X.75 protocol

(2) Section 14.11, BOC Notes on the LEC Networks (Bellcore Pub: SR-TSV-002275)

C.2.3.2 Frame Relay Service

FRS provides reliable, high speed connectivity between user locations at guaranteed performance levels. The flexibility and reliability of the service make it an attractive alternative to private line networks. The following sections provide the requirements for FRS.

C-133


C.2.3.2.1 Frame Relay Service Access Requirements


FRS shall provide a frame-switched, connection-oriented, data transmission service at data rates up to DS1.

FRS shall conform to the ANSI T1 standards, in particular T1.606/614/617/618, and ITU-TSS I, Q, and X series recommendations for the provision of FRS and the North American adaptations of these recommendations as defined by the Alliance for Telecommunications Industry Solutions (ATIS) (formerly the Exchange Carrier Standards Association [ECSA]) T1 Committee. The FRS shall also conform to the industry agreements of the Frame Relay Forum, the Internet Engineering Task Force (IETF), and the North American ISDN Users Forum (NIUF). The FRS shall support frame sizes up to 4096 bytes, including, at a minimum, sizes of 64, 128, 256, 512, 1024, 2048 and 4096 bytes. The FRS shall offer a minimum Committed Information Rate (CIR) of 1024 kb/s for PVCs. However, for point-to-point connections, the CIR shall fallback to the smaller of the subscribed CIR value of the connected points for the duration of the call/connection.

Pursuant to Section C.2.1.16, the contractor shall provide dedicated and optionally internetworked originating and/or terminating access connections for FRS calls. Originating access connections shall connect FRS on-net originating locations with the associated POP. Terminating access connections shall connect the terminating POP with FRS on-net terminating locations.

FRS access shall be delivered directly to user’s terminal equipment, such as intelligent multiplexing/switching devices, or Local Area Network (LAN) routers, or DTE (e.g., host computers). The user’s terminal equipment can be both frame-relay capable equipment, which supports frame relay protocol, and non-frame relay capable, which does not support frame relay protocol. The capability for non-frame relay capable equipment or frame relay capable equipment to send and receive data to other non-frame relay capable equipment or frame relay capable equipment by setting up PVCs shall be provided by the contractor. The non-frame relay capable equipment may be an asynchronous ASCII terminal, an IBM BSC protocol terminal, or an IBM SNA/SDLC terminal. In addition, the data terminals may also be executing protocols such as UNISYS Poll/Select or IEEE 802 LAN router. The interfaces to these items of equipment are defined in Section C.2.3.2.1.4.1.

C-134


The contractor may exceed the basic requirements by providing the following:

(a) FRS would support multi-point connections. When supporting multi-point connections, the CIR would fallback to the smallest of the subscribed CIR value of all the connected points for the duration of the call/connection.

(b) FRS would provide a frame-switched, connection-oriented, data transmission service at data rates from DS1 to DS3 in increments of DS1.

(c) FRS via internetworked access arrangement (see Section C.2.1.16), when the following additional capabilities would be supported:

(1) FRS would support SVCs using a numbering plan that follows the ITU-TSS E.164 ISDN numbering and addressing recommendation.


When FRS access is provided via the optional internetworked access arrangement (see Section C.2.1.16), the following access features shall be provided.


None.


(a) Priority Levels. FRS shall support four priority levels for Virtual Circuits. Higher priority traffic shall be delivered ahead of lower priority traffic and shall be discarded only after all lower priority traffic has been discarded.


The access performance parameters for originating or terminating access connection between a POP and an SDP shall meet the following.


(1) For dedicated access arrangements, the FRS access delay shall not exceed the delay caused by the access line speed.

C-135


(b) Availability

(1) The availability of the FRS access shall be at least 99.8 percent.



The contractor shall support the following interfaces at the SDP for the provisioning of FRS access.


(a) Interface

(1) ITU-TSS V.35(2) EIA RS-232(3) EIA RS-422(4) EIA RS-449(5) EIA RS-530(6) ISDN PRI (Standard: ANSI T1.607 and 610)(7) IEEE 802.3 (Ethernet) all cable and connector types(8) IEEE 802.5 (Token Ring) all cable and connector types

(b) Data Transfer Speed: The FRS shall support data transfer speeds of 19.2 kb/s, and from 64 kb/s to T1/E1 (Non Domestic)

(c) Protocols Supported

(1) Frame relay protocol

(2) Non-frame relay protocols (i.e., Asynchronous ASCII, IBM BSC, IBM SNA/SDLC, UNISYS Poll/Select, IP or IEEE 802 LAN) via contractor’s provided Frame Relay Assembler/Disassembler (FRAD).

C-136



Table C.2.3.2.1.4.1.1-1. Mandatory User-to-Network Interfaces for Frame Relay Service

UNI Type

Interface Type Payload Data Rate (Note 2)

Protocol Type

1 ITU-TSS V.35 Up to 1.536 Mb/s Frame Relay2 ITU-TSS V.35 Up to 1.536 Mb/s Asynchronous ASCII3 ITU-TSS V.35 Up to 1.536 Mb/s IBM BSC4 ITU-TSS V.35 Up to 1.536 Mb/s IBM SNA/SDLC5 ITU-TSS V.35 Up to 1.536 Mb/s UNISYS Poll/Select6 ITU-TSS V.35 Up to 1.536 Mb/s IP7 All 802.3 cable and

connector typesUp to 1.536 Mb/s (See Note 1)

IEEE 802.3 IP/IPX

8 All 802.5 cable and connector types

Up to 1.536 Mb/s (See Note 1)

IEEE 802.5 IP/IPX

9 EIA RS-232 Up to 19.2 kb/s Asynchronous ASCII10 EIA RS-232 Up to 19.2 kb/s IBM BSC11 EIA RS-232 Up to 19.2 kb/s IBM SNA/SDLC12 EIA RS-232 Up to 19.2 kb/s UNISYS Poll/Select13 EIA RS-232 Up to 19.2 kb/s IP14 EIA RS-422 Up to 1.536 Mb/s Frame Relay15 EIA RS-422 Up to 1.536 Mb/s Asynchronous ASCII16 EIA RS-422 Up to 1.536 Mb/s IBM BSC17 EIA RS-422 Up to 1.536 Mb/s IBM SNA/SDLC18 EIA RS-422 Up to 1.536 Mb/s UNISYS Poll/Select19 EIA RS-422 Up to 1.536 Mb/s IP20 EIA RS-449 Up to 1.536 Mb/s Frame Relay21 EIA RS-449 Up to 1.536 Mb/s Asynchronous ASCII22 EIA RS-449 Up to 1.536 Mb/s IBM BSC23 EIA RS-449 Up to 1.536 Mb/s IBM SNA/SDLC24 EIA RS-449 Up to 1.536 Mb/s UNISYS Poll/Select25 EIA RS-449 Up to 1.536 Mb/s IP26 EIA RS-530 Up to 1.536 Mb/s Frame Relay27 EIA RS-530 Up to 1.536 Mb/s Asynchronous ASCII28 EIA RS-530 Up to 1.536 Mb/s IBM BSC29 EIA RS-530 Up to 1.536 Mb/s IBM SNA/SDLC

C-137


Table C.2.3.2.1.4.1.1-1. Mandatory User-to-Network Interfaces for Frame Relay Service (Concluded)

UNI Type

Interface Type Payload Data Rate (Note 2)

Protocol Type

30 EIA RS-530 Up to 1.536 Mb/s UNISYS Poll/Select31 EIA RS-530 Up to 1.536 Mb/s IP32 ISDN PRI (Multirate) Up to 1.472 Mb/s Frame Relay33 ISDN PRI (Multirate) Up to 1.472 Mb/s IBM BSC34 ISDN PRI (Multirate) Up to 1.472 Mb/s IBM SNA/SDLC35 ISDN PRI (Multirate) Up to 1.472 Mb/s UNISYS Poll/Select36 ISDN PRI (Multirate) Up to 1.472 Mb/s IP

Note 1: Output data rate of a contractor-provided router connecting to a LAN.Note 2: Where E-1 carrier service is provided, appropriate corresponding payload data rates apply.

C.2.3.2.1.4.1.2 Optional

(a) Interface

(1) T3 (Standard: Bellcore PUB GR-499-CORE)(2) E3 for Non-Domestic use (Standard: ITU TSS G.702)(3) IEEE 802.x (x = 3 and 5) LAN, all cable and connector types(4) ISDN BRI (Standard: ANSI T1.607 and 610)

(b) Data Transfer Speed: The FRS shall support data transfer speeds from T1/E1 to T3/E3 (Non Domestic)

(1) Frame relay protocol

(2) Non-frame relay protocols (i.e., IP or IEEE 802 LAN IPv4/IPv6/IPX/SNA) via contractor’s provided FRAD

C-138


If the option is proposed, the contractor shall support the following UNI types as given in Table C.2.3.2.1.4.1.2-1 in addition to the above generic requirements.

Table C.2.3.2.1.4.1.2-1. Optional User-to-Network Interface for Frame Relay Service

UNI Type


1 T3 Up to 43.008 Mb/s Frame Relay2 T3 Up to 43.008 Mb/s IPv4 and IPv63 All IEEE 802 all cable

and connector typesUp to 43.008 Mb/s (Note 1) IEEE 802.x (x=3,5)

IPv6/IPX/SNA/IPv44 E3 (non-domestic) Up to 30.72 Mb/s Frame Relay5 E3 (non-domestic) Up to 30.72 Mb/s IPv4 and IPv66 ISDN BRI (Multirate) Up to 128 kb/s Frame Relay7 ISDN BRI (Multirate) Up to 128 kb/s Asynchronous ASCII8 ISDN BRI (Multirate) Up to 128 kb/s IBM BSC9 ISDN BRI (Multirate) Up to 128 kb/s IBM SNA/SDLC

10 ISDN BRI (Multirate) Up to 128 kb/s UNISYS Poll/Select11 ISDN BRI (Multirate) Up to 128 kb/s IP12 All IEEE 802 all cable

and connector types (non-domestic)

Up to 30.72 Mb/s (Note 1) IEEE 802.x (x=3,5) IPv6/IPX/SNA/IPv4

Note 1: Output data rate of a contractor-provided router connecting to a LAN.


Pursuant to Section C.2.1.16, the contractor shall support/provide the following interfaces to connect to a POP for the provision of FRS access.


(a) Mandatory



(3) T3 channelized (Standard: Bellcore Pub: GR-499-CORE)

C-139



(5) DS0 (Bellcore Pub: SR-TSV-002275)

(b) Optional


(2) Channelized E3 for Non-Domestic use (Standard: ITU-TSS G.702)

(3) Fractional T3 channelized (Bellcore: GR-499-CORE)

C.2.3.2.1.4.2.2 Reserved


(a) Mandatory

(1) None

(b) Optional

(1) Frame Relay Inter-Carrier Interface (ICI), Section 14.13, BOC Notes on the LEC Networks (Bellcore Pub: SR-TSV-002275)

(2) Frame Relay Service Network Node Interface (NNI), Section 14.12, BOC Notes on the LEC Networks (Bellcore Pub: SR-TSV-002275)

C.2.3.2.2 Frame Relay Service Transport Requirements


FRS shall provide a frame-switched, connection-oriented, data transmission service at data rates up to DS1.

FRS shall conform to the ANSI T1 standards, in particular T1.606/614/617/618, and ITU-TSS I, Q, and X series recommendations for the provision of FRS and the North American adaptations of these recommendations as defined by the ATIS T1 Committee. The FRS shall also conform to the industry agreements of the Frame Relay Forum, the Internet

C-140


Engineering Task Force (IETF), and the North American ISDN Users Forum (NIUF). For PVCs FRS shall support frame sizes up to 4096 bytes, including, at a minimum, sizes of 64, 128, 256, 512, 1024, 2048 and 4096 bytes. The FRS shall offer a minimum CIR of 1024 kb/s. However, for point-to-point service the CIR shall fallback to the least subscribed CIR value of the connected points for the duration of the call/connection.

Pursuant to Section C.2.1.16, the contractor shall provide FRS POP-to-POP connections between the contractor’s listed POPs. The contractor shall accept at any of its listed POPs which support the appropriate on-net service, originating FRS calls via dedicated and optionally internetworked access arrangement from the associated access providers. The contractor shall hand off terminating FRS calls via dedicated, and optionally internetworked access arrangement from any of its listed POPs which support the appropriate on-net service to the associated access providers.

The contractor shall support dial-in capability to FRS. Authorized users will access this capability through the appropriate CSS (options include SVS, Toll Free Service, or CSDS [see Section C.2.2]). The dial-in location(s) for FRS shall be within the transport network. The FRS shall support both on-net FTS2001 phone numbers and toll free phone numbers for dial-in access to FRS through asynchronous access and through synchronous access using the ISDN LAPB protocol. Access to the network shall be provided only after verification of the authorization code entered by the user. If toll free phone numbers are utilized, the contractor shall bill the CSS charges to the appropriate user organization. The contractor shall support the following data rates:

(1) Asynchronous up to 28.8 kb/s(2) ISDN LAPB at 56/64 kb/s using digital facilities



(a) FRS would support multi-point (three or more) connections. When supporting multi-point connections, the CIR would fallback to the smallest of the subscribed CIR value of all the connected points for the duration of the call/connection.

(b) FRS would provide a frame-switched, connection-oriented, data transmission service at data rates from DS1 to DS3 in increments of DS1.

(c) When FRS is provided via internetworked access arrangement (see Section C.2.1.16), the following additional capabilities would be supported:

C-141


(1) FRS would support SVCs, and a numbering plan for SVCs that shall follow the ITU-TSS E.164 ISDN numbering and addressing recommendation.


The following FRS transport features shall be provided.


None.


(a) Priority Levels. FRS shall support four priority levels for Virtual Circuits. Higher priority traffic shall be delivered ahead of lower priority traffic and shall be discarded only after all lower priority traffic has been discarded.




(1) The performance (e.g., frame transfer delay, lost/errored frames ratio, and misdelivered frames ratio) shall satisfy at least the values and ranges set forth in the Bellcore FRS standards (i.e., Bellcore Pubs: TR-TSV-001369 and TR-TSV-001370). In addition , the contractor shall also comply with the ANSI T1.606/614/617/618 standards.


(1) The availability of the FRS transport shall be at least 99.8 percent.

C-142




Pursuant to Section C.2.1.16, the contractor shall support/provide the following interfaces (i.e., LANI) at each POP listed for the provision of FRS transport.


(a) Mandatory



(3) T3 channelized (Standard: Bellcore Pub: GR-499-CORE)



(b) Optional



(3) Fractional T3 (Bellcore Pub: GR-499-CORE)

C.2.3.2.2.4.1.2 Reserved


(a) Mandatory

(1) None

C-143


(b) Optional

(1) Frame Relay Inter-Carrier Interface (ICI), Section 14.13, BOC Notes on the LEC Networks (Bellcore Pub: SR-TSV-002275)

(2) Frame Relay Service Network Node Interface (NNI), Section 14.12, BOC Notes on the LEC Networks (Bellcore Pub: SR-TSV-002275)

(3) Multi-Services Broadband ISDN Inter-Carrier Interface (B-ICI), Section 14.12, BOC Notes on the LEC Networks (Bellcore Pub: SR-TSV-002275)

C.2.3.3 Internet Protocol Internetworking Service

Networks based on the TCP/IP protocol suite are the most prevalent data communication networks in existence. This connectionless service interoperates with the widest variety of applications and external networks. As such, IPS is the leading candidate for providing true, Government-wide connectivity. It’s interoperability with the Internet will also be a vital link between Government and public networks. The Government’s IPS user community is expected to be among the fastest growing and most widely used during the period of this contract. The following sections provide the requirements for IPS.

C.2.3.3.1 Internet Protocol Internetworking Service Access Requirements


IPS shall support connectionless service between users (i.e., IP hosts) for execution of applications based on protocols, such as File Transfer Protocol (FTP), SMTP, HyperText Transfer Protocol (HTTP), and connection to remote hosts (TELNET). An IP version 4 (v4) or optional version 6 (v6) host could be stand-alone or router connected to a LAN or in the Internet. The Government intends to use this service as a government-wide intranet, and for access to extranets and to the global Internet.

The IPS shall conform to all RFCs cited as required or recommended by the Internet Architecture Board (IAB), as documented in the current version of RFC 2200 (Internet Official Protocol Standards).

C-144


Pursuant to Section C.2.1.16, the contractor shall provide dedicated, and optionally internetworked originating and/or terminating access connections for IPS packets. Originating access arrangements shall connect IPS on-net originating locations with the associated POP. Terminating access arrangements shall connect the terminating POP with IPS on-net terminating locations.

IPS access shall be delivered directly to IP-terminals (e.g., router, computer) operating under IP protocol standard, as well as to LANs operating under LAN protocol standards, such as IEEE 802.3 Ethernet, 802.5 Token Ring, Fiber Distributed Data Interface (FDDI), through an IP-router operating under IP protocol standard. The interfaces to the equipment are defined in Section C.2.3.3.1.4.1.


(a) IPS access would additionally be delivered directly to terminals operating under IBM SNA/SDLC, Data Link Switching (DLS), NetBIOS/NetBEUI, Switched Ethernet (up to 100 Mb/s), Switched FDDI, Fiber channel, and High Performance Parallel Interface (HPPI) protocols.

(b) When IPS is provided via internetworked access arrangement (see Section C.2.1.16), the following additional capabilities would be supported:

(1) The IPS would support outgoing connections to IP-hosts in the FTS2001 networks and the Internet.

(2) The contractor would provide an addressing plan for the IPS that is based on the standard for IPv4 and IPv6 addressing.


The following access features shall be supported.


None.

C-145



The IPS shall provide the following features:

(a) Incoming connections to FTS2001 users (IP-hosts) shall only be allowed from authorized users. The contractor shall provide IP firewalls that are capable of user authentication, login, and packet filtering. Firewalls shall also be capable of supporting tunneling and encrypted tunneling.

When IPS access is provided via internetworked access arrangement (see Section C.2.1.16), the following access features shall be provided:

(b) The contractor shall administer a Domain Name Service (DNS) for Class C addresses. It shall be possible to assign a unique domain name to a stand alone host, a host attached to a LAN or to the Internet. If a host has a unique domain name assigned to it, then it shall be possible to address the host by its domain name instead of its numeric IP address.




(1) For dedicated access arrangements, the IPS access delay shall not exceed the delay caused by the access line speed.


(1) The availability of the IPS access shall be at least 99.8 percent.



The contractor shall support the following interfaces at the SDP for the provisioning of IPS access.

C-146



(a) Interfaces to be supported:

(1) EIA RS-449

(2) EIA RS-530

(3) EIA RS-232

(4) ITU-TSS V.35

(5) T1

(6) E1

(7) IEEE 802.3 (Ethernet/Fast Ethernet) all cable and connector types

(8) IEEE 802.5 (Token Ring) all cable and connector types

(9) ANSI FDDI/FDDI 2 all cable and connector types

(b) Data Transfer Speeds:

(1) EIA RS-449 shall support an information payload rate of up to 1.536 Mb/s


(3) ISDN PRI at 64 kb/s to 1.536 Mb/s in increments of 64 kb/s

(c) Protocols to be supported:

(1) IPv4-Terminal (e.g., router, computer)


C-147


Table C.2.3.3.1.4.1.1-1. Mandatory User-to-Network Interfaces for Internet Protocol Internetworking Service

UNI Type


1 All FDDI cable and connector types

Up to 43.008 Mb/s (Note 1) FDDI IPv4

2 All Fast Ethernet cable and connector types

Up to 43.008 Mb/s (Note 1) IEEE 802.3u IPv4

3 All IEEE 802.5 cable and connector types

Up to 43.008 Mb/s (Note 1) IEEE 802.5 IPv4/IPX


Up to 1.536 Mb/s (Note 1) IEEE 802.3 IPv4/IPX

5 EIA RS-232 Up to 19.2 kb/s IPv46 EIA RS-449 Up to 1.536 Mb/s IPv47 EIA RS-530 Up to 1.536 Mb/s IPv48 ITU-TSS V.35 Up to 1.536 Mb/s IPv49 ISDN PRI Up to 1.536 Mb/s IPv410 T1 Up to 1.536 Mb/s IPv411 E1 (non Domestic) Up to 1.92 Mb/s IPv4

Note 1: Output data rate of a contractor-provided router connecting to a LAN.

C.2.3.3.1.4.1.2 Optional

(a) Interfaces to be supported:

(1) T3

(2) E3

(3) All physical interfaces (i.e., cabling types) and speeds supported by IBM SNA/SDLC, DLS, and NetBIOS/NetBEUI

(4) IEEE 802.3 Switched Ethernet

(5) SONET OC-1 to OC-12

(6) ISDN BRI (Standard: see Section C.2.1.16.3.3.1 UNI)

C-148





(3) SONET at OC-1 to OC-12 shall support an information payload rate up to 594.432 Mb/s

(4) E3 shall support an information payload rate of 30.72 Mb/s

(5) ISDN BRI at 64 kb/s and 128 kb/s

(c) Protocols to be supported:

(1) IBM SNA/SDLC, DLS, and NetBIOS/NetBEUI(2) IPv6 and IPv4

The contractor shall support the following UNI types as given in Table C.2.3.3.1.4.1.2-1 in addition to the above generic requirements.

Table C.2.3.3.1.4.1.2-1. Optional User-to-Network Interfaces for Internet Protocol Internetworking Service

UNI Type


1 T3 Up to 43.008 Mb/s IPv4 and IPv62 E3 Up to 30.72 Mb/s IPv4 and IPv63 SONET OC-n Up to 594.432 Mb/s IPv4 and IPv64 IBM DLS all cables and

connectorsUp to 1.536 Mb/s (Note 2) IPv4 and IPv6

5 IBM NetBIOS/NetBEUI all cable and connectors

Up to 1.536 Mb/s (Note 2) IPv4 and IPv6

6 All Fast Ethernet cable and connector types


7 All FDDI cable and connector types






C-149


Table C.2.3.3.1.4.1.2-1. Optional User-to-Network Interfaces for Internet Protocol Internetworking Service (Concluded)

UNI Type


10 EIA RS-232 Up to 19.2 kb/s IPv6 and IPv411 ISDN BRI Up to 128 kb/s IPv412 EIA RS-449 Up to 1.536 Mb/s IPv6 and IPv413 EIA RS-530 Up to 1.536 Mb/s IPv6and IPv414 ITU-TSS V.35 Up to 1.536 Mb/s IPv6 and IPv415 ISDN BRI Up to 128 kb/s IPv6 and IPv416 T1 Up to 1.536 Mb/s IPv6 and IPv417 E1 (non Domestic) Up to 1.92 Mb/s IPv6 and IPv4

Note 2: Output data rate of a contractor-provided bridge or router connecting to a LAN.


Pursuant to Section C.2.1.16, the contractor shall support/provide the following interfaces to connect to a POP for the provision of IPS access.


(a) Mandatory



(3) T3 and Fractional T3 (Standard: Bellcore Pub: GR-499-CORE)



(b) Optional

(1) Synchronous Optical Network (SONET) OC-1/1c - OC-12/12c; Transport Systems: Common Generic Criteria (Bellcore Pub: GR-253-CORE) (Standard: ANSI T1.105 and 106)

C-150



(3) Subrate DS0 (Bellcore Pub: SR-TSV-002275)

C.2.3.3.1.4.2.2 Reserved


(a) Mandatory

(1) None

(b) Optional

(1) IPv4 and IPv6 as per RFC 2200

C.2.3.3.2 Internet Protocol Internetworking Service Transport Requirements


IPS shall support connectionless service between users (i.e., IP hosts) for execution of user applications based on protocols, such as FTP, SMTP, HTTP, and connection to remote hosts (TELNET). An IP v4 or optional v6 host could be stand-alone or router connected to a LAN or in the Internet. The Government intends to use this service as a government-wide intranet, and for access to extranets and to the global Internet.

The IPS shall conform to all RFCs cited as required or recommended by the IAB, as documented in the current version of RFC 2200 (Internet Official Protocol Standards).

Pursuant to Section C.2.1.16, the contractor shall provide interconnections between the contractor’s listed POPs. The contractor shall accept at any of its listed POPs which support the appropriate on-net service, originating IPS packets via dedicated, and internetworked access arrangement from the associated access providers. The contractor shall hand off terminating IPS packets via dedicated, and internetworked access arrangements from any of its listed POPs which support the appropriate on-net service to the associated access providers.

C-151


The contractor shall support dial-in capability to IPS. Authorized users will access this capability through the appropriate CSS (options include SVS, Toll Free Service, or CSDS [see Section C.2.2]). The dial-in location(s) for IPS shall be within the transport network. The IPS shall support both on-net FTS2001 phone numbers and toll free phone numbers for dial-in access to IPS through asynchronous access and through synchronous access using the point-to-point protocol. Access to the network shall be provided only after verification of the authorization code entered by the user. If toll free phone numbers are utilized, the contractor shall bill the CSS charges to the appropriate user organization. The contractor shall support the following data rates:

(a) Point-to-point protocol up to 28.8 kb/s using analog facilities(b) Point-to-point protocol at 56/64/128 kb/s using digital facilities


The IPS shall support outgoing connections to IP-hosts in the FTS2001 networks and in the Internet. Incoming connections to FTS2001 users (IP-hosts) shall only be allowed from authorized users in FTS2001 networks and in the Internet.

The contractor shall provide an addressing plan for the IPS that is based on the standard for IPv4 addressing.

The following additional capabilities shall be supported:

(c) The contractor shall administer a DNS for Class C address. It shall be possible to assign a unique domain name to a stand alone host, a host attached to a LAN, or to the Internet. If a host has a unique domain name assigned to it, then it shall be possible to address the host by its domain name instead of its numeric IP address. The contractor shall accommodate all existing Government IP addresses. In addition, the contractor shall provide permanent (static) and temporary (dynamic) assigned IP addresses for circuit switched users.


(d) For circuit switched calls the contractor would support dynamically allocated IP address, and dynamically updating the DNS with the domain name and assigned IP address.

(e) The contractor would provide an addressing plan for the IPS that is based on the standard for IPv6 addressing as stated in IETF RFC 2200.

C-152


(f) The contractor would support dial-in capability using asynchronous access. The contractor shall provide shell accounts for ASCII text based terminals. These shell accounts shall provide for a command line interface and shall support all TCP/IP command line commands. The contractor shall support access for these asynchronous terminals operating at the following data rates:

(1) Asynchronous up to 28.8 kb/s


The following IPS transport features shall be provided.


(a) The contractor shall provide as a minimum, the following IP firewall capabilities:

(1) A filter definition language, a set of logging and reporting tools for per-port and per socket management and administration

(2) The ability to filter both incoming and outgoing traffic

(3) Provision of preconfigured checks for known methods of attack

(4) Application specific forwarding capability (e.g., Telnet/FTP only)

(5) Support of encrypted tunneling


(a) The contractor shall additionally support IBM SNA/SDLC, DLS, NetBIOS/NetBEUI, Switched Ethernet (up to 100 Mb/s), Switched FDDI, Fibre Channel, and HPPI protocols.



C-153



IPS transport shall meet the following performance parameters:

(1) One-Way Packet Delay (Limits: less than 200 milliseconds on the average)


(1) The availability of the IPS transport shall be at least 99.8 percent



Pursuant to Section C.2.1.16, the contractor shall support/provide the following interfaces (i.e., LANI) at each POP listed for the provision of IPS transport.


(a) Mandatory






(b) Optional

(1) Synchronous Optical Network (SONET) OC-1, OC3/3c - OC-12/12c; Transport Systems: Common Generic Criteria (Bellcore Pub: GR-253-CORE) (Standard: ANSI T1.105 and 106)

C-154



(3) Subrate DS0 (Bellcore Pub: SR-TSV-002275)

C.2.3.3.2.4.1.2 Reserved


(a) Mandatory

(1) IPv4

(b) Optional

(1) IPv6

C.2.3.4 Asynchronous Transfer Mode Service

ATMS is rapidly becoming the service choice for high-speed data and multimedia applications. This connection-oriented service provides the highest bandwidth available in the SDS family and maintains performance for each class of traffic using the service. ATM is expected to provide a mechanism for integrating all of the Government’s various traffic types over a single media backbone. The following sections provide the requirements for ATMS.

C.2.3.4.1 Asynchronous Transfer Mode Service Access Requirements


ATMS shall support the transmission and aggregation of a broad range of user information, including voice, data, and video via circuit-mode and packet-mode transmission. ATMS shall use cell-switching and multiplexing technology that conforms with ATMF, ANSI, and ITU-TSS standards.

C-155


The ATMS shall comply with ATMF and all applicable ITU-TSS Recommendations including I.113, I.121, I.150, I.211, I.311, I.321, I.327, I.361, I.362, I.363, I.413, I.432, I.610, signaling adaptation layer (i.e., ITU-TSS Q.2100 Series), ATMF, and ANSI T1.105. The ATMS shall offer Sustained Cell Rates (SCRs) of 4, 8, 16, and 32 Mb/s for Variable Bit Rate (VBR) traffic including cell overhead. However, for point-to-point connections, the SCR shall fallback to the smaller subscribed SCR value of the connected points for the duration of the call/connection.

Pursuant to Section C.2.1.16, the contractor shall provide dedicated, and optionally internetworked originating and terminating access arrangements for ATMS. Originating access arrangements shall connect ATMS on-net originating locations with the associated POP. Terminating access arrangements shall connect the terminating POP with ATMS on-net terminating locations.

ATMS access shall be delivered directly to user equipment, such as PBX, ATM edge switches, router, or MUX. ATMS shall support the router for IEEE 802 LANs (Token Ring, Ethernet) and FDDI at a minimum. The interfaces to these equipment are defined in Section C.2.3.4.1.4.1.

The contractor may exceed the basic requirements by providing ATMS via internetworked access arrangement (see Section C.2.1.16), when the following additional capabilities would be supported.

(a) The ATMS would support Bandwidth-on-Demand (BOD) capability, by allocating incremental bandwidths in response to a user’s demand for additional bandwidth. For the circuit-mode of data transfer, the demand for additional bandwidth would be initiated by using a contractor-specified procedure; for the packet-mode of data transfer BOD would be initiated automatically by sending increased numbers of packets.

(b) The following ATM Adaptation Layer (AAL) capabilities would be supported and comply with ITU-TSS Recommendations I.361, I.362, and I.363, and Q.2100 for signaling:

(1) AAL Type 1 Constant Bit Rate (CBR). ATMS would support circuit-mode services at the E1 (for non-domestic), and E3 (for non-domestic), SONET OC-3c, and SONET OC-12c levels on an end-to-end basis.

(2) AAL Type 2 VBR-Real Time. ATMS would support a real time connection oriented service with low delay variance and access to variable network bandwidth.

C-156


(3) AAL Type 3/4 Connectionless Data Service. ATMS would support a packet-mode connectionless data service (e.g., IP).

(4) AAL Type 5 Connection-Oriented VBR Non-Real Time. ATMS would support packet-mode connection-oriented VBR data transfer service where end-user’s protocol ensures end-to-end data integrity (e.g., TCP). Non-delay sensitive VBR traffic could be transferred at Unspecified Bit Rate (UBR) where performance guarantee (e.g., Minimum Cell Rate [MCR]) is not required.

(5) AAL Type 3/4 and 5 Available Bit Rate (ABR). A connection oriented data transfer service supporting variable traffic with a guarantee of a MCR.

(6) AAL Type any UBR. A connection oriented data transfer service supporting traffic that is sensitive to loss but not to delay, using UBR data transfer.

(c) ATMS would support the following connection types for PVCs:

(1) Point-to-Point Connection. This feature would allow dedicated connection between two points.

(2) Point-to-Multipoint Connection. This feature would allow connection of three or more points. For point-to-multipoint connections, the SCR would fallback to the smallest subscribed SCR value of all the connected points for the duration of the call/connection.

(d) ATMS would support two priority levels for packet Virtual Circuits (VCs). A higher priority VC would receive preferential treatment over a lower priority VC in terms of delay and guarantee of delivery (if there is possibility of discard) during network congestion.

C-157


(e) ATMS would support the following connection types for SVCs:

(1) SVC. Point-to-point and point-to-multipoint connection types for SVCs, when the specifications are defined in the future including support for the ITU-TSS E.164 ISDN numbering and addressing plan and ATMF UNI signaling.


The following access features shall be supported.


None.


None.




(1) For dedicated access arrangements, the ATMS access delay shall not exceed the delay caused by the access line speed.


(1) The availability of the ATMS access shall be at least 99.8 percent.


C.2.3.4.1.4.1 User-to-Network-Interfaces

The contractor shall support the following interfaces at the SDP.

C-158



(a) Interfaces

(1) ITU-TSS V.35

(2) EIA RS-449

(3) EIA RS-530

(4) DS1 at line-rate of 1.544 Mb/s and information-payload data-rate of 1.536 Mb/s. (Standard: Bellcore’s BOC Notes on the LEC Network [SR-TSV-002275]; and ANSI T1.403)

(5) DS3 at line-rate of 44.736 Mb/s and information-payload data-rate 43.008 Mb/s including cell overhead. (Standard: Bellcore GR-499-CORE: ATMF UNI specification for T3 supporting Physical Layer Coverage Protocol [PLCP])

For all of the above mentioned interfaces, if an interface is addressed in the ATMF UNI specification, then the conformance with the ATMF UNI specification has higher precedence over the above mentioned standards.

(b) Data Transfer Speeds, inclusive of cell overhead:

(1) ITU-TSS V.35 shall support an information payload rate of up to 1.536 Mb/s.

(2) EIA RS-449 shall support an information payload rate of up to 1.536 Mb/s.

(3) EIA RS-530 shall support an information payload rate of up to 1.536 Mb/s.

(4) DS1 ATMS shall support an information-payload data-rate of up to 1.536 Mb/s.

(5) DS3 ATMS shall support an information rate of 1.536 Mb/s to 43.008 Mb/s in increments of 1.536 Mb/s (i.e., NxDS1).

C-159



(1) AAL Type 1(2) AAL Type 5(3) Native Mode


Table C.2.3.4.1.4.1.1-1. Mandatory User-to-Network Interfaces for Asynchronous Transfer Mode Service

UNI Type

Interface Type Payload Data Rate* Protocol Type**

1 ITU-TSS V.35 Up to 1.536 Mb/s AAL Type 52 EIA RS-449 Up to 1.536 Mb/s AAL Type 53 EIA RS-530 Up to 1.536 Mb/s AAL Type 54 DS1 Up to 1.536 Mb/s AAL Type 15 DS1 Up to 1.536 Mb/s AAL Type 56 DS3 Up to 43.008 Mb/s AAL Type 17 DS3 Up to 43.008 Mb/s AAL Type 58 DS1 Up to 1.536 Mb/s Native Mode9 DS3 Up to 43.008 Mb/s Native Mode

*The payload data rates above include cell overhead

** When AAL Type is specified, the contractor shall provide the ATM adaptation function. For native mode, the user traffic type will be AAL Type 1 or AAL Type 5.

C.2.3.4.1.4.1.2 Optional

(a) Interfaces

(1) ITU-TSS V.35

(2) EIA RS-449

(3) EIA RS-530

C-160


(4) SONET OC-3c to OC-48c at line-rate of 2.488 Gigabit per second (Gb/s) and information-payload data-rate of 2.378 Gb/s. (Standard: ANSI T1.105 and 106)




(1) The ATMS shall support SONET, with an information-payload data-rate from 148.608 Mb/s to 2.378 Gb/s including cell overhead.

(2) The ATMS shall support E1 (for Non-Domestic ) with an information payload rate of from 1.92 Mb/s to 30.72 Mb/s including cell overhead.


(1) AAL Type 3 and 4(2) AAL Type 5

If the option is proposed, the contractor shall support the following UNI types as given in Table C.2.3.4.1.4.1.2-1 in addition to the above generic requirements.

Table C.2.3.4.1.4.1.2-1. Optional User-to-Network Interfaces for Asynchronous Transfer Mode Service

UNI Type

Interface Type Payload Data Rate* Protocol Type

1 ITU-TSS V.35 Up to 1.536 Mb/s AAL Type 3/42 EIA RS-449 Up to 1.536 Mb/s AAL Type 3/43 EIA RS-530 Up to 1.536 Mb/s AAL Type 3/44 DS1 Up to 1.536 Mb/s AAL Type 3/45 DS3 Up to 43.008 Mb/s AAL Type 3/46 SONET OC-3c Up to 148.608 Mb/s AAL Type 3/4

C-161


Table C.2.3.4.1.4.1.2-1. Optional User-to-Network Interfaces for Asynchronous Transfer Mode Service (Concluded)

UNI Type

Interface Type Payload Data Rate* Protocol Type

7 SONET OC-12c Up to 594.432 Mb/s AAL Type 3/48 SONET OC-48c Up to 2.378 Gb/s AAL Type 59 SONET OC-48c Up to 2.378 Gb/s AAL Type 3/410 E1 (Non Domestic) Up to 1.92 Mb/s AAL Type 3/411 E3(Non Domestic) Up to 30.72 Mb/s AAL Type 3/4

*The payload data rates above include cell overhead


Pursuant to Section C.2.1.16, the contractor shall support/provide the following interfaces to connect to a POP for the provision of ATMS access.


(a) Mandatory

(1) T1 with ESF (Standard: Bellcore Pub: SR-TSV-002275; ANSI T1.102/107/403)


(b) Optional

(1) SONET OC-1 and OC-1 VT (Standard: ANSI T1.105 and 106)(2) SONET (OC-3c to OC-12c) (Standard: ANSI T1.105 and 106)(3) E1 for Non-Domestic use (Standard: ITU-TSS G.702)(4) E3 for Non-Domestic use (Standard: ITU-TSS G.702)(5) ISDN PRI (Standard: ANSI T1.607 and T1.610)

C.2.3.4.1.4.2.2 Reserved

C-162



(a) Mandatory

(1) None

(b) Optional


C.2.3.4.2 Asynchronous Transfer Mode Service Transport Requirements


ATMS shall support the transmission and aggregation of a broad range of user information, including voice, data, and video via circuit-mode and packet-mode transmission. ATMS shall use cell-switching and multiplexing technology that conforms with ATMF, ANSI, and ITU-TSS standards.

The ATMS shall comply with ATMF and all applicable ITU-TSS Recommendations including I.113, I.121, I.150, I.211, I.311, I.321, I.327, I.361, I.362, I.363, I.413, I.432, I.610, ITU-TSS Q.2100 Series, ATMF, and ANSI T1.105. The ATMS shall offer SCRs of 4, 8, 16, and 32 Mb/s for VBR traffic. However, for point-to-point connections, the SCR shall fall back to the least subscribed SCR value of all the connected points for the duration of the call/connection.

Pursuant to Section C.2.1.16, the contractor shall provide ATMS POP-to-POP connections between the contractor’s listed POPs. The contractor shall accept at any of its listed POPs which support the appropriate on-net service, originating ATMS connections via dedicated and optionally internetworked access arrangement from the associated access providers. The contractor shall hand off terminating ATMS connections via dedicated, and optionally internetworked access arrangement from any of its listed POPs which support the appropriate on-net service to the associated access providers.

C-163



(a) The following AAL capabilities shall be supported and comply with ITU-TSS Recommendations I.361, I.362, and I.363, and ITU-TSS Q.2100 Series for signaling:

(1) AAL Type 1 Constant Bit Rate. ATMS shall support circuit-mode services at the DS1 and DS3 levels on an end-to-end basis.

(2) AAL Type 5 Connection-Oriented VBR. ATMS shall support packet-mode connection-oriented data transfer service at DS1 and DS3, where end-user’s protocol ensures end-to-end data integrity (e.g., TCP).

(b) ATMS shall support the following connection types for PVCs:

(1) Point-to-Point Connection. This feature shall allow dedicated connection between two points.

(c) The ATMS transport shall support the following CBR payload data rates:

(1) DS1 at information-payload data-rate of 1.536 Mb/s, including cell overhead(2) DS3 at information-payload data-rate 40.704 Mb/s, including cell overhead

(d) ATMS shall support two levels of cell loss priority for VCs. A higher priority VC shall receive preferential treatment over a lower priority VC in terms of cell loss (if there is possibility of discard) during network congestion.


(e) ATMS would support services at the E1 (for non-domestic), E3 (for non-domestic), and SONET OC-3c to SONET OC-48c levels for the following:

(1) AAL Type 1 CBR. ATMS would support circuit-mode services on an end-to-end basis.

(2) AAL Type 2 VBR. ATMS would support real time connection oriented service with low delay.

(3) AAL Type 3/4 Connectionless Data Service. ATMS would support a packet-mode connectionless data service (e.g., IP).

C-164


(4) AAL Type 3/4 and 5 ABR. A connection oriented data transfer service supporting variable traffic with a guarantee of a MCR.

(5) UBR. A Connection oriented data transfer service supporting traffic that is sensitive to loss but not to delay, using UBR data transfer.

(f) Point-to-multipoint connection PVCs would allow connection of three or more points. For point-to-multipoint connections, the SCR would fallback to the smallest subscribed SCR value of all the connected points for the duration of the call/connection.

(g) The ATMS transport would support the following CBR data rates:

(1) SONET OC-3c to OC-48c(2) E1 (Non-Domestic Use)(3) E3 (Non-Domestic Use)

(h) ATMS BOD

(1) The ATMS transport would support bandwidth-on-demand capability, by allocating incremental bandwidths in response to a user’s demand for additional bandwidth. The demand for additional bandwidth would be indicated by vendor-provided dialing sequence for circuit-mode of data transfer and automatically by sending increased number of packets for packet-mode of data transfer.

(i) ATMS would support the following connection types for SVCs:

(1) SVC. Point-to-point and point-to-multipoint connection types for SVCs, when the specifications are defined in the future including support for the ITU-TSS E.164 ISDN numbering and addressing plan and ATMF UNI signaling (i.e., ITU-TSS Q.2931 ATM signaling).

(2) Future Broadband ISDN Services.

C-165



The following ATMS transport features shall be supported.


None.


None.C.2.3.4.2.3 Performance



The performance for circuit-mode transmission shall satisfy at least the values and ranges set forth in the ANSI T1.503/510 for DS1 data rate, Bellcore Pub. GR-342-CORE for DS3 data rate. The performance for packet-mode transmission (e.g., cell delay, cell loss ratio, cell error ratio, cell misinsertion ratio, and cell out of sequence packets ratio) for data transmission rates at or below SCR shall satisfy at least the values and ranges set forth in the ATMF UNI specification, International Telecommunications Union, and Bellcore Broadband service standards (i.e., ITU Recommendations: ITU-T I.356 and ITU-T G826 and Bellcore Pubs: GR-1110-CORE, GR-1111-CORE, TR-TSV-000772, and TR-TSV-001369) in that order of preference. For both circuit-mode and packet-mode transmissions, if performance is addressed in the ATMF UNI specification, then the conformance with the ATMF UNI specification has higher precedence over the above mentioned standards.


The availability of the ATMS transport shall be at least 99.8 percent.

C-166




Pursuant to Section C.2.1.16, the contractor shall support/provide the following interfaces (i.e., LANI) at each POP listed for the provision of ATMS transport.


(a) Mandatory

(1) T1 with ESF (Standard: Bellcore Pub: SR-TSV-002275; ANSI T1.102/107/403)


(b) Optional

(1) ISDN PRI (Standard: ANSI T1.607 and 610)(2) SONET OC-1 and OC-1 VT (Standard: ANSI T1.105 and 106)(3) SONET OC-3c to OC-12c (Standard: ANSI T1.105 and 106)(4) E1 for Non-Domestic use (Standard: ITU-TSS G.702)(5) E3 for Non-Domestic use (Standard: ITU-TSS G.702)

C.2.3.4.2.4.1.2 Reserved


(a) Mandatory

(1) None

(b) Optional


(2) Private Network-to-Network Interface (PNNI) (Standard: ATMF PNNI specification)

C-167


C.2.4 Dedicated Transmission Service

DTS provides dedicated, reliable bandwidth for agency-specific data networks and mission critical applications. The range of line speeds and reliability options provided within this service category allow Government users to satisfy their diverse needs. The following sections provide the requirements for DTS.

The interface and performance requirements in Sections C.2.4.1.3 and C.2.4.1.4 shall also apply to contractor-provided dedicated access facilities used to provide access service integration and to the connection of Government-provided access service integration equipment to contractor-provided access circuits. The interface requirements in Section C.2.4.2.4 shall also apply to the termination of Government-provided dedicated access at the contractor’s POP.

C.2.4.1 Dedicated Transmission Service Access Requirements

C.2.4.1.1 Basic Service Description

DTS access includes dedicated transmission service between an SDP and a POP. The connection between the locations receiving this service shall be permanently established unless a service request for modification, move, or disconnect is received. This service can be used for any application, such as voice, data, video, and multimedia.

Dedicated transmission service shall comply with ITU T1.503 and all applicable Bellcore and ANSI standards, primarily ANSI T1.102/107/403 for T1, Bellcore PUB GR-499-CORE for T3, and ANSI T1.105 and 106 for SONET.

Pursuant to Section C.2.1.16, the contractor shall provide DTS access connections between the POPs and the SDPs, as specified by the Government.

DTS access connections shall be delivered directly (i.e., via dedicated access line) to equipment, such as analog terminal equipment (e.g., analog PBX, modem), data terminal equipment (e.g., Computer, Group 4 FAX, video codec), and also to a digital PBX, multiplexer, or LAN router. Both analog and digital mode of transmission shall be supported. The interfaces to this equipment are defined in Section C.2.4.1.4.1. For analog DTS, the contractor shall accept and deliver an analog signal whose nominal bandwidth is 4 kHz.

C-168


For digital DTS, the network shall provide network-derived clocking, where appropriate as determined by the contractor (e.g., T1) and when requested by the user, to the connected DTE, digital PBX, Intelligent MUX, or LAN router. However, if a user requires networked-derived clocking for any other speeds, it shall be negotiated on an individual case basis. The service shall provide data transport and shall be transparent to any protocol used by the DTE or router. All bit sequences transmitted by the DTE through the SDP shall be treated with data transparency.

The following categories of DTS service shall be supported:

(a) Analog. This category of DTS service shall support a nominal 4 kHz bandwidth.

(b) Subrate DS0. This category of DTS service shall support subrate DS0 at information payload data rates of 4.8 and 9.6 kb/s.

(c) DS0. This category of DTS service shall support information payload data rates of 56 and 64 kb/s.

(d) T1. This category of DTS service shall support a line rate of 1.544 Mb/s, which may be used to provide channelized or unchannelized T1 service as follows:

(1) Channelized T1. In this mode, 24 separate DS0s clear channels of 56/64 kb/s shall be supported.

(2) Unchannelized T1. In this mode, a single 1.536 Mb/s information payload shall be supported.

(e) Fractional T1. This category of DTS service shall support two, four, six, eight, or twelve adjacent DS0 clear channels, over an interface of T1 with a line rate of 1.544 Mb/s.

(f) T3. This category of DTS service shall support a line rate of 44.736 Mb/s, which may be used to provide channelized or unchannelized T3 service as follows:

(1) Channelized T3. In this mode, 28 separate DS1 channels of 1.536 Mb/s information payload rate shall be supported.

(2) Unchannelized T3. In this mode, a single 43.008 Mb/s payload shall be supported.

C-169


(g) Fractional T3. This category of DTS service shall support three, four, five, or seven adjacent DS1 clear-channels over an interface of T1 or T3.

(h) E1 (For Non-Domestic Use). This category of DTS service shall support a line rate of 2.048 Mb/s, which may be used to provide channelized or unchannelized E1 service as follows:

(1) Channelized E1. In this mode, 30 separate DS0 clear channels shall be supported.

(2) Unchannelized E1. In this mode, a single 1.92 Mb/s information payload shall be supported.

The contractor may exceed the basic requirements by providing the following categories of DTS service:

(i) Subrate DS0. This category of DTS service would support subrate DS0 at information payload data rate of 19.2 kb/s.

(j) E3 (For Non-Domestic Use). This category of DTS service would support a line rate of 34.368 Mb/s, which may be used to provide channelized or unchannelized E3 service as follows:

(1) Channelized E3. In this mode, 16 separate E1 channels would be supported.

(2) Unchannelized E3. In this mode, a single 30.72 Mb/s information payload would be supported.

(k) SONET OC-1. This category of DTS service would support a single SONET OC-1 channel with the information payload data rate of 49.536 Mb/s over an interface with a line rate of 51.840 Mb/s.

(l) SONET OC-1 Virtual Tributary. This category of DTS service would support seven Virtual Tributary (VT) groups over a single SONET OC-1 interface with a line rate of 51.840 Mb/s. Each VT group would be able to carry independently either four T1s or two DS1Cs or one DS2 channel(s); where each T1 has a line rate of 1.544 Mb/s and payload data rate of 1.536 Mb/s, and each DS1C has a line rate of 3.152 Mb/s and information payload data rate of 3.072 Mb/s, and each DS2 has a line rate of 6.312 Mb/s and information payload data rate of 6.144 Mb/s.

C-170


(m) SONET OC-3. This category of DTS service would support a line rate of 155.520 Mb/s, which may be used to provide channelized OC-3 or concatenated OC-3c service as follows:

(1) Channelized OC-3. In this mode, three separate OC-1 channels, each with an information payload data rate of 49.536 Mb/s, would be supported.

(2) Concatenated OC-3c. In this mode, a single channel equivalent to information payload data rate of 148.608 Mb/s would be supported.

(n) SONET OC-12. This category of DTS service would support a line rate of 622.080 Mb/s, which may be used to provide channelized OC-12 or concatenated OC-12c.

(1) Channelized OC-12. In this mode, 4 separate OC-3 channels, each with an information payload data rate of 148.608 Mb/s, would be supported.

(2) Concatenated OC-12c. In this mode, a single channel equivalent to an information payload data rate of 594.432 Mb/s would be supported.

(o) SONET OC-48. This category of DTS service would support a line rate of 2.488 Gb/ s, which may be used to provide channelized OC-48 or concatenated OC-48c.


(2) Concatenated OC-48c. In this mode, a single channel equivalent to an information payload data rate of 2.378 Gb/s would be supported.

(p) All other DTS data rates that are available or become available during the life of the contract.

C-171


C.2.4.1.2 Features

The following DTS access features shall be supported.

C.2.4.1.2.1 Mandatory

(a) Multipoint Connection. This feature shall allow connection of three or more subscribers’ premises at a single POP for analog services and for digital services at least up to 56/64 kb/s. The following capabilities shall be supported:

(1) Branch-Off. In this mode, all points shall be treated as if in one shared medium with the ability of autonomous sending and receiving of data by each point. However, the Customer Premises Equipment (CPE) application will ensure master/slave mode of operation (e.g., polling scheme used in IBM 3270 mode of data communication).

(b) Analog Line Conditioning. This feature shall provide voice grade, C (e.g., C3) and D (e.g., D6) conditioning to support analog modem data rates of at least 19.2 kb/s and preferably 28.8 kb/s (including Standard: Bellcore Pubs: TR-NWT-000335 and TR-NWT-000965).

C.2.4.1.2.2 Optional

(a) Multipoint Connection. This feature shall allow connection of three or more subscribers’ premises at a single POP. The following capabilities shall be supported:

(1) Drop-and-Insert. In this mode, previously specified channels of a channelized T1, T3, SONET OC-3, or SONET OC-12 service category shall be able to be dropped off, and simultaneously new channels shall be able to be picked up or inserted.

(b) 7.5 kHz Audio. This feature shall allow a 7.5 kHz audio signal, delivered and received in analog form, which shall be compressed by the contractor provided equipment for transmission over a DS0 channel. The audio quality shall not be less than what is available using ADPCM compression technology (standard: ITU-TSS G.721).

C-172


(c) Service Assurance. This feature shall allow improved availability of DTS circuits, including such schemes as automatic restoration and reconfiguration, as specified below:

(1) Availability 99.97 percent

(2) Trouble identification Less than 20 minutes

(3) Time to restore Less than 2 hours in at least 99.95 percent of the cases

(d) Enhanced Service Assurance. When requested by a user, the contractor shall provide 99.98 percent availability on an individual case basis.

(e) Low Bit Rate Voice. This feature shall allow for voice at 32 kb/s and for analog data at 4.8 kb/s utilizing contractor provided equipment and shall conform to Adaptive Differential Pulse Code Modulation (ADPCM) according to North American adaptation of ITU-TSS recommendation G.721 (compression of a ITU-TSS B.711 voice band signal at 32 kb/s), as modified by ANSI.

C.2.4.1.3 Performance

The access performance parameters for originating or terminating access connection between a POP and an SDP, or between two SDPs, shall meet the following:


(1) All analog transmission parameters shall satisfy at least the values and ranges set forth in Section 7, Transmission, BOC Notes on the LEC Networks (Bellcore Pub: SR-TSV-002275). Additional analog transmission parameters for conditioned circuits shall include Intralata Voice Grade Private Line Services (Bellcore Pub: TR-NWT-000965), and Voice Grade Special Access Services - Transmission Parameter Limits and Interface Combinations (Bellcore Pub: TR-NWT-000335).

C-173


(2) All digital transmission parameters shall satisfy at least the values and ranges set forth in the High-Capacity Digital Special Access Service - Transmission Parameter Limits and Interface Combinations (Bellcore Pub: GR-342-CORE); and additionally, ANSI T1.503/510 for T1, Bellcore PUB GR-499-CORE for T3, and ITU-TSS G.702 and related recommendations for E1.


(1) The availability of a DTS access circuit shall be at least 99.8 percent.

C.2.4.1.4 Interfaces

C.2.4.1.4.1 User-to-Network Interface

The contractor shall support the following interfaces at the SDP for the provisioning of dedicated transmission service:


(a) ITU-TSS V.35

(b) EIA RS-449

(c) EIA RS-232

(d) EIA RS-530

(e) RJ-x (e.g., RJ-11/45)

(f) T1 (with ESF format) at line-rate of 1.544 Mb/s and information-payload data-rate of up to 1.536 Mb/s. (Standard: Bellcore’s BOC Notes on the LEC Networks [SR-TSV-002275], and ANSI T1.403)

(g) T3 at line-rate of 44.736 Mb/s and information-payload data-rate of 43.008 Mb/s. (Standard: Bellcore PUB GR-499-CORE)

(h) E1 at line-rate of 2.048 Mb/s and information-payload data-rate of 1.92 Mb/s. (Standard: ITU-TSS G.702)

C-174


In addition to the above generic requirements, the contractor shall support the following UNI types as specified in Table C.2.4.1.4.1.1-1.

Table C.2.4.1.4.1.1-1. Mandatory User-to-Network Interfaces for Dedicated Transmission Service

UNI Type


Signaling Type

1 ITU-TSS V.35 Up to 1.92 Mb/s N/A2 EIA RS-449 Up to 1.92 Mb/s N/A3 EIA RS-232 Up to 19.2 kb/s N/A4 EIA RS-530 Up to 1.92 Mb/s N/A5 RJ-x (e.g., RJ-11/45) 4/7.5 kHz Bandwidth N/A6 T1 (with ESF) Up to 1.536 Mb/s N/A7 T3 Up to 43.008 Mb/s N/A8 E1 Up to 1.92 Mb/s N/A


(a) E3 at line-rate of 34.368 Mb/s and information-payload data-rate of 30.72 Mb/s. (Standard: ITU-TSS G.702)

(b) SONET OC-1 at line-rate of 51.840 Mb/s and information-payload data-rate of 49.536 Mb/s. (Standard: ANSI T1.105 and 106)

(c) SONET OC-3 and OC-3c at line-rate of 155.520 Mb/s and information-payload data-rate of 148.608 Mb/s. (Standard: ANSI T1.105 and 106)

(d) SONET OC-12 and OC-12c at line-rate of 622.080 Mb/s and information-payload data-rate of 594.432 Mb/s. (Standard: ANSI T1.105 and 106)

(e) SONET OC-48 and OC-48c at line-rate of 2.488 Gb/s and information-payload data-rate of 2.378 Gb/s. (Standard: ANSI T1.105 and 106)

C-175


If the option is bid, the contractor shall support the following UNI types as specified in Table C.2.4.1.4.1.2-1 in addition to the above generic requirements.

Table C.2.4.1.4.1.2-1. Optional User-to-Network Interfaces for Dedicated Transmission Service

UNI Type


1 E3 Up to 30.72 Mb/s N/A2 SONET OC-1 49.536 Mb/s N/A3 SONET OC-3 148.608 Mb/s N/A4 SONET OC-3c 148.608 Mb/s N/A5 SONET OC-12 594.432 Mb/s N/A6 SONET OC-12c 594.432 Mb/s N/A7 SONET OC-48 2.378 Gb/s N/A8 SONET OC-48c 2.378 Gb/s N/A

C.2.4.1.4.2 Local Access to Network Interface

Pursuant to Section C.2.1.16, the contractor shall support/provide the following interfaces to connect to a POP listed for the provisioning of DTS access:


(a) T1 and Fractional T1 with ESF (Standard: Bellcore Pubs: SR-TSV-002275; ANSI T1.102/107/403)

(b) T3 and Fractional T3 (Standard: Bellcore Pub: GR-499-CORE)

(c) E1 for Non-Domestic use (Standard: ITU-TSS G.702)

(d) Analog (Bellcore Pub: SR-TSV-002275)

(e) DS0 and Subrate DS0 (Bellcore Pub: SR-TSV-002275)

C-176



(a) SONET (OC-1 VT and OC-1 to OC-12 and OC-3c to OC-12c) (Standard: ANSI T1.105 and 106)

(b) E3 for Non-Domestic use (Standard: ITU-TSS G.702)

C.2.4.2 Dedicated Transmission Service Transport Requirements


DTS transport includes dedicated transmission service between two or more POPs. The connection between the locations receiving this service shall be permanently established unless a service request for modification, move, or disconnect is received. This service can be used for any application, such as voice, data, video, and multimedia.

Dedicated transmission service shall comply with ITU T1.503 and all applicable Bellcore and ANSI standards, primarily ANSI T1.102/107/403 for T1, Bellcore PUB GR-499-CORE for T3, and ANSI T1.105 and 106 for SONET.

Pursuant to Section C.2.1.16, the contractor shall provide DTS POP-to-POP connections between the contractor’s listed POPs. The contractor shall accept at any of its listed POPs which support the appropriate on-net service, DTS access connections from the associated access providers.

All bit sequences transmitted shall be treated with data transparency.

The following categories of DTS service shall be supported.

(a) Analog DTS. This category of DTS service shall support a 4 kHz bandwidth.

(b) Subrate DS0. This category of DTS service shall support subrate DS0 at information payload data rates of 4.8 and 9.6 kb/s.

(c) DS0. This category of DTS service shall support information payload data rates of 56 and 64 kb/s.

C-177


(d) T1. This category of DTS service shall support a line rate of 1.544 Mb/s, which may be used to provide channelized or unchannelized T1 service as follows:

(1) Channelized T1. In this mode, 24 separate DS0s clear channels of 56/64 kb/s shall be supported.

(2) Unchannelized T1. In this mode, a single 1.536 Mb/s information payload shall be supported.

(e) Fractional T1. This category of DTS service shall support two, four, six, eight, or twelve adjacent DS0 clear channels over an interface of T1 with a line rate of 1.544 Mb/s.

(f) T3. This category of DTS service shall support a line rate of 44.736 Mb/s, which may be used to provide channelized or unchannelized T3 service as follows:

(1) Channelized T3. In this mode, 28 separate DS1 channels of 1.536 Mb/s information payload rate shall be supported.

(2) Unchannelized T3. In this mode, a single 43.008 Mb/s payload shall be supported.

(g) Fractional T3. This category of DTS service shall support three, four, five, or seven adjacent DS1 clear-channels over an interface of T1 or T3.

(h) E1 (For Non-Domestic Use). This category of DTS service shall support a line rate of 2.048 Mb/s, which may be used to provide channelized or unchannelized E1 service as follows:

(1) Channelized E1. In this mode, 30 separate DS0 clear channels shall be supported.

(2) Unchannelized E1. In this mode, a single 1.92 Mb/s information payload shall be supported.

The contractor may exceed the basic requirements by providing the following categories of DTS service:

(i) Subrate DS0. This category of DTS service would support subrate DS0 at information payload data rate of 19.2 kb/s.

C-178


(j) E3 (For Non-Domestic Use). This category of DTS service would support a line rate of 34.368 Mb/s, which may be used to provide channelized or unchannelized E3 service as follows:

(1) Channelized E3. In this mode, 16 separate E1 channels would be supported.

(2) Unchannelized E3. In this mode, a single 30.72 Mb/s information payload would be supported.

(k) SONET OC-1. This category of DTS service would support a single SONET OC-1 channel with the information payload data rate of 49.536 Mb/s over an interface with a line rate of 51.840 Mb/s.

(l) SONET OC-1 Virtual Tributary. This category of DTS service would support seven Virtual Tributary (VT) groups over a single SONET OC-1 interface with a line rate of 51.840 Mb/s. Each VT group would be able to carry independently either four T1s or two DS1Cs or one DS2 channel(s); where each T1 has a line rate of 1.544 Mb/s and payload data rate of 1.536 Mb/s, and each DS1C has a line rate of 3.152 Mb/s and information payload data rate of 3.072 Mb/s, and each DS2 has a line rate of 6.312 Mb/s and information payload data rate of 6.144 Mb/s.

(m) SONET OC-3. This category of DTS service would support a line rate of 155.520 Mb/s, which may be used to provide channelized OC-3 or concatenated OC-3c service as follows:

(1) Channelized OC-3. In this mode, three separate OC-1 channels, each with an information payload data rate of 49.536 Mb/s, would be supported.

(2) Concatenated OC-3c. In this mode, a single channel equivalent to information payload data rate of 148.608 Mb/s would be supported.

(n) SONET OC-12. This category of DTS service would support a line rate of 622.080 Mb/s, which may be used to provide channelized OC-12 or concatenated OC-12c.


(2) Concatenated OC-12c. In this mode, a single channel equivalent to an information payload data rate of 594.432 Mb/s would be supported.

C-179


(o) SONET OC-48. This category of DTS service would support a line rate of 2.488 Gb/s, which may be used to provide channelized OC-48 or concatenated OC-48c.


(2) Concatenated OC-48c. In this mode, a single channel equivalent to an information payload data rate of 2.378 Gb/s would be supported.

(p) All other DTS data rates that are available or become available during the life of the contract are included in the scope of the contract.

C.2.4.2.2 Features

The following DTS transport features shall be supported.


(a) Multipoint Connection. This feature shall allow connection of three or more subscribers’ premises (i.e., POPs). The following capabilities shall be supported:

(1) Branch-Off. In this mode, all points shall be treated as if in one shared medium with the ability of autonomous sending and receiving of data by each point. However, the CPE application will ensure master/slave mode of operation (e.g., polling scheme used in IBM 3270 mode of data communication).

(b) Analog Line Conditioning. This feature shall provide voice grade, C (e.g., C3) and D (e.g., D6) conditioning to support analog modem data rates of at least 19.2 kb/s and preferably 28.8 kb/s (including Standard: Bellcore Pubs: TR-NWT-000335 and TR-NWT-000965).

(c) Special Routing. This feature shall provide different routes for DTS circuits, for up to T3 data-rate, based on the following arrangements:

C-180


(1) Transport Diversity. Between connecting POPs, the contractor shall supply two or more physically separated routes for DTS circuits. Between two pairs of diverse POPs, the contractor shall supply two physically separated routes for DTS circuits and shall coordinate with the access diversity providers (see Section C.2.1.16) to achieve end-to-end diversity. These diverse routes shall not share common telecommunications facilities or offices. The contractor shall maintain a minimum separation of 30 feet throughout all diverse POP-to-POP routes that are more than 100 feet from the originating and terminating POPs. The Government recognizes that uncompromised (i.e., adhering to the minimum separation requirements as described above) diversity may not be available in some locations. Where uncompromised diversity is not available, the contractor shall exert best efforts to propose an acceptable arrangement along with documentation describing the compromise. Each pair of circuits which must be diverse from each other constitutes a relationship pair. For example, three circuits ordered as being diverse from each other constitute three relationship pairs i.e., 1 and 2, 1 and 3, and 2 and 3. If diversity is not available or the compromised diversity is not acceptable to the Government, it shall be negotiated on an individual case basis.

(2) Avoidance. Between connecting POPs, the contractor shall supply the capability for a customer to define a geographic location or route on the network to avoid. However, the Government recognizes that avoidance may not be available in some locations. Where avoidance is not available, the contractor shall exert best efforts to propose an acceptable arrangement along with documentation describing the reasons for the unavailability.

The contractor shall establish internal control (i.e., electronic flagging of routes) to prevent the accidental dismantling of diversified/avoidance routes, especially during routine route optimization initiatives by the contractor.

The contractor shall provide within 30 calendar days of the implementation of transport diversity or avoidance and again thereafter when a change is made, a graphical representation (e.g., diagrams/maps) of transport circuit routes to show where diversity or avoidance has been implemented. The contractor shall provide to the agency, with a copy to the PMO, written notification for Government

C-181


approval of any proposed reconfigurations of routes, previously configured for transport diversity or avoidance at least 30 calendar days in advance of implementation. For each diverse or avoidance route the contractor shall conform to the requirements for performance as specified in Section C.2.4.2.3.


(a) Multipoint Connection. This feature shall allow connection of three or more subscribers’ premises at a single POP. The following capabilities shall be supported:

(1) Drop-and-Insert. In this mode, previously specified channels of a channelized T1, T3, SONET OC-3, or SONET OC-12 service category shall be able to be dropped off, and simultaneously new channels shall be able to be picked up or inserted.

(b) Service Assurance. This feature shall allow improved availability of DTS circuits, including such schemes as automatic restoration and reconfiguration, as specified below:

(1) Availability 99.97 percent

(2) Trouble identification Less than 20 minutes

(3) Time to restore Less than 2 hours in at least 99.95 percent of the cases

(c) Enhanced Service Assurance. When requested by a user, the contractor shall provide 99.98 percent availability on an individual case basis.

(d) Low Bit Rate Voice. This feature shall allow for voice at 32 kb/s and for analog data at 4.8 kb/s utilizing contractor provided equipment and shall conform to Adaptive Differential Pulse Code Modulation (ADPCM) according to North American adaptation of ITU-TSS recommendation G.721 (compression of a ITU-TSS B.711 voice band signal at 32 kb/s), as modified by ANSI.

C-182



The performance parameters for POP-to-POP connection shall meet the following:

(a) Transmission Performance:

(1) All analog transmission parameters shall satisfy at least the values and ranges set forth in Section 7, Transmission, BOC Notes on the LEC Networks (Bellcore Pub: SR-TSV-002275). Additional analog transmission parameters for conditioned circuits shall include Intralata Voice Grade Private Line Services (Bellcore Pub: TR-NWT-000965), and Voice Grade Special Access Services - Transmission Parameter Limits and Interface Combinations (Bellcore Pub: TR-NWT-000335).

(2) All digital transmission parameters shall satisfy at least the values and ranges set forth in the ANSI T1.503/510 for T1, Bellcore PUB GR-499-CORE for T3, and ITU-TSS G.702 and related recommendations for E1.


(1) The availability of a DTS transport circuit shall be at least 99.8 percent.

C.2.4.2.4 Interfaces

C.2.4.2.4.1 Local Access to Network Interfaces

Pursuant to Section C.2.1.16, the contractor shall support/provide the following interfaces (i.e., LANI) at their listed POPs for the provisioning of DTS transport:


(a) T1 and Fractional T1 with ESF (Standard: Bellcore Pub: SR-TSV-002275; ANSI T1.102/107/403)

(b) T3 and Fractional T3 (Standard: Bellcore Pub: GR-499-CORE)

C-183


(c) E1 for Non-Domestic use (Standard: ITU-TSS G.702)

(d) Analog (Bellcore Pub: SR-TSV-002275)

(e) DS0 and Subrate DS0 (Bellcore Pub: SR-TSV-002275)


(a) SONET (OC-1 VT and OC-1 to OC-12 and OC-3c to OC-12c) (Standard: ANSI T1.105 and 106)

(b) E3 for Non-Domestic use (Standard: ITU-TSS G.702)

C.2.5 Wireless Services (Optional)

The Government has a growing community of wireless telecommunications services and products users who continue to demonstrate the importance of wireless services as a vital communications tool for Government operations. The rapid emergence of new wireless service capabilities is expected to continue thus enabling the Government to improve its operations in support of law enforcement, health and human services, national defense, disaster response, and routine business applications. New wireless service capabilities are also expected to facilitate the Government objectives for wireless telecommunications that can generally be characterized as digital, ubiquitous, interoperable, transparent, and secure. During the term of the FTS program, it is expected that commercial digital wireless coverage will significantly expand and that Government users will benefit from a rapid conversion to digital wireless.

C.2.5.1 Cellular Voice Service (Optional)

The Government desires a CVS that provides a wireless switched voice-band service. The CVS shall enable users to make full-duplex switched voice telephone calls using wireless terminals. CVS shall provide circuit switched data communications at rates up to at least 14.4 kb/s using cellular voice band modems (based on the ITU-TSS standards of V.32 for data and V.17 for FAX), and with short message service features as defined in Section C.2.5.1.2.1 where digital CVS is provided. For circuit switched data communications, the CVS shall operate in both full-duplex and half-duplex modes.

C-184


The CVS shall be provided in accordance with one or more of the following standards:

(a) EIA/TIA-553 Mobile Station-Land Station Compatibility Specification (Advanced Mobile Phone Service [AMPS])

(b) EIA/TIA IS-54B Cellular System Dual-Mode Mobile Station-Base Station Compatibility Standard Time Division Multiple Access (TDMA)

(c) TIA/EIA IS-95 Mobile Station-Base Station Compatibility Standard for Dual-Mode Wideband Spread Spectrum Cellular System Code Division Multiple Access (CDMA)

As a minimum, the contractor shall provide CVS in accordance with the EIA/TIA-553 AMPS specification. The contractor shall also provide the CVS in accordance with either the EIA/TIA IS-54B or the TIA/EIA IS-95 standard or both.

The contractor shall provide an access connection for all CVS calls that incur transport charges. An access connection shall connect a CVS user to the FTS2001 wireline network.

The contractor shall provide an end-to-end connection for all calls that do not incur transport charges. An end-to-end connection may connect a CVS user to another CVS user, or to a wireline voice user within the local calling area.

C.2.5.2 Wireless Digital Packet Data Service (Optional)

The Government desires a WDPDS that provides a wireless digital packet data transfer service. WDPDS shall enable users to perform data transmissions using wireless modems at a minimum transmission rate of 4.8 kb/s.

WDPDS shall be provided in accordance with one or more of the following standards:

(a) Cellular Digital Packet Data (CDPD)(b) Mobitex Interface(c) Radio Data-Link Access Protocol (RD-LAP) 19,200 b/s

The contractor shall provide an access connection for all WDPDS transmissions that incur transport charges. An access connection shall connect a WDPDS user to the contractor’s wireline network.

C-185


The contractor shall provide an end-to-end connection for all transmissions that do not incur transport charges. An end-to-end connection may connect a WDPDS user to another WDPDS user, or to a non-FTS2001 data network (e.g., Internet).

C.2.5.3 One-Way Paging Service (Optional)

The Government desires a OPS that provides wireless one-way paging over simplex RF communications links.

The OPS shall conform to the following standard:

(a) International Radio Consultative Committee (CCIR), Radiopaging Code No. 1, Post Office Code Standardization Advisory Group (POCSAG) standard.

An OPS page shall consist of one or more of the following characteristics:

(b) An audible tone, mechanical vibration, or combined tone and vibration

(c) A string of numeric digits that are visually displayed on a pager

(d) A string of alphanumeric characters that are visually displayed on a pager

(e) A string of alphanumeric characters that may be visually displayed by a DTE attached to the pager for extended text messaging

C.2.6 Satellite Services (Optional)

C.2.6.1 Mobile Satellite Service (Narrow Band) (Optional)

MSS is envisioned as providing users on-demand voice and low-rate data services. Users may employ MSS to obtain access to PSNs from locations that are not served by other access arrangements.

The Government desires a MSS that provides a ubiquitous satellite-based full-duplex circuit switched voice and data service, capable of supporting land mobile, maritime mobile, and aeronautical mobile communications for MSS users. The MSS shall support half-duplex and full-duplex data calls at rates up to at least 4.8 kb/s for FAX and for data using wireless modems. The service shall be global unless otherwise stated.

C-186


The MSS shall be provided in accordance with the following standards:

(a) American Mobile Satellite Corporation (AMSC) standards for MSS

(b) International Maritime Satellite Organization (INMARSAT) specifications for Class B Service

(c) INMARSAT specifications for Class M Service

The contractor shall provide an end-to-end connection for all MSS calls where the satellite service area allows connecting one MSS user, directly to another MSS user or for calls that can be completed by a wireline carrier where no direct usage charges apply. These calls will not incur a transport charge.

The contractor shall provide an access connection to the FTS2001 wireline network for calls that cannot be completed end-to-end in the manner described above. These calls will incur a transport charge.

C.2.6.2 Fixed Satellite Service - Wideband (Optional)

FSS is envisioned as providing users dedicated and reservation based voice, data, and video services. Users may employ FSS to obtain high speed data transmission and wireless network capabilities. In addition, users may employ FSS to obtain multipoint transmissions between geographically dispersed locations.

The Government desires an FSS that provides satellite based transmission of voice, data, and video traffic. The FSS shall provide full-duplex and simplex transmissions for broadcast analog and point-to-point digital communications. As a minimum, the contractor shall provide FSS for both C-band and Ku-band transmissions.

The contractor shall provide an access connection for all FSS transmissions that incur wireline transport charges. An access connection shall connect an FSS user to the contractor’s wireline network.

The contractor shall provide an end-to-end connection for all transmissions that do not incur wireline transport charges. An end-to-end connection may connect an FSS user to another FSS user, or to a non-FTS2001 service satellite transponder (e.g., commercial broadcast television network satellite transponder) which is properly configured.

C-187


The contractor shall define the contours of the FSS coverage. The offeror shall provide in its proposal and the contractor shall provide and maintain after award service coverage maps that show the satellite foot print for the frequency band(s) for each satellite providing FSS service.

FSS shall provide space segment capacity on a full-time as well as on a reservation basis.


(a) End-to-End Digital Connection Capability. FSS shall provide point-to-point and point-to-multipoint connections. FSS terminals shall include dedicated earth stations and Very Small Aperture Terminals (VSATs). Data transmissions shall be simplex, half duplex, full duplex, asymmetrical or broadcast. FSS shall support Ethernet and Token Ring LAN interconnects. FSS shall provide the following data rates:

(1) Data rates up to DS0 (4.8, 9.6, 19.2 and 56/64 kb/s)(2) Data rates up to DS1 (128, 256, 384, 512 and 768 kb/s and 1.544 Mb/s)(3) Data rates at 3.3, 4.5 and 6.6 Mb/s(4) DS3 data rates

(b) Video Transmission Capability. FSS shall provide analog channel capacity for transmission of National Television Standards Committee video with accompanying audio. The video transmission capability shall provide service performance comparable to that specified in EIA RS-250C with the following exceptions:

(1) The minimum signal-to-noise ratio shall be 49 dB(2) The availability shall be 99.7 percent

FSS shall provide digital channel capacity for transmission of digital compressed video with accompanying audio. FSS shall provide transmission data rates at 3.3, 4.5, and 6.6 Mb/s.

(c) Reservation. The contractor shall provide a single point of contract for only an authorized user to schedule reservations based space segment capacity.

The Designated Agency Representative (DAR) will notify the contractor of those individuals authorized to schedule space segment capacity.

C-188


C.2.7 Value Added Services

VAS are application level services which provide additional capability and functionality beyond the other telecommunications services. These use other telecommunications services for underlying transmission support.

C.2.7.1 X.400 Based Electronic Messaging Service (Optional)

The Government desires a X.400 based EMS that provides a store-and-forward message handling system for electronic transfer of messages. A message shall consist of an envelope and content. The envelope contains addressing information, and attributes (e.g., date, time, priority, and subject). The content includes heading and one or more body parts, such as text message, FAX, application data (e.g., spreadsheet attachment, Geographic Information System data), voice, video, or multimedia message.

The X.400 based EMS shall conform to, at a minimum, 1992 X.400 series recommendations of ITU-TSS as profiled by National Institute of Standards and Technology’s (NIST’s) Open System Environment (OSE) Implementors Workshop (OIW) implementation agreements. The contractor shall support the service functions as defined by the Elements of Service (EOS) specified in the X.400 series recommendations. The service functions supported shall include and conform with EOS specified by NIST’s OIW implementation agreements and specifications of the Internationally Standardized Profiles (ISPs) for Message Handling Systems, both the common messaging profile (International Organization for Standardization/International Electrotechnical Commission [ISO/IEC] ISP 10611) and the interpersonal messaging profile (ISO/IEC ISP 12062).

The electronic messages shall be delivered directly to the DTEs. These DTEs may represent local E-Mail system servers, microcomputer-based systems, gateways, and other X.400 E-Mail systems.

C.2.7.2 Simple Mail Transfer Protocol Based Electronic Messaging Service (Optional)

The Government desires an SMTP based EMS that provides a message handling system for electronic transfer of messages between SMTP based EMS users and users on the Internet using Post Office Protocol Version 3 in conformance with RFCs 821, 822, and 974 of IETF. SMTP based EMS shall support Multipurpose Internet Mail Extensions (MIME) protocols for application specific binary attachments to messages in conformance with the RFC 1521.

C-189


The SMTP based EMS messages shall be delivered directly to the DTEs that represent:

(a) Microcomputer-based end user systems i.e., IBM compatible PCs, Macintoshes, or Workstations (e.g., Sun, IBM and HP Workstations) with their operating system (e.g., DOS, DOS/Windows 3.X, NT, Windows 95, OS/2 2.X, Mac OS, or UNIX-based OS).

(b) Local E-Mail servers (e.g., cc:Mail, Microsoft Exchange Server).

The addressing plan shall be based on Internet addressing plan in conformance with RFCs 821 and 974. Domain Name Service shall be based on RFC 1034 and 1035. Both the contractor and the user provided addresses shall be supported.

The contractor’s infrastructure shall support best commercial practices against threats from hacker, criminal, and terrorist activities. In addition, the contractor’s infrastructure security shall comply with the OMB Circular A-130 which ensures adequate security commensurate with the risk and magnitude of harm resulting from the loss, misuse, or unauthorized access to or modification of information.

C.2.7.3 Electronic Commerce Service (Optional)

The Government desires an ECS that provides the capability for automated electronic exchange of business transactions (e.g., invoices, price/sale catalogs, request for quotations, purchase orders, contract awards, shipping information, payment orders, remittance advice, and healthcare claims) that conform to the EDI standards of both ANSI chartered Accredited Standards Committee X12 and United Nations Electronic Data Interchange For Acquisition Commerce and Transport (EDIFACT) standard.

C.2.7.4 Video Teleconferencing Service


The contractor shall provide a VTS whereby participants at different physical locations may conduct activities such as interactive dialogues by simulating face-to-face meetings and discussions. VTS shall provide point-to-point and multipoint arrangements for video teleconferencing. In addition, VTS shall support ancillary data transmission for sharing of software applications and various types of data files (e.g., graphic, spreadsheet, and word processing files) among VTS participants, and VTS shall support other value added applications of video services.

C-190


(a) For FTS2001 on-net locations served by the contractor, VTS shall utilize CSDS or DTS available under this contract for the underlying transmission. When the VTS is ordered for a location that is not already served by DTS or CSDS service, the appropriate service, as requested by the DAR, shall be provided by the contractor.

(b) When a VTS conference is ordered that includes any locations that are on-net with another FTS2001 contractor, the contractor under this contract shall provide transmission to the other contractor’s teleconferencing facility.

(c) When a VTS conference is ordered that includes any locations that are not on-net with any FTS2001 contractor, the users at those locations shall be responsible for providing transmission to the contractor’s teleconferencing facility.

(d) VTS shall conform with the Federal Telecommunications Recommendations (FTR) 1080 - 1997 (hereafter referred to as FTR-1080) issued by the Technology and Standards Division of the National Communication System (NCS). FTR 1080 covers the specifications for narrow-band audio and video teleconferencing, at 56 kb/s to 1,920 kb/s, based on the ITU-TSS series H.320 recommendations. VTS shall also support the TSS T.120 document conferencing standards no later than the date those standards are supported for any of the contractor’s other customers.

(e) VTS shall support three user configurations, namely room, rollabout, and desktop.

(f) The contractor shall provide VTS to any of the following service delivery points:

(1) When the VTS uses CSDS with dedicated access, the service shall be delivered directly to one of the following:

(i) Government furnished inverse multiplexer.

(ii) Government furnished codec. The contractor shall provide the service to the codec with or without the inverse multiplexing function, according to the UNI specified.

C-191


(iii) Government furnished audio, video, and ancillary data source(s) inputs and outputs (cameras, speakers, microphones and data ports) of the codec that interfaces with the video teleconferencing equipment. The contractor shall provide the encoding/decoding function with or without the inverse multiplexing function, according to the UNI specified. Video teleconferencing for the desktop configuration shall support computer systems operating under Microsoft Windows 3.x/95/NT operating systems.

(2) When the VTS uses CSDS with circuit switched access or uses DTS, the service shall be delivered directly to one of the following:

(i) Government furnished codec.

(ii) Government furnished audio, video, and ancillary data source(s) inputs and outputs of the codec that interfaces with the video teleconferencing equipment. The contractor shall provide the encoding decoding function. Video teleconferencing for desktop shall support computer systems operating under Microsoft Windows 3.x/95/NT operating systems.

The VTS shall support the following capabilities for room, rollabout, and desktop user configurations unless otherwise noted.

C.2.7.4.1.1 Connection Arrangements

(a) Point-to-Point. The VTS shall support point-to-point connection arrangements with full-duplex video, audio, and ancillary data transmission between participating locations. If one of the locations is not on the contractor’s network, connection shall be made as provided in Section C.2.7.4.1(b) or C.2.7.4.1(c).

(b) Multipoint. VTS multipoint arrangements shall be provided in conjunction with the contractor’s VTS reservation feature. The multipoint arrangement shall have the capability of providing service to users of a different FTS2001 contractor’s network on an on-net basis and to users of other public or private networks on an off-net basis. The multipoint arrangements shall support full-duplex audio among

C-192


all participating locations. During the conduct of a multipoint conference, the addition of a party to, or the deletion of a party from, the conference shall be indicated by a tone or by a verbal or visual announcement. If any of the locations are not on the contractor’s network, connection shall be made as provided in Section C.2.7.4.1(b) or C.2.7.4.1(c).

The multipoint arrangement shall provide the following capabilities:

(1) Voice Activation. The video transmitted to all locations is selected by voice activation, automatically, after audio from that location exceeds a preset level for a specified amount of time.

(2) Chairperson Control. The person in control of the video teleconference sends his or her own video or selects a return video from one of the participating locations to be transmitted to all participating locations. The chairperson has the capability of passing control of the video teleconference to another presenter at his or her location.

(3) Lecture Control (Broadcast Video with Audio Return). The video from the lecturer’s location is transmitted to all participants. Audio, but no video, is returned to the lecturer’s location from all other participating locations. The lecturer can select one or all of the audio signals for transmission to all participants.

The contractor may exceed the basic requirements by providing the following capability.

(c) Continuous Presence. In a multipoint arrangement, the VTS would support continuous presence in which the video from a minimum of three up to16 participating locations (more as technology allows) may be viewed simultaneously at each participating location. If the number of locations participating in the video conference exceeds the number being viewed via continuous presence, the selection of the video from a participating location that is displayed would be coordinated among the contractor and the participants.

C.2.7.4.1.2 Connection Data Rates

The VTS shall support the following connection data rates for CSDS and DTS for room, rollabout, and desktop user configurations:

C-193


(a) DS0 (i.e., 56 kb/s and 64 kb/s)

(b) T1 (DS1) (optional)

(c) Multirate DS0 (i.e., 2/4/6/8/12 x DS0 for dedicated access and 2/6/12 x DS0 for circuit switched access)

(d) ISDN PRI

(e) E1 at line rate of 2.048 Mb/s and payload rate of 1.92 Mb/s (for non domestic users)

C.2.7.4.2 Features

The VTS shall provide the following features.


(a) Reservation. For the room, rollabout, and desktop configurations, the VTS shall provide a central reservation capability to permit authorized video teleconference users to schedule and establish multipoint video teleconferences. For point-to-point video teleconferences, reservations shall be required only when coding conversion, format conversion, or rate adaptation features are needed, or when connection to an off-net location is desired.

The DAR will notify the contractor of the individuals authorized to schedule video teleconferences at the time the order for VTS is placed. The list of authorized individuals may be changed by the DAR at any time after the service has been initiated, at no additional cost to the Government.

(1) The VTS reservation system shall have the following capabilities:

(i) A single point of contact with the contractor to schedule reservation-based video teleconferences

(ii) The ability for VTS authorized users to schedule one or more video teleconferences by time and day of the week either as a single event or recurring event on a daily, weekly, monthly, or other periodic basis

C-194


(iii) The ability for VTS authorized users to submit reservation requests up to one year in advance by voice, FAX, E-Mail, and electronic bulletin board

(iv) The ability for the VTS reservation system to create printed reports with the following information:

(A) A directory of all locations authorized to use the VTS reservation system. Inclusion in the directory shall be with approval of the agencies.

(B) Reservation confirmation and cancellation notices.

(C) Monthly performance reports covering:

(1) Number of video teleconferences scheduled, during prime and non-prime hours, using the reservation feature.

(2) Number of video teleconferences per month that did not start at the scheduled time, the cause of which was attributable to the contractor’s actions.

(3) Number of video teleconferences per month which were started but then failed or suffered degraded quality, as a result of the contractor’s failure to perform properly.

(4) Total number of requests (each individual request for a particular time and date is considered a separate request) for reservation of video teleconferencing which were not honored due to unavailability of resources of bridging capability, format conversion, rate adaptation, or coding conversion.

(v) The ability for the VTS users to schedule a “meet-me” reservation based video teleconference.

(2) The VTS reservation system shall contain the following information:

(i) Name of the person scheduling a video teleconference

(ii) Organization of the person scheduling a video teleconference

C-195


(iii) Telephone number of the person scheduling a video teleconference

(iv) Name of the contact person at participating locations

(v) Telephone numbers of the contact persons participating in a video teleconference

(vi) Locations of the persons participating in a video teleconference (at the user’s discretion)

(vii) Date of a video teleconference

(viii) Time of a video teleconference

(ix) Scheduled length of a video teleconference.

(3) The VTS shall provide VTS reservation users with the following capabilities:

(i) Schedule a non-recurring multipoint or point-to-point video teleconference within 30 minutes after the advance reservation request, provided the bridging capacity or the required network functions (i.e., format conversion, rate adaptation, or coding conversion) are available.

(ii) Based on availability of bridging capacity and required network functions, request a delay in the scheduled termination time of a video teleconference, which is already in progress, shall be granted, if the request is made at least 20 minutes before the scheduled terminating time of the video teleconference.

(iii) Permit VTS users to cancel a video teleconference up to 30 minutes before the scheduled start time of the video teleconference without incurring any charge for the canceled video teleconference.

(iv) Support a minimum of 25 simultaneous multipoint video teleconferences, with an average of 6 locations each, at an average data rate of 384 kb/s. All simultaneous video teleconferences shall be capable of supporting the following functions in any combination.

(A) Coding conversion(B) Format conversion

C-196


(C) Rate adaptation

(b) Coding Conversion. The VTS shall provide a coding conversion capability that permits operation between:

(1) Codecs, all of which use the National Television Standards Committee (NTSC) video format, but none of which support the FTR 1080 and none of which use the same encoding/decoding algorithm(s).

(2) Codecs, all of which use the NTSC video format, in which one or more of the codecs support the FTR 1080 and in which one or more of the codecs do not support the FTR 1080.

As a minimum, the contractor shall support coding conversion for the current FTS2000 proprietary encoding/decoding algorithms of the Compression Labs Inc. Rembrandt II, Rembrandt II/06, and Rembrandt II/VP codecs.

The contractor shall provide this coding conversion capability in a manner such that VTS users may avail themselves of it for reservation-based video teleconferences and for video teleconferences established via dedicated connections and circuit switched data connections.

(c) Video Format Conversion. The VTS shall provide a video format conversion capability that permits operation between:

(1) Codecs which operate in the NTSC video format and codecs which operate in the Phase Alternation by Line (PAL) video format.

(2) Codecs which operate in the NTSC video format and codecs which operate in the Système Electronique Couleur Avec Memoire (SECAM) video format.

The contractor shall provide this video format conversion capability in a manner such that VTS users may avail themselves of it for reservation-based video teleconferences and for video teleconferences established via dedicated connections and circuit switched data connections.

(d) Security. VTS shall provide unclassified but sensitive level of secure video teleconferencing capability for point-to-point and multipoint video teleconferences.

C-197


(e) Rate Adaptation. VTS shall provide a data rate adaptation capability to ensure that all VTS locations participating in a video teleconference can interconnect with each other using any of the data rates specified in C.2.7.4.1.1.2. The rate adaptation feature shall be used in conjunction with the reservation feature.


(a) Access to the Contractor’s Reservation System. The capability shall be provided, for the authorized VTS users to electronically access, as specified by the contractor, the VTS reservation system and obtain system information related to only their agency, including all unscheduled time slots by day, week, and month.


(a) Digital. The VTS shall deliver the following digital performance:

(1) When the contractor furnishes only a reservation, coding conversion, format conversion, and/or rate adaptation feature(s), the encoded audio, video, and ancillary data signals that the contractor delivers as part of the VTS shall be in conformance with the signals required by the user’s codec.

(2) When the contractor furnishes the encoding/decoding function, the digital performance for data rates specified in Section C.2.7.4.1.2 shall be in conformance with FTR 1080 performance at the given data rate employed in the video teleconference.

(b) Availability. The availability of the VTS shall be at least 99.5 percent.

(c) Synchronization. The VTS shall maintain lip synchronization between the audio and video signals within +2 video frames to the extent possible with the video frame rate employed in the video teleconference.

(d) Other. If the number of requests denied during a calendar quarter exceeds by five percent the number of participating locations supported during the same calendar quarter, the contractor shall increase its multipoint capacity at 384 kb/s by 10 percent during the subsequent quarter.

C-198


The contractor shall compute the number of requested locations denied by counting the cumulative number of locations associated with each conference that could not be scheduled for a particular date and time requested. The contractor shall compute the number of locations supported by counting the cumulative number of locations associated with each conference that was held. In calculating locations denied and locations served, locations on the contractor’s network and on another FTS2001 network shall be included, but locations on other (non-FTS2001) networks shall be excluded.

C.2.7.4.4 User-to-Network Interface


The contractor shall support the following interfaces at the SDP. The inverse multiplexing function, where provided, shall conform to the TIA-EIA-619 standard for Aggregation of Multiple Independent 56 kb/s or 64 kb/s channels in a synchronized wideband connection (formally known as BONDING [0, 1, and 3] standard).

(a) If the government provides the codec and the inverse multiplexer and the contractor provides only reservation, coding conversion, and/or format conversion, the UNIs supported shall include:

(1) ITU-TSS V.35(2) EIA RS-449(3) EIA RS-530(4) T1(5) E1(6) RJ-x (e.g., RJ-45)(7) ISDN PRI(8) FT1

(b) If the government provides the codec and the contractor provides only reservation, coding conversion, and/or format conversion, the UNIs supported shall include the UNIs for CSDS given in Table C.2.2.2.1.4.1.1-1.

C-199


(c) If the contractor provides the inverse multiplexing function and the government provides the codec, the following interfaces shall be supported:

(1) EIA RS-449 (with RS366A)(2) EIA RS-530 (with RS366A)(3) ITU-TSS V.35 (with RS366A)

(d) If the contractor provides the encoding/decoding function with or without the inverse multiplexing function, the following interfaces shall be supported.

(1) Video Input/Output:

(i) NTSC composite analog video signal (according to standards EIA-170 and EIA RS-250)

(ii) Y/C analogY: 1.0 volt peak-to-peak, at 75 ohmsC: 0.286 volt peak-to-peak, at 75 ohms

(2) Audio Input:

(i) Line Level(ii) Microphone Level

(3) Audio Output:

(i) Line Level(ii) Speaker Level(iii) Headphone Level

(4) Data Interface(s) (any combination of the following data interfaces shall be supported by the VTS):

(i) EIA RS-232(ii) EIA RS-449(iii) ITU-TSS V.35(iv) EIA RS-530

C-200



None.

C.2.8 Emerging Services

Given the rapid pace of communications technology expansion, a number of services and applications are expected to emerge during the course of the FTS program. As the commercial infrastructure evolves, and new services become commercially available, the Government intends to add new services to maintain the technical adequacy of its communication systems. If any of these services are available at time of proposal submission, the offeror is encouraged to propose them.

ES are expected to interoperate seamlessly with FTS2001 services, as well as other ES when incorporated into this contract, as appropriate.:

The following are selected examples of ES in that their commercial availability is very limited and standards are still evolving.

(a) Network Information Discovery and Retrieval (NIDR)(b) Collaborative Computing(c) Location System Services using global positioning system technology(d) Personal Communication Service (PCS)(e) Two-Way Paging Service (TPS)(f) Enhanced Specialized Mobile Radio Service (ESMRS)(g) Advanced Mobile Satellite Service (AMSS)(h) Cellular Dispatch Service (CDS)(i) Digital Wireless STU-III Service(j) Asymmetric Digital Subscriber Line Access(k) Very High Speed Digital Subscriber Line Access(l) Smart Calling Cards(m) Satellite Band PC Services

C-201


C.3 MANAGEMENT AND OPERATIONS

This section states the Government’s management and operations related requirements. Specific management and operation report deliverables are identified in Section C.6. Test requirements are identified in Section E and delivery requirements are identified in Section F. Specific data access requirements to be made available to the Government are defined in this section.

Instructions to offeror relating to this section are provided in Section L.38.2.

C.3.1 General Information

The Management and Operations section identifies the contractor’s requirements to provide data access, reports, equipment, systems access, and other information to the responsible FTS PMO enabling the Government to manage the program and perform contract administration activities on an international scale. PMO activities include: monitoring certain contractor statistical and performance compliance with contractual obligations; facilitating customer service and satisfaction; performing contract administration; and effectively managing daily operational activities of the program. The PMO will be the Government’s primary point of contact with the contractor for the aforementioned program activities.

The requirements stated in Section C.3 pertain to the Mandatory Telecommunications Services including mandatory features provided under FTS2001. An optional feature or interface of a mandatory service must comply with the relevant requirements that pertain to that service, but need not comply exactly with the specific requirements stated for the optional feature or interface. Section C.2 presents requirements for optional features and interfaces of mandatory services and for optional services (see Section C.2.1.1.1).

The contractor shall ensure that the full operational capabilities of the customized Management and Operations Systems (MOPS) apply for new and enhanced FTS2001 telecommunications service offerings (see Section C.2.1.1.1.2) as these are implemented, except for Additional Offerings (Optional) that were proposed and accepted in conjunction with the contractor’s proposal for Mandatory Services Telecommunications The Government desires that MOPS for Additional Offerings (Optional) that were proposed and accepted in conjunction with the contractor’s proposal for Mandatory Services be as similar as possible to those MOPS provided for Mandatory Telecommunications Services.

Instructions to offerors relating to MOPS for Additional Offerings (Optional) are provided in Sections L.38.2.7 and L.38.4. See also Section B.8.19.

C-202


This section also defines the Customer Service Office (CSO) and its responsibilities; specifies service ordering processes and requirements; details billing and invoicing specifications and requirements, including disputes and adjustments; defines network management capabilities; specifies the contractor’s role in planning and engineering; defines trouble reporting requirements; and addresses training requirements.

C.3.1.1 Terms, Abbreviations, and Definitions

The following terms, abbreviations, and definitions are commonly used throughout this section of the RFP/contract and are presented here for clarification and reader convenience.

(a) Program Management Office (PMO) - An office within the FTS organization responsible for management and contract administration of a telecommunications program. Within the context of this RFP, it refers to the specific PMO responsible for the FTS2001 program.

(b) Customer Service Office (CSO) - An organization which will be established by the FTS2001 contractor to provide direct, day-to-day customer service.

(c) Agency - An authorized user organization as defined in Section H.2.

(d) Designated Agency Representative (DAR) - A Government individual who has been authorized by his or her agency to submit service requests, thereby obligating agency funds.

(e) Agency DAR Administrator - A Government individual identified by the agency who has been authorized by his/her agency to designate DARs.

(f) Service Coordinator (SC) - A Government individual identified on a service order as the program or project coordinator for completion of a service request or group of service requests.

(g) Local Government Contact (LGC) - An individual who has been identified by an agency as an on-site contact to the FTS2001 contractor to facilitate installation of service.

C-203


(h) Government Management Center (GMC) - The physical Government office facility (building and infrastructure) within which the PMO resides.

(i) Information Exchange Guide (IEG) - A document providing process descriptions, forms, and formats to facilitate electronic exchange of information.

C.3.1.2 Section Outline

The Management and Operations Section has been divided into major categories to facilitate the presentation of Government requirements; to delineate the contractor’s role and responsibilities; to perform daily operational activities; and to support PMO program management and contract administration.

Program Administration (Section C.3.2) presents the Government’s requirements of the contractor for the provision of administrative activities associated with the management and operations of the program. These activities include establishing and maintaining various lists of contact points, providing periodic statistical and performance monitoring reports, supporting user forums, providing administrative and operating data, supporting the Numbering Plan and participating in its administration, and complying with the IEG.

Program Management Office (Section C.3.3) identifies the Government’s requirements of the contractor for support of the PMO. This support includes providing dedicated and capable CSO staff possessing the technical and management skills to perform liaison activities. This support also includes the provision of compatible equipment (hardware and software) for use in the GMC by the PMO. In addition, this section describes contractor responsibilities supporting the GMC relocation facility.

Customer Service Office (Section C.3.4) presents the Government’s requirements of the contractor to establish and operate a customer service office (CSO) consisting of the contractor’s dedicated staff for providing management and operations support to the PMO and the agencies. This section also defines the contractors’ customer service functions which are be supported by its CSO.

Service Ordering (Section C.3.5) contains the Government’s requirements of the contractor specifying a user-to-contractor service ordering process; providing an automated system to facilitate this process; supporting standardized electronic transaction processing; and, retaining and processing specified Government-supplied data between the automated service ordering and billing systems.

Billing (Section C.3.6) addresses the Government’s requirements of the contractor to utilize an automated billing system; to develop a Billing System Validation Test Plan according to

C-204


the requirements of Section E.2; to support delivery of data and invoices in standard formats; and, to provide a process for disputes and adjustments.

Network Management Capabilities (Sections C.3.2.7, C.3.2.7.1 and C.3.7.7) outline the Government’s requirements of the contractor to provide network management information enabling the PMO and requesting agencies to monitor network status, performance, and service-affecting events.

Planning and Engineering (Section C.3.8) states the Government’s requirements of the contractor for ensuring reliability and availability of the contractor’s engineered services and assuring interoperability to equivalent services obtained from other FTS and Federal Government contracts, the PSN, and other existing Federal Government telecommunications infrastructure.

Trouble Reporting (Section C.3.9) presents the Government’s requirements for the contractor to provide an automated system for entering and handling trouble reports.

Training (Section C.3.10) describes the Government’s requirements of the contractor to provide training to various levels of Government staff and agency personnel. Training is either technical or non-technical in nature and is delivered (i.e., presented) utilizing a variety of disciplines.

C.3.2 Program Administration

The contractor shall work with the Government to support program management and administrative activities.

C.3.2.1 Contractor’s Program Management Office Points of Contact

The contractor shall provide the PMO with the identity of contractor points of contact, the results of national agency checks or background investigations, and the security clearance levels held by these individuals. Levels of security clearances and access authorizations required of the contractor’s personnel are discussed in Section C.2.1.12.9.

The contractor shall provide the PMO a list of the contractor’s points of contact within 30 calendar days after notice to proceed and within 5 calendar days after changes to the list. The contractor shall mark the changes to the list upon providing the update. Refer to Section C.3.2.7 for the media of delivery and Section F for other deliverable requirements.

C-205


C.3.2.2 Contractor’s Agency Points of Contact

The contractor shall identify the contractor’s personnel whom the agencies should contact for issues associated with initiating new services, changing or canceling existing services, reporting troubles, and obtaining status of outage reports, service orders, and billing inquiries. A contractor representative shall be available for continuous full-time coverage (i.e., 24 hours per day, 7 days per week). The contractor shall provide the PMO and agencies with a list of the names and telephone numbers of these contacts within 30 calendar days after notice to proceed and within 5 calendar days after changes to the list. The contractor shall mark the changes to the list upon providing the update. Refer to Section C.3.2.7 for the media of delivery and Section F for other deliverable requirements.

C.3.2.3 Reserved

C.3.2.4 Reserved

C.3.2.5 Reporting Requirements

The contractor shall provide to the PMO the reports and/or data as described in this contract.

C.3.2.6 Support User Forums

The contractor shall support user forums, i.e., periodic meetings held at least annually with members of its user community, during which topics and questions of mutual interest are discussed. The contractor shall make its representatives available at user forums to answer questions and document issues raised by agencies and to report on the status of contract modifications and the resolution of outstanding actions from previous user forums. The contractor shall provide demonstrations of new technology recently added to the FTS2001 contract. The contractor shall provide User Forum Issues Reports, as described in Section C.6.1.8 on a quarterly basis.

C.3.2.7 Data Requirements

The contractor shall provide the Government all data and information necessary to permit the Government to conduct contract administration and to manage the FTS2001 program. The contractor shall provide Customer Operational and Administrative Data (COAD) and Network Monitoring and Management (NMM) data to the Government. The contractor shall provide COAD and NMM data in near real-time through password-protected, on-line, electronic access via at least one of the methods specified in (a) through (c) below.

C-206


(a) Web Browser/Server Technology(b) Electronic Bulletin Board(c) Other on-line access to contractor’s information systems

On-line data shall be accessible using a personal computer running Microsoft Windows 95 or 98 operating system (or later versions of Windows as these become commercially available).

When more appropriate for the data requirement and/or upon request by the Government, the contractor shall provide COAD in the Government’s choice of off-line media specified in (d) through (j) below:

(d) E-Mail(e) Magnetic tape cartridge(f) CD-ROM(g) Write Once, Read Many (WORM)(h) 3.5 inch diskette(i) Paper(j) FAX

The contractor shall deliver COAD and NMM data in Microsoft Office format in versions designated by the PMO. When more appropriate, on-line data may be presented in current Web formats approved by the PMO.

A summary of contract deliverables and associated requirements is provided in Section F, Table 2-1.

Instructions to offerors relating to this section are provided in Section L.38.2.1.2.

C.3.2.7.1 Contract Administration

C.3.2.7.1.1 Program Management Office Contract Operational and Administrative Data Requirements

The contractor shall provide the PMO with access to the following types of COAD to support the PMO’s activities. This COAD shall include all available customer data and reports for the subscribed services for each functional area cited below.

(a) Service order tracking data, as described in Section C.3.5.7

(b) Trouble reporting data, as described in Section C.3.9

C-207


(c) Billing data, as described in Section C.3.6

(d) Transition, migration, and implementation data, as described in Section C.4

(e) Dispute data, as described in Section C.3.6.6

(f) Number administration data, as described in Section C.3.2.7.4

(g) Service affecting events data, as described in Section C.3.7

(h) Performance and other data, as described in Section C.6

The contractor shall provide COAD to PMO within 30 calendar days after contract award with updates upon request. Refer to Section C.3.2.7 for the media of delivery and Section F for other deliverable requirements.

C.3.2.7.1.2 Agency Customer Operational and Administrative Data Access and Delivery Requirements

The contractor shall deliver to agencies subscribing to the receipt of COAD the items specified in Section C.3.2.7.1.1(a) through (h) and service related reports as described in Section C.2 within 30 calendar days after contract award with updates upon request. The provision of access service needed to connect to the contractor’s COAD access function will be the responsibility of the customer and will use facilities provided elsewhere within the FTS2001 contract.

The contractor shall ensure that data provided to a subscribing agency or sub-agency applies to only that agency or sub-agency. Refer to Section C.3.2.7 for the media of delivery and Section F for other deliverable requirements.

C.3.2.7.2 Network Monitoring and Management Data Access and Delivery Requirements

The contractor shall deliver to the Government near real-time NMM data that the Government will use to observe the operation and performance of the services provided by the contractor.

C-208


C.3.2.7.2.1 Program Management Office Network Monitoring and Management Data Access and Delivery Requirements

The contractor shall provide the hardware and software for the PMO’s NMM workstations according to Section C.3.7.7 at no additional cost. The contractor shall provide the PMO’s NMM workstations with access to the same network monitoring and management data and information that the contractor uses to monitor and manage the services it delivers. The contractor shall specify the type of connection required to its NMM workstations at the PMO.

C.3.2.7.2.2 Agency Network Monitoring and Management Data Access and Delivery Requirements

Upon the Government’s request, the contractor shall provide access to the contractor’s network monitoring and management data. The contractor shall provide appropriate NMM workstations (hardware and software) for support of agency specific network monitoring and management requirements to any agency subscribing to such capability. The contractor shall specify the type of connection required to its NMM workstations at each subscribing agency.

The contractor shall provide a subscribing agency with access to the same type of data and information that is available to the PMO but prohibit an agency from accessing any data or information not associated with that agency.

C.3.2.7.3 Government Rights to Data and Reports

The Government reserves the right to require the contractor to provide the PMO and direct billed agencies, according to Section C.3.2.7, reports describing the derivation of data and information provided by the contractor. The contractor shall provide these reports at an additional cost to be negotiated on an individual case basis. The Government will use these reports for the purpose of contract administration and operation of the FTS2001 contract(s) and the FTS program. The Government will take all reasonable measures to ensure protection of the contractor’s proprietary rights and will not disseminate without prior permission of the contractor, except as required by law, any information marked as “contractor proprietary” to parties other than the Government or its designated representatives.

The contractor shall provide, upon request, the following data:

(a) Status and performance data concerning any system resource used in the provision of services.

C-209


(b) Status and performance data concerning automated data processing support systems used in the provision of services.

(c) Status and performance data concerning the timely delivery of services to Government locations.

(d) Billing data concerning the delivery of services.

(e) Any other data which the Government considers essential to support or resolve claims for consideration or credits, to determine compliance with the contract, and to resolve any dispute including fraud, waste, and abuse.


C.3.2.7.4 Number Administration

The Government will assign the Number Administration function to a designated Number Administrator outside of the FTS2001 contract(s).

The contractor shall provide the Government’s designated Number Administrator with information related to the contractor’s number assignments provided under the FTS2001 program. The contractor shall provide this information to the Number Administrator via SMTP or X.400-based E-Mail on a daily basis or as numbers are added, deleted, and changed. The Number Administrator will retain this information in a database so it can be accessed by FTS2001 contractors to retrieve information regarding the number assignments associated with other FTS2001 contractors.

C.3.2.7.4.1 Reserved

C.3.2.7.4.2 Contractor’s Responsibilities

The contractor shall perform the following functions at no additional cost to the Government on a daily basis or as numbers are added, deleted, and changed, unless otherwise noted:

C-210


(a) Coordinate with the Number Administrator for the exchange of information related to the assignment of on-net numbers including NANP, non-commercial agency-specific private numbers (see Section C.2.2.1.2.1), non-domestic, and other individual network contractor assigned numbers in accordance with Section C.2.1.6 which are utilized for specific network functions such as security, customer assistance, and other situations where assignment of an NANP or non-domestic number is not appropriate.

(b) Coordinate with the Number Administrator regarding information related to additions, deletions, and modifications of the contractor’s private numbers.

(c) Support PMO conducted audits as they occur to ensure accuracy of the contractor’s on-net assigned numbers.

(d) Coordinate changes in the contractor’s numbering plan with the contractor’s users.

(e) Based on input from the Number Administrator, coordinate changes in the other FTS2001 contractors’ numbering plans with the contractor’s users.

(f) Coordinate, with vendors supplying any equipment and/or services, numbering plan changes that could affect the operation of the equipment connected to the contractor’s network.

(g) Ensure that updates to its numbering plan are maintained to be current in accordance with C.3.2.7.4.2(a).


C.3.2.7.5 Reserved

C.3.2.7.6 Service Delivery Point Identification Administration

The Government will assign the SDP ID Administrator function to a designated SDP ID Administrator outside of the FTS2001 contract(s).

C-211



C.3.2.7.6.2 Service Delivery Point Identification Code

Each SDP will have an associated unique SDP ID Code. This code comprises 14 character places. The first 10 character places form the SDP ID Base Code.

The SDP ID Administrator will assign a unique SDP ID Base Code, i.e., character places 1 through 10 in Table C.3.2.7.6.2-1, to each location to which FTS2001 services are delivered. The SDP ID Base Code will adhere to the format illustrated in Table C.3.2.7.6.2-1. Each SDP ID Base Code will uniquely map to a single physical address and building. The SDP ID Administrator will not assign character places 11 through 14. All 14 characters constitute the SDP ID Code and the first eight characters constitute the Location Code. The contractor shall use the SDP ID Code for domestic as well as non-domestic locations.

Table C.3.2.7.6.2-1. Format for FTS2001 Service Delivery Point Identification Code

1 2 3 4 5 6 7 8 9 10 11 12 13 14A A A A A A X X A A X X X X

Place S/P/C Building Contractor SDP

Location Code

SDP ID Base Code Contractor Assigned

SDP ID Code

A = Alpha Characters, A-ZX = Alpha (A-Z) or Numeric (0-9) CharactersS/P/C = State/Province/Country

The SDP ID Administrator will provide FTS2001 contractors with Internet access to the records containing the SDP ID Base Codes and the related location addresses. The SDP ID Administrator will accept inputs from the DARs and FTS2001 contractors identifying new locations for which the SDP ID Administrator will create new SDP ID Base Codes.

SDP ID Codes will not be required for non-provisioned services, such as calling cards. SDP ID Codes will apply to only physical locations.

C-212


C.3.2.7.6.3 Contractor’s Responsibilities

At no additional cost to the Government, the contractor shall perform the following functions in its relationship with the SDP ID Administrator:

(a) Coordinate with the SDP ID Administrator to obtain SDP ID Base Codes when assigning a new SDP ID Code for the provision of services at a location.

(b) Complete the SDP ID Code by assigning the last four characters in the SDP ID Code when establishing a new SDP, and notifying the SDP ID Administrator of the assignment.

C.3.2.7.7 Reserved

C.3.2.8 Information Exchange Guide

The Government has developed an IEG to support the implementation of a common, consistent, and standardized approach to the electronic exchange of information. This will enable the Government and its FTS2001 contractors to conduct certain business processes electronically. The initial set of business processes include electronic submission of standard purchase order and invoice transactions, processing electronic payments, and electronic delivery of formatted reports, data, and other information.

The IEG is part of the FTS2001 RFP/contract. The IEG extends the FTS2001 RFP/contract to a greater level of detail and therefore contains certain information exchange requirements (e.g., data elements) and certain guidelines (e.g., formats) that are not specified in the RFP/contract. Any inconsistency between the RFP/contract and the IEG shall be resolved by giving precedence to the Sections A through K of RFP/contract.

The Government’s intention is to adopt new industry-wide standards and guidelines as they become available, and are integrated into commercial practice, throughout the life of the program. Changes in standards shall be implemented by the contractor in accordance with Section C.2.1.7, Conformity to Standards.

Modifications to the IEG may be required to reflect modifications that are made in other contract documents. These IEG modifications may result from the introduction of new or changed standards, advances in technology, operating experience with the FTS2001 contracts, or changes in Government requirements. Such IEG modifications may be proposed for consideration to the FTS2001 CO by any interested party, including the FTS2001 PMO, Government customers, or FTS2001 contractors.

C-213


The IEG is provided with this RFP.

C.3.3 Program Management Office

The PMO supports the following activities related to the FTS2001 contracts:

(a) Program management and contract administration(b) Centralized customer service(c) Ongoing coordination and procurement of services(d) Interoperability support(e) Billing support to agencies(f) Engineering, planning, and performance support(g) Data audits(h) Fraud detection management

Instructions to offerors relating to Section C.3.3 are provided in Section L.38.2.1.3.

C.3.3.1 Contractor’s Liaison Function

As part of the contractor’s customer service activities, the contractor shall provide a liaison function to the PMO for coordinating contractor activities within the FTS2001 Program. The contractor’s liaison function shall provide technical expertise associated with the contractor’s network management center, help desk, management chain of command, and all other contractor organizations used to provide service and support to the Government. The contractor’s liaison function shall be responsible for answering Government questions (asked by the PMO) related to the contractor’s network management activities. The contractor’s liaison function shall provide the means by which the contractor or the Government can escalate issues to the appropriate levels of the contractor’s management in order to resolve disputes, escalate contractor actions, or direct work.

The contractor liaison function shall be supported by personnel normally assigned as liaison representatives to the contractor’s customers. The contractor shall provide a list of designated personnel including name, postal address, telephone number, FAX number, and E-Mail address to the PMO within 30 calendar days after notice to proceed and updated monthly thereafter. Refer to Section C.3.2.7 for the media of delivery and Section F for other deliverable requirements.

At a minimum the contractor’s liaison representatives shall have the capability and authority to:

(a) Support disaster recovery planning and execution

C-214


(b) Resolve interoperability problems

(c) Respond to escalation of service concerns

(d) Participate in contract performance reviews

(e) Participate in contract modification negotiations

(f) Perform basic network management functions in support of the Government

(g) Help resolve billing queries and reconciliation issues

(h) Support NS/EP requirements per Section C.5.7

(i) Provide the PMO with information on customer requirements and customer demographics

C.3.3.2 Government Management Center Relocation Facility

The GMC is a Government provided facility which will house the PMO. To provide for continuity of operations if the GMC should become inoperable or inaccessible, the contractor shall provide a designated site pre-selected for relocation of up to four selected Government personnel to continue contract administration and operations management activities specific to that contractor. The contractor shall provide functional office space and equipment for Government use at the relocation site (e.g., within one of the contractor’s existing facilities). In the relocation facility, the Government shall have access to the same operational and administrative data available to Government personnel within the GMC. Workstation(s) shall be configured to allow Government access to the same NMM capabilities provided by the contractor at the GMC. The contractor shall provide access to telephone, Internet, and E-Mail services along with FAX and reproduction equipment for Government personnel use. Within 120 calendar days after contract award, the contractor shall place the relocation site in a standby condition ready to be made operational within 24 hours notice. The relocation facility shall be located within the continental United States.

The decision to close or reoccupy the GMC will be made by the Government. The Government may remain at the contractor’s relocation site indefinitely until returning to the GMC or until other arrangements can be made.

The requirement for the contractor’s GMC relocation plan is discussed in Section C.3.8(c).

C-215


C.3.4 Customer Service Office

The CSO shall be the primary contractor provided point of contact for subscribing agencies, DARs, and PMO representatives to conduct business with the contractor.

The contractor shall administer and support customer service functions. These functions include the following activities:

(a) Accepting, acting upon, and providing status on user trouble reports and complaints

(b) Accepting and acting on user service inquiries and service orders

(c) Accepting billing inquiries and providing status

(d) Providing training registration and distributing training manuals along with other training documentation

(e) Providing technical support


C.3.4.1 Establishment of Customer Service Office

The contractor shall establish and operate a CSO to provide management and operations support to the Government. The CSO shall be located on the contractor’s premises.

Because of the international nature of the services, the CSO shall conduct business 24 hours per day, 7 days per week. The contractor shall establish the CSO within 30 calendar days after notice to proceed. The CSO shall be appropriately staffed as each required function becomes operational.

The contractor’s CSO shall assign different toll free and on-net telephone numbers for accessing customer service activities. Via TDDs or functional equivalents, the contractor shall provide access to the CSO for individuals who are deaf, hard of hearing, or have speech disabilities. Calls placed to the CSO shall be answered by the contractor’s personnel within five rings.

C.3.4.2 Customer Service Office Functions Supported

The contractor shall support the customer service functions as described in the following sections or as otherwise directed by the PMO.

C-216


C.3.4.2.1 User Trouble and Complaint Reporting Procedures

The contractor shall accept trouble and complaint reports and provide the status of trouble and complaint reports within the CSO in support of the functions specified in C.3.9. The Government will review the trouble and complaint handling procedures, processes, data access provisions, performance reporting (requirements specified in Section C.6), and identified modifications to the contractor’s existing systems, if any, within 60 calendar days after contract award and may request revisions. The contractor shall submit requested revisions, if any, within 60 calendar days after receiving notice that revisions are required. The Government intends to approve final revisions within 21 calendar days after receipt. Refer to Section C.3.2.7 for the media of delivery and Section F for other deliverable requirements.

C.3.4.2.2 Accept General User Inquiries

The contractor’s CSO shall provide responses to user inquiries of a general nature such as:

(a) Contractor’s established administrative and operational procedures(b) Contractor’s points of contact(c) User forum and training information(d) Trouble report, complaint, and service order status

C.3.4.2.3 Accept Billing Inquiries

The contractor’s CSO shall provide responses to billing inquiries, such as:

(a) Credit and debit requests(b) Credit and debit status(c) Dispute status(d) Account status

C.3.4.2.4 Training Registration and Distributing Documentation

The contractor’s CSO shall manage the contractor’s training activities in support of Section C.3.10 including:

C-217


(a) Registration of attendees(b) Scheduling of classes(c) Teaching of classes(d) Development and maintenance of training materials and associated documentation

C.3.4.2.5 Provide Technical Support

The contractor’s CSO shall provide a technical group to support user agencies and the PMO regarding the services the contractor delivers to the Government. Such support shall include, but not be limited to:

(a) Answering questions related to how users can obtain the basic functions designed into the services the contractor delivers.

(b) Advising users on the capabilities incorporated into service features.

(c) Providing technical support to assist either the contractor technicians or the agencies or other organizations or personnel in the timely resolution of troubles.

(d) Notifying users of new services and features that are planned or that have recently been added to the contract.

(e) Providing support for service ordering and tracking process.

C.3.5 Service Ordering

The contractor shall provide a system for the administration and processing of service orders, service requests, and price quotes as well as and for directing and accomplishing provisioning of the ordered services.

This section addresses the contractor’s responsibilities for providing automated interface systems, maintaining Government contact lists, and processes and procedures to facilitate requests for price quotes and service ordering.


C.3.5.1 System(s) Requirements

While the Government intends to use the contractor’s existing service order processes as much as possible for ordering and tracking service orders, it requires certain minimum functionality and process coordination identified here and in the IEG.

C-218


The contractor shall provide a means whereby the PMO can gain electronic, on-line access to all service order data and agencies can gain electronic, on-line access to the agencies’ own service order data. The contractor shall provide an updated description of its service ordering system, procedures, and the related ordering intervals within 30 calendar days after contract award. The Government intends to review the updated description of the procedures and related intervals and provide comments to the contractor within 30 calendar days after receipt of the updated description of the procedures. The contractor shall provide a revised description and related ordering intervals within 21 calendar days after receipt of the Government’s comments. The Government intends to approve the final description of the procedures and related intervals within 21 calendar days after its receipt. Refer to Section C.3.2.7 for the media of delivery and Section F for other deliverable requirements.

The contractor shall provide the PMO and agencies software necessary to interface with its service ordering and tracking system. The contractor shall provide the PMO the hardware necessary to interface with its service ordering and tracking system. The contractor shall provide the subscribing agencies information needed to procure the hardware necessary to interface with its service ordering and tracking system. The contractor shall provide assistance (including help desk assistance and help screens) as part of the software application used to access its system. The contractor shall make upgrades to its service ordering templates available without charge by allowing the Government to download the upgraded templates.

Electronic Service Ordering transactions between the contractor and the Government shall conform to the ANSI X12 850 family of transaction sets, as interpreted by the Telecommuni-cations Industry Forum (TCIF) and described in the IEG. Templates are provided in Section B.2.5 of the IEG that show the essential service ordering data elements required by the Government for SVS, PSS, DTS, and Toll Free Services. The contractor shall provide the data elements identified in the IEG for the above listed services but may use its own template for entering and displaying the data.

The contractor shall provide EDI transactions for service ordering to customers that are EDI capable. Service ordering transactions that are not provided via EDI shall be provided in data formats consistent with the contractor’s existing practices as approved by the FTS2001 CO.

The approach for implementing EDI transactions for service ordering shall be consistent with the ANSI X12 850 family of transaction sets as interpreted by the TCIF and described in the IEG. EDI service ordering data models provided in Section C.2.2 of the IEG have been developed to assist the offeror in preparing its proposal. These data models were developed in consonance with TCIF efforts to define implementation guidelines for 811 and

C-219


850 transaction sets and are based on GSA’s approach to providing billing services. The Government desires that the implementation of EDI service ordering transactions be consistent with the illustrated approach.

C.3.5.2 Government Contacts

The Government will designate personnel with whom the contractor shall work to complete service orders.

C.3.5.2.1 Designated Agency Representative

A DAR is an employee of an agency who has been authorized by his/her respective agency to initiate and track service orders. An agency may designate and authorize one or more individuals who are not employees of the agency to perform DAR functions. Each agency will identify to the contractor its authorized DARs, providing the following information: name, agency represented, current address, telephone number, E-Mail address, the services the DAR is authorized to order, indication whether the DAR has expedited ordering authority. The contractor shall maintain a directory of all agency DARs, and a composite list of Government DARs. The contractor shall provide the initial version of this composite list within 60 calendar days after contract award and updated monthly thereafter. Refer to Section C.3.2.7 for the media of delivery and Section F for other deliverable requirements.

C.3.5.2.2 Agency Designated Agency Representative Administrator

Each subscribing agency will identify a DAR administrator who will make available to the contractor a current list of DARs who are authorized to initiate service requests. DAR authorization will define the types of service that the DAR is authorized to order. To the extent possible, the Government will make the list of DARs available to the contractor in an electronic format mutually agreed upon by the agency and the contractor.

C.3.5.2.3 Local Government Contact

On a service request a DAR may designate an LGC to interface with the contractor at a specific agency location. An LGC may participate in service transition planning and implementation activities for a location. The DAR will identify the LGC by name, agency represented, address, telephone number, and E-Mail address. This information is provided for contractor convenience; the contractor is not required to maintain a directory of LGCs separate from the service orders.

C.3.5.2.4 Service Coordinator

C-220


An SC may be designated on a service request to provide liaison and coordination for the services being requested. The SC will normally be an agency project or network manager responsible for the coordinated installation of multiple services, service trials, demonstrations, orders, and/or projects.

C.3.5.3 Service Price Quote Process

The contractor shall provide service price quotes as provided below. All prices quoted shall be binding on the contractor for the time period stated with the price quote.

C.3.5.3.1 Simple Price Quotes

The contractor shall propose its existing system to permit the Government to electronically request and receive service charge information that reflects current contract pricing. For simple price quotes the functionality shall be provided via Internet, IPS, dial-up access, or other access arrangement proposed by the contractor and agreed to by the Government. This capability shall allow an agency to identify a specific service and its associated features and to receive a price quote prior to submitting a service request. The contractor’s pricing information shall identify all recurring and nonrecurring charges along with the service availability interval offered. If applicable, prices shall identify charges for expedited service implementation. The pricing information shall be based upon the following information provided by the Government:

(a) Type of service and associated features(b) Location for service delivery (e.g., NPA/NXX)(c) Any additional information required to complete the price inquiry

C.3.5.3.2 Complex Price Quotes

Where complex service implementation solutions are needed to meet a stated functional requirement, more information is required than an agency simply identifying a contract service for price quote. If an agency has a complex telecommunications requirement, the contractor shall work directly with an agency representative to identify and develop technical, scheduling, and costing alternatives for consideration. In such a case, the contractor shall provide the Government a service price quote describing the technical details, price, and proposed schedule information regarding the implementation of the proposed service.

C-221


C.3.5.4 Service Order Processing

The service order process provides for an exchange of detailed service request, order, and status information between the customer and the contractor. Questions regarding technical solutions, costs, specific features, scheduling, etc., will normally be resolved utilizing the service price quote procedure.

The service order process shall follow the sequence of steps outlined below:

(a) Service Request Submission(b) Service Request Acknowledgment(c) Service Order Notification(d) Service Order Implementation(e) Service Order Completion(f) Service Acceptance/Non-Acceptance

C.3.5.4.1 Service Request Submission

Each agency will submit to the contractor requests for initiating, adding, changing or terminating service. Changes include “no charge record changes”, i.e., any changes to a record that do not install, delete, or change a billable service (such as changing a billing address, contact name, etc.). The contractor shall be responsible for directing and accomplishing tasks associated with processing the service requests. The contractor shall enable the Government to input service requests to the contractor via the following means:

(a) Voice request over telephone to the contractor (followed by written request in one of the forms found in items (b) or (c) below)

(b) Group III FAX of Completed Service Order Form/Template

(c) Electronically to its service ordering system via:

(1) E-Mail Completed Service Order Form/Template

(2) Completed Service Order Form/Template via Web Browser and Internet including electronic file transfer (e.g., via Point-to-Point Protocol, HTTP, Sun Network File System, FTP, Win FTP)

(3) EDI transactions

(4) Dial-up over voice line using a modem

C-222


The contractor’s replies to a service request shall be via one or more of the means listed above for submittal of the service request.

C.3.5.4.1.1 Service Request Templates - Functionality

Upon the Government’s request, the contractor shall provide the Government the necessary service request template software and associated software application(s) to operate on one or more of the following microcomputer-based systems:

(a) IBM-compatible PCs with Windows 3.x(b) IBM-compatible PCs with Windows (95, NT, or later) operating system(c) IBM-compatible PCs with OS/2 operating system(d) Macintosh with Mac OS operating system

This software shall present standard templates to users for their placement of service requests and shall allow users to perform the following activities associated with placing service requests:

(e) Complete templates on-line while connected to the contractor’s service ordering system.

(f) Download templates from the contractor’s service ordering system for later completion.

(g) Complete templates off-line for subsequent forwarding to the contractor’s service ordering system via the means listed in Section C.3.5.4.1.

The contractor shall make these templates available to the DARs within 30 calendar days after notice to proceed.

C-223


C.3.5.4.1.2 Service Request Templates - Information Content

The standard service request templates shall include the information in (a) through (g) below. This information is required to enable the Government to track service order implementation throughout the automated service ordering and billing systems. Information placed by the authorized DAR will include at least the following information:

(a) Service Requested. Defined in Section C.2.

(b) Agency Name. Name of agency or organization as allowed in Section H.2.

(c) SDP ID Base Code. Uniquely identifying a location where service is or shall exist, as defined in Section C.3.2.7.6.

(d) One of the following:

(1) Agency Billing Code(2) Agency Billing ID

(e) Agency Designated Hierarchy Codes. Identifying each subscribing agency organizational level for which ordering and billing data is to be aggregated. The contractor shall use these codes in its ordering and billing systems to guarantee that proper debits, credits, and accounting collection functions occur at the specified hierarchical levels. A maximum of six of these four character alphanumeric codes can be used in the Agency Hierarchy Code (see Table C.3.5.4.1.2 (e)).

Table C.3.5.4.1.2 (e). Hierarchy Codes

Agency Billing Code, or

Agency Billing ID

4 alphanumeric characters

First Agency Designated

Hierarchy Code


Second Agency Designated

Hierarchy Code


Third Agency Designated

Hierarchy Code


Fourth Agency Designated

Hierarchy Code


Fifth Agency Designated

Hierarchy Code


Sixth Agency Designated

Hierarchy Code


Reserved

2 alphanumericcharacters

Agency Hierarchy Code, 28 Alphanumeric Characters

EDI Hierarchy Code, 30 Alphanumeric Characters

C-224


(f) Service Due Date. Identifies the date when the requester expects the service order to be completed and billing to become effective. Services will be considered late if not completed by 5:00 PM local time on the service due date. If the service request does not include a service due date, the contractor shall assume a date which does not exceed the contractor’s standard service interval for the type of service requested. The service due date shall become the service order “official date” that will be monitored by the Government. To accommodate the Government’s requirements in special cases, the Government may request that the contractor’s proposed service due date be earlier or later than that determined in accordance with the standard service interval. In such cases, the earlier requested date will be handled according to Section C.3.5.5.2 Expedited Service Order Processing, and the later requested date shall be considered the “official date.”

(g) Agency Service Request Number. Uniquely identifying a service request placed by the DAR.

C.3.5.4.2 Service Request Acknowledgment

A Service Request Acknowledgment simply indicates receipt of a readable service request or service order change request by the contractor. Following receipt of a service request or change request, the contractor shall provide the Service Request Acknowledgment within the following timeframes:

(a) For electronic file transfer, E-Mail and FAX submission - by close of business of the next business day at the ordering office.

(b) For person-to-person voice transmission - immediately with written (or electronic) confirmation within five business days.

C.3.5.4.3 Service Order Notification

The contractor shall promptly review each submitted service request to ensure the validity of the authorization and of other information contained and shall respond with either a signed Service Order Notification, a written request for clarification, or with a rejection notice as appropriate. Issuance of a Service Order Notification indicates the contractor’s acceptance of the service request and marks the transition from service request to service order. Issuance of a Service Order Notification implies that sufficient information is contained in the Government’s service request so that the contractor can assign a service order number and begin processing the request. Acceptance of the service order by the Government is assumed upon the Government’s receipt of the Service Order Notification.

C-225


C.3.5.4.3.1 Authorization and Validation

Upon receipt of a service request, the contractor shall verify that the individual requesting the service is authorized to order the type of service requested and that a direct billing agency has furnished accounting appropriation data ensuring the availability of funds.

The contractor shall reject any request for service that the DAR is not authorized to order.

The contractor shall also reject any service request that is out of scope with the contract, that is not feasible or available, or that does not contain required information or sufficient information to allow service implementation. The contractor shall notify the DAR and the PMO of any rejected requests. The rejection notification shall be delivered within three business days.

C.3.5.4.3.2 Contractor-Provided Information

The contractor shall review the service request and plan to satisfy the requirement in the manner that is most efficient and cost-effective for the customer. The Service Order Notification shall indicate the approach that will be taken by the contractor to satisfy the service request (if that approach is not obvious). Thus the notification may contain a technical result that is unexpected and, possibly, unacceptable to the customer. If this is the case, the customer may instruct the contractor to either cancel or delay the service request (see Section C.3.5.6). The contractor and the customer shall work together to resolve the issue, possibly utilizing the Service Price Quote Process.

Following issuance of its Service Request Acknowledgment the contractor shall provide a Service Order Notification, a written request for clarification, or a rejection notice as appropriate to the DAR and the PMO within three business days. Refer to Section C.3.2.7 for the media of delivery and Section F for other deliverable requirements.

The contractor shall assign a unique service order ID number and shall include it on the service order notification and service order. This ID shall flow through to the invoices or invoice supporting reports for tracking purposes and invoice verification. The service order numbers shall be planned and formatted by the contractor to prevent duplication. The contractor shall complete the SDP ID Code, as described in Section C.3.2.7.6.

C-226


The Service Order Notification shall contain pertinent user information including the service order number assigned, the agency service request number, any relevant technical information, service initiation charges and other costing information that will be applied per contract, and expected service implementation date. The contractor shall include in this information the contractor’s follow-up contact name, telephone number, and E-Mail address.

C.3.5.4.4 Service Order Implementation

Upon completion of the Service Order Notification, the contractor shall begin to complete the tasks in the service order. The contractor shall complete the tasks in the service order in accordance with the committed official date.

At locations where Government involvement is required to support the installation or removal of equipment to fulfill a service order, and the due date is more than 10 days in the future, the contractor shall notify the LGC, if provided, or the DAR of needed Government actions at least 10 business days before the Government action so the contractor can comply with the installation or removal due date.

C.3.5.4.5 Service Order Completion Notice

Within 24 hours after completion of the service order the contractor shall send the Service Order Completion Notice to the Government representatives identified in the service order (DAR, SC and LGC) indicating that the service order is complete. The contractor shall use any of the means identified in Section C.3.5.4.1 that are acceptable to the Government representatives to send the Service Order Completion Notice. Voice-only notification, is not permitted.

The Service Order Completion Notice shall identify all costs including any discounted or waived costs (but not volume discounts that can not be known until the end of the month or other activity period) to be billed to the Government for the implementation of the service order. If service initiation charges were waived, the Service Order Completion Notice shall identify that service initiation charges were waived.

The contractor shall start billing for the service on the Effective Billing Date (EBD) as defined in Section C.3.6.4.5. For service disconnects, the contractor shall cease billing as of the approved or accepted disconnect date and issue a notification of the disconnect to the requester.

C-227


The contractor shall provide the PMO and direct billed agency customers with access to copies of the completed service orders via one or more of the electronic means described in Section C.3.5.4.1(a) or C.3.2.7 (a), (b), or (c). The contractor shall ensure that access to a copy of a completed a service order is available within one business day after the service order is completed.

C.3.5.4.6 Service Acceptance

When ordering the installation of service associated with transition, migration, or a major implementation project, the Government agency will require successful completion of acceptance testing of the service before permitting the contractor to invoice for the service. Upon notification by the contractor that installation is completed, the agency will conduct the 72 hour acceptance testing described in Section E.2.2.3. Upon the successful completion of this acceptance testing, the agency will notify the contractor by telephone (voice), E-Mail, or Group III FAX that the contractor may invoice the Government for the service as of the effective billing date as described in Section C.3.6.4.5.

For services being implemented other than as part of a project, the Government may, at its option, conduct acceptance tests as described in Section E.2.2.3. In these cases, unless the Government notifies the contractor to the contrary within the 72 hour testing period, the contractor may begin to invoice the agency for the service on the effective billing date, as described in Section C.3.6.4.5.

C.3.5.5 Options Within the Service Ordering Process

The contractor shall make service orders available with the following options:

(a) Standard service order intervals(b) Expedited service order intervals(c) Trials and/or Operational Capability Demonstrations for New/Enhanced Services(d) Bulk service ordering(e) Project service ordering(f) Batch service ordering

C.3.5.5.1 Standard Service Order Intervals

The standard service order intervals for both initial service and subsequent service shall be no longer than the contractor’s standard commercial intervals available to the best commercial customers of the contractor. The contractor shall notify the PMO and agencies within 30 calendar days prior to any change of the contractor’s standard service order intervals. The contractor shall obtain PMO approval at least 7 calendar days prior to any

C-228


extension of the intervals. Refer to Section C.3.2.7 for the media of delivery and Section F for other deliverable requirements.

C.3.5.5.2 Expedited Service Order Processing

The contractor shall provide an expedited service ordering process for all service types. This expedited process shall reduce the service order processing intervals below the contractor’s standard service order intervals for the following conditions:

(a) Class A. This is a condition in which an agency requires priority provisioning for NS/EP circumstances or other circumstances in which the Telecommunication Service Priority (TSP) system is invoked. Essential priorities, as certified by a TSP assignment number from the TSP Program Manager, require the contractor’s best effort to provide services by the requested date. Billing for this priority provisioning will be in accordance with TSP procedures.

(b) Class B. This is a condition that is not covered by TSP but a condition in which the standard order interval would bring hardship to the subscribing agency. A Class B expedite may be requested by an agency at any time during the service order process. The contractor shall develop a procedure for proposing an expedite schedule for accelerated service provisioning and shall inform the requesting agency of the projected expedite date. Once an agency formally requests the expedite and accepts the expedite date, related charges, as described in Section B.8.2.2, are committed even though the agency might subsequently cancel the order. Additionally, if the contractor does not meet the expedite date, the expedite charges do not apply. The expedite charges will be allowed if the expedite date is missed by the contractor due to customer caused delay. All charges for expedited service will be identified in service price quotes and Service Order Completion Notices.

The contractor shall update the draft description of the procedures that was provided with it proposal and submit it to the PMO within 60 calendar days after contract award. The PMO intends to approve the final version within 30 calendar days after receipt of the updated draft procedures. After approval by the PMO these procedures shall become part of the contract. The contractor shall submit any modifications of these procedures to the PMO for approval 30 calendar days prior to their planned implementation.

C-229


The contractor shall be permitted to reject a request for expedited service ordering provided that the contractor has sufficiently justified to the Government the reason for the rejection. This justification shall be provided by the CSO to the PMO or DAR, who will either agree, reevaluate the issue or escalate the issue to the CO for resolution.

C.3.5.5.3 Service Order Processing for Trials and/or Operational Capability Demonstrations for New/Enhanced Services

The contractor shall support Operational Capability Demonstrations (OCDs) and service trials as specified below.

(a) OCDs. An OCD shall demonstrate the contractor’s capabilities and provide service acceptance criteria. The contractor shall comply with a Government request to demonstrate a service offering, a large or complicated service upgrade for an agency, or a change to a critical facility. The conduct of an OCD shall not incur associated collateral or other cost impacts of any kind to the Government. The CO shall be notified by the contractor in writing when any OCD is planned. The contractor shall obtain written permission from the CO if the demonstration could have network affecting implications. The contractor shall report the completion of each OCD to the CO in writing.

(b) Service Trials. A service trial is defined as the use of proposed future enhancements by an agency that takes place for an agreed upon period of time, at agreed upon locations. The contractor shall provide written notification to the CO and associated agency prior to initiation of any trial program with the agency. This notification shall include the start date and duration, a copy of the informal estimate of collateral costs that the contractor gave to the agency, and the section of the contract the trial proposes to enhance. The CO will respond with approval or rejection within 15 business days after receipt of the notification. The contractor will not be reimbursed for trial costs exceeding the cost estimate unless prior approval for such costs has been made by the CO. The contractor shall report the status of all trials to the PMO in accordance with the reporting requirement in Section C.6.1.10. The contractor shall report the completion of each trial to the CO in writing.

C.3.5.5.4 Processing of Multiple Service Requests

The contractor shall accept bulk, project, or batch groupings of multiple service requests at the request of the agencies. The contractor shall process the multiple requests under the same conditions that the contractor would receive and process a single service request.

C-230


(a) Bulk Service Ordering Processing. The contractor shall provide the capability for an agency to submit “bulk” service requests, i.e., multiple requests for the same service with the same features via a single service request. The contractor shall ensure that each item is processed separately and stands alone for future potential activity. Refer to Section C.3.6.4.4.

(b) Project Service Order Processing. The contractor shall provide the capability to submit service requests based on a particular project, i.e., “project” service requests. Project service requests are related and should be implemented as a group in a coordinated fashion. The contractor shall accept project identifiers associated with project service requests. The contractor shall issue Service Request Acknowledgments, and Service Order Completion Notices, etc., that include these project identifiers. The contractor shall provide the capability for agencies to track the status of these orders using the project identifiers. Notices of completion and billing reports shall include project identifiers.

(c) Batch Service Order Processing. The contractor shall provide the capability for the Government to submit “batch” service requests in which individual service requests have been aggregated into a composite file that is forwarded via electronic file transfer to the contractor. The contractor shall accept service requests submitted in a batch mode and have the capability to process the individual requests contained in this aggregate file in the same manner it would process the receipt of separate service requests. No requirement shall exist for the individual service requests to contain any similarities.

C.3.5.5.5 Change of Service Order Record Data

The contractor shall accept and process requests to update service order records. The contractor shall update service order records at no additional cost to the Government. Service order record changes shall be accessible along with copies of completed service orders that are available to the PMO and direct billed agency customers in accordance with Section C.3.5.4.5.

C.3.5.6 Changes During Service Order Process

The contractor shall accept and process service order cancellations and changes from the DARs using the contractor’s own service order supplement procedure so that the sequence of service request revisions is clearly distinguished. For example, an ascending alpha character could be assigned for each supplement.

C.3.5.6.1 Agency Cancellation of Service Order

C-231


An agency has the right to cancel any service order at any time during the service order process. If the cancellation request is issued at least ten business days prior to the service due date for bandwidths equal to or below T1, the contractor shall assess no charges to the agency. If the cancellation request is issued at least 45 calendar days prior to the service due date for bandwidths above T1, the contractor shall assess no charges to the agency. Section B.8.2.2 specifies the way charges may be applied for cancellation requests received less than aforementioned time intervals prior to the service due date. Refer to Section C.3.2.7 for the media of delivery and Section F for other deliverable requirements.

C.3.5.6.2 Change of Service Order Due Date

An agency may delay a service order due date at any time during the service order process. If the request for one delay is issued at least ten business days prior to the service due date, no charges will be assessed to the agency. Section B.8.2.2 of this RFP specifies the way delay charges may be applied for delay requests received less than ten business days before the service due date. When a service order is delayed once by an agency, the new implementation date shall be negotiated between the contractor and the agency. When the renegotiated access due date arrives, the contractor may begin charging for the access costs unless the agency elects to cancel the service order. The contractor shall not delay a service order due date unless agreed to by the agency DAR requesting the service.

C.3.5.7 Service Order Tracking

The contractor shall provide service order tracking capabilities to the PMO and to subscribing agencies in accordance with its existing system as specified in Section C.3.5.1. This capability shall provide the Government with the means to determine the status of service orders from service request to order completion. This capability shall permit the Government to identify the contents and status of all in-progress service orders by the following groupings:

(a) Services(b) Agencies(c) Service Due Dates(d) Project Identifiers(e) Locations(f) Service Order ID Number

Upon an agency’s subscribing to this capability, the contractor shall make this information available on an agency-specific basis as specified in C.3.5.1.

C-232


C.3.5.8 Service Order Measurements

The contractor shall collect and make available to the Government measurements to assess the performance of processing service orders.

C.3.5.8.1 Service Order Tracking and Administrative Measurements

In accordance with Section C.3.2.7.1.1, the contractor shall provide the following statistics associated with service requests. The contractor shall provide this information to the PMO and subscribing agencies in a monthly report (if requested by the PMO or subscribing agency) within fifteen business days after the end of the previous month. Refer to Section C.3.2.7 for the media of delivery and Section F for other deliverable requirements. This information shall include:

(a) Number of requests by type and status (open, rejected, closed, etc.)(b) Number of requests by request interval type(c) Number of requests by submission method(d) Number of requests by requesting agency(e) Number and cost of requested date changes(f) Number and cost of canceled requests

C.3.5.8.2 Service Order Performance Measurements

The contractor shall provide a report generation capability for obtaining reports that summarize service order activities that occurred during the reporting interval as specified in Sections C.6.1.3.

C.3.5.9 Service Order System Validation Test Plan

The requirements for testing are described in Section E.2.3.2. No agency-initiated service orders will be processed until the Government certifies that the contractors Service Ordering System meets the approved criteria agreed upon in the Service Order System Validation Test Plan. The Government reserves the right to require the development of additional test plans and/or to conduct joint testing of the contractor’s Service Order System during the life of the contract. The cost for the development of additional test plans and/or the conduct of joint testing for the contractor’s Service Order System will be negotiated on a case-by-case basis.

Instructions to offerors relating to Section C.3.5.9 are provided in Section L.38.2.1.10.2.

C-233


C.3.6 Billing


C.3.6.1 Billing Overview

This section addresses the contractor’s responsibilities for system requirements and test validation of the billing system according to the requirements of Section E.2.3.3, data requirements, billing requirements, invoice requirements, dispute process requirements, and special billing requirements.

Note, the Government recognizes that the billing processes and requirements specified herein may actually be provided by more than one contractor system. The use of the term billing “system” herein should not be construed to require the contractor to provide the billing processes using only one system.

FTS2001 allows agencies to select either centralized or direct billing. After award and before notice to proceed, the PMO will identify to the contractor which agencies and/or sub-agencies will receive centralized or direct billing. The contractor shall produce payable invoices for both options, billing details are further described in Sections C.3.6.2, C.3.6.5, C.3.6.6, C.3.6.7, C.3.6.8, and G.1.

(a) For centralized billing, the contractor shall provide an invoice and CDR to GSA for payment and processing.

At the Government’s request, the contractor shall deliver its CDR data directly to an agency or sub-agency in electronic format as specified in Section C.3.6.3.1.

(b) For direct billing, the contractor shall provide an invoice and CDR to each agency or sub-agency, as directed by the PMO, for payment and processing.

(c) For centralized and direct billing, the contractor shall manage a base GSA Management Service (GMS) fee. The contractor shall include this base GMS fee in all of its published prices. The Government will advise the contractor after award the amount of this fee in terms of a percentage to be applied to all of the contractor’s base prices. The Government will evaluate the GMS fee on an annual basis. The contractor shall implement changes in the GMS fee at no additional cost to the Government. The contractor shall collect a base GMS fee from the direct billed agencies. The contractor shall remit the total GMS fees on the revenue collected from the direct billed agencies, along with a list of the directly invoiced agencies or sub-agencies as provided in Section C.6.4. The payment shall be made

C-234


to GSA via direct payment (not as a credit on the invoice) within 60 calendar days after the end of the applicable reporting period. For direct billed agencies the contractor shall not show the GMS fee as a separate item on the invoice. For centralized billing, the contractor shall show the GMS fee as a separate item and shall subtract the GMS fee from the gross amount due to show the net amount due from GSA.

Upon 90 days notice by the PMO, the contractor shall change an agency or sub-agency from centralized to direct billing or vice versa, at no additional cost to the Government.

If the full amount of the GMS fee is not paid within 60 calendar days after the end of the applicable reporting period, the nonpayment shall constitute a contract debt to the United States Government under the terms of Part 32.6 of the Federal Acquisition Regulations.

GSA is responsible to pay the contractor only for the FTS2001 centralized invoices which charge the centralized billing user agencies or sub-agencies. GSA, while offering two billing methods for FTS2001, will not be responsible for any charges directly invoiced to any agency or sub-agency. The contractor shall be responsible for the collection of charges from the directly billed agencies or sub-agencies.

C.3.6.2 System Requirements

The contractor’s billing system’s capabilities, shall meet the following requirements:

(a) Support a volume of billing transactions commensurate with the traffic levels provided in Section J.8.

(b) Support the suppression of CDRs for any service that generates CDRs for selected users as specified and approved by the PMO. The contractor shall summarize separately, for each agency suppressing CDR, the suppressed call charges, number of calls, and call minutes by Agency Billing Code for purposes of balancing the invoice.

C-235


(c) Support, to the extent possible, consolidated invoicing for services that use the same billing period.

(d) Support date management in compliance with year 2000 requirements. The system shall function properly during the transition to year 2000 and for the duration (including any extensions) of this contract.

The contractor shall allow the Government to audit the contractor’s billing process with at least 10 business days notice and identification of the purpose of the audit.

The contractor shall provide a description(s) of the commercially available formats of all records provided in the invoice. To the extent possible, these records shall conform to the ANSI X12 811 transaction set as interpreted by the TCIF and described in the IEG.

The contractor shall:

(e) Provide the PMO a consolidated invoice of charges for all agencies receiving GSA’s centralized billing.

(f) Provide consolidated invoice charges to all agencies and sub-agencies electing to use direct billing.

(g) Provide the PMO one consolidated invoice copy of all charges sent to agencies receiving direct billing.

C.3.6.2.1 Billing System Validation Test Plan

The Billing System Validation Test Plan shall assure that billing support data required to verify each invoiced charge will be processed through the contractor’s billing system to the invoice, including the following data:

(a) Government-provided

(1) Agency Billing Code (for centralized accounts)(2) Agency Designated Hierarchy Codes(3) Accounting Control Transaction (ACT) number (Section C.3.6.5.6)(4) PMO and Agency generated dispute ID numbers(5) Agency Billing ID (for direct accounts)

C-236


(b) Contractor-provided

(1) Reserved

(2) Contractor service order ID number(unique service order identification number as defined in Section C.3.5.4.3.2)

(3) Service order effective billing dates

(4) Unit quantities accepted from a service order

(5) On-net telephone numbers

(6) Contractor adjustment ID numbers

(7) Service outage credit ID number

(8) Traffic volumes

(9) Revenue discounts

(10) SDP ID code

(11) Contractor dispute ID number

The contractor shall participate in validation test of its billing system in accordance with the requirements of Section E.2.3.3. No agency-initiated service orders will be processed for billing until the Government certifies that the contractor’s billing system meets the approved criteria agreed upon in the Billing System Validation Test Plan. The Government reserves the right to require the development of additional test plans and/or to conduct joint testing of the contractor’s billing system during the life of the contract. The cost for the development of additional test plans and/or the conduct of joint testing for the contractor’s billing system will be negotiated on a case-by-case basis.

Instructions to offerors relating to Section C.3.6.2.1 are provided in Section L.38.2.1.10.3.

C.3.6.3 Billing Data Requirements

This section addresses the requirements for data exchange, data retention, and Government required billing data.

C-237


Electronic invoicing transactions between the contractor and the Government shall conform to the ANSI X12 811 family of transaction sets, as interpreted by the TCIF and described in the IEG. Templates are provided in Section B.3.3 of the IEG that show the essential invoicing data elements required by the Government for SVS, PSS, DTS, and Toll Free Services. The contractor shall provide the data elements identified in the IEG for the above listed services but may use its own template for entering and displaying the data.

The contractor shall provide EDI transactions for billing customers that are EDI capable. Invoicing transactions that are not provided via EDI shall be provided in data formats consistent with the contractor’s existing practice as approved by the FTS2001 CO.

The approach for implementing EDI data models for invoicing shall be consistent with the ANSI X12 811 family of transaction sets as interpreted by the TCIF and described in the IEG. EDI invoicing data models provided in Section C.3.2 of the IEG have been developed to assist the offeror in preparing its proposal. These data models were developed in consonance with TCIF efforts to define implementation guidelines for 811 and 850 transaction sets and are based on GSA’s approach to providing billing services. The Government desires that the implementation of EDI invoicing transactions be consistent with the illustrated approach.

C.3.6.3.1 Data Exchange

C.3.6.3.1.1 Centralized Billing Data Exchange

The contractor shall deliver all of the centralized billing data elements to the PMO and CDR to authorized users monthly. Refer to Section C.3.2.7 for the media of delivery and Section F for other deliverable requirements.

C.3.6.3.1.2 Direct Billing Data Exchange

The contractor shall deliver all of the direct billing data elements and CDR to the agencies or sub-agencies which are authorized for direct billing and the PMO monthly. Refer to Section C.3.2.7 for the media of delivery and Section F for other deliverable requirements.

C.3.6.3.2 Data Retention

The contractor shall retain all data, hardcopy, letters, memorandums, adjustment data and other data pertaining to the billing of contract services as specified in Section I.9. The contractor shall provide this data to the Government within 10 business days after receiving the Government’s request for the data.

C-238


C.3.6.3.3 Government Required Billing Data

The contractor shall ensure that the Agency Billing Code for centralized billing accounts, Agency Billing ID for direct billing accounts, Agency Hierarchy Code, SDP ID Base Code, SDP ID Code, and contractor service order ID number, where appropriate, appear on the invoice or invoice supporting report.

C.3.6.4 Billing Requirements

This section addresses the Government’s requirements regarding the billing of charges, Service Initiation Charges (SIC), allocation of non-ANI data, bulk, project, and batch orders as well as clarifying already established EBDs, and third party bills.

C.3.6.4.1 Billing of Charges

The Government desires a billing period that runs from the 1st through the 31st of the month for the majority of the contractor’s services. However, the Government will accept billing periods other than the 1st through the 31st of the month for those services for which the contractor bills commercially in such billing periods. The contractor shall invoice all services having the same billing period either on a consolidated invoice reflecting that billing period or use “electronic stapling” for invoices in that billing period. The contractor shall submit only one invoice per billing period for a service. The contractor shall notify its directly billed customers that they will receive multiple invoices at differing times of the month and the times of the month when the contractor’s customers will receive these invoices. The contractor shall invoice any service up to 90 calendar days after the close of the billing period in which the service was rendered. Services not invoiced within this 90 day period shall not be payable by the Government.

The contractor shall use “electronic stapling” to combine invoices the contractor does not aggregate into a single consolidated invoice. In this context, the term “electronic stapling” is the process of combining individual invoices created by separate billing systems into a single invoice.

C.3.6.4.2 Billing of Service Initiation Charges

The contractor shall bill the entire SIC, and may indicate waived or discounted charges, on the invoice following acceptance by the Government for the installation of the service contained in the completed service order.

C-239


C.3.6.4.3 Allocation of Non-Automated Number Identification Data

The Government will provide station allocation data down to three decimal places. The contractor shall ensure that all data regarding allocations at GSA consolidated switches and/or data presented for allocation by an exclusive-use host, received within 15 calendar days after the close of the billing period for a service, shall be utilized in the contractor’s billing for the following month’s charges for the service. The contractor shall utilize the data to three decimal places to allocate the total charges, total number of calls, and total called minutes on the invoice data to the proper levels of the Agency Hierarchy Code.

C.3.6.4.4 Billing of Multiple Service Requests

The contractor shall provide itemized billing when processing multiple service requests. The contractor shall ensure that billing items, which were ordered in bulk, project, and batch format may be separated or processed singly without disrupting the activity of other billing items. For example, it shall be possible to separate one calling card from the original order of 10 calling cards without affecting the billing associated with the other calling cards.

C.3.6.4.5 Effective Billing Dates

The period for which the contractor bills shall:

(a) Begin on the EBD, that is, the start date of successful (72-hour) acceptance testing for provisioned services as defined in Section E.2.2.3.

(b) Stop on the disconnect date requested by the agency.

C.3.6.4.6 Service Order Delay, Expedite, or Cancellation Charges

When additional or fractional charges apply for cancellations, due date changes, or expedites, the contractor shall enter the charged amount on the service order and process charges resulting from the completed order through to the invoice.

C.3.6.4.7 Reserved

C.3.6.4.8 Access Billing Allocation

For the purposes of billing access, the channels on the access circuit are divided into two categories, shared and non-shared. Shared access channels are those that may be used by different users at different times; non-shared access channels are those that can be used only by one user. SVS access channels to a PBX/CENTREX may be shared; DTS and SDS channels are dedicated to individual users and generally are not shared. CSDS channels may

C-240


be shared if they are routed through an appropriate digital PBX/CENTREX or equivalent. The Government will designate shared and non-shared channels where necessary to ensure correct billing.

Each month the contractor shall ensure the identification and allocation, for billing, of integrated access. For billing purposes, charges for the access circuit shall be allocated by the contractor equally to each active channel.

For non-shared channels, these allocated charges shall be billed to the appropriate parties as designated by the Government.

For shared channels, further allocation shall be performed by the contractor before billing as follows:

(a) Where ANI (or equivalent) is available, the contractor shall bill charges to the appropriate parties as designated by the Government by allocating charges based on actual usage (outbound usage for non-toll free, inbound usage for toll free). The Government will provide appropriate station identification data to allow the contractor to associate stations with billed parties.

(b) Where ANI (or equivalent) is not available, the Government will provide allocation factors (up to three decimal places). The contractor shall bill charges to the appropriate parties as designated by the Government using these allocation factors.

(c) The Government reserves the right to provide allocation factors for any location to be used in lieu of all other allocation methods.

C.3.6.4.9 Third Party Billing

When a host agency sub-lets reservations-based telecommunication services to another agency, the contractor shall provide a billing capability to enable the individual usage, monthly recurring charge, and/or non-recurring charge to be billed to the Agency Hierarchy Code of the agency using the telecommunications services.

The agency sub-letting the reservation-based service will provide necessary invoicing information to the contractor at the time the reservation is made.

C-241


C.3.6.5 Invoicing Requirements

This section addresses invoice payments, withholding invoice payments, invoice balances, invoice discounts, the contractor’s responsibilities for delivery of the invoice, invoice content, invoice format, and making invoice changes.

C.3.6.5.1 Invoice Payment

The payment of a proper invoice will be made by the Government as detailed in Sections G.1 and I (FAR 52.232-01, Payments).

C.3.6.5.2 Withholding Payment of Invoice

The Government reserves the right to withhold a partial or entire payment of an invoice as detailed in Section I (FAR 52.232-01, Payments).

C.3.6.5.3 Invoice Balances

The contractor shall maintain records of the current status of its financial accounts and support PMO and directly billed agency inquiries to reconcile account balances within two (2) business days after receipt of notification by the PMO or the agency.

C.3.6.5.4 Discount Reporting

The contractor shall report discounts for the current invoice as a separate line item credit on the current invoice on the totals page to be clearly distinguished from the charges for each service. However, if the vendor can give discounts to a chargeable line item, then the Government desires that the discount be shown at the hierarchy level versus the Agency Billing Code level. The contractor shall deduct this credit from the current invoice charges.

C.3.6.5.5 Invoice Delivery

Instruction for delivery of invoices are specified in Section G.1.

C.3.6.5.6 Invoice Content

The contractor shall consolidate FTS2001 services where possible and submit invoices according to the requirements of Section C.3.6.4. The contractor shall ensure that all charges are shown on the invoices and no additional tapes or materials are required by the Government to verify all price elements. The invoices shall also include additional items consistent with the contractor’s existing practice. The contractor shall carry the appropriate contract ACT number on its invoices. Any changes to the invoice content, including

C-242


changes resulting from the inclusion of future services, enhancements, which are in accordance with commercial invoicing capabilities shall be implemented at no additional cost to the Government.

C.3.6.5.6.1 Invoice Totals Page

The contractor shall identify its current month’s charge as a separate entry on the invoice. The contractor shall show any contractor-generated adjustments and discounts as separate entries on the invoice or invoice supporting reports. The contractor shall include PMO and agency disputes as separate entries on the invoice.

C.3.6.5.6.2 Invoice Summary Section

The contractor shall have an Agency Summary Section which depicts charges for all types of services at the Agency Hierarchy Code level.

C.3.6.5.6.3 Invoice Detail Section

The contractor shall include a service order activity section and a detailed billing activity section that is grouped by Agency Hierarchy Code. These sections shall be used to provide Other Credits and Charges (OCC) invoice data. The OCC type of invoice data shall include Service Initiation Charges and Feature Initiation Charges in accordance with the ANSI/TCIF 811 transaction set.

The contractor shall ensure that the detailed sections will group the current recurring and non-recurring charges, adjustments, surcharges, and special allowances in the manner specified by the Agency Hierarchy Code in a manner consistent with commercial practice. The contractor shall show all federal, state, and local taxes and surcharges as separate line items.

C.3.6.5.6.4 Call Detail Records

The contractor shall identify the lowest level of call origination possible, i.e., the originating station calling number, authorization code, or trunk as appropriate. The Government considers the CDR data to be sensitive information, and the contractor shall take appropriate safeguards to protect it. The CDR shall contain sufficient data elements to verify the charges that it represents. Each price element in the CDR shall be uniquely identified with its Service Configuration Identification (SCID) numbers, its SCID type number, and its location code (if applicable). All on-net charges shall be referenced to the appropriate SDP ID Code.

C-243


The contractor shall deliver all CDR for both centralized and direct billed agencies to the PMO monthly.

The Government reserves the right to instruct the contractor, with 60 days notice, to also distribute the CDR to specified agencies using centralized billing. The contractor shall provide its standard end-user software report generation tools, when available at no additional cost to the Government.

The contractor shall distribute the CDR to directly billed agencies or sub-agencies. Delivery of the CDR shall include the contractor’s standard end-user software report generation tools, when available at no additional cost to the Government.


C.3.6.5.7 Invoice Format

The contractor shall use a format in accordance with the ANSI/TCIF 811 transaction set. These formats, as well as formats for future services, enhancements, or changes shall be implemented at no additional cost to the Government when consistent with commercial practice.

C.3.6.5.8 Invoice Changes

The contractor shall provide 60 calendar days notice to the PMO in writing before making changes to the invoice content or format. The frequency of such changes, including changes resulting from the introduction of new services or industry standards modifications, shall not exceed once every 60 calendar days unless the change was mandated by a Federal, state, and/or local public utility regulatory authority or such other process that requires implementation in less than 60 calendar days. The contractor shall provide a detailed specification of the revised format to the PMO. Refer to Section C.3.2.7 for the media of delivery and Section F for other deliverable requirements.

Invoice changes initiated by changes in the invoice standards by an authorized regulatory body or at the direction of the contractor shall be done at no cost to the Government. The contractor shall obtain written approval from the CO to initiate an emergency change. All changes will be reflected in updates to the IEG.

C-244


Agencies and/or sub-agencies that elect direct billing may request invoice changes to their invoice content or format through contract modifications via the PMO. Charges for invoice formats that differ from the standard FTS2001 invoice format (i.e., customized formats) shall be addressed on an individual case basis.

C.3.6.6 Disputes and Adjustments

This section addresses the separate issues of PMO and agency filed disputes as well as adjustments initiated by the contractor due to discrepancies in an invoice.

The Government intends to participate with industry in accredited standards bodies to develop standard EC/EDI transaction sets for disputes, adjustments, and service credit outages. Until such standards are developed, dispute, adjustment, and credit reports shall be provided as identified in Section C.6 and containing data elements as defined in Sections B.4 and B.5 of the IEG. Dispute numbers, credit numbers, or other data that are included on the contractor’s invoice shall conform to the ANSI X12 811 transaction set as interpreted by the TCIF and described in the IEG.

The Government will accept a pro-rata GMS fee adjustment for disputes and adjustments in cases where a dispute is made against a prior invoice period(s) for which payment by the Government has already been made and GMS fees have been paid by the contractor.

C.3.6.6.1 Program Management Office Disputes

The contractor shall, upon the receipt of a dispute from the PMO, assign its own dispute number. The contractor shall return a dispute receipt acknowledgment to the PMO showing the assigned billing dispute number for tracking purposes.

After resolution of the PMO dispute, this contractor-assigned dispute number shall appear on the invoice or invoice supporting reports with the debit or credit line item at the appropriate level of the Agency Hierarchy Code. The dispute number area on the invoice or invoice supporting reports shall comply with the appropriate ANSI/TCIF 811 transaction set.

If the contractor’s billing system is unable to accommodate incorporation of the dispute number on the invoice, the contractor shall provide the dispute information in a management report containing dispute numbers. This information shall be at the appropriate level of the Agency Hierarchy Code.

C-245


C.3.6.6.2 Agency Disputes

The contractor shall, upon the receipt of a dispute from a centralized or directly billed agency, assign its own dispute number. The contractor shall return a receipt acknowledgment to the agency, with a copy to the PMO on an as required basis, showing the assigned dispute number for tracking purposes.

After resolution of the agency dispute, this contractor-assigned dispute number shall appear on the invoice or invoice supporting reports with the debit or credit line item at the appropriate level of the Agency Hierarchy Code. The dispute number area on the invoice or invoice supporting reports shall comply with the appropriate ANSI/TCIF 811 transaction set.

If the contractor’s billing system is unable to accommodate incorporation of the dispute number on the invoice, the contractor shall provide the dispute information in a management report containing dispute numbers. This information shall be at the appropriate level of the Agency Hierarchy Code.

C.3.6.6.3 Contractor Adjustments

The contractor shall notify the PMO and all directly billed agencies and sub-agencies immediately of any contractor initiated invoice errors via E-Mail, electronic file transfer, or FAX. The contractor shall assign a unique adjustment number, which shall be used for tracking purposes.

After resolution of the contractor adjustment, the contractor-assigned adjustment number shall appear on the invoice or invoice supporting reports with the debit or credit line item at the appropriate level of the Agency Hierarchy Code. The contractor shall not issue a check to any agency or to the PMO for chargeback to the agency.

C.3.6.6.4 Program Management Office and Agency Dispute Resolution Timetable

The contractor shall, upon the receipt of a PMO or agency dispute, adhere to the following time frames within which to resolve the dispute unless otherwise extended by the PMO:

(a) 30 calendar days for individual disputes less than or equal to $10,000(b) 60 calendar days for individual disputes over $10,000

C-246


The contractor shall process the dispute debit or credit for the exact amount in dispute on the next invoice for all resolved disputes. The contractor shall submit resolutions that are less than the exact amount in dispute to the dispute’s initiator for acceptance or denial. The PMO or agency initiator will respond with a proposed resolution. If negotiations between the contractor and the dispute’s initiator fail to achieve resolution, the PMO or agency will escalate the dispute to the CO, who will work with all parties to reach a mutually agreeable resolution.

After award the contractor shall work with the PMO to develop procedures identifying documentation required to support disputes and to develop a process to avoid generating duplicate disputes raised by both the PMO and an agency. After contract award, the contractor shall negotiate specifics regarding the dispute process with the PMO.

The contractor shall, for any dispute or adjustment totaling over $50,000, contact the agency or PMO for direction on which specific invoice the parties involved want the debit or credit to be processed.

C.3.6.6.5 Dispute and Adjustment Database and Adjustment Reports

The contractor shall deliver to the PMO by the 5th business day following close of the billing report period for each service one copy of its Dispute Database (see Section F) representing the complete status of all disputes at the close of the reporting period for each service. The Dispute Database shall identify all dispute activities for the reporting period for that service and show the balance forward data at the beginning and end of the reporting period. The contents of the database are described in Section C.6.1.5.1.

The contractor shall deliver one copy of its Monthly Adjustment Database to the PMO by the 5th business day of the month following close of the billing report period for each service. The database shall identify all adjustments being made to the centralized invoice to correct any previous reporting period billing errors and shall identify the Agency Billing Code, Agency Hierarchy Code and service order ID number as appropriate for each adjustment amount. The contents of the Adjustment Report are described in Section C.6.1.6.1.1.

The contractor shall deliver to each agency using direct billing, one copy of a Dispute Database, by the 5th business day of the month following close of the billing report period for each service, as described in Section C.6.1.5.2, which shall reflect only that agency’s monthly dispute activity.

C-247


The contractor shall deliver to each agency using direct billing, one copy of a Monthly Adjustment Database, by the 5th business day of the month following close of the billing report period for each service, as described in Section C.6.1.6.1.2, which shall reflect only that agency’s activity.

The contractor shall deliver to the PMO by the 15th business day following close of the billing report period a Dispute Report.

The contractor shall deliver to the PMO by the 15th business day following the close of the billing report period a Monthly Adjustment Report.

The contractor shall deliver to each agency using direct billing, one copy of a Dispute Report by the 15th business day of the month following the close of the billing report period.

The contractor shall deliver to each agency using direct billing, one copy of a Monthly Adjustment Report by the 15th business day of the month following the close of the billing report period.

For the Dispute and Adjustment Reports, the Government is seeking to know the status of disputes and adjustments at close of the billing period for that service. The Government recognizes that not all disputes and adjustments for a particular billing period may be reflected in the reports due for the period because of a lack of certain information. The contractor shall include in the next billing period’s report dispute and adjustment information not contained in the previous billing period’s report for a service.

C.3.6.7 Agency Service Outages

This section addresses the issue of agency filed trouble reports for service outages and contractor reported service outages, potentially involving service credits, as described in Section H.13.

C.3.6.7.1 Credit for Service Outages

The contractor shall assign a trouble reporting number to each outage, whether reported directly by the agency or discovered by the contractor, and advise the agency of this number. After resolution of the service outage, the contractor’s assigned trouble reporting number shall appear on the invoice or invoice supporting reports with the amount credited. No checks for such credit shall be issued to the agency, sub-agencies, or GSA. The trouble number for the credit shall appear on the invoice or invoice supporting reports in compliance with the ANSI/TCIF 811 transaction sets.

C-248


C.3.6.7.2 Agency Service Outage Resolution Timetable

The contractor shall process credits for reported service outages on an invoice within three billing cycles (90 calendar days) for all services.

C.3.6.8 Special Billing Arrangements

The contractor shall bill in accordance with specifications of this contract unless special billing arrangements are approved in advance by the PMO. Special billing arrangements include the following situations in Sections C.3.6.8.1 through C.3.6.8.3.

C.3.6.8.1 Transition Billing Arrangements

The contractor shall, upon the instruction of the PMO, arrange for SIC charges to be separately billed to the PMO and not to the agencies that are being transitioned.

C.3.6.8.2 Migration Billing Arrangements

The contractor shall, upon the instruction of the PMO, arrange for SIC charges to be separately billed to the PMO and not to the agencies that are being migrated.

C.3.6.8.3 New Services Billing Arrangements

The contractor shall, while planning for new services or enhancements, work with the PMO to plan and coordinate methods and procedures for billing the services. The contractor shall not issue a separate invoice outside the ACT number assigned to this contract. Billing for new services shall be integrated with existing consolidated invoices for the same billing period to the extent possible.

C.3.7 Network Management

This section specifies the quantity and type of Network Management (NM) data the Government needs for its administration of this FTS2001 contract.


C-249


C.3.7.1 Network Service Affecting Event Information

The contractor shall provide the PMO access to current information regarding the service affecting event types listed below in items C.3.7.1(a) through (f). The contractor shall make this information available to the PMO using its existing NM reporting system and delivery methods.

The contractor’s network management system shall enable the Government to monitor service-affecting events from the NMM workstations located at the PMO and at subscribing agencies. Events considered to be service-affecting include the following:

(a) Outages of network switches or facilities, including planned outages

(b) Outages causing site impairments and/or isolations from service

(c) Faults/failures of other network elements, such as routers and multiplexers

(d) Outages/failures of major access facilities

(e) Any hazardous condition that has the potential for major service impact

(f) Network controls initiated by the contractor

To the extent possible using the contractor’s existing systems, the form of presentation of such service-affecting events at each NMM workstation shall include visuals (e.g., color and/or motion changes), and/or audible alarms, and textual message shall be associated with an audible and/or visual alarm to provide information about the reported event. The service affecting event information shall contain, at least, the following types of data:

(g) Event description (e.g., definition of problem)

(h) Event date and detected time

(i) To the extent possible, service(s) affected by the event

(j) Information about detection of service affecting events for peripheral network resources indicating whether the event is internal or external to the contractor’s network

(k) To the extent possible, identification of agencies affected by the event.

C-250


The contractor shall make only the information applicable to an agency available to that agency.


C.3.7.1.1 Electronic Access to Network Fault Management Status

To the extent possible within the constraints of the contractor’s existing NM system, the contractor shall provide electronic, on-line access with appropriate security controls to NM status (preferably via a Web site) to inform agencies and the PMO of major outages or potential hazards to service on a real-time basis. This electronic access shall be utilized by the contractor to present clearance of these same situations.

C.3.7.2 Network Configuration Management

The contractor shall provide notification to the PMO of any contractor network and related support systems’ configuration changes affecting or likely to affect users’ services and resources. In addition, the contractor shall notify and coordinate with the PMO and affected agencies regarding planned network maintenance activity for shared facilities supporting the subscribed services and related support systems (hardware and software) that likely could affect users’ services.

When requested the contractor shall maintain and provide access to a network configuration database that shows the connectivity between significant network components. This database shall enable the PMO and/or agencies to perform impact analyses on their networks during outages. Charges for this access shall be negotiated on an individual case basis.

C.3.7.3 Network Accounting Management

The contractor’s network accounting management system shall provide for the generation and distribution of usage data to support Government monitoring for detection of agency waste, fraud, and abuse; contract compliance; and telecommunications planning.

C.3.7.4 Network Performance Management

The contractor shall provide all subscribing agencies and the PMO with access to all available customer performance reporting capabilities for subscribed services on the same basis (i.e., means of delivery, frequency, and content) that they are available to other customers.

C-251


C.3.7.5 Network Security Management

The contractor shall provide network security services as specified in Section C.2.1.12, “Security of Contractor Infrastructure.” The contractor shall report to the PMO via E-Mail or facsimile within the time frame normally provided its commercial customers for notification after detection of each unauthorized intrusion, of fraudulent use of services, and all other security breaches. The contractor shall provide the PMO with a monthly Status of Network Fraud and Security Breach Detections Report. The report shall contain the information as described in Section C.6.1.1. Refer to Section C.3.2.7 for the media of delivery and Section F for other deliverable requirements.

Instructions to offerors relating to Section C.3.7.5 are provided in Section L.38.1.3.3.

C.3.7.6 Fraud Prevention Management

The contractor shall take a proactive approach in developing methods to prevent, detect and report fraudulent use of services. Within the time frame normally provided its commercial customers for notification after detection the contractor shall report to the affected agencies and the PMO all incidents where it detects or suspects fraudulent use of services.

The Government is particularly concerned with potential fraud associated with both domestic and non-domestic use of calling card authorization codes and wireless services. In particular and since authorization cards are intended for only individual use and not group use, the contractor shall automatically block simultaneous calls made from the same card. The contractor shall notify the DAR when triggers, such as the allowable cost or traffic threshold(s) (as mutually agreed between the PMO and the contractor,) are reached on any calling card. In limited instances, an agency may wish to have unrestricted calling cards. In those cases, the agency will identify the users of those cards and setup special fraud management arrangements with the vendor on an individual case basis following award.

The contractor shall take all prudent measures to detect and prevent fraud abuse related to the FTS program. The contractor shall identify all fraud related system and network vulnerabilities and take corrective measures to eliminate them, perform message and calling pattern analyses prior to and after billing, investigate annoyance calls, investigate incidents of misprogrammed system and network computers, and act as a consultant to agencies concerning their efforts for fraud prevention and detection techniques. The contractor shall maintain and update its draft description of its procedures to deter, detect and prevent fraud after award. The contractor shall provide the initial update within 60 calendar days after

C-252


notice to proceed with further updates as requested by the PMO. The procedures shall become effective upon written acceptance from the CO. Refer to Section C.3.2.7 for the media of delivery and Section F for other deliverable requirements.


C.3.7.6.1 Financial Responsibility for Fraud

The contractor shall assume financial responsibility for all costs resulting from fraudulent use of FTS2001 services except for cases where there is Government negligence or willful misconduct, or as specified in Section C.3.7.6.

C.3.7.6.2 Protection of Agency Systems

In accordance with the contractor’s commercial security offerings, the contractor, upon request, shall examine agency-owned Private Branch Exchanges and other agency-owned equipment that is connected to the network and shall make recommendations, as appropriate, to protect against fraudulent use of FTS2001 services. If the agency acts upon the recommendations it receives, it will be presumed not to be negligent as provided in Section C.3.7.6.1.

C.3.7.6.3 Fraud Reporting

The contractor shall provide a monthly summary report of its fraud detection and prevention activities for all services and features as identified in Section C.6.1.1.

C.3.7.7 Program Management Office Network Monitoring and Management Workstations

The contractor shall provide the PMO a sufficient number of NMM workstations (one of which shall be used for backup) at no additional cost. These will be used by the Government to monitor the contractor’s service management event data stream for subscribed network services. This equipment shall be used to support the NMM functions described in Section C.3.2.7.2.1. The contractor shall upgrade the NMM workstations provided to the Government consistent with the contractor’s own upgrades to its network management system at no additional cost to the Government. The contractor may provide PMO NMM workstation(s) at the GMC relocation facility pursuant to the same pricing provisions provided for in Section B for agency NMM workstations (Section C.3.7.8).

The provision of access facilities needed to connect the workstations to the network will be the responsibility of the customer and will use facilities provided elsewhere within the

C-253


FTS2001 contract. The contractor may also offer as an alternative to an NMM workstation, a software-only package for use with a customer-provided terminal to provide the same or similar capabilities available with the use of a contractor-provided NMM workstation.

C.3.7.8 Agency Network Monitoring and Management Workstations

The contractor shall provide to each agency subscribing to the NMM function a sufficient number of NMM workstations that will be used by the agency to monitor the agency’s portion of the network services by accessing the contractor’s network management systems. This equipment will be used to support the network management functions described in Sections C.3.2.7.2.2 and C.3.7.1. The contractor shall upgrade the NMM workstations provided to each subscribing agency consistent with the contractor’s own upgrades to its network management system at no additional cost to the Government.

C.3.8 Planning and Engineering

The contractor shall provide a planning and engineering function to ensure that telecommunications resources are available and capable of meeting evolving Government requirements. The principal functions associated with such planning and engineering shall include the following activities:

(a) Ensure service interoperability with other FTS contractors and Government and commercial networks where such interoperability is required by the Government and is being implemented commercially.

(b) Develop and maintain a contingency and restoral plan that prevents deterioration of network services.

(c) Develop and maintain a GMC relocation plan (see Section C.3.3.2). As requested by the PMO, the contractor shall provide the PMO an updated description of its GMC relocation plan. Refer to Section C.3.2.7 for the media of delivery and Section F for other deliverable requirements.

(d) Continuously assess current and anticipated communications technologies to meet the Government goals and plan network services that meet the near-term and long-term requirements.

Instructions to offerors relating to Section C.3.8 are provided in Sections L.38.2.1.7, L.38.2.1.10.7, L.38.2.1.10.8, and L.38.2.1.10.9.

C-254


C.3.8.1 Technical Advisory Group

The contractor shall make available as requested technical expertise to the Government for resolution of service problems of a complex technical nature that cannot be, or have not been, resolved through normal procedures.

C.3.8.2 Network and Access Cost Minimization

The contractor shall review, at least semi-annually, all network and access service arrangements it provides pursuant to this contract and shall conduct analyses to determine where opportunities exist to reduce the Government’s costs through optimization of service provisioning both in the Government’s use of the contractor’s network and in the contractor’s provision of billable access to every user location and/or SDP. Examples of such opportunities include, but are not limited to:

(a) Optimization of access at an SDP, such as conversion of switched access to dedicated access or the use of (or the more efficient use of) access integration arrangements

(b) Combining two or more collocated (or nearly collocated) SDPs and/or user locations into a single SDP and/or user location

(c) Grouping user locations and/or SDPs into an access network (LAN or Metropolitan Area Network [MAN]) arrangement

(d) Conversion of one type of service to another, such as replacement of DTS by SDS

The contractor shall identify opportunities to the agency or agencies that may benefit from cost minimization. If the proposed cost minimization opportunity is chosen for implemen-tation by the agency or agencies concerned, the normal service order process will be utilized to effect the change. The contractor shall report the proposed optimization opportunities to the PMO in accordance with the reporting requirements in Section C.6.1.12.

C-255


C.3.8.3 Contractor Initiated Network Changes

The contractor shall notify the PMO at least 60 calendar days in advance of all significant planned changes to its network. The contractor shall obtain the approval of the PMO at least 30 calendar days before instituting any planned changes that would adversely affect FTS2001 services.

Any changes in the network or support systems made by the contractor that result in service degradation, erroneous billing, or other service deficiencies, or that impair interoperability within or among networks, shall be rectified at no cost to the Government. Any charges or damages incurred by the Government as a result of such degradation, errors, or deficiencies shall be credited to the Government. Prior to issuance of any credits, the parties will discuss and reach mutual agreement regarding the actual effects of, and credits for, such degradation.

C.3.9 Trouble and Complaint Reporting

Using the contractor’s commercial trouble reporting system (and extensions, if necessary), the contractor shall establish and implement its procedures and processes, as provided in accordance with the requirement of Section C.3.4.2.1, for trouble collection, entry, tracking, analysis, priority classifications, and escalation for all services to ensure that problems are resolved within the specified time frames. The trouble reporting system shall be operational 24 hours a day, 7 days a week. The contractor shall use its existing automatic and manual trouble reporting escalation process.

The contractor’s trouble reporting system shall:

(a) Centralize the receipt of trouble reporting for all services.

(b) Identify and clear troubles for both agency-identified mission-critical (TSP) and non mission-critical (non-TSP) services.

(c) Maintain audit trails of trouble resolution activities.

(d) Respond to inquiries on trouble resolution status.

(e) Provide trend analysis of trouble reports.

C-256


(f) Sort trouble reports by type, duration, location, or as otherwise done commercially by contractor.

(g) Provide trouble escalation for normal and emergency events.

Using the contractor’s commercial complaint reporting system (and extensions, if necessary), the contractor shall establish and implement its procedures, as provided in accordance with the requirement of Section C.3.4.2.1, for complaint collection, entry, tracking, and resolution within the contractor’s commercial time frames. The complaint reporting system shall be operational during the days and hours provided by the contractor in its commercial practice.

The contractor’s complaint reporting system shall:

(a) Centralize the receipt of complaint reports

(b) Maintain audit trails for complaint resolution activities

(c) Respond to inquiries on complaint resolution status

(d) Sort complaint reports by subject, complainant, or as otherwise done commercially by the contractor

(e) Provide means to escalate complaint resolution efforts.

Instructions to offerors relating to Section C.3.9 are provided in Sections L.38.2.1.8 and L.38.2.1.10.10.

C.3.9.1 Entering and Handling Trouble and Complaint Reports

Users shall be able to reach the contractor’s trouble and complaint reporting center via the contractor’s CSO.

The contractor shall perform the following activities regarding the handling of trouble reports and complaints:

(a) Identify each reported trouble or complaint via a unique trouble and complaint report number

(b) Provide trouble repair time estimates to users

C-257


(c) Report the close-out of trouble reports to the reporting party or its designee

(d) Report the resolution of the complaint to the complainant.

The contractor shall use the same trouble reporting system when initiating its own trouble reports.

C.3.9.2 Trouble Report Status Reporting

In accordance with the contractor’s procedures provided as in response to Section C.3.9, the contractor shall advise users submitting a trouble report of the status of clearing the trouble report and the resolution of the trouble report when cleared. The contractor shall verbally report the status of trouble resolution efforts according to the contractor’s existing commercial procedures. However, the Government desires that the verbal reporting occur every two hours, unless the requester authorizes updates either via E-Mail, a longer reporting duration than two hours, or agrees to obtain updates via the contractor’s trouble reporting status system. In accordance with its existing procedures, the contractor shall report status resolution efforts for all services classified as NS/EP and for services covered by the TSP System. The Government desires that such status reports be made at least hourly.

A trouble report will be closed out only when the reporting party or its designee agrees that service has been restored. If the Government’s site representative is unavailable to confirm reestablishment of service, the contractor shall compute the service outage interval using the close-out time for the trouble as logged by the contractor. If the Government’s site representative is unavailable to participate in cooperative testing to confirm reestablishment of the service, the contractor shall note the time interval between the request for the Government’s assistance and the time the Government’s assistance for cooperative testing was actually obtained. This time interval shall be subtracted from the total outage time in order to compute the interval for credit adjustment.

The contractor shall be responsible for maintaining a record of the close-out which includes recording entries for the beginning time and ending time of the outage. This information shall be included in a PMO periodic report as specified in Section C.6.1.4. The contractor shall process any credits applicable to the service outage based on this record of information.

C.3.9.3 User Trouble and Complaint Report Data Access

For status inquiries, the contractor shall provide on-line real-time access to trouble reporting information. For status inquiries, the contractor shall provide complaint reporting information using its existing access procedures.

C-258


The contractor shall make the status of trouble and complaint reports accessible via the user entering either the trouble or complaint report number or the name of the reporting party for troubles or the complainant for complaints.

The contractor’s data access capability shall allow the PMO and agencies to obtain the contents of user-specified trouble reports opened by or for the Government user.

C.3.9.4 Ad Hoc Trouble/Complaint Reporting Capability

To the extent possible, using the contractor’s existing trouble and complaint reporting capability, the contractor shall provide the capability to collect and sort trouble and complaint records by any field or combination of fields in each record.

The contractor shall:

(a) Maintain, according to its existing practice, the Government’s access to trouble and complaint report and resolution data for all reports.

(b) Maintain an archive, according to its existing practice, of trouble and complaint reports and their resolutions.

(c) According to its existing practice and upon request from the PMO and agencies, deliver archived trouble and complaint report data per the contractor’s commercial time frame(s) for delivery of such information.

C.3.9.5 Measurement of Time to Restore Service

As requested by the PMO, the contractor shall calculate and report a Time to Restore Service as specified in Section C.6.1.13.

C.3.10 Training

The contractor shall develop and implement a training program for the following four segments of the Government population:

(a) Executive (approximately 500 individuals)(b) General user trainers (approximately 1000 individuals)(c) DAR (approximately 2000 individuals)(d) Administration and operations (approximately 300 individuals)

All training shall be provided using the English language.

C-259


As requested by the PMO the contractor shall update the draft training plan and submit it to the CO. Refer to Section C.3.2.7 for the media of delivery and Section F for other deliverable requirements.

The Government reserves the right to monitor training classes to ensure appropriateness of material and presentation. The Government will provide the vendor prior written notice that a course is being monitored, and will identify the individuals (not to exceed two) performing the monitoring. The contractor shall not account attendance of the monitor(s) against the class size or the student attendance. The contractor will be notified by the Contracting Officer in writing of any training that is deemed unacceptable. This notification will identify the portion(s) of the training that are unacceptable. Training presented subsequent to this notification that continues to be unacceptable may result in non-payment and/or rejection of the new or initial service.

Whenever possible, the contractor shall provide training at user sites or, at the Government’s discretion, within daily commuting distance of user sites. However, for non-domestic sites the Government will address each training requirement on an individual basis to develop the most cost effective solution for the Government and the contractor.

The contractor shall provide the Government the ability to request any training and training materials through the contractor’s standard service ordering process with any subsequent charges processed through the standard monthly billing system. The contractor shall also provide for customers to directly order and be invoiced for training and training materials.

At the inception of service and at no cost to the Government, the contractor shall provide initial training for provisioned services. Within the first six months after a new service type or feature is ordered at a location, the contractor shall provide initial training at no cost to the Government.

Instructions to offerors relating to Section C.3.10 are provided in Sections L.38.2.1.9 and L.38.2.1.10.11.

C.3.10.1 Executive Training

The contractor shall provide executive training through seminar-type programs designed to inform senior-level Government managers of the capabilities and applications of the contractor’s services.

C-260


C.3.10.2 General User Trainer Training

Upon the initial turn-up of CSS, SDS and VTS at a location, the contractor shall train Government trainers, who in turn will train other Government personnel. The contractor shall assume that the Government trainers are knowledgeable about the telecommunications services for which they will provide training. Each training class shall not exceed 32 individuals per class. The minimum class size shall be 12 students.

Following this training, the contractor shall provide the Government trainers, at no additional cost to the Government, with reasonable quantities of supplementary materials for them to use in training others. This supplemental material shall include brochures, audio/visual aids, desk top guides, or other materials as deemed appropriate. These supplemental materials shall contain descriptions of services and features with explanations of how to use services and how to report user troubles and complaints. The contractor shall also develop and distribute supplemental documentation about handling credit adjustments, service assistance, conference calls, and other appropriate subjects suitable for inclusion in agency-published directories. The contractor shall distribute the training and supplemental materials to Government trainers in sufficient quantities to supply all trainees. The Government reserves the right to copy or duplicate any training material provided under the FTS2001 contract. Refer to Section F for deliverable requirements.

During the transition, migration, or implementation of new services at locations, the contractor shall complete the training of the trainers 30 calendar days prior to cutover of services at the locations unless prior approval is obtained from the PMO.

In addition to usage of the specific CSS, SDS and VTS, the contractor shall provide training for Government trainers in additional areas, such as the following, covering each area’s potential applicability to all service categories:

(a) Coordinating with the CSO(b) Trouble reporting procedures(c) Accessing the status of trouble reports/complaints(d) Escalation procedures for trouble resolution(e) Procedures for obtaining credit adjustments for incorrectly dialed numbers(f) Fraud prevention, including customer premises safeguards

C-261


C.3.10.3 Designated Agency Representatives Training

The contractor shall provide training on the contractor’s service ordering and billing processes. This training shall include how to:

(a) Place a service request to add, terminate, or change services(b) Obtain price quotes(c) Modify or cancel service orders(d) Obtain status reports from the service order tracking system(e) Indicate service acceptance or rejection(f) Submit a notice of service order acceptance or non-acceptance(g) Verify billing data(h) Initiate and track billing disputes(i) Obtaining status of credit adjustments

For the initial training, the contractor shall provide DAR training to selected individuals, not to exceed 32 individuals per class.

C.3.10.4 Administration and Operations Training

The contractor shall provide training to PMO personnel on all administrative and operational support systems. This training shall provide initial instructions for the operation of these systems. The contractor shall provide additional training on the systems whenever any of the systems change and affect the user or on an annual basis, whichever comes first. Changes and upgrades that are transparent to the end user, with the approval of the PMO, will not trigger a requirement for training.

C.3.10.4.1 Administrative Systems Training

The contractor shall provide training for the use of administrative systems that includes:

(a) Service ordering system(b) Trouble/complaint reporting system(c) Bill generation process(d) Dispute processing system

C-262


C.3.10.4.2 Operations Systems Training

Within 60 days after contract award, the contractor shall provide training as to how to receive or access the contractor’s NM data specified in Section C.3.7. This training should include access and use of the NMM workstations. Refer to Section F for deliverable requirements.

C.3.10.5 Supplemental Training

The contractor shall update training documentation as required by the CO to maintain currency of the training documentation and provide additional training upon request by the Government. The Government reserves the right to supervise the quality of the training and request updates when it deems necessary. Updates will not be required more frequently than four times per year. Refer to Section F for deliverable requirements.

C.4 TRANSITION, MIGRATION AND IMPLEMENTATION

C.4.1 Introduction

This section describes the actions and responsibilities associated with transitioning FTS2000 services, migrating existing services on particular legacy networks to the contractor’s network, and implementing new services. The contractor’s support systems will be tested and accepted before any services are transitioned, migrated, or implemented (see Section E.2). The implementation plans and procedures specified will be required only for significant implementation activities (i.e., involving more than 50 discrete street addresses), such as large implementation projects or the first implementation of a new or enhanced service offering under the contract. The Government does not anticipate requiring these plans and procedures for the routine implementation of mature services.

Within the PMO, the Government will create the Transition Control Center (TCC), which will have overall responsibility for managing, directing, and coordinating the transition activities. The TCC will exist for only the duration of the transition activities. The TCC Director will manage the overall activities of transition with Contracting Officer Representative (COR) authority.

Similarly for migration and implementation projects, the Government will establish a Migration Control Center (MCC) or an Implementation Control Center (ICC), as appropriate. The MCC/ICC may be an organization within the PMO or it may be delegated to the agency participating in the migration or implementation project. An MCC/ICC will be established for each migration/implementation project undertaken and will cease to exist at

C-263


the conclusion of that migration or implementation project. The MCC/ICC Director will manage the overall activities of migration or implementation with COR authority. The Government will notify the contractor at the inception of the migration or implementation project whether the MCC/ICC duties and authority has been delegated to an agency. In all cases, the MCC/ICC will have the authority to approve all contractor plans and activities.

The contractor shall support the TCC, MCC(s), and ICC(s). The contractor shall work with the TCC, MCC(s), and ICC(s) in the conduct of transition, migration, and implementation activities. The TCC, MCC(s), and ICC(s) will be the contractors principal points of contact within the PMO or agency for the coordination of transition, migration, and implementation activities. The contractor shall recognize that the TCC, MCC(s), and ICC(s) will represent the agencies when dealing with the contractor on strategic transition, migration and implementation issues.

C.4.1.1 Transition

Transition is the process of planning for and transferring services from the existing FTS2000 networks to the contractor’s network.

The Government’s goals and objectives for the transition activities are to:

(a) Maximize the rate at which existing users’ services are transitioned to the contractor’s network

(b) Minimize disruptions and maintain the continuity of services to the users

(c) Ensure cost effective transition of services to the contractor’s network

(d) Optimize existing service during transition

(e) Adopt best commercial practices

The contractor shall complete the transition of FTS2000 services for which it is responsible within 12 months after the agreed start of transition as specified in the final Comprehensive Transition Plan (CTP) (Section C.4.2.2) but no later than the expiration of the current FTS2000 contracts or any extensions thereof unless otherwise authorized by the CO. The Government reserves the right to require the contractor to expedite those service orders necessary to complete the transition in less than 12 months.

C-264


C.4.1.2 Migration

Migration is the process of planning for and transferring services from existing networks (i.e., those networks not currently associated with FTS2000 networks) to the contractor’s networks. Migration also includes planning for and transferring services from one FTS2001 contractor’s network to another FTS2001 contractor’s network.

The Government’s goals and objectives for the migration activities are to:

(a) Maximize the rate at which existing users’ services are migrated to the contractor’s network

(b) Minimize disruptions and maintain the continuity of services to the users

(c) Ensure cost effective migration of services to the contractor’s network

(d) Adopt best commercial practices

(e) Avoid undue price increases or degradation of performance of existing services during migration

C.4.1.3 Implementation

Implementation is the process of providing new service. New service may mean:

(a) Provisioning of services which already are implemented elsewhere in the network to new SDPs (or expansion of service at existing SDPs) where complexity or quantity justify treatment as a project

(b) Provisioning of a service offering which has not been implemented before (i.e., a new or enhanced service under the contract)

The Government’s goals and objectives for implementation activities vary somewhat according to which type of implementation is taking place. Under (a) above, the Government wishes to ensure the cost-effective, on-schedule delivery of service to users with minimum disruption. Under (b) above, the Government is also especially concerned to ensure that the new or enhanced service offering works effectively across the network before implemen-tation. The Government will work with the contractor to determine a mutually agreed upon schedule for conducting implementation projects activities after giving notice to begin a particular implementation project.

C-265


C.4.1.4 Overview of Transition, Migration and Implementation Plans

Before any transition, migration, or implementation activities take place, certain plans are required. There are four categories of plans. These are outlined here:

(a) Transition, Migration, and Implementation Plans. An agreed-to Comprehensive Transition Plan is required before the start of transition (Sections C.4.2.1 and C.4.2.2). Similarly, agreed-to Migration (Section C.4.3.1) or Implementation (Section C.4.4.1) Plans are required before the start of any migration or any significant implementation.

(b) Transition, Migration and Implementation Management Plans. These plans are developed by the contractor, consistent with the approved plans described in (a) above. They serve as progress reports, master logs, and working blueprints (Sections C.4.2.4, C.4.3.3, and C.4.4.2).

(c) Transition, Migration, and Implementation Verification Test Plans. Verification test plans are required for each transition, migration, or implementation activity. They describe the verification test activities to be performed by the contractor (Section E.2.2).

(d) Other Plans. These include interconnection plans and private dialing plans.

C.4.1.5 Overview of Transition, Migration and Implementation Processes

The contractor shall submit for approval by the Government a transition, migration, or implementation plan providing a broad overview of what the contractor intends to do. These plans shall describe testing activities, schedules ( to the extent known) agreed to by the agencies involved, as well as discussion of other factors, such as risk management and logistics. For the first implementation of a new or enhanced service offering as described in Section C.4.1.3(b), the implementation plan also shall include the means to prove that the service offering works prior to implementation, e.g., OCDs or service trials.

The contractor shall submit a verification test plan which shall describe the tests to be performed by the contractor to ensure that interface and service requirements will be met at the SDPs. The Government shall be allowed to observe verification testing and to examine the test results.

C-266


Finally, the 72-hour acceptance test period allows the Government to verify the correctness of the installation and take appropriate action, if necessary (Section E.2.2.3).

The contractor shall take a pro-active stance in all transition, migration, and implementation activities, and shall work closely with the users to ensure that user requirements are fully understood and are fully met.

Upon contract award, the Government will provide the contractor guidance to facilitate the preparation of the CTP and associated management plans and verification test plans. This guidance will ensure a consistent format and content in the plans and will describe the Government’s approach to reviewing the plans and its criteria for approval. The Government reserves the right to provide similar guidance at notice to begin migration activities (see Section C.4.3) and at notice to begin a specific implementation project (see Section C.4.4.1).

C.4.1.6 Access Service Optimization

Based on an analysis of available FTS2000 traffic information and data on existing access circuit arrangements, obtained from the Government and/or from its own site surveys, the FTS2001 contractor shall propose access service facility arrangements to serve user requirements that meet both applicable service performance requirements and the cost minimization provisions of Section C.3.8.2. The contractor shall document its approach to access circuit optimization in the CTP, each Migration Plan (MP), and each Implementation Plan (ImP), as described in Sections C.4.2.2, C.4.3.1, and C.4.4.1, respectively. The contractor shall propose optimum access circuit arrangements in the Transition Management Plan (TMP), each Migration Management Plan (MMP), and each Implementation Management Plan (IMP), as described in Sections C.4.2.4, C.4.3.3, and C.4.4.2, respectively. Upon Government review and acceptance of the contractor’s proposed access service facility arrangements, as outlined in the TMP, MMP, or IMP, all such dedicated access service arrangements become Class 2 dedicated access, as described in Section C.2.1.16. The following shall become Class 1 dedicated access, as described in Section C.2.1.16:

(a) Contractor proposed dedicated access service arrangements reduced in capacity by direction of the ordering agency prior to release of transition-, migration-, or implementation-associated service orders

C-267


(b) Contractor-provided dedicated access facilities when an agency subscribes to or uses the make-busy feature

(c) Those contractor-provided dedicated access facilities for which the responsible agency refuses, after transition/migration/implementation, to submit a service request(s) to modify the access facilities to meet recommendations that the contractor certifies are necessary to meet Class 2 performance and cost minimization requirements

Class 1 access may be converted to Class 2 access upon user agency conformance with the contractor’s stipulated Class 2 dedicated access implementation. When Class 2 dedicated access is converted to Class 1 dedicated access, or vice versa, the contractor will so inform the DAR of the affected agency(s) and the PMO by registered letter. Disputes between an agency and the contractor over conversions from one Class of dedicated access to another shall be arbitrated by the PMO.

C.4.2 Transition

C.4.2.1 Reserved

C.4.2.2 Comprehensive Transition Plan

The contractor shall update the TP that was provided with the proposal to become the CTP and shall deliver its CTP to the TCC within 75 calendar days after notice to proceed. The CTP shall be based on the information contained in the contractor’s TP and reflect the actual services to be transitioned and the agencies to which the services will be transitioned. With the cooperation of the TCC if necessary, the contractor shall coordinate its CTP with the CTPs of other FTS2001 contractors, as appropriate. The TCC, in conjunction with affected agencies, will review the contractor’s CTP for integrity, completeness, and responsiveness. The TCC, in coordination with affected agencies, will review and coordinate recommended changes to the CTP with the contractor. The TCC intends to approve the CTP within 45 calendar days after its submission. With the approval of the TCC, transition activities may begin without the TCC’s approval of the CTP. Refer to Section C.3.2.7 for the media of delivery and Section F for other deliverable requirements.

The TCC, in conjunction with affected agencies, will determine the sequence in which agencies will transition their services based on the agencies’ missions and the criticality of the services to be transitioned. This sequence will then be coordinated with the contractor. The contractor shall incorporate this sequence into its CTP.

C-268


The actual schedules for the transition activities the contractor includes in its CTP shall be based on information collected by the contractor following award. The contractor shall phase all schedules and consider the resources available to the contractor and to the Government to accomplish the transition activities and provide an evaluation of their potential impact.

The successful accomplishment of activities described in the CTP shall become the sole responsibility of the contractor, and all dates and other requirements contained in the CTP shall constitute a firm commitment by the contractor. Any change from the schedule in the approved CTP shall be in the best interests of the Government and shall require approval by the Government. The contractor shall notify the Government in writing of any condition(s) that threaten to delay completion of the transition beyond the time specified in the CTP or beyond the date of expiration of the FTS2000 contracts.

The CTP shall include details of:

(a) Transition schedules

(1) Phasing of service types being cut over

(2) Identifying service locations for the cutovers

(3) Identifying the lead-times required for cutovers

(4) Identifying the month in which services at each location will be cut over

(5) Identifying the steps required to prepare the locations for the cutovers

(6) Identifying the steps required to complete the cutovers

(7) Identifying how each type of existing service may be affected during the cutover activities

(b) Identification of the responsible contractor’s subcontractors at a location

(c) Type of Government equipment involved at each location in which services will be cut over

(d) Agency controlling the Government equipment

(e) Originating traffic at each location

C-269


(f) Logistics

(g) Emergency procedures

(h) Creation and use of a database (as described in Section C.4.2.7.4)

(i) New construction

(j) Circuit grooming needed at each location

(k) Access service optimization (as described in Section C.3.8.2 and C.4.1.6)

C.4.2.3 Transition Interconnection Plan

For transition, the contractor shall provide a Transition Interconnection Plan (TIP) to the TCC no later than 60 calendar days after notice to proceed. This plan shall describe the interconnection arrangements between the contractor’s network facilities and existing FTS2000 network, the interconnection arrangements with FTS2001 contractors, and the interconnection arrangements between the FTS2001 contractor and the PSN required to provide interoperability and continued uninterrupted service as all traffic is transitioned onto the contractor’s network facilities. Refer to Section C.3.2.7 for the media of delivery and Section F for other deliverable requirements.

The TIP shall include:

(a) Listing of the network facilities to be used during the interconnection of networks to include such items as:

(1) Number and type(s) of gateways(2) Description of network-to-network interface(s)(3) Type(s) of temporary equipment and its (their) location(s)

(b) Anticipated amount of traffic, by service type, to be carried at each interconnection including the approach to aggregate traffic, by service type, during the transition

(c) Coordination of routing, numbering, dialing, and signaling plan changes

(d) Arrangements used to achieve interconnectivity between the FTS2000 network(s) and the contractor’s network during the transition of services

C-270


The TCC, in conjunction with affected agencies, will review and coordinate recommended changes to the TIP and intends to approve the TIP within 60 calendar days after its submission. With the approval of the TCC, transition activities may begin before approval of the TIP.

C.4.2.4 Transition Management Plan

The contractor shall develop and maintain a TMP consistent with the contractor’s Government approved CTP. The TMP shall serve as a progress report, master log, and a working blueprint for the contractor’s day-to-day activities during the transition of services at individual users’ locations. The initial version of the TMP shall be submitted to the TCC by the contractor no later than 50 calendar days prior to the first scheduled movement of traffic to the contractor’s network. The TCC intends to approve the initial TMP within 30 calendar days after its submission. With the approval of the TCC, transition activities may begin without the TCC’s approval of the TMP.

The TMP shall contain all schedules, exceptions, and any deviations from the testing procedures contained in the contractor’s Transition Verification Test Plan (Section E.2.2.2.1). The TMP shall contain cutover contingency plans (Section C.4.2.7.10.4) for each location at which services are transitioned to the contractor’s network. The TMP shall contain all proposed changes to the existing FTS2000 access facilities to optimize access service as described in Sections C.3.8.2 and C.4.1.6. The contractor shall make the data in the TMP available to the TCC on-line. Refer to Section C.3.2.7 for the media of delivery and Section F for other deliverable requirements. The contractor shall control access to the TMP through the use of appropriate security techniques, such as passwords, for authorized individuals. The TMP shall be organized by weeks and updated daily. The contractor’s initial version of its TMP shall begin with the month in which the first transition activities are scheduled to occur.

No later than the second Government business day following the weekly reporting interval, the contractor shall provide weekly summaries of cutover activities to the TCC on-line regarding the progress of pending and concluded transition activities and the status of activities delineated in the TMP. The weekly reports shall contain the following information, distinguished by service type and agency:

(a) Count and identification of services cutover since last report

(b) Locations at which services were cutover since last report

(c) Number of locations remaining to be completed for all services scheduled for transition

C-271


(d) Number of services remaining to be completed for all services scheduled for transition

(e) Comparison of services cutover to date with the number and locations of services proposed in the latest coordinated and approved transition schedule

(f) Description of services (and their locations) for which cutover is in jeopardy of not meeting the current transition schedule

(g) During the weekly reporting period, reports of service impairment or degraded service quality (together with service failures and service blockage events), including gateways established between FTS2001 and FTS2000 contractors

(h) Discussion of any issues affecting the timely completion of all cutover activities

Representatives of the contractor shall meet with appropriate Government representatives as deemed necessary by the TCC and the contractor to apprise the Government of progress in completing the transition schedules and to obtain approval for any changes to the transition activities and schedules as they occur. The contractor shall be responsible for coordinating and establishing an agenda for all meetings. Where transition activities of jointly served locations are involved, the contractor shall participate in joint meetings held among all interested contractors and Government personnel.

C.4.2.5 Private Dialing Plan for Transition

In coordination with the Number Plan Administrator function (Section C.3.2.7.4), the contractor shall develop and administer a plan for transitioning stations that require contractor-specific private numbers (Section C.3.2.7.4.2(b)). This private dialing plan consisting of contractor-specific numbers, shall be provided to the TCC by the contractor within 45 calendar days after notice to proceed. The TCC, in conjunction with advice from affected agencies, intends to approve the plan within 45 calendar days after its receipt by the TCC. With the approval of the TCC, transition activities may begin without the TCC’s approval of the Private Dialing Plan for Transition. Refer to Section C.3.2.7 for the media of delivery and Section F for other deliverable requirements.

C.4.2.6 Transition Verification Test Plans

The contractor shall provide the Transition Verification Test Plans to the CO as described in Section E.2.2.2.1.

C-272


C.4.2.7 Contractor Responsibilities for Transition

C.4.2.7.1 Office of Transition Management

The contractor shall establish an Office of Transition Management (OTM) within 15 calendar days following contract award. The OTM shall be charged with overseeing all aspects of the activities related to the transition of services from the existing FTS2000 networks onto the contractor’s network. During the transition period, the OTM shall provide a single point of contact for these activities with the TCC and with agency users at locations where transition activities will occur. The OTM shall administer all contractor plans, policies, and specific transition schedules regarding the contractor’s services.

The contractor’s OTM shall provide a single point of contact for each LGC for transitioning services. The OTM’s responsibility for coordinating all activities extends to any activity conducted by any subcontractor or vendor on behalf of the contractor. All requests for information or assistance directed to individual user locations for purposes of site preparation shall come through the OTM and shall be directed to the appropriate user location’s LGC.

The contractor shall provide an OTM representative for each location where transition activities are to occur. This representative shall be available to communicate with the site’s representatives prior to, during, and immediately following cutover activities. This OTM representative shall be available to answer any questions related to transition.

Via the contractor’s service order tracking system, the OTM shall make available to the TCC information related to the content of service orders (e.g., equipment and special engineering requirements) and the status of service orders associated with the transition of services onto the contractor’s network and the removal of services from the FTS2000 networks. The contractor shall update daily the information available from the service order tracking system.

C.4.2.7.2 Transition Network and User Location Inventories

The contractor shall begin to conduct its own network and user location inventories no later than 30 calendar days after notice to proceed. These inventories may be based upon information provided by the Government. The contractor shall begin providing to the TCC the information defined below in this section no later than 15 calendar days after the contractor begins conducting its own network and user location inventories. Refer to Section C.3.2.7 for the media of delivery and Section F for other deliverable requirements.

C.4.2.7.2.1 Transition Network Inventory

C-273


The contractor shall obtain from Government sources, where available, or by means of a site survey, as necessary, all information that is needed to accomplish the transition of all services for which the contractor is responsible.

C.4.2.7.2.2 Transition User Location/Service Delivery Point Inventory

The contractor shall obtain from Government sources, where available, or by means of a site survey, as necessary, all information regarding the user location/SDP equipment which has an impact on the delivery of service(s) to that location/SDP. The acquisition of this information shall be the sole responsibility of the contractor. The contractor shall complete a user location/SDP inventory for each location/SDP with which it is associated. The contractor shall obtain an SDP ID Base Code from the SDP ID Administrator for each SDP. This inventory shall be entered into the Transition Database (Section C.4.2.7.4).

C.4.2.7.3 Transition Traffic Statistics

The contractor shall obtain from Government sources, where available, or by means of the contractor’s site surveys, as necessary, an update of all FTS2000 traffic information necessary for the preparation of the contractor’s proposed CTP. The Government will provide to the contractor FTS2000 call detail data. The OTM shall verify, to the extent possible, all FTS2000 traffic information for a given location in advance of all specific transition activities at that location. The contractor shall begin providing to the TCC this information no later than 30 calendar days after verification. Refer to Section C.3.2.7 for the media of delivery and Section F for other deliverable requirements.

C.4.2.7.4 Transition Database

The contractor shall develop, provide, and maintain information regarding transition schedules along with a summary of all information contained in the TMP for the contractor’s user locations/SDPs. The contractor shall ensure that the access to this database is granted to only authorized users. The contractor shall provide access no later than 15 calendar days after approval of the TMP. The database shall be as complete as possible initially, continually updated as more precise information becomes available, and fully up-to-date regarding information on a particular user location at the time access service is ordered for that location. The database information shall continue to be updated as required to maintain its currency and accuracy until transition is complete. At the completion of the transition activities, the contractor shall provide the Government the contents of the complete transition database including all information from the contractor’s transition activities. Refer to Section C.3.2.7 for the media of delivery and Section F for other deliverable requirements.

C-274


In the database, the contractor shall maintain the following information in addition to the information mentioned in Sections C.4.2.7.2 and C.4.2.7.3.

(a) User SDP ID (including the physical address by country, state, city, street address, zip+4 represented by the SDP ID base code)

(b) User Location NPA/NXX or equivalent for non-domestic locations

(c) Agency(s) user located at User Location, itemized by Agency department or division name

(d) User Location managing agency

(e) User Location’s Designated Connecting POP ID and physical location

(g) LGC name and commercial telephone number

(g) Date and time that user location is scheduled for transition

(h) All preparatory steps prior to action at each user location with scheduled dates for the initiation and completion by the contractor of each step of the action

(i) All activities required to be completed by the LGC at each user location with dates when the LGC shall be notified of these requirements by the contractor

(j) All FTS2000 telecommunications facilities currently employed at the user location, including:

(1) Number and description of dedicated access circuits used for connecting FTS2000 services to the User Location (if a virtual on-net location, so note and list telephone numbers presubscribed to FTS2000 contractor)

C-275


(i) Identified circuits by type(s) of FTS2000 service (SVS, SDS, PSS, DTS, Compressed VTS, VTS) carried

(ii) Identified as to which circuits are multiplexed to provide multi-channel integration and/or service aggregation and which are using ISDN or SS7 call set-up signaling

(iii) Identify type(s) of FTS2000 contractor-provided equipment that each circuit (or each channel in a multiplexed circuit) is terminated in (e.g., data service unit, channel bank, PAD or FRAD, modem, etc.) at the user location

(2) Vendor(s) providing facilities

(k) All planned FTS2001 access service facilities and the vendors providing the facilities that shall be ordered by the contractor in order to provide the location with transitioned services, including:

(1) Number and description of dedicated access circuits required for service at a User Location, identifying each access circuit by an ID code (if the User Location will use circuit-switched on-net access, so note and list telephone numbers that will be presubscribed to FTS2001 contractor)

(i) Identifying all dedicated access circuits (by access circuit ID) terminated at a User Location

(ii) Identifying which circuits serve only a single SDP/UNI, where the UNI matches the bandwidth/payload data rate of the circuit

(iii) Identifying circuits (by an integration group ID) providing “access service integration,” and whether the associated AAF service function is contractor-provided or Government-provided

(iv) Identifying circuits (by a trunk group ID) that constitute by themselves or that are, in whole or in part, part of a trunk group for GOS measurement purposes

C-276


(v) Identifying (describing and locating) each SDP (using an SDP ID) served at the User Location and associate each identified SDP with its related access circuit ID and, as applicable, with its integration group ID and/or its trunk group ID


(3) Schedule for ordering planned access service facilities described above

(l) Status information regarding the transition activities (highlighted in the database record if the cutover is in jeopardy or delayed)

(m) Circuits associated with ‘critical users’, as defined by the TSP

(n) Service order numbers, with each service order number associated with its related User Location ID, SDP ID, access circuit ID, and, as applicable, with its integration group ID and/or its trunk group ID

(o) Configuration data at each SDP (identified by SDP ID) including:

(1) Terminating equipment type(2) Signaling type(3) Protocol interfaces

(p) Indication of direct or centralized billing, by agency at User Location

(q) Security clearances required for personnel involved in transition

C.4.2.7.5 Coordination During Transition

During the transition of services, the contractor shall be responsible for coordinating all aspects of the transitioning of traffic at user locations for which it is responsible. When transitioning of traffic involves the simultaneous actions at a location of more than one contractor, the TCC may appoint, if it deems appropriate, one contractor as overall coordinator at a location. The other contractor(s) shall work cooperatively with the overall coordinator at that location. However, each contractor shall be responsible for its own transition activities required at a location irrespective of the Government’s appointment of an overall coordinator.

C-277


The contractor’s coordination responsibilities shall include the following areas:

(a) Developing transition procedures to facilitate the coordination of all activities with the TCC, LGC, and other contractors. (These procedures shall be utilized for transition preparations, schedules, required Government resources, and progress in all areas relating to the transition of traffic at user locations.)

(b) Coordinating all requests to the LGC for disconnection of present FTS2000 services as a result of transition activities.

(c) Coordinating all information-gathering activities with the TCC, other contractors, and Government representatives at user locations in order to provide services and associated features.

(d) During transition activities, coordinating all on-site visits to user locations with the LGC, the TCC, subcontractors, and any other involved parties.

C.4.2.7.6 Transition Notification and Scheduling

During the transition of services, the contractor shall notify the LGC about cutover activity at least 60 calendar days before the location is to be transitioned, except as otherwise directed by the Government. The contractor shall follow the procedures listed below when notifying all involved parties concerning activities:

(a) The contractor shall initially notify each LGC of the approved scheduled transition date and time for the particular user location. The contractor shall be responsible to verify receipt of the notification by the LGC.

(b) The contractor shall provide detailed documentation to both the LGC and the TCC at least 60 calendar days prior to transition activities beginning at a location, including the following information:

(1) Agreed-upon date and time for the activities.

(2) The quantity and type of new or modified circuits and facilities required at the location.

C-278


(3) The commercial circuit numbers of the new or modified circuits and access facilities. The contractor may provide the documentation without the circuit numbers if circuit numbers are not available when the documentation is to be provided. The contractor shall update the documentation with the circuit numbers when the numbers become available.

(4) The name and commercial telephone number of the contractor’s local representative.

(5) Requests for assistance required by the contractor from the individual user location in order to complete transition activities, including actions such as unlocking telephone rooms and providing special security passes for personnel.

(6) A transition activities list informing each user location of all peripheral activity that will take place prior to the actual physical transition of service(s). As an example, this list shall include installation of equipment at various times prior to transition activities or on-site visits by subcontractors. Representatives of the contractor shall be solely responsible for coordinating all such activity and visits with each LGC. This coordination effort includes scheduling visits, making any requests for assistance from the user location, and verifying with the user location that schedules have been adhered to by subcontractors.

(7) Procedures to be followed for trouble reporting during the activities.

(8) The security clearances, as required, of personnel to perform the transition activities on Government sites.


The contractor shall initiate and complete all cutover activities outside of normal business hours unless otherwise arranged with, or requested by, the user location’s LGC or other authorized representative. All cutover activities at a location shall be completed within 12 hours after being initiated unless special approval is obtained in advance from the TCC.

The contractor’s local representative shall be accessible to support planning and coordination of location-specific activities. The contractor’s local representative shall provide direct on-site support as needed, consistent with normal commercial practices.

C-279


C.4.2.7.7 Establishment of Local Committees for Transition

During the transition of services, the contractor shall be responsible for establishing a local committee that includes its representatives, the LGC, and appropriate local vendors for each location where services are to be transitioned. At a location for which more than one contractor is responsible, all involved contractors shall agree on the composition of a local committee at the location with the assistance of the TCC, if required.

The contractor shall establish the local committee at least 50 calendar days prior to the beginning of transition activities at the location. The contractor shall invoke its existing commercial coordination processes when establishing the local committee. Face-to-face meetings need not always be held. Teleconferencing resources should be used whenever possible.

The local committee will provide a forum for coordination of issues related to the transition activities at a location. Through the committee, the contractor shall facilitate cooperation among the participating members. At a minimum, the committee members shall coordinate cutover schedules, necessary equipment installations, and site modifications.

C.4.2.7.8 Verification of Transition Information

The contractor shall negotiate a date with the Government after which no changes that would affect transition will be made at a location. After this date, the contractor shall verify with the LGC for that location all information the contractor requires for the proper and efficient transition of services at that location.

C.4.2.7.9 Notification of Completion of Transition Activity

The contractor shall inform the LGC at a user location and the TCC when activities, including installation and all required contractor-performed testing, are completed at the location according to the requirements of Section E.

C.4.2.7.10 Transition Technical Requirements

The Government requires compliance with a number of technical requirements to ensure quality of service and continuity of service for all FTS users as their services are transitioned. The contractor shall be responsible for adhering to the requirements set forth below.

C-280


C.4.2.7.10.1 Direct Station-to-Station Dialing for Switched Voice Service

During transition, the contractor shall maintain the ability for any authorized on-net FTS2000 SVS user or FTS2001 contract SVS user to direct dial any other such user with 10-digit dialing. This capability does not preclude the use of the PSN for carrying such traffic, if necessary and approved by the TCC.

C.4.2.7.10.2 Direct Station-to-Station Dialing for Circuit Switched Data Service

During transition, the contractor shall maintain the ability for any authorized FTS2000 SDS user or FTS2001 contract CSDS user to direct dial any other such user with 10-digit dialing. This capability does not preclude the use of the PSN for carrying such traffic.

C.4.2.7.10.3 National Security and Emergency Preparedness Requirements

The contractor shall adhere to all NS/EP requirements, as specified in Section C.5, pertaining to the provision of services and associated features during the period in which services are transitioned from its contract.

C.4.2.7.10.4 Location Cutover Contingency

As part of the contractor’s TMP described in Section C.4.2.4, the contractor shall submit to the TCC contingency plans covering each location at which services are transitioned from the FTS2000 networks to the contractor’s network. These plans shall describe how the contractor will provide for 100 percent restoration of FTS2000 services in the event that the contractor’s services do not pass acceptance testing. The activation of contingency plans shall take no longer than four hours. The contractor shall maintain the capability to activate contingency plans until the contractor’s services at a location have been accepted by the authorized user. The contractor shall immediately activate its contingency plans for any of the following reasons:

(a) Failure of 10 percent or more of the access facilities for the contractor’s services at a location

(b) Failure of acceptance testing at a location

(c) Other needs determined by the TCC or the LGC

C-281


C.4.2.8 Government Responsibilities During Transition

C.4.2.8.1 Letter of Agency

For transition the CO will issue the contractor a letter of agency as specified in Section G.8. The letter of agency may include the authority to arrange for disconnection of service.

C.4.2.8.2 Role of Program Management Office

The functions to be performed by the Government and/or its representatives regarding transition activities will include the following actions:

(a) As required, reviewing and recommending approval or rejection of all plans related to transition activities.

(b) Approving the number of locations by service type to be cut over per phase of the transition activities.

(c) Ensuring that the contractor provides user training, if required, at locations acquiring service from the contractor.

(d) Reviewing test results as required (Section E).

(e) Assisting in resolving any conflicts with the incumbent service providers and other contractors during the transition of services to the contractor’s network.

(f) Overall program management and transition responsibility.

(g) Monitor and facilitate coordination with agencies, local sites, and local contractors.

C.4.2.8.3 Role of Local Government Contact

The Government will identify the LGC for each location within 30 calendar days after notice to proceed. The LGCs will be responsible for coordinating all transition planning and other activities through, at least, the acceptance of all transitioned services at the location(s) for which they are responsible. The LGC may or may not actually be located at the location(s) acquiring service from the contractor. If the identities of the LGCs are required for any of the plans associated with transition activities and if the identities have not been made known to the contractor prior to the submission of those plans to the Government, the Government will not hold the contractor responsible for the lack of LGC identities in the plans. The contractor shall indicate in any of the plans which require the LGC identities or LGC

C-282


provided information or assistance that the identities will be supplied by the Government and that the contractor shall include the identities or information in any subsequent submission(s) of the plans.

The responsibilities of the LGCs include but are not limited to, the following:

(a) Serve as the Government’s local central point of contact for a location’s Government-related transition planning and coordination activities.

(b) Assist the contractor during the user location inventory by providing any available telecommunications information about that location(s) and providing other assistance required, such as building access.

(c) Assist the contractor in ascertaining from the incumbent contractors the type of equipment that is required to support the type and quantity of the contractor’s service(s) to be installed.

(d) Upon receipt of information from the FTS2001 contractor regarding the cutover date and location requirements, coordinate with the appropriate incumbent contractors or other contractor(s) who are providing that location with telephone switching (i.e., whether PBX or Centrex) and other telecommunications facilities.

(e) Disseminate to location users all training materials that have been obtained from the contractor and coordinate the internal scheduling of personnel for training sessions at locations where it has been agreed the Government will perform those functions.

(f) If desired by the LGC or associated agency, monitor cutover and testing on site as performed by the contractor. Accept or reject service in accordance with the contract. Notify the TCC whether the service is acceptable following acceptance testing.

The contractor will not be held responsible for the lack of LGC provided information or assistance if the Government has not provided the identity of the LGC.

C.4.3 Migration

C.4.3.1 Migration Plan

The contractor shall deliver a MP to the MCC within 60 calendar days after receiving notice from the Government to begin migration activities to move designated existing service(s) on

C-283


particular legacy networks onto the contractor’s network. The contractor shall prepare a separate MP for each migration project. Each MP shall document the contractor’s migration and cutover strategies for all services to be migrated in that project, including coordination with the agency or agencies whose legacy network(s) is/are being migrated. The MCC, in conjunction with affected agencies, will review the MP within 30 days after its submission. The contractor shall submit a revised MP within 15 days after receiving the review from the MCC. The MCC, in conjunction with advice from affected agencies, intends to approve each MP within 15 days after receiving the revised MP. Refer to Section C.3.2.7 for the media of delivery and Section F for other deliverable requirements.

The contractor shall present its approach to optimizing access service (Sections C.3.8.2 and C.4.1.6) based on the available traffic information and the existing access circuit arrangements.

Each MP shall describe the possibility of operating services in parallel, i.e., full service operation on agencies’ existing legacy network(s) with associated operation of test traffic on the contractor’s network. Each MP shall describe the capability, if needed, for services to be temporarily returned to their original networks and configurations prior to the services being accepted on the contractor’s network.

Each MP shall include an analysis of the key areas of risk entailed in the migration activities. The MP shall address the impact and extent of possible disruptions, if any, on users regarding operation of their services or networks during the cutover activities. Each MP shall describe the contractor’s approach to minimize any impact in order to make the migration as transparent as possible to the users.

Each MP shall address the mission criticality of the services being migrated and describe the cutover options that the contractor intends to use for migrating critical and other services.

Each MP shall include a general description of the tasks required to prepare locations for the cutovers. It shall describe the means the contractor will use to verify that services are performing satisfactorily after the cutovers are completed.

In conjunction with the agencies whose services on particular legacy networks are to be migrated, the MCC will determine the sequence in which agencies will migrate their services based on the agencies’ missions. This sequence will then be coordinated with the contractor. The contractor shall incorporate this sequence into its MP.

Each MP shall include details of:

(a) Migration schedules

C-284


(1) Phasing of service types being cut over

(2) Identifying service locations for the cutovers

(3) Identifying the lead-times required for cutovers

(4) Identifying the month in which services at each location will be cut over

(5) Identifying the steps required to prepare the locations for the cutovers

(6) Identifying the steps required to complete the cutovers

(7) Identifying how each type of existing service may be affected during the cutover activities


(c) Type of Government equipment involved at each location in which services will be cut over



(f) Logistics




C-285



(k) Access circuit optimization (as described in Sections C.3.8.2 and C.4.1.6)

(l) Security clearances required for personnel involved in the migration

C.4.3.2 Migration Interconnection Plan

The contractor shall provide a separate Migration Interconnection Plan (MIP) to the MCC within 90 calendar days after being notified by the MCC for each occurrence when service(s) on particular legacy networks are to be migrated onto the contractor’s network. Each of these MIPs shall describe the interconnection arrangements between the contractor’s network facilities and legacy networks required in order to continue uninterrupted service as all traffic is migrated onto the contractor’s network facilities. Refer to Section C.3.2.7 for the media of delivery and Section F for other deliverable requirements.

Each MIP shall include:

(a) Listing of the network facilities to be used during the interconnection of networks to include such items as:

(1) Number and type(s) of gateways(2) Description of network-to-network interface(s)(3) Type(s) of temporary equipment and its (their) location(s)

(b) Anticipated amount of traffic, by service type, to be carried at each interconnection including the approach to aggregate traffic, by service type, during the migration

(c) Coordination of routing, numbering, dialing, and signaling plan changes

(d) Arrangements proposed to achieve interconnectivity between the legacy networks and the contractor’s network during the migration of services

The MCC, in conjunction with affected agencies, will review and coordinate recommended changes to each MIP and intends to approve each Interconnection Plan within 60 calendar days after its submission.

C.4.3.3 Migration Management Plan

The contractor shall develop and maintain a MMP consistent with the contractor’s Government approved MP for each occurrence when service(s) on particular legacy

C-286


networks are to be migrated onto the contractor’s network. Each MMP shall serve as a progress report, master log, and a working blueprint for the contractor’s day-to-day activities during the migration of services at individual users’ locations. The initial version of each MMP shall be submitted to the MCC by the contractor no later than 50 calendar days prior to the first scheduled migration activity for the contractor. A local committee (Section C.4.3.6.7) shall be responsible for reviewing and updating each MMP, as necessary. The Government intends to approve each MMP within 30 calendar days after its submission.

The MMP shall contain all schedules, exceptions, and any deviations from the testing procedures contained in the contractor’s Migration Verification Test Plans (Section E.2.2.2.2). The MMP shall contain migration contingency plans (Section C.4.3.6.10.4) for each location at which services are migrated to the contractor’s network. The MMP shall contain all proposed changes to the existing access service facilities to optimize access service as described in Section C.4.1.6. The contractor shall make the data in each MMP available to the MCC on-line. Refer to Section C.3.2.7 for the media of delivery and Section F for other deliverable requirements. The contractor shall control access to the MMP through the use of appropriate security techniques, such as identification and authentication, for authorized individuals. The MMP shall be organized by weeks, and updated daily. The contractor’s initial version of each MMP shall begin with the month in which the first migration activities are scheduled to occur.

No later than the second Government business day following the weekly reporting interval, the contractor shall provide weekly summaries of migration activities to the MCC on-line regarding the progress of pending and concluded migration activities and the status of activities delineated in each MMP. These weekly reports shall contain the following information:

(a) Count and identification of services migrated since last report

(b) Locations at which services were migrated since last report

(c) Number of locations remaining to be completed for all services scheduled for migration

(d) Number of services remaining to be completed for all services scheduled for migration

C-287


(e) Comparison of services migrated to date with the number and locations of services proposed in the latest coordinated and approved migration schedule

(f) Description of services (and their locations) for which migration is in jeopardy of not meeting the current migration schedule

(g) During the weekly reporting period, reports of service impairment or degraded service quality (together with service failures and service blockage events), including gateways established between FTS2001 and non-FTS2001 contractors

(h) Discussion of any issues affecting the timely completion of all migration activities

Representatives of the contractor shall meet with appropriate Government representatives as deemed necessary by the MCC and the contractor to apprise the Government of progress in completing the migration schedules and to obtain approval for any type of changes to the migration activities and schedules as they occur. The contractor shall be responsible for coordinating all meetings and establishing an agenda. Where migration activities of jointly served locations are involved, the contractors shall participate in joint meetings held among all interested contractors and Government personnel.

C.4.3.4 Private Dialing Plans for Migration

In coordination with the Number Plan Administrator function (Section C.3.2.7.4), the contractor shall develop and administer plans for migrating stations that require contractor-specific private numbers (Section C.3.2.7.4.2(b)). Each private dialing plan shall be provided to the MCC by the contractor within 15 calendar days after receiving notice from the Government to begin migration activities. Each dialing plan shall be based on the information provided to the contractor by the Government identifying the service(s) on particular legacy networks to be migrated. The MCC in conjunction with affected agencies, will provide a review of the dialing plan within 15 days after its submission. The contractor shall submit a revised dialing plan within 15 days after receiving the review from the MCC. The MCC, in conjunction with affected agencies, intends to approve a final dialing plan 15 days after receiving the revised dialing plan. Refer to Section C.3.2.7 for the media of delivery and Section F for other deliverable requirements.

C.4.3.5 Migration Verification Test Plans

The contractor shall provide Migration Verification Test Plans to the CO as described in Section E.2.2.2.2.

C-288


C.4.3.6 Contractor Responsibilities for Migration

C.4.3.6.1 Office of Migration Management

The contractor shall establish an Office of Migration Management (OMM) within 15 calendar days following notice to begin migration activities. The OMM shall be charged with overseeing all aspects of the activities related to the migration of services from the existing legacy network onto the contractor’s network. During the migration period, the OMM shall provide a single point of contact for these activities with the MCC and with agency users at locations where migration activities will occur. The OMM shall administer all contractor plans, policies, and specific migration schedules regarding the contractor’s services.

The contractor’s OMM shall provide a single point of contact for each LGC for migrating services. The OMM’s responsibility for coordinating all activities extends to any activity conducted by any subcontractor or vendor on behalf of the contractor. All requests for information or assistance directed to individual user locations for purposes of site preparation shall come through the OMM and shall be directed to the appropriate user location’s LGC.

The contractor shall provide an OMM representative for each location where migration activities are to occur. This representative shall be available to communicate with the site’s representatives prior to, during, and immediately following cutover activities. This OMM representative shall be available to answer any questions related to migration.

Via the contractor’s service order tracking system, the OMM shall make available to the MCC information related to the content of service orders (e.g., equipment and special engineering requirements) and the status of service orders associated with the migration of services onto the contractor’s network and the removal of services from the existing legacy networks. The contractor shall update daily the information available from the service order tracking system.

C.4.3.6.2 Migration Network and User Location Inventories

The contractor shall begin to conduct its own network and user location inventories related to migrating service(s) on particular legacy networks no later than 30 calendar days after receiving notice from the Government to begin migration activities. The contractor shall begin providing to the MCC the inventory information defined below in this section no later than 30 calendar days after approval of the contractor’s revised MP. Refer to Section C.3.2.7 for the media of delivery and Section F for other deliverable requirements.

C-289


C.4.3.6.2.1 Migration Network Inventory

The contractor shall obtain from Government sources, where available, or by means of a site survey, as necessary, all information that is needed to accomplish the migration of all services for which the contractor is responsible.

C.4.3.6.2.2 Migration User Location/Service Delivery Point Inventory

The contractor shall obtain from Government sources, where available, or by means of a site survey, as necessary, all information regarding the user location/SDP equipment which has an impact on the delivery of service(s) to that location/SDP. The acquisition of this information shall be the sole responsibility of the contractor. The contractor shall complete a user location/SDP inventory for each location/SDP with which it is associated. The contractor shall obtain an SDP ID Base Code from the SDP ID Administrator where necessary for each SDP. This inventory shall be entered into the Migration Database (Section C.4.3.6.4).

C.4.3.6.3 Migration Traffic Statistics

Using Government sources associated with the service(s) on particular legacy networks being migrated or physical checks, as necessary, the contractor shall obtain an update of all legacy system traffic information necessary for the completion of the contractor’s MP. The Government will provide the contractor with traffic data from the legacy network(s) as available. The contractor shall verify all legacy system traffic information for a given location in advance of all specific migration activities at that location. The contractor shall begin providing traffic information to the MCC no later than 30 calendar days after delivery of the contractor’s MP. Refer to Section C.3.2.7 for the media of delivery and Section F for other deliverable requirements.

C.4.3.6.4 Migration Database

The contractor shall develop, provide, and maintain information schedules along with a summary of all information contained in the MMP for the contractor’s user locations/SDPs. The contractor shall ensure that the access to this database is granted to only authorized users. The contractor shall provide access no later than 30 calendar days after approval of each MMP. The database shall be as complete as possible initially, continually updated as more precise information becomes available, and fully up-to-date regarding information on a particular user location at the time access service is ordered for that location. The database information shall continue to be updated as required to maintain its currency and accuracy until migration is complete. Following completion of the migration activities, the contractor shall provide the Government the contents of the complete migration database including all

C-290


information from the contractor’s migration activities. Refer to Section C.3.2.7 for the media of delivery and Section F for other deliverable requirements.

In the database, the contractor shall maintain the following information in addition to the information mentioned in Sections C.4.3.6.2 and C.4.3.6.3:



(c) Agency(s) user located at User Location, itemized by Agency department or division name



(f) LGC name and commercial telephone number

(g) Date and time that user location is scheduled for migration



(j) All legacy network system telecommunications facilities currently employed at the user location, including:

(1) Number and description of dedicated access circuits used for connecting legacy services to the User Location

(i) Identified circuits by type(s) of legacy service (SVS, SDS, PSS, DTS, Compressed VTS, VTS) carried


C-291


(iii) Identify type(s) of legacy contractor-provided equipment that each circuit (or each channel in a multiplexed circuit) is terminated in (e.g., data service unit, channel bank, PAD or FRAD, modem, etc.) at the user location









C-292




(l) Status information regarding the migration activities (highlighted in the database record if the cutover is in jeopardy or delayed)






(q) Security clearances required for personnel involved in migration

C.4.3.6.5 Coordination During Migration

During the migration of services, the contractor shall be responsible for coordinating all aspects of the migration of traffic at user locations for which it is responsible. When migration of traffic involves the simultaneous actions at a location of more than one contractor, the MCC may appoint, if it deems appropriate, one contractor as overall coordinator at a location. The other contractor(s) shall work cooperatively with the overall coordinator at that location. However, each contractor shall be responsible for its own migration activities required at a location irrespective of the Government’s appointment of an overall coordinator.

C-293



(a) Developing migration procedures to facilitate the coordination of all transition or migration activities with the MCC, LGC, and other contractors. These procedures shall be utilized for migration preparations, schedules, required Government resources, and progress in all areas relating to the migration of traffic at user locations.

(b) Coordinating all requests to the LGC for disconnection of present non-FTS2000 services as a result of migration activities.

(c) Coordinating all information-gathering activities with the MCC, other contractors, and Government representatives at user locations in order to provide services and associated features.

(d) During migration activities, coordinating all on-site visits to user locations with the LGC, the MCC, subcontractors, and any other involved parties.

C.4.3.6.6 Migration Notification and Scheduling

During the migration of services, the contractor shall notify the LGC about cutover activity at least 60 calendar days before the location is to be migrated, except as otherwise directed by the Government. The contractor shall follow the procedures listed below when notifying all involved parties concerning migration activities:

(a) The contractor shall initially notify each LGC of the approved scheduled migration date and time for the particular user location. The contractor shall be responsible to verify receipt of the notification by the LGC.

(b) The contractor shall provide detailed documentation to both the LGC and to the MCC at least 60 calendar days prior to the start of service cutover at a location, including the following information:



C-294


(3) The commercial circuit numbers of the new or modified circuits and access facilities. The contractor may provide the documentation without the circuit numbers if the numbers are not available when the documentation is to be provided. The contractor shall update the documentation with the circuit number when the numbers become available


(5) Requests for assistance required by the contractor from the individual user location in order to complete migration activities, including actions such as unlocking telephone rooms and providing special security passes for personnel.

(6) A migration activities list informing each user location of all peripheral activity that will take place prior to the actual physical migration of service(s). As an example, this list shall include installation of equipment at various times prior to migration activities or on-site visits by subcontractors. Representatives of the contractor shall be solely responsible for coordinating all such activity and visits with each LGC. This coordination effort includes scheduling visits, making any requests for assistance from the user location, and verifying with the user location that schedules have been adhered to by subcontractors.

(7) Procedures to be followed for trouble reporting during the migration activities.

(8) The security clearances, as required, of personnel to perform the migration activities on Government sites.

The contractor shall initiate and complete all cutover activities outside of normal business hours unless otherwise arranged with, or requested by, the user location’s LGC or other authorized representative. All cutover activities at a location shall be completed within 12 hours after being initiated unless special approval is obtained in advance from the MCC.


C-295


C.4.3.6.7 Establishment of Local Committees for Migration

During the migration of services, the contractor shall be responsible for establishing a local committee that includes its representatives, the LGC, and appropriate local vendors for each location where services are to be migrated. At a location for which more than one contractor is responsible, all involved contractors shall agree on the composition of a local committee at the location with the assistance of the MCC, if required.

The contractor shall establish the local committee at least 50 calendar days prior to the start of service cutover at the location. The contractor shall invoke its existing commercial coordination processes when establishing the local committee. Face-to-face meetings need not always be held. Teleconferencing resources should be used whenever possible.

The local committee will provide a forum for coordination of issues related to the migration activities at a location. Through the committee, the contractor shall facilitate cooperation among the participating members. At a minimum, the committee members shall coordinate cutover schedules, necessary equipment installations, and site modifications.

C.4.3.6.8 Verification of Migration Information

The contractor shall negotiate a date with the Government after which no changes that would affect migration will be made at a location. After this date, the contractor shall verify with the LGC for that location all information the contractor requires for the proper and efficient migration of services at that location.

C.4.3.6.9 Notification of Completion of Migration Activity

The contractor shall inform the LGC at a user location and the MCC when migration activities, including installation and all required contractor-performed testing, are completed at the location according to the requirements of Section E.2.

C.4.3.6.10 Migration Technical Requirements

The Government requires compliance with a number of technical requirements to ensure quality of service and continuity of service for all legacy network users as their services are migrated. The contractor shall be responsible for adhering to the requirements set forth below.

C-296


C.4.3.6.10.1 Direct Station-to-Station Dialing for Switched Voice Service

During the migration of switched voice service from a legacy network to the contractor’s network, the contractor shall maintain the ability for any existing legacy switched voice user to direct dial any on-net SVS user and any on-net SVS user to direct dial any existing legacy switched voice user associated with the switched voice service being migrated. This capability does not preclude the use of the PSN for carrying such traffic, if necessary and approved by the MCC.

C.4.3.6.10.2 Direct Station-to-Station Dialing for Circuit Switched Data Service

During the migration of circuit switched data service from a legacy network to the contractor’s network, the contractor shall maintain the ability for any existing legacy circuit switched data service user to direct dial any CSDS user and any CSDS user to direct dial any existing legacy circuit switched data service user associated with the circuit switched data service being migrated. This capability does not preclude the use of the PSN for carrying such traffic.


The contractor shall adhere to all NS/EP requirements, as specified in Section C.5, pertaining to the provision of services and associated features during the period in which services are migrated from its contract.

C.4.3.6.10.4 Location Cutover Contingency

As part of the contractor’s MMP described in Section C.4.3.3, the contractor shall submit to the MCC contingency plans covering each location at which services are migrated from legacy networks to the contractor’s network. These plans shall describe how the contractor will provide for 100 percent restoration of existing non-FTS2000 services in the event that the contractor’s services do not pass acceptance testing. The activation of contingency plans shall take no longer than four hours. The contractor shall maintain the capability to activate contingency plans until the contractor’s services at a location have been accepted by the authorized user. The contractor shall immediately activate its contingency plans for any of the following reasons:

C-297


(a) Failure of 10 percent or more of the access facilities for the contractor’s services at a location

(b) Failure of acceptance testing at a location

(c) Other needs determined by the MCC or the LGC

C.4.3.7 Government Responsibilities During Migration


For migration, the CO will issue the contractor a letter of agency as specified in Section G.8. The letter of agency may include the authority to arrange for disconnection of service.


The functions to be performed by the Government and/or its representatives regarding migration activities will include the following actions:

(a) As required, reviewing and recommending approval or rejection of all plans related to migration activities.

(b) Approving the number of locations by service type to be cut over per phase of the migration activities.

(c) Ensuring that the contractors provide user training, if required, at locations acquiring service from the contractor.

(d) Reviewing test results as required in Section E.

(e) Assisting in resolving any conflicts with the incumbent service providers and other contractors during the migration of services to the contractor’s network.

(f) Overall program management and migration responsibility.


C-298



The Government will identify the LGC for each location within 30 calendar days after notice to proceed with migration. The LGC will be responsible for coordinating all migration planning and other activities through, at least, the acceptance of all migrated services at the location(s) for which they are responsible. The LGC may or may not actually be located at the location(s) acquiring service from the contractor. If the identities of the LGCs are required for any of the plans associated with transition activities and if the identities have not been made known to the contractor prior to the submission of those plans to the Government, the Government will not hold the contractor responsible for the lack of LGC identities in the plans. The contractor shall indicate in any of the plans which require the LGC identities that the identities will be supplied by the Government and that the contractor shall include the identities in any subsequent submission(s) of the plans.

The responsibilities of the LGC include but are not limited to, the following:

(a) Serve as the Government’s local central point of contact for a location’s Government-related migration planning and coordination activities.


(c) Assist the contractor in ascertaining from incumbent contractors the type of equipment that is required to support the type and quantity of the contractor’s service(s) to be installed.

(d) Upon receipt of information from the FTS2001 contractor regarding the cutover date and location requirements, coordinate with the appropriate incumbent contractors or other contractor(s) who are providing that location with telephone switching (i.e., whether PBX or Centrex) and other telecommunications facilities.


(f) If desired by the LGC or associated agency, monitor cutover and testing on site as performed by the contractor. Accept or reject service in accordance with the contract. Notify the MCC whether the service is acceptable following acceptance testing.

C-299


C.4.4 Implementation

The following requirements will apply for those implementation activities that are deemed by the Government to be sufficiently important or complex as to require them, such as large implementation projects or the first implementation of a new or enhanced service. The Government does not anticipate applying these requirements to the routine implementation of limited quantities of mature services.

C.4.4.1 Implementation Plan

The contractor shall deliver an ImP within 15 calendar days after receiving notice from the Government to begin a specific implementation project. The contractor shall prepare a separate ImP for each set of services to be implemented. Each ImP shall document the contractor’s implementation strategies, including coordination with the user agency(ies). The contractor shall present its approach to optimization of access service (Section C.4.1.6) based on the available traffic information and the existing access circuit arrangements. The ICC, in coordination with the affected agency or agencies, will review the ImP within 15 days after its submission. The contractor shall submit a revised ImP within 15 days after receiving the review from the ICC. The ICC intends to approve a final ImP within 15 days after receiving the revised ImP. Refer to Section C.3.2.7 for the media of delivery and Section F for other deliverable requirements.

Each ImP shall include an analysis of the key areas of risk entailed in the implementation activities. Each ImP shall describe the contractor’s approach to minimize any impact in order to make the implementation as easy as possible to the users. Each ImP shall address the criticality of the services being implemented and describe the options that the contractor intends to use to assure that mission-critical requirements will be met.

Each ImP shall include a general description of the tasks required to prepare locations for the implementation. It shall describe the means the contractor will use to verify that services are performing satisfactorily after the implementations are completed.

For new or enhanced service(s), the ImP shall describe how, prior to implementation, the contractor will ensure that the service(s) and any necessary support systems (including service ordering and automated billing) will operate correctly. The ImP shall describe how the Government will be able to verify correct operation of the service(s) and support systems prior to implementation. The contractor may use OCDs, trials, or other means to support these requirements.

In conjunction with the user agencies, the ICC will determine the sequence in which agencies will implement their services based on the agencies’ missions. This sequence will

C-300


then be coordinated with the contractor. The contractor shall incorporate this sequence into its ImP.

The ImP shall include details of:

(a) Implementation schedules

(1) Phasing of service types being implemented

(2) Identifying service locations for the implementations

(3) Identifying the lead-times required for implementations

(4) Identifying the month in which services at each location will be implemented

(5) Identifying the steps required to prepare the locations for the implementations

(6) Identifying the steps required to complete the implementations

(7) Identifying how each type of existing service may be affected during the implementation activities


(c) Type of Government equipment involved at each location in which services will be implemented



(f) Logistics





C-301


(k) Access service optimization (as described in Sections C.3.8.2 and C.4.1.6)

(l) Optimize new services with existing services of the same agency during implementation

(m) Security clearances required for personnel involved in the implementation project

C.4.4.2 Implementation Management Plan

The contractor shall develop an IMP consistent with the contractor’s Government approved ImP (Section C.4.4.1) for each implementation project. Each IMP shall serve as a progress report, master log, and a working blueprint for the contractor’s day-to-day activities during the implementation of services at individual users’ locations. The initial version of each IMP shall be submitted to the ICC by the contractor after ImP approval, but no later than 50 calendar days prior to the first scheduled implementation activity for the contractor. A local committee (Section C.4.4.5.7) shall be responsible for reviewing and updating the IMP. The Government intends to approve the final IMP within 30 calendar days after receiving the revised IMP. With the approval of the ICC, implementation activities may begin before approval of the IMP.

Each IMP shall contain all schedules, exceptions, and any deviations from the testing procedures contained in the contractor’s Implementation Verification Test Plans (Section E.2.2.2.3). The IMP shall contain all proposed changes to the existing access service facilities to optimize access service as described in Section C.4.1.6. The contractor shall make the data in each IMP available to the ICC on-line. Refer to Section C.3.2.7 for the media of delivery and Section F for other deliverable requirements. The contractor shall control access to the IMP through the use of appropriate security techniques, such as identification and authentication, for authorized individuals. The IMP shall be organized by weeks, and updated daily. The contractor’s initial version of each IMP shall begin with the month in which the first implementation activities are scheduled to occur.

No later than the second Government business day following the weekly reporting interval, the contractor shall provide weekly summaries of implementation activities to the ICC via the Internet regarding the progress of pending and concluded implementation activities and the status of activities delineated in each IMP. These weekly reports shall contain the following information:

C-302


(a) Count and identification of services implemented since last report

(b) Locations at which services were implemented since last report

(c) Number of locations remaining to be completed for all services scheduled for implementation

(d) Number of services remaining to be completed for all services scheduled for implementation

(e) Comparison of services implemented to date with the number and locations of services proposed in the latest coordinated and approved implementation schedule

(f) Description of services (and their locations) for which implementation is in jeopardy of not meeting the current implementation schedule

(g) During the weekly reporting period, reports of service impairment or degraded service quality (together with service failures and service blockage events)

(h) Discussion of any issues affecting the timely completion of all implementation activities

Representatives of the contractor shall meet with appropriate Government representatives as deemed necessary by the ICC and the contractor to apprise the Government of progress in completing the implementation schedules and to obtain approval for any type of changes to the implementation activities and schedules as they occur. The contractor shall be responsible for coordinating all meetings and establishing an agenda. Where implementation activities at jointly served locations are involved, the contractor shall participate in joint meetings held among all interested contractors and Government personnel.

C.4.4.3 Private Dialing Plan for Implementation

In coordination with the Number Plan Administrator function (Section C.3.2.7.4), the contractor shall develop and administer a plan for implementing stations that require non-commercial agency-specific private numbers (Section C.3.2.7.4.2(a)). This private dialing plan shall be provided to the ICC within 15 calendar days after receiving notice from the Government to begin implementation activities. The dialing plan shall be based on the information provided to the contractor by the Government identifying the service(s) on particular networks to be implemented. The ICC, in conjunction with advice from affected agencies, will provide a review on the dialing plan within 15 days after its submission. The contractor shall submit a revised dialing plan within 15 days after receiving the review from

C-303


the ICC. The ICC, in conjunction with advice from affected agencies, intends to approve a final dialing plan 15 days after receiving the revised dialing plan. Refer to Section C.3.2.7 for the media of delivery and Section F for other deliverable requirements.

C.4.4.4 Implementation Verification Test Plans

The contractor shall provide Implementation Verification Test Plans to the CO as described in Section E.2.2.2.3.

C.4.4.5 Contractor Responsibilities for Implementation

C.4.4.5.1 Office of Implementation Management

The contractor shall establish an Office of Implementation Management (OIM) within 15 calendar days following notice to begin an implementation project. The OIM shall be charged with overseeing all aspects of the activities related to the implementation of services on the contractor’s network. During the implementation period, the OIM shall provide a single point of contact for these activities with the ICC and with agency users at locations where implementation activities will occur. The OIM shall administer all contractor plans, policies, and specific implementation schedules regarding the contractor’s services.

The contractor’s OIM shall provide a single point of contact for each LGC for implementing services. The OIM’s responsibility for coordinating all activities extends to any activity conducted by any subcontractor or vendor on behalf of the contractor. All requests for information or assistance directed to individual user locations for purposes of site preparation shall come through the OIM and shall be directed to the appropriate user location’s LGC.

The contractor shall provide an OIM representative for each location where implementation activities are to occur. This representative shall be available to communicate with the site’s representatives prior to, during, and immediately following implementation activities. This OIM representative shall be available to answer any questions related to implementation.

Via the contractor’s service order tracking system, the OIM shall make available to the ICC information related to the content of service orders (e.g., equipment and special engineering requirements) and the status of service orders associated with the implementation of services onto the contractor’s network. The contractor shall update daily the information available from the service order tracking system.

C-304


C.4.4.5.2 Implementation Network and User Location Inventories

The contractor shall begin to conduct its own network and user location inventories no later than 30 calendar days after notice to begin implementation activities. The contractor shall begin providing to the ICC the information defined below in this section no later than 15 calendar days after the contractor begins conducting network and user location inventories. Refer to Section C.3.2.7 for the media of delivery and Section F for other deliverable requirements.

C.4.4.5.2.1 Implementation Network Inventory

The contractor shall obtain from Government sources, where available, or by means of a site survey, as necessary, all information that is needed to accomplish the implementation of all services for which the contractor is responsible.

C.4.4.5.2.2 Implementation User Location/Service Delivery Point Inventory

The contractor shall obtain from Government sources, where available, or by means of a site survey, as necessary, all information regarding the user location/SDP equipment which has an impact on the implementation of service(s) to that location/SDP. The acquisition of this information shall be the sole responsibility of the contractor. The contractor shall complete a user location/SDP inventory for each location/SDP where service is to be implemented with which it is associated. The contractor shall obtain an SDP ID Base Code from the SDP ID Administrator where necessary for each SDP. This inventory shall be entered into the Implementation Database (Section C.4.4.5.4).

C.4.4.5.3 Implementation Traffic Statistics

From Government sources, where available, or by means of the contractor’s site surveys, as necessary, the contractor shall obtain a projection of traffic information necessary for the completion of the ImP. The contractor shall verify, to the extent possible, all traffic information for a given location in advance of all specific implementation activities at that location. The contractor shall begin providing traffic information it obtained to the ICC no later than 15 calendar days after approval of the contractor’s ImP by the Government. Refer to Section C.3.2.7 for the media of delivery and Section F for other deliverable requirements.

C-305


C.4.4.5.4 Implementation Database

The contractor shall develop, provide, and maintain information implementation schedules along with a summary of all information contained in the ImP for the contractor’s user locations/SDPs. The contractor shall ensure that the access to this database is granted to only authorized users. The contractor shall provide access no later than 30 calendar days after approval of the IMP. The database shall be as complete as possible initially, continually updated as more precise information becomes available, and fully up-to-date regarding information on a particular user location at the time access service is ordered for that location. The database information shall continue to be updated as required to maintain its currency and accuracy until implementation is complete. Following completion of the implementation activities, the contractor shall provide the Government the contents of the complete implementation database including all information from the contractor’s implementation activities. Refer to Section C.3.2.7 for the media of delivery and Section F for other deliverable requirements.

In the database, the contractor shall maintain the following information in addition to the information mentioned in Sections C.4.4.5.2 and C.4.4.5.3:



(c) Agency user(s) located at User Location, itemized by Agency department or division name



(f) LGC name and commercial telephone number

(g) Date and time that user location is scheduled for implementation



C-306


(j) All FTS2001 network system telecommunications facilities currently employed at the user location, including:

(1) Number and description of dedicated access circuits used for connecting FTS2001 services to the User Location (if a virtual on-net location, so note and list telephone numbers presubscribed to FTS2001 contractor)

(i) Identified circuits by type(s) of FTS2001 service (SVS, SDS, PSS, DTS, Compressed VTS, VTS) carried


(iii) Identify type(s) of FTS2001 contractor-provided equipment that each circuit (or each channel in a multiplexed circuit) is terminated in (e.g., data service unit, channel bank, PAD or FRAD, modem, etc.) at the user location







C-307






(l) Status information regarding the implementation activities (highlighted in the database record if the implementation is in jeopardy or delayed)






(q) Security clearances required for personnel involved in implementation

C.4.4.5.5 Coordination During Implementation

During the implementation of services, the contractor shall be responsible for coordinating all aspects of the implementation of traffic at user locations for which it is responsible. When implementation of traffic involves the simultaneous actions at a location of more than one contractor, the ICC may appoint, if it deems appropriate, one contractor as overall coordinator at a location. The other contractor(s) shall work cooperatively with the overall

C-308


coordinator at that location. However, each contractor shall be responsible for its implementation activities required at a location irrespective of the Government’s appointment of an overall coordinator.


(a) Developing implementation procedures to facilitate the coordination of implementation activities with the ICC, LGC, and other contractors. These procedures shall be utilized for implementation preparations, schedules, required Government resources, and progress in all areas relating to implementation of traffic at user locations.

(b) Coordinating all requests to the LGC for disconnection of services as a result of implementation activities.

(c) Coordinating all information-gathering activities with the ICC, other contractors, and Government representatives at user locations in order to provide services and associated features.

(d) During implementation activities, coordinating all on-site visits to user locations with the ICC, subcontractors, and any other involved parties.

C.4.4.5.6 Implementation Notification and Scheduling

During implementation of services, the contractor shall notify the LGC about implementation activity at least 60 calendar days before the location is to be implemented, except as otherwise directed by the Government. The contractor shall follow the procedures listed below when notifying all involved parties concerning implementation activities:

(a) The contractor shall initially notify each LGC of the approved scheduled implementation date and time for the particular user location. The contractor shall be responsible to verify receipt of the notification by the LGC.

(b) The contractor shall provide detailed documentation to both the LGC and to the ICC at least 60 calendar days prior to implementation activities beginning at a location, including the following information:

C-309




(3) The commercial circuit numbers of the new or modified circuits and access facilities.


(5) Requests for assistance required by the contractor from the individual user location in order to complete implementation activities, including actions such as unlocking telephone rooms and providing special security passes for personnel.

(6) An implementation activities list informing each user location of all peripheral activity that will take place prior to the actual physical implementation of service(s). As an example, this list shall include installation of equipment at various times prior to implementation activities or on-site visits by subcontractors. Representatives of the contractor shall be solely responsible for coordinating all such activity and visits with each LGC. This coordination effort includes scheduling visits, making any requests for assistance from the user location, and verifying with the user location that schedules have been adhered to by subcontractors.

(7) Procedures to be followed for trouble reporting during implementation activities.

(8) The security clearances, as required, of personnel to perform the implementation activities on Government sites.


The contractor shall initiate and complete all service initiation activities outside of normal office/business hours unless otherwise arranged with, or requested by, the user location’s LGC or other authorized representative. All service initiation activities at a location shall be completed within 12 hours after being initiated unless special approval is obtained in advance from the ICC.

C-310



C.4.4.5.7 Establishment of Local Committees for Implementation

During the implementation of services, the contractor shall be responsible for establishing a local committee that includes its representatives, the LGC, and appropriate local vendors for each location where services are to be implemented. At a location for which more than one contractor is responsible, all involved contractors shall agree on the composition of a local committee at the location with the assistance of the ICC, if required.

The contractor shall establish the local committee at least 50 calendar days prior to the start of service initiation activities at the location. The contractor shall invoke its existing commercial coordination processes when establishing the local committee. Face-to-face meetings need not always be held. Teleconferencing resources should be used whenever possible.

The local committee will provide a forum for coordination of issues related to imple-mentation activities at a location. Through the committee, the contractor shall facilitate cooperation among the participating members. At a minimum, the committee members shall coordinate implementation schedules, necessary equipment installations, and site modifications.

C.4.4.5.8 Verification of Implementation Information

The contractor shall negotiate a date with the Government after which no changes that would affect implementation will be made at a location. After this date, the contractor shall verify with the LGC for that location all information the contractor requires for the proper and efficient implementation of services at that location.

C.4.4.5.9 Notification of Completion of Implementation Activity

The contractor shall inform the LGC at a user location and the ICC when implementation activities, including installation and all required contractor-performed testing, are completed at the location according to the requirements of Section E.

C-311


C.4.4.5.10 Implementation Technical Requirements

The Government requires compliance with a number of technical requirements to ensure quality of service and continuity of service for all users as their services implemented. The contractor shall be responsible for adhering to the requirements set forth below.


The contractor shall adhere to all NS/EP requirements, as specified in Section C.5, pertaining to the provision of services and associated features during the period in which services are implemented on its contract.

C.4.4.6 Government Responsibilities During Implementation


For implementation, the CO will issue the contractor a letter of agency if required as specified in Section G.8. The letter of agency may include the authority to arrange for disconnection of service.


The functions to be performed by the Government and/or its representatives regarding to implementation activities will include the following actions:

(a) As required, reviewing and recommending approval or rejection of all plans related implementation activities.

(b) Approving the number of locations by service type to be implemented per phase of implementation activities.

(c) Ensuring that the contractors provide user training, if required, at locations acquiring service from the contractor.

(d) Reviewing test results as required (Section E).

(e) Assisting in resolving any conflicts with the incumbent service providers and other contractors during the implementation of services to the contractor’s network.

(f) Overall program management and implementation responsibility.

C-312




The Government will identify the LGC for each location within 30 calendar days after notice to proceed with implementation. The LGCs will be responsible for coordinating all implementation planning and other activities through, at least, the acceptance of all implemented services at the location(s) for which they are responsible. The LGC may or may not actually be located at the location(s) acquiring service from the contractor. If the identities of the LGCs are required for any of the plans associated with transition activities and if the identities have not been made known to the contractor prior to the submission of those plans to the Government, the Government will not hold the contractor responsible for the lack of LGC identities in the plans. The contractor shall indicate in any of the plans which require the LGC identities that the identities will be supplied by the Government and that the contractor shall include the identities in any subsequent submission(s) of the plans.

The responsibilities of the LGCs include but are not limited to, the following:

(a) Serve as the Government’s local central point of contact for a location’s Government-related implementation planning and coordination activities.


(c) Assist the contractor in ascertaining from the other contractors the type of equipment that is required to support the type and quantity of the contractor’s service(s) to be installed.

(d) Upon receipt of information from the FTS2001 contractor regarding the implementation date and location requirements, coordinate with the appropriate other contractor(s) who are providing that location with telephone switching (i.e., whether PBX or Centrex) and other telecommunications facilities.

C-313



(f) If desired by the LGC or associated agency, monitor and testing on site as performed by the contractor. Accept or reject service in accordance with the contract. Notify the ICC whether the service is acceptable following acceptance testing.

C.5 NATIONAL SECURITY AND EMERGENCY PREPAREDNESS

C.5.1 Introduction

Telecommunications requirements for NS/EP are based on a set of telecommunications policies and procedures established by the National Communications System (NCS) in accordance with Executive Order 12472, developed to ensure critical Government and industry needs are met when an actual or potential emergency threatens the security or socio-economic structure of the U.S.

A national emergency is any circumstance or crisis (local, national, or international) that causes, or could cause, injury or harm to the population, damage to or loss of property, or that degrades or threatens the NS/EP posture of the U.S. under conditions of natural and man-made disasters and emergencies. Within the context of telecommunications services, emergency preparedness is the maintenance of a telecommunications capability that is in a state of readiness to meet the needs of Government (state, local, tribal, and Federal) during national emergencies. To meet these NS/EP telecommunications requirements the NCS has implemented the Government Emergency Telecommunications Service (GETS). As an extremely important telecommunications asset of the Government, FTS2001 is required to support GETS. Furthermore, because FTS2001 service extends into thousands of Government offices throughout the country, the FTS2001 networks represent a key resource for coping with emergency and disaster situations, and the FTS2001 networks are required to be maintained in a state of readiness for any emergencies. Detailed requirements are given in the following sections.

Service capabilities specified here are not intended to replace capabilities provided under GETS or any other Government contracts but rather to assure that FTS2001 contract services, as a result of the networks’ characteristics and the use of prudent emergency contingency planning, provide FTS2001 users availability and reliability during emergencies that is comparable to the service provided during normal conditions.

C-314


The following definitions are used in this section:

The term contractor’s FTS2001 network includes all infrastructure, SDP to SDP, used by the contractor to provide FTS2001 services, whether or not that infrastructure is owned by the contractor, but excluding the access portions of an end-to-end circuit when circuit-switched access is used.

Critical users of telecommunications are key Government officials whose position requires special access and network treatment to assure telecommunications services during emergencies. During an emergency, critical users at Federal agencies generally interact with the management of critical industries, other Federal agencies, and state, local, and tribal Governments, on both an individual and regional basis, for developing emergency response options. It is estimated that the number of FTS2001 critical users will not exceed 10,000, and for the purposes of traffic analyses it may be assumed that they are distributed uniformly among the population that utilizes SVS.

The list of FTS2001 critical users is independent of the list of GETS users, which is maintained by the NCS, although the lists may overlap. Services provided to GETS users will have priority over all other FTS2001 services.

C.5.2 NS/EP Capabilities for Voice Services

The contractor shall support the following FTS2001 NS/EP capabilities for providing SVS (see Section C.2.2.1) during emergencies:

(a) Authorized access(b) Priority treatment(c) Enhanced routing(d) Non-domestic connectivity(e) Interoperability with other networks(f) Switching and Signaling augmentation and restoration(g) Protection of classified and sensitive information(h) Assured service

The requirements for these NS/EP capabilities are described in more detail below.

C-315


C.5.2.1 Authorized Access

The contractor shall provide capability that will allow FTS2001 critical users priority access to services. Each critical user, or a group of users, shall be provided with a unique authorization code (Section C.2.2.1.2.1) that can be used to access the services.

An FTS2001 critical user shall have the capability of automatic authorization by assigned COS (derived, for example, from access-circuit line-marking, traveling class-mark, ANI or other means). The FTS2001 critical users shall be provided an authorization code that shall override an existing station/line authorization (i.e., COS). The services shall be provided to critical users after proper authorization. The same procedure shall also be used to allow critical users to gain access from stations that are not pre-subscribed to FTS2001 by utilizing SVS switched access capability.

Once the authorization code is validated, the call shall be processed. If the authorization code is not valid (for example, if entered incorrectly), the caller shall be prompted to reenter the authorization code. If the authorization code, after three attempts, is again determined to be invalid, the call shall be disconnected.

If the automated access authorization system fails, the call shall be processed through a network operator and shall be allowed to complete with proper authorization.

C.5.2.2 Priority Treatment

FTS2001 critical users’ origination and termination traffic shall receive priority treatment over normal traffic through the use of:

(a) Control mechanisms, such as trunk queuing, trunk subgrouping, or trunk reservation.

(b) Exemption from restrictive network management controls that are used to reduce network congestion.

(c) Operator assistance to achieve preferential treatment, such as interrupting an ongoing call.

C-316


C.5.2.3 Enhanced Routing

Enhanced routing for FTS2001 critical users (e.g., routing calls around congestion or around failure of switching or transmission element in the contractor’s network) shall be used to improve performance and the capability of the contractor’s FTS2001 network to meet NS/EP objectives.

C.5.2.4 Non-Domestic Connectivity

Non-domestic outgoing calling capability during an emergency shall be provided for FTS2001 critical users after proper authorization (as specified in Section C.5.2.1). Non-domestic incoming calls from FTS2001 critical users (as identified either from traveling class-mark or from authorization code) shall be routed to the access authorization system for proper authorization (as specified in Section C.5.2.1) and then to the destination. The contractor shall additionally provide operator assistance for priority call handling.

C.5.2.5 Interoperability With Other Networks

FTS2001 shall recognize the GETS Universal Access Number, 710-NCS-GETS (710-627-4387), and shall pass GETS calls to the Public Switched Network for subsequent priority call processing. After contract award, the FTS2001 contractors shall participate, upon Government request and on an individual case basis, in studies to determine appropriate ways in which FTS2001 network assets, and especially the many FTS2001 dedicated access lines, may be used to support GETS.

When FTS2001 critical users’ calls can not be completed using the contractor’s FTS2001 network, whether because of equipment outages or traffic congestion, the contractor shall support such calls using other networks as follows:

(a) If there is a second FTS2001 contractor, critical users’ calls shall be routed to its network. This requirement is expected to necessitate post-award study and agreements for special arrangements.

(b) Critical users’ calls that do not complete using any FTS2001 contractor’s network shall be routed to the PSN at an appropriate point. When it becomes possible to do so without causing GETS interference, functionality such as that provided by High Probability of Completion (HPC) shall be utilized. (HPC is defined in ANSI Standard T1.631, SS7-HPC Network Capability, and is being further developed in ongoing Bellcore activities.)

C-317


If requested, the contractor shall support interoperability with other Government networks on an individual case basis.

C.5.2.6 Protection of Classified and Sensitive Information

The contractor shall follow best commercial practices to protect its computer systems with regard to NS/EP-related sensitive systems. These sensitive systems include, but are not limited to, databases for classified information; critical users’ locations, identifications, authorization codes, and call records; customer profiles; and, computer systems that control or can control the network or services. In addition, the contractor will be provided access to certain classified and sensitive materials required for the planning, management, and operations for NS/EP. That information will be in various forms, including hardcopy and electronic media. It will be identified as to its classification and shall be protected by the contractor in accordance with applicable industrial security regulations (National Industrial Security Program Operating Manual [NISPOM] for Safeguarding Classified Information). The level of classification will be up to and including Top Secret, and will be identified by the Government. The contractor shall protect unclassified sensitive information with the same level of protection required of For Official Use Only information as defined by industrial security regulations.

C.5.2.7 Assured Service

The contractor shall provide technical systems and administrative, management, and operational plans that assure the contractual Grade of Service (GOS) to all FTS2001 users will be maintained during periods when the PSN in the U.S. is in severe overload. In addition, FTS2001 critical users shall experience two percent or less blocking for access and one-half percent or less blocking for transport under PSN overload conditions. These requirements assume that the contractor’s FTS2001 network is not damaged; it is understood that appropriate adjustments in the requirements must be made in areas where damage has occurred.

With the exception of the network switch or switches serving Washington, DC, the loss of a single switch shall not result in a disruption of more than 15 percent of network traffic. Because of the high concentration of traffic in and out of the Washington, DC, area, the contractor shall use at least two network switches to serve the Washington, DC, area.

The contractor shall annually update its service assurance plans included with its proposal and shall provide the updated plans to the PMO. Refer to Section C.3.2.7 for the media of delivery and to Section F for other deliverable requirements.

C-318


C.5.3 NS/EP Capabilities for Data Services

C.5.3.1 NS/EP Capabilities for Circuit Switched Data Service

The following capabilities shall be supported for CSDS (i.e., CSDS at DS0 and N x DS0 (where N = 2/6/12) data rates [see Section C.2.2.2]) during emergency conditions for FTS2001 critical users:

(a) Interoperability

(1) Interoperate with domestic and non-domestic public switched networks to the extent possible.

(b) Security

(1) Support “denial-of-service” protection for domestic and non-domestic traffic as specified in Section C.2.1.12.2 consistent with best commercial practices.

(2) Ensure authorized access (as specified in Section C.5.2.1).

(3) Transport Government encrypted traffic of various security classifications.

C.5.3.2 NS/EP Capabilities for Switched Data Services

The following capabilities shall be supported for PSS (Section C.2.3.1) and IPS (Section C.2.3.3) during emergency conditions for FTS2001 critical users:

(a) Interoperability

(1) IPS shall interoperate with domestic and non-domestic public switched IP networks to the extent possible.

(2) Support Internet addressing plan (as specified in Section C.2.3.3.1).

(3) Interface with the Internet.

(b) Assured Service

(1) Priority traffic handling when available commercially.

(c) Security

C-319


(1) Support denial-of-service protection for domestic and non-domestic traffic consistent with best commercial practices.

(2) Ensure authorized access (as specified in Section C.5.2.1).

(3) Transport Government encrypted traffic of various security classifications.

(d) Survivability

(1) Provide diverse routing and robustness in the backbone.

(2) Support routing via Internet if the contractor’s FTS2001 network is unable to handle traffic demands.

C.5.4 NS/EP Capabilities for Network Facilities and Infrastructure

C.5.4.1 Network Facility Augmentation and Restoration

The contractor shall utilize the following means, at a minimum, to provide network facility augmentation and restoration during times of stress:

(a) National Telecommunications Management Structure (NTMS) and TSP or any subsequent TSP replacement system (see C.5.4.2) for providing network management, provisioning, and restoration.

(b) Reserve and emergency power as per best commercial practices and use of Telecommunications Electric Service Priority (TESP) in all transmission, switching, signaling, and major facility nodes.

C.5.4.1.1 Transmission Facilities

The contractor shall utilize one or more of the following means, at a minimum, to provide transmission augmentation and restoration during times of stress:

(a) Commercial satellite service, including reserved transponder capacity and/or VSAT, for providing transmission augmentation and restoration. Such satellite links shall be encrypted. New and emerging satellite resources may also be utilized if deemed applicable and prudent.

C-320


(b) Commercial networks for providing transmission augmentation using terrestrial, fiber optic, microwave, and transportable capabilities.

(c) Rapid restoration of network transmission facilities by deployment of such techniques as SONET self-healing architecture.

C.5.4.1.2 Switching and Signaling Augmentation and Restoration

The contractor shall follow best commercial practices to protect against the loss of services caused by the failure, blockage, or damage of a switching or signaling node.

C.5.4.2 Telecommunication Service Priority

The TSP System (NCS-3-1-2 and NCS-3-1-3) provides a framework for telecommunications services vendors to initiate, restore, or otherwise act on a priority basis to ensure effective NS/EP telecommunication services. The TSP System applies to common carriers, to Government, and to private systems that interconnect with commercially provided services or facilities. The TSP System is intended to apply to all aspects of end-to-end NS/EP telecommunication services. The TSP system allows five levels of priorities for restoration and provisioning.

The contractor shall fully comply with the TSP system for priority provisioning (i.e., installation of new circuits), restoration of previously provisioned circuits, and priority level for design change of circuits, including coordination with local access providers. The contractor shall also fully comply with any future TSP replacement system.

Should the contractor’s network experience significant degradation or failure, the contractor shall provide priority restoration of affected FTS2001 services in accordance with the TSP system five levels of priorities.

C.5.5 Signaling System

Common channel signaling (ITU-TSS No. 7 or SS7) paths shall be protected. This protection shall not preclude the use of encryption equipment endorsed under the National Security Agency (NSA) Commercial COMSEC Endorsement Program (CCEP) or any other National Institute of Standards and Technology (NIST)/NSA approved encrypted/non-encrypted forms of protection.

C-321


C.5.6 Satellite Communications Command Link Protection

If satellite communications are used in providing any services, the contractor shall encrypt the command and control link to any satellite launched after June 17, 1990, (in accordance with the National Telecommunications Interagency Security Subcommittee, No. 1). However, if there are other measures available that can mitigate command-link takeover, they shall be utilized wherever economical and approved on a prior basis by the Government.

C.5.7 NS/EP Interface with the Contractor

The contractor shall provide an NS/EP liaison officer, cleared at the Top Secret level, to meet with the Government whenever required by the PMO. The purpose of the liaison presence is to provide a means of discussing classified requirements or problems with the contractor at the planning and operational level, for crisis or emergency situations. Therefore, the liaison officer shall be familiar with the general and technical management organization of the contractor and have established channels for initiating necessary actions and obtaining necessary decisions.

The liaison officer or his fully-qualified alternate shall be on site at the PMO, expeditiously but in any event no later than four hours after receiving, notice of an emergency. In an extended emergency, this presence may be required on an extended basis. This requirement shall also apply to any contractor personnel designated after contract award if deemed necessary by the Government.

C.5.8 Contractor’s Emergency Management

The contractor shall notify the PMO immediately when event(s) arise that may have major consequences on its network. The PMO will set priorities. However, the contractor shall be solely responsible for network operations. The contractor shall update and provide the emergency management plans that were included in its proposal to the Government annually for emergency management actions affecting the contractor’s network based on the critical users’ requirements for service to continue during emergencies. Refer to Section C.3.2.7 for the media of delivery and Section F for other deliverable requirements.

The emergency management capability will be activated at the discretion of the PMO. Communication requirements from the contractor’s network control center(s) to NCS locations or other critical Government locations during an emergency will be defined after contract award during transition planning.

C-322


The contractor’s network management system design shall provide features that will make real-time network monitoring resistant to failure and avoid the possibility of a single point of failure impacting the entire network management function. If the network management does fail, the contractor shall continue to supply telecommunications services without interruption or impairment. In addition, the contractor’s network management system shall continue to provide network management functions during emergency periods or periods of severe overload conditions.

C.5.9 Readiness of NS/EP Capabilities

The contractor’s NS/EP capabilities shall be maintained in a constant state of readiness for any emergency.

The contractor shall demonstrate NS/EP capabilities as and when requested by the Government on an individual case basis.

C.6 PERFORMANCE DATA REPORTING REQUIREMENTS

The contractor shall deliver the performance-related statistical reports described in this section to the PMO and agencies. These statistical reports include data related to the performance requirements specifically identified in Section C. Section C.6.1 describes general performance data reporting requirements that are common to all telecommunications services furnished by the contractor. Section C.6.2 describes the specific periodic performance data reporting requirements that are unique to each type of service. Section C.6.3 describes the daily performance data reporting requirements. The format of all performance reports shall be consistent with the contractor’s existing practice using guidance in the IEG Section B.5. Refer to Section C.3.2.7 for the media of delivery and Section F for other deliverable requirements.

The contractor shall provide all required monthly performance data reports to the PMO and to subscribing agencies on or before the 15th Government business day of the month following the reporting interval. If requested by the PMO or requested by subscribing agencies the contractor shall provide any of the reports listed in Section C.6 in printed format within five business days from when the report was due electronically. The contractor shall provide the daily morning report electronically to the PMO and to those agencies subscribing to it by 0800 local time each Government business day. In addition, the contractor at the request of the PMO or subscribing agencies, shall provide special reports on a case by case basis as negotiated with the Government. Refer to Section C.3.2.7 for the media of delivery of these special reports and Section F for other deliverable requirements.

C-323


In agency or sub-agency specific reports, the contractor shall include only information relating to that agency’s services.

The contractor shall archive these reports for three years after maintaining the reports on-line for 60 calendar days. The contractor shall make the archived reports available to the PMO or requesting agencies within 96 hours after the request is made. Refer to Section C.3.2.7 for the media of delivery and Section F for other deliverable requirements.

The Government desires to receive the reports in the format specified in the IEG Section B.5.5. Unless otherwise indicated, monthly reports shall present the required performance data for the previous calendar month together with the associated data for each of the preceding eleven months. Each daily report shall present the required performance data for the previous Government business day and any intervening Federal holidays and weekends.

Unless otherwise indicated in the following descriptions, the contractor shall report the performance statistics at the program aggregate level for each specific service. The contractor, if requested by the PMO or a subscribing agency, shall provide all or any part of the listed performance data on an agency-specific basis. Refer to Section C.3.2.7 for the media of delivery and Section F for other deliverable requirements. The performance reports listed in Sections C.6.1, C.6.2, and C.6.3 and their associated data elements listed in the IEG shall be augmented by the contractor in the future to cover changes in services and any additional services that become available under the contract.

Within the first 24 months after the initial generation of each report, the Government may specify, and the contractor shall incorporate, additional data elements for the report provided that these data elements are within the overall intent of the report. The cost for reporting the additional data elements will be negotiated on a case-by-case basis.

The methods specified herein to compute performance parameters for the reports of Section C.6 shall be used by the contractor to compute the same performance parameters for the same services that are specified in Section C.2.

C.6.1 General Performance Data Reporting Requirements

The contractor shall provide the following performance-related reports. Unless otherwise indicated in the following descriptions, the reports shall be provided monthly, and the contractor shall report these statistics for each service delivered as described in Section C.2. The detailed data elements and required calculations for each report are described in the IEG as referenced.

C-324


C.6.1.1 Status of Network Fraud and Security Breach Detections Report

The contractor shall report all contract network fraud and security breach attempts detected (Section C.3.7.5) and the status of associated investigations and resolutions. The report shall include the data elements listed in IEG Section B.5.5.1.

C.6.1.2 Reserved

C.6.1.3 Service Order Completion Status Report

The contractor shall report on service orders, by type of order (i.e., initiation, addition, change, and termination) and by order interval type (standard and expedited) that had completion due dates falling within the reporting period. The report shall include the data elements listed in IEG Section B.5.5.3.

C.6.1.4 Trouble Reports Status Report

The contractor shall report on trouble reports by service and by cause for transport, access, and contractor-provided customer premises equipment. The report shall include the data elements listed in IEG Section B.5.5.4.

C.6.1.5 Monthly Dispute Databases and Reports

C.6.1.5.1 Program Management Office Monthly Dispute Database and Report

The contractor shall deliver one copy of its Monthly Dispute Database to the PMO by the 5th business day of the month following close of the billing report period for each service and a Dispute Report by the 15th business day. The Dispute Report shall identify all dispute activities for centralized and directly billed accounts in the reporting period for that service and show the balance forward data at the beginning and end the reporting period. The report shall include the data elements listed in IEG Section B.5.5.5.1.

C.6.1.5.2 Direct Billed Agency Monthly Dispute Database and Report

The contractor shall provide one copy of its Monthly Dispute Database to each agency or sub-agency being invoiced directly by the 5th business day of the month following close of the billing report period for each service and a Dispute Report by the 15th business day. The Dispute Report shall identify all dispute activities for directly billed accounts in the reporting

C-325


period for that service and show the balance forward data at the beginning and end the reporting period. The report shall include the data elements listed in IEG Section B.5.5.5.2. Information in the report shall be limited to only the agency for which the report is generated.

C.6.1.6 Contractor Adjustment Reports

C.6.1.6.1 Monthly Adjustment Database(s) and Reports

C.6.1.6.1.1 Program Management Office Monthly Adjustment Database and Report

By the 5th business day of the month following the close of the billing period for each service, the contractor shall deliver one copy of the Adjustment database to the PMO for all agencies receiving centralized and direct billing. By the 15th business day of the month following close of the billing report period for each service, the contractor shall deliver one copy of a Monthly Adjustment Report to the PMO for all agencies receiving centralized and direct billing. The report shall include the data elements listed in IEG Section B.5.5.6.1.1.

C.6.1.6.1.2 Direct Billed Agency Monthly Adjustment Database and Report

By the 5th business day of the month following the close of the billing period for each service, the contractor shall deliver one copy of the Adjustment database to the each agency or sub-agency receiving direct billing. By the 15th business day of the month following close of the billing report period for each service, the contractor shall deliver one copy of a Monthly Adjustment Report to each agency or sub-agency receiving direct billing. The report shall include the data elements listed in IEG Section B.5.5.6.1.2. Information in the report shall be limited to only the agency for which the report is generated.

C.6.1.6.2 Service Outage Credit Reports

C.6.1.6.2.1 Program Management Office Service Outage Credit Report

The contractor shall deliver one copy of a Service Outage Credit Report to the PMO for all agencies receiving centralized and direct billing by the 15th business day of the month following close of the billing report period for each service. The report shall include the data elements listed in IEG Section B.5.5.6.2.1.

C-326


C.6.1.6.2.2 Direct Billed Agency Service Outage Credit Report

The contractor shall deliver one copy of a Service Outage Credit Report to the agency or sub-agency using direct billing by the 15th business day of the month following close of the billing report period for each service. The report shall include the data elements listed in IEG Section B.5.5.6.2.2. Information in the report shall be limited to only the agency for which the report is generated.

C.6.1.7 Reserved

C.6.1.8 User Forum Issues Report

The contractor shall report quarterly on issues which were identified at User Forums. The report shall include the data elements listed in IEG Section B.5.5.8.

C.6.1.9 Contract Modification Status Report

The contractor shall report the status of the contract modifications that were in process during the reporting interval. The report shall include the data elements listed in IEG Section B.5.5.9.

C.6.1.10 Service Trial Status Report

The contractor shall provide the PMO a summary report of the status of all on-going service trials. The report shall include the data elements listed in IEG Section B.5.5.10.

C.6.1.11 Reserved

C.6.1.12 Network Cost Minimization Opportunities Report

The contractor shall provide the PMO and the affected agencies with a semi-annual (March and September) Network Cost Minimization Opportunities Report that describes service optimization and aggregation opportunities, with associated potential cost savings, that the contractor proposes for FTS2001 contracted network locations. The report shall include the data elements listed in IEG Section B.5.5.12. The report shall apply only to those services the contractor provides at a location.

C-327


C.6.1.13 Percentage Service Restoral Time Report

C.6.1.13.1 Reserved

C.6.1.13.2 Service Assurance Service Restoral Time Report

The contractor shall provide the PMO a report on the time to restore DTS service supplied under the Service Assurance feature. The report shall include the data elements listed in IEG Section B.5.5.13.2

C.6.2 Service-Specific Monthly Performance Reports

The contractor shall provide in its monthly report the following specific performance-related reports for each service being delivered under the contract as described in Section C.2.

C.6.2.1 Circuit Switched Services

C.6.2.1.1 Circuit Switched Services Percent Availability

C.6.2.1.1.1 Access Segment

The contractor shall report on availability for each type of circuit switched service. The report shall include the data elements listed in IEG Section B.5.6.1.1.1.

C.6.2.1.1.2 Transport Segment

The contractor shall report on availability for each type of circuit switched service. The report shall include the data elements listed in IEG Section B.5.6.1.1.2.

C.6.2.1.2 Circuit Switched Service Busy Hour Grade of Service for Blockage


The contractor shall report on monthly GOS for each type of CSS. The report shall include the data elements listed in IEG Section B.5.6.1.2.1.


The contractor shall report on the monthly GOS for each type of CSS. The report shall include the data elements listed in IEG Section B.5.6.1.2.2.

C.6.2.1.3 Audio Teleconference Summary

C-328


The contractor shall report on audio teleconferences during the reporting month. The report shall include the data elements listed in IEG Section B.5.6.1.3.

C.6.2.1.4 Fraud Prevention Performance Measurements

The contractor shall provide monthly statistics regarding its efforts concerning fraud detection and prevention. The report shall include the data elements listed in IEG Section B.5.6.1.4.

C.6.2.1.5 Operator Services

The contractor shall report on operator services by type of service. The report shall include the data elements listed in IEG Section B.5.6.1.5.

C.6.2.1.6 Circuit Switched Service Trouble Reports

The contractor shall report on troubles for each type of circuit switched service available under the contract. The report shall include the data elements listed in IEG Section B.5.6.1.6.

C.6.2.2 Switched Data Services

C.6.2.2.1 Switched Data Services Percent Availability


The contractor shall report on availability for each type of switched data service. The report shall include the data elements listed in IEG Section B.5.6.2.1.1.


The contractor shall report on availability for each type of switched data service. The report shall include the data elements listed in IEG Section B.5.6.2.1.2.

C-329


C.6.2.2.2 Switched Data Services Transmission Performance


The contractor shall report on monthly transmission performance for each type of SDS. For transmission performance requirements see Sections C.2.3.1.1.3 for PSS, C.2.3.2.1.3 for FRS, C.2.3.3.1.3 for IPS, and C.2.3.4.1.3 for ATMS. The report shall include the data elements listed in IEG Section B.5.6.2.2.1.


The contractor shall report on transmission performance for each type of SDS. For transmission performance requirements see Sections C.2.3.1.2.3 for PSS, C.2.3.2.2.3 for FRS, C.2.3.3.2.3 for IPS, and C.2.3.4.2.3 for ATMS. The report shall include the data elements listed in IEG Section B.5.6.2.2.2.

C.6.2.3 Dedicated Transmission Service

C.6.2.3.1 Dedicated Transmission Service Availability for Access and Transport Segments

The contractor shall report on all DTS circuits that fail to meet the availability requirements for each category of DTS circuit. The report shall include the data elements listed in IEG Section B.5.6.3.1.

C.6.2.4 Video Teleconferencing Service

The contractor shall report on the availability of the Video Teleconferencing Service as specified in IEG Section B.5.6.6.2.

The contractor shall also provide monthly performance reports as specified in Section C.2.7.4.

C-330


C.6.2.5 Reserved

C.6.2.6 Reserved

C.6.2.7 Reserved

C.6.3 Daily Performance Data Requirements

C.6.3.1 Daily Status Morning Report

Each Government business day, the contractor shall provide a “morning report” containing the data elements listed in IEG Section B.5.7.1.

Following contract award, the Government will advise the contractor which locations the Government considers to be critical locations.

The contractor shall provide the morning report using the electronic access arrangement specified in Section C.3.7.1.1. This report shall contain all reportable incidents occurring since publication of the previous report.

C.6.4 General Services Administration Management Services Fee Performance Data Requirements

C.6.4.1 General Services Administration Management Services Fee Collection Report

The contractor shall provide the PMO with a monthly GSA Management Services Fee Collection Report for direct and centralized billing agencies that contains the data elements listed in IEG Section B.5.8.1.

C-331

section c - cell phones, mobile phones & wireless … · web viewvincent and the grenadines...

Documents