Ms. Derrig you may begin.

Transcription

1 Verizon Internal September 14, 2005 Confirmation # Operator: Pardon the interruption, Jean Derrig now joins. All lines will be open and interactive throughout the call. If you should need operator assistance please pick up your handset and press star, then zero, and an operator will be standing by to assist you. If you are unable to mute your line from your end you can press star, six on your touchtone phone and that will mute and unmute your line. Again to mute your line you can press star, six, on your touchtone phone. Ms. Derrig you may begin. Thank you. Good morning everyone and welcome to the September 2005 East change management meeting. I want to thank everyone for their flexibility on the change of date as well. I m going to start by going around the room and having everyone introduce themselves and then I will ask for the CLECs to introduce themselves on the phone. Peggy Rubino: Linda Dorsey: Alex Kuhner: Madison Berry: Pam Beattie: Ann Kawolchik (sp?): Beth Cohen, Verizon. Peggy Rubino, Trinsic. Linda Dorsey, PWC. Alex Kuhner, ATX. Madison Berry, CTSI. Pam Beattie, DSCI. Mike Clancy, Covad Communications. Ann Kawolchik, Verizon. OK, and can the CLECs on the conference bridge please introduce themselves. Carol Frike: Chris Gambino: Kent Mingy: Carol Frike with Sprint. Chris Gambino, Cablevision. Kent Mingy (sp?), Comcast.

2 Lisa Provenzo: Melanie Desmaris: Jennifer Kuhns: Rebecca Baldwin: Ninsa Bennett: Communications. Dok Matthews: Leo Dimitriadis: Larry Blair: Shelley Pascoe: James McCluskey: Lisa Provenzo, MCI. Melanie Desmaris, CTC Communications. Jennifer Kuhns, Broadview Network. Rebecca Baldwin, Telcove. Ninsa Bennett and Gayle Gissendanner for Cox Dok Matthews at Penn Telecom. Leo Dimitriadis, AT & T Consumer. Larry Blair, Remi Communications. Shelley Pascoe with ChoiceOne Communications. James McCluskey with Accenture. Any other CLECs that have not announced themselves. John Guzman: Carol Yozzo. Carol Yozzo: Sue Pistacchio: Dan Duris: John Guzman with Synchronous. Any others? All right, I m looking for my presenters. Yes I m here. Sue Pistacchio. I m here. Dan Duris. Yes. Is anyone sitting in for Cindy Vaughan? OK, I ll be covering that I guess. Joan? Joan Costello: Yes I m here. Jamey Rawls?

3 Jamey Rawls: Stephen Cuttle: Yes I m on. Right, thank you, and Stephen Cuttle. Yes I m on Jean. OK thanks everyone. All right let s start with the agenda. The first agenda item is LSOG 5 and LSOG 9, Carol. Carol Yozzo: Thank you Jean, good morning everyone. I ll give you the LSOG 5 sunset side of that anyway. We are on target to have all CLECs transitioned before the sunset in October. As it now stands we ve got about 85% of our EDI activity coming in in LSOG 6, which is very good. We know we have a few CLECs that are still in the process of doing their CTE testing and we hope to get them through within the next couple of weeks and get them into LSOG 6 but we re looking like we are in very good shape at this point. LSI is doing even better, we re about 95% of our activity is already in LSOG 6 and by the time you factor in any supplemental activity on existing LSOG 5 PONs I think we re in very good shape there. So as far as the transition goes, that pretty much covers it unless there are any questions. I ll still talk about pipeline though in a minute. Are there questions on transitioning? OK then, as far as the pipeline goes we are in the process of providing files to CLECs that still have any LSOG 5 PONs in the pipeline and those are any PONs that are due after sunset or any PONs that appear to be abandoned, namely rejects, jeoped or queried PONs, so anything that needs attention, needs to be cleaned up, we will be notifying the CLECs with those, and the volume is very low. I believe I said that the last month or two in fact, that we are, we have a very manageable volume of pipeline PONs but we do have some cleanup work to do. Any questions on that part? Great, then I ll turn it over to Sue for LSOG 9. Sue Pistacchio: Good morning everybody. For LSOG 9, very little to communicate. We have the final version of the business rules for the October, which was posted on September 1 st. At this point in time for LSOG 9 implementation we are following the normal October timeline. CLEC testing is due to start in the CT environment on September 19 th and at this point in time we do not have any pending LSOG 9 open issues from a business rule perspective or the CORBA EDI so things are looking pretty good. Are there any questions with the LSOG 9 implementation? With that I will turn it back over to you Jean.

