Start with a specific problem, not a large project.

For management and the staff responsible for daily operations

Shared information, different working views.

Municipal asset management brings together management decisions and the practical work of asset managers, energy managers and technicians. We are developing SmartGovIOT so that these roles can work with interconnected information, each within the scope they need.

Mayor and municipal management

Management needs to know which sites and problems require attention, how important tasks are progressing and what information is available for the next decision.

The shared overview should help set priorities, prepare maintenance and plan renewal. It need not contain every technical detail. What matters is being able to move from a summary to a specific record and check the basis of the information.

Head of the municipal office and office coordination

Coordinating work requires knowing to whom a request was assigned, what has already been done and what is being awaited. A task-status record should reduce the need to repeatedly ask several staff members for the same information.

A traceable process can also help when covering for a colleague or handing over responsibilities. The newly responsible staff member should build on available findings and information, not start the entire process again.

Asset manager

An asset manager needs records of sites, spaces and equipment together with documentation, operational records and deadlines. For a particular building, it should be possible to establish which data is available and what still needs to be added or checked.

This foundation supports preparation for inspections, repairs and information for management. It also helps distinguish currently verified information from older documents describing only the initial condition.

Energy manager or finance officer

For consumption, correct assignment of metering points, available history and data provenance matter. An energy manager or the person responsible for the relevant information can compare periods, investigate deviations and prepare overviews according to the solution's scope.

Consumption and costs represent different perspectives. Connecting them should preserve the meaning of measurements and billing data, not replace the accounting system or a professional energy assessment.

Technical staff and maintenance

A technician needs to know what to do, where the equipment is located and what information is available for the intervention. Documentation, the problem description and the history of previous repairs should be assigned to the correct site.

After the work, it should be possible to record the result and any further action required. The information does not then remain only with the person who was on site.

In a smaller municipality, one person may handle several areas. Dividing roles should therefore not create new jobs or unnecessary administration; it should express actual responsibility and the permissions needed.

When data exists but the connections between it are missing

Documentation may be organised by supplier, consumption by invoice and faults by email message. Each set of records may serve its original purpose, yet combining them into one picture for a particular site may not be easy.

SmartGovIOT is intended to help with precisely these connections. Which device does a service report concern? Does a meter cover the entire building or only part of it? Is a repeatedly reported problem still the same fault?

The aim is not to move everything into a new application without further assessment. We first need to establish which information should be shared, what an existing system already handles reliably and where gaps arise today.

What a municipality should prepare for the first contact

A brief description of the need is more useful than an incomplete technical specification.

State what you need to improve and what outcome you expect. For example, having documentation alongside the correct equipment, tracking unresolved faults or comparing consumption at selected buildings. An explanation of how you carry out the activity today also helps.

Add which sites, devices or areas the request concerns. This need not be a complete list. Naming a selected building, group of metering points or workflow may be sufficient for the initial assessment.

Also state what information and systems you already have: spreadsheets, documentation, meter readings, meters or an existing application. The information need not be complete or perfectly organised. What matters is knowing what exists and who understands it.

A contact person familiar with current operations and able to add practical information is helpful. If you have a priority, deadline or budget framework, provide it as a basis for proposing a proportionate scope.

Simply describe the available information in your first message. Do not send passwords, access credentials or sensitive technical documentation; we will agree on the required scope and handover method afterwards.

How to choose a suitable first step

A good starting point has a clear subject and an outcome that can be verified.

A suitable initial scope need not be the largest or most technically complex. It should address a specific need, have basic information available and have a designated staff member who will help verify its practical usability.

It may involve one building, a selected group of devices, a particular measurement or a fault-resolution process. It is important to define in advance what should be ready on completion and how we will establish that it serves its purpose.

If the main problem is missing equipment identification, records are prepared first. If the equipment is known but measurement history is missing, checking the data source may make sense. Buying new sensors therefore need not be the first step in every project.

