Energy & utilities

District cooling maintenance software for efficient plants

Mintema is district cooling plant and network maintenance software. Chillers, towers, pumps, pipes and customer stations sit in one register, efficiency is watched live, and equipment is maintained on condition.

All use cases
The challenge

Energy is your largest cost, and the biggest savings hide in one underperforming chiller.

Chillers, towers, pumps and customer stations feed a network under contract. Without live efficiency and one equipment record, a small loss of performance becomes a large energy bill.

Typical assets in scope
ChillersCooling towersPrimary and secondary pumpsThermal storageDistribution pipesValvesEnergy transfer stationsMetersWater treatment
What the operation requires
  • Plant and network structure
  • Live efficiency and temperatures
  • Condition-based maintenance
  • Cooling tower inspections
  • Customer stations and meters
  • Energy and cost reporting
Built in Mintema

How district cooling is configured, step by step

Every part below is configured in the platform without code: the asset type, its structure, the inspection form and scoring, the work, the sensors and the dashboards. Click a step, or let it play.

Illustrative configuration on sample data. Your fields, forms, scales and workflows are designed with your team.

What you use

The modules behind this use case

One platform and one data model, so the inspection, the work order, the spare part, the sensor and the dashboard all refer to the same asset.

Plant monitoring

Efficiency and temperatures live.

Automation

Efficiency drops turned into jobs.

Inspections

Chiller and tower inspections.

Work orders

Condition-based maintenance.

Network map

Pipes and customer stations on the map.

Dashboards

Efficiency and customer delivery.

Business value

What it is worth to the organisation

The value is measured in fewer failures, less wasted effort, lower risk and better use of budget.

How it usually works
With Mintema
01Efficiency
Checked in monthly reports.
Watched live, with alerts.
02Maintenance
Fixed calendar.
Based on condition and performance.
03Customer stations
Visited when someone complains.
Monitored with history.
04Water treatment
Paper logs.
Scheduled jobs with results.
FAQ

District cooling, answered

Have a question that is specific to your organisation? A solution engineer will answer it against your own assets, processes and data.

It records chillers, cooling towers, pumps, pipes and customer energy transfer stations, watches efficiency live, plans maintenance on condition and reports against customer contracts.

Yes. Plant and building control systems can send readings over standard internet protocols, directly or through a gateway.

Yes. Readings are recorded per chiller and rules alert when efficiency drops.

Yes. Energy transfer stations and meters are assets with their own data and history.

Yes. Treatment jobs record results and findings for each cooling tower.

Yes. Power and cooling output post to each chiller, so kW per ton is visible and trends trigger maintenance.

Each station is an asset on the network with its meters, inspections and work history linked to the customer contract.

The modules that matter most here

IoT & devices

Sensors on the assets they measure, with alerts the moment something goes wrong.

 Automation Studio

Routine checks and alerts that run on their own, built without code.

 Work orders

Maintenance that follows your rules, with the right crew, parts and full cost on the asset.
Telecom towers & sites
A WORKING SESSION

District cooling,
configured live.

We will configure this use case on sample data during the call: the asset type, an inspection form with its scoring, a work order type and a rule.

Talk to sales