Wholesale: Products & Services

Archived System CR SCR102505-02 Detail

1. Please confirm when DACT is required – if it is only required when populate the DDA address fields are populated (DDASN is the key address field then DACT & DELNUM are populated)

ans: 1. Correct. DACT is only required when the user is establishing, changing or removing the Delivery address.

2. Please confirm when CLEC should send DDA field – only when not the same as service address

ans: 2. Correct. Only when the end user has requested that their phone book be delivered to an address different from their Service Address. Otherwise, the DA fields should be left blank.

3. Is it possible to have DACT = Z and have the DDA address fields null

ans: 3. NO

4. The response to question on DDQTY is answered in Question #119 - DDQTY can be populated with DACT = null (I e DACT related to the DDA fields and DELNUM)

ans: 4. Correct.

Based on the following responses we can summarize that DDA fields are required only when requesting that the Delivery Address for directories is different than the Service Address. The DACT is populated only when the Delivery Address fields are populated with a new Delivery Address, Changed Delivery Address or a Deleted Delivery Address. Based on this relationship it is possible to have edits for DACT based on the condition that DDASN (or another Key DDA field) is populated and the value for DACT can also be based on the Listing Activity (LACT) of the Main Listing (LML).

The concern addressed in this Change Request is that DACT edits should NOT be based on the population of the DDQTY field as currently stated in the IMA rules. DDQTY indicates the number of instances of Directory Delivery Address records and can be populated based on setting the DIRQTYA and/or DIRQTYNC book quantities equal to zero (0). Thus DDQTY can = 1 and the DDA fields can be null as they are the same as the Service Address fields and DACT should not be populated

Expected Deliverables/Proposed Implementation Date (if applicable):

Propose that the following covers the rule requirements without causing a CLEC to enter DDA fields with the DACT = Z when the Delivery Address is equivalent to the Service Address and thus are not normally required because the customer request a zero book quantity.

Under the DACT field – replace DDQTY condition with key DDA field tag – here using the DDASN for

Products 1, 3, 4, 7, 8, 9, 9a, 10, 11, 12, 13, 14, 16, 17, 18, 20, 21, 25, 28, 29, 30, 31, 33, 34, 35, 37, 38, 39, 40, 41, 42:

If LACT = N and DDASN not = null then DACT must = N

If LACT = D and DDASN not = null then DACT must = D

If LACT = I and DDASN not = null then DACT must = I or Z

If LACT = O and DDASN not = null then DACT must = O or Z

If LACT = Z and DDASN not = null then DACT must = D, N, or Z

Under the DDQTY field for all Products listed except Product 14

Added rule DDQTY = 1 is required if either (DACT not = null) or (DIRQTYNC or DIRQTYA = 0)

Status History

Project Meetings

Hi, I'm ok to close all 20.0 CRs except SCR121305-01 Implement XML Interface for IMA EDI. I would like for this to remain in CLEC test until we have some users actually in production on this. At this time there is no one in production yet. So we can not really say how its going or say we have given it a fair test.

Thanks

Steph

Stephanie Prull EDI Business Analyst Eschelon Telecom, INC Voice - 612-436-6058 Fax - 612-436-6158 Email - saprull@eschelon.com Web - www.eschelon.com

11/15/06 Systems CMP Meeting

Mark Coyne-Qwest stated that this CR deployed on October 16, 2006 with the IMA 20.0 release and asked if this CR could be closed. Bonnie Johnson-Eschelon stated that she would like to check with Steph Prull (Eschelon) before closing this CR. She said that she would send an e-mail to the CMP CR mailbox if the CR could be closed.

10/18/06 Systems CMP Meeting

Susan Lorence-Qwest stated that this CR deployed on October 16, 2006 with the IMA 20.0 release and will remain in CLEC Test.

9/20/06 Systems CMP Meeting

Mark Coyne-Qwest stated that this CR will deploy in the IMA 20.0 release on 10/16/06.

5/17/06 Systems CMP Meeting

IMA and SATE 20.0 Release - Packaging and Commitment Jill Martain - Qwest reviewed the IMA Release 20.0 Packaging and Commitment documents. She said that Item #2 – SCR021904-02 Suppression of Jeopardy Status Updates will be withdrawn. Jill said that the following CRs will be included in the IMA 20.0 Release scheduled in October: SCR010705-01 - Directory Listing Changes in Conjunction with LNP SCR042704-01 - FBDL PON Field SCR102505-02 - Edits for the LSR Delivery Address Activity (DACT) SCR032202-1 - Download capability for all applications of the post order status tool

5/10/06 Clarification Meeting