4 Thanks Sue. OK, next agenda item is CABS consolidation, Dan. Dan Duris: me OK? Speakers: Yes. Good morning everyone. Can everyone hear Yes. Good morning Dan. Dan Duris: Funny! I m here to tell everyone that the last phase of our consolidation, which will be for the states of Maryland, Virginia, West Virginia, and the District of Columbia, consolidating those to the CABS East system, we plan to do that effective October 1 st and that will complete the consolidation of CABS South to CABS East. I m going to provide you a different today than what I normally provide you in case you would like to get an old BAN new BAN spreadsheet, for your old BAN to new BAN relationship. If you would like one of those you may send an to kathysdingler@verizon.com. If you have any questions about the CABS consolidation you may contact me on , and might there be any questions I might be able to answer today? Lisa Provenzo: Dan Duris: Dan. Yes? Lisa Provenzo: This is Lisa with MCI. We re still having great issues about the old account and the new account or any ACNA that Verizon labels ZZZ, so will Kathy be able to firm this up for us? Will we feel a bit more comfortable with this conversion, because it s kind of, it's still well out of the comfort zone from our folks. Dan Duris: OK and I guess I m not totally familiar with what the issue is. Is it just getting, finding the right account? Lisa Provenzo: Amy O Hara. Dan Duris: Well that and the communication that came out from (Inaudible) Lisa Provenzo: Right, it doesn t, it basically says instead of, you know, we don t always know our account number when you, when it s a fictitious ACNA so it looks like you re looking for the CLECs to provide all the information when, you know, there s no communication working with the CLECs to look at the old and new account, so they just feel there s a gap.

5 Dan Duris: OK, and you know for the ZZZ ACNAs we really need to rely upon you being able to provide your old account number because there s nothing, you know, there s nothing unique for us to use to identify it, like when you use an ACNA. Lisa Provenzo: OK so Kathy would be the person if I wanted to Dan Duris: She can work with you and we can do things like try to search by a bill name but if, depending upon how that was set up. Lisa Provenzo: Dan Duris: Lisa Provenzo: Dan Duris: All right. Well I ll call you and work with you offline. Sure. That would be great, thank you. Anyone else? Rebecca Baldwin: Dan hi, this is Rebecca with Telcove. Can you spell Kathy s last name again please? Dan Duris: Sure, it s Dingler like Dingle the well let me just D- i-n-g-l-e-r, Dingler. Rebecca Baldwin: Dan Duris: Rebecca Baldwin: It s just kathysdingler, it s not kathy.s.dingler? I m sorry, yes Kathy dot s dot dingler@verizon.com. OK, and your phone number again please. Dan Duris: Rebecca Baldwin: OK great, thank you. Dan Duris: And I will tell everyone I m going to take a couple of days off starting tomorrow but I will be back the middle of next week. Dan Duris: Dok Matthews: Dan Duris: I don t know if that s allowed Dan. I got to get it in now! Hey Dan its Dok from TTI. Hi Dok.

6 Dok Matthews: Who are we supposed to contact when Verizon really screwed up on transferring the account balances when they went from one, from the old CABS to the new CABS? According to Verizon we owe you guys a lot less money than we actually owe you. Dan Duris: Well gee. Dok Matthews: At Penn Telecom we don t just complain about our bills being off, we complain when our bills are wrong, OK. Thank you Dok. Dan Duris: I am so impressed. Someone from my group could help you with that, or your billing representative could but we would be glad to help you with that. Dok Matthews: Well that s real pleasant. Which group, which person would you like to direct this one to? Dan Duris: imagine you Dok Matthews: Dan Duris: I am getting ready to take a couple of days off and I You know I heard that before. If you want to deal with it now. Dok Matthews: No I don t care; I ll wait until you come back. Just send me an when you come back, OK. Dan Duris: week. Dok Matthews: Dan Duris: OK, thank you. Dan Duris: Yes, I ll do a follow up. It will be like Thursday next Sounds like a plan. I ll have a beer waiting for then. Thank you Dok, I ll get hold of you. Anyone else? OK thanks Dan. OK, bye. The next topic is the migration of ACCORD to the south versus replacing EXACT. This is the ASR middleware. Cindy couldn t be with us today but basically I think the last update is still the same. They ve pushed out the date and there s no new date. They do believe it s not going to

7 happen before the end of the year, so it s going to be some time in 2006 when this is going to actually be rescheduled for. Any questions on that? Moving on to Sue with FTP report migration. Sue Pistacchio: Hello again, the FTP migration. First we ve had a successful FTP retirement of certain of the previous FTP reports which were the CSR report, the SAG, PSA, USOC, the provider notification LL format only, and the bulk loop qual. What we have also done is just to kind of circle back with a lot of our front tier organizations and everything has been extremely quiet and at this point in time we don t have any outstanding access issues or registration issues with the use or getting these reports via the new customer wholesale portal process, so that s really good news. The other good news that I have is we finally have a committed date for the transition of the directory listing verification report. What we re looking at now is the commitment date for November 26 th to migrate these reports from their existing place on the FTP server over to the new CWP process. This is both for East and West. What we are going to do, instead of just blanket distribution of registration letters, what we are going to ask is that the CLECs that do require access to the DLVR via the new portal process, that they send an to us at our transition web address - and we are going to send a letter on this so if you don t capture this we will be sending out a notice within the next week or so, but we are going to ask the CLECs to send a request to the customer.transition.planning.cwp@core.verizon.com and show the Sue Pistacchio: Dok Matthews: Sue say it again. You want me to do it real fast this time? I saw heads shake around the table so. Do it with that Boston accent. Sue Pistacchio: I don t have a it s Rhode Island Dok, you should know that. It s not Boston, it s a little different. verizon.com. That is our official transition site. Just send an to that address and designate that you want access to the DLVR. We need your company name, a contact and a contact number and also your fax number. We cannot send the registration letter out via . We have to either mail it or fax it but we re going to fax these. You can send a report to us at any point in time. We will store them. We are not going to distribute the registration letters until November 28 th which will be the first day that you can actually go in and register. You re going to do the same thing where we re going to have an approximate 30 day registration process which will run from

