Primary headline goes here Secondary headline

1
BellSouth 20.0 LOH Overview
2
PURPOSE

• Provide a high-level overview of the
  documentation changes impacting the LOH or LEO IG
  V2 for the 20.0 production release.
• This presentation includes summaries of all
  release related item not just those with impacts
  to the LOH or LEO IG V2 documents.
• Note This presentation is not inclusive of the
  changes made in the LOH. The LSR originator
  should consult the LOH ordering guides when
  submitting LSR requests

3
Features and CRs

• The following list of features have LOH impact
  and will be discussed in this presentation
• F-25288 (1260)
• F-37109 (1907)
• F-38901 (2183)

4
Features and CRs cont.

• The following list of features do not have LOH
  impact but will be summarized in this
  presentation
• F-21863 (n/a)
• F-35758 (n/a)
• F-37665 (1980)
• F-38007 (1928)
• F-38138 (2025)
• F-38684 (n/a)

5
F-25288 (CR 1260)

• Current Process
• On a request for REQTYP A, ACT D, the system
  requires the user provide NC Code(s), but does
  not validate them against the circuit ID to be
  disconnected.
• If an incorrect NC code is populated for the
  circuit being disconnected, the order receives a
  SOER error due to mismatch in the BCS on the
  order and BCS from the CSR.
• Expected Process
• Upon implementation of this feature, on a request
  for REQTYP A, ACT D, the system will validate the
  NC Code(s) provided against the circuit ID to be
  disconnected.
• This will allow the request to flow through with
  the correct BCS from the CSR.

6
F-25288 (CR 1260) cont.

• What is affected with this change
• LOH changes to ELMS6 and TCIF9
• Made Rule changes to the NC, NCI, and SECNCI
  fields on the LSR Data Dictionary

7
F-37109 (CR 1907)

• Current Process
• CLEC to CLEC Conversions for REQTYP A UNE Loops
  is a manual process only since there is no
  current functionality for REQ A, ACT W.
• Expected Process
• Upon implementation of this feature, requests for
  CLEC to CLEC Conversions for REQTYP A can be
  submitted electronically with the ACT of W and
  the order be generated electronically
• What is affected with this change
• LOH changes to ELMS6 only
• Made rule changes to the LSR, EU and LS Data
  Dictionaries,
• Added R/C/O tables for ACT W for applicable
  REQTYP A products.
• Removed existing R/C/O tables from CLEC to CLEC
  Conversion product documentation

8
F-38901 (CR 2183)

• Current Process
• All Listing Instruction Code (LIC) data, and
  some FIDS, existing in BOCRIS have not been
  categorized for the CSR WBS (CSR Wholesale
  Business System). These codes/fids are not
  supported electronically, and therefore, CSR WBS
  is generating incorrect listing data for this
  subset of un-categorized LICs and FIDs.
• Expected Process
• This feature will identify the Listing
  Instruction Codes (LICs), and some FIDs, that
  have not been categorized for the CSR WBS, and
  that can not be supported electronically.
  Functionality will prohibit the entire listing
  that contains these LICs or FIDs from being
  returned on the Parsed CSR fielded section of the
  response message.
• What is affected with this change
• LOH changes to ELMS6 and TCIF9
• Notes made in LOH Pre-Ordering on PCSRR
  Transaction

9
F-21863 (CR n/a)

• Current Process
• The USOC UEAL2 is generated on SL1 UNBUNDLED LOOP
  orders, at the CKL-2 location.
• Expected Process
• Upon implementation of this feature the system
  will generate the new UEASL USOC instead of the
  UEAL2 USOC at CKL-2 of all SL1 UNBUNDLED LOOP
  orders.  
• What is affected with this change
• No LOH changes required for this
  feature.

10
F-35758 (CR n/a)

• Current Process
• Today when a LSR is submitted in TN KY and the
  USOC ARZPK appears or is being generated by the
  system, the LSR will fall to center for SAE 009
  Error. A rep must manually add the PKG FID (/PKG
  AP-WITH-CPCH) behind the line class of service
  and all USOCS associated with Complete Choice.
  Currently, there is a date/time stamp field on
  the LENS LSR Summary. However, it only shows the
  date the LSR was submitted-not the time.
