4 · web viewcross reference matrix table j.9.1. technical volume part c.2.1 rfp section statement...

Cross Reference Matrix

Table J.9.1. Technical Volume Part C.2.1

RFP Section Statement of Requirement Proposal

Reference Comply Exception

C.1.2 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.

Management Volume

Yes

C.1.4 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.

Management Volume

Yes

C.2.1.1(a) The contractor shall provide Telecommunications Services. These services will be used for communications between users.

B

1.1

Yes

C.2.1.1(b) The contractor shall provide 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.

B

1.1

Yes

C.2.1.1(b) The contractor shall provide 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.

B

1.1

Yes

C.2.1.1(c) The contractor shall provide 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.

B

1.1

Yes

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

B

1.1

Yes

C.2.1.1.1 As used in this RFP/contract, the term “Mandatory” identifies core items that must be offered.

B

1.1.1

Yes

C.2.1.1.1 The contractor is not permitted to provide prices for B Yes

Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposal. 1-Cross-Ref-1Revised November 30, 1998




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.

1.1.1

C.2.1.1.1 Each mandatory item shall meet or exceed the associated performance requirements as specified in this RFP.

B

1.1.1

Yes

C.2.1.1.1 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.2.1.1.1.1(a) The contractor shall offer and provide the following Circuit Switched Services, throughout the life of the contract 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)

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

1.1.1.1

Yes

C.2.1.1.1.1(b) The contractor shall offer and provide the following Switched Data Services (SDS), throughout the life of the contract 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)

B

1.1.1.1

Yes

C.2.1.1.1.1(c) The contractor shall offer and provide Dedicated Transmission Services (DTS), throughout the life of

B Yes





the contract in which communications circuits are allocated to one user or a group of users.

1.1.1.1

C.2.1.1.1.1(d) The contractor shall offer and provide Video Teleconferencing Service (VTS), which is a value added service, throughout the life of the.

B

1.1.1.1

Yes

C.2.1.1.1.1 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 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.

B

1.1.1.1

Yes

C.2.1.1.2 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.

B

1.1.2

Yes

C.2.1.1.2 After award, the contractor shall update the security plan that was submitted with its proposal, and perform the risk analyses described in the plan.

B

1.1.2

Yes

C.2.1.1.2 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.

B

1.1.2

Yes

C.2.1.1.2 The risk analyses shall identify all risks, including identification of critical risks.

B

1.1.2

Yes

C.2.1.1.2 The risk analyses shall include identification of measures to ameliorate risks.

B

1.1.2

Yes

C.2.1.1.2 The risk analysis results must be approved by the B Yes





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.

1.1.2

C.2.1.1.2(a) In order to support the Government security needs, the contractor shall provide - Basic security of contractor infrastructure (see Section C.2.1.12)

B

1.1.2

Yes

C.2.1.1.2(b)(1) In order to support the Government security needs, the contractor shall provide Fee-based security services - Protection of airwave propagation or wireline assurance.

B

1.1.2

Yes

C.2.1.1.2(b)(1) 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.

B

1.1.2

Yes

C.2.1.1.2(b)(2) In order to support the Government security needs, the contractor shall provide Fee-based security services - other features, as required by the user. The cost of these features shall be negotiated on an individual case basis.

B

1.1.2

Yes

C.2.1.1.3 The contractor shall support a multitiered (i.e., contractor, GSA oversight, and agency) management approach and a centralized contractual and system/operations management capability.

B

1.1.3

Yes

C.2.1.1.3 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.

B

1.1.3

Yes

C.2.1.1.3 This capability shall also enable agencies to manage the operation of their service environment effectively.

B

1.1.3

Yes





C.2.1.1.3 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.

B

1.1.3

Yes

C.2.1.1.3 The overall objective shall be to provide near real-time telecommunications management information efficiently and cost-effectively, Government-wide and agency-specific.

B

1.1.3

Yes

C.2.1.1.3 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.

B

1.1.3

Yes

C.2.1.1.3 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.

B

1.1.3

Yes

C.2.1.1.3 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.

B

1.1.3

Yes

C.2.1.1.3 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.

B

1.1.3

Yes

C.2.1.1.3 The contractor shall deliver service in the most cost effective and resource efficient fashion possible.

B

1.1.3

Yes

C.2.1.1.3 The contractor shall identify to the Government redundancies, under-utilized circuits, and other network management issues.

B

1.1.3

Yes

C.2.1.1.4 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.

B

1.1.4

Yes





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 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 (i.e., shall) 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.2 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.

B

1.1.4

Yes

C.2.1.2 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 after contract award and continually update the availability dates for features as a function of NPA/NXX. 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).

B

1.1.4

Yes

C.2.1.2 The contractor shall complete the right-most column of Table C.2.1.2-2 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).

B

1.1.4

Yes

C.2.1.2 The contractor shall complete the right-most column of Table C.2.1.2-3 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

B

1.1.4

Yes





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

C.2.1.2 The contractor shall complete the right-most column of Table C.2.1.2-4 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).

B

1.1.4

Yes

C.2.1.2 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.

B

1.1.4

Yes

C.2.1.2 As a consequence of such changes, the contractor shall also update Tables C.2.1.2-3 and C.2.1.2-4.

B

1.1.4

Yes

C.2.1.3 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.

B

1.3

Yes

C.2.1.3 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.

B

1.3

Yes

C.2.1.4(a) The contractor shall provide services to On-net locations - 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

1.4

Yes

C.2.1.4(b) The contractor shall provide services to Off-net locations - locations that 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.

B

1.4

Yes





C.2.1.5(b) Where local access-to-network interface (LANI) is used and the Government provides access, the SDP shall be at the standard carrier demarcation point at the contractor’s POP.

B

1.5

Yes

C.2.1.5.1 The contractor is responsible for (i.e., shall) delivering service to the SDP. The physical location of SDPs will be determined by the Government on an order by order basis. 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]).

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

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

B

1.5

Yes Amend. 5 deleted some of these reqmts.

C.2.1.5.2 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).

B

1.5.2

Yes

C.2.1.5.2 For non-domestic locations, the contractor shall follow country-specific applicable wiring/cabling standards and guidelines.

B

1.5.2

Yes

1 Connection from POP to POP.





C.2.1.5.2 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.

B

1.5.2

Yes

C.2.1.5.2 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.

B

1.5.2

Yes

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

B

1.5.2

Yes

C.2.1.5.2 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 the 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.

B

1.5.2

Yes

C.2.1.6 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) 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 services or the service-specific numbering and addressing plan supported for that service at the time of contract award.

B

1.6

Yes





C.2.1.6 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.

B

1.6

Yes

C.2.1.6 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.

B

1.6

Yes

C.2.1.6 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).

B

1.6

Yes

C.2.1.7 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.

B

1.7

Yes

C.2.1.7 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.

B

1.7

Yes

C.2.1.7 Where multiple standards are cited, the order of precedence shall be industry forum specification (e.g., ATMF), followed by ANSI, followed by Bellcore, followed by ITU-TSS, unless otherwise specified.

B

1.7

Yes

C.2.1.8 The contractor shall be responsible for all aspects of service quality, security, interconnectivity, 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

B

1.8

Yes





parameter is defined in terms of the minimum acceptable level of performance for the service or feature.

C.2.1.8 The performance provided shall always be at a level not less than what is available commercially.

B

1.8

Yes

C.2.1.8 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.

B

1.8

Yes

C.2.1.8 The contractor shall be responsible for delivering all services at the required performance levels as specified in this solicitation.

B

1.8

Yes

C.2.1.8 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.

B

1.8

Yes

C.2.1.8 The contractor shall meet the specified performance regardless of traffic congestion in the contractor’s commercial or other private networks.

B

1.8

Yes

C.2.1.9 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.

B

1.9

Yes

C.2.1.9 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.

B

1.9

Yes

C.2.1.9 To resolve any interoperability problems, the contractor 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

B

1.9

Yes





Government will be responsible for costs associated with equipping or modifying its switches to accomplish call routing to the contractor's network.

C.2.1.9 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.

B

1.9

Yes

C.2.1.9 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.

B

1.9

Yes

C.2.1.9 The contractor shall be responsible for 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.

B

1.9

Yes

C.2.1.10 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.

B

1.10

Yes

C.2.1.10 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.

B

1.10

Yes

C.2.1.10 The contractor shall submit Station Identified Call Detail record information - Centralized Billing to the PMO on a monthly basis or when requested.

B

1.10

Yes

C.2.1.10 The contractor shall also submit Station Identified Call Detail record information - Direct Billing to the agencies or sub-agencies monthly or as requested.

B

1.10

Yes

C.2.1.10 Switched voice station identification may be provided by Automatic Identification of Outward Dialing (AIOD), Automatic Number Identification (ANI)

B

1.10

Yes





(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 CDR purposes. As used in this contract, the term ANI includes all above-mentioned methods of voice station identification.

C.2.1.10 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.

B

1.10

Yes

C.2.1.10 Suppression of calling number delivery shall be provided as specified in Section C.2.2.1.2.2.1(g).

B

1.10

Yes

C.2.1.10 The contractor shall coordinate with law enforcement officials having appropriate authorization for obtaining call trace information and provide them with required information.

B

1.10

Yes

C.2.1.11 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.

B

1.11

Yes

C.2.1.11 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.

B

1.11

Yes

C.2.1.11 The contractor shall notify the Government of the details of the level of interoperability available for the service

B

1.11

Yes





C.2.1.11 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.

B

1.11

Yes

C.2.1.11 The contractor shall provide interoperability of its SVS, Toll Free Service, and 900 Service with the Public Switched Telephone Network (PSTN).

B

1.11

Yes

C.2.1.11 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)

B

1.11

Yes

C.2.1.11 The contractor shall coordinate with the Federal Networking Council for interconnection standards.

B

1.11

Yes

C.2.1.11 If a user wants interoperability for any other FTS2001 service(s), the contractor shall provide such interoperability on an individual case basis.

B

1.11

Yes

C.2.1.11 The contractor shall also support interconnection with other Government networks/acquisitions (e.g., city specific MAA) at the contractor’s POP.

B

1.11

Yes

C.2.1.11 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

B

1.11

Yes





plan compatible with the FTS2001 addressing and/or numbering plan.

C.2.1.11 The FTS2001 contractor shall support and work cooperatively with other Government networks/acquisitions

B

1.11

Yes

C.2.1.11 The FTS2001 contractor shall be responsible for all testing, maintenance, outage time, and trouble repair associated with its LANI.

B

1.11

Yes

C.2.1.12 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.

B

1.12

Yes

C.2.1.12 The contractor’s infrastructure shall support best commercial practices against threats from hacker, criminal, and terrorist activities.

B

1.12

Yes

C.2.1.12.1 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.

B

1.12.1

Yes

C.2.1.12.2 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.

B

1.12.2

Yes

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

B

1.12.3

Yes





C.2.1.12.3 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.

B

1.12.3

Yes

C.2.1.12.3 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.

B

1.12.3

Yes

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

B

1.12.4

Yes

C.2.1.12.5 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.

B

1.12.5

Yes

C.2.1.12.6 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 PSN (e.g., maintenance ports).

B

1.12.6

Yes

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

B

1.12.6

Yes

C.2.1.12.7 The contractor shall identify and report all security violations and breaches within four (4) hours.

B

1.12.7

Yes

C.2.1.12.7 The contractor shall be responsible for resolving all security violations and breaches.

B

1.12.7

Yes

C.2.1.12.7 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.

B

1.12.7

Yes

C.2.1.12.7 The contractor shall work closely with agencies to B Yes





resolve all security violations. 1.12.7

C.2.1.12.7 The contractor shall cooperate with the Government in any criminal investigations resulting from a security breach related to the contractor’s network.

B

1.12.7

Yes

C.2.1.12.7 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.

B

1.12.7

Yes

C.2.1.12.7 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.

B

1.12.7

Yes

C.2.1.12.7 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.

B

1.12.7

Yes

C.2.1.12.7 These real-time operational procedures shall be provided within 60 calendar days after contract award with updates as requested by the Government

B

1.12.7

Yes

C.2.1.12.8 The contractor shall provide protection for the databases and information processing systems that are critical for the continuous, reliable operation of its network.

B

1.12.8

Yes

C.2.1.12.8 The contractor shall provide protection against unauthorized access by external communications means, whether from authorized or unauthorized devices such as terminals.

B

1.12.8

Yes

C.2.1.12.8 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.

B

1.12.8

Yes





C.2.1.12.8 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.

B

1.12.8

Yes

C.2.1.12.8 Where these security functions and controls cannot be satisfied, access to these systems will be restricted to small populations of authorized users and protected against unauthorized access.

B

1.12.8

Yes

C.2.1.12.8 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.

B

1.12.8

Yes

C.2.1.12.8 The Government intends to approve a final plan within 30 calendar days of 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.

B

1.12.8

Yes

C.2.1.12.8 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.

B

1.12.8

Yes

C.2.1.12.9 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.

B

1.12.9

Yes

C.2.1.12.9 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

B

1.12.9

Yes





clearances to have access to such information.

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

B

1.12.10

Yes

C.2.1.12.11(a) The contractor shall establish, and provide to the Government security procedures within 60 days after contract award, including procedures for controlling access to Government-related sensitive databases and information.

B

1.12.11

Yes

C.2.1.12.11(b) The contractor shall establish, and provide to the Government security procedures within 60 days after contract award, including procedures to prevent fraudulent use of Government information or services.

B

1.12.11

Yes

C.2.1.12.11(c) The contractor shall establish, and provide to the Government security procedures within 60 days after contract award, including procedures to prevent fraudulent use of FTS2001 Calling Cards.

B

1.12.11

Yes

C.2.1.12.12 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.

B

1.12.12

Yes

C.2.1.12.12 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.

B

1.12.12

Yes

C.2.1.12.12 If these security-related standards are implemented at no additional cost to any commercial customers, then the Government shall receive the same treatment.

B

1.12.12

Yes

C.2.1.12.12 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.

B

1.12.12

Yes

C.2.1.12.12 The contractor shall work with the Government on an ongoing basis to certify and enhance the strength of security.

B

1.12.12

Yes





C.2.1.12.12 The security plan shall describe planned enhancements to security of the network

B

1.12.12

Yes

C.2.1.12.12 The security plan shall be updated annually as a minimum after contract award.

B

1.12.12

Yes

C.2.1.12.12(a) Post award activities shall include, providing the Government with summaries of security related events as described in Section C.6.

B

1.12.12

Yes

C.2.1.12.12(b) Post award activities shall include, 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.

B

1.12.12

Yes

C.2.1.12.12(c) Post award activities shall include, preparation of security practices and briefings for GSA and agency representatives and, upon request, conducting the briefings.

B

1.12.12

Yes

C.2.1.13 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.

B

1.13

Yes

C.2.1.13 The following requirements for numbering plan, features, performance, interfaces, security, and management and operations considerations that are applicable to the non-domestic services shall supersede the corresponding requirements specified for the domestic services:

B

1.13

Yes

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

B

1.13

Yes

C.2.1.13(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.

B

1.13

Yes

C.2.1.13(c) Dial-In: The contractor shall support country-specific non-domestic PSN numbers and/or toll free numbers, if

B Yes





commercially available, for dial-in access of services. 1.13

C.2.1.13(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.

B

1.13

Yes

C.2.1.13(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, unless Government equipment conforms to a North American standard.

B

1.13

Yes

C.2.1.13(e) 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..

B

1.13

Yes

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

B

1.13

Yes

C.2.1.13(f) The contractor shall 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.

B

1.13

Yes

C.2.1.13(f) 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.

B

1.13

Yes

C.2.1.13(f) 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.

B

1.13

Yes





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

B

1.13

Yes

C.2.1.14 Hardware and software, where specified within this contract, shall be provided as an integral part of the services.

B

1.14

Yes

C.2.1.14 Any such hardware and software (excluding data) shall remain the property of the contractor, unless otherwise specified or agreed.

B

1.14

Yes

C.2.1.15 The transition, implementation and migration strategies shall satisfy, at a minimum, the above Government goals and objectives as stated in Section C.4.

B

1.15

Yes

C.2.1.16 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.

B

1.16

Yes

C.2.1.16 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.

B

1.16

Yes

C.2.1.16 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 (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.

B

1.16

Yes

C.2.1.16 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.

B

1.16

Yes





C.2.1.16(a)(1) The contractor shall support Dedicated Access type of 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).

B

1.16

Yes

C.2.1.16(a)(2) The contractor shall support Dedicated Access type of Class 2: Where a user agency orders a service, 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 will revert to Class-1.

B

1.16

Yes

C.2.1.16(b) The contractor shall support 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.

B

1.16

Yes

C.2.1.16 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.

B

1.16

Yes

C.2.1.16 The performance provided for the above access types shall always be within the specification of Section C and at least as good as what is available commercially.

B

1.16

Yes

C.2.1.16 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 necessary, to provide the specified UNI and will authorize the use without charge of a reasonable amount of space and power.

B

1.16

Yes

C.2.1.16(d) The contractor shall also provide all necessary Access Adaptation Functions (AAFs) for 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.,

B

1.16

Yes





T1).

C.2.1.16(e) The contractor shall also provide all necessary Access Adaptation Functions (AAFs) 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.

B

1.16

Yes

C.2.1.16 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.

B

1.16

Yes

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

B

1.16.1

Yes

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

B

1.16.1

Yes

C.2.1.16.1 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, and C.2.2.3. 1 and C.2.2.4.1.

B

1.16.1

Yes

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

B

1.16.1

Yes

C.2.1.16.1 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.

B

1.16.1

Yes

C.2.1.16.2(a)(1) The contractor shall provide Access Route or Path Diversity for connecting an SDP to its associated POP via dedicated access when requested by the Government 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.

B

1.16.2.1

Yes Non Domestic

C.2.1.16.2(a)(1) Diverse routes shall not share any common B Yes Non





telecommunications facilities or offices including common building entrance.

1.16.2.1

Domestic

C.2.1.16.2(a)(1) 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.

B

1.16.2.1

Yes Non Domestic

C.2.1.16.2(a)(1) For cable crossovers, the contractor shall maintain a minimum vertical separation of two feet, with cables encased (separately) in steel or concrete.

B

1.16.2.1

Yes Non Domestic

C.2.1.16.2(a)(1) 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.

B

1.16.2.1

Yes

C.2.1.16.2(a)(1) 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.

B

1.16.2.1

Yes

C.2.1.16.2(b) The contractor shall provide, Access Route or Path Avoidance for dedicated access, when requested by the government, 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.

B

1.16.2.2

Yes Non Domestic

C.2.1.16.2(b) 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.

B

1.16.2.2

Yes

C.2.1.16.2 The contractor shall provide within 30 calendar days of the implementation of access diversity or avoidance and again there after 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.

B

1.16.2.2

Yes





C.2.1.16.2 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.

B

1.16.2.2

Yes

C.2.1.16.2 The contractor shall conform to the requirements for performance and service assurance feature 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)

B

1.16.2.2

Yes

C.2.1.16.2 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.

B

1.16.2.2

Yes

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

B

1.16.3

Yes

C.2.1.16.3 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.

B

1.16.3

Yes

C.2.1.16.3 The ISDN access arrangement shall conform to ANSI T1.620/607/606/610/614/608/602/609/612/626 and ITU I.300/610.

B

1.16.3

Yes

C.2.1.16.3 The ISDN PRI shall comprise twenty-three 64 kb/s B channels and one 64 kb/s D channel (23B+D).

B

1.16.3

Yes

C.2.1.16.3 Where more than one PRI is provisioned at one SDP, it shall be possible to arrange for them to share one D channel wherever 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.

B

1.16.3

Yes

C.2.1.16.3 The contractor shall provide originating and/or terminating access for circuit-mode and packet-mode calls.

B

1.16.3

Yes





C.2.1.16.3 The ISDN access shall provide access to and from transport-network via PRI.

B

1.16.3

Yes

C.2.1.16.3 Originating ISDN access shall connect on-net originating locations with the associated POP.

B

1.16.3

Yes

C.2.1.16.3 Terminating access shall connect the terminating POP with the on-net terminating locations.

B

1.16.3

Yes

C.2.1.16.3 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.

B

1.16.3

Yes

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

B

1.16.3

Yes

C.2.1.16.3 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.

B

1.16.3

Yes

C.2.1.16.3(a) 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 for: Baseband at 64 kb/s over one B channel.

B

1.16.3

Yes

C.2.1.16.3(b) For all SDS and CSDS, the ISDN access shall 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 for: Wideband/Multirate at N times 64 kb/s over N x B channels (where N = 2 to 23 for PRI).

B

1.16.3

Yes

C.2.1.16.3(c) The ISDN access shall support 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 for Baseband at 64 kb/s over one B channel.

B

1.16.3

Yes

C.2.1.16.3(d) The ISDN access shall support packet-mode data rates over B channels as specified in ANSI T1.614, T1.603

B Yes





and T1.604 for PSS; and, ANSI T1.606 for FRS for Wideband/Multirate at N times 64 kb/s over N x B channels (where N = 2 to 23 for PRI).

1.16.3

C.2.1.16.3.1 (a)(1)

The ISDN access features shall be supported for 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

1.16.3.1

Yes

C.2.1.16.3.2 (a)(1)

The ISDN Access performance parameters for Transmission Performance for originating or terminating access connection between a POP and an SDP for providing switched services: 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

1.16.3.2

Yes

C.2.1.16.3.2 (b)(1)

The ISDN Access performance parameters for GOS for originating or terminating access connection between a POP and an SDP for providing switched services: For circuit switched access, the blockage shall be 3 percent or less.

B

1.16.3.2

Yes

C.2.1.16.3.2(c)(1)

The ISDN Access performance parameters for availability for originating or terminating access connection between a POP and an SDP for providing switched services: The ISDN access shall provide an availability of at least 99.8 percent.

B

1.16.3.2

Yes

C.2.1.16.3.3.1 (a)(1)

The contractor shall support the Interface at the SDP for ISDN Access provisioning for PRI (at line-rate of 1.544 Megabit per second (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

1.16.3.3.1

Yes

C.2.1.16.3.3.1.1 (b)(1)

The contractor shall support Signaling conforming to ANSI T1.615 “Telecommunications ISDN - Digital Subscriber Signaling System No. 1 (DSS1) - Layer 3 Overview for ISDN signaling”

B

1.16.3.3.1

Yes

C.2.1.16.3.3.1.1 (b)(2)

The contractor shall support Signaling conforming to ANSI T1.602 “Telecommunications ISDN - Data-Link Layer Signaling Specification for Application at the

B

1.16.3.3.1

Yes





User-Network Interface for D channel signaling”.

C.2.1.16.3.3.1.1 (b)(3)

The contractor shall support Signaling conforming to ANSI T1.609 “Telecommunications - Interworking Between the ISDN User-Network Interface Protocol and the Signaling System Number 7 ISDN User Part”.

B

1.16.3.3.1

Yes

C.2.1.16.3.3.1.1 (b)(4)

The contractor shall support Signaling conforming to ANSI T1.612 “Telecommunications - ISDN - Terminal Adaptation Using Statistical Multiplexing” while providing rate adaptation for ISDN Customer Premises Equipment (CPE).

B

1.16.3.3.1

Yes

C.2.1.16.3.3.1.1 (b)(5)

The contractor shall support Signaling conforming to ANSI T1.626 “Telecommunications - Switch-Computer Applications Interface” while providing a computer to ISDN switch interface.

B

1.16.3.3.1

Yes

C.2.1.16.3.3.1.1 (b)(6)

The contractor shall support Signaling conforming to SS7 Signaling Interface (Standard: ANSI (T1. 110 through T1.116 and T1.611) and Bellcore GR-246-CORE).

B

1.16.3.3.1

Yes

C.2.1.16.3.3.1.1 The contractor shall support the UNI types as specified in Table C.2.1.16.3.3.1.1-1.

B

1.16.3.3.1

Yes

C.2.1.16.3.3.2.1 (a)(1)

Pursuant to Section C.2.1.16, the contractor shall support/provide the Dedicated Access interfaces to connect to a POP listed for the provisioning of ISDN Access conforming to ISDN PRI (Standard: ANSI T1.607 and 610)

B

1.16.3.3.2.1

Yes

C.2.1.16.3.3.2.1 (a)(2)

Pursuant to Section C.2.1.16, the contractor shall support/provide the Dedicated Access interfaces to connect to a POP listed for the provisioning of ISDN Access conforming to E1 for non-domestic use (Standard: ITU-TSS G.702).

B

1.16.3.3.2.1

Yes

C.2.1.16.3.3.2.2 (a)(1)

Pursuant to Section C.2.1.16, the contractor shall support/provide the Circuit Switched Access interfaces to connect to a POP listed for the provisioning of ISDN Access conforming to Integrated Digital Loop Carrier System Generic Requirements, Objectives, and Interfaces (Bellcore Pub: GR-303-CORE).

B

1.16.3.3.2.2

Yes





C.2.1.16.3.3.2.2 (a)(2)

Pursuant to Section C.2.1.16, the contractor shall support/provide the Circuit Switched Access interfaces to connect to a POP listed for the provisioning of ISDN Access conforming to Switching System Generic Requirements for Interexchange Carrier Interconnection using ISDN User Part (ISDNUP) (Bellcore Pub: GR-394-CORE).

B

1.16.3.3.2.2

Yes

C.2.1.16.3.3.2.2 (a)(3)

Pursuant to Section C.2.1.16, the contractor shall support/provide the Circuit Switched Access interfaces to connect to a POP listed for the provisioning of ISDN Access conforming to National ISDN-1 (Bellcore Pub: SR-NWT-001937).

B

1.16.3.3.2.2

Yes

C.2.1.16.3.3.2.2 (a)(4)

Pursuant to Section C.2.1.16, the contractor shall support/provide the Circuit Switched Access interfaces to connect to a POP listed for the provisioning of ISDN Access conforming to National ISDN-2 (Bellcore Pub: SR-NWT-002120).

B

1.16.3.3.2.2

Yes

C.2.1.16.3.3.2.2 (a)(5)

Pursuant to Section C.2.1.16, the contractor shall support/provide the Circuit Switched Access interfaces to connect to a POP listed for the provisioning of ISDN Access conforming to All applicable sections, related to 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).

B

1.16.3.3.2.2

Yes

C.2.1.16.3.3.2.2 (a)(6)

Pursuant to Section C.2.1.16, the contractor shall support/provide the Circuit Switched Access interfaces to connect to a POP listed for the provisioning of ISDN Access conforming to Compatibility Information for Feature Group D Switched Access Service (Bellcore Pub: TR-NPL-00258).

B

1.16.3.3.2.2

Yes

C.2.1.16.3.3.2.2 (a)(7)

Pursuant to Section C.2.1.16, the contractor shall support/provide the Circuit Switched Access interfaces to connect to a POP listed for the provisioning of ISDN Access conforming to IC/INC Interconnection (Bellcore Pub: GR-690-CORE).

B

1.16.3.3.2.2

Yes

C.2.1.16.3.3.2.2 (a)(8)

Pursuant to Section C.2.1.16, the contractor shall support/provide the Circuit Switched Access interfaces to connect to a POP listed for the provisioning of ISDN Access conforming to Bellcore Specification of SS7

B

1.16.3.3.2.2

Yes





(Bellcore Pub: GR-246-CORE).

C.2.1.16.3.3.2.2 (a)(9)

Pursuant to Section C.2.1.16, the contractor shall support/provide the Circuit Switched Access interfaces to connect to a POP listed for the provisioning of ISDN Access conforming to SONET Transport Systems: Common Generic Criteria (Bellcore Pub: GR-253-CORE).

B

1.16.3.3.2.2

Yes





C.2.2.1.1.1 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.

B

2.1.1.1

Yes

C.2.2.1.1.1 SVS 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.

B

2.1.1.1

Yes

C.2.2.1.1.1 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.

B

2.1.1.1

Yes

C.2.2.1.1.1 Pursuant to Section C.2.1.16, the contractor shall provide dedicated and switched originating and/or terminating access connections for SVS calls.

B

2.1.1.1

Yes

C.2.2.1.1.1 Originating access connections shall connect SVS on-net originating locations with the associated POP.

B

2.1.1.1

Yes

C.2.2.1.1.1 Terminating access connections shall connect the terminating POP with SVS on-net terminating locations.

B

2.1.1.1

Yes

C.2.2.1.1.1 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.

B

2.1.1.1

Yes

C.2.2.1.1.1(a) When SVS access is provided via switched access arrangement (see Section C.2.1.16), the contractor shall

B Yes





support a uniform numbering plan for all on-net Government locations whereby each station receiving service shall be identified by a unique directory number.

2.1.1.1

C.2.2.1.1.1(a) The numbering plan shall support commercial PSN numbers, and contractor’s network-specific private numbers.

B

2.1.1.1

Yes

C.2.2.1.1.1(a) 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

2.1.1.1

Yes

C.2.2.1.1.1(b) When SVS access is provided via switched access arrangement (see Section C.2.1.16), 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.

B

2.1.1.1

Yes

C.2.2.1.1.1(b) The contractor shall identify numbers to be reserved for special uses, such as access to contractor’s operators, trouble reporting, or other special applications.

B

2.1.1.1

Yes

C.2.2.1.1.1(c) When SVS access is provided via switched access arrangement (see Section C.2.1.16), the contractor shall provide network intercept to recorded announcements as an inherent network capability when a call cannot be completed.

B

2.1.1.1

Yes

C.2.2.1.1.1(c) 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.

B

2.1.1.1

Yes

C.2.2.1.1.1 SVS shall provide the capability for calls to terminate via Inmarsat (all terminal types A, B, M, Mini-M, and Aeronautical)

B.2.1.1.1 Yes

C.2.2.1.1.3(a)(1) All analog transmission parameters for originating or terminating access connection between a POP and an SDP shall satisfy at least the values and ranges set forth in Section 7, Transmission, BOC Notes on the LEC

B

2.1.1.3

Yes





Networks. (Bellcore Pub: SR-TSV-002275).

C.2.2.1.1.3(a)(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

2.1.1.3

Yes

C.2.2.1.1.3(b)(1) For switched access arrangement and dedicated - Class 2 access arrangements, the blockage shall be 3 percent or less.

B

2.1.1.3

Yes

C.2.2.1.1.3(c)(1) SVS access shall provide an availability of at least 99.8 percent for originating or terminating access connection between a POP and an SDP.

B

2.1.1.3

Yes

C.2.2.1.1.3(d)(1) Post dialing delay shall not exceed best commercial practice

B

2.1.1.3

Yes

C.2.2.1.1.4.1.1 (a)(1)

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

B

2.1.1.4.1.1

Yes

C.2.2.1.1.4.1.1 (b)(1)

The contractor shall support Two-wire access circuits. Bellcore’s BOC Notes on the LEC Networks [SR-TSV-002275]).

B

2.1.1.4.1.1

Yes

C.2.2.1.1.4.1.1 (b)(2)

The contractor shall support Four-wire E&M access circuit. Bellcore’s BOC Notes on the LEC Networks [SR-TSV-002275]).

B

2.1.1.4.1.1

Yes

C.2.2.1.1.4.1.1 (c)(1)

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

B

2.1.1.4.1.1

Yes

C.2.2.1.1.4.1.1 (c)(2)

The contractor shall support ISDN PRI at a 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)

B

2.1.1.4.1.1

Yes

C.2.2.1.1.4.1.1 (c)(3)

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

B

2.1.1.4.1.1

Yes





C.2.2.1.1.4.1.1 (c)(4)

The contractor shall support E1 channelized at a 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.

B