8 November 28 th to December 23 rd and then we will also have an approximate 30 day dual mode operational window which will run from November 26 th to January 20 th and we will send out the reminder ring or the reminder notice approximately 2 weeks before we retire the DLVR from the FTP server. I have that date marked down as January 6 th. So once we turn this up, as long as you register quickly you will have a full 60 days to get through the registration process and acclimate yourselves to retrieving the reports on the new portal process. For people that maybe haven t used it before I know that there is training that is scheduled. It mostly goes through the registration process. The last I heard it was tentatively scheduled for October 18 th. I don t know if that has gotten finalized or not. That s pretty much all I have to communicate for the FTP migration. Does anybody have any questions? Sue it s Beth. I assume it s going to go out in a notice to the industry with all the information you just provided. Sue Pistacchio: Rebecca Baldwin: Sue Pistacchio: Rebecca Baldwin: Sue Pistacchio: Yes. OK. Hi Sue, its Rebecca Baldwin at Telcove. Hi Rebecca. How are you? Good. Rebecca Baldwin: I m very excited about this. On the that you d like us to send to the customer.transition.planning etc. (inaudible) company contact number and fax the company contact or the folks that are actually going to be doing the registration and that kind of thing. Sue Pistacchio: It s really just who, when we send the fax to somebody, who we should be sending it to. Rebecca Baldwin: Sue Pistacchio: Rebecca Baldwin: OK, so you want a point of contact. Yes, it s really a point of contact. For the letter. Sue Pistacchio: Right, because we do need to fax it to somebody so we just really need to know who we re sending the registration letter to. Rebecca Baldwin: OK, that answers my question, great. Thank you.

9 Sue Pistacchio: you. Are there any other questions? Then Jean it s back to Thanks Sue. Moving on to the next agenda item, it s provider notification report. Carol you re back up. Carol Yozzo: OK I m going to start by apologizing for that customer.transition.planning (inaudible) on every mailbox we have. I m going to see what I can do to shorten those down in the future. That was a terrible plan, I admit it, so maybe we could make it CTP going forward but for now you have to go with the long name. OK, provider notification report, and this is related primarily to the SRPT report that is still on the FTP server, so what Sue was just talking about with the LLR Prod version which is on the CWP side. We had some open issues from the June release which were resolved with the August release so we are proceeding with our plan to retire the SRPT report from the FTP server with the October release. There was an industry notification that went out, I think it was early September. It was the 45 day notice for the October release and that was included in there. So this is a reminder that if you are still using the SRPT report and have not registered for CWP, you must do so and I am tracking down any CLECs that are, either may not be aware - I find that hard to believe with all the communications we ve done - but for whatever reason have not yet registered, just to make sure that everybody has a smooth transition there. Questions on that? Great, thank you very much. Carol Yozzo: OK Carol you re next so I m up again. End user listing. Carol Yozzo: OK, end user listing, we are really flying through this conversion. It s going a lot more quickly than we could have ever anticipated. We ve been able to accelerate the rate to the extent that we are now over 50% complete in terms of the volume of listings and we had nearly a million listings to convert in the North, so this is really good news. We re continuing with the remaining CLECs. We ve got about five CLECs remaining and that includes a couple of really high volume CLECs so even though there are only five CLECs there are still about, its actually about 45% of the listings remaining. And it is expected to wrap up by the end of this year. I had been saying it would probably flow over into the first quarter of next year but as we continue with the accelerated pace it s looking better and better for completing before the end of this year. The implication though of the, or the relevance of the completion rate is that any CLEC doing a migration is more and more likely now to find that the

10 listing they re migrating is already in end user format, though you should be checking that CSR, checking for the end user class of service and everyone should be creating their new listings in end user format. Any questions on end user? Lisa Provenzo: I do. It s Lisa with MCI. When can we expect a report so we can just see what s been converted over? Carol Yozzo: You know what, I just got the report about a day or two ago Lisa. Yours is on there so I will have that out to you, probably today. Lisa Provenzo: OK great. Carol Yozzo: And yours is completed by the way. All of your listings that were eligible are completed so I will have the report out so you can have it. Lisa Provenzo: Carol Yozzo: OK I look forward to seeing the on the status. Any other questions? Carol Frike: Yes, this is Carol Frike with Sprint. We ve gotten some error back when we ve done new directory listings. Is that something that a trouble ticket should be opened or? Carol Yozzo: Yes it should. Yes I m sorry, I haven t had a chance to get back to your message. I saw that yesterday. You were having a problem with the BAN, was that correct? Carol Frike: Carol Yozzo: Carol Frike: Carol Yozzo: Right. Right, you should open a trouble ticket on that. OK. Any other questions? Great, thank you very much. Thanks Carol. The next agenda item is to review the open items that we continue to put into the materials. Since I ve been here, I guess it s my twelfth month, we haven t reviewed this so I thought, we just thought it would be a good time to sit back and look at it and see where we can go, if nothing else reducing the, some of the history of it. So I ll turn this over to Joan right now to go through these open items. Joan Costello: OK Jean, thank you. I m sorry? I was just saying it s tab one for people in the room.

