OSS Interface Change Management Meeting October 14, 2003

Transcription

1 OSS Interface Change Management Meeting October 14, :00 AM 12:00 PM 1095 Avenue of the Americas, New York, NY Fl/Rm Dial-In: (312) Agenda I) Welcome and Introductions (Tom Rodgers) II) Special Projects Wireless LNP (Ed Amato) III) Departmental Discussion (10:10 11:00) Website Enhancements (Linda Senne) Business Rules Engine - (Susan Pistacchio) IV) CMP Topic Review (11:00 12:00 ) Topic# 73 Prioritization Process V) CLEC Discussion Lunch Noon 1:00 P.M VI) Change Control Items By Release (1:00 1:30) VII) CLEC Initiated Change Requests C : LSI-RETAS make fields required for Create, Modify, and Inquiry C : Query for LNA C on PS/RS Form When No Changes Are Being Made C : Make PS/RS Form Optional with Hunting Change Requests C : Query Resale Disconnects for Incorrect DISC NBR C : Query When the WTN (Main BTN) is Disconnected on ACT C VIII) Verizon Initiated Change Requests C : ASR for Collocation Applications 2811: ALI Code Spreadsheet Upgrade C Shared UNE Loop Product C Change for existing CLEC customer s to convert from an analog to a digital circuit as Hot Cuts C : Allow Multiple Phone Numbers and Circuit IDs on one Trouble Ticket C : Type 5 - Parse out Hunting Details on BCN

2 October 2003 OSS Interface Change Management Meeting Topic # Description Date Discussion 3/14/00 - CLEC to CLEC migration is a difficult task. The CLEC s expressed great concern with the sharing of 67 CLEC to CLEC Migration 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 October 2003 East CMP Revisions Dated October 7,

3 October 2003 OSS Interface Change Management Meeting Topic # Description Date Discussion 3/11/03 - CLEC community requests a recap or summary of all change requests associated with CLEC to CLEC conversion listed here. The following Change Requests have either been completed or are pending that impact CLEC to Migrations. - CR IT# Flow Through SUP 2 for change of date due, North and South, all services.- Completed 12/ CR1187/1411-IT# Allow Level 5 Flow-Through on a Platform CLEC to CLEC migration- Completed 6/ CR IT# Process CLEC to CLEC Migration As Is at Level 5 - Completed 2/ CR IT# End User Level Listings Account - Phase 9- Candidate 4/ CR IT# CLEC to CLEC Migrations (Phase 1) - Committed 6/ CR IT# CLEC to CLEC Migrations Provider Notification (phase 2) - Committed 6/ CR IT# Type 5 - Enhance xdsl Migration-Requirements will be worked with CR IT# Line share CTX FT VZ North- Not Scheduled - CR IT# Hot Cuts for xdsl Loops - Candidate 10/ CR IT# AOS Form for CLEC to CLEC Migrations - Not Scheduled 8/5/03 - CR IT# End User Level Listings Account - Phase 9- Committed 8/ CR IT# CLEC to CLEC Migrations (Phase 1) - Completed 6/ CR IT# CLEC to CLEC Migrations Provider Notification (phase 2) - Completed 6/ CR IT# Type 5 - Enhance xdsl Migration-Requirements will be worked with (Phase 4 Not Scheduled) - CR IT# Line share CTX FT VZ North- Completed 7/ CR IT# Hot Cuts for xdsl Loops - Candidate 4/ CR IT# AOS Form for CLEC to CLEC Migrations - Not Scheduled 69 PONTRONICS 6/13/00 - 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. October 2003 East CMP Revisions Dated October 7,

4 October 2003 OSS Interface Change Management Meeting Topic # Description Date Discussion 1/14/03 - CMP Team cross relating issue with pending T5 to identify next step 73 Prioritization Process Documentation 2/11/03 - Verizon requests clarification of issue or closure. CLEC community object closure 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 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. 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. 5/13/03 - PWG Requirements Review Session scheduled and conducted on May 21, /8/03 - Prioritization process discussed as Agenda Item at the request of the NY PUC staff. Discussion resulted in CLEC community agreeing to draft and revise new language for submission to Verizon at the August CMP meeting. October 2003 East CMP Revisions Dated October 7,

5 October 2003 OSS Interface Change Management Meeting Topic # Description Date Discussion 8/12/03 CLEC community submitted changes to Verizon via . The proposed new language was reviewed at the meeting. Verizon will provide a word document of the April 2001 CMP Agreement. The CLEC community will insert the proposed language in redline format. The redline version will be distributed to the CMP distribution list. Verizon to provide questions or comments at the September CMP meeting. 74 Wholesale Provisioning Tracking System (WPTS) 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 /8/03 - The New Loop capability was not added. Prospects are uncertain. 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, 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. October 2003 East CMP Revisions Dated October 7,

6 October 2003 OSS Interface Change Management Meeting Topic # Description Date Discussion 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 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 dis cussed in the workshop. 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. The Directories are not merging. October 2003 East CMP Revisions Dated October 7,

7 October 2003 OSS Interface Change Management Meeting Topic # Description Date Discussion 4/8/03 - Verizon suggests the removal of Virginia Uniformity documentation found on page 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. 7/8/03 - The CLEC community requested a notation summarizing earlier communication placing the completion of the PA Project on indefinite hold. 76 Billing 1/14/ Vz advised that an 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. 5/21/03 - CLEC concurrence received at May CMP meeting to remove September 2001 January 2003 status. No billing issues to report at May meeting. 7/8/03 o Billing issues discussed. 8/12/03 Verizon will distribute an to the CLEC industry adding a time stamp to the Verizon South NDM Bill format Hour/Minute/Second. This information will assis t in the identification of duplicate or resend s bills. This change is considered to have no CLEC impact. The notice under development will include the format. Verizon is seeking concurrence to implement in the September release. October 2003 East CMP Revisions Dated October 7,

8 October 2003 OSS Interface Change Management Meeting Topic # Description Date Discussion 79 Web Enhancements 02/12/02 - VZ will be giving monthly updates on changes and enhancements to the website: 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 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. October 2003 East CMP Revisions Dated October 7,

9 October 2003 OSS Interface Change Management Meeting Topic # Description Date Discussion 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 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. 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 October 2003 East CMP Revisions Dated October 7,

10 October 2003 OSS Interface Change Management Meeting Topic # Description Date Discussion 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. 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. October 2003 East CMP Revisions Dated October 7,

11 October 2003 OSS Interface Change Management Meeting Topic # Description Date Discussion 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/ 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. 2/11/03 - 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. October 2003 East CMP Revisions Dated October 7,