2.1.1.4.1.1

Yes

C.2.2.1.1.4.1.1 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.

B

2.1.1.4.1.1

Yes

C.2.2.1.1.4.2.1 (a)(1)

Pursuant to Section C.2.1.16, the contractor shall support/provide Dedicated Access to connect to a POP via T1 and Fractional T1 channelized with ESF. (Standard: Bellcore Pubs: SR-TSV-002275; ANSI T1.102/107/403).

B

2.1.1.4.2.1

Yes

C.2.2.1.1.4.2.1 (a)(2)

Pursuant to Section C.2.1.16, the contractor shall support/provide Dedicated Access to connect to a POP via ISDN PRI. (Standard: ANSI T1.607 and 610).

B

2.1.1.4.2.1

Yes

C.2.2.1.1.4.2.1 (a)(3)

Pursuant to Section C.2.1.16, the contractor shall support/provide Dedicated Access to connect to a POP via T3 and Fractional T3 channelized. (Standard: Bellcore Pub: GR-499-CORE).

B

2.1.1.4.2.1

Yes

C.2.2.1.1.4.2.1 (a)(4)

Pursuant to Section C.2.1.16, the contractor shall support/provide Dedicated Access to connect to a POP via E1 channelized for non-domestic use. (Standard: ITU-TSS G.702)

B

2.1.1.4.2.1

Yes

C.2.2.1.1.4.2.1 (a)(5)

Pursuant to Section C.2.1.16, the contractor shall support/provide Dedicated Access to connect to a POP via Analog. (Standard: Bellcore Pub: SR-TSV-002275).

B

2.1.1.4.2.1

Yes

C.2.2.1.1.4.2.2 (a)(1)

Pursuant to Section C.2.1.16, the contractor shall support/provide Circuit Switched Access to connect to a POP conforming to all applicable sections, related to LEC to IC/INC interconnections for CSSs, BOC Notes on the LEC Networks. (Bellcore Pub: SR-TSV-002275).

B

2.1.1.4.2.2

Yes

C.2.2.1.1.4.2.2 (a)(2)

Pursuant to Section C.2.1.16, the contractor shall support/provide Circuit Switched Access to connect to a POP conforming to Compatibility Information for Feature Group D Switched Access Service. (Bellcore Pub: TR-NPL-00258).

B

2.1.1.4.2.2

Yes

C.2.2.1.1.4.2.2 (a)(3)

Pursuant to Section C.2.1.16, the contractor shall support/provide Circuit Switched Access to connect to a POP conforming to Exchange Access Interconnection.

B Yes





FSD 20-24-0000 (Bellcore Pub: GR-690-CORE). 2.1.1.4.2.2

C.2.2.1.1.4.2.2 (a)(4)

Pursuant to Section C.2.1.16, the contractor shall support/provide Circuit Switched Access to connect to a POP conforming to Bellcore Specification of Signaling System Number 7. (Bellcore Pub: GR-246-CORE).

B

2.1.1.4.2.2

Yes

C.2.2.1.2.1 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.

B

2.1.2.1

Yes

C.2.2.1.2.1 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.

B

2.1.2.1

Yes

C.2.2.1.2.1 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.

B

2.1.2.1

Yes

C.2.2.1.2.1 Pursuant to Section C.2.1.16, the contractor shall provide SVS POP-to-POP connections between the contractor’s listed POPs.

B

2.1.2.1

Yes

C.2.2.1.2.1 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.

B

2.1.2.1

Yes

C.2.2.1.2.1 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.

B

2.1.2.1

Yes

C.2.2.1.2.1 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.

B

2.1.2.1

Yes

C.2.2.1.2.1 The numbering plan shall support commercial PSN numbers, non commercial agency specific private numbers, and contractor’s network-specific private numbers.

B

2.1.2.1

Yes

C.2.2.1.2.1 The numbering plan established for on-net stations shall accommodate current FTS2000 numbers already

B Yes





following NANP, and commercial non-domestic numbers, although some exceptions may be approved or requested by the Government at no additional cost.

2.1.2.1

C.2.2.1.2.1 The contractor shall identify numbers to be reserved for special uses, such as access to contractor’s operators, trouble reporting, or other special applications.

B

2.1.2.1

Yes

C.2.2.1.2.1 The contractor shall provide network intercept to recorded announcements as an inherent network capability when a call cannot be completed.

B

2.1.2.1

Yes

C.2.2.1.2.1 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.

B

2.1.2.1

Yes

C.2.2.1.2.1 The contractor shall provide authorization codes. B

2.1.2.1

Yes

C.2.2.1.2.1 The purpose of an authorization code is to provide to the network a calling identification and COS for users.

B

2.1.2.1

Yes Non Domestic No C.O.S

C.2.2.1.2.1 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.

B

2.1.2.1


C.2.2.1.2.1 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.

B

2.1.2.1


C.2.2.1.2.1 The format of the authorization code shall be determined by the contractor except as described in Section C.5.2.1.

B

2.1.2.1

Yes

C.2.2.1.2.1 The contractor shall provide credit card-sized B Yes





authorization code card(s), also called FTS2001 Calling Cards, unless otherwise directed by the Government.

2.1.2.1

C.2.2.1.2.1 FTS2001 Calling Cards shall be made of durable plastic with magnetic strip (swipe) coding and imprinted with authorization code, user’s name, and organization.

B

2.1.2.1

Yes

C.2.2.1.2.1 The FTS2001 Calling Cards and user instructions shall be issued and delivered at no cost to the Government.

B

2.1.2.1

Yes

C.2.2.1.2.1 The contractor shall take safeguards against potential fraud and theft regarding issuance, distribution, and activation of authorization codes.

B

2.1.2.1

Yes

C.2.2.1.2.1 Personal Identification Numbers (PINs) shall be delivered independently from the calling cards.

B

2.1.2.1

Yes

C.2.2.1.2.1 The last 4 digits of authorization codes (i.e., Personal Identification Number [PIN]), shall not be included in billing records.

B

2.1.2.1


C.2.2.1.2.1 If the calling card has sufficient space, the Federal Relay “TDD/800-877-8339” shall be included on the back of the calling card.

B

2.1.2.1

Yes

C.2.2.1.2.1 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.

B

2.1.2.1

Yes

C.2.2.1.2.1 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.

B

2.1.2.1


C.2.2.1.2.1 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.

B

2.1.2.1

Yes

C.2.2.1.2.1 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).

B

2.1.2.1

Yes





C.2.2.1.2.1 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.

B

2.1.2.1

Yes

C.2.2.1.2.1 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.

B

2.1.2.1

Yes

C.2.2.1.2.1 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.

B

2.1.2.1

Yes

C.2.2.1.2.1 The boundaries of these regions shall be defined by the contractor.

B

2.1.2.1

Yes

C.2.2.1.2.1 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.

B

2.1.2.1

Yes

C.2.2.1.2.1 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.

B

2.1.2.1

Yes

C.2.2.1.2.1 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.

B

2.1.2.1

Yes

C.2.2.1.2.2.1(a) The Agency-Recorded Message Announcements feature shall allow authorized Government personnel to record message announcements within the network.

B

2.1.2.2.1.1

Yes

C.2.2.1.2.2.1(a) The recording shall be assigned an on-net number and B Yes





shall be accessible from on-net and off-net stations. 2.1.2.2.1.1

C.2.2.1.2.2.1(a) 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).

B

2.1.2.2.1.1

Yes

C.2.2.1.2.2.1(a) A call to the announcement must be answered within five rings, and barge-in access to the announcement shall be permitted.

B

2.1.2.2.1.1

Yes

C.2.2.1.2.2.1(a) The contractor shall provide a system-wide capability for storing a minimum of 300 recorded messages.

B

2.1.2.2.1.1

Yes

C.2.2.1.2.2.1(a) This feature shall enable a minimum of 250 callers, concurrently, to access an announcement.

B

2.1.2.2.1.1

Yes

C.2.2.1.2.2.1(b) Operators shall provide support services in English for users.

B

2.1.2.2.1.2

Yes

C.2.2.1.2.2.1(b) This service shall be made available 24 hours per day, 7 days per week.

B

2.1.2.2.1.2

Yes

C.2.2.1.2.2.1(b) Users shall not receive a busy tone when calling for operator services.

B

2.1.2.2.1.2

Yes

C.2.2.1.2.2.1(b) Calls to operators shall be answered within five rings 90 percent of the time.

B

2.1.2.2.1.2

Yes

C.2.2.1.2.2.1 (b)(1)

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

B

2.1.2.2.1.2

Yes

C.2.2.1.2.2.1 (b)(2)

Operators shall be available to assist users encountering dialing difficulties while using the contractor’s services.

B

2.1.2.2.1.2

Yes

C.2.2.1.2.2.1 (b)(2)

The operator shall remain on the line until the call has been connected.

B

2.1.2.2.1.2

Yes





C.2.2.1.2.2.1 (b)(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.

B

2.1.2.2.1.2

Yes

C.2.2.1.2.2.1 (b)(3)

The contractor shall maintain its locator database for the Government.

B

2.1.2.2.1.2

Yes

C.2.2.1.2.2.1 (b)(4)

Operators shall be able to complete calls for accessing the network from off-net and on-net locations.

B

2.1.2.2.1.2

Yes

C.2.2.1.2.2.1 (b)(4)

Operators shall be able to verify authorization codes given verbally by callers accessing the network.

B

2.1.2.2.1.2

Yes

C.2.2.1.2.2.1 (b)(4)

Upon confirmation of the authorization code, operators shall be able to complete the call.

B

2.1.2.2.1.2

Yes

C.2.2.1.2.2.1 (b)(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.

B

2.1.2.2.1.2

Yes

C.2.2.1.2.2.1 (b)(5)

A user shall be able to call an operator by dialing a special number to obtain a credit adjustment for a completed call to a wrong number, an interrupted call, or unsatisfactory transmission.

B

2.1.2.2.1.2

Yes

C.2.2.1.2.2.1(c) 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.

B

2.1.2.2.1.2

Yes Non Domestic

C.2.2.1.2.2.1 (c)(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.

B

2.1.2.2.1.2

Yes Non Domestic

C.2.2.1.2.2.1 (c)(1)

COS shall be determined from ANI, authorization code, traveling classmark, or trunk group.

B

2.1.2.2.1.2

Yes Non Domestic





C.2.2.1.2.2.1 (c)(1)

The COS derived from an authorization code shall take precedence over that derived from other means.

B

2.1.2.2.1.2

Yes Non Domestic

C.2.2.1.2.2.1 (c)(1)

Classes of service shall identify, but not be limited to, access and feature restrictions.

B

2.1.2.2.1.2

Yes Non Domestic

C.2.2.1.2.2.1 (c)(1)(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.

B

2.1.2.2.1.2

Yes Non Domestic

C.2.2.1.2.2.1 (c)(1)(ii)

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

B

2.1.2.2.1.2

Yes Non Domestic

C.2.2.1.2.2.1 (c)(2)

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.

B

2.1.2.2.1.2

Yes Non Domestic

C.2.2.1.2.2.1 (c)(3)

The Traveling Classmark 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.

B

2.1.2.2.1.2

Yes Non Domestic

C.2.2.1.2.2.1 (c)(3)

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.

B

2.1.2.2.1.2

Yes Non Domestic

C.2.2.1.2.2.1 (c)(4)

The Code Block 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.

B

2.1.2.2.1.2

Yes Non Domestic

C.2.2.1.2.2.1(d) 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.

B

2.1.2.2.1.4

Yes

C.2.2.1.2.2.1(e) The contractor shall provide network audio conferencing for two- and four-wire audio conference equipment, as

B Yes





well as to any telephone accessible via the contractor’s network.

2.1.2.2.1.5

C.2.2.1.2.2.1 (e)(1)

The User-Initiated Conference 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.

B

2.1.2.2.1.5

Yes

C.2.2.1.2.2.1 (e)(1)(i)(A)

The Meet-Me Conference (in Automated Mode) 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 that conference.

B

2.1.2.2.1.5

Yes

C.2.2.1.2.2.1 (e)(1)(i)(A)

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

2.1.2.2.1.5

Yes

C.2.2.1.2.2.1 (e)(1)(i)(B)

The Preset Conference (in Automated Mode) capability shall allow authorized users to activate a previously defined conference and associated conferees, by dialing an access number followed by an authorization code. Once activated, the system will attempt to connect the pre-designated participants.

B

2.1.2.2.1.5

Yes

C.2.2.1.2.2.1 (e)(1)(ii)

In Manual Mode 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.”

B

2.1.2.2.1.5

Yes

C.2.2.1.2.2.1 (e)(2)

The Operator-Controlled Conference capability shall allow operators to establish a conference.

B

2.1.2.2.1.5

Yes

C.2.2.1.2.2.1 (e)(2)

Conferees shall be able to recall an operator during a conference for immediate attention such as general assistance, or adding or dropping participants.

B

2.1.2.2.1.5

Yes





C.2.2.1.2.2.1 (e)(2)

This service shall be made available 24 hours per day, 7 days per week.

B

2.1.2.2.1.5

Yes

C.2.2.1.2.2.1(e) 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.

B

2.1.2.2.1.5

Yes

C.2.2.1.2.2.1(e) 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.

B

2.1.2.2.1.5

Yes

C.2.2.1.2.2.1(e) The service shall allow storage and retrieval of up to at least 1,000 predefined conferences of an average seven ports per conference.

B

2.1.2.2.1.5

Yes

C.2.2.1.2.2.1(e) 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.

B

2.1.2.2.1.5

Yes

C.2.2.1.2.2.1(e) This service shall provide transmission bridging arrangements, including automatic, dynamic control of volume, noise, and echo, with minimum break-in difficulties.

B

2.1.2.2.1.5

Yes

C.2.2.1.2.2.1(e) This service shall also minimize the need for special user and operator instructions and training.

B

2.1.2.2.1.5

Yes

C.2.2.1.2.2.1(e) These arrangements shall minimize the impact of network difficulties, such as “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.

B

2.1.2.2.1.5

Yes

C.2.2.1.2.2.1(e) 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.

B

2.1.2.2.1.5

Yes

C.2.2.1.2.2.1 (e) The contractor shall support/provide sufficient capacity to B Yes





(3) support an average daily conference load of 300 conferences (of all 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.

2.1.2.2.1.5

C.2.2.1.2.2.1 (e)(4)

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

B

2.1.2.2.1.5

Yes

C.2.2.1.2.2.1 (e)(5)

At least 36 simultaneous conference calls shall be able to be monitored by operators.

B

2.1.2.2.1.5

Yes

C.2.2.1.2.2.1 (e)(6)

The contractor shall support/provide establishment of unscheduled operator-controlled conferences within ten minutes of a request, 24 hours per day, 7 days per week.

B

2.1.2.2.1.5

Yes

C.2.2.1.2.2.1(f) When an authorization code is used for the service, it shall be verified without involving an operator before the service is provided.

B

2.1.2.2.1.6

Yes

C.2.2.1.2.2.1(g) 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.

B

2.1.2.2.1.7

Yes

Domestic & Calling Card

Non Domestic

C.2.2.1.2.2.1(h) 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).

B

2.1.2.2.1.8

Yes

C.2.2.1.2.2.1(h) CDRs shall reflect all relevant data, including these internal agency accounting code digits, on the call.

B

2.1.2.2.1.8

Yes

C.2.2.1.2.2.1(h) The call shall be charged to the authorization code rather than to the originating station.

B

2.1.2.2.1.8

Yes

C.2.2.1.2.3(a)(1) All digital transmission parameters for POP-to-POP connection 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

2.1.2.3

Yes





C.2.2.1.2.3(b)(1) The blockage (i.e., GOS) for POP-to-POP connection shall be 1 percent or less.

B

2.1.2.3

Yes

C.2.2.1.2.3(c)(1) SVS transport for POP-to-POP connection shall provide an availability of at least 99.8 percent.

B

2.1.2.3

Yes

C.2.2.1.2.3(d)(1) Post dialing delay shall not exceed best commercial practice.

B

2.1.2.3

Yes

C.2.2.1.2.4.1.1 (a)(1)

Pursuant to Section C.2.1.16, the contractor shall support/provide Dedicated Access via T1 and Fractional T1 channelized with ESF. (Standard: Bellcore Pubs: SR-TSV-002275; ANSI T1.102/107/403).

B

2.1.2.4.1.1

Yes

C.2.2.1.2.4.1.1 (a)(2)

Pursuant to Section C.2.1.16, the contractor shall support/provide Dedicated Access via ISDN PRI. (Standard: ANSI T1.607 and 610).

B

2.1.2.4.1.1

Yes

C.2.2.1.2.4.1.1 (a)(3)

Pursuant to Section C.2.1.16, the contractor shall support/provide Dedicated Access via T3 and Fractional T3 channelized. (Standard: Bellcore Pub: GR-499-CORE).

B

2.1.2.4.1.1

Yes

C.2.2.1.2.4.1.1 (a)(4)

Pursuant to Section C.2.1.16, the contractor shall support/provide Dedicated Access via E1 channelized for Non-Domestic use. (Standard: ITU-TSS G.702).

B

2.1.2.4.1.1

Yes

C.2.2.1.2.4.1.1 (a)(5)

Pursuant to Section C.2.1.16, the contractor shall support/provide Dedicated Access via Analog (Standard: Bellcore Pub: SR-TSV-002275)

B

2.1.2.4.1.1

Yes

C.2.2.1.2.4.1.2 (a)(1)

Pursuant to Section C.2.1.16, the contractor shall support/provide Circuit Switched Access conforming to all applicable sections, related to LEC to IC/INC interconnections for CSSs, BOC Notes on the LEC Networks. (Bellcore Pub: SR-TSV-002275).

B

2.1.2.4.1.2

Yes

C.2.2.1.2.4.1.2 (a)(2)

Pursuant to Section C.2.1.16, the contractor shall support/provide Circuit Switched Access conforming to Compatibility Information for Feature Group D Switched Access Service. (Bellcore Pub: TR-NPL-00258).

B

2.1.2.4.1.2

Yes

C.2.2.1.2.4.1.2 (a)(3)

Pursuant to Section C.2.1.16, the contractor shall support/provide Circuit Switched Access conforming to Exchange Access Interconnection. FSD 20-24-

B

2.1.2.4.1.2

Yes





0000(Bellcore Pub: GR-690-CORE).

C.2.2.1.2.4.1.2 (a)(4)

Pursuant to Section C.2.1.16, the contractor shall support/provide Cirucit switched Access conforming to Bellcore Specification of Signaling System Number 7. (Bellcore Pub: GR-246-CORE).

B

21.2.4.1.2

Yes

C.2.2.2.1.1 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.

B

2.2.1.1

Yes

C.2.2.2.1.1 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.

B

2.2.1.1

Yes

C.2.2.2.1.1 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.

B

2.2.1.1

Yes

C.2.2.2.1.1 Pursuant to Section C.2.1.16, the contractor shall provide dedicated and switched originating and/or terminating access connections for CSDS calls.

B

2.2.1.1

Yes

C.2.2.2.1.1 Originating access connections shall connect CSDS on-net originating locations with the associated POP.

B

2.2.1.1

Yes

C.2.2.2.1.1 Terminating access connections shall connect the terminating POP with CSDS on-net terminating locations.

B

2.2.1.1

Yes

C.2.2.2.1.1 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.

B

2.2.1.1

Yes

C.2.2.2.1.1 CSDS shall provide network-derived clocking to the DTE or PBX/multiplexer (MUX) at the SDP.

B

2.2.1.1

Yes

C.2.2.2.1.1 Once a call has been established, all bit sequences transmitted by the DTE shall be transported as data/bit

B Yes





transparent, maintaining data/bit sequence integrity. 2.2.1.1

C.2.2.2.1.1(a) For the DS0 Category, CSDS shall support the dialable information-payload bandwidth of DS0 (i.e., 56 kb/s and 64 kb/s) data rate.

B

2.2.1.1.1

Yes

C.2.2.2.1.1(b) For the DS1 Category, CSDS shall support dialable information-payload bandwidth of DS1 (i.e., 1.536 Mb/s).

B

2.2.1.1.1

Yes

C.2.2.2.1.1(c) For the Multirate DS0 category of service, the dialable bandwidth shall be two times DS0 (i.e., 56 kb/s and 64 kb/s), six times DS0, and twelve times DS0.

B

2.2.1.1.1

Yes

C.2.2.2.1.1(d) When CSDS is provided via switched access arrangement (see Section C.2.1.16), the contractor shall support a uniform numbering plan for all on-net Government locations.

B

2.2.1.1.2

Yes

C.2.2.2.1.1(d) When CSDS is provided via switched access arrangement, each station receiving service shall be identified by a unique directory number which will be employed by CSDS users for calling each other.

B

2.2.1.1.2

Yes

C.2.2.2.1.1(d) When CSDS is provided via switched access arrangement (see Section C.2.1.16), this numbering plan shall use the NANP as proposed for SVS (refer to Section C.2.2.1.1).

B

2.2.1.1.2

Yes

C.2.2.2.1.1(d) When CSDS is provided via switched access arrangement, this numbering plan shall be integrated with the NANP.

B

2.2.1.1.2

Yes

C.2.2.2.1.1(d) Calling capability shall be spontaneous. B

2.2.1.1.2

Yes

C.2.2.2.1.1(d) Calling capability shall not require scheduling. B

2.2.1.1.2

Yes

C.2.2.2.1.1(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.

B

2.2.1.1.2

Yes

C.2.2.2.1.3 (a)(1) All digital transmission parameters for originating or B Yes





terminating access connections between a POP and an SDP 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).

2.2.1.3

C.2.2.2.1.3(b)(1) For the switched access arrangement and dedicated - Class 2 access arrangement trunk groups, the blockage (i.e., GOS) for originating or terminating access connections between a POP and an SDP shall be 3 percent or less.

B

2.2.1.3

Yes

C.2.2.2.1.3(c)(1) CSDS access for originating or terminating access connections between a POP and an SDP shall provide an availability of at least 99.8 percent.

B

2.2.1.3

Yes

C.2.2.2.1.4.1.1 (a)

The contractor shall support a UNI at the SDP via ITU-TSS V.35.

B

2.2.1.4.1.1

Yes

C.2.2.2.1.4.1.1 (b)

The contractor shall support a UNI at the SDP via EIA RS-449.

B

2.2.1.4.1.1

Yes

C.2.2.2.1.4.1.1 (c)

The contractor shall support a UNI at the SDP via EIA RS-530.

B

2.2.1.4.1.1

Yes

C.2.2.2.1.4.1.1 (d)

The contractor shall support a UNI at the SDP via ISDN PRI with multirate facility, 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).

B

2.2.1.4.1.1

Yes

C.2.2.2.1.4.1.1 (e)

The contractor shall support a UNI at the SDP via 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 Network [SR-TSV-002275], and ANSI T1.102/107/403).

B

2.2.1.4.1.1

Yes

C.2.2.2.1.4.1.1 (f) The contractor shall support a UNI at the SDP via SS7 signaling interface. (Standard: ANSI T1.110 through T1.116 and T1.611).

B

2.2.1.4.1.1

Yes

C.2.2.2.1.4.1.1 The contractor shall support the UNI types as given in Table C.2.2.2.1.4.1.1-1.

B

2.2.1.4.1.1

Yes

C.2.2.2.1.4.2.1 Pursuant to Section C.2.1.16, the contractor shall B Yes





(a)(1) support/provide Dedicated Access to connect to a POP via T1 and Fractional T1 with ESF. (Standard: Bellcore Pub: SR-TSV-002275; ANSI T1.102/107/403).

2.2.1.4.2.1

C.2.2.2.1.4.2.1 (a)(2)


B

2.2.1.4.2.1

Yes

C.2.2.2.1.4.2.1 (a)(3)

Pursuant to Section C.2.1.16, the contractor shall support/provide Dedicated Access to connect to a POP via T3 and Fractional T3 channelized (Standard: Bellcore Pub: GR-499-CORE).

B

2.2.1.4.2.1

Yes

C.2.2.2.1.4.2.1 (a)(4)

Pursuant to Section C.2.1.16, the contractor shall support/provide Dedicated Access to connect to a POP via DS0 and Subrate DS0 (Bellcore Pub: SR-TSV-002275)

B

2.2.1.4.2.1

Yes

C.2.2.2.1.4.2.2 (a)(1)

Pursuant to Section C.2.1.16, the contractor shall support/provide Circuit Switched Access to connect to a POP conforming to all applicable sections, related to LEC to IC/INC interconnections for CSSs, BOC Notes on the LEC Networks (Bellcore Pub: SR-TSV-002275).

B

2.2.1.4.2.2

Yes

C.2.2.2.1.4.2.2 (a)(2)


B

2.2.1.4.2.2

Yes

C.2.2.2.1.4.2.2 (a)(3)

Pursuant to Section C.2.1.16, the contractor shall support/provide Circuit Switched Access to connect to a POP conforming to Exchange Access Interconnection FSD20-24-0000 (Bellcore Pub: GR-690-CORE).

B

2.2.1.4.2.2

Yes

C.2.2.2.1.4.2.2 (a)(4)


B

2.2.1.4.2.2

Yes

C.2.2.2.1.4.2.2 (a)(5)

Pursuant to Section C.2.1.16, the contractor shall support/provide Circuit Switched Access to connect to a POP conforming to Switched DS0 (Bellcore Pub: SR-TSV-002275)

B

2.2.1.4.2.2

Yes

C.2.2.2.2.1 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

B Yes





on-net and off-net locations. 2.2.2.1

C.2.2.2.2.1 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.

B

2.2.2.1

Yes

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

B

2.2.2.1

Yes SONET is a United States standard and not available non-domestically

C.2.2.2.2.1 Pursuant to Section C.2.1.16, the contractor shall provide CSDS POP-to-POP connections between the contractor's listed POPs.

B

2.2.2.1

Yes

C.2.2.2.2.1 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.

B

2.2.2.1

Yes

C.2.2.2.2.1 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.

B

2.2.2.1

Yes

C.2.2.2.2.1 The contractor shall support a uniform numbering plan for all on-net Government locations.

B

2.2.2.1

Yes

C.2.2.2.2.1 Each station receiving service shall be identified by a unique directory number which will be employed by CSDS users for calling each other.

B

2.2.2.1

Yes

C.2.2.2.2.1 This numbering plan shall use the NANP as proposed for SVS (refer to Section C.2.2.1.1.1).

B

2.2.2.1

Yes

C.2.2.2.2.1 The NANP shall be integrated with that plan. B

2.2.2.1

Yes





C.2.2.2.2.1 Calling capability shall not require scheduling. B

2.2.2.1

Yes

C.2.2.2.2.1 Once a call has been established, all bit sequences transmitted shall be transported as data/bit transparent, maintaining data/bit sequence integrity.

B

2.2.2.1

Yes

C.2.2.2.2.1(a) For the DS0 Category of service, CSDS shall support dialable information-payload bandwidth at the DS0 (i.e., 56 kb/s and 64 kb/s) data rate.

B

2.2.2.1.1

Yes

C.2.2.2.2.1(b) For the Multirate DS0 Category of service, CSDS shall support dialable information-payload bandwidth of 2 times DS0 data rates, 6 times DS0 data rate, and 12 times DS0 data rate.

B

2.2.2.1.1

Yes

C.2.2.2.2.1(c) For the DS1 Category of service, CSDS shall support dialable information-payload bandwidth at the DS1 (i.e., 1.536 Mb/s) data rate.

B

2.2.2.1.1

Yes

C.2.2.2.2.1 For a multirate (e.g., Multirate DS0 category), the contractor shall provide a dialing sequence for initiating calls with different bandwidths.

B

2.2.2.1.1

Yes

C.2.2.2.2.1 Once a call has been established by this dialing sequence, all bit sequences transmitted shall be transported as data/bit transparent.

B

2.2.2.1.1

Yes

C.2.2.2.2.2.1(a) 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.

B

2.2.2.2.1

Yes

C.2.2.2.2.2.1(a) 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

2.2.2.2.1

Yes

C.2.2.2.2.3(a)(1) All CSDS digital network transport transmission performance parameters for POP-to-POP connections 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

2.2.2.3

Yes

C.2.2.2.2.3(b)(1) The CSDS network transport transmission performance blockage (i.e., GOS) for POP-to-POP connections shall be 1 percent or less.

B

2.2.2.3

Yes





C.2.2.2.2.3(c)(1) The CSDS network transport transmission performance for POP-to-POP connections shall provide an availability of at least 99.8 percent.

B

2.2.2.3

Yes

C.2.2.2.2.4.1 (a)(1)

Pursuant to Section C.2.1.16, the contractor shall support/provide Dedicated Access at each POP via T1 and Fractional T1 with ESF. (Standard: Bellcore Pub: SR-TSV-002275; ANSI T1.102/107/403).

B

2.2.2.4.1

Yes

C.2.2.2.2.4.1 (a)(2)

Pursuant to Section C.2.1.16, the contractor shall support/provide Dedicated Access at each POP via ISDN PRI. (Standard: ANSI T1.607 and 610).

B

2.2.2.4.1

Yes

C.2.2.2.2.4.1 (a)(3)

Pursuant to Section C.2.1.16, the contractor shall support/provide Dedicated Access at each POP via T3 and Fractional T3 channelized (Standard: Bellcore Pub: GR-499-CORE).

B

2.2.2.4.1

Yes

C.2.2.2.2.4.1 (a)(4)

Pursuant to Section C.2.1.16, the contractor shall support/provide Dedicated Access at each POP via DS0 and Subrate DS0 (Bellcore Pub: SR-TSV-002275)

B

2.2.2.4.1

Yes

C.2.2.2.2.4.2 (a)(1)

Pursuant to Section C.2.1.16, the contractor shall support/provide Circuit Switched Access at each POP conforming to all applicable sections, related to LEC to IC/INC interconnections for CSSs, BOC Notes on the LEC Networks (Bellcore Pub: SR-TSV-002275).

B

2.2.2.4.2

Yes

C.2.2.2.2.4.2 (a)(2)

Pursuant to Section C.2.1.16, the contractor shall support/provide Circuit Switched Access at each POP conforming to Compatibility Information for Feature Group D Switched Access Service. (Bellcore Pub: TR-NPL-000258).

B

2.2.2.4.2

Yes

C.2.2.2.2.4.2 (a)(3)

Pursuant to Section C.2.1.16, the contractor shall support/provide Circuit Switched Access at each POP conforming to Exchange Access Interconnection. FSD 20-24-0000 (Bellcore Pub: GR-690-CORE).

B

2.2.2.4.2

Yes

C.2.2.2.2.4.2 (a)(4)

Pursuant to Section C.2.1.16, the contractor shall support/provide Circuit Switched Access at each POP conforming to Bellcore Specification of Signaling System Number 7. (Bellcore Pub: GR-246-CORE).

B

2.2.2.4.2

Yes

C.2.2.2.2.4.2 (a)(5)

Pursuant to Section C.2.1.16, the contractor shall support/provide Circuit Switched Access at each POP conforming to Bellcore Specification of Switched DS0

B Yes





(Bellcore Pub: SR-TSV-002275). 2.2.2.4.2

C.2.2.3.1.1 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.

B

2.3.1.1

Yes

C2.2.3.1.1 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.

B

2.3.1.1

Yes

C2.2.3.1.1 Pursuant to Section C.2.1.16, the contractor shall provide dedicated and switched access connections for the toll free service calls.

B

2.3.1.1

Yes

C2.2.3.1.1 Access connections shall connect the terminating POP with the toll free services on-net terminating locations.

B

2.3.1.1

Yes

C2.2.3.1.1 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.

B

2.3.1.1

Yes

C2.2.3.1.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.

B

2.3.1.1

Yes

C2.2.3.1.1 The contractor shall provide network intercept to recorded announcements as an inherent network capability when a

B Yes





call cannot be completed. 2.3.1.1

C2.2.3.1.1 At a minimum, such announcements shall be provided for time out during dialing.

B

2.3.1.1

Yes

C2.2.3.1.1 At a minimum, such announcements shall be provided for network congestion.

B

2.3.1.1

Yes

C2.2.3.1.1 At a minimum, such announcements shall be provided for denial of access to non-domestic calls.

B

2.3.1.1

Yes

C2.2.3.1.1 At a minimum, such announcements shall be provided for denial of access to features and other related conditions.

B

2.3.1.1

Yes

C2.2.3.1.1 As a default, the contractor shall provide a busy signal for all calls encountering network congestion and/or terminating egress congestion.

B

2.3.1.1

Yes

C.2.2.3.1.2.1 At a minimum, the toll free service access features Make Busy Arrangement shall be supported.

B

2.3.1.2

Yes

C.2.2.3.1.2.1(a) The Make Busy Arrangement 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.)

B

2.3.1.2.1

Yes

C.2.2.3.1.2.1(a) The contractor shall provide the subscribing agency with the capability of busying-out individual circuits within a trunk group or an entire trunk group.

B

2.3.1.2.1

Yes

C.2.2.3.1.2.1(a) The contractor shall provide an input system such that the subscribing agency shall have the capability of entering the needed information.

B

2.3.1.2.1

Yes

C.2.2.3.1.2.1(a) 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).