11 Joan Costello: Speaker: OK. The first item (Inaudible) if we re on line? It s within the title it says Open Items, Open Issues. I m a little it actually says (inaudible). Open issues, right, open items. whoever asked? It s a separate piece. Yes, they are all separate PDFs. Can you find it, Speaker: September 5? Speaker: Yes. OK, thank you. Joan Costello: OK, I m just going to start with the first topic; it is number 67, CLEC to CLEC migration. In addition to being carried here in change management it is also an open issue in the CUF meetings. What we d like to do on this is to pick up the history from the July 12 th 2005 meeting and drop the previous, you know, history back to March of Dropping the history from this document really wouldn t impact anyone because the previous history is also available on the wholesale website in the, under Archived Meetings, so at any time it can be found easily. Any objection? I think we should know if we drop the history that there is a history so that the implication is not made that there is no history. be found in been archived. That s a good idea. OK we ll put like a prior to this all previous history can You can say history from this date to that date has OK. So that the end reader knows that there is earlier history, that it s a long standing ongoing item.

12 Joan Costello: be found on page 11. Gotcha, good. OK, thank you. Now on to item number 69, which can Joan before you go on, once we have this is from yesterday s discussion at CUF. So once we have, once we get to the point of having a new reprioritized list of the whatever it was, 19 or 20 outstanding migration scenarios, I assume that that will become, at that point in time, the working list. Right, and we will put that, even though we re, it s kind of really removed over to CUF we will still carry that in here as well. I would almost ask, once we do that, if we can actually even take out it makes the archive a little longer because I think it gets confusing when you have all of these other lists, because even from July of 2005 we ve got a list in there so my recommendation Only keep the current list? Only keep the current list and then archive. We can make a notation September, you know, July version archived or replaced with whatever. most current active list. I think it gets too confusing for people on what s the (Inaudible) OK. Joan Costello: OK, topic 69 which is PONTRONICS, it can be found on page 11 of this month s document. This topic we would like to close. The topic was originally opened also in 2000 and since that time there have been numerous system updates. The notifier status is available via LSI. Using the CLEC self service tool a PON exception ticket can be entered to quickly get the notifier status back and service order status has been implemented using a preorder transaction since the original opening date of this item, and we would like to close it. The referred to CR was never about PONTRONICS. As a matter of fact this is Elliott Goldberg and I opened that CR and the whole point was excuse me? The original number I think was 1455 Beth. The whole point of it was that

13 Whoever is typing in the background can you please mute your phone. Thank you. It was a problem with what PONTRONICS looks at the last sent notifier. The point of the change was to look at the actual status of work, because frequently the request, the answer that comes back is something that s already known and has been known for some time. It doesn t identify the fact that something is missing or late, it identifies that something was done at a prior time, and I ll illustrate it. If, for argument s sake, a PCN is three days overdue, and the provisioning interval was argumentatively five days, so you re now looking for something eight days after the confirmation, PONTRONICS will tell you that it was confirmed. We already know that, that s how you knew the due date and you knew when to expect the PCS. That was the problem with PONTRONICS and that s the explanation I ve made since 2000 and that s why I ve never closed this CR, because the problem was what PONTRONICS looked at, not that PONTRONICS does not look at things, not that PONTRONICS does not provide information, not that various information is available, but the whole point of this was to flag things that weren t happening on time and before the CLECs had to then submit a trouble ticket saying where is this missing notifier, or whatever, that there should be a system that flags hey it s missing, somebody go look for it. Somebody react proactively. But that s the CR, so from this issue what is the issue capturing that the CR isn t capturing? Well what, you know, the first line of the history of issue 69, MetTel has submitted a Type 5 requesting functionality. Now I don t care if you want to drop, drop PONTRONICS but I don t want the CR to be confused with PONTRONICS, because it is asking for a very specifically different thing. So for the issue what were you asking? You opened the issue, or Verizon, or a predecessor. A predecessor, because Verizon kept trying to explain that PONTRONICS was the answer to the CR and I kept saying no it s not, it s looking at a different thing. The whole point of the CR was to capture them before they became issues. We could proactively manage the situation rather than waiting for afterwards, and by the way we still don t get status information like that from PONTRONICS. It tells us the last thing that was sent. Well first off you don t get anything from PONTRONICS, you get all your information via notifiers. PONTRONICS was an internal system.