Attendees: Rosalin Davis - Verizon Business, Jane Torrens - Verizon Business, Lee Gomez - Qwest, Anders Ingemarson - Qwest, Carol McKenzie - Qwest, Sonja Reis, Lynn Stecklein - Qwest, Anne Robberson - Qwest

Lee Gomez - Qwest reviewed the rules and changes that will take place with the deployment of this request.

- DDQTY is required when any field in the Delivery Address/Info Section is populated and Delivery Address information is only required when it is different from the Service Address. - If DACT = N or D then DEL NUM must = 1 - If DACT = O/I then DEL NUM must = 1 for DACT = O and 2 for DACT = 1 - DACT - When changing the Delivery Address or the Delivery Address/DIRQTYA/DIRQTRNC fields, two Delivery Address/Info Sections are required, one with DACT = O (old data) and one with DACT = I (new data) If DDQTY = 2 then the DACT must be O and I - DACT is only for RTY = LML - DDASF - Only valida if DDANO is present. This field is optional, however if this field is populated it will be validated against valid values. - DDASD - This field is optional, however if this field is popilated it will be validated against valid values. - DDASN - Required when DDQTY = 2 and DIRQTA/DIRQTY fields are no 0 - DDASS - This field is optional, however if this field is populated it will be validated against valid values. - DDQTYA - Populated if customer does not want any phone books delivered. If DIRQTYA = 0 (zero) then DIRQTYNC must = 0. Required when DDQTY = 1 or 2 and DDASN is blank. - DIRQTYNC - Populated if customer does not want any phone books delivered. If DIRQTY = 0 (zero) then DIRQTYNC must = 0. Required when DDQTY = 1 or 2 and DDASN is blank.

5/5/06 E-mail from Verizon Business

Jane Torrens - Verizon Business stated that this request is not Product specific.

The bottom line is that you cannot request a zero book quantity on a move order

The LML has a LACT = I/O pair and the only valid DACT = I or Z

DACT = Z get dropped and is ignored

DACT = I is invalid for book change - can only do DACT = N or D on the books

5/4/06 Clarification Meeting

Attendees: Jane Torrens - Verizon Business, Rosalin Davis - Verizon Business, Lee Gomez - Qwest, Anders Ingemarson - Qwest, Lynn Stecklein - Qwest

Lynn Stecklein - Qwest stated that the purpose of this call was to further clarify and discuss a potential solution.

Lee Gomez - Qwest stated that the DL DACT and the Listing ACT

Jane Torrens - Verizon Business stated that her understanding is that the DDA should be used when the end user has requested that their phone book be delivered to an address different from their service address. She said that otherwise the field should be left blank and that DACT is only required when the user is establishing, changing or removing the Delivery Address.

Lee Gomez - Qwest stated that the EDI translator requires that any time the DIR Qty field is populated the DDA is required. She said that the DelNum triggers the update process.

Jane Torrens - Verizon Business stated that the bottom line is that you cannot request a zero book quantity on a move order. She said that the LML has a LACT = I/O pair and the only valid DACT = I or Z, DACT = Z get dropped and is ignored, DACT = I is invalid for book change – can only do DACT = N or D on the books.

Lee Gomez - Qwest stated that the Del Act is tied to all fields in the Section and said that anytime a field is changed the ACT is required.

Jane Torrens - Verizon Business stated that the ACT is not related to the DACT.

Lee Gomez - Qwest stated that the description is misleading and is not specific to the address.

Jane Torrens - Verizon Business stated that if you have something in the field, you need a value.

Lee Gomez- Qwest said that for a residential customer requesting that no phone books be delivered you take out 0 and that the logic is based on the end state

Jane Torrens - Verizon Business provided the following example:

It would happen on any inward order where it is possible to include Directory Delivery address and Book quantity information

Directory Only, UNE-P, LNP and LNP with Loop (Products 13, 14, 25, 5 and 7) are the products used by Verizon Business where we are not easily able to code the logic for no change in Directory delivery address but a request for Book Quantity = zero (0). The basic test case scenario is customer requests that books are sent to service address (which means no separate directory delivery address) and customer requests that Zero books be sent

The UNE-P test case where the work around suggested by Qwest is to send DACT = Z and is what we do in all production code to pass edits.

Customer Moves and changes LML requesting that Book Quantity = 0 and the Service address = Directory Delivery address.

Current logic does for DL section

PO1 loop 1, LACT = 1, RTY = LML, DDQTY = 1 PO1 loop 2, LACT = 0, RTY = LML, DDQTY = null PO1 Loop 3, DACT = Z, DIRQTYA = 0

This works as the rule states that if LACT = I and DDQTY = 1 then DACT must be I or Z.