B

2.3.1.2.1

Yes

C.2.2.3.1.2.1(a) The contractor shall execute all subscribing agency entered requests within one hour.

B

2.3.1.2.1

Yes





C.2.2.3.1.2.1(a) The contractor shall be responsible for providing software necessary for the subscribing agency to utilize this feature on a subscribing agency-provided terminal.

B

2.3.1.2.1

Yes

C.2.2.3.1.3(a)(1) All analog transmission parameters for originating or terminating access connection between a POP and an SDP 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

2.3.1.3

Yes

C.2.2.3.1.3(a)(2) All digital transmission parameters for originating or terminating access connection between a POP and an SDP 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

2.3.1.3

Yes

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

B

2.3.1.3

Yes

C.2.2.3.1.3(c)(1) For toll free services access for originating or terminating access the performance of the connection between a POP and an SDP shall provide an availability of at least 99.8 percent.

B

2.3.1.3

Yes

C.2.2.3.1.3(d)(1) Post dialing delay shall not exceed best commercial practice

B

2.3.1.3

Yes

C.2.2.3.1.4.1.1 (a)(1)

The contractor shall support an Analog Line interface at the SDP at the call terminating end via two- and four-wire access circuits. (Standard: Bellcore’s BOC Notes on the LEC Networks [SR-TSV-002275]).

B

2.3.1.4.1.1

Yes

C.2.2.3.1.4.1.1 (b)(1)

The contractor shall support an Analog Trunk interface at the SDP at the call terminating end via two-wire loop start or ground start access circuits. (Standard: Bellcore’s BOC Notes on the LEC Networks [SR-TSV-002275]).

B

2.3.1.4.1.1

Yes

C.2.2.3.1.4.1.1 (b)(2)

The contractor shall support an Analog Trunk interface at the SDP at the call terminating end via four-wire E&M access circuits. (Standard: Bellcore’s BOC Notes on the LEC Networks [SR-TSV-002275]).

B

2.3.1.4.1.1

Yes

C.2.2.3.1.4.1.1 (c)(1)

The contractor shall support a Digital Trunk interface at the SDP at the call terminating end via T1 channelized

B Yes





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

2.3.1.4.1.1

C.2.2.3.1.4.1.1 (c)(2)

The contractor shall support a Digital Trunk interface at the SDP at the call terminating end via 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).

B

2.3.1.4.1.1

Yes

C.2.2.3.1.4.1.1 (c)(3)

The contractor shall support a Digital Trunk interface at the SDP at the call terminating end via SS7 Signaling Interface. (Standard: ANSI [T1. 110 through T1.116 and T1.611] and Bellcore GR-246-CORE).

B

2.3.1.4.1.1

Yes

C.2.2.3.1.4.1.1 (c)(4)

The contractor shall support a Digital Trunk interface at the SDP at the call terminating end via 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).

B

2.3.1.4.1.1

Yes


B

2.3.1.4.1.1

Yes

C.2.2.3.1.4.2.1 (a)(1)

Pursuant to Section C.2.1.16, the contractor shall support/provide Dedicated Access to connect to a POP via T1 and Fractional T1 channelized with ESF. (Standard: Bellcore Pub: SR-TSV-002275; ANSI T1.102/107/403).

B

2.3.1.4.2.1

Yes

C.2.2.3.1.4.2.1 (a)(2)


B

2.3.1.4.2.1

Yes

C.2.2.3.1.4.2.1 (a)(3)


B

2.3.1.4.2.1

Yes

C.2.2.3.1.4.2.1 (a)(4)

Pursuant to Section C.2.1.16, the contractor shall support/provide Dedicated Access to connect to a POP via Analog (Bellcore Pub: SR-TSV-002275).

B

2.3.1.4.2.1

Yes

C.2.2.3.1.4.2.2 (a)(1)

Pursuant to Section C.2.1.16, the contractor shall support/provide Circuit Switched Access to connect to a POP conforming to all applicable sections, related to LEC

B

2.3.1.4.2.2

Yes





to IC/INC interconnections for CSSs BOC Notes on the LEC Networks (Bellcore Pub: SR-TSV-002275).

C.2.2.3.1.4.2.2 (a)(2)


B

2.3.1.4.2.2

Yes

C.2.2.3.1.4.2.2 (a)(3)

Pursuant to Section C.2.1.16, the contractor shall support/provide Circuit Switched Access to connect to a POP conforming to Exchange Access Interconnection FSD 20-24-0000 (Bellcore Pub: GR-690-CORE).

B

2.3.1.4.2.2

Yes

C.2.2.3.1.4.2.2 (a)(4)


B

2.3.1.4.2.2

Yes

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

B

2.3.2.1

Yes

C.2.2.3.2.1 The toll free service shall comply with all Bellcore and ANSI standards, primarily Bellcore's BOC Notes on the LEC Networks, and ANSI ISDN and SS7 standards.

B

2.3.2.1

Yes

C.2.2.3.2.1 Pursuant to Section C.2.1.16, the contractor shall provide toll free service connections between the contractor’s listed POPs.

B

2.3.2.1

Yes

C.2.2.3.2.1 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.

B

2.3.2.1

Yes

C.2.2.3.2.1 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.

B

2.3.2.1

Yes

C.2.2.3.2.1 The toll free services shall be available from on-net and off-net locations.

B

2.3.2.1

Yes

C.2.2.3.2.1 For domestic services, numbering shall be consistent with B Yes





800, 888 and other toll free service access 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.

2.3.2.1

C.2.2.3.2.1 Therefore, the contractor shall accept, as a minimum, at any of its listed POPs which support the appropriate service, calls originating from the PSN.

B

2.3.2.1

Yes

C.2.2.3.2.1 The toll free service contractor shall accommodate the presently assigned Government 800 and 888 numbers.

B

2.3.2.1

Yes

C.2.2.3.2.1 It shall be possible to assign Government requested 800 and 888 “vanity” numbers (e.g., 1-800-CALLGSA), as available.

B

2.3.2.1

Yes

C.2.2.3.2.1 In addition, the contractor shall support toll free 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.

B

2.3.2.1

Yes

C.2.2.3.2.1 The toll free service contractor shall provide network intercept to recorded announcements as an inherent network capability when a call cannot be completed.

B

2.3.2.1

Yes

C.2.2.3.2.1 At a minimum, such intercept to recorded announcements shall be provided for time out during dialing.

B

2.3.2.1

Yes

C.2.2.3.2.1 At a minimum, such intercept to recorded announcements shall be provided for network congestion.

B

2.3.2.1

Yes

C.2.2.3.2.1 At a minimum, such intercept to recorded announcements shall be provided for denial of access to off-net and non-domestic calls.

B

2.3.2.1

Yes

C.2.2.3.2.1 At a minimum, such intercept to recorded announcements shall be provided for denial of access to features and other related conditions.

B

2.3.2.1

Yes

C.2.2.3.2.1 As a default, at the subscribing agency’s discretion the contractor shall provide a busy signal or recorded announcement for all calls encountering network

B

2.3.2.1

Yes





congestion and/or terminating egress congestion.

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

B

2.3.2.1

Yes

C.2.2.3.2.2 The toll free transport 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..

B

2.3.2.2

Yes

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

B

2.3.2.2.1

Yes

C.2.2.3.2.2.1(a) The toll free Number Assignment and Maintenance feature shall allow users to request assignment and maintenance of toll free numbers.

B

2.3.2.2.1.1

Yes

C.2.2.3.2.2.1(b) The Terminating Announcement 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 mot be a stand-alone feature.

B

2.3.2.2.1.2

Yes

C.2.2.3.2.2.1(b) The contractor shall provide capability for announcements up to two minutes in length.

B

2.3.2.2.1.2

Yes

C.2.2.3.2.2.1(b) Such announcements shall always be played from the beginning for each caller.

B

2.3.2.2.1.2

Yes

C.2.2.3.2.2.1(b) 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' terminals (e.g., Telecommunications Device for the Deaf [TDD]) designed to transmit/receive information

B

2.3.2.2.1.2

Yes





in Baudot or American Standard Code for Information Interchange/Teletypewriter (ASCII/TTY) code format.

C.2.2.3.2.2.1(c) The In-Route Announcements 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.

B

2.3.2.2.1.3

Yes

C.2.2.3.2.2.1(c) The contractor shall provide for all the capabilities associated with recorded announcements (see Section C.2.2.3.2.2.1(b)).

B

2.3.2.2.1.3

Yes

C.2.2.3.2.2.1(d) The Routing Control 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.

B

2.3.2.2.1.4

Yes

C.2.2.3.2.2.1(d) The contractor shall provide adequate security procedures that will prevent unauthorized access to this feature.

B

2.3.2.2.1.4

Yes

C.2.2.3.2.2.1(d) The contractor shall provide any hardware/software (e.g., terminal, modem) necessary to permit the user to utilize this feature.

B

2.3.2.2.1.4

Yes

C.2.2.3.2.2.1(d) Subscribing agencies shall have direct access to this feature a minimum of 20 hours a day, 7 days a week.

B

2.3.2.2.1.4

Yes

C.2.2.3.2.2.1(d) The feature shall be available with no break during the period from 6:00 AM to 12:00 midnight, local prevailing time.

B

2.3.2.2.1.4

Yes

C.2.2.3.2.2.1(d) The contractor shall support a minimum of 12 predefined alternative call routing plans for a subscribing agency.

B

2.3.2.2.1.4

Yes

C.2.2.3.2.2.1(d) Uploading of the 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.

B

2.3.2.2.1.4

Yes

C.2.2.3.2.2.1(e) The Dialed Number Identification feature shall permit a user with multiple toll free numbers in the same service group to identify electronically the specific toll free

B

2.3.2.2.1.5

Yes





number that was dialed by the calling party.

C.2.2.3.2.2.1(f) The Interactive Announcement/Response Arrangement feature shall be available 24-hours a day, 7 days a week.

B

2.3.2.2.1.6

Yes

C.2.2.3.2.2.1(f) This feature shall permit callers to hear generic or agency-specific information after dialing a toll free number.

B

2.3.2.2.1.6

Yes

C.2.2.3.2.2.1 (f)(1)

In conjunction with interactive prompting, the contractor shall provide a means for callers to select via DTMF signal, pre-recorded informational messages provided by the subscribing agency.

B

2.3.2.2.1.6

Yes

C.2.2.3.2.2.1 (f)(1)

The contractor shall provide capability for announcements up to two minutes in length.

B

2.3.2.2.1.6

Yes

C.2.2.3.2.2.1 (f)(1)

Such announcements shall always be played from the beginning for each caller.

B

2.3.2.2.1.6

Yes

C.2.2.3.2.2.1 (f)(1)

The contractor shall provide the capability to have the announcements recorded and stored in English and other languages after obtaining subscribing agency script approval.

B

2.3.2.2.1.6

Yes

C.2.2.3.2.2.1 (f)(2)

In conjunction with interactive prompting, the contractor shall provide a means for callers to leave caller information via DTMF signal or speech (e.g., names, addresses, account information, phone numbers, responses).

B

2.3.2.2.1.6

Yes

C.2.2.3.2.2.1 (f)(3)

In conjunction with interactive prompting, the contractor shall provide a means for callers to 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

B

2.3.2.2.1.6

Yes





discretion.

C.2.2.3.2.2.1(f)(3)

The contractor shall also provide a 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.

B

2.3.2.2.1.6

Yes

C.2.2.3.2.2.1(f)(3)

The matched street name shall then be spoken back to the caller to verify the correct address.

B

2.3.2.2.1.6

Yes

C.2.2.3.2.2.1(f) The contractor shall provide a means for verification of caller entered information.

B

2.3.2.2.1.6

Yes

C.2.2.3.2.2.1(f) 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.

B

2.3.2.2.1.6

Yes

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

B

2.3.2.2.1.6

Yes

C.2.2.3.2.2.1(f) 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.

B

2.3.2.2.1.6

Yes

C.2.2.3.2.2.1(g) The Percentage Routing 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.

B

2.3.2.2.1.7

Yes

C.2.2.3.2.2.1(h) The NPA/NXX Routing 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

B

2.3.2.2.1.8

Yes





subscriber specified location. Where NPA/NXX is not available, calls shall be routed to an agency defined default location.

C.2.2.3.2.2.1(i) The ANI-Based Routing feature shall permit calls to be routed based on the full ANI of the callers.

B

2.3.2.2.1.9

Yes

C.2.2.3.2.2.1(i) Default routing defined by the subscribing agency shall be used if ANI is not available.

B

2.3.2.2.1.9

Yes

C.2.2.3.2.2.1(j) The Time of Day Routing feature shall permit calls to be routed to different agency specified location 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.

B

2.3.2.2.1.10

Yes

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

B

2.3.2.2.1.11

Yes

C.2.2.3.2.2.1(l) The Command Routing 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.

B

2.3.2.2.1.12

Yes

C.2.2.3.2.2.1(l) 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.

B

2.3.2.2.1.12

Yes

C.2.2.3.2.2.1(l) The routing command shall be executed within 10 minutes of issuance.

B

2.3.2.2.1.12

Yes

C.2.2.3.2.2.1(l) The contractor shall provide adequate security procedures that can be used to prevent unauthorized activation of this feature.

B

2.3.2.2.1.12

Yes

C.2.2.3.2.2.1(l) The contractor shall also support a minimum of 12 predefined alternatives call routing plans for a subscribing agency.

B

2.3.2.2.1.12

Yes





C.2.2.3.2.2.1(m) The Cascade Routing 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.

B

2.3.2.2.1.13

Yes Non Domestic

C.2.2.3.2.2.1(m) 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.

B

2.3.2.2.1.13

Yes Non Domestic

C.2.2.3.2.2.1(m) Up to 99 such SDP locations shall be made available in a sequence to be defined by the subscribing agency.

B

2.3.2.2.1.13

Yes Non Domestic

C.2.2.3.2.2.1(m) 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.

B

2.3.2.2.1.13

Yes Non Domestic

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

B

2.3.2.2.1.14

Yes Non

Domestic

C.2.2.3.2.2.1(n) 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.

B

2.3.2.2.1.14

Yes Non

Domestic

C.2.2.3.2.2.1(n) 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.

B

2.3.2.2.1.14

Yes Non

Domestic

C.2.2.3.2.2.1(n) 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

B

2.3.2.2.1.14

Yes Non

Domestic





(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.2.2.3.2.2.1(n) 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

B

2.3.2.2.1.14

Yes Non

Domestic

C.2.2.3.2.2.1(n) 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.

B

2.3.2.2.1.14

Yes Non

Domestic

C.2.2.3.2.2.1(n) The Network Call Distribution Routing 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.

B

2.3.2.2.1.14

Yes Non

Domestic

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

B

2.3.2.2.1.14

Yes Non

Domestic

C.2.2.3.2.2.1(n) 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).

B

2.3.2.2.1.14

Yes Non

Domestic





C.2.2.3.2.2.1(n) 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.

B

2.3.2.2.1.14

Yes Non

Domestic

C.2.2.3.2.2.1(n) 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.

B

2.3.2.2.1.14

Yes Non

Domestic

C.2.2.3.2.2.1(n) The feature shall be offered in two versions:(22)Contractor-provided and contractor-based 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 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.

B

2.3.2.2.1.14

Yes Non

Domestic

C.2.2.3.2.2.1(n) 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.

B

2.3.2.2.1.14

Yes Non

Domestic

C.2.2.3.2.2.1(o) The Network Queuing feature 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.

B

2.3.2.2.1.15

Yes Non Domestic

C.2.2.3.2.2.1(o) Upon entering the queue, the caller shall hear an initial announcement.

B

2.3.2.2.1.15

Yes Non Domestic

C.2.2.3.2.2.1(o) The caller shall hear a reassurance announcement every 30 seconds after hearing the initial announcement.

B

2.3.2.2.1.15

Yes Non Domestic

C.2.2.3.2.2.1(o) 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.

B

2.3.2.2.1.15

Yes Non Domestic





C.2.2.3.2.2.1(o) The contractor shall be responsible for recording announcements after subscribing agency script approval.

B

2.3.2.2.1.15

Yes Non Domestic

C.2.2.3.2.2.1(p) Agency Based Routing Database 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.

B

2.3.2.2.1.16

Yes Non

Domestic

C.2.2.3.2.2.1(p) The contractor shall provide a call by call query to a subscribing agency provided call routing processor housed at the subscribing agency’s location.

B

2.3.2.2.1.16

Yes Non

Domestic

C.2.2.3.2.2.1(p) The query shall contain at a minimum:(1) The dialed toll-free number(2) The caller’s originating 10 digit number(3) The caller’s entered digits

B

2.3.2.2.1.16

Yes Non

Domestic

C.2.2.3.2.2.1(p) 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.

B

2.3.2.2.1.16

Yes Non

Domestic

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

B

2.3.2.2.1.16

Yes Non

Domestic

C.2.2.3.2.2.1(p) The feature shall be capable of processing up to 100 call inquiries per second per toll-free number without any degradation in performance.

B

2.3.2.2.1.16

Yes Non

Domestic

C.2.2.3.2.2.1(p) The contractor shall be responsible for providing any communications software necessary for the connection.

B

2.3.2.2.1.16

Yes Non

Domestic

C.2.2.3.2.2.1(p) 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.

B

2.3.2.2.1.16

Yes Non

Domestic

C.2.2.3.2.2.1(p) The agency’s routing processor will respond to a network query in 250 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.

B

2.3.2.2.1.16

Yes Non Domestic

C.2.2.3.2.2.1(q) The Call Redirection feature shall allow an incoming toll B Yes Non





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.

2.3.2.2.1.17

Domestic

C.2.2.3.2.2.1(q) The contractor shall provide for up to a minimum of 2,000 speed-dial codes for use of this feature.

B

2.3.2.2.1.17

Yes Non Domestic

C.2.2.3.2.2.1(r) The Call Prompter Routing feature shall allow callers to be routed to various network locations by dialing via DTMF or speaking specific route selection information.

B

2.3.2.2.1.18

Yes

C.2.2.3.2.2.1(r) 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.

B

2.3.2.2.1.18

Yes

C.2.2.3.2.2.1(r) The contractor shall support multi-tiered prompting such that another series of options can be provided to the caller after making the initial selection.

B

2.3.2.2.1.18

Yes

C.2.2.3.2.2.1(r) The contractor shall support a minimum of 8 options per tier and 3 tiers per call.

B

2.3.2.2.1.18

Yes

C.2.2.3.2.2.1(r) 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.

B

2.3.2.2.1.18

Yes

C.2.2.3.2.2.1(r) To accommodate callers with dial-pulse telephone sets, the contractor shall support speech recognition as a valid caller input.

B

2.3.2.2.1.18

Yes

C.2.2.3.2.2.1(r) The contractor shall support at a minimum, the all spoken numeric digits as well as “yes” and “no.”

B

2.3.2.2.1.18

Yes

C.2.2.3.2.2.1(r) English and Spanish language callers shall be supported. B

2.3.2.2.1.18

Yes

C.2.2.3.2.2.1(r) The contractor shall be able to accept and process at a minimum 95 percent of the above speech responses.

B

2.3.2.2.1.18

Yes





C.2.2.3.2.2.1(r) 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.

B

2.3.2.2.1.18

Yes

C.2.2.3.2.2.1(s) The Call Prompter Routing - Electronic Access 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.

B

2.3.2.2.1.19

Yes

C.2.2.3.2.2.1(s) This feature shall support callers' terminals (e.g., TDD) transmitting or receiving information in Baudot Code and/or ASCII formats.

B

2.3.2.2.1.19

Yes

C.2.2.3.2.2.1(t) The Call Status Report shall provide the subscribing agency with information about the status of calls placed to each toll free number.

B

2.3.2.2.1.20

Yes

C.2.2.3.2.2.1(t) The contractor shall provide this information on a daily, weekly, monthly, and quarterly basis.

B

2.3.2.2.1.20

Yes

C.2.2.3.2.2.1(t) Daily, weekly, monthly, and quarterly reports shall contain information summarized in 60 minute increments.

B

2.3.2.2.1.20

Yes

C.2.2.3.2.2.1(t) Multiple report formats shall be available which further summarize the information by time zone or subscribing agency region.

B

2.3.2.2.1.20

Yes

C.2.2.3.2.2.1(t) 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.

B

2.3.2.2.1.20

Yes

C.2.2.3.2.2.1(t) Unless affected by a weekend or 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.

B

2.3.2.2.1.20

Yes

C.2.2.3.2.2.1(t) 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])

B

2.3.2.2.1.20

Yes





C.2.2.3.2.2.1 (t)(1)

Each report shall contain standard information including the title of the report.

B

2.3.2.2.1.20

Yes

C.2.2.3.2.2.1 (t)(2)

Each report shall contain standard information including the date of the report.

B

2.3.2.2.1.20

Yes

C.2.2.3.2.2.1 (t)(3)

Each report shall contain standard information including the period covered by the report.

B

2.3.2.2.1.20

Yes

C.2.2.3.2.2.1 (t)(4)

Each report shall contain standard information including name of the subscribing agency.

B

2.3.2.2.1.20

Yes

C.2.2.3.2.2.1 (t)(5)

Each report shall contain standard information including the toll free number.

B

2.3.2.2.1.20

Yes

C.2.2.3.2.2.1 (t)(6)

For any given toll free number, the contractor shall, at a minimum, provide information within the reports for the number of calls from each area code that dialed the toll free number (i.e., call attempts).

B

2.3.2.2.1.20

Yes

C.2.2.3.2.2.1 (t)(7)(i)

For any given toll free number, the contractor shall, at a minimum, provide information within the reports for the number of calls and the percentage of all calls that encounter a busy signal (i.e., that are blocked) in the contractor’s network.

B

2.3.2.2.1.20

Yes

C.2.2.3.2.2.1 (t)(7)(ii)

For any given toll free number, the contractor shall, at a minimum, provide information within the reports for the number of calls and the percentage of all calls that encounter a busy signal (i.e., that are blocked) at the user’s terminating access.

B

2.3.2.2.1.20

Yes

C.2.2.3.2.2.1 (t)(8)

For any given toll free number, the contractor shall, at a minimum, provide information within the reports for the number of calls offered to the user’s terminating access (i.e., egress trunk group).

B

2.3.2.2.1.20

Yes

C.2.2.3.2.2.1 (t)(9)

For any given toll free number, the contractor shall, at a minimum, provide information within the reports for the number of calls received at each user’s terminating access.

B

2.3.2.2.1.20

Yes

C.2.2.3.2.2.1 (t)(10)

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

B Yes





number of received calls at each user’s terminating access that resulted in successful answerback supervision.

2.3.2.2.1.20

C.2.2.3.2.2.1 (t)(11)

For any given toll free number, the contractor shall, at a minimum, provide information within the reports for the average duration of calls answered at each user’s terminating access.

B

2.3.2.2.1.20

Yes

C.2.2.3.2.2.1 (t)(12)

For any given toll free number, the contractor shall, at a minimum, provide information within the reports for the average duration of all calls answered for a given toll free number at all users terminating access serving the toll free number.

B

2.3.2.2.1.20

Yes

C.2.2.3.2.2.1 (t)(13)

For any given toll free number utilizing Call Prompter Access, the contractor shall, at a minimum, provide information within the reports for the number of calls offered to the call prompter.

B

2.3.2.2.1.20

Yes

C.2.2.3.2.2.1 (t)(14)

For any given toll free number utilizing Call Prompter Access, the contractor shall, at a minimum, provide information within the reports for the number of calls to the call prompter that were abandoned without making a selection.

B

2.3.2.2.1.20

Yes

C.2.2.3.2.2.1 (t)(15)

For any given toll free number utilizing Call Prompter Access, the contractor shall, at a minimum, provide information within the reports for the average duration of all calls while in the caller prompter.

B

2.3.2.2.1.20

Yes

C.2.2.3.2.2.1 (t)(16)

For any given toll free number utilizing Call Prompter Access, the contractor shall, at a minimum, provide information within the reports for the number and percentage of calls selecting each option.

B

2.3.2.2.1.20

Yes

C.2.2.3.2.2.1 (t)(17)

For any given toll free number utilizing Interactive Announcement/Response Arrangement (IA/RA), the contractor shall, at a minimum, provide information within the reports by application for the number of calls offered to the IA/RA.

B

2.3.2.2.1.20

Yes

C.2.2.3.2.2.1 (t)(18)

For any given toll free number utilizing Interactive Announcement/Response Arrangement (IA/RA), the contractor shall, at a minimum, provide information within the reports by application for the number of calls completed (i.e., successfully accessing) to the IA/RA.

B

2.3.2.2.1.20

Yes





C.2.2.3.2.2.1 (t)(19)

For any given toll free number utilizing Interactive Announcement/Response Arrangement (IA/RA), the contractor shall, at a minimum, provide information within the reports by application for the number and percentage of calls completed to the IA/RA but abandoned.

B

2.3.2.2.1.20

Yes

C.2.2.3.2.2.1 (t)(20)

For any given toll free number utilizing Interactive Announcement/Response Arrangement (IA/RA), the contractor shall, at a minimum, provide information within the reports by application for the number and percentage of calls selecting each option.

B

2.3.2.2.1.20

Yes

C.2.2.3.2.2.1 (t)(21)

For any given toll free number utilizing Interactive Announcement/Response Arrangement (IA/RA), the contractor shall, at a minimum, provide information within the reports by application for the average duration of calls selecting each option.

B

2.3.2.2.1.20

Yes

C.2.2.3.2.2.1 (t)(22)

For any given toll free number utilizing Terminating Announcement or In-Route Announcements, the contractor shall, at a minimum, provide the information within the reports for the number of calls offered to the announcement.

B

2.3.2.2.1.20

Yes

C.2.2.3.2.2.1 (t)(23)

For any given toll free number utilizing Terminating Announcement or In-Route Announcements, the contractor shall, at a minimum, provide the information within the reports for the number of calls blocked at the announcement.

B

2.3.2.2.1.20

Yes

C.2.2.3.2.2.1 (t)(24)

For any given toll free number utilizing Terminating Announcement or In-Route Announcements, the contractor shall, at a minimum, provide the information within the reports for the number of calls completed in the announcement.

B

2.3.2.2.1.20

Yes

C.2.2.3.2.2.1 (t)(25)

For any given toll free number utilizing Terminating Announcement or In-Route Announcements, the contractor shall, at a minimum, provide the information within the reports for the average duration of calls to each announcement.

B

2.3.2.2.1.20

Yes

C.2.2.3.2.2.1 (t)(26)

For any given toll free numbers utilizing In-Route Announcements, the contractor shall, at a minimum, provide information within the reports for the number of abandoned calls for In-Route Announcements.

B

2.3.2.2.1.20

Yes





C.2.2.3.2.2.1 (t)(27)

For any given toll free number utilizing Cascade Routing, the contractor shall, at a minimum, provide information within the reports for the number of calls that were rerouted to an alternate SDP (Cascade Routing) or toll free service group (Alternate Routing).

B

2.3.2.2.1.20

Yes

C.2.2.3.2.2.1 (u)(1)

For Lost Callers, the Caller Profile Report, at a minimum, shall enumerate the number of callers who never called back after an incomplete attempt during the reporting period.

B

2.3.2.2.1.21

Yes

C.2.2.3.2.2.1 (u)(2)

For the Average Number of Attempts Per Caller, the Caller Profile Report shall provide, at a minimum, the grand total number of call attempts divided by the number of first call attempts during the reporting period.

B

2.3.2.2.1.21

Yes

C.2.2.3.2.2.1 (u)(3)

For the Average Number of Contacts Per Caller, the Caller Profile Report shall provide, at a minimum, the number of attempts generated from each telephone number on average during this reporting period. This average 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.

B

2.3.2.2.1.21

Yes

C.2.2.3.2.2.1 (u)(4)

For the 50 Percent of Successful Attempts Within 1,000 Calls, the Caller Profile Report shall provide, at a minimum, the number of attempts it took to access the network for 50 percent of the callers who completed.

B

2.3.2.2.1.21

Yes

C.2.2.3.2.2.1 (u)(5)


B

2.3.2.2.1.21

Yes

C.2.2.3.2.2.1 (u) 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)

B

2.3.2.2.1.21

Yes

C.2.2.3.2.2.1(v) The Caller Information Report provides information about the ANI of all callers to a given toll free number.

B Yes





2.3.2.2.1.22

C.2.2.3.2.2.1(v) 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.

B

2.3.2.2.1.22

Yes

C.2.2.3.2.2.1(v) Zeroes shall be substituted in place of any missing digits. B

2.3.2.2.1.22

Yes

C.2.2.3.2.2.1 (v)(1)

For any given toll free number, the contractor shall, at a minimum, provide the date of call for each call within the Caller Information Report.

B

2.3.2.2.1.22

Yes

C.2.2.3.2.2.1 (v)(2)

For any given toll free number, the contractor shall, at a minimum, provide the time of call (expressed using a 24 hour clock or a 12 hour clock with an AM/PM indicator, eastern prevailing time) for each call within the Caller Information Report.

B

2.3.2.2.1.22

Yes

C.2.2.3.2.2.1 (v)(3)

For any given toll free number, the contractor shall, at a minimum, provide the ANI of caller (if available) for each call within the Caller Information Report.

B

2.3.2.2.1.22

Yes

C.2.2.3.2.2.1 (v)(4)

For any given toll free number, the contractor shall, at a minimum, provide the dialed (i.e., destination) 10 digit number for each call within the Caller Information Report.

B

2.3.2.2.1.22

Yes

C.2.2.3.2.2.1 (v)(5)

For any given toll free number, the contractor shall, at a minimum, provide the duration of call (to the nearest 6 seconds) for each call within the Caller Information Report.

B

2.3.2.2.1.22

Yes

C.2.2.3.2.2.1 (v)(6)(i)

For any given toll free number, the contractor shall, at a minimum, provide the disposition of call (i.e., using an alpha or numeric code) to include, at a minimum, call blocked within contractor’s network for each call within the Caller Information Report.

B

2.3.2.2.1.22

