General Guidelines for SPOP - PowerPoint PPT Presentation

About This Presentation
Title:

General Guidelines for SPOP

Description:

SPOP conversions must follow Qwest project guidelines ... LEHI. HEBER CITY. AMERICAN FORK. CUSTOMER NAME and ACNA. REV. 7/21/09 ... – PowerPoint PPT presentation

Number of Views:50
Avg rating:3.0/5.0
Slides: 20
Provided by: ToddRo8
Category:

less

Transcript and Presenter's Notes

Title: General Guidelines for SPOP


1
UTAH LATA 660
General Guidelines for SPOP
  • SPOP is ordered and implemented on a per switch,
    per LATA basis
  • Overflow is not permitted/allowed among/between
    different switches
  • SPOP conversions must follow Qwest project
    guidelines
  • Service Managers must obtain appropriate LATA
    Maps from the Wholesale SPOP website and email
    diagrams to customer to complete
  • Service Managers will control and validate LATA
    Maps (diagrams) to be used in conjunction with
    the Customer SPOP Checklist in the kick off
    (pre-provisioning meeting)
  • Completion of the SPOP Checklist and LATA Maps
    are required as part of the Joint Planning
    Process
  • Customer is responsible for sharing LATA Maps,
    Customer SPOP Checklist and all documentation
    related to SPOP with people within their own
    company associated with SPOP implementation
    (e.g., Network, Order Writing, Provisioning,
    etc.,)
  • For WSPs, the Service Manager will assist the
    customer for localities where 2 way trunking is
    not available due to cell pack feature
    unavailability.
  • SLRN may be in affect on your local trunk groups
    - Conversion to SPOP may result in traffic
    pattern changes
  • You may not need a trunk group to the local
    tandem
  • If you are only serving customers in this Local
    Tandem Area using a LRN that is outside of the
    Local Calling Area and
  • You do not have a full NPA-NXX and
  • You exchange less than one DS1 or less than 512
    BHCCS worth of traffic to the local tandem and
    you are not using ARLRN but normal (default)
    routing
  • You may still want a trunk group to the local
    tandem for your originating traffic to Qwest and
    other A-Record Holder Providers in the Local
    Calling Area

Rev 5/6/09
2
Subtending Localities















UTAH LATA 660
CUSTOMER NAME and ACNA
ALTA LOGAN
BOUNTIFUL MAGNA
BRIGHAM CITY MIDVALE
CLEARFIELD MORGAN
CORINNE MOUNTAIN GREEN
COTTONWOOD MURRAY
DRAPER OGDEN
FARMINGTON PARK CITY
GRANTSVILLE RICHMOND
HEBER CITY RIVERTON
HOLLADAY ROY
HUNTSVILLE SALT LAKE CITY
HYRUM SMITHFIELD
KAYSVILLE TOOLE
KEARNS WEST JORDAN
Locality covered by local tandem submit
diagram for local tandem, also.
REV. 10/10/08
3
INSTRUCTIONS
UTAH LATA 660
  • Use previous slide as a template. Copy all and
    paste to new document
  • In top left box enter the full NPA-NXXs
    assigned to the switch and in LATA 660 (on ASR,
    full NPA-NXXs should go in CNPANXX fields on
    Translations Questionnaire).
  • In center left boxes enter LERG switch CLLI (this
    is always the PSL on the Access Service Request
    Form) and POI/ACTL CLLI (this is the ACTL on the
    Access Service Request Form). If POI/ACTL CLLI
    is owned by another OCN, LOA must be provided.
  • In lower left hexagon enter actual switch CLLI
    from SHA screen in LERG and point code (actual
    switch CLLI is always the CSL and the point code
    is entered in the CSPC field on the TRUNKING form
    of the ASR). LERG switch CLLI and actual switch
    CLLI may be the same if the actual switch is in
    the same LATA and then PSL and CSL would be the
    same CLLI.
  • EITHER enter a single line from POI/ACTL CLLI box
    to each access tandem circle and label 2W SPOP
    COMBINED and include quantity of trunks
    requested OR enter 2 lines from POI/ACTL CLLI box
    to each access tandem circle and label top line
    2W SPOP IXC and bottom line 2W SPOP
    Local/Intra and include quantity of trunks
    requested.
  • Indicate the QWEST localities where you will be
    conducting business by changing the color to red.
  • Full NPA-NXXs also known as Code Holder,
    LERG Assignee, or A Record Holder

