**NCS Handbook 3-1-2**

**December 10, 2000**

**SERVICE VENDOR HANDBOOK**

**FOR THE**

**TELECOMMUNICATIONS SERVICE PRIORITY (TSP)**

**PROGRAM**

![](media/image1.wmf){width="3.36875in" height="3.2534722222222223in"}

**Office of the Manager**

**National Communications System**

**701 South Court House Road**

**Arlington, Virginia 22204-2198**

######## NATIONAL COMMUNICATIONS SYSTEM

######## Arlington, VA 22204-2198

######### NCS Handbook 3-1-2

######## TELECOMMUNICATIONS OPERATIONS

**Telecommunications Service Priority (TSP) Program for**

**National Security and Emergency Preparedness (NS/EP)**

**1. [Purpose]{.underline}.** In the interest of a uniform, responsive,
and well‑maintained system serving the Nation's NS/EP telecommunications
requirements, the TSP Program establishes certain requirements for
service vendors. To that end, the purpose of this handbook is to provide
operational details of the TSP Program, without straying into
implementation details that are properly internal to each vendor
organization. The principal objectives of this Service Vendor Handbook
are:

-   To provide the necessary information for service vendors to comply
    with TSP Program requirements

-   To provide a standard basis for the development of policies,
    methods, procedures, and training within each vendor organization

-   To provide information for the development of service vendors'
    systems necessary to meet TSP Program reporting requirements.

**2. [Authority]{.underline}.** This handbook is issued by the Manager,
National Communications System (NCS), with the approval of the FCC under
the authority of Title 47, Code of Federal Regulations (CFR), Part 64,
Appendix A, "Telecommunications Service Priority (TSP) System for
National Security Emergency Preparedness (NS/EP)," and NCS Directive
(NCSD) 3-1, "Telecommunications Service Priority (TSP) System for
National Security Emergency Preparedness (NS/EP)," August 10, 2000.

The FCC, as defined in its TSP Report and Order (FCC 88-341) (also
referred to as the TSP Program rules), which established the TSP
Program, retains final authority regarding interpretations of any
information contained in this handbook that impinge on the FCC's TSP
Program rules. This handbook is designed to supplement but not supplant
the FCC's TSP Program rules. In the event of contradictions between
information contained in this handbook and the FCC's TSP Program rules,
the FCC's TSP Program rules will prevail.

**3. [Applicability]{.underline}.** This handbook applies to all
telecommunications service vendors involved in the provisioning or
restoration of NS/EP telecommunications services. This handbook,
however, is not applicable to the provisioning or restoration of
customer premises equipment (CPE) or customer premises wiring (CPW).
Service users or contracting activities requiring priority treatment of
CPE and CPW from vendors will separately obtain such treatment through
proper contractual mechanisms. Vendor responsibilities should be
specified in such contractual provisions.

**4. [References]{.underline}.** Procedures outlined in this handbook
are based, in part, on information from the following documents:

-   Title 47, CFR, Part 64, Appendix A, "Telecommunications Service
    Priority (TSP) System for National Security Emergency Preparedness
    (NS/EP)."

-   NCSD 3-1, "Telecommunications Service Priority (TSP) System for
    National Security Emergency Preparedness (NS/EP)," August 10, 2000.

-   NCS Manual 3-1-1, "Service User Manual for the Telecommunications
    Service Priority (TSP) System," May 5, 2000.

**5. [Effective Date]{.underline}.** This handbook supersedes NCS
Handbook 3-1-2, "Telecommunications Service Priority (TSP) System for
National Security and Emergency Preparedness (NSEP) Service Vendor
Handbook," July 9, 1990, and is effective immediately.

**6. [Expiration]{.underline}.** This handbook is in effect until
superseded or canceled.

/s/

HARRY D. RADUEGE, JR.

Lieutenant General, USAF

Manager

Summary of Changes:

1\. Initial Publication: July 9, 1990

2\. Second Publication: December 10, 2000

**THE SERVICE VENDOR HANDBOOK FOR THE TSP SYSTEM**

The *Service Vendor Handbook for the TSP System* provides reference
information on the TSP Program as well as detailed procedural
instructions for TSP service vendors. This manual is structured into the
following six chapters accompanied by three appendices.

-   Chapter 1, TSP Program Overview, provides background information on
    TSP; details the scope of the TSP Program; outlines the TSP request
    process; provides information on TSP categories, service profiles,
    and priority levels; outlines the roles and responsibilities of the
    participants who provide and use the TSP Program; and provides
    details on the TSP Authorization Code. Information on problem
    resolution and the international extension of the TSP Program is
    also provided.

-   Chapter 2, Provisioning of TSP Services, details service vendors'
    TSP provisioning responsibilities, and includes information on
    priority provisioning of TSP services.

-   Chapter 3, Restoration of TSP Services, describes service vendors'
    TSP restoration responsibilities, relationships between service
    vendors, the order of restoration of TSP service, and preemption to
    restore TSP services.

-   Chapter 4, Confirmation and Verification of TSP Service Information,
    discusses service vendor responsibilities regarding the confirmation
    of TSP service order activity and verification of TSP assignments.

-   Chapter 5, Reconciliation of TSP Service Information, provides
    details on reconciliation and resolution of TSP service information
    between the OPT and service vendors and between service vendors and
    subcontractors.

-   Chapter 6, Service Vendors' Requests for TSP Assignments, details
    information on service vendors' requests for priority treatment of
    services they own or lease.

-   Appendix A provides TSP Program contact information.

-   Appendix B contains electronic file requirements for confirmation
    and reconciliation information.

-   Appendix C contains TSP forms: SF 315, SF 318, and SF 319.

    **TABLE OF CONTENTS**