14 No I still get a PON status when I send in a trouble ticket and it gives me the latest PONTRONICS answer which is, 90% of the time, something I already knew, maybe more. Maybe it s 95 or 97%. OK so I think what I heard this is Mike Clancy. What I heard so far is that you didn t open the issue. Right. You put in a Type 5 request. Right. Your Type 5 request handles what you asked for. Correct. So you don t care if they take this off or not. No, but I don t want it to be confused in any way that this is relating to that CR, which is the first item. So does anybody have any objection to closing this particular issue? The CR still sits on the PWG in a not scheduled status. Right but you see Now it goes to the archive. Starting with June of 2000 and even the last entry, next to last entry of January 03, that you re still cross relating the issue with the pending T5. This issue is not the pending T5. PONTRONICS does not answer that CR. Right, so get rid of this issue from the documentation. It eliminates all that confusion. Right. OK. Thank you. Joan Costello: Thank you. OK we re going to move on to topic number 73, which is the prioritization process documentation and in light of the agreement for the proposed changes that were made at the July meeting, we d like to drop the history prior to July 2005 once again and make a note that the archived information, where it can be found easily.

15 Peggy Rubino: Any problem? Seems like this was actually done. We were wanting to keep it open until it actually got through the different Commissions that need to agree and we d get it back up online, so we were the one s that wanted to keep this open until it actually officially was out on line. Peggy Rubino: (Inaudible) I haven t gotten enough feed from legal. I send my little reminder notes every once in a while. So yes, I think we want to keep this open just (inaudible) get rid of some of the history. To be socially responsible and save some (inaudible). Exactly. Can we at least then make the note for today s discussion that we will leave this open until the legal hurdles are Until it passes regulatory approval. Right, exactly. It s not legal it s regulatory. Right. Joan Costello: OK, good. OK, topic number 74 which is on page 13, is wholesale provisioning tracking system and we would like to close this topic because the new loop capability is available for CLEC use. I have a question, this is Mike Clancy. I have a question. Do we carry it as an issue in Verizon West? Joan Costello: I don t have the material but I don t believe it is. I don t think so. So I m OK with closing this out here but I might want to open it up in Verizon West. OK.

16 This is, in some respects this goes to the discussion we had yesterday where we took some actions to try to understand what are the differences East and West with the EWPCS, so maybe we should open it as an issue in the CUF as opposed to here. I would say that if they re, if the community is, desires having EWPCS in the West and we do not have a plan to put it on track - I m really putting ourselves on the top here, then we should probably be opening a CR in change management to have that capability in the West. That would be my recommendation how to handle this activity. OK, so then the first step would be to determine the status in the CUF and then if it needs a CR. Yes. OK, thank you. OK, then I hear no objections to closing this? OK. Joan Costello: OK, item number 85, which is also on page 13, end user level listing project. As everyone knows this is an ongoing topic each month on the agenda. We d like to leave the entry open but drop all previous history from today s update. Actually we might want to keep a few months. We will look back. We might start, just from where we start talking about North only conversion since that s only (inaudible). West. (inaudible). How about just leaving prior to the first of the year? Yes, I think that s when we started reporting North and And annotate where the prior history is. Yes we re going do that for each that we re dropping Joan Costello: OK, so we re going to pick that up from the beginning of 2005 and note where the previous is. Good. Topic number 86, notification of Verizon declared emergency condition. This is an ongoing topic at the CUF meeting so we re requesting that we remove this and close it from here in change management. And keep it just in CUF.

17 I m OK with that; everybody else? Any objections? OK. Joan Costello: And the last one, number 87, FTP report migration. Another one we d like to leave open until the DLVR report is retired, which we heard with be done in, at the end of November, but once again drop the previous history and note where the previous history can be found. Joan Costello: Any objections? OK. OK great, thanks everybody. (Inaudible) Send a memo to her first. Moving on to our next agenda item, WCCC update. I believe Jamey is still filling in for Nik today. Jamey Rawls: Yes that s right. WCCC and CT updates, just real quickly. For the October CLEC impacting release, the CT environment will be available on Monday to begin the October release testing. We received test plans and have, I believe, most of those, if not all of those, finalized so we will begin testing on Monday. The upgrade occurs into CTE beginning Thursday evening through Friday. If there are any questions with the CT update let me know, or any WCCC questions. I ll take those at this time. Jamey this is Mike Clancy. I ve been told in other conversations that the WCCC will be updating the CLEC community on this call as to the investigation into the July breakdown in Blue Hills on the interfaces and what Verizon has done to, or plans to do, to prevent that from happening in the future. Do you have anything to report? Actually if it was requested Jim McDonald is available. I just have to step out to call him and ask him to join us all to give that readout. later. OK, great. Then I can wait until later. We can do it I ll call him and why don t we go on to the next item. (Inaudible)

18 I only have one other question, kind of a process question. If it s a billing issue does it go to the WCCC or is there another like billing (inaudible). There s a different billing Jamey Rawls: Yes we have a separate billing group but you would still open a trouble ticket for that, just identifying it as a billing ticket. So we d open it in the WCCC state? Jamey Rawls: You would, if you used self service you would open it up on line and open it as a billing ticket. If you contacted the call center then you would just identify it to them as a billing ticket. Jamey Rawls: to Jamey Rawls: OK. I believe we re all set then. If Beth s issue is going Yes she just called Jim. OK. He said he d join in a second. OK, but anything else for Jamey? OK, Stephen Cuttle, if you give your update and then we will come back to Jim. Stephen Cuttle: Stephen Cuttle: OK, fine. Did Jim join? He s going to access through the operator. OK. OK so I should proceed? Yes. Stephen Cuttle: OK. Good morning everyone, I m just going to reference a couple of items that were documented in the September enhancements to Verizon s website notification that went out this past Monday, and then discuss a few other topics briefly.

