After years of virtually no innovation from telecom operators, 2014 will be different. Not because telecom dinosaurs have all of a sudden become lean mean innovation machines. Quite the contrary. Most operators are still focusing on rolling out THIS YEAR’s (instead of today’s) “innovative” service which will be just a copycat of some famous dotcom.
So why the excitement?
2014 will be the pivot year. The year that will be marked in history books as the year old school lost and innovators won.
The first Ryanair-like disruptive telecoms will leave their borders and start bankrupting “traditional telecoms”. Cross-platform voice/video 4G apps will reach the tipping point. Cloud Telco PaaS will be reality. Individual communication solutions or iCommunication will be a reality. Web 3.0 will include voice & video communication. NFV will be driven by non-telecom players. WAN SDN will be deployed by more than only Google, Amazon, etc. Cloud Media Streaming will reach the tipping point. Internet of things will meet Cloud will meet Big Data will meet Mobile will meet disruptive communication solutions. Early adopters paradise…
2014 will be an exciting year for those that love telecom innovation!!! Bit pipe nightmares becoming reality for others.
Fujitsu just presented SaaSification on Cebit. Existing applications can be easily brought to the Cloud and sold via App Stores and SaaS marketplaces. IBM is also working on SaaSification and even adds multi-tenancy.
What is next?
Everybody wants to have a full App Store or SaaS Marketplace, so SaaSification is the next step after launching your store. However converting a client/server application to the Cloud is only step 1. Step 2 is creating new services that are specifically built for the Cloud.
What does Built-for-the-Cloud means?
Cloud-Ready applications should also accept the new reality of APIs. Both for exposure as well as consumption. This means that applications need to be redesigned according to application slices.
So if SaaSification wants to be successful then it needs to add quick enablers for multi-tenancy, big data, integration with external APIs as well as API exposure, etc. This integration concept can be called iPaaS or integration platform-as-a-Service. iPaaS should not only focus on exposing or integrating APIs but on providing complex services by integration multiple SaaS solutions together.
Other enablers should be added as well. Basically 80% of a SaaS solution consists out of the same elements or tries to solve the same problems. These could all be provided via a SaaSification PaaS:
- Blog – to describe the newest ideas.
- Forum – for people to get answers from the community.
- IT PaaS – where you run the actual business logic and UI. Data storage is assumed to be provided by the Big Data elements.
- Portal and Mobile Portal – allows to quickly define the “static” content for the web and mobile site.
- Deployment management – ideally continuous deployment or integration tools that allow fast feature by feature deployment.
- A/B testing – allow new features to be deployed to subsets of users and check which version of a feature has the highest impact on the bottom-line. A/B testing was made popular by Amazon.
- Automated testing – lots of testing can be automated but especially end-to-end and performance testing are the harder tests that should be focused on.
- Configuration management – manage the version control of the code.
- Metering and billing – be able to meter the resource usage by users, companies or any other element you want to meter and be able to bill users both for subscriptions as well as for usage, ideally with advanced set-up with overage, etc.
- Marketplace listing and provisioning – automate the listing of products on the marketplace as well as the provisioning of new services.
- Single sign-on & identity management – allow companies to use their own user credentials (e.g. SAML), authorization for third-parties (e.g. oAuth), etc.
- Reporting and data warehousing – this can be part of the big data stack but especially being able to create ad-hoc reports for instance for A/B testing . Of course regular business reporting needs to be included as well.
- ERP – accounting, resource management, etc.
- CRM – sales and lead management
- Operations & Maintenance – automation of back-ups, monitoring both for the performance and fault management but as well business monitoring.
- Support – helpdesk, ticketing system, SLA management, etc.
- Social integration – tools to add social aspects like Facebook apps, Twitter feeds, etc.
The idea is not that a SaaSification PaaS offers all these solutions by custom development. Instead the SaaSification PaaS should allow startups to assemble an ideal architecture by combining different solutions from different providers. For example you would be able to select the support solution you prefer, e.g. desk.com, zendesk.com, etc. and this solution would be completely integrated into the overall stack, e.g. CRM integration with help desk and fault management together with sign sign-on.
SaaSification 2.0 should focus on making sure that 2-5 people can start a new dotcom solution and focus on creating a killer service and not on building up yet another stack of solutions for configuration management, support, billing, etc. If a SaaSification PaaS can shorten the time to launch with months and reduce the needs to operate the solution with several people then startups will see the value. Instead of SaaSification PaaS a good term could be Incubation PaaS, to incubate SaaS solutions. Once the business model and solution is proven, there will be money to move to a custom-build stack but during incubation and crossing-the-chasm enterpreneurs should be able to focus on delivering value to their customers and not on re-inventing the startup wheel.
I want to take the opportunity to make some suggestions that would make Fon a really disruptive player.
Fon has some really nice residential WiFi routers. A basic version, the Fonera Simpl with an optional antenna, Fontenna, to reach more distance. Additionally there is the Fonera 2.0 N which allows a community of developers to extend the product with new functionality. Finally they can embed their software into operator’s existing WiFi routers.
Fon’s routers are based on OpenWrt, an open source Linux firmware distribution for embedded devices. Developers can create extra plugins / packages that can be deployed on the router.
How to make Fon more disruptive?
For many technical people having access to a global set of WiFi points all over the globe is a really good reason to buy a Fon WiFi. Unfortunately non-technical people might be lost in the technical details about how you can access somebody’s else Internet and might be scared of other people using their Internet. So for most people the Fon offering is like a vitamine and not really a painkiller.
By changing the value proposition of Fon towards becoming a painkiller for more people, Fon would be able to get more active demand for its products from consumers and also via telecom operators.
Fon painkiller example: Parental Control
Most parents would not care less which router is used to access the Internet. The only thing they know is that their offspring knows a hundred times more about Internet then they do. Additionally they know that Internet is full of dangers for kids and teenagers. Children always tell their parents they need Internet to do their home work. But reality is that most surfing is not done for homework ;-)
So what if Fon would have an OpenFlow compatible WiFi router with FlowVisor combined with a Cloud solution. To spare the technical details, the summary is that parents would be able to partition their Internet access based on who is accessing. What would this bring?
Kids Internet – 3-8 year olds would only have access to a strict whitelist of Internet pages. Parents would not have to find this white page themselves. Instead people and companies could make white lists and parents could subscribe to them. Examples could be a Disney white list, a SuperNanny [the television show] whitelist. Parents would know that their young children could never go to pages that are unsuitable. Young children would have a start page with icons like the iPad in which they can click on the page and immediately go their favourite games or watch cartoons. Children could be limited in the time they can spend on Internet and special bonus points for good behaviour could buy them more time or bad behaviour could be punished with less time. Parents would need an “Apple” friendly interface to pick whitelists and set-up and manage Internet access times.
Pre-teens / Teens Internet – 9-17 years od – restrictions apply. Parents could define studying time slots in which only certain Internet content can be accessed, e.g. Wikipedia. Also here external entities could define whitelists. Time-based filters for open Internet access could also be set. Additionally special purpose filters are set-up, e.g. Facebook, Twitter, MSN, Skype, eMule, Google+ etc. This would allow teens to access Facebook and other sites but to have their behaviour screened. Teens could be prohibited to upload pictures of persons, share email/telephone or physical addresses, use F* words, access adult content, etc. There would be a dynamic firewall for each service. Parents could have a high-level reporting interface to see what their kids are doing.
Parental control is just one example of how a generic router that is connected to a niche Cloud application could be a painkiller for parents. Operators could have other pain points, e.g. reduce botnets, spam, P2P content optimization, etc. Shop owners could have other pain points, e.g. social games for bars, etc.
A lot of possibilities are opening up if routers could be externally managed and very specific easy to use interfaces and solutions are build towards which communities and external companies can contribute and generate new revenue with.
The fact that every Fon router will give you access to a global free broadband network will be a nice add-on for most…
Not so many years ago, Europe was the leader in telecom. Nokia was the dominant phone maker. Symbian the dominant operating system. GSM/GPRS/3G driven from within Europe. Ericsson the dominant network solution provider.
Fast forward 2011/2012
Only Ericsson is still leading the network solution market. Their mobile arm is being absorbed by Sony however. Symbian is dead. Nokia is in coma, let’s hope its doctor from the Microsoft hospital is able to revive them. LTE is being deployed widely, except for Europe.
The new rulers are Apple, Google and Huawei. Countries like South-Korea and Japan have gigabit fiber to the home. Something no European country can match.
What should Europe do?
First of all there is a legal problem in Europe that blocks a lot of innovations from reaching Europeans. Europe does not exist in telecom world. Instead there is a collection of small and medium countries that each have their own incumbant operator and legal framework.
The first thing should be to move the telecom legal framework to European level and stimulate the creation of one open market. It can not be that in Germany or France it is not possible to get a virtual phone number [DID] without having an address of residence. Services like Twilio have a hard time to deploy in Europe because of this.
The European Union should drastically reduce its help to farmers, especially industrial farming, and instead use the funds to build gigabit fiber-to-the-home. The UK model whereby the fixed infrastructure is separated from the go-to-market entities should be a good model to follow. If we want to have more Internet companies in Europe, we should start by having fast Internet in all mid to large cities. As well as LTE access for all Europeans in 2013.
European Silicon Valleys
The next step is to create European Silicon Valleys in which startups and universities get easy access to venture capital. Without European innovation, it is hard to see how the European telecom industry will blossom again. Large telecom operators have shown few success-stories when it comes to telecom innovation. They are better at buying successful startups, then starting new innovations themselves. But before you can buy, you must have them first.
What is the alternative of not doing anything?
European employment will suffer. Telecom hardware and software development will be moved permanently to China and India. With only some small design shops in Europe at best.
Operators will become bitpipes which means that only a fraction of the current employees are needed.
American dotcoms and large corporations will attract all investments.
If there ever was a time to feel European, now is the time…