Lee Gomez - Qwest stated that we may have to include an EDI person in these discussions. She said that she now had a better understanding of what this CR is requesting, Lee asked if Verizon Business could provide examples of the orders that they cannot get worked because of the business rules

Lynn Stecklein - Qwest stated that Qwest would regroup interally and schedule another meeting with Verizon Business.

5/5/06 E-mail from Verizon Business

The bottom line is that you cannot request a zero book quantity on a move order

The LML has a LACT = I/O pair and the only valid DACT = I or Z

DACT = Z get dropped and is ignored

DACT = I is invalid for book change - can only do DACT = N or D on the books

--Original Message-- From: Rosalin Davis [mailto:rosalin.davis@mci.com] Sent: Monday, May 08, 2006 2:25 PM To: 'Stecklein, Lynn' Cc: 'Jane Torrens' Subject: RE: Call to discuss SCR102505-02 Edits for the LSR DACT field

Lynn,

Because we end up sending the directory we do not have any examples. Jane suggests Qwest place a test order from their side and try to do a move without a change in DDA and request zero books in the quantity field.

-

From: Stecklein, Lynn [mailto:Lynn.Stecklein@qwest.com] Sent: Monday, May 08, 2006 11:07 AM To: Rosalin Davis Cc: Jane Torrens Subject: RE: Call to discuss SCR102505-02 Edits for the LSR DACT field

Hi Rosalin,

Thanks for the information. Would you happen to have examples ofLSR IDs that have been rejected or created errors?

Thanks,

Lynn Stecklein

Qwest Wholesale CRPM

303 382-5770

-

From: Rosalin Davis [mailto:rosalin.davis@verizonbusiness.com] Sent: Friday, May 05, 2006 11:18 AM To: Stecklein, Lynn Cc: 'Jane Torrens' Subject: FW: Call to discuss SCR102505-02 Edits for the LSR DACT field Importance: High

Lynn,

Below is Jane's response.

-

From: Jane Torrens [mailto:jane.torrens@mci.com] Sent: Friday, May 05, 2006 11:00 AM To: 'Rosalin Davis' Subject: RE: Call to discuss SCR102505-02 Edits for the LSR DACT field Importance: High

The issue is unrelated to product

It would happen on any inward order where it is possible to include Directory Delivery address and Book quantity information

Directory Only, UNE-P, LNP and LNP with Loop (Products 13, 14, 25, 5 and 7) are the products used by Verizon Business where we are not easily able to code the logic for no change in Directory delivery address but a request for Book Quantity = zero (0). The basic test case scenario is customer requests that books are sent to service address (which means no separate directory delivery address) and customer requests that Zero books be sent

The UNE-P test case where the work around suggested by Qwest is to send DACT = Z and is what we do in all production code to pass edits

Customer Moves and changes LML requesting that Book Quantity = 0 and the Service address = Directory Delivery address

Current logic does for DL section

PO1 loop 1

LACT = I

RTY = LML

DDQTY = 1

PO1 Loop 2

LACT = O

RTY = LML

DDQTY = null

PO1 Loop 3

DACT = Z

DIRQTYA = 0

DIRQTYNC = 0 This works as the rule states that if LACT = I and DDQTY = 1 then DACT must be I or Z

But according to Lee then the information on book quantities is ignored and the customer receives a book

My thought is that this logic is not correct and that DACT should only be tired to the Directory Delivery fields and never to the books

In the case above it is impossible to enter the DACT = I as would NEVER have DACT = I and O pair as related to a book quantity change – only valid entries are N and D as related to the books.

But in the case where the customer is changing the Delivery Address then the DACT = I / O pair is required to show the change even though you can NEVER show the Book change – could be noted with the DACT = I but never with the O so it becomes unrelated to the DACT field value and it is illogical to force the relationship.

--Original Message-- From: Rosalin Davis [mailto:rosalin.davis@mci.com] Sent: Friday, May 05, 2006 11:30 AM To: 'Jane Torrens' Subject: FW: Call to discuss SCR102505-02 Edits for the LSR DACT field

Jane,

Can you please send a couple of examples to Lynn at Qwest. Just use the test cases, if you have to.

- From: Stecklein, Lynn [mailto:Lynn.Stecklein@qwest.com] Sent: Friday, May 05, 2006 8:22 AM To: Rosalin Davis Subject: FW: Call to discuss SCR102505-02 Edits for the LSR DACT field

Hi Rosalin,

Can you send a couple of examples of orders that you cannot get worked because of the business rules around DACT?

Also, does this include FBDL?

Thanks, Lynn Stecklein

