Scenario 1: Custom Solutions for Large-Scale and Medium-Scale Enterprises
This scenario assumes one-off customized product sales. Your cloud platform is used for data collection, storage, analytics, and visualization. The enterprise customers have multiple device types that should be connected both directly (for IP devices) and via IoT gateways.
The vertical solution implementation often assumes inviting a system integrator having:
- Essential industry skills (e.g., predictive maintenance of turbine generator units or refrigerator energy saving enhancement in retail networks)
- Trained and certified engineers with the IoT platform technology expertise
Your key account managers along with the salespeople of an industrial partner (system integrator/engineering company) can drive a sale of such a custom solution. Tibbo employees can also participate in the sales on behalf of our partners.
In such projects, the automated billing is not applicable. The pricing proposal and billing methods are developed individually.
There is a separate platform instance (server) provided for every customer. Multi-tenant servers are not used. In most cases, the cloud platform server is integrated into the customer’s corporate system within the project scope.
The IoT platform edge instances can operate inside gateways and perform the following tasks:
- Direct alarm messaging to local operators
- Data buffering upon the cloud connection failure
- Simple audio/video analytics (e.g., motion detection)
- IoT edge analytics based on the machine learning, etc.
Update, management and configuration of the edge platform instances is performed by the main platform server. This centralized edge gateway management is a part of the value proposition to customers having a large number of remote objects (e.g., hub sites, transforming sub-stations, fuel filling stations, etc.).
Scenario 3: IoT Application Enablement for IoT Device Manufacturers
IoT OEMs face the same challenges as smaller companies implementing their IoT projects: preparation of a cloud infrastructure, deployment and maintenance of a device management software, designing a monitoring system atop of it. The companies producing smart meters, fitness bands and pet trackers serve as good examples for the case.
It often happens that such companies start developing their own cloud system from scratch, but soon realize that the costs for its development and support are huge. However, the system they are trying to build is hardly customizable and doesn’t meet the high-profile customer requirements.
Having an option to host the IoT platform (according to PaaS model) at a predictable price comparable with the server hosting costs (i.e. 2-5 times higher, though not 10-100 times), many of such companies will employ a cloud platform from day one, the others will even give up on the software development.
In contrast to the SMB scenario, most OEM vendors develop their own unique system front-end (interface) regardless of the quality and capabilities of the Platform's UI Builder.
In a technical sense, this scenario is scarcely different from the SMB scenario. Billing and scalability are handled in the same way. However, some minor differences still exist:
- Since the equipment is in-house development, the quality of step-by-step IoT app enablement instructions is of top priority
- The quality of APIs and documentation allowing to implement a vendor-specific front-end is an important functionality of the platform’s visual UI building tools