FAQ INTEGRATION

Our traditional engagement model for CSensorNet is as a SaaS IoT Platform. However, we also offer on-prem deployment model for our clients that are not cloud-enabled.

Our CSensorNet IoT platform is highly scalable. Every component of CSensorNet can be scaled due to the decoupled architectural design. Each component of that architecture can be managed separately. Some examples of our platforms scalability features are cluster managemetn for Messaging and Data Management components, Database Clusterings, and the entire architecture is Microservices based. Additionally, we are built on Azure Cloud which has infrastructure (Compute/Storage) that can be easily scaled by leveraging the Azure Cloud Ecosystem.

CSensorNet uses a SSL/TLS based encryption at each end point where the data gets transferred between it various subsystems. CSensorNet utlizies SSL/TLS in these areas:

1. Edge gateway to Cloud communication
2. Communication between microservices (if public subnet deployment is used)
3. Messaging subsystem and Data Management subsystem (if public subnet deployment is used)
4. DB encryption with sensitive fields encrypted using AES encryption through standard libraries
5. HTTPS based administration and visualization applications

There are two types of data in CSensorNet:

1. Admin App (CSensorNet Configuration Platform - CCP) - That data type is stored in RDBMS (Postgres) database.
2. Transactional/Device Data- All transactional data is stored either in Cassandra or InfluxDB which are both residing on Clovity's cloud. The usage will depend upon the client's visualization requirements for the solution.
Our data is backed up periodically and the frequency of data back-up and archival can be configured based on client requirements as well.

Clovity's Service Level Agreements:

Email Support only (We have a 24/7 on-call support model as well which we offer as optional).
Email Acknowledgement during business hours: 15 minutes.
Email Acknowledgement during off hours: Next Business Day.

Priority 1 resolution: Next business day.
Priority 2 resolution: 5 business days.
Priority 3 resolution: Next Product Release

Key Highlights & SLA’s:

Email Support only (We have a 24/7 on-call support model as well which we offer as optional).
Email Acknowledgement during business hours: 15 minutes.
Email Acknowledgement during off hours: Next Business Day.
Priority 1 resolution: Next business day.
Priority 2 resolution: 5 business days.
Priority 3 resolution: Next Product Release

This is highly dependent on the level of complexity of the added feature. Please contact Clovity Sales Representative for a quote based off the business requirements.

Yes our platform can do live automobile tracking and diagnostics. As long as the hardware can allow PUSH/PULL of Data and has endpoints exposed to do so, CSensorNet can definitely do live fleet tracking. We have case studies in Telematics (Fleet Health and Fleet Live modules) space currently which are readily demonstratable.

Yes, pushing a live view of an asset in the field is easily attainable. Enhancing CSensorNet to include this functionality won't be a problem. Some aspects of this already exists in the platform currently . For example we already have an integration to Lyft for some of our healthcare clients.

Yes, we love to train people on CSensorNet. We provide On and Offsite training and the cost is part of the one time implementation fee. Clovity's goal is to empower our clients to use our platform to refine and grow the solution. However, we are to help remedy any problems they cannot solve.

CSensorNet provides device management capabilities like Device Provisioning, Templating, Sandboxing etc. Our customers have complete access to this module and can create role based access to their organization. All device management aspects can be done by the customer directly.

Responsive and Progressive Web Apps is an OOB Platform feature. However, we have done a number of native apps for client specific customer development requests depending on their use case.

Multi-tenancy is already supported and is OOB feature of the platform. Role based screen functionality which falls under Multi-hierarchy and Super User permissions is also currently included in platform features. Each Customer customer deployment will have its own Cloud and can easily be white-labeled as needed to fit our client's needs.

Currently Clovity's platform billing capabilities are limited to Platform Billing such as the number of devices connected, payload size, throughput etc.

Yes, this capability is deployable within CSensorNet.

Yes, this would fall under Clovity's Scripts & Alerts category. It can be done as long as a Device or the Device API's are providing battery diagnostic information. Our team would then configure the business rules accordingly to trigger the purchase of replacement batteries. This could work for a myriad of use cases including lightbulbs, air filters, etc.

