OSS Interface Change Management Meeting May 13, 2003 - Verizon

OSS Interface Change Management Meeting 

May 13, 2003 

10:00 AM – 12:00 PM 

1095 Avenue of the Americas, New York, NY – Fl/Rm. 26-36 

Dial-In: (312) 461-9457 

Agenda 

I) Welcome and Introductions – Tom Rodgers 

II) Special Projects (10:00 – 10:20) 

PA/VA Uniformity - (Kim Brown and Ed Amato) 

III) Departmental Discussion (10:20 – 11:00) 

WCCC - (Patricia Pungitore) 

Billing - (Kathleen Conroy) 

Website Enhancements – (Linda Senne) 

Provider Notification - (Maryellen Langstine) 

IV) CMP Issues (11:00 – Noon) 

Status CMP Open Issues 

New CMP Issues and Discussion 

- End User level listing (CR# 2397) – (Susan Pistacchio) 

- Pending Order Error Message(CR# 2500) – Tom Rodgers 

- LSOG7 – Tom Rodgers 

Lunch Noon – 1:00 P.M 

V) Change Control Items By Release – (1:00 – 1:30) 

VI) Verizon Initiated Change Requests– (1:30 – 2:00) 

C03-0723: Add Trouble Ticket/PON to BDT 

C03-0571: Retas Screen Enhancement 

VII) CLEC Initiated Change Requests 

2889: Change their bill format to include the CKL information for analog loops on UNE-L 

bills on the CSRs 

2811: ALI Code Spreadsheet Upgrade 

2815: AOS Form for CLEC to CLEC Migrations

May 2003 

Topic # Description Date Discussion 

51 Wholesale Customer 

Care Center/ formerly 

Bell Atlantic Help Desk 

May 2003 East CMP Revisions Dated April 30, 2003 

1 


2/08/00 - Bell Atlantic told the CLECs the Help Desk Hours of Operation. 

- BA to have the handbook updated with the correct hours of the Help Desk. These hours are EST. 

- BA explained that out of hours, you can actually page somebody, and they will get back to you. CLECs took an 

action item to check with their organizations and see it the response is satisfactory when the BA Help Desk gets 

paged. 

- CLECs asked to have a workshop to review the Help Desk Processes, and to make sure that it is working for 

everyone. 

- BA to send out a note with logistics for a meeting and solicit agenda topics in writing from the industry. 

- CLECs asked for BA to clarify the 6 help desks. 

- MCI wants to see a Help Desk recovery plan. 

3/7/00 - BA recommends closing. BA held a Help Desk meeting on 3/7/00. BA will continue to hold workshops on a 

monthly basis. Next Help Desk meeting is scheduled for 3/21/00. 

3/14/00 - CLECs request this item remain open. 

- BA believes 3/21 meeting may be postponed. 

4/11/00 - Help Desk meeting is scheduled for 4/14/00 

- Meeting materials will be sent to CLEC’s prior to meeting 

5/9/00 - Status from Help Desk workshop to be addressed before next meeting 

- One of the most sought after issues was the number of past date due PON type tickets, backlog and clean-up 

resolution. A process is now in place. 

- If a CLEC has a question about a pending ticket, they should call the Help Desk. Once it is identified, it will be 

given to a particular person decreasing the turnaround time 

- A new workshop will be scheduled 

6/13/00 - CLECs wanted to know when the next Help Desk meeting will be held. 

- BA to schedule another workshop 

7/11/00 - BA advised CLECs of the upcoming workshop and conference calls scheduled 

- Future workshops are planned for: 

- July 18, 2000 (on site) 

- July 21, 2000 – August 7, 2000 - August 14, 2000 – August 21, 2000 

- Mettel asked when will the Help Desk have only one number as promised 

08/08/00 - This topic being discussed at weekly help desk calls, see schedule above. 

09/12/00 - CLECs have concerns regarding some type of service level agreement with the help desk. They would like to 

start up talks to get some type of agreement in place. Another request was to have the architecture that is used 

for order and pre-order documented so that when the CLEC discusses a problem with the help desk, there is a 

clear understanding of where the problem may be and what is being done to fix it.


2 




10/10/00 - Bernie Bolinski presented an update regarding the help desk. 

- The speed at which the calls are answered is running at approximately 80 to 85% answered within 20 seconds. 

Overall, status back to the customer is happening within 2 or 3 days. 

- Verizon advised that a customer advocate group will be started soon. This group will focus on tracking 

pending reports and responding to escalations. This group will also work with customers and internal groups to 

facilitate timely ticket resolution. 

- Bernie is also getting an analysis group underway. Their responsibility will be to identify process 

improvements and track historical trends. 

- Tivoli is a reporting system that is being rolled out to internal work groups so that everyone is on the same 

ticketing system, which will lead to easier tracking of tickets. 

- CLECs requested that there be bi-weekly calls with Bernie and Help Desk personnel to discuss overall process 

issues. Bernie agreed, and the first call was set up for 10/26. 

11/14/00 - CLECs would like documentation on the Help Desk process – they are confused as to where they should call 

for what items. 

- Documentation should say what the Help Desk turn-around times are. RCN asked for a Help Desk process 

flow to help discern where to go with GUI issues. 

- CLECs would like weekly meetings with the Help Desk as originally planned at the last Change Control 

meeting. A date was set, however the meeting did not take place. BA advised that when a firm meeting is 

planned, the CLEC community would be notified. BA to speak with Help Desk personnel for further status 

12/12/00 - CLEC want an overview of the new processes and changes occurring at the HelpDesk. Verizon will look into 

scheduling a date in January. CLECs would also like to discuss mechanized tracking of trouble tickets 

- CLECs would like clear definition on turnaround time of trouble tickets from the Help Desk 

- CLECs were unhappy about the systems being down and not reported to the industry. Concern was also raised 

over the pager notification process of when the system goes down and when it is brought back up 

- CLECs would like possible causes of outages included in the down or slow response message sent to the 

industry 

- CLECs would like the contact list updated on the Web. HelpDesk (T. Thirsk) will work to get the list current 

1/9/01 - CLECs were given details on the involvement of Managers in the process of tracking trouble tickets. The 

process is expected to be in place within 2 months 

- BA advised that a smaller group would be handling calls and turning trouble tickets over to the Managers 

- CLECs wanted to know when an overview of the new process would be discussed. Discussions will take place 

as soon as it is finalized. 

- CLECs asked if they could have a profile for their company readily available when reporting troubles which 

would streamline the entire process. BA will take a look into those address identifiers, but did advise the 

process may need to remain internal needs


3 




2/13/01 - CLEC questioned VZ about of issue regarding billing trouble ticket policy. VZ will check into this issue 

further. 

- CLEC (Dressler) informed VZ that when dealing with a GUI (system) issue, the WCCC will not create a 

trouble ticket until it is first reported to the GUI HelpDesk. 

- Another issue with the HelpDesk is a trouble ticket will not be opened unless there is a sign-on ID. CLECs do 

not feel they should have an ID for each individual representative. VZ to explore both of the above issues 

3/13/01 - CLECs advised of the problems they are experiencing getting CSRs over the past two to three weeks. After 

speaking with an Acct Mgr, it was determined that VZ is aware of the situation and it has been escalated. 

- CLECs would like status on when the problem would be fixed. They are getting an error message that says the 

query cannot be responded to at this time. Trouble tickets have been submitted to the WCCC 

- CLECs are also concerned about how quickly the HelpDesk responds to trouble ticket 

- VZ to work with HelpDesk team on response turnaround time on trouble tickets 

- CLECs would like representation from the HelpDesk at next ICC meeting 

- Another CLEC concern is turnaround timeframes for EDI issues. It appears that it is taking a long time to 

resolve 

- VZ to explore 

4/10/01 - VZ (Pat) will be covering this topic going forward. Her role as a manager is handling escalations, billing and 

various off-line functions. She is actively involved in the call center 

- CLECs (Worldcom) uneasy about the escalation process regarding billing issues. The concern is the 

appearance of an internal timeframe at VZ that is not relative to the Website. VZ (Pat) advised that she is 

actively working on getting the turnaround time on billing issues reduced. CLECs are finding that some billing 

issues take up to 45 days to resolve. CLECs would like to know what VZs personnel is trained to inform 

CLECs regarding billing issues. VZ (Pat) will explore further. 

- CLECs voiced concern about issues they are experiencing when reporting problems to VZ and are connecting 

to the VZ firewall. VZ is therefore not sending out proper or accurate notification. VZ will take this issue back 

as an action item. 

- CLECs questioned system outages and would like to know what is the process whereby an issue is reported to 

VZ and when does it physically begin as a problem for the CLECs. CLECs are actually experiencing a longer 

delay than what is reported. VZ (Dave/WCCC) advised that those discrepancies should be called into a 1st 

Level Manager (Specialist) to address. 

5/8/01 - VZ probed CLECs for HelpDesk concerns. One issue related to agents opening trouble tickets and transmitting 

a change order. Attempts were made to leave a message with the HelpDesk, however a response was never 

received. VZ to do further exploration 

- CLECs question HelpDesk contact information on the Website. VZ advised and provided the correct Web 

address that should be accessed for Verizon East HelpDesk contact data


4 




6/12/01 - CLECs questioned trouble tickets regarding submitting orders via EDI - LSOG4 with AHN. VZ will research 

for more details to bring about resolution 

- CLECs concerned about the amount of time it takes to resolve trouble tickets before escalation proceedings are 

warranted. Also raised was the back and forth motion between the Tisoc, HelpDesk and Account Managers. 

VZ to explore 

- CLECs would like an overview of the HelpDesk process. VZ to comply 

- Other CLEC concerns include the TISOC not being able to see an order before it gets rejected automatically in 

the GUI, the GUI HelpDesk and the HelpDesks reluctance to give information without having the CLECs ID, 

and the CLECs would like VZs reps to have the ability to print an order and fax it to them for quicker 

resolution 

7/10/01 - VZ reported that there are several questions still outstanding from the WCCC presentation on 6/27 and we are 

working diligently on getting responses to those questions 

- CLEC, Connective is concerned about a problem they are having with their audit which shows they are still be 

billed by VZ when a customer has been disconnected. VZ advised those CLECs experiencing this problem 

should open a trouble ticket for further investigation. 

- Some CLECs have opened a trouble ticket regarding JEP codes they receive and have no way to differentiate a 

good confirmation vs a confirmation that has a jeopardy. VZ to explore 

8/14/01 - VZ, (WCCC) will be working with individual CLECs on an ongoing basis for system cleanups. The WCCC 

will send CLECs a template and they will be required to fill out and send back to VZ. VZ will then work 

internally to either send a notifier back to the CLEC or will take the appropriate action to move or fix the 

PCN/BCN. If its found on VZs end, we will then notify the CLEC via daily updates. 

- VZ advised that the WCCC will automatically open a trouble ticket and will send the CLEC a template. Once 

the template is received, going forward; we will send a template out automatically just in case there is a CLEC 

calling in for the first time and does not have one. If any CLEC already have a template, they do not have to 

wait to receive one. The CLEC can pre-populate the template and fill in the ticket number once given. 

- CLECs request the template be sent to all CLECs via BA Change Control 

09/20/01 - CLECs concerned about long delays in getting trouble tickets responded to. They wanted to know the time 

intervals associated with trouble tickets reported to VZ. VZ stated that documentation states once a ticket is 

reported, VZ will respond within 1 business day to let the CLEC know who the ticket has been assigned to and 

their telephone number. As status is obtained, VZ would contact the CLEC who actually reported the ticket. 

CLECs have a different view of the current process and believe that it is currently not working 

- VZ did advise that we are looking into ways to shorten this turnaround time. A time log of trouble tickets is 

now in place and VZ will continue to look at ways of improvement


5 




10/09/01 - CLEC (Cox) reported that they tried to get through to the WCCC to report trouble tickets and received a 

recording that the mailbox was full. CLECs wanted to know what should they do if that occurs again. VZ 

responded to either call P. Pungitore (VZ) directly or contact their Account Managers. VZ will make a note of 

the date and time this occurred and will review 

- CLECs report problems with opening trouble tickets and questioned trouble ticket turnaround response time. 

VZ advised that the agreement states that once a ticket is opened, VZ will respond within one business day to 

advise who it was assigned to and their telephone number 

11/13/01 - VZ provided feedback to the CLECs regarding the issue of being able to reach the WCCCs voicemail. That 

concern was relayed to the center's manager, investigated and no issues were found. VZ would need the 

specific dates and times in order to explore further 

- CLECs expressed concern with some trouble tickets going through. VZ advised the CLECs to either call (617) 

743-2516 or go to the VZ east website for further instructions 

12/11/01 - CLECs questioned whether there was going to be a VE 10 field in the ICSD code in CSG for wholesale orders 

and if so, what would be the time frame. VZ (WCCC) responded stating that this question should be forwarded 

to the Business Rules group or to the appropriate Acct Manager. 

- CLEC (AT&T) requested that the IDO Pre -order specs be published in Word format along with the PDF 

version. VZ advised that we are publishing some of the documents in PDF and RTF. VZ to do further 

exploration 

01/08/02 - CLECs questioned content of data on the line loss report when a response comes back fro m the WCCC and 

who should they go to get enhancements to report to clarify what is listed on the report. CLECs would like a 

matrix that identifies all exceptions 

- VZ explained the process when a call is made to the WCCC Call Center. The CLECs would like to make a 

distinction between the HelpDesk, the Web GUI HelpDesk and the Call Center for trouble reports. VZ advised 

to contact Barry Kearns 

- VZ will also explore these CLECs concerns internally and will respond? 

02/12/02 - VZ told the CLECs that the WCCC document on the VZ website has been updated with the proper e-mail 

addresses and new management changes 

- CLECs question where are the Business Rules questions relative to upcoming releases. CLECs wanted to 

know whether they should be contacting the WCCC or CIRT group 

- VZ advised that all pre-production questions should be sent to BA Change Control whereby they would be 

referred to the Business Rules team for proper responses. VZ stated if a CLEC is testing and has testing 

questions, they should be referred to the testing coordinator 

3/12/02 - CLEC questioned if WCCC has a how-to help desk portion regarding using the CSR and the DLR function 

with Verizon. 

- VZ advised that the WCCC is not a help desk. It responds to issues concerning business rules when CLECs get 

errors. VZ advised that because they are a web-GUI user the CIRT Help Desk can offer help.


6 




4/09/02 - CLEC advised they are having trouble pulling CSRs. CLEC question if there could be a workaround to correct 

problem while waiting for the problem to be fixed in April. CLEC also provided trouble ticket. 

- VZ advised will check on trouble ticket provided and CLEC and will discuss further off line. 

5/14/02 - Per CLEC request VZ explained the difference between the WCCC and the CIRT group. 

- VZ advised that the WCCC handles software issues if it is inconsistent with the business rules. The CIRT group 

helps with the navigation and providing answers to questions pertaining to the business rules. So like if you are 

unsure of what to populate in what field they will assist you in that 

6/11/02 - No concerns were raised by CLECs 

7/9//02 - CLEC question the location of assignment for pre-validation, CLEC also question if the WCCC is involved in 

placing the metric reports on WISE, CLEC request this be discussed on the next call 

- VZ advised the concern regarding pre-validation was previously forwarded to the SME of VZ, VZ also advised 

that there has been no knowledge of WCCC being involved in posting the metric to WISE. 

8/13/02 - CLEC questioned the turnaround time for response to close tickets or acknowledgement when a ticked is 

submitted to the WCCC. CLEC raised question because after submitting a ticket to the WCC regarding 

problems accessing a CSR, the CLEC later attempted to access the CSR and was successful. However, there 

was no notification to the CLEC advising that the ticket was closed and that the issue was resolved. 

- VZ advised there is no set turn-around time for ticket close-out notification. 

9/10/02 - CLEC commented on problem that a lot of FOCs for unbundled loop orders are being sent back via EDI which 

is resulting in a lot of erroneous data coming back missing ore un-sequenced properly. CLECS also questioned 

if GUI users are also experiencing the same problem. 

- VZ advised there have been no issue reported by GUI users, however VZ have been working closely with 

CLECs who have reports in to resolve this issue. VZ explained that the issues with the NMC is that the reps are 

prematurely hitting the send/receive button, and that’s an issue within that organization. This is not system 

related. 

- CLECs commented that if there is an incomplete FOC, then there should be some sort of FOC SUP message 

sent by Verizon to fill in the missing data, and not a second FOC. CLECS feel that if representatives in the 

NMC are clicking buttons too soon for FOCS then this is an edit check that should be in the system. 

- VZ advised will take comment back to the NMC


7 




10/8/02 - CLEC AT&T advised they have been getting a lot of rejects in BAN, using the BAN batch that is provided by 

Verizon. CLEC questioned if the WCCC or the NMC should be helping with this problem or providing the 

correct BAN number? 

- VZ advised that the WCCC would be able to provide the trouble ticket and attempt to investigate but would not 

have this information. 

- CLEC AT&T also expressed concern that they are also receiving rejects because of the list of ALI codes being 

received from Verizon. 

- CLEC was advised that a trouble ticket should be opened for this problem. 

- CLEC Broadview advised that they have been experiencing problems on remote call forwarding service, 

whenever they attempt to snip or restore. Broadview advised that two trouble tickets were opened in April. 

Broadview advised that they have been told that this now requires business rules change. Initiative 374299, 

with a change request of 2434, is currently outstanding for this, Broadview advised that they have gone through 

the change control documentation, and do not see information regarding this. CLEC stated they would like 

additional information on this change. 

- VZ advised that this change is being escalated and hopefully will be implemented in April 2003. 

11/12/02 - ATT questioned why an initial application bulletin was distributed from the WCCC which mentioned the LSI. 

Approximately 2 hours later, the final application bulletin was distributed. This addressed the LSI issue, but 

also a CORBA issue. ATT questioned why the initial bulletin did not identify a problem with CORBA 

- VZ advised will investigate this issue. 

- Allegiance stated that they are still having trouble opening a trouble ticket on something that is an ordering 

issue. 

- VZ advised if CLECS receive a manual query, it should always go back to the NMC. VZ advised if CLECS 

receive a system query, and there seems to be no errors made after checking the business rules, there should be 

no problem opening a trouble ticket. If there is a problem opening the trouble ticket then manager, Tom 

Scanlon should be contacted.


8 




12/10/02 - CLECS questioned if escalation process should be followed if there seems to be no progress after a trouble 

ticket has been opened and they are following up with a Verizon contact. 

- VZ advised to first contact the specialist who is the point of contact then follow the documented escalation 

procedure. 

- CLECS expressed concern that there seems to be confusion pertaining to what VZ department whether the 

WCCC or CIRT should help with certain types of problems. The CLECS advised that recently there was a 

CSR which had a sender field which was blank. The CLECS were advised that a trouble ticket should be 

opened to handle the problem. The CLECS were then advised that this would be referred back to the NMC to 

be corrected. 

- VZ advised that if it’s a manual query this should be referred to the NMC. “How to” questions such as how to 

complete a LSR should be referred to CIRT. If it’s a system query then this should be referred to the WCCC. 

CLECS are advised to refer to the business rules to ensure that their orders are being imputed correctly before 

contacting these groups. 

4/11/00 - BA will be scheduling a workshop regarding this CR 

10/8/02 - VZ recommends closing this topic. No CLEC objections 

1/14/03 - Verizon proposes to treat topic as CMP agenda item. Verizon will status in CMP Meeting Notes. Move to 

CMP Archive to reduce volume of paper 

- CLEC expressed concerns about a published loss of functionality bulletin, regarding EDI ordering. CLECS 

stated that it would be helpful if, those bulletins are sent out, with a little bit more detail relative to the loss of 

functionality. 

- Verizon advised the group that created the bulletin will be contacted to determine what additional information 

could have been included.


9 




3/11/03 CLECs requested publication of the February 7, 2003 meeting notes and inclusion in CMP Action Items for April. 

Meeting notes distributed March 19,2003. 

- Verizon will verify the NMC can actually see all lines of CSI information that a CLEC can view on-line. 

Instances were cited that suggest the NMC could not view the same content. See Open Issue 79. 

- The CLEC community also recommended providing the NMC with access to LSI. The interaction with the 

NMC could be improved if both the NMC and CLEC were looking at the same LSR. See Open Issue 80. 

- CLECs are again encouraged to use WPTS to identify missing port indicators or omitted TNs. This tool should 

be used prior to the due date to identify omissions. 

- Verizon will republish where to find important pre-order information on-line. There were questions about how 

to look at the CSI prior to transmitting the LSR. See CMP Open Issue 81. 

- CLECs are experiencing excessive hold times into CIRT and WCCC. 

- There was a suggestion to expand the WCCC escalation list available on-line. The strong preference was to 

reduce the hold times and to avoid escalation. See CMP Open Issue 82. 

- There was a suggestion to expand the CIRT escalation list available on-line. The strong preference was to 

reduce the hold times and to avoid escalation. See CMP Open Issue 83. 

- In response to a system generated error message, there was a CLEC request to improve coordination between 

the WCCC and NMC and NMC and CIRT. CLECs will forward examples for evaluation where the referral to 

another center was inappropriate. 

- Realign the reporting relationship of the WCCC and CIRT into the NMC. This was proposed to improve 

communication between three centers by making them part of the same organization. 

- Inaccurate CSR information was problematic. Problems with service address or features caused unnecessary 

corrective service orders to be written. 

67 CLEC to CLEC Migration 3/14/00 - CLEC to CLEC migration is a difficult task. The CLEC’s expressed great concern with the sharing of a 

customers CSR between them. 

- BA to hold a workshop in the first week of April. 

4/11/00 - Several sessions are being held now on CLEC to CLEC migration within BA 

- Workshop scheduled for 5/16/00 

5/9/00 - Workshop was held on 5/16. Workshop covered moving an end-user customer from one CLEC to another 

CLEC’s requested Listings be discussed at the workshop 

- PSC attended the workshop as requested by the CLEC community 

- A workshop will be scheduled 

6/13/00 - A CLEC to CLEC workshop was held on 6/26/00 

10/8/02 - VZ recommends closing. CLEC recommends this topic remain open since NY State recently opened Phase 3 

of the CLEC to CLEC migration proceedings 

1/14/03 - Verizon requests closure or clarification of issue


10 




3/11/03 - CLEC community requests a recap or summary of all change requests associated with CLEC to CLEC 

conversion listed here. 

69 PONTRONICS 

The following Change Requests have either been completed or are pending that impact CLEC to 

Migrations. 

CR1143 - IT#365011 – Flow Through SUP 2 for change of date due, North and South, all services.- 

Completed 12/2002 

CR1187/1411-IT#360441 - Allow Level 5 Flow-Through on a Platform CLEC to CLEC migration- 

Completed 6/2000 

CR1863 - IT#366855 - Process CLEC to CLEC Migration As Is at Level 5 - Completed 2/2002 

CR2397.9 - IT#373105 - End User Level Listings Account - Phase 9- Candidate 4/2003 

CR2600 - IT#373630 - CLEC to CLEC Migrations – (Phase 1) - Committed 6/2003 

CR2600.1 - IT#373630.2 - CLEC to CLEC Migrations – Provider Notification (phase 2) - Committed 

6/2003 

CR2454 - IT#373630 - Type 5 - Enhance xDSL Migration-Requirements will be worked with 373630 

CR2625.9 - IT#377163.9 – Line share CTX FT VZ North- Not Scheduled 

CR2632 - IT#374752 - Hot Cuts for xDSL Loops - Candidate 10/2003 

6/13/00 - 

CR2815 - IT#380732 - AOS Form for CLEC to CLEC Migrations - Not Scheduled 

Mettel has submitted a Type 5 change requesting functionality that is similar to PONTRONICS. Mettel feels 

that the system they are proposing would be a better choice 

- Mettel would like a “phased” approach and easy availability to this system if implemented 

- AT&T would like BA Help Desk to have tools such as this to help limit trouble ticket turnaround time 

08/08/00 - BA will look into scheduling a meeting on PONTRONICS 

11/14/00 - CLECs would like a meeting to further discuss Pontronics with respect to a similar Change Request submitted 

by Mettel. 

- BA advised that when a meeting is scheduled, the CLEC community will be notified. 

10/8/02 - VZ awaiting resolution.



1/14/03 - CMP Team cross relating issue with pending T5 to identify next step 

70 Line Loss 6/30/00 – 2/11/03 

Provider Notification – 

2/11/03 Forward 


11 

2/11/03 - Verizon requests clarification of issue or closure. CLEC community object closure 


6/13/00 - BA provided information regarding Line Loss report issue status 

- The Line Loss Group is presently working on individual CLEC spreadsheets to resolve outstanding issues 

- BA advised the CLECs of the general delays experienced between the North and South 

- CLECs request this topic to become a permanent item the agenda 

- CLECs request a workshop on Line Loss. BA suggested a delay in that request to allow time on the resolution 

of issues. 

- BA will provide the CLECs with status of line loss at each monthly Industry Change Control meeting and once 

between meetings when feasible 

7/11/00 - BA continues to provide status and work with individual CLEC’s line loss issues 

- L. Ziccardi advised that she would work directly with those CLECs that had questions, but all troubles still 

require a ticket be opened for tracking purposes 

- MetroTeleconnect advised that they have experienced some inconsistencies in the line loss report display, 

Linda to work with them individually 

- BA has seen great improvement in the line loss reports since mid April. BA asked if CLECs noticed 

improvement. CLECs responded that they won't be able to answer until the normal lag-time passes 

- BA will check with TISOC to see if they would agree to field calls from CLECs regarding line lose dates 

08/08/00 - Linda Ziccardi reports that she has seen great improvement on the Line Loss reports from Mettel. 

09/12/00 - Linda Ziccardi reported on the status of line loss, and the fixes scheduled for Sept 29th. In the North and South 

there will be a fix to add the pulling of losses generated on both the local side This was not a significant 

number, but will increase accuracy. Also a fix is going in to care for a coding error in our system that if a 

customer was migrating from BA to a CLEC, and at the same time was disconnecting a ringmate line or an 

additional line on that service order, we were changing the account first to the new CLEC and then doing the 

disconnect, which meant we were sending out numbers to the line loss report of the old CLEC that never even 

had the line. Most of the issues that are currently coming up are issues that happened prior to our April fix. 

Also, on October 21 we are putting in a release so that the line loss can be reported by EDI. Mettel asked if the 

10 day delay between the time the account left an the time when the CLECs got the information has improved. 

Linda reported that now the delay in the North is only 5 days, and in the South is 2 days. In 1Q 2001 changes 

to the parser will bring the North time down to 2 days. 

10/10/00 - Linda Ziccardi joined the call to provide status on line loss issues. She reviewed items that were included in 

