We put Excel + the OSOS portal, SCADA / building automation and energy monitoring software side by side on 11 criteria. An approach comparison, not a brand comparison, with 10 questions to ask before you buy.
Facilities track energy consumption in one of three ways today: following bills and the distribution company's OSOS portal in Excel, looking at the site's SCADA or building automation system, or using consumption-focused energy monitoring software (EMS). Each is strong at one job; trouble starts when the wrong tool is picked for the job.
This is not a brand comparison; we name no competitors and quote no competitor prices. The criteria are kept objective, and the 6S Teknoloji column lists only what the platform does today. Pricing details are on the pricing page, the full platform on the energy monitoring system page.
Each row is a topic to raise during purchasing. The SCADA column describes typical installations; individual projects may differ.
| Criterion | Excel + OSOS Portal | SCADA / Building Automation | Energy Monitoring Software (6S Teknoloji) |
|---|---|---|---|
| Data frequency | Monthly bill; OSOS load profile delayed on the portal | Real time, on the operator screen | Read interval configured per site; hourly and daily summaries stored |
| ₺ reporting | Calculated by hand | Usually none; kWh and kW focused | Consumption converted to ₺ with the tariff, month-end budget projection |
| Electricity + water + gas | Separate bills, separate files | Mostly electrical and mechanical; water and gas need extra integration | All three energy types on one panel |
| Warning before the bill | None; problems show up on the bill | Threshold alarms, no billing context | Early alarms for reactive ratio, peak demand and budget deviation |
| Tenant allocation | Manual spreadsheet | Usually out of scope | Sub-tenant billing from sub-meters |
| Meters read | Only the distribution company's main meter | Devices wired into the project | Modbus TCP/RTU, M-Bus, BACnet/IP, MQTT; BEDAŞ OSOS and İGDAŞ AVE integration |
| Explainable alarms | None | "Threshold exceeded" only | Rule-based alarms with the cause and the related measurement |
| When the connection drops | Not applicable (monthly data) | Depends on local logging setup | Queue + ACK on the field box, at least a 30-day buffer, zero data loss |
| Mobile access | File sharing | Mostly a local screen; remote access via VPN | Web and mobile, role-based permissions |
| Deployment model | No installation, ongoing manual effort | Project-based engineering, on-site server | Cloud + field box; on-site installation can also be evaluated |
| Pricing model | No license; cost is staff time | Project + license + maintenance contract | Quote based on site and device scale |
Whatever software you evaluate, ask for clear written answers to these questions.
What the distribution company portal has and lacks: the what is OSOS article and the cross-check logic.
How analyzers and meters are read: energy monitoring with Modbus.
When the connection drops, readings wait on the field box: data assurance.
Allocating consumption from sub-meters to tenants: sub-tenant billing.
Explore the system with your own data in a demo session.