The core source code of CSensorNet will be retained by Clovity. We take this approach so that all Clovity clients who are using CSensorNet have the same version of the core plaform. All customized products that are developed on top of the core immediately become IP of the client. Clovity is responsible for the maintenance of the CSensorNet core across all clients and is included as part of our service free of charge (upgrades, maintenance, etc).

Yes, it will be fixed free under 30 day warranty.

Our Platform is a SaaS deployment and we have dedicated servers on Microsoft Azure. CSensorNet can effectively work on AWS and Google Cloud if that is our client's preference. A Cloud can be easily spun up by our team for a small cost, with billing on actuals for usage.

Yes, it is part of our Managed Support package.

Yes, the CSensorNet agent which connects the hardware end point to the s/w cloud endpoint is included.

We build the CSensorNet software to be agnostic of the hardware and we configure to each API. This is included in the Implementation fee for each initiative based on the APIs that are desired to finalize the solution.

Yes, Cloud storage/analytics, API's, rules, reports, alerts, notifications via email/text/push, and dashboard visualization features already exist in our OOB SaaS Platform. Only big ticket items such as Geo-fencing functionality or Customer Specific custom reports will have to built and configured as per Customer's use case.

Yes, white labelling is included in the upfront cost.

Yes, multi-tenancy is included.

Yes, but please note that the UI may not vary much in terms of look and feel but functionaly will be limited based on the determined user permissions.

Yes, these are included in the CSensorNet platform.

Clovity will have our code base on Git Hub and is always accessible to our Customers. All core source code will be white labeled for Customer use and any 'customized' solutions geared for our Customer's business will be Customer IP. The core source code of CSensorNet will be Clovity IP. We take this approach so that all Clovity clients who are using CSensorNet have the same version of the core, then all customized products that are developed on top of the core are IP of the client. Clovity is responsibile for the maintenance of the core across all clients and is included as part of our service free of charge (upgrades, maintenance, etc).

Git Hub is where we provide access per client to their own code base and CSensorNet's latest enahancements, core, etc.

The core receives updates each quarter and as necessary due to security compliance as well as good coding practices. Any updates made to the core will be shared with our Customers. We can perform the upgrade for you or you can do so based on the schedule with of our client's IT group. We are flexible either way. Clovity will send notifications and can provide a Test enviornment to ensure you are good to go with your udpates.

The software core is available immediately and would be until we go out of business. However, if that were to occur or more likely if we were to be purchased, the standing release is what our clients would still have access to. We would enable some sort of agreement either with the new owners of our company or set you up with one from Clovity directly. Our goal is never to limit or impact your busienss model, so we will readily come up with an agreement to give our clients full access to the core.

For Clovity's current customers, there is no charge for our maintaining the core or for any upgrades that other clients ask us to make as a 'standard' for the core. The core is Clovity IP, the development or customization that is done on top of that is Customer IP. It is available via Git Hub as part of our contract agreement. Once a customer signs the agreement, that code that is built on top of our core is theirs from day 1.

This would happen quickly, we can easily hand over the Git Hub repository same day in almost all cases.

No, our clients would continue to be online with the latest release prior to the initiation of migration/transfer. From the source or code perspective, Clovity is completely transparent to the end users or our client's customers. However, if a client decides to change hardware, network provider or Cloud provider, then there would be possible impacts to the client's customers. In most cases, switching cloud providers causes no impact as it is not done during business hours. If a client decides to switch hardware, for example, which is connected to the Verizon network to another hardware provider that is connected to a different network provider, then there would be an impact to migrate existing users on to another hardware provider. All new customers using any new go forward hardware strategy and new network would not see any difference.