the previous release, and discussed plans for fixes to be included in future releases. 

- Linda took some issues and individual callback items from CLECs which she will follow up on offline. 

11/14/00 - CLECs had no issues to report. The line loss report in the CLEC handbook, volume 2 has been changed and is 

available on the web now.


12 




12/12/00 - CLECs were advised of a release going in at the end of January. This release will include the addition of NDM 

- Z-tel’s order issues will also be addressed with the January release 

- CLEC (AT&T) concerned about long-standing trouble tickets, Verizon explained the manual review process of 

their spreadsheet and will discuss further with AT&T and Acct Team Manager offline 

- Verizon requested this topic be removed from the agenda, CLECs objected and would like it to remain 

1/9/01 - BA updated CLECs of release scheduled for the end of January 2001. NDM will be going in the weekend of 

January 26. 

- CLECs directly affected by NDM should contact their Acct Team Managers for any questions 

- BA opened the floor to any questions from CLECs. There were no questions or comments from CLECs 

2/13/01 - VZ updated CLECs on issues that have been remedied since the last meeting. VZ informed the CLECs of 

incorrect effective dates shown on the line loss report which have since been recovered and corrected. 

- VZ again advised of the release that occurred at the end of January. A new problem was discovered with the 

release when an end user migrated to a new CLEC and changed the PIC or LPIC at the same time. This has 

since been corrected. A recovery from 1/28 to 2/10 is now being performed. 

- Some NDM processes were addressed with the January release with success reported from those affected 

CLECs 

- VZ advised that the next release is targeted for April 2001. Prioritization has not yet taken place 

3/13/01 - VZ advised that a recovery from 1/28 to 2/10 will be sent out by Excel spreadsheets by 3/30/2001 to only those 

CLECs impacted by errors in the effective dates shown on the LLR 

- VZ (Linda) gave an update on the Line Loss Report. An emergency release will be going in to make some 

fixes to the reports, but has not been scheduled. The fixes will include, but are not limited to: migrations on 

D&N orders, migrated ISDN lines, bus to residence changes, canceled orders and the like are targeted for this 

emergency release occurring in the spring 2001. Another release is currently scheduled for 4/6. The next 

release isn’t until the fall 

4/14/01 - VZ (Linda) share information regarding a release that occurred this past weekend. A fix was put in so that in 

the past we were picking up on the line loss report, disconnects that the CLECs had initiated. This will no 

longer be the case 

- VZ advised that effective Monday, the ninth, if the CLEC places a disconnect of a line, that number will no 

longer be on the line loss report 

- CLECs advised of another issue where segmented orders weren't always picking up the correct effective date. 

The release also addressed this issue also


13 




5/8/01 - VZ advised CLECs of a release planned for June 1st . Three changes/additions will be going in to correct some 

inaccuracies on the LLR for the South. If a CLEC changes the class of service on their own customers account 

from res to bus or from bus to res, it is then put on the LLR. VZ is working to correct this. Also in the South, 

VZ is addressing migration codes on partial migrations. When a MTN is going to a CLEC, any additional lines 

that are not—a D order must be issued for the one line that is remaining with either VZ or the CLEC and also 

for the lines that will migrating. VZ would like to give a true picture of which lines are just migrating and 

which lines are disconnecting. 

- Also for the South, if a customer is migrating one of their customers from resale to platform – and the CLEC 

isn't changing – it's still that CLECs customer. “If the OCN of the local service provider, or CLEC, is the 

same for resale and platform, that end user will not be on the line loss report. Since the local service provider 

that is making the change, they should know not to disconnect this customer because they're initiating the 

change for that WTN. If the OCN is the same in the south, if the OCN for the reseller and the platform for that 

local service provider is the same, there's doubt the telephone numbers will be on the line loss report.” 

- VZ advised of a third quarter release which will be scheduled for the North. Massive change will be made for 

the North so that things that currently occur in the South today will occur in the North and will sync up with 

data on the LLR consistently. 

6/12/01 - CLECs raised questions concerning a software problem/fix from June 3rd - 4th requesting the CLECs not to 

process data received the day prior regarding many files that appeared on the line loss report. Also, no notice 

was sent via BA Change Control. 

- CLECs would like to know what happened and what can be done to prevent this from happening in the future. 

- VZ to work with internal teams to investigate what actually occurred. Some CLECs stated that they opened a 

trouble ticket specifically relating to this issue 

- VZ will look into sending an industry mailing as notification. 

- VZ advised CLECs to always put in a trouble ticket which aids in tracking issues such as the above and major 

issues alike 

7/60/01 - VZ began by stating that there were no problems or issues with the Line Loss report-- 

- CLECs questioned double billing on the line loss report. VZ requested in which jurisdiction and was told PA 

and NY. VZ advised to put in a trouble ticket a provide examples of affected telephone numbers for further 

exploration 

- CLECs also questioned response time once a trouble ticket is opened. VZ advised that once a ticket is inputted, 

someone from VZ should be calling within 48 hours, two business days because it has been assigned 

8/14/01 - VZ stated that a recovery will be going in—in PA and NJ by the 19th of August for TN’s missing from the 

LLR. There is also another change request going in that same weekend to correct a timing issue between the 

receipt of an order and order migrations, which are causing problems with new LST indicator blanks on the 

LLR when it should have been; normally unbundled, but sometimes should be resale


14 




9/20/01 - VZ advised that there was nothing new to report on the LLR topic 

- CLECs informed VZ of some problems they are experiencing regarding incorrect indicators on the LLR. 

Trouble tickets have been opened, however no response has been received to date. VZ questioned whether it 

was for the new LSP indicator. CLEC responded, yes. VZ advised that a fix with the October release should 

correct that problem. A release is scheduled to take place from October 17th through the 19th 

10/9/01 - CLECs asked (VZ) to review which changes are going into the October release for Line Loss, particularly 

fixes. VZ questioned if there was something specific that they were looking for. CLECs responded yes. They 

wanted to know about some outstanding issues regarding disconnects being included on an LSP indicator and 

improving interval dates for the reporting of the numbers. VZ unsure and will follow-up. 

- VZ advised that a release will be occurring in December. Change Request 2023 with the WCCC will be 

included in this release. That Change Request will cover an LSP request to change from resale to platform 

when the end-user stays with the same LSP. That WTN will not appear on the LLR 

11/13/01 - CLECs questioned system ups and downs and duplications in what was shown on the line loss report. CLECs 

wanted to know whether there was a notification bulletin. VZ explained that there was no bulletin, however 

there was a recent holiday (election day) in NY and an upcoming holiday (veterans day) for NY as well. 

CLECs would like to be notified when the system is not going to be working or if there will be a system delay. 

- VZ suggests including line loss and system processing implications on the new holiday schedule for 2002. 

- CLECs questioned having a metric for line loss. This topic shall be talked about and explored further at future 

meetings 

- CLECs questioned the escalation process and trouble ticket turnaround time. VZ advised this information can 

be found on the VZ East website or by calling (617) 743-2516 or (617) 743-6523 

12/11/01 - CLECs questioned a line loss document sent on 12/7. VZ advised that an Informational message was 

distributed to the industry regarding replacement of some incorrect data on the LLR. On October 21st through 

October 27th, the LLR had some incorrect data and those files were replaced by close of business on 12/7 

- CLECs observed that there were a number of holidays forthcoming which effect system processing schedules. 

They would like advanced notice of the impact to these systems. The CLECs want to be informed when there 

is a change in system content or data flow for the LLR for holidays. CLEC concern is that sometimes when 

01/08/01 

there is a holiday, they do not see the impact to the LLR until a few days later. VZ will explore further 

- VZ advised of a recovery that took place in December on the LLR. The recovery was conducted between 

October 21st through 27th whereby files were replaced. CLECs state that they are still seeing trouble tickets 

from June August and October that VZ confirmed that the line loss notification never made through the normal 

channels. CLECs are worried that there are still system issues and are concerned that these recoveries are not 

capturing everything. VZ will speak with Barry Kearns and will respond.


15 




02/12/01 - Line loss SME was unable to attend this session 

- CLEC stated they were having some problems with line loss 

- VZ advised that the best way to handle would be to submit a trouble ticket through the WCCC and if 

satisfaction is not felt to escalate utilizing the escalation list 

- CLEC asked if the HelpDesk for future developments could have a recovery process in place 

- VZ advised that a recovery process is possible and will further explore 

73 Prioritization Process 

Documentation 

3/12/02 - VZ recommend closing 

12/10/02 - VZ advised that the Line Loss report would now be called Provider Notification with the February 2003 

release. VZ is making changes to the line loss production process. One of the issues is that there were several 

type 5’s submitted by CLECS that VZ wanted to resolve. In addition there are some differences in the North 

and the South. The aim is to bring more uniformity into the production process. 

- VZ advised that there would be no change to the fields or content of the line loss report. The purpose of the 

report also has not changed. 

- VZ advised that it was planned to have the transition ready earlier this year however there were some complex 

scenarios that needed to be worked and tested to ensure that the report being produced meets the required 

standard. There are 5 weekends that is scheduled in the month of January 2003 and February 2003 to ensure 

that the reports being received are being generated from the new process. 

- CLECS were advised that if they are receiving the report via FTP, EDI or Connect Direct, a schedule would be 

arranged with them. CLECS who are not currently participating in the call will be contacted to ensure that they 

are aware of the transition and that the time fits into their schedule. 

1/14/03 - Verizon requests closure. After February, any new issue would be a Provider Notification issue not a Line 

Loss issue Vz advised that conversion was a success. Conversion will continue as indicated on the previous 

calls, through the weekend of February 16th. 

8/08/00 - A workshop has been scheduled for September 8 th to discuss and document the prioritization process. There 

will be 3 CLECs attending the meeting as volunteers to review and provide feedback to the initial process 

document. Volunteers are Claudia Dressler, AT&T, Elliot Goldberg, Mettel, Tyra Colbert, MCI. 

9/12/00 - A meeting was scheduled to discuss the prioritization process on 9/20/00 

2/6/01 - BA recommends closing. 

3/6/01 - BA recommends closing. Closing was not addressed at ICC Mtg held on 2/13/01 

3/13/01 - CLECs request this item remain open 

10/8/02 - VZ recommends closing. CLECs request a specific tie to a regulatory requirement in order for a change to be 

considered a Type 2. Item remains open pending Verizon investigation


16 




2/11/03 - Verizon introduced DENY status for T5 change requests. The ability for Verizon to deny a T5 is not part of the 

CMP Agreement. Language supporting a Deny status needs to be addressed by a working group along with 

prioritization of Vz initiated change request as Type 1, Type 2, or Type 4. The use of DENY at this time 

indicated the CR is still open, but not being actively pursued for development. 

74 Wholesale Provisioning 

Tracking System 

4/18/03 - At the April CMP meeting, April 17 was selected as a meeting date to continue the discussion. On April 17 

meeting notes were issued. The Agreement was reached to pursue action on the following items as part of the 

current CMP meeting schedule. The PWG session may extend when necessary to address these concerns. The 

following action items will be reflected in Topic #73. 

- Verizon to provide a detailed explanation for each T5 CR with a current status of Denied at the next CMP 

meeting. Verizon committed to revisit each initiative and to provide a more detailed explanation on why 

the CR is inactive. 

- CLECs agree to evaluate the explanation given and to either withdraw or escalate the CR. 

- CLECs agree to validate the importance of CRs and to withdraw any unnecessary enhancements. 

- CLECs request clarification of change requests types and continue to challenge the assignment of Type 2 

when the flow through metric is being exceeded. The Type 2 designation should include a rationale. 

- CLECs expect a status of T5 CRs every month. 

- CLECs expect a 12 month rolling development schedule 

- CLECs expect a return to the former process of reviewing requirements associated with pending T5. 

1/9/01 - BA advised CLECs of this new tracking system. The system will give the ability to monitor loop migrations 

and new loops under development. This new system is for Loops only. In February, four CLECs will be a part 

of a tracking system pilot with full deployment planned for June/July 

- BA plans to have a three day seminar for this system, however a date has not yet been determined 

- CLECs would like to receive feedback from the CLECs involved in the pilot 

3/13/01 - VZ again explained the tracking system as a system we are about to introduce on a trial basis. The trial was to 

begin on 3/5, but has since been delayed. Current status was not available at the start of this meeting. The 

delay is due to some software issues. Once in place, the system will give the ability to track the progress of a 

hot-cuts for new loops or migration, etc 