12 October 2003 OSS Interface Change Management Meeting Topic # Description Date Discussion 3/11/03 - Vz advised that the will be a workshop on March 19, 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. - Vz advised of a CLEC ordering workshop on March 19, /8/03 - Look for new web content pertaining to Billing and Collocation. - The Contact Us section now has Profile information - Visit the Verizon Wholesale Calendar for information associated with a PON workshop scheduled for 7/15. - Questions taken on the Search tool for Wholesale web site as a whole and a specific problem with the Search for the Tariffs info. 85 End User Level Listing Project 5/13/03 - This issue was created at the May CMP meeting to provide a reference point for the many phases associated with this project. 07/8/03 - UNE Loop Listings will be converted to End User Listing Account with Class of Service LXR (residence) and LYB (business). This will provide a retail-like listing structure. - This project will be phased across the jurisdictions and includes BETA conversions. MD, DC and VA Beta conversions were completed in April and June releases. The remainder of MD, DC, VA and WV is scheduled for October 2003, - NY, MA, RI, NH, RI CT and VT Beta conversions are scheduled for August The remainder of conversion in those stated is scheduled in a phased approach between September 2003 and January Notification of Verizon Declared Emergency Conditions - NJ, PA and DE beta conversions are scheduled for October 2003, the remainder of conversions in those states is scheduled in a phased approach between November 2003 and March /12/03 - CLECs reported two situations in July and early August, where due date assignment into New York was suspended because of a Verizon declared emergency condition. CLECs asked for clarification as to 1) the media Verizon uses to notify the CLEC community of these changes, 2) additional information on the treatment of pipeline LSRs impacted by the emergency and 3) the use of unique error messages or response codes during emergency. October 2003 East CMP Revisions Dated October 7,

13 October 2003 OSS Interface Change Management Meeting Topic # Description Date Discussion 87 Wireless LNP Project 8/12/03 - This is a tracking issue associated with CR 2461 Wireless LNP appearing on the IBR for October This issue involves the wireline to wireless porting envisioned as part of the FCC Order with a November 24, 2003 effective date. Verizon CMP extended an invitation to the Wireless community to participate in CMP in anticipation of LSRs to port out a Verizon native number to a wireless provider. Verizon wholesale is not involved in the wireless to wireless or wireless to wireline scenarios. The wireless community is encouraged to 1) initiate a wireless interconnection agreement by contacting Reneee.Ragsdale@Verizon.com, 2) completing the Profile and 3) participate in LSR training. Additional information will be shared with the wireless community over the next couple of months. -. October 2003 East CMP Revisions Dated October 7,

14 Customer Distribution List October 2003 Distribution List

15 Customer Distribution List October 2003 Distribution List

16 Customer Distribution List October 2003 Distribution List

17 Customer Distribution List October 2003 Distribution List

18 Customer Distribution List October 2003 Distribution List

19 Customer Distribution List om October 2003 Distribution List

20 Customer Distribution List October 2003 Distribution List

21 Customer Distribution List October 2003 Distribution List

22 Customer Distribution List October 2003 Distribution List

23 Customer Distribution List October 2003 Distribution List

24 Customer Distribution List October 2003 Distribution List

25 Customer Distribution List October 2003 Distribution List

26 Customer Distribution List October 2003 Distribution List

27 Customer Distribution List October 2003 Distribution List

28 Customer Distribution List m winchj@ctcnet.com wps-ics-east@core.verizon.com Verizon_Change_Control@elec-corp.com wps-ics-east@verizon.com October 2003 Distribution List

29 Verizon-East Wholesale Systems OSS Interface Change Management Meeting Process Verizon-East Wholesale Systems System Implementation System Decommission Preorder LSI Oct-99 - EDI ( LSOG5, v 5.5) Jun-03 Oct-03 EDI ( LSOG5, v 5.6)* Oct-03 Feb-04 EDI ( LSOG5, v 5.7)* Feb-04 Jun-04 EDI ( LSOG6, v 6.1) Jun-03 Oct-03 EDI ( LSOG6, v 6.2)* Oct-03 Feb-04 EDO (LSOG6,v 6.3)* Feb-04 Jun-04 CORBA(LSOG5, v5.5) Jun-03 Oct-03 CORBA(LSOG5, v 5.6)* Oct-03 Feb-04 CORBA (LSAOG5, v 5.7)* Feb-04 Jun-04 CORBA (LSOG6, v 6.1) Jun-03 Oct-03 CORBA (LSOG6, v 6.2)* Oct-03 Feb-04 CORBA (LSOG6, v 6.3)* Feb-04 Jun-04 Order EDI (LSOG5, v 5.5) Jun-03 Oct-03 EDI ( LSOG5, v 5.6)* Oct-03 Feb-04 EDI ( LSOG5, v 5.7)* Feb-04 Jun-04 EDI ( LSOG6, v 6.1) Jun-03 Oct-03 EDI (LSOG6, v 6.2)* Oct-03 Feb-04 EDI (LSOG6, v 6.3)* Feb-04 Jun-04 LSI Oct-99 - Billing BDT (V39) Apr-03 Oct-03 BDT (V40) Oct-03 Apr-04 ASR ASR v26 Mar-03 Sep-03 ASR v27 Sep-03 Mar-04 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 Verizon and TCs reserve the right to seek full application or enforcement of such federal or state requirements or provisions. 3 of 4 * Planned ** Tentative Meeting System Matrix_Qtr-3rd

30 Verizon CMP Topic #73 Prioritization Process WNS OSS Interface Change Management Process Version 2.1 Dated April 2001 Original language: Page 4 III. Change Classifications Type 2 (Regulatory) Change Changes affecting the interfaces between the TC s and Verizon s operational support systems required in order to comply with state or federal law, orders or specific directives by regulatory authorities (such as the Federal Communications Commission), state or federal court orders, or required to meet standards, metrics, or other obligations imposed by, or under agreement with, the FCC or state commissions. Either Verizon or, as applicable, the TC may initiate the Change Request. August 12 CLEC Proposed Modification Type 2 (Regulatory) Change Changes affecting the interfaces between the TC s and Verizon s operational support systems required in order to: 1) Comply with state or federal law, orders or specific directives by regulatory authorities (such as the Federal Communications Commission), state or federal court orders. Verizon will provide written evidence, to the industry, of the specific order or directive issued from the regulatory authority to Verizon. 2) Or required to Meet standards, or metrics, or other obligations imposed by, or under agreement with, the FCC or state commissions. Such change requests would apply to metrics currently not being met by Verizon that result in financial penalties. Verizon will provide documentation that the Change Request is part of an action plan that will result in Verizon meeting the metric and will quantify the expected improvement in performance resulting from the Change Request. The Change Request must reduce financial penalties to Verizon and must be implemented across the entire Verizon East Region. Either Verizon or, as applicable, the TC may initiate the Change Request. OCTOBER 9, 2003 REVISION 2.0 T. RODGERS (215) PAGE 1 OF 11