How working together proceeds

We begin with a description of the request and an initial assessment. We review its basic scope, the available information and SmartGovIOT's suitability. If something is missing, we identify specific questions instead of making a general request for all documentation.

We then prepare a recommended approach. We propose a consultation when it will help clarify technical conditions, work organisation or responsibilities. Before implementation, the scope, price, cooperation required and evaluation method are agreed.

After introduction or pilot testing, the result is assessed against the agreed objective. The municipality can then decide whether to retain the original scope, adjust it or add further sites and areas.

What the municipality receives at each stage

After the initial assessment

You receive a recommendation on whether and in which direction it makes sense to continue, together with identification of the information and questions needed for the next proposal. If equipment first needs to be checked, records organised or missing data added, we state that as part of the next steps.

The initial assessment of the basic scope and suitability of the solution is free of charge. It does not automatically include preparing a detailed technical design.

When preparing a specific solution

We prepare a recommended scope and distinguish available features, pilot testing and capabilities in development. We clarify the sites concerned, data, integrations and cooperation required.

A quotation and implementation plan follow from the scope defined in this way. They should also explain what is not included, so that expectations do not exceed the agreement.

During implementation and handover

Work proceeds according to the agreed plan. The particular scope defines the necessary checks, how staff will be familiarised with use and the information to be handed over.

The municipality should know what has been introduced, which data has been verified and whether any questions remain open. Access to an application alone does not replace checking that the prepared way of working meets the agreed objective.

When evaluating the pilot

We summarise what was verified, which limitations emerged and what would need further additions. The result may be a recommendation to continue, adjust the approach or not expand the scope for now.

A pilot should help make an informed decision. It is not an automatic commitment to introduce every platform feature.

What getting started can look like in practice

Illustrative situation: technical equipment records for a sports complex

A municipality has a partial equipment list and documentation from several suppliers. When preparing maintenance, however, it is not always clear which device a document belongs to or what was last inspected.

The initial scope therefore focuses on a selected technical part of the complex. Equipment identification is checked, available documents are assigned and missing information is identified. A staff member is designated to update the records and investigate open questions.

One work situation is then worked through within the agreed pilot scope, such as preparing an inspection or recording a fault. This checks whether staff can find the correct equipment and available information and record the result.

Decisions about other parts of the complex or other sites follow only from this experience. Measurements and integrations are added where they provide specific value.

This is an illustrative example of preparing and testing a scope, not a description of a particular customer implementation.

Who will work with the data after introduction

Usable records also need an agreed way of keeping them up to date.

Preparing a solution requires defining who will add a new document, record equipment replacement or close a completed task. Otherwise, even a well-prepared register may gradually diverge from the actual condition.

These responsibilities are set according to the existing organisation of work. Not every user has to edit every data item. It is important to make clear who can confirm information and who will arrange the next steps when something is unclear.

The pilot does not include access for external service personnel. If a supplier carries out an intervention, an authorised member of the organisation's staff receives their supporting material and assigns it to the relevant site or task.

Pricing according to the actual scope

The price of the solution is prepared according to the sites, metering points, devices, integrations and related services it is to include. There is also a difference between processing prepared information and a situation in which data must first be added or checked on site.

The free initial assessment helps identify a suitable direction. More detailed analysis, a site visit, preparation of records, integrations and implementation are handled according to the conditions subsequently agreed.

Expansion is decided separately. Even a smaller solution may remain the final scope if it meets the municipality's need.

Does your municipality have a specific problem or request?

Tell us what you need to address, which sites or areas it concerns and what outcome you expect. You do not need to know the right combination of features or prepare technical connections.

We first assess the request. If additional information is needed, we will identify specific questions and propose the next steps. The scope and conditions of any implementation will be agreed separately.

Describe your requirements · View solutions

Alternative contact: info@smartgov.sk

Existing customers can send their requests to support@smartgov.sk.