Skip to content
Industrial hall illustrating an environment for IoT solutions

eMonit Cloud IoT

Custom IoT applications

Need a different report, an integration or support for an unusual device? We develop eMonit around a specific process and agreed requirements.

Describe your project

What can we customise?

We first establish the business need and assess technical options. Scope, cost and delivery dates are confirmed before work begins.

System integrations

Data exchange with ERP, CRM, SAP or other software after analysing available interfaces and access permissions.

Reports and analysis

Custom summaries, printouts and calculations. Data presentation adapted to users and their workflows.

Interface and modules

User views and additional features based on the agreed use case, without assuming an off-the-shelf module exists for every process.

Non-standard devices

Assessment of support for non-standard sensors, control modules and data sources based on their documentation.

Integration does not mean automatic compatibility with every system. We need software versions, interface documentation and a description of the expected data exchange.

First the process, then the solution

The starting point is the existing eMonit system: readings, history, alerts and data presentation. Additional features are designed around the way you work.

  • Clear scopeWe describe what should change, which data is needed and what is outside the project scope.
  • Acceptance criteriaBefore implementation, we agree on test scenarios and how the features will be verified.
  • Post-deployment maintenanceSupport and responsibility for the environment are defined separately to meet the project's needs.
Example eMonit dashboard with a site visualisation and measurements
An example of the current eMonit dashboard, not a mock-up of a custom project.

Environment and maintenance

A new feature also brings requirements for access, infrastructure and ongoing support.

Cloud or intranet

We can assess deployment in an agreed environment, including an intranet. Infrastructure and update arrangements must be defined.

Data access

Permissions, integration accounts and data flows are agreed with the responsible people on the customer's side.

Support scope

Maintenance may include administration, availability monitoring, log analysis, backups and error handling, according to the agreement.

What should you prepare for the discussion?

A description of the problem matters more than a finished technical specification. Do not send passwords, API keys or confidential data in the initial inquiry.

Describe your project
  1. Purpose and users

    Describe your current workflow, the desired change and who will use the solution.

  2. Data and devices

    Identify systems, versions, interfaces, device models and available documentation.

  3. Scope and priorities

    List the key features, target date and maintenance requirements.

Questions before deployment

Do I need a complete specification?

No. A description of the process and problem is enough. During analysis, we will clarify requirements, dependencies and acceptance criteria.

Is ERP or CRM integration available immediately?

Do not assume so. Feasibility depends on the system, version, available interfaces and documentation access. Scope is confirmed after analysis.

Can the solution run on an intranet?

This option requires an individual project. We define server requirements, responsibility for the environment, updates, access and backups.

How do you determine the price and timeline?

After agreeing on scope, dependencies on other systems and required tests. Changes to requirements may affect the quote and schedule.

What does post-deployment support include?

Support scope, response times and responsibilities are agreed for the project. We do not assume that round-the-clock support or unlimited changes are included in the deployment price.

Let us discuss your project

Describe the process you want to improve and the systems you use.

Contact us