- CLECs questioned who would be the trial participants. VZ responded (AT&T, Broadview and Network 

Solutions, although validity of participants would need to be identified. CLECs would like a report from those 

participants utilized for the trial. The trial should last between 30 and 60 days 

10/8/02 - VZ recommends closing. CLEC advised that the WPTS process for new loop was not in place and that this 

item should remain open pending resolution. VZ will have WPTS SME discussing status during Nov 12, 2002 

CMP meeting. 

1/14/03 - Awaiting confirmation of new loop WPTS capability



4/8/03 - The ability to status a new loop order in WPTS is targeted for June 2003. 


17 


75 PA Uniformity 9/10/02 - VZ advised the company is starting to get ready for the Pennsylvania conversion. VZ advised this conversion 

will include and cover the former GTE Pennsylvania customers being converted to the former Bell Atlantic 

suite of systems and OSS systems. VZ advised a phase one conversion will be done on the weekend of March 

15th, 2003 this will cover the entire Eerie LATA. The second phase of the conversion, which will be the 

remainder of the state, will occur over the weekend of May 17th, 2003. 

- VZ advised that the plan is to do similar type activity of sharing information and posting information to the 

Verizon website, similar to what was previously done forVirginia. There will be a specific place on the 

Wholesale website under the category of VAGTE Merger Commitments that will be entitled PAOSS 

Uniformity. 

- VZ advised that each company that is involved in this conversion has been contacted. VZ advised if there are 

any CLECs who are involved and have not been contacted, should contact VZ ASAP. 

- VZ advised that a change control notice will be distributed probably within the next several days. 

10/8/02 - VZ discussed the change control notification that officially stated that there will be a migration of the former 

GTE OSS interfaces in business rules for Pennsylvania to Verizon East, former Bell Atlantic interface business 

rules. This was a 2-page document that lists NPA and NXXs that are involved in the pilot, which will be in 

March of 2003. This notification also indicates that phase 2 will be in May 2003, for the balance of the NPA 

NXXs 

- VZ advised that as part of the education process, there would be workshops similar to what was held last year 

for Virginia, which would include a few hours of walking through the CLEC guide. There will be two 

workshops, the first will be held on November 14th. This will be held as a conference call. VZ advised the 

next workshop would most likely be in the early to mid spring. 

- VZ advised that there will be a CLEC guide, which will, at a fairly high level, describe the transition process. 

This will have an overview of the impact to the CLEC. This will show the differences between what CLECs 

are doing today and what will be done in the future. This document is approximately 30 pages in length and 

will also include contact information. It will also be posted to the Verizon website. 

- VZ advised all CLECs that are going through this process in Pennsylvania must provide a new profile. The 

deadline for this was September 27th 

11/12/02 - VZ advised that the Pennsylvania conversion to former BA OSS interfaces is on track for 3/17/03 for phase one 

for the Erie LATA and for May 17th for the balance of the NPA NXX’s in Pennsylvania. VZ advised a 

workshop is scheduled to walk through the conversion details. The workshop is not only for those in 

Pennsylvania who will be converting but for anyone who wants to participate. VZ advised the WEBEX will be 

used for the training therefore advance registration is necessary. VZ advised that the e-mail also included a 

mailbox for the communications group, this is pava.clec.communication@verizon.com. 

- VZ advised there will be a change control notice for Bill Manager, which is replacing Simple View which will 

be discussed in the workshop.


18 




12/10/02 - VZ thanked all CLECS who participated in the conference for Pennsylvania last month. VZ advised that this 

was a success, and that there were many participants using the WEBEX, which was used for the first time in 

these meetings. VZ advised this will continue to be used. 

- VZ advised there will be a second conference which will take place on February 20th from 1-3p.m Easter 

standard time. A notice will be distributed shortly which will provide the date and call in number. A reminder 

will also be distributed as the February 20th date approaches. 

- VZ advised an informational bulletin will also be distributed to advise that Cyber DS1, which was only 

available in the former GTE, will now be available in the former Bell Atlantic regions. 

- VZ advised that questions asked at the conference regarding PAVA are also in the process of being completed 

and responses will be provided shortly. 

- VZ advised that new profiles received from CLECS who are involved in the PA conversion still need a bit 

more work. These CLECS should have or will receive a call from their account manager within the next 24 

hours. CLECS were advised to treat this with a sense of urgency, as the profiles must be updated to be very 

complete and accurate. 

- 

1/14/03 - Verizon proposes to treat topic as CMP agenda item. Verizon will status in CMP Meeting Notes. Move to 

CMP Archive to reduce volume of paper. 

- Vz advised that it is very important that all Pennsylvania impacted CLECS complete a new profile. 

- Vz advised that communication with the PA impacted CLECS as a follow up session has begun. 

- Vz advised that there is a new CLEC guide version 2 that has been completed, this will be posted by the end of 

this week on the OSS website. 

2/11/03 - CMP notice will be issue to explain the move of the Erie LATA pilot from March to May. With the date for 

phase 2 to be available latter in 3 rd Q03. The Team is continuing one-on-one calls and responding to CLEC 

questions. CLEC encouraged to visit website for detailed Q/A. The workshop will be rescheduled for mid 

April. The USOC conversion document should be available on-line this week. 

3/11/03 - Expect notification of April 16 workshop to be issued within the next two weeks. The business rules used for 

Directory in fGTE may be different than the rules used by fBA. These are Directory Company differences. 

4/8/03 

The Directories are not merging. 

- Verizon suggests the removal of Virginia Uniformity documentation found on page 17-25 and renaming pages 

25 as Pennsylvania Uniformity with the May material. No CLEC objections to the proposal were noted. The 

VA Project is considered closed. The PA Project Team mentioned the April 16 PA Workshop, the need to 

check the PA section of the Verizon Wholesale website, and ongoing business to business contacts.


19 




76 Billing 09/20/01 - VZ gave clarification on items discussed in August. BDT format is now available on CD-Rom for wholesale 

customers in the VZ footprint 

- VZ announced that resellers can choose BDT as their bill of record in NJ. CLECs can choose to receive a BDT 

with a paper summary bill or a BDT with full detail paper bill at no additional charge at this time To request 

this option, an e-mail can be sent to your account manager 

10/09/01 - CLECs had a question dealing with platform BDTs where USOCs are not associated with a WTN. VZ replied 

that this does not occur with every USOC on the platform accounts, only certain ones. VZ stated that this does 

show as a billing issue, however there is nothing in the BDT software that can correct it due to the fact that 

there is no associated WTN provided at the time for the order. A suggestion to AT&T was to provide a change 

control request that the WTN be associated with those USOCs and get an agreement with the CLEC 

community to change this going forward. 

11/13/01 - Topic not discussed, SME unavailable. 

12/11/01 - VZ reviewed two documents that was distributed to CLEC community the at the end of November. 

- The 1st document pertained to Delaware Billing Options. The purpose of that communication was to advise 

CLECs and Resellers that effective, 12/01/2001, VZ DE will offer CLECs and Resllers in DE the option of 

treating either the paper bill or the BOS BDT as their bill of record for the bill periods completed after the date 

of election. 

- The 2 nd document pertained to DE billing option. The purpose of that communication was to advise CLECs 

and Resellers that VZ has implemented a new quality assurance process for all (BDTs) in the states of VA West 

VA. This new quality assurance process shall become effective in these states with the December 1st billing 

cycle. 

01/08/02 - VZ covered three documents that was distributed to the CLEC community via BA Change Control. 

- The 1st topic was the VZ BDT Quality Assurance Process in MD and DC. The purpose of this communication 

was to advise CLECs and Resellers that VZ has implemented a new quality assurance process for all BDTs in 

MD and DC. These new processes became effective with the January 1st billing cycle. 

- CLECs questioned if these areas were expressTrak. VZ to follow-up 

- The 2 nd topic was regarding a Billing Process Job Aid. The WCCC will handle media recreates, resends and 

technical problems with any electronic files for BDT. They can be reached via the Website (below). A second 

group, the Connectivity team will handle media, address changes or customer documentation questions. 

- The 3rd topic, Verizon Billing and Collections Operations Center. This center will handle claims, adjustments 

and rate disputes. Website: http://128.11.40.241/east/wholesale/customer_docs/master.htm


20 




02/12/02 - VZ advised CLECs of a document sent via BA Change Control on January 25th regarding BOS BDT Phrase 

Code Conversion and Phrase Code List scheduled for the February 2002 release. VZ will be implementing 

BOS BDT functionality changes for wholesale products. The purpose of this retail phrase code is to have them 

appear on the CABS BDT as appropriate. The first four pages list the new phrase codes. The next group show 

a group of variable codes, “x” codes. Those will contain variable text or data information such as installment 

billing information where you have to put in a specific month. The next group of pages show the former North 

codes . The last group of pages show the form and retail billing codes 

3/12/02 - VZ advised that there will be new state codes that will be appearing on the BDT for the conversions that will be 

happening in March, the Virginia accounts,. The State codes will be VG for the former GTE accounts and VC 

for the former Con-Tel. Those will take the place of the current state code of VA. 

- VZ advised that this same approach will be taken when the Pennsylvania accounts are converted and that time 

frame is either in May or at least not in March. 

4/09/02 - VZ announced the update to the implementation of the latest requested updates to CABs BDT. –VZ advised 

this is done in VZ at least every six months following Telcordia’s standards. VZ will implement Version 37 for 

wholesale customers effective April 5, 2002 in New York and New England, effective April 20th in New 

Jersey, Pennsylvania, Delaware, Maryland, DC, Virginia and West Virginia 

5/14/02 - VZ advised CLECs of the elimination of nine-track reel to reel tapes. The nine-track reel to reel tapes will no 

longer be available as a method of delivery option in Verizon. 

- The manufacturers of this tape will discontinue their production and maintenance of nine-track reel to reel tapes 

due to outdated technology. As a result, Verizon will no longer offer nine-track reel to reel tapes as a method 

of delivery option for Daily Usage Files (DUF), operator services usage files, meet point for access usage files 

and/or Billing Data Tapes known as a BDT. 

- VZ advised CLECS to contact their account manager to choose another method of delivery if they are currently 

receiving nine-track reel tapes for any of the mentioned files. 

- VZ advised if alternative arrangements are not made by November of this year files will automatically be 

upgraded to a 3480 Tape Cartridge by January 1st, 2003. 

6/11/02 - VZ advised CLECs of Change Control distributed on May 16th regarding the correction to double billing of 

loops. The original Change Control on this subject went out on February 21st, which was the initial 

announcement of both the double billing of loop. 

- VZ advised CLECs of e-mail distributed on May 28 th regarding the implementation of Verizon East Wholesale 

CABS boss BDT version 38 in October 2002 version 38. 

- -VZ advised CLECs of e-mail distributed on May 28th regarding the Bill of Record for Maryland, D.C, 

Virginia and West Virginia.


21 




7/09/02 - VZ advised, Effective July 1 st , 2002, Verizon will begin offering the option to receive UNE listing accounts on 

BDT, billed out of Verizon’s Express Track in Maryland, District of Columbia, Virginia, and West Virginia. 

BDT will be available via NDM, also known as Connect Direct, cartridge, or CD-ROM. 

- VZ advised an e-mail regarding this topic will be distributed later in the month of July 

8/13/02 - VZ updated CLECS on the topic of Resale Uniformity. An e-mail was distributed on June 7th regarding this 

subject. VZ advised that there are three main areas in resale uniformity. The implementation in some of these 

areas will be deferred fro m August 19th to October. 

- VZ reminded CLECs that paper and CABS BOSS BDT functionality changes for resale products will be 

implemented throughout Verizon East on August 19, 2002. This project will deliver CABS BOSS BDT in a 

uniform record format throughout Verizon East. All CLECs using Verizon resale products will be affected. 

- VZ advised CLECs that a change control was distributed last Friday to advise that the product and usage level 

discounting for the NPD area, for New Jersey, Pennsylvania, and Delaware will be delayed until October 19th. 

This will result in resale discounting being applied at the usage product level. This is currently practiced in the 

New York, New England region. This piece of uniformity will be delayed until October 19th for the NPD area. 

Meaning resale discounting will be done at each usage and product level in MDVW on the 19th as it’s done in 

the North. 

- VZ advised in the area of uniformity, there were five categories that were being updated – RST/RSE values, 

local calling plan type codes, uniformity of the sign, usage record sequence, and discount OCC record removal. 

What was deferred was the New York and New England LCPT codes. All files in all jurisdictions New York 

files except for the LCPT codes in New York, and England. In other words, for those in NPD and MDVW the 

new codes will be displayed as VE appropriate next to bytes of the four character fields. In New York and New 

England these codes will remain at the current values of an X and the next two appropriate characters of that 

four character field. 

- VZ advised that in the August release, Verizon will be implementing an administrative bill for the former Bell 

Atlantic South. This is to mirror what is currently received in the former Bell Atlantic North. The bill will 

contain all ancillary charges, and they will be moved from the master account to this separate bill. 

- VZ advised the first bill will be the September 1st bill


22 




9/10/02 - VZ advised CABS BOS version 38 will be implemented in Verizon East wholesale on October 1, 2002. The 

version consists of 12 items – there is one OBF issue, 5 tariff policy requests, 5 clarification requests, and a 

phrase code update. The attachment in the e-mail and the differences list previously distributed has all the 

specifics. 

- VZ advised the wholesale bill manager, which is a new product offering being introduced on October 19th, is a 

PC based analytical tool providing customers with the image of the paper bill and the tools necessary to 

manipulate the data and create custom reporting. This is new for resellers in the former BA North territory, and 

is going to replace Simple View, which is the current offering in the south. Simple View will be retired on 

April 2003. VZ advised CLECS who are interested in this product to contact their account manager and 

arrange for a demonstration. 

- VZ reminded CLECs that billing inquiries regarding Simple View media issues are handled by the Verizon 

Wholesale Customer Care Center at 877-946-5222. 

- VZ advised that as part of a plan of record, Verizon agreed to make uniform the presentation of circuit 

delimiters on the bill data tape for UNI resale. This change is going to be implemented in the December 2002 

release, and will change the circuit delimiters from commas to periods in the Verizon East New York/New 

England jurisdictions, making them uniform with the other former BA jurisdictions. This is a BDT change 

only and will not impact circuit inventory or the CSR. 

10/8/02 - VZ discussed the elimination of the nine track reel-to-reel tape. VZ advised that CLECs were asked in April to 

contact VZ if they do not want to receive a 3480 tape cartridge as a default 

- VZ advised that so far no CLEC have made contact regarding this matter therefore the 3480 tape cartridge will 

automatically be distributed if no CLEC makes contact by November 1st. 

11/12/02 

- VZ advised there is no update for this topic


23 




12/10/02 - VZ advised of the circuit delimiter change which will be happening on December 21st. The notice advising of 

this change was distributed previously. The delimiters will be changed to periods from commas, which will 

make them uniform across the Verizon East footprint. That was a BDT only change. 

- VZ advised that the option to receive UNI listing on BDT will become available December 23rd. A notice was 

distributed to advise of this. This option will be available in New York, New England, New Jersey, 

Pennsylvania, and Delaware. 

- VZ advised that a notice was distributed to inform of the upcoming Bill Manager training. The first took place 

on 12/05/20. Subsequent training will be on December 12, January 9, January 16, and January 23. CLECS who 

use Simple View are urged to attend the training because eventually Simple View will not be available because 

Bill Manager will be the replacement. 

- VZ advised that installment billing, usually an 18 month type of contract installment payments, and was 

available from April 1, 1998 to August 14, 2001 is just now being removed from the systems. By December all 

systems will have removed any installment billing contracts and installment billing options. 

- VZ advised that 3-4 notices to inform that 9 track reel to reel is going away as of January 1 st have been 

distributed in the past. If CLECS have not opted to receive NDM for DUF or NDM or CED-ROM for BDT, 

they will be converted to cartridge. Therefore CLECS are urged to fill out a new profile if for example they are 

planning on moving to NDM in order to avoid receiving cartridge. 

- VZ advised that a notice was also distributed regarding the BDT balance issue. The USOC money and charges 

on records were correct but the balance due was overstated. Credit will be applied and should beginning 

reflecting on the December bill. 

1/14/2003 - Vz advised that an email was distributed advising CLECS of the option to receive UNI listing accounts on bill 

data tape in New York, New England, and New Jersey, Pennsylvania, and Delaware. This is available through 

the normal BDT forms of media and the M cartridge CD-ROM. 

- Vz advised that Bill Manager training is still continuing every Thursday. Bill Manager will replace 

SimpleView. This will not be an automatic replacement. CLECS will have to call and order Bill Manager or 

call to update their profile to request Bill Manager instead of SimpleView. 

- Vz advised that in June, BARM – which is Bell Atlantic regenerated media – billing files will no longer be 

available in New Jersey, Pennsylvania, and Delaware. This was a grandfathered form of bill media was retired 

in MDVW when accounts all converted to eTrack. CLECS were advised to contact there account manager to 

update their profile form if they wanted to convert from BARM to BOSS BDT. 

- Vz advised that in February usage for New Jersey, Pennsylvania, and Delaware, Maryland, DC, Virginia, and 

West Virginia will be separated by month for the 1039 BDT records instead of it being grouped together when 

over three months old. 

2/11/03 - Vz reported that Simple View will be going away. Bill Manager training has been completed. 

3/11/03 - Vz advised that we don’t have anything major to report for billing other than a couple of enhancements with 

adding CLLI code & surcharge dates to surcharge and tax records.


24 




Web Enhancement 

02/12/02 - VZ will be giving monthly updates on changes and enhancements to the website: www.verizon.com\wholesale. 

VZ is in the process of reforming the website to be more interactive 

- A notification was distributed last week about sample orders. Those sample orders can now be obtained as 

follows. Directions: go to the main url address click on training and education click on local service 

providers click on online library. Eight sample orders appear - four for VZ West and four for VZ East 

- VZ is looking for customers interested in doing usability testing. VZ would like to observe actual orders from 

representatives. VZ would like to follow through to submission to see how testing is done through the systems. 

VZ has talked to a few customers and are looking for more volunteers for usability testing. If you would like to 

volunteer your company, send an e-mail to verizon.systems.team@verizon.com and indicate your interest 

- VZ plans to post a rolling calendar to the website of scheduled events, workshops, and meetings. Searches on 

the website will be accessible by topic and prior presentations will be posted. 

- The training and education link has been updated to include online registration capabilities. A 2002 Workshop 

schedule will be posted. All former workshops and presentations will be included 

- There will be web-based training modules on the website. UNI and UNI platform has a self paced training 

module that allows you to take the class as well as practice online the types of transactions you would be 

placing. This service is available 24/7 from your PC and can be accessed through the training and education 

link on the website 

- Other future plans include interactive functionality. We will be rolling out a connectivity wizard that will 

establish online connectivity which will ask your interface type, etc. The website will then give you choices to 

select the connectivity wanted and it will drive the user to fill out a form. That form will be forwarded to 

connectivity management to start the implementation process 

- Also under development is CLEC connectivity profile and CTE profile information. Your connectivity 

arrangements with VZ are shared internally as needed. VZ is working with its IP business partners to roll this 

out to customers so that CLECs would be able to access, read and verify its content. 

- VZ will be building online capability for the CLEC to submit information. VZ would like the website to be 

user friendly 

3/12/02 

- VZ advised we will be introducing the web architects design in April called the Wizard. This will include all of 

the information pertaining to establishing connectivity with Verizon. Information previously seen on the 

website or in the handbooks will now be much easier to find by searching and navigating through wizard. This 

will be discussed further at next month’s ICC meeting. 

- VZ advised we will also be requesting volunteers to participate in usability testing . 

- VZ advised that CLECS using the LSI or the web-GUI should remember to contact connectivity management 

to obtain their digital certificate for the web-GUI before the deadline of April 1.


25 




04/09/02 - VZ repeated the GUI help desk number for CLECs. CLECs were advised that a voice mail can be left if they 

are held in a holding pattern or an e-mail can be forwarded with their particular question. 

- VZ also advised that there will be some things that will be coming up on the Verizon Wholesale Website, 

probably towards the end of this month or probably before the next Change Management meetings. VZ advised 

a notice will be distributed through VZ Change Management. 

- VZ advised that the new connectivity guide and the connectivity wizard should be available at the end of this 

month on the website. The connectivity guide will include all the content for both Verizon East and West, but 

specifically information regarding local connectivity which was included in volume 2 of the CLEC handbook. 

- VZ advised that 26 sample orders will be added to the Wholesale website by the end of the month. VZ also 

advised that attempts are being made to have all sample order scenarios in one location on the website 

05/14/02 - VZ advised that the connectivity wizard and guide should be launched this month or in May. Verizon’s aim is 

to include as much order and pre-order content out on the Website by the end of June. The entire Website is 

targeted to be completed by the end of the year. 

6/11/02 - VZ advised CLECs there are currently 36 sample orders on the Wholesale website, this is a split between 

sample orders for the east and sample orders for the west, and a split between UNE, resale, and platform. VZ 

advised 26 additional sample orders were added last month, some of which include ISDN. 

- VZ advised the next release on June 28 th includes changing 8 original samples that were in LSOG 4 to LSOG5 

which means all samples on the website will be in LSOG 5. An additional 68 samples from the CTE test deck 

will also be added. 

- VZ reminded CLECs of changes taking place in September regarding the process for submitting caption 

information. CLECs were encouraged to take a look at these samples when they become available in June. 

- VZ advised CLECs to take a look at the Connectivity Wizard and the Connectivity Guide. This can be 

accessed by going on the wholesale website, clicking on local service providers and then on tools and 

applications. CLECs were advised that the Wizard allows them to select the kind of Connectivity they want to 

establish the different types of domains, such as pre-order, order, provisioning, billing, maintenance and repair 

7/09/02 - VZ advised 76 additional order samples, east and west, were added to the website. These order samples we 

gleaned from the VZ CTE test stacks, and There were also 10 East caption list workshop material scenarios 

added which also give a brief description of what the caption would actually look like. Samples for the west 

will be added in the coming months. 

- VZ advised the video for the Caption Listing website will also be included on the website. 

- VZ advised that time will be spent working directly with customers , VZ advised this will be discussed further 

in the future. 

- VZ advised there will be announcements made regarding WEBX via VE Change Control, regarding reviewing 

and touring the new contents such as showing all the samples that are currently available.


26 




8/13/02 - No updates made regarding this topic. However, CLECs were advised VZ will schedule a Webex tour which 

will be announced later this month 

9/10/02 - No updates made regarding this topic. 

10/8/02 - VZ advised that there is new Trouble Administration feature on the web site that gives information regarding 

putting in tickets through. VZ advised that a host of pre-order samples are also live on the web today. There 

are approximately 29 different pre-order samples and they are done in the same fashion as the order samples. 

Some of these samples include Address Validation, CSRs, Loop Qual, Loop Makeup and Location Porting. 

- VZ also advised that the connectivity form that is filled out in order to establish access to different OSS has 

been removed from the connectivity guide section of the web (near the tools and applications tab). This has 

now been made a link 

- VZ also reminded CLECs that the current URL for the LSI is changing. For those who access the LSI via the 

internet, the current URL will be removed on November 24th of this year. The new URL for the LSI will be 

available on October 20th. Current username and password, along with digital certificates, are still valid to be 

used.


27 




11/12/02 - VZ advised there are 112 sample orders on the website today. They can be found on the online library. There 

are also various links from other locations to access these sample orders. VZ advised there are continuos 

enhancements being made to the sample orders. Some of these enhancements include one of the last things that 

were done, which was adding the directory listing samples to the east. There will also be 7 new directory cap 

listing samples added for the west. They will be the same samples that were used in the June workshop, except 

that they will be updated to reflect the October release. 

- VZ advised that we are working on complex services from a sample order perspective, as well. This is a large 

project, therefore, this will be done almost product by product. One of the first product that will be done is 

Centrex AD9 platform. There will be probably be two samples for this product, a migration as specified 

activity, and also a New activity. These samples should be on the website by the end of the year. 

- VZ advised that an enhancement was made to sample 7E, the basic rate ISDN migration as 

specified sample. Field 45, the spec filed was added. This is a field was added even though 

it is optional and information in the field is often not provisioned. 

- VZ advised that enhancements are also being made to the training and education information that is on the 

website. VZ advised that currently enhancements are being made to the web based training in the east so that it 

is updated for LSOG 5 and in the West for both resale and UNI. No dates for either of these items have yet 

been confirmed 

- VZ advised that work is being done to provide documentation via the website for some of the various FTP 

server reports that are available. The documentation will include information about the reports. It will also 

include information on how to establish access to the FTP servers. Links will be added to the website that will 

connect to the connectivity options, which are available through the connectivity guide. The connectivity guide 

can be accessed through the online library. 

- VZ advised that the aim is to make the website more user friendly and basically update any information on the 

website to ensure that it is current with the current LSOG versions. 

- VZ advised as the enhancements are made, the look and feel of the website will change drastically. Webex 

sessions will be held to allow users to become familiar with the new format.


28 




12/10/02 - VZ advised that there were 7 new LSOG 5 directory caption samples made available on the Verizon West 

website on 12/02. 

- VZ advised there will also be possibly, by the end of December or the beginning or January, three new Centrex, 

AD9 sample orders for platform, Migration as is, Migration as specified, and New 

- VZ advised that a reminder was distributed via Change Control for the upcoming CLEC Ordering Workshop. 

CLECS were encouraged to participate as there many useful information covered in these sessions. A 

Connectivity workshop is also being planned and the date will be communicated. This workshop will help in 

giving information on the new location of information of the website. 

- VZ advised that as changes/enhancement are continued to be made to the website, the CLEC handbook will 

basically be retired as is discussed in various workshops. All information that is now currently located on the 

CLEC support site will be moved over to Verizon.com, this is being targeted for the beginning of January. A 

notice will be distributed via Change Control once the dates have been confirmed. This will again be discussed 

in the future to ensure that all CLECS are aware of the change. 

- VZ encouraged the use of the website content available, particularly web based training. Continuous 

enhancements are being made to the website to ensure that it is kept up to date, and that it has the latest 

information and is available 24/7. 

- VZ advised the there are ordering problems that are sometimes queried back to the CLEC which is a result of 

the lack of use of the pre-order guide. The local ordering guide available on the website, found in the online 

library has an entire section that covers each of the pre-order transactions and sample orders for each 

transaction. 

1/14/2003 - Vz advised that three new East UNI P will be added for assume dial 9 samples to the website by the end of the 

month. Vz will also have USOC guides associated with those sample orders. The sample orders will cover As 

Is, migration, As specified, and New. Verizon will cover those samples in the February ordering workshop. 

- VZ advised that there was a connectivity workshop to introduce the fact that in Verizon East and West, 

connectivity will be removed. That is, the connectivity information will be moved from volume two of the 

handbook and the CLEC guide into the Connectivity guide. Volume two and the information in the CLEC 

guide will be retired. CLECS were advised to go through the connectivity guide to view the information.. 

- Vz advised that the Ordering workshop is on February 19th, CLECS were advised that they can register via the 

website. This information will be found on the events calendar. 

- Vz advised that all CLECS should be aware that the connectivity guide is available. It includes information for 

pre-order, order, trouble admin, and the provisioning domains. It can be accessed through the connectivity 

wizard. Also access request can be submitted directly from the connectivity guide for various connectivity 

options via online forms available on that site. 

- CLECS were advised that a new tab in the connectivity guide containing billing information will also be 

available in the first quarter of this year. VZ advised that the local order guide in wizard will have 

enhancements made in the first quarter. That guide and wizard can be accessed through the online library on the 

LSP page.


29 




2/11/03 - Vz advised that the will be a workshop on March 19, 2003. You can go to the event calendar to sign up for the 

workshop. The workshop will cover a couple of things, Vz resale and platform error scenario and invalid due 

date less than standard to date interval. Also change to class of service. 

79 NMC Access to CSI 

80 NMC Access to LSI 

81 

3/11/03 - Vz advised of a CLEC ordering workshop on March 19, 2003. 

April 03 From Feb 7, 2003 conference call. Verizon will verify the NMC can actually see all lines of CSI information that a 

CLEC can view on-line. Instances were cited that suggest the NMC could not view the same content. 

5/13/03 Verizon confirms NMC access to all lines of the end user account record information available to the CLEC in LSI. 

The format the information is presented may differ. 

April 03 From February 7, 2003 conference call. The CLEC community recommended providing the NMC with access to 

LSI. The interaction with the NMC could be improved if both the NMC and CLEC were looking at the same LSR. 

5/13/03 NMC believe the issue can be addressed by improved training. 

Pre-Order Training April 03 From February 7, 2003 conference call. Verizon will republish where to find important pre-order information online. 

There were questions about how to look at the CSI prior to transmitting the LSR. 

Response: The Pre-Order Guide describes all the transactions available in both East and West Regions. The 

location is http://www22.verizon.com/wholesale/. Also see the on-line training archive for Pre - 

Order Workshop information from April 2002. Pre -order samples exist on-line for all transactions. The LSI online 

user guide also contains pre-order information. The EDI and CORBA specifications and CTE Test Deck also 

document pre-order transactions. 

CLOSED with CLEC Concurrence April CMP. Shading indicates removal from June list. 

82 WCCC Escalation List April 03 From February 7, 2003 conference call. There was a suggestion to expand the WCCC on-line escalation list. The 

strong preference was to reduce the hold times and to avoid escalation. 

Response: April 03 – the WCCC documentation includes three levels of escalation with the fourth level available 

upon request. The current version is January 2003 and available at 

http://www.verizon.com/wholesale/clecsupport/east/wholesale/customer_docs/pdf 

s/wccc.pdf 

CLOSED with CLEC Concurrence April CMP. Shading indicated removal from June list.


30 




83 CIRT Escalation List April 03 From February 7, 2003 conference call. There was a suggestion to expand the CIRT on-line escalation list. The 

strong preference was to reduce the hold times and to avoid escalation. . 

84 Caller ID Exhaust 570/572 3/11/03 CLECs reporting production problems associated with a conversion of caller id from retail to resale or UNE P is 

being dropped during conversion. 

Response: Production impacting - under active investigation.

Customer Distribution List 

ABarone@BroadViewNet.com kathrynpedersen@att.com 

ABarone@BroadViewNet.com kdclark@att.com 

AMY@EZPHONEUSA.COM kdiloren@telcordia.com 

AWiley@nfis.com kducharme@thelocalphonecompany.net 

Adrian.Gamory@GGN.COM keithd@d-tel.net 

Al_Mayerhoff@nyigc.com kenya@unitedllc.com 

Alain.Boudreau@prexar.net kestes@groveline.com 

Alan.Flanigan@twtelecom.com kevin@qis.net 

Alan.Thompson@rcn.net khetherington@choiceonecom.com 

Angela.N.Jones@wcom.com kim.bridge@westelcom.net 

Angie.Fisher@globalcrossing.com kim.conway@onepointcom.com 

Anne.Cullather@Qwest.com kim@d-tel.net 

Annox2@annox.com kinya@closecall.com 

Apentland@dsl.net kj1614@sbc.com 

Armando.Garcia@OnePointCom.com kking@dpiteleconnect.com 

1 May 2003 Distribution List


Aschanzer@utilisave.com kknapp@groveline.com 

aarmstro@telcordia.com kkordus@ems.att.com 

abe.connectel@verizon.net kmorales@nos.com 

acarey@att.com kmraz@thebiz.net 

adudley@lightship.net kwalker@bridgecomtel.com 

adunbar@ccitelecom.com kwhittard@wvfibernet.net 

aeconomou@mettel.net kwoodard@thebiz.net 

afitzsimmons@att.com LBlair@RemiCommunications.com 

agooden@biztelone.com LEC.Liaison@localaudit.com 

ahampel@commsouth.net LEVYASSOCIATE@AOL.COM 

alain.boudreau@prexar.com LMitchell@wisor.com 

albielecki@msn.com LPRobinson@ATT.com 

alex.pantazis@algx.com) Leon.Rhyne@rcn.net 

alice_allen@cable.comcast.com Linda_Duggan@rcn.net 

alltelecom@aol.com Lisa.Kuehn@ComScape.net 

amccaslin@ctel.net Lisa_Spalding@commercelink.com 

amigliassi@groveline.com Lissa.Provenzo@wcom.com 

amy.kwak@ct-enterprises.com Loriann.Ercan@allegiancetelecom.com 

andreassis@electricfiber.com larry@thorn.net 



anne.lynch@reconex.com launch-now.notify@accenture.com 

anthony.triola@adelphia.com lcamillo@granitenet.com 

apandina@choiceonecom.com ldavidov@dset.com 

aprovencher@lightship.net ldavis@metrotelco.com 

arichardson@capsulecom.com ldimi@ems.att.com 

asanjuan@mettel.net leahb@midmaine.com 

aspina@corp.thorn.net lellis@choiceonecom.com 

asturtz@choiceonecom.com lenam@lightyearcom.com) 

aulisio@att.com lgannon@thebiz.net 

BAnotes@talk.com lhopkins@eftia.com 

BFlynn@xtel.net linda@annox.com 

BGuido@RemiCommunications.com lisa.fasciana@adelphia.com 

BKoenig@onestarld.com


benm@nxgt.com lopezr@mid-hudson.com 

bettybarrett@att.com lora@currycommunications.net 

beverly@rnktel.com lpellegrino@pelltel.com 

bgoodwin@cambrian.net lsampson@ctcnet.com 

bgreeley@dscicorp.com lscalley@broadviewnet.com 

bkarmake@telcordia.com lsims@cavaliertelephone.com) 

blmcgrath@att.com lsorino@xtel.net 

bmiraval@broadviewnet.com lthompson@z-tel.com 

bob@digitalconnections.net ltillett@dsl.net 

bparmer@dande.com lwelch@nuitele.com 

bpetersen@dsl.net lyn.pinto@adelphia.com 

br1716@sbc.com lynn.eckert@adelphia.com 

brauchle@att.com MLally@BroadViewNet.com 

brian@mid-hudson.com Micki.Jones@wcom.com 

brian.moynihan@xo.com macdon@ctcnet.com 

broadband@gwi.net macek@ntelos.com 

brogers@att.com mark@annox.com 

browand@captel.com mark.anthony@spectrotel.com 

bryan.jacobson@atx.com markc@exceleron.com 



bstewart@biztelone.com mary.clarke@cox.com 

bwolfe@4-procom.com mary.hunt@wcom.com 

CCardiff@RemiCommunications.com mataris@aol.com 

CGAMBINO@cablevision.com matt.noll@onepointcom.com 

Charles@intelecomsolutions.com mattk@mid-hudson.com 

Chris@Linesystems.com maureen.vitiello@rcn.net 

Christine.Delizzio@atx.com mbatdorf@atx.com 

Clemishia.hubbard@algx.com mboger@groveline.com 

cardinal.southwell@spectrotel.com mciccanti@xtel.net 

carol.grover@pinetreenetworks.com mclancy@covad.com 

ccassel@bullseyetelecom.com mclarke@cavtel.com 

ccastanz@optonline.ne mcoleman@broadviewnet.com 

ccherry@rnetworx.com mconry@infohwy.com 

ccoombs@ems.att.com mdonmoyer@dscicorp.com 

cdigilio@xtel.net mforan@coastalnyc.com 

cdressler@att.com mheffley@amll.com 

cfrenette@groveline.com michael@alookahead.com 

cgilman@choiceonecom.com mike@telion.tv 

change.control@currycommunications.net mitch.wright@spectrotel.com 



change-verizon@sover.net mkinney@techvalleycom.com 

changecontrol.verizon@onepointcom.com mladue@choiceonecom.com 

chappa@bpu.state.nj.us mmckenna@cavtel.com 

charles@QTelSolutions.com mmoreno@eztalktelephone.com 

charon@linesystems.com moneill@mcgrawcom.net 

chelmke@midmaine.com


cvacanti@choiceonecom.com nbattaglia@att.com 

cwelsh@cavtel.com nbrady@businessedge.com 

DANNcommINC@aol.com nconant@telcordia.com 

DJOHNSON@SITEHELP.ORG nikkei.goodwin@adelphia.com 

DMULLICK@GENESISLD.COM njanja.mathu@atx.com 

(immediate) notify@paclec.com 

DYEAGER@METROTELCO.COM nthomps1@telcordia.com 

Daniel.Doherty@rcn.ne nutelphone@fast.net 

Daniel.Toth@wcom.com nytelsave@tccteleplex.com 

David.Burley@wcom.com nzeitvogel@lightship.net 

Dawn.Tapley@Cox.Com PRubino@Z-TEL.com 

Deb.Comeau@rcn.net PaulB@Planbcom.com 

Dennis@reconex.com) Paul.McNamara@Cox.com 

Dev.Misser@rcn.net Pbolen@metrotelco.com 

Donna@reconex.com Posullivan@transbeam.com 

Doreen.Best@allegiancetelecom.com paul.naugle@atx.com 

Dpeck@uslec.com pbatista@att.com 

dallis@thelocalphonecompany.net pbeattie@dscicorp.com 

darlene.maurer@ams.com pbulloch@infohighway.com 



dave@bayring.com pchallenger@conversent.com 

dave@dmrcom.net pdillon@covad.com 

david_weiss@icgcom.com pf4768@sbc.com 

davidtk@rnktel.com phil.jones@algx.com 

davidtownsend@att.com phuberhauck@choiceonecom.com 

dchristo@telcordia.com pjhurley@att.com 

dcochrane@conversent.com pkennedy@intellec.net 

ddash@nuitele.com plaisier@bright.net 

dennis.guard@wcom.com ppron@telcordia.com 

dennis.kelley@reconex.com provisioning@monmouth.com 

dennis.stanek@adelphia.com provisioning@penntele.com 

dennymichaud@teletech.com pstutzman@granitenet.com 

derekbrown@att.com Rae.Couvillion@wcom.com> (immediate) 

devon@fullservicenetwork.net Ray_Dickler@hp.com 

dhoyt@hoyt.com Rflorio@hamptons.com 

dianna.stevens@adelphia.com Rich.Frantz@allegiancetelecom.com 

dkgilbert@att.com Richard.Glasgow@btitele.com 

dklein@flcommunications.com Rick.Garger@rcn.net 

dlight@eztalktelephone.com Rick.Heck@Planbcom.com 



dlilly@vartec.ne Rlaine@Broadviewnet.com 

dlinso@ctcnet.com Rmaimon@mettel.net 

dlovejoy@1cominc.com Rochelle.Jones@twtelecom.com 

dmalfara@remicommunications.com Roderick.Bourn@cox.com 

dmattson@ceni.com Ronald_Vero@DPS.State.NY.US 

dmina@att.com Ronnie.Johns@allegiancetelecom.com 

dmiriki@stis.com Ronnie.johns@algx.com 

dosteele@usa.capgemini.com randik@ntenet.com 

doug.turrell@xo.com rcairnes@biztelone.com 

dparobeck@mettel.ne rd5335@momail.sbc.com 

dpatota@bcm-tel.com reba.blake@wcom.com 

dpetry@ix.netcom.com rebecca.baldwin@telcove.com 

dscoville@wvfibernet.net remanda.champion@planbcom.com 

dsmith10@ems.att.com rengaj@ctcnet.com 

EDDIE.DAVIS@EUREKAGGN.COM repair@lightship.net 

ELSA@gldstr.com resale@conversent.com 

EddieD@planbcom.com rfragola@cambrian.net 

Edward.Fisher@world-link.com rgoodband@advance2000.com 

Ellen.Frantz@rcn.net rhahn@wvfibernet.net 



Ewrann@dsl.net rich.figueroa@ggn.com 

eaizenman@bcm-tel.com richard.cahill@spectrotel.com 

ebonding@algx.com rick.garman@qwest.com 

egoldberg@mettel.net rickh@Planbcom.com 

eileen.veilleux@midmaine-telplus.com robert.mckay@atx.com 

elagg@intelecomsolutions.com rodgersj@ntelos.com 

emcgraw@att.com ross.martin@xo.com 

emcneice@atx.com rselden@telcordia.com 

epierce@cavtel.com rsemidey@veranet.net 

epugsley@nwp.com rsteller@lightship.net 

erin.drake@twtelecom.com Sherry.Lichtenberg@wcom.com 

estrickland@metrotelco.com Steve.Jennings@nowcommunications.com 

eswanson@dscicorp.com samy@unitedtelcom.com 

Fran.Obrien@adelphia.com sandi.rothman@idea.com 

fabbd1@ctcnet.com scott.d.dusten@xo.com 

fglover@4-Procom.com sfarkouh@broadviewnet.com 

GHenderson@Z-TEL.com sgoodwin@cavtel.com 

GPino@GGN.com sheri.bancroft@atx.com 

Genine.Tyson@rcn.net shobbs@dsl.net 



ganderson@ccsinet.com showson@conversent.com 