REV. 10/10/08
4
Subtending Localities

UTAH LATA 660
CUSTOMER NAME and ACNA
AMERICAN FORK HEBER CITY
LEHI
MONROE
NEPHI
OREM
PAYSON
PLEASANT GROVE
PROVO
RICHFIELD
SALINA
SANTAQUIN
SPANISH FORK
SPRINGVILLE
Locality covered by local tandem submit
diagram for local tandem, also.
REV. 10/10/08
5
INSTRUCTIONS
UTAH LATA 660
  • Use previous slide as a template. Copy all and
    paste to new document
  • In top left box enter the full NPA-NXXs
    assigned to the switch and in LATA 660 (on ASR,
    full NPA-NXXs should go in CNPANXX fields on
    Translations Questionnaire).
  • In center left boxes enter LERG switch CLLI (this
    is always the PSL on the Access Service Request
    Form) and POI/ACTL CLLI (this is the ACTL on the
    Access Service Request Form). If POI/ACTL CLLI
    is owned by another OCN, LOA must be provided.
  • In lower left hexagon enter actual switch CLLI
    from SHA screen in LERG and point code (actual
    switch CLLI is always the CSL and the point code
    is entered in the CSPC field on the TRUNKING form
    of the ASR). LERG switch CLLI and actual switch
    CLLI may be the same if the actual switch is in
    the same LATA and then PSL and CSL would be the
    same CLLI.
  • EITHER enter a single line from POI/ACTL CLLI box
    to each access tandem circle and label 2W SPOP
    COMBINED and include quantity of trunks
    requested OR enter 2 lines from POI/ACTL CLLI box
    to each access tandem circle and label top line
    2W SPOP IXC and bottom line 2W SPOP
    Local/Intra and include quantity of trunks
    requested.
  • Indicate the QWEST localities where you will be
    conducting business by changing the color to red.
  • Full NPA-NXXs also known as Code Holder,
    LERG Assignee, or A Record Holder

REV. 10/10/08
6
Subtending Localities

UTAH LATA 660
CUSTOMER NAME and ACNA
BEAVER
BRIAN HEAD
CEDAR CITY
HURRICANE
LEEDS
PAROWAN
SPRINGDALE
ST GEORGE
VEYO

REV. 10/10/08
7
INSTRUCTIONS
UTAH LATA 660
  • Use previous slide as a template. Copy all and
    paste to new document
  • In top left box enter the full NPA-NXXs
    assigned to the switch and in LATA 660 (on ASR,
    full NPA-NXXs should go in CNPANXX fields on
    Translations Questionnaire).
  • In center left boxes enter LERG switch CLLI (this
    is always the PSL on the Access Service Request
    Form) and POI/ACTL CLLI (this is the ACTL on the
    Access Service Request Form). If POI/ACTL CLLI
    is owned by another OCN, LOA must be provided.
  • In lower left hexagon enter actual switch CLLI
    from SHA screen in LERG and point code (actual
    switch CLLI is always the CSL and the point code
    is entered in the CSPC field on the TRUNKING form
    of the ASR). LERG switch CLLI and actual switch
    CLLI may be the same if the actual switch is in
    the same LATA and then PSL and CSL would be the
    same CLLI.
  • EITHER enter a single line from POI/ACTL CLLI box
    to each access tandem circle and label 2W SPOP
    COMBINED and include quantity of trunks
    requested OR enter 2 lines from POI/ACTL CLLI box
    to each access tandem circle and label top line
    2W SPOP IXC and bottom line 2W SPOP
    Local/Intra and include quantity of trunks
    requested.
  • Indicate the QWEST localities where you will be
    conducting business by changing the color to red.
  • Full NPA-NXXs also known as Code Holder,
    LERG Assignee, or A Record
  • Holder

REV. 10/10/08
8
Subtending Localities

