- Every Krika has to be connected permanently in the end-user’s local network to execute the local routine scheduled every 5 minutes. Krika can determine the exact model names, status, firmware, serial number or settings of your Krikakompliant connected devices.
- Krika implements various protocols for detection such as TCP, HTTP, UPNP (powered by Plugis), SNMP, etc…
- Krika mini and Krika One execute the local routine and send a report to Krika cloud-based servers in order to execute the server routine (1)
- The server routine processes and analyzes the reports. It is instantly operated by Krika cloud-based servers which will generate a dashboard the installer can consult on Krika’s website from any web browser without having to log onto the customer’s local network (2)
- The dashboard contains a detailed list of all devices connected to the local network. List is refreshed about every 5 minutes. The installer will define the email and/or sms alerts required for most important devices
- When a report sent by Krika contains some information requiring to trigger an alert, the hosted services reading and processing the report will send an email and/or an sms to the persons mentioned in the dashboard
(1) With an in-house server installation these operations are processed locally
(2) With a Krika One solution the installer can eventually access the device but cannot access the main part of Krika