31 Verizon CMP Topic #73 Prioritization Process September 10 Verizon Response to August 12 Proposed Modification With regard to 1) Verizon seeks clarification on CLEC rationale for the proposed deletion of the CLEC phrase or under agreement with. Verizon has in past collaborative sessions worked with the CLEC community to define solutions without requiring the issuance of an Order. The removal of the language would appear to prevent Verizon from working through issues with the CLECs on an informal basis. With regard to 2), the CLEC proposed language appears not to allow Verizon to do changes that will sustain metric performance. The proposed language eliminates Verizon s ability to maintain and sustain performance. Verizon seeks CLEC comment on why sustaining performance is not considered critical to CLEC operations and interests. Verizon believes that the proper place to discuss C2C issues covered by an Action Plan is with the Carrier Working Group and not CMP. Verizon seeks CLEC comment on the circumstance where a CLEC would initiate a Type 2 Regulatory Change Request under the proposed conditions 1 and 2. September CMP Meeting Discussion The proposed strike of other obligation was not intended to thwart informal discussions. If the initiative is to be considered a Type 2 Regulatory initiative, the agreement should be at least documented in an from the PUC staff member or from meeting minutes. Absent documentation of an informal discussion, the proposed system enhancement should be CLEC or Verizon initiated. CLEC support for Verizon initiatives that sustain metric improvement could be improved if Verizon: Improve visibility of the enhancement prior to packaging into the release. Provide the state where the metric improvement is at risk Provide additional internal review on low volume enhancements Move non CLEC impacting enhancements to non CLEC impacting releases OCTOBER 9, 2003 REVISION 2.0 T. RODGERS (215) PAGE 2 OF 11

32 Verizon CMP Topic #73 Prioritization Process October Verizon Proposed Language Proposed CMP Action Item Type 2 (Regulatory) Change Changes affecting the interfaces between the TC s and Verizon s operational support systems required in order to: 1) Comply with state or federal law, orders or specific directives by regulatory authorities (such as the Federal Communications Commission), state or federal court orders. Verizon will provide written evidence, to the industry, of the specific order or directive issued from the regulatory authority to Verizon. Either Verizon, or as applicable a TC may initiate the Change Request. 2) Meet standards or metrics imposed by, or under written informal agreement with, the FCC or state commissions. Verizon will provide an explanation as to why Verizon has determined the Change Request has been designated as a Type 2 Verizon will inventory pending enhancements currently designated as Type 2 and apply the revised definitions. Initiatives not meeting the revised definitions will be evaluated and presented as a Verizon initiated Type 4 Change Request. Interim meetings will be scheduled in 4Q03 and will complete no later than February OCTOBER 9, 2003 REVISION 2.0 T. RODGERS (215) PAGE 3 OF 11

33 Verizon CMP Topic #73 Prioritization Process WNS OSS Interface Change Management Process Version 2.1 Dated April 2001 Original language: Page 6 VIII. Prioritization Process TCs will use the process below to prioritize, as described above, Type 4 and Type 5 Change Requests. Change Requests may not be implemented in the priority order specified by TCs due to the complexity of the Change Request, the relationship between the implementation of one change and changes specified in other Change Requests, and other factors. Implementation decisions will remain within Verizon s discretion, consistent with applicable law and regulatory authority and resource constraints. Verizon will consider TC prioritization in exercising this discretion. August 12 CLEC Proposed Modification VIII. Prioritization Process TCs will use the process below to prioritize, as described above, Type 4 and Type 5 Change Requests. Change Requests may not be implemented in the priority order specified by TCs due to the complexity of the Change Request, the relationship between the implementation of one change and changes specified in other Change Requests, and other factors. Implementation decisions will remain within Verizon s discretion, consistent with applicable law and regulatory authority and resource constraints. Verizon will consider TC prioritization in exercising this discretion. At each prioritization meeting, Verizon will provide the status of each open change request on the format shown as Attachment A. In cases where the implementation schedule differs materially from the priority order specified by TCs, VZ will provide CLECs with a detailed explanation of the factors that led to its proposed implementation schedule. September 10 Verizon Response to August 12 Proposed Modification Verizon requests CLEC clarification of the following items associated with Attachment A - CR Summary Log. Is Attachment A incremental to the Items by Release Report and the PWG Not Rated/Re-Rated System Impacting Change Requests Type 4 & 5 or a replacement for both reports? If incremental, why wouldn t the CLEC expectation be satisfied by adding Initiative Number and Level of Effort to the existing documents? Please explain the rationale for including Type 1 Change Requests. Please provide a CLEC description of the Status Value Hold. OCTOBER 9, 2003 REVISION 2.0 T. RODGERS (215) PAGE 4 OF 11

34 Verizon CMP Topic #73 Prioritization Process September CMP Meeting Discussion CLECs responded that Attachment A was incremental to existing documentation. They agreed to revisit the importance of the Initiative Number and including Type 1 Change Requests which are Bulletins. Verizon requested the CLECs reconsider the need for Attachment A with assurance that Verizon would add Level of Effort information to existing PWG document. Verizon would also discontinue the use of the DENY status and replace with HOLD. October Verizon Proposed Language TCs will use the process below to prioritize, as described above, Type 4 and Type 5 Change Requests. Change Requests may not be implemented in the priority order specified by TCs due to the complexity of the Change Request, the relationship between the implementation of one change and changes specified in other Change Requests, and other factors. Implementation decisions will remain within Verizon s discretion, consistent with applicable law and regulatory authority and resource constraints. Verizon will consider TC prioritization in exercising this discretion. Verizon prefers the current language for the following reasons. Compliance with the CLEC proposed language obligates a mandatory status of every initiative at every CMP meeting. For Verizon to comply with this expectation, the CMP meeting would need to be expanded by one additional day per month. The CMP meeting material is available for CLEC inspection in advance of the CMP meeting. Verizon s preference is to use the meeting to answer CLEC questions with the status provided. Additional discussion is required. Attachment A contains the same information as currently available, but in a different format. Verizon objects to providing the same information in two different formats. OCTOBER 9, 2003 REVISION 2.0 T. RODGERS (215) PAGE 5 OF 11

35 Verizon CMP Topic #73 Prioritization Process WNS OSS Interface Change Management Process Version 2.1 Dated April 2001 Original language: Page 8 IX. Notification Timelines Notification and confirmation of the scheduled implementation of Change Requests will be accompanied by the appropriate documentation (business rules, technical specifications). Type 1 Notification and confirmation timelines for Type 1 are determined on an individual case basis based on the severity of the problem. August 12 CLEC Proposed Modification IX. Notification Timelines Notification and confirmation of the scheduled implementation of Change Requests will be accompanied by the appropriate documentation (business rules, technical specifications). Type 1 Notification and confirmation timelines for Type 1 are determined on an individual case basis based on the severity of the problem. Initial notification shall be provided to all CLECs within 20 min of identification: e.g. for populating a project field based on systems issues as workaround. September 10 Verizon Response to August 12 Proposed Modification Verizon prefers the original language. The proposed language appears too focused on only one situation. Verizon suggests the creation of a CMP Topic to address the proper use of the project field and distribution to all CLEC as the appropriate course of action address this situation. OCTOBER 9, 2003 REVISION 2.0 T. RODGERS (215) PAGE 6 OF 11