UTAH LATA 660
CUSTOMER NAME and ACNA
BOUNTIFUL
COTTONWOOD
DRAPER
FARMINGTON
HOLLADAY
KAYSVILLE
KEARNS
MAGNA
MIDVALE
MURRAY
RIVERTON
SALT LAKE CITY
WEST JORDAN
If Existing POI/ACTL CLLI Identify the POI/ACTL
CLLI If Need New POI/ACTL CLLI Identify City
Name for the POI/ACTL CLLI
REV. 7/21/09
9
INSTRUCTIONS
UTAH LATA 660
WARNING SLRN may be in affect on your local
trunk groups - Conversion to SPOP may result in
traffic pattern changes
  • Use previous slide as a template. Copy all and
    paste to new document
  • In top left box enter the full NPA-NXXs
    assigned to the switch and in the SALT LAKE
    LOCAL CALLING AREA (on ASR, full NPA-NXXs
    should go in CNPANXX fields on Translations
    Questionnaire). If no full NPA-NXXs, MAY REQUEST
    ARLRN. SEE ARLRN PCAT FOR MORE INFORMATION.
    http//www.qwest.com/wholesale/clecs/slrn.html
  • In center left boxes enter LERG switch CLLI (this
    is always the PSL on the Access Service Request
    Form) and POI/ACTL CLLI (this is the ACTL on the
    Access Service Request Form). If POI/ACTL CLLI
    is owned by another OCN, LOA must be provided.
  • In lower left hexagon enter actual switch CLLI
    from SHA screen in LERG and point code (actual
    switch CLLI is always the CSL and the point code
    is entered in the CSPC field on the TRUNKING form
    of the ASR). LERG switch CLLI and actual switch
    CLLI may be the same if the actual switch is in
    the same LATA and then PSL and CSL would be the
    same CLLI.
  • Enter a single line from POI/ACTL CLLI box to
    each local tandem circle and label 2W SPOP
    LOCAL and include quantity of trunks requested.
  • Indicate the QWEST localities where you will be
    conducting business by changing the color to red.
  • Full NPA-NXXs also known as Code Holder,
    LERG Assignee, or A Record Holder

REV. 2/5/09
10
Subtending Localities

LATA 660
CUSTOMER NAME and ACNA
AMERICAN FORK
HEBER CITY
LEHI
OREM
PAYSON
PLEASANT GROVE
PROVO
SANTAQUIN
SPANISH FORK
SPRINGVILLE
If Existing POI/ACTL CLLI Identify the POI/ACTL
CLLI If Need New POI/ACTL CLLI Identify City
Name for the POI/ACTL CLLI
REV. 7/21/09
11
INSTRUCTIONS
UTAH LATA 660
WARNING SLRN may be in affect on your local
trunk groups - Conversion to SPOP may result in
traffic pattern changes
  • Use previous slide as a template. Copy all and
    paste to new document
  • In top left box enter the full NPA-NXXs
    assigned to the switch and in the PROVO LOCAL
    CALLING AREA (on ASR, full NPA-NXXs should go
    in CNPANXX fields on Translations Questionnaire).
    If no full NPA-NXXs, MAY REQUEST ARLRN. SEE
    ARLRN PCAT FOR MORE INFORMATION.
    http//www.qwest.com/wholesale/clecs/slrn.html
  • In center left boxes enter LERG switch CLLI (this
    is always the PSL on the Access Service Request
    Form) and POI/ACTL CLLI (this is the ACTL on the
    Access Service Request Form). If POI/ACTL CLLI
    is owned by another OCN, LOA must be provided.
  • In lower left hexagon enter actual switch CLLI
    from SHA screen in LERG and point code (actual
    switch CLLI is always the CSL and the point code
    is entered in the CSPC field on the TRUNKING form
    of the ASR). LERG switch CLLI and actual switch
    CLLI may be the same if the actual switch is in
    the same LATA and then PSL and CSL would be the
    same CLLI.
  • Enter a single line from POI/ACTL CLLI box to
    each local tandem circle and label 2W SPOP
    LOCAL and include quantity of trunks requested.
  • Indicate the QWEST localities where you will be
    conducting business by changing the color to red.
  • Full NPA-NXXs also known as Code Holder,
    LERG Assignee, or A Record Holder