Yes

C.2.2.3.2.2.1 (v)(6)(ii)

For any given toll free number, the contractor shall, at a minimum, provide the disposition of call (i.e., using an alpha or numeric code) to include, at a minimum, call blocked at user’s terminating access for each call within the Caller Information Report.

B

2.3.2.2.1.22

Yes

C.2.2.3.2.2.1 (v) For any given toll free number, the contractor shall, at a B Yes





(6)(iii) minimum, provide the disposition of call (i.e., using an alpha or numeric code) to include, at a minimum, call completed to user’s terminating access for each call within the Caller Information Report.

2.3.2.2.1.22

C.2.2.3.2.2.1 (v)(6)(iv)

For any given toll free number, the contractor shall, at a minimum, provide the disposition of call (i.e., using an alpha or numeric code) to include, at a minimum, other (e.g., caller abandoned enroute to user’s terminating access, no answer back supervision received, etc.) for each call within the Caller Information Report.

B

2.3.2.2.1.22

Yes

C.2.2.3.2.2.1(v) The contractor shall provide the information in the Caller Information Report on a daily basis

B

2.3.2.2.1.22

Yes

C.2.2.3.2.2.1(v) The contractor shall present the information in the Caller Information Report chronologically sequenced .

B

2.3.2.2.1.22

Yes

C.2.2.3.2.2.1(v) Unless affected by a weekend or 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)

B

2.3.2.2.1.22

Yes

C.2.2.3.2.2.1(w) For the 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:(1) Network Data Mover™ (using SNA/SNI)

B

2.3.2.2.1.23

Yes

C.2.2.3.2.2.1(x) The Real-Time Call Status feature shall permit the user to receive information about the status of the calls in

B Yes





progress on a near real-time (e.g., refreshed within five minutes) basis.

2.3.2.2.1.24

C.2.2.3.2.2.1(x) The contractor shall provide all necessary hardware/software (including terminals) to provide this information in a graphical format to the subscribing agency.

B

2.3.2.2.1.24

Yes

C.2.2.3.2.2.1 (x)(1)

At a minimum, the contractor shall provide the number of calls from each area code who have dialed a given toll free number.

B

2.3.2.2.1.24

Yes

C.2.2.3.2.2.1 (x)(2)

At a minimum, the contractor shall provide the number of calls directed to a subscribing agency’s terminating SDP.

B

2.3.2.2.1.24

Yes

C.2.2.3.2.2.1 (x)(3)

At a minimum, the contractor shall provide the number of calls directed to a subscribing agency’s terminating SDP(s) that could not be completed (i.e., connected to the users premises equipment) due to an All-Trunks-Busy (ATB) condition.

B

2.3.2.2.1.24

Yes

C.2.2.3.2.2.1 (x)(4)

At a minimum, the contractor shall provide the percentage of trunks busy at a users terminating SDP.

B

2.3.2.2.1.24

Yes

C.2.2.3.2.2.1 (x)(5)

At a minimum, the contractor shall provide any other reports or information available to commercial users.

B

2.3.2.2.1.24

Yes

C.2.2.3.2.2.1(y) The Operator Connect Bridging 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.

B

2.3.2.2.1.25

Yes

C.2.2.3.2.2.1(y) The contractor’s operator shall assist the caller in reaching an agency location based on agency predetermined default routing.

B

2.3.2.2.1.25

Yes

C.2.2.3.2.2.1(z) The FAX Catalog 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.

B

2.3.2.2.1.26

Yes

C.2.2.3.2.2.1(z) 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

B

2.3.2.2.1.26

Yes





(e.g., a FAX machine or a PC equipped with FAX modem).

C.2.2.3.2.2.1(z) Once a document is stored in the FAX catalog, it shall be immediately made available to the callers for retrieval.

B

2.3.2.2.1.26

Yes

C.2.2.3.2.2.1(z) 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.

B

2.3.2.2.1.26

Yes

C.2.2.3.2.2.1(z) The contractor shall FAX requested document(s) within one hour after the call.

B

2.3.2.2.1.26

Yes

C.2.2.3.2.2.1(z) 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).

B

2.3.2.2.1.26

Yes

C.2.2.3.2.2.1(z) Each FAX shall include a cover sheet, which could be customized to include an agency logo, to be defined at service ordering time.

B

2.3.2.2.1.26

Yes

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

B

2.3.2.2.1.27

Yes Non Domestic

C.2.2.3.2.2.1 (bb) The Service Assurance Rerouting 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.

B

2.3.2.2.1.28

Yes Non Domestic

C.2.2.3.2.3 (a)(1) All digital transport transmission parameters for POP-to-POP connections 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

2.3.2.3

Yes

C.2.2.3.2.3 (b)(1) The digital transport transmission performance for blockage (i.e., GOS) for POP-to-POP connections shall 1 percent or less.

B

2.3.2.3

Yes

C.2.2.3.2.3 (c)(1) The digital transport transmission performance for toll B Yes





free services for POP-to-POP connections shall provide an availability of at least 99.8 percent.

2.3.2.3

C.2.2.3.2.3 (d)(1) The digital transport transmission performance for post-dialing delay for POP-to-POP connection shall not exceed best commercial practice.

B

2.3.2.3

Yes

C.2.2.3.2.4.1.1 (a)(1)

Pursuant to Section C.2.1.16 and for Dedicated Access, the contractor shall support/provide at each POP the LANI via T1 and Fractional T1 channelized with ESF. (Standard: Bellcore Pubs: SR-TSV-002275; ANSI T1.102/107/403).

B

2.3.2.4.1.1

Yes

C.2.2.3.2.4.1.1 (a)(2)

Pursuant to Section C.2.1.16 and for Dedicated Access, the contractor shall support/provide at each POP the LANI via ISDN PRI. (Standard: ANSI T1.607 and 610).

B

2.3.2.4.1.1

Yes

C.2.2.3.2.4.1.1 (a)(3)

Pursuant to Section C.2.1.16 and for Dedicated Access, the contractor shall support/provide at each POP the LANI via T3 and Fractional T3 channelized. (Standard: Bellcore Pub: GR-499-CORE).

B

2.3.2.4.1.1

Yes

C.2.2.3.2.4.1.2 (a)(1)

Pursuant to Section C.2.1.16 and for Circuit Switched Access, the contractor shall support/provide at each POP the LANI conforming to all applicable sections, related to LEC to IC/INC interconnections for CSSs. BOC Notes on the LEC Networks (Bellcore Pub: SR-TSV-002275).

B

2.3.2.4.1.2

Yes

C.2.2.3.2.4.1.2 (a)(2)

Pursuant to Section C.2.1.16 and for Circuit Switched Access, the contractor shall support/provide at each POP the LANI conforming to Compatibility Information for Feature Group D Switched Access Service. (Bellcore Pub: TR-NPL-00258).

B

2.3.2.4.1.2

Yes

C.2.2.3.2.4.1.2 (a)(3)

Pursuant to Section C.2.1.16 and for Circuit Switched Access, the contractor shall support/provide at each POP the LANI conforming to Exchange Access Interconnection. FSD 20-24-0000 (Bellcore Pub: GR-690-CORE).

B

2.3.2.4.1.2

Yes

C.2.2.3.2.4.1.2 (a)(4)

Pursuant to Section C.2.1.16 and for Circuit Switched Access, the contractor shall support/provide at each POP the LANI Bellcore Specification of Signaling System Number 7. (Bellcore Pub: GR-246-CORE).

B

2.3.2.4.1.2

Yes

C.2.2.4.1.1 The 900 service shall allow the public to be connected from off-net locations to predesignated users and

B Yes





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 or answering agents.

2.4.1.1

C.2.2.4.1.1 The information to be provided by 900 service call handling equipment could be passive, interactive, opinion polls or database access by callers.

B

2.4.1.1

Yes

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

B

2.4.1.1

Yes

C.2.2.4.1.1 Pursuant to Section C.2.1.16, the contractor shall provide dedicated access connections for the 900 service calls.

B

2.4.1.1

Yes

C.2.2.4.1.1 Access connections shall connect the terminating POP with the 900 service on-net terminating locations.

B

2.4.1.1

Yes

C.2.2.4.1.1 Terminating access for 900 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 facsimile 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 these equipment types are defined in Section C.2.2.4.1.4.1.

B

2.4.1.1

Yes

C.2.2.4.1.1 The contractor shall provide network intercept to recorded announcements as an inherent network capability when a call cannot be completed.

B

2.4.1.1

Yes

C.2.2.4.1.1 At a minimum, such announcements shall be provided for B Yes





time out during dialing. 2.4.1.1

C.2.2.4.1.1 At a minimum, such announcements shall be provided for network congestion.

B

2.4.1.1

Yes

C.2.2.4.1.1 At a minimum, such announcements shall be provided for denial of access to non-domestic calls.

B

2.4.1.1

Yes

C.2.2.4.1.1 At a minimum, such announcements shall be provided for denial of access to features and other related conditions.

B

2.4.1.1

Yes

C.2.2.4.1.1 As a default, the contractor shall provide a busy signal for all calls encountering network congestion and/or terminating egress congestion.

B

2.4.1.1

Yes

C.2.2.4.1.3(a)(1) All analog transmission parameters for originating or terminating access connection between a POP and an SDP 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

2.4.1.3

Yes

C.2.2.4.1.3(a)(2) All digital transmission parameters for originating or terminating access connection between a POP and an SDP 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

2.4.1.3

Yes

C.2.2.4.1.3(b)(1) For Switched and Dedicated - Class 2 access arrangement trunk groups, the blockage (i.e., GOS) for originating or terminating access connection between a POP and an SDP for 900 service shall be 3 percent or less.

B

2.4.1.3

Yes

C.2.2.4.1.3(c)(1) For 900 service access for originating or terminating access the performance of the connection between a POP and an SDP shall provide an availability of at least 99.8 percent.

B

2.4.1.3

Yes

C.2.2.4.1.3(d)(1) Post-dialing delay for originating or terminating access connection between a POP and an SDP shall not exceed best commercial practice.

B

2.4.1.3

Yes

C.2.2.4.1.4.1.1 (a)(1)

The contractor shall support an analog interface at the SDP at the call terminating end via two- and four-wire access circuits. (Standard: Bellcore’s BOC Notes on the

B

2.4.1.4.1.1

Yes





Intra-LEC Networks [SR-TSV-002275]).

C.2.2.4.1.4.1.1 (b)(1)

The contractor shall support an analog interface at the SDP at the call terminating end via two-wire loop start or ground start access circuits. (Standard: Bellcore’s BOC Notes on the LEC Networks [SR-TSV-002275]).

B

2.4.1.4.1.1

Yes

C.2.2.4.1.4.1.1 (b)(2)

The contractor shall support an analog interface at the SDP at the call terminating end via four-wire E&M access circuits. (Standard: Bellcore’s BOC Notes on the LEC Networks [SR-TSV-002275]).

B

2.4.1.4.1.1

Yes

C.2.2.4.1.4.1.1 (c)(1)

The contractor shall support a digital interface at the SDP at the call terminating end via 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).

B

2.4.1.4.1.1

Yes

C.2.2.4.1.4.1.1 (c)(2)

The contractor shall support a digital interface at the SDP at the call terminating end via 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).

B

2.4.1.4.1.1

Yes

C.2.2.4.1.4.1.1 (c)(3)

The contractor shall support a digital interface at the SDP at the call terminating end via 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).

B

2.4.1.4.1.1

Yes


B

2.4.1.4.1.1

Yes

C.2.2.4.1.4.2.1 (a)(1)

Pursuant to Section C.2.1.16, the contractor shall support/provide Dedicated Access to connect to a POP via T1 and Fractional T1 channelized with ESF. (Standard: Bellcore Pub: SR-TSV-002275; ANSI T1.102/107/403).

B

2.4.1.4.2.1

Yes

C.2.2.4.1.4.2.1 (a)(2)


B

2.4.1.4.2.1

Yes





C.2.2.4.1.4.2.1 (a)(3)


B

2.4.1.4.2.1

Yes

C.2.2.4.1.4.2.1 (a)(4)

Pursuant to Section C.2.1.16, the contractor shall support/provide Dedicated Access to connect to a POP via analog. (Bellcore Pub: SR-TSV-002275).

B

2.4.1.4.2.1

Yes

C.2.2.4.2.1 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.

B

2.4.2.1

Yes

C.2.2.4.2.1 The information to be provided by 900 service call handling equipment could be passive, interactive, opinion polls and database access from callers.

B

2.4.2.1

Yes

C.2.2.4.2.1 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.

B

2.4.2.1

Yes

C.2.2.4.2.1 Pursuant to Section C.2.1.16, the contractor shall provide 900 service connections between the contractor’s listed POPs.

B

2.4.2.1

Yes

C.2.2.4.2.1 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.

B

2.4.2.1

Yes

C.2.2.4.2.1 The 900 service shall be available from off-net locations. B

2.4.2.1

Yes

C.2.2.4.2.1 Therefore, the contractor shall accept, as a minimum, at any of its listed POPs which support the appropriate service, calls originating from the PSN.

B

2.4.2.1

Yes

C.2.2.4.2.1 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.

B

2.4.2.1

Yes





C.2.2.4.2.1 When the capability is commercially available from the contractor, the contractor shall accommodate the Federal Government's currently assigned 900 numbers.

B

2.4.2.1

Yes

C.2.2.4.2.1 Call charges to callers shall begin at a time set by agreement with the agency.

B

2.4.2.1

Yes

C.2.2.4.2.1 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).

B

2.4.2.1

Yes

C.2.2.4.2.1 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.

B

2.4.2.1

Yes

C.2.2.4.2.2 The 900 service transport features in Section C.2.2.4.2.2 shall be supported.

B

2.4.2.2

Yes

C.2.2.4.2.2 The 900 service transport features shall be capable of being used independently of each other or in any combination, except where noted.

B

2.4.2.2

Yes

C.2.2.4.2.2 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.

B

2.4.2.2

Yes

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

B

2.4.2.2.1

Yes

C.2.2.4.2.2.1(a) The 900 Number Assignment and Maintenance feature shall allow users to request assignment and maintenance

B Yes





of 900 numbers. 2.4.2.2.1.1

C.2.2.4.2.2.1(b) 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.

B

2.4.2.2.1.2

Yes

C.2.2.4.2.2.1(b) The contractor shall be responsible for recording the preamble message after obtaining Government approval of scripts.

B

2.4.2.2.1.2

Yes

C.2.2.4.2.2.1(c) The Terminating Announcement 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.

B

2.4.2.2.1.3

Yes

C.2.2.4.2.2.1(c) The contractor shall provide capability for announcements up to two minutes in length.

B

2.4.2.2.1.3

Yes

C.2.2.4.2.2.1(c) Such announcements shall always be played from the beginning for each caller.

B

2.4.2.2.1.3

Yes

C.2.2.4.2.2.1(c) 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' terminals (e.g., Telecommunications Device for the Deaf [TDD]) designed to transmit/receive information in Baudot or ASCII/TTY code formats.

B

2.4.2.2.1.3

Yes

C.2.2.4.2.2.1(d) The Dialed Number Identification 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.

B

2.4.2.2.1.4

Yes

C.2.2.4.2.2.1(e) The Interactive Announcement/Response Arrangement feature shall be available 24-hours a day, 7 days a week.

B

2.4.2.2.1.5

Yes

C.2.2.4.2.2.1(e) This feature shall permit users to provide agency-specific dial-up information to callers dialing a 900 number.

B

2.4.2.2.1.5

Yes

C.2.2.4.2.2.1 (e) In conjunction with interactive prompting, the contractor B Yes





(1) shall provide a means for callers to select via DTMF signal, pre-recorded informational messages provided by the subscribing agency.

2.4.2.2.1.5

C.2.2.4.2.2.1 (e)(2)

In conjunction with interactive prompting, the contractor shall provide a means for callers to leave caller information via DTMF signal or speech (e.g., names, addresses, account information, phone numbers, responses).

B

2.4.2.2.1.5

Yes

C.2.2.4.2.2.1 (e)(3)

In conjunction with interactive prompting, the contractor shall provide a means for callers to 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.

B

2.4.2.2.1.5

Yes

C.2.2.4.2.2.1(e)(3)

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.

B

2.4.2.2.1.5

Yes

C.2.2.4.2.2.1(e)(3)

The matched street name shall then be spoken back to the caller to verify the correct address.

B

2.4.2.2.1.5

Yes

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

B

2.4.2.2.1.5

Yes

C.2.2.4.2.2.1(e) 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 format.

B

2.4.2.2.1.5

Yes

C.2.2.4.2.2.1(f) The Percentage Routing 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.

B

2.4.2.2.1.6

Yes

C.2.2.4.2.2.1(g) The NPA/NXX Routing feature shall permit calls originating from within agency subscriber-selected

B Yes





geographic areas, defined by one or more NPAs and/or NPA/NXX combinations, to be routed to an agency subscriber specified location.

2.4.2.2.1.7

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

B

2.4.2.2.1.8

Yes

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

B

2.4.2.2.1.9

Yes

C.2.2.4.2.2.1(j) The Command Routing 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.

B

2.4.2.2.1.10

Yes

C.2.2.4.2.2.1(j) 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.

B

2.4.2.2.1.10

Yes

C.2.2.4.2.2.1(j) The routing command shall be executed within 10 minutes of issuance.

B

2.4.2.2.1.10

Yes

C.2.2.4.2.2.1(j) The contractor shall provide adequate security procedures that can be used to prevent unauthorized activation of this feature.

B

2.4.2.2.1.10

Yes

C.2.2.4.2.2.1(j) The contractor shall also support a minimum of 12 predefined routing alternatives that can be accommodated by this feature.

B

2.4.2.2.1.10

Yes

C.2.2.4.2.2.1(k) The Call Status Report shall provide the subscribing agency with information about the status of calls placed to each 900 number.

B

2.4.2.2.1.11

Yes

C.2.2.4.2.2.1(k) The contractor shall provide this information on a daily, weekly, monthly, and quarterly basis.

B

2.4.2.2.1.11

Yes

C.2.2.4.2.2.1(k) Daily, weekly, monthly, and quarterly reports shall contain information summarized in 60 minute increments.

B Yes





2.4.2.2.1.11

C.2.2.4.2.2.1(k) Multiple report formats shall be available which further summarize the information by time zone or subscribing agency region.

B

2.4.2.2.1.11

Yes

C.2.2.4.2.2.1(k) Call time indicators within the report will be set to Eastern Prevailing Time with presentation of hours using a 24 hour clock or a 12 hour clock with an AM/PM indicator..

B

2.4.2.2.1.11

Yes

C.2.2.4.2.2.1(k) Unless affected by a weekend or 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.

B

2.4.2.2.1.11

Yes

C.2.2.4.2.2.1 (k)(1)

Each report shall contain standard information including the title of the report.

B

2.4.2.2.1.11

Yes

C.2.2.4.2.2.1 (k)(2)

Each report shall contain standard information including the date of the report.

B

2.4.2.2.1.11

Yes

C.2.2.4.2.2.1 (k)(3)

Each report shall contain standard information including the period covered by the report.

B

2.4.2.2.1.11

Yes

C.2.2.4.2.2.1 (k)(4)

Each report shall contain standard information including name of the subscribing agency.

B

2.4.2.2.1.11

Yes

C.2.2.4.2.2.1 (k)(5)

Each report shall contain standard information including the 900 number.

B

2.4.2.2.1.11

Yes

C.2.2.4.2.2.1 (k)(6)

For any given 900 number, the contractor shall, at a minimum, provide information within the reports for the number of calls from each area code that dialed the 900 number (i.e., call attempts).

B

2.4.2.2.1.11

Yes

C.2.2.4.2.2.1 (k)(7)(i)

For any given 900 number, the contractor shall, at a minimum, provide information within the reports for the number of calls that encounter a busy signal (i.e., that are blocked) in the contractor’s network.

B

2.4.2.2.1.11

Yes

C.2.2.4.2.2.1 (k)(7)(ii)

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

B Yes





number of calls that encounter a busy signal (i.e., that are blocked) at the user’s terminating access.

2.4.2.2.1.11

C.2.2.4.2.2.1 (k)(8)

For any given 900 number, the contractor shall, at a minimum, provide information within the reports for the number of calls offered to the user’s terminating access (i.e., egress trunk group).

B

2.4.2.2.1.11

Yes

C.2.2.4.2.2.1 (k)(9)

For any given 900 number, the contractor shall, at a minimum, provide information within the reports for the number of calls received at each user’s terminating access.

B

2.4.2.2.1.11

Yes

C.2.2.4.2.2.1 (k)(10)

For any given 900 number, the contractor shall, at a minimum, provide information within the reports for the number of received calls at each user’s terminating access that resulted in successful answer-back supervision.

B

2.4.2.2.1.11

Yes

C.2.2.4.2.2.1 (k)(11)

For any given 900 number, the contractor shall, at a minimum, provide information within the reports for the average duration of calls answered at each user’s terminating access.

B

2.4.2.2.1.11

Yes

C.2.2.4.2.2.1 (k)(12)

For any given 900 number, the contractor shall, at a minimum, provide information within the reports for the average duration of all calls answered for a given 900 number at all users terminating access serving the 900 number.

B

2.4.2.2.1.11

Yes

C.2.2.4.2.2.1 (k)(13)

For any given 900 number utilizing Interactive Announcement/Response Arrangement (IA/RA), the contractor shall, at a minimum, provide information within the reports by application for the number of calls offered to the IA/RA.

B

2.4.2.2.1.11

Yes

C.2.2.4.2.2.1 (k)(14)

For any given 900 number utilizing Interactive Announcement/Response Arrangement (IA/RA), the contractor shall, at a minimum, provide information within the reports by application for the number of calls completed (i.e., successfully accessing) to the IA/RA.

B

2.4.2.2.1.11

Yes

C.2.2.4.2.2.1 (k)(15)

For any given 900 number utilizing Interactive Announcement/Response Arrangement (IA/RA), the contractor shall, at a minimum, provide information within the reports by application for the number and percentage of calls completed to the IA/RA but abandoned.

B

2.4.2.2.1.11

Yes





C.2.2.4.2.2.1 (k)(16)

For any given 900 number utilizing Interactive Announcement/Response Arrangement (IA/RA), the contractor shall, at a minimum, provide information within the reports by application for the number and percentage of calls selecting each option.

B

2.4.2.2.1.11

Yes

C.2.2.4.2.2.1 (k)(17)

For any given 900 number utilizing Interactive Announcement/Response Arrangement (IA/RA), the contractor shall, at a minimum, provide information within the reports by application for the average duration of calls selecting each option.

B

2.4.2.2.1.11

Yes

C.2.2.4.2.2.1 (k)(18)

For any given 900 number utilizing Terminating Announcement, the contractor shall, at a minimum, provide the information within the reports for the number of calls offered to the announcement.

B

2.4.2.2.1.11

Yes

C.2.2.4.2.2.1 (k)(19)

For any given 900 number utilizing Terminating Announcement, the contractor shall, at a minimum, provide the information within the reports for the average duration of calls to each announcement.

B

2.4.2.2.1.11

Yes

C.2.2.4.2.2.1 (l)(1)

For Lost Callers, the Caller Profile Report, at a minimum, shall enumerate the number of callers who never called back after an incomplete attempt during the reporting period.

B

2.4.2.2.1.12

Yes

C.2.2.4.2.2.1 (l)(2)

For the Average Number of Attempts Per Caller, the Caller Profile Report shall provide, at a minimum, the grand total number of call attempts divided by the number of first call attempts during the reporting period.

B

2.4.2.2.1.12

Yes

C.2.2.4.2.2.1 (l)(3)

For the Average Number of Contacts Per Caller, the Caller Profile Report shall provide, at a minimum, the number of attempts generated from each telephone number on average during this reporting period. This average 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.

B

2.4.2.2.1.12

Yes

C.2.2.4.2.2.1 (l)(4)


B

2.4.2.2.1.12

Yes

C.2.2.4.2.2.1 (l) For the 75 Percent of Successful Attempts Within 1,000 B Yes





(5) Calls, the Caller Profile Report shall provide, at a minimum, the number of attempts it took to access the network for 75 percent of the callers who completed.

2.4.2.2.1.12

C.2.2.4.2.2.1(l) The contractor shall provide the Caller Information Report 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.

B

2.4.2.2.1.12

Yes

C.2.2.4.2.2.1(m) The Caller Information Report shall provide information about the ANI of all callers to a given 900 number.

B

2.4.2.2.1.13

Yes

C.2.2.4.2.2.1(m) 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.

B

2.4.2.2.1.13

Yes

C.2.2.4.2.2.1(m) Zeroes shall be substituted in place of any missing digits. B

2.4.2.2.1.13

Yes

C.2.2.4.2.2.1 (m)(1)

For any given 900 number, the contractor shall, at a minimum, provide the date of call for each call within the Caller Information Report.

B

2.4.2.2.1.13

Yes

C.2.2.4.2.2.1 (m)(2)

For any given 900 number, the contractor shall, at a minimum, provide the time of call (expressed using a either a 24 hour clock or a 12 hour clock with an AM/PM indicator, eastern prevailing time) for each call within the Caller Information Report.

B

2.4.2.2.1.13

Yes

C.2.2.4.2.2.1 (m)(3)

For any given 900 number, the contractor shall, at a minimum, provide the ANI of caller (if available) for each call within the Caller Information Report.

B

2.4.2.2.1.13

Yes

C.2.2.4.2.2.1 (m)(4)

For any given 900 number, the contractor shall, at a minimum, provide the dialed (i.e., destination) 10 digit number for each call within the Caller Information Report.

B

2.4.2.2.1.13

Yes

C.2.2.4.2.2.1 (m)(5)

For any given 900 number, the contractor shall, at a minimum, provide the duration of call (to the nearest 6 seconds) for each call within the Caller Information Report.

B

2.4.2.2.1.13

Yes





C.2.2.4.2.2.1 (m)(6)(i)

For any given 900 number, the contractor shall, at a minimum, provide the disposition of call (i.e., using an alpha or numeric code) to include, at a minimum, call blocked within contractor’s network for each call within the Caller Information Report.

B

2.4.2.2.1.13

Yes

C.2.2.4.2.2.1 (m)(6)(ii)

For any given 900 number, the contractor shall, at a minimum, provide the disposition of call (i.e., using an alpha or numeric code) to include, at a minimum, call blocked at user’s terminating access for each call within the Caller Information Report.

B

2.4.2.2.1.13

Yes

C.2.2.4.2.2.1 (m)(6)(iii)

For any given 900 number, the contractor shall, at a minimum, provide the disposition of call (i.e., using an alpha or numeric code) to include, at a minimum, call completed to user’s terminating access for each call within the Caller Information Report.

B

2.4.2.2.1.13

Yes

C.2.2.4.2.2.1 (m)(6)(iv)

For any given 900 number, the contractor shall, at a minimum, provide the disposition of call (i.e., using an alpha or numeric code) to include, at a minimum, other (e.g., caller abandoned enroute to user’s terminating access, no answer back supervision received, etc.) for each call within the Caller Information Report.

B

2.4.2.2.1.13

Yes

C.2.2.4.2.2.1(m) The contractor shall provide the information in the Caller Information Report on a daily basis.

B

2.4.2.2.1.13

Yes

C.2.2.4.2.2.1(m) The contractor shall contain the information in the Caller Information Report chronologically sequenced.

B

2.4.2.2.1.13

Yes

C.2.2.4.2.2.1(m) 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.

B

2.4.2.2.1.13

Yes

C.2.2.4.2.2.1(n) The FAX Catalog 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.

B

2.4.2.2.1.14

Yes

C.2.2.4.2.2.1(n) 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

B

2.4.2.2.1.14

Yes





modem).

C.2.2.4.2.2.1(n) Once a document is stored in the FAX catalog, it shall be immediately made available to the callers for retrieval.

B

2.4.2.2.1.14

Yes

C.2.2.4.2.2.1(n) 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.

B

2.4.2.2.1.14

Yes

C.2.2.4.2.2.1(n) The contractor shall FAX requested document(s) within one hour after the call.

B 2.4.2.2.1.14

Yes

C.2.2.4.2.2.1(n) 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).

B 2.4.2.2.1.14

Yes

C.2.2.4.2.2.1(n) Each FAX shall include a cover sheet, which could be customized to include an agency logo, to be defined at service ordering time.

B 2.4.2.2.1.14

Yes

C.2.2.4.2.3(a)(1) All digital transport transmission parameters for POP-to-POP connections 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 2.4.2.3 Yes

C.2.2.4.2.3(b)(1) The digital transport transmission performance for blockage (i.e., GOS) for POP-to-POP connections shall be 1 percent or less.

B 2.4.2.3 Yes

C.2.2.4.2.3(c)(1) The digital transport transmission performance for 900 services for POP-to-POP connections shall provide an availability of at least 99.8 percent.

B 2.4.2.3 Yes

C.2.2.4.2.3(d)(1) The digital transport transmission performance for post-dialing delay for POP-to-POP connection shall not exceed best commercial practice.

B 2.4.2.3 Yes

C.2.2.4.2.4.1.1 (a)(1)

Pursuant to Section C.2.1.16 and for Dedicated Access, the contractor shall support/provide at each POP the LANI via T1 and Fractional T1 channelized with ESF. (Standard: Bellcore Pubs: SR-TSV-002275; ANSI T1.102/107/403).

B 2.4.2.4.1.1

Yes





C.2.2.4.2.4.1.1 (a)(2)

Pursuant to Section C.2.1.16 and for Dedicated Access, the contractor shall support/provide at each POP the LANI via ISDN PRI. (Standard: ANSI T1.607 and 610).

B 2.4.2.4.1.1

Yes

C.2.2.4.2.4.1.1 (a)(3)

Pursuant to Section C.2.1.16 and for Dedicated Access, the contractor shall support/provide at each POP the LANI via T3 and Fractional T3 channelized. (Standard: Bellcore Pub: GR-499-CORE).

B 2.4.2.4.1.1

Yes




C.2.2.4.2.4.1.1 (a)(4)

Pursuant to Section C.2.1.16 and for Dedicated Access, the contractor shall support/provide at each POP the LANI via Analog (Bellcore Pub: SR-TSV-002275).

B 2.4.2.4.1.1

Yes

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

B 3.1.1.1 Yes

C.2.3.1.1.1 PSS shall conform to the ITU-TSS X.25/X.28/X.29/X.3/X.32/ X.121 recommendations, Federal Information Processing Standard-Publication (FIPS-PUB) 100-1, Federal Standard (FED-STD) 1013/1020A/1030A/1033 and ANSI T1.504/614.

B 3.1.1.1 Yes

C.2.3.1.1.1 The contractor shall support packet lengths of 64, 128, 256, 512 and 1024 bytes, at a minimum.

B 3.1.1.1 Yes

C.2.3.1.1.1 Pursuant to Section C.2.1.16, the contractor shall provide dedicated access connections for PSS calls.

B 3.1.1.1 Yes

C.2.3.1.1.1 Originating access connections shall connect PSS on-net originating locations with the associated POP.

B 3.1.1.1 Yes

C.2.3.1.1.1 Terminating access connections shall connect the terminating POP with PSS on-net terminating locations.

B 3.1.1.1 Yes

C.2.3.1.1.1 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.

B 3.1.1.1 Yes





C.2.3.1.1.1 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.

B 3.1.1.1 Yes

C.2.3.1.1.1 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.

B 3.1.1.1 Yes

C.2.3.1.1.3(a)(1) Transmission performance parameters for originating or terminating access between a POP and an SDP for dedicated access arrangements, the PSS access delay shall not exceed the delay caused by the access line speed.