• Today when a LSR is submitted in MS and the USOC
  ARPEC appears or is being generated by the
  system, the LSR will fall to the center for SAE
  009 Error. A rep must manually add the PKG FID
  (/PKG ACP ECONO-CC) behind the line class of
  service and all USOCS associated with Complete
  Choice.
• When a UPP USOC currently exists on the CSR and
  an LSR is submitted to add (inward activity) the
  system will populate the UPP USOC for the same
  line creating an error on the service order.

11
F-35758 (CR n/a) cont.

• Expected Process
• When a LSR is submitted in TN KY and the USOC
  ARZPK appears or is being generated by the
  system, the system will float the PKG FID (/PKG
  AP-WITH-CPCH) behind the line class of service
  and all USOCS associated with Complete Choice.
• When a LSR is submitted in MS and USOC ARPEC
  appears or is being generated by the system, the
  system will float the PKG FID (/PKG ACP ECONO-CC)
  behind the line class of service and all USOCS
  associated with Complete Choice.
• When a UPP USOC currently exists on the CSR and
  an LSR is submitted to add a new UPP USOC to
  the same line, the system will O action code
  the existing USOC and I action code the
  requested USOC.

12
F-35758 (CR n/a) cont.

• What is affected with this change
• No LOH changes required for this feature.

13
F-37665 (CR 1980)

• Current Process
• The Central Office Address and Central Office
  Switch Type are not returned with the address
  data that is returned, when an address is
  validated by TN or Address.
• The customer must execute two separate queries to
  obtain both the validated address and to view the
  Central Office address information.
• Expected Process
• When an address is validated by TN or Address,
  the Central Office Address and Central Office
  Switch Type will be returned with the address
  data that is returned, when an address is
  validated by TN or Address.
• The View CO Switch Address query will present
  the CO switch type when executed.
• What is affected with this change
• No LOH changes required for this feature.

14
F-38007 (CR 1928)

• Current Process
• The customer does not have the ability to
  populate data in the access field in LENS.
• Expected Process
• The customer will have the ability to populate
  the access field in LENS with data for REQTYP E
  (non-complex) and M (non-complex)
• What is affected with this change
• No LOH changes required for this feature.

15
F-38138 (CR 2025)

• Current Process
• When an LNP LSR has been submitted, has not
  completed its initial processing, and the CLEC
  runs a status summary query, the system is
  returning an improper status message to the CLEC
  in response to a status summary.
• Expected Process
• When an LNP LSR has been submitted, has not
  completed its initial processing, and the CLEC
  runs a status summary query, the message "PON NOT
  FOUND" will be replaced with a message similar to
  "THE REQUESTED PON IS STILL BEING PROCESSED.
  PLEASE TRY AGAIN LATER
• What is affected with this change
• No LOH changes required for this feature.

16
F-38684 (CR n/a)

• Current Process
• Currently, Pre-Order queries and responses are
  available for both TCIF 9 and ELMS 6.
• Expected Process
• Pre-Order queries and responses will be
  developed for ELMS 10.
• What is affected with this change
• No LOH changes required at this time. System
  changes are being made in advance of Release 22
  (ELMS10). Actual LOH changes will be made with
  Release 22.

17

• For more information on 20.0 LOH documentation
  changes please refer to the Summary of Changes
  section of the LOH at
• ELMS6
• http//interconnection.bellsouth.com/guides/leo/bb
  rlo_releases/20_0/docs/200-1.pdf
• TCIF9
• http//interconnection.bellsouth.com/guides/leo/bb
  rlo_releases/20_0/docs/T-200-1.pdf

18

• For more information on 20.0 LEO IG V2
  documentation changes please refer to the LEO IG
  V2 at
• http//interconnection.bellsouth.com/guides/usoc/h
  tml/gleod010/index.htm