EMIKO modules

Extend the platform around the way you operate

Mapper, EasyShare, Warning and Forecast use the assets, permissions and data already available in EMIKO. Add the modules your operation requires without creating a separate system for each need.

One data path, several operational uses

The modules are connected by the same asset and measurement records.

SENSOR Measured value WIND, LEVEL, ENERGY FORECAST Projected value THE SAME SERIES, AHEAD WARNING Threshold crossed EMAIL, PUSH, SMS EASYSHARE Published view LINK OR EMBED MAPPER Where each of these sits, and what it is connected to THE RECORD BEHIND EVERY VALUE ABOVE

Each module can be licensed separately. The shared data model prevents the same equipment and values from being recreated in several disconnected tools.

EMIKO Mapper

Document where assets are installed, what supplies or controls them and which equipment depends on each part of the infrastructure. Use layers, history and attributed updates to keep the operational record current.

EMIKO EasyShare

Share approved readings through a public link or embed them in another website. The recipient sees only the selected asset and values, while the rest of the Partner environment remains private.

EMIKO Warning

Apply thresholds to supported measurements, projected values and equipment states. Send notifications through the configured email, in-platform or SMS channel.

EMIKO Forecast

Display projections for supported WeatherStation and OceanWatcher series alongside the measured history. Use Warning to evaluate thresholds against projected values where enabled.

How one reading travels through the modules

Each step uses the record created by the one before it.

  • Mapper records where the sensor or equipment is installed and what it is connected to
  • Forecast projects supported measured series forward
  • Warning evaluates configured conditions against measured and projected values
  • EasyShare publishes selected current and projected information to an external audience

Add capability as the requirement appears

Partners can begin with the core access, control and metering functions, then add modules when the operational use case is clear.

Book a demo