gary.paa@adelphia.com sjones@choiceonecom.com 

gayle.gissendanner@cox.com sm5480@sbc.com 

gbennett@ironton.com smathews@penntele.com 

gcoller@stratuswave.com smaynard@broadviewnet.com 

gcookman@granitenet.com smcginty@primelink1.net 

george.murdock@prexar.net smendez@bcm-tel.com 

georgia.tulloch@stis.com smendez@bridgecomtel.com 

ggaillard@dsl.net smithwl@att.com 

ghammond@dsl.net snahar@tri-telcom.com 

ghawley@servisense.com sparrott@primelink1.net 

ginger.dyer@cox.com sriddle@matrixvalue.com 

gloriav@att.com ssheflett@winstar.com 

gmcdonal@telcordia.com stephanie@ezphoneusa.com 



gorengo@thebiz.ne steve.bogdan@talkingnets.com 

greg@closecall.com steve.mcgranaghan@adelphia.come 

grobideau@oxfordnetworks.com steve.taff@allegiancetelecom.com 

gruss@ccsinet.com stogie99@optonline.net 

gtoland@att.com stourangeau@conversent.com 

gwardell@cablevision.com strachan@primelink1.net 

gwood@covista.com 

Heather.Thompson2@allegiancetelecom.c 

susan.clark@algx.com 

om swoods@z-tel.com 

Helen.Allard@Cox.com TCarter@metrotelco.com 

halpin@att.com TGalipea@covad.com 

handym@ctcnet.com TINA.GENERAL@KMCTELECOM.COM 

hanleym@corp.smokesignal-clec.com TMURPHY@USLEC.COM 

hazbro@gwi.net TRamsey@ne.health.net 

henry@intelecomsolutions.com Terry.Clark@KMCTELECOM.COM 

hjacks@talk.com Tgregson@metrotelco.com 

hviolette@midmaine.com TkWilliams@BroadViewNet.Com 

ifajerman@dnetit.com Tony_Jones@hp.com 

ilec.interaction@xo.com Towanda.Russell@rcn.net 

ilecinfo@txmail.sbc.com tcassera@tri-telcom.com 



ilecnotes@talk.com tchaput@vibrant-1.com 

ilecnotification@dcaweb.net tclark@kmctelecom.com 

info@lightship.net team-tel@sover.net 

isaac.honig@verizon.net thickey@lightship.net 

JATWELL@ATT.COM thomas.panko@rcn.net 

JBROWN@QUANTUMSHIFT.COM thomas_taccetta@frontiercorp.com 

JLambert@lightship.net timw@digitalconnections.net 

JLennon@BroadViewNet.com tlcraig@att.com 

JRC@dps.state.ny.us tlyons@atx.com 

JR@GTB.net tmcqueen@onestarld.com 

JWight@BroadViewNet.com tmorris@digitalsignal.com 

JZIEGELE@broadviewnet.com tomm@midmaine.com 

Jadkin@kmctelecom.com) tomt@westelcom.com 

James_Noonan@cable.comcast.com tony.hanuman@talkingnets.com 

Jay.Day@rcn.ne trank@XO.com 

Jblackwell@broadviewnet.com) traven@oxfordnetworks.com 

Jeanette.Hatchett@cox.com tsalame@mettel.net 

Jkuhns@broadviewnet.com tscoville@wvfibernet.net 

Jmarqu@kmctelecom.com ttrowbridge@techvalleycom.com 

13 May 2003 Distribution List


Joe.Levesque@cox.com VF5164@SBC.COM 

Joseph.Hames@allegiancetelecom.com VKBaldwin@allconnectel.com 

Judy@RNKTEL.COM 

VendorChangeNotification@QuantumShift. 

com 

jaltman@xtel.net Verizon_Change_Control@elec-corp.com 

james.busi@onepointcom.com 

Verizon- 

East_Announcements@cable.comcast.com 

james.webber@corecomm.com Vparsons@wvfibernet.net 

jared.welch@accesspointinc.com vburke@skow.net 

jason.tallman@rcn.net vendorrelations@bullseyetelecom.com 

jaym@mcgrawcom.net 

jays@dsl.net vhonor@yahoo.com 

jboshier@covad.com vickif@att.com 

verizon.east.change.management@core.ve 

rizon.com 

jc@trucom.net vickyd@lightyearcom.com 

jcarney@broadviewnet.com vzchange@dnetit.com 

jennifer.benard@adelphia.com vze23qjm@verizon.net 

jennifer.benard@telcove.com WDawson@rhythms.net 

jennifer.gleason@kmctelecom.com Wadew@lan.dftel.com 

jennifer.holsopple@core.verizon.com Warren@Linesystems.com 

jeremy.bye@cox.com Wayne_Brodbeck@hp.com 

jfaulkner@decommunications.com WorldCal@bestweb.net 



jfountain@z-tel.com wccc@core.verizon.com 

jgelfand@mettel.net wcengstr@vartec.net 

jgorman@dreamscape.com wilsonch@ntelos.com 

jharpold@wvfibernet.net winchj@ctcnet.com 

jim.sanders@talkingnets.com wps-ics-east@core.verizon.com 

jkeegan@bcm-tel.com wps-ics-east@verizon.com 

jlee@ctcnet.com wtunis@att.com 

jlog323@aol.com ylee@cavtel.com 

jmapes@sover.net yolanda.williams@adelphia.com 

jmarino@amll.com yshepard@vibrant-1.com 

jmilnor@qwest.com zns_bacc@z-tel.com 

jmorea@broadviewnet.com 

jmoticka@dsl.net 

mperry@att.com 

mperry@ems.att.com 

jnelson@xtel.net 

KANIELSE@VARTEC.NET 

KKarran@XchangeTele.com 

Kevin.McGrory@Qwest.com 


Kisua.Render@cox.com 

karind@covad.com 

karla.gallenberger@globalcrossing.com 

kath@bayring.com 

katherine.couture@adelphia.com 



3 of 4 

Process Verizon-East 

System 

System 

Wholesale Systems 

Implementation Decommission 

Preorder LSI Oct-99 - 

EDI ( LSOG5, v 5.4) Feb-03 Jun-03 

EDI ( LSOG5, v 5.5)* Jun-03 Oct-03 



CORBA(LSOG5, 5.4) Feb-03 Jun-03 

CORBA(LSOG5, 5.5)* Jun-03 Oct-03 

CORBA (LSOG6, v 6.0) Feb-03 Jun-03 

CORBA (LSOG6, v 6.1)* Jun-03 Oct-03 

Order EDI (LSOG5, v 5.4) Feb-03 Jun-03 



EDI (LSOG6, v 6.1)* Jun-03 Oct-03 

LSI Oct-99 - 

Billing BDT (V38) Oct-02 Apr-03 

BDT (V39) Apr-03 

Verizon-East Wholesale Systems 


This document is intended to supplement rather than replace 

any state or federal requirements or provisions regarding 

notice of changes, including, without limitation, changes 

pursuant to 47 C.F.R Sections 51.325-51.335. Verizon and 

TCs reserve the right to seek full application or enforcement 

of such federal or state requirements or provisions. 

* Planned 

** Tentative 

Meeting System Matrix_Qtr-2nd

Release CR # / Initiative 

#/ 

April 21, 2003 

Completed 

1108.4 

362386.5 

Change Control Items by Release 

Description of Change Request CR Type Data Added 

Title: Flow through Hunting on Migrations - Phase 5 

Description: Flow through orders when Hunting is present on Migrations. Errors returned directly to the 

CLEC are: 

• 7020HT13 - HT not found in Hunt Group on CSR (LSOG 5)/HTN not found in Hunt Group on CSR 

(LSOG 6) 

• 7020HT19 - HTSEQ is invalid 

Reason: Flow Through – Metric OR501, OR503 

Jurisdiction: North, South System: Other; Primary Area: UNE-P; LSOG Version: 5 and above 

Documentation Impact: Flow through ordering scenarios 

May 6, 2003 

Page 1 of 33 

2 9/3/02


#/ 


Completed 

1466 

363851 


Title: Community Choice 

Description: The goal of this initiative is to provide a default for the community choice service in areas 

where a selection is required and to query the Reseller when the FID LUD is provided for an NPANXX 

where it is not available. Currently, the FID LUD is missing from the LSR each time a new service request is 

received and the end user resides in jurisdictions that only offers Community Choice. This situation results 

in service orders that are issued and then fail to a service order error. 

A new edit has been established to verify based on NPA NXX in the VA if the LUD FID is required. If 

required and the FID is not on the RS Form then the request will default to LUD A. If not allowed and the 

FID is on the RS Form then the request will be queried using existing error 7020SC12-Invalid Disposition of 

@ (LUD). 

There are three options which are identified by the FID LUD (Local Usage Detail), followed by 

a code set of A, B, or C. Options are on an account basis only and the specified option will 

apply to every line on the customer’s account. 

• LUD A = Minutes of USE 

• LUD B = Timed Message Units 

• LUD C = Flat Rate Option - the flat rate amount is billed to each line on the account 

Scope for these requests are REQTYP = EB and ACT = N, T, C or V. 

Reason: Flow through – Metric OR501, OR503 

Jurisdiction: VA; System: Other; Primary Area Resale; LSOG Version: LSOG 5 and above 

Documentation Impact: Flow through ordering scenarios 


Page 2 of 33 

2 2/4/03


#/ 


Completed 


Completed 


Completed 

1676 

365397 

1857 

366822 

2040.1 

368650.2 


Title: Use of the @ symbol to provide for E-Mail address 

Description: The goal of this request is to allow subscribers to give their e-mail address as contact 

information. The symbol @ must be allowed to be mapped to Remarks. When the LSR contains an @ in any 

field to be mapped to Remarks, such as LCON and ACC fields on the EU form, place it in Remarks section of 

service order instead of blanking it out as is presently done. We need to allow the @ for e-mail address 

information. 


Jurisdiction: North & South; System: Other; Primary Area: UNE, Resale UNE-P; LSOG Version: LSOG 5 

and above 

Documentation Impact: None 

Title: Process additional NE residence additional lines at Level 5 

Description: The goal of this project is to allow additional flow through of Retail to Platform migration 

requests for NE residence additional lines. 


Jurisdiction: North; System: Other; Primary Area UNE-P; LSOG Version: LSOG 5 and above 


Title: Date Due Cutoff Time-Phase 2 

Description: The purpose of this phase is to change the cut off times for certain Resale and Platform 

products and scenarios. In all cases, if the LSR DDD field is longer than the calculated due date, the orders 

will carry the due date provided on the LSR. The objective is to make sure flow through is in synch with 

established guidelines for the due date intervals. A complete list of due date intervals is available on the 

web. 


Jurisdiction: South; System: Other; Primary Area UNE-P, Resale; LSOG Version: LSOG 5 and above 



Page 3 of 33 

2 2/4/03 

2 10/1/02 

2 2/4/03


#/ 


Completed 


Completed 

2500 

375216 

2550 

375880 


Title: Pending LSRs 

Description: The purpose of this initiative is to create an automated process in Verizon systems to reject 

certain requests when pending LSRs exist. Currently, Verizon accepts and processes multiple requests 

submitted from different CLEC’s for the same end user customer. This overlap may cause service order 

errors, accidental disconnection of an end user’s service or incorrect billing. 

Comments: CLEC community requests a retransmission of the new error message and accompanying 

documentation; This change request has been negotiated with the industry through several Pending Order 

workshops held in 2002. All scenarios to be included have been reviewed by the industry. 


Jurisdiction: North & South; System: Other; Primary Area UNE, Resale, UNE-P; LSOG Version: LSOG 5 

and above 

Documentation Impact: Order Error Messages 

Title: Process for OC4 on Resale and Platform Migrations 

Description: The purpose of this request is to give instructions to Verizon systems to remove OC4 during a 

migration to Platform. OC4 will be removed on existing accounts with migration to Platform. An error 

will be sent for new requests for OC4 on Platform accounts. In addition for Resale migration requests, OC4 

blocking will be allowed using BLOCK "D" only. Requests with OC4 in the feature field will no longer be 

accepted. The following existing error will be returned 7030V185 “USOC invalid @” 

Comments: Verizon confirms this change will not imp act UNE products. 


Jurisdiction: South; System: Other; Primary Area: UNE-P, Resale; LSOG Version: LSOG 5 and above 



Page 4 of 33 

4 2/4/03 

2 2/4/03


#/ 


Completed 


Completed 

2562.3 

376027.3 

2625 

377163.4 


Title: LSOG 6: Miscellaneous Changes (not covered in other CRs) 

Description: This request will capture all minor miscellaneous changes. Detailed analysis shows 

approximately 100 miscellaneous revisions. These would include revisions to Definitions, text modifications 

on Notes and Conditions, length changes, new Valid Entries. 

Comments: There is a Phase 3 scheduled for the April 2003 release. 2 new edits will be going back to the 

CLECs: EU105 and RS 083. 

For ZIP field on End User Form EU105 - "Required if the AFT field is populated, otherwise prohibited." 

For BLOCK field on RS form RS 083 - "Required when the BA field is "A", "D" or "E" otherwise 

prohibited.". 

Reason: Industry Standard 

Jurisdiction: North & South; System: LSI, EDI; Primary Area: Resale, UNE, UNE-P; LSOG Version: 6 

Documentation Impact: Error Message document 

Title: FT MDVW LNP requests which have non-engineered centrex phase 4 

Description : This initiative will FT at level 4 MDVW LNP requests which have non-engineered centrex on 

the retail account. NPD will be addressed in a later phase. Partial migrations will still drop to Level 2. This 

initiative addresses full migrations of retail non-engineered centrex to LNP only. 

Comments: This initiative will be completed in multiple phases. Phases 2 and 7 completed in March 2003; 

Phase 4 is Committed for April 2003; Phases 1, 3, 5, 6, and 8 Candidates for June 2003. 

Reason: Flow through - Metric OR501, OR503 

Jurisdiction: MD, DC, VA, VW; System: Other; Primary Area UNE; LSOG Version: LSOG 5 and above 



Page 5 of 33 

3 10/1/02 

2 4/1/03


#/ 


Completed 

2642.1 

375483.2 


Title: Fictitious Billing Telephone Numbers (fBTN) - Phase 2 

Description: Ensure that all Wholesale systems and processes will be able to handle the new fBTN format 

being implemented in MDVW, as well as the current format. 

Business Narrative: This change request will introduce new fictitious billing account numbers in DC, MD, 

VA, WV. This will allow additional NPAs for new accounts only. There will be no change to the embedded 

base. This will be applicable for fictitious bans for listings and loops. Each state will have specific code in 

NNX. 

Examples of the new fBTN format: 

? 1st character = “0” 

? 2nd character = mapped to a state 

? MD = 1 

? DC = 3 

? VA = 4 

? WV = 5 

? NOTE: A value of 2 will not be used, since it is already being used throughout the 

existing systems 

? 3rd character = 0 through 9 

? 4th through 6th characters = 001 through 999. 

7th through 10th characters = 0001 through 9999. 

Comments: In response to COVAD challenge of CR Type. Verizon agrees that the Type 2 designation was 

inappropriate and that a more accurate designation is a Type 1 Severity 3. This CR was generated because 

of FTN number exhaust. We were running out of available numbers to assign. This CR only creates a new 

number scheme: Phase 2 is a Candidate for April 2003. 

Reason: System enhancement 

Jurisdiction: MD, DC, VA, WV; System: Other; Primary Area UNE; LSOG Version: 5 & 6; 



Page 6 of 33 

1 12/3/02


#/ 


Completed 


Completed 

2827.2 

380857.2 

2833 

380872 


Title: Platform FX Query - Phase 2 

Description: With Platform Foreign Exchange requests in the South, if a CLEC submits LSR with an 

incorrect TOS for Foreign Exchange (4th character=F), the NMC sends a manual query. This project will 

instruct Verizon system to send error message to the CLECs. 

Error returned directly to the CLEC is: 

7949G093 - TOS invalid for FX request, LSR in query. 

Comments: Phase 1 Completed 3/16/03 


Jurisdiction: South; System: Other; Primary Area UNE-P; LSOG Version: LSOG 5 and above 

Documentation Impact: Error message document 

Title: Flow through– CLT- FID MDVW -Resale End-User Accounts 

Description: The purpose of this initiative is to flow through migration and disconnect requests when the 

CLT FID is found on the account. 


Jurisdiction: DC, MD, VA, WV; System: Other; Primary Area: Resale; LSOG Version: 5 and above 



Page 7 of 33 

2 3/4/03 

2 3/4/03


#/ 


Completed 


Completed 

2834 

380873 


Title: Flow through – CLT-MDVW -Platform fid on End-User Account 




Jurisdiction: DC, MD, VA, WV; System: Other; Primary Area: UNE-P; LSOG Version: 5 and above 


378748 Title: CABS BOS Version 39 

Description: Implement CABS BOS Version 39 

Business Narrative : Implement CABS BOS Version 39 

Reason: Industry standard compliance - VZ customers would not be able to process the bills they receive 

from us. 

Jurisdiction: North & South; System: BDT-related systems ; Primary Area: NA; LSOG Version: NA 

Documentation Impact: CABS/BOSS Differences List & Explanation Letter 


Page 8 of 33 

2 3/4/03 

3 4/1/03


#/ 

June 21, 2003 

Committed 

1472 

365405 


Title: Revise ISDN Platform Process - SPEC/TOS 

Description: The purpose of this initiative is to update the Service and Product Enhancement Code field 

(SPEC) and the TOS field edits on the LSR form in order for a CLEC request for ISDN BRI to be processed. 

Business Narrative : In order for a CLEC request for ISDN BRI to be processed, the Service and Product 

and Enhancement field (SPEC) on the LSR form needs to be modified. ISDN BRI is a Remand issue. There is 

no way a request for new ISDN BRI can be provisioned without the SPEC field being populated. 

Reason: Remand 

Jurisdiction: North & South; System: LSI, EDI; Primary Area: UNE-P; LSOG Version: 5 and above 

Documentation Impact: LSOG 5 & 6 Order Business Rules and Error Messages 


Page 9 of 33 

2 3/4/03


#/ 


Committed 


Committed 

1959.1 

368522.2 

2068 

369065 


Title: Flow-Through Local Package - Phase 2 

Description: The goal of the project is to eliminate 7020OS01 NOT A FLOWTHRU USOC @ PGORP & 

PGORS by allowing Local Package to flow through for Resale. 

Business Narrative : Presently, in Resale, if the PGORS & PGORP USOCs are present on a CSR the request 

will receive 7020OS01 NOT A FLOWTHRU USOC @ PGORP & PGORS or V108 NOT A FLOWTHRU USOC 

@ PGORP & PGORS. Both errors need to be eliminated and allow the packages to flow through. Presently, 

in Platform, if the Local Package USOCs are received new, a V108 error is generated to the NMC. This 

should be redirected to the CLEC as “USOC XXXX not eligible for Platform”. 

Comments: Phase 1 was completed in June, 2002 

Reason: Flow through 

Jurisdiction: South; System: LSI, EDI; Primary Area: Resale, UNE-P; LSOG Version: 5 and above 

Documentation Impact: Flow through scenarios 

Title: Lineshare Disconnect Notification 

Description: The purpose of this initiative is to create a process to automatically trigger a service order for 

the wholesale line share service whenever the retail end user initiates a number change or disconnect 

request. Upon completion of the order the CLEC/DLEC should be electronically notified (via Provider 

Notification) to update their records accordingly. 

Business Narrative : This Initiative will include a Verizon initiated LSR when a retail business office order is 

completed to disconnect, change or move the telephone number on a line which has data. The LSR will 

generate a service order to update the CLEC’s records. A Provider Notification report will send the updated 

information to the CLEC. 

Reason: New functionality 

Jurisdiction: North & South; System: Other; Primary Area: UNE; LSOG Version: 5and above 

Documentation Impact: Provider Notification 


Page 10 of 33 

2 2/5/02 

5 3/4/03


#/ 


Committed 

2259.2 

371639.3 


Title: Implement an address validation process (North) & enhance the address validation process (South) 

Description: This phase will implement a previous occupant process for both the North and South and a 

new due date process for additional lines for the South. The previous occupant process allows us to verify 

the status of service at the address that the CLEC provides. If there is no working service, we continue 

processing the request. If there is working service, we check the WSOP to see if the CLEC is requesting an 

additional line. If they are, we process. If not, we will query. If the previous service is "pend out" which 

means a disconnect order was placed, we check to see if the DD of the CLEC order is greater than the DD of 

the disconnect order. If it is, we continue. If it isn't, we check to see if this will be an additional line. If not we 

will query. 

Comments: The scope for this initiative is Resale/Platform, Residence, ACT "N" or "T".. 


Jurisdiction: North & South; System: LSI, EDI; Primary Area: Resale, UNE-P; LSOG Version: 5 and 

above 

Documentation Impact: LSOG 5 & 6 Order Business Rules 


Page 11 of 33 

2 3/4/03


#/ 


Committed 

2397. 

373105 


Title: End User UNE Listing Account Structure 

Description: This initiative includes the conversion of CLEC UNE listing accounts to the new End User 

Listing Account structure using the class of service of LWR (residence) and LYB (business). This will 

provide a retail like listing structure. Due the scope of this project it will be phased across the jurisdiction 

and will include BETA trials. MD, DC and VA BETA trial completed for April release. 

A short summary of rollout is as follows: 

DC, MD, VA, WV 

4/03 - BETA 

6/03 - Additional BETA conversions 

10/03 - Full conversion 

North 

8/03 - BETA 


DE, NJ, PA 

10/03 - BETA 


Reason: Enhancement 

Jurisdiction: MD, DC, VA, WV; System: LSI, EDI; Primary Area: UNE; LSOG Version: LSOG 5 and 

above 

Documentation Impact: LSOG 5 & 6 Pre Order and Order Business Rules and Error Messages 


Page 12 of 33 

4 4/1/03


#/ 


Committed 


Committed 

2498 

371305 

2513 

375306 


Title: Ability to do Line Share on House & Riser 

Description: This initiative provide the ability to provision line share on House & Riser which is an ADSL 

high frequency transition channel between the MDU and the customer premises. Power is not provided 

with LSH&R. LSH&R is only available on distribution pairs that have been previously equipped with VZ 

dial tone and where the high frequency portion of the spectrum is available for ADSL use. 

Reason: The ability of the CLEC to use the high frequency portion of the House and Riser loop is found in 

the UNE Remand Order FCC 99-338. 

Jurisdiction: North; System: LSI, EDI: Primary Area: UNE; LSOG Version; 5 and above 


Title: Call Forward Numbers and Flow Through South 

Description: The purpose of this initiative is to allow migrations on accounts with call forwarding to flow 

through. 


Jurisdiction: South; System: Other; Primary Area: Resale, UNE-P; LSOG Version: 5 and above 



Page 13 of 33 

2 4/1/03 

2 3/4/03


#/ 


Moved from 

4/21/03 to 

Committed 

6/21/03 


Committed 

2545.1 

372086.6 

2551 

375876.1 


Title: Repair Screen Redesign-Phase 6 

Description: This initiative provides for the redesign of the Trouble Administration screens. These design 

changes will have no impact on overall functionality. The URL will not be changing. 

Business Narrative : The Trouble Administration Business Rules must be modified to be in sync with the 

revised Repair interface. The changes to LSI will provide better navigation and a more efficient process for 

creating, modifying, and tracking trouble tickets. In addition, a more accurate and timely status will be 

returned. 


Jurisdiction: North & South; System: Other; Primary Area: Resale, UNE-P, UNE; LSOG Version: NA 

Documentation Impact: RETAS Training Manual for Unbundled and Resold Services, RETAS LSI User 

Guide 

Title: Change flow through to accept the BTN on the loop order. 

Description: CLECs would like flexibility to add new loops to an existing BTN requested on the LSR. (for the 

same end user location). Currently we are receiving new miscellaneous BTNs on our FOCs due to the order 

flowing through the system. If the NMC catches the problem, they correct it before a FOC is sent. If the 

NMC does not see the order, we then need to call the NMC to correct the problem. 

Scope for this project is REQTYP = AB, ACT = C, LNA = N. CLECs will populated the existing loop account 

number in either the BAN1 or BAN2 field. 


Jurisdiction: South; System: LSI, EDI; Primary Area: UNE; LSOG Version: 5 and above 



Page 14 of 33 

4 1/7/03 

5 3/4/03


#/ 


Committed 


Committed 

2554 

375858.1 

2600 

373630.1 and 

373630.2 


Title: Host-Remote Loops 

Description: FGTE in Virginia and Pennsylvania provide some Loop service to CLECs that are served from 

Host/Remote switches. The Remote CLLI is required in order to provision the service properly. This 

initiative will open up the APOT field and a new TOS value to designate a remote CLLI. Remote CLLIs will 

be added to the TOS table in the business rules and a new CLEC edit will be returned if invalid information 

is populated in the APOT field: "Incorrect CLLI in APOT field" 

Reason: Merger 

Jurisdiction: South; System: LSI, EDI; Primary Area: UNE; LSOG Version: 5 and above 

Documentation Impact: LSOG 5 & 6 Order Business Rules, Error Messages 

Title: CLEC to CLEC Migrations and Provider Notifications 

Description: The goal of this project is to fully automate the process for migration of an end user 

unbundled loop from one CLEC to another when VZ is the facilities provider. This change request is in 

agreement with Case # 00-C-0188 phase II of End User Migration Guidelines. In addition this project will 

establish provider notification to the losing CLEC (OLSP). 

Comments: This will care for Type 5, CR2454 - Enhance xDSL Migration 

Business Narrative: This Initiative will include Two Wire Analog Loop to Two Wire Analog Loop, Two 

Wire ISDN Loop to Two Wire ISDN Loop, Two Wire Digital Loop to Two Wire Digital Loop and Lineshare 

(VZ voice and DLEC data) to Lineshare (VZ voice and DLEC data). In addition, this phase covers provider 

notification for OLSP. 

Reason: Conform with NY PSC CLEC to CLEC Guidelines 

Jurisdiction: North & South; System: Other; Primary Area: UNE; LSOG Version: 5 and above 

Documentation Impact: LSOG 5 & 6 Order Business Rules, Provider Notification 


Page 15 of 33 

2 3/4/03 

2 3/4/03


#/ 


Committed 


Committed 


Committed 

2624 

377162 

2625 

377163 

2634 

376795 


Title: Creation of SUP types 4 & 5 

Description: This initiative will add the SUP values of 4 and 5 to VZ East Use of these new supp values 

instead of a supp value of 3 will allow the LSR to flow through. The new values are: 4 - New facility 

assignment and 5-New NC/NCI/SECNCI codes. 