REV. 2/5/09
12
Subtending Localities

LATA 660
CUSTOMER NAME and ACNA

CLEARFIELD
HUNTSVILLE
MORGAN
MOUNTAIN GREEN
OGDEN
ROY
If Existing POI/ACTL CLLI Identify the POI/ACTL
CLLI If Need New POI/ACTL CLLI Identify City
Name for the POI/ACTL CLLI
REV. 7/21/09
13
INSTRUCTIONS
UTAH LATA 660
WARNING SLRN may be in affect on your local
trunk groups - Conversion to SPOP may result in
traffic pattern changes
  • Use previous slide as a template. Copy all and
    paste to new document
  • In top left box enter the full NPA-NXXs
    assigned to the switch and in the OGDEN LOCAL
    CALLING AREA (on ASR, full NPA-NXXs should go
    in CNPANXX fields on Translations Questionnaire).
    If no full NPA-NXXs, MAY REQUEST ARLRN. SEE
    ARLRN PCAT FOR MORE INFORMATION.
    http//www.qwest.com/wholesale/clecs/slrn.html
  • In center left boxes enter LERG switch CLLI (this
    is always the PSL on the Access Service Request
    Form) and POI/ACTL CLLI (this is the ACTL on the
    Access Service Request Form). If POI/ACTL CLLI
    is owned by another OCN, LOA must be provided.
  • In lower left hexagon enter actual switch CLLI
    from SHA screen in LERG and point code (actual
    switch CLLI is always the CSL and the point code
    is entered in the CSPC field on the TRUNKING form
    of the ASR). LERG switch CLLI and actual switch
    CLLI may be the same if the actual switch is in
    the same LATA and then PSL and CSL would be the
    same CLLI.
  • Enter a single line from POI/ACTL CLLI box to
    each local tandem circle and label 2W SPOP
    LOCAL and include quantity of trunks requested.
  • Indicate the QWEST localities where you will be
    conducting business by changing the color to red.
  • Full NPA-NXXs also known as Code Holder,
    LERG Assignee, or A Record Holder

REV. 2/5/09
14
Subtending Localities

LATA 660
CUSTOMER NAME and ACNA
HURRICANE
LEEDS
SPRINGDALE
ST GEORGE
VEYO
If Existing POI/ACTL CLLI Identify the POI/ACTL
CLLI If Need New POI/ACTL CLLI Identify City
Name for the POI/ACTL CLLI
REV. 7/21/09
15
INSTRUCTIONS
UTAH LATA 660
WARNING SLRN may be in affect on your local
trunk groups - Conversion to SPOP may result in
traffic pattern changes
  • Use previous slide as a template. Copy all and
    paste to new document
  • In top left box enter the full NPA-NXXs
    assigned to the switch and in the ST. GEORGE
    LOCAL CALLING AREA (on ASR, full NPA-NXXs
    should go in CNPANXX fields on Translations
    Questionnaire). If no full NPA-NXXs, MAY REQUEST
    ARLRN. SEE ARLRN PCAT FOR MORE INFORMATION.
    http//www.qwest.com/wholesale/clecs/slrn.html
  • In center left boxes enter LERG switch CLLI (this
    is always the PSL on the Access Service Request
    Form) and POI/ACTL CLLI (this is the ACTL on the
    Access Service Request Form). If POI/ACTL CLLI
    is owned by another OCN, LOA must be provided.
  • In lower left hexagon enter actual switch CLLI
    from SHA screen in LERG and point code (actual
    switch CLLI is always the CSL and the point code
    is entered in the CSPC field on the TRUNKING form
    of the ASR). LERG switch CLLI and actual switch
    CLLI may be the same if the actual switch is in
    the same LATA and then PSL and CSL would be the
    same CLLI.
  • Enter a single line from POI/ACTL CLLI box to
    each local tandem circle and label 2W SPOP
    LOCAL and include quantity of trunks requested.
  • Indicate the QWEST localities where you will be
    conducting business by changing the color to red.
  • Full NPA-NXXs also known as Code Holder,
    LERG Assignee, or A Record Holder