No, Cloivty nor our solutions delivered to the market have ever had a security breach. We perform rigorous DAST and SAST testing on our software quarterly to ensure we up to date on the latest security standards. Our Cloud partnerships are Microsoft Azure, AWS and Google and backed by their security standards, and again our cloud solution has never had a breach. Our hardware providers are also certified for connectivity or 'tapping' and for physcial introusion breaches. Clovity even adds an extra layer of security by breaking up and encrypting data in transit from device to network. In case of network breach, the data transmission with Clovity's software is replicated and re-routed via a different network path so that any breach will only result in a single packet of data nullifying the objective of the intrusion.

No such incident has happened till now.

Clovity has network layer firewalls for on-premise deployment, Web Application Firewall (WAF) Plus for Cloud deployment (which helps prevent a lot of common security breaches like DDoS, etc.) and additional levels of security as the CSensorNet SaaS version is deployed on Azure Cloud. Clovity hasn't had a breach to date, but if there was a chance that something got breached somewhere in the supply chain of data, our software can quickly detect and will notify us in real time where the breach is located. Because we monitor the hardware, data and network from beginning to end, we will be able to quicly troubleshoot what the problem on a 24/7 basis. We would then work to create any security patch to resolve the issue and determine what data was breached if any.

Yes, Clovity's Services team will notify all Customer of any severe level issues we have detected and will deliver our time to remediate per our SLA agreement .

CSensorNet uses TLS 1.2 as well as at least a 128 bit encryption with additional layer of network encryption for redundancy.

This functionality is currently under development and is scheduled to be released in Q1 2020

Clovity utilizes TLS 1.2 Encryption.

Our resources have certifications in OWASP, HIPAA, NIST, CMMI, ITIL, and TIA.

Clovity's current accolades include 2018 & 2019 Growth IoT company of the year by CIO Review Award as well as 2020 IoT Breakthrough Award for “Emerging Company of the Year for the Enterprise Market”.

We are currenly on a number of lists including SAM - System of Award Management for Government contracts; Smart City Alliance, and HIMMS- Healthcare Information and Management Systems Society.

For 2020, our growth strategy will be to leverage our 5G partnerships to develop products that can be sold through our Arrow Partnerships and existing customer channels. We will grow in our partnerships with the state of Colorado and initiatives for Smart City as well as International Trade with India. Clovity will be bringing smart Agriculture and Smart Cities innovation hub to Rino/Denver and deliver in solutions in various states in India. Last we plan to grow by white-labeling our products to several key clients who are looking to grow their product offering in the Industrial space (schools, hospitals, emergency and Oil & Gas). We plan to open a hub location in 2020 in RiNo district in Denver, Colorado.

In next 3 years, Clovity looks to have a CAGR of 1200%. We see the most growth is coming from new partnerships, IoT-as-a-Service, 5G and industrial IoT bundles.

Yes, we are doing this currently with some of our clients who are interested in selling our product under their banner. We are also open to selling under our current sales channel under Customer Smart label. We are part of the Arrow selling program which puts our IoT bundled products and services through Arrow's $20 Billion sales channel. We would be open to introducing new Customer bundled product and sell that through the Arrow marketplace. This can happen as soon as we create a bundled product and Clovity generates a SKU.

If it's through our sales channel, Clovity will work on a simple revenue sharing agreement. If it is through a client's sales channel, the structure would look like our traditional MVP deployment. Costs will include a monthly subscription price, an Implemenation or activation one time fee, and a one time hardware purchase fee (if applicable in that solution). We are flexible to other models, however. Since Clovity also provides an 'on-premise' model of CSensorNet which is less like a subscription model but most as a monthly fee for the application (without including cloud or network connectivity costs).

Clovity backs up its data weekly. Of course, the frequency of data back-up and archival can be configured based on client requirements.

Data is stored for 30 days for Live Data and can be configured based on the client preference. Our Archival mechanism holds the data in the archival and reporting databases for a term of 1 year as per GDPR guidelines.

Yes, Storage Costs and Network/Data Transfer costs would increase in this regard. However, with many of our clients, we implement an archive strategy so keep transactional costs low. Additionally we can move data from transactional nodes to a data warehouse for histroical reporting and trending which will lower costs. Through Clovity's partnerships, we can help negotiate costs should the frequency, demand and size increase over time.