19 A significant update to the wholesale website that just took place last Friday is a new site map. The site map has been added to; you can link to that site map on every page on the wholesale website. At the top of each page there are what we call global icons for the glossary, the calendar and so forth, and there is now a site map icon that exists on every Verizon wholesale page, and the site map is designed to provide a list of all the content areas on the wholesale website so hopefully you will find that. It will be helpful to navigate through the website, and that is now on the web. As far as workshops go, for the rest of September there is just one remaining workshop scheduled for the LSI trouble administration application. That s scheduled for September 20 th and that is on the events calendar. An action item I just want to report back on, from last month s change management meeting. We have updated the profile management information in Contact Us so the second level of escalation. That is now live. With our CIRT helpdesk some of the topics that are associated when your teams are submitting etickets to the CIRT team, two of the topics were updated. The PON and/or RPON topic has been added replacing PON and RPON and a CSR, CSI and preorder topic has been added, replacing a CSR and CSI topic. It s basically name changes to the existing topics. One item I did want to bring to your attention this month, associated with the CIRT helpdesk, the CIRT team will be trialing a change in calling hours to the 800 number that CIRT has opened. The trial will incorporate a change of hours. Current hours for calling CIRT are 8 am to 6 pm Eastern. The new hours will be 9 am to 5 pm Eastern. The trial is set for three months. It goes into effect September 21 st and the trial will end on December 21 st. Your team can still contact the CIRT team electronically either before the 9 am start time or after the 5 pm start time. There will be existing eticket process. This change is based on some CIRT call analysis that the center receives very few calls in those early morning and then late afternoon hours and the, what the CIRT team will plan to do is proactively reach out to customers who have been contacting CIRT or submitting etickets to help, assist them on some of their particular training issues during those offline hours. At the end of the trial period, based on CIRT eticket data, and the CIRT team will also be soliciting feedback on the new hours and the eticket process to customers directly through some surveys, they will make the determination if the existing hours will continue. So again that begins on September 21 st and will run through December 21 st. The hours of operation for calling CIRT will be updated on the website to coordinate with the 9/21 start date and the recording on the CIRT 800 number will reflect the new hours also as of 9/21. The final item I wanted to review is Verizon will be introducing a redesigned time page and a solutions area to the wholesale

20 website. The effective date for that launch is now scheduled for October 17 th. I will point out that the solutions section will replace the existing product and services guide. It s a name change with a lot of good redesign incorporated to that. We ve received many suggestions and feedback from many customers of Verizon through this entire process, both in providing us with feedback on the existing home page and solutions pages and also providing feedback on the design for the new home page and solutions section. I think you ll find that the home page will be much more dynamic. It will include direct links to product information as well as the applications that you re using to do business with us. There will be other operational content, direct links to such areas like the business rules and order samples and there will be a section that will (inaudible) significant updates that have been made to the wholesale website. In addition, to help make your experience with the website positive, the existing design or architecture of the website has been maintained. In other words if you look at the wholesale website today you basically have four areas where information is carried: doing business, systems and measure, the resource library, and products and services. The architecture of that design or navigation will remain in place and you will still be able to navigate to those areas when the new home page launches. Just a note about the new solutions area; that will actually include, in addition to the existing information today about products and services, it will have information and links to related products and services and also direct links to operational content associated with those products such as applications for ordering, order samples. There will be links to billing, trouble admin and so forth, all contained within those particular product, or I should say solutions, pages. In addition to the launch we will be enhancing the search function. It s, there s been obviously some feedback that it s not as good as it needs to be so I think you ll find that the search engine will be much more enhanced and will be able to provide more specific results, and also an enhanced glossary section. The site map I mentioned that just launched, as I said, does reflect the current design. When the new home page launches and the solutions pages, that site map will also be updated at the same time. And to assist you and your folks to be familiar with the website, in addition to an industry letter that will go our next month, Verizon is working on developing an instructional video that will be housed right on the home page and will kind of give a navigational tour. That will launch with the October 17 th date and the customer training team will host a series of web tours starting the launch week and continuing through the month of October and probably subsequent months, to actually guide customers through the new home page and solutions page. There will be a lot more information coming on that next month. Any questions?

21 Stephen Cuttle: Stephen this is Mike Clancy from Covad. Hi. And I m really chagrined that you re going to make the search engine find more specific data because it reduces my value to Covad. But in the products and services area, there are a number of products and services, the way that those pages are structured there are, like detailed information and technical data sections and sections like that, that for a long, long time just don t have any information in them. Will this updated solutions section take care of that? Will that be revisited? It s like kind of sections that are under construction you ll see on some websites. Those have been under construction for a couple of years now, so. Stephen Cuttle: No, I hear what you re saying and I know as part of the redesign that there has been some work done to fill in some of those gaps. It won t be complete but it certainly I think is definitely an effort that s started to fill in the gaps with documentation that has been lacking. If I come across a particular example when I m doing a search, should I give that to any particular organization in Verizon as a request? Stephen Cuttle: Something like that you can certainly send to my team s attention. If it s not I don t actually oversee the products and services guide but I work with Verizon s marketing group and if it s not something we can deal with directly I can certainly pass that along to the appropriate group. You can either me directly or you can send that to my team s mailbox, which is verizon.system.team@verizon.com address. Stephen Cuttle: Gloria Velez: Stephen Cuttle: OK great, thank you Stephen. You re welcome. This is Gloria Velez, Stephen. Hi Gloria. Gloria Velez: Hi. I ve noticed that the bulletins and the outage notifications that are sent via sometimes take a long time to get posted on the website, and the industry letters that you send out, they get posted relatively quickly. I think yesterday or the day before yesterday there were two industry letters and I think those industry letters are out on the website.