B 3.1.1.3 Yes

C.2.3.1.1.3(b)(1) The availability of the PSS access shall be at least 99.8 percent.

B 3.1.1.3 Yes

C.2.3.1.1.4.1.1 (a)(1)(i)

UNIs supported for DTE (Packet-Mode and Non-Packet-Mode) shall include ITU-TSS V.35.

B 3.1.1.4.1.1

Yes

C.2.3.1.1.4.1.1 (a)(1)(ii)

UNIs supported for DTE (Packet-Mode and Non-Packet-Mode) shall include EIA RS-232.

B 3.1.1.4.1.1

Yes

C.2.3.1.1.4.1.1 (a)(1)(iii)


B 3.1.1.4.1.1

Yes

C.2.3.1.1.4.1.1 (a)(1)(iv)


B 3.1.1.4.1.1

Yes

C.2.3.1.1.4.1.1 (a)(1)(v)


B 3.1.1.4.1.1

Yes

C.2.3.1.1.4.1.1 (a)(1)(vi)

UNIs supported for DTE (Packet-Mode and Non-Packet-Mode) shall include ISDN PRI. (Standard: ANSI T1.607 and 610).

B 3.1.1.4.1.1

Yes

C.2.3.1.1.4.1.1 (a)(2)

For DTE (Packet mode and non packet mode) Asynchronous Data Transfer Speeds shall include (300/1200/2400/4800/9600/14400/28800 bits per second [b/s]).

B 3.1.1.4.1.1

Yes

C.2.3.1.1.4.1.1 (a)(2)

For DTE (Packet mode and non packet mode) Synchronous Data Transfer Speeds shall include (4.8/9.6/19.2/56/

B 3.1.1.4.1.1

Yes





64 kb/s).

C.2.3.1.1.4.1.1 (a)(3)

For DTE (Packet mode and non packet mode) Protocols supported shall include X.25; asynchronous ASCII protocol; IBM BSC protocol (including at a minimum IBM 3270 and 3780); IBM SNA/SDLC protocol; X.25 Link Access Protocols B (LAPB) for use over ISDN B-channel; Unisys Poll/Select protocol.

B 3.1.1.4.1.1

Yes


B 3.1.1.4.1.1

Yes

C.2.3.1.1.4.2.1 (a)(1)

For dedicated access the contractor shall support T1 and Fractional T1 channelized with ESF (Standard: Bellcore Pub: SR-TSV-002275; ANSI T1.102/107/403).

B 3.1.1.4.2.1

Yes

C.2.3.1.1.4.2.1 (a)(2)

For dedicated access the contractor shall support ISDN PRI (Standard: ANSI T1.607 and 610).

B 3.1.1.4.2.1

Yes

C.2.3.1.1.4.2.1 (a)(3)

For dedicated access the contractor shall support T3 and Fractional T3 channelized (Standard: Bellcore Pub: GR-499-CORE).

B 3.1.1.4.2.1

Yes

C.2.3.1.1.4.2.1 (a)(4)

For dedicated access the contractor shall support E1 channelized for Non-Domestic use (Standard: ITU-TSS G.702).

B 3.1.1.4.2.1

Yes

C.2.3.1.1.4.2.1 (a)(5)

For dedicated access the contractor shall support DS0 and Subrate DS0 (Bellcore Pub: SR-TSV-002275).

B 3.1.1.4.2.1

Yes

C.2.3.1.1.4.2.1 (a)(6)

For dedicated access the contractor shall support Analog (Bellcore Pub: SR-TSV-002275).

B 3.1.1.4.2.1

Yes

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

B 3.1.2.1 Yes

C.2.3.1.2.1 The PSS transport shall conform to the ITU-TSS X.25/X.28/X.29/X.3/X.32/X.75/X.121 recommendations.

B 3.1.2.1 Yes

C.2.3.1.2.1 The PSS transport shall conform to Federal Information Processing Standard-Publication (FIPS-PUB 100-1).

B 3.1.2.1 Yes

C.2.3.1.2.1 The PSS transport shall conform to FED-STD 1013/1020A/1030A/1033.

B 3.1.2.1 Yes

C.2.3.1.2.1 The PSS transport shall conform to ANSI T1.504/614. B 3.1.2.1 Yes





C.2.3.1.2.1 The contractor shall support packet sizes up to 1024 bytes in length, including, at a minimum, sizes of 64, 128, 256, and 512 bytes.

B 3.1.2.1 Yes

C.2.3.1.2.1 Pursuant to Section C.2.1.16, the contractor shall provide PSS POP-to-POP connections between the contractor’s listed POPs.

B 3.1.2.1 Yes

C.2.3.1.2.1 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.

B 3.1.2.1 Yes

C.2.3.1.1 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.

B 3.1.2.1 Yes

C.2.3.1.2.1 The contractor shall support dial-in capability to PSS. B

3.1.2.2.1

Yes

C.2.3.1.2.1 The dial-in location(s) for PSS shall be within the transport network.

B

3.1.2.2.1

Yes

C.2.3.1.2.1 The PSS shall support both on-net FTS2001 phone numbers and toll free phone numbers for dial-in access to PSS through asynchronous access and through synchronous packet-switched access using the X.32 protocol.

B

3.1.2.2.1

Yes

C.2.3.1.2.1 Access to the network shall be provided only after verification of the authorization code entered by the user.

B

3.1.2.2.1

Yes

C.2.3.1.2.1 If toll free phone numbers are utilized, the contractor shall bill the CSS charges to the appropriate user organization.

B

3.1.2.2.1

Yes

C.2.3.1.2.1(1) The contractor shall support asynchronous data rates up to 28.8 kb/s.

B

3.1.2.2.1

Yes

C.2.3.1.2.1(2) The contractor shall support data rates using X.32 protocol up to 28.8 kb/s using analog facilities.

B

3.1.2.2.1

Yes





C.2.3.1.2.1(3) The contractor shall support X.32 at 56/64 kb/s using digital facilities.

B

3.1.2.2.1

Yes

C.2.3.1.2.1(a) PSS transport shall support 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

3.1.2.2.1

Yes

C.2.3.1.2.1(b) PSS transport shall support the capability to support a numbering plan that shall follow the ITU-TSS X.121 numbering plan.

B

3.1.2.2.1

Yes

C.2.3.1.2.1(c)(1) The contractor shall support, as specified in FIPS-PUB 100-1, reverse charging.

B

3.1.2.2.1

Yes

C.2.3.1.2.1(c)(2) The contractor shall support, as specified in FIPS-PUB 100-1, reverse charging acceptance.

B

3.1.2.2.1

Yes

C.2.3.1.2.1(c)(3) The contractor shall support, as specified in FIPS-PUB 100-1, local charging prevention.

B

3.1.2.2.1

Yes

C.2.3.1.2.1(c)(4) The contractor shall support, as specified in FIPS-PUB 100-1, nonstandard default packet size.

B

3.1.2.2.1

Yes

C.2.3.1.2.1(c)(5) The contractor shall support, as specified in FIPS-PUB 100-1, nonstandard default window size.

B

3.1.2.2.1

Yes

C.2.3.1.2.1(c)(6) The contractor shall support, as specified in FIPS-PUB 100-1, incoming calls barred.

B

3.1.2.2.1

Yes

C.2.3.1.2.1(c)(7) The contractor shall support, as specified in FIPS-PUB 100-1, outgoing calls barred.

B

3.1.2.2.1

Yes

C.2.3.1.2.1(c)(8) The contractor shall support, as specified in FIPS-PUB 100-1, one-way logical channel outgoing.

B

3.1.2.2.1

Yes

C.2.3.1.2.1(c)(9) The contractor shall support, as specified in FIPS-PUB 100-1, one-way logical channel incoming.

B

3.1.2.2.1

Yes

C.2.3.1.2.1(c) (10)

The contractor shall support, as specified in FIPS-PUB 100-1, default throughput classes assignment.

B Yes





3.1.2.2.1

C.2.3.1.2.1(c) (11)

The contractor shall support, as specified in FIPS-PUB 100-1, flow control parameter negotiation.

B

3.1.2.2.1

Yes

C.2.3.1.2.1(c) (12)

The contractor shall support, as specified in FIPS-PUB 100-1, throughput class negotiation.

B

3.1.2.2.1

Yes

C.2.3.1.2.1(c) (13)

The contractor shall support, as specified in FIPS-PUB 100-1, fast select.

B

3.1.2.2.1

Yes

C.2.3.1.2.1(c) (14)

The contractor shall support, as specified in FIPS-PUB 100-1, fast select acceptance.

B

3.1.2.2.1

Yes

C.2.3.1.2.1(c) (15)

The contractor shall support, as specified in FIPS-PUB 100-1, hunt group facilities, including round robin, closest, and ordered list.

B

3.1.2.2.1

Yes

C.2.3.1.2.1(c) (16)

The contractor shall support, as specified in FIPS-PUB 100-1, 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.

B

3.1.2.2.1

Yes

C.2.3.1.2.1(c) (17)

The contractor shall support, as specified in FIPS-PUB 100-1, transit delay selection and notification.

B

3.1.2.2.1

Yes

C.2.3.1.2.1(c) (18)

The contractor shall support, as specified in FIPS-PUB 100-1, abbreviated address calling.

B

3.1.2.2.1

Yes

C.2.3.1.2.1(c) (19)

The contractor shall support, as specified in FIPS-PUB 100-1, call redirection notification.

B

3.1.2.2.1

Yes

C.2.3.1.2.1(c) (20)

The contractor shall support, as specified in FIPS-PUB 100-1, called line address modification notification.

B

3.1.2.2.1

Yes

C.2.3.1.2.1(c) (21)

The contractor shall support, as specified in FIPS-PUB 100-1, on-line facilities registration.

B

3.1.2.2.1

Yes

C.2.3.1.2.1(c) (22)

The contractor shall support, as specified in FIPS-PUB 100-1, extended packet sequence numbering (modulo 128).

B

3.1.2.2.1

Yes





C.2.3.1.2.1(c) (23)

The contractor shall support, as specified in FIPS-PUB 100-1, packet retransmission.

B

3.1.2.2.1

Yes

C.2.3.1.2.1(c) (24)

The contractor shall support, as specified in FIPS-PUB 100-1, multilink procedure.

B

3.1.2.2.1

Yes

C.2.3.1.2.1(c) (25)

The contractor shall support, as specified in FIPS-PUB 100-1, direct call.

B

3.1.2.2.1

Yes

C.2.3.1.2.1(c) (26)

The contractor shall support, as specified in FIPS-PUB 100-1, d-bit modification.

B

3.1.2.2.1

Yes

C.2.3.1.2.1(c) (27)

The contractor shall support, as specified in FIPS-PUB 100-1, call redirection.

B

3.1.2.2.1

Yes

C.2.3.1.2.1(c) (28)

The contractor shall support, as specified in FIPS-PUB 100-1, NUI.

B

3.1.2.2.1

Yes

C.2.3.1.2.1(c) (29)

The contractor shall support, as specified in FIPS-PUB 100-1, extended frame sequence numbering.

B

3.1.2.2.1

Yes

C.2.3.1.2.1(c) (30)

The contractor shall support, as specified in FIPS-PUB 100-1, call deflection subscription.

B

3.1.2.2.1

Yes

C.2.3.1.2.1(c) (31)

The contractor shall support, as specified in FIPS-PUB 100-1, call deflection selection.

B

3.1.2.2.1

Yes

C.2.3.1.2.3(a)(1) For POP-to-POP transmission, the PSS transport performance shall meet the following (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).

B 3.1.2.3

Yes

C.2.3.1.2.3(b)(1) For POP-to-POP transmission the availability of the PSS transport shall be at least 99.8 percent.

B 3.1.2.3 Yes





C.2.3.1.2.4.1.1 (a)(1)

For dedicated access, the contractor shall provide the following interfaces (i.e., LANI) at each POP listed for the provision of PSS transport for T1 and Fractional T1 channelized with ESF (Standard: Bellcore Pub: SR-TSV-002275; ANSI T1.102/107/403).

B 3.1.2.4.1.1

Yes

C.2.3.1.2.4.1.1 (a)(2)

For dedicated access, the contractor shall provide the following interfaces (i.e., LANI) at each POP listed for the provision of PSS transport for ISDN PRI (Standard: ANSI T1.607 and 610).

B 3.1.2.4.1.1

Yes

C.2.3.1.2.4.1.1 (a)(3)

For dedicated access, the contractor shall provide the following interfaces (i.e., LANI) at each POP listed for the provision of PSS transport for T3 and Fractional T3 channelized (Standard: Bellcore Pub: GR-499-CORE).

B 3.1.2.4.1.1

Yes

C.2.3.1.2.4.1.1 (a)(4)

For dedicated access, the contractor shall provide the following interfaces (i.e., LANI) at each POP listed for the provision of PSS transport for E1 channelized for Non-Domestic use (Standard: ITU-TSS G.702).

B 3.1.2.4.1.1

Yes

C.2.3.1.2.4.1.1 (a)(5)

For dedicated access, the contractor shall provide the following interfaces (i.e., LANI) at each POP listed for the provision of PSS transport for DS0 and Subrate DS0 (Bellcore Pub: SR-TSV-002275).

B 3.1.2.4.1.1

Yes

C.2.3.1.2.4.1.1 (a)(6)

For dedicated access, the contractor shall provide the following interfaces (i.e., LANI) at each POP listed for the provision of PSS transport for Analog (Bellcore Pub: SR-TSV-002275).

B 3.1.2.4.1.1

Yes

C.2.3.2.1.1 The FRS shall provide a frame-switched, connection-oriented, data transmission service at data rates up to DS1.

B 3.2.1.1 Yes

C.2.3.2.1.1 The FRS shall conform to the ANSI T1 standards, in particular T1.606/614/617/618.

B 3.2.1.1 Yes

C.2.3.2.1.1 The FRS shall conform to 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.

B 3.2.1.1 Yes

C.2.3.2.1.1 The FRS shall also conform to the industry agreements of the Frame Relay Forum, the Internet Engineering Task

B 3.2.1.1 Yes





Force (IETF).

C.2.3.2.1.1 The FRS shall conform to the North American ISDN Users Forum (NIUF).

B 3.2.1.1 Yes

C.2.3.2.1.1 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.

B 3.2.1.1 Yes

C.2.3.2.1.1 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.

B 3.2.1.1 Yes

C.2.3.2.1.1 Pursuant to Section C.2.1.16, the contractor shall provide dedicated originating and/or terminating access connections for FRS calls.

B 3.2.1.1 Yes

C.2.3.2.1.1 Originating access connections shall connect FRS on-net originating locations with the associated POP.

B 3.2.1.1 Yes

C.2.3.2.1.1 Terminating access connections shall connect the terminating POP with FRS on-net terminating locations.

B 3.2.1.1

Yes

C.2.3.2.1.1 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.

B 3.2.1.1 Yes

C.2.3.2.1.1 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.

B 3.2.1.1 Yes

C.2.3.2.1.3(a)(1) For dedicated access arrangements, the FRS access delay shall not exceed the delay caused by the access line speed.

B 3.2.1.3 Yes

C.2.3.2.1.3(b)(1) The availability of the FRS access shall be at least 99.8 percent.

B 3.2.1.3

Yes

C.2.3.2.1.4.1.1 (a)(1)

The interfaces supported at the SDP for the provisioning of FRS access shall include ITU-TSS V.35.

B 3.2.1.4.1.1

Yes





C.2.3.2.1.4.1.1 (a)(2)

The interfaces supported at the SDP for the provisioning of FRS access shall include EIA RS-232.

B 3.2.1.4.1.1

Yes

C.2.3.2.1.4.1.1 (a)(3)


B 3.2.1.4.1.1

Yes

C.2.3.2.1.4.1.1 (a)(4)


B 3.2.1.4.1.1

Yes

C.2.3.2.1.4.1.1 (a)(5)


B 3.2.1.4.1.1

Yes

C.2.3.2.1.4.1.1 (a)(6)

The interfaces supported at the SDP for the provisioning of FRS access shall include ISDN PRI (Standard: ANSI T1.607 and 610).

B 3.2.1.4.1.1

Yes

C.2.3.2.1.4.1.1 (a)(7)

The interfaces supported at the SDP for the provisioning of FRS access shall include IEEE 802.3 (Ethernet) all cable and connector types.

B

3.2.1.4.1.1

Yes

C.2.3.2.1.4.1.1 (a)(8)

The interfaces supported at the SDP for the provisioning of FRS access shall include IEEE 802.5 (Token Ring) all cable and connector types.

B

3.2.1.4.1.1

Yes

C.2.3.2.1.4.1.1 (b)

The FRS shall support data transfer speeds of 19.2 kb/s, and from 64 kb/s to T1/E1 (Non Domestic).

B 3.2.1.4.1.1

Yes

C.2.3.2.1.4.1.1 (c)(1)

Protocols supported for the provisioning of FRS access shall include frame relay protocol.

B 3.2.1.4.1.1

Yes

C.2.3.2.1.4.1.1 (c)(2)

Protocols supported for the provisioning of FRS access shall include 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).

B 3.2.1.4.1.1

Yes


B 3.2.1.4.1.1

Yes

C.2.3.2.1.4.2.1 (a)(1)

Local Access to Network Interface (LANI), to connect to a POP, for FRS dedicated access shall include T1 and Fractional T1 with ESF. (Standard: Bellcore Pubs: SR-TSV-0002275; ANSI T1.102/107/403).

B 3.2.1.4.2.1

Yes

C.2.3.2.1.4.2.1 (a)(2)

Local Access to Network Interface (LANI) to connect to a POP, FRS for dedicated access shall include ISDN PRI

B 3.2.1.4.2.1

Yes





(Standard: ANSI T1.607 and 610).

C.2.3.2.1.4.2.1 (a)(3)

Local Access to Network Interface (LANI) to connect to a POP, for FRS dedicated access shall include T3 channelized (Standard: Bellcore Pub: GR-499-CORE)

B 3.2.1.4.2.1

Yes

C.2.3.2.1.4.2.1 (a)(4)

Local Access to Network Interface (LANI) to connect to a POP, for FRS dedicated access shall include E1 for Non-Domestic use (Standard: ITU-TSS G.702).

B 3.2.1.4.2.1

Yes

C.2.3.2.1.4.2.1 (a)(5)

Local Access to Network Interface (LANI) to connect to a POP, for FRS dedicated access shall include DS0 (Bellcore Pub: SR-TSV-002275).

B 3.2.1.4.2.1

Yes

C.2.3.2.2.1 FRS transport shall provide a frame-switched, connection-oriented, data transmission service at data rates up to DS1.

B 3.2.2.1 Yes

C.2.3.2.2.1 FRS shall conform to the ANSI T1 standards, in particular T1.606/614/617/618.

B 3.2.2.1 Yes

C.2.3.2.2.1 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.

B 3.2.2.1 Yes

C.2.3.2.2.1 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).

B 3.2.2.1

Yes

C.2.3.2.2.1 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.

B 3.2.2.1 Yes

C.2.3.2.2.1 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.

B 3.2.2.1 Yes

C.2.3.2.2.1 Pursuant to Section C.2.1.16, the contractor shall provide FRS POP-to-POP connections between the contractor’s listed POPs.

B 3.2.2.1 Yes

C.2.3.2.2.1 The contractor shall accept at any of its listed POPs which support the appropriate on-net service, originating FRS calls via dedicated access arrangement from the associated access providers.

B 3.2.2.1 Yes





C.2.3.2.2.1 The contractor shall hand off terminating FRS calls via dedicated access arrangement from any of its listed POPs which support the appropriate on-net service to the associated access providers.

B 3.2.2.1 Yes

C.2.3.2.2.1 The contractor shall support dial-in capability to FRS. B 3.2.2.1 Yes

C2.3.2.2.1 The dial-in location(s) for FRS shall be within the transport network.

B 3.2.2.1 Yes

C.2.3.2.2.1 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.

B 3.2.2.1 Yes

C.2.3.2.2.1 If toll free phone number are utilized, the contractor shall bill the CSS charges to the appropriate user organization.

B 3.2.2.1 Yes


B 3.2.2.1 Yes

C.2.3.2.2.1(1) The contractor shall support asynchronous data rates up to 28.8 kb/s.

B 3.2.2.1 Yes

C.2.3.2.2.1(2) The contractor shall support ISDN LAPB data rates at 56/64 kb/s using digital facilities.

B 3.2.2.1 Yes

C.2.3.2.2.1(c)(1) When FRS is provided via internetworked access arrangement (see Section C.2.1.16), FRS shall support SVCs, and a numbering plan for SVCs that shall follow the ITU-TSS E.164 ISDN numbering and addressing recommendation.

B 3.2.2.1 Yes

C.2.3.2.2.3(a)(1) The network transport performance parameters for POP-to-POP connection (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).

B 3.2.2.3 Yes

C.2.3.2.2.3(a)(1) The network transport performance shall also comply with the ANSI T1.606/614/617/618 standards.

B 3.2.2.3 Yes

C.2.3.2.2.3(b)(1) The availability of the FRS transport shall be at least 99.8 percent.

B 3.2.2.3 Yes

C.2.3.2.2.4.1 Pursuant to Section C.2.1.16, the contractor shall B 3.2.2.4.1 Yes





support/provide interfaces (i.e., LANI) at each POP listed for the provision of FRS transport.

C.2.3.2.2.4.1.1 (a)(1)

The Interfaces (i.e., LANI) at each POP listed for the provision of FRS transport, for Dedicated Access shall include T1 and Fractional T1with ESF (Standard: Bellcore Pub: SR-TSV-002275; ANSI T1.102/107/403).

B 3.2.2.4.1.1

Yes

C.2.3.2.2.4.1.1 (a)(2)

The Interfaces (i.e., LANI) at each POP listed for the provision of FRS transport, for Dedicated Access shall include ISDN PRI (Standard: ANSI T1.607 and 610).

B 3.2.2.4.1.1

Yes

C.2.3.2.2.4.1.1 (a)(3)

The Interfaces (i.e., LANI) at each POP listed for the provision of FRS transport, for Dedicated Access shall include T3 channelized (Standard: Bellcore Pub: GR-499-CORE).

B 3.2.2.4.1.1

Yes

C.2.3.2.2.4.1.1 (a)(4)

The Interfaces (i.e., LANI) at each POP listed for the provision of FRS transport, for Dedicated Access shall include E1 for Non-Domestic use (Standard: ITU-TSS G.702).

B 3.2.2.4.1.1

Yes

C.2.3.2.2.4.1.1 (a)(5)

The Interfaces (i.e., LANI) at each POP listed for the provision of FRS transport, for Dedicated Access shall include DS0 (Bellcore Pub: SR-TSV-002275).

B 3.2.2.4.1.1

Yes

C.2.3.3.1.1 IPS shall support connectionless service between users (i.e., IP hosts) for execution of user 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.

B 3.3.1.1 Yes

C.2.3.3.1.1 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).

B 3.3.1.1 Yes

C.2.3.3.1.1 Pursuant to Section C.2.1.16, the contractor shall provide dedicated originating and/or terminating access connections for IPS packets.

B 3.3.1.1 Yes

C.2.3.3.1.1 Originating access arrangements shall connect IPS on-net originating locations with the associated POP.

B 3.3.1.1 Yes





C.2.3.3.1.1 Terminating access arrangements shall connect the terminating POP with IPS on-net terminating locations.

B 3.3.1.1 Yes

C.2.3.3.1.1 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.

B 3.3.1.1 Yes

C.2.3.3.1.3(a)(1) For dedicated originating or terminating access arrangements, the IPS access delay between a POP and an SDP shall not exceed the delay caused by the access line speed.

B 3.3.1.3 Yes

C.2.3.3.1.3(b)(1) The availability of the IPS access shall be at least 99.8 percent.

B 3.3.1.3 Yes

C.2.3.3.1.4.1.1 (a)(1)

The IPS Interfaces to be supported shall include EIA RS-449.

B 3.3.1.4.1.1

Yes

C.2.3.3.1.4.1.1 (a)(2)


B 3.3.1.4.1.1

Yes

C.2.3.3.1.4.1.1 (a)(3)


B 3.3.1.4.1.1

Yes

C.2.3.3.1.4.1.1 (a)(4)

The IPS Interfaces to be supported shall include ITU-TSS V.35.

B 3.3.1.4.1.1

Yes

C.2.3.3.1.4.1.1 (a)(5)

The IPS Interfaces to be supported shall include T1. B 3.3.1.4.1.1

Yes

C.2.3.3.1.4.1.1 (a)(6)

The IPS Interfaces to be supported shall include E1. B 3.3.1.4.1.1

Yes

C.2.3.3.1.4.1.1 (a)(7)

The IPS Interfaces to be supported shall include IEEE 802.3 (Ethernet/Fast Ethernet) all cable and connector types.

B 3.3.1.4.1.1

Yes

C.2.3.3.1.4.1.1 (a)(8)

The IPS Interfaces to be supported shall include IEEE 802.5 (Token Ring) all cable and connector types.

B 3.3.1.4.1.1

Yes

C.2.3.3.1.4.1.1 (a)(9)

The IPS Interfaces to be supported shall include ANSI FDDI/FDDI 2 all cable and connector types.

B 3.3.1.4.1.1

Yes





C.2.3.3.1.4.1.1 (b)(1)

The IPS using EIA RS-449 shall support an information payload rate of up to 1.536 Mb/s.

B 3.3.1.4.1.1

Yes

C.2.3.3.1.4.1.1 (b)(2)

The IPS using EIA RS-530 shall support an information payload rate of up to 1.536 Mb/s.

B 3.3.1.4.1.1

Yes

C.2.3.3.1.4.1.1 (b)(3)

The IPS using ISDN PRI shall support data transfer speeds of 64 kb/s, up to 1.536 Mb/s in increments of 64 kb/s.

B 3.3.1.4.1.1

Yes

C.2.3.3.1.4.1.1 (c)(1)

The contractor shall support the IPv4-Terminal (e.g., router, computer) interface at the SDP for the provisioning of IPS access.

B 3.3.1.4.1.1

Yes

C.2.3.3.1.4.1.1 In addition, the contractor shall support the UNI types as given in Table C.2.3.3.1.4.1.1-1.

B 3.3.1.4.1.1

Yes

C.2.3.3.1.4.2.1 (a)(1)

For IPS dedicated access, the contractor shall support/provide the LANI interface for the T1 and Fractional T1with ESF (Standard: Bellcore Pubs: SR-TSV-002275; ANSI T1.102/107/403).

B 3.3.1.4.2.1

Yes

C.2.3.3.1.4.2.1 (a)(2)

For IPS dedicated access, the contractor shall support/provide the LANI interface for the ISDN PRI (Standard: ANSI T1.607 and 610).

B 3.3.1.4.2.1

Yes

C.2.3.3.1.4.2.1 (a)(3)

For IPS dedicated access, the contractor shall support/provide the LANI interface for theT3and Fractional T3 (Standard: Bellcore Pub: GR-499-CORE).

B 3.3.1.4.2.1

Yes

C.2.3.3.1.4.2.1 (a)(4)

For IPS dedicated access, the contractor shall support/provide the LANI interface for the E1 for Non-Domestic use (Standard: ITU-TSS G.702).

B 3.3.1.4.2.1

Yes

C.2.3.3.1.4.2.1 (a)(5)

For IPS dedicated access, the contractor shall support/provide the LANI interface for DS0 (Bellcore Pub: SR-TSV-002275).

B 3.3.1.4.2.1

Yes

C.2.3.3.2.1 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).

B 3.3.2.1 Yes

C.2.3.3.2.1 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).

B 3.3.2.1

Yes





C.2.3.3.2.1 Pursuant to Section C.2.1.16, the contractor shall provide interconnections between the contractor’s listed POPs.

B 3.3.2.1 Yes

C.2.3.3.2.1 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.

B 3.3.2.1

Yes

C.2.3.3.2.1 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.

B 3.3.2.1

Yes

C.2.3.3.2.1 The contractor shall support dial-in capability to IPS. B 3.3.2.1

Yes

C.2.3.3.2.1 The dial-in location(s) for IPS shall be within the transport network.

B 3.3.2.1

Yes

C.2.3.3.2.1 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.

B 3.3.2.1

Yes


B 3.3.2.1

Yes

C.2.3.3.2.1 If toll free phone numbers are utilized, the contractor shall bill the CSS charges to the appropriate user organization.

B 3.3.2.1

Yes

C.2.3.3.2.1(a) The contractor shall support point-to-point protocol data rates up to 28.8 kb/s using analog facilities.

B 3.3.2.1

Yes

C.2.3.3.2.1(b) The contractor shall support point-to-point protocol data rates at 56/64/128 kb/s using digital facilities.

B 3.3.2.1

Yes

C.2.3.3.2.1 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.

B 3.3.2.1 Yes

C.2.3.3.2.1 The contractor shall provide an addressing plan for the IPS that is based on the standard for IPv4 addressing.

B 3.3.2.1 Yes

