Why You Need a Next-Gen (Low-Code) BSS
for IoT Today and 5G Tomorrow
The buzz for 5G is building. This next generation of technology, with high bandwidth and low latency, is expected to change just about everything that we have come to know about wireless service. Instead of monthly rate plans, subscriptions, and leased devices, we’ll see far more on-demand ordering and new business models, like pay-as-you-go and dynamic pricing – where prices are based on supply and demand.
To succeed, carriers must throw out the rulebook that uses legacy code-based BSS systems – which are exceptionally slow to change. They must deploy new, dynamic tools to manage the Internet of Things (IoT) on current network speeds and future-proof themselves for 5G. They need a different type of back office to change offers and services on the fly, modify business rules in real time, and sell features or services by the hour, like a video game in HD, or a connected car with on-demand infotainment options.
In short, they need a low-code, next-gen BSS to bill, monetize, package, market, and serve all these new products and applications.
Carriers, MVNOs and others can’t wait years to launch new services. They must move fast.
A low-code, next-gen BSS strategy is essential because it speeds application development. While the analysis/requirements stage is the same, just about every other aspect of the development process is put on steroids. That’s because applications are customized and even integrated visually, using drag and drop functionality. Little to no hand coding is required, eliminating huge chunks of time.
In addition, business rules, workflows and user interfaces can all change dynamically and restructure the behavior of the application in real time. This is a critical differentiator and paves the way for:
- Dynamic pricing models, where prices are created on the fly (based on supply and demand)
and showcased in web and mobile interfaces
- New bundles of third-party products and services
- Different customer interaction channels
- Customer experiences that are specific to IoT applications
Say, for example:
A subscriber is traveling with her family in her connected car (an automotive MVNO using a wireless carrier’s network). They pass a soccer stadium for the next US World Cup qualifier match and the kids
want to see the game, but there’s no tickets. So the best option is to park outside for a flash tailgate party. The mom uses her wireless service to order the live broadcast just for the night. It then displays on the kids’ tablets and the car’s infotainment system. Pizza is delivered through a concierge delivery service, which knows exactly where the car is parked in the 2-mile wide parking lot.
A low-code BSS can manage all of these transactions easily because it connects swiftly to back-end systems and enables integrations using visual tools, not code. Plus, the ease-of integration supports multi-sided business models, where multiple software vendors, systems integrators, MVNE/MVNOs and others execute transactional billing, with real-time settlements on the fly.
This makes it simple to add third-party partners, like the concierge service or the one-night-only TV
subscription, and bill for their services.
Low Code Manages Huge Amounts of Complexity
A low-code, next gen BSS is also equipped to handle huge amounts of complexity. With business models such as pay-as-you-go, carriers will have to manage thousands of different instant upsells for diverse features, services, speeds, capacity, devices and things.
Going back to the soccer example, the connected car may inadvertently run over a nail on the way home from the tailgating party. The third-party concierge service dispatches a road crew to change the tire and offers to pick up a low-fat latte for Mom and healthy snacks – without peanuts – for the kids. The service changes the tires in minutes and mom is on her way. Using the connected car information, the concierge service sends a satisfaction survey when mom is safely at home and can read the text.
To execute these types of transactions, carriers must predict the most relevant upsells to individual subscribers and make timely offers, or risk leaving money on the table. They need back office systems (product catalog and order management applications) to ensure market-readiness and all downstream fulfillment. Customer care must be able to view upsells history, upsells offered, upsells purchased, qualifying/nonqualifying upsells, ideally in a 360-degree CRM.
An omnichannel architecture is also needed to manage these interactions in-app, in-store, via the web, and through app-specific partners, as well as internal and outsourced support centers. Finally, carriers need to manage those channels and handle split-billing, commissioning, and settlements.
A low-code BSS enables all this. It supports any type of marketing campaign, third-party bundle, and dynamic pricing strategy because it can adapt workflows, user interfaces, and business rule changes, all on the fly. Plus, it can enable the customer care and omnichannel architecture needed.
Fast Innovation with On-the-Fly Changes
To handle IoT now and prepare for 5G, marketing, sales and operations teams should identify their back-office capabilities to determine the following:
- Can their BSS support these types of interactions and new business models with newer
services and newer players?
- Can their BSS support changes on the fly to business rules, workflows and user interfaces?
- Can they support new revenue opportunities, such as upselling, with newer policies, newer
omni-channel markets, and newer business models?
If not, they should investigate how a low-code, next gen BSS platform can help them with IoT now and 5G tomorrow.
With both technologies, business processes, business rules, user interfaces, data interfaces, functions and general BSS processes will have to change frequently and fast. Traditional development can’t be that dynamic. But a low-code, next gen BSS can.