22 This is Jean, let me address that. The bulletins that go out through my team and then we deal with the posting, so we do at least try, we send it out first and then we worry about getting it posted, and we usually, its usually posted and Gill, correct me if I m wrong because she s the one that posts it, it is within the next day. We do have to work with an internal group to get it posted. I believe the industry letter process is they post and then send out the notice, so it s a slightly different, you know, it s within a day but we will look into the timing of our bulletin postings. Like they re usually within the 24 hours of when we send it. Gloria Velez: You might want to check that out because I don t think it s 24 hours. I mean go take a look and you can see that the last things that were posted were like sometime I think, and I was just there, I think it was August and like you sent out now maybe I m looking in the wrong spot. We will look at it Gloria. Gloria Velez: And let me get back to you then. Are we supposed to find on that link the notifications that are sent out when your out of hours get adjusted? For example yesterday or Monday there was I know this is Verizon East, but Verizon West sent out a notification changing the timeframe That s actually under the I know but it s not in front of me under the Systems section and then you scroll down and there s the West availability exceptions. Gloria Velez: Yes that I know but when you I know that but when you actually send out the bulletin. When we send out the notice we re saying there s been a change to that document and that document has been just updated. Gloria Velez: Gloria Velez: OK so you wouldn t, I wouldn t You would not see that as a separate section. OK, thank you. East and West is slightly different on the availability scenario. OK any other questions for Stephen? Rebecca Baldwin: Stephen Cuttle: Rebecca Baldwin: Hi Stephen, this is Rebecca. Hi. How are you?

23 Stephen Cuttle: Well, how are you? Rebecca Baldwin: Doing good thanks. Just some clarification; you re sending out, or will an industry letter be coming out I didn t quite catch that. Are you referring to the enhancements that are going to be made to updating the home page with the additional solutions area and the search engine and the glossary? Is that all going to be included in that industry notice or is it just something specific on that industry notice that s coming out? Stephen Cuttle: notification. All that information would be included in the industry Rebecca Baldwin: OK so it s all in the above. OK, how about on the CIRT, the trial that Verizon is basically on, I haven t seen anything concerning that. Will that be an advance notification prior to the 9 th when you want trial? Stephen Cuttle: Well the purpose of the, the purpose of my bringing it up today was to notify the CLEC community about the trail and the change in calling hours. Rebecca Baldwin: OK, however not every CLEC is on this call so can I request that an industry letter come out notifying the CLEC community of the change in hours and CIRT even though it s on a trial basis and what the criteria is for the trial basis, and what can the CLECs expect as well as, you know, what you would like for us as a CLEC to notify you on. I understand that you re going to be having some kind, soliciting some feedback. I think it s important that the entire CLEC community be aware of the change, even though it s on a trial basis. there. Rebecca Baldwin: Stephen Cuttle: Lisa Provenzo: Stephen Cuttle: Lisa Provenzo: Stephen Cuttle: OK we will look into seeing what we re going to get out Thank you. Anything else for Stephen? Thank you Stephen. You re welcome. Stephen. Yes? Hi this is Lisa Provenzo with MCI. Hi.

24 Lisa Provenzo: Hi. I have one question for you about the redesign. Have they done anything to change the connectivity page so that it goes back to the original design where you don t have to have a cumbersome step to pick preorder and fill out your user name for like, you know, a GUI user and then go back in and do the whole thing all over again for order. Stephen Cuttle: Lisa Provenzo: did. No Lisa, that wasn t part of this redesign. Jean you were looking at to change that. I know we We looked at let s talk about it again offline. From what we and I ll have to go back in history, but I didn t think that was a major - I didn t think that was a change and there is a way to bypass that step to get to the, directly to the forms you need. Lisa Provenzo: All right, well if you can tell me how that is and get back with me I d greatly appreciate it. I don t see anything and you haven t gotten back with me so. Lisa Provenzo: All right. I d still like to take a look at changing that. I can t promise anything but we will talk through that again. OK, anything else for Stephen. All right, Jim McDonald have you joined the call? Jim McDonald: Jim McDonald: Blue Hill. I have, good morning. Morning. Good morning everybody. So you want to know about Well Mr. Clancy would like to know about that. Well what we want to know is who is Brownie? (Inaudible) Jim McDonald: Well I ll tell you what I know. Actually we just concluded a post mortem and I can (inaudible) for everybody on the call. Verizon did just sustain a system outage in July and we just concluded with our vendors a post mortem of that outage to better understand what was the root cause and what could be learned from that experience, and I can share those details with

