Seemoto service is responsible for:
- Receiving, aggregation and storing of data from sensor and gateway devices; measurements and location information
- Controlling and configuration of devices according the system configurations
- Alert creation according alert configurations and related messaging activities
- Giving access for customers to their company data through browser based User Interface
Access to the service is provided through standard web browser. Following browser versions are supported Google Chrome, Explorer 9, Mozilla Firefox 10 or later.
When user logs in to the service the current version of the service is shown on the top right-hand corner of the browser.
The Seemoto user interface is grouped according to function based views: Assets, Alarms, Map, Reports and Maintenance (for administrators).
The key concept is asset, which is logical representation of the base unit under monitoring – room, container, vehicle or equipment. Each asset must have at least one node, which in practice is the physical Seemoto device. Each Seemoto device has at least 1 sensor that transmits data (e.g temperature). Asset structure is illustrated below (minimum configuration in color):
There are no limits to the number of assets or nodes an asset can have. Therefore the highest level, asset view, may be configured according to customer preference. One asset can contain a single refrigerator with one (or more) temperature sensing devices, or company’s all refrigerators.
There are two main types of assets, fixed and moving, but various sub-types are available.
The asset view consists of the Top Bar (1) and the asset listing (2), See picture below. All views share the same top bar, where the user can choose the language, navigate between views and change your password/ logout.
Assets are all listed on the left hand side. By activating the asset you want to look at, you are able to see all the sensors included in the asset as well as their latest measurement value and time.
The Grid view is an alternative to the List view. Both views allow one-click access to the sensor value reports (1 and 2 in the picture below).
The map view is for tracking the location, routes and localized measurements of moving assets. A moving asset can be a vehicle, or a cold box. In terms of device types, a moving asset is either a gateway or sensor (e.g. Logger).
The user interface provides several predefined report templates: sensor value report, which covers all sensors defined for the asset.
Data can be filtered according to time, asset or sensor (1). Customer can save the personalized report for future re-use (2), or export (3) in an Excel, PDF or CSV format for offline use and storage or further distribution. Personalized reports can also be subscribed for automated, timed sending via email.
User can define alarms based on any sensor measurement, for example temperature, location, speed or time. Alert condition may include delay if alert should not be triggered due to single measurement exceeding the set limits. When measurement again returns within acceptable limits, the alert ends. Alert notifications can be delivered through user interface, email or SMS. Active alerts are shown in the side bar (1) and details of the selected alert in the main window (2). Alerts can be listed in a report (3) and exported as PDF document (4).
Adding of users or assets to the system is done by user rights. User rights can be based on role (for example Administrator) or they can be granted in more specifically to certain functions (e.g. alert modification). Each customer company has at least 1 administrator who manages the assets and users according to company policy.
In addition to customer Administrator, Seemoto service administrator has access to customer service view. Seemoto service administrator can also perform functions that are not available at customer level, for example, create new customer service views.
Administrators can also control how other users can see company assets. Users may view only (read-only rights) individual asset(s) or groups, or they may be able to edit the asset properties (write rights) of the assets they have access to.