Selection criteria for energy management software

Choosing energy management software is not just about dashboard aesthetics; OSOS integration is the combined evaluation of invoice verification, multi-site scalability and regulation reporting capacity. In 2026, the energy expense share in electricity consumption, which constitutes approximately half of industrial facilities, will remain in the range of 5-20%; the right software makes this expense visible and manageable. This guide provides category-based testable criteria without naming the product.

Why is OSOS integration the first criterion?

OSOS integration means that the software automatically retrieves the distribution company meter data and provides a 15-minute or hourly profile; Without this, reactive penalty and demand management will remain after the invoice. Test: live data stream with at least one real installation, reactive ratio calculation (9 kW exemption, 33%/20% or 20%/15% limits) and demand profile must be displayed. The fundamental role of OSOS is detailed in our guide to Energy Use Measurement in Industry. The integration architecture is summarized on our OSOS consumption monitoring page.

How to test invoice verification capacity?

Invoice verification is the automatic comparison of OSOS consumption data and invoice items (active kWh, unit price, reactive, demand). Test: upload past period invoice; The system should display the kWh deviation and unit price difference on an item basis. For free consumer subscribers, the expected unit price calculation should be supported with the formula (PTF+YEKDEM)×KBK. The tariff transition effect should be monitored for subscribers with SKTT limit of 15,000 kWh/year (industry). It also produces an automated process audit trail compared to manual Excel reconciliation.

In what scenarios is multi-site support required?

Multi-facility support is the management of dozens of subscriber numbers in a single panel in chain stores, OIZs, municipalities or holding structures. Testing: Subscriber inventory, central reconciliation and deviation ranking should work in a demo environment with at least 10 installations. multi-line production scenario in our industrial energy management solutions; Organized industrial zone portfolio structure is exemplified on our OIZ energy management page. Single site software does not scale across a multi-subscriber portfolio — a separate Excel file for each site creates operational risk.

Why are SPP and production monitoring evaluated separately?

SPP and production monitoring requires a different data source (inverter, SCADA, offset) from the consumption software. Test: production kWh, self-consumption rate and energy supplied to the grid should be displayed separately; Production-consumption matching should be supported in post-hourly settlement periods. Consumption-only software does not show the bill effect of the solar energy investment. Platforms with solar energy production monitoring modules combine consumption and production in a single graph.

How to verify reporting and EIVER compliance?

Reporting and EİVER compliance means the ability to transfer energy consumption data to reporting (EİVER, energy audit) formats within the scope of the Energy Efficiency Law. Test: annual consumption summary, industry benchmark metrics (kWh/product, kWh/m²) and export formats (Excel, PDF) should be checked. The liability calendar in our Energy Audit and EIVER guide must be matched with the reporting module. Data infrastructure is essential for the PDCA cycle in our ISO 50001 Energy Management System guide.

What should the alarm and warning system offer?

The alarm system should produce proactive notifications for reactive limit approach, demand exceedance, abnormal consumption increase and SKTT limit proximity. Test: threshold values ​​should be adjustable on a facility basis; Email or panel notification should work without delay. Reactive penalty limits (9 kW exemption, 33%/20%) must be monitored live — the opportunity to intervene without invoicing is provided with these alarms. A live alert instead of a static report determines the operational value of energy management.

Why is data ownership and integration flexibility important?

Data ownership includes the export of your consumption and billing data, API access and data portability at the end of the contract. Test: raw OSOS export, invoice archive and calculation logs should be downloadable; API connection to third-party ERP or BI tool should be possible. Closed ecosystem software poses a risk of addiction in the long term. In our TEP calculation tool, energy unit conversion works independently; Similar clear calculation logic should be sought in software selection.

What is the difference between integrated platforms and general EMS software?