Qwest Wholesale CRPM

303 382-5770

12/14/05 December Systems CMP Meeting

Jill Martain/Qwest stated that the LOE for this CR is 400 to 665 hours.

11/16/05 November Systems CMP Meeting

Rosalin Davis/MCI presented the information contained in the CR. Jill Martain/Qwest said that this CR will move to a Presented Status.

11/2/05 Clarification Meeting

Attendees: Jane Torrens - MCI, Rosalin Davis - MCI, Chad Warner - Qwest, Kim Isaacs - Eschelon, Lynn Hankins - Covad, Steve Kast - Qwest, Cim Chambers - Qwest, Carol Mckenzie - Qwest, Chuck Anderson - Qwest, Jamal Boudhaouia - Qwest, Anne Robberson - Qwest, Lynn Stecklein - Qwest

Review Description of Change Lynn Stecklein - Qwest stated that MCI submitted questions to the Q&A log and received responses that prompted them to submit this CR.

Discussion

Jane Torrens - MCI reviewed the questions and responses that were submitted to the Qwest IMA EDI 16.0 as follows:

1. Please confirm when DACT is required - if it is only required when populate the DDA address fields are populated (DDASN is the key address field then DACT & DELNUM are populated) ans: 1. Correct. DACT is only required when the user is establishing, changing or removing the Delivery address.

2. Please confirm when CLEC should send DDA field only when not the same as service address ans: 2. Correct. Only when the end user has requested that their phone book be delivered to an address different from their Service Address. Otherwise, the DA fields should be left blank.

3. Is it possible to have DACT = Z and have the DDA address fields null ans: 3. NO 4. The response to question on DDQTY is answered in Question #119 - DDQTY can be populated with DACT = null (I e DACT related to the DDA fields and DELNUM) ans: 4. Correct.

Jane also said based on the following responses we can summarize that DDA fields are required only when requesting that the Delivery Address for directories is different than the Service Address. She said that the DACT is populated only when the Delivery Address fields are populated with a new Delivery Address, Changed Delivery Address or a Deleted Delivery Address. Jane said that based on this relationship it is possible to have edits for DACT based on the condition that DDASN (or another Key DDA field) is populated and the value for DACT can also be based on the Listing Activity (LACT) of the Main Listing (LML). The concern addressed in this Change Request is that DACT edits should NOT be based on the population of the DDQTY field as currently stated in the IMA rules. DDQTY indicates the number of instances of Directory Delivery Address records and can be populated based on setting the DIRQTYA and/or DIRQTYNC book quantities equal to zero (0). Thus DDQTY can = 1 and the DDA fields can be null as they are the same as the Service Address fields and DACT should not be populated

Jane said that MCI is proposing that the following covers the rule requirements without causing a CLEC to enter DDA fields with the DACT = Z when the Delivery Address is equivalent to the Service Address and thus are not normally required because the customer request a zero book quantity:

Under the DACT field – replace DDQTY condition with key DDA field tag – here using the DDASN for Products 1, 3, 4, 7, 8, 9, 9a, 10, 11, 12, 13, 14, 16, 17, 18, 20, 21, 25, 28, 29, 30, 31, 33, 34, 35, 37, 38, 39, 40, 41, 42: If LACT = N and DDASN not = null then DACT must = N If LACT = D and DDASN not = null then DACT must = D If LACT = I and DDASN not = null then DACT must = I or Z If LACT = O and DDASN not = null then DACT must = O or Z If LACT = Z and DDASN not = null then DACT must = D, N, or Z

Under the DDQTY field for all Products listed except Product 14 Added rule DDQTY = 1 is required if either (DACT not = null) or (DIRQTYNC or DIRQTYA = 0)

There were no other questions and Qwest stated that they understood the CR.

Products Impacted Lynn Stecklein - Qwest verified the products impacted noted on the CR - Resale, Loop, UNE-P. Jane Torrens - MCI stated that any product that has a Directory delivery address.

Establish Action Plan Lynn Stecklein - Qwest stated that MCI will be presenting this change request in the November CMP Meeting. Rosalin Davis - MCI stated that she will be presenting this CR.

CenturyLink Response

December 6, 2005

RE: SCR102505-02 Edits for the LSR Deliver Address Activity (DACT) field

Qwest has reviewed the information submitted as part of Change Request (SCR102505-02). Based upon the scope of this CR as agreed to in the Clarification Meeting (held November 2, 2005) Qwest is able to provide an estimated Level of Effort (LOE) of 400to 600 hours for this IMA Change Request.

This Change Request is an eligible candidate for the IMA 20.0 prioritization vote.

Sincerely, Qwest