36 Verizon CMP Topic #73 Prioritization Process September CMP Meeting Discussion During discussions CLECs mentioned a need for broader distribution of information associated with the use of the project field. CLECs preferred the language as suggested and requested Verizon counter with a different notification interval. October Verizon Proposed Language Type 1 Notification and confirmation timelines for Type 1 are determined on an individual case basis based on the severity of the problem. Verizon prefers the original language. OCTOBER 9, 2003 REVISION 2.0 T. RODGERS (215) PAGE 7 OF 11

37 Verizon CMP Topic #73 Prioritization Process WNS OSS Interface Change Management Process Version 2.1 Dated April 2001 Original language: Page 8 IX. Notification Timelines Notification and confirmation of the scheduled implementation of Change Requests will be accompanied by the appropriate documentation (business rules, technical specifications). Type 2 Timelines for Type 2 Change Requests are, in general, determined based on applicable law/regulatory rules. If timelines are not specified by the regulatory action and business rules are impacted, reasonable efforts will be made to follow, for Type 2 Change Requests, the same notification intervals for Type 4 and Type 5 Change Requests. Verizon will use reasonable efforts to provide at least 45 days notification prior to implementation of Type 2 Change Requests that do not impact business rules. August 12 CLEC Proposed Modification IX. Notification Timelines Notification and confirmation of the scheduled implementation of Change Requests will be accompanied by the appropriate documentation (business rules, technical specifications). Type 2 Timelines for Type 2 Change Requests are, in general, determined based on applicable law/regulatory rules. If timelines are not specified by the regulatory action and business rules are impacted, reasonable efforts will be made to follow, for Type 2 Change Requests will follow the same notification intervals for Type 4 and Type 5 Change Requests. Verizon will use reasonable efforts to provide at least a minimum 45 days notification prior to implementation of Type 2 Change Requests that do not impact business rules. September 10 Verizon Response to August 12 Proposed Modification Verizon understands the importance placed on the introduction of Type 2 changes with business rule impact. OCTOBER 9, 2003 REVISION 2.0 T. RODGERS (215) PAGE 8 OF 11

38 Verizon CMP Topic #73 Prioritization Process September CMP Meeting Discussion Reviewed without comments noted. October Verizon Propose Language Type 2 Timelines for Type 2 Change Requests are, in general, determined based on applicable law/regulatory rules. If timelines are not specified by the regulatory action and business rules are impacted Type 2 Change Requests will follow the same notification intervals for Type 4 and Type 5 Change Requests. Verizon will provide a minimum 45 days notification prior to implementation of Type 2 Change Requests that do not impact business rules. Verizon accepts the CLEC proposed language. OCTOBER 9, 2003 REVISION 2.0 T. RODGERS (215) PAGE 9 OF 11

39 Verizon CMP Topic #73 Prioritization Process WNS OSS Interface Change Management Process Version 2.1 Dated April 2001 Original language: Page 9 IX. Notification Timelines Notification and confirmation of the scheduled implementation of Change Requests will be accompanied by the appropriate documentation (business rules, technical specifications). Type 4 and Type 5 Generally, notification of the scheduled implementation of Type 4 and Type 5 changes will follow the schedule below: 73 days prior to implementation draft business rules are published 66 days prior to implementation draft technical specifications are published TCs have 15 business days from publication of documents to provide comments 45 days prior to implementation change confirmation occurs through the publication of final business rules, technical specifications and error message documentation. For Type 4 and Type 5 Change Requests, in some instances, it will make sense to provide more notification, or less notification, based upon the severity and the impact of the change. For example, if the change has a benefit and has little material impact on the interface, Verizon will bring the Change Request to the TCs with for implementation with shortened notification timelines. An example of such a change is the introduction of new functionality that does not impact existing functionality. More notification would be provided in the case of a major backend system introduction that significantly impacts the OSS interface. August 12 CLEC Proposed Modification BETA Testing Verizon will inform the CLEC community of any proposed Beta trial and solicit volunteer CLECs to participate in the trial, prior to any development work. September 10 Verizon Response to August 12 Proposed Modification Verizon considers the additional language unnecessary and linked to a one time situation. Verizon believes there is sufficient precedent that Verizon has initiated BETA trials and involved as many CLECs as Verizon could support in the trials. Verizon is not opposed to the language with CLEC clarification on the intent of the phrase, prior to any development work. OCTOBER 9, 2003 REVISION 2.0 T. RODGERS (215) PAGE 10 OF 11

40 Verizon CMP Topic #73 Prioritization Process September CMP Meeting Discussion Verizon s proposed strike of the phrase, prior to any development work was not objected too. October Verizon Proposed Language BETA Testing Verizon will inform the CLEC community of any proposed Beta trial and solicit volunteer CLECs to participate in the trial. OCTOBER 9, 2003 REVISION 2.0 T. RODGERS (215) PAGE 11 OF 11

41 Change Control Items by Release Release October 18, 2003 Committed CR # / Initiative #/ Description of Change Request CR Type Data Added Title: Expand Parsed CSR functionality to include Complex Listings Description: This change request will expand the existing CSR parsing functionality to encompass all complex listings associated with an account. 5 6/3/03 Business Narrative: Complex listing information will be parsed in discreet fields, which correspond to the OBF listing fields. Today, the parsed CSR does not return complex listings. Complex listings include caption and straight line under listings. Comment: Phase I implementation February 2002 included simple additional listings, phase II implementation June 2002 included simple main listings. Reason: Enhancement Jurisdiction: North, South System: EDI, CORBA; Primary Area Resale, UNE, UNE-P LSOG Version: LSOG 5 and above Documentation Impact: LSOG 5, LSOG 6 Business Rules Pre Order 1 of 25 October 7, 2003 Page 1 of 25

42 Release October 18, 2003 Committed CR # / Initiative #/ Description of Change Request CR Type Data Added Title: Expand Parsed CSR functionality to include Grandfathered Centrex accounts. Description: This change request will expand the existing CSR parsing functionality to encompass all grandfathered centrex accounts. Same logic will be applied as was implemented with the October 2002 release with parsing for non-grandfathered centrex accounts. Reason: Enhancement Jurisdiction: North, South System: EDI, CORBA; Primary Area Resale, UNE-P LSOG Version: LSOG 5 and above 5 6/3/03 October 18, 2003 Committed Documentation Impact: LSOG 5, LSOG 6 Business Rules Pre Order Title: Line Loss Reporting Enhancements - Remove APON field from Line Loss Report Description: This change request will remove the APON field from Provider Notification. The APON field is not applicable to Wholesale. The field currently appears on the NDM provider notification record. It is being removed, as it is unnecessary. 5 10/7/03 Reason: Enhancement Comment: Primary phase implementation in February 2003 removed intra core company migrations from line loss report. Jurisdiction: North, South System: NDM Primary Area: Resale, UNE-P, UNE LSOG Version: NA Documentation Impact: Provider Notification 2 of 25 October 7, 2003 Page 2 of 25