General EMS (Energy Management System) software offers ISO 50001 focused policy, target and documentation management; OSOS and invoice reconciliation generally require separate modules or integrations. Integrated platforms combine consumption, invoice, SPP and supply data in a single panel. The choice depends on your needs: if you are only aiming for ISO 50001 certification, EMS may be sufficient; If invoice reconciliation and OSOS live monitoring are priorities, an integrated platform is preferred. In both categories, evaluate by capability matrix rather than product name.

How is the selection process structured?

The software selection process proceeds in four stages: (1) needs map — how many facilities, is there OSOS, is there SPP, is there EIVER obligation; (2) shortlist — skill matching with the table in this guide; (3) pilot — 30 days of live testing with at least one real installation; (4) contract — data ownership, SLA and price model. Reactive alarm, invoice reconciliation and multi-site ranking should be tested during the pilot phase. Sector-based usage scenarios can be viewed on our References page.

Why should the procurement and portfolio module be considered in selection?

For eligible consumer subscribers, the supply decision (bilateral agreement, SKTT risk, PTF+YEKDEM projection) should be evaluated together with operational consumption data. If there is a supply module in the software, SKTT limit (industry 15,000 kWh/year) monitoring, contract renewal calendar and portfolio-based cost scenario work in a single panel. OSOS platforms without a procurement module show consumption, but you need to go out for procurement cost projection. In our energy supplier software solution, portfolio and consumption are handled together.

How to measure user experience and training cost?

User experience means the field operator can use the dashboard on a daily basis — complex dashboard increases training cost. Test: Give a user who is not an energy engineer the task of drawing basic reports and interpreting alarms after 30 minutes of training. Mobile access, Turkish interface and tr-TR date/number format should be considered mandatory in Türkiye operations. Training time and support response time should be included in the total cost of ownership.

What are the security and data hosting criteria?

Energy consumption data is a trade secret; Data hosting location, encryption, backup and access logs should be evaluated when choosing software. Testing: data export, API key management and role-based access (RBAC) should be checked. A data portability clause should be mandatory at the end of the contract — it is the legal equivalent of the data ownership criterion. In public and holding tenders, KVKK compliance and audit trail are also questioned.

Pilot evaluation checklist

• OSOS live data: 15 min profile, reactive rate, demand viewing.
• Invoice reconciliation: historical invoice loading, kWh and unit price deviation.
• Reactive alarm: notification on limit approach (9 kW exemption, 33%/20%).
• Multi-facility: 10+ subscriber inventory and deviation ranking.
• SPP (if available): production-consumption combined chart.
• Reporting: EIVER/ISO 50001 format export.
• Data export: raw OSOS and invoice archive download.

Common selection mistakes and how to avoid them?

Five common mistakes: (1) price comparison only — no TCO calculation; (2) decision with demo data — skipping actual installation pilot; (3) contract without OSOS testing — failure to verify live data stream; (4) ignoring the need for multiple facilities — portfolio management with a single facility license; (5) data ownership clause missing — data lock at contract end. Each of these mistakes can be prevented with the pilot checklist and TCO chart. Sector-based usage scenarios can be viewed on our References page.

How to define support and SLA expectations?

When choosing software, support quality is as important as technical ability. Within the scope of SLA, response time, response to OSOS disconnection and update frequency should be questioned. For critical alarms (reactive limit, demand exceedance), 24/7 support or a guaranteed response time within at least business hours should be defined.

Integration API and ecosystem compatibility

Integration with your existing ERP, accounting or BI tools should be possible via API. Test: Can consumption and billing data be captured via REST or webhook? Is SCADA or inverter data (if there is SPP) on the same platform? Closed systems create data silos in the long run. Open API and standard export formats (CSV, Excel, JSON) are the technical equivalent of the data ownership criterion. Inverter integration is exemplified in our solar power generation monitoring module.

Conclusion

Energy management software selection should be based on testable criteria centered on OSOS integration and bill verification. Multi-site, SPP, EIVER reporting, alarms and data ownership are not secondary — they are operational requirements. Category-based evaluation without naming the product both reduces legal risk and provides objective comparison. Convert the table in this guide into a scoring matrix before the election.