1.0 TSP PROGRAM OVERVIEW 1-[1](#tsp-program-overview)

1.1 Scope of the TSP Program 1-[2](#scope-of-the-tsp-program)

1.2 TSP Service Description 1-[2](#tsp-service-description)

1.3 TSP Request Process 1-[4](#tsp-request-process)

1.3.1 Disaster Field Office Coordination
1-[5](#disaster-field-office-coordination)

1.4 TSP Categories, Service Profiles, And Priority Levels
1-[5](#tsp-categories-service-profiles-and-priority-levels)

1.5 TSP Authorization Code 1-[7](#tsp-authorization-code)

1.6 OPT Revocation of TSP Codes 1-[8](#opt-revocation-of-tsp-codes)

1.7 Responsibilities 1-[9](#responsibilities)

1.7.1 Federal Communications Commission
1-[9](#federal-communications-commission)

1.7.2 Executive Office of the President
1-[9](#executive-office-of-the-president)

1.7.3 Manager, National Communications System, and the Office of
Priority Telecommunications
1-[9](#manager-national-communications-system-and-the-office-of-priority-telecommunications)

1.7.4 Service Vendor 1-[9](#service-vendor)

1.7.5 Service User\..... 1-[11](#service-user)

1.7.6 TSP Oversight Committee 1-[11](#tsp-oversight-committee)

1.8 Problem Resolution 1-[11](#problem-resolution)

1.9 International Extension of the TSP Program
1-[12](#international-extension-of-the-tsp-program)

2.0 PROVISIONING OF TSP SERVICES 2-[1](#provisioning-of-tsp-services)

2.1 Service Vendors' TSP Service Provisioning Responsibilities
2-[1](#service-vendors-tsp-service-provisioning-responsibilities)

2.2 Priority Provisioning of Emergency TSP Services
2-[2](#priority-provisioning-of-emergency-tsp-services)

2.3 Priority Provisioning of Essential TSP Services
2-[3](#priority-provisioning-of-essential-tsp-services)

2.4 Preemption to Provision TSP Services
2-[4](#preemption-to-provision-tsp-services)

3.0 RESTORATION OF TSP SERVICES 3-[1](#restoration-of-tsp-services)

3.1 Service Vendors' TSP Service Restoration Responsibilities
3-[1](#service-vendors-tsp-service-restoration-responsibilities)

3.2 Relationships Between Service Vendors
3-[1](#relationships-between-service-vendors)

3.3 Order of Restoration 3-[2](#order-of-restoration)

3.4 Preemption to Restore TSP Services
3-[3](#preemption-to-restore-tsp-services)

4.0 CONFIRMATION AND VERIFICATION OF TSP SERVICE INFORMATION
4-[1](#confirmation-and-verification-of-tsp-service-information)

4.1 Confirmation of TSP Service Order Activity
4-[1](#confirmation-of-tsp-service-order-activity)

4.2 Verification of TSP Assignments
4-[2](#verification-of-tsp-assignments)

5.0 RECONCILIATION OF TSP SERVICE INFORMATION
5-[1](#reconciliation-of-tsp-service-information)

5.1 Reconciliation of TSP Service Information Between the OPT and Prime
Service Vendors
5-[1](#reconciliation-of-tsp-service-information-between-the-opt-and-prime-service-vendors)

5.2 Resolution of TSP Service Information Discrepancies Between the
Records of the OPT and Prime Service Vendors
5-[2](#resolution-of-tsp-service-information-discrepancies-between-the-records-of-the-opt-and-prime-service-vendors)

5.2.1 Restoration Priority Discrepancy
5-[3](#restoration-priority-discrepancy)

5.2.2 Circuit ID Discrepancy 5-[3](#circuit-id-discrepancy)

5.2.3 Revoked Service and Archived Service
5-[3](#revoked-service-and-archived-service)

5.3 Reconciliation of TSP Service Information Between Prime Service
Vendors and Subcontractors
5-[3](#reconciliation-of-tsp-service-information-between-prime-service-vendors-and-subcontractors)

6.0 SERVICE VENDORS' REQUESTS FOR TSP ASSIGNMENTS
6-[1](#service-vendors-requests-for-tsp-assignments)

6.1 Exempt Control Services And Orderwires
6-[1](#exempt-control-services-and-orderwires)

6.2 Nonexempt Control Services and Orderwires
6-[1](#nonexempt-control-services-and-orderwires)

6.3 Requesting a TSP Assignment for Other Service Vendor NS/EP
Requirements
6-[1](#requesting-a-tsp-assignment-for-other-service-vendor-nsep-requirements)

**APPENDICES**

Appendix A: Telecommunications Service Priority Program Contact
Information A-1

Appendix B: Electronic File Requirements B-1

Appendix C: TSP Forms C-1

**LIST OF FIGURES**

Figure 1-1 TSP Request Process 1-5

Figure 1-2 Categories, Service Profiles, and Priority Levels 1-6

Figure 1-3 Elements of the TSP Authorization Code 1-7

Figure 5-1 Reconciliation Timeline 5-4

# 1.0 TSP PROGRAM OVERVIEW

On November 17, 1988, the FCC issued a Report and Order (FCC 88-341)
establishing the TSP Program. The Report and Order established the TSP
Program for NS/EP as an amendment to Part 64 of the Commission's Rules
and Regulations (Title 47 CFR). The FCC designated the Executive Office
of the President (EOP) as administrator of the TSP Program. The EOP
delegated responsibilities to the Manager, NCS, who, in turn, assigned
the administration and execution of the TSP Program to the Office of
Priority Telecommunications (OPT) located at the NCS.

The Telecommunications Service Priority (TSP) Program for national
security and emergency preparedness (NS/EP) has been developed to ensure
priority treatment of our Nation's most important telecommunications
services. Telecommunications services are defined as the transmission,
emission, or reception of intelligence of any nature, by wire, cable,
satellite, fiber optics, laser, radio, visual or other electronic,
electric, electromagnetic, or acoustically coupled means, or any
combination thereof. Under the rules of the TSP Program,
telecommunications service vendors are both authorized and required,
when necessary, to provision and restore those telecommunications
services with TSP assignments before services without such assignments.

Only services that support NS/EP missions are eligible for TSP
assignments. The Federal Communications Commission (FCC) defines NS/EP
services as those telecommunications services that are used to maintain
a state of readiness or to respond to and manage any event or crisis
(local, national, or international), which causes or could cause injury
or harm to the population, causes damage to or loss of property, or
degrades or threatens the NS/EP posture of the United States.

Eligibility for a TSP assignment is not limited to Federal Government
services. State, local, and foreign governments may have
telecommunications services that qualify for TSP, and certain private
industry telecommunications services may qualify as well. Only a small
percentage of telecommunications services satisfy the NS/EP definition
and meet TSP Program criteria. The TSP Program provides strict
guidelines for determining eligibility for a TSP assignment.

The TSP Program establishes priority-levels for both provisioning and
restoration of NS/EP telecommunications services. These priority-levels
are the basis for TSP assignments that are provided to
telecommunications service vendors by the user. The service vendors then
use the TSP assignments to guide them on the sequence in which they are
to respond to provisioning and restoration requirements: as a general
rule, services with TSP assignments must, when necessary, be provisioned
or restored in the order of their priority-level assignments before
other services.

This chapter provides additional information on the TSP Program
including the scope of the TSP Program; TSP categories, service profiles
and priority levels; the TSP request process; the TSP authorization
code; responsibilities of the various participants in the TSP Program;
and international extension of the TSP Program. It is important that TSP
vendors understand this information to assure their compliance with TSP
Program requirements and to implement TSP procedures effectively within
their organizations.

## 1.1 Scope of the TSP Program

The TSP Program rules, as specified in the TSP Report and Order (FCC
88-341), authorize priority treatment to the following
telecommunications services:

**[Domestic NS/EP Services]{.underline}:**

-   Common carrier services that are interstate and foreign
    telecommunications services

-   Common carrier services that are intrastate telecommunications
    services inseparable from interstate or foreign telecommunications
    services, including intrastate telecommunications services to which
    TSP priority levels are assigned

-   Services that are provided by government and noncommon carriers and
    are interconnected to common carrier services assigned TSP priority
    levels.

**[Control Services and Orderwires]{.underline}:** The TSP Program
established by the FCC's TSP Program rules is not applicable to control
services or orderwires owned by a service vendor and needed for
provisioning, restoration, or maintenance of other services owned by
that service vendor. Such control services and orderwires shall have
priority provisioning and restoration over all other telecommunications
services (including TSP services) and shall be exempt from preemption.
However, the TSP Program established by the FCC's TSP Program rules is
applicable to control services or orderwires leased by a service vendor.

**[Other Services]{.underline}:** In addition, priority treatment may be
authorized at the discretion of, and upon special arrangements by, the
NS/EP TSP Program users involved, to the following telecommunications
services:

-   Government or noncommon carrier services that are not connected to
    common carrier provided services assigned a priority level

-   Portions of U.S. international services that are provided by foreign
    correspondents. (U.S. telecommunications service vendors are
    encouraged to ensure that relevant operating arrangements are
    consistent to the maximum extent practicable with the TSP Program.
    If such arrangements do not exist, U.S. telecommunications service
    vendors should handle service provisioning and restoration in
    accordance with any system acceptable to their foreign
    correspondents that comes closest to meeting the procedures
    established in the FCC's TSP Program rules.)

## 1.2 TSP Service Description

The TSP Program has two components: provisioning and restoration. A
provisioning priority is obtained to facilitate priority installation of
new telecommunications services. Provisioning on a priority basis
becomes necessary when a service user has an urgent requirement for a
new NS/EP service that must be installed immediately (e.g., an
emergency) or by a specific due date (e.g., essential) that can be met
only by a shorter than standard service vendor provisioning timeframe.

A restoration priority is assigned to new or existing telecommunications
services to ensure restoration before non-TSP services. Priority
restoration should be assigned to a new service when interruptions may
have a serious, adverse effect on the supported NS/EP function. TSP
restoration priorities must be requested and assigned before a service
outage occurs.

To provide priority provisioning or restoration of a telecommunications
service, a service vendor must receive a service order containing a TSP
Authorization Code. The TSP Authorization Code, a 12-digit alphanumeric
code, serves as official authorization from the OPT for a TSP vendor to
provide priority provisioning and/or restoration to an identified
service. (Section 1.5 contains detailed information on the TSP
Authorization Code.) The TSP Authorization Code has two parts: (1) the
TSP control identifier (ID), an alphanumeric identifier for tracking
purposes, and (2) the TSP priority levels that identify the provisioning
and restoration priority-level assignment. The TSP provisioning priority
level will be E (the highest), 1, 2, 3, 4, or 5. Note: Priority level
"E" is assigned only to Emergency provisioning requests. The TSP
restoration priority level will be 1 (the highest), 2, 3, 4, or 5. A
zero (0) in either priority-level position indicates no priority.
(Section 1.4 provides details on TSP priority levels.) Note that prime
service vendors are required to forward TSP Authorization Codes to
applicable subcontractors to ensure that priority-level assignments of
NS/EP services are accurately identified "end-to-end."

In addition, service vendors are required to provision and/or restore
NS/EP telecommunications services according to the following
priority-level-based sequence:

> 1\. Restore TSP services assigned restoration priority 1;
>
> 2\. Provision Emergency TSP Services assigned provisioning priority E;
>
> 3\. Restore TSP Services assigned restoration priority 2, 3, 4, or 5;
> and
>
> 4\. Provision TSP Services assigned provisioning priority 1, 2, 3, 4,
> or 5.

Service vendors should refer to Chapters 2 and 3 of this handbook for
details on TSP provisioning and restoration responsibilities. In
addition, service vendors should refer NS/EP customers who request
priority provisioning and restoration of services to the OPT for
detailed information on the TSP Program. (contact information for the
OPT is contained in Appendix A.) The OPT will forward the *Service User
Manual for the TSP System* (NCSM 3-1-1) to the customers for their
review. The following sections (1.3 and 1.4) provide a more detailed
description of the process a potential TSP user must follow to obtain a
TSP assignment.

## 1.3 TSP Request Process

To request TSP, a TSP user must:

1\. Certify that the telecommunications service supports an NS/EP
function listed under one of five TSP categories (as explained in
section 1.4).

> 2\. Verify, if requesting a provisioning priority, that a service
> vendor cannot meet the service due date without a TSP assignment.
> After this is verified, obtain approval from the service user's
> invocation official to request a provisioning priority.
>
> 3\. Identify the priority level to be requested for the
> telecommunications service. The priority level is determined by the
> user's TSP category and service profile (as explained in section 1.4).
> The service profile defines the user's level of support to the portion
> of the telecommunications service that the user owns and operates.
>
> 4\. Complete the TSP Request for Service Users form (SF 315). (A copy
> of the
>
> SF 315 is included in Appendix C.)
>
> 5\. Non-Federal users must have their TSP requests approved by a
> Federal agency sponsor. Non-Federal users should contact the OPT for
> information on identifying a sponsor for TSP requests.
>
> 6\. Submit the SF 315 to the OPT. See Appendix A for TSP Program
> contact information.
>
> 7\. Include the TSP Authorization Code obtained from the OPT in the
> service order to the service vendor.

After receiving the TSP Authorization Code, prime service vendors are
responsible for forwarding the TSP assignment to applicable
subcontractors. This ensures that priority-level assignments of NS/EP
services are accurately identified "end-to-end." Figure 1-1 provides an
overview of the TSP request process.

![](media/image2.wmf){width="5.514583333333333in"
height="3.688888888888889in"}

**Figure 1-1**

**TSP Request Process**

### 1.3.1 Disaster Field Office Coordination

When the President declares a specific area a "Federal disaster area,"
the Federal Emergency Management Agency (FEMA) will establish a Disaster
Field Office (DFO) in that location to coordinate disaster relief
efforts. Service vendors should be aware that, in these instances, TSP
service users may be directed by the OPT to submit their provisioning
requests directly to the DFO. The DFO will coordinate all provisioning
activities with the OPT, the service users, and the service vendors to
ensure that all concerned parties clearly understand the requirements
and priorities.

The following sections detail the criteria followed by TSP users to
determine the priority level(s) for which their NS/EP telecommunications
service qualifies. These criteria are also used by the OPT in evaluating
a TSP request.

## 1.4 TSP Categories, Service Profiles, and Priority Levels

As outlined in section 1.3, potential TSP users must determine their TSP
category, service profile, and priority level(s) before requesting a TSP
assignment. This section provides more detailed information on each of
these processes.

Figure 1-2 presents an overview of the relationships among categories,
service profiles, and priority levels.

![](media/image3.wmf){width="5.792361111111111in"
height="5.129166666666666in"}

**Figure 1-2**

Categories, Service Profiles, and Priority Levels

TSP users can choose categories A, B, C, or D for "Essential" priority
provisioning and restoration requests. Category E is to be used only for
"Emergency" priority provisioning requests. Essential requests are for
those telecommunications services that support an NS/EP function and
must be provisioned or restored in a faster than normal service time
period.

Emergency provisioning requests are for those services that support one
of the NS/EP functions listed as a criterion for category E and are so
critical that they must be provisioned at the earliest possible time,
without regard to cost to the user.

Each category is composed of a specific set of criteria. To qualify for
a category, the user's telecommunications service must support one of
the criteria listed under that category. For example, if a service
supported the distribution of medical supplies, it would qualify for the
Public Health, Safety, and Maintenance of Law and Order category.

After the category has been identified, the user must determine service
profile information. The service profile defines the user's level of
support to the portion of the telecommunications service that the user
owns and operates, such as CPE (e.g., spare CPE is available to back up
primary equipment) and customer CPW. The more extensive the support by
the user, the higher the priority level that can be requested.

After the TSP category and service profile elements are determined, TSP
users can then determine the priority level(s) for which their
service(s) qualifies. Priority levels E (the highest), 1, 2, 3, 4, and 5
are assigned to TSP provisioning requests. Note: Priority level "E" is
assigned only to Emergency provisioning requests. Priority levels 1 (the
highest), 2, 3, 4, and 5 are assigned to TSP restoration requests. A
zero (0) in either priority-level position indicates no priority.

After a user completes a TSP request that includes the above
information, the request is forwarded to the OPT for approval. The OPT
will process provisioning requests immediately, and will strive to
process restoration requests within 10 working days of receipt. If the
OPT approves the request, the user then receives a Priority Action
Notice from the OPT that contains the TSP Authorization Code.

## 1.5 TSP Authorization Code

A TSP Authorization Code is the official authorization from the OPT for
a TSP vendor to provide priority provisioning and restoration to an
identified service for a particular TSP user. TSP authorization codes
are assigned on a per-service basis (i.e., one TSP Authorization Code
for each telecommunications service) by the OPT. The TSP Authorization
Code (TSP assignment) is approved for 2 years and must be included in
the service order that is sent to the vendor by the user. Vendors should
be aware that after the 2-year authorized period, the OPT requests that
the user revalidate its TSP assignments. If a service is not
revalidated, the OPT can revoke the TSP Authorization Code via the
service vendor (as explained in section 1.6). Figure 1-3 illustrates the
elements of a TSP Authorization Code.

![](media/image4.wmf){width="5.179166666666666in"
height="2.6486111111111112in"}

**Figure 1-3**

**Elements of the TSP Authorization Code**

The TSP Authorization Code has two parts: (1) the TSP control identifier
(ID), an alphanumeric identifier for tracking purposes, and (2) the TSP
priority levels that identify the provisioning and restoration
priority-level assignment.

The *TSP Control ID* occupies positions 1 through 9 of the TSP
Authorization Code. In Figure 1-3, the control ID is "TSP0A2M6C." The
10th position is always a hyphen, which simply separates the TSP Control
ID from the TSP Priority-levels.

**Note: The letters I, O, S, and Z are never used in the TSP Control
ID.**

The *TSP Priority levels* occupy positions 11 and 12 of the TSP
Authorization Code. In figure 1-3, it is "03," which means there is no
provisioning priority and that the restoration priority level is 3.
Acceptable values for both provisioning and restoration include the
following:

-   For the *provisioning* priority field, E, 1, 2, 3, 4, 5, or 0 (zero)
    is acceptable. A zero indicates that no provisioning priority is
    assigned.

-   For the *restoration* priority field, 1, 2, 3, 4, 5, or 0 (zero) is
    acceptable. A zero indicates that no restoration priority is
    assigned.

Note: Revocation of a priority-level assignment is indicated if the TSP
priority levels (both the provisioning priority field and the
restoration priority field) of a TSP Authorization Code contain two
zeros.

After the TSP Authorization Code is assigned, the service user must keep
it on record. If discrepancies occur at a later date regarding the
priority assignment, the TSP Authorization Code will assist in uniquely
identifying the service. The TSP Control ID portion of the TSP
Authorization Code remains the same for as long as a priority assignment
continues to be required.

## 1.6 OPT Revocation of TSP Codes

The OPT is authorized to revoke a service user's TSP Authorization
Code(s) if the user does not respond to an OPT request for revalidation
of TSP services. (Service users are required to revalidate information
for all their TSP services every 2 years with the OPT by using the TSP
Revalidation for Service Users standard form \[SF 314\]). If the OPT
does not receive a response within 30 days of an initial revalidation
notice, the OPT sends the service user a reminder notice to revalidate
its TSP services. If there is still no response after 10 business days,
the OPT forwards a followup letter to the service user and the head of
the user organization. The letter states that if the user's TSP services
are not revalidated within 10 business days, the OPT may contact the
user's service vendor to revoke its TSP assignments. If the user fails
to respond, the OPT will send a notice instructing the prime service
vendor to remove TSP restoration priority from the service(s). The
service user will be provided a copy of the notice and should be aware
that the removal of the TSP assignment(s) may result in a charge.

## 1.7 Responsibilities

This section describes the responsibilities of TSP Program participants,
including service users, invocation officials, service providers, and
Government organizations that maintain key roles within the TSP Program.

### 1.7.1 Federal Communications Commission

The FCC provides regulatory oversight of NS/EP TSP Program
implementation. It also enforces TSP rules and regulations; acts as a
final authority for approval, revision, or disapproval of priority
actions by the EOP; and functions as a sponsoring Federal organization.

### 1.7. 2 Executive Office of the President

The FCC designated the EOP as the official administrator of the TSP
Program. The EOP has delegated responsibilities to the Manager, NCS, but
acts as the final approval or denial authority for assignments of TSP
priority levels. The EOP also acts as the adjudicator of disputes during
the exercise of the President's war emergency powers under section 706
of the Communications Act of 1934.

### 1.7.3 Manager, National Communications System, and the Office of Priority Telecommunications

The Manager, NCS, is responsible for implementing the TSP Program and
has established the OPT to administer the system on a daily basis. The
OPT's responsibilities are as follows:

-   Receive, process, and evaluate requests for priority actions from
    service users or sponsoring Federal Government organizations on
    behalf of service users

```{=html}
<!-- -->
```
-   Approve TSP priority-level assignments for service users

-   Convey TSP priority-level assignments to the service user

-   Revise, revalidate, reconcile, and revoke TSP priority-level
    assignments with service users and service vendors as necessary to
    maintain the viability of the TSP Program

-   Maintain a database of TSP priority-level assignments and TSP users

-   Issue new or revised regulations, procedures, and instructional
    material supplemental to and consistent with the operation,
    administration, and use of the TSP Program.

### 1.7.4 Service Vendor

A telecommunications service vendor refers to any individual,
association, partnership, corporation, organization, or other entity
(including common carriers, telecommunications carriers, and government
organizations) offering telecommunications equipment, facilities,
services, or combination thereof. As an FCC-licensed telecommunications
carrier, a service vendor who receives a TSP assignment will perform the
following:

-   Provide TSP service only after receipt of a TSP authorization code

-   Revoke TSP services at the direction of the user or the OPT

-   Ensure that TSP Program priorities supersede any other
    telecommunications priority that may be provided (other than control
    services and orderwires)

-   Designate a 24-hour point of contact (POC) to receive reports of TSP
    service outages from TSP service users

-   Designate a 24-hour POC to coordinate TSP processes with the OPT

-   Confirm completion of TSP service order activity (when acting as a
    prime service vendor) to the OPT

-   Participate in reconciliation of TSP information at the request of
    the OPT

-   Complete reconciliation of TSP information with all subcontractors

-   Ensure that priority-level assignments of NS/EP services are
    accurately identified "end-to-end" by providing to subcontractors
    and service vendors who supply underlying facilities the
    provisioning and/or restoration priority level assigned to a service

-   Disclose content of the NS/EP TSP database only as may be required
    by law

-   Comply with regulations and procedures supplemental to and
    consistent with guidelines issued by the OPT.

#### 1.7.4.1 Service Vendor Considerations

Although not a requirement, TSP service vendors should consider the
following internal administrative procedures when implementing TSP in
their networks:

-   Identify corporate personnel to perform TSP administration

-   Identify a TSP provisioning services and restoration/trouble center
    24‑hour POC

-   Identify necessary modifications to network operations, information
    technology and processes, programming systems, and operation support
    systems (OSS)

-   Identify necessary circuit records and billing modifications

-   Identify specific costs to network operations for TSP implementation
    and cost recovery mechanisms

-   Determine if unique service order codes are required for TSP

-   Develop internal TSP training methods and procedures

-   Develop interface procedures for customers, other service providers,
    and the OPT

-   Develop processes for transmitting TSP assignments to subcontractors
    and for reconciling TSP codes with subcontractors

-   Develop a process to identify TSP services to vendors that supply
    underlying facilities.

### 1.7.5 Service User

A TSP service user is any individual or organization (including a
service vendor) supported by a telecommunications service for which a
TSP assignment has been requested or assigned. NS/EP telecommunications
services within the Federal, State, local, or foreign governments, as
well as private industry, are eligible for TSP. Federal users do not
require a sponsor. Non-Federal users (e.g., State, local, foreign
governments) require a Federal agency to sponsor their request. Service
users or entities acting on their behalf will perform the following:

-   Identify telecommunications services requiring priority

-   Request, justify, and revalidate all priority-level assignments

-   Accept services assigned priority levels by the service due dates
    or, for service in the Emergency category, when they are available

-   Have CPE and CPW available by the requested service due date and
    ensure (through contractual means or otherwise) priority treatment
    for CPE and CPW necessary for end‑to‑end service continuity

-   Pay vendors any authorized costs associated with priority services

-   Report to vendors any failed or unusable services with priority
    levels

-   Designate a 24-hour POC for each TSP request and apprise the
    Manager, NCS

-   Cooperate with the Manager, NCS, during reconciliation and
    revalidation.

### 1.7.6 TSP Oversight Committee

The TSP Oversight Committee (OC), established in July 1990, is
responsible for identifying, reviewing, and recommending actions to
correct or prevent any systemic problems in the TSP Program. The TSP OC
membership comprises 19 individuals from Federal agencies, State
government, and industry.

## 1.8 Problem Resolution

Numerous organizations participate in requesting and providing priority
treatment in the TSP Program. The TSP Program rules provide safeguards
against misuse (see FCC TSP Program rules, Section 9), but the
effectiveness of the system ultimately depends on the good-faith efforts
of participants to abide by the spirit and intent of the TSP Program
rules. Disagreements will, nevertheless, occur from time to time. A
basic premise regarding the TSP Program is that, wherever possible,
problems should be addressed and resolved by the people most directly
involved and knowledgeable. Most problems can be resolved following the
service vendor's existing procedures and channels of communication. If
service vendors cannot resolve a TSP problem internally they should
contact the OPT. Any concerns that cannot be resolved with the OPT will
be referred to the Manager, NCS. Alternatively, service vendors may
always contact the FCC for any problems concerning the TSP Program. The
TSP OC can also address any problems related to the TSP Program. Vendors
should contact the OPT for TSP OC POC information. (See Appendix A for
OPT contact information.)

## 1.9 International Extension of the TSP Program

It is desirable for priority treatment to be provided for all segments
of an NS/EP service. The FCC-authorized TSP Program, however, applies
only to telecommunications services within FCC jurisdiction. For
international services, that jurisdiction extends to the U.S. portion of
the service (from the end user in the U.S. to a hypothetical midpoint).
The FCC-authorized TSP Program does *not* extend to telecommunications
services wholly within foreign countries, or to those portions of
international telecommunications services provided by foreign carriers
(from the hypothetical midpoint to the end user in the foreign country).
Accordingly, special arrangements are required if priorities similar to
TSP Program priorities are to be provided on the foreign portion of
NS/EP services.

# 2.0 PROVISIONING OF TSP SERVICES

A TSP provisioning priority is obtained by a TSP service user to
facilitate priority installation of new telecommunications services.
Provisioning on a priority basis becomes necessary when a service user
has an urgent requirement for a new NS/EP service that must be installed
immediately or by a specific due date that can be met only by a shorter
than standard service vendor provisioning timeframe. (Note: The user is
responsible for ensuring that all other avenues for obtaining service
have been exhausted before resorting to TSP procedures.) This chapter
highlights service vendor responsibilities regarding provisioning of TSP
services.

## 2.1 Service Vendors' TSP Service Provisioning Responsibilities

A priority provisioning requires the service vendor to provision the
following:

-   TSP services assigned an "E" provisioning priority (Emergency TSP
    services) as soon as possible

-   TSP services assigned provisioning priorities 1--5 (Essential TSP
    services) ensuring best efforts to meet the requested service date.

Service vendors are authorized to receive compensation for priority
provisioning through properly filed State or Federal tariffs, or
applicable portions of properly negotiated contracts (if the service
vendor is not required to file tariffs).

Service vendors may, during certain emergencies, receive TSP assignments
verbally. In these cases, written service orders should follow within 2
working days. If prime service vendors do not receive the written
service order within 2 working days, they may contact the OPT. Prime
service vendors should accept a TSP assignment only if the service order
(or verbal request) includes a TSP Authorization Code. The only
condition under which a prime service vendor is authorized to accept a
provisioning TSP assignment without a TSP Authorization Code is when the
service user or its contracting activity asserts it is unable to
communicate with either the OPT or the FCC. Service vendors may attempt
to contact the OPT or the FCC for verification. If contacting the FCC,
call the FCC Watch Office and ask for the TSP point of contact. (TSP
Program contact information is contained in Appendix A.)

Prime service vendors who subcontract portions of TSP services are
required to convey the TSP assignment to subcontractors and
interconnecting carriers, as well as to maintain the TSP assignment in
their own records. (Service vendors should refer to internal procedures
and industry guidelines regarding TSP service information transfer
between prime service vendors and subcontractors.) In the event the TSP
assignment is changed or revoked through a subsequent service order, the
prime service vendor will convey these changes to subcontractors and
interconnecting carriers, as well as adjust its own records.

As specified in the TSP rules, service vendors will cooperate with other
service vendors involved in provisioning a TSP service by honoring
requests for assistance. Additionally, all service vendors, specifically
including resale carriers, will ensure that service vendors supplying
the underlying facilities are provided the information necessary to
implement priority treatment of facilities that support TSP services.
For instance, a service vendor providing a TSP service to a service user
via leased facilities must inform the vendor who owns the facilities of
the priority service carried on those facilities.

In the event of problems regarding TSP services, service vendors and
service users or their contracting activities should first attempt to
determine solutions among themselves. However, any conflicts that cannot
be resolved to the mutual satisfaction of service vendors and service
users or their contracting activities should be referred to the OPT.
Service vendors should also refer to their internal escalation
procedures and industry guidelines.

Within 45 calendar days of completing a TSP service order, prime service
vendors are required to provide confirmation information to the OPT.
(See section 4.1, Confirmation of TSP Service Order Activity.) This
requirement is in addition to the normal service vendor business
practice of reporting completion of a service order back to the service
user or their contracting activity. This confirmation information serves
to verify that the TSP assignment the service vendor recorded matches
the TSP assignment the OPT assigned.

## 2.2 Priority Provisioning of Emergency TSP Services

In response to an emergency, a service user may request an Emergency
priority (E) to provision a new service. To be assigned an Emergency
provisioning priority, the need for a service has to be so critical that
the service must be provisioned at the earliest possible time, without
regard to the cost to the service user.

Service vendors are required to provide 24-hour POCs for receiving
Emergency provisioning requests. When service vendors receive an E
provisioning priority, they will take immediate action and allocate the
resources necessary to provide the service as soon as possible,
including dispatching personnel outside normal business hours.

Service vendors are required, by the FCC's TSP Program rules, to
provision Emergency TSP services before provisioning Essential TSP
services. (Essential provisioning is explained in section 2.3.) Service
vendors will provision services assigned E provisioning priorities
first; then Essential TSP services assigned provisioning priority 1; and
so forth. If a service vendor receives more than one Emergency TSP
service request from different service users, the service vendor will
provision them in order of receipt. However, if one service user submits
multiple Emergency TSP service requests, the service user may specify
the sequence of provisioning.

If a service vendor questions an E provisioning priority, the vendor may
contact the OPT via telephone\--4 hours a day, 7 days a week\--to verify
the TSP Authorization Code. However, a service vendor will not delay
provisioning of Emergency TSP services for verification purposes. (See
section 4.2, Verification of TSP Assignments.)

It is important to note that, as a matter of general practice, service
vendors should restore existing TSP services before provisioning new TSP
services. In resolving conflicts, the EOP requires that restoration or
provisioning of TSP services follows this sequence:

> 1\. Restore TSP services assigned restoration priority 1
>
> 2\. Provision Emergency TSP Services assigned provisioning priority E
>
> 3\. Restore TSP Services assigned restoration priority 2, 3, 4, or 5
>
> 4\. Provision TSP Services assigned provisioning priority 1, 2, 3, 4,
> or 5.

## 2.3 Priority Provisioning of Essential TSP Services

An Essential provisioning priority satisfies a requirement for a new
NS/EP service that must be installed by a specific date that cannot be
met using normal business procedures. Essential NS/EP services may be
assigned provisioning priority levels 1, 2, 3, 4, or 5.

The service user or its contracting activity will provide a provisioning
priority on the initial TSP service order to the service vendor. In this
situation, the service user has determined, through informal
negotiations with the service vendor before issuing a service order,
that a TSP service cannot be provided by the service user's requested
service due date without authorizing a priority provisioning.

Upon receipt of the provisioning priority, the prime service vendor will
make its best effort to meet the requested service due date. By passing
a provisioning priority to the prime service vendor, the service user is
immediately liable to pay the prime service vendor any authorized costs
associated with provisioning the service within a shorter than standard
interval.

Essential TSP service provisioning priority levels (i.e., 1, 2, 3, 4, or
5) are requirements by which the service vendor is to adjust its
resources to meet the service due date. When a service vendor receives
multiple TSP service orders assigned the same service due date, and when
resource constraints prevent the service vendor from providing all the
services on time, the service vendor will provide TSP services in order
of the provisioning priority assignment. TSP services that are assigned
the same provisioning priority and the same service due date will be
provisioned in the order the service vendor received the service
request.

The service vendor will use its best judgment to allocate resources
within the particular circumstance to ensure its best effort to provide
TSP services assigned provisioning priorities on the requested service
due dates. For instance, the service vendor is not obligated to suspend
work in progress to provision a TSP service assigned a provisioning
priority of 5 just to commence work to provision a TSP service assigned
a provisioning priority of 1; however, the service vendor is free to do
so if necessary to meet the required service due date for the TSP
service assigned a provisioning priority of 1. If an Essential TSP
service due date is missed, the service vendor should first contact the
service user for direction. If a mutually acceptable solution cannot be
reached, the service vendor may contact the OPT for assistance. (See
Appendix A for OPT contact information.)

## 2.4 Preemption to Provision TSP Services

Service vendors are authorized by the FCC's TSP Program rules to preempt
existing services to provision Emergency and Essential TSP services that
are assigned provisioning priorities when, in their best judgment,
preemption is necessary. Prior consent of the service user whose service
will be preempted is not required. However, the service vendor will make
its best effort to notify the user of the preempted service and state
the reason for, and estimated duration of, the preemption.

When the service vendor determines that preemption is necessary (e.g.,
no spare services are available), non-TSP services may be preempted.
After ensuring a sufficient number of public switched services are
available for public use, based on the service vendor's best judgment,
such services may be used to satisfy a requirement for provisioning TSP
services. If no suitable spare or non-TSP services are available, the
service vendor may preempt an existing TSP service to provision a TSP
service with a higher priority-level assignment. When this action is
necessary, the service vendor will select TSP services for preemption in
the inverse order of priority assignment.

# 3.0 RESTORATION OF TSP SERVICES

The purpose of restoration priority assignments is to guide a service
vendor on the sequence for restoring NS/EP services in the event of an
outage or failure of multiple services. All TSP services, regardless of
their restoration priority levels, will be restored before any non-TSP
services. This chapter delineates service vendors' restoration
responsibilities; highlights the method by which service vendors will
receive restoration priority assignments; and presents guidelines for
service vendors to follow to provide priority restoration of TSP
services.

## 3.1 Service Vendors' TSP Service Restoration Responsibilities

After being assigned a TSP Authorization Code for its service, the
service user or its contracting activity will transmit the TSP
Authorization Code to the prime service vendor on a service order. The
OPT does not give the TSP Authorization Code directly to the prime
service vendor. This transfer is part of the normal contractual process
that takes place between the service user or its contracting activity
and the prime service vendor. Prime service vendors are not to accept
initial TSP assignments, or subsequent orders involving TSP services,
without the 12-character TSP Authorization Code.

Service vendors are required to restore TSP services with restoration
priority assignments before telecommunications services without
restoration priority assignments. However, control services and
orderwires that are wholly owned and operated by a service vendor and
crucial to the operation of that service vendor's network are exempted
from this requirement. (See section 6.1, Exempt Control Services and
Orderwires.)

A service vendor who accepts TSP service orders is required to provide
24-hour POCs to receive reports of TSP service outages from service
users. This need not be a single dedicated POC for TSP service outages
and may, in fact, be the contact to whom service outages would normally
be reported. When service vendors recognize that a TSP service is out of
service, unusable, or they receive a trouble report, they will allocate
available resources to restore the service as quickly as practicable.
Service vendors will dispatch personnel outside normal business hours if
necessary to restore TSP services assigned a restoration priority of 1,
2, or 3. Service vendors are required to dispatch personnel outside
normal business hours to restore TSP services assigned 4 or 5 only when
the next business day is more than 24 hours away.

## 3.2 Relationships Between Service Vendors

Prime service vendors who subcontract portions of TSP services are
required to convey the TSP assignment to subcontractors and
interconnecting carriers. Subcontractors will accept and honor the TSP
assignment supplied by the prime service vendor. (Service vendors should
refer to internal procedures and industry guidelines regarding transfer
of TSP service information between prime service vendors and their
subcontractors and interconnecting carriers.) Service vendors will
cooperate with other service vendors involved in restoring a TSP service
by honoring requests for restoration assistance. Additionally, all
service vendors, specifically including resale carriers, will ensure
that service vendors supplying the underlying facilities are provided
the information necessary to implement priority treatment of facilities
that support TSP services.

If there is a discrepancy between the records of the prime service
vendor and the subcontractor, the subcontractor will accept the
restoration priority supplied by the prime service vendor while
restoring the service. The prime service vendor is responsible for
verifying the restoration priority assigned by the OPT and ensuring that
the information is correctly recorded by both the prime service vendor
and its subcontractor(s). (See section 4.2, Verification of TSP
Assignments.)

## 3.3 Order of Restoration

TSP services will be restored in order of restoration priority level:
i.e., TSP services assigned a restoration priority of 1 will be restored
first; then TSP services assigned a restoration priority of 2 will be
restored, etc.

Service vendors will restore TSP services assigned the same restoration
priority based on the service vendor's determination of which service
can be restored first. In lieu of a clear distinction, the service
vendor will use its best judgment to determine the restoration order.
The service vendor should not normally interrupt TSP service restoration
work in progress to restore another TSP service assigned the same
priority level. The service vendor is not prevented from allocating its
resources in a manner that, in its best judgment, will most efficiently
facilitate restoration of TSP services as soon as possible.

Any conflicts regarding the restoration priority of TSP services that
cannot be resolved to the mutual satisfaction of the service vendor and
the service user or their contracting activity should be referred to the
OPT. (See Appendix A for OPT contact information.) However, the service
vendor and service user or their contracting activity should first
attempt to resolve conflicts among themselves. The service vendor should
also refer to its internal escalation procedures and industry
guidelines.

In addition, service vendors are permitted to provide priority
restoration to multiple service facilities (e.g., DS1 or DS3 facilities)
that contain TSP services, even though services assigned no priority or
lower priority may be restored along with or sometimes ahead of some
higher priority-level services. Alternatively, the service vendor may
reroute individual TSP services from a failed facility onto another
facility to hasten restoration.

Service vendors will consider the priority levels of the TSP services
supported by a multiple service facility when determining the order of
restoration. For example, a multiple service facility supporting TSP
services assigned restoration priorities 1 and 2 should be restored
before a multiple service facility supporting TSP services assigned
restoration priorities 3, 4, and 5. Service vendors will use their best
judgment to determine the restoration order of multiple service
facilities that support a number of TSP services with a variety of
restoration priority assignments.

As a matter of general practice, service vendors should restore existing
TSP services before provisioning new TSP services. In resolving
conflicts, the EOP requires that restoration or provisioning of TSP
services follows this sequence:

> 1\. Restore TSP services assigned restoration priority 1
>
> 2\. Provision Emergency TSP services assigned provisioning priority E
>
> 3\. Restore TSP services assigned restoration priority 2, 3, 4, or 5
>
> 4\. Provision TSP services assigned provisioning priority 1, 2, 3, 4,
> or 5.

## 3.4 Preemption to Restore TSP Services

Service vendors are authorized by the FCC's TSP Program rules to preempt
existing services to restore TSP services when, in their best judgment,
preemption is necessary. Prior consent of the service user whose service
will be preempted is not required. However, the service vendor will make
its best effort to notify the user of the preempted service and state
the reason for, and estimated duration of, the preemption.

When the service vendor determines that preemption is necessary (e.g.,
no spare services are available), non-TSP services may be preempted.
After ensuring a sufficient number of public switched services are
available for public use, based on the service vendor's best judgment,
such services may be used to satisfy a requirement for restoring TSP
services. If no suitable spare or non-TSP services are available, the
service vendor may preempt an existing TSP service to restore a TSP
service with a higher restoration priority assignment. When this action
is necessary, the service vendor will select TSP services for preemption
in the inverse order of priority assignment.

# 4.0 CONFIRMATION AND VERIFICATION OF TSP SERVICE INFORMATION

Service vendors are required, by the FCC's TSP Program rules, to submit
reports to the OPT confirming the completion of all TSP service orders
for which they are the prime service vendor. The prime service vendor
will provide a TSP Service Confirmation to the OPT within 45 calendar
days of completing a TSP service order. Confirmation reports can be
submitted to the OPT via the electronic or paper TSP Service
Confirmation for Service Vendors form (SF 318). These reports serve two
purposes:

-   Confirm that the same priority assigned by the OPT has been
    implemented by the prime service vendor

-   Provide the OPT with the Prime Service Vendor Circuit ID(s) for that
    TSP service.

The requirement to confirm completion of TSP service order activity to
the OPT is in addition to the standard service vendor business practice
of reporting completion of service orders back to the service user or
its contracting activity. Service vendors may also verify TSP
assignments at any time to the OPT if they question the authenticity of
the TSP assignment.

This section highlights a prime service vendor's responsibilities
regarding confirmation of TSP services to the OPT and presents methods
for submitting confirmation reports. Guidelines for service vendors to
follow to verify TSP assignments are also presented in this section.

## 4.1 Confirmation of TSP Service Order Activity

TSP service confirmations will contain the following information:

-   Full name of vendor. Prior to or when submitting their first
    confirmation, prime service vendors must designate to the OPT a
    standard company name. It is critical that prime service vendors
    consistently use the exact company name originally designated to the
    OPT; any further confirmations submitted under a different company
    name will be rejected. The OPT will store all TSP service
    information for prime service vendors based on this designation of
    their name.

-   Vendor POC name or title, phone number, and address. (The OPT will
    refer all questions/issues regarding confirmation to this POC.)

-   Date data compiled.

-   Number of items reported.

For each TSP service being confirmed, report the:

-   TSP Authorization Code (all 12 characters)

-   Prime Service Vendor Circuit ID

-   Type of order:

```{=html}
<!-- -->
```
-   New

-   Change

-   Disconnect.

Service vendors can submit confirmation information to the OPT using the
electronic file format specified in Appendix B, Electronic File
Requirements, or the SF 318 confirmation form found in Appendix C. For
additional information on submission options, contact the OPT. (Contact
information for the OPT is contained in Appendix A.)

## 4.2 Verification of TSP Assignments

TSP assignments are made by the OPT, and therefore the TSP Client-Server
database is the standard for verifying TSP assignments. To verify a
provisioning or restoration priority assignment with the OPT, the
service vendor must identify either the TSP Authorization Code or the
Prime Service Vendor Circuit ID. The OPT will then verify whether or not
the TSP assignment received by the service vendor is correct.

Service vendors may contact the OPT via telephone between 8:00 a.m. and
4:00 p.m. eastern time Monday through Friday to verify non‑Emergency
priority-level assignments. However, the OPT will be available 24 hours
a day, 7 days a week, to verify Emergency provisioning priorities.
(Contact information for the OPT is contained in Appendix A.)

# 5.0 RECONCILIATION OF TSP SERVICE INFORMATION

Reconciliation of TSP service information is intended to ensure that
information identifying TSP services and their associated TSP
assignments is accurately maintained by service vendors. As such, all
service vendors who accept orders for TSP services are required by the
FCC's TSP Program rules to participate in reconciliation.

Service vendors are required to reconcile information for all TSP
services for which they are the prime service vendor every year with the
OPT. Vendors acting as prime service vendors are also required to
reconcile information with each of their subcontractors once every 3
years for all TSP services they jointly provide.

This section presents guidelines for service vendors to follow in
submitting TSP service information to the OPT for reconciliation
purposes, resolving discrepancies discovered between the prime service
vendor's records and the NCS TSP database, and reconciling prime service
vendor TSP service information with their subcontractors.

## 5.1 Reconciliation of TSP Service Information Between the OPT and Prime Service Vendors

The OPT will initiate reconciliation with prime service vendors once a
year by sending a letter to the prime service vendor. The OPT will
request information on all TSP services with a restoration priority for
which the service vendor is the prime contractor.[^1] The prime service
vendor will provide the requested information to the OPT within 30
calendar days of receipt of the request. This information must be
derived from those records the service vendor uses to restore services
(e.g., maintenance records).

Prime service vendors may submit reconciliation information to the OPT
via the electronic or paper TSP Service Reconciliation for Service
Vendors form (SF 319). The electronic file format must conform to the
specifications outlined in Appendix B, Electronic File Requirements, or
Appendix C contains a TSP Service Reconciliation for Service Vendors
form (SF 319). For additional information on submission options, contact
the OPT. (Contact information for the OPT is contained in Appendix A.)

The prime service vendor will provide the following reconciliation
information:

-   Full name of vendor. Prime service vendors must use their standard
    company name designated to the OPT for TSP service order
    confirmation. (See Section 4.1, Confirmation of TSP Service Order
    Activity.)

-   Date data compiled

-   Number of items reported

-   Vendor POC name or title, phone number, and address. (The OPT will
    refer all questions/issues regarding reconciliation to this POC.)

In addition, for each TSP service being reconciled, the following will
be provided:

-   TSP Priority Levels. Both characters of the priority-level
    assignment are mandatory. Prime service vendors are encouraged to
    submit the complete TSP Authorization Code, in which case the TSP
    Control ID portion of the TSP Authorization Code will also be
    reconciled. Submission of all 12 digits of the code increases the
    ability of the OPT to assist in resolving discrepancies. (See
    section 1.5 for a description of the TSP Authorization Code.)

> **Note: The provisioning priority level of a completed provisioning
> action may be reported as either the assigned priority level or as a
> zero (0) to indicate the completion of the order.**

-   Prime Service Vendor Circuit ID.

The OPT will compare data received from prime service vendors with
information resident in the NCS TSP database and identify discrepancies.
The OPT will send a discrepancy report to the prime service vendor
within 45 calendar days of receipt of the prime service vendor data.

Working in conjunction with the OPT and service users or their
contracting activities, prime service vendors will resolve discrepancies
within 45 calendar days of receipt of the discrepancy report from the
OPT. Note that the prime service vendor should correct obvious
typographical errors in reconciliation information. When changes to TSP
assignments (e.g., wrong priority levels or wrong TSP Authorization
Codes) in the prime service vendor's records are necessary, the OPT will
contact the service user to submit the change. Service users or their
contracting activity must submit service orders for those changes. If a
prime service vendor needs additional time to resolve discrepancies, the
prime service vendor may request an extension from the OPT.

The prime service vendor will return the discrepancy report to the OPT
within 45 calendar days of receiving the report with indication of
corrections or that errors are being resolved. The prime service vendor
reconciliation is considered complete when all errors have been
resolved. The prime service vendor will also initiate necessary changes
to correct any affected subcontractor TSP service information.

## 5.2 Resolution of TSP Service Information Discrepancies Between the Records of the OPT and Prime Service Vendors

Discrepancies between the records of the OPT and a prime service vendor
are due to a mismatch of the restoration priority level, the service
identifier, or the TSP Authorization Code. This section discusses the
resolution of discrepancies that could occur when reconciling prime
service vendor TSP service records against the TSP Client-Server
database.

### 5.2.1 Restoration Priority Discrepancy

A restoration priority discrepancy occurs when the OPT and the prime
service vendor identify the same TSP service; however, the associated
restoration priority reported by the prime service vendor does not match
the restoration priority in the TSP Client-Server database for that
service. To resolve such a discrepancy, the OPT will first contact the
prime service vendor (normally by telephone) to attempt to resolve the
mismatch. Any discrepancies that cannot be resolved with the prime
service vendor will be resolved between the OPT, the service vendor, and
the service user. Correcting a discrepancy with the service user in this
way may result in a new service order.

### 5.2.2 Circuit ID Discrepancy

Circuit ID discrepancy occurs when the circuit ID provided by the vendor
in the reconciliation file does not match the circuit ID provided by the
vendor in the confirmation of TSP service orders. The prime service
vendor is responsible for either correcting the confirmed circuit ID or
changing the circuit ID in the reconciliation file.

### 5.2.3 Revoked Service and Archived Service

When a user no longer requires priority restoration on a service, it
must submit a revocation request to the OPT and issue a change order to
the vendor. Occasionally, a discrepancy occurs during reconciliation
when the OPT has revoked a TSP assignment, but the vendor has not
removed the TSP assignment for that service. When this situation occurs,
the OPT will contact the user to have it correct the discrepancy with
the vendor. If the user fails to respond, the OPT will notify the user
that the service vendor is being instructed to revoke its TSP
assignment. The notice will also include the warning that the removal of
the TSP assignment may result in a charge to the user. A copy of this
notice to the user will be forwarded to the prime service vendor along
with the OPT instruction to the vendor to remove TSP restoration
priority from the service.

Vendors should also note that 45 calendar days after the OPT receives a
disconnect service action for a TSP assignment from a user, the service
is archived.

## 5.3 Reconciliation of TSP Service Information Between Prime Service Vendors and Subcontractors

All service vendors who accept TSP service orders and subsequently
subcontract portions of those TSP services are required, by the FCC's
TSP Program rules, to periodically reconcile TSP service information
with each of their subcontractors. In this context, the Manager, NCS,
defines "periodically" as at least once every 3 years. The Manager, NCS,
also suggests that prime service vendors should initiate reconciliation
with a subcontractor within 60 calendar days of completing
reconciliation of their "prime" TSP service information with the OPT to
ensure that "prime to subcontractor" reconciliation is conducted with
the most accurate TSP service information. Figure 5-1 is a timeline
illustrating the reconciliation sequence between prime service vendors
and the OPT and between prime service vendors and their subcontractors.

![](media/image5.wmf){width="6.500694444444444in" height="7.3375in"}

Figure 5-1

**Reconciliation Timeline**

After completing the prime vendor reconciliation, the OPT will send a
letter to the prime service vendor directing it to initiate
subcontractor reconciliation and to report completion to the OPT. To
initiate reconciliation with a subcontractor, the prime service vendor
will request, in writing, information on all TSP services that that
subcontractor jointly provides with the prime service vendor. The
subcontractor will provide the requested information within 30 calendar
days of receipt of the request. This information must be derived from
those records the subcontractor uses to restore service (e.g.,
maintenance records).

> The subcontractor will provide the following information for each
> reconciliation report:

-   Subcontractor Name

-   Subcontractor POC Information.

For each portion of a TSP service it is responsible for, the
subcontractor will also provide the following information to the prime
service vendor:

-   Subcontractor Service ID (e.g., Circuit ID)

-   TSP Priority levels (both characters are mandatory).

The prime service vendor and the subcontractor may determine the
specific format and media for submitting this data. Additionally, prime
service vendors and subcontractors should consider applicable industry
guidelines regarding reconciliation procedures. The OPT suggests that
electronic ASCII text format be used as the medium for conveying
information by carriers with more than 100 TSP assignments, while paper
format could be used by carriers with fewer than 100 TSP assignments.

Within 45 calendar days of receipt, the prime service vendor will
compare the data received from the subcontractor with TSP service
information resident in it records and identify discrepancies. The prime
service vendor will report these discrepancies to the subcontractor and
work with the subcontractor to resolve them.

The prime service vendor's records are the standard against which the
subcontractor data will be reconciled. Therefore, when the prime service
vendor identifies a different restoration priority assignment in the
subcontractor's records for the same TSP service, the prime service
vendor will instruct the subcontractor to correct its TSP service
records used to restore services. (In these cases, the vendor will not
receive change orders from the service user. However, the prime service
vendor may need to forward a change order to the subcontractor.) Prime
service vendors and subcontractors should consult applicable industry
guidelines for direction regarding resolution of billing issues
associated with "prime service vendor to subcontractor" reconciliation
discrepancies.

It should be noted that the OPT will forward a reminder notice to the
prime service vendor 6 months before the subcontractor reconciliation
completion date. This notice will instruct prime vendors to report
subcontractor reconciliation information to the OPT by the completion
date. In addition, vendors must report to the OPT any subcontractors
that do not respond to their requests for reconciliation. The OPT will
forward at least two letters to subcontractor(s) requiring their
compliance to the reconciliation request. If the subcontractor(s) fail
to respond to the requests, the OPT will report the noncompliance to the
FCC.

The prime service vendor will complete the "prime service vendor to
subcontractor" reconciliation once every 3 years for each subcontractor
with which the prime service vendor jointly provides TSP services. Upon
completion of each "prime to subcontractor" reconciliation, the prime
service vendor will notify the OPT that all TSP service information
discrepancies with each subcontractor have been identified and resolved.
(If prime service vendors need additional time to identify and resolve
discrepancies, the prime service vendor may request an extension from
the OPT.) If the prime service vendor fails to submit the subcontractor
reconciliation information within 30 days of the due date (and has not
filed a request for an extension), the OPT will send a late notice to
the prime vendor. If the prime vendor fails to respond to the late
notice, the OPT will report the noncompliance to the FCC.

# 6.0 SERVICE VENDORS' REQUESTS FOR TSP ASSIGNMENTS

Telecommunications service vendors may themselves require priority
treatment of services they lease, particularly those services that
support a maintenance or network monitoring function and thus are
critical to the integrity of the service vendor's network. The FCC's TSP
Program rules recognize that significance and make provisions for
service vendor requirements. Service vendors who use other service
vendor's networks and who want a TSP assignment should refer to *Service
User Manual for the TSP System* (NCSM 3-1-1) for information on
requesting TSP. (Copies are available from the OPT.)

## 6.1 Exempt Control Services And Orderwires

Control services or orderwires wholly owned and supplied by a service
vendor and needed by that same vendor for provisioning, restoration, or
maintenance of other services are exempt from the FCC's TSP Program
rules. Such control services and orderwires shall have priority of
provisioning and restoration over all other telecommunications services
(including TSP services) and are exempt from preemption. In other words,
any service vendor owning a service that is used as a control service or
orderwire critical to the integrity of that service vendor's own network
may afford that service the highest priority for provisioning and
restoration even before services with TSP assignments, and need not
request a TSP assignment from the OPT.

## 6.2 Nonexempt Control Services and Orderwires

Control services and orderwires used by one service vendor, but leased
from another service vendor, are not exempt from the FCC's TSP Program
rules. In other words, such services will not be afforded priority
treatment by the service vendor providing the service unless it has a
TSP assignment. The telecommunications service vendor that is leasing
the control service or orderwire may request a TSP assignment following
the procedures outlined in the *Service User Manual for the TSP System
(NCSM 3-1-1).*

## 6.3 Requesting a TSP Assignment for Other Service Vendor NS/EP Requirements

A service vendor may also request a TSP assignment for a provisioning
and restoration priority for any other service (not used as a control
service or orderwire) that fulfills an NS/EP requirement and qualifies
under the TSP Program. For such requirements, the service vendor should
contact the OPT for assistance.

**APPENDIX A**

**[Telecommunications]{.smallcaps}**

**[Service Priority (TSP)]{.smallcaps}**

**[Program Contact]{.smallcaps}**

##### Information

**TSP PROGRAM CONTACT INFORMATION**

**8 a.m. to 5 p.m. (Eastern Time), Monday through Friday**

**TELEPHONE:**

Business hours: 703-235-5359 After Hours: 703-217-4118

> 703-235-5650 703-887-7689

**FACSIMILE:**

Unclassified: 703-235-5806

**NOTE**: Call the TSP Program Office to obtain classified facsimile
information.

Contact 703-235-5359 if you have additional questions.

**E-MAIL:**

tsp@dhs.gov

**TSP HOME PAGE:**

http://tsp.ncs.gov **(see page A-2 for detailed information on the TSP
home page)**.

**MAILING ADDRESS:**

DHS/NPPD/CS&C

National Communications System

ATTN: TSP Program Office

Mail Stop 8510

245 Murray Road, Bldg. 410

Washington, DC 20528-8510

**FEDERAL COMMUNICATIONS COMMISSION**

**FCC Watch Office**

**TELEPHONE:**

\(202\) 632-6975

**NOTE: Ask for the TSP Point of Contact.**

**TSP HOME PAGE**

The TSP home page informs readers of activities related to the TSP
Program. The TSP home page (http://tsp.ncs.gov) provides an overview of
the TSP Program, explains eligibility requirements, and contains
TSP-related documentation. TSP-related documentation that can be
downloaded or viewed from the TSP home page includes the following:

-   FCC TSP Report and Order, 88-341

-   NCS Directive 3-1, "TSP System for NS/EP"

-   NCS Manual 3-1-1, "Service User Manual for the TSP System"

-   NCS Handbook 3-1-2, "Service Vendor Handbook for the TSP System"

-   TSP Forms

-   TSP Oversight Committee meeting announcements

-   TSP training dates.

    **APPENDIX B**

##### Electronic File 

**[Requirements]{.smallcaps}**

**STRUCTURE OF CONFIRMATION (SF 318) ELECTRONIC FILES**

**FOR INTERCHANGE BETWEEN**

**THE PRIME SERVICE VENDOR AND THE OPT**

###### FILES MUST BE IN ASCII FORMAT

**FIRST LINE:** Point of contact information

  -------------------------------------------------------------------------------------
  **Columns**   **Width**   **Field   **Description**   **Remarks**
                            \#**                        
  ------------- ----------- --------- ----------------- -------------------------------
  1-30          30          7         POC name          UPPERCASE; LAST NAME, FIRST
                                                        NAME

  31-60         30          3A        POC title         UPPERCASE; optional

  61-100        40          1         POC organization  UPPERCASE
  -------------------------------------------------------------------------------------

**SECOND LINE:** Header record

  ----------------------------------------------------------------------------------
  **Columns**   **Width**   **Field   **Description**      **Remarks**
                            \#**                           
  ------------- ----------- --------- -------------------- -------------------------
  1-2           2           N/A       (Two dollar signs)   

  3-42          40          1         Vendor name          UPPERCASE

  43-48         6           4         Date data compiled   MMDDYY format

  49-54         6           5         Number of items      Right-justified
                                      reported             
  ----------------------------------------------------------------------------------

**ALL OTHER LINES:** Detail records

  ----------------------------------------------------------------------------------
  **Columns**   **Width**   **Field   **Description**      **Remarks**
                            \#**                           
  ------------- ----------- --------- -------------------- -------------------------
  1-9           9           2B1       TSP control ID       UPPERCASE

  10            1           N/A       (One hyphen)         

  11            1           2B2       Provisioning         
                                      Priority             

  12            1           2B2       Restoration Priority 

  13-55         43          2C1       Circuit ID           UPPERCASE

  56            1           2D        Type of order        UPPERCASE
  ----------------------------------------------------------------------------------

**Please see notes below and on next page.**

The three names specified in line 1 and the vendor name in line 2 must
be spelled and punctuated as they appear in the TSP database. If there
is uncertainty as to these, please contact the OPT at 703-607-4933 prior
to submitting files.

Valid order types (in detail lines) are as follows: N (new), C (change),
D (disconnect).

**EXAMPLE**: (The first two lines identify columns.)

  -------------------------------------------------------------------------------------- --------- --------- -------- -------- ------- -------- ----------
  **1**                                                                                  **2**     **3**     **4**    **5**    **6**   **7**    **8**

  **12345678901234567890123456789012345678901234567890123456789012345678901234567890**                                                          
  -------------------------------------------------------------------------------------- --------- --------- -------- -------- ------- -------- ----------

**SMITH, JOHN TSP MOGUL ABC, INC.**

**\$\$ABC, INC. 020794 2**

**TSP01ABCD-04RUEJ109273 N**

####### TSP00GMBH-22PLLH42783ADI02 D 

**STRUCTURE OF RECONCILIATION (SF 319) ELECTRONIC FILES**

**FOR INTERCHANGE BETWEEN**

**THE PRIME SERVICE VENDOR AND THE OPT**

**[FILES MUST BE IN ASCII FORMAT]{.underline}**

**FIRST LINE:** Point of contact information

  -------------------------------------------------------------------------------------
  **Columns**   **Width**   **Field   **Description**   **Remarks**
                            \#**                        
  ------------- ----------- --------- ----------------- -------------------------------
  1-30          30          7         POC name          UPPERCASE; LAST NAME, FIRST
                                                        NAME

  31-60         30          3A        POC title         UPPERCASE; optional

  61-100        40          1         POC organization  UPPERCASE
  -------------------------------------------------------------------------------------

**SECOND LINE:** Header record

  ----------------------------------------------------------------------------------
  **Columns**   **Width**   **Field   **Description**      **Remarks**
                            \#**                           
  ------------- ----------- --------- -------------------- -------------------------
  1-2           2           N/A       (Two dollar signs)   

  3-42          40          1         Vendor name          UPPERCASE

  43-48         6           4         Date data compiled   MMDDYY format

  49-54         6           5         Number of items      Right-justified
                                      reported             
  ----------------------------------------------------------------------------------

**ALL OTHER LINES:** Detail records

  ----------------------------------------------------------------------------------
  **Columns**   **Width**   **Field   **Description**      **Remarks**
                            \#**                           
  ------------- ----------- --------- -------------------- -------------------------
  1-9           9           2B1       TSP Control ID       UPPERCASE

  10            1           N/A       (One hyphen)         

  11            1           2B2       Provisioning         
                                      Priority             

  12            1           2B2       Restoration Priority 

  13-55         43          2C1       Circuit ID           UPPERCASE
  ----------------------------------------------------------------------------------

**Please see notes below.**

The three names specified in line 1 and the vendor name in line 2 must
be spelled and punctuated as they appear in the TSP database. If there
is uncertainty as to these, please contact the OPT at 703-607-4933 prior
to submitting files.

**EXAMPLE**: (the first two lines identify columns)

  -------------------------------------------------------------------------------------- ------- -------- --------- --------- ------- ------- --------------------------
  **1**                                                                                  **2**   **3**    **4**     **5**     **6**   **7**   **8**

  **12345678901234567890123456789012345678901234567890123456789012345678901234567890**                                                        
  -------------------------------------------------------------------------------------- ------- -------- --------- --------- ------- ------- --------------------------

**SMITH, JOHN TSP MOGUL ABC, INC.**

**\$\$ABC, INC. 020794 2**

**TSP01ABCD-04RUEJ109273**

**TSP00GMBH-22PLLH42783ADI02**

##### APPENDIX C

**TSP F[orms:]{.smallcaps}**

**[- SF 315]{.smallcaps}**

**[- SF 318]{.smallcaps}**

**[- SF 319]{.smallcaps}**

[^1]: By performing reconciliation, the Manager, NCS (through the OPT)
    is complying with a portion of his responsibility to administer the
    TSP Program, and in that capacity is not obligated to reimburse the
    service vendor for any reconciliation costs. Costs associated with
    reconciliation should be directed to the service user. Service
    vendors may recover the costs associated with reconciliation through
    provisions contained in properly filed State or Federal tariffs or
    provisions of properly negotiated contracts.