Article written by Krzysztof Kwiatkowski, BSS Product Manager.

[…] Supporting M2M with an existing BSS platform creates major problems with configuration, integration and processes. Most operators, therefore, go for separate organizational units and a dedicated software stack, mainly in terms of BSS. This is the preferred approach because traditional telecoms business and M2M necessitate different partners and logistic processes, while the various business verticals served by the latter all have their own individual needs. Another, even more important, reason for building
a separate “silo” for M2M relates to costs. In the US, ARPU from traditional telecom services is about $50, while the costs of network management, customer management and acquisition are at about $20-30.
In comparison, M2M has an ARPU of $3 and costs of about $1.4-1.6 – systems supporting M2M are very
cheap to maintain and operate, particularly as these figures include the costs of labour and licenses.
When it comes to deciding about the right delivery model for an M2M platform, there are also two approaches. One is to choose an outsourced platform through a SaaS model or using a platform alongside other operators via an advanced cooperation programme – usually related to international roaming and accessing M2M applications for particular verticals. This approach may have low start-up and operational costs and assure a potentially faster launch but as it enables one platform to be used by many different operators, it dilutes the possibility of building a competitive market strategy.

In addition, the ownership of the customer database is shared, which entails obvious risks. The other approach is a licensed platform model, which may prove to be slightly less efficient in terms of OPEX,
but grants the operator full ownership of the platform and their customers.[…]

Full article available at: