VERIZON SERVICES CORPORATION
Moderator: Frank Malecki
05-11-10/12:48 am CT
Confirmation #7511700
Page 1
VERIZON SERVICES CORPORATION
Moderator: Frank Malecki
May 11, 2010
12:48 am CT
Coordinator:All lines will be open for the duration of today's conference.At any time if you do need assistance it is star 0.To mute your line it is star 6 to mute and star 6 to un-mute.
I would also like to reminder participants that today's conference is being recorded.If anyone has any objections, you may disconnect at this time.
And now I will turn the meeting over to Mr. Frank Malecki.Sir you may begin.
Frank Malecki:Thank you very much.Welcome everybody to the change of management meeting.My name is Frank Malecki.
I'd like to begin the call today, I just want to go over the agenda real quick because I added a couple of things that you might normally not see.
There's a change of management piece to the agenda because I wanted to discuss briefly the change of management piece as it relates to the (unintelligible) or North Central and Verizon.
And then there's a couple of things that I wanted to make sure I discussed that we took away from the last meeting, or had talked about in the interim.And one is the test of arm and expansions for the simple port release that's been scheduled for August 1.
And then the directory listing issue that had come up for litigation out in California.I'll discuss that.And then we can have a little round table for any other issues that you want to talk about.
We can go to the department updates.Is (Paul White) on?I know I didn't receive anything for any issues regarded to any system problems.So as far as I know all of the systems are working as they should.
Kim Taylor are you on?
Kim Taylor:I am.
Frank Malecki:Okay could you provide an (SP) update?
Kim Taylor:Sure, I'll be glad to.Good afternoon everyone.Just want to go over some pertinent dates for the June release.Our test plans were due yesterday.The environment (CTE) environment will be down on May 21 which is a Friday for code installs the June release.
Our testing starts May 24.Testing ends June 17.And production is 6/21.Does anyone have any questions?Thank you.
Frank Malecki:Thank you Kim.
Kim Taylor:You're welcome.
Frank Malecki:I don't know if (Victor Barrell) is on the call today.I did not receive any enhancements for the Web from him.
The third item on the agenda is the prioritization working group which I wasn't going to spend a whole lot of time with.
But there was an issue brought to me, excuse me, it was actually a cuff related as well.But it has to do with the change request that been floating around.And Carol Frank from Sprint had brought this up.
And I don't know if you're, anybody has the prioritization or the change of request history.There was a request for enhancing the automated jeopardy that's been floating around.
The current status it's feasible.It's Page 16 of the 50-page document change request history.The change of request number was C040284.We don't have to have a lot of discussion around it today.
I just wanted to let everybody know that Carol had brought to my attention looking for a way to see if we can't do anything with that.My initial response was Carol was the response that we've given this year as far as budget limitations.
But what I'm going to do with this particular request is I'll do a little investigation since I'm not very familiar with the issue itself.I'm assuming that automated jeopardy's or automation of status for orders, there are some things that are sent electronically and some things that are not sent electronically.
And two of those are within this request.One is for a (Jet EO) and then one's for a (Jet PCO).So I just wanted to let everybody know that, and Carol in particular that as far as budget, you know, that hasn't really changed.
But I will do some research on this issue to see exactly what it would take.And then I'll let everybody know.
Carol Frank:Thank you.
Frank Malecki:You're welcome.The next item on the agenda is change management at process and educations itself.I've had some discussions, I had a meeting last Wednesday and I'm going to have another meeting this Wednesday with the team that's tasked with replication if you will, change process management process for North Central.
We're still in discussions about the overall questions that they have that complete replication of the change management process.Whether it regards IT or the request documentation, the overviews and things like that, the notifications that go out to the (C LA) community.
And I'll be reporting on that.But I wanted to give you an heads up that I have not changed any email notifications within change of management process because we're basically still working on the replication piece for change management.
And does anybody have any questions around that?I know there was some confusion about, or some questions related to notifications.But right now I am in the process of working with that team to make sure that nothing is dropped when we make the break.
All the third part of the agenda is the - there had been a question or request that the, for the simple port enhancement initiative that the test window be extended by one or two weeks.
Right now I believe it's the 19th of July through the 30th of July.And the reason for that is because of the code being available on July 19.So there's no way to actually extend it other than beyond July 30, key testing, if you will, once the code is put in place.But there's no way to being testing at an earlier time.
And the sixth item on the agenda is the directory listing issue that was brought out regarding Santa Monica and Playa Vista.I had touched base with the contact for directory listings.
Actually apparently there have been a number of folks involved from directory listing with also people within the NNMC trying to resolve this issue.
Hopefully I got some information saying that we may have something this week regarding that issue. Carol I think that's your issue too, Carol Frank from Sprint.
Carol Frank:That's mine, yes thank you.
Frank Malecki:So hopefully we'll have something.I know that apparently a number of folks had been working on it.I know that there is something, I thought it would roll by the interconnection agreement.
But I'm not familiar enough with the agreement itself to know what's in it as far as directory listings go and how to franchise telephone numbers.But they are working on it.And hopefully we'll have something by this week.
Carol Frank:Thank you.
Frank Malecki:You're welcome.
(Laurie Ann):Frank this is (Laurie Ann) at XO.Could you maybe explain a little bit what that issue is because I know we're having a problem right now with a pool of numbers that we acquired from a wireless carrier.
And we cannot get them, we cannot get those numbers in directory.I'm wondering if this is sort of tied in with that?
Frank Malecki:Well it's a Santa Monica, California, or Santa Monica slash Playa Vista, California attempted to get a directory listing based on the telephone number.
And the telephone number is not Verizon owned so the address is not built into the - the engineers don't build it in the database.So you have to provide the city where you normally wouldn't have to provide a city to get that directory listing.
The reason is because it's not, since it's not a Verizon owned exchange or a telephone number.It's, the engineers don't build the address in the database.
(Laurie Ann):This was similar but I mean these are numbers in Washington, DC.
Frank Malecki:As long as they're Verizon numbers.Are they Verizon?
(Laurie Ann):Well they're XLM - they're XO numbers.You know, we ported them but the numbers at one point had been owned by Verizon Wireless.But we brought the pool of numbers or acquired a pool of numbers, I don't know.
Frank Malecki:All wireless?
(Laurie Ann):Yes.But they're not being used as wireless.
Frank Malecki:How are they being used?
(Laurie Ann):As land lines.
Frank Malecki:Oh okay.
(Laurie Ann):Yes, I mean we just brought the block of numbers.
((Crosstalk))
Frank Malecki:They're not actually wireless numbers, they're just numbers now that they're…
(Laurie Ann):Right now that we got them, they're just numbers.
Frank Malecki:Okay got you.
Woman:Cox Communications is having the same issue on the East Coast. And we've been told that I guess it's some sort of coding issue that Verizon has to work through getting these numbers built into their system.
(Laurie Ann):Yes this is (Laurie Ann) again.We've been working with our account team.But this has been going on for months.
Woman:And we've had the same issue and it's negatively impacting our ability to get our customers listed even in 4-1-1.
(Laurie Ann):Right, yes I mean I was told that, you know, they should have something this week as well.You know, because they think our regulatory folks are going to get involved.
Frank Malecki:Are these, now these aren't the same issue of porting wireless numbers?
(Laurie Ann):No.
Frank Malecki:Okay.But is it all ported numbers where you can't get directory business?Is that the comment?
(Laurie Ann):Well I guess they, in this case these numbers were assigned by XO.We got the numbers so, you know, they're like XO numbers but they're within an area that Verizon serves.
Carol Frank:Yes that sounds similar.This is Carol, where our breakdown is happening is we can't get a valid address.And so without the address validating in their database, we're going to continue to get rejects.
I don't know if that's where yours is breaking or what.But, you know, it's the same situation where we, you know, it's a native (TN) to Sprint.And then we're trying to set up the listing because it's Verizon territory.
I don't know if that sounds like…
(Laurie Ann):Yes it's a little different because we didn't have a problem with the address.We were just being told the number can't be listed because it wasn't a Verizon NPA NXX, it belongs wireless.But it doesn't belong to wireless anymore.Now it's ours.
So, you know, we kept being told that, you know, they don't have a way to figure this out and build it in the database.
Antoinette Griffin:I'm sorry, this is Antoinette Griffin with Cox Communications.What NPA NXX are you having issues with with Verizon?Is there a particular one?
(Laurie Ann):Yes, it's from this group of numbers.Hold on one second.
Antoinette Griffin:Because we're having the exact same issue here.
(Laurie Ann):This one happens to be 202591.
Frank Malecki:They are now XO, formerly Verizon.But formerly Verizon Wireless.
(Laurie Ann):Right, yes that pool of numbers or whatever, block of numbers.
Frank Malecki:Now was it you that said, or if it's somebody else talking about coding issue?
Antoinette Griffin:That's what we were told.This is Antoinette with Cox Communications.We were told that these numbers weren't built into I guess whatever system or database that Verizon uses.
Frank Malecki:Right.
Antoinette Griffin:And because they weren't built, they basically couldn't offer us service.So again now it's going up through regulatory and whatever groups are involved to try to get these codes put in.
But that's still impacting our ability to get our customers listed in 4-1-1.And again, this has been going on for quite some time.
(Laurie Ann):Yes, we're getting an error that says invalid NPA NXX, you know, 202591 is an independent exchange and cannot be listed.
Antoinette Griffin:Same here.
Frank Malecki:Okay.For the, do you have somebody, account management or some place you've been working with to get it fixed, anybody?
Antoinette Griffin:We do.
(Laurie Ann):Yes, XO has been working through our account team. But this started in February.
Frank Malecki:Who is that, is that Verizon?
(Laurie Ann):For XO it's (Mike Conoway).
Antoinette Griffin:And for Cox it's (Kevin Kincaid).
Frank Malecki:Okay.I can follow up with them just to get a handle on.
(Laurie Ann):Thank you.
Frank Malecki:Okay.I don't have anything else.Does anybody else have anything?
Carol Frank:Yes hi, it's Carol Frank again.The only thing that I was still waiting on a reply was the directory listing inquiry where the city is being required.Did you get any further with that one?
Frank Malecki:Yes I have made - have been communicating with (unintelligible).
Carol Frank:(Dunrendon).
Frank Malecki:Yes and apparently some other folks have been involved with the NMC and other departments to try to, like I say we're trying to work around the (bit) work.But I should know something this week.
Carol Frank:Okay.Thank you.
Valerie Cardwell:Hi Frank, this is Valerie Cardwell from Comcast.
Frank Malecki:I'm sorry, say your name again.
Valerie Cardwell:Valerie Cardwell from Comcast.
Frank Malecki:Okay.
Valerie Cardwell:I have two - one question and then one maybe suggestion.My question is about next day porting and whether the CSR there will be a specific field or something to indicate that a number is eligible I guess I would say for to be ported as a simple port?That's a question.
Frank Malecki:Eligible for - this related to the simple port initiative?
Valerie Cardwell:Right, so for next…
((Crosstalk))
Valerie Cardwell:Well for next space hording, you know the first criteria is the account has to be quote on quote, you know, for a "simple" port.And we're wondering if there is going to be a field perhaps on the CSR or some type of indicator when we pull the CSR that, you know, that particular lot or account is eligible for a simple port?
Frank Malecki:Oh okay.I'll have to find that out.
Kim Taylor:Frank this is Kim.Not that I know the answer, I don't know the answer to that because requirements are not all, haven't been sent to me.
But, you know, there will be a call on June 3 giving you all the requirements.
Frank Malecki:Oh okay.
Valerie Cardwell:Okay, yes I'll find out.I don't know.The challenge we have as we all know is each company has their own windows to work with for doing change management and things like that.
So our folks are trying to, you know, gear up and get things ready as much in advance as possible.So I'll let my team know.My person that normally deals with this issue, (Bennet Pang) couldn't make the call and he wanted me to raise the question.
I'll go back to him and tell him that June 3 we'll know like all the details and see if he has any concerns with that date.
Kim Taylor:Well that's the call to go over all the requirements with you.Now the 73-day notice will go out on May 20.
Valerie Cardwell:Okay.
Kim Taylor:Okay and that's the commun - you know, the notification for the business roll changes and so forth.So you'll know May 20.But the call, the requirement call with the (zelite) community will be on June 3.
Valerie Cardwell:Okay but, and anyone on this call can answer this specific question whether those business rules were contained a specific…
Kim Taylor:No.
Valerie Cardwell:Okay, all righty.And then the second thing is more of an overall question or suggestion.Now that Frank you (unintelligible) change management.And I believe you still do the cuff as well.
Is there any thought to combining the effort that is to say now that, I think you have this call scheduled for an hour from 2 to 3.Whereas before when we started I think it was like two hours.
Frank Malecki:Right.
Valerie Cardwell:We wanted to suggest that perhaps in terms of being efficient and just, you know, consolidating resources, if it's possible, and I know the (zelites) also have to support this.
But thinking about making the CMP calls from 2 to 3 and maybe the cuff calls from 3 to 4 on the same day so that we're not tying up, you know, folks for two days.Because a lot of times I think the same people from a carrier perspective are on the call.
So I wanted to throw that out as a suggestion both to Verizon and to other carriers.
Frank Malecki:Okay well I can definitely take that back and we can see what the - everybody in the (zelite) community thinks and everybody in the house.It sounds like a good idea.
Valerie Cardwell:Okay thank you.
Frank Malecki:Thank you.
(Jeannie Calesa):Frank this is (Jeannie Calesa) from (Synchronize).I have a question.
Frank Malecki:Okay.
(Jeannie Calesa):Back in I think February when we had the split off from (retanko) versus the (syncho) as they're calling it, the North Central region.I believe that a letter came out saying that this weekend, May 16, this bid for Verizon West is changing from 0772 to 5040.