43 Release October 18, 2003 Committed Change North BETA to December 2003 from August 2003 and full conversion (North) from September 2003 to January 2004 CR # / Initiative #/ and and Description of Change Request CR Type Data Added 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 12/03 BETA (Phase 9) Full conversion DE, NJ, PA 10/03 - BETA 11/03 4 4/1/03 Reason: Enhancement Comments: Additional phases: Phase 9 - Committed December 2003; Phase 15 Candidate January 2004 Jurisdiction: MD, DC, VA, WV, NJ, PA, DE; 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 3 of 25 October 7, 2003 Page 3 of 25

44 Release October 18, 2003 Committed CR # / Initiative #/ Description of Change Request CR Type Data Added Title: Wireless LNP Description: The purpose of this initiative is to prepare all Verizon systems for the porting out and porting in of wireless telephone numbers. Per FCC Docket , all carriers must prepare their networks and enable their systems to accommodate porting of telephone numbers between wireless carriers and wireline/wireless carriers. 2 6/3/03 Reason: FCC Mandate FCC Docket Jurisdiction: North, South; System: LSI, EDI; Primary Area: UNE LSOG Version: LSOG 5 and above. Documentation Impact: LSOG 5, LSOG 6 Business Rules Order 4 of 25 October 7, 2003 Page 4 of 25

45 Release October 18, 2003 Committed CR # / Initiative #/ Description of Change Request CR Type Data Added 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. Reason: System enhancement Comments: Phase 2 is Committed for December Jurisdiction: North, South System: Other; Primary Area: Resale, UNE, UNE-P; LSOG Version: 5 and above 5 5/6/03 October 18, 2003 Committed & Documentation Impact: None Title: LSOG 6: Miscellaneous Changes Description: This change request will revise edits for caption lists to replicate the LSOG 5 process. Reason: Industry Standard 3 6/3/03 Jurisdiction: North & South; System: LSI, EDI; Primary Area: UNE, Resale, UNE-P; LSOG Version: 6 Documentation Impact: LSOG 6 Order Business Rules 5 of 25 October 7, 2003 Page 5 of 25

46 Release October 18, 2003 Committed CR # / Initiative #/ Description of Change Request CR Type Data Added Title: Hot Cuts for xdsl Loops Description: The scope of this initiative is to introduce hot cuts for xdsl loops. The following scenarios are in scope for this project: 1-Retail, Resale,Platform POTS to 2 Wire ISDN Loop with and without LNP 2-Retail, Resale, Platform ISDN(BRI) to 2 Wire ISDN Loop with and without LNP 3-Retail, Resale,Platform POTS to 2 Wire ADSL-C with and without LNP 2 Wire ADSL-R with and without LNP Very Low Band Class 1 DSL with and without LNP Low Band Class 2 DSL with and without LNP 2 Wire HDSL Loop with and without LNP 2 wire Non Conforming Loops with and without LNP The following CFA changes are in scope for this project:: -Change of POT BAY assignment (Analog and Digital Loops in the North) -Change the PORT Assignment (Analog and Digital Loops in the South -Change in Splitter Assignment Line Sharing/Splitting North and South) Business Narrative: Currently Verizon offers Hot Cuts for migrations from Retail POTS and ISDN service to 2 Wire Analog and 2 Wire ISDN Loops with or without number portability. As the Digital XDSL UNE Loops (including Line Sharing and Line Splitting) are more widely deployed, the CLEC/DLEC community has requested we entertain performing Hot Cuts on a number of digital Loop scenarios. Additionally, we have been mandated to provide these Hot Cuts in New Jersey and New York/CT as part of our agreements with the commissions in these states. 2 6/3/03 Reason: Regulatory mandate PSC916 - agreed at NY DSL collaborative Jurisdiction: North & South; System: LSI, EDI; Primary Area: UNE; LSOG Version: 5 and above Documentation Impact: LSOG 5 & 6 Order Business Rules 6 of 25 October 7, 2003 Page 6 of 25

47 Release October 18, 2003 Committed CR # / Initiative #/ Description of Change Request CR Type Data Added Title: Special Characters Description: The change request would identify at a field level any applicable special characters that are supported. Phase 1 will include the following forms: LSR, EU, HGI, LS, LSNP, DL, NP, PS, RS. Reason: Documentation Enhancement Comments: Phase 2 is a candidate for February Jurisdiction: North & South; System: NA; Primary Area: UNE, UNE-P, Resale; LSOG Version: 5 and above 5 6/3/03 October 18, 2003 Committed and Documentation Impact: LSOG 5 & 6 Order Business Rules 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. 3 3/4/03 Comments: This initiative will care for Type 5 CR1102, Application to Application interface for UNE Loop Trouble Administration. the XML Pilot - CR 1102, (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 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 7 of 25 October 7, 2003 Page 7 of 25

48 Release October 18, 2003 Committed CR # / Initiative #/ Description of Change Request CR Type Data Added Title: Identify if DLC has copper for xdsl loop qual Description: The purpose of this initiative is to expand the functionality of the xdsl loop qualification transaction to designate if loop with DLC has loaded copper and to provide loop length. This new functionality will also be provided in the DSL Extract. Reason: System Enhancement Jurisdiction: North & South; System: LSI, EDI, CORBA; Primary Area: UNE, Resale, UNE-P; LSOG Version: 5 and above 5 6/3/03 October 18, 2003 Committed Documentation Impact: LSOG 5 & 6 Business Rules - Pre Order, DSL Extract 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. 4 7/2/02 Comments: Phase 1 of this initiative was completed in October 2002 under Phase 3 is a Candidate for February 2004; Phase 4 is a Candidate for April Reason: System Enhancement Jurisdiction: North & South; System: LSI; Primary Area: UNE, Resale, UNE-P; LSOG Version: 5 and above Documentation Impact: LSI Users Guide 8 of 25 October 7, 2003 Page 8 of 25

