Lower OPEX

The Axiros architecture is designed to prevent the risk arising from multiple deployments of non interworking IoT applications that share the same operational processes but – at the same time – they do not share the same operational tools.

The typical stove pipe IoT application design – focused on the vertical integration of the data streams coming from the field – does not integrate the core OSS functions in a unified framework. As a result, large scale processes which involve provisioning, configuration, activation, maintenance, monitoring, performance management and alarming of the connected IoT infrastrcuture happen on a chaotic and intrinsically inefficient platform – typically made of a multiplicity of tools and data interfaces.

This is a major obstacle to scaling the solutions for service provider and one of the main reasons for dissatisfaction from the customer base in the assurance cycle.

By contrast the Axiros AXPERIENCE architecture aims at reducing the number of intermediate software components levels and providers a comprehensive view of the service configuration and performance indicator on a single pane of glass – even though the underlying software architecture might be extremely diversified and complex.

This technology – which has been initially developed for the large telco carriers and for complex service architectures – fits naturally in the heterogeneous environment of IoT deplyments, where the complexity arises from the variety of technologies and proprietary implementations.

The benefit for the service provider becomes obvious:

• A unified framework to incorporate new applications in the same application container
• A single viewpoint for the technical support team, irrespective of the complexity of the service
• An integrated set of access APIs that enable end to end execution of fulfillment and assurance cycles
• A data normalization layer, that decouples service logic from actual device implementation, thus ensuring real hardware independence

This table provides an overview on how an IoT deployment for a Residential alarming service might be affected, in its lifecycle, by missing the key features that enable the customer care team to be effective up to the point to generate several millions USD per year of inefficiency on a sizable deployment.

Even though the business case might hold completely just with the operational efficiency, this is not the only area will benefit from the introduction of AXPERIENCE. Some more examples come from:

• Quicker time to market: which is due to the ability to resuse componenets of the operational framework already developed for other applications
• Reduced need for engineering recycles: which comes from the ability to test and exercise the platform already in the early stage of the product development
• Fast propotyping: as for the AXPERIENCE platform even an incomplete mock up can be treated as a full-featured device by using the internal workflows to supplement the missing features
• Better control in the supply chain: which comes from the hardware independence capability

Even with all of the advantages indicated above AXPERIENCE does not force the application developer to change the tollchain or adopt a new methodology.

The contacts points and the API of the platform are extremely non instrusive and designed to preserve the efficiency of the IoT development team while – at the same time – simplifing the implementation of ripetitive tasks. The intergration between AXPERIENCE and the hosted IoT application happens with a common set of REST APIs – available in the majority of modern development systems.

Source: Axiros