C.2.3.3.2.1(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

B 3.3.2.1 Yes





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.

C.2.3.3.2.1(c) In addition, the contractor shall provide permanent (static) and temporary (dynamic) assigned IP addresses for circuit switched users.

B 3.3.2.1 Yes

C.2.3.3.2.1(c) The contractor shall accommodate all existing Government IP addresses.

B 3.3.2.1 Yes

C.2.3.3.2.2.1 (a)(1)

The contractor shall provide as a minimum IP firewall capability of a filter definition language, a set of logging and reporting tools for per-port and per socket management and administration.

B 3.3.2.2.1 Yes

C.2.3.3.2.2.1 (a)(2)

The contractor shall provide as a minimum IP firewall capability to filter both incoming and outgoing traffic.

B 3.3.2.2.1 Yes

C.2.3.3.2.2.1 (a)(3)

The contractor shall provide as a minimum IP firewall capability of provisioning of preconfigured checks for known methods of attack.

B 3.3.2.2.1 Yes

C.2.3.3.2.2.1 (a)(4)

The contractor shall provide as a minimum IP firewall capability of application specific forwarding capability (e.g., Telnet/FTP only).

B 3.3.2.2.1 Yes

C.2.3.3.2.2.1 (a)(5)

The contractor shall provide as a minimum IP firewall capability of support of encrypted tunneling.

B 3.3.2.2.1 Yes

C.2.3.3.2.3(a)(1) IPS transport POP-to-POP shall provide a one-way Packet Delay of less than 200 milliseconds on the average.

B 3.3.2.3 Yes

C.2.3.3.2.3(b)(1) The transport POP-to-POP availability of the IPS transport shall be at least 99.8 percent

B 3.3.2.3 Yes

C.2.3.3.2.4.1.1 (a)(1)

The contractor shall provide/support an interface (i.e., LANI) for the T1 and Fractional T1 with ESF (Standard: Bellcore Pub: SR-TSV-002275; ANSI T1.102/107/403) for dedicated access to connect at each POP for provision of IPS transport.

B 3.3.2.4.1.1

Yes

C.2.3.3.2.4.1.1 (a)(2)

The contractor shall provide/support an interface (i.e., LANI) for ISDN PRI (Standard: ANSI T1.607 and 610) for dedicated access to connect at each POP for provision of IPS transport.

B 3.3.2.4.1.1

Yes





C.2.3.3.2.4.1.1 (a)(3)

The contractor shall provide/support an interface (i.e., LANI) for T3 and Fractional T3(Standard: Bellcore Pub: GR-499-CORE) for dedicated access to connect at each POP for provision of IPS transport.

B 3.3.2.4.1.1

Yes

C.2.3.3.2.4.1.1 (a)(4)

The contractor shall provide/support an interface (i.e., LANI) for E1 for Non-Domestic use (Standard: ITU-TSS G.702) for dedicated access to connect at each POP for provision of IPS transport.

B 3.3.2.4.1.1

Yes

C.2.3.3.2.4.1.1 (a)(5)

The contractor shall provide/support an interface (i.e., LANI) for DS0 (Bellcore Pub: SR-TSV-002275) for dedicated access at each POP for provision of IPS transport.

B 3.3.2.4.1.1

Yes

C.2.3.3.2.4.1.3 (a)(1)

The contractor shall support IPv4 for internetworked access provision of IPS transport.

B 3.3.2.4.1.3

Yes

C.2.3.4.1.1 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.

B 3.4.1.1

Yes

C.2.3.4.1.1 ATMS shall use cell-switching and multiplexing technology that conforms with ATM Forum (ATMF), ANSI, and ITU-TSS standards.

B 3.4.1.1 Yes

C.2.3.4.1.1 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.

B 3.4.1.1 Yes

C.2.3.4.1.1 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.

B 3.4.1.1 Yes

C.2.3.4.1.1 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.

B 3.4.1.1 Yes

C.2.3.4.1.1 The contractor shall provide dedicated, originating and terminating access arrangements for ATMS.

B 3.4.1.1 Yes

C.2.3.4.1.1 Originating access arrangements shall connect ATMS on-net originating locations with the associated POP.

B 3.4.1.1 Yes

C.2.3.4.1.1 Terminating access arrangements shall connect the B Yes





terminating POP with ATMS on-net terminating locations. 3.4.1.1

C.2.3.4.1.1 ATMS access shall be delivered directly to user equipment, such as PBX, ATM edge switches, router, or MUX.

B 3.4.1.1 Yes

C.2.3.4.1.1 ATMS shall support the router for IEEE 802 LANs (Token Ring, Ethernet) and FDDI at a minimum.

B 3.4.1.1 Yes

C.2.3.4.1.1(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 shall be initiated by using a contractor-specified procedure; for the packet-mode of data transfer BOD shall be initiated automatically by sending increased numbers of packets.

B 3.4.1.1

Yes

C.2.3.4.1.3(a)(1) For dedicated access arrangements between a POP and an SDP, the ATMS access delay shall not exceed the delay caused by the access line speed.

B 3.4.1.3

Yes

C.2.3.4.1.3(b)(1) The availability of the ATMS access shall be at least 99.8 percent.

B 3.4.1.3 Yes

C.2.3.4.1.4.1.1 (a)(1)

The interfaces provided at the SDP shall support ITU-TSS V.35.

B 3.4.1.4.1.1

Yes

C.2.3.4.1.4.1.1 (a)(2)

The interfaces provided at the SDP shall support EIA RS-449.

B 3.4.1.4.1.1

Yes

C.2.3.4.1.4.1.1 (a)(3)

The interfaces provided at the SDP shall support EIA RS-530.

B 3.4.1.4.1.1

Yes

C.2.3.4.1.4.1.1 (a)(4)

The interfaces provided at the SDP shall support 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).

B 3.4.1.4.1.1

Yes

C.2.3.4.1.4.1.1 (a)(5)

The interfaces provided at the SDP shall support DS3 at line-rate of 44.736 Mb/s and information-payload data-rate 43.008 Mb/s. including cell overhead. (Standard: Bellcore PUB GR-499-CORE): ATMF UNI specification for T3 supporting Physical Layer Coverage Protocol [PLCP])

B 3.4.1.4.1.1

Yes

C.2.3.4.1.4.1.1 (b)(1)

The interface provided at the SDP shall support ITU-TSS V.35 at an information payload rate of up to 1.536 Mb/s.

B 3.4.1.4.1.1

Yes





C.2.3.4.1.4.1.1 (b)(2)

The interface provided at the SDP shall support EIA RS-449 at an information payload rate of up to 1.536 Mb/s.

B 3.4.1.4.1.1

Yes

C.2.3.4.1.4.1.1 (b)(3)

The interface provided at the SDP shall support EIA RS-530 at an information payload rate of up to 1.536 Mb/s.

B 3.4.1.4.1.1

Yes

C.2.3.4.1.4.1.1 (b)(4)

The interface provided at the SDP shall support DS1 ATMS at an information-payload data-rate of 1.536 Mb/s.

B 3.4.1.4.1.1

Yes

C.2.3.4.1.4.1.1 (b)(5)

The interface provided at the SDP shall support DS3 ATMS at an information rate of 1.536 Mb/s to 43.008 Mb/s in increments of 1.536 Mb/s. (i.e., NxDS1).

B 3.4.1.4.1.1

Yes

C.2.3.4.1.4.1.1 (c)(1)

The interface provided at the SDP shall support the ATMS AAL Type 1 protocol.

B 3.4.1.4.1.1

Yes

C.2.3.4.1.4.1.1 (c)(2)

The interface provided at the SDP shall support the ATMS AAL Type 5.

B 3.4.1.4.1.1

Yes

C.2.3.4.1.4.1.1 (c)(3)

The interface provided at the SDP shall support the ATMS Native Mode.

C.2.3.4.1.4.1 The contractor shall support the UNI types given in Table C.2.3.4.1.4.1.1-1.

B 3.4.1.4.1.1

Yes

C.2.3.4.1.4.2.1 (a)(1)

The contractor shall provide T1 with ESF (Standard: Bellcore Pub: SR-TSV-002275; ANSI T1.102/107/403) for dedicated access to connect a POP for the provision of ATMS access.

B 3.4.1.4.2.1

Yes

C.2.3.4.1.4.2.1 (a)(2)

The contractor shall provide T3 and Fractional T3 (Standard: Bellcore Pub: GR-499-CORE) for dedicated access to connect a POP for the provision of ATMS access.

B 3.4.1.4.2.1

Yes

C.2.3.4.2.1 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.

B 3.4.2.1 Yes

C.2.3.4.2.1 ATMS shall use cell-switching and multiplexing technology that conforms with ATMF, ANSI, and ITU-TSS standards.

B 3.4.2.1 Yes

C.2.3.4.2.1 The ATMS shall comply with ATMF and all applicable ITU-TSS Recommendations including I.113, I.121, I.150,

B 3.4.2.1

Yes





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.

C.2.3.4.2.1 The ATMS shall offer SCRs of 4, 8, 16, and 32 Mb/s for VBR traffic.

B 3.4.2.1

Yes

C.2.3.4.2.1 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.

B 3.4.2.1

Yes

C.2.3.4.2.1 Pursuant to Section C.2.1.16, the contractor shall provide ATMS POP-to-POP connections between the contractor’s listed POPs.

B 3.4.2.1

Yes

C.2.3.4.2.1 The contractor shall accept at any of its listed POPs which support the appropriate on-net service, originating ATMS connections via dedicated access arrangement from the associated access providers.

B 3.4.2.1

Yes

C.2.3.4.2.1 The contractor shall hand off terminating ATMS connections via dedicated access arrangement from any of its listed POPs which support the appropriate on-net service to the associated access providers.

B 3.4.2.1

Yes

C.2.3.4.2.1(a) The contractor shall comply with ITU-TSS Recommendations I.361, I.362, and I.363, and ITU-TSS Q.2100 for signaling:

B 3.4.2.1 Yes

C.2.3.4.2.1(a)(1) AAL Type 1 Constant Bit Rate (CBR), ATMS shall support circuit-mode services at the DS1 and DS3 levels on an end-to-end basis.

B 3.4.2.1 Yes

C.2.3.4.2.1(a)(2) AAL Type 5 Connection-Oriented Variable Bit Rate (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 3.4.2.1 Yes

C.2.3.4.2.1(b)(1) ATMS shall support Point-to-Point connection PVCs to allow dedicated connections between two points.

B 3.4.2.1 Yes

C.2.3.4.2.1(c)(1) The ATMS transport shall support CBR over DS1 at information-payload data-rate of 1.536 Mb/s , including cell overhead.

B 3.4.2.1 Yes

C.2.3.4.2.1(c)(1) The ATMS transport shall support CBR over DS3 at information-payload data-rate 40.704 Mb/s, including cell

B 3.4.2.1 Yes





overhead.

C.2.3.4.2.1(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.

B 3.4.2.1 Yes

C.2.3.4.2.3(a) The network transport performance for circuit-mode transmission for POP-to-POP connections 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.

B 3.4.2.3 Yes

C.2.3.4.2.3(a) 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-T I.356 and ITU-T G826 and Bellcore Pubs: GR-1110-CORE, GR-1111-CORE, TR-TSU-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.

B 3.4.2.3 Yes

C.2.3.4.2.3(b) The availability of the ATMS transport shall be at least 99.8 percent.

B 3.4.2.3 Yes

C.2.3.4.2.4.1.1 (a)(1)

The contractor shall provide an interface (i.e., LANI) for T1 with ESF (Standard: Bellcore Pubs: SR-TSV-002275; ANSI T1.102/107/403) for dedicated access to connect at each POP for provision of ATMS transport.

B 3.4.2.4.1.1

Yes

C.2.3.4.2.4.1.1 (a)(2)

The contractor shall provide an interface (i.e., LANI) for T3 and Fractional T3 (Standard: Bellcore Pub: GR-499-CORE) for dedicated access to connect at each POP for provision of ATMS transport.

B 3.4.2.4.1.1

Yes

C.2.4 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.1 The connection between the locations receiving DTS service shall be permanently established unless a service request for modification, move, or disconnect is received.

B 4.1.1

Yes

C.2.4.1.1 Dedicated transmission service (DTS) shall comply with ITU T1.503 and all applicable Bellcore standards.

B 4.1.1

Yes

C.2.4.1.1 DTS shall comply with ANSI standards, primarily ANSI T1.102/107/403 for T1.

B 4.1.1

Yes

C.2.4.1.1 DTS shall comply with Bellcore PUB GR-499-CORE for T3.

B 4.1.1

Yes

C.2.4.1.1 DTS service shall comply with ANSI T1.105 and 106 for SONET.

B 4.1.1

Yes

C.2.4.1.1 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.

B 4.1.1

Yes

C.2.4.1.1 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.

B 4.1.1

Yes

C.2.4.1.1 DTS shall support both analog and digital mode of transmissions.

B 4.1.1

Yes

C.2.4.1.1 For analog DTS, the contractor shall accept and deliver an analog signal whose nominal bandwidth is 4 kHz.

B 4.1.1

Yes

C.2.4.1.1 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.

B 4.1.1

Yes

C.2.4.1.1 The service shall provide data transport and shall be transparent to any protocol used by the DTE or router.

B

4.1.1

Yes

C.2.4.1.1 All bit sequences transmitted by the DTE through the SDP shall be treated with data transparency.

B 4.1.1

Yes

C.2.4.1.1(a) DTS service categories supported shall include analog B Yes





service with nominal 4 kHz bandwidth. 4.1.1

C.2.4.1.1(b) DTS service categories supported shall include subrate DS0 service at payload data rates of 4.8 and 9.6 kb/s.

B 4.1.1

Yes

C.2.4.1.1(c) DTS service categories supported shall include DS0 service with payload data rates of 56 and 64 kb/s.

B 4.1.1

Yes

C.2.4.1.1(d)(1) DTS service categories supported shall include T1 service with line rate of 1.544 Mb/s, which may be used to provide support 24 separate DS0s clear channels of 56/64 kb/s in channelized mode.

B 4.1.1

Yes

C.2.4.1.1(d)(2) DTS service categories supported shall include T1 service with line rate of 1.544 Mb/s, which may be used to provide a single 1.536 Mb/s in unchannelized mode.

B 4.1.1

Yes

C.2.4.1.1(e) DTS service categories supported shall include Fractional T1 service to 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.

B 4.1.1

Yes

C.2.4.1.1(f)(1) DTS service categories supported shall include T3 service to support a line rate of 44.736 Mb/s, which may be used to provide 28 separate DS1 channels of 1.536 Mb/s information payload rate in channelized mode.

B 4.1.1

Yes

C.2.4.1.1(f)(2) DTS service categories supported shall include T3 service to support a line rate of 44.736 Mb/s, which may be used to provide a single 43.008 Mb/s payload in unchannelized mode.

B 4.1.1

Yes

C.2.4.1.1(g) DTS service categories supported shall include Fractional T3 service to support three, four, five, or seven adjacent DS1 clear-channels over an interface of T1 or T3.

B 4.1.1

Yes

C.2.4.1.1(h)(1) DTS service categories supported shall include E1 service to support a line rate of 2.048 Mb/s with 30 separate DS0 clear channels in channelized mode.

B 4.1.1

Yes

C.2.4.1.1(h)(2) DTS service categories supported shall include E1 service to support a line rate of 2.048 Mb/s with a single 1.92 Mb/s information payload in unchannelized mode.

B 4.1.1

Yes

C.2.4.1.2.1(a) DTS shall support Multipoint Connection feature to allow connection of three or more subscribers' premises at a single POP for analog services and for digital services at

B 4.1.2.1

Yes Non Domestic





least up to 56/64 kb/s.

C.2.4.1.2.1(a)(1) DTS Multipoint Connection feature shall support 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.

B 4.1.2.1

Yes Non Domestic

C.2.4.1.2.1(b) The Analog Line Conditioning 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).

B 4.1.2.1

Yes Non Domestic

C.2.4.1.3(a)(1) For performance, 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 4.1.3

Yes

C.2.4.1.3(a)(1) For access performance, 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.2.4.1.3(a)(2) For access performance, 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 4.1.3

Yes

C.2.4.1.3(a)(2) For access performance, all digital transmission parameters shall satisfy ANSI T1.503/510 for T1.

B 4.1.3

Yes

C.2.4.1.3(a)(2) For access performance, all digital transmission parameters shall satisfy Bellcore PUB GR-499-CORE for T3.

B 4.1.3

Yes

C.2.4.1.3(a)(2) For access performance, all digital transmission parameters shall satisfy ITU-TSS G.702 and related recommendations for E1.

B 4.1.3

Yes

C.2.4.1.3(b)(1) The availability of a DTS access circuit shall be at least 99.8 percent.

B 4.1.3

Yes

C.2.4.1.4.1.1(a) User-to-Network Interfaces supported by the contractor shall include: ITU-TSS V.35.

B 4.1.4.1.1

Yes





C.2.4.1.4.1.1(b) User-to-Network Interfaces supported by the contractor shall include: EIA RS 449.

B 4.1.4.1.1

Yes

C.2.4.1.4.1.1(c) User-to-Network Interfaces supported by the contractor shall include: EIA RS 232.

B 4.1.4.1.1

Yes

C.2.4.1.4.1.1(d) User-to-Network Interfaces supported by the contractor shall include: EIA RS-530.

B 4.1.4.1.1

Yes

C.2.4.1.4.1.1(e) User-to-Network Interfaces supported by the contractor shall include: RJ-x (e.g., RJ-11/45).

B 4.1.4.1.1

Yes

C.2.4.1.4.1.1(f) User-to-Network Interfaces supported by the contractor shall include: 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 Notes on the LEC Network [SR-TSV-002275], and ANSI T1.403).

B 4.1.4.1.1

Yes

C.2.4.1.4.1.1(g) User-to-Network Interfaces supported by the contractor shall include: 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 4.1.4.1.1

Yes

C.2.4.1.4.1.1(h) User-to-Network Interfaces supported by the contractor shall include: E1 at line-rate of 2.048 Mb/s and information-payload data-rate of 1.92 Mb/s. (Standard: ITU-TSS G.702).

B 4.1.4.1.1

Yes

C.2.4.1.4.1.1 User-to-Network Interfaces supported by the contractor shall include UNI types as specified in Table C.2.4.1.4.1.1-1.

B 4.1.4.1.1

Yes

C.2.4.1.4.2.1(a) Pursuant to Section C.2.1.16, the Local Access to Network Interfaces supported/provided contractor shall include: T1 and Fractional T1 with ESF (Standard: Bellcore Pub: SR-TSV-2275; ANSI T1.102/107/403).

B 4.1.4.2.1

Yes

C.2.4.1.4.2.1(b) Pursuant to Section C.2.1.16, the Local Access to Network Interfaces supported/provided contractor shall include: T3 and Fractional T3 (Standard: Bellcore Pub: GR-499-CORE).

B 4.1.4.2.1

Yes

C.2.4.1.4.2.1(c) Pursuant to Section C.2.1.16, the Local Access to Network Interfaces supported/provided contractor shall include: E1 for Non-Domestic use (Standard: ITU-TSS G.702).

B 4.1.4.2.1

Yes

C.2.4.1.4.2.1(d) Pursuant to Section C.2.1.16, the Local Access to Network B Yes





Interfaces supported/provided contractor shall include: Analog (Bellcore Pub: SR-TSV-002275).

4.1.4.2.1

C.2.4.1.4.2.1(e) Pursuant to Section C.2.1.16, the Local Access to Network Interfaces supported/provided contractor shall include: DS0 and Subrate DS0 (Bellcore Pub: SR-TSV-002275).

B 4.1.4.2.1

Yes

C.2.4.2.1 The connection between the DTS transport locations shall be permanently established.

B 4.2.1

Yes

C.2.4.2.1 DTS shall comply with ITU T1.503 and all applicable Bellcore and ANSI standards.

B 4.2.1

Yes

C.2.4.2.1 DTS shall comply with primarily ANSI T1.102/107/403 for T1.

B 4.2.1

Yes

C.2.4.2.1 DTS shall comply with Bellcore PUB GR-499-CORE for T3.

B 4.2.1

Yes

C.2.4.2.1 DTS shall comply with ANSI T1.105 and 106 for SONET. B 4.2.1

Yes

C.2.4.2.1 Pursuant to Section C.2.1.16, the contractor shall provide DTS POP-to-POP connections between the contractor’s listed POPs.

B 4.2.1

Yes

C.2.4.2.1 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.

B 4.2.1

Yes

C.2.4.2.1 All bit sequences transmitted shall be treated with data transparency.

B 4.2.1

Yes

C.2.4.2.1 (a) DTS service categories supported shall include analog service with nominal 4 kHz bandwidth.

B 4.2.1.1

Yes

C.2.4.2.1 (b) DTS service categories supported shall include subrate DS0 service at payload data rates of 4.8 and 9.6 kb/s.

B 4.2.1.1

Yes

C.2.4.2.1 (c) DTS service categories supported shall include DS0 service with payload data rates of 56 and 64 kb/s.

B 4.2.1.1

Yes

C.2.4.2.1(d)(1) DTS service categories supported shall include T1 service with line rate of 1.544 Mb/s, which may be used to provide support 24 separate DS0s clear channels of 56/64 kb/s in channelized mode.

B 4.2.1.1

Yes





C.2.4.2.1(d)(2) DTS service categories supported shall include T1 service with line rate of 1.544 Mb/s, which may be used to provide a single 1.536 Mb/s in unchannelized mode.

B 4.2.1.1

Yes

C.2.4.2.1(e) DTS service categories supported shall include Fractional T1 service to 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.

B 4.2.1.1

Yes

C.2.4.2.1(f)(1) DTS service categories supported shall include T3 service to support a line rate of 44.736 Mb/s, which may be used to provide 28 separate DS1 channels of 1.536 Mb/s information payload rate in channelized mode.

B 4.2.1.1

Yes

C.2.4.2.1(f)(2) DTS service categories supported shall include T3 service to support a line rate of 44.736 Mb/s, which may be used to provide a single 43.008 Mb/s payload in unchannelized mode.

B 4.2.1.1

Yes

C.2.4.2.1(g) DTS service categories supported shall include Fractional T3 service to support three, four, five, or seven adjacent DS1 clear-channels over an interface of T1 or T3.

B 4.2.1.1

Yes

C.2.4.2.1(h)(1) DTS service categories supported shall include E1 service to support a line rate of 2.048 Mb/s with 30 separate DS0 clear channels in channelized mode.

B 4.2.1.1

Yes

C.2.4.2.1(h)(2) DTS service categories supported shall include E1 service to support a line rate of 2.048 Mb/s with a single 1.92 Mb/s information payload in unchannelized mode.

B 4.2.1.1

Yes

C.2.4.2.2.1(a) DTS shall support Multipoint Connection feature to allow connection of three or more subscribers' premises at a single POP.

B 4.2.2.1

Yes Non Domestic

C.2.4.2.2.1(a)(1) DTS Multipoint Connection feature shall support 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.

B 4.2.2.1

Yes Non Domestic

C.2.4.2.2.1(b) The Analog Line Conditioning. 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).

B 4.2.2.1

Yes Non Domestic

C.2.4.2.2.1(c) Special Routing feature shall provide different routes for B Yes Non





DTS circuits, for up to T3 data-rate. 4.2.2.1 Domestic

C.2.4.2.2.1(c)(1) Special routing arrangement shall include Transport Diversity between connecting POPs, by supplying two or more physically separated routes for DTS circuits.

B 4.2.2.1

Yes Non Domestic

C.2.4.2.2.1(c)(1) 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.

B 4.2.2.1

Yes Non Domestic

C.2.4.2.2.1(c)(1) The diverse routes shall not share common telecommunications facilities or offices.

B 4.2.2.1

Yes Non Domestic

C.2.4.2.2.1(c)(1) 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.

B 4.2.2.1

Yes Non Domestic

C2.4.2.2.1(c)(1) 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.

B 4.2.2.1

Yes Non Domestic

C.2.4.2.2.1(c)(1) If diversity is not available or the compromised diversity is not acceptable to the Government, it shall be negotiated on an individual case basis.

B 4.2.2.1

Yes Non Domestic

C.2.4.2.2.1(c)(2) For 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.

B 4.2.2.1

Yes Non Domestic

C.2.4.2.2.1(c)(2) 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.

B 4.2.2.1

Yes Non Domestic

C.2.4.2.2.1(c) 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.

B 4.2.2.1

Yes Non Domestic





C.2.4.2.2.1(c) 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.

B 4.2.2.1

Yes

C.2.4.2.2.1(c) The contractor shall provide to the agency, with a copy to the PMO written notification for Government approval of any proposed reconfigurations of routes, previously configured for transport diversity or avoidance at least 30 calendar days in advance of implementation.

B 4.2.2.1

Yes

C.2.4.2.2.1(c) For each diverse or avoidance route the contractor shall conform to the requirements for performance as specified in Section C.2.4.2.3

B 4.2.2.1

Yes

C.2.4.2.3(a)(1) For POP-to-POP transmission performance, 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).

B 4.2.3

Yes

C.2.4.2.3(a)(2) For POP to POP transmission performance, all digital transmission parameters shall satisfy at least the values and ranges set forth in ANSI T1.503/510 for T1

B 4.2.3

Yes

C.2.4.2.3(a)(2) For POP to POP transmission performance, all digital transmission parameters shall satisfy at least the values and ranges set forth in Bellcore PUB GR-499-CORE for T3

B 4.2.3

Yes

C.2.4.2.3(a)(2) For POP to POP transmission performance, all digital transmission parameters shall satisfy at least the values and ranges set forth in ITU-TSS G.702 and related recommendations for E1.

B 4.2.3

Yes

C.2.4.2.3(b)(1) The availability of a DTS transport circuit shall be at least 99.8 percent.

B 4.2.3

Yes

C.2.4.2.4.1.1(a) For the provisioning of DTS transport, pursuant to Section C.2.1.16, the contractor shall support/provide LANI for T1 and Fractional T1 with ESF (Standard: Bellcore

B 4.2.4.1.1

Yes





Pubs: SR-TSV-002275; ANSI T1.102/107/403).

C.2.4.2.4.1.1(b) For the provisioning of DTS transport, pursuant to Section C.2.1.16, the contractor shall support/provide LANI for T3 and Fractional T3 (Standard: Bellcore Pub: GR-499-CORE).

B 4.2.4.1.1

Yes

C.2.4.2.4.1.1(c) For the provisioning of DTS transport, pursuant to Section C.2.1.16, the contractor shall support/provide LANI for E1 for Non-Domestic use (Standard: ITU-TSS G.702).

B 4.2.4.1.1

Yes

C.2.4.2.4.1.1(d) For the provisioning of DTS transport, pursuant to Section C.2.1.16, the contractor shall support/provide LANI for analog (Bellcore Pub: SR-TSV-002275).

B 4.2.4.1.1

Yes

C.2.4.2.4.1.1(e) For the provisioning of DTS transport, pursuant to Section C.2.1.16, the contractor shall support/provide LANI for DS0 and Subrate DS0 (Bellcore Pub: SR-TSV-002275).

B 4.2.4.1.1

Yes


Table J.9.1. Technical Volume Part C.2.7.4



C.2.7.4.1 The VTS shall provide a service whereby participants at different physical locations may conduct interactive dialogues by simulating face-to-face meetings and discussions.

B 12.4.3

Yes

C.2.7.4.1 VTS shall provide point-to-point, and multipoint arrangements for video teleconferencing.

B12.4.3.1

Yes

C.2.7.4.1 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.

B12.4.3.1

Yes

C.2.7.4.1 VTS shall support other value added applications of video services.

B12.4.3.1

Yes

C.2.7.4.1(a) For FTS2001 on-net locations served by the contractor, VTS shall utilize CSDS or DTS available under this contract for the underlying transmission.

B12.4.3.1

Yes

C.2.7.4.1(a) 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.

B12.4.3.1

Yes

C.2.7.4.1(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.

B12.4.3.1

Yes

C.2.7.4.1(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 transport to the contractor’s teleconferencing facility.

B12.4.3.1

Yes

C.2.7.4.1(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).

B12.4.3.1

Yes

C.2.7.4.1(d) VTS shall also support the ITU-TSS T.120 document conferencing standards no later than the date those standards are supported for any of the contractor’s other customers

B12.4.3

Yes

C.2.7.4.1(e) VTS shall support the three user configurations, namely room, rollabout, and desktop.

B12.4.3

Yes






B 12.4.3

Yes

C.2.7.4.1(f) (1) (i)

When the VTS uses CSDS with dedicated access, the service shall be delivered directly to a Government furnished inverse multiplexer.

B12.4.3

Yes

C.2.7.4.1(f) (1) (ii)

When the VTS uses CSDS with dedicated access, the service shall be delivered directly to a Government furnished codec. The contractor shall provide the service to the codec with or without the inverse multiplexing according to the UNI specified.

B12.4.3

Yes

C.2.7.4.1(f) (1) (iii)

When the VTS uses CSDS with dedicated access, the service shall be delivered directly to 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 telecon-ferencing for the desktop configuration shall support computer systems operating under Microsoft Windows 3.x/95/NT operating systems.

B12.4.3

Yes

C.2.7.4.1(f) (2) (i)

When the VTS uses CSDS with circuit switched access or uses DTS, the service shall be delivered directly to a Government furnished codec.

B12.4.3

Yes

C.2.7.4.1(f) (2) (ii)

When the VTS uses CSDS with circuit switched access or uses DTS, the service shall be delivered directly to 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.

B12.4.3

Yes

C.2.7.4.1.1(a)

VTS shall support the capability for room, rollabout, and desktop user configurations for 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

B12.4.3.1.1

Yes






B 12.4.3

Yes

shall be made as provided in Section C.2.7.4.1(b) or C.2.7.4.1(c).

C.2.7.4.1.1(b)

VTS shall support the capability for room, rollabout, and desktop user configurations for multipoint arrangements which shall be provided in conjunction with the contractor’s VTS reservation feature.

B12.4.3.1.1

Yes

C.2.7.4.1.1(b)

The VTS multipoint arrangement shall have the capability of providing service to users of a different FTS2001 contractor’s network on an on-net basis and the users of other public or private networks on an off-net basis.

B12.4.3.1. 1

Yes

C.2.7.4.1.1(b)

The multipoint arrangements shall support full-duplex audio among all participating locations.

B12.4.3.1.1

Yes

C.2.7.4.1.1(b)

During the conduct of a multipoint conference, the addition of a party to, the deletion of a party from the conference shall be announced 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).

B12.4.3.1.1

Yes

C.2.7.4.1.1(b) (1)

The VTS multipoint arrangement shall provide the following capabilities: Voice Activation. The video transmitted to all locations is selected by voice activation, in which the video from a location is selected after audio from that location exceeds a preset level for a specified amount of time.

B12.4.3.1.1

Yes

C.2.7.4.1.1(b) (2)

The VTS multipoint arrangement shall provide the following capabilities: 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 locationsto 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.

B12.4.3.1.1

Yes

C.2.7.4.1.1(b) (3)

The VTS multipoint arrangement shall provide the following capabilities Lecture Control. 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

B12.4.3.1.1

Yes






B 12.4.3

Yes

participating locations. The lecturer can select one or all of the audio signals for transmission to all participants.

C.2.7.4.1.2 VTS shall support the following connection data rates for CSDS and DTS for room, rollabout, and desktop user configurations:

(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)

B12.4.3.1.2

Yes

C.2.7.4.2.1 (a) For the room, rollabout, and desktop configurations, the VTS shall provide a central reservation capability to permit only authorized video teleconference users to schedule and establish multipoint video teleconferences.

B12.4.3.2.1

Yes

C.2.7.4.2.1 (a) For point-to-point video teleconferences reservations that 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.

B12.4.3.2.1

Yes

C.2.7.4.2.1 (a)(1) (i)

The VTS reservation system shall have the capability of a single point of contact with the contractor to schedule reservation-based video teleconferences.

B12.4.3.2.1.1

Yes

C.2.7.4.2.1 (a)(1) (ii)

The VTS reservation system shall have the ability for only 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.

B12.4.3.2.1.1

Yes






B 12.4.3

Yes

C.2.7.4.2.1 (a)(1) (iii)

The VTS reservation system shall have the ability for only VTS authorized users to submit reservation requests up to one year in advance by voice, FAX, E-Mail, and electronic bulletin board.

B12.4.3.2.1.1

Yes

C.2.7.4.2.1 (a)(1) (iv)(A)

The VTS reservation system shall have the ability for the to create printed reports with a directory of all locations authorized to use the VTS reservation system. Inclusion in the directory shall be with approval of the agencies.

B12.4.3.2.1.1

Yes

C.2.7.4.2.1 (a)(1) (iv)(B)

The VTS reservation system shall have the capability to create printed reports with informtion on reservation confirmation and cancellation notices.

B12.4.3.2.1.1

Yes

C.2.7.4.2.1 (a)(1) (iv) (C )(1)

The VTS reservation system shall have the capability of providing monthly performance reports covering the number of video teleconferences scheduled, during prime and non-prime hours, using the reservation feature.

B12.4.3.2.1.1

Yes

C.2.7.4.2.1 (a)(1) (iv) (C )(2)

The VTS reservation system shall have the capability of providing monthly performance reports covering the 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.

B12.4.3.2.1.1

Yes

C.2.7.4.2.1(a)(1) (iv)(C )(3)

The VTS reservation system shall have the capability of providing monthly performance reports covering the 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.

B12.4.3.2.1.1

Yes

C.2.7.4.2.1(a)(1) (iv)(C )(4)

The VTS reservation system shall have the capability of providing monthly performance reports covering the total number of requests (each individual requestfor a particular time and date is considered a 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.

B12.4.3.2.1.1

Yes

C.2.7.4.2.1(a)(1) (v)

The VTS reservation system shall have the capability of providing the ability for the VTS users to schedule a “meet-

B12.4.3.2.1.

Yes






B 12.4.3

Yes

me” reservation based video teleconference. 1

C.2.7.4.2.1(a)(2) (i )

The VTS reservation system shall contain the name of the person scheduling a video teleconference.

B12.4.3.2.1.1

Yes

C.2.7.4.2.1(a)(2) (ii)

The VTS reservation system shall contain the organization of the person scheduling a video teleconference.

B12.4.3.2.1.1

Yes

C.2.7.4.2.1(a)(2) (iii)

The VTS reservation system shall contain the telephone number of the person scheduling a video teleconference.

B12.4.3.2.1.1

Yes

C.2.7.4.2.1(a)(2) (iv)

The VTS reservation system shall contain the name of the contact person at participating locations.

B12.4.3.2.1.1

Yes

C.2.7.4.2.1(a)(2) (v)

The VTS reservation system shall contain the telephone numbers of contact persons at participating locations.

B12.4.3.2.1.1

Yes

C.2.7.4.2.1(a)(2) (vi)

The VTS reservation system shall contain the locations of the persons participating in a video teleconference (at the user’s discretion).

B12.4.3.2.1.1

Yes

C.2.7.4.2.1(a)(2) (vii)

The VTS reservation system shall contain the date of a video teleconference.

B12.4.3.2.1.1

Yes

C.2.7.4.2.1(a)(2) (viii)

The VTS reservation system shall contain the time of a video teleconference.

B12.4.3.2.1.1

Yes

C.2.7.4.2.1(a)(2) (ix)

The VTS reservation system shall contain the scheduled length of a video teleconference.

B12.4.3.2.1.1

Yes

C.2.7.4.2.1(a)(3) (i)

VTS shall provide, VTS reservation users, with the capability to schedule a non-recurring multipoint or point-to-point video teleconference within 30 minutes after the advance reservation request, provided the bridging capacity

B12.4.3.2.1.1

Yes






B 12.4.3

Yes

or the required network functions (i.e., format conversion, rate adaptation, or coding conversion) are available.

C.2.7.4.2.1(a)(3) (ii)

VTS shall provide, VTS reservation users, with the capability based on availability of bridging capacity and required network functions, to request a delay in the scheduled termination time of a video teleconference, which is already in progress, which shall be granted, if the request is made at least 20 minutes before the scheduled terminating time of the video teleconference.

B12.4.3.2.1.1

Yes

C.2.7.4.2.1(a)(3) (iii)

VTS shall provide, VTS reservation users, with the capability to 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.

B12.4.3.2.1.1

Yes

C.2.7.4.2.1(a)(3) (iv)

VTS shall provide, VTS reservation users, with the capability to support a minimum of 25 simultaneous multipoint video teleconferences, with average of 6 locations each at a 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) Rate adaptation

B12.4.3.2.1.1

Yes

C.2.7.4.2.1(b)(1)

The VTS shall provide a coding conversion capability that permits operation between 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).