49 Release October 18, 2003 Committed CR # / Initiative #/ Description of Change Request CR Type Data Added Title: Create RSU Flag in xdsl Loop Qualification Description: The purpose of this initiative is expand functionality of the xdsl loop qualification transaction to identify if a location or WTN is serviced by a remote switch or remote terminal. This new functionality will also be provided in the DSL Extract. Reason: System Enhancement Jurisdiction: North & South; System: LSI, EDI, CORBA; Primary Area: UNE, Resale, UNE-P; LSOG Version: 5 and above 5 6/3/03 October 18, 2003 Committed Documentation Impact: LSOG 5 & 6 Business Rules - Pre Order, DSL Extract Title: Provide an electronic delivery method for Customer Service records that exceed the 10K Line Count Description: The goal of this initiative is to provide a method to return CSRs that exceed the 10K limit by notifying the CLEC that the maximum line size has been exceeded. The CSR will then be automatically transmit to a server for retrieval via NDM or FTP. 5 6/3/03 Reason: Process change Jurisdiction: North & South; System: LSI, EDI, CORBA; Primary Area: Resale, UNE, UNE-P; LSOG Version: 5 and above Documentation Impact: LSOG 5 & 6 Pre Order Business Rules 9 of 25 October 7, 2003 Page 9 of 25

50 Release October 18, 2003 Committed CR # / Initiative #/ Description of Change Request CR Type Data Added Title: Allow PSEBE on UNE & UNE-P Payphone Services Description: The purpose of this initiative is to allow limited interlata dialing feature (USOC: PSEBE) and one-way service restriction (USOC: PSEB1) on UNE & UNE-P Payphone services in NJ. Reason: Regulatory Mandate - FCC 1, Section 6 Access Tariff and Verizon NJ B.P.U. No. 2 Sec. 6 Jurisdiction: NJ; System: Other; Primary Area: UNE, UNE-P; LSOG Version: 5 and above 2 6/3/03 October 18, 2003 Committed C Documentation Impact: LSOG 5, LSOG 6 Business Rules Order Title: Flow Through Customized Routing Description: The purpose of this initiative is to provide flow through of Customized Routing. Reason: Flow through - Metric OR501, OR /3/03 Jurisdiction: South; System: Other; Primary Area: UNE-P; LSOG Version: 5 and above Documentation Impact: Flow through scenarios 10 of 25 October 7, 2003 Page 10 of 25

51 Release October 18, 2003 Committed CR # / Initiative #/ C Description of Change Request CR Type Data Added Title: Define value for Status field on Address Validation Transaction Description: This change request is will provide clarification to STATUS field on the Address Validation Response, the TOS field on the Scheduling Availability Response and the WSOP field on the End User Form. 5 10/7/03 Business Narrative : Phase 1 is documentation only and provides additional clarity to certain fields in an effort to demonstrate how they work together. Reason: Enhancement Comment: Issued as bulletins 2942 for Pre-Order changes and 2943 for Order changes. Jurisdiction: North, South System: NA; Primary Area: Resale, UNE-P LSOG Version: LSOG 5 and above Documentation Impact: LSOG 5, LSOG 6 Business Rules Pre Order and Order 11 of 25 October 7, 2003 Page 11 of 25

52 Release December 20, 2003 Candidate CR # / Initiative #/ Description of Change Request CR Type Data Added Title: Process at Level 5 when BTN is migrated for a Partial Migration Description: The purpose of this initiative is to process all requests for Partial Migrations with the Billing Telephone Number being migrated are processed at Level 2 by the NMC. The current process needs to be modified to process these requests at Level 5. Reason: Flow through Metric OR501, OR503 Comment: North and NJ, PA, DE completed in Aug 02. Jurisdiction: South; System: Other; Primary Area: UNE; Version: LSOG 5 and above 2 4/2/02 December 20, 2003 Committed Documentation Impact: None 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 this is not being done. It is not known whether additional blocks are required. 4 10/7/03 Reason: Flow through Metric OR501, OR503 Jurisdiction: South; System: LSI, EDI; Primary Area: UNE-P, Resale; Version: LSOG 5 and above Documentation Impact: Edits 12 of 25 October 7, 2003 Page 12 of 25

53 Release December 20, 2003 Committed CR # / Initiative #/ Description of Change Request CR Type Data Added Title: Ignore Local Provider Freeze for intra-company migrations Description: The goal of this initiative is to change the process so that CLECs can migrate their OWN customers from one product to another even if there is a freeze (RSCP) on the line, i.e. from Resale to UNE- P. Minor business rules changes to add field note for clarification. Received industry 8/12 CMP okay to implement in December with business rules change via bulletin. Reason: Process change Jurisdiction: North & South; System: LSI, EDI; Primary Area: Resale, UNE, UNE-P; LSOG Version: 5 and above 5 6/3/03 December 20, 2003 Committed Documentation Impact: LSOG 5, LSOG 6 Business Rules Order Title: Flowthrough for Wholesale for Digital Companion Description: The goal of this initiative is to ensure that Digital Companion FIDs and USOCs are removed on migrations. 4 10/7/03 Reason: Flow through Metric OR501, OR503 Jurisdiction: North & South; System: LSI, EDI; Primary Area: Resale, UNE, UNE-P; LSOG Version: 5 and above Documentation Impact: Edits 13 of 25 October 7, 2003 Page 13 of 25

54 Release February 21, 2004 Candidate CR # / Initiative #/ Description of Change Request CR Type Data Added Title: Expand Parsed CSR Functionality to include ISDN accounts Description: This change request will expand the existing CSR parsing functionality to encompass all ISDN accounts. Reason: Enhancement Jurisdiction: North, South; System: EDI, CORBA; Primary Area: Resale, UNE-P LSOG Version: LSOG 5 and above. 5 6/3/03 February 21, 2004 Candidate Documentation Impact: LSOG 5, LSOG 6 Business Rules Pre Order Title: Expand Parsed CSR Functionality to include all Private Line service Description: The purpose of this initiative would allow the CLEC's to view all Private Line service on the CSR. 5 9/2/03 Reason: System enhancement Jurisdiction: North & South; System: EDI, CORBA; Primary Area: UNE, Resale; LSOG Version: LSOG 5 and above. Documentation Impact: LSOG 5, LSOG 6 Business Rules Pre Order 14 of 25 October 7, 2003 Page 14 of 25

55 Release February 21, 2004 Committed CR # / Initiative #/ Description of Change Request CR Type Data Added Title: Allow limited use of the EBD (Effective Bill Date) field for Number Portability requests Description: The goal of this project is to allow limited use of the EBD field for NP requests. Currently, Verizon does not accept an EBD on the LSR. Reason: Regulatory - NY PSC Case 01-C-0095 footnote 104 and Virginia CC Docket No Jurisdiction: NY, VA; System: LSI, EDI; Primary Area: UNE; LSOG Version: LSOG 5 and above. 2 9/2/03 February 21, 2004 Candidate Documentation Impact: LSOG 5 & 6 Order Business Rules Title: Creation of SUP types 4 & 5 Description: Phase 5 of this initiative will change two NMC directed edits/errors created in phase 4. Phase 4 was implemented in August The two edits involved are: edit for an LNUM match and edit for a SYS ID verification. Phase 5 will change these edits from NMC to CLEC bound errors. 2 3/4/03 Reason: Flow through Metric OR501, OR503 Comments: Phase 2 Candidate December 2003, Phases 3 and 4 Completed August 2003 Jurisdiction: North & South; System: LSI, EDI; Primary Area: UNE; LSOG Version: 5 and above Documentation Impact: LSOG 5 & 6, Order Business Rules 15 of 25 October 7, 2003 Page 15 of 25