Jurisdiction: North & South; System: LSI, EDI; Primary Area: UNE; LSOG Version: 5 and above 

Documentation Impact: LSOG 5 & 6, Order Business Rules 

Title: Centrex Eligibility for Flow Through 

Description: Currently, there are about 1400 Centrex classes of service, which are not eligible for FT. This 

initiative would allow us to reduce these numbers. 


Jurisdiction: North & South; System: Other; Primary Area: UNE-P; LSOG Version: 5 and above 


Title: Change CSS Designed Loop Intervals from 6 to 5 days, North and South 

Description: The purpose of this initiative is to reduce the interval for CSS Designed Loops from 6 to 5 days 

in VZ East (North & South). 



Documentation Impact: Product Interval Guide 


Page 16 of 33 

2 3/4/03 

2 3/4/03 

2 3/4/03


#/ 


Committed 


Committed 


Committed 

2658 

377796 

2670 

377892 

2694 

377048.1 


Title: Allow the FID DPA to Flow Through on Lineshare requests 

Description: The goal of this project is to improve flow through by processing LineShare request when the 

existing Retail account contains the FID DPA and the line they are adding Lineshare to is not the line 

containing the FIDS. 




Title: Standardize TEL NO Field Data 

Description: This initiative will allow up to 17 characters in the TEL NO field on the LSR form. Currently the 

business rules support up to 17 characters but internal edits only accepted 10. 


Jurisdiction: South; System: Other; Primary Area: UNE, Resale, UNE-P; LSOG Version: 5 and above 


Title: New Hot Cut Non-Recurring USOCs for the State of Delaware 

Description: The purpose of this initiative is to apply a new structure for non-recurring charges for all UNE 

hot cut elements, which will replace the existing NRC rate structure for hot cuts. 

Reason: Regulatory/Billing compliance with tariff 

Jurisdiction: DE; System: Other; Primary Area: UNE; LSOG Version: 5 and above 

Documentation Impact: LSOG 5 & 6, Order Business Rules 


Page 17 of 33 

2 3/4/03 

2 3/4/03 

2 3/4/03


#/ 


Committed 


Committed 

2764 

379402 

2787 

379688.1 


Title: Query for Invalid LTOS 

Description: The goal of this initiative is to ensure that the CLEC is populating the LTOS correctly. 

Reason: Flow through - Metric Impacted: OR-5-01, OR-5-03. 

Jurisdiction: North & South; System: LSI, EDI; Primary Area: UNE, UNE-P; LSOG Version: 5 and above 


Title: LMU PAVA Uniformity Enhancements 

Description: VZ East must implement 3 new fields in the LMU transaction to maintain uniformity with 

changes made to the VZ West Loop Qual for PA. The fields that need to be added to the VZ East LMU 

transaction are LPAC, LSA and RTIND. 


Jurisdiction: North & South; System: LSI, EDI, CORBA; Primary Area: Resale, UNE; LSOG Version: 5 

and above 

Documentation Impact: LSOG 5 & 6 Pre Order Business Rules 


Page 18 of 33 

2 4/1/03 

2 3/4/03


#/ 


Changed from 

Candidate 

4/21/03 to 

Committed 

6/21/03 

2795 

378408.1 


Title: RSCP – Local Service Freeze Implementation for UNE - P 

Description: NJ Regulatory requires the implementation of local service freeze capability for unbundled 

platform customers. This project will implement the product in all remaining states outside of PA. 

Comments: April is the initial phase for NJ; Phase 2 will implement in DE, MD. DC. VA, WV, ME, NH, RI, 

MA. In October 2001, this service was made available in PA on project 360043. After change control review, 

the CLEC's advised they did not want it to be made available and we did not make available except where it 

was mandated. 

With the implementation of this initiative RSCP will not be allowed in the FEATURE field for Platform 

requests. Existing CLEC edit 7030V371 - "Invalid data populated in FEATURE field" will be returned 

Reason: Regulatory Mandate from NJ PSC #14:10-11-16 pgs 10-22 

Jurisdiction: NJ; System: Other; Primary Area UNE-P; LSOG Version: LSOG 5 and above 



Page 19 of 33 

2 2/4/03


#/ 


Committed 

2813 

378605 


Title: Premise Services on ARDU Stand Alone Loop - East 

Description: The goal of this project is to add a new product option “Premise Service Portfolio” for any 

Digital Capable UNE loop. Two scenarios will be used for the DLEC to request a DSLPSP (Premise Service 

Portfolio) for UNE Loops. The first is a Premise Service Portfolio Visit at the same time that Loop is 

requested. The second scenario will be to request standalone request that will only include information 

pertaining to the Premise Service Portfolio Visit and be provisioned after the Loop request has been 

completed. 

• DSL Premise Service Portfolio will be offered in conjunction with DSL-capable UNE loops or as a standalone 

product after the Loop has been provisioned. 4 Wire HDSL will not be part of this offering. 

• The combination of the SAN field and the CCEA field on the LS form will be used to order what is 

needed for the DSL Premise Service Portfolio. 

• 2 New values will be added to the SAN field and 8 new values will be added to the CCEA field on the 

LS form. 

• The current rules for Standalone Premise Service Portfolio will continue to use the LNA = “P” in 

addition to the new values in SAN and CCEA fields only when the LSR is requesting a Digital Loop. 

A dispatch charge will be added to the Standalone request. 

Reason: New product 

Jurisdiction: North & South; System: LSI, EDI; Primary Area: UNE; LSOG Version: 5 and above 



Page 20 of 33 

4 3/4/03


#/ 


Committed 


Candidate 

2828 

380769.1 

2836 

380875.1 


Title: Flow through WSOP=V 

Description: The goal of this project is to allow flow through when the WSOP field on the LSR is populated 

with V. Currently, when the WSOP field =V, the request falls to manual processing. The NMC rep then 

investigates the working service at the address or the invalid address, and per NMC procedures issues the 

order or queries the CLEC. This will initiative will flow through the order and then drop to the NMC for 

investigation. The rep will then be able to correct and release the order rather than type it manually. 

. 


Jurisdiction: South; System: Other; Primary Area: UNE-P, Resale; LSOG Version: 5 and above 

Documentation Impact: LSOG 5 & 6 Order Business Rules (Valid Entry Notes) 

Title: Flow Through – CLT- MDVW Line Sharing on End-User Accounts 




Jurisdiction: DC, MD, VA, WV; System: Other; Primary Area: UNE, Resale, UNE-P; LSOG Version: 5 

and above 



Page 21 of 33 

2 3/4/03 

2 3/4/03


#/ 


Committed 


Committed 

2855 

381335 

2879 

381622 


Title: New process to handle Project V 

Description: This initiative will add edits to control the use of the PROJECT field to allow for optimal 

flowthrough levels. All requests that use the PROJECT field are not eligible for flow through. Currently this 

field is used in many cases when it is not applicable. New CLEC edits are: 

• SR301 – “Use of this PROJECT value is not established” 

• SR302 - "Use of this PROJECT value has expired." 

• SR300 –“Invalid Value Populated in PROJECT field” 

Reason: Flow through - Metric OR501, OR503 

Jurisdiction: North, South; System: Other; Primary Area: Resale, UNE, UNE- P; LSOG Version: 5 and above 

Documentation Impact: Order Error Messages 

Title: Flow Through of SUP’s 1 & 2 when LSR in Jeopardy status 

Description: The purpose of this initiative is when SUP 1 or SUP 2 requests are not processed due to an 

LSR in jeopardy status, this process will provide requirements to ensure the completion of the SUP 1 or 2. 


Jurisdiction: North & South; System: Other; Primary Area: UNE-P; LSOG Version: 5 and above 



Page 22 of 33 

2 4/1/03 

2 4/1/03


#/ 

July 19, 2003 

Changed from 

Candidate 

4/21/03 to 

Candidate 

7/19/03 

2695 

372640 


Title: Line Sharing additional Class of Service Codes 

Description: The purpose of this initiative is to update the list of Class of Services that are now eligible for 

Linesharing. The following is a list of class of service which will now support line sharing and flow 

through: 

PA/DE---1MA, 18H,19A,19H,19Q,19W,1DO,1DU,1UO,1UU 

NJ---1WA,1DO,1DU,1UO,1UU 

MD---19Q,1MA,1DO,1DU,1UO,1UU 

VA---12G,19Q,1MA,1ZA,2EW,1DO,1DU,1UO,1UU 

WV---15Q,19Q,1MA,1DO,1DU,1UO,1UU 

DC---1WA,1DO,1DU,1UO,1UU 

*NY---19G,19T,15U,15S,19W,19Z,19Q,15P,15E,15H,15B 

*NE---1MA,1FY,AL2,19Q,15Q,1UE 

* NOTE: Any of the above Qualified CODES (for NY or NE) that also carry the USOC for "Line Side Answer 

Supervision" (AS8LX) would drop this line to a not qualified status. 

The following Centrex Classes of Service will now support linesharing (North and South) 

UCS, NH2, NH3. 

Reason: Regulatory Complaint from NY PSC 

Comment: CLEC community requests NY PSC Docket Number added to report. Met Tel references a NY 

PSC Order that mandates that any and all features available for line share are also required for Line Splitting. 

Jurisdiction: North & South; System: Other; Primary Area Resale; LSOG Version: LSOG 5 and above 



Page 23 of 33 

2 2/4/03


#/ 

August 16, 


Candidate 

August 16, 


Committed 

2537 

375716.1 

2638 

376773 


Title: Incomplete Firm Order Confirmations (FOC) 

Description: This initiative will increase the number of system driven confirmations which currently require manual 

processing by the NMC. In addition, for confirmations that still require manual intervention, this initiative will 

minimize the amount of information that needs to be added by the NMC. 


Jurisdiction: North, South System: Other; Primary Area: Resale, UNE, UNE-P; LSOG Version: 5 and 

above 


Title: Change NE and NY Hot Cut Intervals to Match South Intervals 

Description: The purpose of this initiative is to bring Hot Cut Intervals in New England and New York in 

parity with Hot Cut Intervals in the South. This only affects NY/NE 2-wire analog loop Hot Cuts. 

For both NY & NE, change current interval calculation to the following: 

1-10 loops = 5 days 

11-20 loops = 10 days 

21+ negotiated 

Reason: System enhancement, Parity issue 

Jurisdiction: North; System: Other; Primary Area: UNE; LSOG Version: 5 and above 

Documentation Impact: Product Interval Guide 


Page 24 of 33 

5 5/6/03 

4 5/6/03


#/ 

August 16, 


Moved from 

Candidate 

6/21/03 to 

Candidate 

8/16/03 

2814 

380523 


Title: Edit for Bill Section when EATN is required on AB requests 

Description: This project will create an upfront edit for the bill section when the EATN is required. 

Currently the EATN field is required for certain type of AB request. However, if the entire end user bill 

section is missing, the EATN edit is not enforced. The request then flows through with missing information 

and is eventually dropped to the NMC for manual processing. This will create an upfront edit for the Bill 

Section eliminating the need for the NMC to manually error back to the CLEC. 

No additional field edits will be corrected. This will only fix an existing edit to ensure of correct processing. 





Page 25 of 33 

2 3/4/03


#/ 

October 18, 


Moved from 

Candidate 

6/21/03 to 

Candidate 

10/18/03 

October 18, 


Moved from 

Candidate 

6/21/03 to 

Candidate 

10/18/03 

2552.2 

369105.5 

2735 

372847.3 


Title: Packet Switching at the Remote Terminal Service (PARTS), Release 2 

Description: This initiative will establish two new speeds for PART products. This initiative will also define 

the acceptable range of VPI1/VCI1. Implement two additional speeds (768k, 768k and 7100k, 768K) for all 

PARTS products and provide a standard range of values for VPI1/VCI1. 

Reason: New Product 

Jurisdiction: North & South; System: LSI, EDI; Primary Area: UNE, UNE-P; LSOG Version: 5 and above 


Title: Establish XML Business Rules for Trouble Administration 

Description: This request is being submitted to establish a new set of Business Rules for CLECs who will 

access Trouble Admin services via the web using XML. 

Comments: This initiative will care for Type 5 CR1102, Application to Application interface for UNE Loop 

Trouble Administration. the XML Pilot - CR 1102, 372847.2 (Type 5) will be extended adding additional 

functionality for June. There is only one CLEC participating in the pilot - Broadview. There is no Business 

Rules impact resulting from the new functionality in June. 

CR 2735, which was submitted for the new XML Bus Rules for 372847.3 to provide full functionality for all 

transactions has been moved from June to October. The new Business Rules deliverable is now moved to 

October as well. 

Reason: Industry Standard 

Jurisdiction: North & South; System: XML; Primary Area: UNE, Resale, UNE-P; LSOG Version: 5 and 

above 

Documentation Impact: Business Rules for Trouble Administration Web Servers for TML 


Page 26 of 33 

4 3/4/03 

3 3/4/03


#/ 

October 18, 


Moved from 

Candidate 

6/21/03 to 

Candidate 

10/18/03 

December 20, 


Moved from 

Candidate 

6/21/03 to 

Candidate 

12/20/03 

2775 

379437.2 

2823 

380802 


Title: LSI-LSR Processing Redesign 

Description: The purpose of this change will make the LSR Processing more dynamic and greatly enhance 

the CLECs ability to process LSRs. The way LSRs are processed will be re-engineered to be more user 

friendly. 

Comments: Phase 1 of this initiative was completed in October 2002 under 376010. 

Reason: System Enhancement 

Jurisdiction: North & South; System: LSI; Primary Area: UNE, Resale, UNE-P; LSOG Version: 5 and 

above 

Documentation Impact: LSI Users Guide 

Title: TD7 valid as a Block entry only 

Description:. This initiative is to prevent the Clecs/Resellers from ordering TD7 in the Feature Field. The 

Feature needs to be provisioned with BLKD A and by having it appear in the Feature Field, it is not 

correctly processed for flow through. 


Jurisdiction: South; System: Other; Primary Area: UNE-P, Resale; LSOG Version: 5 and above 



Page 27 of 33 

4 7/2/02 

2 3/4/03


#/ 

Withdrawn 

4/2/03 

October 18, 


Moved from 

Candidate 

6/21/03 to 

Withdrawn 

Not Scheduled 

Moved from 

Candidate 

6/21/03 to Not 

Scheduled 

2835 

380874 

2876 

372344.1 

2769 

371249 


Title: Flow through– CLT- fid NPD-Line Share End-User Accounts 




Jurisdiction: DE, NJ, PA; System: Other; Primary Area: UNE, Resale, UNE-P; LSOG Version: 5 and 

above 


Title: PA Uniformity - Listings 

Description: With the merger of Bell Atlantic (Verizon-East) and GTE (Verizon-West), a merger commitment 

requires fGTE PA and fBA PA to reside on a common OSS Platform by June 2003. This initiative will 

address additional FIDs & USOCs that need to be cared for in the Business Rules and applications. 

Changes include new or revised use of the following fields: LTXNUM, DLNUM, NICK and LALO, new or 

revised use of values LOI, URL and EM for the LTXTY field, and creation of a new group to better support 

multiple occurrence of the LTXTY, LTEXT fields. 

Reason: Regulatory/Merger Agreement 

Jurisdiction: fGTE PA; System: LSI, EDI; Primary Area: Resale, UNE, UNE-P; LSOG Version: 5 and 

above 

Documentation Impact: LSOG 5 & 6 Order Business Rules, Error Messages 

Title: Flowthru Centranet PIC changes and Disconnects 

Description: Verizon will flowthru PIC changes and Disconnects of Centranet service for fGTE PA 

jurisdictions. 

Reason: Regulatory/Merger compliance 

Jurisdiction: PA; System: Other; Primary Area: Resale; LSOG Version: 5 and above 



Page 28 of 33 

2 3/4/03 

2 4/1/03 

2 3/4/03

CR 

Number 

VERIZON EAST ERROR CODES FOR ITEMS BY RELEASE REPORT 

Initiative Title LSOG Change/New Error Code # Error Code Message 

June Release 

1472 Revise ISDN Platform Process - 

SPEC/TOS 

5&6 New SR096 SPEC field required for Platform Product 

1472 “ 5&6 New SR097 ISDN-BRI ORDERING CODE NOT AVAILABLE AT THIS 

TIME. 

1472 “ 5&6 Change SR043 The 1 st character is required, the 2 nd character must = “C”, 

“D”, “E”, “H”, “K”, “J”, “T” or “-“, and 3 rd character must = 

“A”, “B” or “-“, and 4 th character must =”F”, “R" or “-“, 

when the LNA field on the PS form is “N” and the REQTYP = 

DB. 

2068 Lineshare Disconnect 

Notification 

6 Change LS003 When ACT = C, this field must = N, C, D, P or R. 

2259 Implement an address 5&6 New EU080 Optional when ((the first character of the LSR REQTYP = “E” 

validation process (North) & 

or D”) and (((the LSR ACT = “C” or “V”) and (the PS LNA or 

enhance the address validation 

RS LNA = “N” or “X”)) or ((the LSR ACT = “C”) and (the PS 

process (South) 

LNA or RS LNA = “C”) and (the PS OTN or RS OTN is 

populated))). 

2259 “ 5&6 New EU080 Otherwise prohibited. 

2259 “ 5&6 Change 7071LW45 TN disconnect more than 30 days assign new TN 

2259 “ 5&6 Change EU080 (Field) optional when the SASN field is populated. 

2498 Ability to do Line Share on 5&6 New 7030Z807 CCNA:XXX not established for Line Share House and Riser 

House & Riser 

Service 

2498 “ 5&6 New EU016 "House and Riser Lineshare not available XXXXSTATE 

2498 “ 5&6 Change LS019 Prohibited in "NY" if the 2nd char of TOS = "6" or "Z" of the 

LSR.SLI = "H", otherwise optional. 

2498 “ 5&6 Change LS022 Required when the LSR.SLI = "H" and the 2nd character of 

the LSR.TOS = "1", otherwise optional. 

2498 “ 5&6 Change LS038 CBCID1 required when ((the LNA field on the LSR Form is 

equal to "N" or "V" and SLI field on the LSR Form = "B" and 

the 2nd character of the TOS field on the LSR Form = "1", 

"2", "3", "4" or "R") or (the LNA field on the LS Form is 

equal to "N" or "V" and the SLI field on the LSR Form "H" 

and the 2nd character of the TOS field on LSR Form = "R")). 


Page 29 of 33

CR 

Number 


2498 “ 5&6 Change LS038 CBCID1 is optional when (the LNA field = "C" and the SLI 

field on the LSR "1", "2", "3", "4" or "R"). 

2498 “ 5&6 Change LS038 Otherwise prohibited. 

2498 “ 5&6 Change LS039 Required when (the LS.LNA = "N" or "V" and LSR.SLI = "B" 

and the 2nd character of the LSR.TOS = "3" or "4". 

2498 “ 5&6 Change LS039 Optional when (the LSR.LNA = "C" and the LSR.SLI = "B" 

and the 2nd character of the LSR.TOS = "3" or "4"). 

2498 “ 5&6 Change LS039 Otherwise prohibited. 

2498 “ 5&6 Change LSNP009 Prohibited in "NY" if the 2nd char of the TOS = "6" or "Z" or 

the LSR.SLI = "H", otherwise optional. 

2498 “ 5&6 Change LSNP011 Required when the LSR.SLI = "H" and the 2nd character of 


2498 “ 5&6 Change LSNP012 Required when the LSR.SLI = "H" and the 2nd character of 


2498 “ 5&6 Change SR035 Required when the first position of the REQTYP is "A" and 

the ((ACT = "N","T" or "V" or ACT = "C" and LNA on LS 

form = "N") and 2nd char of TOS = "1", "2", "3", "4", "P", 

"R", "W", "X") and (the SLI on the LSR Form is NOT equal 

to "H")). 

2498 “ 5&6 Change LS021 Required when the LSR.SLI = "H" and the 2nd character of 


2551 Change flowthrough to accept 

the BTN on the loop order 

5&6 New 7070UA63 INCORRECT BAN FOR CLASS OF SERVICE 

2554 Host Remote Loops 5&6 New SR188 (LSR:A4) Access Customer Terminal Location A4 Required 

when the LSR Form APOT field is populated. 

2554 “ 5&6 New SR189 (LSR:B2) Additional Point of Termination B2 required (when 

REQTYP = AB & (ACT = N, V or (ACT = C & any 

LS.LNA=N)) & 3rd TOS = R & LSR is a fGTE VA LSR. 

2554 “ 5&6 New SR189 (LSR:B2) Additional Point of Termination B2 required when 

REQTYP = BB & ACT= V & 3rd char TOS = R & LSR is a 

fGTE VA LSR). 

2554 “ 5&6 New SR189 Otherwise prohibited. 


Page 30 of 33

VERIZON EAST ERROR CODES FOR ITEMS BY RELEASE REPORT (cont'd) 

CR 

Number 


2554 “ 5&6 New SR190 (LSR:L5) Network Channel Code L5 Required when the LSR 

Form APOT field is populated. 

2554 “ 5&6 New SR191 (LSR:L6)Network Channel Interface Code L6 Required when 

the LSR Form APOT field is populated. 

2554 “ 5&6 New SR192 (LSR:Q2) Secondary Network Channel Interface Code Q2 

Required when the LSR form APOT field is populated. 

2600 CLEC to CLEC End-User Loop 

Migration 

5&6 New LS065 Required when the first position of the REQTYP field is “A” 

and the LNA field = “W”, Otherwise prohibited. 

2600 “ 5&6 New LS066 Required when the RL field on the LS Form is populated, 

otherwise prohibited. 

2600 “ 5&6 New 7020SC37 Existing CLEC is not the same for all Circuits 

2600 “ 5&6 Change LS002 When ACT = V, this field must = D, N, V, or W 

2600 “ 5&6 Change LS006 (Field) required when the LNA field = “N”, “V” or “W” and 

the 2 nd char. of TOS = 1,2,3,4,6,7,8,9,0, R,U,V,W or X. 

2600 “ 5&6 Change LS017 Required in Verizon South when LNA = “N”, “V” or “W” and 

SLI = S, V and ((2 nd char of TOS = “1”, “2”, “3”, “W” or “X”) 

or (2 nd char of TOS = “4” and 3 rd char of TOS = “4” or “9”)) 

2600 “ 5&6 Change LS018 Required when ((the LNA field = “N”, “V” or “W”) and (the 

LSR SLI = “S” or “V”) and ((the 2 nd char of the LSR TOS = 

“1”, “2”, “3”, “W” or “X”) or when (the 2 nd char of the LSR 

TOS = “4” and the 3 rd char of the LSR TOS = “4” or “9”))). 

2600 “ 5&6 Change LS045 Required when the LNA field = “N”, “V” or “W” and the 2 nd 

character of the LSR.TOS = “F” or “R” or “P” and the 

LSR.SLI = “S” 

2600 “ 5&6 Change LS047 Required when the LNA field = “N”, “V” or “W” and the 2 nd 


Page 31 of 33 

character of the LSR.TOS = “F” or “R” or “P” and the 

LSR.SLI = “S.

VERIZON EAST ERROR CODES FOR ITEMS BY RELEASE REPORT (cont'd) 

CR 

Number 


2600 “ 5&6 Delete SR115 ACT = “V” not allowed when 2 nd char of TOS = “W” or “X” 

or 3 rd char of TOS = “2”,”3”,”4”,”6”. 

2624 Creation of SUP Types 4 & 5 5&6 New SR193 (LSR:R1) Supplement Type R1 if SUP= "4" or "5", then 

REQTYP must = "AB" or "BB" and SLI = "S". 

2624 “ 5&6 New SR194 "Shelf, Slot, Relay Rack not changed SUP = 4". 

2624 “ 5&6 New SR195 "NC/NCI not changed SUP =5". 

2694 New Hot Cut Non-Recurring 

USOCs for the State of 

Delaware 

5&6 Change SR011 Required when ((the first position of the REQTYP field is 

"A", "B" or "M") and (the ACT field = "V") and ((the 2nd 

character and 3rd character of the TOS field = "1-", "15", 

"35" or "49") and the SLI field is not equal to "B")). 

2764 Query for Invalid LTOS 5&6 New PS103 (PS:MA) Line Type of Service MA Invalid TOS & LTOS 

combination. 

2813 Premise Services on ARDU 

Stand Alone Loop 

5&6 New LS067 (LS:DQ) Subscriber Authorization Number DQ Valid value 

"K", "KL", "LK" prohibited when 2nd character of TOS field 

on the LSR Form is "R". 

2813 “ 5&6 New LS068 (LS:DQ) Subscriber Authorization Number DQ Valid value 

"A", "B", "C", "D", "E", "F", "G", "H", "J" prohibited when 

valid value "K", "KL", "LK" present. 

2813 “ 5&6 New LS069 (LS:DQ) Subscribe Authorization Number DQ Valid Value 

"L" prohibited as a sole entry. 

2813 “ 5&6 New LS070 (LS:MS) Cross Connection Equipment Assignment MS 

Required when the SAN field = "K", "KL" or "LK", 

Otherwise prohibited. 

2813 “ 5&6 Change SR132 (LSR:S4) Type of Service S4 a value of "R" in the 2nd char or 

a value of "21" or "22" or "23" or "24" or "26 or "W-" or "X-" 

in the 2nd and 3rd char is required when the LNA field on the 

LS form equals "P". 

2855 New Process to handle Project 

V 

5&6 New SR300 XXXX - "Invalid Value Populated in PROJECT field". 

2855 “ 5&6 New SR301 XXXX - "Use of this PROJECT value is not established". 

2855 “ 5&6 New SR302 XXXX - "Use of this PROJECT value has expired". 


Page 32 of 33

Prioritization Working Group 

WNS OSS Interface Change Management Process 

May 13, 2003 Logistics and Agenda 

Logistics 

Time: 1:00 PM – 3:00 PM 

Place: 1095 Avenue of the Americas, New York 

Room: Floor 26, Room 36 

Bridge: (312) 461 - 9457 

Chair: Tom Rodgers 

Agenda 

I) Review April 2003 Meeting Summary notes 

II) Review new, not rated, and re-rated Change Requests 

III) Status update on existing Change Requests (see Status/Comments column) 

IV) Change Control Items for April 2003 through August 2003 

April 8, 2003 Meeting Summary 

Participants 

The participants included Allegiance, AT&T, Broadview, Cat Communications, Cavalier, 

Choice One, Covad, Cox, CTSI, MetTel, One Communications, Penn Telecom, Remi Telecom, 

Talk America, Worldcom, Z-Tel, and VarTec. 

Intent 

• Discuss and rate the new, not rated, and re-rated Change Requests. 