B12.4.3.2.1.2

Yes

C.2.7.4.2.1(b)(2)

The VTS shall provide a coding conversion capability that permits operation between 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.

B12.4.3.2.1.2

Yes






B 12.4.3

Yes

C.2.7.4.2.1(b)

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.

B12.4.3.2.1.2

Yes

C.2.7.4.2.1(b)

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.

B12.4.3.2.1.2

Yes

C.2.7.4.2.1(c)(1)

The VTS shall provide a video format conversion capability that permits operation between codecs which operate in the NTSC video format and codecs which operate in the Phase Alternation by Line (PAL) video format.

12.4.3.2.1.3

Yes

C.2.7.4.2.1(c)(2)

The VTS shall provide a video format conversion capability that permits operation between codecs which operate in the NTSC video format and codecs which operate in the Système Electronique Couleur Avec Memoire (SECAM) video format.

12.4.3.2.1.3

Yes

C.2.7.4.2.1(c)

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.

12.4.3.2.1.3

Yes

C.2.7.4.2.1(d)

For the room, rollabout, and desktop user configurations, the VTS shall provide unclassified but sensitive level of secure video teleconferencing capability for point-to-point and multipoint video teleconferences.

12.4.3.2.1.4

Yes

C.2.7.4.2.1(e)

The 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 Section C.2.7.4.1.1.2. The rate adaptation feature shall be used in conjunction with the reservation feature.

12.4.3.2.1.5

Yes






B 12.4.3

Yes

C.2.7.4.3(a) (1)

The VTS shall deliver the following digital performance: 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 the contractor delivers as part of the VTS shall be in conformance with the signals required by the user’s codec.

12.4.3.3 Yes

C.2.7.4.3(a) (2)

The VTS shall deliver the following digital performance: When the contractor furnishes the encoding/decoding function the digital performance for data rates specified in Section C.2.7.4.1.1.2 shall be in conformance with FTR 1080 performance at the given data rate employed in the video teleconference.

12.4.3.3 Yes

C.2.7.4.3(b) The availability of the VTS shall be at least 99.5 percent. 12.4.3.3 Yes

C.2.7.4.3(c) 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.

12.4.3.3 Yes

C.2.7.4.3(d) 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.

12.4.3.3 Yes

C.2.7.4.3(d) 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.

12.4.3.3 Yes

C.2.7.4.3(d) 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.

12.4.3.3 Yes

C.2.7.4.4.1 The contractor shall support the interfaces at the SDP 12.4.3.4.1 Yes






B 12.4.3

Yes

specified in Section C.2.7.4.4.1. As part of this support, 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).

C.2.7.4.4.1(a)(1)

The contractor shall support the following interfaces at the SDP: If the government provides the codec and the contractor provides only reservation, coding conversion, and/or format conversion, the UNIs supported shall include ITU-TSS V.35.

12.4.3.4.1 Yes

C.2.7.4.4.1(a)(2)

The contractor shall support the following interfaces at the SDP: If the government provides the codec and the contractor provides only reservation, coding conversion, and/or format conversion, the UNIs supported shall include EIA RS-449.

12.4.3.4.1 Yes

C.2.7.4.4.1(a)(3)

The contractor shall support the following interfaces at the SDP: If the government provides the codec and the contractor provides only reservation, coding conversion, and/or format conversion, the UNIs supported shall include EIA RS-530.

12.4.3.4.1 Yes

C.2.7.4.4.1(a)(4)

The contractor shall support the following interfaces at the SDP: If the government provides the codec and the contractor provides only reservation, coding conversion, and/or format conversion, the UNIs supported shall include T1.

12.4.3.4.1 Yes

C.2.7.4.4.1(a)(5)

The contractor shall support the following interfaces at the SDP: If the government provides the codec and the contractor provides only reservation, coding conversion, and/or format conversion, the UNIs supported shall include E1.

12.4.3.4.1 Yes

C.2.7.4.4.1(a)(6)

The contractor shall support the following interfaces at the SDP: If the government provides the codec and the contractor provides only reservation, coding conversion, and/or format conversion, the UNIs supported shall include

12.4.3.4.1 Yes






B 12.4.3

Yes

RJ-x (e.g., RJ-45).

C.2.7.4.4.1(a)(7)

The contractor shall support the following interfaces at the SDP: If the government provides the codec and the contractor provides only reservation, coding conversion, and/or format conversion, the UNIs supported shall include ISDN PRI.

12.4.3.4.1 Yes

C.2.7.4.4.1(a)(8)

The contractor shall support the following interfaces at the SDP: If the government provides the codec and the contractor provides only reservation, coding conversion, and/or format conversion, the UNIs supported shall include FT1.

12.4.3.4.1 Yes

C.2.7.4.4.1(b)

The contractor shall support the following interfaces at the SDP: 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.

12.4.3.4.1 Yes

C.2.7.4.4.1(c)

The contractor shall support the following interfaces at the SDP: If the contractor provides the inverse multiplexing function and the government provides the codec:

(1) EIA RS-449 (with RS366A)

(2) EIA RS-530 (with RS366A)

(3) ITU-TSS V.35 (with RS366A)

12.4.3.4.1 Yes

C.2.7.4.4.1(d)(1) (i)

If the contractor provides the encoding/decoding function with or without the inverse multiplexing function, the following Video Input/Output interface shall be supported:. NTSC composite analog video signal (according to standards EIA-170 and EIA RS-250).

12.4.3.4.1 Yes

C.2.7.4.4.1(d)(1) (ii)

If the contractor provides the encoding/decoding function with or without the inverse multiplexing function, the following Video Input/Output interface shall be supported: Y/C analog

Y: 1.0 volt peak-to-peak, at 75 ohms

12.4.3.4.1 Yes






B 12.4.3

Yes

C: 0.286 volt peak-to-peak, at 75 ohms

C.2.7.4.4.1(d)(2) (i)

If the contractor provides the encoding/decoding function with or without the inverse multiplexing function, the Line Level Audio Input interface shall be supported.

12.4.3.4.1 Yes

C.2.7.4.4.1(d)(2) (ii)

If the contractor provides the encoding/decoding function with or without the inverse multiplexing function, the Microphone Level Audio Input interface shall be supported.

12.4.3.4.1 Yes

C.2.7.4.4.1(d)(3) (i)

If the contractor provides the encoding/decoding function with or without the inverse multiplexing function, the Line Level Audio Output interface shall be supported.

12.4.3.4.1 Yes

C.2.7.4.4.1(d)(3) (ii)

If the contractor provides the encoding/decoding function with or without the inverse multiplexing function, the Speaker Level Audio Output interface shall be supported.

12.4.3.4.1 Yes

C.2.7.4.4.1(d)(3) (iii)

If the contractor provides the encoding/decoding function with or without the inverse multiplexing function, the Headphone Level Audio Output interface shall be supported.

12.4.3.4.1 Yes

C.2.7.4.4.1(d)(4) If the contractor provides the encoding/decoding function with or without the inverse multiplexing function, the following 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

12.4.3.4.1 Yes

Table J.9.1. Technical Volume Parts C.5 Through C.5.2.7 and C.5.3 Through C.5.6RFP

Section Statement of Requirement Proposal Reference Comply Exception

C.5.2(a) The contractor shall support authorized access for B Yes




providing SVS (see Section C.2.2.1) during emergencies. 9.2

C.5.2(b) The contractor shall support priority treatment for providing SVS (see Section C.2.2.1) during emergencies.

B9.2

Yes

C.5.2(c) The contractor shall support enhanced routing for providing SVS (see Section C.2.2.1) during emergencies.

B9.2

Yes

C.5.2(d) The contractor shall support non-domestic connectivity for providing SVS (see Section C.2.2.1) during emergencies.

B9.2

Yes

C.5.2(e) The contractor shall support interoperability with other networks for providing SVS (see Section C.2.2.1) during emergencies.

B9.2

Yes

C.5.2(f) The contractor shall support switching and signaling augmentation and restoration for providing SVS (see Section C.2.2.1) during emergencies.

B9.2

Yes

C.5.2(g) The contractor shall support protection of classified and sensitive information for providing SVS (see Section C.2.2.1) during emergencies.

B9.2

Yes

C.5.2(h) The contractor shall support assured service for providing SVS (see Section C.2.2.1) during emergencies.

B9.2

Yes

C.5.2.1 The contractor shall provide the capability that will allow FTS2001critical users priority access to the services.

B9.2.1

Yes

C.5.2.1 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.

B9.2.1

Yes

C.5.2.1 An FTS2001 critical user shall have the capability of automatic authorization by assigned COS (derived from access-circuit line-marking, traveling class-mark, ANI or other means).

B

9.2.1

Yes

C.5.2.1 The FTS2001 critical users shall be provided an authorization code that shall override an existing station/line authorization (i.e., COS).

B

9.2.1

Yes

C.5.2.1 The services shall be provided to critical users after proper authorization.

B

9.2.1

Yes

C.5.2.1 The same procedure shall also be used to allow critical B Yes




users to gain access from stations that are not pre-subscribed to FTS2001 by utilizing the SVS switched access capability.

9.2.1

C.5.2.1 Once the authorization code is validated, the call shall be processed.

B

9.2.1

Yes

C.5.2.1 If the authorization code is not valid (for example, if entered incorrectly), the caller shall be prompted to reenter the authorization code.

B

9.2.1

Yes

C.5.2.1 If the authorization code, after three attempts, is again determined to be invalid, the call shall be disconnected.

B

9.2.1

Yes

C.5.2.1 If the automated access authorization system fails, the call shall be processed through a network operator.

B

9.2.1

Yes

C.5.2.1 If the automated access authorization system fails, the call shall be allowed to complete with proper authorization.

B

9.2.1

Yes

C.5.2.2(a) FTS2001 critical users' origination and termination traffic shall receive priority treatment over normal traffic through the use of control mechanisms, such as trunk queuing, trunk subgrouping, or trunk reservation.

B

9.2.2

Yes

C.5.2.2(b) FTS2001 critical users'origination and termination traffic shall receive priority treatment over normal traffic through the use of exemption from restrictive network management controls that are used to reduce network congestion.

B

9.2.2

Yes

C.5.2.2(c) FTS2001 critical users' origination and termination traffic shall receive priority treatment over normal traffic through the use of operator assistance to achieve preferential treatment, such as interrupting an ongoing call.

B

9.2.2

Yes

C.5.2.3 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.

B

9.2.3

Yes




C.5.2.4 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).

B

9.2.4

Yes

C.5.2.4 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.

B

9.2.4

Yes

C.5.2.4 The contractor shall additionally provide operator assistance for priority call handling.

B

9.2.4

Yes

C.5.2.5 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.

B

9.2.5

Yes

C.5.2.5 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.)

B

9.2.5

Yes

C.5.2.5 If requested, the contractor shall support interoperability with other Government networks on an individual case basis.

B

9.2.5

Yes

C.5.2.6 The contractor shall follow best commercial practices to protect its computer systems with regard to NS/EP-related

Mgmt. Volume C

Yes




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 hard copy and electronic media.

C.5.2.6 The information 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.

Mgmt. Volume C

Yes

C.5.2.6 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.

Mgmt. Volume C

Yes

C.5.2.7 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 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.

Mgmt. Volume C

Yes

C.5.2.8 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.

Mgmt. Volume C

Yes

C.5.2.7 The contractor shall annually update its service assurance Mgmt. Yes




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.

Volume C

C.5.3.1(a)(1) During emergency conditions for FTS2001 users, the contractor shall ensure CSDS (i.e., CSDS at DS0 and N x DS0 (where N = 2/6/12) data rates [see Section C.2.2.2]) supports interoperability so that CSDS interoperates with domestic and non-domestic public switched networks to the extent possible for FTS2001 critical users.

B

9.3.1

Yes

C.5.3.1(b)(1) During emergency conditions the contractor shall ensure CSDS (i.e., CSDS at DS0 and N x DS0 (where N = 2/6/12) data rates [see Section C.2.2.2]) supports “denial-of-service” protection for domestic and non-domestic traffic as specified in Section C.2.1.12.2 consistent with best commercial practices for FTS2001 critical users.

B

9.3.1

Yes

C.5.3.1(b)(2) During emergency conditions the contractor shall ensure CSDS (i.e., CSDS at DS0 and N x DS0 (where N = 2/6/12) data rates [see Section C.2.2.2]) ensures authorized access (as specified in Section C.5.2.1) for FTS2001 critical users.

B

9.3.1

Yes

C.5.3.1(b)(3) During emergency conditions the contractor shall ensure CSDS (i.e., CSDS at DS0 and N x DS0 (where N = 2/6/12) data rates [see Section C.2.2.2]) supports the transport of Government encrypted traffic of various security classifications for FTS2001 critical users.

B

9.3.1

Yes

C.5.3.2(a)(1) During emergency conditions for FTS2001critical users, the contractor shall ensure that IPS interoperates with domestic and non-domestic public switched IP networks to the extent possible.

B

9.3.2

Yes

C.5.3.2(a)(2) During emergency conditions for FTS2001 critical users, the contractor shall ensure SDS supports Internet addressing plan (as specified in Section C.2.3.3.1).

B

9.3.2

Yes

C.5.3.2(a)(3) During emergency conditions for FTS2001 critical users, the contractor shall ensure SDS supports an interface with Internet.

B

9.3.2

Yes

C.5.3.2(b)(1) During emergency conditions for FTS2001 critical users, the contractor shall ensure SDS supports priority traffic handling when available commercially.

B

9.3.2

Yes




C.5.3.2(c)(1) During emergency conditions for FTS2001 critical users, the contractor shall ensure SDS supports denial-of-service protection for domestic and non-domestic traffic consistent with best commercial practices.

B

9.3.2

Yes

C.5.3.2(c)(2) During emergency conditions for critical users, the contractor shall ensure SDS supports ensure authorized access (as specified in Section C.5.2.1).

B

9.3.2

Yes

C.5.3.2(c)(3) During emergency conditions for FTS2001 critical users, the contractor shall ensure SDS supports transport of Government encrypted traffic of various security classifications.

B

9.3.2

Yes

C.5.3.2(d)(1) During emergency conditions for FTS2001 critical users, the contractor shall ensure SDS provides diverse routing and robustness in the backbone.

B

9.3.2

Yes

C.5.3.2(d)(2) During emergency conditions for cFTS2001 ritical users, the contractor shall ensure SDS supports routing via Internet if the contractor's FTS2001 network is unable to handle traffic demands.

B

9.3.2

Yes

C.5.4.1(a) To provide network facility augmentation and restoration during times of stress, the contractor shall, at a minimum, utilize 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

9.3.3

Yes

C.5.4.1(b) To provide network facility augmentation and restoration during times of stress, the contractor shall, at a minimum, utilize 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.

B

9.3.3

Yes

C.5.4.1.1(a) To provide transmission augmentation and restoration during times of stress, the contractor shall, at a minimum utilize 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.

B

9.3.3

Yes

C.5.4.1.1(b) To provide transmission augmentation and restoration B Yes




during times of stress, the contractor shall, at a minimum utilize commercial networks for providing transmission augmentation using terrestrial, fiber optic, microwave, and transportable capabilities.

9.3.3

C.5.4.1.1(c) To provide transmission augmentation and restoration during times of stress, the contractor shall, at a minimum utilize rapid restoration of network transmission facilities by deployment of such techniques as SONET self-healing architecture.

B

9.3.3

Yes

C.5.4.1.2 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.

B

9.3.3

Yes

C.5.4.2 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.

B

9.3.3

Yes

C.5.4.2 The contractor shall fully comply with any future TSP replacement system.

B

9.3.3

Yes

C.5.2.7 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.

Mgmt Volume C

Yes

C.5.5 Common channel signaling (ITU-TSS No. 7 or SS7) paths shall be protected.

B

9.5

Yes

C.5.5 This protection shall not preclude the use of encryption equipment endorsed under the NSA Commercial COMSEC Endorsement Program (CCEP) or any other NIST/NSA approved encrypted/non-encrypted forms of protection.

B

9.5

Yes

C.5.6 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).

B

9.6

Yes

C.5.6 However, if there are other measures available that can B Yes




mitigate command-link takeover, they shall be utilized wherever economical and approved on a prior basis by the Government.

9.6


Table J.9.1. Technical Volume Parts C.6.2 and C.6.3



C.6.2 The contractor shall provide in its monthly report the specific performance-related reports specified in Sections C.6.2.1 through C.6.2.3.1 for each service being delivered under the contract as described in Section C.2.

B

10.0

Yes

C.6.2.1.1.1 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.

B

10.1.1.1

Yes

C.6.2.1.1.2 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.

B

10.1.1.2

Yes

C.6.2.1.2.1 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.

B

10.1.2.1

Yes

C.6.2.1.2.2 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.

B

10.1.2.2

Yes

C.6.2.1.3 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.

B

10.1.3

Yes

C.6.2.1.4 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.

B

10.1.4

Yes

C.6.2.1.5 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.

B

10.1.5

Yes

C.6.2.1.6 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.

B

10.1.6

Yes

C.6.2.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.1.

B

10.2.1.1

Yes


Table J.9.1. Technical Volume Parts C.6.2 and C.6.3



C.6.2.2.1.2 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.

B10.2.1.2

Yes

C.6.2.2.2.1 The contractor shall report on monthly transmission performance for each type of SDS. The report shall include the data elements listed in IEG Section B.5.6.2.2.1.

B10.2.2.1

Yes

C.6.2.2.2.2 The contractor shall report on transmission performance for each type of SDS. The report shall include the data elements listed in IEG Section B.5.6.2.2.2.

B10.2.2.2

Yes

C.6.2.3.1 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.

B10.3.1

Yes

C.6.2.4 The contractor shall report on the availablility of the Video Teleconferencing Service as specified in IEG Section B.5.6.2.

B10.4

Yes

C.6.2.4 The contractor shall also provide monthly performance reports as specified in Section C.2.7.4.

B10.4

Yes

C.6.3.1 Each Government business day, the contractor shall provide a “morning report” containing the data elements listed in IEG Section B.5.7.1.

B 11.1

Yes

C.6.3.1 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.

B 11.1

Yes


Table J.9.1. Technical Volume Part L



L.2(b)(i) The offeror shall provide information, other than cost and pricing data, for but not limited to optional items, contractor-specific services and features not listed in the RFP, and alternate proposals.

All Volumes

Yes

L.2(c) The information shall be submitted in the electronic format described in Section L.37.1.

All Volumes

Yes

L.9 The offeror shall identify each requirement, clause, provision or term and condition for which exceptions and/or deviations are requested in the appropriate volume of its proposal.

All Volumes

Yes

L.14 The offeror's attention is called to the requirement that any restrictions on the Government concerning use or disclosure of computer software that was developed at private expense and is to be delivered under the contract must be set forth in an agreement to be negotiated prior to award and made a part of the contract. Therefore, the offeror shall identify in its proposal, to the extent feasible, any such computer software that was developed at private expense and upon which it desires to negotiate restrictions, and shall state the nature of the proposed restrictions.

All Volumes

Yes

L.16(b) The oral presentation by the offeror shall include a technical response to requirements.

All Volumes

Yes

L.16(d) The oral presentation by the offeror shall include technical plans and procedures.

N/A Yes

L.16(g) The oral presentation by the offeror shall include IPS interoperability.

N/A Yes

L.16(h) The oral presentation by the offeror shall include emerging services.

N/A Yes

L.16(i) The oral presentation by the offeror shall include security. N/A Yes

L.16(j) The oral presentation by the offeror shall include switched data plans incorporating technical aspects.

N/A Yes

L.17(a) Changes in proposal revisions/updates shall be submitted in the same hardcopy and electronic copy quantities as required for the initial proposal submission for all proposal revisions/updates.

All Volumes

Yes





L.17(a) Electronic revision submissions shall conform with the organization and format requirements for the original submission as described in Section L.37.1.

All Volumes

Yes

L.17(a) For Electronic submissions, the offeror shall resubmit in its entirety the lowest-level numbered section of its proposal that contains the change. Such changed sections shall be digitally signed in the same way as the original proposals.

All Volumes

Yes

L.17(c) The offeror shall submit hardcopy changes as complete change pages.

N/A N/A

L.17(c) Changes shall be indicated by vertical lines adjacent to the change in the right margin to indicate any change that has been made.

N/A N/A

L.17(d) Offeror shall include the date of the modification in the lower right hand corner at the bottom of the respective page.

N/A N/A

L.17(d) For inserted pages, offeror shall number each page using an alphanumeric designator (e.g., 1, 1a, 1b, 2, 3, if two pages are inserted between pages 1 and 2).

N/A N/A

L.17(e) Offeror shall maintain the separation of cost and pricing data as specified for the original proposal submission for changes that involve pricing data.

All Volumes

Yes

L.18 The offeror shall be the prime contractor for procurement of the services offered.

All Volumes

Yes

L.20 Offerors shall make available to the auditor(s) all books and financial records considered by the auditor(s) to be essential in the discharge of their duties under Part 15.8 of the FAR whenever the audit is conducted.

Business Volume

Yes

L.23.1 Offerors may submit more than one proposal in response to this solicitation provided that each proposal addresses and meets all requirements specified herein. If multiple proposals are submitted, each proposal shall be clearly labeled and identified on the cover page of each separate document.

N/A N/A

L.23.1 If multiple proposals are submitted, the reason for each additional proposal and its comparative benefits shall be explained.

N/A N/A





L.23.1 Each page of each multiple proposal shall identify the proposal to which it belongs.

N/A N/A

L.23.1 Each multiple proposal shall be a complete offer in and of itself.

N/A N/A

L.31 Each volume shall include the following components: N/A N/A

L.31(a) Each volume's cover page shall include the solicitation name, solicitation number, volume name, volume number, date, name(s) of responding organization(s), and revision number if appropriate.

Cover Pages for all Volumes

Yes

L.31(b) Each proposal volume shall have a table of contents. All Volumes

Yes

L.31(c) Each proposal shall contain Information Requested in Instructions.

All Volumes

Yes

L.31 Electronic media versions of the volumes as specified in Section L.37.1 shall be digitally signed by the official authorized to bind the responding organization(s).

All Volumes

Yes

L.37 The maximum number of pages in the Technical Volume is 1,200.

Technical Volume

Yes

L.37 Each volume shall contain an Executive Summary. The Executive Summary shall be written so that a lay person can easily grasp the essence of the network design.

All Volumes

Yes

L.37 The Executive Summary shall not exceed seven (7) pages and shall contain no price information.

All Volumes

Yes

L.37 Each volume shall contain the cross-reference table requirements in the RFP to the appropriate sections of the proposal for that volume.

All Volumes

Yes

L.37 If additional offerings (optional) are offered, the offeror shall provide complete Table J.9.5 as appropriate providing cross-references between optional requirements that are addressed and its proposal. These tables shall be provided in the addenda to the offeror’s proposal that address optional items only.

L.37.1.1(a)(1) Four master copies of the technical proposal shall be submitted as specified in (1) below:

Technical Volume

Yes





Technical Proposal Files on CD-ROM. All word processing files (containing embedded graphical, spreadsheet, multimedia, or other objects) that comprise the Technical Volume.

L.37.1.1(a)(1) The offeror shall also provide all embedded object files in their native formats, subject to the restrictions enumerated in Sections L.37.1.5 and L.37.1.6.

All Volumes

Yes

L.37.1.1(a)(1) No file on this CD-ROM shall contain any price information.

All Files Yes

L.37.1.1(a)(1) Each copy shall be digitally signed according to further instructions as specified in Section L.31 before being recorded on the CD-ROM.

All Volumes

Yes

L.37.1.2 Offerors shall submit CD-ROMs (650 megabyte nominal capacity) that are written in compliance with the International Organization for Standardization-9660 standard for file format structure.

All Volumes

Yes

L.37.1.2 Each CD-ROM’s root directory shall contain a text file named 00README.TXT that explains the volume’s directory structure, briefly describes each file’s contents, and lists the name and telephone number of the offeror’s technical point of contact who can answer questions in the event of problems in reading the contents of the CD-ROM.

All CDs Yes

L.37.1.4 All word processing files provided on the CD-ROMs shall be written in Microsoft Word 97 format with all external objects embedded (not linked).

All CDs Yes

L.37.1.4 The Word documents shall be organized at the major section level of the proposal volume to which they belong, and further partitioned into separate Word documents at the subsection or lower level, as required for convenient viewing.

All Volumes

Yes

L.37.1.4 All word documents shall be submitted with all revisions accepted by the offeror; no revision marks shall be visible to the Government.

All Volumes

Yes

L.37.1.5 Image files provided on the Master CD-ROMs shall be stored in one of the formats listed below, as appropriate:

(a) Bitmapped images are to be stored in either Graphics Interchange Format (87a or 89a, interlaced or

All Volumes

Yes





non-interlaced formats) or Joint Photographic Experts Group (JPEG) image formats

L.37.1.5 Vectored images are to be stored in Windows MetaFile format (must be recognizable in Word 97); however, graphics created within PowerPoint as part of a PowerPoint presentation are to be stored in PowerPoint presentation (.ppt) format.

All Volumes

Yes

L.37.1.6 Embedded multimedia objects shall be playable with either QuickTime 32 version 2.1.2 (.mov or .mpg format) or the Media Player provided with Windows (.avi format).

All Volumes

Yes

L.37.1.7 Files delivered on any of the CD-ROMs may be compressed using WinZip for Windows 95, available via the Internet at http://www.winzip.com/win95d/winzip.htm. This is an external file compression utility that generates files with a zip file extension. Single files or groups of files compressed into a single zip file must be contained on a single CD-ROM. A compressed single file shall not “span” across multiple CD-ROMs. File compression that is a standard characteristic of the file format (e.g., JPEG) is permitted. However, there shall be no reliance on hardware decompression to allow a file to be viewed at its intended image size, resolution, and/or speed (e.g., requiring a hardware codec to play a video file at an acceptable frame rate).

All Volumes

Yes

L.37.2 Six copies of any hardcopy items shall be provided at time of proposal submission.

Separately Bound

Yes

L.37.3 Additional technical information, equipment specifications, operating documentation of a detailed nature, and similar material may be submitted as appendices to the proposal at the offeror’s option. Such appendices shall be clearly marked as to their contents and purpose, and shall be referenced in the main body of the proposal so that they can be associated with any of the four proposal volumes where appropriate.

Appendices

Yes

L.38 Each volume shall be separate and complete in itself. For each volume, the offeror shall present information in sufficient detail to enable an evaluator, having a general professional expertise in the response area of interest, to adequately and thoroughly understand the response to this solicitation. The detail shall be such that no reference to

All Volumes

Yes





other volumes of the proposal or to non-proposal material would be required to understand the offeror’s response, and that the proposal clearly demonstrates the offeror’s ability to perform in accordance with the Government’s requirements.

L.38 Information on corporate qualifications and past performance shall be provided identically in both the Technical and Management proposals.

Technical and Management Volumes

Yes

L.38(a) The proposal shall include appropriate diagrams (e.g., network architecture) showing the functional and, as required, physical interfaces associated with meeting a requirement.

A,B Yes

L.38(b) The proposal shall include identification and examples of the offeror’s capability in that area.

B Yes

L.38(c) The proposal shall include identification and examples of proposed subcontractor’s capability in that area.

N/A Yes

L.38(d)(1) The proposal shall include identification of new or additional technology, systems, processes, procedures or capabilities that the offeror and/or subcontractor would require to fulfill the requirements of this solicitation including the proposed schedule for obtaining this technology, systems, processes, procedures, or capabilities.

V1.A.1.0 Yes

L.38(d)(2) The proposal shall include identification of new or additional technology, systems, processes, procedures or capabilities that the offeror and/or subcontractor would require to fulfill the requirements of this solicitation including staffing (quantity of personnel by types of skill levels and brief resume of that skill level) required to develop or otherwise provide the technology/capability.

V1.A.1.0 Yes

L.38(e) The proposal shall include other pertinent information the offeror believes will assist the evaluator to understand the offeror’s response.

B Yes

L.38 The offeror’s proposal shall clearly demonstrate its ability and capability as contractor to perform in accordance with the Government’s requirements.

B Yes

L.38 Any offeror restrictions on disclosure of data shall be in accordance with Section L.1.8, Restriction on Disclosure

All Volumes

Yes





and Use of Data.

L.38.1 The offeror shall prepare its Technical Proposal to address all mandatory requirements specified in this RFP.

Technical Proposal

Yes

L.38.1 The proposal shall address the mandatory requirements identified in Sections C.2, C.5.1 through C.5.2.6, C.5.2.9 through C.5.6, C.6.2, and C.6.3.

Technical Proposal

Yes

L.38.1 The Technical Proposal shall be divided into three parts (Technical Approach to Service Delivery, Service and Feature Descriptions, and Corporate Qualification and Past Performance References) plus all specific plans and descriptions associated with the Technical Proposal.

Technical Proposal

Yes

L.38.1 No prices or other cost information shall be included in any of these sections of the Technical Proposal.

Technical Proposal