25 you. What I ll do is I ll run through an overview of the events at Blue Hill and when I conclude I ll just open it up to any questions. So in fact there were two separate power incidents at Verizon s Blue Hill datacenter in New York on July 18 th and 19 th. The first event occurred on Monday July 18 th when the commercial power substation that feeds the Blue Hill datacenter sustained a lightning strike at about 7.15 in the evening. The interruption of commercial power at that power substation triggered an automatic switchover in Blue Hill to local generator power; however, subsequent to the actual lightning strike a UPS power system in the Blue Hill datacenter was damaged, and just to give you some background on what a UPS system is, it s actually a large power console and UPS I believe stands for Uninterruptible Power System, which is a little ironic, but that s the abbreviation. These are large power consoles and they are designed, anybody with any familiarity with datacenters or central office operations, the UPS is designed to smooth out any of the fluctuations that occur in the commercial power feed. As anybody that has a desktop in their office, you typically hook that up via a power strip to commercial power because commercial does, in the normal course of events, it does, it ebbs and flows and surges and everything else and any sensitive electronic equipment can be seriously damaged by those fluctuations in current. So the UPS sits between all of the mainframe applications and commercial power, and again it s designed to kind of smooth out any of the ripples that would occur that could potentially damage that equipment. In the event of this lightning strike one of those UPS consoles was damaged in Blue Hill and so during the transition to local generator power there were retail and wholesale applications that were fed by that damaged UPS that sustained the power interruption. Again we had the lightning strike, the loss of commercial power, the transfer to generator power, but during that transfer any of the applications being fed by this damaged UPS did loose power during that transfer. Jim McDonald: you know. Jim McDonald: Jim, can I ask a question? This is Elliott. He said wait until he is done. If it s a clarification Elliott, go right ahead. Otherwise, Well it s something you said that s confusing me. Yes. You know I m on a UPS that I work with all over the world, the batteries feed the processors and the commercial power feeds the batteries, so that if or the generator feeds the battery, so that if there is a failure the battery provides constant power until such time as it runs down. So that s

26 what s confusing me about every one of these explanations I ve heard about this. Is it it sort of presupposes that it s done the other way, that if the UPS fails there is no power. Normally there s shutdown power or four hours of power, or six hours of power, however the batteries are set up, and your explanation confuses me because it again implies the reverse. Jim McDonald: Well let me just go back to the UPS itself and clarify some things. Within this UPS there are actually four modules. It s designed to N+1 redundancy, so you need three of the four modules operating in order to sustain the UPS functionality. The damage that was incurred at this UPS was so severe and so extensive that it basically just took the entire thing off the power grid. So to your point we not only had the damage to the actual modules but we also had an interruption in that battery provided backup supply coming out of the UPS and that was, you know, what basically left those applications high and dry during the transfer. The transfer was pretty quick from commercial to generator, on the order of a minute or two, and to your point Elliott, during a normal transfer like that a working UPS would sustain power to the applications through the battery backup until the generators came online and then it would continue about its business. In fact just a half hour prior to the lightning strike we had a pretty big surge in the power system which the UPS handled without incident. They were fine, but this particular event it, to put it in the crudest terms I can, it completely fried that UPS console. Dok Matthews: Jim, did you say that happened prior to the lightning strike or after the lightning strike? Jim McDonald: It was about a half hour prior to the lightning strike there was a substantial surge in the commercial power feed and the UPS they took it, absorbed it and there was no noticeable impact within the datacenter. Dok Matthews: lightning strike. And then it crapped out on you, then you had the Jim McDonald: Then we had the lightning strike about 7.15 and that s where things got interesting. Dok Matthews: But if I understand you right your UPS supplies the power directly to your datacenter. Your datacenter runs off the UPS? Jim McDonald: feed. Yes the UPS sits in between the commercial power Dok Matthews: And it s always actually it is always actually supplying the datacenter and... Jim McDonald: It s always in line, yes.

27 Dok Matthews: Jim McDonald: Dok Matthews: Sort of like we use rectifiers in our COs. Absolutely. OK. Jim McDonald: The commercial power is coming in, it s rippling, it surges, there s ebbs and the UPS smoothes it all out so that the applications on the output see a nice, constant power supply. Dok Matthews: So when it fried you were running the datacenter just on commercial power alone. Jim McDonald: Well we had the commercial power; we had the lightning hit, the loss of commercial power now. Dok Matthews: Right. Jim McDonald: So automatically the generators, the systems detect loss of commercial power and there s an automatic transfer then to local generator power. Dok Matthews: But my question was you said the word subsequent. I m taking it that the UPS died before the commercial power died. Jim McDonald: To the best of our knowledge the UPS console died at the same time as the lightning strike hit the substation. We re tying the damage in the UPS to the lightning strike. Dok Matthews: coincidentally then. Jim McDonald: Dok Matthews: think you described to us. Jim McDonald: OK, coincidentally it occurred, not subsequently; Concurrent with the lightning strike, yes. Concurrent; OK thanks. Jim this is Mike Clancy. Let me try to clarify what I Sure. It s a UPS that s situated in between commercial power and the datacenter. Jim McDonald: Correct.