Feature INTEGRATION

A Platinum Support option is available for CSensorNet Standalone. This additional support package is designed to help you achieve your business performance goals.

Filter

CSN (OOB Features) - Technical

Security: What type of Security features does CSensorNet currently utilize?

All communication between devices are fully encrypted using TLS.

API access is controlled by the industry-standard OAuth2 standard. Remote API access tokens are also by OAuth 2 standards.

Devices that communicate using MQTT make use of application secrets for validating incoming data from device

Storage of all sensitive data is encrypted.

Architecture: What type of architecture is CSensorNet built with?

Readily supports Multi Tenancy architectures.

CSensorNet is built with a Microservice architecture and includes Event logging.

Comes standard with messaging queue for various interservice communications.

CSensorNet is cloud ready and can be deployed on any Cloud platform.

User Accounts: How are User Accounts used and permissioned in CSensorNet?

Organizations are the highest level resource in most of the CSN platform. All applications and dashboards are either owned by a user or by an organization (of which users can be members).

User profiles store information like name and email address.

CSensorNet users are authenticated by OAuth2 web services.

Sandbox/Mocking Device: How easy is it to sandbox or mock a device in CSensorNet for testing?

With CSensorNet's Sandbox functionality it is easy to mock your physical device and its data push. Using this functionality can allow for visual dashboard development in advance of actually connecting a physical device.

Organizations: What are "organizations" and how are they deliniated in CSensorNet?

Organizations allow users to unlock the full potential of the platform by positioning multiple members to manage devices, dashboards and utlize the sandbox environment.

An organization can have multiple members, enabling certain limits on different member profiles pending invitations by admins which is dependent on the organization’s tier level.

We can define multiple levels of roles as per any organization's needs.

Organizations and Sandboxes within the platform are subject to certain limits based on the number of resources (e.g. devices, applications and more) that are registered on CCP portal.

Enterprise organizations have access to all audit logs meaning there are details on the creation, modification, and deletion of resources by your organization’s team members.

CI & CD: Does CSensorNet use tradtional DevOps methods for deployment?

Builds and updates are managed by Jenkins pipelines

Jenkin publishes docker images to Docker hub for deployment.

White Labeling: How easily can CSensorNet be white-labeled for their client's usage?

Easy white labeling functionality enables CCP to be highly customized on its overall look and feel. Clients can use their custom domains and logo as well for further branding alignment.

Workflow: How does Clovity manage workflow in CSensorNet?

Clovity utililzes Node Red workflows in creation of the workflow via an API.

This enables custom node creation which can used in NodeRed.

Device Management: How does Device Management work on the CSensorNet portal, CCP?

CSensorNet has device configuration with automated payload parsing.

Devices push their state via different protocols to the CSN platform.

Device triggers allow users to instruct devices as well as services to take some kind of action. This can be readily configured on device management module of CSN's Configuration Platform (CCP).

Some types of devices, like Bluetooth sensors, cannot connect directly to another platform. They require some form of middleware, like raspberry pie, in order to communicate externally. These types of gateways can directly connect to CSensorNet using different protocols.

Edge devices are similar to the concept of a gateway device, but have addiitonal functionality to act on the data they receive from their peripheral systems.

Dashboards: What are the features of the dashboards utilized by CSensorNet?

Dashboards provide a powerful way to display information that is relevant to the user and aids in analytical processes. We currently use an open sourced platfrom called grafana for creating these dashboards.

We created numerous Grafana plugins suitable for different types of analysis.

Dashboards have three levels of access: admin, viewer and editor.

"CSensorNet dashboards or panels can be embedded into an HTML document."

Grafana is integrated via an API in CSensorNet.

Reporting platform: How many types of reporting can CSensorNet do?

CSensorNet supports multiple reporting formats depending on the data that the platform is surfacing. Standard reports as well as customized reports are available.

MQTT: Does CSensorNet support two-way MQTT communication with devices?

CSensorNet supports MQTT by receiving data on its MQTT queue.

REST API: How does CSensorNet utilize REST APIs?

CSN Configuration Platform consists of Device management, User management other CCP features are configured via REST API.

WEB SOCKET: Can CSensorNet utilize Web Sockets?

CSensorNet supports WebSockets for Device communication

Devices can send data via REST APIs and through HTTP calls.

CSN (OOB Features) - Business

Security: What type of Security features does CSensorNet currently utilize?

All the communication between Edge and Cloud layers are secured using TLS encyrption.

Admin application access is encrypted using both SSL and TLS encryption protocols.

User access is controlled by the organization's administrator. Role Types CSensorNet supports are:

Super Admin
Org Admin
User

Databases used by CSensorNet are encrypted and obfuscated using database level encryption methods.