• Discuss the order of the prioritization spreadsheet, which is based upon the CLEC CR ratings 

from the previous working group session. 

• Provide updated information for a number of Change Requests. 

Materials 

• Prioritized spreadsheet of unscheduled Type 4 and Type 5 Change Requests based upon the 

CR ratings from the previous working group session 

• New Change Requests as provided by the initiating CLEC (Type 5) or Verizon (Type 4) 

April 8, 2003 Summary 

• Please Note: Those CLECs who participate in the meeting will prioritize the Change 

Requests. 

• New and not previously rated Change Requests were described by the initiator and rated by 

the participants (if no clarification was needed). Updates are provided when available or not 

reflected in the meeting material. Attached is an updated spreadsheet, which reflects how 

CLECs ranked each Change Request. 

May 6, 2003


• Change Request spreadsheets are listed in order from highest ranking to lowest ranking, then 

by date received, and separated by Type 5 System Impacting and Non-System Impacting, 

and Type 4 System Impacting. 

• New Change Requests will be distributed with the PWG meeting materials if the change 

request is received before the meeting materials are distributed (normally one week prior to 

the meeting date). Verizon will provide a written assessment (bottom fields on Type 5 

Change Request form) if the change request is received 2 weeks prior to the meeting date. 

Otherwise, a verbal assessment of the new change request is provided at the PWG meeting. 

• Mike Toothman continues to reiterate that Verizon will work to get as many Type 5 change 

requests implemented as possible. Upcoming projects such as CLEC to CLEC Migrations 

and Line Splitting will utilize project capacity. 

Change Request Summary 

5 CRs were added and/or deferred and are attached: 

C03-0723: Add Trouble Ticket/PON information to BDT 

C03-0571: RETAS Screen Enhancements 

2889: Change their bill format to include the CKL information for analog loops on UNE- 

L bills on the CSRs 

2811: ALI Code Spreadsheet Upgrade 

2815: AOS Form for CLEC to CLEC Migrations 

3 CRs were deleted: 

2896: CSR DSL Provider Identification Status - Voice service provider identified by 

UNN1 SPEC (Code) in North Region by AECN in S Region by ACNA. Withdrawn by 

originator. 

2883: Allow CLECs to be billed for recreation of billing data - Withdrawn by the 

originator. 

2904: CSR Template - Withdrawn by originator. 



Explanation of Change Request Status 

• NOT RATED – Change request has not been rated by the industry 

• NEW – Change request has been rated by the industry, requirements have not been 

developed 

• ON HOLD – Change request is being reviewed and feasibility of implementation being 

determined 

• REQUIREMENTS PENDING – Requirements are actively being worked, working with 

CLECs to obtain agreement, internal meetings being held 

• PENDING SCHEDULING – Requirements are complete and final, change request is waiting 

for scheduled release date 

• SCHEDULED MONTH YEAR – Change request has been committed to a release date 

Change Request Rating Rules 

The following information has been extracted from the Change Management Process, Version 

2.0, and can be used as easy reference for rating new change requests. 

• The initiating TC must participate at PWG meetings to review new change request(s). New 

change request(s) will not be reviewed at PWG meetings until the initiating TC participates. 

If the initiating TC is not represented at two consecutive PWG meetings, the request will be 

canceled and removed from the Not Rated list unless another TC champions the change 

request. 

• Each TC is allowed one vote and should have one representative responsible for providing a 

rating. Each participating TC can only assign a rating to a change request at the PWG 

meeting. A rating will not be accepted outside of the PWG meeting (e.g., via e-mail, etc.). 

• TCs may only provide a rating at the PWG meeting where the new change request is 

introduced to the PWG. TCs that were not present at that meeting may not submit ratings at 

subsequent meetings. 

• TCs can defer/pass on voting. Ratings of defer or pass will not be averaged in the overall 

rating. If a rating is received subsequent to the meeting after a deferral is requested, the 

average rating will be adjusted accordingly. 

• For change requests that are to be re-rated, all TCs participating at the subsequent PWG 

meeting can submit a rating. TCs that fail to attend a PWG meeting when a re-rate occurs 

will not have an opportunity to re-rate the change request. The initial rating for that TC will 

be carried forward. 

• TCs can request an addendum or modification to a new change request, if agreed to by the 

originating TC. The originating TC or TC requesting the addendum must re-submit the 

change request, if an addendum or modification is agreed upon. TCs will be allowed to rate 

the new change request prior to the addendum or modification, provided the addendum or 

modification is clearly conveyed at the PWG meeting. 

• TCs may co-sponsor a change request. 

• Each participating TC ranks each change request by providing a rank from 1 (low) to 5 (high) 

based on the following criteria: Interface Usability, Benefit to TCs, Productivity Impact, 

Cost/Expense to Develop and Operate, LSOG or other Industry Guideline Conformity. 


Rating Breakdown 

Rating System 

Impacting 



Non-System 

Impacting 

4.0-5.0 32 0 

3.0-3.9 11 0 

2.0-2.9 1 0 

1.0-1.9 0 0 

Not Rated/Re-Rated 4 1 

Cancelled/Withdrawn in 2003 (T5) 4 0 

Implemented/Completed in 2003 (T5) 4 0 

Cancelled/Withdrawn in 2002 (T5) 17 2 

Implemented/Completed in 2002 (T5) 27 0 

Total 100 3 

High Priority (CRs with a rate greater than or equal to 4) 

1 2601: Standalone Digital UNE Loop Outside Moves through a Single Order Process (5.0) 

2 2611: Outside Moves for Shared Services (5.0) 

3 2711: Same Day Pair Changes (5.0) 

4 2738: Electronic completion notification on (5.0) 

5 2731: Special Characters (5.0) 

6 2805: Linesplitting Data Migrations - East (5.0) 

7 2139: ALI Code on Directory Listing Response (4.9) 

8 2454: Line Share Migration (4.9) 

9 2785: Create RSU Flag in Loop Qualification (4.9) 

10 2304: Jeopardy for facility Notice Transactions (4.8) 

11 2068: Provide feed to CLEC when a disconnect/seasonal suspend/move is initiated for 

customer with line sharing (4.6) 

12 2266: Expand ALI Code – 6 Characters (4.6) 

13 2537: Incomplete FOC (4.6) 

14 2602: DS0 UNE Loop Interval to 5 Days (4.6) 

15 2691: 2 Day Line Sharing Interval (4.6) 

16 2773: Improved Loop Qual with DLC (4.6) 

17 2775: LSI (Local Service Interface) LSR Processing Redesign (4.5) 

18 2772: Timely Update to bulk Loop Qual (4.5) 

19 1891: Enhance the CRIS CSR Response to parse Complex services into fielded response 

format (4.4) 

20 2460: Line Station Transfer Notification (4.4) 

21 2522: Electronic notification of pre-cut jeopardies (4.4) 

22 2680: CNR Additional Notification (4.4) 

23 2771: Additional Bulk Pre Qual Info (4.4) 

24 2860: Provide an electronic delivery method for Customer Service records that exceed the 

10K line restriction (4.3) 

25 2715: Type 4 – 11 Digit CLLI (4.3) 

26 2894: POTS Reuse for T1 Service (4.2)


27 2353: Ability to Query Against ILEC Pending Activity (4.1) 

28 2354: Accept LSR on Account with Pending Inward Activity (4.1) 

29 2551: Flow through to accept BTN on Loop orders (4.1) 

30 2579: Directory Listing USOCs on Summary Billing (4.1) 

31 2545: RETAS Screen Redesign-Phase 4 (4.1) 

Documentation Release Dates 

Documentation February June October 

2003 2003 2003 

Draft Business Rules (73 days) 12/05/2002 04/10/2003 08/07/2003 

Draft Technical Specifications (66 days) 12/12/2002 04/17/2003 08/14/2003 

Final Business Rules & Error Messages (45 days) 01/02/2003 05/08/2003 09/04/2003 

Final Technical Specifications (45 days) 01/02/2003 05/08/2003 09/04/2003 

Final Technical Specifications (45 days) 01/02/2003, 5/08/2003, 9/04/2003 

Scheduling and Implementation History of CLEC Rated Type 4/5 Change Requests by 

Release 

Release Date Type 4 

Scheduled/ 

Committed 


Type 5 

Scheduled/ 

Committed 

Type 4 

Implemented 

Type 5 

Implemented 

January 20, 2002 1 0 

February 17, 2002 1 7 

April 21, 2002 0 4 

May 19, 2002 0 1 

June 16, 2002 3 7 

August 18, 2002 0 1 

October 20, 2002 5 5 5 5 

November 17, 2002 0 0 0 0 

December 22, 2002 1 2 1 2 

February 2003 2 4 1 4 

March 2003 1 0 1 0 

April 2003 0 0 0 0 

Unassigned 7 31

Rank CR#/ 

Type 

0 C03- 

0571 

Type 5 

0 C03- 

0723 

Type 5 


Not Rated/Re-Rated System Impacting Change Requests – Type 4 & 5 

Description of CR CLEC Ratings Status/Comments 

Title: RETAS Screen Enhancements 

Description: The purpose of this initiative is to add RETAS Screen Enhancements 


Process: Trouble Maintenance; Jurisdiction: North & South; System: EDI, LSI 

Primary Area: UNE Loop, Resale, UNE-P; LSOG Version: NA 

Initiator: Alan Rothenstreich, New York Telsave , 3/31/03 

Title: Add Trouble Ticket/PON information to BDT 

Description: The purpose of the initiative is to pass the trouble ticket number and 

/or PON, thru to the Wholesale BDT files and populate on the 103005 OC&C record 

when a repair charge is billed. 

Reason: 

Process: Billing; Jurisdiction: North; System: Other; Primary Area: UNE Loop, 

Resale, UNE; LSOG Version: NA 

Initiator: Arthur Barone, Jr., Broadview Networks, 5/2/03 


Overall = 

Allegiance = 

AT&T = 

Broadview = 

Cavalier = 

Choice One= 

Covad = 

Cox = 

CTSI= 

Met Tel = 

TalkAmerica= 

VarTec = 

Worldcom= 

Z-Tel = 

Overall = 

Allegiance = 

AT&T = 

Broadview = 

Cavalier = 

Choice One= 

Covad = 

Cox = 

CTSI= 

Met Tel = 

TalkAmerica= 

VarTec = 

Worldcom= 

Z-Tel = 

STATUS: NOT RATED 

5/6/03 Added to list. 


5/6/03 Added to list.

Rank CR#/ 

Type 

0 2889 

Type 5 

0 2811 

Type 5 


Not Rated/Re-Rated System Impacting Change Requests – Type 4 & 5 


Title: Change bill format to include the CKL information for analog loops on UNE- 

L bills on the CSR 

Description: The purpose of this initiative is to change CLECs bill format to 

include the CKL information for analog loops on UNE-L bills on the CSRs. So the 

bills can be processed in CLEC’s systems. A solution is to add the CKL information 

to the CSR similar to the format for the MDVW and Verizon North UNE-L bills. 

Process: Billing; Jurisdiction: DE, NJ, PA; System: EDI, LSI 

Primary Area: UNE Loop; LSOG Version: 5 and above 

Initiator: Joyce Atwell, AT&T, 3/10/03 

Title: ALI Code Spreadsheet Upgrade 

Description: The Ali code spreadsheet provided by Verizon does not supply CLECs 

with required information to accurately complete directory listing service orders. 

The solution will be to add an additional column to the current spreadsheet which 

will indicate the directory. 


Process: Order, Pre -Order; Jurisdiction: North, South System: EDI, LSI, CORBA 

Primary Area: UNE, Resale, UNE-P; LSOG Version: LSOG 5 and above. 

Initiator: Rebecca Baldwin, Adelphi Business Solutions, 1-20-03 


Overall = 

Allegiance = 

AT&T = 

Broadview = 

Cavalier = 

Choice One= 

Covad = 

Cox = 

CTSI= 

Met Tel = 

TalkAmerica= 

VarTec = 

Worldcom= 

Z-Tel = 

Overall = 

Allegiance = 

AT&T = 

Broadview = 

Cavalier = 

Choice One= 

Covad = 

Cox = 

CTSI= 

Met Tel = 

TalkAmerica= 

VarTec = 

Worldcom= 

Z-Tel = 


4/8/03 The CLECs consider this a Type 3 - 

compliance with standard. To be reviewed 

with Verizon billing. 

STATUS: HOLD 

2/11/03 - The Directory Listing Query can 

be used pre and post LSR to obtain DL 

information. Reliance on the ALI code 

spreadsheet can thus be eliminated. CLEC 

will reassess need. 

LOE= High 

2/4/03 New to list.

Rank CR#/ 

Type 

0 2815 

Type 5 


Not Rated/Re-Rated Non-System Impacting Change Requests – Type 4 & 5 


Title: AOS Form for CLEC to CLEC Migrations 

Description: The AOS form that the Verizon requires for the Resale, as-is migration 

of contracted services must be modified in order to apply to the situation where the 

end-user is migrating from one CLEC to another CLEC. Verizon is currently 

requiring that the OLSP, as opposed to the end-user, sign the AOS form as the 

“Assignor”, prior to allowing the migration order to go through. The language on 

the AOS, as it stands today, is not appropriate for this type of transaction. The terms 

that the “Assignor” is agreeing to make sense when an end-user is the “Assignor” 

but are totally unacceptable for a CLEC to agree to as the “Assignor”. 

. 


Process: Order; Jurisdiction: NY; System: EDI, LSI 

Primary Area: Resale; LSOG Version: LSOG 5 and above. 

Initiator: Sadia Mendez, McGraw Communications, 1-27-03 


Overall = 

Allegiance = 

AT&T = 

Broadview = 

Cavalier = 

Choice One= 

Covad = 

Cox = 

CTSI= 

Met Tel = 

TalkAmerica= 

VarTec = 

Worldcom= 

Z-Tel = 

STATUS: HOLD 

2/11/03 - Verizon agrees the Assignment 

of Services (AOS) form requires 

enhancement to address CLEC to CLEC 

assumption of liability for centrex services 

with a termination liability. The 

recommendation is to first enlist Account 

Management and Contract Negotiations to 

create language possibly within the 

Interconnection Agreement to address this 

circumstance. The CR will remain open 

and unrated. 

2/4/03 New to list.

Rank CR#/ 

Type 

1 2601 

Type 5 

2 2611 

Type 5 


Prioritization of System Impacting Change Requests – Type 4 & 5 


Title: Standalone Digital UNE Loop Outside Moves through a Single Order 

Process 

Description: CLECs cannot process change orders when an end user moves to a 

new address in the same serving central office district. This can be done on retail 

POTS service 

Process: Order; Jurisdiction: North, South System: Other Primary Area: UNE; 

LSOG Version: LSOG 5 and above 

Initiator: Mike Clancy, Covad, 6/27/02 

Title: Outside Moves for Shared Services 

Description: Currently CLECs cannot process change orders when an end user 

moves to a new address in the same serving central office district. For loops with 

shared service, all move activity must be managed by the DATA CLEC. The voice 

CLEC or ILEC, should notify the end user to generate the activity through the 

DATA CLEC. Elements of the migration process should be used to facilitate 

outside moves. The CLEC ordering the service should first perform loop 

qualification to assure the service is viable at the new address and then issue a 

change order to move the service to the new address. 

Process: Order Jurisdiction: North, South System: LSI, EDI, CORBA Primary 

Area Line Sharing, Line Splitting; LSOG Version: LSOG 4and above 

Initiator: Michael Clancy, Covad, 7/17/02 


Overall = 5 

Allegiance = P 

AT&T = P 

Broadview = P 

Cavalier = P 

Choice One=P 

Conversent= P 

Covad = 5 

Cox = P 

CTSI= P 

Met Tel =5 

Qwest= P 

TalkAmerica=P 

VADI = 5 

Worldcom=P 

Z-Tel = P 

Overall = 5 


AT&T = 5 

Broadview = P 

Choice One= P 

Covad = 5 

Cox = P 

MetTel = 5 

Qwest= 5 

TalkAmerica=P 

Z-Tel = P 

STATUS: HOLD 

7/9/02 – Rated by CLECs 

7/2/02 – New to list 

STATUS: HOLD 


8/13/02 – Initiator/representative not 

present; hold for September meeting 

8/13/02 – LOE=High 

8/6//02 – New to list

Rank CR#/ 

Type 

3 2711 

Type 5 



Title: Same Day Pair Changes 

Description: Currently when a hot cut is scheduled and a NDT condition on one or 

more lines cannot be resolved, the CLEC is required to send a supp, changing the 

affected pair (s). The only option to the standard 5 day interval for this type of 

change is a cumbersome escalation process to the NMC and RCCC to get 

management personnel to push the request through. We would like an automated 

process that will update CFA information quickly without management intervention. 

Process: Order; Jurisdiction: North, South; System: Other Primary Area: UNE- 

Hot Cut; LSOG Version : 5 and above 

Initiator: Loriann Ercan, Allegiance Telecom, 10/18/02 


Overall = 5.0 

Allegiance = 5 

AT&T = 5 

Broadview = 5 

Cavalier = 5 

Choice One= 5 

Conversent=5 

Covad = 5 

Cox = 5 

CTSI= 5 

Met Tel = 4.5 

MetroTelconnct=P 

OneCom=5 

TalkAmerica=P 

Worldcom= 5 

STATUS: NEW 

11/12/02 – Rated by CLECs; LOE = Low 

11/5/02 – New to list

Rank CR#/ 

Type 

4 2738 

Type 4 



Title: Electronic completion notification on IDD 

Description: The ILEC systems need to generate an electronic completion 

notification on ILEC Date Due (IDD, not IDD+1). In order to meet on time 

provisioning from the day the customer calls for DSL, the PCN needs to be received 

on IDD. If the IDD and Service Ready Date (SRD) are the same day, the CLEC can 

still meet the commitment to the customer if the PCN is transmitted on that day. 

Also, the customer who has an IDD after the SRD will not have to wait as long for 

service if the PCN is transmitted on IDD. 

. 

Process: Order Jurisdiction: North, South; System: EDI, LSI Primary Area: 

All Products; LSOG Version: 5 and above 

Initiator: Melissa Brill/Karen duBourg, VADI 


Overall = 5.0 

Allegiance =4.5 

AT&T = 5 

Broadview =5 

Cavalier = 5 

Choice One=5 

Conversent=5 

Covad = 5 

Cox = 5 

Met Tel = 5 

MetroTelecnnct =5 

OneCom=P 

TalkAmerica=P 

Worldcom= 5 

STATUS: NEW 


11/12/02 – Rated by CLECs; changed 

Primary Area to “All Products” 


Rank CR#/ 

Type 

5 2731 

Type 5 



Title: Special Characters 

Description: For all Order & Pre Order functions, at a field level of detail, 

identify any applicable special characters. This would be effective for both CLEC to 

VZ and VZ to CLEC transactions. The change request would be effective for EDI – 

Ordering and EDI & CORBA for Pre Order. 

For fields that contain or edit against special characters, VZ would identify the data 

characteristics as A/N/S and would include any applicable special characters. 

This change request could be implemented in a phased approach whereby high 

usage Order & Pre Order forms or functions would be prioritized over low usage 

forms or functions. 

Process: Order, Pre-Order Jurisdiction: North, South; System: EDI, CORBA 

Primary Area: Resale, UNE, UNE-P; LSOG Version: LSOG 5 and above 

Initiator: David Burley, Worldcom; Mary Halpin, AT&T, 10/30/02 


Overall = 5 


AT&T = 5 

Broadview = 5 

Cavalier = 5 

Choice One= 5 

Covad = 5 

Cox = 5 

Met Tel = 5 

TalkAmerica= 

5 

VarTec = 5 

Worldcom= 5 

Z-Tel = 5 

Mcgraw = 5 

NOS Com=5 

STATUS: PENDING SCHEDULING 

5/6/03 Candidate October 2003. 

3/4/03 LOE=Medium 

2/4/03 – Production impacting discussion 

around use of “asterisk ” and “pipe” as 

EDI delimiter. Vz EDI will adapt to 

delimiter used by CLEC in our response. 

This may help issue where * appears in 

data. CLECs asked to prioritize forms or 

fields for investigation. 

1/14/03 - Rated 

12/10/02 – Provide M. Halpin with 

estimated date of when this can be 

completed. 

11/12/02 – CLECs suggested this should 

be handled as a Type 1 CR; maintenance 

issue for the Business Rules. 


Rank CR#/ 

Type 

6 2805 

Type 5 



Title: Linesplitting Data Migrations - East 

Description: The purpose of this initiative is to expand the interim migration 

capability to include the migration of data on linesplit loops. This would include a 

migration scenario for LineSplitting to LineSplitting where the data carrier changes. 


Process: Order, Pre -Order; Jurisdiction: North, South System: EDI, LSI, CORBA 

Primary Area: UNE; LSOG Version: LSOG 5 and above. 

Initiator: Michael Clancy, COVAD, 1-15-03 


Overall = 5.0 


AT&T = 5 

Broadview = P 

Cavalier = P 

Choice One= P 

Covad = 5 

Cox = P 

CTSI= P 

Met Tel = 5 

TalkAmerica= 

P 

VarTec = P 

Worldcom= 5 

Z-Tel = 5 

Adelphia= 5 

McGraw= 5 

Conestoga= 5 

STATUS: DENY 

5/6/03 There is not enough volume to 

justify resources to develop an LSR 

based process. Requests to migrate data 

providers in a line split arrangement 

will be handled on a project basis. 

2/11/03 Rated by CLECs 

LOE=High 

2/4/03 New to list.

Rank CR#/ 

Type 

7 2139 

Type 5 

8 2454 

Type 5 



Title: ALI Code on Directory Lis ting Response 

Description: Verizon should provide a reliable, easy way to obtain ALI Code 

information. Verizon should provide the ALI code on the Directory Listing 

Response. The ALI Code Report is not a good tool for obtaining the ALI code. 

Often the telephone numbers are missing requiring a search by listed name. The 

format for listed name is not consistent and the search function requires exact 

criteria, including spaces. Listings are missing or incomplete. 

Process:Pre-Order Jurisdiction: North, Syste m: Web GUI Primary Area: N/A 

LSOG Version: 5 and above 

Initiator/Date: Sybil O’Shaughnessy, Conectiv, 6/15/01 

Title: Line Share Migration 

Description: Permit the migration of data service using a single LSR and a single 

order. Today this requires a disconnect order and a connect order, and requires the 

completion of the disconnect prior to the initiation of the connect order. 

Process: Order, Pre-Order Jurisdiction: North , South System: Web GUI, EDI 

Primary Area: Line Sharing, Line Splitting LSOG Version: 5/6 

Initiator: Michael Clancy, Covad Communications, 3/19/02 


Overall = 4.9 

AT&T = 5 

Bridgecom = 5 

Broadview = 5 

Cavalier =5 

Choice One =5 

Conectiv = 5 

Covad = P 

Cox = 5 

CTC = 5 

NetworkOne=4 

Sprint = 5 

VADI = P 

Overall = 4.9 


AT&T = 5 

Broadview = P 

Cavalier =P 

Covad =5 

Cox = P 

D-Set = P 

Met-Tel = 4.5 

VADI = 5 

Worldcom= 5 

Z-Tel = P 

STATUS: HOLD 

5/30/02 – Issue would be resolved with 

End User Level UNE Listing Accounts 

CR2397 (373105) in June 2003 

11/27/01-Requirements Document review 

7/10/01 – Rated by CLECs; LOE = High 

7/10/01 – Conectiv to provide Verizon 

with examples of ALI Code Report 

discrepancies 


STATUS: SCHEDULED June 2003 

5/6/03 Committed June 2003 

12/4/02 – Candidate for June 2003 

11/15/02- LOE = High; committed for 

February 2003 Line share only 

10/29/02 – Interim process implemented in 

July 2002 that uses one LSR for Line 

Sharing. 

7/23/02 – Targeted for February 2003 

5/8/02 – Requirements Document review 

session/signoff 



Rank CR#/ 

Type 

9 2785 

Type 5 

10 2304 

Type 5 



Title: Create RSU flag in Loop Qual 

Description: Add "RSU" flag to loop qual database and note the RSU CLLI in the 

database. 

Process: Order, Pre -Order, Loop Qual Jurisdiction: North, South System: EDI, 

LSI, CORBA 

Primary Area: UNE, UNE-P; LSOG Version: NA 


Title: Jeopardy for Facility Notice Transactions 

Description: The CLEC community would like to receive via EDI and or the GUI 

detailed response of the Facility Problem and expected delay time on all orders that 

are placed in Jeopardy due to Facilities. Our understanding is the WFA comments 

do not flow through to SOP and therefore do not flow through to EDI or GUI. 

Process: Pre-Order, Order Jurisdiction: North, South System: EDI, Web GUI 

Primary Area: UNE; LSOG Version: N/A 

Initiator: John Berard & Libba Fennell-Johnson, Covad, 10/23/01 


Overall = 4.90 


AT&T = 5 

Broadview = 5 

Cavalier = 5 

Choice One= 

4.5 

Covad = 5 

Cox = P 

CTSI= 5 

Met Tel = 5 

TalkAmerica= 

P 

VarTec = P 

Worldcom= 5 

Z-Tel = P 

Adelphia= P 

McGraw= P 

Conestoga= P 

Overall = 4.8 

AT&T = 4.5 

Bridgecom = 5 

Broadview= 4.5 

Covad = 5 

Cox = 5 

Met-Tel = 

Qwest = 5 

SBC = 5 

Sprint = 5 

Worldcom= 5 

Z-Tel = 4 

STATUS: REQUIREMENTS 

PENDING 

5/6/03 Candidate October 2003 


1/14/03 – Held Not Rated 

1/7/03 – New to list/LOE=Low 

STATUS: DENY 

5/6/03 Verizon does not build facilities to 

meet UNE demand. Information on 

future jobs to provide facilities is not 

readily available. Cost to provide would 

be prohibited. 

11/15/02 – LOE = High 

7/2/02 – Verizon reviewing jeopardy 

process to determine best solution. This 

request is being taken into consideration 

in that review. 

11/27/01 – Requirements Document 

review 

11/13/01 – Rated by CLECs

Rank CR#/ 

Type 





Rank CR#/ 

Type 

11 2068 

12 

Type 5 

2266 

Type 5 



Title: Provide feed to CLEC when a disconnect/seasonal suspend/move is initiated 

for customer with line sharing 

Description: Create a process to provide a feed to the CLEC when a disconnect, 

suspend, or move is initiated within the ILEC for customers with line sharing. This 

feed would provide the necessary information for the CLEC to process orders to 

move the DSL service and/or to disconnect, suspend, or restore line sharing services 

