![]() ![]() ![]() |
|
mattbush: If it is officially an excuse that they have 3 systems and cannot merge them for 2 years than this is very lame. Vodafone NZ on the world stage is a small player and much much larger mergers and acquisitions happen daily without this sort of nonsense after 2 years.
mattbush: If it is officially an excuse that they have 3 systems and cannot merge them for 2 years than this is very lame. Vodafone NZ on the world stage is a small player and much much larger mergers and acquisitions happen daily without this sort of nonsense after 2 years.
KiwiNZ:mattbush: If it is officially an excuse that they have 3 systems and cannot merge them for 2 years than this is very lame. Vodafone NZ on the world stage is a small player and much much larger mergers and acquisitions happen daily without this sort of nonsense after 2 years.
Maybe you could post some suggestions and insights for them here to pick up on.
mattbush:KiwiNZ:mattbush: If it is officially an excuse that they have 3 systems and cannot merge them for 2 years than this is very lame. Vodafone NZ on the world stage is a small player and much much larger mergers and acquisitions happen daily without this sort of nonsense after 2 years.
Maybe you could post some suggestions and insights for them here to pick up on.
There are hundreds of examples out there. I am sure all the fat cat execs are aware of them, but would sooner fatten their salaries/bonuses then improve their systems. As I said earlier it does cost a lot to merge legacy systems from past mergers, but this should be budgeted for as part of the merger/acquisition.
NonprayingMantis: they acquired iHug around ten years ago.
AFAIK you still cannot have 'vodafone' (iHug) broadband on the same bill as a mobile.
Demeter:That would be mainly because any time we change something that might affect the way services are billed, no matter how minor, people cry rivers of tears. We would have merged everything together years ago if it were possible or simple.
zaptor:Demeter:That would be mainly because any time we change something that might affect the way services are billed, no matter how minor, people cry rivers of tears. We would have merged everything together years ago if it were possible or simple.
This.
For those who have experience with Enterprise level real-time billing systems, they are anything but trivial. This is just the front end operational side, let alone the back end (which typically comprises several disparate middle-ware services, feeding heavy duty database instances).
Even when two companies merge, who both use the same exact billing vendor there are significant issues in customer/subscription migration.
Although, billing protocols (like Diameter) exist for standardisation of inter-entity communication it doesn't saying anything about how each entity is implemented or how data is stored.
It is not easy.
Demeter:NonprayingMantis: they acquired iHug around ten years ago.
AFAIK you still cannot have 'vodafone' (iHug) broadband on the same bill as a mobile.
That would be mainly because any time we change something that might affect the way services are billed, no matter how minor, people cry rivers of tears. We would have merged everything together years ago if it were possible or simple.
zaptor:Demeter:That would be mainly because any time we change something that might affect the way services are billed, no matter how minor, people cry rivers of tears. We would have merged everything together years ago if it were possible or simple.
This.
For those who have experience with Enterprise level real-time billing systems, they are anything but trivial. This is just the front end operational side, let alone the back end (which typically comprises several disparate middle-ware services, feeding heavy duty database instances).
Even when two companies merge, who both use the same exact billing vendor there are significant issues in customer/subscription migration.
Although, billing protocols (like Diameter) exist for standardisation of inter-entity communication it doesn't saying anything about how each entity is implemented or how data is stored.
It is not easy.
networkn: Is there ANYTHING that can be done to change the music. I have spent what seems like 2 months on hold and I am getting homicidal listening to crowded house. It's a LONG LONG LONNNNNNGGGGGGGG standing complaint. Someone have Russell's Number, perhaps we could make him stay in one place for a few days listening to the same song over and over!
Insanely frustrating. Worse still it restarts everytime you are on hold and then picked up and then put on hold again!!!!!
zaptor:Demeter:That would be mainly because any time we change something that might affect the way services are billed, no matter how minor, people cry rivers of tears. We would have merged everything together years ago if it were possible or simple.
This.
For those who have experience with Enterprise level real-time billing systems, they are anything but trivial. This is just the front end operational side, let alone the back end (which typically comprises several disparate middle-ware services, feeding heavy duty database instances).
Even when two companies merge, who both use the same exact billing vendor there are significant issues in customer/subscription migration.
Although, billing protocols (like Diameter) exist for standardisation of inter-entity communication it doesn't saying anything about how each entity is implemented or how data is stored.
It is not easy.
"When the people are being beaten with a stick, they are not much happier if it is called 'the People's Stick'"
|
![]() ![]() ![]() |