Ordering process, Interoffice transport orders, Unbundled dark fiber – Sprint Nextel Unbundled Dark Fiber User Manual
Page 7
Unbundled Dark Fiber
10/02 Version 1
Copyright 2002 Sprint Communications Company
7
Ordering Process
UDF must be ordered via a Local Service Request (LSR) or an Access Service Request (ASR),
depending on the type of route requested. Refer to Table 1 below to determine which type of order
to use. Submission of a UDF firm order indicates that the CLEC agrees to pay the quoted monthly
recurring and non-recurring charges.
Sprint will provide the UDF route to the CLEC within 20 business days after a firm order is
received from CLEC. Sprint will begin invoicing of the monthly recurring and non-recurring charges
upon completion of the order.
Table 1 – Order Types for Unbundled Dark Fiber
Route Type
Definition
Order
Type
1) CO to CO (interoffice
transport)
Dark fiber transport is between two Sprint FPPs in two
separate Sprint offices.
ASR
2) CO to an end-user
premises located FPP
(loop)
Dark fiber loop is between a Sprint FPP located in a Sprint
CO and a Sprint FPP located at an end-user premises.
LSR
3) CO to remote (feeder
subloop)
Dark fiber feeder is between two Sprint FPPs - one located
in a Sprint CO and one at a remote location served by that
CO.
LSR
4) Remote to remote
(distribution subloop)
Dark fiber distribution can be between Sprint FPPs at two
remote locations, such as digital loop carriers.
LSR
5) Remote to an end-
user premises located
FPP (distribution
subloop)
Dark fiber distribution can be between a Sprint FPP located
outside a Sprint CO (e.g., remote site) and a FPP located at
end-user premises.
LSR
Interoffice Transport Orders
Route Type 1 is considered Interoffice Transport. Route Type 1 should be ordered via an ASR and
submitted to the Sprint National Access Service Center (NASC).
Additionally, orders may be placed in Access Request Management System (ARMS) via Sprint’s
Host on Demand. The entries required for Interoffice Transport orders placed into ARMS are
provided on the sample screens below. Each field should be populated with end-user specific
information.