56 Release February 21, 2004 Candidate CR # / Initiative #/ Description of Change Request CR Type Data Added Title: Flow Through changes from Business to Residence or Residence to Business Description: The goal of this project is to improve flow through on Platform & Resale requests to change from Business to Residence or Residence to Business at migration or post migration. There are major Business Rules changes along with the introduction of a new LSR field. Reason: Flow through Jurisdiction: North & South; System: LSI, EDI; Primary Area: UNE-P, Resale; LSOG Version: 5 and above 2 6/3/03 February 21, 2004 Committed Documentation Impact: LSOG 5 & 6 Order Business Rules Title: Special Characters Description: The change request would identify at a field level any applicable special characters that are supported. Phase 2 will include all order forms not covered in phase Reason: Documentation Enhancement Jurisdiction: North & South; System: NA; Primary Area: UNE, UNE-P, Resale; LSOG Version: 5 and above February 21, 2004 Committed Documentation Impact: LSOG 5 & 6 Order Business Rules Title: LSOG 5 Miscellaneous Changes Description: The goal of this initiative is to modify LSOG 5 items that did not get included per the standard correctly when LSOG 5 was implemented Reason: Industry Standard Jurisdiction: North & South; System: LSI, EDI, CORBA; Primary Area: UNE; LSOG Version: 5 Documentation Impact: LSOG 5, Order Business Rules 16 of 25 October 7, 2003 Page 16 of 25

57 Release February 21, 2004 Candidate CR # / Initiative #/ Description of Change Request CR Type Data Added Title: Platform Disconnect All Lines Description: This request will allow CLECs to use TNS=A for a complete platform account disconnect. Also, if a CLEC chooses to list all lines, an edit will be created to require all lines be listed for disconnect or the request will be rejected. Reason: System Enhancement Jurisdiction: North & South; System: LSI, EDI; Primary Area: UNE-P; LSOG Version: 5 and above 2 6/3/03 February 21, 2004 Candidate C Documentation Impact: LSOG 5 & 6 Business Rules - Order, Service Order Mapping Title: Revise the hunting format for the parsed CSR Description: The change request will enhance the return of hunting information for the parsed CSR by returning each hunting telephone numbers in a separate field. 5 10/7/03 Reason: System enhancement Jurisdiction: North & South; System: EDI, CORBA; Primary Area: UNE, Resale, UNE-P; LSOG Version: 5 and above Documentation Impact: LSOG 5 & 6 Business Rules Pre Order 17 of 25 October 7, 2003 Page 17 of 25

58 Release February 21, 2004 Candidate CR # / Initiative #/ C Description of Change Request CR Type Data Added Title: Add Trouble Ticket/PON information to BDT Description: The purpose of the initiative is to pass the trouble ticket number and/or PON, through to the Wholesale BDT files and populated on the OC&C record when a repair charge is billed. This is currently done with (Special) Access accounts. Reason: System enhancement Jurisdiction: North; System: Other; Primary Area: UNE, Resale, UNE-P; LSOG Version: NA 5 9/2/03 February 21, 2004 Candidate C Documentation Impact: None Title: Revise STAT Field on Address Validation Transaction Description: The purpose of this initiative is to strip out the DCR (Disconnect Code Reason) from the Status information in the Address Validation transaction. 5 9/2/03 Reason: System enhancement Jurisdiction: North & South; System: LSI, EDI, CORBA; Primary Area: UNE, Resale, UNE-P; LSOG Version: 5 and above Documentation Impact: LSOG 5 & 6 Business Rules Pre Order 18 of 25 October 7, 2003 Page 18 of 25

59 Release February 21, 2004 Candidate CR # / Initiative #/ C Description of Change Request CR Type Data Added Title: : Enhance Cut Through Functionality Description: Due to requests from the CLEC community, Verizon will implement a real-time interface between our address repository and our facility repository for Cut Through facilities. This will enable more accurate information provided. In addition Verizon will add new functionality that will allow for the number of cut through facilities available up to 10. This functionality is available for Residence only. Reason: System enhancement Jurisdiction: North & South; System: LSI, EDI, CORBA; Primary Area: Resale, UNE-P; LSOG Version: 5 and above 4 10/7/03 February 21, 2004 Candidate C Documentation Impact: LSOG 5 & 6 Business Rules Pre Order Title: LSI-RETAS make fields required for Create, Modify, and Inquiry Description: The purpose of this initiative is to change the end customer person name and end customer person reach TN to required for trouble ticket create, modify, and inquiry. 4 10/7/03 Reason: System enhancement Jurisdiction: North & South; System: LSI; Primary Area: Resale, UNE-P; LSOG Version: NA Documentation Impact: Business Rules Trouble Maintenance 19 of 25 October 7, 2003 Page 19 of 25

60 20 of 25 October Release VERIZON EAST ERROR CODES FOR ITEMS BY RELEASE REPORT CR Number Initiative Title LSOG Change/N ew/delete Form Field Name Error Code # Error Code Message 2397 End User Level UNE Listing Accounts 5 & 6 Change DL LACT DL095 If the LACT is not null then it must be a value of N, when the REQTYP is AB and the ACT is N. 5 New DL LACT DL160 If the LACT is not null then it must be a value of N, when the REQTP is AB and the ACT is V and the ERL field is not equal to E or P. 5 New DL LACT DL161 If the LACT is not null then it must be a value of D, I, N or Z, when the REQTP is AB and the ACT is V and the ERL field = E or P. 6 New DL LACT DL162 If the LACT is not null then it must be a value of N, when the REQTP is AB and the ACT is V and the ELT field is not equal to E or P. 6 New DL LACT DL163 If the LACT is not null then it must be a value of D, I, N or Z, when the REQTP is AB and the ACT is V and the ELT field = E or P Wireless LNP 5 Change DRS NPI 8001 When the first position of the LSR REQTYP = N, the only valid entry is C, D, E or F. 5 & 6 Change CRS NPI CR012 When the first position of the REQTYP field on the LSR Form is P, the only valid entry is C, D, E or F. 5 & 6 Add CRS NPI CR051 When the LSR NPDI = B the only valid entry that is optional is E. 5 Add DRS NPI DRS013 When the LSR NPDI = B, the only valid entry that is optional is E. 5 & 6 Add PS NPI PS105 Required when the NPDI field on the LSR Form = B or D, otherwise prohibited. 5 & 6 Add PS NPI PS106 A valid Value of E or F is required when the NPDI field on the LSR Form = B. 5 & 6 Add PS NPI PS107 A Valid Value of C or F is required when the NPDI field on the LSR Form = D. 5 & 6 Delete RS NPI RS001 (Field) required when ONSP is populated, otherwise prohibited. 5 & 6 Add RS NPI RS084 Required when the NPDI field on the LSR Form = B or D, otherwise prohibited. 5 & 6 Add RS NPI RS085 A Valid Value of E or F is required when the NPDI October 7, 2003 Page 20 of 25