This is directly proportional to the frequency of back-ups and duration of data storage. However, through a comprehensive archive strategy that can mitigate the increase in data size, Clovity can work to keep costs as low as possible to the client.

Key Highlights & SLA’s:

Email Support only (We have a 24/7 on-call support model as well which we offer as optional).
Email Acknowledgement during business hours: 15 minutes.
Email Acknowledgement during off hours: Next Business Day.
Priority 1 resolution: Next business day.
Priority 2 resolution: 5 business days.
Priority 3 resolution: Next Product Release

The standard support out of the box is through email during business hours. However, if more support is needed and/or immediate contact is required, Clovity has our premium support package which is $1,500/per month per customer and includes live 24x7 support during US hours.

MVP Pricing Only, exclusion of any customized (non-standard) reports and excludes some Geo-fencing, these can be fast followers to deployment.

CSensorNet is built on the micro-services architecture with each micro-service being deployed on a separate server instance. Typically, each server instance requires 2-4GB RAM/20GB HDD. This architecture allows us to grow the system horizontally as well as vertically. We use the combination of Load Balancers/Scaling Groups to enhance the capacity of a particular MS.

Apart from the middle tier, we allocate compute and storage capability for the User Interface, Core Engine and the Database layer.

All the APIs can be found on https://developer.csensornet.com.

Please note, Release 3 for the Platform with lot more additional features (including 24 AI/ML algorithms) is scheduled for end of May and additional API’s will be added to the above portal post this release.

The end-to-end transmission of data is secured using SSL/TLS encryption. Apart from that, for interacting with the APIs of the system, we are using MFA/OAuth2.0. Additionally, Release 3 incorporates Application Secret Keys which further enhances the system security.

Sure. We can either share screenshots of the platform or alternatively (which is recommended), we can schedule a deep dive walkthrough of the platform covering all the platform capabilities including UI/Analytics as well as AI/ML aspects.

Device Management (Interface, Integration and Management of Sensors, Gateways, Edge Components) is the heart of CSensorNet. Most of the features of CSensorNet are directly or indirectly related to the devices. Devices can interface with CSensorNet either directly (provided the devices possess such capabilities) or through the Edge Gateways. CsensorNet’s edge module, also known as CSensorNet Edge Agent (CEA), is deployed on the edge gateways and aids in interfacing sensors with CSensorNet.

As a point of reference, below architecture outlines various modules, standards and features of CSensorNet Platform.

Through the CSensorNet Configuration Portal (CCP), an administrator can administer the entire IoT network for any scaled enterprise level implementation under one place from registration, provisioning, and monitoring of edge devices to managing the data ingestion and transformation, including user management restrictions. Also, please refer to https://developers.csensornet.com for additional details on features covered under Device Management among others.

CSensorNet is an end-to-end IoT software Platform where we offer a complete ecosystem including integration with the devices/edge agents (CSensorNet Edge Agent - CEA), management of data (CSensorNet Configuration Portal - CCP/Core), cloud management (CCP/Core), and dashboard/business rules capabilities which includes AI/ML modeling (Core/CSensorNet DataInsights – CDI). However, we have also exposed most of the core platform APIs via REST services, the details can be found on https://developers.csensornet.com. Other systems can make use of these APIs and build their own systems on top of CSensorNet.

CSensorNet is offered in following models currently:

A. IoT-As-A-Service (IoTaaS): Clovity’s Managed Service takes care of everything you need to deploy IoT in customer’s organization. Clovity’s single monthly pricing per sensor or a fixed monthly platform fee provides seamless management of hardware (sensor), activation and monitoring, all big data analytics and data management, all hosted cloud services and network connectivity so that customers can focus on the actionable insights as well as impacts for greater business value.

B. On Premise: Installation of our application CSensorNet deployed into a customer’s own Data Center or the customers private Cloud supported by Clovity. The pricing model is a combination of Onboarding cost & with monthly support and monitoring cost.