Managed services contracts are a big source of revenue for many big telcos. There are many variants on what a managed service is but l’ll loosely define it here as a contract between a service provider and an organisation where the organisation delegates some responsibility for running their communication network to the CSP. It could be for managing telephony, LAN, WAN, etc on behalf of the organisation.
In many ways, this type of contract makes sense as it allows the organisation to focus on their core business, which could be banking, mining, manufacturing, etc.
Generally the scope of the managed service is restricted to operations of the network. It could be so much more, but we’ll have that conversation another day.
Each organisation has their own unique characteristics such as network, reporting, processes, team structures, etc. Despite this, I’ve been surprised at how little OSS re-use has been applied across managed service contracts at the carriers I’ve assisted.
I’ve been surprised that architectures, processes and even OSS products have been built independently, almost from scratch for each customer. There seems to be so much opportunity to build a templated management solution for all managed services contracts that are then tweaked to meet the unique needs of each.
Each new managed services contract would be dimensioned, stamped out from the template and then configured for specific needs.
I’m sure most OSS vendor offerings could be architected for templated builds, just like they are when set up to serve multiple environments (eg PROD, TEST, DEV, etc) but I’ve never seen this as a distinct pitch / offering from any vendors interestingly.
The benefits of a “building block” OSS for managed services are numerous, but ultimately lead to more efficiency and consistency,Read the Passionate About OSS Blog for more or Subscribe to the Passionate About OSS Blog by Email