61 CR Number 21 of 25 Initiative Title LSOG Change/N ew/delete Form Field Name Error Code # October 7, 2003 Page 21 of 25 Error Code Message field on the LSR Form = B. 5 & 6 Add RS NPI RS086 A Valid Value of C or F is required when the NPDI field on the LSR Form = D. 5 Change LSR ONSP SR031 Required when the REQTYP is DB, EB, FB or MB and any NPI field on the PS or RS Form = C or E, or when REQTYP is NB or PB and any NPI field on the CRS, DRS Form = C, D or E, otherwise prohibited. 6 Change LSR ONSP SR031 Required when the REQTYP is DB, EB, FB or MB and any NPI field on the PS or RS Form = C or E, or when REQTYP is NB or PB and any NPI field on the CRS, DDPS Form = C, D or E, otherwise prohibited. 6 Add LSR NPDI SR197 Required when ((the first position of the REQTYP field = B or C ) or ((the first position of the REQTYP field = D, E, F, P or N ) and (at least one occurrence of the NPI field on the PS, RS, CRS or DDPS Form = C or E ))), otherwise prohibited. 5 Add LSR NPDI SR197 Required when ((the first position of the REQTYP field = B or C ) or ((the first position of the REQTYP field = D, E, F, P or N ) and (at least one occurrence of the NPI field on the PS, RS, CRS or DRS Form = C or E ))), otherwise prohibited. 6 Add LSR NPDI SR198 A Valid Entry of B or D is required when ((the first position of the REQTYP field = D, E, F, P or N ) and (at least one occurrence of the NPI field on the PS, RS, CRS or DDPS Form = C or E )). 5 Add LSR NPDI SR198 A Valid Entry of B or D is required when ((the first position of the REQTYP field = D, E, F, P or N ) and (at least one occurrence of the NPI field on the PS, RS, CRS or DRS Form = C or E )). 5 & 6 Add LSR NPDI SR199 A Valid Entry of C or D is required when the first position of the REQTYP field = C. 5 & 6 Add LSR NPDI SR200 A Valid Entry of D is required when the first position of the REQTYP field = B. 6 Add DDPS NPI DDPS029 When the LSR NPDI = "B" the only valid entry that is optional is "E". 6 Add DDPS NPI DDPS030 When the first position of the LSR REQTYP = "N", the

62 CR Number Initiative Title LSOG Change/N ew/delete Form Field Name Error Code # Error Code Message only valid entry is "C", "D", "E" or "F" Directory Fields LVL 6 Change DL PLS DL103 Required when the DOI field is greater than or equal to 2, otherwise prohibited. 6 Change DL PLINFO DL104 Required when the DOI field is greater than or equal to 2, otherwise prohibited. 6 Delete DL PLS DL156 A Valid Entry of N is prohibited when the corresponding PLTN field is populated 2632 Hot Cuts for xdsl Loops 5 & 6 Add N/A SYSTEM EDIT 7020LN24 Circuit found on Account is not eligible for Migration. 5 & 6 Add LS TNT LS072 Prohibited when ((the 2 nd character of the TOS field = 2 ) and (the 3 rd character of the TOS field = 1, 2, 3, 4, 6 or R )), otherwise optional (PA only). 5 & 6 Add LSNP TNT LSNP039 Prohibited when ((the 2 nd character of the TOS field = 2 ) and (the 3 rd character of the TOS field = 1, 2, 3, 4, 6 or R )), otherwise optional (PA only). 5 & 6 Change LSR CHC SR010 Required when the first position of the REQTYP field is A, B or M ) and (the ACT field = V and the LNA field on the LS Form = V ) and ((the 2 nd character and 3 rd character of the TOS field = 1-, 15, 35 or 49 ) and the SLI field is not equal to B )). 5 & 6 Add LSR CHC SR201 Required when ((the first position of the REQTYP field = A, B or M ) and (the ACT field = V and the LNA field on the LS Form = W ) ((the 2 nd and 3 rd characters of the TOS field = 1-, 15, 1R, 21, or 2R ) and the SLI field is = S )). 5 & 6 Add LSR CHC SR202 When the first position of the REQTYP field is A, then the ACT field must be C, D, N or V. 5 & 6 Add LSR CHC SR203 When the 2 nd character of the TOS field = Z, the valid entry N is prohibited. 5 & 6 Add LSR NC SR204 Required when (the 1 st position of the REQTYP = A or B ) and (ACT field = V ) and (the LNA field on the LS or LSNP Form = V ) and (2 nd character of the TOS field = 2 ) and (the 3 rd character of the TOS field = 1, 2, 3, 4, 6 or R ). 22 of 25 October 7, 2003 Page 22 of 25

63 VERIZON EAST ERROR CODES FOR ITEMS BY RELEASE REPORT December Release CR Initiative Title LSOG Change/N Form Field Name Error Code # Error Code Message Number ew/delete 2823 TD7 valid as a Block entry only 5 & 6 New RS FEATURE RS087 USOC invalid for field. 5 & 6 New CRS FEATURE CR052 USOC invalid for field. 5 & 6 New PS FEATURE PS108 USOC invalid for field. C FT for Wholesale for Digital Companion 5 & 6 Change NA System Edit 7030V185 USOC (Existing error with new use) 23 of 25 October 7, 2003 Page 23 of 25

64 December Release Industry Notification Letter September 30, 2003 Dear Customer: SUBJECT: AVE ROLLOUT PHASE 8 This is a notification that Verizon will be adding edits to the Access Validation Engine (AVE) process effective December 13, We will continue to edit for REQTYPs of M, S, E, V and X, with Activities (ACTs) of N, M, C, T, D and R, as well as validation at the META and form levels for REQTYPs of L, A, W and R. We are adding the fields on the TQ form to our validation process. Implementation will occur simultaneously in Verizon North, South and West. The following is Verizon s batch file implementation schedule. Please note that the clock times listed below refer to Eastern Daylight Time: Saturday, December 13, 2003: All Verizon Service Regions until 11:59 PM: All in-scope inbound ASRs with ACTs = N, M, T, C, D and R will be edited through the Access Validation Engine without implementation of new edits or fields on the TQ form. Sunday, December 14, 2003: All Verizon Service Regions after 12:00 AM: Access Validation Engine Business Rules can be found at: All in-scope inbound ASRs with ACTs = N, M, T, C, D and R will be edited through the Access Validation Engine including validation of all new edits and fields on the TQ form. 24 of 25 October 7, 2003 Page 24 of 25