Dashboard access and editings are governed using roles like Editor and Viewer.

Architecture: What type of architecture is CSensorNet built with?

"CSensorNet can either be deployed in a private cloud or can be used as SaaS. The Multitenancy capability caters to SaaS model of CSensorNet wherein the same instance can be used to support multiple clients."

The intentionally created "loose coupling" between various CSN components ensures that the sub-systems are not interdependent on each other.

Industry standard messaging protocols like MQTT and Kafka form the backbone of the messaging system of CSensorNet for two way communication as well as real time data processing.

CSensorNet has been developed keeping in mind that it should support cloud agnostic deployment as well as on premise deployment.

User Accounts: How are User Accounts used and permissioned in CSensorNet?

Organizations are the highest level resource in most of platform. All applications and dashboards are either owned by a user or by an organization (of which users can be members).

User profile stores information like name and email address.

Industry standard user authentication and authorization protocols like OAuth2 are being utilized.

We supports Social Integrations of Google/LinkedIn

Sandbox/Mocking Device: What does the Sandboxing feature of CSensorNet enble clients to do?

Sandboxing helps the potential clients to check how their devices that integrate with the system would behave in a real world.
With a data generation capability of up to 6 months helps in understanding and gauging the real behavior of the system over a long term period.

Organizations: What are "organizations" and how are they deliniated in CSensorNet?

Organizations allow users to unlock the full potential of the platform by allowing multiple members to manage devices, dashboards and sandbox.

An organization can have multiple members, enabling certain limits on different member profiles pending invitations by admins which is dependent on the organization’s tier level.

We can define multiple levels of roles as per any organization's needs.

Organizations and Sandboxes within the platform are subject to certain limits based on the number of resources (e.g. devices, applications and more) that are registered on CCP portal.

"CSensorNet keeps track of all the activities being performed by users of the system.
This helps in auditing of the various changes and even aids in retracting any changes that are made if any errors occur. "

CI & CD: Does CSensorNet use tradtional DevOps methods for deployment?

All the changes being committed are released every night as Nightly Builds.

Docker images ensure that the latest changes are readily downloadable to the clients as needed.

White Labeling: How easily can CSensorNet be white-labeled for their client's usage?

White labeling enabled CCP to customize look and feel.

Workflow: How does Clovity manage workflow in CSensorNet?

Edge workflows can de easily deployed by employing the industry standard Node-Red API.

Custom node catering to various functionalities are being developed using Custom nodes
https://flows.nodered.org/node/node-red-contrib-azure-event-hub-send-message

Device Management: How does Device Management work on the CSensorNet portal, CCP?

Adding, Deleting, and Updating devices can all be done through the CCP module.

Create template recipes for bulk device creation and deployment.

"Enabling, Disabling, and Deactivating devices are simplistic.
All the capability lies in the hand of the users with CSensorNet and the CCP module."

Dashboards: What are the features of the dashboards utilized by CSensorNet?

Dashboards provide a powerful way to display information that is relevant to the user and aids in analytical processes. We currently use an open sourced platfrom called grafana for creating these dashboards.

We created different type of Grafana plugin suitable for different type of analysis.

Dashboards have a three levels of access: Admin, Viewer and Editor.

"CSensorNet dashboards or panels can be embedded into an HTML document."

Grafana is integrated via an API in CSensorNet.

Reporting Platform: How many types of reporting can CSensorNet do?

CSensorNet supports multiple reporting formats depending on the data that the platform is surfacing. Standard reports as well as customized reports are available.

Clients or our engineers can configure a set of email addresses to receive a PDF report of the dashboard at a regular intervals.

Implementation: How long is the standard imlementation of CSensorNet?

"Every CSensorNet implementation or deployment has a 6 weeks implementation time. The following artifacts are included with each implementation: "

By default, 7 custom reports are included in the implementation of our platform.

"5 visualization dashboards would be included in the implementation. There needs to be a prior agreement with the client on the datapoints to be used for the deployment to ensure the right data is being targeted for visualization. "

10 Triggers per device can be configured with each deployment.

Connect With CSensorNet Experts

Talk to an Expert

Using CSensorNet is simple and turnkey, however there are times when Clovity may need to step in to help with a particular integration or feature set up. The development experts at Clovity can guide or take over the action to ensure that CSensorNet is fitting our clients needs precisely. Reach out to us for help, we are always ready to assist.

Request a Demo of CSensorNet

Nothing is better than seeing a particular technology in action to judge its value. Schedule some time with our CSensorNet experts to show you how our solution can bring your connected device initiatives to life in a matter of days or weeks, not months or years.
 

Download our complete IoT whitepaper.

Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled.

LEARN MORE