verizon west lsog 5 & 6 june 2005 release overview only – over 12,000 ft lxn- 02qb5.001 txfu...
TRANSCRIPT
FINAL DOCUMENT Release Date – June 13, 2005
Verizon West LSOG 5 & 6
June 2005 Release Overview
This document contains material which is a proprietary property of and confidential to VERIZON. Disclosure outside VERIZON is prohibited except by written permission, license agreement or other
confidentiality agreement. Unauthorized reproduction or distribution of this document in any form or by any electronic or mechanical means is expressly prohibited.
Copyright @2002 by VERIZON. All Rights Reserved Worldwide
FINAL DOCUMENT Release Date – June 13, 2005
TABLE OF CONTENTS
1. REVISION HISTORY.................................................................................................................... 3
2. SYSTEM RELEASE NOTIFICATION ........................................................................... 4 CLEC IMPACTING:............................................................................................................................................... 4
C03-0480/382056 - 2W IDSL/SDSL-capable UNE Loop (West) ....................................................................... 4 C04-0896/388292 - If Pending order Reject LSR .............................................................................................. 5 C04-1132/388718 - Flow Through to Automate Disconnect orders without NC/NCI code.............................. 13 C04-1755/390290 - Packet Switching Deployment in fGTE ............................................................................ 14 C04-0707/387800 - Sunset of SARv3.............................................................................................................. 15 E05-0001/388922.7 - Remove Edit E05/6FLDH01046.................................................................................... 19 E05-0006/388922.10 - Sunset of LSOG 5 West .............................................................................................. 20 E05-0007/388922.11 - Modify E06FLDH05192 to include FA=V .................................................................... 21 E05-0008/388922.12 - New Edit to require Correct CLLI Length .................................................................... 22 Business Rule Database Updates.................................................................................................................... 23 C04-1943/390836 - LSRs with Account Type B1 and Coin ECS..................................................................... 26 C03-2229/385658 - Strip leading zeros from fields to match EDI Specifications ............................................ 27 C04-1631/389920 - T5 Address Validation returns alternative with a complete parsed service address ....... 28 C04-1089/388839 - Flow Through: Modify Edits to allow Wholesale request when the BTN has been previously ported on accounts with subordinate telephone numbers still retail ............................................... 29
NON-CLEC SYSTEM IMPACTING:.................................................................................................................... 30 C03-0986/383486 - Flow Through: Outside Plant Charge for OH.................................................................. 30 C04-0874/388229 - Flow Through to Automate all Pending orders................................................................. 31 C04-1727/390287 - RFIC/BFIC Auto Completion ............................................................................................ 32
FINAL DOCUMENT Release Date – June 13, 2005
1. REVISION HISTORY
Revision Date Description of Change 04/28/2005 45-Day Notification
C04-0896 *Bulletin O-05-010 – Modified Edit Impacts Table. C04-0707 Documentation update. Modified SN length to 28, covered with CLECs during Pre-Release call on 4/20/05. * Bulletin O-05-007 - Modified field length for HTSEQ.
* Bulletin O-05-008 – Modified field length for HT/HTN.
C04-1943 * Bulletin O-05-009 – Modified Edit Impacts Table. C04-1089 Documentation Update - Added REQTYP=BB to description, covered with CLECs during Pre-Release Call on 4/20/2005. * Bulletins were covered with CLECs on 4/27/05.
06/13/2005 C04-0896 – Added scenarios. C04-0707 – Added additional information for HNTYP field. All changes are in blue font.
FINAL DOCUMENT Release Date – June 13, 2005
2. SYSTEM RELEASE NOTIFICATION
CLEC IMPACTING: C03-0480/382056 - 2W IDSL/SDSL-capable UNE Loop (West) Type: 4 Description: Develop and implement unique NC/NCI codes for ordering IDSL and SDSL. Details: Currently CLECs in Verizon West order loops capable of supporting IDSL and SDSL via 2W Digital xDSL process. This initiative establishes unique NC/NCI codes for IDSL and SDSL and an applicable line IOSC. The following table depicts new NC/NCI Codes and associated IOSC. TOS 2nd Char
TOS 4th Character 1=Non-Design 2=Design
LSR SLI
Element NC Code NCI Code SCMD REQTYP IOSC
SDSL-Capable 2 WIRE LOOP 2 1 S 2-Wire SDSL Capable Loop LX-- 02QB5.002 TXXS AB 89582-MRC
2 1 S 2-Wire SDSL Capable – Remove Bridged Tap only – UNDER 12,000 FT LX-N 02QB5.002 TXFS AB 89582-MRC
2 1 S 2-Wire SDSL Capable – Remove Bridge Tap and Load Coils – OVER 12,000 FT LXUN 02QB5.002 TXFS AB 89582-MRC
2 1 S 2-Wire SDSL Capable – Remove Load Coils only – OVER 12,000 FT LXR- 02QB5.002 TXFS AB 89582-MRC
2 1 S 2-Wire SDSL Capable – Remove Bridged Tap only – OVER 12,000 FT LXN- 02QB5.002 TXFS AB 89582-MRC
IDSL-Capable 2 WIRE LOOP 2 1 S 2-Wire IDSL Capable Loop LX-- 02QB5.001 TXXU AB 89592-MRC
2 1 S 2-Wire IDSL Capable – Remove Bridged Tap only – UNDER 12,000 FT LX-N 02QB5.001 TXFU AB 89592-MRC
2 1 S 2-Wire IDSL Capable – Remove Bridged and Load Coils – OVER 12,000 FT LXUN 02QB5.001 TXFU AB 89592-MRC
2 1 S 2-Wire IDSL Capable – Remove Load Coils only – OVER 12,000 FT LXR- 02QB5.001 TXFU AB 89592-MRC
2 1 S 2-Wire IDSL Capable – Remove Bridged Tap only – OVER 12,000 FT LXN- 02QB5.001 TXFU AB 89592-MRC
Business Rule Impacts: None Edit Impacts: None
FINAL DOCUMENT Release Date – June 13, 2005 C04-0896/388292 - If Pending order Reject LSR Type: 4 Description: The scope of this initiative is to reject or process any incoming LSR that has an existing “Pending Order” on the account based on scenarios. Details: Automated processes will check for existing “Pending Orders” in the ordering system and Reject the incoming LSR if pending orders exist for the same Account Telephone Number, unless the incoming LSR is for the same CCNA/PON as the pending order. New Auto Reject Error will be sent and the message will include the expected Due Date of the pending order with the exception of a Duplicate Request. Business Rule Impacts: LSR/Administrative/REQTYP for LSOG5 and LSOG6. Added New Error Message and Usage Note for the 2nd position of TOS=P. Edit Impacts: The following table depicts the edit changes associated with this change request:
Action LSOG Version
Form Section Field LSOG 5 Error Code
LSOG 6 Error Code
New Error Message
Add 5 6 LSR Administrative REQTYP E05FLDH01509 E06FLDH01509 If SLI=S, ACT=N and position 2 of TOS=P then REQTYP must =MB.
The following table depicts the Auto/Standardized Manual edit changes associated with this change request:
Action LSOG Version
Form Section Field LSOG 5 Error Code
LSOG 6 Error Code
New Error Message
Add 5 6 LSR Admin REQTYP E05FLDH99829 E06FLDH99829 Pending Change Orders. Due mm/dd/yyyy.
Add 5 6 LSR Admin REQTYP E05FLDH99835 E06FLDH99835 Pending Move Orders. Due mm/dd/yyyy.
Add 5 6 LSR Admin REQTYP E05FLDH99836 E06FLDH99836 Pending Disconnect Orders. Due mm/dd/yyyy.
Add 5 6 LSR Admin REQTYP E05FLDH99847 E06FLDH99847 Pending Conversion Orders. Due mm/dd/yyyy.
Add 5 6 LSR Admin REQTYP E05FLDH99852 E06FLDH99852 Pending Suspend Orders. Due mm/dd/yyyy.
Add 5 6 LSR Admin REQTYP E05FLDH99865 E06FLDH99865 Pending Restore Orders. Due mm/dd/yyyy.
Add 5 6 LSR Admin REQTYP E05FLDH99866 E06FLDH99866 Duplicate Request.
FINAL DOCUMENT Release Date – June 13, 2005 Listed below are the scenarios: Situations when LSR should be rejected (CCNA/PON of incoming LSR is different than the pending LSR) PLATFORM (MB)/RESALE (EB) PENDING ORDER GUIDELINES Exclude Line Splitting (MB, 2nd TOS character = P) LSR Coming
in: And Pending Order from previous LSR is a:
Reject with the Error message
Error Code
1.
REQTYP = EB Act = W/V or REQTYP=MB, ACT=V is received.
Platform or Resale Conversion Pending Conversion Orders. Due mm/dd/yyyy.
E0xFLDH99847
2.
REQTYP = EB Act = W/V or REQTYP=MB, ACT=V is received.
Disconnect Order
Pending Disconnect Orders. Due mm/dd/yyyy.
E0xFLDH99836
3.
REQTYP = EB Act = W/V or REQTYP=MB, ACT=V is received.
Move Order
Pending Move Orders. Due mm/dd/yyyy.
E0xFLDH99835
4.
REQTYP = EB Act = W/V or REQTYP=MB, ACT=V is received.
Change Order
Pending Change Orders. Due mm/dd/yyyy.
E0xFLDH99829
5
REQTYP = MB/EB ACT = S is received
Conversion (MB/EB, ACT=W/V, clec to clec migration) and due date is equal to or earlier than the suspend/restore due date
Pending Conversion Orders. Due mm/dd/yyyy.
E0xFLDH99847
6
REQTYP = MB/EB ACT = B is received
Conversion (MB/EB, ACT=W/V, clec to clec migration) and due date is equal to or earlier than the suspend/restore due date.
Pending Conversion Orders. Due mm/dd/yyyy.
E0xFLDH99847
7
REQTYP = MB/EB ACT = D is received
Conversion (MB/EB, ACT=W/V, clec to clec migration), And due date is within two business days of disconnect due date.
Pending Conversion Orders. Due mm/dd/yyyy.
E0xFLDH99847
8
REQTYP = MB/EB ACT = D is received
Conversion (MB/EB, ACT=W/V, clec to clec migration) and due date is more than two business days of disconnect due date
Pending Conversion Orders. Due mm/dd/yyyy.
E0xFLDH99847
9
REQTYP = MB/EB ACT = C is received
Conversion (MB/EB, ACT=W/V, clec to clec migration)
Pending Conversion Orders. Due mm/dd/yyyy.
E0xFLDH99847
10
REQTYP = MB/EB ACT = T is received
Conversion (MB/EB, ACT=W/V, clec to clec migration)
Pending Conversion Orders. Due mm/dd/yyyy.
E0xFLDH99847
FINAL DOCUMENT Release Date – June 13, 2005 LINE SPLITTING (MB and AB) PENDING ORDER GUIDELINES 2nd character of TOS = P LSR Coming
in: And Pending Order from previous LSR is a:
Reject with the Error message
Error Code
11
REQTYP = AB/MB ACT = V is received
Move Order Pending Move Orders. Due mm/dd/yyyy.
E0xFLDH99835
12
REQTYP = AB/MB ACT = V is received
Change Order and due date is equal to or greater than conversion due date.
Pending Change Orders. Due mm/dd/yyyy.
E0xFLDH99829
13
REQTYP =MB ACT = V is received
Change Order and due date is earlier than the conversion due date
Pending Change Orders. Due mm/dd/yyyy.
E0xFLDH99829
14
REQTYP = MB, ACT = D is received
Disconnect Order (Same ACT and different REQTYP)
Pending Disconnect Orders. Due mm/dd/yyyy.
E0xFLDH99836
15
REQTYP = MB, ACT = D is received
Conversion (MB, ACT=W/V, CLEC to CLEC migration) and due date is within two business days of disconnect due date
Pending Conversion Orders. Due mm/dd/yyyy.
E0xFLDH99847
16
REQTYP = AB/MB ACT = D is received
Conversion (MB, ACT=W/V, clec to clec migration) (DD is more than two business days of disconnect due date)
Pending Conversion Orders. Due mm/dd/yyyy.
E0xFLDH99847
17
REQTYP = AB/MB ACT = C is received
Conversion (MB/EB, ACT=W/V, clec to clec migration)
Pending Conversion Orders. Due mm/dd/yyyy.
E0xFLDH99847
18
REQTYP = MB ACT = S is received
Conversion (due date is equal to or earlier than suspend date)
Pending Conversion Orders. Due mm/dd/yyyy.
E0xFLDH99847
19
REQTYP = MB ACT = B is received
Conversion (due date is equal to or earlier than restore date)
Pending Conversion Orders. Due mm/dd/yyyy.
E0xFLDH99847
20
REQTYP = AB ACT = V is received
Change Order (Due date is earlier than the conversion due date)
Pending Change Orders. Due mm/dd/yyyy.
E0xFLDH99829
FINAL DOCUMENT Release Date – June 13, 2005 CONVERSION TO UNE LOOP / PORT-OUTS (AB,BB,CB) PENDING ORDER GUIDELINES. Exclude Line share, Line Splitting and Loop share (2nd TOS character = R, F, or P) LSR Coming
in: And Pending Order from previous LSR is a:
Reject with the Error message
Error Code
21
REQTYP = AB/BB/CB ACT = V is received
Conversion to UNE Loop/Port Out (Same ACT and Same REQTYP)
Pending Conversion Orders. Due mm/dd/yyyy.
E0xFLDH99847
22
REQTYP = BB ACT = V is received
Conversion (BB/V)
Pending Conversion Orders. Due mm/dd/yyyy.
E0xFLDH99847
23
REQTYP = AB/BB/CB ACT = V is received
Disconnect Order Pending Disconnect Orders. Due mm/dd/yyyy.
E0xFLDH99836
24
REQTYP = AB/BB/CB ACT = V is received
Change Order Pending Change Orders. Due mm/dd/yyyy.
E0xFLDH99829
25
REQTYP = AB/BB/CB ACT = V is received
Move Order Pending Move Orders. Due mm/dd/yyyy.
E0xFLDH99835
UNE LINE SHARE PENDING ORDER SCENARIOS
2nd character of TOS = R and SAME SLTN LSR Coming
in: And Pending Order from previous LSR is a:
Reject with the Error message Error Code
26
REQTYP = AB ACT = N is received
Change order Pending Change Orders. Due mm/dd/yyyy.
E0xFLDH99829
27
REQTYP = AB ACT = V is received
Change order Pending Change Orders. Due mm/dd/yyyy.
E0xFLDH99829
28
REQTYP = AB ACT = V is received
Move Order Pending Move Orders. Due mm/dd/yyyy.
E0xFLDH99835
29
REQTYP = AB ACT = V is received
Disconnect Order Pending Disconnect Orders. Due mm/dd/yyyy.
E0xFLDH99836
30
REQTYP = AB ACT = D is received
Disconnect Order (Due Date is equal to or less than the Line Share Disconnect Due Date)
Pending Disconnect Orders. Due mm/dd/yyyy.
E0xFLDH99836
31
REQTYP = AB ACT = D is received
Move Order (Due Date is equal to or less than the Line Share Disconnect Due Date)
Pending Move Orders. Due mm/dd/yyyy.
E0xFLDH99835
32
REQTYP = AB ACT = D is received
Change order (Change of TN and DD is equal to or less than Line Share Disconnect Due Date)
Pending Change Orders. Due mm/dd/yyyy.
E0xFLDH99829
FINAL DOCUMENT Release Date – June 13, 2005 Situations when pending order is Retail order PLATFORM (MB)/RESALE (EB) PENDING ORDER GUIDELINES Exclude Line Splitting (MB, 2nd TOS character = P) LSR Coming
in: And Pending Order from previous LSR is a:
Reject with the Error message Error Code
1
REQTYP = EB Act = W/V or REQTYP=MB, ACT=V is received.
Disconnect Order
Pending Disconnect Orders. Due mm/dd/yyyy.
E0xFLDH99836
2
REQTYP = EB Act = W/V or REQTYP=MB, ACT=V is received.
Move Order
Pending Move Orders. Due mm/dd/yyyy.
E0xFLDH99835
3
REQTYP = EB Act = W/V or REQTYP=MB, ACT=V is received.
Change Order
Pending Change Orders. Due mm/dd/yyyy.
E0xFLDH99829
LINE SPLITTING (MB and AB) PENDING ORDER GUIDELINES 2nd character of TOS = P LSR Coming
in: And Pending Order from previous LSR is a:
Reject with the Error message Error Code
4
REQTYP = MB ACT = V is received
Disconnect Order Pending Disconnect Orders. Due mm/dd/yyyy.
E0xFLDH99836
5
REQTYP = MB ACT = V is received
Change order (Due date is equal to or greater than conversion due date)
Pending Change Orders. Due mm/dd/yyyy.
E0xFLDH99829
6
REQTYP =MB ACT = V is received
Change order (Due date is earlier than the conversion due date)
Pending Change Orders. Due mm/dd/yyyy.
E0xFLDH99829
7
REQTYP = MB ACT = V is received
Move Order Pending Move Orders. Due mm/dd/yyyy.
E0xFLDH99835
CONVERSION TO UNE LOOP / PORT-OUTS (AB,BB,CB) PENDING ORDER GUIDELINES. Exclude Line share, Line Splitting and Loop share (2nd TOS character = R, F, or P) LSR Coming
in: And Pending Order from previous LSR is a:
Reject with the Error message Error Code
8
REQTYP = AB/BB/CB ACT = V is received
Disconnect Order Pending Disconnect Orders. Due mm/dd/yyyy.
E0xFLDH99836
9
REQTYP = AB/BB/CB ACT = V is received
Change Order Pending Change Orders. Due mm/dd/yyyy.”
E0xFLDH99829
10
REQTYP = AB/BB/CB ACT = V is received
Move Order Pending Move. Due mm/dd/yyyy. E0xFLDH99835
FINAL DOCUMENT Release Date – June 13, 2005 UNE LINE SHARE PENDING ORDER SCENARIOS 2nd character of TOS = R and SAME SLTN LSR Coming
in: And Pending Order from previous LSR is a:
Reject with the Error message Error Code
11
REQTYP = AB ACT = V is received
Change Order Pending Change Orders. Due mm/dd/yyyy.
E0xFLDH99829
12
REQTYP = AB ACT = V is received
Move Order Pending Move Orders. Due mm/dd/yyyy.
E0xFLDH99835
13
REQTYP = AB ACT = D is received
Disconnect Order (Due Date is equal to or less than the Line Share Disconnect Due Date)
Pending Disconnect Orders. Due mm/dd/yyyy.
E0xFLDH99836
14
REQTYP = AB ACT = D is received
Move Order (Due Date is equal to or less than the Line Share Disconnect Due Date)
Pending Move Orders. Due mm/dd/yyyy.
E0xFLDH99835
15
REQTYP = AB ACT = D is received
Change Order (Due Date is equal to or less than the Line Share Disconnect Due Date)
Pending Change Orders. Due mm/dd/yyyy.
E0xFLDH99829
LOOP SHARE (AB OR BB) PENDING ORDER GUIDELINES 2nd character of TOS = F LSR Coming
in: And Pending Order from previous LSR is a:
Reject with the Error message Error Code
16
REQTYP = AB/BB ACT = V is received
Change Order Pending Change Orders. Due mm/dd/yyyy.
E0xFLDH99829
17
REQTYP = AB/BB ACT = V is received
Disconnect Order Pending Disconnect Orders. Due mm/dd/yyy.
E0xFLDH99836
18
REQTYP = AB/BB ACT = V is received
Move Order Pending Move Orders. Due mm/dd/yyyy.
E0xFLDH99835
WINBACK (MB OR EB) PENDING ORDER GUIDELINES: LSR Coming
in: And Pending Order from previous LSR is a:
Reject with the Error message Error Code
19
REQTYP = MB/EB ACT = S is received
Pending Retail Winback
Pending Conversion Orders. Due mm/dd/yyyy.
E0xFLDH99847
20
REQTYP = MB/EB ACT = D is received
Pending Retail Winback
Pending Conversion Orders. Due mm/dd/yyyy.
E0xFLDH99847
21
REQTYP = MB/EB ACT = C is received
Pending Retail Winback
“Pending Conversion Orders. Due mm/dd/yyyy.
E0xFLDH99847
24
REQTYP = MB/EB ACT = T is received
Pending Retail Winback
Pending Conversion Orders. Due mm/dd/yyyy.
E0xFLDH99847
FINAL DOCUMENT Release Date – June 13, 2005 Situations when LSR is to be rejected/processed when CCNA is same PLATFORM (MB)/RESALE (EB) PENDING ORDER GUIDELINES Exclude Line Splitting (MB, 2nd TOS character = P) LSR Coming
in: And Pending Order from previous LSR is a:
Reject with the Error message Error Code
1
REQTYP = EB ACT = W/V is or when REQTYP MB, ACT=V is received
Platform or Resale Conversion (same ACT, same REQTYP)
Duplicate Request E0xFLDH99866
2
REQTYP = MB/EB ACT = S is received
Platform or Resale Temporary Disconnect (ACT=S) (Same ACT and same REQTYP)
Duplicate Request E0xFLDH99866
3
REQTYP = MB/EB ACT = B is received
Platform or Resale Reconnect (ACT=B) (Same ACT and same REQTYP)
Duplicate Request E0xFLDH99866
4
REQTYP = MB/EB ACT = D is received
Disconnect Order (Same ACT and same REQTYP)
Duplicate Request E0xFLDH99866
5
REQTYP = MB/EB ACT = C is received
Change Order Pending Change Orders. Due mm/dd/yyyy.
E0xFLDH99829
6
REQTYP = MB/EB ACT = T is received
Move Order Duplicate Request E0xFLDH99866
LINE SPLITTING (MB and AB) PENDING ORDER GUIDELINES 2nd character of TOS = P LSR Coming
in: And Pending Order from previous LSR is a:
Reject with the Error message Error Code
7
REQTYP = AB/MB ACT = V is received
Line Split Conversion (Same ACT and same REQTYP)
Duplicate Request E0xFLDH99866
8
REQTYP = MB ACT = D is received
Disconnect Order (Same ACT and same REQTYP)
Duplicate Request’ E0xFLDH99866
9
REQTYP = MB ACT = D is received
Disconnect Order (Same or Different CCNA, Same ACT and different REQTYP)
Pending Disconnect Orders. Due mm/dd/yyyy.
E0xFLDH99836
FINAL DOCUMENT Release Date – June 13, 2005 UNE LOOP (AB) PENDING ORDER GUIDELINES Exclude Line Share, Loop Share and Line Splitting (2nd TOS character equals R, P, or F) LSR Coming
in: And Pending Order from previous LSR is a:
Reject with the Error message Error Code
10
REQTYP = AB ACT = C is received
Change Order (UNE change, same CKT ID, same ACT)
Pending Change Orders. Due mm/dd/yyyy.
E0xFLDH99829
11
REQTYP = AB ACT = C is received
Change Order (UNE Change, different change activity)
Pending Change Orders. Due mm/dd/yyyy.
E0xFLDH99829
12
REQTYP = AB ACT = C LNA = D is received
Change Order (UNE Change, same CKT ID)
Pending Change Orders. Due mm/dd/yyyy.
E0xFLDH99829
CONVERSION TO UNE LOOP / PORT-OUTS (AB,BB,CB) PENDING ORDER GUIDELINES. Exclude Line share, Line Splitting and Loop share (2nd TOS character = R, F, or P) LSR Coming
in: And Pending Order from previous LSR is a:
Reject with the Error message Error Code
13
REQTYP = AB/BB/CB ACT = V is received
Conversion to UNE Loop/Port Out (Same ACT and Same REQTYP)
Duplicate Request E0xFLDH99866
14
REQTYP = AB/BB/CB ACT = V is received
Conversion to UNE Loop/Port Out (Same ACT and different REQTYP)
Pending Conversion Orders. Due mm/dd/yyyy.
E0xFLDH99847
UNE LINE SHARE PENDING ORDER SCENARIOS 2nd character of TOS = R and SAME SLTN LSR Coming
in: And Pending Order from previous LSR is a:
Reject with the Error message Error Code
15
REQTYP = AB ACT = V is received
Conversion to line share (Same CFA, Same ACT)
Pending Conversion Orders. Due mm/dd/yyyy.
E0xFLDH99847
16
REQTYP = AB ACT = C is received
Change Order (Duplicate Line Share Change request from the Same CCNA)
Pending Change Orders. Due mm/dd/yyyy.”
E0xFLDH99829
FINAL DOCUMENT Release Date – June 13, 2005 C04-1132/388718 - Flow Through to Automate Disconnect orders without NC/NCI code Type: 4 Description: Flow Through is routing LSRs for manual processing when NC/NCI code is not present on the LSR and the Customer Profile when ACT=D. Details: The purpose of this initiative is to automate LSRs for Loops, UNE & UNE-P, when the NC/NCI code is not present on Disconnects orders. The NC/NCI code must be present on the LSR so that the state specific disconnect charge(s) can be applied correctly. Business Rule Impacts: Edit Impacts: The following table depicts the edit changes associated with this change request:
Action LSOG Version
Form Section Field LSOG 5 Error Code
LSOG 6 Error Code
New Error Message
New 05 06 LSR Admin NC E05FLDH01510 E06FLDH01510 Required if REQTYP=AB,MB and ACT=D.
New
05 06 LSR Admin NC E05FLDH01511 E06FLDH01511 If REQTYP=AB and ACT=D then NC must match customer profile.
New 05 06 LSR Admin NCI E05FLDH01512 E06FLDH01512 If REQTYP=AB and ACT=D then NCI must match customer profile.
FINAL DOCUMENT Release Date – June 13, 2005 C04-1755/390290 - Packet Switching Deployment in fGTE Type: 4 Description: UNE Platform and UNE Port will no longer be offered in central offices once they convert to Packet Switching technology. Details: LSRs with REQTYP=MB, FB, with the exclusion of ACT=D, for areas converting to Packet Switching technology, will be rejected if DDD is later than 14 calendars before the switch conversion date. Business Rule Impacts: Added usage note to E05/6FLDH01484. Edit Impacts: Edit “E05/6FLDH01484 Product not available, unable to process request.” is being modified to invoke if the Desired Due Date is later than fourteen calendar days before the switch conversion date.
FINAL DOCUMENT Release Date – June 13, 2005 C04-0707/387800 - Sunset of SARv3 Type: 4 Description: LSOG 5 introduced the industry-standard Completion Notice (CN) also identified as Service Activation Report v4 (SARv4). Prior to CN (SARv4), Verizon West provided this information to the CLECs via SARv3 and SARv3 Loss Notification, proprietary forms specific to Verizon. SARv3 and SARv3 Loss Notification have not received any coding updates since the CN (SARv4) was implemented with LSOG 5 due to the size of SARv3. Details: SARv3 and SARv3 Loss notification will be sunset. New fields will be added SARv4 to accommodate CLEC recommendations. After the sunset of SARv3, if a CLEC requests a resend of a SAR that was generated as Version 3, it will be returned in the new Version 4 format. The new fields added with this initiative will return blank values. The following fields are being moved as-is from SARv3 to the CN: ORDTYP – Service Order Type SN – Subscriber Name FA – Feature Activity IOSC – SOSC/IOSC (Renamed to FEATURE – Feature Codes) QTY – Quantity HNTYP – Hunt Type HTSEQ – Hunt Sequence HT/HTN – Hunt Telephone Number. The following fields are being added as new fields to the CN: ALI – Alpha/Numeric Listing Identifier. Eleven (11) Alpha/Numeric character field, positions 1-5 will return the ALI code provided on the inbound DL form (if provided), position 6 a hyphen (-), positions 7 through 11 will return the ALI code assigned on the Service Order. This will be the same ALI code that will appear on Profile once the service order completes.
The ALI field Length displayed in the Business Rules for the DL Form and CSI R Transaction is being updated to reflect five (5) Numeric Characters to match current coding. HID – Hunt Group Identifier. This will return the Hunt Group assigned on the Verizon Service Order. Two conditions have been discovered where the HNTYP cannot be returned and are outlined below. We have coded the system to return HNTYP=N in the following conditions: Scenario 1: Adding new lines to an existing account, identifying the new lines on the HGI form as LNUMs (example shows adding three new lines as a hunt group). Inbound HGI form: HA=N HID=N HNTYP=2 HT/HTN=00001 (LNUM Value), HTSEQ=0001 HT/HTN=00002 HTSEQ=0002 HT/HTN=00003 HTSEQ=0003
FINAL DOCUMENT Release Date – June 13, 2005 Provisioning Order indicates: HID HTN HSEQ 1 8139791111 0001 1 8139793222 0002 1 8139793333 0003 Completion Notice will return: HNTYP: N HID: 1 HTSEQ: 0001 HTN: 8139791111 HID: 1 HTSEQ: 0002 HTN: 8139793222 HID: 1 HTSEQ: 0003 HTN: 8139793333 Note: In this scenario, if any of the HT/HTN value on the inbound LSR HGI form contains a 10 digit TN (regardless of HTSEQ), the system will return the HNTYP value as populated on the inbound LSR. Scenario 2: Adding a new Hunt Group, populating a HID value that already exists. When this occurs, Verizon processes the service order assigning the next available Hunt Group Identifier, returned on the LR. Inbound HGI form: HA=N HID=1 (exists on Profile) HNTYP=2 HT/HTN=8139791111 HTSEQ=0001 HT/HTN=8139793222 HTSEQ=0002 HT/HTN=8139793333 HTSEQ=0003 Provisioning Order indicates: HID HTN HSEQ
2 8139791111 0001 2 8139793222 0002 2 8139793333 0003
Completion Notice will return: HNTYP: N HID: 2 HTSEQ: 0001 HTN: 8139791111 HID: 2 HTSEQ: 0002 HTN: 8139793222 HID: 2 HTSEQ: 0003 HTN: 8139793333 Both of the above scenarios will return the correct HID, HT/HTN and HTSEQ as they were provisioned on the Verizon Service Order. All scenarios involving Hunting will return the appropriate Hunting IOSC added on the service order at a line level indicating the actual Type of Hunting provisioned in the FEATURE field for the appropriate Telephone Numbers.
FINAL DOCUMENT Release Date – June 13, 2005 Business Rule Impacts: The following table depicts LSOG 5/LSOG 6 Business Rule changes associated with this initiative.
Action Form or Transaction/ Section
Field # Header Section Valid Entry Section
Add CN/Admin 018e/018d ORDTYP – Service Order Type Field Length: 1 Characteristics: A/N Usage: Required Indicator: VERIZON SPECIFIC FIELD
Valid Entries: I = Installation of new service. O = Removal of service. C = Change in service detail. F = Moving from old service location. T = Moving to new service location. R = Records.
Add CN/Admin 010b/005b SN – Subscriber Name Field Length: 25 28 Characteristics: A/N Usage: Required Indicator: VERIZON SPECIFIC FIELD
Add CN/Admin 018f/018e FA – Feature Activity Field Length: 1 Characteristics: A/N Usage: Conditional Indicator: VERIZON SPECIFIC FIELD
Valid Entries: A=Add D=Delete
Add CN/Admin 018g/018f FEATURE – Feature Codes (Formerly IOSC – SOSC / IOSC on v3) Field Length: 6 Characteristics: A/N Usage: Conditional Indicator: VERIZON SPECIFIC FIELD
Add CN/Admin 018h/018g QTY - Quantity Field Length: 5 Characteristics: N Usage: Conditional Indicator: VERIZON SPECIFIC FIELD
Add CN/Admin 018j/018h ALI – Alpha/Numeric Listing Identifier Field Length: 11 Characteristics: A/N Usage: Conditional Indicator: VERIZON SPECIFIC FIELD
Valid Entries: Positions 1-5 will return ALI if provided by the CLEC. Position 6 = Hyphen (-) Positions 7-11 will return ALI assigned by Verizon if directory activity has occurred.
Add CN/Admin 018j/018i HNTYP – Hunt Type Field Length: 1 Characteristics: A/N Usage: Conditional Indicator: VERIZON SPECIFIC FIELD
Valid Entries: 2 = Sequential 3 = Circular 4 = Combination (Could apply to Centrex or others) S = Multi-line
Add CN/Admin 018k/018j HID – Hunt Group Information Field Length: 12 Characteristics: A/N Usage: Conditional Indicator: VERIZON SPECIFIC FIELD
Valid Entries: Hunt Group Identifier (1-9, A-M, O-Z)
Add CN/Admin 018l/018k HUNT SEQ – Hunting Sequence Field Length: 7 10 Characteristics: A/N Usage: Conditional Indicator: VERIZON SPECIFIC FIELD
Add CN/Admin 018m/018j HT – Hunt Telephone Number/ HTN – Hunt Telephone Number Field Length: 10 15 Characteristics: A/N Usage: Conditional Indicator: VERIZON SPECIFIC FIELD
Change DL/Listing Control
011/010 ALI – ALI – Alpha/Numeric Listing Identifier Code Modify Field Length FROM: 6 To: 5*
FINAL DOCUMENT Release Date – June 13, 2005 The following table depicts LSOG 5/LSOG 6 Pre-Order Business Rule changes associated with this initiative.
Action Form or Transaction/ Section
Field # Header Section Valid Entry Section
Change CSI R/Definitions
142/145 ALI – ALI – Alpha/Numeric Listing Identifier Code Modify Field Length FROM: 6 To: 5*
Edit Impacts: None
FINAL DOCUMENT Release Date – June 13, 2005 E05-0001/388922.7 - Remove Edit E05/6FLDH01046 Type: 4 Description: Due to the Form Level META Edits, E05/6FLDH01046 on the LSR/ACT field and E05/6FLDH01040 on the LSR/REQTYP field will never invoke. Details: Remove edits E05/6FLDH01046 and E05/6FLDH01040. Business Rule Impacts: None Edit Impacts: The following table depicts the edit changes associated with this change request:
Action LSOG Version
Form Section Field LSOG 5 Error Code
LSOG 6 Error Code
New Error Message
Remove 5 6 LSR Admin ACT E05FLDH01046 E06FLDH01046 Remove 5 6 LSR Admin REQTYP E05FLDH01040 E06FLDH01040
FINAL DOCUMENT Release Date – June 13, 2005 E05-0006/388922.10 - Sunset of LSOG 5 West Type: 3 Description: LSOG 5 will sunset in October 2005. To prohibit any orders with a due date beyond 10/7/05, new edits are being established on the DDD and DDDO fields. Details: Add new edits to the DDD and DDDO fields. Orders will no longer be processed with a DDD or DDDO value that extends beyond October 7, 2005. Business Rule Impacts: None Edit Impacts: The following table depicts the edit changes associated with this change request:
Action LSOG Version
Form Section Field LSOG 5 Error Code
LSOG 6 Error Code
New Error Message
Add 5 LSR Admin DDD E05FLDH01513 If populated, must be prior to October 8, 2005.
Add 5 LSR Admin DDDO E05FLDH01514 If populated, must be prior to October 8, 2005.
FINAL DOCUMENT Release Date – June 13, 2005 E05-0007/388922.11 - Modify E06FLDH05192 to include FA=V Type 1 Description: Edit does recognize FA=V when requesting UNE-P MWI on a conversion as specified without fixed call forwarding added on the LSR or existing on the account. Details: When a CLEC requests a UNE-P Conversion with Message Waiting Indicator (MWI) using REQTYP=MB, ACT=V, LNA=V, edit E06FLDH05192 will invoke if the LSR does not include 69179 Fixed Call Forwarding. When ordering UNE-P MWI, the only Fixed Call Forwarding IOSC that is valid with this service request is 69179. Business Rule Impacts: Modify usage note to include FA=V. Edit Impacts: Edit “E06FLDH05192 Fixed Call Forwarding not present on account or LSR.” will now invoke when FA=V with a UNE-P MWI IOSC and 69179 – Fixed Call Forwarding is not present on the LSR or on Customer Profile. The error message will remain unchanged.
FINAL DOCUMENT Release Date – June 13, 2005 E05-0008/388922.12 - New Edit to require Correct CLLI Length Type: 4 Description: Current edit does not check for valid CLLI Code length in the LST field. The CLLI code must be eleven characters to be considered valid. Details: Adding new edit to require LSR/LST to be eleven (11) characters. Business Rule Impacts: None Edit Impacts: The following table depicts the edit changes associated with this change request:
Action LSOG Version
Form Section Field LSOG 5 Error Code
LSOG 6 Error Code
New Error Message
Add 5 6 LSR Admin LST E05FLDH01515 E06FLDH01515 If populated, must be eleven characters.
FINAL DOCUMENT Release Date – June 13, 2005 Business Rule Database Updates Description: Modifications have been made to the Verizon West Business Rule Database to include the Standardized Manual Edits at the Field Level. Details: Effective with the June 2005 system release, all Standardized Manual Edits will appear at the field level, located below the Edits/Usage Rules section of the Field-Level Business Rule. With this change, you will now be able to include the these edits in the “Look Up an Error Code” section of the Business Rules in the same manner as the system-generated edits. The Proposed Edit Matrix will now track all additions, changes and deletions to the Standardized Manual Edits. Changes to the Standardized Manual Edits will appear below the Field Level Edit changes on the Proposed Edit Matrix. Business Rule Impacts: New section added under “Edits/Usage Rules” titled “Standardized Manual Edits”. Edit Impacts: Standardized Manual Edits will now appear at the Field Level.
DRAFT DOCUMENT Release Date – June 13, 2005
Page 24
Form: LSR, Local Service Request Category: Order Section: Administrative LSOG: 5 Field: PON ~ Purchase Order Number Region: West Field #: 002 Last Updated: MM/DD/YYYY Field Length: 16 Version: 0.0.0 Characteristics: A/N Usage: Required Definitions Usage Indicator Identifies the customer's unique purchase order or requisition number that authorizes the issuance of this request or supplement.
No. Note Usage Indicator 1 The Purchase Order Number may be reused after two years from the due date of the
original request.
Valid Entries Value Description Usage Indicator CLEC PON Number Verizon Added No. Note Usage Indicator Edits / Usage Rules No. Usage Note Error Code Error Message Explanation / Action Usage Indicator 1 E05FLDH01003 Required field not populated. 2 E05METH00001 PON field must contain the
same value on all forms. Verizon Added
Standardized Manual Edits No. Usage Note Error Code Error Message Explanation / Action Usage Indicator 1 E05FLDH99907 Invalid Pre-Order request.
Order already worked on different PON.
2 E05FLDH99985 Separate LSR Required/TN not on same account
Field Notes No. Note Usage Indicator
DRAFT DOCUMENT Release Date – June 13, 2005
Page 26
C04-1943/390836 - LSRs with Account Type B1 and Coin ECS Type: 1 Description: Allow edits to pass when ACT=V or W and the first character of TOS=1 and the second character of TOS=C. Details: Edit E05/6FLDH01259 and E05/6FLDH01295 will not invoke when the first character of TOS=1 (Business) and second=C (Coin). Business Rule Impacts: None Edit Impacts: The following table depicts the edit changes associated with this change request:
Action LSOG Version
Form Section Field LSOG 5 Error Code
LSOG 6 Error Code
New Error Message
Change 5 6 LSR Admin TOS E05FLDH01259 E06FLDH01259 If ACT=V,W and AR is not populated then positions 1 and 2 of TOS must agree with business, residence, government and coin characteristics on customer profile.
Change 5 6 LSR Admin TOS E05FLDH01295 E06FLDH01295 If REQTYP=AB, ACT=N, TOS position 2 = R then positions 1 and 2 of TOS must agree with business, residence, government and coin characteristics on customer profile. If REQTYP=AB, ACT=N, TOS position 2=R then positions 1 and 2 of TOS must agree with business, residence, government and coin characteristics on customer profile
FINAL DOCUMENT Release Date – June 13, 2005
Page 27
C03-2229/385658 - Strip leading zeros from fields to match EDI Specifications Type: 4 Description: Remove the leading zeros from quantity segments to match EDI standards. Details: There is a conflict when leading zeros are returned in EDI quantity segments and the leading zeros are not valid or insignificant to EDI. This change request will remove the leading zeros from quantity segments to match EDI standards. Business Rule Impacts: The following table depicts LSOG 5/LSOG 6 Business Rule changes associated with this initiative.
Action Form or Transaction/ Section
Field # Header Section Valid Entry Section
Change AV R 034/035 ALTADDNUM – Alternate Addresses Number From: 00-20 To: 0-20
Edit Impacts: None
FINAL DOCUMENT Release Date – June 13, 2005
Page 28
C04-1631/389920 - T5 Address Validation returns alternative with a complete parsed service address Type: 5 Description: Pre-Order address validation near matches will add two new fields to assist the end user in determining the necessary corrections / changes to obtain an exact match. Details: A new field, CAII - Concatenated Address Information Identifier will be added to Pre-Order Address Validation Responses indicating the address validation value associated with the CAI field. The entry in this field will indicate the address element that needs to be corrected in order to obtain an exact match. A new field, PAV – Partial Address Validation will be added to the Pre-Order Address Validation Response indicating valid service address details for a partial match. This field will only be populated if an address is submitted with an LDn or an LDn and LVn value and an exact match is not found. The user will receive up to 50 near matches. Listed below is an example of the PAV - Partial Address Validation field: 100 Main St Apt 1 Tampa, Fl, 33612 100 Main St Apt 2 Tampa, Fl, 33612 100 Main St Apt 3 Tampa, Fl, 33612 100 Main St Apt 4 Tampa, Fl, 33612 100 Main St Apt 5 Tampa, Fl, 33612 Please note, if the PAV field is populated the CAI and CAII fields will be blank. Business Rule Impacts: The following table depicts LSOG 5/LSOG 6 Business Rule changes associated with this initiative. Action:
Form or Transaction
Field Number Header Section Valid Entry Section
New AV R 013a/013a Field Name: CAII – Concatenated Address Information Identifier Length: 20 Characteristics: A Usage: Conditional Field Level Indicator: Verizon Specific
The valid entries will be: Street Address City Zip Validation Note: 1. The Street Address label applies to SAPR, SANO, SASF, SASD, SASN, SATH, and SASS.
New AV R 014a/014a Field Name: PAV - Partial Address Validation Field Length: 200 Characteristics: A/N Usage: Conditional Field Level Indicator: Verizon Specific
Edit Impacts: The following table depicts the Response Codes associated with this request. Action: Response
Code: Response Description: Notes:
New 710 Additional LDn / LVn values may be valid at this address. If more than 50 alternate addresses are valid, the response code will be returned.
FINAL DOCUMENT Release Date – June 13, 2005
Page 29
C04-1089/388839 - Flow Through: Modify Edits to allow Wholesale request when the BTN has been previously ported on accounts with subordinate telephone numbers still retail Type: 4 Description: Modify edits to allow EB/MB/BB ACT=V to review retail subordinate telephone numbers for conversions. Details: Currently the edit reviews to see if the BTN is ported out. This initiative will include the review of retail subordinate telephone numbers for port out information. Business Rule Impacts: None Edit Impacts: The following table depicts the Standardized Manual edit changes associated with this change request:
Action: Add / Change / Delete
LSOG Version 5
LSOG Version 6
Form Section Field LSOG 5 Error Code
LSOG 6 Error Code
New Error Message
New LSOG5 LSOG6 LSR Admin ATN E05FLDH99816 E06FLDH99816 LSR ACTIVITY INVALID, TN IS PORTED
New LSOG5 LSOG6 LSR Admin ATN E05FLDH99817 E06FLDH99817 LSR ACTIVITY INVALID, TN IS PORTED
New LSOG5 LSOG6 LSR Admin ATN E05FLDH99818 E06FLDH99818 LSR ACTIVITY INVALID, TN IS PORTED
New LSOG5 LSOG6 RS Service Detail
TNS E05FLDH99819 E06FLDH99819 LSR ACTIVITY INVALID, TN IS PORTED
New LSOG5 LSOG6 PS Service Detail
TNS E05FLDH99820 E06FLDH99820 LSR ACTIVITY INVALID, TN IS PORTED
New LSOG5 LSOG6 LSNP Service Detail
PORTED NBR
E05FLDH99821 E06FLDH99821 LSR ACTIVITY INVALID, TN IS PORTED
FINAL DOCUMENT Release Date – June 13, 2005
Page 30
NON-CLEC SYSTEM IMPACTING: C03-0986/383486 - Flow Through: Outside Plant Charge for OH Description: Ohio requires an additional NRC per the tariff. Details: When a Premise Visit is required in the state of Ohio, an additional NRC IOSC 74667 will automatically be added to the service order. There is no need for the CLEC to add the IOSC on the LSR. Business Rule Impacts: None Edit Impacts: None
FINAL DOCUMENT Release Date – June 13, 2005
Page 31
C04-0874/388229 - Flow Through to Automate all Pending orders Description: This initiative will remove the process that returns all Pending Orders to NMC. Details: This initiative will remove logic in Flow Through that routes a pending order back to the NMC for verification. Pending Orders will be processed like normal LSRs. This initiative will work in conjunction with C04-0896/388292. This will involve about 4,000 orders per month. Business Rule Impacts: None Edit Impacts: None
FINAL DOCUMENT Release Date – June 13, 2005
Page 32
C04-1727/390287 - RFIC/BFIC Auto Completion Description: Completion of RFIC/BFIC Directory listing orders has been a manual process. Details: Flow Through will be updated to disconnect old fictitious listing accounts when it receives a new request for the same TN. Verizon’s system will be modified to identify and verify that provisioning order(s) for the same account are complete before completing the new fictitious listing order. Business Rule Impacts: None Edit Impacts: None