concurrently, or as close as possible, with the ILEC’s order changes to the POTS 

service. 

Process: Order; Jurisdiction: North, South; System: LSI, EDI, CORBA; 

Primary Area: UNE Loop LSOG Version: 5 and above 

Initiator/Date: Leanne Gorman, VADI 5/1/01 

Title: Expand ALI Code – 6 characters 

Description: Expand the ALI Code field to six characters. This will allow more ALI 

codes per BAN. 

Process: Pre-order, Order; Jurisdiction: North, South; System: LSI, EDI, 

CORBA Primary Area: Resale, UNE , UNE-P LSOG Version: 5 and above 

Initiator: C. Dressler, AT&T, 9/26/01 


Overall = 4.6 

AT&T = 5 

Bridgecom = P 

Broadview = P 

Conectiv = P 

Covad = 4 

CTC = P 

MCI = P 

Met-Tel = P 

Rhythms = 4 

Sprint = 5 

Overall = 4.6 


AT&T = 5 

Cox = 4.5 

CTC = 4 

Met-Tel = 4.5 

Sprint = 5 

VADI = P 

Worldcom=5.0 

STATUS : SCHEDULED June 2003 

1/28/03 - Committed for June 2003 


10/31/02 – Committed for February 2003 

9/27/02 – Candidate for February 2003 


7/19/01 –Requirements Document Review 

sign-off pending 

7/11/01 LOE=High 


scheduled for July 19, 2001. 


6/12/01 – Per M. Toothman, Suspend will 

only block Voice, not Data. 

6/5/01 – New to List 

STATUS: HOLD 

5/30/02 – Issue will be resolved with End 

User Level UNE Listing Accounts 

CR2397 (373105) in June 2003 

11/27/01 – Requirements Document 

review/signoff 

10/9/01– Rated by CLECs 

10/2/01 – New to list; LOE = High

Rank CR#/ 

Type 

13 2537 

Type 5 



Title: Incomplete FOC 

Description: Currently the quality of manually generated FOCs sent back to CLECs 

are inconsistent. If the NMC Rep does not key all pertinent information on the FOC 

or changes the sequence of the LNUMs on the FOC and then the FOC received by 

the CLEC is missing information or has LNUMs out of the original sequence. In 

the case of missing information, the CLEC must generate an unnecessary call to the 

NMC for the information. In the case of the incorrectly sequenced LNUMs, the 

CLEC cannot take advantage of gateway automation to process the FOC 

electronically because the sequence differs from the original sequence sent. 

The suggested solution is to have an internal edit in the wholesale systems that does 

not allow an FOC to be sent out to the CLEC unless it is properly sequenced and 

contains complete FOC data. 

Process: Order; Jurisdiction: North, South System: EDI, LSI; Primary Area 

UNE-L, Number Portability Only, New Loop, UNE-P, Resale; LSOG Version : 5 

& above 

Initiator: Alex Pantazis, Allegiance 5/13/02 


Overall = 4.6 


AT&T = 4 

Broadview =4.5 

Cavalier =4 

Choice One= 5 

Conversent=5 

Covad =P 

Cox = 4.5 

CTSI= 4 

Met-Tel = P 

Qwest= 5 

TalkAmerica=5 

VADI = 4.5 

Z-Tel = 5 


2/11/03 - Verizon considers this a non- 

CLEC impacting enhancement. CLEC 

community did not object to scheduling in 

August. 

1/3/03 - Candidate for August 2003 


6/11/02 – Changes jurisdiction to North, 

South; Added LSI to System; added UNE- 

P, Resale to Primary Area 



Rank CR#/ 

Type 

14 2602 

Type 5 



Title: UNE DSO Interval 5 Days for Installation of New Loop 

Description: In Verizon West, the interval to provision these UNE Loops is 5 days. 

In Verizon East the interval is 6 days. This request is to establish a standard interval 

of 5 days. 

Process: Order Jurisdiction: North, South System: Other Primary Area: UNE; 

LSOG Version: LSOG 5 and above 



Overall = 4.6 


AT&T = 5 

Broadview = 5 

Cavalier = 5 

Choice One=4 

Conversent= 5 

Covad = 5 

Cox = P 

CTSI= 5 

Met Tel =5 

Qwest= 4 

TalkAmerica=P 

VADI = 5 

Worldcom= 4 

Z-Tel = P 

STATUS: DENY 

5/6/03 Verizon cannot reliably 

guarantee meeting a 5 day interval for 

provisioning of new loops and is not 

willing to commit to reducing the 

interval. 

2/11/03 - Verizon cannot support the 

reduction in interval at this time. 

11/21/02 Changed to Not Scheduled 

10/31/02 – Targeted for June 2003 

7/9/02 – Rated by CLECs: LOE = Low 


Rank CR#/ 

Type 

15 2691 

Type 5 



Title: 2 Day Line Sharing Interval 

Description: Change the standard Line Sharing interval to 2 days from 3 days. 

This will match the best in class among ILECs line sharing interval currently offered 

and will be consistent with migration intervals 

Process: Order; Jurisdiction: North, South; System: LSI, EDI, Corba Primary 

Area: Line Share; LSOG Version: NA 



Overall = 4.6 


AT&T = 5 

Broadview = P 

Cavalier = P 

Choice One=P 

Conversent= P 

Covad = 5 

Cox = 3 

CTSI= P 

Met Tel = 5 

OneCom =P 

TalkAmerica=P 

Worldcom= 5 

STATUS: DENY 

5/6/03 Due to complexities and 

variations in provisioning situations, 

Verizon cannot commit to meeting a 2 

day interval. 

2/11/03 - Verizon cannot support the 

reduction in interval at this time. 

11/21/02 - Changed to Not Scheduled 

11/15/02 – June 2003 candidate 

11/12/02 – Rated by CLECs; LOE = 

Medium 

11/12/02 – Added Line Splitting to 

Primary Area 


Rank CR#/ 

Type 

16 2773 

Type 5 



Title: Type 5 - Improved Loop Qual with DLC 

Description: Verify that all loops disqualified as DLC be reviewed to determine 

those that may also have copper facilities available. Show those loops as DLC and 

copper. CLEC could then perform LMU dip to determine if the working loop is 

copper or DLC and take appropriate actions. 

For loops that have DLC and copper, identify the copper as loaded, if loaded, and 

provide loop length for the loaded copper loops. 

For loops that have DLC and copper, and the copper is not loaded, provide loop 

length for the copper loops. 

For loops that are DLC only, identify them as DLC ONLY. 

For ISDN capable DLC, indicate DLC ONLY - ISDN CAPABLE. 

Process: Pre-Order, Bulk Loop Qual Jurisdiction: North, South; System: LSI,. 

EDI, Corba Primary Area: Line Sharing, Line Splitting, UNE xDSL; LSOG 

Version: 5 and above 



Overall = 4.6 


AT&T = 5 

Choice One= 5 

Covad = 5 

CTSI= 4 

Met Tel = 4.5 

MetroTelcnnct=4 

TalkAmerica=P 

VarTec = P 

Worldcom= 5 

Z-Tel = P 



2/25/03 During CLEC call, it was 

determined that 2 of the requirements 

needed to be removed from CR 2773 and 

that the other 2 requirements are still being 

investigated for feasibility. Therefore we 

are in a pending requirements status. 


12/4/02 – New to list/LOE=Low

Rank CR#/ 

Type 

17 2775 

18 

Type 4 

2772 

Type 5 



Title: LSI LSR Processing Redesign 

Description: The Goal of Phase 1 of this project was to redesign the LSR 

Processing to more closely match the Pre Order Navigation. The Goal of Phase 2 of 

this project will be to make the LSR Processing more dynamic. 

Process: Pre-Order, Order Jurisdiction: North, South System: LSI Primary 

Area: Resale, UNE, UNE-P; LSOG Version : 5 and above 

Initiator: Tim Burkhart, Verizon 

Title: Type 5 - Timely Updates to Bulk Qual 

Description: Change production date of Bulk Loop Extract from Tuesday to 

Saturday. New lines, disconnects and changes to existing lines are not reflected in 

the Bulk Loop Qualification database in real time. This results in order processing 

delays and customer dissatisfaction. Verizon has this information in real time. 

Process: Pre-Order Bulk Loop Qual; Jurisdiction: North, South; System: Other 

Primary Area: UNE, Line Sharing, Line Splitting; LSOG Version: 5 and above 



Overall = 4.5 


AT&T = 5 

Broadview =5 

Cavalier =5 

Conversent= 5 

Covad =4 

Cox = 5 

CTSI= 4 

Qwest= 5 

TalkAmerica=P 

VADI = 3 

Z-Tel = 4 

Overall = 4.5 

Allegiance = 

4.5 

AT&T = 5 

Broadview = P 

Cavalier = 4 

Choice One= 4 

Covad = 5 

Cox = 4 

Met Tel = 4.75 

VarTec = P 

Worldcom= 5 

Z-Tel = P 

NOS Com = 4 

Mcgraw = P 


3/16/03 Phase 2 is a Candidate for October 

2003. 

1/17/03 Phase 2 Added as a Candidate for 

June 2003. 

10/28/02 – Phase 1 implemented October 

2002 

7/2/02 – Phase 1 committed for October 

2002 

6/11/02 – Phase 1 rated by CLECs 

6/4/02 – New to list/LOE=High 

STATUS: DENY 

3/4/03- We informed Covad that we can 

not do based on feedback from Verizon 

Application group. They informed us that 

they can only run these jobs on the 

weekend and it takes a long time due to the 

volumes. To move this date would 

jeopardize getting the extract to the CLECs 

on time if they want by Saturday or 

Sunday and they can't run during the week 

due to other business activities. 

1/14/03 – Issue clarified to request for East 

bulk Loop Extract to be produced on a 

Saturday rather than a Tuesday. Issue 

rated with clarifications made. 

12/10/02 – CLECs want to know how is 

pending activity is reflected in Livewire 

before rating this CR. 


Rank CR#/ 

Type 

19 1891 

Type 5 



Title: Enhance the CRIS CSR Response to pars e Complex Services into a fielded 

response format 

Description: Verizon currently parses non-complex services into a fielded response 

format; parsing complex services seems like a natural evolution to improve this 

transaction. Use a phased approach by service type, i.e., Phase 1 & 2 – Centrex 

Services (Grandfathered & non-Grandfathered); Phase 3 – PBX Services; Phase 4- – 

ISDN Services; Phase 5 - WATS; Phase 6 – DID/Flexpath Services, etc. 

Process: Pre-order; Jurisdiction: North, South; System: LSI, EDI, CORBA 

Primary Area: Platform, Resale LSOG Version: 5 and above 

Initiator/Date: J. Ziegele, Broadview, 01/15/01 


Overall = 4.4 

AT&T = 4 

Broadview = 5 

Covad = P 

Cox = 4 

CTC = 4 

MCI = 5 

Met-Tel = 4.5 

Sprint = 4 


5/6/03 - Phase 4 Candidate 10/2003 

4/1/03 – Phase 2 , Candidate 10/2003; 

Centrex Phase 3, PBX, Not Scheduled, 

Phase 4 ISDN, Candidate 10/2003; Phase 5 

–WATS, Not Scheduled; Phase 6- 

DID/Flexpath, Not Scheduled 

11/15/02 – LOE = High 

10/28/02 – Phase 1 (centrex services) 

implemented October 2002. Phase 2 

candidate for June 2003 

6/4/02 – Phase 1 committed for October 

2002 

1/9/02 – Phase 1 candidate for October 

2002 

7/31/01 – Phase 1 will be worked in three 

parts: Part A – all Centrex Services in 

North/South that are not graandfathered: 

Intellipath II, Centrex Plus, TX+AD9 

(Custopak), Custopak, Custoflex 2100 

Part B – NOVA, Intellipath, Custoflex, 

Basic, Centrex Extended 

Part C: Custom, Centrex I/II, Centrex 50/99, 

Centrex III 

03/22/01 – Status changed from New to 

Pending Scheduling 

03/22/01 – Requirements review - sign-off 

3/6/01 

02/13/01 – Rated by CLECs 


Rank CR#/ 

Type 

20 2460 

Type 5 



Title: Line Station Transfer Notification 

Description: Today Verizon initiates Line Station Transfers when an end user’s 

loop is served via DLC. Verizon has been doing this proactively without charge to 

the CLEC. Recently, Verizon began to charge for this activity. CLECs should have 

the opportunity to choose to accept the charge or not. Covad requests that Verizon 

change the process to notify the CLEC that a LST is required and have the CLEC 

give authorization. 

Process: Pre-Order; Jurisdiction: North, South; System: LSI, EDI; Primary Area: 

Line Sharing, Line Splitting; LSOG Version: 5 and above 

Initiator: Michael Clancy, Covad Communications, 3/22/02 


Overall = 4.4 


AT&T = 4 

Broadview =4.5 

Cavalier = P 

Choice One= P 

Conversent=4.5 

Covad =5 

Cox = 4 

CTSI= 4.5 

Met-Tel =4.5 

Qwest= P 

VADI = P 

Z-Tel = P 

STATUS: ON HOLD 

12/10/02 - Changed to Not Scheduled 

11/15/02 – LOE = Medium; HOLD 



6/11/02: What is the turnaround time for the 

response? There will be several levels of 

responses, however, the metrics will not be 

impacted. 

6/11/02: Rated by CLECs; changed process 

to Pre-Order 

5/14/02 – Hold for answers to questions - 

rate at 6/11/02 meeting 

4/9/02 – Hold for 5/14/02. Sue Pistacchio to 

determine if information (copper vs DLC) 

can be provided on PreOrder transaction for 

the TN. 


Rank CR#/ 

Type 

21 2522 

Type 5 

22 2680 

Type 4 



Title: Electronic Notification of Pre-cut Test Jeopardy 

Description: Establish a process whereby the CLEC will receive electronic 

notification of pre -cut test jeopardizes via the same method that the LSR was sent. 

Example: During testing, prior to Due Date, the CLEC wants to receive a 

notification (JEP) that there is an issue with cross wiring, so the CLEC can resolve 

the problem prior to the DD. 

Process: Order Jurisdiction: North, South ; System: LSI, EDI Primary Area 

xDSL Loop, UNE-Loop; LSOG Version : 5 and above 

Initiator: Mary Halpin, AT&T 5/7/02 

Title: CNR Additional Notification 

Description: Verizon would like to provide the CLECs with two additional 

notifications via CNR when an order is coded as C01. The additional notifications 

would be done on DD+10 and DD+20. This would impact all ASRs that are for 

UNE HICAP orders and are coded as C01. Additional notifications to the CLEC 

will ensure that they are aware that VZ will cancel the order 31 days past the 

original due date and they will be notified to accept the circuit or change the due 

date. 

Process: Order; Jurisdiction: North, South; System: Other; Primary Area: UNE- 

HICAP; LSOG Version: ASR25 

Initiator: Nancy Donovin, Verizon, 9/19/02 


Overall = 4.4 


AT&T = 5 

Cavalier = 4 

Choice One= 4 

Conversent= 4 

Covad = 5 

Cox = 4 

CTSI= 3 

Met-Tel = 4 

Qwest= 3 

SBC= P 

TalkAmerica=P 

VADI = 5 

VarTec= 3 

Z-Tel = P 

Overall = 4.4 


AT&T = 5 

Broadview = 4 

Cavalier = 4 

Covad = 5 

Met Tel = P 


TalkAmerica=P 

VarTec = P 

Worldcom= 4 

Z-Tel = P 

STATUS: DENY 

5/6/03 – Pre-cut test results are available 

through WPTS. The result is not a 

jeopardy because Verizon continues to 

move toward provisioning on the date due. 

To modify systems to allow this nonjeopardy 

to be returned via EDI or LSI 

would be a very high work effort to 

duplicate information. 

11/15/02 – LOE = Medium; Not Scheduled 



6/11/02 – Is this handled by WPTS? 

6/11/02 – Hold for July; jurisdiction changed 

to North, South and added xDSL Loops to 

Primary Area 



1/28/03 - Candidate for October 2003 

10/8/02 – CLECs rated. CLECs agreed to the 

implementation of a manual process in 

October 2002. 

10/1/02 – New to list/LOE=Low

Rank CR#/ 

Type 

23 2771 

Type 5 



Title: Type 5 – Additional Bulk Pre Qual Info 

Description: When a CLEC uses the Bulk Loop Qualification information 3 rd 

Party Voice Provider (UNE P) existing DSL (shared line), and Resold Voice line are 

not indicated. As a result, bad volumes are created. Orders are sent to Verizon will 

not be fulfilled. 

The result of not having these qualifying flags in the bulk pre -qualification tool is 

that CLECs submit orders for loops that are not qualified, defeating the value of 

bulk pre -qualification. Verizon works on orders that shouldn't be processed and the 

CLECs are charged for service orders that cannot be fulfilled. 

Process: Pre-Order, Bulk Loop Qual; Jurisdiction: North, South System: Other 

Primary Area: Line sharing, Line Splitting ; LSOG Version: 5 and above 



Overall = 4.4 


AT&T = 4.5 

Choice One= 4 

Covad = 5 

Cox = P 

CTSI= 4 

Met Tel = 5 

MatroTelccnnct=4 

McGraw=P 

NOS Comm=P 

TalkAmerica=P 

VarTec = P 

Worldcom= 4 

Z-Tel = P 

STATUS: DENY 

5/6/03 -This information is considered 

CPNI and cannot be provided on a 

wholesale basis on the DSL extract. 

Resold voice and DSL are available by 

reviewing the CSR. Current LSP 

information should be obtained from the 

end user. 

12/10/02 – Rated by CLECs. Covad is 

requesting unique flags. Vz considers this 

information as protected CPNI; loop qual is 

only to tell you if address is capable of 

providing DSL. 


Rank CR#/ 

Type 

24 2860 

Type 5 



Title: Provide an electronic delivery method for Customer Service records that 

exceed the 10K line restriction. 

Description: The purpose of this initiative is to notify the CLEC that the maximum 

line size is exceeded and then automatically transmit the CSR via NDM or FTP 

where the CLEC can retrieve the file for processing. Online retrieval of the entire 

CSR when it exceeds the 10, 000 line maximum is not a feasible approach since it is 

performance impacting. 


Process: PreOrder; Jurisdiction: North, South; System: LSI, EDI, CORBA; 

Primary Area: Resale; LSOG Version : 5 and above 

Initiator : Janice Ziegele, Broadview, 2/26/03 


Overall = 4.3 

Allegiance = 

4.5 

AT&T = 5 

Broadview =5 

Cavalier = 4 

Choice One= 4 

Covad = P 

Cox = 5 

Met Tel = 4 

TalkAmerica= 

4 

VarTec = 4 

Worldcom= 4 

Z-Tel = P 

Conversant =4 

McGraw= 4.5 

Cat Comm – 4 

Adelphia=5 

DSL NET=P 

Penn 

Telecom=4 

MetroTelleconn 

ect=4 

NOSCom=3 




3/4//03 - – New to list/LOE=High

Rank CR#/ 

Type 

25 2715 

Type 4 



Title: Type 4 – 11 Digit CLLI 

Description: This request is for the generation of the complete 11 digit switch 

CLLI code for all WTNs/addresses in the East DSL Loop Qual Extract, and for the 

capability to provide all distinct switch (Host, Remote, or Optical Remote) and RT 

CLLIs associated with all WTNs/addresses through EDI, Corba, and LSI 

transactions. 

Process: Pre-Order, Order; Jurisdiction: North, South; System: EDI, CORBA, 

LSI; Primary Area: Line Sharing; LSOG Version: 5 and above 

Initiator: Karen duBourg, VADI 


Overall = 4.3 


AT&T = 4 

Choice One= 4 

Covad = 5 

Cox = P 

CTSI= P 

GlobalTel=P 

McGraw=P 

Met Tel = 4.5 

MetroTelcnnt=4 

NOS Comm=P 

TalkAmerica=P 

VarTec = P 

Worldcom=P 

Z-Tel = P 

STATUS: REQUIREMENTS PENDING 

2/11/03 - LOE=Medium 

12/10/02 – Applies to xDSL Loop Qual 


Rank CR#/ 

Type 

26 2894 

Type 5 



Title: POTS Reuse for T1 Service 

Description: The purpose of this initiative is to provide the CLECs with the ability 

to review end user address specific circuit information that would enable the CLEC 

to evaluate/propose rearrangements of end user lines/circuits when a no facility 

condition is encountered for UNE T1 orders.. This circuit specific information 

would include those lines/circuits also provided by other CLECs. 

Process: PreOrder; Jurisdiction: MA, NY, DC, MD, NJ, PA; System: LSI, EDI; 

Primary Area: UNE, UNE-P; LSOG Version: 5 and above. 

Initiator: Alex Pantazis, Allegiance Telecom, 3/17/03 


Overall = 4.2 


AT&T = 3.5 

Broadview = P 

Cat Comm= P 

Cavalier = 4 

Choice One= 5 

Covad = 4 

Cox = 3 

CTSI= 5 

Met Tel = 4.5 

One Comm = 4 

Penn Telecom = 

4 

Remi Telecom 

= 4.5 

TalkAmerica = 

4 

VarTec = 3.5 

Worldcom= P 

Z-Tel = P 

STATUS: New 

4/8/03 New to list/LOE=Low

Rank CR#/ 

Type 

27 2353 

Type 5 



Title: Ability to Query Against ILEC Pending Activity 

Description: Today’s process is linear. The POTS move order is processed and 

service installed at the new address, and the billing record (CSR) must be updated 

before the DSL order can start. It takes 3 to 5 days before the CSR is updated, 

therefore, delaying the ability to process a DSL order through DLEC systems 

Requesting the ability to query against ILEC pending activity rather than just the 

CSR. 

Return: 

TN (From & To TN) 

To/Inward Address 

ILEC Ckt ID 

Line Share TN 

ILEC Order # 

Due Date 

From & To Wire Center 

Process: Pre-Order; Jurisdiction: North, South; System: EDI, Web GUI 

Primary Area: Line Sharing, Line Splitting, UNE-P, Resale; LSOG Version: 5 

and above 

Initiator: Karen duBourg, VADI, 12/17/01 


Overall = 4.1 


AT&T = 3.75 

Broadview = 4 

Choice One = P 

Cox = 3 

E.Spire= P 

Met-Tel = 4.5 

VADI = 5 


2/11/03 - Verizon reviewing for feasibility of 

parallel provisioning. 

11/15/02 – LOE = High; Not Scheduled 


2/12/02 – Rated by CLECs; ratings 

predicated on Line Splitting/Line Sharing 

being completed at same time 

1/8/02 – CLECs deferred rating to February 

meeting; ; Pending Order Issue Workshop to 

be held 1/28/02; Primary Area expanded to 

include Line Splitting, Platform, Resale 


Rank CR#/ 

Type 

28 2354 

Type 5 

29 2551 

Type 5 



Title: Accept LSR on Account with Pending Inward Activity 

Description: When a line sharing LSR is submitted, and pending activity exists on 

the account, the LSR should not be rejected. The overall objective is to achieve a 

parallel process to have DSL service working by at least the day after POTS service 

is installed. 

Process: Order; Jurisdiction: North, South; System: EDI, LSI 

Primary Area: Line Sharing; LSOG Version: 5 and above 

Initiator: Karen duBourg, VADI, 12/17/01 

Title: Flow through to accept the BTN on Loop order 

Description: CTSI would like the new loops to be added to the misc. BTN 

requested on the LSR. Currently we are receiving new misc. BTNs on our FOCs 

due to the order flowing through the system. If the NMC catches the problem, they 

correct it before a FOC is sent. If the NMC does not see the order, we then need to 

call the NMC to correct the problem. 

Process: Order; Jurisdiction: North, South; System: EDI, LSI; Primary Area: 

UNE-Loop; LSOG Version: 5 and above 

Initiator: Amy Kwak, CTSI, 5/16/02 


Overall = 4.1 


AT&T = 3.75 

Broadview = 4 

Choice One = P 

Cox = 3 

E.Spire= P 

Met-Tel = 4.5 

VADI = 5 

Overall = 4.1 


AT&T = 4 

Broadview =4 

Cavalier =4 

Choice One=4 

Conversent=P 

Covad =3 

Cox = 4.5 

CTSI= 5 

Qwest= P 

TalkAmerica=P 

VADI = P 

Z-Tel = P 


2/11/03 - Verizon reviewing for feasibility of 

parallel provisioning 

11/15/02 – Not Scheduled 

2/27/02 – Candidate for June 2002 


1/8/02 – CLECs deferred rating to February 

meeting; ; Pending Order Issue Workshop to 

be held 1/28/02 

1/2/02 – New to list; LOE = High 


5/6/03 Committed for June 2003, Phase 2 

Candidate for February 2004. 


6/11/02 – Changed jurisdiction to North, 

South; added EDI to Primary Area 



Rank CR#/ 

Type 

30 2579 

Type 5 



Title: Directory Listing USOCs on Summary Billing 

Description: Provide USOC summaries on 3 rd party directory listing invoices. 

Having actual counts of services (i.e., how many monthly recurring services such as 

non-list and non published) will enable the CLEC to see exactly what they are being 

charged for and thus enable them to validate the invoices before payment 

Process: Billing; Jurisdiction: North, South; System: Other; Primary Area: 

UNE: LSOG Version : 5 and above 

Initiator: Joyce Perry, AT&T, 6/13/02 


Overall = 4.1 


AT&T = 5 

Broadview=4.5 

Cavalier = 4 

Choice One=4 

Conversent= 3 

Covad = P 

Cox = 5 

CTSI= 3 

Met Tel = P 

Qwest= P 

SBC=P 

TalkAmerica=4 

VADI =P 

VarTec=P 

Worldcom=4 

Z-Tel = 4 

STATUS: DENY 

5/6/03 - DL USOCs are available on the 

BDT and can be summarized by the 

CLEC. 

2/11/03 Verizon cannot support at this time. 



Rank CR#/ 

Type 

31 2545.6 

Type 4 



Title: RETAS Screen Redesign-Phase 6 

Description: This initiative provides for the redesign of the RETAS screens. These 

design changes will have no impact on overall functionality. The URL will not be 

changing. The Trouble Administration Business Rules must be modified to be in 

sync with the revised Repair interface. The changes to LSI will provide better 

navigation and a more efficient process for creating, modifying, and tracking trouble 

tickets. In addition, a more accurate and timely status will be returned. 


Process: Trouble Administration; Jurisdiction: North & South; System: LSI; 

Primary Area: Resale, UNE-P, UNE; LSOG Version: NA 

Initiator: Tom Zablocki, Mary Ellen Hanley, Verizon, 5/2/02 