Yes

L.38.1(a)(1) The Technical Approach to Service Delivery shall analyze the service requirements specified in this solicitation.

A 1.0

Yes

L.38.1(a)(2) The Technical Approach to Service Delivery shall propose logical and reasonable approaches to service delivery.

A 2.0

Yes

L.38.1(a)(3) The Technical Approach to Service Delivery shall describe the problems that could be encountered in meeting the requirements, and propose solutions to any foreseen problems.

A 3.0

Yes

L.38.1(b) The Service and Feature Descriptions Technical Proposal shall describe in detail each of the services.

B Yes

L.38.1(b) The offeror's response to all requirements shall be provided in detail in this section.

B Yes

L.38.1(b)(1) All mandatory and optional items offered shall be described in detail to include a technical description of the capability.

B Yes (mandatory items)

L.38.1(b)(2) All mandatory and optional items offered shall be described in detail to include proposed performance standards (for optional items).

B Yes

(mandatory items)

L.38.1(c) For Corporate Qualification and Past Performance References, the offeror shall provide client references capable of documenting the offeror’s performance on

B Yes





similar contracts.

L.38.1.1 The offeror shall describe the means by which the requirements specified in Section C will be delivered to the Government.

A 2.0

Yes

L.38.1.1(a) The offeror shall address the overall network architecture, including the types and capacity of the transmission and switching media, the transmission facility(ies) configuration, and the type of equipment used in its network.

A 2.1 B 2.0

Yes

L.38.1.1(b) The offeror shall address the rationale for the network architecture design.

A 2.2 B 2.0

Yes

L.38.1.1(c) The offeror shall address the congestion and flow control strategy including redundant switch and transmission facilities, control mechanisms, and the degree of flexibility inherent in the architectural design to handle predicted and unpredicted increased traffic loads and/or switch and transmission failures.

A 2.3 B 2.0

Yes

L.38.1.1(d) The offeror shall address the amount of the offeror’s equipment that would be required at Government locations to deliver the services, including the amount of power, floor space, along with heating, ventilation, and air conditioning loads.

A 2.4 B 2.0

Yes

L.38.1.1(e) The offeror shall address traffic calculations that indicate network and service performance during estimated normal, 10 percent, 25 percent, and 50 percent above the estimated normal FTS2001 traffic loads and the means to ensure achieving the required performance as specified in this solicitation.

A 2.5 B 2.0

Yes

L.38.1.1(f) The offeror shall address an assessment of the impact of various levels of feature usage on service performance.

A 2.6 B 2.0

Yes

L.38.1.1(g) The offeror shall address description of network control and diagnostic capabilities and systems, including equipment and procedures for monitoring and testing each of the services and associated features.

A 2.7 B 2.0

Yes

L.38.1.1(h) The offeror shall address network transmission and synchronization plans for the various services.

A 2.8 B 2.0

Yes





L.38.1.1(i) The offeror shall address the approach for incorporating into the offeror’s network, at some future time, the emerging services listed in Section C.2.8that the offeror believes is likely to become commercially available in the time frame covered by this acquisition, including discussion of potential problems and proposed solutions.

A 2.9 B 2.0

Yes

L.38.1.1(j) The offeror shall address the approach for adapting the offeror’s network and services to meet the Government’s evolving service requirements.

A 2.10 B 2.0

Yes

L.38.1.1(k) The offeror shall address the offeror’s ability to meet the domestic and international service coverage requirements including limitations in current coverage (especially non-domestic dedicated access) and the offeror’s plans for increasing this coverage after contract award and during the term of the contract, including explicit lists of where and when services and features will be offered.

A2.11B2.0

Yes

L.38.1.1(l) The offeror shall address the performance standards associated with the international carriers and service providers the offeror proposes to use.

A 2.12 B 2.0

Yes

L.38.1.1(m) The offeror shall address the network evolution approach to optimizing the Government’s switched data cost-effectiveness (e.g., by extending network concentration and switching point).

A 2.13 B 2.0

Yes

L.38.1.1(o) The offeror shall address the approach to achieve IPS interoperability.

A 2.14 B 2.0

Yes

L.38.1.2 The offeror shall describe in detail the basic service and all mandatory features specified for each of the services in Section C that it is proposing.

C Yes

L.38.1.2 The Service and Features Descriptions section of the offeror’s proposal shall be organized according to the order of the services in Section C.

C Yes

L.38.1.2(a) The offeror’s Service and Features Descriptions section shall include the ability of the offeror to provide the services as specified.

C Yes

L.38.1.2(b) The offeror’s Service and Features Descriptions section shall include the ability of the offeror to provide the complete set of mandatory features for each service.

C Yes





l.38.1.2(c) The offeror’s Service and Features Descriptions section shall include any modifications required of the offeror’s network in order to support and/or deliver any of the services and their associated features.

C Yes

L.38.1.2(d) The offeror’s Service and Features Descriptions section shall include any unique requirements, special interfaces, or limitations regarding the implementation of the services and associated features at the Service Delivery Points (SDPs).

C Yes

L.38.1.2(e) The offeror’s Service and Features Descriptions section shall include any special contractor equipment required at the SDPs in order to deliver the services.

C Yes

L.38.1.3.1 The offeror shall provide a detailed description of its response to the tables that are provided in Section J.8.

C Yes

L.38.1.3.1 For each SDS service where the offeror is providing local telephone numbers for dial-in users, the offeror shall provide a list of cities where local calling is supported.

C Yes

L.38.1.3.1 The offeror shall provide information on the geographic unavailability of all domestic and non-domestic access and transport Circuit Switched Service, Service Data Service (SDS) and Dedicated Transmission Service features by completing Tables C.2.1.2-1 through C.2.1.2-4, except for the right-most column of each table.

C Yes

L.38.1.3.2 The offeror shall provide a Numbering and Addressing Plan with its proposal in accordance with Section C.2.1.6.

C Yes

L.38.1.3.2 The offeror shall identify numbers to be reserved for special uses, such as access to network operators, trouble reporting, or other special applications, as described in Section C.2.2.1.2.1.

C Yes

L.38.1.3.3 The offeror shall provide a security plan, as part of its proposal, that addresses in detail its security solutions for supporting the security requirements, as described in Sections C.2.1.1.2, C.2.1.12 and C.3.7.5.

C Yes

L.38.1.3.3 This security plan shall include a description of risk analyses that shall be undertaken by the contractor after award.

C Yes

L.38.1.3.4 The offeror shall provide with its proposal a plan for implementing IPS interoperability as specified in

C Yes





Section C.2.1.11.

L.38.1.3.4 This plan for implementing IPS interoperability shall address interoperability in sufficient detail to permit the Government to gain a thorough understanding of the offeror’s interoperability approach and to verify the soundness of the approach.

C Yes

L.38.1.3.5 The offeror shall provide with its proposal a plan for optimizing the provisioning of Switched Data Service (SDS).

C Yes

L.38.1.3.5 The plan shall include descriptions of how the contractor would utilize technology (e.g., remote concentration and/or switching capabilities and wide band transmission facilities [possibly including satellite transmission]), to enhance the proposed network architecture, optimize performance, encourage migration from private networks, and minimize cost of SDS for the Government as a whole (all authorized users), for an individual agency, or for a specific application.

C Yes

L.38.1.3.5 If applicable, the offeror shall include the possibility of initiating a consolidated access solution for areas where large concentrations of Government data applications exist.

BC

Yes

L.38.1.4 Offerors shall submit with their Technical Proposal six references as specified in Section L.38.2.5.

D 1.0

Yes

L.38.1.4 The references submitted with the Technical Proposal shall be the same as those submitted with the Management Proposal.

D 1.0

Yes


Table J.9.1A. Technical Volume Part C.2

RFP Section

Item Exceeding Basic Requirements (these are not mandatory)

Certification that there is No Additional

Charge Over the Life of the Contract

Proposal Reference

C.2.2.1.2.1 The contractor may exceed the basic requirements SVS Transport 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.

Yes B.2.1.2.1

C.2.2.2.1.1(f) The contractor may exceed the basic requirements for CSDS Access 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 Multirate DS1 category of information-payload bandwidth. 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.

YesWhen commercially available

B.2.2.1.1.2

C.2.2.2.1.1(g) The contractor may exceed the basic requirements for CSDS Access 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 DS3 category of information-payload bandwidth. For this category of service, the dialable bandwidth would be DS3 (i.e., 43.008 Mb/s) data rate.


B.2.2.1.1.2

C.2.2.2.1.1(h) The contractor may exceed the basic requirements for CSDS Access 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 SONET Level-I (i.e., OC-1) category of information-payload bandwidth. For this category of service, the dialable information-payload bandwidth would be SONET OC-1 (i.e., 49.536 Mb/s) data rate.


B.2.2.1.1.2

C.2.2.2.1.1(i) The contractor may exceed the basic requirements for CSDS Access 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 SONET Level -II (i.e., Multirate OC-1) category of information-payload bandwidth. 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.


B.2.2.1.1.2



RFP Section




Proposal Reference

C.2.2.2.1.1(j) The contractor may exceed the basic requirements for CSDS Access 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 SONET Level -III (i.e., Multirate OC-3) category of information-payload bandwidth. 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.


B.2.2.1.1.2

C.2.2.2.2.1 The contractor may exceed the basic requirements for CSDS Transport 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.


B.2.2.2.1

C.2.2.2.2.1(d) If the contractor exceeds the basic CSDS Transport requirements then CSDS would support the Multirate DS1 Category of information-payload bandwidth. 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.


B.2.3.1.1

C.2.2.2.2.1(e) If the contractor exceeds the basic CSDS Transport requirements then CSDS would support the DS3 Category of information-payload bandwidth. For this category of service, the dialable bandwidth would be DS3 (i.e., 43.008 Mb/s) data rate.


B.2.3.2.1

C.2.2.2.2.1(f) If the contractor exceeds the basic CSDS Transport requirements then CSDS would support the SONET Level-I (i.e., OC-1) Category of information-payload bandwidth. For this category of service, the dialable information-payload bandwidth would be SONET OC-1 (i.e., 49.536 Mb/s) data rate.


B.2.4.1.1

C.2.2.2.2.1(g) If the contractor exceeds the basic CSDS Transport requirements then CSDS would support the SONET Level-II (i.e., Multirate OC-1) Category of information-payload bandwidth. For this category of service, the dialable information-payload bandwidth would be available from SONET OC-1 to N times OC-1 data rates, where N varies from two to three.


B.2.4.1.1

C.2.2.2.2.1(h) If the contractor exceeds the basic CSDS requirements Yes B.2.2.2.1.2



RFP Section




Proposal Reference

when CSDS is provided via switched access arrangement, the additional capabilities would be 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.

When commercially available

C.2.3.1.1.1(a) The contractor may exceed the basic requirements by providing PSS access via an internetworked access arrangement (see Section C.2.1.16). When this access is provided the capability for a DTE to send and receive data by setting up Permanent Virtual Circuits (PVC) and/or Switched Virtual Circuits (SVC) would be supported.

Yes B.3.1.1.1.1

C.2.3.1.1.1(b) The contractor may exceed the basic requirements by providing PSS access via an internetworked access arrangement (see Section C.2.1.16). When this access is provided the capability to support a numbering plan that would follow the ITU-TSS X.121 numbering plan would be supported.

Yes B.3.1.1.1.1

C.2.3.1.1.1(c)(1) The contractor may exceed the basic requirements by providing PSS access via an internetworked access arrangement (see Section C.2.1.16). When this access is provided the contractor would support the capability for reverse charging as specified in FIPS-PUB 100-1.

Yes B.3.1.1.1.1

C.2.3.1.1.1(c)(2) The contractor may exceed the basic requirements by providing PSS access via an internetworked access arrangement (see Section C.2.1.16). When this access is provided the contractor would support the capability for reverse charging acceptance as specified in FIPS-PUB 100-1.

Yes B.3.1.1.1.1

C.2.3.1.1.1(c)(3) The contractor may exceed the basic requirements by providing PSS access via an internetworked access arrangement (see Section C.2.1.16). When this access is provided the contractor would support the capability for local charging prevention as specified in FIPS-PUB 100-1.

Yes B.3.1.1.1.1

C.2.3.1.1.1(c)(4) The contractor may exceed the basic requirements by providing PSS access via an internetworked access arrangement (see Section C.2.1.16). When this access is provided the contractor would support the capability for

Yes B.3.1.1.1.1



RFP Section




Proposal Reference

nonstandard default packet size as specified in FIPS-PUB 100-1.

C.2.3.1.1.1(c)(5) The contractor may exceed the basic requirements by providing PSS access via an internetworked access arrangement (see Section C.2.1.16). When this access is provided the contractor would support the capability for nonstandard default window size as specified in FIPS-PUB 100-1.

Yes B.3.1.1.1.1

C.2.3.1.1.1(c)(6) The contractor may exceed the basic requirements by providing PSS access via an internetworked access arrangement (see Section C.2.1.16). When this access is provided the contractor would support the capability for incoming calls barred as specified in FIPS-PUB 100-1.

Yes B.3.1.1.1.1

C.2.3.1.1.1(c)(7) The contractor may exceed the basic requirements by providing PSS access via an internetworked access arrangement (see Section C.2.1.16). When this access is provided the contractor would support the capability for outgoing calls barred as specified in FIPS-PUB 100-1.

Yes B.3.1.1.1.1

C.2.3.1.1.1(c)(8) The contractor may exceed the basic requirements by providing PSS access via an internetworked access arrangement (see Section C.2.1.16). When this access is provided the contractor would support the capability for one-way logical channel outgoing as specified in FIPS-PUB 100-1.

Yes B.3.1.1.1.1

C.2.3.1.1.1(c)(9) The contractor may exceed the basic requirements by providing PSS access via an internetworked access arrangement (see Section C.2.1.16). When this access is provided the contractor would support the capability for one-way logical channel incoming as specified in FIPS-PUB 100-1.

Yes B.3.1.1.1.1

C.2.3.1.1.1(c)(10)

The contractor may exceed the basic requirements by providing PSS access via an internetworked access arrangement (see Section C.2.1.16). When this access is provided the contractor would support the capability for default throughput classes assignment as specified in FIPS-PUB 100-1.

Yes B.3.1.1.1.1

C.2.3.1.1.1(c)(11)

The contractor may exceed the basic requirements by providing PSS access via an internetworked access arrangement (see Section C.2.1.16). When this access is provided the contractor would support the capability for flow control parameter negotiation as specified in FIPS-PUB 100-1.

Yes B.3.1.1.1.1



RFP Section




Proposal Reference

C.2.3.1.1.1(c)(12)

The contractor may exceed the basic requirements by providing PSS access via an internetworked access arrangement (see Section C.2.1.16). When this access is provided the contractor would support the capability for throughput class negotiation as specified in FIPS-PUB 100-1.

Yes B.3.1.1.1.1

C.2.3.1.1.1(c)(13)

The contractor may exceed the basic requirements by providing PSS access via an internetworked access arrangement (see Section C.2.1.16). When this access is provided the contractor would support the capability for 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 as specified in FIPS-PUB 100-1.

Yes B 3.1.1.1.1

C.2.3.1.1.1(c)(14)

The contractor may exceed the basic requirements by providing PSS access via an internetworked access arrangement (see Section C.2.1.16). When this access is provided the contractor would support the capability for fast select as specified in FIPS-PUB 100-1.

Yes B.3.1.1.1.1

C.2.3.1.1.1(c)(15)

The contractor may exceed the basic requirements by providing PSS access via an internetworked access arrangement (see Section C.2.1.16). When this access is provided the contractor would support the capability for fast select acceptance as specified in FIPS-PUB 100-1.

Yes B.3.1.1.1.1

C.2.3.1.1.1(c)(16)

The contractor may exceed the basic requirements by providing PSS access via an internetworked access arrangement (see Section C.2.1.16). When this access is provided the contractor would support the capability for hunt group facilities, including round robin, closest, and ordered list as specified in FIPS-PUB 100-1.

Yes B.3.1.1.1.1

C.2.3.1.1.1(c)(17)

The contractor may exceed the basic requirements by providing PSS access via an internetworked access arrangement (see Section C.2.1.16). When this access is provided the contractor would support the capability for 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 as specified in FIPS-PUB 100-1.

Yes B.3.1.1.1.1

C.2.3.1.1.1(c)(18)

The contractor may exceed the basic requirements by providing PSS access via an internetworked access arrangement (see Section C.2.1.16). When this access is

Yes B.3.1.1.1.1



RFP Section




Proposal Reference

provided the contractor would support the capability for transit delay selection and notification as specified in FIPS-PUB 100-1.

C.2.3.1.1.1(c)(19)

The contractor may exceed the basic requirements by providing PSS access via an internetworked access arrangement (see Section C.2.1.16). When this access is provided the contractor would support the capability for abbreviated address calling as specified in FIPS-PUB 100-1.

Yes B.3.1.1.1.1

C.2.3.1.1.1(c)(20)

The contractor may exceed the basic requirements by providing PSS access via an internetworked access arrangement (see Section C.2.1.16). When this access is provided the contractor would support the capability for charging information as specified in FIPS-PUB 100-1.

Yes B.3.1.1.1.1

C.2.3.1.1.1(c)(21)

The contractor may exceed the basic requirements by providing PSS access via an internetworked access arrangement (see Section C.2.1.16). When this access is provided the contractor would support the capability for call redirection notification as specified in FIPS-PUB 100-1.

Yes B.3.1.1.1.1

C.2.3.1.1.1(c)(22)

The contractor may exceed the basic requirements by providing PSS access via an internetworked access arrangement (see Section C.2.1.16). When this access is provided the contractor would support the capability for called line address modification notification as specified in FIPS-PUB 100-1.

Yes B.3.1.1.1.1

C.2.3.1.1.1(c)(23)

The contractor may exceed the basic requirements by providing PSS access via an internetworked access arrangement (see Section C.2.1.16). When this access is provided the contractor would support the capability for on-line facilities registration as specified in FIPS-PUB 100-1.

Yes B.3.1.1.1.1

C.2.3.1.1.1(c)(24)

The contractor may exceed the basic requirements by providing PSS access via an internetworked access arrangement (see Section C.2.1.16). When this access is provided the contractor would support the capability for extended packet sequence numbering (modulo 128) as specified in FIPS-PUB 100-1.

Yes B.3.1.1.1.1

C.2.3.1.1.1(c)(25)

The contractor may exceed the basic requirements by providing PSS access via an internetworked access arrangement (see Section C.2.1.16). When this access is provided the contractor would support the capability for

Yes B.3.1.1.1.1



RFP Section




Proposal Reference

packet retransmission as specified in FIPS-PUB 100-1. C.2.3.1.1.1(c)(26)

The contractor may exceed the basic requirements by providing PSS access via an internetworked access arrangement (see Section C.2.1.16). When this access is provided the contractor would support the capability for multilink procedure as specified in FIPS-PUB 100-1.

Yes B.3.1.1.1.1

C.2.3.1.1.1(c)(27)

The contractor may exceed the basic requirements by providing PSS access via an internetworked access arrangement (see Section C.2.1.16). When this access is provided the contractor would support the capability for direct call as specified in FIPS-PUB 100-1.

Yes B.3.1.1.1.1

C.2.3.1.1.1(c)(28)

The contractor may exceed the basic requirements by providing PSS access via an internetworked access arrangement (see Section C.2.1.16). When this access is provided the contractor would support the capability for The contractor may exceed the basic requirements by D-bit modification as specified in FIPS-PUB 100-1.

Yes B.3.1.1.1.1

C.2.3.1.1.1(c)(29)

The contractor may exceed the basic requirements by providing PSS access via an internetworked access arrangement (see Section C.2.1.16). When this access is provided the contractor would support the capability for call redirection as specified in FIPS-PUB 100-1.

Yes B.3.1.1.1.1

C.2.3.1.1.1(c)(30)

The contractor may exceed the basic requirements by providing PSS access via an internetworked access arrangement (see Section C.2.1.16). When this access is provided the contractor would support the capability for Network User Identification (NUI)as specified in FIPS-PUB 100-1.

Yes B.3.1.1.1.1

C.2.3.1.1.1(c)(31)

The contractor may exceed the basic requirements by providing PSS access via an internetworked access arrangement (see Section C.2.1.16). When this access is provided the contractor would support the capability for extended frame sequence numbering as specified in FIPS-PUB 100-1.

Yes B.3.1.1.1.1

C.2.3.1.1.1(c)(32)

The contractor may exceed the basic requirements by providing PSS access via an internetworked access arrangement (see Section C.2.1.16). When this access is provided the contractor would support the capability for call deflection subscription as specified in FIPS-PUB 100-1.

Yes B.3.1.1.1.1

C.2.3.1.1.1(c)(33)

The contractor may exceed the basic requirements by providing PSS access via an internetworked access

Yes B.3.1.1.1.1



RFP Section




Proposal Reference

arrangement (see Section C.2.1.16). When this access is provided the contractor would support the capability for call deflection selection as specified in FIPS-PUB 100-1.

C.2.3.1.2.1 The contractor may exceed the basic requirements for PSS Transport 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.

Yes B.3.1.2.1

C.2.3.1.2.1 The contractor may exceed the basic requirement by providing local telephone numbers for dial-in users.

Yes B.3.1.2.1

C.2.3.1.2.1 The contractor may exceed the basic requirements by providing the following options after successful logon for the asynchronous dial-in users:Direct Access Without Menu. With this option, a user can have 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.

Yes B.3.1.2.1

C.2.3.2.1.1(a) The contractor may exceed the basic requirements for Frame Relay Service Access by providing FRS which 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.

Yes B.3.2.1.1

C.2.3.2.1.1(b) The contractor may exceed the basic requirements for Frame Relay Service Access by providing FRS that would provide a frame-switched, connection-oriented, data transmission service at data rates from DS1 to DS3 in increments of DS1.

Yes B.3.2.1.1

C.2.3.2.1.1(c)(1) The contractor may exceed the basic requirements for Frame Relay Service Access by providing FRS via an internetworked access arrangement that would support SVCs using a numbering plan that follows the ITU-TSS E.164 ISDN numbering and addressing

Yes B.3.2.1.1



RFP Section




Proposal Reference

recommendation.C.2.3.2.2.1 The contractor may exceed the basic requirement by

providing local telephone numbers for dial-in users.Yes B.3.2.2.1

C.2.3.2.2.1(a) The contractor may exceed the basic Frame Relay Service Transport requirements by providing and FRS that 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.

Yes B.3.2.2.1

C.2.3.2.2.1(b) The contractor may exceed the basic Frame Relay Service Transport requirements by providing and FRS that would provide a frame-switched, connection-oriented, data transmission service at data rates from DS1 to DS3 in increments of DS1.

Yes B.3.2.2.1

C.2.3.2.2.1(c)(1) The contractor may exceed the basic Frame Relay Service Transport requirements by providing and FRS that when provided via internetworked access arrangement (see Section C.2.1.16), FRS would support SVCs, and a numbering plan for SVCs that would follow the ITU-TSS E.164 ISDN numbering and addressing recommendation.

Yes B.3.2.2.1

C.2.3.3.1.1(a) The contractor may exceed the basic requirements for IPS Access by providing IPS access that 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.

Yes B.3.3.1.1

C.2.3.3.1.1(b)(1) The contractor may exceed the basic requirements for IPS Access that when IPS is provided via internetworked access arrangement (see Section C.2.1.16), the IPS would support outgoing connections to IP-hosts in the FTS2001 networks and the Internet.

Yes B.3.3.1.1

C.2.3.3.1.1(b)(2) The contractor may exceed the basic requirements for IPS Access that when IPS is provided via internetworked access arrangement (see Section C.2.1.16), the contractor would provide an addressing plan for the IPS that is based on the standard for IPv4 and IPv6 addressing.

Yes B.3.3.1.1

C.2.3.3.2.1 The contractor may exceed the basic requirement by providing local telephone numbers for dial-in users.

Yes B.3.3.2.1



RFP Section




Proposal Reference

C.2.3.3.2.1(b) The contractor may exceed the basic requirements for IP Internetworking Service Transport by providing circuit switched calls where the contractor would support dynamically allocated IP address, and dynamically updating the DNS with the domain name and assigned IP address.

Yes B.3.3.2.1

C.2.3.3.2.1(c) The contractor may exceed the basic requirements for IP Internetworking Service Transport where 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.

Yes B.3.3.2.1

C.2.3.4.1.1(a) The contractor may exceed the basic requirements by providing ATMS via internetworked access arrangement (see Section C.2.1.16), where 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.

Yes B.3.4.1.1

C.2.3.4.1.1(b)(1) The contractor may exceed the basic requirements by providing ATMS via internetworked access arrangement (see Section C.2.1.16), where The following ATM Adaptation Layer (AAL) capabilities would be supported and comply with ITU-TSS Recommendations I.361, I.362, and I.363, and ITU-TSS Q.SAAL for signaling: 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.

Yes B.3.4.1.1

C.2.3.4.1.1(b)(2) The contractor may exceed the basic requirements by providing ATMS via internetworked access arrangement (see Section C.2.1.16), where The following ATM Adaptation Layer (AAL) capabilities would be supported and comply with ITU-TSS Recommendations I.361, I.362, and I.363, and ITU-TSS Q.SAAL for signaling: 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.

Yes B.3.4.1.1

C.2.3.4.1.1(b)(3) The contractor may exceed the basic requirements by providing ATMS via internetworked access arrangement

Yes B.3.4.1.1



RFP Section




Proposal Reference

(see Section C.2.1.16), where The following ATM Adaptation Layer (AAL) capabilities would be supported and comply with ITU-TSS Recommendations I.361, I.362, and I.363, and ITU-TSS Q.SAAL for signaling: AAL Type 3/4 Connectionless Data Service. ATMS would support a packet-mode connectionless data service (e.g., IP).

C.2.3.4.1.1(b)(4) The contractor may exceed the basic requirements by providing ATMS via internetworked access arrangement (see Section C.2.1.16), where The following ATM Adaptation Layer (AAL) capabilities would be supported and comply with ITU-TSS Recommendations I.361, I.362, and I.363, and ITU-TSS Q.SAAL for signaling: 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.

Yes B.3.4.1.1

C.2.3.4.1.1(b)(5) The contractor may exceed the basic requirements by providing ATMS via internetworked access arrangement (see Section C.2.1.16), where The following ATM Adaptation Layer (AAL) capabilities would be supported and comply with ITU-TSS Recommendations I.361, I.362, and I.363, and ITU-TSS Q.SAAL for signaling: 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.

Yes B.3.4.1.1

C.2.3.4.1.1(b)(6) The contractor may exceed the basic requirements by providing ATMS via internetworked access arrangement (see Section C.2.1.16), where The following ATM Adaptation Layer (AAL) capabilities would be supported and comply with ITU-TSS Recommendations I.361, I.362, and I.363, and ITU-TSS Q.SAAL for signaling: 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.

Yes B.3.4.1.1

C.2.3.4.1.1(c)(1) The contractor may exceed the basic requirements by providing ATMS via internetworked access arrangement (see Section C.2.1.16), where ATMS would support the following connection types for PVCs: Point-to-Point Connection. This feature would allow dedicated

Yes B.3.4.1.1



RFP Section




Proposal Reference

connection between two points.C.2.3.4.1.1(c)(2) The contractor may exceed the basic requirements by

providing ATMS via internetworked access arrangement (see Section C.2.1.16), where ATMS would support the following connection types for PVCs 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.

Yes B.3.4.1.1

C.2.3.4.1.1(d) The contractor may exceed the basic requirements by providing ATMS via internetworked access arrangement (see Section C.2.1.16), where 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.

Yes B.3.4.1.1

C.2.3.4.1.1(e)(1) The contractor may exceed the basic requirements by providing ATMS via internetworked access arrangement (see Section C.2.1.16), where ATMS would support SVC connections as follows: 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.

Yes B.3.4.1.1

C.2.3.4.2.1(e)(1) The contractor may exceed the basic requirements by providing ATMS Transport where ATMS would support services at the E1 (for non-domestic), E3 (for non-domestic), and SONET OC-3c to SONET OC-48c levels for AAL Type 1 VBR. ATMS would support circuit-mode services on an end-to-end basis.


B.3.4.2.1

C.2.3.4.2.1(f) The contractor may exceed the basic requirements by providing ATMS Transport where ATMS would support services at the E1 (for non-domestic), E3 (for non-domestic), and SONET OC-3c to SONET OC-48c levels for 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.

Yes B.3.4.2.1

C.2.3.4.2.1(g)(1) The contractor may exceed the basic requirements by Yes B.3.4.2.1



RFP Section




Proposal Reference

providing ATMS Transport where ATMS would support services at the E1 (for non-domestic), E3 (for non-domestic), and SONET OC-3c to SONET OC-48c levels where the ATMS transport would support the CBR data rates for SONET OC-3c to OC-48c.

C.2.3.4.2.1(g)(2) The contractor may exceed the basic requirements by providing ATMS Transport where ATMS would support services at the E1 (for non-domestic), E3 (for non-domestic), and SONET OC-3c to SONET OC-48c levels where the ATMS transport would support the CBR data rates for E1 (Non-Domestic Use).

Yes B.3.4.2.1

C.2.3.4.2.1(g)(3) The contractor may exceed the basic requirements by providing ATMS Transport where ATMS would support services at the E1 (for non-domestic), E3 (for non-domestic), and SONET OC-3c to SONET OC-48c levels where the ATMS transport would support the CBR data rates for E1 (Non-Domestic Use).

Yes B.3.4.2.1

C.2.3.4.2.1(h)(1) The contractor may exceed the basic requirements by providing ATMS Transport where ATMS would support services at the E1 (for non-domestic), E3 (for non-domestic), and SONET OC-3c to SONET OC-48c levels for ATMS BOD. 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.

Yes B.3.4.2.1

C.2.3.4.2.1(i)(1) The contractor may exceed the basic requirements by providing ATMS Transport where ATMS would support services at the E1 (for non-domestic), E3 (for non-domestic), and SONET OC-3c to SONET OC-48c levels for ATMS SVCs supporting the following connection type: 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).

Yes B.3.4.2.1

C.2.3.4.2.1(i)(2) The contractor may exceed the basic requirements by providing ATMS Transport where ATMS would support services at the E1 (for non-domestic), E3 (for non-

Yes B.3.4.2.1



RFP Section




Proposal Reference

domestic), and SONET OC-3c to SONET OC-48c levels for ATMS SVCs supporting the following connection type: Future Broadband ISDN Services.

C.2.4.1.1(i) The contractor may exceed the basic requirements for DTS Access by providing the following categories of DTS service Subrate DS0. This category of DTS service would support subrate DS0 at information payload data rate of 19.2 kb/s.

Yes B.4.1.12

C.2.4.1.1(p) The contractor may exceed the basic requirements for DTS Access by providing DTS service for all other DTS data rates that are available or become available during the life of the contract.

Yes B.4.1.12

C.2.4.2.1(i) The contractor may exceed the basic requirements for DTS Transport service by providing Subrate DS0 DTS service. This category of DTS service would support subrate DS0 at information payload data rate of 19.2 kb/s.

Yes B.4.2.12

C.2.4.2.1(p) The contractor may exceed the basic requirements for DTS Transport service by providing 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.

Yes B.4.2.12

C.2.7.4.1.1(c) The contractor may exceed the basic requirements for VTS by providing continuous presence. In a multipoint arrangement, the VTS would support continuous presence in which the video from between three 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.

Yes B.12.4.3.1.1


4 · web viewcross reference matrix table j.9.1. technical volume part c.2.1 rfp section statement...

Documents