REV. 2/5/09
16
UTAH LATA 660
CUSTOMER NAME and ACNA
Subtending Localities
Park City





If Existing POI/ACTL CLLI Identify the POI/ACTL
CLLI If Need New POI/ACTL CLLI Identify City
Name for the POI/ACTL CLLI
REV. 9/3/09
17
UTAH LATA 660
INSTRUCTIONS
WARNING SLRN may be in affect on your local
trunk groups - Conversion to SPOP may result in
traffic pattern changes
  • Use previous slide as a template. Copy all and
    paste to new document
  • In top left box enter the full NPA-NXXs
    assigned to the switch and in the Park City LOCAL
    CALLING AREA (on ASR, full NPA-NXXs should go
    in CNPANXX fields on the Translations
    Questionnaire). If no full NPA-NXXs, MAY
    REQUEST ARLRN. SEE ARLRN PCAT FOR MORE
    INFORMATION. http//www.qwest.com/wholesale/clecs/
    slrn.html
  • In center left boxes enter LERG switch CLLI (this
    is always the PSL on the Access Service Request
    Form) and POI/ACTL CLLI (this is the ACTL on the
    Access Service Request page). If POI/ACTL CLLI
    is owned by another OCN, LOA must be provided.
  • In lower left hexagon enter actual switch CLLI
    from SHA screen in LERG and point code (actual
    switch CLLI is always the CSL and the point code
    is entered in the CSPC field on the TRUNKING form
    of the ASR). LERG switch CLLI and actual switch
    CLLI may be the same if the actual switch is in
    the same LATA and then PSL and CSL would be the
    same CLLI.
  • Enter a single line from POI/ACTL CLLI box to
    each local tandem circle and label 2W SPOP
    LOCAL and include quantity of trunks requested.
  • Indicate the QWEST localities where you will be
    conducting business by changing the color of the
    font to red.

Full NPA-NXXs also known as Code Holder,
LERG Assignee, or A Record Holder
REV. 2/5/09
18
UTAH LATA 660
CUSTOMER NAME and ACNA
Subtending Localities
TOOLUTMA01T LOCAL TANDEM LED 10/6/09
TOOELE GRANTSVILLE





If Existing POI/ACTL CLLI Identify the POI/ACTL
CLLI If Need New POI/ACTL CLLI Identify City
Name for the POI/ACTL CLLI
LED LERG Effective Date
REV. 9/3/09
19
INSTRUCTIONS
UTAH LATA 660
WARNING SLRN may be in affect on your local
trunk groups - Conversion to SPOP may result in
traffic pattern changes
  • Use previous slide as a template. Copy all and
    paste to new document
  • In top left box enter the full NPA-NXXs
    assigned to the switch and in the TOOELE, UT
    LOCAL CALLING AREA (on ASR, full NPA-NXXs
    should go in CNPANXX fields on the Translations
    Questionnaire). If no full NPA-NXXs, MAY
    REQUEST ARLRN. SEE ARLRN PCAT FOR MORE
    INFORMATION. http//www.qwest.com/wholesale/clecs/
    slrn.html
  • In center left boxes enter LERG switch CLLI (this
    is always the PSL on the Access Service Request
    Form) and POI/ACTL CLLI (this is the ACTL on the
    Access Service Request page). If POI/ACTL CLLI
    is owned by another OCN, LOA must be provided.
  • In lower left hexagon enter actual switch CLLI
    from SHA screen in LERG and point code (actual
    switch CLLI is always the CSL and the point code
    is entered in the CSPC field on the TRUNKING form
    of the ASR). LERG switch CLLI and actual switch
    CLLI may be the same if the actual switch is in
    the same LATA and then PSL and CSL would be the
    same CLLI.
  • Enter a single line from POI/ACTL CLLI box to
    each local tandem circle and label 2W SPOP
    LOCAL and include quantity of trunks requested.
  • Indicate the QWEST localities where you will be
    conducting business by changing the color of the
    font to red.

Full NPA-NXXs also known as Code Holder,
LERG Assignee, or A Record Holder
REV. 9/3/09
Write a Comment
User Comments (0)
About PowerShow.com