Overall = 4.1 

Allegiance =4 

AT&T = 4 

Choice One= 5 

Covad = 5 

CTSI= 5 

GTB=4 

Met Tel = 4 


McGraw=5 

NOS Comm=5 

TalkAmerica=4 

VarTec = 4 

Worldcom= 4 

Z-Tel = 4 

STATUS: SCHEDULED JUNE 2003 

3/11/03 Phase 6 Committed for June 2003 

release. 

3/4/03 Phase 4 Completed 2/20/03, Phase 6 

is Committed for 4/03 Release. 

12/10/02 – Rated by CLECs/LOE=High 


Rank CR#/ 

Type 

32 1455 

Type 5 



Title: Develop Order Tracking System 

Description: Develop a complete and comprehensive system for tracking and 

reconciling all orders submitted from CLECs. Goals: Provide positive control over 

all incoming and outgoing orders and provide enhanced status information flow. 

Objectives: enable proactive control over all PONs, ensure all PONs proceed 

through the processing cycle in a timely manner, enable a proactive corrective 

response for any PON not being processed in a timely manner, ensure a positive 

notification and correction system for all transmissions. 

Process: Order; Jurisdiction: North, South; System: LSI, CORBA, EDI; Primary 

Area: All; LSOG Version: 5 and above 

Initiator/Date: E. Goldberg/D. Feinberg, Met-Tel, 05/15/00 


Overall = 3.9 

AT&T = 3.5 

Conectiv = 3 

CTC = 3 

MCI = 3.5 

Sprint = 4 

Z-Tel = 5 

Met-Tel = 5 

Cllr Rntls = 5 

Time Wrnr = 3 

STATUS: DENY 

5/6/03- Since the creation of this CR, 

Verizon has instituted many controls on 

the notifier processes. Instances of 

delayed notifiers have been greatly 

reduced. Notifier status may be obtained 

via LSI. 

2/11/03 MetTel challenges DENY Status 

11/15/02 – LOE = High 

7/9/02 – CR 1455 should be satisfied by 

Order Status (370851). MetTel will test to 

verify whether or not this meets their needs. 

2/05/01 – Status changed from 

REQUIREMENTS PENDING to PENDING 

SCHEDULING 

01/18/01 Requirements Review sign-off 

01/03/01 – Requirements Review session 

09/12/00 – CLECs request requirements 

meeting to be scheduled 

06/13/00 – CLECs raised the following 

concerns: Pontronics doesn’t provide 

integration of all systems, is this based on 

Carrier to Carrier Guidelines, can same 

control points be set up for VAM 

connectivity, will this move to LSOG 4, will 

this be a tool for Help Desk or CLECs, Met- 

Tel suggested the PSC should have an access 

code. Z-Tel sent an email to Change Control 

rating this a 5 after the meeting.

Rank CR#/ 

Type 

33 2156 

Type 5 



Title: Optional BAN1 & BAN2 fields 

Description: For REQTYP JB orders, change requirements for the LSR BAN1 and 

BAN2 fields from “Required” to “Optional” or support value of “E” on all LSRs. 

Process: Ordering Jurisdiction: North, South; System: EDI, LSI; Primary Area: 

UNE, Resale LSOG Version: 5 and above 

Initiator/Date: Amy Stramel, Sprint, 7/10/01 


Overall = 3.9 

AT&T = 4 

Bridgecom = 3 

Broadview = 4 

Cox = 4 

EnterpriseAmer 

=P 

Met-Tel = 3.5 

SBC = P 

Sprint = 5 

Z-Tel = P 

STATUS: HOLD 

5/30/02 – Issue will be resolved with End 

User Level UNE Listing Accounts CR2397 

(373105) in June 2003 

11/27/01 Requirements Document review; 

sign off received 

8/30/01 – Why does Vz have restriction of 

10,000 ALI codes per account? Legacy 

systems only accept 3 character codes, 

restricting the possibilities to approximately 

18,000 codes per BAN. 

8/14/01 – Rated by CLECs; status changed to 

Requirements Pending 

8/7/01 – New to list; LOE = High

Rank 

CR#/ 

Type 

34 2071 

Type 4 



Title: Provide additional fields for parsed CSR for non complex accounts 

Description: Provide additional information needed for LSR preparation on the 

parsed CSR that is currently provided via the unparsed CSR. This includes: 

Header--- CUSCODE, Last Posted Service Order, Last change date of CSR; IDV--- 

PCL, RSID/AECN, BLACT, TAR, RSCP; BIL---TAR, PNP, TBE; S&E--- Last 

activity date for each feature; SUMY--- Summary section; USOC--- USOC 

Description section; and (TBD Exchange Key) 

Process: Pre-order; Jurisdiction: North, South System: EDI, CORBA 

Primary Area: Resale, UNE, UNE-P LSOG Version: 5 and above 

Initiator: R. Walsh, Verizon 


Overall = 3.9 


AT&T = 4 

Cox = 4 

CTC = 4 

Sprint = 3.5 

Worldcom= 4 


11/25/02 Requirements completed. 

9/20/01 – AT&T suggests all parsing CRs 

be done together as long as they are not in 

conflict or contention with Type 5 CRs. 

WCOM requested that LSCP be a specific 

field in LSOG 4/5. Sprint requested the “Bill 

To Indicator” (aka Gift Billing) be included. 

Request currently being reviewed by Vz to 

determine if they can be accommodated. 

9/20/01 –Rated by CLECs 

9/4/01- Additional fields identified and CR 

attached. 

8/30/01 – Why is SUS FID stripped from 

unparsed CSR? Ans: The customer's CSR 

does not reflect non-payment suspension 

activity; the rep would have to access 

BOSS/CRIS to determine to determine if an 

account is suspended for non payment. To 

protect the end-users privacy, no information 

is given to the CLEC to indicate a retail 

account was suspended for non-payment. 

8/30/01 – South restores on migration but 

North does not. Is it different for Platform? 

Ans: No different for Platform; Platform for 

the North does not restore on migration. The 

rep issues the restore order and then issues 

the migration. 

8/14/01 – Hold for additional information 


Other parsing initiatives include: 822 (adding 

feature quantity and rate), 1710 (parsing for 

simple additional listings), 1815 (new 

parsing requirements for distinctive ring).

Rank 

CR#/ 

Type 




None of these pending CRs are in conflict 

with or touch upon the same requirement as 

this initiative

Rank CR#/ 

Type 

35 1102 

Type 5 



Title: Application to application interface for UNE Loop trouble administration 

Description: Allow CLECs to administer troubles via an application to application 

interface-something that will be more efficient than the WEB GUI and which is 

needed as volumes of orders increase. 

Process: Trouble/Maintenance; Jurisdiction: North, South; System: EDI/CORBA; 

Primary Area: N/A; LSOG Version: N/A 

Initiator/Date: L. Brown, Broadview, 11/24/99 


Overall = 3.7 

AT&T = 4 

Broadview = 4 

CTC = 4.5 

MCI = 2 

Sprint = 4 


5/6/03 Phase 3 Committed June 2003, 

Phases 6-9 Candidates for October 2003. 


12/11/01 – ATIS adoption of CORBA 

standard expected 1Q02 following completion 

of 45-day industry comment period. Verizon 

expects to submit contribution for ATIS 

adoption of an XML standard 1Q02. 

2/13/01 – CORBA standards to be adopted in 

March 2001; Verizon will implement in 4Q01 

12/12/00 – This will remain on hold for 

industry standards to be developed. 

12/12/00 – No response from originator. CR 

will be canceled and removed with Jan update. 

11/07/00 – Verizon called Lauren Brown to 

request cancellation of CR, Lauren no longer 

handles and will refer to appropriate person. 

09/12/00 – Industry standards are handled by 

the ECIC committee for CORBA and EDI. 

07/11/00 – Electronic Bonding is available. 

BA will not implement until industry 

standards are developed. 

03/14/00 CTC questioned if BA is 

participating in EDI/CORBA meetings. CTC 

wouldchampionwithBAtoimplement standard. 

02/08/00 – BA to work with EDI once 

industry standard is established. 

01/11/00 –BA to work with Broadview offline 

12/14/99 – BA to investigate how and why 

loop troubles are administered. Once 

understood, will determine needs for 

workshop. EDI is developing standard for 

troubles and will publish these standards.

Rank CR#/ 

Type 

36 2085 

Type 5 



Title: UNE T1 Ordering Capability on LSR 

Description: Provide UNE-T1 ordering capability via the LSR. Currently only 

available through the ASR. 

Process: Pre-Order, Order; Jurisdiction: North, South; System: LSI, EDI; 

Primary Area: UNE Loop LSOG Version: 5 and above 

Initiator/Date: Patricia Garcia, Covad, 5/8/01 


Overall = 3.7 

AT&T = 3.5 

Bridgecom = 4.5 

Broadview = 4 

Conectiv = 2 

Covad = 5 

CTC = 4 

MCI = P 

Met -Tel = 4 

Rhythms = 4 

Sprint = 2 

VADI = 4 

STATUS: DENY 

5/6/03- In 1999 collaborative, it was agreed 

to move to ordering DS1s via the ASR. To 

go back and open up ordering via the LSR 

would be a very high work effort to 

duplicate an existing ordering vehicle. 

7/11/01 – Currently ILECs do not accept both 

ASR and LSR, at the customer’s discretion, 

for UNE DS1 loops. (info obtained from 

Verizon, Qwest, BellSouth, SBC) 


scheduled for July 19, 2001; Requirements 

Document sign off received. 


6/5/01 – New to List

Rank CR#/ 

Type 

37 2900 

Type 5 



Title: Assignment Change Notification 

Description: The purpose of this initiative is to have Verizon coordinate changes of 

cable and pair assignments as part of a migration to a CLEC with the CLECs. In 

April, CLEC experienced change in cable pair assignment during conversion at a 

rate of 8-10% of the LSR order volume. 

Process: Order; Jurisdiction: North & South; System: LSI, EDI; 

Primary Area: UNE, UNE-P; LSOG Version: 5 and above 

Initiator: Larry Blair, REMI Communications, 3/21/03 


Overall = 3.7 


AT&T = 4 

Broadview = 4 

Cat Comm = 3 

Cavalier = 3 

Choice One= 4 

Covad = 4 

Cox = 3 

CTSI= 3 

Met Tel = 4 

One Comm = 4 


P 

Remi Telecom 

= 3.5 

TalkAmerica= 

4 

VarTec = 4 

Worldcom= 3 

Z-Tel = 4 

STATUS: NEW 

4/8/03 New to list.

Rank CR#/ 

Type 

38 2485 

Type 5 



Title: Enhance Web GUI Extended Loop Qual 

Description: The xDSL Loop Qualification Extended Query needs to function in a 

bulk fashion. CLECs need the ability to submit bulk requests to the ILEC for 

investigation. Also this query needs to have a tracking mechanism for the CLEC to 

track queries and responses. 

Process:Pre-Order; Jurisdiction: North, South; System: LSI; Primary Area: UNE; 

LSOG Version: 5 and above 

Initiator: Barbara Vahey, VADI 4/15/02 


Overall = 3.6 


AT&T = 4 

Broadview = P 

Cavalier = 2 

Choice One= 1 

Conversent= P 

Covad =4.5 

Cox = P 

CTSI= P 

Met-Tel = 4 

Qwest= 5 

TalkAmerica=P 

VADI = 5 

Z-Tel = P 

STATUS: DENY 

5/6/03 Bulk preorder transactions should 

be submitted via EDI or CORBA. 

Allowing bulk transactions to be submitted 

via LSI could degrade performance for all 

users. 

3/4/03 Verizon cannot support this initiative. 

9/25/02 - Not Scheduled 



Rank CR#/ 

Type 

39 C03- 

0501 

Type 5 



Title: Hunting format in CSR follow TCIF 

Description: The purpose of this initiative is to have hunting details presented in the 

CSR transaction be in compliance with TCIF guidelines. In April, the CLEC 

community clarified that presentation of Hunt Group information in TCIF format 

applies only to EDI and not CORBA. CORBA is not impacted by this request. 


Process: PreOrder; Jurisdiction: North, South; System: EDI; Primary Area: 

UNE, Resale, UNE-P; LSOG Version: 5 and above 

Initiator: Lissa Provenzo & Dave Burley, WorldCom, 3/27/03 


Overall = 3.6 


AT&T = P 

Broadview = P 

Cavalier = P 

Cat Comm = P 

Choice One= 3 

Covad = P 

Cox = P 

CTSI= P 

Met Tel = 4 

One Comm = 4 


P 

Remi Telecom 

= 3.5 

TalkAmerica= 

P 

VarTec = P 

Worldcom= P 

Z-Tel = P 

STATUS: NEW 

4/8/03 New to list

Rank CR#/ 

Type 

40 2120 

Type 5 



Title: Identify Foreign Exchange accounts in Bulk Loop Qual Extract 

Description: The ILEC should identify Foreign Exchange accounts in the Bulk 

Loop Qual Extract. If a loop qualification is performed by using the address of a 

customer, the results may show false information. The customer may reside in the 

jurisdiction for a particular CO, but since they are located closer to a CO outside 

their exchange, they are serviced by the closer CO, thus having a Foreign Exchange. 

The CLEC needs to know the correct CO to determine if the customer is loop 

qualified. 

Process: Pre-Order; Jurisdiction: North, South; System: LSI, EDI, CORBA 

Primary Area: UNE Loop; LSOG Version: N/A 

Initiator/Date: Barbara Vahey, VADI, 6/6/01 


Overall = 3.4 

AT&T = 3 

Bridgecom =3 

Broadview = P 

Choice One =P 

Conectiv = 3 

Cox = P 

CTC = P 

NetworkOne=P 

Sprint = 3 

VADI = 5 

STATUS: DENY 

5/6/03 - This is considered CPNI 

information and cannot be provided on the 

extract. 

11/27/01 – Requirements Document review; 

signoff 11/30/01 

7/10/01 – Rated by CLECs; LOE = Medium; 

Status changed to Requirements Pending 


Rank CR#/ 

Type 

41 2858 

Type 5 



Title: Migrate w/ freeze if w/in same company (i.e. from Resale to UNE-P) 

Description: The goal of this initiative is to change the process so that we 

can migrate our OWN customers from one product to another even if there is 

a freeze (RSCP) on the line. 

Reason: Process change 

Process: Order; Jurisdiction: North, South; System: LSI, EDI; Primary Area: 

UNE, Resale, UNE-P; LSOG Version : 5 & above 

Initiator : Amanda “AJ” Dunbar, Cat Communications International, 2/25/03 


Overall = 3.4 


AT&T = P 

Broadview = 4 

Cavalier = P 

Choice One= 3 

Covad =P 

Cox = P 

CTSI= 

Met Tel =1 

TalkAmerica= 

3 

VarTec = 3 

Worldcom=P 

Z-Tel = 3 

Conversant=P 

McGraw=4 

CatComm=4.4 

Adelphia=P 

DSL Net=P 

Penn 

Telecom=4 

Metro 

Telleconnect=4 

NOS Com=3 




3/4//03 - – New to list

Rank CR#/ 

Type 

42 2394 

Type 4 

43 2189 

Type 5 



Title: Return RESNO on Direct TN Reservation 

Description Add RESNO field to the Address Validation Direct TN Selection 

Response transaction. Currently this information is not returned on the transaction 

although it is associated with the TN when it is reserved. CLECs may be reserving 

more TNs than they need. By providing this information, additional unnecessary 

reservations may be prevented and thus save valuable numbering resources. 

Process: Pre-Order; Jurisdiction: North, South; System: LSI, EDI, CORBA; 

Primary Area: UNE ; LSOG Version: 5 and above 

Initiator: Jim Parks, Verizon 

Title: ILEC Service ID 

Description: A Service Identifier needs to be included with all associated Working 

Telephone Numbers in the East Bulk Loop Qualification Extract. Example: Identify 

UNE-P, ISDN. And XDSL already on line. 

Process: Pre-Order, Jurisdiction: North, South; System: LSI, EDI, CORBA 

Primary Area UNE -Loop; LSOG Version: N/A 

Initiator/Date: Barbara Vahey, VADI, 7/31/01 


Overall = 3.3 


AT&T = 4 

Broadview= 3.5 

Cavalier = P 

Covad =2 

D-Set = P 

Met-Tel = P 

VADI = P 

Worldcom= 3 

Z-Tel =3 

Overall = 2.8 


AT&T = 3 

Bridgecom = 2 

Broadview = 1 

Covad = 3 

Cox = 3 

CTC = P 

Sprint = 2 

VADI = 5 




STATUS: DENY 

5/6/03 This is considered CPNI information 

and cannot be provided on the extract. 

11/15/02 – Not scheduled 


9/27/02 – Candidate for February 2003 

5/30/02 – Candidate for October 2002 

11/27/01 – Requirements Document review; 

signoff 11/30/01 


8/14/01 – VADI not represented at PWG 

session; hold until 9/11/01 meeting for rating 

8/7/01 – New to list; LOE = Very High

Initiator 

Telephone Number 

E-mail 

Initiator Company 

Date request sent to Change 

Control 

Identify the States that are affected 

by this change 

Identify the products that are 

affected by this change 

Identify the processes that are 


Identify the transactions that are 


Identify the interfaces that are 


Identify the LSOG versions that 

are affected by this change 

Describe the Change 

Describe the functionality that you 

would like to enhance 

Note: Describe what your Change 

Request is. Do not specify how to 

implement it. 

Refer Questions to: 


Change Request Number: 2811 

Title: ALI Code Spreadsheet Upgrade 

Rebecca Baldwin 

Back-up: Nancy Taborda 

Rebecca Baldwin: 832-553-2205 

Nancy Taborda: 716-819-2147 

rebeccca.baldwin@adelphia.com 

Adelphia Business Solutions 

January 21, 2003 

All Verizon EAST states 

Directory Listing 

Service order processing for directory listing 

Pre-order and order transactions 

LSI 

LSOG 5 

Ali code spreadsheet provided by Verizon does not supply 

CLEC with required information to accurately complete 

directory listing service orders. 


Provide an example that justifies 

the change 

Include attachments if available 

How will your company benefit 

from completing the Change 

Request? 

Describe the proposed solution to 

the change 

How do you propose the Change 

Request can be implemented? 

What is the expected output 

resulting from the proposed 

solution? 


CLEC needs to know the directory the listings appears in. 

Example: Foreign Listing FID: FL does not provide the 

foreign directory appearance 

CLEC will be able to process listing changes/additions/ 

deletions for it’s own end users and will minimize contacting 

Verizon Support personnel for assistance 

Add additional column to the current spreadsheet which will 

indicate the directory. 

Updated Ali Code spreadsheet format 

Interface Usability To be completed by Verizon 

Benefit to CLECs To be completed by Verizon 

Productivity Impact To be completed by Verizon 

Cost/Time Explanation 

LSOG Conformity 

Remarks 

To be completed by Verizon 






Title: AOS Form for CLEC to CLEC 

Migrations 

Initiator Sadia Mendez 

Telephone Number 212-849-2267 

E-mail smendez@mcgrawcom.net 

Initiator Company McGraw Communications 


Control 


















implement it. 


Sadia Mendez, Carrier Division Manager 

McGraw Communications 

212-849-2267 

smendez@mcgrawcom.net 

January 27, 2003 

New York 

Services provided under Service Agreements 

Order 

Resale As-Is and As-Specified Migrations 

LSI, EDI 

All 

The AOS form that the NY NMC requires for the Resale, as-is 

migration of contracted services must be modified in order to 

apply to the situation where the end-user is migrating from one 

CLEC to another CLEC. The NMC is currently requiring that 

the OLSP, as opposed to the end-user, sign the AOS form as the 

“Assignor”, prior to allowing the migration order to go through. 

The language on the AOS, as it stands today, is not appropriate 

for this type of transaction. The terms that the “Assignor” is 

agreeing to make sense when an end-user is the “Assignor” but 

are totally unacceptable for a CLEC to agree to as the 

“Assignor”. 



the change 




Request? 


the change 





solution? 




Cost/Time Explanation To be completed by Verizon 

LSOG Conformity To be completed by Verizon 

Remarks To be completed by Verizon 


Sadia Mendez, Carrier Division Manager 

McGraw Communications 

212-849-2267 

smendez@mcgrawcom.net 


The following PONs are orders currently being held by the 

NMC until they receive an AOS signed byt the losing CLEC. 

The losing CLEC is refusing to agree to the terms on the current 

AOS. (rightfully so). The NMC refuses to release the order 

without the AOS signed by the losing CLEC: SMRESALE491, 

SMRESALE479, SMRESALE499. 

Also, See AOS form attached to email with this request to 

review the terms defined on it. 

A modified AOS will result in “losing” CLECs agreeing to sign 

the AOS forms and the orders being held-up by the NMC 

pending a signed AOS will be processed. 

Remove the first two paragraphs under the terms of the current 

AOS and leave only the last paragraph in that section. Change 

the Name of the form to specify that this AOS applies to CLEC 

to CLEC migrations. 

Timely, uninterrupted migration of end-users between CLECs. 



ASSIGNMENT OF SERVICE PROVIDED UNDER SERVICE AGREEMENT 

Current Billed Party / Assignor: New Billed Party / Assignee: 

(Company Name) (Company Name) 

(Address) (Address) 

(City, State, Zip) (City, state, Zip) 

The Current Billed Party (“Assignor”) hereby assigns the Contract or Service Agreement for Tariffed 

Product/Service (“Service Agreement”) identified below to the New Billed Party (“Assignee”): 

Billed Telephone Number: 

Tariffed Product/Service: 

Requested Date of Assigned Service: 

Purchase Order Number: 

The Assignor agrees that it will remain jointly and severally liable with the Reseller, as the Assignee, and any future 

assignees, for all obligations to New England Telephone and Telegraph Company or New York Telephone 

Company (Collectively “BA”) arising out of the Service Agreement. 

The Assignor further agrees that notwithstanding this Agreement, the Assignor remains responsible for all payment 

obligations for any Yellow Page Advertising charges associated with the above-referenced billed telephone number, 

both for any current published directory and for any future directory for which such advertising has been ordered. 

The Yellow Page advertising will be removed from the above referenced account and billed directly to Bell Atlantic 

Yellow Pages Company to the Assignor. 

The Assignee agrees to assume all of the rights, liabilities, and obligations of the Assignor under the Service 

Agreement. The Assignee also agrees that it will be obligated to comply with all of the terms and conditions of the 

Service Agreement, including the payment of retail rates. 

AGREED and ACCEPTED: 

(Assignor) (Assignee) 

By: By: 

signature of authorized employee signature of authorized employee 

Name/title: Name/title: 

Date: Date: 

Fax TN: Fax TN: 

To be completed by BA: 

Original Service (Service Agreement) Date: 

Scheduled Expiration date of Service Period: 

Current Number of Centrex lines in Service: 

Order Number: 

Consented To: 

Name/Title (printed) 

Date: 

signature of a BA representative 


Change Request Form 

Type 5 

Appendix B: Bulletin Format 

For System Outage, System Availability, and Type 1 Change Request Bulletins, the general format will be the same as described 

below. 

Verizon 

VERIZON Wholesale Customer Care Center 

Type of Bulletin 

Severity: 1 

ID#: 1000 

Subject: Web GUI System Outage 

Date and Time of Bulletin: 06/28/99; 05:49:21 PM 

Date and Time Issue Identified: 06/26/99; 03:30:05 PM 

Report: Initial 

Category: System 

Systems Impacted: WEB GUI 

Area Impacted: TSR, UNE 

Process Affected: Pre-Order 

Region: South 

Documentation Impacted: Business Rules v 1.1.1 

Resolution: 

Effective date: 

Details: 



Type 5 


the change 




Request? 


the change 





solution? 


Title: Change bill format to include the 

CKL information for analog loops on 

UNE-L bills on the CSRs 






In the last few months AT&T had to request resends of their 

Pennsylvania UNE-L bills because the bills were mailed to the 

wrong address. It usually takes at least five boxes to mail these 

bills. A useable mechanized bill would eliminate any need for 

AT&T to require a paper bill. It would also allow AT&T to 

review all the charges on these bills since the paper bill does not 

provide all the billing details such as the USOC’s on the 

embedded base of circuits. 

It would allow us to electronically receive, verify and process 

the UNE-L bills for New Jersey, Pennsylvania and Delaware. 

This would reduce the number of billing inquiries we submit. 

We would no longer have to wait for resends of misdirected 

bills and would allow us to pay our bills on the due date. It 

would allow us to financially assure all rates against the 

Interconnection Agreements. 

A solution is to add the CKL information to the CSR similar to 

the format for the MDVW and Verizon North UNE-L bills. 

We expect to have a location CKL for each CLS on the bill. 

This would allow us to electronically receive, verify and process 

the bill for payment. 




Type 5 

Remarks 






Type 5 

Initiator 


E-mail 

Change Request Number: C03-0571 

Title: RETAS Screen Enhancements 

Alan Rothenstreich 

Initiator Company New York Telsave 


Control 


















implement it. 


"Alan Rothenstreich" 

3/31/03 

Verizon East 

RETAS 

All functions 

All ReTAS Functions 

1. Create one screen for type of line prefix 

2. Add a drop down for the trouble type codes 

3. remove the drop down for premise and circuit access date and 

time, replace it with a simple fillin box. 



Type 5 


the change 




Request? 


the change 





solution? 

Reduce the steps for creating transactions in RETAS and make 

the screens simpler to use 

By changing the screens in RETAS 






Remarks 

Refe r Questions to: 

Easier to use screens with less steps to create transactions. 






Type 5 

Initiator 


E-mail 

Initiator Company 


Control 


















implement it. 

Refer Questions to: Arthur Barone 

Change Request Number: C03-0723 

Title: Add Trouble Ticket/PON 

information to BDT 

ARTHUR P. BARONE JR. 

718.947.8669 

ABARONE@BROADVIEWNET.COM 

BROADVIEW NETWORKS 

5/2/03 

NY, MA, RI, NH, ME, VT 

UNE-P (J); LOOP (N) & TSR (Q) 

Billing - Bill Data Tape 

N/A 

CRIS; CABS 

N/A 

TROUBLE TICKET # AND/OR PON, NEEDS TO 

PASSED THRU TO THE WHOLESALE BDT FILES AND 

POPULATED ON THE 103005 OC&C RECORD, WHEN A 

REPAIR CHARGE IS BILLED. 

FYI .. THIS IS CURRENTLY DONE W/ (SPECIAL) 

ACCESS ACCOUNTS. 



Type 5 


the change 




Request? 


the change 





solution? 






Remarks

OSS Interface Change Management Meeting May 13, 2003 - Verizon

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?