1 / 23

BellSouth 22.0 LOH Overview

BellSouth 22.0 LOH Overview. PURPOSE. Provide a high-level overview of the documentation changes impacting the LOH or LEO IG V2 for the 22.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.

evette
Download Presentation

BellSouth 22.0 LOH Overview

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. BellSouth 22.0 LOH Overview

  2. PURPOSE • Provide a high-level overview of the documentation changes impacting the LOH or LEO IG V2 for the 22.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-38889 (CR 2134) • F-39589 (CR 2210) • F-38702 (CR 2191) • F-38694 (CR 2191) • F-38697 (CR 2191) • F-38700 (CR 2191) • F-38708 (CR 2191) • F-38353 (CR 2191) • F-37825 (CR 2191) Release 21 item worked to LOH with Release 22 • F-38684 (CR 2191) Release 20 item worked to LOH with Release 22

  4. Features and CRs cont. The following list of features do not have LOH impact but will be summarized in this presentation: • F-39024 (CR 2173) • F-37952 / F-40701 (CR 2301)

  5. F-38889 (CR 2134) • Current Process • For REQTYP J, requests to change the service address on listing only accounts must be submitted manually, using the EUMI field. • Expected Process: • With the implementation of this feature, requests to change the service address on listing only accounts will be handled electronically, using the EUMI field.

  6. F-38889 (CR 2134) cont. • What is affected with this change: LOH changes to ELMS6 and ELMS10: • Made changes to REQTYP-J R/C/O tables • Made changes in the LSR, EU, and DL Data Dictionaries.

  7. F-39589 (CR 2210) • Current Process • LSRs that need to utilize the NCON field must be submitted manually. • Expected Process: • Upon implementation of this feature, if the NCON field is populated on a REQ A, ACT N or T, the system will validate the service address only. The service order will be generated with the LOC the CLEC provides. • What is affected with this change: LOH changes for ELMS6 and ELMS10: • Made changes to REQTYP–A R/C/O tables.

  8. F-38702 (CR 2191) • Current Process: • The Ordinance (ORDN) field is not returned in the Parsed CSR Response • Expected Process: • When a Parse CSR Query is executed and the BOCRIS CSR contains Ordinance (ORDN) number, the data shall be returned in the ORDN field on the Parsed CSR Response. • What is affected with this change: LOH changes forELMS10: • Added the ORDN field to the EDI and TAG Pre- Order Data Dictionaries • Added the ORDN field to the Pre-Order PCSRR transaction grid for EDI and TAG

  9. F-38694 (CR 2191) • Current Process • When executing a Parsed CSR query the valid values of J, K, L and P are applicable as entries for the FPI field. • Expected Process: • When executing a Parsed CSR query the valid values of J, K, L and P will no longer be applicable for the FPI field.   • What is affected with this change: LOH changes forELMS10: • Modified the Valid Entries in the FPI field in the EDI and TAG Pre-Order Data Dictionaries

  10. F-38697 (CR 2191) • Current Process • Currently the valid values for the FPI field are E, A, B, J, K, L, O, P, R, S and T. • Expected Process: • The valid values J, K, L and P will no longer be valid and will be removed from the FPI field as valid values. • What is affected with this change: LOH changes forELMS10: • Changed the valid values in the FPI field on the Ordering RS, PS, and DIDDODPBX Data Dictionaries

  11. F-38700 (CR 2191) • Current Process • The Ordinance Number (ORDN) is a new ELMS 10 field. In the state of Mississippi, orders are being processed without an ordinance number, which is required in most counties. LENS does not display the Service Instruction field nor the data that is returned • Expected Process: • With implementation of this feature, the Ordinance Number (ORDN) will be used to provide the Ordinance permit number that is required in counties in the state of Mississippi as determined by the city, county or state government agency. With implementation of this feature, LENS will display the Service Instruction field along with the data that is returned. Note: This field will also be applicable in the EDI and TAG schemas.

  12. F-38700 (CR 2191) continued • What is affected with this change: LOH changes forELMS10: • Added the ORDN field to the Ordering EU data dictionary • Added the ORDN field to the REQTYP E and REQTYP M (Non-Complex) R/C/O tables

  13. F-38708 (CR 2191) • Current Process: • Currently, the SO, FAINFO, & FATN fields in the Listing Instruction section on the Directory Listing screen are prohibited. Currently, there are no ELMS 10 service order generation rules for the HS, SHTN, SO, FAINFO, FATN, PLSO, PLFAINFO, & PLFATN fields. Currently, the DOI value must be 0-6 • Expected Process: • Add functionality for the SO, FAINFO, & FATN fields in the Listing Instruction section on the Directory Listing screen. Add ELMS 10 service order generation rules for the HS, SHTN, SO, FAINFO, FATN, PLSO, PLFAINFO, & PLFATN fields. With implementation of this feature, the DOI value must be 0-7

  14. F-38708 (CR 2191) continued • What is affected with this change: LOH changes forELMS10: • Made changes to the following fields in the Ordering DL Data Dictionary: ADI, DOI, LVL, PLS, PLINFO, PLTN, SO, LTEXT. FAINFO, and FATN. LOH changes forELMS6: • Made changes to the following fields in the Ordering DL Data Dictionary: ADI, DOI, LVL, PLS, PLINFO, PLTN, SO, and LTEXT.

  15. F-38353 (CR 2191) • Current Process: • WEB Base LSRs are formatted to appear like the ELMS6 manual forms. • Expected Process: • Modify WEB Based LSRs to appear like the ELMS10 manual forms. • What is affected with this change: • Modified Web Based LSR forms to match ELMS10.

  16. F-37825 (CR 2191) • Current Process: • Currently, LSR forms are submitted electronically via TCIF 9 and ELMS 6 Industry Maps. Currently, REQTYP M uses the Resale Form and Port Form. • Expected Process: • With implementation of this feature, LSR forms will be submitted electronically via separate ELMS 6 and ELMS 10 Industry Maps. In ELMS 10, REQTYP M will use the Port Form only. In ELMS 6, REQTYP M will continue to use the Resale and Port Forms. The Internal SCHEMA will represent a combined ELMS 6 and ELMS 10 Industry view.

  17. F-37825 (CR 2191) continued • What is affected with this change: Note: This is a Release 21 item that prepared fro ELMS10. LOH changes were not made until Release 22 when ELMS10 was effective. LOH changes forELMS10: • Added the HS, SHTN, PLSO, PLFAINFO, & PLFATN fields to the REQTYP J R/C/O tables. • Added the HS, SHTN, PLSO, PLFAINFO, & PLFATN fields to the Ordering DL Data Dictionary. • Added new fields to Responses. • Made changes to REQTYP-B and REQTYP-J R/C/O tables.

  18. F-38684 (CR 2191) • 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. There are no changes to Pre-Order queries and responses for ELMS 10 except for Parse CSR. Pre-Order queries and responses for TCIF 9 and ELMS 6 are not changing

  19. F-38684 (CR 2191) continued • What is affected with this change: Note: This is a Release 21 item that prepared fro ELMS10. LOH changes were not made until Release 22 when ELMS10 was effective. LOH changes for ELMS10: • Added the following fields to the Pre-Order EDI and TAG Parsed CSR Query / Response grids: PLSO, PLFAINFO, PLFATN, HS, and SHTN. • Added the following fields to the Pre-Order EDI and TAG Data Dictionaries: PLSO, PLFAINFO, PLFATN, HS, and SHTN. • Made changes to the following existing field in the Pre-Order EDI and TAG Data Dictionaries: FATN, FAINFO, and SO.

  20. F-39024 (CR 2173) • Current Process: • LSRs are being returned to the user with an error of “TOS Invalid for TXT-“, when the TOS is 2A-- or 2B-- on REQTYP B/ACT V requests where NC is TXT-. • Expected Process: • When LSRs are submitted for REQTYP B/ACT V and NC is TXT- and TOS is 2A-- or 2B--, the system will process the request. • What is affected with this change: There are no LOH changes required for this feature.

  21. F-37952 / F-40701 (CR 2301) • Current Process: - Currently, inside wire maintenance plans cannot be ordered electronically for REQTYP M. • Expected Process: - The system will allow inside wire maintenance plans to be ordered electronically for REQTYP M. • What is affected with this change: LOH changes for ELMS6 and ELMS10: • Made changes to REQTYP–M R/C/O tables. • Made changes to LSR, EU and PS Data Dictionaries

  22. For more information on 22.0 LOH documentation changes please refer to the Summary of Changes section of the LOH at: ELMS6: http://interconnection.bellsouth.com/reference_library/guides/leo/bbrlo_releases/22_0/docs/22-e06-1.pdf ELMS10: http://interconnection.bellsouth.com/reference_library/guides/leo/bbrlo_releases/22_0/docs/22-e10-1.pdf

  23. For more information on 22.0 LEO IG V2 documentation changes please refer to the LEO IG V2 at: http://interconnection.bellsouth.com/reference_library/guides/leo/gleod018/index.htm

More Related