Loading report ...

Blendcom

Entries

Reasons for upgrade

 
# Content Date
Total 6
Unanswered 1
7
To get the latest and greatest and to hook the phone system to our network
 10:44am · 2011-05-24
6
Primarily ongoing support. We've retained the media gateway's to facilitate TDM connectivity and as yet haven't deployed any IP handset's (although this is inevitable) we've also removed the Group Switch but this wasn't a deliverable of the project.
4:17pm · 2011-05-23
5
To enable IPT telephony
 3:48pm · 2011-05-23
4
We are adding four new sites to existing set up so upgrade to MX-One TSE at existing sites was Stage One
2:49pm · 2011-05-23
3
Un supported Platform and needed to migrate to a solution that had the potential for growth
 4:20pm · 2011-05-19
2
Support for SIP Keeping on a current platform Server based solution gives more scalable solution for IPT than using IPLU/ELU32 cards
 4:25pm · 2011-05-18

Upgrade previous version

 
Choices Percentage Count
  Total Entries 7
BC13 (TSW)
42.86% 		3
MX-One TSE (versions 2 or 3)
42.86% 		3
BC11 or earlier
14.29% 		1
BC12
14.29% 		1
Pre-Upgrade
Client asked to comment on the activities leading up to the upgrade.

Upgrade project

training requirements

your responsibilities

Infrastructure readiness

Additional Comments

 
# Content Date
Total 4
Unanswered 3
7
A full project outline and full testing before hand would have ironed out many of the errors. Making sure that our current vm system would work with the new, but didn't and so had to upgrade which was at a cost.
10:44am · 2011-05-24
6
The upgrade of the core telephony components went very well and was easy to plan. The biggest issues are around the applications prinicpally MP and CMG. I don't think either party fully undetstood the requirements (from the Bank) and limitations (from Damovo). I think the Bank would have benefitted from training in advance of embarking on the planing phase but logically within business this doesn't tend to take place until after the event. From the last user group I fully endorse Damovo view that training can greatly aid the design phase.
 4:17pm · 2011-05-23
4
We had not previously used our data network for voice (it had bee a small standalone network) so we had lots of changes to make within the Infrastructure. It was new territory for the IT guy and sometimes there was confusion over what was required for the implementation i.e rack space, number of servers etc.
 2:49pm · 2011-05-23
2
Generally, all the pre-implementation work was very good. key issues that weren't identified were: needing the re-number all the LIMs and due to that, the call logging output changed - the latter wasn't noticed by us until 2 weeks post-implementation.
 4:25pm · 2011-05-18
Executing the Upgrade
Views on the key activities undertaken as part of the actual upgrade project

Planned Outage

Data extraction/re-application

Integration into infrastructure

Acceptance Testing

DNA to CMG
Migration from existing DNA to CMG

DNA to CMG overall managed

Awareness of management tools and Directory changes

Operator awareness of changes

Comment on any specific issues/observations of the overall activity

 
# Content Date
Total 4
Unanswered 3
6
We are still running on DNA for operators although we've tested NOW. The major issue here is how the data in CMG is kept current. There has been a dispropotional amount of work (more effort has been spent on CMG than on the Core component upgrade) invloved in trying to integrate the Bank's HR databases into CMG. Therefore, businesses shouldn't assume this is a seemless migration. However, this obviously depends on their current process and database/application integration. Both the Bank and Damovo have been working very well together on this so this is no slight on Damovo. The leason learnt here is for both parties to understand the requirement and communication of the limitaions of the system.
 4:17pm · 2011-05-23
4
I felt that although it was called an upgrade, it was, in fact, a complete new system, albeit similar, but this seemed to have been glossed over by our Account Manager and Aastra e.g. given the opportunity I would have cleansed my directory beforehand, instead of which the existing directory was uploaded incorrectly. Causing us to completely re-write our directory and have that loaded at the very last minute.
 2:49pm · 2011-05-23
3
The data capture and subsequent upload highlited a Bug in the system which was resolved via a patch
4:20pm · 2011-05-19
2
These went well, but there is a noticeable difference between what people are 'taught' in the training sessions and how the engineers come to implement the solution. For example, in the training my team went on, they were told that Manager Provisioning could automatically populate CMG. What happens in practice is that although this can work, MP doesn't support punctuation, so O'Sullivan would be OSullivan and Price-Jones would be PriceJones. Because we use CMG to feed an online search, we decided not to implement the link.
 4:25pm · 2011-05-18

Satisfaction with upgrade

 
Choices (Score) Percentage Count
  Total 7
  Avg Score 1.3
No (2)
28.57% 		2
Yes (1)
71.43% 		5

Any Ongoing Issues?

 
Choices (Score) Percentage Count
  Total 7
  Avg Score 1.3
No (2)
28.57% 		2
Yes (1)
71.43% 		5

Confidence in moving forward with the platform?

 
Choices (Score) Percentage Count
  Total 7
  Avg Score 1.1
No (2)
14.29% 		1
Yes (1)
85.71% 		6

Upgrade to Version 4

May 16, 2012 · 5:03 PM